Please refer to following post for basic troubleshooting of Emulex OneConnect.
How to Install Proper Drivers for 3rd Party Network Adapter on ESXi 5.x
I have a box uses Emulex OneConnect OCe10102 network adapters. The adapter is quite old and Emulex brand card doesn’t support ESXi 6.0. I upgraded the server to ESXi 6.0 and the Emulex adapters lost.
In the initial troubleshooting, I noticed that the adapters are still visible in BIOS. So it should be some driver level issues. I checked VMware Compatibility Guide. The model OCe10102 doesn’t support by ESXi 6.0.
If you run the following command you will still be able to see the adapters in PCI list on ESXi.
esxcli hardware pci list
So it indicates the adapters are not visible in ESXi since the newer Emulex driver doesn’t contain the model of the adapter in ESXi 6.0 native driver.
Then I uninstalled the native Emulex driver for ESXi 6.0 by the following command and rebooted the ESXi host.
esxcli software vib remove -n elxnet
The adapters still not visible after rebooting since no any drivers for Emulex adapters. Then I downloaded the Emulex drivers for ESXi 5.5 on VMware website and uploaded the “offline” package in the zip file to /tmp directory of the host. Then installed the driver by the following command:
esxcli software vib install -d "/tmp/xxxxx.zip"
The adapters appeared after rebooting the host.
There is an issue been identified in VMware Tools 10.3.0 can result in a PSOD or guest network connectivity loss. VMware has released KB57796 for that.
When you upgrade or patch vCenter Server 6.0 for Windows, you may see following symptoms:
“The older version of cis-upgrade-runner cannot be removed. Contact your technical support group.”
Or error code 1063:
“Installation of component VMware CIS upgrade runner failed with error code ‘1063’”
That means the vCenter Server installer cannot find MSI files of existing vCenter Server services. It could be following reasons:
- You delete MSI files in “Temp” folder of the profile you used to install vCenter Server.
- The account you used to login and install vCenter Server was roaming profile. The profile’s “Temp” folder was automatically deleted when you reboot/logoff the server.
vCenter Server 6.0 for Windows is consist of lot of standalone package. The upgrading process usually uninstall old packages, and then install newer packages. So the failure doesn’t impact to database or inventory data. You can re-initiate the upgrading again.
But you cannot manually uninstall old package since upgrading process brings down vCenter services first then uninstall old packages. If you already uninstalled old packages, the upgrading process will be stuck on bring down vCenter Services stage since some processes may already be removed. For example “vmware-python” it maps to “VMware vCenter Configuration Service”. If you manually uninstalled it before launch upgrading. It removes the service. Upgrading is not able to check status of the service.
Easiest way to get ride of this problem is
- Open Registry Editor (regedit) and go to the path: “HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products”
You would see lot of keys are there.
- Search keyword “vmware-“. These keys store package info of vCenter Server.
- Expand one of the keys. Go to “SourceList”.
- The value of “LastUsedSource” is path of MSI file of old vCenter Server installer.
For example my value is “m;1;X:\vcenter-server\packages\”.
- Make sure your server has the path mentioned in previous step (My case it’s X:\vcenter-server\packages\) and old MSI files are available in the path. If it’s a CD-ROM letter, you just need mount old vCenter Server image to the drive.
- Copy new vCenter Server image to a local folder, uncompresse and launch installer locally.
- Now the upgrading process can read original packages on the mentioned path in step 4. It will automatically remove old packages by the old MSI files.
There are two other workarounds. One is modify the value of “LastUsedSource” to reflect a new location of packages. But you still need the old MSI files be there. Another way is delete the key after you find it in step 2. (I never tested this way but it should work as it let vCenter Server installer thinks the server is brand new so installer can override the existing folders)
I also wrote another article for upgrading error on vCenter Server 5.5 for your reference:
CustomAction VM_InstallJRE returned actual error code 1624
Few days ago, VMware sent an email notification to me that my blog was award to vExpert 2014. I would thanks Sean’s reference and suggestion. I’m very glad to hear that news! It encourage me continue contribute to virtualization community, share my experience with people. Here is the link lists my name and Twitter account. http://blogs.vmware.com/vmtn/2014/10/vexpert-2014-q3-announcement.html.
First, I would like to recommend DELL M4800 for small home lab, I spent lot of time to looking for a solution for my lab, I need some hardware low noise, low weight, and it is better portable. I checked out HP mini server, Apple MAC mini, Mac book pro…etc. They are nice products to show best design of IT industry, but no one perfect. Finally I choose DELL M4800. The reason is RAM can be upgraded to 32GB. 3 SSD hard disks is supported, you can install one native SSD, one in CD-ROM slot, another msata SSD in WAP slot. SSD disk is must have for IT LAB, it can provide you more than 10K IOPS without significant performance degrade.
Okay, back to topic…if you want to testing Windows Server 2012 R2 Hyper-V on lab, you probably prefer install it on a VM of VMware Workstation. You have to follow up proper steps to make sure the Hyper-V functionally.
After you create Hyper-V VM:
- Keep VM power off status.
- Go to Settings of VM.
- Highlight Processors.
- Select Virtualize Intel VT-x/EPT or AMD-V/RVI option.
- Go to Options tab.
- Highlight General.
- Select Microsoft Windows.
- Select Hyper-V on drop-list.
- Power on.