Major slowness with get-vm using 1.0 build

[jbarr]

Hey all,

With great anticipation I installed the new build however get-vm now takes a full 5 minutes longer than with the beta. It seems like there is a timeout that is happening before it finally works. Here are results from beta build vs ga build:

I have 260+ VMs on VC running the release build of 2.5.

Beta

PS C:\> measure-command {$vm=get-vm}

Days : 0

Hours : 0

Minutes : 0

Seconds : 20

Milliseconds : 570

Ticks : 205704576

TotalDays : 0.000238084

TotalHours : 0.005714016

TotalMinutes : 0.34284096

TotalSeconds : 20.5704576

TotalMilliseconds : 20570.4576

GA

PS C:\> measure-command {$vm=get-vm}

Days : 0

Hours : 0

Minutes : 5

Seconds : 27

Milliseconds : 731

Ticks : 3277319374

TotalDays : 0.00379319371990741

TotalHours : 0.0910366492777778

TotalMinutes : 5.46219895666667

TotalSeconds : 327.7319374

TotalMilliseconds : 327731.9374

Thanks

[admin]

Let's try to address this in two parts, first is a script for anyone brave enough to make the switch:

$vms = get-vm
foreach ($vm in $vms) {
 $adapters = $vm | get-networkadapter
 foreach ($adapter in $adapters) {
  if ($adapter.Type -eq "Vmxnet") {
   if ($adapter.ConnectionState.StartConnected) {
    new-networkadapter -vm $vm `
                                 -networkname $adapter.NetworkName `
                                 -startconnected `
                                 -type flexible
   } else {
    new-networkadapter -vm $vm `
                                 -networkname $adapter.NetworkName `
                                 -type flexible
   }
   $adapter | remove-networkadapter
  }
 }
}

I've also attached the script since our forum is developer-challenged. Anyway, that script will convert all vmxnet adapters to flexible.

The other question is "What are the results of making this change?" I'm not the expert here, but here's a good resource to look at. My interpretation is that the flexible adapter type causes the vmxnet adapter to be used if tools is installed in the guest and vlance if it's not. In other words, it seems that if you make this conversion on VMs that have tools installed, you shouldn't see any difference in the guest from a configuration or performance point of view. Unfortunately I can't really say that with any degree of certainty.

[jguidroz]

I checked my environment.

Count Name

-

---

-

---

65 Flexible

113 Vmxnet

I never installed the Beta, so I can't comment on any differences in time. It's interesting that people had no issues with the Beta, but now have issues with the final version, and it's due to the type of network adapter on the VMs.

Has anyone tested the script posted? How will running this script affect running VM's?

[jasonah]

Count Name

-

---

-

---

262 Flexible

128 Vmxnet

30 e1000

1 EnhancedVmxnet

get-vm on a single vm takes about 4 minutes regardless of what type of adapter it has configured.

-Jason

[admin]

get-vm on a single vm takes about 4 minutes regardless of what type of adapter it has configured.

The reason for this is that filtering is being done on the client side. I asked several knowledgeable people around here and they said that due to architectural limitations the filtering has to happen on the client side.

[admin]

Hi everyone, we've identified the solution to this problem and I want to understand if we should make a special release to fix it or not. Please vote in our poll, which you can find on the left-hand side of the screen when you visit the front page of the VI Toolkit community.

Thanks.

[rt7500]

Count Name Group

-

---

-

---

-

---

1704 Flexible {Network Adapter 1, Network Adapter 1, Network Adapter 1, Network Adapter 1...}

58 Vmxnet {Network Adapter 1, Network Adapter 1, Network Adapter 1, Network Adapter 1...}

1 e1000 {Network Adapter 1}

[admin]

Hi everyone,

Update 1 is posted and should resolve all slowness problems. You can download it as always at http://vmware.com/go/powershell

Carter Shanklin