It seems the fix is comitted with
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1848497. Closing
this issue
** Changed in: qemu
Status: New => Fix Committed
** Changed in: qemu
Status: Fix Committed => Fix Released
** Changed in: cloud-archive
Status: New => Fix Releas
I forked that new discussion into
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1848497
Please follow there and leave this bug here to the originally reported error
signature.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
ht
> 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
> 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
Dnaiel: That's a different problem; 'Bad config data: i=0x10 read: a1
device: 1 cmask: ff wmask: c0 w1cmask:0'; so should probably be a
separate bug.
I'd bet on this being the one fixed by
2bbadb08ce272d65e1f78621002008b07d1e0f03
--
You received this bug notification because you are a member of
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: Connectio
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: qemu (Ubuntu)
Status: New => Confirmed
--
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:
virt
In regard to "similar bugs" it sounds more like [1] to me.
Which was around needing [2].
But just like the commit David mentioned is in 2.8 this one is in since
2.6 (and backported).
[1]: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1647389
[2]:
https://git.qemu.org/?p=qemu.git;a=commit;h
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
--
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
Hi Bjoern,
I don't think this is the same bug as the one you reference; that's a config
space disagreement, not a virtio queue disagreeement.
It almost feels like the old 4a1e48becab81020adfb74b22c76a595f2d02a01
stats migration fix; but that went in with 2.8 so shouldn't be a problem
going 2.10
** Description changed:
- We upgraded the libvirt UCA packages from 3.6 to 4.0 as part of a queens
upgrade and noticed that
+ 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 mig
11 matches
Mail list logo
