I'm not familiar enough with virtualbox to provide a walkthrough. But .iso files are want you want to start with. Then you run the setup in virtualbox and it will create a format specific to virtualbox called .vdi that the program then uses. Simply renaming the files will not work (one can always do trial and error to test that). One would need to go through the setup to get a .vdi file.
Information on iso files http://www.virtualbox.org/manual/ch03.html#guestossupport information on the setup http://www.virtualbox.org/manual/ch01.html#gui-createvm There are a lot more documentation files available online. Getting a non-supported guest operating system running will take a bit of playing around. On Nov 7, 2010, at 9:50 AM, Caryl Bigenho wrote: > Hi All, > > I have included the testing list in this mailing because solving this problem > will help me (and other Mac users) participate in testing SoaS. ;-D > > Still trying to get SoaS to run on Virtual Box. Need to do it today > (hopefully). Will keep checking and trying off and on all day until I get it. > Here is my first question... > > I currently have several virtual machines I have installed in Virtual Box. > Only 2 out of the 5 will run. They are both ".vdi" files. The rest are ".iso" > files. Does a file need to be labeled ".vdi" to work? If that is the case, > will renaming an .iso file at the time of downloading to .vdi, do the trick? > > Thanks, > > Caryl > _______________________________________________ > IAEP -- It's An Education Project (not a laptop project!) > [email protected] > http://lists.sugarlabs.org/listinfo/iaep
_______________________________________________ Testing mailing list [email protected] http://lists.laptop.org/listinfo/testing
