From: "Christian Ehrhardt " <1838569@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1838569] Re: virtio-balloon change breaks post 4.0 upgrade
Date: Thu, 17 Oct 2019 12:34:00 -0000 [thread overview]
Message-ID: <157131564016.22358.3211420100953453665.malone@wampee.canonical.com> (raw)
In-Reply-To: 156460681322.6584.3709701644111615718.malonedeb@soybean.canonical.com
> I'd bet on this being the one fixed by
> 2bbadb08ce272d65e1f78621002008b07d1e0f03
But wasn't the breakage this fixes only added in qemu 4.0?
He reports his change is from qemu 2.10 to 2.11.
Unfortunately 2bbadb08 doesn't have a "fixes" line, maybe Ubuntu has
something backported that makes the Ubuntu 2.11 being affected by it.
I checked the Delta but there was nothing related backported that I
could identify.
But I agree, that first of all this should be a new bug instead of
reviving the old one here.
P.S. this will race as I sent the same via mail :-/, but I need to
extend.
I have now realized that the later report (comment #4) is about
Openstack Train which at least on Ubuntu would come with qemu 4.0 - and
since 2bbadb08 was released only with 4.1 that would be an open issue.
--
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 Ubuntu Cloud Archive:
New
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/cloud-archive/+bug/1838569/+subscriptions
next prev parent reply other threads:[~2019-10-17 12:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 21:00 [Qemu-devel] [Bug 1838569] [NEW] virtio-balloon change breaks post 4.0 upgrade Bjoern Teipel via Qemu-devel
2019-08-01 2:58 ` [Qemu-devel] [Bug 1838569] " Bjoern Teipel via Qemu-devel
2019-08-07 10:18 ` Dr. David Alan Gilbert
2019-08-07 10:35 ` Christian Ehrhardt
2019-08-07 10:44 ` Christian Ehrhardt
2019-10-17 10:33 ` Launchpad Bug Tracker
2019-10-17 10:34 ` Daniel 'f0o' Preussker
2019-10-17 11:00 ` Dr. David Alan Gilbert
2019-10-17 12:27 ` Christian Ehrhardt
2019-10-17 12:34 ` Christian Ehrhardt [this message]
2019-10-17 12:37 ` Christian Ehrhardt
2020-02-21 15:52 ` Bjoern Teipel via
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=157131564016.22358.3211420100953453665.malone@wampee.canonical.com \
--to=1838569@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.