VM guest resolution is not saved anymore
This bug report will be marked for expiration in 22 days if no further activity occurs. (find out why)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
I am running Ubuntu 24.04 as host and a VM with Ubuntu 24.04 as guest.
I am using VirtIO as driver on Spice (localhost).
The log was created from the VM.
The VMM window is set with these options:
- Scale Display: Always + Auto resize VM with window
Steps to repro:
- I set the resolution of the guest to 1920x1080
- maximize the VMM window (or change the window size in any other way)
The resolution is now 5120x2672) which is weird as the monitor is "just" 4K.
Before upgrading to 24.04 I was on 23.10 and this never occurred.
According to the "Scale Display" option, the window should stretch, making the content bigger. Instead, it resets the resolution to the maximum available which is far bigger than the supported monitor resolution.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu3
ProcVersionSign
Uname: Linux 6.8.0-35-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckR
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Jun 10 16:11:30 2024
DistUpgraded: 2024-05-30 17:43:10,553 DEBUG migrateToDeb822
DistroCodename: noble
DistroVariant: ubuntu
GraphicsCard:
Red Hat, Inc. Virtio 1.0 GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller])
Subsystem: Red Hat, Inc. Virtio 1.0 GPU [1af4:1100]
InstallationDate: Installed on 2024-02-16 (115 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU Tablet
Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU Tablet
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Lsusb-t:
/: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=
|__ Port 001: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 480M
|__ Port 002: Dev 003, If 0, Class=Human Interface Device, Driver=usbhid, 480M
/: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=
MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-
XDG_RUNTIME_
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to noble on 2024-05-30 (11 days ago)
dmi.bios.date: 04/01/2014
dmi.bios.release: 0.0
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.16.3-
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.
dmi.modalias: dmi:bvnSeaBIOS:
dmi.product.name: Standard PC (Q35 + ICH9, 2009)
dmi.product.
dmi.sys.vendor: QEMU
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.120-2build1
version.
version.
version.
version.
version.
version.
version.
summary: |
- Resolution is not saved anymore + VM guest resolution is not saved anymore |
"Scale Display: Always + Auto resize VM with window" sounds like a feature of the hypervisor. Which hypervisor are you using?
Usually to resize a VM dynamically it either uses;
(a) A custom Xorg driver in the guest (but you're not using Xorg); or
(b) Virtually hotplugging the virtual monitor with one of a new resolution.
Overall I'm not sure which software component is expected to be responsible for this. It might help to take a closer look at 23.10 where it worked and list the differences in the guest like kernel driver in use, and Wayland vs Xorg.