The win64 guest is a p2v machine (with some cruddy HP device drivers I can't uninstall), but the win10 machine is a clean ISO install done on this laptop.īoth behave identically when it comes to aborting on undock. When undocking the laptop (separate switch to disconnect the base station, this also cuts ethernet, power & usb devices, although I do not knowingly have any USB passed through. Docked, 2nd monitor -> guest running fullscreen -> Undock -> guest aborted.
Undocked, laptop displayport monitor -> Fullscreen guest on -> disconnect hdmi cable -> fullscreen window moves to laptop screen. Docked, 2nd monitor -> guest Non-fullscreen (Windowed?) -> Undocked -> guest windows moved to another monitor. Docked, 2nd monitor -> guest running Fullscreen mode -> hdmi disconnected -> Fullscreen guest moved to another monitor. The guests are configured to use 2x monitors & I can direct fullscreen output to any pair without difficulty.īoth guest types will be aborted only if an Undock occurs when they are fullscreen & are using one of the external monitors. The laptop display resolution is identical to one of the monitors (and the other is the same resolution in portrait format). When docked I have 2x external HDMI monitors & a laptop display available. 
I have a patched windows 10 laptop host running V 5.10Ģx guests, win7-64 & win10, both patched & running GA. I can reliably crash either of my guests by undocking my laptop when running a vbox guest in a fullscreen on an external monitor.
0 kommentar(er)
