#2763 closed defect (fixed)
Vista (32 bit) host with ATI x1250 -> Linux guest -> BSOD / fixed in SVN/2.1.4
Reported by: | Joerg78 | Owned by: | |
---|---|---|---|
Component: | VMM/HWACCM | Version: | VirtualBox 2.1.0 |
Keywords: | bsod amd vista | Cc: | |
Guest type: | Linux | Host type: | Windows |
Description (last modified by )
Bug since (at least) version 1.6.0: Following combination leads to a BSOD:
- Physical machine: HP 6715b, AMD Turion CPU (Dualcore), x1250 graphic chipset
- Running Virtualbox on Vista 32 bit host
- Linux as guest, eg Ubuntu 8.10 (same problem with Ubuntu 8.04 or OpenSolaris as mentioned here: http://forums.virtualbox.org/viewtopic.php?t=12231
Starting the virtual machine leads to a BSOD (host) after selecting something in linux (guest) bootmanager.
Windows Eventmanager tells me something about a crash of the display driver (in german it says: Anzeigetreiber atikmdag reagiert nicht mehr und wurde erfolgreich wieder hergestellt., in english it's something like Display driver atikmdag stopped responding and was successfully recovered. Display driver and bios of laptop is up-to-date.
A workaround is to enable AMD-V, guest will run normally then. BSOD will only appear with disabled AMD-V (which is the default setting after installation).
Attachments (2)
Change History (9)
by , 16 years ago
comment:1 by , 16 years ago
Component: | VMM → VMM/HWACCM |
---|---|
Description: | modified (diff) |
comment:2 by , 16 years ago
comment:3 by , 16 years ago
priority: | major → critical |
---|
comment:4 by , 16 years ago
Sorry, I have no VESA drivers available (where can I found some?). Using the Standard VGA driver the host machine will not crash. I tried different versions of the ATI driver, but all of them crash. Maybe the issue also exists with the x3100 card (see http://forums.virtualbox.org/viewtopic.php?p=50539#50539)
comment:5 by , 16 years ago
Summary: | Vista (32 bit) host with ATI x1250 -> Linux guest -> BSOD → Vista (32 bit) host with ATI x1250 -> Linux guest -> BSOD / fixed in SVN/2.1.4 |
---|
This fix will be in the next maintenance release (due out soon).
comment:6 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
vbox Logfile