Showing posts with label VMWare. Show all posts
Showing posts with label VMWare. Show all posts

Sunday, December 31, 2017

FreeBSD 11.x Guest Keyboard Stops Working in VMware

If you're firing up a 11.x instance of FreeBSD in VMware, you may find that the keyboard works until you shift focus to a different window. Shifting focus back to the FreeBSD window will not give you keyboard input again.

For me the fix was this:

In the .vmx file (or in the GUI under Edit Settings -> Options -> General, then Configuration Parameters...) add this line:

Let me know if you needed to do something different to make it work.

keyboard.typematicMinDelay = "2000000"

Let me know if you needed to do something different to make it work. 

Wednesday, April 1, 2015

Installing vCenter 6.0.0 gives: Installation of component VCSServiceManager failed with error code '1603'. Check the logs for more details.

I'm rolling out a new vCenter 6.0.0 install from scratch to test our environment on it, and quickly ran into a show stopper:

Installation of component VCSServiceManager failed with error code '1603'. Check the logs for more details.

I was installing on a fresh new Windows 2012R2 server with all the updates, but I hadn't installed the .NET 3.5 feature. 

The release notes from VMware mention this exact error, but in the context of an ipv4 address issue, so that wasn't much help, as all of my ipv4 addressing was correct. 

After a bit of poking around, I noticed that a 1603 error in a MSI is often due to .NET being missing.

After installing .NET 3.5 and updates, the install worked properly.

There is no mention of .NET being required in the Release Notes, the Windows Requirements, etc. 

Hopefully that saves someone a bit of time. :-)

Now let's see what that new Web Client performs like. 

Thursday, April 17, 2014

Alternate Method for Converting VMware vCenter Server from Physical to Virtual (VM)

At some point you are going to figure out that the advantages of having your vCenter Server as a VM outweigh the risks, and you're going to want to convert your existing physical vCenter into a virtual one.

There are a few ways of going about this, including just migrating vCenter to a fresh VM.

However, if you're stuck using only the VMware Converter standalone, you may find it frustratingly hard to make the conversion.

If you throw caution to the wind and just convert the vCenter Server on the fly while it's running (using the sync command to try an clean up after), you may get lucky, but more than likely you will have database corruption and other fun.

If you follow VMware's procedures for converting the machine and shut down all the services, the SQL databases, etc. then the VMware Converter can't connect to your vCenter to add the machine to the cluster.

One way around that would be converting to a seperate ESXi host that isn't in your cluster, and later join the host to the cluster, bringing vCenter with it.

However, that's a bit difficult when you are remote to a network (like I was) so there is no oppourtunity to provision physical hardware.

The answer? Double-Conversion.

Shut down all of the necessary services on your vCenter server, and run the Standalone VMware Converter.

Once there, simply convert your vCenter server to a VMware Workstation/Fusion .vmdk image.

Once that is complete, reboot vCenter so all the services are functional again, and convert that .vmdk into a VM on your cluster with the Standalone VMware Converter. vCenter treats this like any other vanilla VM, nothing special is needed.

Yes, you have a period of time where the old vCenter is running and controlling the network, and you're going to be 'going back in time' so to speak to the time of the conversion, but it's no worse than restoring vCenter from a backup.

I connected my new vCenter VM to a dummy network, and did all the final cleanup on it (installing vmxnet3, pvscsi, etc).

Make sure vCenter is running. If you have 5.1 with the Single Sign On (SSO) service, it will probably keep you from running vCenter.

It's not an error in the conversion process. When enough hardware changes, it breaks the SSO service, which still starts normally. However, vCenter won't start. The full article from VMware about this condition is here:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2036170

The set of commands I had to use was:

set JAVA_HOME=C:\Program Files\VMware\Infrastructure\jre
cd C:\Program Files\VMware\Infrastructure\SSOServer\Utils
rsautil manage-secrets -a recover -m MASTER_PASSWORD


(Where MASTER_PASSWORD is your master password when you installed vCenter/SSO)


When you have everything on your vCenter VM running smoothly, shut down your physical vCenter server, and connect your vSphere Client to the raw ESXi host holding your vCenter VM. Once you start it, you'll be able to connect to vCenter as per normal.

Make sure you've read the various forums on how to protect yourself from a bad situation with a virtual vCenter server.

Oh, and if you can keep the old physical server around for a bit, you have a quick emergency backup in case you run into a problem cold-starting your datacenter. 


Wednesday, December 12, 2012

VMWare Enhanced vMotion Compatibility (EVC) Not Needed between AMD Bulldozer 6234 and AMD Piledriver 6348 on VMware ESXi 5.1

I recently upgraded one of our datacenter servers from an AMD Bulldozer 6234 to a AMD Piledriver 6348.

I did find the new chip was faster for memory/CPU operations in our VM's, but I'll post about that in a different article.

What surprised me was that I didn't need to turn on EVC to allow VM's to migrate between hosts running the different CPU's.

Either VMware 5.1 doesn't recognize the new instruction set, or they don't matter in terms of migration.

Either way, I can migrate to the newer chips without worry, and since the 63xx are socket compatible with the 62xx and 61xx series, I have a fairly easy upgrade path for our servers if I wish.

Thursday, November 22, 2012

ESXi 5.1 running FreeBSD 9.0 / 9.1 and VMware Tools

Note - I have another article for ESXi 5.0. These instructions won't work for a 5.0 box.

ESXi 5.1 includes support for the official VMware Tools on FreeBSD 9.0 (yay!).

I'm somewhere between 9.0 and 9.1 RC3, but I feel these instructions will work for either. 

I'll be testing the throughput of the vmxnet3 driver under FreeBSD shorty. For now, I can just confirm that bothe vmxnet2 and vmxnet3 drivers show in FreeBSD, and can ping.

Here's a quick script to install it for you.

You will need to start a VMware Tools install from the guest before running this.


echo "Make sure you have started the vmware tools install"
mount -t cd9660 /dev/cd0 /media
cp /media/vmware-freebsd-tools.tar.gz ~
cd ~
tar xvf vmware-freebsd-tools.tar.gz
cd vmware-tools-distrib
./vmware-install.pl
echo # DONE. Remember that the vmxnet3 driver is called vmxnet3f0


ESXi 5.0 running FreeBSD 9.0 / 9.1 and VMware Tools

Note - I have another article for ESXi 5.1. If you are running 5.1, these instructions won't work for you.

Installing the proper VMware Tools for FreeBSD 9.0 / 9.1 can be a pain.

The hard work to figure this out has already been done by others (http://ogris.de/vmware/), so here is a quick script that will install the official VMware Tools using Dru's patch.

Make sure to start a vmtools install from your vsphere console so ESXi will make the CD available to you.

If you run into problems with a missing library when you try and execute /usr/local/bin/vmare-toolbox-cmd, try looking here (http://lists.freebsd.org/pipermail/freebsd-questions/2010-June/217718.html) it solved the problem for me. 

(Cut-n-Paste into a terminal window with root access)

echo "Make sure you have started the vmware tools install"
mount -t cd9660 /dev/cd0 /media
cp /media/vmware-freebsd-tools.tar.gz ~
cd ~
tar xvf vmware-freebsd-tools.tar.gz
cd vmware-tools-distrib
cd lib/modules/source
tar xvf vmblock.tar
tar xvf vmmemctl.tar
tar xvf vmxnet.tar
tar xvf vmxnet3.tar

fetch http://ogris.de/vmware/vmxnet.diff
fetch http://ogris.de/vmware/vmxnet3.diff

echo #
echo # If it's thinking you have a previously applied patch (-R) say yes.
echo #

patch -p1 < vmxnet.diff
patch -p0 < vmxnet3.diff


cd vmblock-only
make && make install
cd ..

cd vmmemctl-only
make && make install
cd ..

cd vmxnet-only
make && make install
cd ..

cd vmxnet3-only
make && make install
cd ..

cd ~/vmware-tools-distrib


./vmware-install.pl

echo # DONE. Remember that the vmxnet3 driver is called vmxnet3f0

Saturday, September 27, 2008

Speed Increase - ESXi Update2

Has anyone else noticed a speed increase since updating to ESXi Update 2?

I have.

I also notice a further speed increase with the 1006 version of BIOS for the ASUS DSEB board I use.

I did make some speed tests to show the increase, but I'm too lazy to post this morning - Just throwing this out there to see if anyone else has noticed it.

Thursday, July 17, 2008

RAID Alignment and VMware ESX 3i 3.5

Make sure to create your datastores from within the Virtual Infrastructure Client GUI, don't take what the ESX install CD creates (this means deleting any data stores created by the install CD).

It's because the Install CD creates the partitions on the standard Sector 63 starting position (31.5k into the drive. This isn't a proper multiple of any common RAID stripe size (2k, 4k, 8k, 16k, 32k, 64k, etc) so the partition ends up being out of alignment with the RAID stripe elements, and READ/WRITE performance will suffer.

This is all documented in a number of VMware documents.

Creating the partitions in VCI makes them start on sector 128 (64k into the drive), which lines up properly.

Questions on what RAID stripe size and what Windows Allocation Unit size to use will be in another post.

Sunday, February 24, 2008

VMWare ESX 3i 3.5 Speed vs Physical

(Note - Red is Physical Machine with 8 CPUs, Blue is ESX 3i 3.5 with 4 CPUs)


If you're serious about moving to Virtual Servers, you're going to want to know what type of performance hit you're taking for using this technology.

My rough, fairly unscientific results show that using ESX 3i 3.5;

CPU - About 5-10% less than physical

Memory - Nearly physical speed

Disk - Between 50%-75% of physical speed.


Disk takes the largest hit, so you best make sure to follow all the standard ESX "best practices" - Use SAS drives, put Swap on a seperate controller, etc, etc.

Details follow:

I have a new ASUS DSEB-D16/SAS motherboard that I have been running some tests on. So far the speed has ben quite good for ESX 3i 3.5.



My test platform:

- ASUS DSEB-D16/SAS Motherboard

- Two Xeon 2.0 GHz Quad Cores, 45nm

- 8 Gigs ECC Kingston Ram, 667Mhz

- 2 Segate 250 SATAII Drives, set up as Stripe





I've made some tests with Windows 2008 RC1 in both 64 and 32 bit modes, and with Windows 2003 64 bit mode.



I've always used the latest Window drivers for the board and controller.



I used PassMark 6.1 for my testing - It's not overly in depth, but it gives a good overview for what I'm wanting to do.


There is one major messup that I didn't expect - I can only run 4 virtual CPU's in 3i, not the 8 that I have. The first test was with 8 CPUs, and thusly the CPU speed is roughly 50% less in my 3i run. Passmark does make use of every CPU for the CPU portion of the tests (and it runs single CPU for the Memory and Disk mark tests), so this will affect the CPU portion of the tests only.

I have run the test again with only 2 virtual CPUs in 3i, and the results were roughly 50% less than with 4 CPUs. It stands to reason that wil a full 8 CPUs in 3i we'd be very close to the speed of the physical machine.

All my 3i settings are pretty default. I'm going to switch to SAS drives shortly, but I wanted to see the disk test speeds with the existing SATA 250s I used for Windows 2008.

So far, so good. I'm happy with the 3i speed. I can use 32 meg of RAM with my current setup, and it's less than $100 for a 2 Gig stick of ECC 667. I'll keep the RAM high so it's not swapping to disk, and minimize my performance hit on the drives with beefy SAS drives.

ASUS DSEB LSI 1068 MegaRaid Speed vs Intel Matrix

Okay, spent a few hours making some speed tests between the two built in controllers.

I have stats to back up my words, but I don't feel like dragging out all the tests I did and splicing up the graphics/results. I may get to it later.

In a nutshell, with Windows 2008 RC1 64 Bit on a ASUS DSEB-15/SAS Board with 2 Xeon Quads;

- Intel Matrix controller is ever-so-slightly faster for SATA drives than the LSI Megaraid, but not enough to really worry about.
- ESX 3i 3.5 does see the Intel matrix controller, but doesn't see the RAID sets created on it - Just the individual drives.

It looks like you'll still need the SAS option for this board if you want to run RAID of any kind in ESX 3i 3.5

Friday, February 8, 2008

VMWare ESX 3.5 and 3i on ASUS DSEB-D16/SAS Motherboard with SATA drives

Okay, the board arrived yesterday. So far both VMWare's ESX 3.5 and 3.5i are able to boot, install, and stay stable.

I'm not using the LSI SAS controller as of yet - Just the Intel Matrix controller, with a plain old SATA drive. I haven't created any RAID, so both versions of 3.5 are able to spot the Intel controller and work just fine.

This means that people wanting to save a few bucks could use the Intel 6321 controller only board (no SAS).

Watch out - Make sure you use SATA ports 1-4. Ports 5 and 6 are not spotted by the install scripts.