From mboxrd@z Thu Jan  1 00:00:00 1970
From: Alex Bligh <alex@alex.org.uk>
Subject: Re: HVM Migration of domU on Qemu-upstream DM causes
 stuck system clock with ACPI
Date: Fri, 31 May 2013 12:18:23 +0100
Message-ID: <812D96B527897D84E2E13CD4@nimrod.local>
References: <1717491994.10371605.1369131737226.JavaMail.root@zimbra002>
	<519B50C9.1000008@citrix.com>
	<519B577E.6070200@flexiant.com>	<519B6D51.2060508@citrix.com>
	<951B3441BAE2324286D3AA6D@Ximines.local>
	<CAFLBxZbBz-vKSd9KHA9uLahk7=L5GrDAiWNzem+0PvCK8SmpNA@mail.gmail.com>
	<420439EA40B15FCBFDFF2BE3@nimrod.local>
	<1369557503.22605.11.camel@dagon.hellion.org.uk>
	<51A4C7EB.1010406@flexiant.com>
	<CAFLBxZYbzuhR3SK6dw0xsuF7QPG164h-0bJ+n+xEDKvzbYoHzw@mail.gmail.com>
	<51A7767A.9030904@flexiant.com>
	<51A7791C.2020208@eu.citrix.com>	<51A8608F.9000302@flexiant.com>
	<51A88151.3080001@eu.citrix.com>
Reply-To: Alex Bligh <alex@alex.org.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <51A88151.3080001@eu.citrix.com>
Content-Disposition: inline
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: George Dunlap <george.dunlap@eu.citrix.com>, Diana Crisan <dcrisan@flexiant.com>
Cc: Ian Campbell <Ian.Campbell@citrix.com>, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>, xen-devel@lists.xen.org, David Vrabel <david.vrabel@citrix.com>, Alex Bligh <alex@alex.org.uk>, Anthony PERARD <anthony.perard@citrix.com>
List-Id: xen-devel@lists.xenproject.org

George,

--On 31 May 2013 11:54:09 +0100 George Dunlap <george.dunlap@eu.citrix.com> 
wrote:

> So I wrote a script to run "date", sleep for 2 seconds, and run "date" a
> second time -- and eventually the *sleep* hung.
>
> The VM is still responsive, and I can log in; if I type "date" manually
> successive times then I get an advancing clock, but if I type "sleep 1"
> it just hangs.

Yes that's exactly what we're seeing. Anything that uses the wallclock
hangs. IE you can ping the VM, but the VM can't ping as the ping command
uses the wallclock timer.

I'll leave the point about dmseg to Diana.

-- 
Alex Bligh