Allowing VMware ESX Private Virtual Networks to Migrate
When VMs are placed on a private virtual switch they have no external physical NIC so are generally not allowed to be moved from one host to another with vMotion. You must first power them down then power them on.
This impediment implies that private test labs and those virtual switches that sit behind virtual firewalls suffer from this in ability.
Yet there is a solution.
If you modify the file C:\Document and Settings\All Users\Application Data\VMware\VMware VirtualCenter\vpxd.cfg with the following additions before the closing </config> you can enable vMotion for these virtual networks.
 <migrate><test><CompatibleNetworks>
<VMOnVirtualIntranet>false</VMOnVirtualIntranet>
</CompatibleNetworks></test></migrate>
Now all your VMs will participate within vMotion, but just remember that a private network is private to an VMware ESX host and NOT an VMware Cluster. Therefore if you migrate one, you will have to migrate them all if they need to intercommunicate.
Sign up for ITworld's Daily newsletter
Follow ITworld on Twitter @IT_world
Esther Schindler
If the comments are ugly, the code is ugly
claird
SVG a graphics format for 21st century
pasmith
Take Chrome OS for a test spin
Sandra Henry-Stocker
Solaris Tip: Have Your Files Changed Since Installation?
jfruh
Android fragments vs. the iPhone monolith
mikelgan
What Gizmodo missed about the Pro WX Wireless USB disk drive
Where Google Chrome security fails: the password
I heard mention that the Chrome OS will have some sort of encryption available a la bitlocker. If it's possible to encrypt personal data using another password or key, then it may have potential for very secure data.... And Ubuntu has an 'encrypt home directory' option, perhaps google should follow suit.
- Dann
Join the conversation here
Quick, practical advice for IT pros. Made fresh daily.
Want to cash in on your IT savvy? Send your tip to tips@itworld.com. If we post it, we'll send you a $25 Amazon e-gift card.
