openstack team mailing list archive

[Eric Luo <nextfool@xxxxxxxxx>]

>
> Hello ,all
> I am doing live-migration with 3 nodes installation .Everything is set
> just as the official document instructed here:
> http://docs.openstack.org/trunk/openstack-compute/admin/content/configuring-live-migrations.html
>
>
> When I use the command " nova live-migration vm1 HostC" , nova wouldn't
> give me any error information.But I checked the vm with "nova show
> vm1",and found the migration is not succeeded, *vm1* is still running on
> the source compute node .I checked the /var/log/libvirt/libvirtd.log ,and
> found the following error:
>
>
> 2012-05-29 03:43:47.543+0000: 8875: error :
> virNetClientProgramDispatchError:174 : internal error process exited while
> connecting to monitor: char device redirected to /dev/pts/1
> inet_listen_opts: bind(ipv4,192.168.0.205,5900): Cannot assign requested
> address
> inet_listen_opts: FAILED
>
> 2012-05-29 06:30:29.828+0000: 8875: error :
> virNetClientProgramDispatchError:174 : Unable to read from monitor:
> Connection reset by peer
>
>
> if , I disabled the vnc by commenting out all the vnc related lines in
> /etc/nova/nova.conf on both compute nodes ,and launched a new instance *vm2
> *,then vm2 can be migrated between the two compute nodes freely without
> any error.
>
> So I guess there may be some problems with the vnc when doing live
> migration in nova? Also ,I googled and found a bug report here ,please
> check it out:
> https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=703851
>
> I don't know whether it is related to my problems here .Please tell me if
> it is a bug of nova or just something I did wrong.
>
> Thank you in advance! .
>
> Eric Luo.
>
>
> --
> Stay with me,stay with my heart,honey.....
>
> --
> Stay with me,stay with my heart,honey.....
>
>