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 19738 root 20 0 1139m 40m 1876 R 7.3 0.3 2501:57 qemu-system-x86 32521 root 20 0 495m 407m 1876 S 6.9 2.5 136:23.23 qemu-system-x86 21773 root 20 0 495m 407m 1876 S 5.6 2.5 575:01.44 qemu-system-x86 6720 root 20 0 2168m 2.0g 1876 R 4.6 12.9 524:55.70 qemu-system-x86 6819 root 20 0 2168m 2.0g 1876 S 4.6 12.9 489:24.24 qemu-system-x86 12752 root 20 0 495m 407m 1876 S 4.6 2.5 0:44.57 qemu-system-x86 22803 root 20 0 1139m 211m 1868 S 4.0 1.3 1217:21 qemu-system-x86 27083 root 20 0 1139m 1.0g 1868 S 4.0 6.5 121:58.05 qemu-system-x86 21970 root 20 0 495m 407m 1876 S 3.6 2.5 434:48.36 qemu-system-x86 3649 root 20 0 496m 394m 1908 S 3.3 2.5 39:41.61 qemu-system-x86 19919 root 20 0 559m 402m 1880 S 3.3 2.5 469:57.14 qemu-system-x86 24461 root 20 0 495m 2048 1876 S 3.3 0.0 1081:41 qemu-system-x86 24619 root 20 0 688m 536m 1880 S 3.0 3.3 293:15.38 qemu-system-x86 24776 root 20 0 495m 407m 1856 S 3.0 2.5 92:08.95 qemu-system-x86 ... So, how can I prevent the paused/stopped VM's to use my CPU from the hostsystem ? Is there a way to handle this ? Sure, stop+migrating the vm to filesystem will solve my problem - but restart (migrate back from filesystem to RAM) takes a lot (>30 seconds) of time. best regards Danny -- 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
