All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Richard W.M. Jones" <rjones@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: Aleksei Kovura <alex3kov@zoho.com>,
	Xiao Guangrong <guangrong.xiao@linux.intel.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Shannon Zhao <zhaoshenglong@huawei.com>,
	Michael Tokarev <mjt@tls.msk.ru>,
	qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
	Igor Mammedov <imammedo@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/4] set the OEM fields in the RSDT and the FADT from the SLIC
Date: Thu, 14 Jan 2016 10:03:59 +0000	[thread overview]
Message-ID: <20160114100359.GU1766@redhat.com> (raw)
In-Reply-To: <1452735417-5461-1-git-send-email-lersek@redhat.com>

On Thu, Jan 14, 2016 at 02:36:53AM +0100, Laszlo Ersek wrote:
> This matters mostly for Win7 installations that were converted with p2v.
> Testing feedback from such environments would be appreciated.

Just to note first that no RHEL customer has ever reported this bug to
us.

To test this is going to require a spare UEFI-capable physical machine
where I can install Windows 7, and I don't have such a machine.

I could test it using a virt-p2v conversion from a VM, but then I
guess we'd have to apply these patches to qemu before conversion, and
so it wouldn't be clear to me exactly what we were testing.

Anyway I'll keep an eye on this and if I get hardware capable of
testing it, then I'll do so.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-p2v converts physical machines to virtual machines.  Boot with a
live CD or over the network (PXE) and turn machines into KVM guests.
http://libguestfs.org/virt-v2v

  parent reply	other threads:[~2016-01-14 10:04 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-14  1:36 [Qemu-devel] [PATCH 0/4] set the OEM fields in the RSDT and the FADT from the SLIC Laszlo Ersek
2016-01-14  1:36 ` [Qemu-devel] [PATCH 1/4] acpi: take oem_id in build_header(), optionally Laszlo Ersek
2016-01-14  1:36 ` [Qemu-devel] [PATCH 2/4] acpi: expose oem_id and oem_table_id in build_rsdt() Laszlo Ersek
2016-01-14  1:36 ` [Qemu-devel] [PATCH 3/4] acpi: stash the OEM ID and OEM Table ID fields from an external SLIC table Laszlo Ersek
2016-01-14 10:21   ` Michael S. Tsirkin
2016-01-14 16:38     ` Laszlo Ersek
2016-01-14  1:36 ` [Qemu-devel] [PATCH 4/4] pc: set the OEM fields in the RSDT and the FADT from the SLIC Laszlo Ersek
2016-01-14 10:24   ` Michael S. Tsirkin
2016-01-14 16:44     ` Laszlo Ersek
2016-01-14 17:09       ` Laszlo Ersek
2016-01-14 10:03 ` Richard W.M. Jones [this message]
2016-01-14 10:06   ` [Qemu-devel] [PATCH 0/4] " Alex
2016-01-14 10:23     ` Richard W.M. Jones
2016-01-14 16:35       ` Laszlo Ersek
2016-01-15 16:07         ` Richard W.M. Jones
2016-01-15 16:13           ` Alex
2016-01-21 11:37         ` Richard W.M. Jones
2016-01-21 11:42           ` Michael Tokarev
2016-01-21 11:44             ` Richard W.M. Jones
2016-01-21 11:55             ` Laszlo Ersek

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=20160114100359.GU1766@redhat.com \
    --to=rjones@redhat.com \
    --cc=alex3kov@zoho.com \
    --cc=guangrong.xiao@linux.intel.com \
    --cc=imammedo@redhat.com \
    --cc=lersek@redhat.com \
    --cc=mjt@tls.msk.ru \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=zhaoshenglong@huawei.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.