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
* enable SSH and connect to the ESXi server with admin right
* esxcli system module list | grep igb
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.
After some Google research I came across following blog
And adding the advanced setting to VM2 fixed the problem.
Before starting an upgrade at a customer site I was surprised how long an ESXi host can run. Here the proof.
A lot of my customers are running the vCenter Appliance version 5.1. Now they start to ask to upgrade this appliance to the newest version.
Here I will show you step by step the upgrade process. This is based on the VMware KB article 2058441
- Verify the time set on the old (VMware vCenter 5.1) appliance and the new (VMware vCenter 5.5) appliances are in sync. Be aware that from version 5.5 the clock on the appliance is always set to the UTC time zone. In the older version you could select your own tome zone. (see VMware KB)
- Be sure SSO (if installed on separate machine) is on the same version of the vCenter you want to upgrade to.
- If the vCenter database is external, make backup on the Database server. For backing up the embedded database look at this KB
- Create a snapshot of the OLD vCenter appliance before you start the upgrade procedure.
- First step of the upgrade procedure is deploying a fresh VM of the latest vCenter Appliance.
- Next is to configure the VM so that network connectivity is possible. The only thing that needs to be configured is IP address, subnet and gateway. The Original vCenter hostname and IP settings will be configured (copied) in the NEW vCenter Appliance based on the setting of the old vCenter.
- Connect to the old and new vCenter appliance via a supported web browser. (personal experience is that IE works and Chrome not! For the upgrade process.
On the NEW vCenter, Accept the EULA
- Next step in the upgrade process is to specify that you want to upgrade from a previous version
- Still in the NEW appliance, copy the local appliance code to the clipboard
On the OLD vCenter appliance, go to the Upgrade tab and paste the clipboard content in the text box and press the import button.
If the import was successful you get a notice and then copy the upgrade key back to the clipboard
On the NEW server paste the upgrade key in the bottom text box and proceed by clicking the next button.
There is an option to replace the SSL certificates on the NEW with those ones from the OLD vCenter Appliance
Now the new SSO password must be entered for the SSO administrator account firstname.lastname@example.org. (this was admin@system-domain in pre 5.5 versions)
Select now all the servers that need to check for compatibility with the new vCenter
After pressing next we see that we are ready to start the migration.
Pressing next will get following screen where you have to confirm that the upgrade process can proceed.
When you hit the start, the migration process start.
When you start the migration you will notice that the OLD vCenter server will be shut downed and the NEW vCenter server will have the IP configuration (hostname, IP settings) of the OLD ESX host.
After a successful upgrade you can start upgrading the ESXi hosts to the latest ESXi version.
- Can you login in the new vCenter Appliance via the Web Client and everything works fine you can remove the old vCenter Appliance from the inventory and from disk.
During an upgrade at a customer site we removed a Dell Appliance that was connected to vCenter. We dit remove the aplliance just by powering it off and then remove it from the entry. Normally you should do an unregister from in the Dell Appliance.
Now we saw that there was a plugin that could not be loaded.
After some research on the internet I passed by on the website of William Lam (virtuallyGhetto).
He has written a nice article that describes step by step how to fix the problem we had. Look here.
Problem solved, thanks William for the good work.
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.
Gert Van Gorp
I get a lot of questions of students and customers about resizing a virtual disk. This is the reason for this blog.
The following procedure will guide you step by step through the process of resizing (increasing) a disk of a virtual machine.
Before you make virtual hardware changes be sure you have taken a full backup of the virtual machine.
NOTE: If you do not want any troubles only increase the disk size. Decreasing can cause loss of data.
Increase Disk using diskpart
Step 1: Edit the virtual machine settings and increase the size of the disk (VMDK).
Step 2: Open the console of this virtual machine and start a command prompt.
Step 3: Start diskpart and execute following steps.
à this gives you a list of the available partitions
select volume x
à select the partition number you want to increase
à this will add the empty disk space into the partition.
Now the partition has increased in size.
NOTE: On Windows 2008 this can be done via the Device Manager / Storage, but I have seen some weird things like showing incorrect partition sizes.
Increase Disk using Third Party tool
Step 1: Be sure you have a boot image (ISO) of the Acronis Disk Director Tool that supports your guest OS.
Step 2: Boot your virtual machine using the boot image ISO. Use the ESC button during booting your virtual machine to activate the “one time boo menu”
Step 3: Select the partition you want to increase and right mouse click on it. Then select “Resize Volume”
Step 4: Increase the disk space of the selected partitions by decreasing the unallocated space to 0
Step 5: After increasing the partition you have to commit the changes.
Step 6: Now you need to reboot your virtual machine after disconnecting the boot image.
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.
Remove-VMHost “HostThatCannotBeRemovedViaGui” –confirm:$false
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
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.