Hi All,
Looking closely it looks like there is an issue when, the esx.pm picks all the
parameters to initiate a poweroff command on the VMguest using the VMware Perl
toolkit API
Please advise ...if my understanding below is right or wrong?
2010-03-22 16:51:09|15553|2:2|image|esx.pm:capture(64
I believe when you are creating a base image, the vmguest name should be the
same as the name of the image you are creating it should be in a format like
vmwarewinxp-base7-v1. Note that the vm you are imaging should have this
name as well as the vmdk file. Your other problem with the hostname is
Hi Ryan,
Thank you for your quick response. I just realized the part with giving
hostname rather than just the IP for VMhost by looking at the regular
expression parsing for hostname.
I didn't know that we need to have the same name for Vmguest and the base
image. Now that you mentioned it m
On 18 Mar 2010, at 0742h, Andy Kurth wrote:
> Hi Terry,
> Sorry for the delay. This information is helpful. You're right, the root
> cause seems to be that sysprep_cmdlines.cmd isn't running.
>
> I have seen the issue where you can't enter a password before. This only
> seems to happen for
When testing the service I noticed something curious. If I make a
reservation, the vm files are copied and powered on. When I end the
reservation, the copied vm files are destroyed and copied again and the vm
is powered on again - the vm is reloaded. What is strange to me is that
when I create a
