xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Diana Crisan <dcrisan@flexiant.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: HVM Migration of domU on Qemu-upstream DM loses ACPI data in xenstore
Date: Fri, 17 May 2013 18:33:48 +0100	[thread overview]
Message-ID: <1368812028.24012.64.camel@hastur.hellion.org.uk> (raw)
In-Reply-To: <1230090824.8634328.1368537142268.JavaMail.root@zimbra002>

On Tue, 2013-05-14 at 14:12 +0100, Diana Crisan wrote:
> Prior to issuing a migration the lines 'platform = ""', 'acpi = "1"',
> 'acpi_s3 = "1"' and 'acpi_s4 = "1"' are present in xenstore (despite
> the fact xl.conf does not explicitly specify them). However, after the
> migration succeeds on the receiving side, those lines are missing. 

Is the lack of these keys causing you a problem? IIRC they are used by
the builder to communicate with hvmloader (the pre-BIOS loader used in
HVM guests) so it can setup ACPI tables etc as appropriate. Nothing else
should be using them. They are documented as INTERNAL in
docs/misc/xenstore-paths.markdown.

Ian.

  reply	other threads:[~2013-05-17 17:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <514405924.8634267.1368537117719.JavaMail.root@zimbra002>
2013-05-14 13:12 ` HVM Migration of domU on Qemu-upstream DM loses ACPI data in xenstore Diana Crisan
2013-05-17 17:33   ` Ian Campbell [this message]
2013-05-18  9:52     ` Alex Bligh
2013-05-18 11:02       ` Ian Campbell
2013-05-18 11:17         ` Alex Bligh
2013-05-20  8:40           ` Ian Campbell
2013-05-20 11:50             ` Alex Bligh
2013-05-20 12:01               ` Ian Campbell
2013-05-21 10:08                 ` Diana Crisan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1368812028.24012.64.camel@hastur.hellion.org.uk \
    --to=ian.campbell@citrix.com \
    --cc=dcrisan@flexiant.com \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).