Apologies for the delay. I can't even seem to reproduce the original
issue on the affected hardware before upgrading, so I can't confirm the
fix in vivid or wily.
I'd be fine with closing this can (no longer) reproduce—maybe my
recollection is playing funny tricks on me.
--
You received this
Public bug reported:
In the thread at
http://thread.gmane.org/gmane.comp.emulators.kvm.devel/127042/focus=129294,
three commits were identified to fix live migration for qemu 2.0 (at
least), which I am using on trusty. I would like to get these pulled-in
by the package maintainer.
I have
That's awesome. I just got a chance to test it out, and with a couple
hiccups (below), I seem to have successfully migrated a guest from a
precise host to a new trusty one.
It looks like qemu failed to build in Serge's PPA due to the spice that
also lives in that PPA. I built the qemu from the
This is also blocking a precise - trusty migration for me.
Would it be possible / feasible to provide a pc-1.0-precise machine
type in qemu for trusty and an updated libvirt for precise that allows
you to change the machine attribute on the type element for migration,
so I could specify a
Then perhaps this is a documentation bug instead. --hint force_hosts
is the currently-documented method in the Compute Administration Manual:
http://docs.openstack.org/trunk/openstack-compute/admin/content/specify-
host-to-boot-instances-on.html
--
You received this bug notification because you
I ran into the same problem. It seems that HostState.passes_filters
gets called with different data in filter_properties than it expects.
The attached patch makes it work, but I doubt it's a completely correct
solution, since I don't handle more than one host in the force_hosts
list.
** Patch
