VCL creates VMs in either persistent or nonpersistent mode depending on
whether you made an imaging reservation.
If you click on "New Reservation" to create a normal, non-imaging
reservation, the VM gets created in nonpersistent mode. This allows the
large .vmdk files to be shared by multiple VMs to save space. The downside
is that changes to the hard drive are lost if the VM is rebooted. The .vmdk
files reside in a directory named after the image name:
"vmwarewinxp-base7-v1". The .vmx and other files specific to the VM reside
in a directory named after the image name, with the VM computer name
If you click on "Manage Images", the VM gets created in persistent mode.
The VM has sole possession of the .vmdk files, changes are written to the
.vmdk files directly, and changes persist if the VM is rebooted. The .vmdk
and .vmx files reside in a directory named after the request ID and VM
comptuer name (I think): "1234vmguest-1".
You'll have to view the vcld.log file to figure out what's going wrong with
normal reservations. Run 'vmware-cmd -l' on the VM host after the normal
reservation is loaded to list the registered VMs. Do you see one pointing
to the .vmx file in the vmwarewinxp-base7-v1vmguest-1 directory? This list
should coincide with the VMs you see on the GUI VMware console.
If you don't see the VM registered, find the section in vcld.log where it
registers the VM. There should be a command like 'vmware-cmd -s register
Hope this helps,
- Показване на цитирания текст -
Kalina Spasova wrote:
> Your help is more than appreciated and I will resend everything just now.
> Currently, I have managed to set it up correctly and even to connect to a
> virtual machine via RDP thanks to you :D. However, there is another doubt
> raising. Every time I try to create reservation through New Reservation ->
> Now VCL creates a new virtual machine with a name like the following:
> vmwarewinxp-base7-v1vmguest-1, but it doesn't acknowledge it through the
> web interface even if it adds it to the database's tables 'request' and
> 'reservation", so that I can click the Connect button. On the other hand,
> when I go to Manage Images->Create/Update it works just fine. I thought
> about that but couldn't think of a proper solution.
> Thanks a lot about your response and help!
> 2010/3/22 Andy Kurth <andy_ku...@ncsu.edu>
>> Sorry for the delay. I have been trying to keep up with the questions on
>> the vcl-dev list but this one was sent directly to me and got filtered
>> another folder so I missed it. Please send all messages to the list so
>> the info can be shared by others encountering the same problems.
>> Kalina Spasova wrote:
>> I am sorry but I have some questions that have risen from using the
>>> Standalone Vmware installation.
>>> Now every time I try to make an reservation the vcld daemon gets stuck
>>> a loop like the following.
>>> 2010-03-15 19:53:15|4455|31:31|new|vmware.pm:load(868)|sshd is NOT
>>> I know that the problem is in the Cygwin but the thing is that in order
>>> make Cygwin to work I have added the currently assigned IP address into
>>> host table. Probably this is not the proper way to do it. and maybe this
>>> causing the mistake and then I've configured the ethernet adaptor to get
>>> IP via DHCP. Which brings me to my next question.
>>> Yes, this loop where it's getting stuck is happening because the Cygwin
>> SSHD service never responds on the VM.
>> In the Standalone instructions the DHCP is configured to serve only
>>> so I decided to assign static IP addresses to the computer in order to
>>> access to the internet, however, when I managed to capture an image from
>>> Manage imaged -> Create/Update images the newly created vm'root password
>>> not the one given by the RPD file and I think this is not the image vcl
>>> refering to. It gives me prompt only for the root password.
>>> I'm not exactly sure what you changed between reservation 31 and 32.
>> Reservation 31 never got past the "sshd is NOT active" loop? The
>> reservation 32 output you have included below appears to show everything
>> working correctly.
>> How did you assign static IP addresses? If you manually configured a
>> static IP address in the image before it was captured then it would be
>> erased during image capture. VCL sets both the public and private
>> interfaces to use DHCP before an image is captured.
>> Do you use DHCP on the public network or do you need to assign static
>> addresses? If static, you can configure vcld.conf so that VCL assigns
>> static public IP addresses to the VM when it comes up by setting the
>> following lines:
>> DNSserver=<IP address>
>> GATEWAY=<IP address>
>> VCL will manually assign the value in computer.ipaddress after an image is
>> loaded if you configure vcld.conf this way. If you use DHCP for your
>> addresses, then ipconfiguration should be set to dynamicDHCP.
>> I'm not sure what you mean regarding the passwords and the RDP file.
>> reservation 31 is never completely loaded, you would not have an RDP file
>> for that reservation. Are you referring to the RDP file and password you
>> used when the image was captured? If so, then this will certainly not
>> You can disregard any password given out in the connection info page or
>> file once that previous reservation is done.
>> When an image is captured, VCL sets the password of the root and
>> Administrator accounts in the image to the value configured in the
>> file. After the image comes up and SSHD responds, VCL then assigns a
>> password to theses accounts. You can figure out what this random password
>> is by finding the section where it gets set in the vcld.log file.
>> Since SSHD never responds for reservation 31, the passwords are never
>> randomized and an additional account for the reservation is never added to
>> the machine. The passwords for root and Administrator should be the value
>> set in vcld.conf. If this isn't working, view the vcld.log output when the
>> image was captured. The passwords get set pretty early on. It should show
>> what they were set to.
>> And one last question during the capture the output says that the
>>> reservation remote IP is not defined. where should I define it?
>>> remote IP is not defined
>>> And this goes on and on for a long time
>>> You never have to set this. The remote IP is the IP of the machine you
>> connecting to the VM from. It gets collected when you click on "Connect"
>> from the web page. The output you have included below shows this to be
>> working correctly. The "reservation remote IP is not defined" loop stops
>> when you click Connect. As shown below, it retrieved your IP and then
>>> remote IP for reservation 32: 22.214.171.124
>>> Everything else looks correct, it then proceeds to loop until you
>> via RDP:
>> 2010-03-15 20:08:58|7360|32:32|reserved|reserved.pm:
>>> flag is set to 1 and imageosname is vmwarewinxp, checking for connection
>>> 2010-03-15 20:08:58|7360|32:32|reserved|utils.pm:
>>> for connection by administrator on vmguest-2, attempt 1
>>> 2010-03-15 20:08:58|7360|32:32|reserved|utils.pm:
>>> SSH command on vmguest-2:
>>> |7360|32:32|reserved| /usr/bin/ssh -i /etc/vcl/vcl.key -l root -p 22 -x
>>> vmguest-2 'netstat -an' 2>&1
>>> 2010-03-15 20:09:19|7360|32:32|reserved|utils.pm:
>>> for connection by administrator on vmguest-2, attempt 2
>>> 2010-03-15 20:09:19|7360|3
>>> You should have been able to log on for this reservation using the
>> information presented on the page after you clicked Connect. This wasn't
Virtual Computing Lab
Office of Information Technology
North Carolina State University