With recent release of OpenStack Train this issue reappears...
Upgrading from Stein to Train will require all VMs to be hard-rebooted
to be migrated as a final step because Live Migration fails with:
Oct 17 10:28:43 h2.1.openstack.r0cket.net libvirtd[1545]: Unable to read from
monitor: Connection reset by peer
Oct 17 10:28:43 h2.1.openstack.r0cket.net libvirtd[1545]: internal error: qemu
unexpectedly closed the monitor: 2019-10-17T10:28:42.981201Z
qemu-system-x86_64: get_pci_config_device: Bad config data: i=0x10 read: a1
device: 1 cmask: ff wmask: c0 w1cmask:0
2019-10-17T10:28:42.981250Z qemu-system-x86_64: Failed to load PCIDevice:config
2019-10-17T10:28:42.981263Z qemu-system-x86_64: Failed to load
virtio-balloon:virtio
2019-10-17T10:28:42.981272Z qemu-system-x86_64: error while loading state for
instance 0x0 of device '0000:00:05.0/virtio-balloon'
2019-10-17T10:28:42.981391Z qemu-system-x86_64: warning: TSC frequency mismatch
between VM (2532609 kHz) and host (2532608 kHz), and TSC scaling unavailable
2019-10-17T10:28:42.983157Z qemu-system-x86_64: warning: TSC frequency mismatch
between VM (2532609 kHz) and host (2532608 kHz), and TSC scaling unavailable
2019-10-17T10:28:42.983672Z qemu-system-x86_64: load of migration failed:
Invalid argument
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1838569
Title:
virtio-balloon change breaks post 4.0 upgrade
Status in QEMU:
New
Status in qemu package in Ubuntu:
Confirmed
Bug description:
We upgraded the libvirt UCA packages from 3.6 to 4.0 and qemu 2.10 to 2.11
as part of a queens upgrade and noticed that
virtio-ballon is broken when instances live migrate (started with a prior 3.6
version) with:
2019-07-24T06:46:49.487109Z qemu-system-x86_64: warning: Unknown firmware
file in legacy mode: etc/msr_feature_control
2019-07-24T06:47:22.187749Z qemu-system-x86_64: VQ 2 size 0x80 <
last_avail_idx 0xb57 - used_idx 0xb59
2019-07-24T06:47:22.187768Z qemu-system-x86_64: Failed to load
virtio-balloon:virtio
2019-07-24T06:47:22.187771Z qemu-system-x86_64: error while loading state for
instance 0x0 of device '0000:00:05.0/virtio-balloon'
2019-07-24T06:47:22.188194Z qemu-system-x86_64: load of migration failed:
Operation not permitted
2019-07-24 06:47:22.430+0000: shutting down, reason=failed
This seem to be the exact problem as reported by
https://lists.gnu.org/archive/html/qemu-devel/2019-07/msg02228.html
Listed the packages which changed:
Start-Date: 2019-07-06 06:40:55
Commandline: /usr/bin/apt-get -y -o Dpkg::Options::=--force-confdef -o
Dpkg::Options::=--force-confold install libvirt-bin python-libvirt qemu
qemu-utils qemu-system qemu-system-arm qemu-system-mips qemu-system-ppc
qemu-system-sparc qemu-system-x86 qemu-system-misc qemu-block-extra qemu-utils
qemu-user qemu-kvm
Install: librdmacm1:amd64 (17.1-1ubuntu0.1~cloud0, automatic),
libvirt-daemon-driver-storage-rbd:amd64 (4.0.0-1ubuntu8.10~cloud0, automatic),
ipxe-qemu-256k-compat-efi-roms:amd64
(1.0.0+git-20150424.a25a16d-0ubuntu2~cloud0, automatic)
Upgrade: qemu-system-mips:amd64 (1:2.10+dfsg-0ubuntu3.8~cloud1,
1:2.11+dfsg-1ubuntu7.13~cloud0), qemu-system-misc:amd64
(1:2.10+dfsg-0ubuntu3.8~cloud1, 1:2.11+dfsg-1ubuntu7.13~cloud0),
qemu-system-ppc:amd64 (1:2.10+dfsg-0ubuntu3.8~cloud1,
1:2.11+dfsg-1ubuntu7.13~cloud0), python-libvirt:amd64 (3.5.0-1build1~cloud0,
4.0.0-1~cloud0), qemu-system-x86:amd64 (1:2.10+dfsg-0ubuntu3.8~cloud1,
1:2.11+dfsg-1ubuntu7.13~cloud0), libvirt-clients:amd64
(3.6.0-1ubuntu6.8~cloud0, 4.0.0-1ubuntu8.10~cloud0), qemu-user:amd64
(1:2.10+dfsg-0ubuntu3.8~cloud1, 1:2.11+dfsg-1ubuntu7.13~cloud0),
libvirt-bin:amd64 (3.6.0-1ubuntu6.8~cloud0, 4.0.0-1ubuntu8.10~cloud0),
qemu:amd64 (1:2.10+dfsg-0ubuntu3.8~cloud1, 1:2.11+dfsg-1ubuntu7.13~cloud0),
qemu-utils:amd64 (1:2.10+dfsg-0ubuntu3.8~cloud1,
1:2.11+dfsg-1ubuntu7.13~cloud0), libvirt-daemon-system:amd64
(3.6.0-1ubuntu6.8~cloud0, 4.0.0-1ubuntu8.10~cloud0), qemu-system-sparc:amd64
(1:2.10+dfsg-0ubuntu3.8~cloud1, 1:2.11+dfsg-1ubuntu7.13~cloud0),
qemu-user-binfmt:amd64 (1:2.10+dfsg-0ubuntu3.8~cloud1,
1:2.11+dfsg-1ubuntu7.13~cloud0), qemu-kvm:amd64 (1:2.10+dfsg-0ubuntu3.8~cloud1,
1:2.11+dfsg-1ubuntu7.13~cloud0), libvirt0:amd64 (3.6.0-1ubuntu6.8~cloud0,
4.0.0-1ubuntu8.10~cloud0), qemu-system-arm:amd64
(1:2.10+dfsg-0ubuntu3.8~cloud1, 1:2.11+dfsg-1ubuntu7.13~cloud0),
qemu-block-extra:amd64 (1:2.10+dfsg-0ubuntu3.8~cloud1,
1:2.11+dfsg-1ubuntu7.13~cloud0), qemu-system-common:amd64
(1:2.10+dfsg-0ubuntu3.8~cloud1, 1:2.11+dfsg-1ubuntu7.13~cloud0),
qemu-system:amd64 (1:2.10+dfsg-0ubuntu3.8~cloud1,
1:2.11+dfsg-1ubuntu7.13~cloud0), libvirt-daemon:amd64 (3.6.0-1ubuntu6.8~cloud0,
4.0.0-1ubuntu8.10~cloud0)
End-Date: 2019-07-06 06:41:08
At this point the instances would have to be hard rebooted or
stopped/started to fix the issue for future live migration attemps
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1838569/+subscriptions
