I'm still running into issues with OVMF resolution setting.
This issue is referenced in an earlier thread:
https://forum.proxmox.com/threads/cant-change-screen-resolution-in-windows-10-vm.27584/
It still seems to persist in 5.4 and with the same caveats.
I have an EFI disk attached and the Resolution information is indeed saved. However, the first cold boot of the VM will always be in 800x600. The fix is to soft-reboot the VM which will then trigger it to use the correct resolution.
This is significantly annoying when host reboots are required as it means I cannot simply leave it to reboot and start VMs, but must login to each VM and reboot them manually just to get resolution parameter back.
For reference, here's my pveversion:
VM Config:
This issue is referenced in an earlier thread:
https://forum.proxmox.com/threads/cant-change-screen-resolution-in-windows-10-vm.27584/
It still seems to persist in 5.4 and with the same caveats.
I have an EFI disk attached and the Resolution information is indeed saved. However, the first cold boot of the VM will always be in 800x600. The fix is to soft-reboot the VM which will then trigger it to use the correct resolution.
This is significantly annoying when host reboots are required as it means I cannot simply leave it to reboot and start VMs, but must login to each VM and reboot them manually just to get resolution parameter back.
For reference, here's my pveversion:
Code:
root@node:~# pveversion -v
proxmox-ve: 5.4-1 (running kernel: 4.15.18-16-pve)
pve-manager: 5.4-6 (running version: 5.4-6/aa7856c5)
pve-kernel-4.15: 5.4-4
pve-kernel-4.15.18-16-pve: 4.15.18-41
pve-kernel-4.15.18-13-pve: 4.15.18-37
pve-kernel-4.15.18-9-pve: 4.15.18-30
pve-kernel-4.15.18-8-pve: 4.15.18-28
pve-kernel-4.15.17-1-pve: 4.15.17-9
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-10
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-52
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-13
libpve-storage-perl: 5.0-43
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-3
lxcfs: 3.0.3-pve1
novnc-pve: 1.0.0-3
proxmox-widget-toolkit: 1.0-28
pve-cluster: 5.0-37
pve-container: 2.0-39
pve-docs: 5.4-2
pve-edk2-firmware: 1.20190312-1
pve-firewall: 3.0-22
pve-firmware: 2.0-6
pve-ha-manager: 2.0-9
pve-i18n: 1.1-4
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 3.0.1-2
pve-xtermjs: 3.12.0-1
qemu-server: 5.0-52
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.13-pve1~bpo2
Code:
agent: 1
balloon: 0
bios: ovmf
bootdisk: scsi0
cores: 4
efidisk0: lvm-purestorage:vm-4310-disk-1,size=128K
machine: q35
memory: 4096
name: RD-test
net0: virtio=66:20:3B:CA:E9:51,bridge=vmbr0,tag=1411
numa: 1
ostype: win10
sata3: none,media=cdrom
sata4: none,media=cdrom
scsi0: lvm-purestorage:vm-4310-disk-0,size=64G
scsihw: virtio-scsi-pci
smbios1: uuid=812281cd-7630-4b84-8da5-7aa48289e73c
sockets: 1
vmgenid: f12334dc-79c6-4d30-bafb-fab0b46befef
