Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#77821 - [linux] upgrade linux 6.2.2.arch1-1 to 6.2.2.arch2-1 results in failing qdisk
Attached to Project:
Arch Linux
Opened by Arthur Borsboom (ArthurBorsboom) - Sunday, 12 March 2023, 12:24 GMT
Last edited by Toolybird (Toolybird) - Sunday, 12 March 2023, 23:30 GMT
Opened by Arthur Borsboom (ArthurBorsboom) - Sunday, 12 March 2023, 12:24 GMT
Last edited by Toolybird (Toolybird) - Sunday, 12 March 2023, 23:30 GMT
|
DetailsDescription:
After upgrading kernel 6.2.2.arch1-1 to linux 6.2.2.arch2-1 in Dom0 of the Xen Hypervisor, all virtual machines fail to start. Downgrading 'kernel' and 'kernel-headers' back to 6.2.2.arch1-1 restores the functionality. A kernel upgrade a couple of days before (6.0.12.arch1-1 -> 6.2.2.arch1-1), did not result in this breakage. The error message reported in the xen logging is (example of 1 VM): qemu-system-i386: failed to create 'qdisk' device '51712': failed to create drive: Could not stat file '/dev/nvme0n1p12': No such file or directory The partition referred in the error message does exist and is accessible. I am not sure if this is a Xen, Libvirt, Qemu or kernel issue, but the problem gets resolved by the downgrade from '6.2.2.arch2-1' to '6.2.2.arch1-1'. Additional info: * package version(s) xen 4.17.0-1 (Xen Hypervisor) xen-pvhgrub 2.11.119.3c60d90-1 xen-qemu 7.2.0-1 kernel: 6.2.2.arch2-1 (Xen Dom0) libvirt-xen 9.0.0-1 qemu-audio-spice 7.2.0-3 qemu-base 7.2.0-3 qemu-block-curl 7.2.0-3 qemu-block-dmg 7.2.0-3 qemu-block-nfs 7.2.0-3 qemu-block-ssh 7.2.0-3 qemu-chardev-spice 7.2.0-3 qemu-common 7.2.0-3 qemu-hw-display-qxl 7.2.0-3 qemu-hw-display-virtio-gpu 7.2.0-3 qemu-hw-display-virtio-gpu-gl 7.2.0-3 qemu-hw-display-virtio-gpu-pci 7.2.0-3 qemu-hw-display-virtio-gpu-pci-gl 7.2.0-3 qemu-hw-display-virtio-vga 7.2.0-3 qemu-hw-display-virtio-vga-gl 7.2.0-3 qemu-hw-s390x-virtio-gpu-ccw 7.2.0-3 qemu-hw-usb-host 7.2.0-3 qemu-hw-usb-redirect 7.2.0-3 qemu-hw-usb-smartcard 7.2.0-3 qemu-img 7.2.0-3 qemu-pr-helper 7.2.0-3 qemu-system-x86 7.2.0-3 qemu-system-x86-firmware 7.2.0-3 qemu-tools 7.2.0-3 qemu-ui-curses 7.2.0-3 qemu-ui-opengl 7.2.0-3 qemu-ui-spice-app 7.2.0-3 qemu-ui-spice-core 7.2.0-3 qemu-virtiofsd 7.2.0-3 Steps to reproduce: Upgrade kernel in Dom0 to 6.2.2.arch2-1 Reboot Dom0 systemctl start libvirtd VM's fail to start Errors in: /var/log/xen/qemu-dm-*.log |
This task depends upon
Closed by Toolybird (Toolybird)
Sunday, 12 March 2023, 23:30 GMT
Reason for closing: None
Additional comments about closing: See comments
Sunday, 12 March 2023, 23:30 GMT
Reason for closing: None
Additional comments about closing: See comments
https://github.com/archlinux/linux/compare/v6.2.2-arch1...v6.2.2-arch2
In the config / packaging CONFIG_EFI_HANDOVER_PROTOCOL was re-enabled:
https://github.com/archlinux/svntogit-packages/compare/7e9c5b59807312ca5c1a49f6c17f571b39a9265f...cce69da8b2bac00534f0817555ef6815de90dead
These changes appear unrelated to your issue.
I can't wrap my head around it yet.
I will try another kernel upgrade in the upcoming one or two weeks.
If the problem does magically disappears, then it is all good to me and I will close this ticket.
At least there is a note of this encountered issue, just in case other people might have a similar issue (although unlikely).