Hi,
today I deliver a moose one-click image downloaded from the moose ci and the vm was crashing on start. the OS was Windows 7 64-bit. Any idea / know problem? Cheers, Fabrizio _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
No. I can take a look on Monday.
Doru On 16 Nov 2012, at 18:09, Fabrizio Perin <[hidden email]> wrote: > Hi, > today I deliver a moose one-click image downloaded from the moose ci and the vm was crashing on start. the OS was Windows 7 64-bit. > Any idea / know problem? > > Cheers, > Fabrizio > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- www.tudorgirba.com "Speaking louder won't make the point worthier." _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Hi,
I think the problem is the size of the image. By simply downloading a fresh image from the moose jenkins server it open under windows with no problems. If I try to open a image 360MB big an out of memory error message appear. Is this a know problem or my image is corrupted? Cheers, fabrizio 2012/11/16 Tudor Girba <[hidden email]> No. I can take a look on Monday. _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Unfortunately, this is a known issue. It is unclear whether the number of objects or the size of the image is the problem. I have the problem.
However, in my experience, when you save Moose images of more than 300Mb on a Windows Server, they get corrupted. However, on a Windows7, it seems I can work with larger images.
Cheers, Doru On Sat, Nov 17, 2012 at 11:53 AM, Fabrizio Perin <[hidden email]> wrote: Hi, "Every thing has its own flow" _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Hi,
I tried to setup the same image I had under mac in windows 7 and it works. So, same image, same model loaded, and so same image size, but everything done and saved under windows and it works. The problem than seems to be some sort of incompatibility between how the image is saved under mac and loaded in windows. Which are the OS dependent factors involved in saving or loading an image? Cheers, Fabrizio 2012/11/19 Tudor Girba <[hidden email]> Unfortunately, this is a known issue. It is unclear whether the number of objects or the size of the image is the problem. I have the problem. _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
The problem is the Windows VM, not the image. So, as long as you build the image on Windows, there isn't much you can do.
But, the good news is that the image does not crash while it is created actually. So, you can still run the exporter to Hudson.
So, what I do is to export the XML report, and when I need to take a look at the live image, I load the MSE file again. Ideally, I want to do it via FuelMoose, but this is broken these days, too.
Cheers, Doru On Mon, Nov 19, 2012 at 12:47 PM, Fabrizio Perin <[hidden email]> wrote: Hi, "Every thing has its own flow" _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Free forum by Nabble | Edit this page |