So I'm *still* having a CPU at 100% problem while running any single on
a Linux x86_64 host. (proc: Core2 Duo E6600) I can work around this by
opening a second guest with no OS on it ("FATAL: No bootable medium
found!"), at which point both guests drop their CPU usage to low levels.
However in VirtualBox 3.0.10 r54097, this crappy workaround has a bug:
Time on the *guest* machine is elapsing too slowly. To view this, open
the "Date and Time Properties" and watch the analog clock - it takes
about 3 seconds for a second to elapse on the clock on my own system.
Closing the second (OS-less) guest causes the XP guest's time to elapse
at a normal rate again - but also causes VirtualBox's CPU usage to go
back to 100% on my system. I do not recall seeing this time issue on
previous versions of VirtualBox but I may simply have not noticed.
Any thoughts, folks? Anyone else seen this?
Cheers,
Greg
_______________________________________________
vbox-users mailing list
vbox-users@virtualbox.org
http://vbox.innotek.de/mailman/listinfo/vbox-users
