Public bug reported:
Version: openstack-nova-compute-2014.2.2-1.el7.noarch
Enabling serial console causes the live migration process to fail with
the following error in nova-compute.log:
nova[12362]: 2015-05-14 21:57:21.108 ERROR nova.virt.libvirt.driver [-]
[instance: a4d0bd8f-666e-4606-9e2a-4c583719719e] Live Migration failure:
internal error: process exited while connecting to monitor: Warning: option
deprecated, use lost_tick_policy property of kvm-pit instead.
qemu-kvm: -chardev socket,id=charserial0,host=1.2.3.4,port=10000,server,nowait:
Failed to bind socket: Cannot assign requested address
qemu-kvm: -chardev socket,id=charserial0,host=1.2.3.4,port=10000,server,nowait:
chardev: opening backend "socket" failed
The host IP is coming from the proxyclient_address setting which can't
be 0.0.0.0, but even if it is changed to 0.0.0.0 the port number stays
the same and will likely conflict on the destination. If there is no
port conflict the live migration will succeed.
** Affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1455252
Title:
enabling serial console breaks live migration
Status in OpenStack Compute (Nova):
New
Bug description:
Version: openstack-nova-compute-2014.2.2-1.el7.noarch
Enabling serial console causes the live migration process to fail with
the following error in nova-compute.log:
nova[12362]: 2015-05-14 21:57:21.108 ERROR nova.virt.libvirt.driver [-]
[instance: a4d0bd8f-666e-4606-9e2a-4c583719719e] Live Migration failure:
internal error: process exited while connecting to monitor: Warning: option
deprecated, use lost_tick_policy property of kvm-pit instead.
qemu-kvm: -chardev
socket,id=charserial0,host=1.2.3.4,port=10000,server,nowait: Failed to bind
socket: Cannot assign requested address
qemu-kvm: -chardev
socket,id=charserial0,host=1.2.3.4,port=10000,server,nowait: chardev: opening
backend "socket" failed
The host IP is coming from the proxyclient_address setting which can't
be 0.0.0.0, but even if it is changed to 0.0.0.0 the port number stays
the same and will likely conflict on the destination. If there is no
port conflict the live migration will succeed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1455252/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
