[
https://issues.apache.org/jira/browse/CLOUDSTACK-5644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh resolved CLOUDSTACK-5644.
---------------------------------------
Resolution: Invalid
This is a setup issue and outside the scope of cloudstack. When ip is given,
the destination host is not able to check for permissions on the smb share and
it fails migration. Migration also fails if it is tried from hyper-v manager
and cloudstack isn't involved.
> [Hyper-v] VM live migration fails if IP address is given as primary storage
> server
> ----------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-5644
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5644
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Doc, Hypervisor Controller
> Affects Versions: 4.3.0
> Environment: Hypervisor: Hyperv
> Storage: SMB for both primary and secondary storage
> Reporter: Sanjeev N
> Priority: Critical
> Labels: hyper-V,, hyper-v, hyperv
> Fix For: 4.3.0
>
>
> [Hyper-v] VM live migration fails if IP address is given as primary storage
> server.
> In CS while adding primary storage server we can specify either the IP
> address of the SMB server or the Domain name . However if the storage server
> is domain joined then vm live migration only works if the domain name of the
> server is given while adding Primary Storage in the CS.
> And the domain name is case sensitive.
> Eg: If the primary storage domain name is : Host13 and domain is BLR then in
> CS give the storage details in the same way. If we specify the Server as
> "host13" storage will be mounted on the hosts properly, but while migrating
> the vm the Domain joined hosts in the cluster will not get the access to the
> root disks present in the primary storage.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
