VM /ETC

Archive for the ‘how to’ Category

Managing and troubleshooting ESXi 4 can be a little alien when an administrator is used to the Service Console of ESX Classic. Specifically, troubleshooting remote connectivity to the ESX management interface after adding a second NIC involves local esxcfg-vswitch commands on ESX, but with ESXi the esxcfg commands are only available via the RCLI. Problem is you can’t use the RCLI if you lost remote management connectivity! Luckily, the local ESXi GUI lets you reconfigure your mistake and re establish remote connections.

Hit F2 on the ESXi Console and enter the System Configuration Menu

  Choose to Configure Management Network > Network Adapters

Read the rest of this entry »

http://kb.vmware.com/kb/1010718 explains the normal way for disabling and removing a VMware ESX/ESXi vNetwork Distributed Switch (vDS or DVS or VDS – LOL), but when I recently tried to do so I received the following error:

“The resource ‘1′ is in use. DVS [vDS Name] port 1 is reserved by to entity <not-found.> vnic 4000, type:vmVnic”

The screen shot shows the actual error I received.

After thinking about that message, I decided to check to see if any ports were in fact being used on the vDS. Although PortID 1 dvPortGroups did not show it being used as expected, other PortIDs were, in fact, in use. See image below.

I tried messing around with disabling the ports (blocking was the terminology in the vSphere Client, I believe) but I still could not delete the vDS. It was Saturday and I had family stuff to do so I reluctantly gave up at the time. However, 3 days later I was able to easily remove it via the Remove link on vDS Configuration screen just like I was supposed to be able to do all along. Needless to say I was a bit perplexed.

After researching I discovered that

Read the rest of this entry »

The LackRack

Most of my colleagues have a home lab with at least some equipment that is rackable, but because of expense, room size, or the decor concerns of a much smarter significant other purchasing a data center rack is not possible (or advisable). In fact, our servers, storage and switches are stacked under a desk, piled in a corner, or hidden in a coat closet. Virtualization and server consolidation has helped reduce the total amount of hardware we need running at home, but we still end up with a makeshift and cluttered workspace that keeps us in the dog house.

Now, imagine this conversation:

Yes, going to IKEA with your Love is a dangerous undertaking, but it’s a reality to consider for your home lab.

The IKEA Lack tables are the perfect size

Read the rest of this entry »

I created a Windows 7 virtual machine in VMware Player, ran it for a while on my Windows notebook, and then decided to move it to one of my Ubuntu machines and host it in VirtualBox. I had no problem copying the folder and files between the different host based hypervisors. VirtualBox can use a virtual disk in the VMware .vmdk format so it was just a matter of file transfers between computers. VirtualBox has it’s own Guest Editions (or host tools) to add functionality and improve performance, so I needed to make that switch inside the VM too. My problem was that I did not remove the VMware Tools before I moved the VM.

When I went to uninstall VMware Tools after powering the VM on Ubuntu and in VirtualBox I received a message that “no VMware Products were detected”. Luckily, I quickly figured out I wasn’t the first to attempt this move and experience this hurdle. The post Uninstalling VMware tools when not running on a VMware host tells the same tale and provides the answer.

“I added the VMware Tools ISO to that VM and opened a command prompt. Then I found the “setup.exe” or “setup64.exe” files on the cd. Run those in the cmd window with a /c switch. (example:  ”setup64.exe /c” )  This will remove the Tools.  I installed the VirtualBox additions and then reboot.  On my Windows 2008 server it crashed on first reboot, then then I tried again and it loaded up just fine.  Network works and everything! Yay!”

On my Windows host with VMware Player installed (VMware Workstation has a similar location) the windows.iso file was found at C:\program files(x86)\VMware\VMware Player\windows.iso. Your path needs to be adjusted based on whether you have a 32 bit or 64 bit OS obviously. Mine was a 64 bit host even though the directory was at c:\program files(x86), by the way.

I’ll let you figure out your preferred method on how to copy the windows.iso file to the Ubuntu host, but once you do you can:

Read the rest of this entry »

I’ve had my share of difficulties with the HP Server Utilities after a P2V migration. Granted, when you are building a new server the SmartStart CD makes life easy for completing the “Setup and installation for HP ProLiant ML and DL 300, 500 and 700 series and HP ProLiant BL Servers and supported server options”, but when that server restarts as a VM with the HP software still installed and running it is sluggish and slow. Extremely sluggish and slow in my experience.

After having to boot several VMs in Windows Safe Mode in order to prevent the various HP utilities and drivers from attempting to load I finally got a clue and made sure I disabled all HP Services before running the P2V conversion. That made the start up as a new VM better, but I still had to spend some quality time with Add/Remove Programs in the Windows Control Panel to uninstall all of those HP programs!

You may be thinking “OK. You should just uninstall all the HP Programs and Drivers before the P2V.” I could, but there goes my safety net, fall back plan. I want the physical server to remain operational exactly as it was in case something unexpected prevents the P2V from succeeding. It’s rare, but if it does happen I want to be able to power back on the physical server. Maintenance windows are short and I’m not one to make my night longer than necessary.

Looks like one of my GestaltIT Tech Field Day brothers has made my next late night date with HP server migrations a little easier. Simon Seagrave’s post VMware P2V – Easy Method to Remove HP Agents and Utilities is about the HP Proliant Support Pack Cleaner v1.1 utility available from ctxadmtools.musumeci.com.ar – a site self described as full of “FREE Tools for Citrix, Microsoft and VMware Administrators and Consultants.”

I haven’t tried this utility myself yet, there doesn’t appear to be any documentation for it, and Seagrave doesn’t mention how/when he uses the utility, so I’ll have to figure out later if my process of disabling all the HP services works with this Support Pack Cleaner. I imagine it’ll work fine. I’ll just run it after I boot the migrated VM for the first time.

Sorry Windows Control Panel and Add/Remove Programs, we’ve spent a lot of time together over the years but it’s time for me to move on. Thanks Simon!

Seagrave has also previously posted about a script to do the same job. Check out both of his posts!

If you are looking at various options to automate virtual machine (VM) ip address reconfiguration when failing over virtual machines to a disaster recovery (DR) site, this post explains an option so simple it is beautiful. To give full credit, the Vizioncore vReplicator 2.5 Best Practices document enlightened me to the strategy of using a local only VMware vSwitch and an extra virtual NIC (vNIC) in each VM. It’s been a long time since I had a “ton of bricks” moment, but this concept crashed down on me with the realization of a configuration that works in any version of ESX, doesn’t require extra software or hardware, and better yet, doesn’t have to be scripted! Just configure some extra virtual networking and forget about it!

Here is a general outline for automating the DR ip addressing with this method:

At the Primary Site

• For these instructions assume the production vSwitch at the primary site has a Portgroup named VM Network
• Build a new vSwitch and do not attach any physical NICs (local only isolated switch). Create a Portgroup named DR Network
• For each VM you need to fail over to a DR site, add an extra vNIC and attach it to the DR Network Portgroup

At the DR Site

• Create your DR site production vSwitch, attach physical NICs and add a Portgroup named DR Network.
• Create another vSwitch and do not attach any physical NICs (local only isolated switch). Create a Portgroup named VM Network

All you have to do for this to work is

Read the rest of this entry »

How to increase the number of simultaneous VMotions of guests allowed between VMware ESX hosts has been covered many times already. In fact, check out the following blog posts on this topic for extra information and insight not provided here.

• Increase Simultaneous VMotions as well as Increase Performance
• Guest blog entry: VMotion performance » broche.net – VMware …
• VMware Communities: ESX Tips: Increase number of VMotions per host
• Increase number of VMotions per host

One possible scenario for changing this setting would be to temporarily increase VMotions allowed in order to evacuate ESX hosts within a short maintenance window. I prefer to leave the setting at the default, so for this scenario be sure to change it back after the maintenance is complete. if you read the links provided above, others suggest they have changed the settings permanently.

This rest of this post contains a cut and paste of the steps necessary to make the configuration change with a brief explanation about setting the appropriate value. I am pasting from a VMware Partner PDF communication assembled by Michael White, VMware engineer.

Read the rest of this entry »