64-bit Guests don't work after 2.2 upgrade

[Zrax]

I have two 64-bit guests I had been using on 2.1.4, namely a Vista SP1 and an Ubuntu 9.04 machine, but since I updated to 2.2.0, both fail to start with a Guru Meditation message right after loading the guest kernel. As far as I can tell, all of my 32-bit guests are still working fine. I'm running Vista 32-bit as my host OS, and I did make sure that the AMD-v option was still enabled for both machines. Should I have removed the VBox extensions before updating?

[Zrax]

The 64-bit Ubuntu LiveCD is doing the same thing, so I guess it's nothing to do with the VBox extensions. Anyone have any ideas/suggestions?

[sunandwavs]

I'm running Vista x64 for host with Fedora 10 x64 as guest. After installation of 2.2, I had network errors. After a Repair install, everything is running fine now. If you rerun the 2.2 installation .exe file it will present an option of Repair. Select it and follow through until the host reboot has completed. This may help your issue.

[Zrax]

Thanks for the suggestion. I originally had this problem when I first installed 2.2 also, but re-running the installer a third time still doesn't seem to have fixed my issue.

The whole log seems too large to post here, but the point where the Ubuntu machine seems to be failing has the following log lines:

Code: Select all

00:00:07.263 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'.
00:00:07.297 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=088d0000 w=1024 h=768 bpp=16 cbLine=0x800
00:00:07.298 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={09789f63-4525-48e5-a5e4-1080453b0eab} aComponent={Display} aText={Could not take a screenshot (VERR_BUFFER_OVERFLOW)} aWarning=false, preserve=false
00:00:11.090 Console::powerDown(): A request to power off the VM has been issued (mMachineState=6, InUninit=0)
00:00:11.126 Changing the VM state from 'GURU_MEDITATION' to 'OFF'.
00:00:11.161 Changing the VM state from 'OFF' to 'DESTROYING'.

I've searched for the VBOX_E_IPRT_ERROR on these forums, but most of them seem to point to freezing problems in older builds, not to Guru Meditations.


EDIT: Sorry, I guess the actual error is a bit earlier than that:

Code: Select all

00:00:03.977 Guest Log: BIOS: Boot from Floppy 0 failed
00:00:03.978 Guest Log: BIOS: CDROM boot failure code : 0003
00:00:03.978 Guest Log: BIOS: Boot from CD-ROM failed
00:00:03.978 Guest Log: BIOS: Booting from Hard Disk...
00:00:03.979 PIIX3 ATA: Ctl#0: RESET, DevSel=0 AIOIf=0 CmdIf0=0x20 (-1 usec ago) CmdIf1=0x00 (-1 usec ago)
00:00:03.979 PIIX3 ATA: Ctl#0: finished processing RESET
00:00:04.013 PIIX3 ATA: Ctl#0: RESET, DevSel=0 AIOIf=0 CmdIf0=0x20 (-1 usec ago) CmdIf1=0x00 (-1 usec ago)
00:00:04.013 PIIX3 ATA: Ctl#0: finished processing RESET
00:00:06.221 Guest Log: BIOS: *** int 15h function AX=ec00, BX=0002 not yet supported!
00:00:06.221 Guest Log: BIOS: KBD: unsupported int 16h function 03
00:00:06.258 
00:00:06.258 !!R0-Assertion Failed!!
00:00:06.258 Expression: pPage && pPage->enmKind != PGMPOOLKIND_FREE
00:00:06.258 Location  : E:/tinderbox/win-rel/src/VBox/VMM\PGMInternal.h(4274) pgmPoolGetPage
00:00:06.258 HCPhys=000000005660c000 pPage=00000000 idx=0
00:00:06.258 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:00:06.258 !!
00:00:06.258 !!                 Guru Meditation -2701 (VERR_VMM_RING0_ASSERTION)
00:00:06.258 !!
00:00:06.258 !!R0-Assertion Failed!!
00:00:06.258 Expression: pPage && pPage->enmKind != PGMPOOLKIND_FREE
00:00:06.258 Location  : E:/tinderbox/win-rel/src/VBox/VMM\PGMInternal.h(4274) pgmPoolGetPage
00:00:06.258 HCPhys=000000005660c000 pPage=00000000 idx=0
00:00:06.258 !!
00:00:06.258 !! ACTIVE TRAP=0e ERRCD=0000000000000006 CR2=0000000000e89000 PC=0000000000100105 Type=0 (Guest!)
00:00:06.258 
00:00:06.258 !!
00:00:06.258 !! {mappings, <NULL>}
00:00:06.258 !!

The entire logs, if anyone's brave enough to read the whole thing, are on pastebin now:
Ubuntu x64: http://pastebin.com/m1cf36610
Vista x64: http://pastebin.com/m4b3ea0a2

Thanks again

[sunandwavs]

Is either SATA or VT-x enabled?

[Zrax]

SATA isn't enabled on either machine, but AMD-V is enabled on both.

[sunandwavs]

After searching VB bug tickets and forums, a shot in the dark is to disable AMD-V and USB (if enabled). If this doesn't help, please open a bug ticket.

As a side-note, the origins of this error text is from a 1980's game console called Amiga http://en.wikipedia.org/wiki/Guru_Meditation#Origins

[Zrax]

USB is also not enabled on either machine, and as much as I'd love to try turning off AMD-V, my host OS is 32-bit, so I don't see that helping much . Both machines worked before on 2.1.4, and I haven't changed any configuration on them since the update (except of course for the automatic config changes that the updater makes)

[Zrax]

After updating to 2.2.2, they still weren't working, but when I disabled nested paging, they started working again... My CPU should support nested paging (and the 32-bit guests work fine with nested paging enabled), but as long as I have my machines working, I won't complain too much . Thanks for the help

[borrisl]

I have the same problem with a new Puma AMD Turion CPU. I believe this is a common problem. The problem is with the AMD-V enabled. It would be nice if this was one of the next bugs fixed.

[frank]

Zrax, can you tell me your exact host CPU?

[borrisl]

AMD ZM-82 and ZM-86 New Turion Ultra X2 or "Puma" CPU

It doesn't seem that many people are completely shut down with this problem like myself. All my Solaris guests are completely useless at this point. Where this proplem started to rear its head is on the 2.2 release and AMD processors. Which happens to be my primary development platform. I would run them in software mode, but 2.2.2 does not allow 64 bit guests to run in that mode. When AMD-V is enabled all 64 bit guest (except Ubuntu 9.04 64bit) crash, fail to start, or are put in a continual loop of reboots.

I see a bug ticket issued, but just wish I knew more so I could get involved with the development side.

[borrisl]

Hahah!!!! I have a temporary work around:

If you edit your machine.xml file and change the virtualization to "false" from "true" it does work. You will get a error message when you boot the guest but it will work.

You can not turn off the virtualization mode in the interface directly because 2.2.2 won't allow that operation on 64 bit guests. That is why you would have to disable it manually. I'm not sure what the implications are, other than the guest is much slower, it does still work. Hope a remedy is somewhere soon.

[frank]

If you disable VT-x for such a 64-bit guest then the guest will be definitley not run in 64-bit mode. Solaris usually detects if the processor is 64-bit capable and will start in 32-bit mode if not.

[borrisl]

If you disable VT-x for such a 64-bit guest then the guest will be definitley not run in 64-bit mode. Solaris usually detects if the processor is 64-bit capable and will start in 32-bit mode if not.

I see... Dang, I had hoped I found a work around. Guess not.