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#72986 - [linux] VM freezes starting with kernel 5.15
Attached to Project:
Arch Linux
Opened by th3voic3 (th3voic31) - Sunday, 12 December 2021, 12:23 GMT
Last edited by Toolybird (Toolybird) - Monday, 29 May 2023, 05:01 GMT
Opened by th3voic3 (th3voic31) - Sunday, 12 December 2021, 12:23 GMT
Last edited by Toolybird (Toolybird) - Monday, 29 May 2023, 05:01 GMT
|
DetailsDescription:
Hi, starting with kernel 5.15 I'm experiencing freezes in my VFIO Windows 10 VM. Downgrading to 5.14.16 fixes the issue. I can't find any error messages in dmesg when this happens and comparing the dmesg output between 5.14.16 and 5.15.7 didn't show any differences. Additional info: * 5.15.x * I'm attaching my libvirt config and my /etc/libvirt/hooks/qemu * My specs are: ** i7-10700k ** ASUS z490-A PRIME Motherboard ** 32 GB RAM ** Passthrough Card: NVIDIA 2070 Super ** Host is using the integrated Graphics chip Steps to reproduce: Boot any 5.15 kernel and start the VM and after some time (no specific trigger as far as I can see) the VM freezes. |
This task depends upon
Closed by Toolybird (Toolybird)
Monday, 29 May 2023, 05:01 GMT
Reason for closing: Fixed
Additional comments about closing: See comments
Monday, 29 May 2023, 05:01 GMT
Reason for closing: Fixed
Additional comments about closing: See comments
qemu.hook
win10.xml
I read about this:
20210713142023.106183-9-mlevitsk@redhat.com/#24319635"> https://patchwork.kernel.org/project/kvm/patch/20210713142023.106183-9-mlevitsk@redhat.com/#24319635
And so I checked
cat /sys/module/kvm_intel/parameters/enable_apicv
which returns Y to me by default.
So I added
options kvm_intel enable_apicv=0
to /etc/modprobe.d/kvm.conf
cat /sys/module/kvm_intel/parameters/enable_apicv
now returns N
So far I haven't encountered any freezes.
The confusing part is that APICv shouldn't be available with my CPU.
Still need to do some long-term testing.
https://bugzilla.kernel.org/show_bug.cgi?id=215459