From mboxrd@z Thu Jan 1 00:00:00 1970 From: Diana Crisan Subject: Re: HVM Migration of domU on Qemu-upstream DM causes stuck system clock with ACPI Date: Mon, 03 Jun 2013 15:01:42 +0100 Message-ID: <51ACA1C6.5090903@flexiant.com> References: <1717491994.10371605.1369131737226.JavaMail.root@zimbra002> <519B6D51.2060508@citrix.com> <951B3441BAE2324286D3AA6D@Ximines.local> <420439EA40B15FCBFDFF2BE3@nimrod.local> <1369557503.22605.11.camel@dagon.hellion.org.uk> <51A4C7EB.1010406@flexiant.com> <51A7767A.9030904@flexiant.com> <51A7791C.2020208@eu.citrix.com> <51A8608F.9000302@flexiant.com> <51A88151.3080001@eu.citrix.com> <0FE70400-1152-45F5-9BF9-973DF1DA9EE8@flexiant.com> <51A88E3E.5090208@eu.citrix.com> <1370004031.5199.133.camel@zakaz.uk.xensource.com> <51A8A0AC.1030301@eu.citrix.com> <51A8BD48.6060104@citrix.com> <51AC55DD.7000507@citrix.com> <51AC6EB6.2010108@citrix.com> <51AC7B1D.8020308@eu.citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <51AC7B1D.8020308@eu.citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: George Dunlap Cc: Ian Campbell , Stefano Stabellini , Konrad Rzeszutek Wilk , xen-devel@lists.xen.org, David Vrabel , Alex Bligh , Anthony PERARD , =?UTF-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= List-Id: xen-devel@lists.xenproject.org > Right -- it seems to be working for me too. I'm on migrate #52, and > there hasn't been a single warning from Linux's clock code about > increasing min_delay. > > Diana / Alex: It looks like we might have a work-around for you. > Diana, would it be possible for you to do the following: > 1. Add tsc_mode="native_paravirt" to your config file > 2. Try it again localhost migrate to see if you run into any problems > 3. Try it again migrating between machines, just to make sure we've > solved the important problem This seems to fix migration for us too. I have tested your two scenarios and also within our code and I can confirm the problem did not reappear yet. I will continue to test throughout the next couple of days and I will update if anything comes up. Thank you for your help, Diana