This bug was fixed in the package qemu - 1:3.1+dfsg-2ubuntu3.7~cloud1
---
qemu (1:3.1+dfsg-2ubuntu3.7~cloud1) bionic-stein; urgency=medium
.
*
d/p/ubuntu/lp-1848497-virtio-balloon-fix-QEMU-4.0-config-size-migration-in.patch:
fix migration issue from qemu <4.0 when using virt
I have verified the package for this specific virtio-balloon issue
discussed in this bug only.
Migrating from 3.1+dfsg-2ubuntu3.2~cloud0
- To the latest released version (3.1+dfsg-2ubuntu3.7~cloud0) fails due to
balloon setup
2020-10-26T07:40:30.157066Z qemu-system-x86_64: get_pci_config_device
Attached backported fix to bug 1847361. Fixes live migrations from
1:2.11+dfsg-1ubuntu7.32 (Queens/Rocky) and 1:3.1+dfsg-2ubuntu3.3 or
previous (Stein) to latest Stein. I also tested the migration from the
patched Stein to Train and works as expected.
--
You received this bug notification because
@vtapia is preparing the patches for qemu in Stein for this bug and bug
1847361
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848497
Title:
virtio-balloon change breaks migration from qemu prior to
The virtio_balloon_config size was changed in the Disco version of qemu because
of bug 1836154, which backported the size change in patch:
ubuntu/lp-1836154-include-update-Linux-headers-to-4.21-rc1-5.0-rc1.patch
which was introduced in qemu version 1:3.1+dfsg-2ubuntu3.4:
http://launchpadlibrarian
> please see https://bugs.launchpad.net/cloud-archive/+bug/1882416
ok i marked that bug as a dup of this one, and we'll prepare the patches
for Stein using this bug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
** Also affects: cloud-archive/stein
Importance: Undecided
Status: New
** Changed in: cloud-archive/stein
Status: New => Triaged
** Changed in: cloud-archive/stein
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
** Changed in: cloud-archive
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848497
Title:
virtio-balloon change breaks migration from qemu prior to 4.0
To manage
** Also affects: cloud-archive/train
Importance: Undecided
Status: New
** Also affects: cloud-archive/ussuri
Importance: Undecided
Status: New
** Changed in: cloud-archive/train
Status: New => Fix Released
** Changed in: cloud-archive/ussuri
Status: New => Fix R
Thanks for your pointers, please see https://bugs.launchpad.net/cloud-
archive/+bug/1882416
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848497
Title:
virtio-balloon change breaks migration from q
BTW 2.11 -> 3.1 without the cloud archive in mind matches a migration from
Bionic to Disco.
I have checked my test logs (a bit ago since Disco itself is EOL).
But at least this January 13 and 16th the migrations 2.11 -> 3.1 still were ok.
In my log that was between
B: qemu: 1:2.11+dfsg-1ubuntu7.2
Hi Sam,
Stein would atm be on "qemu - 1:3.1+dfsg-2ubuntu3.7~cloud0" and that matches
your versions as reported.
3.1 didn't have the particular bug that was discussed and fixed here as
it was only broken by a later commit [1] in qemu 4.0.
Therefore I'd ask you to file a new bug report for it.
Nev
I'm seeing what I think is this issue for the stein cloud archive
packages.
Source host (openstack rocky release):
qemu-system-x86:
Installed: 1:2.11+dfsg-1ubuntu7.26
Destination host (openstack stein release):
qemu-system-x86:
Installed: 1:3.1+dfsg-2ubuntu3.7~cloud0
Live Migration failure:
This bug was fixed in the package qemu - 1:4.0+dfsg-0ubuntu9.2
---
qemu (1:4.0+dfsg-0ubuntu9.2) eoan; urgency=medium
* d/p/ubuntu/lp-1848556-curl-Handle-success-in-multi_check_completion.patch:
fix a potential hang when qemu or qemu-img where accessing http backed
disks via
$ virsh migrate --unsafe --live f-testmigrate qemu+ssh://10.253.194.110/system
(no messages)
With the update from proposed is migrating just fine from Disco to Eoan
now.
Setting verified
** Tags removed: verification-needed verification-needed-eoan
** Tags added: verification-done verification-d
Hello Christian, or anyone else affected,
Accepted qemu into eoan-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/qemu/1:4.0+dfsg-
0ubuntu9.2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:
This was tonight first accepted and then immediately rejected as it was
surpassed by a security fix.
=> Rebased and uploaded 1:4.0+dfsg-0ubuntu9.2 to eoan-unapproved again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
Focal is complete the MPs reviewed, SRU Teamplates ready and pre-tests done.
Uploading to E-unapproved for the SRU Teams consideration.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848497
Title:
v
This bug was fixed in the package qemu - 1:4.0+dfsg-0ubuntu10
---
qemu (1:4.0+dfsg-0ubuntu10) focal; urgency=medium
* d/p/ubuntu/lp-1848556-curl-Handle-success-in-multi_check_completion.patch:
fix a potential hang when qemu or qemu-img where accessing http backed
disks via l
FYI: uploaded to 20.04 Focal, considering SRUs (Eoan) after this
completes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848497
Title:
virtio-balloon change breaks migration from qemu prior to 4.0
Now that Focal is open I have opened proper Focal MP replacing the old one and
also an Eoan SRU MP right away.
=>
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/374770
=>
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/374771
** Description cha
** Also affects: qemu (Ubuntu Focal)
Importance: High
Assignee: Christian Ehrhardt (paelzer)
Status: Confirmed
** Also affects: qemu (Ubuntu Eoan)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu Eoan)
Status: New => Triaged
** Changed in: qemu (Ubu
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/374771
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848497
Title:
virtio-balloon change break
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/374770
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848497
Title:
virtio-balloon change break
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/374446
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848497
Title:
virtio-balloon change break
FYI: The fix in my PPA worked
I can start uploading as soon as Focal is open.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848497
Title:
virtio-balloon change breaks migration from qemu prior to 4
With a migration Bionic to Eoan with a balloon device I can confirm
this.
Guestconfig:
root@testkvm-bionic-from:~# virsh migrate --unsafe --live testguest
qemu+ssh://10.192.69.27/system
error: internal error: qemu unexpectedly closed the monitor:
2019-10-21T13:44:16.1551
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848497
Title:
virtio-balloon change breaks migration from qemu prior to 4.0
To manage notifications about this bug go to:
h
28 matches
Mail list logo
