From: Olaf Hering <olaf@aepfle.de>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: xen-devel@lists.xen.org
Subject: Re: live migrating hvm from 4.4 to 4.5 fails due to kvmvapic
Date: Tue, 2 Aug 2016 16:41:38 +0200 [thread overview]
Message-ID: <20160802144137.GA9057@aepfle.de> (raw)
In-Reply-To: <alpine.DEB.2.10.1605131036460.2494@sstabellini-ThinkPad-X260>
[-- Attachment #1.1: Type: text/plain, Size: 1366 bytes --]
As a followup to the issue below, and the one which "just" popped in in
qemu-2.6+:
Why is the machine description for xen not fixed?
Shouldnt the be some sort of verification of old and new 'xenfv' when a
new qemu rc1 is done?
Is there a way to dump the machine description in text form?
Olaf
On Fri, May 13, Stefano Stabellini wrote:
> On Thu, 12 May 2016, Olaf Hering wrote:
> > On Thu, May 12, Olaf Hering wrote:
> >
> > > One thing to fix it in staging-4.5 is to introduce a dummy device which
> > > handles a section named "kvm-tpr-opt". I already have a hack which does
> > > that, and the migration proceeds. I will propose a patch to deal with
> > > this part of the bug.
> >
> > Something like shown below.
>
> Thanks for looking into this. I don't think that adding a dummy device
> in QEMU is acceptable. This kind of problems is usually solved with
> versioning the PC machine in QEMU, see all the pc_machine_* in
> hw/i386/pc_piix.c. One specific version of the machine is supposed to
> remain identical over multiple QEMU releases. In this case xenfv (or the
> pc machine you are using, if you are not using xenfv) has to be always
> identical. That's why I think we need to add kvmapic back to it for
> compatibility. I know it sucks. But we can choose a different PC machine
> with accel=xen for new VMs.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-08-02 14:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 15:48 live migrating hvm from 4.4 to 4.5 fails due to kvmvapic Olaf Hering
2016-05-12 21:45 ` Olaf Hering
2016-05-13 9:41 ` Stefano Stabellini
2016-08-02 14:41 ` Olaf Hering [this message]
2016-08-02 18:53 ` Stefano Stabellini
2016-05-13 9:43 ` Wei Liu
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=20160802144137.GA9057@aepfle.de \
--to=olaf@aepfle.de \
--cc=sstabellini@kernel.org \
--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).