From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: thomas.lendacky@amd.com, "Kang, Luwei" <luwei.kang@intel.com>,
libvir-list@redhat.com, qemu-devel <qemu-devel@nongnu.org>,
Robert Hoo <robert.hu@linux.intel.com>,
kai.huang@intel.com, robert.hu@intel.com,
Paolo Bonzini <pbonzini@redhat.com>,
Jiri Denemark <jdenemar@redhat.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [PATCH] i386: Re-add "pconfig" CPUID flag name
Date: Fri, 27 Sep 2019 10:09:05 +0100 [thread overview]
Message-ID: <20190927090905.GC20911@redhat.com> (raw)
In-Reply-To: <20190927004220.GV8144@habkost.net>
On Thu, Sep 26, 2019 at 09:42:20PM -0300, Eduardo Habkost wrote:
> (CCing libvir-list)
>
> On Thu, Sep 26, 2019 at 11:58:30PM +0200, Paolo Bonzini wrote:
> > Is this really needed? QEMU's value of pconfig=on vs. off should be
> > provided by QMP CPU model queries, if a property is not available then
> > Libvirt should not try to set it to off.
> >
>
> Libvirt can easily work around it for new VMs, and it should.
>
> The issue are VMs that were created with QEMU 3.1.0. QEMU 3.1.0
> was telling libvirt "Icelake-Server can't be used unless
> pconfig=off is used", and libvirt was adding pconfig=off to the
> domain XML as expected.
>
> It would be wrong for libvirt to remove a device option when
> migrating an existing VM to another QEMU version. We can change
> the rules (and document that), but do we want to?
IIUC currently any existing VMs with Icelake-Server will *not* have
pconfig present, since libvirt is going to set pconfig=off
QEMU has now dropped pconfig CPUID entirely. If libvirt were to stop
setting pconfig=off, then there is NO guest ABI change, so we'd be
safe in that sense.
I'll defer to Jiri on how we'd actually go about making that work
in libvirt from a code POV.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2019-09-27 9:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 21:23 [PATCH] i386: Re-add "pconfig" CPUID flag name Eduardo Habkost
2019-09-26 21:29 ` Eduardo Habkost
2019-09-26 21:58 ` Paolo Bonzini
2019-09-27 0:42 ` Eduardo Habkost
2019-09-27 9:09 ` Daniel P. Berrangé [this message]
2019-09-27 11:44 ` Eduardo Habkost
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=20190927090905.GC20911@redhat.com \
--to=berrange@redhat.com \
--cc=ehabkost@redhat.com \
--cc=jdenemar@redhat.com \
--cc=kai.huang@intel.com \
--cc=libvir-list@redhat.com \
--cc=luwei.kang@intel.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=robert.hu@intel.com \
--cc=robert.hu@linux.intel.com \
--cc=rth@twiddle.net \
--cc=thomas.lendacky@amd.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.