This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Re: [PATCH 15/15] xen: Add a Xen specific ACPI Implementatio

To: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Subject: [Xen-devel] Re: [PATCH 15/15] xen: Add a Xen specific ACPI Implementation to target-xen
From: Anthony Liguori <anthony@xxxxxxxxxxxxx>
Date: Fri, 13 Aug 2010 15:51:06 -0500
Cc: Anthony Perard <anthony.perard@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "qemu-devel@xxxxxxxxxx" <qemu-devel@xxxxxxxxxx>
Delivery-date: Fri, 13 Aug 2010 13:51:44 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <alpine.DEB.2.00.1008132035150.2545@kaball-desktop>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <alpine.DEB.2.00.1008121244200.2545@kaball-desktop> <1281622202-3453-15-git-send-email-stefano.stabellini@xxxxxxxxxxxxx> <4C6595B5.6060300@xxxxxxxxxxxxx> <alpine.DEB.2.00.1008132035150.2545@kaball-desktop>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20100713 Lightning/1.0b1 Thunderbird/3.0.6
On 08/13/2010 02:37 PM, Stefano Stabellini wrote:
On Fri, 13 Aug 2010, Anthony Liguori wrote:
On 08/12/2010 09:10 AM, stefano.stabellini@xxxxxxxxxxxxx wrote:
From: Anthony PERARD<anthony.perard@xxxxxxxxxx>

Xen currently uses a different BIOS (hvmloader + rombios) therefore the
Qemu acpi_piix4 implementation wouldn't work correctly with Xen.
We plan on fixing this properly but at the moment we are just adding a
new Xen specific acpi_piix4 implementation.
This patch is optional; without it the VM boots but it cannot shutdown
properly or go to S3.

What's the long term plan?  Will Xen adopt SeaBIOS or will you adapt
your BIOS to cope with our ACPI implementation?

I think it shouldn't be too difficult to adapt our current BIOS, but
we'll need few xen specific hooks in acpi_piix4.
The price that we'll have to pay doing so is loosing live-migration
compatibility with older xen installations.

Does Xen migrate roms (like the BIOS) in such a way that the persist after a reboot?

I noticed there was only one machine type defined. In our experience, to preserve compatibility with migration, it's useful to have versioned machine names. We also have some special machine parameters to support compatibility with qdev.

How does Xen handle hvm migration machine model compatibility?


Anthony Liguori

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>