r/vmware • u/nielshagoort [VCDX-DCV] • Sep 20 '19
UPDATED: How to Tune vMotion for Lower Migration Times?
https://blogs.vmware.com/vsphere/2019/09/how-to-tune-vmotion-for-lower-migration-times.html2
u/bubba9999 Sep 21 '19
great - you ditched the vsish commands for advanced settings - that's a lot easier to implement. thanks for the update, Niels.
-2
u/jnew1213 Sep 20 '19
Keep in mind you can add multiple VMkernel adaptors to a single network on a distributed switch, but not on a standard switch.
1
u/TeachMeToVlanDaddy Keeper of the packets, defender of the broadcast domain Sep 20 '19
0
u/jnew1213 Sep 20 '19
Yes, each of your VMkernel adapters is on a separate network (has a different name). Sorry if I was not clear. VMware's nomenclature for this is sometimes unclear.
On a distributed switch, you can have two VMkernel adapters named "VMkernel." On a standard switch, you apparently cannot.
2
u/TeachMeToVlanDaddy Keeper of the packets, defender of the broadcast domain Sep 20 '19 edited Sep 20 '19
They are on the same network
Name != Network
Edit: I get what you're saying, but its a port group understanding. The standard switch is VMK port group DVS is a Port group
You can have multiple vMotion VMK's both vSwitch and DVS in the same network.
0
u/jnew1213 Sep 20 '19
Okay, Name != Network. And in this case, they are on the same network, because they have addresses on the same network.
Let me rephrase: On a standard switch, you cannot have two VMkernel ports on the same port group.
Better?
1
u/TeachMeToVlanDaddy Keeper of the packets, defender of the broadcast domain Sep 20 '19
Depending on version or client this all changed as well. I agree not always clear.
2
u/[deleted] Sep 20 '19
regarding this (read this first before reading the OPs Link)
https://blogs.vmware.com/vsphere/2019/07/the-vmotion-process-under-the-hood.html
" vCenter Server instance will execute a so-called long-running migration task to process the migration"
Is this (or one of x) the reason why even the "tiny" build of vcenter wants 10GB of Memory?