You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 3, 2024. It is now read-only.
Hello. My windows 10 virtual machine refuses to change resolution past 1024x768. Trying to change resolution would just end with it reverting to 1024x768. 6.1.12-zen1-1-zen kernel on Arch linux, using Intel i9-10850K CPU. I am using virt-manager paired with looking-glass
For starters, I used the arch wiki's guide for the general setup (https://wiki.archlinux.org/title/Intel_GVT-g). I also set up a libvirt hook within my qemu file found under /etc/libvirt/hooks (https://pastebin.com/NAHVahEj) to automate the creation of mdev device at boot-up of virtual machine.
After installing windows 10 on the virtualmachine itself, I followed (https://wiki.archlinux.org/title/PCI_passthrough_via_OVMF#Using_Looking_Glass_to_stream_guest_screen_to_the_host) this guide to set up looking glass on guest and connected to it from guest using looking-glass-client. Trying to change the resolution within the virtualmachine itself would have no effect and windows would revert back to old resolution. If there is any more information you would like me to add please feel free to ask
Also experiencing the same issue with i5-7200U and HD 620.
A work-around that allows me to go higher is to also use the QEMU VGA adapter (-vga std). It starts at 1024x768 on every boot, but allows changing it after (eg. some startup script).
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello. My windows 10 virtual machine refuses to change resolution past 1024x768. Trying to change resolution would just end with it reverting to 1024x768.
6.1.12-zen1-1-zen
kernel on Arch linux, usingIntel i9-10850K
CPU. I am using virt-manager paired with looking-glassvirtual-machine xml
https://pastebin.com/jcNXuBRB
The text was updated successfully, but these errors were encountered: