From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olaf Hering Subject: Re: live migrating hvm from 4.4 to 4.5 fails due to kvmvapic Date: Tue, 2 Aug 2016 16:41:38 +0200 Message-ID: <20160802144137.GA9057@aepfle.de> References: <20160512154813.GB2960@aepfle.de> <20160512214509.GA5248@aepfle.de> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6144285635258107731==" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xen.org Sender: "Xen-devel" To: Stefano Stabellini Cc: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org --===============6144285635258107731== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="2oS5YaxWCcQjTEyO" Content-Disposition: inline --2oS5YaxWCcQjTEyO Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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: > >=20 > > > One thing to fix it in staging-4.5 is to introduce a dummy device whi= ch > > > handles a section named "kvm-tpr-opt". I already have a hack which do= es > > > that, and the migration proceeds. I will propose a patch to deal with > > > this part of the bug. > >=20 > > Something like shown below. >=20 > 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=3Dxen for new VMs.=20 --2oS5YaxWCcQjTEyO Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlegsR4ACgkQXUKg+qaYNn7gewCgmFMaob75LIiVaD9kQFwZeHiE Z34An1dOGXuDQ841VTmhU4rbRVLSGqO8 =YLnC -----END PGP SIGNATURE----- --2oS5YaxWCcQjTEyO-- --===============6144285635258107731== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWRldmVs IG1haWxpbmcgbGlzdApYZW4tZGV2ZWxAbGlzdHMueGVuLm9yZwpodHRwczovL2xpc3RzLnhlbi5v cmcveGVuLWRldmVsCg== --===============6144285635258107731==--