Virtualbox consuming wcpu
in [Ports]
|
Prev: devel/subversion
Next: equivalent of IA32_BINARY_PORT for USE_LINUX (Was: ports/148379:New port: audio/linux-Nero-AAC-Codec)
From: Paul Schmehl on 6 Jul 2010 12:23 I recently upgraded to the new port version of virtualbox - 3.2.6. After completing the upgrade, I'm seeing a massive amount of wcpu consumption (145%) with virtualbox when I use the vm to rdp to a different windows box. As long as I'm not using rdp, it works fine. When I first start the rdp, wcpu is fine, but it increases over time (20-30 minutes) until it's consuming cpu to the point where the host becomes very sluggish. Has anyone else experienced this? -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. ******************************************* "It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead." Thomas Jefferson _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Jesse Smith on 7 Jul 2010 07:20
-----Original Message----- From: freebsd-ports-request(a)freebsd.org Reply-to: freebsd-ports(a)freebsd.org To: freebsd-ports(a)freebsd.org Subject: freebsd-ports Digest, Vol 372, Issue 3 Date: Wed, 7 Jul 2010 06:30:02 +0000 (UTC) I recently upgraded to the new port version of virtualbox - 3.2.6. After completing the upgrade, I'm seeing a massive amount of wcpu consumption (145%) with virtualbox when I use the vm to rdp to a different windows box. As long as I'm not using rdp, it works fine. When I first start the rdp, wcpu is fine, but it increases over time (20-30 minutes) until it's consuming cpu to the point where the host becomes very sluggish. Has anyone else experienced this? I have run into this problem too. Not sure what the cause is, but it does get out of hand very quickly on my machine. The only work-around I've found is to use "cpulimit" to throttle back the VirtualBox process. The side effect of this, of course, is everything in the VM runs very slowly. But it's the only thing I've found to avoid cooking my laptop. _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org" |