VirtualBox

Changes between Initial Version and Version 1 of Ticket #2763


Ignore:
Timestamp:
12/18/08 08:03:48 (5 years ago)
Author:
frank
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #2763

    • Property Component changed from VMM to VMM/HWACCM
  • Ticket #2763 – Description

    initial v1  
    22Following combination leads to a BSOD: 
    33 
    4 - Physical machine: HP 6715b, AMD Turion CPU (Dualcore), x1250 graphic chipset 
    5 - Running Virtualbox on Vista 32 bit host 
    6 - 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 
     4 * Physical machine: HP 6715b, AMD Turion CPU (Dualcore), x1250 graphic chipset 
     5 * Running Virtualbox on Vista 32 bit host 
     6 * 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 
    77 
    88Starting the virtual machine leads to a BSOD (host) after selecting something in linux (guest) bootmanager. 
    99 
    10 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}}}). 
     10Windows 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''. 
    1111Display driver and bios of laptop is up-to-date. 
    1212 
    1313A 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). 
    14  
    15  

www.oracle.com
ContactPrivacy policyTerms of Use