Hello Nithin, Yes it works if a VM has multiple network adapters. Invocation is different though. Example for a VM with 2 network adapters:
$vnic = Get-VMNetworkAdapter test_2_1 $vnic[0] Connect-VMNetworkAdapter -VMNetworkAdapter $vnic[0] -SwitchName external $vnic[0] | Set-VMNetworkAdapterOVSPort -OVSPortName ovs-port-1 Connect-VMNetworkAdapter -VMNetworkAdapter $vnic[1] -SwitchName external $vnic[1] | Set-VMNetworkAdapterOVSPort -OVSPortName ovs-port-2 $vnic[1] Regards, Alin. -----Mesaj original----- De la: Nithin Raju [mailto:nit...@vmware.com] Trimis: Friday, September 26, 2014 9:35 AM Către: Alin Serdean Cc: dev@openvswitch.org Subiect: Re: [ovs-dev] [PATCH] WMI Script that updates Hyper-V friendly port names On Sep 24, 2014, at 11:18 PM, Alin Serdean <aserd...@cloudbasesolutions.com> wrote: > The following script leverage's the advantages of WMI infrastructure > offered in Hyper-V. > > This scripts allows the user to change the > Msvm_EthernetPortAllocationSettingData property of a VM network > adapter connected to a Hyper-V Virtual Switch. > > Usage: > import-module .\OVS.psm1 > $vnic = Get-VMNetworkAdapter VM1 > Connect-VMNetworkAdapter -VMNetworkAdapter $vnic -SwitchName external > $vnic | Set-VMNetworkAdapterOVSPort -OVSPortName ovs-port-1 > > VM1 - is a VM on top of a Hyper-V > external - is a Hyper-V Virtual Switch hi Alin, Will this code work if the VM has multiple adapters? It is OK if it does not, but I was just curious about it. I'll give this a shot tomorrow. thanks, Nithin _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
