My current suggestion would be to try changing the following CPU
features:
<feature policy='require' name='clflushopt'/>
<feature policy='require' name='md-clear'/>
<feature policy='require' name='stibp'/>
<feature policy='require' name='ssbd'/>
<feature policy='require' name='pdpe1gb'/>
<feature policy='require' name='invtsc'/>
<feature policy='require' name='arch-capabilities'/>
<feature policy='require' name='skip-l1dfl-vmentry'/>
>From the virtual machines in question and checking if that mitigates the
issue (removing first half, and trying, removing the second half,
keeping the first one, and trying, and so on).
That can be achieved with:
virsh edit <machine>
by deleting the lines and re-adding them.
Another attempt to try would be (with and/or without the CPU features)
try to disable all security mitigations from the host and reproduce the
issue.
That can be achieve by changing:
GRUB_CMDLINE_LINUX_DEFAULT="pti=off kpti=off nopcid noibrs noibpb
spectre_v2=off nospec_store_bypass_disable mds=off l1tf=off ..."
in /etc/default/grub and running "update-grub".
And a last one would be to disable apparmor and check.
That can also be achieved by changing:
GRUB_CMDLINE_LINUX_DEFAULT="... apparmor=0"
in /etc/default/grub and running "update-grub".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849720
Title:
Running VM with Virtual NIC Crashes Host OS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1849720/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
