<div dir="ltr">Hello,<div><br></div><div>I've just finished implementing the changes to my production environment and found I needed to do a few more steps. I'm not sure where the difference between the test and production environments are... maybe it's because my test environment is virtual and so kvm and qemu detect things differently or maybe the package juggling in the test environment polluted the tests. No idea... anyway...</div><div><br></div><div>Upon doing an upgrade to the latest mentioned packages, I found that existing instances could then be hard-rebooted. They weren't able to before the latest round of packages, so we're off to a good start. Even more, once hard-rebooted, they could even be migrated.</div><div><br></div><div>But existing instances could not be migrated, soft-rebooted, paused, suspended, etc. Once hard-rebooted, all of those things worked.</div><div><br></div><div>I was just about to cut my losses and consider that acceptable but thought I'd dig into things further. I started reviewing all bug reports mentioned in this thread and closely read the SRU Justification here:</div><div><br></div><div><a href="https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1374622">https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1374622</a><br></div><div><br></div><div>I then configured /etc/libvirt/qemu.conf with:</div><div><br></div><div>allow_incoming_qemukvm = 1<br></div><div><br></div><div>Upon trying a migration again, I got an error about a missing pxe-virtio.rom.12.04. This was also mentioned in this bug report:</div><div><br></div><div><a href="https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1291321">https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1291321</a><br></div><div><br></div><div>So I copied the /usr/share/qemu/pxe-virtio.rom file from a compute node that wasn't yet upgraded as /usr/share/qemu/pxe-virtio.rom.12.04 on the upgraded node (and the destination node of the migration). I rebooted libvirt-bin and sure enough the migration worked!</div><div><br></div><div>Similarly, soft-rebooting et al also works. </div><div><br></div><div>And even better, once live-migrated, the instance takes on the new machine type of "pc-i440fx-trusty" so it's now compatible with 14.04.</div><div><br></div><div>So as far as I can tell, I'm in good shape. I've tested a bunch of scenarios (launching, migrating, rebooting, etc) and everything seems OK. I'll give it a few days to see if any users run into issues.</div><div><br></div><div>Thanks,</div><div>Joe</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Nov 18, 2014 at 12:44 PM, Joe Topjian <span dir="ltr"><<a href="mailto:joe@topjian.net" target="_blank">joe@topjian.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Oops - I just noticed the initial libvirt packages I pasted were wrong... too early in the morning, I guess.<div><br></div><div>I started out with:</div><div><br></div><div><div>libvirt0 1.2.2-0ubuntu13.1.2~cloud0</div><div>libvirt-bin 1.2.2-0ubuntu13.1.2~cloud0</div></div><div>python-libvirt 1.2.2-0ubuntu1~cloud0<br></div><div><br></div><div>And then moved to:</div><div><br></div><div><div style="font-family:arial,sans-serif;font-size:13px">libvirt-bin 1.2.2-0ubuntu13.1.6~cloud2</div><div style="font-family:arial,sans-serif;font-size:13px">libvirt0 1.2.2-0ubuntu13.1.6~cloud2</div><div style="font-family:arial,sans-serif;font-size:13px">python-libvirt 1.2.2-0ubuntu2~cloud0</div></div><span class="HOEnZb"><font color="#888888"><div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">Joe</div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Nov 18, 2014 at 10:49 AM, Joe Topjian <span dir="ltr"><<a href="mailto:joe@topjian.net" target="_blank">joe@topjian.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Daniele,<div><br></div><div>Here are the packages I started with in my test environment and what the initial instances were based on:</div><div><br></div><div>dpkg -l | grep qemu</div><div><div>ii kvm 1:84+dfsg-0ubuntu16+1.0+noroms+0ubuntu14.19</div><div>ii qemu-common 1.0+noroms-0ubuntu14.19 </div><div>ii qemu-kvm 1.0+noroms-0ubuntu14.19 </div><div>ii qemu-utils 1.0+noroms-0ubuntu14.19 </div><div><br></div><div>dpkg -l | grep libvirt</div><div>ii libvirt-bin 1.2.2-0ubuntu13.1.6~cloud2</div><div>ii libvirt0 1.2.2-0ubuntu13.1.6~cloud2 </div><div>ii nova-compute-libvirt 1:2014.1.3-0ubuntu1~cloud0</div><div>ii python-libvirt 1.2.2-0ubuntu2~cloud0</div></div><div><br></div><div>And here's the result after I upgraded the packages using the Icehouse cloud archive:</div><div><br></div><div>dpkg -l | grep qemu</div><div><div>ii ipxe-qemu 1.0.0+git-20131111.c3d1e78-2ubuntu1~cloud0</div><div>ii qemu-common 2.0.0+dfsg-2ubuntu1.6~cloud0</div><div>ii qemu-keymaps 2.0.0+dfsg-2ubuntu1.6~cloud0</div><div>ii qemu-kvm 2.0.0+dfsg-2ubuntu1.6~cloud0</div><div>ii qemu-system-common 2.0.0+dfsg-2ubuntu1.6~cloud0</div><div>ii qemu-system-x86 2.0.0+dfsg-2ubuntu1.6~cloud0</div><div>ii qemu-utils 2.0.0+dfsg-2ubuntu1.6~cloud0</div></div><div><br></div><div>dpkg -l | grep libvirt</div><div><div>ii libvirt-bin 1.2.2-0ubuntu13.1.6~cloud2</div><div>ii libvirt0 1.2.2-0ubuntu13.1.6~cloud2</div><div>ii nova-compute-libvirt 1:2014.1.3-0ubuntu1~cloud0</div><div>ii python-libvirt 1.2.2-0ubuntu2~cloud0</div></div><div><br></div><div>The libvirt packages (1.2.2-0ubuntu13.1.6~cloud2), I think, are the most important part to bridge everything together. These new versions for both 12.04 and 14.04 included the compatibility for vms / instances created with older qemu versions.</div><div><br></div><div>From the tests I've done so far, everything looks good. I'd love to hear if you, or others, are still seeing issues after upgrading to the latest packages.</div><div><br></div><div>Thanks,</div><div>Joe</div></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Nov 18, 2014 at 10:23 AM, Daniele Venzano <span dir="ltr"><<a href="mailto:daniele.venzano@eurecom.fr" target="_blank">daniele.venzano@eurecom.fr</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>Hi,<br>
<br>
Which versions did you test, exactly?<br>
<br>
Here I'm seeing these in APT:<br>
1.0.50-2012.03-0ubuntu2<br>
1.0.50-2012.03-0ubuntu2.1<br>
1.5.0+dfsg-3ubuntu5.4~cloud0 (havana ubuntu cloud repo)<br>
2.0.0+dfsg-2ubuntu1.6~cloud0 (icehouse ubuntu cloud repo)<br>
<br>
Thanks,<br>
Daniele<div><div><br>
<br>
On 11/17/14 21:30, Joe Topjian wrote:<br>
</div></div></div>
<blockquote type="cite"><div><div>
<div dir="ltr">Thanks, Felipe!
<div><br>
</div>
<div>I was going to wait until I did some more testing, but
since I'm on this topic:</div>
<div><br>
</div>
<div>I have done some preliminary tests with the latest libvirt
packages from Ubuntu (available in both 12.04 and 14.04). The
tests were done in a 12.04 Icehouse environment that supports
live migration. I created several instances using the stock
qemu and libvirt packages and then upgraded both sets of
packages.</div>
<div><br>
</div>
<div>Hard rebooting, live migration, and hard reboot of
live-migrated instances were all successful.</div>
<div><br>
</div>
<div>I still want to run through the tests a few more times
(especially migrating to 14.04 hosts), but it looks as though
the latest Ubuntu packages resolve any backwards compatibility
issues.</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Nov 17, 2014 at 9:12 PM, Felipe
Reyes <span dir="ltr"><<a href="mailto:freyes@tty.cl" target="_blank">freyes@tty.cl</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<span><br>
On Tue, 21 Oct 2014 13:42:24 -0600<br>
Joe Topjian <<a href="mailto:joe@topjian.net" target="_blank">joe@topjian.net</a>>
wrote:<br>
<br>
> > I wonder if the qemu update issues are in the
realm of the OpenStack<br>
> > project.<br>
> > Since they are provided / packaged by the
distro's.<br>
> > Maybe people from Ubuntu & Redhat (which I
would be interested in ;)<br>
> > reading this could give some suggestions...<br>
> ><br>
><br>
> I'd really appreciate someone from Ubuntu or Redhat
clarifying this<br>
> situation.<br>
><br>
</span>There is some work on Ubuntu's side to get a clean
migration path, see:<br>
<a href="https://lists.ubuntu.com/archives/ubuntu-server/2014-October/006983.html" target="_blank">https://lists.ubuntu.com/archives/ubuntu-server/2014-October/006983.html</a><br>
<a href="https://lists.ubuntu.com/archives/ubuntu-server/2014-November/006988.html" target="_blank">https://lists.ubuntu.com/archives/ubuntu-server/2014-November/006988.html</a><br>
<br>
Best Regards,<br>
<br>
PS: I'm not involved in any way with that development, just
read about<br>
it :)<br>
<span><font color="#888888">--<br>
Felipe Reyes (GPG:0x9B1FFF39)<br>
<a href="http://tty.cl" target="_blank">http://tty.cl</a><br>
lp:~freyes | freyes@freenode | freyes@github<br>
</font></span></blockquote>
</div>
<br>
</div>
<br>
<fieldset></fieldset>
<br>
</div></div><span><pre>_______________________________________________
OpenStack-operators mailing list
<a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a>
</pre>
</span></blockquote>
<br>
<br>
</div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>