VM fails to start after zesty to artful upgrade

Bug #1738619 reported by Paul Gear on 2017-12-17
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
qemu (Ubuntu)
Undecided
Unassigned

Bug Description

After upgrading from zesty to artful using do-release-upgrade, a VM which previously started no longer does:

root@localhost:~# virsh list --all
 Id Name State
----------------------------------------------------
 - test shut off

root@localhost:~# virsh start test
error: Failed to start domain test
error: unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.

root@localhost:~# lsmod|grep kvm
kvm 581632 0
irqbypass 16384 1 kvm
root@localhost:~# dmesg|tail
[ 29.757516] ip6_tables: (C) 2000-2006 Netfilter Core Team
[ 29.866191] Ebtables v2.0 registered
[ 30.347237] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[ 30.350299] virbr0: port 1(virbr0-nic) entered blocking state
[ 30.350302] virbr0: port 1(virbr0-nic) entered disabled state
[ 30.350366] device virbr0-nic entered promiscuous mode
[ 30.584263] nf_conntrack version 0.5.0 (65536 buckets, 262144 max)
[ 30.695375] virbr0: port 1(virbr0-nic) entered blocking state
[ 30.695379] virbr0: port 1(virbr0-nic) entered listening state
[ 30.774039] virbr0: port 1(virbr0-nic) entered disabled state
root@localhost:~# lsb_release -rd
Description: Ubuntu 17.10
Release: 17.10

Dec 17 21:02:18 localhost libvirtd[1513]: 2017-12-17 11:02:18.161+0000: 1682: error : qemuProcessStartValidate:4619 : unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.

Paul Gear (paulgear) on 2017-12-17
summary: - VMs fail to start after zesty to artful upgrade
+ VM fails to start after zesty to artful upgrade
Andreas Hasenack (ahasenack) wrote :

Did you find out what was going on, or is this still an issue?

Changed in qemu-kvm (Ubuntu):
status: New → Incomplete

Hi Paul,
sorry I didn't see this for a long time until I got aping today.

If kvm is loaded but this message pops up it usually means the arch specific module is missing (and mostly had an issue failign to load).
So kvm_intel or kvm_amd depending on your system.

I've had this I think two times in the last few years and it was one of those mods unable to load in the past.
How about the status of these modules?

If none is loaded load them, does it work now.
If the laod fail what does dmesg tell us about it (the dmesg in the bug is of the time you started the guest, but we need the time the module was loaded)?

In general after the above what does "kvm-ok" return?

affects: qemu-kvm (Ubuntu) → qemu (Ubuntu)
Launchpad Janitor (janitor) wrote :

[Expired for qemu (Ubuntu) because there has been no activity for 60 days.]

Changed in qemu (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers