On zondag 1 juli 2012 18:03:14 Freek de Kruijf wrote: > On zondag 1 juli 2012 17:55:27 Freek de Kruijf wrote: > > I have VirtualBox-4.1.18 installed on three systems. Two systems are > > single core systems, the third is a 4 core system. When I start the > > VirtualBox GUI on two of these systems, one 1-core and the 4-core, I > > immediately have a high CPU load, the 1-core 100% and in the 4-core 3 > > cores at around 40% and the fourth at 3%. Looking at this load using > > top, I see a high activity by VBoxSVC at 110% on the 4-core system and > > on that same system three ksoftirqd processes each at around 16%. > > Starting a VM on the 1-core, this system starts up and seems to work > > properly, although slow. It takes 5 to 6 minutes before I can ssh into > > the 1-core system. Giving this system a poweroff signal it normally > > takes 30 seconds to have it in the status powered off. Now it takes > > around 100 seconds to reach that state. > > > > The odd thing is that the other 1-core system behaves normally, while it > > is practically a duplicate of the other 1-core. Same hardware, same > > software, same patch level. In all three systems a recent change is the > > upgrade to a new kernel. > > > > It does not make any difference whether to start the GUI or starting > > Headless. In the last case, obviously also the VM is started, but after > > that the CPU load remains high, even after having reached an almost idle > > status of the VM. The two mentioned processes VBoxSVC and ksoftirqd are > > the ones with high loads. > > With starting Headless the high load is also due to a third process > VBoxHeadless. The load of VBoxHeadless and VBoxSVC is almost the same. > > > 1-core-a:~ # uname -a > > Linux 1-core-a 2.6.37.6-0.20-default #1 SMP 2011-12-19 23:39:38 +0100 > > x86_64 x86_64 x86_64 GNU/Linux > > > > 1-core-b:~ # uname -a > > Linux 1-core-b 2.6.37.6-0.20-default #1 SMP 2011-12-19 23:39:38 +0100 > > x86_64 x86_64 x86_64 GNU/Linux > > > > 4-core:~ # uname -a > > Linux 4-core 2.6.37.6-0.20-default #1 SMP 2011-12-19 23:39:38 +0100 > > x86_64 x86_64 x86_64 GNU/Linux
After a reboot of the two systems with problems, the situation is back to normal. Although I did a reboot after upgrading the kernel, after which I needed to do a "rcvboxdrv setup", which showed the new kernel modules loaded, apparently a second reboot was necessary. It never was necessary before and also not on that one system that behaves normal. The implicit question was: should I report it as a bug? Because the situation is not reproducible anymore, I will not do that. -- fr.gr. Freek de Kruijf ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ VBox-users-community mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/vbox-users-community _______________________________________________ Unsubscribe: mailto:[email protected]?subject=unsubscribe
