<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">I see this on some guests as well, possibly relating to moving between hosts with the same family of CPU but different absolute CPU speeds?<div><br></div><div> -Darrell</div><div><br></div><div><div><div>On Apr 4, 2014, at 8:33 AM, Michal Skrivanek <<a href="mailto:michal.skrivanek@redhat.com">michal.skrivanek@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><base href="x-msg://1575/"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi,<div>this is more for the KVM folks I suppose…can you get the qemu process cmdline please?</div><div><br></div><div>Thanks,</div><div>michal</div><div><br><div><div>On 3 Apr 2014, at 12:13, Markus Stockhausen wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; border-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-stroke-width: 0px; font-size: inherit;"><div style="direction: ltr; font-family: Tahoma; font-size: 10pt;">Hello,<br><br>we have an up to date ovirt 3.4 installation. Inside we are running SLES11 SP3<br>VMs (Kernel 3.0.76-0.11). After live migration of these VMs they all of a sudden<br>do not react any longer and CPU usage of the VM goes to 100%.<br><br>We identified kvm-clock source to be the culprit and therefore switched to another<br>clocksource. We ended with hpet but are not happy with that as our inital goal<br>was to use the more simple designed TSC clocksoure.<span class="Apple-converted-space"> </span><br><br>The reason behind that is the question I have for you experts.<br><br>Our hosts all have the constant_tsc CPU flag available. Just to mention these<br>are not identical hosts. We have a mix of Xeon 5500 and 5600 machines. E.G.<br>[root@colovn01 ~]# cat /proc/cpuinfo | grep constant_tsc | wc -l<br>8<br><br>When we start the VM the client sees TSC as available clocksource:<br><br>colvm53:~ # cat /sys/devices/system/clocksource/clocksource0/available_clocksource<br>kvm-clock tsc hpet acpi_pm<br><br>After the first live migration to another host that also has constant_tsc (see above)<br>that flag is lost inside the VM.<br><br>colvm53:~ # cat /sys/devices/system/clocksource/clocksource0/available_clocksource<br>kvm-clock hpet acpi_pm<br><br>Any ideas?<br><br>Markus<br><br><br></div><InterScan_Disclaimer.txt>_______________________________________________<br>Users mailing list<br><a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br><a href="http://lists.ovirt.org/mailman/listinfo/users">http://lists.ovirt.org/mailman/listinfo/users</a></span></blockquote></div><br></div></div>_______________________________________________<br>Users mailing list<br><a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>http://lists.ovirt.org/mailman/listinfo/users<br></blockquote></div><br></div></body></html>