I found it. The image data in the database had 0 instead of 512. It seems
like we looked at everything but the most obvious....
Wayne F. Schildhauer
Research Triangle Park, NC
----- Original Message -----
From: "Wayne Schildhauer" <wschi...@linux.vnet.ibm.com>
To: "vcl-dev" <firstname.lastname@example.org>
Sent: Wednesday, 08 April, 2009 18:22
Subject: xp image power on fail
I am sorry for the naive question to come, but we figured out why our
Windows XPs VMs are not powering on. In the deployed vmx file on ESXi,
esx3-windowsxp-v0.vmx, memsize = 0:
config.version = "8"
virtualHW.version = "4"
memsize = "0"
displayName = "windowsxp-bl1"
guestOS = "other"
This causes VMware ESXi to panic the VM with an ASSERT failure.
Our master configuration file shows it being 512 MB (memsize = "512"), and
the slots appear to be configured for 512 MB as well. I suspect that
memsize is not getting initialized, rather than overwritten, but I cannot
trace where the object that is being given to esx.pm is originally
generated. Perhaps in the reservation?