Opened 7 years ago
Last modified 7 years ago
#16917 new defect
vb virtual display adapter not VGA Compatible
| Reported by: | Tracey | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 5.1.22 |
| Keywords: | not VGA Compatible | Cc: | |
| Guest type: | other | Host type: | other |
Description (last modified by )
Is there a Video Debugging script?
Video freezes and guest must be cold started to restore functionality: both audio and video.
Version 5.1.24 r117012 (Qt5.6.2)
My Computer> Manage> Device Manager
Win2Ksp3, Win2Ksp4, WinXPsp3x32
?Other Devices: ?!device not functioning
?! Base System Device (understandable)
?! Video Controller (VGA Compatible disabled)
WinXPsp1x64 ?! Base System Device OK Standard VGA Graphics Adapter 01OCT2002 v5.2.3790.1830 driver:vgapnp.sys srv03_sp1_rtf.050324-1447
Change History (3)
comment:1 by , 7 years ago
comment:2 by , 7 years ago
| Description: | modified (diff) |
|---|
Please attach a VBox.log file of such a VM session.
comment:3 by , 7 years ago
I'm afraid we don't have a video debugging script. From the guest side, I think your best bet is to use standard Windows debugging techniques, without worrying about the fact that the system is running in a virtual machine rather than on physical hardware. If you can rebuild VirtualBox then you might also want to instrument or step through the graphics device code, but I would almost expect you to learn more initially by debugging in the guest and looking at the device source code to match it to the behaviour.
As Frank said, a log file would be the minimum we would need to look at anything ourselves. But a reproduction scenario where you install a Windows guest and reproduce the problem there would be very interesting (and might also help you understand what is happening).
Windows 7 host, Win2K and WinXP guest