Page 1 of 1

vbox gui stopped working for eeepc vhd/vmdk in vista

Posted: 12. Jun 2009, 23:44
by manyone
i managed to obtain vhd and vmdk images for eeepc xandros (i couldnt find any vdi's) and they work well inside virtualpc and vmware player respectively but when i try them inside vbox (2.2.4 in vista 32bit), i get the splash screen ("starting..."), a blank screen, then the "vobx gui stopped working" message.

i've tried reinstalling and running vbox as administrator but i got the same results.

i know vbox can read vhd or vmdk directly - i've proven by running a vhd image of puppy linux inside vbox successfully (after tweaking with xvesa to fix the first garbled desktop).

help!
thanks

Re: vbox gui stopped working for eeepc vhd/vmdk in vista

Posted: 13. Jun 2009, 00:30
by Perryg
Welcome to the forum manyone,

A few questions for you:

Are they 32 or 64 bit copies and do they match your system?
Do you know what the settings are supposed to be set to in VBox?
If you have the vdmk do you also have the ovf file to import it into VBox?
Also if the vdmk came from vmware did you/they remove the vmware guest additions?

Re: vbox gui stopped working for eeepc vhd/vmdk in vista

Posted: 13. Jun 2009, 08:17
by manyone
i misspoke - the vhd under vbox goes as far as the splash screen but the vmdk doesn't get that far. it shows the grub menu, blank screen then error message.

my host is win vista 32bit - i'm assuming these images are for 32bit (after all the vmdk runs in the vmplayer in my machine) and my settings at this point are default/typical (ie. 256mb ram, 12mb video, 8gb disk, etc). i didn't see any vfo file associated with the vmdk - here are the items in the vmdk folder (vmdk, nvram, vmsd, vmx, vmxf)

after the error, here's the last part of the log

(-1 usec ago)
00:00:06.109 PIIX3 ATA: Ctl#0: finished processing RESET
00:00:06.256 PIIX3 ATA: Ctl#0: RESET, DevSel=0 AIOIf=0 CmdIf0=0x20 (-1 usec ago) CmdIf1=0x00 (-1 usec ago)
00:00:06.256 PIIX3 ATA: Ctl#0: finished processing RESET
00:00:16.832 Guest Log: BIOS: KBD: unsupported int 16h function 03
00:00:16.836 Guest Log: BIOS: int13_harddisk: function 02, parameters out of range 0000/0000/0001!
00:00:16.846 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=069d0000 w=640 h=480 bpp=16 cbLine=0x500
00:00:21.073 PIT: mode=2 count=0x2e9c (11932) - 99.99 Hz (ch=0)
00:00:24.561 PATM: Disabling IDT 14 patch handler c034223c
00:00:24.565 PATM: Disable block at c035eb90 - write c035ec00-c035ec04
00:00:28.584
00:00:28.584 !!Assertion Failed!!
00:00:28.584 Expression: <NULL>
00:00:28.584 Location : C:\vbox\branch\win-2.2\src\VBox\VMM\VMMAll\PGMAllPool.cpp(2538) pgmPoolTrackFlushGCPhysPTInt
00:00:28.584 cRefs=1 iFirstPresent=112 cPresent=17 u64=196ca001

thanks for looking

Re: vbox gui stopped working for eeepc vhd/vmdk in vista

Posted: 13. Jun 2009, 08:18
by manyone
. . . also, i cannot tell if the vmdk contains guest additions or not. (how would i add them in vbox if i can't boot?).
thanks again

Re: vbox gui stopped working for eeepc vhd/vmdk in vista

Posted: 13. Jun 2009, 14:56
by Perryg
I know that the last time I tried to load a VHD that I had created in VPC it failed and I had to open it back up in VPC and uninstall the Additions before I could get it to load in VBox. I can not say about the VDMK because I do not have VMWare, but it stands to reason that it too would need the additions removed.

Re: vbox gui stopped working for eeepc vhd/vmdk in vista

Posted: 13. Jun 2009, 21:11
by manyone
... when i start the xandros vmdk from inside vbox i get a grub menu and i edited the first (default) called "vdevel (nounionfs)" and got this console

grub edit> kernel /boot/vmlinuz-2.6.21.4-vmware quiet rw vga=785 root=301 init=/sbin/fastinit

can i insert some extra parameters to fix my gui problem or maybe to start from some kind of safe mode? help!

Re: vbox gui stopped working for eeepc vhd/vmdk in vista

Posted: 13. Jun 2009, 21:23
by Perryg
I really don't know if that would help. It stems more to the fact that the additions are in there and not compatible with VBox. Is there no way that you can get the stripped down version? This will probably be addressed in future versions but since this whole import thing is so new it tends to have its problems. IMHO