From: Antoine Damhet <antoine.damhet@blade-group.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Igor Mammedov <imammedo@redhat.com>,
lersek@redhat.com, "Richard W.M. Jones" <rjones@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [DISCUSSION] Allow ACPI default OEM ID and OEM table ID fields to be set.
Date: Thu, 26 Nov 2020 17:34:50 +0100 [thread overview]
Message-ID: <20201126163450.knb55wh2u7k2qgbb@tartarus> (raw)
In-Reply-To: <20201126082606-mutt-send-email-mst@kernel.org>
On Thu, Nov 26, 2020 at 08:29:41AM -0500, Michael S. Tsirkin wrote:
> On Thu, Nov 26, 2020 at 01:50:12PM +0100, Antoine Damhet wrote:
> > On Thu, Nov 26, 2020 at 06:09:11AM -0500, Michael S. Tsirkin wrote:
> > > On Wed, Nov 25, 2020 at 09:13:22PM +0100, Antoine Damhet wrote:
> > > > On Wed, Nov 25, 2020 at 11:04:55AM -0500, Michael S. Tsirkin wrote:
> > > > > On Wed, Nov 25, 2020 at 01:32:51PM +0000, Richard W.M. Jones wrote:
> > > > > > On Wed, Nov 25, 2020 at 02:27:11PM +0100, Antoine Damhet wrote:
[...]
> Exactly so I ask myself whether it's worth it, their next version
> will check CPUID and then where are we?
Then I guess they will have to admit that they are purposefully blocking
VM use and it's not our problem anymore.
> But maybe it's time we just changed all these IDs to e.g. QEMU.
> We are very far from bochs generated tables by now.
That's a good idea, but I still think they should be user override-able
(unless you think it would be a heavy maintenance burden, in that case
you are king in your castle :D )
> Question is will this cause annoyances with e.g. windows guests?
Windows 10 guests seems unaffected, I cannot say for the other
versions/servers editions.
> Igor what's your experience with this?
[...]
--
Antoine 'xdbob' Damhet
next prev parent reply other threads:[~2020-11-26 16:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 13:27 [DISCUSSION] Allow ACPI default OEM ID and OEM table ID fields to be set Antoine Damhet
2020-11-25 13:32 ` Richard W.M. Jones
2020-11-25 16:04 ` Michael S. Tsirkin
2020-11-25 20:13 ` Antoine Damhet
2020-11-26 11:09 ` Michael S. Tsirkin
2020-11-26 12:50 ` Antoine Damhet
2020-11-26 13:29 ` Michael S. Tsirkin
2020-11-26 16:34 ` Antoine Damhet [this message]
2020-11-26 17:05 ` Michael S. Tsirkin
2020-11-26 19:41 ` Igor Mammedov
2020-11-26 17:09 ` Michael S. Tsirkin
2020-11-26 17:37 ` Antoine Damhet
2020-11-26 12:51 ` Laszlo Ersek
2020-11-26 13:25 ` Michael S. Tsirkin
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=20201126163450.knb55wh2u7k2qgbb@tartarus \
--to=antoine.damhet@blade-group.com \
--cc=imammedo@redhat.com \
--cc=lersek@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.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.