Reviewed: https://review.openstack.org/9179
Committed:
http://github.com/openstack/openstack-manuals/commit/da29b30ead43a3b53d8092f63f3b2aaa5761d32a
Submitter: Jenkins
Branch:stable/essex
commit da29b30ead43a3b53d8092f63f3b2aaa5761d32a
Author: Lorin Hochstein lo...@nimbisservices.com
Date:
Reviewed: https://review.openstack.org/8383
Committed:
http://github.com/openstack/openstack-manuals/commit/e5e6e85ccef04063c275b4fd420ebb4477325bb5
Submitter: Jenkins
Branch:master
commit e5e6e85ccef04063c275b4fd420ebb4477325bb5
Author: Florian Haas flor...@hastexo.com
Date: Sun Jun 10
Hi Hokuto Hoshi,
I had the same problem too.
Thank you very much, VNC and live-migration now works very well.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1009974
Title:
nova
Hi,
I had the same problem, and I couldn't solve it by above ways (remove
double quote and add live_migration_flag in nova.conf).
VM (on Host1 ) - Host2
Host1's ip address is 192.168.0.1
Host2's ip address is 192.168.0.2
I set the configuration of VNC in nova.conf as below:
# on Host1
@mdieder, you do realize that qemu+tcp://%s-x/system will only work in
a situation like the one I originally described? I.e. you have to have a
second IP address on that box, which is resolvable as hostname-x from
the other host. Also, that whitespace before your VIR_MIGRATE_TUNNELLED
would likely
http://review.openstack.org/8383 submitted to the openstack-manuals
repo.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1009974
Title:
nova live-migration fails silently
To manage
** Changed in: openstack-manuals
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1009974
Title:
nova live-migration fails silently
To manage
** Changed in: openstack-manuals
Assignee: (unassigned) = Florian Haas (fghaas)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1009974
Title:
nova live-migration fails silently
** Changed in: openstack-manuals
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1009974
Title:
nova live-migration fails silently
To manage
For anyone else affected by this issue, please see Bug #987473.
In this case, it was apparently caused by the presence of double quotes around
the --live_migration_uri and
--live_migration_flag values. Removing the double quotes immediately made the
issue go away.
** Changed in: nova
Closing as invalid, as this is more of a documentation on general
config-file parsing issue, rather than one caused by nova-compute
directly.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
Added this as a doc bug, here's a copy-paste from an email from Florian:
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
I have the same problem.
I changed the nova.conf:
--live_migration_uri=qemu+tcp://%s-x/system
--live_migration_flag=VIR_MIGRATE_UNDEFINE_SOURCE,VIR_MIGRATE_PEER2PEER,
VIR_MIGRATE_TUNNELLED
and
nova live-migration bd8474bc-2c93-4df8-ae04-372f10471b96 cloud02
But nothing happens. In the logs
** Also affects: nova (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1009974
Title:
nova live-migration fails silently
To manage
14 matches
Mail list logo
