Install of virtual machine on BL20p 'out of memory'

[David Stephens_1]

Scenario:
VMware ESX server v2.1.1 on BL20p blade. Using RDP to install virtual W2K server. The preliminary PXE communications work fine, but when the Windows setup begins, the file-copy phase starts up, then stops with the error "Setup is out of memory and cannot continue." The physical blade has 4GB RAM, I gave the virtual 1.2GB, and there are no other active virtuals on the ESX server. Have followed the 'Best Practices for ESX server on Proliant servers' whitepaper (i.e. mods to unattend.txt and w2k.bat files in RDP.) Is anyone deploying VMs using RDP? Any known gotchas?

[Steven Clementi]

David:

One thing to do is make sure you have the right and most up to date NIC drivers.

Is this the first install your attempting in VMware? or did this problem just crop up?


Steven

[David Stephens_1]

Will verify NIC drivers.
One of my colleagues says he was able to install a VM this way several weeks ago, before we moved our datacenter (with whatever attendent changes in network configuration THAT involved!)...howsomever, no one has been able to get this to work since the move. HP suggested I upgrade RDP from v1.5 to 1.6, which I did to no avail. Deployment to physical blade still works flawlessly. And oh by the way, I misspoke on the configuration of the blade in question - it has 8GB RAM, not 4GB.
Thanks for any insights you can provide.