Aaron,
Thanks for the information. I upgraded to VMware server 2.0, but have
encountered some other issues. I have restored it to 1.0 now.
Yes, I am using VCL 2.2.1. I changed the provision module to 'VMware' and see
more progress for the capturing base image. However, it still failed at the
end. Can you please see what the problem is this time?
Thanks again,
Lei
=================
2011-10-07 15:02:06|624|607:607|image|Module.pm:code_loop_timeout(742)|waiting
for vmguest-3 to power off, maximum of 600 seconds
2011-10-07 15:02:06|624|607:607|image|Module.pm:code_loop_timeout(759)|attempt
1: waiting for vmguest-3 to power off
2011-10-07
15:02:06|624|607:607|image|vmware_cmd.pm:get_vm_power_state(242)|power state of
VM 'CentOS5_5-base10-v0.vmx': off
2011-10-07 15:02:06|624|607:607|image|Module.pm:code_loop_timeout(762)|waiting
for vmguest-3 to power off, code returned true
2011-10-07
15:02:07|624|607:607|image|Linux.pm:file_exists(1404)|'/install/vmware_files/CentOS5_5-base10-v0/CentOS5_5-base10-v0.vmdk'
exists on CSB303, files: 1, directories: 0, links: 0
2011-10-07 15:02:07|624|607:607|image|Linux.pm:file_exists(1390)|file or
directory does not exist on CSB303:
'/install/vmware_files/vmwarelinux-MyCentOS357-v0/vmwarelinux-MyCentOS357-v0.vmdk'
2011-10-07 15:02:07|624|607:607|image|VMware.pm:rename_vmdk(5026)|attempting to
rename vmdk:
'/install/vmware_files/CentOS5_5-base10-v0/CentOS5_5-base10-v0.vmdk' -->
'/install/vmware_files/vmwarelinux-MyCentOS357-v0/vmwarelinux-MyCentOS357-v0.vmdk'
2011-10-07 15:02:07|624|607:607|image|Linux.pm:create_directory(1520)|directory
created on CSB303: '/install/vmware_files/vmwarelinux-MyCentOS357-v0'
2011-10-07
15:02:07|624|607:607|image|VMware.pm:rename_vmdk(5049)|'move_virtual_disk'
subroutine has not been implemented by the API:
VCL::Module::Provisioning::VMware::vmware_cmd
2011-10-07 15:02:07|624|607:607|image|VMware.pm:rename_vmdk(5056)|attempting to
rename vmdk file using vmware-vdiskmanager:
/install/vmware_files/CentOS5_5-base10-v0/CentOS5_5-base10-v0.vmdk -->
/install/vmware_files/vmwarelinux-MyCentOS357-v0/vmwarelinux-MyCentOS357-v0.vmdk
2011-10-07 15:02:07|624|607:607|image|VMware.pm:rename_vmdk(5063)|renamed vmdk
file by executing 'vmware-vdiskmanager' command on VM host:
|624|607:607|image| command: vmware-vdiskmanager -n
"/install/vmware_files/CentOS5_5-base10-v0/CentOS5_5-base10-v0.vmdk"
"/install/vmware_files/vmwarelinux-MyCentOS357-v0/vmwarelinux-MyCentOS357-v0.vmdk"
|624|607:607|image| output: Using log file /tmp/vmware-root/vdiskmanager.log
|624|607:607|image| Renaming completed successfully.
2011-10-07
15:02:07|624|607:607|image|Linux.pm:file_exists(1404)|'/install/vmware_files'
exists on CSB303, files: 0, directories: 1, links: 0
2011-10-07
15:02:07|624|607:607|image|VMware.pm:is_repository_mounted_on_vmhost(5485)|image
repository is mounted on VM host CSB303: /install/vmware_files
2011-10-07 15:02:07|624|607:607|image|VMware.pm:capture(596)|vmdk will be
copied directly from VM host CSB303 to the image repository in the 2gbsparse
disk format
2011-10-07
15:02:08|624|607:607|image|VMware.pm:get_vmhost_product_name(5405)|VMware
product being used on VM host CSB303: 'VMware Server 1.0.10 build-203137'
2011-10-07
15:02:08|624|607:607|image|Linux.pm:file_exists(1404)|'/install/vmware_files/vmwarelinux-MyCentOS357-v0/vmwarelinux-MyCentOS357-v0.vmdk'
exists on CSB303, files: 1, directories: 0, links: 0
2011-10-07
15:02:08|624|607:607|image|Linux.pm:file_exists(1404)|'/install/vmware_files/vmwarelinux-MyCentOS357-v0/vmwarelinux-MyCentOS357-v0.vmdk'
exists on CSB303, files: 1, directories: 0, links: 0
|624|607:607|image| ---- WARNING ----
|624|607:607|image| 2011-10-07
15:02:08|624|607:607|image|VMware.pm:copy_vmdk(4781)|destination vmdk file path
already exists on VM host CSB303:
/install/vmware_files/vmwarelinux-MyCentOS357-v0/vmwarelinux-MyCentOS357-v0.vmdk
|624|607:607|image| ( 0) VMware.pm, copy_vmdk (line: 4781)
|624|607:607|image| (-1) VMware.pm, capture (line: 600)
|624|607:607|image| (-2) image.pm, process (line: 162)
|624|607:607|image| (-3) vcld, make_new_child (line: 568)
|624|607:607|image| (-4) vcld, main (line: 346)
|624|607:607|image| ---- WARNING ----
|624|607:607|image| 2011-10-07
15:02:08|624|607:607|image|VMware.pm:capture(604)|failed to copy the vmdk files
after the VM was powered off:
'/install/vmware_files/vmwarelinux-MyCentOS357-v0/vmwarelinux-MyCentOS357-v0.vmdk'
-->
'/install/vmware_files/vmwarelinux-MyCentOS357-v0/vmwarelinux-MyCentOS357-v0.vmdk'
|624|607:607|image| ( 0) VMware.pm, capture (line: 604)
|624|607:607|image| (-1) image.pm, process (line: 162)
|624|607:607|image| (-2) vcld, make_new_child (line: 568)
|624|607:607|image| (-3) vcld, main (line: 346)
2011-10-07
15:02:08|624|607:607|image|Linux.pm:file_exists(1404)|'/install/vmware_files/vmwarelinux-MyCentOS357-v0/vmwarelinux-MyCentOS357-v0.vmdk'
exists on CSB303, files: 1, directories: 0, links: 0
2011-10-07 15:02:09|624|607:607|image|Linux.pm:file_exists(1390)|file or
directory does not exist on CSB303:
'/install/vmware_files/CentOS5_5-base10-v0/CentOS5_5-base10-v0.vmdk'
2011-10-07 15:02:09|624|607:607|image|VMware.pm:rename_vmdk(5026)|attempting to
rename vmdk:
'/install/vmware_files/vmwarelinux-MyCentOS357-v0/vmwarelinux-MyCentOS357-v0.vmdk'
--> '/install/vmware_files/CentOS5_5-base10-v0/CentOS5_5-base10-v0.vmdk'
2011-10-07 15:02:09|624|607:607|image|Linux.pm:create_directory(1524)|directory
already exists on CSB303: '/install/vmware_files/CentOS5_5-base10-v0'
2011-10-07
15:02:09|624|607:607|image|VMware.pm:rename_vmdk(5049)|'move_virtual_disk'
subroutine has not been implemented by the API:
VCL::Module::Provisioning::VMware::vmware_cmd
2011-10-07 15:02:09|624|607:607|image|VMware.pm:rename_vmdk(5056)|attempting to
rename vmdk file using vmware-vdiskmanager:
/install/vmware_files/vmwarelinux-MyCentOS357-v0/vmwarelinux-MyCentOS357-v0.vmdk
--> /install/vmware_files/CentOS5_5-base10-v0/CentOS5_5-base10-v0.vmdk
2011-10-07 15:02:09|624|607:607|image|VMware.pm:rename_vmdk(5063)|renamed vmdk
file by executing 'vmware-vdiskmanager' command on VM host:
|624|607:607|image| command: vmware-vdiskmanager -n
"/install/vmware_files/vmwarelinux-MyCentOS357-v0/vmwarelinux-MyCentOS357-v0.vmdk"
"/install/vmware_files/CentOS5_5-base10-v0/CentOS5_5-base10-v0.vmdk"
|624|607:607|image| output: Using log file /tmp/vmware-root/vdiskmanager.log
|624|607:607|image| Renaming completed successfully.
2011-10-07 15:02:09|624|607:607|image|VMware.pm:capture(693)|attempting to
delete directory where renamed vmdk resided before reverting the name back to
the original: /install/vmware_files/vmwarelinux-MyCentOS357-v0
|624|607:607|image| command: vmware-vdiskmanager -n
"/install/vmware_files/vmwarelinux-MyCentOS357-v0/vmwarelinux-MyCentOS357-v0.vmdk"
"/install/vmware_files/CentOS5_5-base10-v0/CentOS5_5-base10-v0.vmdk"
|624|607:607|image| output: Using log file /tmp/vmware-root/vdiskmanager.log
|624|607:607|image| Renaming completed successfully.
2011-10-07 15:02:09|624|607:607|image|VMware.pm:capture(693)|attempting to
delete directory where renamed vmdk resided before reverting the name back to
the original: /install/vmware_files/vmwarelinux-MyCentOS357-v0
2011-10-07 15:02:09|624|607:607|image|Linux.pm:delete_file(1459)|deleted
'/install/vmware_files/vmwarelinux-MyCentOS357-v0' on CSB303
2011-10-07 15:02:09|624|607:607|image|Linux.pm:file_exists(1390)|file or
directory does not exist on CSB303:
'/install/vmware_files/vmwarelinux-MyCentOS357-v0'
2011-10-07 15:02:09|624|607:607|image|Linux.pm:delete_file(1473)|confirmed file
does not exist on CSB303: '/install/vmware_files/vmwarelinux-MyCentOS357-v0'
2011-10-07 15:02:09|624|607:607|image|VMware.pm:capture(699)|attempting to
power the VM back on so that it can be captured again
2011-10-07 15:02:10|624|607:607|image|vmware_cmd.pm:vm_power_on(300)|powered on
VM: 'CentOS5_5-base10-v0.vmx'
|624|607:607|image| ---- WARNING ----
|624|607:607|image| 2011-10-07
15:02:10|624|607:607|image|image.pm:process(166)|vmwarelinux-MyCentOS357-v0
image failed to be captured by provisioning module
|624|607:607|image| ( 0) image.pm, process (line: 166)
|624|607:607|image| (-1) vcld, make_new_child (line: 568)
|624|607:607|image| (-2) vcld, main (line: 346)
|624|607:607|image| ---- WARNING ----
|624|607:607|image| 2011-10-07
15:02:10|624|607:607|image|DataStructure.pm:_automethod(812)|corresponding data
has not been initialized for get_management_node_sysadmin_email:
$ENV{management_node_info}{SYSADMIN_EMAIL}
|624|607:607|image| ( 0) DataStructure.pm, _automethod (line: 812)
|624|607:607|image| (-1) Autoload.pm, __ANON__ (line: 80)
|624|607:607|image| (-2) image.pm, reservation_failed (line: 382)
|624|607:607|image| (-3) image.pm, process (line: 167)
|624|607:607|image| (-4) vcld, make_new_child (line: 568)
|624|607:607|image| (-5) vcld, main (line: 346)
2011-10-07
15:02:10|624|607:607|image|DataStructure.pm:get_computer_private_ip_address(1557)|returning
private IP address previously retrieved: 10.10.10.4
2011-10-07 15:02:10|624|607:607|image|utils.pm:is_inblockrequest(6163)|zero
rows were returned from database select
2011-10-07
15:02:10|624|607:607|image|DataStructure.pm:get_image_affiliation_name(2035)|image
owner id: 1
2011-10-07 15:02:10|624|607:607|image|utils.pm:getnewdbh(2709)|database
requested (information_schema) does not match handle stored in $ENV{dbh}
(vcl:localhost)
2011-10-07 15:02:10|624|607:607|image|utils.pm:getnewdbh(2760)|database handle
stored in $ENV{dbh}
2011-10-07
15:02:10|624|607:607|image|DataStructure.pm:retrieve_user_data(1352)|attempting
to retrieve and store data for user: user.id = '1'
2011-10-07 15:02:10|624|607:607|image|utils.pm:getnewdbh(2709)|database
requested (vcl) does not match handle stored in $ENV{dbh}
(information_schema:localhost)
2011-10-07 15:02:10|624|607:607|image|utils.pm:getnewdbh(2760)|database handle
stored in $ENV{dbh}
2011-10-07
15:02:10|624|607:607|image|DataStructure.pm:retrieve_user_data(1415)|data has
been retrieved for user: admin (id: 1)
2011-10-07 15:02:11|624|607:607|image|utils.pm:mail(1268)|SUCCESS -- Sending
mail To: 0, PROBLEM --
607:607|image|image.pm|vmguest-3>CSB303|vmwarelinux-MyCentOS357-v0|admin
|624|607:607|image| ---- CRITICAL ----
|624|607:607|image| 2011-10-07
15:02:10|624|607:607|image|image.pm:reservation_failed(385)|vmwarelinux-MyCentOS357-v0
image creation failed
|624|607:607|image| ( 0) image.pm, reservation_failed (line: 385)
|624|607:607|image| (-1) image.pm, process (line: 167)
|624|607:607|image| (-2) vcld, make_new_child (line: 568)
|624|607:607|image| (-3) vcld, main (line: 346)
2011-10-07 15:02:11|624|607:607|image|utils.pm:mail(1268)|SUCCESS -- Sending
mail To: root@localhost, VCL -- NOTICE DELAY Image Creation MyCentOS3
________________________________________
From: Aaron Peeler [aaron_pee...@ncsu.edu]
Sent: Thursday, October 06, 2011 8:33 AM
To: Huang,Lei
Cc: vcl-user@incubator.apache.org
Subject: Re: questions regarding creating base images
No you don't need to upgrade 2.0. IMO, 2.x is more flakey than 1.x and
will cause you other issues.
If you were to upgrade, I'd recommend to use ESXi.
First, just to make sure, are you using the VCL 2.2.1 release?
If so, you should be able to fix this problem by changing the computer
provisioning module to 'VMware' for each of your vmguest computers.
Aaron
On Wed, Oct 5, 2011 at 4:36 PM, Huang,Lei <lhu...@pvamu.edu> wrote:
> Aaron,
>
> My current setting is using Vmware Server GSX. Do I need to upgrade my
> VM server from 1.0 to 2.0?
>
> Thanks,
> Lei
>
> On 10/5/11 1:33 PM, "Aaron Peeler" <aaron_pee...@ncsu.edu> wrote:
>
>>It looks like your using an older vmware provisioning module called
>>vmware.pm.
>>
>>It should be using the newer one under
>>/../vcl/lib/VCL/Module/Provisioning/VMware/VMware.pm
>>
>>Please check the vm compute nodes in your vcl interface for vmguest-1
>>and vmguest-2.
>>
>>Manage computers -> Select all computers
>>Select Edit Computer Information
>>Make sure Provisioning Engine is selected
>>
>>Hit submit
>>
>>Make sure it says VMware
>>
>>Can you also send the sql output of the below query from your database?
>>This is going to help us make sure the VMware provisioning name listed
>>in the VCL interface is using the correct perl module.
>>
>>On your management node at the mysql command line or via phpmyadmin,
>>run this query on the vcl database.
>>
>>SELECT computer.hostname,provisioning.*,module.perlpackage FROM
>>computer,provisioning, module WHERE computer.hostname like '%vmguest%'
>>AND provisioning.id = computer.provisioningid AND module.id =
>>provisioning.id
>>
>>Thanks,
>>Aaron
>>
>>On Wed, Oct 5, 2011 at 1:54 PM, Huang,Lei <lhu...@pvamu.edu> wrote:
>>> Aaron,
>>> Here is some log information. Please let me know if you need any
>>>more.
>>> Thanks,
>>> Lei
>>> ===============
>>> 2011-10-05
>>> 10:24:38|26273|565:565|image|utils.pm:run_scp_command(5636)|copied file
>>>via
>>> SCP: 'vmguest-1:/etc/init.d/sshd' --> '/tmp/565.ext_sshd'
>>> 2011-10-05
>>>
>>>10:24:38|26273|565:565|image|Linux.pm:generate_ext_sshd_init(2359)|copied
>>> sshd init script from vmguest-1 for local processing
>>> 2011-10-05
>>> 10:24:38|26273|565:565|image|Linux.pm:generate_ext_sshd_init(2369)|read
>>>file
>>> /tmp/565.ext_sshd into array
>>> 2011-10-05
>>> 10:24:38|26273|565:565|image|utils.pm:run_scp_command(5600)|attempting
>>>to
>>> copy file via SCP: '/tmp/565.ext_sshd' -->
>>>'vmguest-1:/etc/init.d/ext_sshd'
>>> 2011-10-05
>>> 10:24:38|26273|565:565|image|utils.pm:run_scp_command(5636)|copied file
>>>via
>>> SCP: '/tmp/565.ext_sshd' --> 'vmguest-1:/etc/init.d/ext_sshd'
>>> 2011-10-05
>>>
>>>10:24:38|26273|565:565|image|Linux.pm:generate_ext_sshd_init(2425)|copied
>>> /tmp/565.ext_sshd to vmguest-1:/etc/init.d/ext_sshd
>>> 2011-10-05
>>> 10:24:38|26273|565:565|image|utils.pm:run_ssh_command(5380)|executing
>>>SSH
>>> command on vmguest-1:
>>> |26273|565:565|image| /usr/bin/ssh -i /etc/vcl/vcl.key -o
>>> StrictHostKeyChecking=no -l root -p 22 -x vmguest-1 'chmod +rx
>>> /etc/init.d/ext_sshd' 2>&1
>>> 2011-10-05
>>>
>>>10:24:38|26273|565:565|image|Linux.pm:generate_ext_sshd_init(2426)|settin
>>>g
>>> vmguest-1:/etc/init.d/ext_sshd executable
>>> 2011-10-05
>>>10:24:38|26273|565:565|image|Linux.pm:pre_capture(179)|shutting
>>> down node for Linux imaging sequence
>>> 2011-10-05
>>> 10:24:38|26273|565:565|image|utils.pm:run_ssh_command(5380)|executing
>>>SSH
>>> command on vmguest-1:
>>> |26273|565:565|image| /usr/bin/ssh -i /etc/vcl/vcl.key -o
>>> StrictHostKeyChecking=no -l root -p 22 -x vmguest-1 '/sbin/shutdown -h
>>>now'
>>> 2>&1
>>> 2011-10-05
>>>
>>>10:24:39|26273|565:565|image|utils.pm:run_ssh_command(5464)|run_ssh_comma
>>>nd
>>> output:
>>> 2011-10-05
>>>10:24:39|26273|565:565|image|utils.pm:run_ssh_command(5478)|SSH
>>> command executed on vmguest-1, returning (0, "")
>>> 2011-10-05
>>> 10:24:39|26273|565:565|image|Module.pm:code_loop_timeout(742)|waiting
>>>for
>>> vmguest-1 to power off, maximum of 120 seconds
>>> 2011-10-05
>>> 10:24:39|26273|565:565|image|Module.pm:code_loop_timeout(759)|attempt 1:
>>> waiting for vmguest-1 to power off
>>> 2011-10-05 10:24:39|26273|565:565|image|vmware.pm:get_vm_paths(2485)|vm
>>> locations:
>>> |26273|565:565|image| vmdk name: vmwarelinux-CentOS55Test46-v0
>>> |26273|565:565|image| vmx path:
>>>
>>>/install/vmware_files/runningvms/vmwarelinux-CentOS55Test46-v0vmguest-1/v
>>>mwarelinux-CentOS55Test46-v0vmguest-1.vmx
>>> |26273|565:565|image| vm directory:
>>>vmwarelinux-CentOS55Test46-v0vmguest-1
>>> |26273|565:565|image| base vm directory: vmwarelinux-CentOS55Test46-v0
>>> 2011-10-05
>>> 10:24:39|26273|565:565|image|vmware.pm:power_status(2407)|attempting to
>>> execute vmware-cmd getstate
>>> 2011-10-05
>>> 10:24:39|26273|565:565|image|utils.pm:run_ssh_command(5380)|executing
>>>SSH
>>> command on CSB302:
>>> |26273|565:565|image| /usr/bin/ssh -i /etc/vcl/vcl.key -o
>>> StrictHostKeyChecking=no -l root -p 22 -x CSB302 'vmware-cmd
>>>
>>>/install/vmware_files/runningvms/vmwarelinux-CentOS55Test46-v0vmguest-1/v
>>>mwarelinux-CentOS55Test46-v0vmguest-1.vmx
>>> getstate' 2>&1
>>> |26273|565:565|image| ---- WARNING ----
>>> |26273|565:565|image| 2011-10-05
>>> 10:24:39|26273|565:565|image|vmware.pm:power_status(2415)|failed to run
>>> vmware-cmd getstate for vmwarelinux-CentOS55Test46-v0vmguest-1 vm, exit
>>> status: 11, output:
>>> |26273|565:565|image| /usr/bin/vmware-cmd: Could not connect to VM
>>>
>>>/install/vmware_files/runningvms/vmwarelinux-CentOS55Test46-v0vmguest-1/v
>>>mwarelinux-CentOS55Test46-v0vmguest-1.vmx
>>> (VMControl error -11: No such virtual machine: The config file
>>>
>>>/install/vmware_files/runningvms/vmwarelinux-CentOS55Test46-v0vmguest-1/v
>>>mwarelinux-CentOS55Test46-v0vmguest-1.vmx
>>> is not registered. Please register the config file on the server. For
>>> example: vmware-cmd -s register
>>>
>>>"/install/vmware_files/runningvms/vmwarelinux-CentOS55Test46-v0vmguest-1/
>>>vmwarelinux-CentOS55Test46-v0vmguest-1.vmx")
>>> |26273|565:565|image| ( 0) vmware.pm, power_status (line: 2415)
>>> |26273|565:565|image| (-1) Provisioning.pm, __ANON__ (line: 324)
>>> |26273|565:565|image| (-2) Module.pm, code_loop_timeout (line: 761)
>>> |26273|565:565|image| (-3) Provisioning.pm, wait_for_power_off (line:
>>>324)
>>> |26273|565:565|image| (-4) Linux.pm, pre_capture (line: 183)
>>> |26273|565:565|image| (-5) vmware.pm, capture (line: 1038)
>>> ================
>>>
>>>
>>> On 10/5/11 12:45 PM, "Aaron Peeler" <aaron_pee...@ncsu.edu> wrote:
>>>
>>> Lei,
>>> Could you provide the vcld.log file? The default location would be
>>> /var/log/vcld.log
>>> Thanks,
>>> Aaron
>>> On Wed, Oct 5, 2011 at 1:41 PM, Huang,Lei <lhu...@pvamu.edu> wrote:
>>>
>>> Aaron,
>>> I changed .vmx file to start it using vmware console. After running
>>>vcld
>>> -setup, it can now log into the VM and change the network settings.
>>>After
>>> it, I see it shuts down the VM and waits for 120 seconds. However, after
>>> it, it cannot bring up the new VM since it is a new image name created.
>>>It
>>> is not registered on my CSB2 vmware yet. I cannot find the new image
>>>files
>>> in my vmware repository and the runningvms directory either. Can you see
>>> what the problem is?
>>> Thanks,
>>> Lei
>>> On 10/5/11 12:04 PM, "Aaron Peeler" <aaron_pee...@ncsu.edu> wrote:
>>>
>>> The easiest way is to use the vmware console.
>>> Log into the vmware host CSB2 and run the command
>>> vmware &
>>> You can either modify the .vmx file or edit the settings via the vmware
>>> console.
>>> Aaron
>>> On Wed, Oct 5, 2011 at 1:01 PM, Huang,Lei <lhu...@pvamu.edu> wrote:
>>>
>>> Aaron,
>>> Thanks for your answer. How can I load my VM using vmguest-1? What
>>> command should I use? Do I need to modify the .vmx file to add the
>>> static
>>> IP address for my new VM?
>>> Thanks,
>>> Lei
>>> On 10/5/11 11:54 AM, "Aaron Peeler" <fapee...@ncsu.edu> wrote:
>>>
>>> Hello Lei,
>>> When prompted for the computer name/IP, you will want to enter
>>> vmguest-1. The vm needs to be running and you need to be able to login
>>> via ssh identity keys from your management node.
>>> Aaron
>>>
>>> On Tue, Oct 4, 2011 at 11:26 PM, Huang,Lei <lhu...@pvamu.edu> wrote:
>>>
>>> Hi everyone,
>>> I am following the instruction of creating a base linux image
>>> (https://cwiki.apache.org/VCL/create-a-linux-base-image.html) , but I
>>> am
>>> very confused about the document, and would appreciate any help. I
>>> have
>>> the
>>> following settings:
>>> 1. Blade #1: management code
>>> 2. Blade #2: a compute node (name: CSB2, VM host computer running
>>> CentOS
>>> 5.5 and VMware server 1.x. It has been added into the VCL database)
>>> 3. Two guest VMs (vmguest-1, vmguest-2) assigned to the VM host
>>> (CSB2)
>>> using the vcl website.
>>> I have created a new virtual machine using VMware console in CSB2.
>>> Now I
>>> would like to capture it. After setting up the network of the VM, I
>>> run
>>> vcld -setup on the management node. When it asks for the computer
>>> name/IP,
>>> and here is my confusion. If I enter CSB2, then it changes the network
>>> configuration of CSB2 and then shut down the node, which made the
>>> entire
>>> process failed. If I enter vmguest-1, it couldn't finish the capture
>>> either
>>> since vmguest-1 is not running. What's wrong in my process? I have
>>> read
>>> the
>>> document several times, but cannot figure it out. Can anyone please
>>> help?
>>> Thanks,
>>> Lei Huang
>>>
>>>
>>> --
>>> Aaron Peeler
>>> Program Manager
>>> Virtual Computing Lab
>>> NC State University
>>> All electronic mail messages in connection with State business which
>>> are sent to or received by this account are subject to the NC Public
>>> Records Law and may be disclosed to third parties.
>>>
>>>
>>>
>>>
>>> --
>>> Aaron Peeler
>>> Program Manager
>>> Virtual Computing Lab
>>> NC State University
>>> All electronic mail messages in connection with State business which
>>> are sent to or received by this account are subject to the NC Public
>>> Records Law and may be disclosed to third parties.
>>>
>>>
>>>
>>>
>>> --
>>> Aaron Peeler
>>> Program Manager
>>> Virtual Computing Lab
>>> NC State University
>>> All electronic mail messages in connection with State business which
>>> are sent to or received by this account are subject to the NC Public
>>> Records Law and may be disclosed to third parties.
>>>
>>
>>
>>
>>--
>>Aaron Peeler
>>Program Manager
>>Virtual Computing Lab
>>NC State University
>>
>>All electronic mail messages in connection with State business which
>>are sent to or received by this account are subject to the NC Public
>>Records Law and may be disclosed to third parties.
>
>
--
Aaron Peeler
Program Manager
Virtual Computing Lab
NC State University
All electronic mail messages in connection with State business which
are sent to or received by this account are subject to the NC Public
Records Law and may be disclosed to third parties.
