I've updated the VCL-130 JIRA ticket with the following: The solution
to be implemented in the esx.pm module is a check to see if a virtual
machine's RAM = 0. If it is then return a friendly, but critical error
message. This should solve the user confusion problem, and the
provisioning
During our Windows XP windows creation we had no problems configuring cywin
sshd. I was able to ssh back and forth from VCL to the VM.
However, after deployment of the VM, cygwin sshd never starts up. I'm able
to login to the VM and ssh into VCL. However, VCL cannot SSH into the
windows vm and
PS. It seems as though cygwin sshd stops working after sysprep. I tried
ssh'ing a few times after the auto_create_image.vbs scripts (from VCL to the
VM) and it seemed to worked fine. Perhaps sysprep or one of the vcl scripts
that are run after deployment changes something?
On Fri, Apr 10,
