Recently, I have upgraded my homelab – yet again. There will be an oncoming post about the hardware I chose and how it is set up. This time, my lab is mobile. I can take it with me on the road or leave it at home. One of the features that I wanted to be able to capture and utilize
Recently, I had to install ESXi 4.1 on an IBM x3850 X5. Once the install was completed and I started configuring the host, I noticed something odd. I had a new vswitch and a network adapter that was defined as vusb0. WTF? At first, I thought I was imagining things. I opened the network adapters view, and sure enough there
I’ve been in a situation where I’ve installed a new NIC and it renumbered the vmnics within an ESX host. The reason this became an issue was that the Service Console vmnic was one of the vmnics that was affected. Thus I lost my access to the ESX host. Thankfully, I could just drive over to the Datacenter and fix
Sometimes a Virtual Machine can’t be stopped via the VIClient. The job just hangs. There are a number of options to stop your Virtual Machine from within the Service Console. Keep in mind that these are last resort options! Stopping the virtual machine by issuing the command: vmware-cmd /vmfs/volumes/datastorename/vmname/vmname.vmx stop This must be done on the ESX host where the