CloudStack communicates to system VMs on KVM and XenServer indirectly; the host OS will SSH to the system VMs on behalf of CloudStack to run commands. For this scenario it is possible for system VMs to have a NIC on an unrouted network that only the hypervisor can access.
This is not done on VMware since the host OS is locked down and missing many commands (e.g. no "ssh" command), so CloudStack will SSH directly to system VMs on VMware. VMware system VMs therefore have an interface on the private/management network that is accessible to CloudStack. Best regards, Kirk On 03/19/2013 07:45 AM, Wang Fei wrote: > AFAIK, Vmware does not support link-local interfaces. But in practice, in > my Vmware based zone, the SSVM and CPVM did not contain this interface. But > the VR not only created this interface. but the ip address is in the same > vlan with private ip network. and I can login to VR by ssh with the > link-local ip address. > > according the wiki item, "Link-local addresses for IPv4 are defined in the > address block 169.254.0.0/16". why the link-local address of VR was not in > this subnet? why vmware can create the link-local interface for VR but SSVM > and CPVM? > > > > ---- > best regards >
