From: "Richard W.M. Jones" <rjones@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Alex <alex3kov@zoho.com>,
Xiao Guangrong <guangrong.xiao@linux.intel.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Shannon Zhao <zhaoshenglong@huawei.com>,
qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Igor Mammedov <imammedo@redhat.com>,
Laszlo Ersek <lersek@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/4] set the OEM fields in the RSDT and the FADT from the SLIC
Date: Thu, 21 Jan 2016 11:44:50 +0000 [thread overview]
Message-ID: <20160121114450.GP1766@redhat.com> (raw)
In-Reply-To: <56A0C40A.1060305@msgid.tls.msk.ru>
On Thu, Jan 21, 2016 at 02:42:02PM +0300, Michael Tokarev wrote:
> 21.01.2016 14:37, Richard W.M. Jones wrote:
>
> > I'm afraid I gave up on this -- did give it my best. It turns out
> > that the machine that I thought supported UEFI boot does not. I'll
> > keep an eye out for such a machine and test this in future.
>
> BTW, why do you guys refer to UEFI boot all the time? The whole thing
> is equally useful on traditional BIOS-booting machines too. Windows7
> uses the same mechanism (looking at RSDT) for offline activation no
> matter if it is EFI system or not.
>
> When I did first version of my patch (based on someone else's version,
> but details escapes my memory already), there was no UEFI support for
> qemu whatsoever, and it allowed me to use my OEM version of Windows7
> inside a qemu virtual machine without second activation.
Could really do with detailed steps to reproduce the problem. We have
never observed it, and I know next to nothing about how "activation"
works.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine. Supports Linux and Windows.
http://people.redhat.com/~rjones/virt-df/
next prev parent reply other threads:[~2016-01-21 11:44 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 ` [Qemu-devel] [PATCH 0/4] " Richard W.M. Jones
2016-01-14 10:06 ` 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 [this message]
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=20160121114450.GP1766@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.