| 2015-02-25 17:45:50 |
Mathieu Gagné |
bug |
|
|
added bug |
| 2015-02-25 17:53:49 |
Launchpad Janitor |
qemu (Ubuntu): status |
New |
Confirmed |
|
| 2015-02-25 18:03:29 |
Robie Basak |
bug task added |
|
cloud-archive |
|
| 2015-02-26 08:12:25 |
Dr. Jens Harbott |
bug |
|
|
added subscriber Dr. Jens Rosenboom |
| 2015-02-27 19:56:06 |
Mathieu Gagné |
bug task added |
|
libvirt (Ubuntu) |
|
| 2015-03-05 21:04:12 |
Serge Hallyn |
nominated for series |
|
Ubuntu Trusty |
|
| 2015-03-05 21:04:12 |
Serge Hallyn |
bug task added |
|
qemu (Ubuntu Trusty) |
|
| 2015-03-05 21:04:12 |
Serge Hallyn |
bug task added |
|
libvirt (Ubuntu Trusty) |
|
| 2015-03-05 21:04:30 |
Serge Hallyn |
qemu (Ubuntu): importance |
Undecided |
High |
|
| 2015-03-05 21:04:40 |
Serge Hallyn |
qemu (Ubuntu Trusty): importance |
Undecided |
High |
|
| 2015-03-05 21:04:45 |
Serge Hallyn |
qemu (Ubuntu Trusty): status |
New |
Confirmed |
|
| 2015-03-05 21:04:49 |
Serge Hallyn |
libvirt (Ubuntu Trusty): importance |
Undecided |
High |
|
| 2015-03-05 21:04:51 |
Serge Hallyn |
libvirt (Ubuntu): importance |
Undecided |
High |
|
| 2015-03-05 21:04:57 |
Serge Hallyn |
libvirt (Ubuntu): status |
New |
Fix Released |
|
| 2015-03-05 21:05:01 |
Serge Hallyn |
libvirt (Ubuntu Trusty): status |
New |
Confirmed |
|
| 2015-03-05 21:05:06 |
Serge Hallyn |
qemu (Ubuntu): status |
Confirmed |
Fix Released |
|
| 2015-03-05 21:08:13 |
Serge Hallyn |
description |
This bug looks to be very similar to bug #1291321.
The source host runs 12.04 Precise with Ubuntu Cloud Archive. This means we have access to more recent QEMU packages.
The source host has QEMU 1.5 installed. (the package looks to be backported from 13.10 Saucy by UCA)
The destination host is running 14.04 Trusty with QEMU 2.0.
The machine type used by the instance I tried to live migrate is 'pc-i440fx-1.5'. (which looks to be the new default in QEMU 1.5)
When performing a live migration from QEMU 1.5 to QEMU 2.0, the migration fails with this error on the destination host:
Length mismatch: 0000:00:03.0/virtio-net-pci.rom: 20000 in != 40000
qemu: warning: error while loading state for instance 0x0 of device 'ram'
My hypothesis is that QEMU 1.5 was built against the qemu-kvm source tree. As mentionned in bug #1291321, the machine types defined in qemu-kvm are not compatible with the ones defined in qemu. This means the source 'pc-i440fx-1.5' mahine type is not compatible with the destination 'pc-i440fx-1.5' machine type.
A workaround has been introduced in QEMU 2.0 to allow incoming qemu-kvm instances (pc-1.0) to be properly translated to pc-1.0-precise) using the allow_incoming_qemukvm libvirt config.
But since the default machine type changed between QEMU 1.0 (pc-1.0) and 1.5 (pc-i440fx-1.5), the above workaround doesn't work for people running QEMU 1.5 introduced by UCA.
This means people with QEMU 1.5 on 12.04 Precise are stuck with instances they cannot migrate to a host running the latest LTS without destructive steps. |
==============================================================
SRU Justification:
Note: This fix is not applicable to vivid, because we only support migration from LTS->LTS, so from 12.04 to 14.04. Therefore a fix is only needed for 14.04
Impact: live migration of VMS from a 12.04+UCA host to 14.04 fail.
Regression potential: the patches to fix this are very similar in nature to those already in the archive for bug 1291321. Therefore we are reasonable sure they should be safe.
Test case: See below. (Start a VM of machine type pc-i440fx-1.5 on a 12.04+UCA host, and migrate it to a 14.04 host)
==============================================================
This bug looks to be very similar to bug #1291321.
The source host runs 12.04 Precise with Ubuntu Cloud Archive. This means we have access to more recent QEMU packages.
The source host has QEMU 1.5 installed. (the package looks to be backported from 13.10 Saucy by UCA)
The destination host is running 14.04 Trusty with QEMU 2.0.
The machine type used by the instance I tried to live migrate is 'pc-i440fx-1.5'. (which looks to be the new default in QEMU 1.5)
When performing a live migration from QEMU 1.5 to QEMU 2.0, the migration fails with this error on the destination host:
Length mismatch: 0000:00:03.0/virtio-net-pci.rom: 20000 in != 40000
qemu: warning: error while loading state for instance 0x0 of device 'ram'
My hypothesis is that QEMU 1.5 was built against the qemu-kvm source tree. As mentionned in bug #1291321, the machine types defined in qemu-kvm are not compatible with the ones defined in qemu. This means the source 'pc-i440fx-1.5' mahine type is not compatible with the destination 'pc-i440fx-1.5' machine type.
A workaround has been introduced in QEMU 2.0 to allow incoming qemu-kvm instances (pc-1.0) to be properly translated to pc-1.0-precise) using the allow_incoming_qemukvm libvirt config.
But since the default machine type changed between QEMU 1.0 (pc-1.0) and 1.5 (pc-i440fx-1.5), the above workaround doesn't work for people running QEMU 1.5 introduced by UCA.
This means people with QEMU 1.5 on 12.04 Precise are stuck with instances they cannot migrate to a host running the latest LTS without destructive steps. |
|
| 2015-05-07 07:59:25 |
gustavo panizzo |
bug |
|
|
added subscriber gustavo panizzo |
| 2015-05-13 16:06:36 |
Serge Hallyn |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2015-05-13 16:07:18 |
Serge Hallyn |
description |
==============================================================
SRU Justification:
Note: This fix is not applicable to vivid, because we only support migration from LTS->LTS, so from 12.04 to 14.04. Therefore a fix is only needed for 14.04
Impact: live migration of VMS from a 12.04+UCA host to 14.04 fail.
Regression potential: the patches to fix this are very similar in nature to those already in the archive for bug 1291321. Therefore we are reasonable sure they should be safe.
Test case: See below. (Start a VM of machine type pc-i440fx-1.5 on a 12.04+UCA host, and migrate it to a 14.04 host)
==============================================================
This bug looks to be very similar to bug #1291321.
The source host runs 12.04 Precise with Ubuntu Cloud Archive. This means we have access to more recent QEMU packages.
The source host has QEMU 1.5 installed. (the package looks to be backported from 13.10 Saucy by UCA)
The destination host is running 14.04 Trusty with QEMU 2.0.
The machine type used by the instance I tried to live migrate is 'pc-i440fx-1.5'. (which looks to be the new default in QEMU 1.5)
When performing a live migration from QEMU 1.5 to QEMU 2.0, the migration fails with this error on the destination host:
Length mismatch: 0000:00:03.0/virtio-net-pci.rom: 20000 in != 40000
qemu: warning: error while loading state for instance 0x0 of device 'ram'
My hypothesis is that QEMU 1.5 was built against the qemu-kvm source tree. As mentionned in bug #1291321, the machine types defined in qemu-kvm are not compatible with the ones defined in qemu. This means the source 'pc-i440fx-1.5' mahine type is not compatible with the destination 'pc-i440fx-1.5' machine type.
A workaround has been introduced in QEMU 2.0 to allow incoming qemu-kvm instances (pc-1.0) to be properly translated to pc-1.0-precise) using the allow_incoming_qemukvm libvirt config.
But since the default machine type changed between QEMU 1.0 (pc-1.0) and 1.5 (pc-i440fx-1.5), the above workaround doesn't work for people running QEMU 1.5 introduced by UCA.
This means people with QEMU 1.5 on 12.04 Precise are stuck with instances they cannot migrate to a host running the latest LTS without destructive steps. |
==============================================================
SRU Justification:
Note: This fix is not applicable to vivid, because we only support migration from LTS->LTS, so from 12.04 to 14.04. Therefore a fix is only needed for 14.04
Impact: live migration of VMS from a 12.04+UCA host to 14.04 fail.
Regression potential: the patches to fix this are very similar in nature to those already in the archive for bug 1291321. Therefore we are reasonable sure they should be safe.
Test case: See below. (Start a VM of machine type pc-i440fx-1.5 on a 12.04+UCA host, and migrate it to a 14.04 host)
Note, for the fix to work, both qemu and libvirt must have the fix.
==============================================================
This bug looks to be very similar to bug #1291321.
The source host runs 12.04 Precise with Ubuntu Cloud Archive. This means we have access to more recent QEMU packages.
The source host has QEMU 1.5 installed. (the package looks to be backported from 13.10 Saucy by UCA)
The destination host is running 14.04 Trusty with QEMU 2.0.
The machine type used by the instance I tried to live migrate is 'pc-i440fx-1.5'. (which looks to be the new default in QEMU 1.5)
When performing a live migration from QEMU 1.5 to QEMU 2.0, the migration fails with this error on the destination host:
Length mismatch: 0000:00:03.0/virtio-net-pci.rom: 20000 in != 40000
qemu: warning: error while loading state for instance 0x0 of device 'ram'
My hypothesis is that QEMU 1.5 was built against the qemu-kvm source tree. As mentionned in bug #1291321, the machine types defined in qemu-kvm are not compatible with the ones defined in qemu. This means the source 'pc-i440fx-1.5' mahine type is not compatible with the destination 'pc-i440fx-1.5' machine type.
A workaround has been introduced in QEMU 2.0 to allow incoming qemu-kvm instances (pc-1.0) to be properly translated to pc-1.0-precise) using the allow_incoming_qemukvm libvirt config.
But since the default machine type changed between QEMU 1.0 (pc-1.0) and 1.5 (pc-i440fx-1.5), the above workaround doesn't work for people running QEMU 1.5 introduced by UCA.
This means people with QEMU 1.5 on 12.04 Precise are stuck with instances they cannot migrate to a host running the latest LTS without destructive steps. |
|
| 2015-05-13 18:45:45 |
Chris J Arges |
libvirt (Ubuntu Trusty): status |
Confirmed |
Fix Committed |
|
| 2015-05-13 18:45:48 |
Chris J Arges |
bug |
|
|
added subscriber SRU Verification |
| 2015-05-13 18:45:53 |
Chris J Arges |
tags |
|
verification-needed |
|
| 2015-05-14 22:39:39 |
Brian Murray |
qemu (Ubuntu Trusty): status |
Confirmed |
Fix Committed |
|
| 2015-05-27 13:00:57 |
Stefan Kooman |
bug |
|
|
added subscriber Stefan Kooman |
| 2015-06-18 17:10:38 |
Seyeong Kim |
tags |
verification-needed |
verification-failed |
|
| 2015-06-18 19:27:32 |
Chris J Arges |
tags |
verification-failed |
|
|
| 2015-06-18 19:27:33 |
Chris J Arges |
tags |
|
verification-needed |
|
| 2015-06-22 02:34:54 |
Seyeong Kim |
bug |
|
|
added subscriber Seyeong Kim |
| 2015-06-22 02:51:43 |
Seyeong Kim |
tags |
verification-needed |
verification-failed |
|
| 2015-07-01 13:47:30 |
Launchpad Janitor |
libvirt (Ubuntu Trusty): status |
Fix Committed |
Fix Released |
|
| 2015-07-01 13:47:40 |
Chris J Arges |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2015-07-01 13:50:57 |
Chris J Arges |
libvirt (Ubuntu Trusty): status |
Fix Released |
In Progress |
|
| 2015-07-08 13:27:01 |
Chris J Arges |
libvirt (Ubuntu Trusty): status |
In Progress |
Fix Committed |
|
| 2015-07-08 13:27:03 |
Chris J Arges |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2015-07-08 13:27:09 |
Chris J Arges |
tags |
verification-failed |
|
|
| 2015-07-08 13:27:10 |
Chris J Arges |
tags |
|
verification-needed |
|
| 2015-07-08 15:01:11 |
Seyeong Kim |
tags |
verification-needed |
verification-done |
|
| 2015-07-15 18:46:50 |
Launchpad Janitor |
qemu (Ubuntu Trusty): status |
Fix Committed |
Fix Released |
|
| 2015-07-15 18:56:15 |
Launchpad Janitor |
libvirt (Ubuntu Trusty): status |
Fix Committed |
Fix Released |
|
| 2015-07-15 18:58:08 |
Chris J Arges |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2015-07-15 18:58:17 |
Chris J Arges |
removed subscriber SRU Verification |
|
|
|
| 2015-09-17 08:46:27 |
James Page |
cloud-archive: status |
New |
Fix Released |
|
