I checked this in house I see 3 option :
Where does it says you are combining vmkernel and vm port group .
It is still separate.
I have an existing vmkernel adapter with management service enabled , if I edit it it doesnt give me any option to make it use for virtual machine , which confirms it is still individual :
regards
Gayathri
when creating a vmkernel nic on a 6.5 u2 host, you get the option to create a new port group, or add it to an existing one:
Creating a new port group, no longer gives the choice between vmkernel or VM port group:
But i just found something out: when you take an existing port group, it becomes unavailable to the VMs already connected to it.
Same thing when creating a new VM: the port group is no longer offered as a choice.
So it appears that this is only an issue in the ESXi web client: it allows you to convert a VM Port Group into a vmkernel port group, even with VMs attached.
Maybe the port group is not really considered a VM port group until a VM is actually running on it.
Testing the same thing with a vm running:
| Failed - A specified parameter was not correct: SelectVnic.vnic |
but then it does go on and create the vmkernel nic:
while at the same time the VM appears to be connected as well:
But checking the VM configuration shows another port group:
Not getting a DHCP request on that network though, so something is not quite working.
Even after a stop/start of the VM anove screens are still the same.
Basically comes down to: as long as you keep doing stuff the way you're supposed to, it all works out.
Trying strange things, which the ui allows you to, but aren't supposed to work, yields strange results.