From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Aaron Lauterer <a.lauterer@proxmox.com>
Subject: [pve-devel] applied: [PATCH qemu-server] cfg2cmd: vga: fix #2749: disable edid for Win+BIOS+VGA machines
Date: Wed, 19 Aug 2020 19:35:23 +0200 [thread overview]
Message-ID: <676fd816-8d1e-59bd-58fe-01d55a69ffb3@proxmox.com> (raw)
In-Reply-To: <20200727135525.18622-1-a.lauterer@proxmox.com>
On 27.07.20 15:55, Aaron Lauterer wrote:
> Edid support was added with Qemu 5. Windows guests seem to not be able
> to get all possible resolutions if the default std VGA device is used as
> GPU and the VM boots in BIOS mode. The result is that only one of the
> following three resolutions can be configured:
>
> 800x600
> 1024x768
> 1920x1080
>
> It is important to note that just booting a Windows VM with the edid=off
> parameter will not make the large list of resolutions available. It
> seems that Windows is caching the list of possible resolutions
> somewhere [0].
>
> Uninstalling the 'Microsoft Basic Display Adapter' in the device manager
> and rebooting the VM is one way I found to force Windows to recreate the
> list of possible resolutions.
>
> Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
>
> [0] https://lists.nongnu.org/archive/html/qemu-devel/2020-07/msg07128.html
> ---
>
> I did test live migration in both directions and it does seem to work.
> Would be great if someone else could verify this as well. Not having to
> version guard this would be nice.
>
> PVE/QemuServer.pm | 7 ++++++-
> test/cfg2cmd/custom-cpu-model-host-phys-bits.conf.cmd | 2 +-
> test/cfg2cmd/custom-cpu-model.conf.cmd | 2 +-
> 3 files changed, 8 insertions(+), 3 deletions(-)
>
>
applied, thanks! Tested a bit around with migrations and changing screen
resolutions and such in-between, worked so far OK.
prev parent reply other threads:[~2020-08-19 17:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 13:55 [pve-devel] " Aaron Lauterer
2020-08-19 17:35 ` Thomas Lamprecht [this message]
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=676fd816-8d1e-59bd-58fe-01d55a69ffb3@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=a.lauterer@proxmox.com \
--cc=pve-devel@lists.proxmox.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