Hi Alex,
Sorry - I'm unclear on this. What do you mean by vmware guest accounts?
Are these vcl account or some other accounts that exist on the vmware
host server?
Could you attach the log file that shows where it fails?
Aaron
On 4/2/10 5:26 PM, Alexander Patterson wrote:
Hello,
We have
Just making sure. Is this the vmx file that was created by vcld?
The displayName doesn't match what vmware.pm would create. displayName
is generally set to the internal imagename + the computername. Something
like esx3-win2003-v0vcl01
Aaron
On 4/6/10 3:41 PM, Kiran N wrote:
Thanks Aaron!
Pl
Sorry Aaron.. That was not the correct file created by vcld.
The correct file is pasted below:
#!/usr/bin/vmware
config.version = "8"
virtualHW.version = "4"
memsize = "512"
displayName = "esx3-win2003-v0vcl01"
guestOS = "winnetenterprise"
uuid.location = "56 4d 48 99 10 26 eb 65-63 28 84 a3 8a b1
No problem, thanks.
Unfortunately I'm not seeing any obvious problems with the vmx file.
Is there any information in the vmware log files? They should be in
/var/log/vmware/ on the esx host.
-A
On 4/7/10 10:02 AM, Kiran N wrote:
Sorry Aaron.. That was not the correct file created by vcld.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've been getting some work done on the frontend issues for the 2.2 release
the last few days. I just remembered that we're supposed to be emailing this
list before we start work on any issues stating which ones and some comments
on how to resolve
Hello,
The .vmx file is dynamically generated when a reservation is made. Your
original .vmx file created when you made the base image isn't used. The VCL
VMware code does not currently support 64-bit images and sets guestOS=winxppro
in the .vmx file for all XP images regardless of the archit
Aaron,
On seeing the log file, I see that it shows .vmdk file not found error. But
the file is actually present in that path. So, is it possible that the file
got locked by any other instance. If so, how do we check that.Or is there
any other possibility..
Please help!
I have pasted a part of the
No, you're not missing a step but this is odd. The key should be there. I
would try to manually create the key and try to capture the image again. The
key can be a string with an empty value.
-Andy
Vinay Venkatesh wrote:
Hi,
While trying to capture a base windows image, I am getting the f
Is SSH working and is everything being processed by vcld to the point where you
see the Connect button on the web page? If you are just manually running the
scripts then RDP won't be available because the firewall port isn't open. vcld
opens it later on in the process.
I have not seen the er
