Skip to content

Posts from the ‘ESXi’ Category

15
May

Enable or Disable VMware 6.5 native drivers

One of my customers had a issue with the native driver igbn (version 1.3.1-1OEM.600.0.0.2768847) that was automatic loaded after install the ESXi host using the Dell Custom install media for 6.5.

After pining with Dell and VMware support desks the result was to switch from the native driver (igbn) to the standard driver (igb)(vmlinux)

Here a link to a VMware KB that gives more info on how to enable or disable native drivers.

Here the steps I followed to disable the igbn driver.

* enable SSH and connect to the ESXi server with admin right
* esxcli system module list | grep igb

* esxcli system module set –enabled=false –module=igbn
* reboot
* enable SSH and connect to the ESXi server with admin right
* esxcli system module list | grep igb

20
Jan

Allow Virtual machines with duplicate MAC address on vSphere 5.5

In a migration project to VMware vSphere 5.5 I bumped into duplicate MAC address issue (I found out after some investigation).

Some info on the setup.

There are ESXi hosts that we are migrating from 5.0 to 5.5. Some VM’s where 2 VM’s (VM1 and VM2) share the same MAC address (production and test machine).

On ESXi 5.0 these 2 VM’s can run together on the same ESXi host.

I want to move the VM’s to an already upgraded ESXi 5.5 host, the first VM (VM1 moves without any problems. ) For the second VM (VM2) I get following error during vMotion. Same error happens when I cold migrate the VM2 to the same host (ESXi 5.5) as VM1 and try to power VM2 on.

2014-01-20_15-46-12

 

 

 

 

 

 

 

 

 

After some Google research I came across following blog

http://jasonnash.com/2008/08/30/disabling-mac-address-checking-in-vmware/

And adding the advanced setting to VM2 fixed the problem.

8
Jan

Where to find VMware version information

Here some links to find version information about VMware vSphere products

http://vsphere-land.com/vinfo/release-build-info

and about VMware Tools versions

http://packages.vmware.com/tools/versions

20
Dec

How long can an ESXi host run?

Before starting an upgrade at a customer site I was surprised how long an ESXi host can run. Here the proof.

 

10
Dec

Upgrade ESXi 5.0 to 5.1 via VMware Update Manager : incompatible

Today I am at customer site to upgrade en vSphere environment to the latest and greatest version of VMware vSphere 5.1.

We started the migration process by importing the VMware ESXi image we downloaded from the VMware download website.

In Update Manager we checked the server and saw that the server was not compliant with the new ESXi version so we could start the remediation.

After the remediation started we got the following message in Update Manager stating that the server was incompatible for this upgrade.

After some research on the internet I found following VMware KB 2034945 article.

As pointed out in this article the upgrade worked after a reboot of the ESX host.

21
May

Unable to expand VMFS partition

Today I was asked to expand a local datastore of a ESXi 4.1. Expanding a disk is normally no problem when you are able to increate the size of the disk. After increasing the disk size you should be able to increate the partition size.

The ESXi was managed by a vCenter 5.0.  On the storage adapter I did a RESCAN data stores after the disk size was increased.  Then I went into the DATASTORE properties and I saw following

 

 

 

 

 

 

 

 

 

 

 

 

This above view was via a vCenter connection.  Then I found following VMware KB which told me to make a direct connection to the ESXi host.  After going to into the datastore properties I found out that I could increase.

 

 

 

 

 

 

 

 

 

 

When I selected this local datastore and finished the expansion I saw following result in the vSphere Client direct to the ESXi and via vCenter.

 

 

 

 

 

 

 

 

 

 

Lucky for the customer this expansion went OK.

Hopefully if you have this problem this KB article fixes also your problem.

Success

 

Gert Van Gorp

30
May

Unable to remove VMware ESXi host in VMware vCenter

During a migration process from ESX to ESXi at a customer site we had a problem removing a server from the vCenter inventory.

We checked the permissions on this server and we saw that the user who wanted to remove the server was admin on datacenter level. Here the screen we got.

Knowing there is a PowerCLI command to remove a ESXi host from the vCenter, we walked that way with success.

I used this
PowerCLI script to remove this server from the inventory after moving the
server out of the cluster to the datacenter level.

Connect-VIServer vCenterServer

Remove-VMHost “HostThatCannotBeRemovedViaGui” –confirm:$false

Disconnect-VIServer –confirm:$false

8
Jan

Migrating Buslogic to LSI Logic SCSI controller in a Virtual Machine

When you use convertor to migrate a physical machine to a virtual machine you get a BusLogic Controller as SCSI controller. Following is tested on vSphere 4.1 with a Virtual Machine hardware version 7

In the Virtual Machine Settings you see this.

µ

In your device manager it is present as a VMware SCSI controller

If you want to change this to a LSI Logic SCSI controller because some application may need it like Trend Micro Deep Security – vShield, you have to follow steps below to get it working

Steps to convert

  • Install the latest VMware Tools.
  • Power down the Virtual Machine (try to use the shutdown so your OS is closed correctly.)
  • Edit Settings of the Virtual Machine and add a new disk (can be small because this will be removed afterwards). We cannot add a new SCSI controller without adding a disk.
  • When you add a new disk select a different SCSI-id then the existing SCSI Controller. First number in the ID is the number of the SCSI controller.

     

  • When the disk is updated, the type of the SCSI controller must be changed.

     

  • When the configuration is updated, you can restart the VM
  • In your device manager you now see 2 types of SCSI controllers

     

  • When you see the LSI logic SCSI controller you can shut down the VM again. Then will remove the just added disk and change the type of SCSI Controller 0

     

  • When this is finished you can restart the Virtual Machine
  • After starting the Virtual Machine you see that new hardware is found, now you need to reboot once more. (Last time to reboot).
  • Now for best practices you need to remove all unused devices in you device manager. Therefor you need to start device manager using a special set parameter.
    • set devmgr_show_nonpresent_devices=1
    • devmgmt.msc

If you now select the SCSI and RAID Controllers, you will see some grayed-out devices. These devices should be uninstalled

  • Now you are done.
7
Jan

Clipboard Copy and Paste not possible in vSphere 4.1 Console connection

Hi,

I have done a lot of migration to VMware vSphere 4.1.  Everytime I bumb into the same issue: When I open a Console to a Virtual Machine and want to copy / paste some info into the Virtual Machine, it does not work anymore.

This because in vSphere 4.1 VMware has introducted one of the setting out of the Security Hardening guide for vSphere 4.0.  There ore 2 ways to bypass these settings:

  1. Use a RDP connection instead of a VMware Console connection to your Windows Machines and then the copy / paste still works (this is a best practice)
  2. Change the settings so copy / paste is allowed again.  Read this VMware KB Article
9
Nov

P2V issues with old hardware & IP addresses

Doing a P2V is very easy using the VMware Converter (Standard / Enterprise).  But after the machine has been migrated the P2V is not yet finished, we need to do some extra stuff.

  • Remove all hardware related software via add / remove programs (if possible) or disable the service.
  • Old unused devices should be removed using device manager after setting a special SET parameter (set devmgr_show_nonpresent_devices=1).  This can be done manually are using a script.
  • Update virtual hardware settings (CPU / Memory)
  • Enter the IP configuration on the new NIC.  (Can be automated)
  • Depending on the MS license you are using you maybe need to reactivate.