The bug is haunting me now has a 100% repro.
Since the shared folder do not work (but should!) As a workaround use network access to a folder listing sharing host.
Just go through the guest host UNC path to "unleash" the bug in question, which brings the process to use the CPU VirtualBox.exe ball, making it virtually unusable while the virtual machine.
That the bug is attributable purely and simply a VirtualBox guest OS and not 'just put in the fact that the virtual machine into hibernation, close and restart VirtualBox' cause things will return to normality '. If the CPU usage was due to the OS CPU guest would find the ball just restored from hibernation, but it is not 'so'.
VirtualBox really count the hours ... I'll 'return to Virtual PC 2007.
<$BlogFeedsVertical$>
0 comments:
Post a Comment