From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Aaron Lauterer <a.lauterer@proxmox.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: Possible regression with VGA and resolutions in Windows 10?
Date: Fri, 24 Jul 2020 15:31:23 +0100 [thread overview]
Message-ID: <20200724143123.GF3146350@redhat.com> (raw)
In-Reply-To: <20200724141032.jmub3zixekeyy3x3@sirius.home.kraxel.org>
On Fri, Jul 24, 2020 at 04:10:32PM +0200, Gerd Hoffmann wrote:
> Hi,
>
> > The behavior is similar when setting a custom resolution with the xres
> > and yres parameters. Setting it the first time works fine and it is
> > shown along with the short list. Setting it to something different on
> > the next boot will not be recognized unless the display adapter is
> > uninstalled and the VM rebooted.
>
> Interesting. Seems Windows caches the list of resolutions (or the edid
> blob) somewhere in the registry instead of loading it on every boot.
> I've seen simliar behavior with usb device info.
>
> [ something for the 5.1 release notes I think, thanks for testing this ]
Do we need to be disabling edid in the old machine types to prevent this
change in guest ABI due to the changed BIOS ?
eg existing VMs using a versioned machine type shouldn't suddenly get edid
enabled where previously it was not present. Only VMs using the new 5.1 or
unversioned machine types should see the change in behaviour.
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:[~2020-07-24 14:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 14:24 Possible regression with VGA and resolutions in Windows 10? Aaron Lauterer
2020-07-23 16:19 ` Laszlo Ersek
2020-07-24 9:41 ` Gerd Hoffmann
2020-07-24 13:17 ` Aaron Lauterer
2020-07-24 14:10 ` Gerd Hoffmann
2020-07-24 14:31 ` Daniel P. Berrangé [this message]
2020-07-24 15:35 ` Gerd Hoffmann
2020-07-27 12:00 ` Aaron Lauterer
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=20200724143123.GF3146350@redhat.com \
--to=berrange@redhat.com \
--cc=a.lauterer@proxmox.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
/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.