On 10/01/2009 12:32 PM, Daniel Schwager wrote:
Hi, we are running some stopped (sending "stop" via kvm-monitor socket) vm's on our system. My intention was to pause (stop) the vm's and unpause (cont) them on demand (very fast, without time delay, within 2 seconds ..). After 'stop'ing, the vm's still using CPU-load, like the "top" will tell: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 25983 root 20 0 495m 407m 1876 R 8.9 2.5 228:09.15 qemu-system-x86 25523 root 20 0 495m 2040 1868 S 7.9 0.0 2700:16 qemu-system-x86
It shouldn't do that. How long is this after the 'stop'? Was the guest doing intensive I/O? Are you sure qemu responded to the stop command (by printing the monitor prompt)?
-- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
