[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] [PATCH 00/02] firmware changes as part of QEMU/Xen merge.



On Mon, 18 Oct 2010, Ian Pratt wrote:
> > We cannot make changes to qemu-dm that are not backwards compatible with
> > saved guests. Not only does this affect qemu in this case, but the
> > register
> > blocks you move around also affect Xen's emulation of ACPI pmtimer. Both
> > will/would need to be configurable based on whether this is an old or new
> > guest.
> > 
> > Hence this has to be strongly NACKed in its current form.
> 
> It's getting to the point where we might have to consider having two qemu 
> binaries, one for compatibility, one that new VMs are transitioned on to.
> 
> Things are now so different that I'm worried that installed guests might 
> complain even when just fresh booted on the new qemu. This is something that 
> we'd need to test and devise workarounds. Trying to retain saved image 
> compatibility with a single binary looks ugly.
> 

I agree.

However in this particular case the firmware changes are only for ACPI
support and we might be able to support both the old AND the new ioports
in qemu-xen, so that we can switch the firmware to the new interface
while keeping backward compatibility in qemu.

That said I doubt we'll be able to do the same in upstream qemu, so at
some point the old ioport interface will probably be dropped.


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.