It works completely different for VMWare and HyperV. Currently on which virtual switch the control nic of hyperv is present? Is there any failure while creating VR on hyper-V? Share the agent and mgmt. logs at the time of failure.
Thanks Rajesh Battala -----Original Message----- From: 穆凯辉 [mailto:k...@landhightech.com] Sent: Friday, December 19, 2014 9:21 AM To: dev@cloudstack.apache.org Subject: 答复: hyper-v VR does not have management network Hyper-v nics without name parameter: {"deviceId":1,"networkRateMbps": -1,"defaultNic":false,"uuid":"dbc356b5-79ca-4f83-9df9-038f89290c89","ip":"19 2.168.10.110","netmask":"255.255.255.0","gateway":"192.168.10.254","mac":"02 :00:40:6f:00:06","broadcastType":"Native","type":"Control","isSecurityGroupE nabled":false} VMware exsi nics with name parameter vSwitch0. {"deviceId":1,"networkRateMbps":-1,"d efaultNic":false,"uuid":"f1ea1c22-e4fa-4a25-9e75-221920982c76","ip":"192.168 .10.150","netmask":"255.255.255.0","gateway":"192.168.10.254","mac":"02:00:5 d:40:00:07","broadcastType":"Native","type":"Control","isSecurityGroupEnable d":false,"name":"vSwitch0"} We have management virtual switch in Hyper-v host for the management and storage network traffic. Thank you very much -----邮件原件----- 发件人: Rajesh Battala [mailto:rajesh.batt...@citrix.com] 发送时间: 2014年12月19日 11:37 收件人: dev@cloudstack.apache.org 主题: RE: hyper-v VR does not have management network When I checked in the pasted log, In the nic json details all the nics have names . Name value is present in each nic details. All the nics have either "public" or "guest" names. Thanks Rajesh Battala -----Original Message----- From: 穆凯辉 [mailto:k...@landhightech.com] Sent: Friday, December 19, 2014 6:11 AM To: dev@cloudstack.apache.org Subject: 答复: hyper-v VR does not have management network We also check the cloud agent status in VR vm, the process of which also exists in VR. -----邮件原件----- 发件人: Rajesh Battala [mailto:rajesh.batt...@citrix.com] 发送时间: 2014年12月18日 22:17 收件人: dev@cloudstack.apache.org 主题: RE: hyper-v VR does not have management network Are you using traffic lables? Hyperv will work only in dedicated zone only , you cannot replace esx host with hyperv host and make the zone to work. There are no issues with VR to run on Hyperv. It works well. If you are using traffic lables, make sure the traffic lable matches to vswitch name on the hyperv host. If there is not matching vswitch name it can fail creating the VM. Thanks Rajesh Battala -----Original Message----- From: 穆凯辉 [mailto:k...@landhightech.com] Sent: Thursday, December 18, 2014 3:38 PM To: dev@cloudstack.apache.org Subject: hyper-v VR does not have management network Hi, We use hyper-v as the hypervisor for cloudstack 4.4.1. The ssvm and cpvm start successfully. But the VR vm can not connect to the cloudstack management. We found that the VR vm used guest virtual switch for the first and second network, and public virtual switch for the third network, and several network without virtual switch. So we checked the log in cloudstack management, and found the parameters to create the CR vm, shown as follows: 2014-12-18 16:48:21,045 DEBUG [c.c.h.h.r.HypervDirectConnectResource] (DirectAgent-152:ctx-17dca502) POST response is [{"com.cloud.agent.api.StartAnswer":{"result":true,"details":null,"vm":{"id" :27,"name":"r-27-VM","type":"DomainRouter","cpus":1,"minSpeed":500,"maxSpeed ":500,"minRam":134217728,"maxRam":134217728,"arch":"x86_64","os":"Debian GNU/Linux 5.0 (64-bit)","bootArgs":" template=domP name=r-27-VM eth2ip=192.168.20.154 eth2mask=255.255.255.0 gateway=192.168.20.254 eth0ip=10.1.1.1 eth0mask=255.255.255.0 domain=cs2cloud.internal cidrsize=24 dhcprange=10.1.1.1 eth1ip=192.168.10.110 eth1mask=255.255.255.0 mgmtcidr=192.168.20.0/24 localgw=192.168.10.254 type=router disable_rp_filter=true extra_pubnics=2 dns1=61.177.7.1 dns2=192.168.10.3 nic_macs=02:00:3d:47:00:02|02:00:40:6f:00:06|06:96:80:00:00:37|02:00:48:ab:0 0:1a|02:00:18:2f:00:1b|02:00:78:3c:00:1c|02:00:1b:aa:00:1d|02:00:79:37:00:1e ","rebootOnCrash":false,"enableHA":true,"limitCpuUse":false,"enableDynamical lyScaleVm":false,"vncPassword":"aa9ef9b5fb278d27","params":{},"uuid":"af08f8 42-49a9-4c24-8eb9-9e8fb89aea7c","disks":[{"data":{"org.apache.cloudstack.sto rage.to.VolumeObjectTO":{"uuid":"22b14554-2172-4502-a125-4b2a4e0228c1","volu meType":"ROOT","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataSto reTO":{"uuid":"88e26dcb-f058-36a7-a616-1f876b837977","id":4,"poolType":"SMB" ,"host":"192.168.10.6","path":"/primary?user=cloudadmin&domain=cloud","port" :445,"url":"SMB://192.168.10.6/primary?user=cloudadmin&domain=cloud/?ROLE=Pr imary&STOREUUID=88e26dcb-f058-36a7-a616-1f876b837977"}},"name":"ROOT-27","si ze":1124355072,"path":"22b14554-2172-4502-a125-4b2a4e0228c1","volumeId":28," vmName":"r-27-VM","accountId":2,"format":"VHD","id":28,"deviceId":0,"hypervi sorType":"Hyperv"}},"diskSeq":0,"path":"22b14554-2172-4502-a125-4b2a4e0228c1 ","type":"ROOT","_details":{"managed":"false","storagePort":"445","storageHo st":"192.168.10.6","volumeSize":"1124355072"}}],"nics":[{"deviceId":2,"netwo rkRateMbps":200,"defaultNic":true,"uuid":"be7dc9f2-eff8-4a7e-8229-ffb3be8f04 af","ip":"192.168.20.154","netmask":"255.255.255.0","gateway":"192.168.20.25 4","mac":"06:96:80:00:00:37","dns1":"61.177.7.1","dns2":"192.168.10.3","broa dcastType":"Vlan","type":"Public","broadcastUri":"vlan://untagged","isolatio nUri":"vlan://untagged","isSecurityGroupEnabled":false,"name":"public"},{"de viceId":0,"networkRateMbps":200,"defaultNic":false,"uuid":"b31abe5f-5f6d-414 3-9581-05f7ab68906a","ip":"10.1.1.1","netmask":"255.255.255.0","mac":"02:00: 3d:47:00:02","dns1":"61.177.7.1","dns2":"192.168.10.3","broadcastType":"Vlan ","type":"Guest","broadcastUri":"vlan://397","isolationUri":"vlan://397","is SecurityGroupEnabled":false,"name":"guest"},{"deviceId":1,"networkRateMbps": -1,"defaultNic":false,"uuid":"dbc356b5-79ca-4f83-9df9-038f89290c89","ip":"19 2.168.10.110","netmask":"255.255.255.0","gateway":"192.168.10.254","mac":"02 :00:40:6f:00:06","broadcastType":"Native","type":"Control","isSecurityGroupE nabled":false},{"deviceId":3,"networkRateMbps":-1,"defaultNic":false,"ip":"0 .0.0.0","netmask":"255.255.255.255","gateway":"192.168.20.254","mac":"02:00: 48:ab:00:1a","dns1":"61.177.7.1","dns2":"192.168.10.3","broadcastType":"Vlan ","type":"Public","broadcastUri":"vlan://untagged","isolationUri":"vlan://un tagged","isSecurityGroupEnabled":false,"name":"public"},{"deviceId":4,"netwo rkRateMbps":-1,"defaultNic":false,"ip":"0.0.0.0","netmask":"255.255.255.255" ,"gateway":"192.168.20.254","mac":"02:00:18:2f:00:1b","dns1":"61.177.7.1","d ns2":"192.168.10.3","broadcastType":"Vlan","type":"Public","broadcastUri":"v lan://untagged","isolationUri":"vlan://untagged","isSecurityGroupEnabled":fa lse,"name":"public"},{"deviceId":5,"networkRateMbps":-1,"defaultNic":false," ip":"0.0.0.0","netmask":"255.255.255.255","gateway":"192.168.20.254","mac":" 02:00:78:3c:00:1c","dns1":"61.177.7.1","dns2":"192.168.10.3","broadcastType" :"Vlan","type":"Public","broadcastUri":"vlan://untagged","isolationUri":"vla n://untagged","isSecurityGroupEnabled":false,"name":"public"},{"deviceId":6, "networkRateMbps":-1,"defaultNic":false,"ip":"0.0.0.0","netmask":"255.255.25 5.255","gateway":"192.168.20.254","mac":"02:00:1b:aa:00:1d","dns1":"61.177.7 .1","dns2":"192.168.10.3","broadcastType":"Vlan","type":"Public","broadcastU ri":"vlan://untagged","isolationUri":"vlan://untagged","isSecurityGroupEnabl ed":false,"name":"public"},{"deviceId":7,"networkRateMbps":-1,"defaultNic":f alse,"ip":"0.0.0.0","netmask":"255.255.255.255","gateway":"192.168.20.254"," mac":"02:00:79:37:00:1e","dns1":"61.177.7.1","dns2":"192.168.10.3","broadcas tType":"Vlan","type":"Public","broadcastUri":"vlan://untagged","isolationUri ":"vlan://untagged","isSecurityGroupEnabled":false,"name":"public"}]},"conte xtMap":{}}}] Yesterday we used vmware exsi as the hypervisor for cloudstack 4.4.1. The ssvm, cpvm and VR vm all start successfully. And we can create vm instance in vmware exsi hosts. Today we use the same advanced network configuration, and just change the vmware esxi to hyper-v 2012 r2. So we also checked the “right” logs for VR vm creating in vmware-esxi as follows: 2014-12-17 16:48:00,078 INFO [c.c.h.v.r.VmwareResource] (DirectAgent-74:ctx-d417ac10 192.168.10.139) Executing resource StartCommand: {"vm":{"id":18,"name":"r-18-VM","bootloader":"HVM","type":"DomainRouter","cp us":1,"minSpeed":500,"maxSpeed":500,"minRam":134217728,"maxRam":134217728,"h ostName":"r-18-VM","arch":"x86_64","os":"Debian GNU/Linux 5.0 (64-bit)","platformEmulator":"debian5Guest","bootArgs":" template=domP name=r-18-VM eth2ip=192.168.20.56 eth2mask=255.255.255.0 gateway=192.168.20. 254 eth0ip=10.1.1.1 eth0mask=255.255.255.0 domain=cs2cloud.internal cidrsize=24 dhcprange=10.1.1.1 eth1ip=192.168.10.150 eth1mask=255.255.255.0 mgmtcidr=192.168.20.0/24 localgw=192.168.10.254 type=router disable_rp_filter=true extra_pubnics=2 dns1=61.177.7.1 dns2=8.8.8.8 nic_macs=02:00:30:c5:00:02|02:00:5d:40:00:07|06:e8:82:00:00:3a|02:00:62:05:0 0:09|02:00:24:b8:00:0a","rebootOnCrash":false,"enableHA":true,"limitCpuUse": false,"enableDynamicallyScaleVm":false,"vncPassword":"2fda0728638c93a5","par ams":{"nicAdapter":"E1000","vmware.reserve.cpu":"false","vmware.reserve.mem" :"false"},"uuid":"03721ec8-d9d2-413a-85aa-5ebd1ca253b5","disks":[{"data":{"o rg.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"f6433d21-4a84-42ba- bd49-d1d3869a9e44","volumeType":"ROOT","dataStore":{"org.apache.cloudstack.s torage.to.PrimaryDataStoreTO":{"uuid":"bb3c9625-7134-4185-b79d-3f7c2fea0538" ,"id":1,"poolType":"LVM","host":"192.168.10.139","path":"datastore-18","port ":0,"url":"LVM://192.168.10.139/datastore-18/?ROLE=Primary&STOREUUID=bb3c962 5-7134-4185-b79d-3f7c2fea0538"}},"name":"ROOT-18","size":2621440000,"path":" ROOT-18-000001","volumeId":18,"vmName":"r-18-VM","accountId":2,"chainInfo":" {\"diskDeviceBusName\":\"scsi0:0\",\"diskChain\":[\"[datastore1 (2)] r-18-VM/ROOT-18-000001.vmdk\"]}","format":"OVA","id":18,"deviceId":0,"hyperv isorType":"VMware"}},"diskSeq":0,"path":"ROOT-18-000001","type":"ROOT","_det ails":{"managed":"false","storagePort":"0","storageHost":"192.168.10.139","v olumeSize":"2621440000"}}],"nics":[{"deviceId":2,"networkRateMbps":200,"defa ultNic":true,"uuid":"c1943fb8-4d33-4f6c-9561-93e24cfa0441","ip":"192.168.20. 56","netmask":"255.255.255.0","gateway":"192.168.20.254","mac":"06:e8:82:00: 00:3a","dns1":"61.177.7.1","dns2":"8.8.8.8","broadcastType":"Vlan","type":"P ublic","broadcastUri":"vlan://untagged","isolationUri":"vlan://untagged","is SecurityGroupEnabled":false,"name":"vSwitch1,,vmwaresvs"},{"deviceId":0,"net workRateMbps":200,"defaultNic":false,"uuid":"a15f81ec-2f93-4e53-8c76-0217ea6 7c107","ip":"10.1.1.1","netmask":"255.255.255.0","mac":"02:00:30:c5:00:02"," dns1":"61.177.7.1","dns2":"8.8.8.8","broadcastType":"Vlan","type":"Guest","b roadcastUri":"vlan://316","isolationUri":"vlan://316","isSecurityGroupEnable d":false,"name":"vSwitch2,,vmwaresvs"},{"deviceId":1,"networkRateMbps":-1,"d efaultNic":false,"uuid":"f1ea1c22-e4fa-4a25-9e75-221920982c76","ip":"192.168 .10.150","netmask":"255.255.255.0","gateway":"192.168.10.254","mac":"02:00:5 d:40:00:07","broadcastType":"Native","type":"Control","isSecurityGroupEnable d":false,"name":"vSwitch0"},{"deviceId":3,"networkRateMbps":-1,"defaultNic": false,"ip":"0.0.0.0","netmask":"255.255.255.255","gateway":"192.168.20.254", "mac":"02:00:62:05:00:09","dns1":"61.177.7.1","dns2":"8.8.8.8","broadcastTyp e":"Vlan","type":"Public","broadcastUri":"vlan://untagged","isolationUri":"v lan://untagged","isSecurityGroupEnabled":false},{"deviceId":4,"networkRateMb ps":-1,"defaultNic":false,"ip":"0.0.0.0","netmask":"255.255.255.255","gatewa y":"192.168.20.254","mac":"02:00:24:b8:00:0a","dns1":"61.177.7.1","dns2":"8. 8.8.8","broadcastType":"Vlan","type":"Public","broadcastUri":"vlan://untagge d","isolationUri":"vlan://untagged","isSecurityGroupEnabled":false}]},"hostI p":"192.168.10.139","executeInSequence":false,"wait":0} We checked these two logs and found that there was no “name” parameter in nics with deviceId 1 in hyper-v VR creating parameters, but the “name” parameter exists in vmware exsi VR Creating parameters with name “vSwitch0” which is the management virtual switch in vmware esxi . So we guess that the management virtual switch has be change to the guest virtual switch in some locations when there is no name parameter in creating VR vm which should be the management virtual switch in hyper-v host. Is this a bug for VR vm creating in hyper-v host? Thank you very much. khmu