Support migration from 12.04

Bug #1374622 reported by Serge Hallyn
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libvirt (Ubuntu)
Won't Fix
High
Unassigned
Trusty
Fix Released
High
Unassigned

Bug Description

Bug 1291321 shows that qemu VMs cannot be migrated from a host running 12.04 to a host running 14.04.

https://wiki.ubuntu.com/QemuPTMigration explains the proposed solution.

One part of the problem is that libvirt in trusty cannot distinguish a pc-1.0 machine being migrated from 12.04 from a pc-1.0 being migrated from 14.04. libvirt needs a flag to tell it which to use when a pc-1.0 VM is migrated to it. This only needs to be done for Trusty. Any VM running on precise can be migrated to trusty with this flag set, which will change the machine type to pc-1.0-precise. From there on it can be migrated to utopic and beyond with no special casing in libvirt.

Note this depends on bugs 1374612 and 1374617, to define the machine type and provide the binary roms which are needed for the pc-1.0-precise machine type to be usable by libvirt.

=============================================================================
SRU Justification

Impact: VM scannot be migrated from precise to trusty
Test case: XXX NOTE XXXX: This requires the proposed fixes for 1374617 and 1374612 as well.
 set up libvirt on a precise and a trusty host;
 add a root ssh key on the precise host and place it in the authorized_hosts file for root on the tursty host;
 restart libvirt on the trusty host.
 start a pc-1.0 vm on precise
 migrate the vm, i.e.:
  virsh migrate --live --p2p --tunnelled --copy-storage-all vm1 qemu+ssh://trusty-host-ip/system
 This should fail. Now edit /etc/libvirt/qemu.conf on the trusty host and add:
  allow_incoming_qemukvm = 1
 restart libvirt. Retry migration, should now work.
Regression potential: this should change nothing if the new assume_incoming_qemukvm is not set.
=============================================================================

Changed in libvirt (Ubuntu):
status: New → Won't Fix
Changed in libvirt (Ubuntu Trusty):
importance: Undecided → High
Changed in libvirt (Ubuntu):
importance: Undecided → High
Revision history for this message
Chris J Arges (arges) wrote : Please test proposed package

Hello Serge, or anyone else affected,

Accepted libvirt into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/libvirt/1.2.2-0ubuntu13.1.6 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in libvirt (Ubuntu Trusty):
status: New → Fix Committed
tags: added: verification-needed
description: updated
Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

verified with trusty-proposed. (Using virtio net and shared nfs storage)

tags: added: verification-done
removed: verification-needed
Revision history for this message
Adam Conrad (adconrad) wrote : Update Released

The verification of the Stable Release Update for libvirt has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libvirt - 1.2.2-0ubuntu13.1.6

---------------
libvirt (1.2.2-0ubuntu13.1.6) trusty-proposed; urgency=medium

  * 9029-ovs-delete-port-if-it-exists-when-adding-new-one: cherrypick commit
    33445ce from upstream (LP: #1343262)
  * fix migration failure with ssh password authentication (LP: #1365947)
    - 9030-virsh-add-keepalive-in-new-vshconnect-fn
    - 9031-cmdmigrate-move-vshconnect-before-vshwatchjob
    - 9032-virsh-initialize-vsh-data-in-cmdmigrate
  * libvirt-bin.postinst: check for confiles whichhave been removed rather
    than fail package install (LP: #1375910)
  * Support incoming migration from 12.04 hosts (LP: #1374622)
    - debian/patches/support-incoming-qemu-kvm: add a flag to
      /etc/libvirt/qemu.conf to specify whether pc-1.0 came from a 12.04 host
    - Add a note in README.Debian.
 -- Serge Hallyn <email address hidden> Tue, 30 Sep 2014 13:54:31 -0500

Changed in libvirt (Ubuntu Trusty):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.