starting VMs causing retpoline4 to reboot
Bug #1747507 reported by
Bryan Quigley
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Critical
|
Andy Whitcroft | ||
Artful |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Using 4.13.0-
CPU: AMD Ryzen 7 1700 Eight-Core Processor
Ubuntu: 17.10.
Steps to reproduce (has occurred both times I tried it):
1. Just run kvm with no options (or virsh start <> or start VM from GUI)
Machine reboots
Going back to 4.13.0-32 has virsh working again. qemu-system-x86_64 command works fine unless you use the enable kvm command.
CVE References
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
description: | updated |
description: | updated |
Changed in linux (Ubuntu): | |
assignee: | nobody → Andy Whitcroft (apw) |
importance: | Undecided → Critical |
status: | Confirmed → In Progress |
Changed in linux (Ubuntu Artful): | |
status: | New → Fix Committed |
Changed in linux (Ubuntu): | |
status: | In Progress → Fix Released |
To post a comment you must log in.
Might be related, might not. This is displayed before the reboot.
host doesn't support requested feature: CPUID.01H:ECX.vmx [bit 5]
I did downgrade from the testing qemu packages, maybe that changed my VMs, but that still shouldn't cause a host reboot (or kvm with no options).