Public bug reported: I used this qemu-system-x86_64 -enable-kvm -display sdl -cpu host -net nic,model=e1000 -serial mon:stdio -m 3072 -drive format=raw,file=var/run/seoul-net.img -machine q35 to emulate a personal hypervisor. But since my ubuntu's kernel was upgraded from 5.0.0-29-generic to 5.0.0-32-generic, the hypervisor crashes during boot time and reboots. When I tried to debug, I discovered that it throws a page fault in the kernel on a specific address while the address is well mapped (checked via info mem and info tlb). I have frozen the kernel on 5.0.0-29 to continue running my hypervisor. The 5.0.0-31-generic version has also the same problem. I don't know for the other versions.
ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 27 21:37:53 2019 InstallationDate: Installed on 2019-09-14 (43 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Description changed: - I used this qemu-system-x86_64 -enable-kvm -display sdl -cpu host -net nic,model=e1000 -serial mon:stdio -m 3072 -drive format=raw,file=var/run/seoul-net.img -machine q35 to emulate a personal hypervisor. - But since my ubuntu's kernel was upgraded from 5.0.0-29-generic to 5.0.0-32-generic, the hypervisor crashes during boot time and reboots. + I used this qemu-system-x86_64 -enable-kvm -display sdl -cpu host -net nic,model=e1000 -serial mon:stdio -m 3072 -drive format=raw,file=var/run/seoul-net.img -machine q35 to emulate a personal hypervisor. + But since my ubuntu's kernel was upgraded from 5.0.0-29-generic to 5.0.0-32-generic, the hypervisor crashes during boot time and reboots. When I tried to debug, I discovered that it throws a page fault in the kernel on a specific address while the address is well mapped (checked via info mem and info tlb). - Know I freeze the kernel on 5.0.0-29 to continue running my hypervisor. The 5.0.0-31-generic version has also the same problem. I don't know for the other version. + I have frozen the kernel on 5.0.0-29 to continue running my hypervisor. The 5.0.0-31-generic version has also the same problem. I don't know for the other versions. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 27 21:37:53 2019 InstallationDate: Installed on 2019-09-14 (43 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850076 Title: Kvm does not work properly when emulating host cpu with qemu-system- x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1850076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs