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 loses
 ACPI data in xenstore
Date: Sat, 18 May 2013 12:17:15 +0100
Message-ID: <7AD24E5E5612F30F1D9EC307@nimrod.local>
References: <1230090824.8634328.1368537142268.JavaMail.root@zimbra002>	
	<1368812028.24012.64.camel@hastur.hellion.org.uk>	
	<D9A4F8CE5A4EEFFCFEC0F7C3@nimrod.local>
	<1368874943.12438.19.camel@dagon.hellion.org.uk>
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: <1368874943.12438.19.camel@dagon.hellion.org.uk>
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: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Diana Crisan <dcrisan@flexiant.com>, Alex Bligh <alex@alex.org.uk>, xen-devel@lists.xen.org
List-Id: xen-devel@lists.xenproject.org

Ian,

--On 18 May 2013 12:02:23 +0100 Ian Campbell <Ian.Campbell@citrix.com> 
wrote:

> These keys have nothing to do with that, all they do is cause hvmloader
> to expose ACPI tables to the guest or to tweak the content of those
> tables. That state is preserved as part of the memory image of the
> guest. The qemu state is also pickled as part of the save image.
>
> ACPI is jut a set of tables describing the hardware, there's no
> "emulation" to turn off and on. Whatever magic I/O ports the ACPI AML
> references are always on, the setting just controls whether the guest
> gets to see that via the AML.

Thanks. So it could not be that the guest gets to see that via the AML
pre migration, but not post migration?

In that case I can only conclude that some part of the qemu state
is not migrating correctly, and the fact that it the cluck stock
doesn't happen if ACPI is enabled in xl.conf is only relevant as
it influences how the guest (linux in this case) chooses its clock
source (i.e. its broken in any case, just the guest does not notice
if the relevant ACPI dtables aren't exposed).

Any ideas on how to debug this further? It is odd that the date command
(used to set a date) will unstick the clock.

-- 
Alex Bligh