[Bug 1575388] Re: Qemu 2.2 should be replaced by 2.5 in Kilo with Ubuntu 14.04 LTS

[Corey Bryant]

** Changed in: cloud-archive
       Status: New => Invalid

** Changed in: cloud-archive/kilo
     Assignee: (unassigned) => Billy Olsen (billy-olsen)

** Changed in: cloud-archive
     Assignee: Billy Olsen (billy-olsen) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.
https://bugs.launchpad.net/bugs/1575388

Title:
  Qemu 2.2 should be replaced by 2.5 in Kilo with Ubuntu 14.04 LTS

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive kilo series:
  New

Bug description:
  Hi,

  I've faced a strange problem with nova and qemu.
  A few enviromental details:
   - We use Ubuntu 14.04 LTS
   - We use Kilo from Ubuntu cloud archive
   - We use KVM as Hypervisor with the stocked qemu 2.2
   - We got Ceph as shared storage with libvirt-rbd devices
   - OVS neutron based networking, but it's all the same with other solutions I think.

  So, the workflow, which need to reproduce the bug:
   - Start a Windows guest (Linux distros not affected as I saw)
   - Live migrate this VM to another host (okay, I know, it's not fit 100% in cloud conception, but we must use it)

  As happend then, is a really wrong behavior:
   - The VM starts to migrate (virsh list shows it in a new host)
   - On the source side, virsh list tells me, the instance is stopped
   - After a few second, the destination host just remove the instance, and the source change it's state back to running
   - The network comes unavailable
   - The horizon reports, the instance is in shut off state and it's definietly not (the VNC is still available for example)
   - We see those lines in a specified libvirt log: "qemu-system-x86_64: load of migration failed: Invalid argument"

  After a few google search whit this error, i've found this site: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1472500
  It's not the exact error, but it's tells us a really important fact: those errors possibly came with qemu 2.2, and it's had been fixed in 2.3...

  First of all, I've installed 2 CentOS compute node, which cames with
  qemu 2.3 by default, and the Windows migration started to work as
  Linux guests did before.

  Unfortunately, we must use Ubuntu, so we needed to find a workaround,
  which had been done yesterday...

  What I did:
   - Added Mitaka repository (which came out few days before)
   - Run this command (I cannot dist-upgrade openstack now): apt-get install qemu-system qemu-system-arm qemu-system-common qemu-system-mips qemu-system-misc qemu-system-ppc qemu-system-sparc qemu-system-x86 qemu-utils seabios libvirt-bin
   - Let the qemu 2.5 installed
   - The migration tests shows us, this new packages solves the issue

  What I want/suggest, to repair this is putting qemu 2.5 in the
  original trusty kilo repository, and we will be able to upgrade
  without any 'quick and dirty' method (add-remove Mitaka repo until
  installing qemu).

  Regards,
   Peter

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1575388/+subscriptions