VirtualBox

Ticket #4988 (closed defect: wontfix)

Opened 11 months ago

Last modified 6 months ago

System reboot or freeze when AMD-V enabled -> BIOS lacks workaround for known AMD errata (Dell D531 Latitude)

Reported by: bepla Assigned to:
Priority: blocker Component: VMM/HWACCM
Version: VirtualBox 3.0.8 Keywords: amd-v reboot freeze
Cc: Guest type: Windows
Host type: Linux

Description

I encounter system reboots or freezes when AMD-V is enabled. It happens on both Win XP and Linux hosts on the same Dell computer Latitude D531 with up to date bios. I noticed this problem many versions ago (before 3.x) but seems not to be solved or coming from my hardware... VirtualBox log joined.

Attachments

VBox.log (36.0 kB) - added by bepla on 2009-09-14 10:53:23.
20091109VBOXLOG.txt (33.1 kB) - added by zaimor on 2009-11-09 11:33:13.
Dell D531 BIOS A08 XP Host Ubuntu Guest VB 3.0.10 Hard Host Reset

Change History

2009-09-14 10:53:23 changed by bepla

  • attachment VBox.log added.

2009-09-14 10:55:58 changed by bepla

By the way, I run no other virtualization software in the same time...

(follow-up: ↓ 5 ) 2009-09-18 13:45:22 changed by sandervl73

All guests and when does it occur? (almost) immediately during guest boot or a bit later?

2009-09-18 15:19:52 changed by gligli

I think i've got the same problem, ie host freeze or reboot. For me, it happens when the guest tries to switch to 64-bit mode (during the guest OS kernel boot) Host: Core 2 Duo on Windows XP 32bit with VT-x enabled. Guest: I tried Vista 64bit and Linux Debian Amd64.

PS: I also have VMWare Professional 6.5.2 installed, and no crash on 64bit guest OS with it.

2009-09-22 10:43:02 changed by ktchv

I have same problem. Logs attached to 4778

(in reply to: ↑ 2 ) 2009-09-23 09:04:57 changed by ktchv

Replying to sandervl73:

All guests and when does it occur? (almost) immediately during guest boot or a bit later?

almost immediately. 50-100 ms

2009-10-07 11:30:24 changed by bepla

I just tried 3.0.8 today and still same problem... It hangs/reboot just after VirtualBox Splash Screen...

2009-10-07 12:10:18 changed by sandervl73

gligli: Your problem is different. do not use 64 bits guests on your 32 bits Windows when this happens.

2009-10-07 13:54:45 changed by sandervl73

  • version changed from VirtualBox 3.0.6 to VirtualBox 3.0.8.

bepla: so even some bootable Linux ISO will trigger the reboot/freeze?

2009-10-07 13:54:53 changed by sandervl73

  • owner changed.
  • component changed from host support to VMM/HWACCM.

2009-10-07 14:20:08 changed by sandervl73

I've found several related pages concerning AMD-V and this particular laptop. E.g http://social.technet.microsoft.com/Forums/en-US/w7itprovirt/thread/85d3ca80-7729-43b5-82f1-c29f6f05f0a1

Several people have reported problems with VirtualPC and XP compatibility mode (in Windows 7). That points to a problem with the machine/BIOS.

Use google and search for 'dell Latitude D531 amd-v reboot'

(follow-up: ↓ 12 ) 2009-10-07 14:22:01 changed by sandervl73

That link lists a conversation with Dell support where they claim to be working on a BIOS update to fix the problem. So it really looks like a BIOS problem.

Have you tried contacting Dell?

(in reply to: ↑ 11 ) 2009-10-09 10:01:17 changed by bepla

Replying to sandervl73:

That link lists a conversation with Dell support where they claim to be working on a BIOS update to fix the problem. So it really looks like a BIOS problem. Have you tried contacting Dell?

I must confess I was suspecting that was a BIOS problem... I go and try to contact Dell... Thank you for your time looking for that problem. I'll post anything interesting here.

2009-10-19 11:19:26 changed by bepla

According to Dell (technical phone support), the buggy AMD Turion 64 x2 proc is the problem and Dell doesn't seem to work on a new BIOS release since the Latitude D531 isn't available no more...

2009-10-19 11:39:10 changed by sandervl73

  • status changed from new to closed.
  • resolution set to wontfix.
  • summary changed from System reboot or freeze when AMD-V enabled to System reboot or freeze when AMD-V enabled -> BIOS lacks workaround for known AMD errata.

True. There are known ways to work around the problem(s), but they require a BIOS update. It's a bit unfortunate that they don't feel it's important enough to warrant some work on the BIOS.

There's not much we can do though. I can try to find a way to detect the missing workaround and refuse to enable AMD-V, but that might take some time.

(follow-up: ↓ 16 ) 2009-10-19 11:59:12 changed by sandervl73

For now the best thing to do is to disable AMD-V in your BIOS as it's unsafe to use.

(in reply to: ↑ 15 ) 2009-11-09 11:30:27 changed by zaimor

Posting information requested by sandervl - having same error:

Machine: Dell D531 (Model: PP04X) WinXPSP2 BIOS A08 (latest) VBox 3.0.10

Attached logfile 20091109VBOXLOG.txt. Crash occurs shortly after "Starting Up..." displays on imported Ubuntu 8.04 VM, host machine hard reboot.

2009-11-09 11:33:13 changed by zaimor

  • attachment 20091109VBOXLOG.txt added.

Dell D531 BIOS A08 XP Host Ubuntu Guest VB 3.0.10 Hard Host Reset

2009-11-09 14:56:00 changed by sandervl73

zaimor: similar report here for MS VirtualPC: http://forums.amd.com/forum/messageview.cfm?catid=33&threadid=96254

Does the solution there help for you?

2009-11-09 14:58:44 changed by sandervl73

Actually you have the exact same model as the original reporter.

2009-11-09 14:59:49 changed by sandervl73

  • summary changed from System reboot or freeze when AMD-V enabled -> BIOS lacks workaround for known AMD errata to System reboot or freeze when AMD-V enabled -> BIOS lacks workaround for known AMD errata (Dell D531 Latitude).

2010-01-23 14:37:30 changed by rraghur

Was having the exact same issue with D531 with AMD turion X2.

Found dell fw update T12 for D531. THis page on technet tracks the issue.

Post the update, can run ubuntu 9.10 image on vbox 3.1.2 with 2 processors and AMD-V enabled (bluescreened within ubuntu first time) but the second time on its been rock solid. YMMV..

Oh, did I mention, ubuntu 9.10 now seems like greased lightning compared to earlier...


Contact – Privacy policy