Clinton's VM did have virtio only network, as well as mine, and I also thought the same about the e1000 emulation not being anywhere close to host kernel. Anyway, I have been trying to reproduce this issue with the attached VMs definition with no success.
To be honest, I'm starting to suspect on the CPU flags and microcode for the specific CPUs. I'm wondering if any HW mitigation, from those CPU's new microcodes, are stepping into our way here. I haven't tested with apparmor enabled, that might be my next step here. GRUB_CMDLINE_LINUX_DEFAULT=" ..." In kernels: - linux-image-5.0.0-32-generic - linux-image-5.0.0-34-generic - linux-image-5.3.0-21-generic With and without host HW/kernel mitigations: pti=off kpti=off nopcid noibrs noibpb spectre_v2=off nospec_store_bypass_disable mds=off l1tf=off With qemus: - 1:3.1+dfsg-2ubuntu3.5 - 1:4.0+dfsg-0ubuntu10 with and without CPU flags: - <feature policy='require' name='arch-capabilities'/> - <feature policy='require' name='skip-l1dfl-vmentry'/> with and without: - all spice configuration (just like given example) - with regular vnc basic configuration (no audio, usbs) with Windows 2019: - Standard Evaluation - Build 17763.rs5_release.180914-1434 with machine types: - i440fx - q35 with the following CPU: Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 39 bits physical, 48 bits virtual CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 2 Core(s) per socket: 2 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 142 Model name: Intel(R) Core(TM) i5-7300U CPU @ 2.60GHz Stepping: 9 -- 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
