qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Yuri Benditovich <ybendito@redhat.com>
Cc: Yan Vugenfirer <yvugenfi@redhat.com>,
	Gerd Hoffmann <kraxel@redhat.com>,
	Eduardo Habkost <ehabkost@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [PULL 1/1] qxl: introduce hardware revision 5
Date: Thu, 5 Mar 2020 16:01:24 +0100	[thread overview]
Message-ID: <e69ea9ab-9fc1-ca12-c7ab-50e094c1c782@redhat.com> (raw)
In-Reply-To: <1472901155.11933269.1583395037984.JavaMail.zimbra@redhat.com>

On 03/05/20 08:57, Yuri Benditovich wrote:
> ----- Original Message -----
>
>> From: "Laszlo Ersek" <lersek@redhat.com>
>> To: "Gerd Hoffmann" <kraxel@redhat.com>
>> Cc: qemu-devel@nongnu.org, "Eduardo Habkost" <ehabkost@redhat.com>,
>> "Yuri Benditovich" <ybendito@redhat.com>, "Yan Vugenfirer"
>> <yvugenfi@redhat.com>
>> Sent: Thursday, March 5, 2020 1:28:23 AM
>> Subject: Re: [PULL 1/1] qxl: introduce hardware revision 5
>
>> this patch -- commit ed71c09ffd6f -- disables ACPI S3 in the Windows
>> 10 guest for me, using OVMF and QXL.
>
>> The "Sleep" menu entry disappears from the power button icon/menu at
>> the login screen, and "psshutdown -d -t 3" (from the pstools package)
>> also stops working (it reports that the computer does not support
>> S3).
>
>> At the parent commit (e18e5501d8ac), S3 suspend/resume works.
>

[...]

>> OVMF is built at current edk2 master: e63d54db9526.
>
>> In the Windows 10 guest, the installed driver has the following
>> properties (per Device Manager):
>
>> - driver date: 7/28/2015
>> - driver version: 22.33.46.473

> This is not what I would expect from any qxl driver for Win10
> What is the name of display adapter?

"Red Hat QXL controller"

> The driver provider is 'Red Hat'?

In the "Red Hat QXL controller Properties" dialog:

- on the General tab, Manufacturer is "Red Hat, Inc."

- on the Driver tab, both the "Driver Provider" and the "Digital Signer"
  fields are "Red Hat, Inc."

This driver comes from "qxlwddm-0.1-12" (buildID=449635), in Brew.

In retrospect it looks like this driver was meant for Windows 8 only,
but it happened to install under, and work OK for, Windows 10 too.

> Does your guest run with secure boot?

Yes, it does. (Double-checked it with "confirm-SecureBootUEFI" in
PowerShell.)

> I do not see such an effect with 'Sleep' with latest qemu master +
> OVMF + qxl + Win10, the sleep button does not disappear.

I'm happy to try other driver versions. Hopefully Windows 10 will
actually see them as upgrading the currently installed driver. (Or
should I uninstall first?)

Thanks!
Laszlo



  reply	other threads:[~2020-03-05 15:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-13  9:06 [PULL 0/1] Vga 20200213 patches Gerd Hoffmann
2020-02-13  9:06 ` [PULL 1/1] qxl: introduce hardware revision 5 Gerd Hoffmann
2020-03-04 23:28   ` Laszlo Ersek
2020-03-05  7:57     ` Yuri Benditovich
2020-03-05 15:01       ` Laszlo Ersek [this message]
2020-03-05 19:09         ` Yuri Benditovich
2020-03-05 22:42           ` Laszlo Ersek
2020-03-05  8:08     ` Gerd Hoffmann
2020-03-05  9:16       ` Yuri Benditovich
2020-02-14 10:21 ` [PULL 0/1] Vga 20200213 patches Peter Maydell

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=e69ea9ab-9fc1-ca12-c7ab-50e094c1c782@redhat.com \
    --to=lersek@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=ybendito@redhat.com \
    --cc=yvugenfi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).