From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alex Bligh Subject: Re: HVM Migration of domU on Qemu-upstream DM causes stuck system clock with ACPI Date: Wed, 29 May 2013 17:16:06 +0100 Message-ID: <88C2AC2D815CF74D637D85FA@nimrod.local> References: <1717491994.10371605.1369131737226.JavaMail.root@zimbra002> <519B50C9.1000008@citrix.com> <519B577E.6070200@flexiant.com> <519B6D51.2060508@citrix.com> <951B3441BAE2324286D3AA6D@Ximines.local> <420439EA40B15FCBFDFF2BE3@nimrod.local> <1369557503.22605.11.camel@dagon.hellion.org.uk> <51A4C7EB.1010406@flexiant.com> Reply-To: Alex Bligh Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <51A4C7EB.1010406@flexiant.com> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Diana Crisan , Ian Campbell Cc: Konrad Rzeszutek Wilk , George Dunlap , xen-devel@lists.xen.org, David Vrabel , Alex Bligh , Anthony PERARD List-Id: xen-devel@lists.xenproject.org --On 28 May 2013 16:06:19 +0100 Diana Crisan wrote: >>>>> FWIW it's reproducible on every host h/w platform we've tried >>>>> (a total of 2). >>>> Do you see the same effects if you do a local-host migrate? >>> I hadn't even realised that was possible. That would have made testing >>> live migrate easier! >> That's basically the whole reason it is supported ;-) >> >>> How do you avoid the name clash in xen-store? >> Most toolstacks receive the incoming migration into a domain named >> FOO-incoming or some such and then rename to FOO upon completion. Some >> also rename the outgoing domain "FOO-migratedaway" towards the end so >> that the bits of the final teardown which can safely happen after the >> target have start can be done so. >> > > I am unsure what I am doing wrong, but I cannot seem to be able to do a > localhost migrate. > > I created a domU using "xl create xl.conf" and once it fully booted I > issued an "xl migrate 11 localhost". This fails and gives the output > below. > > Would you please advise on how to get this working? Any ideas? -- Alex Bligh