Video Card Hardware - vSphere 4

The boss is out this week and I got all of my work done for the day so I thought I would throw up another post that I have been working on. Blogging, and most anything else, is more difficult with a newborn in your life but I wouldn't have it any other way.

I was recently messing with vSphere in my lab environment and tweaking hardware information to determine what was new with vSphere and hardware version 7. One thing that appears to be added is the ability to edit Video Card settings. I began by adjusting the video ram to 32mb and playing with the VM. Imagine my surprise when trying to vMotion the VM and I received the error:

A general system error occurred: Failed to write checkpoint data (offset 33558328, size 16384): Limit exceeded KB 1011971

This is apparently a result of the vRAM assigned is greater than 30MB. This can be reduced in vSphere by:

1. Shut down the VM
2. Right click on the VM in the inventory and select Edit Settings
3. Click on Video Card
4. Change value under "Enter total video RAM" to below 30MB or select "Reserve memory for the following selection" radio button.

Given this limitation I wondered what effect that may have if you have specific hardware needs for VDI or desktops in general.

Display Resolutions at 24bit color depth

Resolution	Video Ram (MB) 24bit color	Video Ram (MB) 32bit color	2 Display 24bit color (MB)	2 Display 32bit color (MB)
800x600	1.37	1.83	5.49	7.32
1024x768	2.25	3	9	12
1280x1024	3.75	5	15	20
1600x1200	5.49	7.32	21.97	29.3
1152x864	2.85	3.8	11.39	15.19
1280x800	2.93	3.91	11.72	15.63
1440x900	3.71	4.94	14.83	19.77
1680x1050	5.05	6.73	20.18	26.91
1920x1200	6.59	8.79	26.37	35.16

Fortunately the only scenario listed here that exceeds 30MB is when running 1920x1200 on two monitors. There are more configurations available but I thought this would be high on practical limit. I sincerely doubt there will be too many people screaming for dual monitors at this resolution.

On the other side of the coin, attempting to run 16bit on lower resolutions yields the error that "The video memory is limited between 1.17 MB and 128 MB. Select different number for the monitors, screen resolution, or color depth."

Running multiple Displays requires that the Virtual Machine Version be at version 7. You can do this by Right Clicking on the guest VM and selecting "Upgrade Virtual Hardware" You will receive the following warning. Keep in mind that ESX 3.5 does not support version 7 so make the upgrade wisely.

Running multiple displays can also force you to consume more video memory causing you to exceed the 30MB limit for vMotion.

I recently posed the question to a VMware sales engineer about what effect this might have on hosts when utilizing virtual desktops and needing that additional video memory resources. He assured me that he does not know of anyone reaching a level of contention but it is something they will be investigating further. I'm open to any additional information that someone may have on the subject.

vSphere - OVF URL Issue (Am I Just Demanding?)

OK, so I haven't posted in a while and I apologize. I'll catch you up by saying that in June 2009 I took a contract position as a VMware Engineer over at CARQUEST Technology and it has been enjoyable thus far. That being said I'm hoping to get a few more posts over the coming weeks on vSphere and other technologies I am working with, such as the IBM XIV storage system.

Earlier today I logged into my vCenter 4 server to import the vSphere Management Assistant (vMA). I typed the web address... "www.vmware.com/go/importvma/vma4.ovf" and received the following error:
"An error occurred while reading the URL: Invalid URI: the format of the URI could not be determined."

To be fair I did not type in http:// as listed on the vMA site but it was disappointing to me that with all the investment that they put into making vSphere fantastic they failed to inlude a simple "IF" statement to check what the inputted string started with and add an HTTP:// if needed.

I then corrected my "error" and included the http:// and received yet another error:
"An error occurred while reading the URL: The remote server returned an error: (407) Proxy Authentication Required."

I am now 0-2 on trying to quickly add an appliance. A quick Google and VMware community search led to only one way to work around this by running the ovftool in the command line

ovftool --proxy=user:pass@proxy.example.com http://external-site.com/ovf/package.ovf

--P.22 of http://www.vmware.com/support/developer/ovf/ovf10/ovftool_10_userguide.pdf--

It seems to me that there should be some way to input the proxy settings either from the environment or through vCenter Server. I can see where there may be some disconnect since the ovftool is separate but this really makes it difficult for me to download appliances as easily as I should in order to best take advantage of OVF based appliances and the VMware Marketplace.

Browsing through the file system led me to a module.properties file under directory "C:\Program Files (x86)\VMware\Infrastructure\tomcat\webapps\ui\jslib-1.0.160852\modules\com.vmware.webaccess.ovf_1.0.0" in 64bit Server 2008 that contained tons of information but no presence of the word "proxy". Perhaps there is a line that can be injected on this or another settings file to eliminate the need to use command line ovftool in order to authenticate against our proxy server. I'll keep digging and update this post if I find another means to access appliances through our Proxy.


One last quick disappointing note: If you bookmark the vMA page you'll notice that the header has Assistant spelled incorrectly with an 'e' instead of the appropriate 'a'. I think in the end I'm disappointed that this appliance and mechanism for deployment isn't more polished like so many other VMware released items. In the end I've had to download the .zip to import the appliance. Not as slick and easy as it was intended to be.