VM fails to start after zesty to artful upgrade

Bug #1738619 reported by Paul Gear on 2017-12-17
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
qemu-kvm (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
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers