[jira] [Resolved] (CLOUDSTACK-5684) kvm - Not able to live migrate Vms outside of cloudstack because of vnc ipaddress being tied up to 1 kvm host.

["edison su (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-5684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

edison su resolved CLOUDSTACK-5684.
-----------------------------------

    Resolution: Won't Fix

It's by design, community changes the vnc listening address to private address of kvm host instead of wildcard *, to make it safer.
Our kvm agent code can workaround this issue, by dynamically change the vnc listening address during the vm migration. So there should not be a problem if the vm is migrated through cloudstack UI.
But it may have a problem when migrating vm out-of-band.

> kvm - Not able to live migrate Vms outside of cloudstack because of vnc ipaddress being tied up to 1 kvm host.
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-5684
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5684
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.3.0
>         Environment: Build from 4.3
>            Reporter: Sangeetha Hariharan
>            Assignee: edison su
>            Priority: Critical
>             Fix For: 4.3.0
>
>
> kvm - Not able to live migrate Vms outside of cloudstack because of vnc ipaddress being tied up to 1 kvm host.
> Steps to reproduce the problem:
> Advanced zone set up with 2 KVM hosts.
> Deploy few Vms in both hosts. 
> Try to live migrate Vm outside of cloudplatform.
> Live migration fails :
> root@Rack3Host14 CloudPlatform-4.3-997-rhel6.3]# virsh migrate --live i-3-5-VM qemu+ssh://10.223.58.130/system
> The authenticity of host '10.223.58.130 (10.223.58.130)' can't be established.
> RSA key fingerprint is fb:07:f7:7e:84:a9:97:7c:3d:35:2a:9e:72:43:75:c5.
> Are you sure you want to continue connecting (yes/no)? yes
> root@10.223.58.130's password:
> error: Cannot recv data: Warning: Permanently added '10.223.58.130' (RSA) to the list of known hosts.
> : Connection reset by peer3.58.130
> [root@Rack3Host14 CloudPlatform-4.3-997-rhel6.3]#
> When I removed the ipadress entry for the VNC from the Vms , we are able to live migrate the Vms successfully.
> To enable live migration:
> <graphics type='vnc' port='5905' autoport='yes'/>
> Current vnc port entries : 
>    <graphics type='vnc' port='5901' autoport='yes' listen='10.223.58.130'>
>       <listen type='address' address='10.223.58.130'/>
>     </graphics>



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)