Hello, I'm not affected by this issue. I was, but it was related to the vnc issue, after disabling the console, the live-migration is performed without any problems.
Regards. On Sat, Jun 9, 2012 at 8:59 PM, Anne Gentle <annegen...@justwriteclick.com>wrote: > Absolutely should be mentioned in the docs - thanks for uncovering! > > Anne Gentle > Content Stacker > a...@openstack.org > > > On Jun 9, 2012, at 1:49 PM, Florian Haas <florian.h...@hastexo.com> wrote: > > > On 06/07/12 14:21, Florian Haas wrote: > >> On Thu, Jun 7, 2012 at 9:53 AM, Thierry Carrez <thie...@openstack.org> > wrote: > >>> Florian Haas wrote: > >>>> a few people have reported issues with live migration lately, and > >>>> I've been digging into them to narrow them down. > >>>> > >>>> The symptom is relatively easy to describe: you run "nova > live-migration > >>>> <guest> <host>", and nothing happens. > >>>> [...] > >>>> I'd be thankful for any clues as to where to dig further. > >>> > >>> You should submit a bug on the bugtracker about that, and continue the > >>> discussion there (pointing to the bug number from here)... I'd hate to > >>> see this one fall under the radar because it's not properly tracked. > >> > >> Done: https://bugs.launchpad.net/nova/+bug/1009974 > > > > Apologies for the noise. I had mistakenly believed that since the list > > of --live_migration_flags contained spaces, it was OK to quote the > > --live_migration_* options. Evidently it's not, as removing the double > > quotes made the problem go away. My guests now do migrate. > > > > Anne/Thierry: I've thus far been unable to find any documentation that > > says "don't use double quotes in nova.conf". In fact, > > > http://docs.openstack.org/trunk/openstack-compute/admin/content/compute-options-reference.html > > uses them in several places, including the --live_migration* flags. That > > quotes can break things appears to be a known issue as per > > https://bugs.launchpad.net/nova/+bug/987473. Is this something that we > > should mention in the documentation, or is this unexpected parser > > behavior that needs to get fixed? > > > > Cheers, > > Florian > > > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp >
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp