On Fri, Aug 3, 2012 at 6:41 AM, Luigi Rizzo <rizzo_at_iet.unipi.it> wrote: > On Fri, Aug 03, 2012 at 07:44:27AM +0200, Bernhard Fr?hlich wrote: >> On Fr.,?? 3. Aug. 2012 06:18:33 CEST, Kevin Oberman <kob6558_at_gmail.com> wrote: >> >> > On Thu, Aug 2, 2012 at 12:54 AM, Hartmann, O. >> > <ohartman_at_zedat.fu-berlin.de> wrote: >> > > I discover that when running Windows 7 in a VirtualBox On FreeBSD 10 >> > > (r238968: Wed Aug 1 14:26:40 CEST 2012), VBox is most recent from the >> > > ports, that the VirtualBox eats up 100% CPU time and freezes Windows 7 >> > > for more than a minute. For a minute or so, I can work, then, the >> > > freeze occurs again. >> > > >> > > I can't see this behaviour with a Ubuntu Guest on the same box. Is >> > > there Windows 7 specifica to be aware of? >> > >> > I am seeing the same thing. Also Win7 guest with Windows showing idle >> > process at 99%, but my system is showing VB at 100%. The VM is only >> > running a single CPU, so FreeBSD is still running OK, but the Win7 >> > system seems to freeze up periodically. >> > >> > 9.1-PRERELEASE on amd64 updated yesterday (though it has been this way >> > since VB was updated to 4.1.18. Guest additions for 4.1.18 >> > installed.All ports current. I'm thinking of backing off to 4.1.16. >> >> Can someone confirm that this is a regression in 4.1.18? Then I could talk to upstream and see if I can get that adressed. > > Could it be a case of kernel and virtualbox modules out of sync ? > I do see occasional crashes with virtualbox in both the host and guest, > but a reinstall of in-sync kernel and modules usually fixes them. Nope. To be really, really sure I just re-built the module and rebooted. VB still eats 100% CPU (out of 400%) continually. Thanks for the suggestion, though. -- R. Kevin Oberman, Network Engineer E-mail: kob6558_at_gmail.comReceived on Fri Aug 03 2012 - 20:36:14 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:29 UTC