VirtualBox

Ticket #5058 (reopened defect)

Opened 2 months ago

Last modified 1 week ago

Windows guest crashes on Linux host if VT-x/AMD-V enabled

Reported by: f.hoefling Assigned to:
Priority: major Component: other
Version: VirtualBox 3.0.8 Keywords: VT-x/AMD-V
Cc: Guest type: Windows
Host type: Linux

Description

Booting Windows XP Prof. (32 bit) in Virtualbox 3.0.6 with VT-x/AMD-V results in a crash of the virtual machine. The problem is solved by disabeling the VT-x/AMD-V option.

Booting and running memtest86 with the same configuration works without problems.

Host configuration: Ubuntu Linux (Jaunty, kernel 2.6.28), AMD PhenomII X4. Virtualization is enabled in the Bios.

Attachments

VBox.png (0.9 kB) - added by f.hoefling on 2009-09-22 14:04:00.
Log file
VBox.log (114.4 kB) - added by f.hoefling on 2009-09-22 14:04:22.
Log file
VBox.log.1 (129.9 kB) - added by f.hoefling on 2009-10-07 10:38:51.
Log file for version 3.0.8 with VT-x/AMD-V enabled
VBox.2.log (43.7 kB) - added by f.hoefling on 2009-10-07 11:14:57.
Log file for version 3.0.8 with VT-x/AMD-V disabled
2009-10-23-20-16-03.060-VirtualBox-9999.log (267 bytes) - added by carlesgs on 2009-10-23 22:19:25.
Log "fatal error in recompiler cpu"
VBox6.log (115.7 kB) - added by carlesgs on 2009-10-23 22:22:02.
Full log in .virtualbox

Change History

2009-09-22 14:04:00 changed by f.hoefling

  • attachment VBox.png added.

Log file

2009-09-22 14:04:22 changed by f.hoefling

  • attachment VBox.log added.

Log file

2009-09-22 14:06:01 changed by f.hoefling

the relevant error message might be this:

fatal error in recompiler cpu: triple fault

2009-09-22 16:42:53 changed by sandervl73

  • summary changed from Windows guest crashes on Linux host if VT-x/AMD-V enabled to Windows guest crashes on Linux host if VT-x/AMD-V enabled -> fixed in SVN/3.0.8.

Right and I happened to be working on a similar bug. Fixed now.

2009-10-06 10:25:05 changed by sandervl73

  • status changed from new to closed.
  • resolution set to fixed.

2009-10-07 10:38:51 changed by f.hoefling

  • attachment VBox.log.1 added.

Log file for version 3.0.8 with VT-x/AMD-V enabled

2009-10-07 10:39:21 changed by f.hoefling

  • status changed from closed to reopened.
  • resolution deleted.

The bug persists in version 3.0.8.

I've updated to virtualbox-3.0_3.0.8-53138_Ubuntu_jaunty, enabled the VT-x/AMD-V option, and Windows still crashes.

2009-10-07 10:59:54 changed by sandervl73

  • version changed from VirtualBox 3.0.6 to VirtualBox 3.0.8.

Which service pack level of Windows XP? Any unusual programs installed (virus scanners)?

2009-10-07 11:12:44 changed by f.hoefling

Thanks for the quick reply. I'm running Windows XP Prof. SP3. The crash occurs during the boot procedure, presumably when Windows switches to graphics mode for the first time. (When the Windows logo appears.) Before, I can select the hardware configuration (text mode). I'm booting from a raw disk (AHCI) - not sure, whether this makes a difference.

My graphics card is nVidia GeForce? 8500 GT. The VM has 48 MB graphics memory and 3D acceleration enabled.

For comparison, I have attached the log-file without the VT-x/AMD-V option.

2009-10-07 11:14:57 changed by f.hoefling

  • attachment VBox.2.log added.

Log file for version 3.0.8 with VT-x/AMD-V disabled

2009-10-09 14:35:21 changed by sandervl73

  • summary changed from Windows guest crashes on Linux host if VT-x/AMD-V enabled -> fixed in SVN/3.0.8 to Windows guest crashes on Linux host if VT-x/AMD-V enabled.

2009-10-09 14:41:27 changed by sandervl73

Did you install SATA drivers in the VM?

2009-10-09 15:12:06 changed by f.hoefling

The disks are running in SATA mode, and I've installed SATA drivers in the native boot configuration of Windows.

In the VM, I can't find that SATA drivers are installed. But there is an unconfigured PCI device: 0x2829 AHCI Controller 0x8086 Intel Corporation

2009-10-09 16:09:40 changed by f.hoefling

I've updated the Virtualbox GuestAdditions?, but nothing has changed.

I've installed the driver for the Intel AHCI controller, no change - it still crashes with virtualization enabled.

2009-10-14 15:43:14 changed by carlesgs

Confirm the situation in Virtualbox 3.0.8 and earlier. If enabled VT-x/AMD-V on a disk with two installations, windows xp professional sp3 and Linux, when Windows starts we get the following error: fatal error in recompiler cpu: triple fault

If not enabled the VT-x/AMD-V, windows xp working properly. This error occurs both with a virtual IDE and SATA disk. I think the system can not access the NTFS partition of wind, and therefore, load the NT loader.

Excuse my poor English

Thanks

2009-10-23 22:19:25 changed by carlesgs

  • attachment 2009-10-23-20-16-03.060-VirtualBox-9999.log added.

Log "fatal error in recompiler cpu"

2009-10-23 22:22:02 changed by carlesgs

  • attachment VBox6.log added.

Full log in .virtualbox

(follow-up: ↓ 13 ) 2009-10-25 05:11:09 changed by kaatmanduu

I was experiencing the same issue, XP would crash with VT-x/AMD-V enabled, and boot without it. I installed the Intel SATA drivers from http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=17882&lang=eng, and I can boot with VT-x/AMD-V enabled. I now have a multi-processor enabled guest, very nice!

(in reply to: ↑ 12 ) 2009-10-27 10:03:28 changed by f.hoefling

Replying to kaatmanduu:

I was experiencing the same issue, XP would crash with VT-x/AMD-V enabled, and boot without it. I installed the Intel SATA drivers from http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=17882&lang=eng, and I can boot with VT-x/AMD-V enabled. I now have a multi-processor enabled guest, very nice!

I just wanted to confirm that the Intel driver (version 8.9.0.1023) doesn't solve the problem for me - but big surprise! Now it works for me too, even with 2 processors enabled :-) But I don't know why.

I'd installed the Intel driver already two weeks ago, and it kept crashing. (See my previous post.) The only thing I've changed since is that Windows boots directly with its standard boot loader, not via Grub. (I'm using raw disk access with "virtual" MBR.)

(follow-up: ↓ 15 ) 2009-10-27 12:32:42 changed by carlesgs

Replying to kaatmanduu:

From the Windows MBR bootloader starts correctly with VT-X enabled or not enabled. With GRUB starts well without VT-X enabled, with VT-X enabled does not start. Linux works always with or without VT-X from GRUB.

Greetings

(in reply to: ↑ 14 ) 2009-10-29 00:37:36 changed by kaatmanduu

Replying to carlesgs:

From the Windows MBR bootloader starts correctly with VT-X enabled or not enabled. With GRUB starts well without VT-X enabled, with VT-X enabled does not start.

I'd changed to use the native Windows boot loader a few days before I installed the drivers. It never occurred to me that this might have an affect on a crash that late in the boot process. I booted using grub, and XP indeed crashes again when AMD-V is enabled.

2009-10-29 17:47:23 changed by carlesgs

I confirm that this error occurs in the new version 3.0.10

2009-10-29 21:00:52 changed by carlesgs

This error occurs in grub, grub2 and lilo, confirmed and tested

2009-11-02 18:58:35 changed by carlesgs

Even if the computer does not have a processor with hardware virtualization, grub can not boot windows xp with enabled VT-x extension. If this extension is not enabled, it starts correctly.

Curious ...

2009-11-03 22:36:30 changed by schabi

I can also reproduce that problem here in 3.10 - it also happened with the 3.0.6 OSE edition coming with debian. I can assist in debugging (provide logfiles, doing diagnostics etc.) if wanted.

As non-virtualized booting is unconsiderably slow, I'll try to find out infos about the direct boot (virtual mbr) mentioned here.

2009-11-11 21:22:55 changed by carlesgs

The error also occurs in version 3.1.0 beta

© 2009 Sun Microsystems, Inc.
Contact – Privacy policy