creating a base image
hi all, i'm having a problem creating a base windows 7 image and i'm wondering if it is because i'm using vcl 2.2.1 and esxi 5. the lines i think are relevant are below. any pointers would be appreciated. thanks. 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:get_vmhost_product_name(5405)|VMware product being used on VM host vclnode01: 'VMware ESXi 5.0.0 build-623860' 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:initialize(307)|product: VMware ESXi 5.0.0 build-623860, OS object: VCL::Module::OS::Linux::UnixLab 2012-06-29 12:08:30|11089|10:10|image|VIM_SSH.pm:_run_vim_cmd(193)|vim-cmd call count: 1 (hostsvc/datastore/listsummary) 2012-06-29 12:08:30|11089|10:10|image|VIM_SSH.pm:_run_vim_cmd(208)|executed command on VM host vclnode01: vim-cmd hostsvc/datastore/listsummary 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:get_datastore_info(5531)|retrieved datastore info from VM host: |11089|10:10|image| datastore1 |11089|10:10|image| datastore2 |11089|10:10|image| WARNING |11089|10:10|image| 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:_get_datastore_name(5848)|unable to determine datastore name from path: '/vmfs/volumes/local-datastore', path does not begin with any of the datastore paths: |11089|10:10|image| '[datastore2]' |11089|10:10|image| '/vmfs/volumes/datastore2' |11089|10:10|image| '/vmfs/volumes/4fd8b523-f4b9c22c-4f9b-001ec9aa4ba2' |11089|10:10|image| '[datastore1]' |11089|10:10|image| '/vmfs/volumes/datastore1' |11089|10:10|image| '/vmfs/volumes/4fcfadc7-c5fa2f69-3ffc-001ec9aa4ba2' |11089|10:10|image| ( 0) VMware.pm, _get_datastore_name (line: 5848) |11089|10:10|image| (-1) VMware.pm, _get_datastore_root_normal_path (line: 5685) |11089|10:10|image| (-2) VMware.pm, _get_normal_path (line: 5775) |11089|10:10|image| (-3) VMware.pm, get_vmx_base_directory_path (line: 2743) |11089|10:10|image| (-4) VMware.pm, initialize (line: 313) |11089|10:10|image| (-5) Module.pm, new (line: 207) |11089|10:10|image| WARNING |11089|10:10|image| 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:_get_datastore_root_normal_path(5687)|failed to determine datastore root normal path, unable to determine datastore name: /vmfs/volumes/local-datastore |11089|10:10|image| ( 0) VMware.pm, _get_datastore_root_normal_path (line: 5687) |11089|10:10|image| (-1) VMware.pm, _get_normal_path (line: 5775) |11089|10:10|image| (-2) VMware.pm, get_vmx_base_directory_path (line: 2743) |11089|10:10|image| (-3) VMware.pm, initialize (line: 313) |11089|10:10|image| (-4) Module.pm, new (line: 207) |11089|10:10|image| (-5) Module.pm, create_provisioning_object (line: 423) |11089|10:10|image| WARNING |11089|10:10|image| 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:_get_normal_path(5777)|unable to determine normal path, failed to determine datastore root normal path: /vmfs/volumes/local-datastore |11089|10:10|image| ( 0) VMware.pm, _get_normal_path (line: 5777) |11089|10:10|image| (-1) VMware.pm, get_vmx_base_directory_path (line: 2743) |11089|10:10|image| (-2) VMware.pm, initialize (line: 313) |11089|10:10|image| (-3) Module.pm, new (line: 207) |11089|10:10|image| (-4) Module.pm, create_provisioning_object (line: 423) |11089|10:10|image| (-5) State.pm, initialize (line: 117) |11089|10:10|image| WARNING |11089|10:10|image| 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:get_vmx_base_directory_path(2749)|unable to determine the vmx base directory path, failed to convert path configured in the VM profile to a normal path: /vmfs/volumes/local-datastore |11089|10:10|image| ( 0) VMware.pm, get_vmx_base_directory_path (line: 2749) |11089|10:10|image| (-1) VMware.pm, initialize (line: 313) |11089|10:10|image| (-2) Module.pm, new (line: 207) |11089|10:10|image| (-3) Module.pm, create_provisioning_object (line: 423) |11089|10:10|image| (-4) State.pm, initialize (line: 117) |11089|10:10|image| (-5) Module.pm, new (line: 207) |11089|10:10|image| WARNING |11089|10:10|image| 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:initialize(315)|unable to determine vmx base directory path on VM host vclnode01 |11089|10:10|image| ( 0) VMware.pm, initialize (line: 315) |11089|10:10|image| (-1) Module.pm, new (line: 207) |11089|10:10|image| (-2) Module.pm, create_provisioning_object (line: 423) |11089|10:10|image| (-3) State.pm, initialize (line: 117) |11089|10:10|image| (-4) Module.pm, new (line: 207) |11089|10:10|image| (-5) vcld, make_new_child (line: 564) |11089|10:10|image| WARNING |11089|10:10|image| 2012-06-29 12:08:30|11089|10:10|image|Module.pm:create_provisioning_object(431)|provisioning object could not be created, returning 0 |11089|10:10|image| ( 0) Module.pm, create_provisioning_object (line: 431) |11089|10:10|image| (-1) State.pm, initialize (line: 117) |11089|10:10|image| (-2) Module.pm, new (line: 207) |11089|10:10|image| (-3) vcld, make_new_child (line: 564) |11089|10:10|image| (-4) vcld, main (line: 346) |11089|10:10|image| WARNING
Re: creating a base image
Will ESXi 5.0 and VCL 2.2.1 work well together. Could please send VM host profile which is assigned to vclnode01 host? What do you have for 'Data Store Path' and 'VM path'? On vclnode01 host, where do you map datastore1 and datastore2? I think 'Data Store Path' and 'VM path' in the profile need to match paths for datastore1 and datastore2 on the VM host. Thanks. On Jun 29, 2012, at 12:31 , William Robinson wrote: hi all, i'm having a problem creating a base windows 7 image and i'm wondering if it is because i'm using vcl 2.2.1 and esxi 5. the lines i think are relevant are below. any pointers would be appreciated. thanks. 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:get_vmhost_product_name(5405)|VMware product being used on VM host vclnode01: 'VMware ESXi 5.0.0 build-623860' 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:initialize(307)|product: VMware ESXi 5.0.0 build-623860, OS object: VCL::Module::OS::Linux::UnixLab 2012-06-29 12:08:30|11089|10:10|image|VIM_SSH.pm:_run_vim_cmd(193)|vim-cmd call count: 1 (hostsvc/datastore/listsummary) 2012-06-29 12:08:30|11089|10:10|image|VIM_SSH.pm:_run_vim_cmd(208)|executed command on VM host vclnode01: vim-cmd hostsvc/datastore/listsummary 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:get_datastore_info(5531)|retrieved datastore info from VM host: |11089|10:10|image| datastore1 |11089|10:10|image| datastore2 |11089|10:10|image| WARNING |11089|10:10|image| 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:_get_datastore_name(5848)|unable to determine datastore name from path: '/vmfs/volumes/local-datastore', path does not begin with any of the datastore paths: |11089|10:10|image| '[datastore2]' |11089|10:10|image| '/vmfs/volumes/datastore2' |11089|10:10|image| '/vmfs/volumes/4fd8b523-f4b9c22c-4f9b-001ec9aa4ba2' |11089|10:10|image| '[datastore1]' |11089|10:10|image| '/vmfs/volumes/datastore1' |11089|10:10|image| '/vmfs/volumes/4fcfadc7-c5fa2f69-3ffc-001ec9aa4ba2' |11089|10:10|image| ( 0) VMware.pm, _get_datastore_name (line: 5848) |11089|10:10|image| (-1) VMware.pm, _get_datastore_root_normal_path (line: 5685) |11089|10:10|image| (-2) VMware.pm, _get_normal_path (line: 5775) |11089|10:10|image| (-3) VMware.pm, get_vmx_base_directory_path (line: 2743) |11089|10:10|image| (-4) VMware.pm, initialize (line: 313) |11089|10:10|image| (-5) Module.pm, new (line: 207) |11089|10:10|image| WARNING |11089|10:10|image| 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:_get_datastore_root_normal_path(5687)|failed to determine datastore root normal path, unable to determine datastore name: /vmfs/volumes/local-datastore |11089|10:10|image| ( 0) VMware.pm, _get_datastore_root_normal_path (line: 5687) |11089|10:10|image| (-1) VMware.pm, _get_normal_path (line: 5775) |11089|10:10|image| (-2) VMware.pm, get_vmx_base_directory_path (line: 2743) |11089|10:10|image| (-3) VMware.pm, initialize (line: 313) |11089|10:10|image| (-4) Module.pm, new (line: 207) |11089|10:10|image| (-5) Module.pm, create_provisioning_object (line: 423) |11089|10:10|image| WARNING |11089|10:10|image| 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:_get_normal_path(5777)|unable to determine normal path, failed to determine datastore root normal path: /vmfs/volumes/local-datastore |11089|10:10|image| ( 0) VMware.pm, _get_normal_path (line: 5777) |11089|10:10|image| (-1) VMware.pm, get_vmx_base_directory_path (line: 2743) |11089|10:10|image| (-2) VMware.pm, initialize (line: 313) |11089|10:10|image| (-3) Module.pm, new (line: 207) |11089|10:10|image| (-4) Module.pm, create_provisioning_object (line: 423) |11089|10:10|image| (-5) State.pm, initialize (line: 117) |11089|10:10|image| WARNING |11089|10:10|image| 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:get_vmx_base_directory_path(2749)|unable to determine the vmx base directory path, failed to convert path configured in the VM profile to a normal path: /vmfs/volumes/local-datastore |11089|10:10|image| ( 0) VMware.pm, get_vmx_base_directory_path (line: 2749) |11089|10:10|image| (-1) VMware.pm, initialize (line: 313) |11089|10:10|image| (-2) Module.pm, new (line: 207) |11089|10:10|image| (-3) Module.pm, create_provisioning_object (line: 423) |11089|10:10|image| (-4) State.pm, initialize (line: 117) |11089|10:10|image| (-5) Module.pm, new (line: 207) |11089|10:10|image| WARNING |11089|10:10|image| 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:initialize(315)|unable to determine vmx base directory path on VM host vclnode01 |11089|10:10|image| ( 0) VMware.pm, initialize (line: 315) |11089|10:10|image| (-1) Module.pm, new (line: 207) |11089|10:10|image| (-2) Module.pm, create_provisioning_object (line: 423) |11089|10:10|image| (-3) State.pm, initialize (line: 117) |11089|10:10|image| (-4) Module.pm, new (line: 207) |11089|10:10|image| (-5) vcld, make_new_child (line: 564) |11089|10:10|image|
Re: creating a base image
you are correct. right now those are set to the system defaults: VMware ESX - local network storage VM type:vmware ESXiImage:No Image Repository Path:null Datastore Path:/vmfs/volumes/nfs-datastore1 VM Path:/vmfs/volumes/local-datastore Virtual Switch 0:Private Virtual Switch 1:Public VM Disk:localdisk i'm updating the profile and will give it another shot. thanks! will On 06/29/2012 01:40 PM, Dmitri Chebotarov wrote: Will ESXi 5.0 and VCL 2.2.1 work well together. Could please send VM host profile which is assigned to vclnode01 host? What do you have for 'Data Store Path' and 'VM path'? On vclnode01 host, where do you map datastore1 and datastore2? I think 'Data Store Path' and 'VM path' in the profile need to match paths for datastore1 and datastore2 on the VM host. Thanks. On Jun 29, 2012, at 12:31 , William Robinson wrote: hi all, i'm having a problem creating a base windows 7 image and i'm wondering if it is because i'm using vcl 2.2.1 and esxi 5. the lines i think are relevant are below. any pointers would be appreciated. thanks. 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:get_vmhost_product_name(5405)|VMware product being used on VM host vclnode01: 'VMware ESXi 5.0.0 build-623860' 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:initialize(307)|product: VMware ESXi 5.0.0 build-623860, OS object: VCL::Module::OS::Linux::UnixLab 2012-06-29 12:08:30|11089|10:10|image|VIM_SSH.pm:_run_vim_cmd(193)|vim-cmd call count: 1 (hostsvc/datastore/listsummary) 2012-06-29 12:08:30|11089|10:10|image|VIM_SSH.pm:_run_vim_cmd(208)|executed command on VM host vclnode01: vim-cmd hostsvc/datastore/listsummary 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:get_datastore_info(5531)|retrieved datastore info from VM host: |11089|10:10|image| datastore1 |11089|10:10|image| datastore2 |11089|10:10|image| WARNING |11089|10:10|image| 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:_get_datastore_name(5848)|unable to determine datastore name from path: '/vmfs/volumes/local-datastore', path does not begin with any of the datastore paths: |11089|10:10|image| '[datastore2]' |11089|10:10|image| '/vmfs/volumes/datastore2' |11089|10:10|image| '/vmfs/volumes/4fd8b523-f4b9c22c-4f9b-001ec9aa4ba2' |11089|10:10|image| '[datastore1]' |11089|10:10|image| '/vmfs/volumes/datastore1' |11089|10:10|image| '/vmfs/volumes/4fcfadc7-c5fa2f69-3ffc-001ec9aa4ba2' |11089|10:10|image| ( 0) VMware.pm, _get_datastore_name (line: 5848) |11089|10:10|image| (-1) VMware.pm, _get_datastore_root_normal_path (line: 5685) |11089|10:10|image| (-2) VMware.pm, _get_normal_path (line: 5775) |11089|10:10|image| (-3) VMware.pm, get_vmx_base_directory_path (line: 2743) |11089|10:10|image| (-4) VMware.pm, initialize (line: 313) |11089|10:10|image| (-5) Module.pm, new (line: 207) |11089|10:10|image| WARNING |11089|10:10|image| 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:_get_datastore_root_normal_path(5687)|failed to determine datastore root normal path, unable to determine datastore name: /vmfs/volumes/local-datastore |11089|10:10|image| ( 0) VMware.pm, _get_datastore_root_normal_path (line: 5687) |11089|10:10|image| (-1) VMware.pm, _get_normal_path (line: 5775) |11089|10:10|image| (-2) VMware.pm, get_vmx_base_directory_path (line: 2743) |11089|10:10|image| (-3) VMware.pm, initialize (line: 313) |11089|10:10|image| (-4) Module.pm, new (line: 207) |11089|10:10|image| (-5) Module.pm, create_provisioning_object (line: 423) |11089|10:10|image| WARNING |11089|10:10|image| 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:_get_normal_path(5777)|unable to determine normal path, failed to determine datastore root normal path: /vmfs/volumes/local-datastore |11089|10:10|image| ( 0) VMware.pm, _get_normal_path (line: 5777) |11089|10:10|image| (-1) VMware.pm, get_vmx_base_directory_path (line: 2743) |11089|10:10|image| (-2) VMware.pm, initialize (line: 313) |11089|10:10|image| (-3) Module.pm, new (line: 207) |11089|10:10|image| (-4) Module.pm, create_provisioning_object (line: 423) |11089|10:10|image| (-5) State.pm, initialize (line: 117) |11089|10:10|image| WARNING |11089|10:10|image| 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:get_vmx_base_directory_path(2749)|unable to determine the vmx base directory path, failed to convert path configured in the VM profile to a normal path: /vmfs/volumes/local-datastore |11089|10:10|image| ( 0) VMware.pm, get_vmx_base_directory_path (line: 2749) |11089|10:10|image| (-1) VMware.pm, initialize (line: 313) |11089|10:10|image| (-2) Module.pm, new (line: 207) |11089|10:10|image| (-3) Module.pm, create_provisioning_object (line: 423) |11089|10:10|image| (-4) State.pm, initialize (line: 117) |11089|10:10|image| (-5) Module.pm, new (line: 207) |11089|10:10|image| WARNING |11089|10:10|image| 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:initialize(315)|unable to determine vmx base directory path on VM host vclnode01 |11089|10:10|image| ( 0)
Re: Creating a base image
[root@VCL-Server Desktop]# perl CatPerlTest.pl
OK: executed command: cat /etc/hosts, pid: 19185, exit status: 0, output:
127.0.0.1 localhost localhost.localdomain localhost4
localhost4.localdomain4
192.168.0.101 1vsphere.upb.pitt.edu 1vsphere
192.168.0.102 2vsphere.upb.pitt.edu 2vsphere
192.168.0.103 3vsphere.upb.pitt.edu 3vsphere
192.168.0.104 4vsphere.upb.pitt.edu 4vsphere
192.168.0.105 5vsphere.upb.pitt.edu 5vsphere
192.168.0.106 6vsphere.upb.pitt.edu 6vsphere
192.168.0.107 7vsphere.upb.pitt.edu 7vsphere
192.168.0.108 8vsphere.upb.pitt.edu 8vsphere
192.168.0.109 9vsphere.upb.pitt.edu 9vsphere
192.168.0.110 10vsphere.upb.pitt.edu 10vsphere
192.168.0.3vsphere.upb.pitt.edu vsphere
192.168.0.2vcl-server.upb.pitt.edu vcl-server
::1 localhost localhost.localdomain localhost6
localhost6.localdomain6
Aaron
I just looked at the peace of code which generates the error.
There is really nothing unusual:
# Retrieve the contents of /etc/hosts using cat
my ($exit_status, $output) = run_command('cat /etc/hosts', 1);
if (defined $exit_status $exit_status == 0) {
notify($ERRORS{'DEBUG'}, 0, retrieved contents of
/etc/hosts on this management node, contains . scalar
@$output . lines);
}
elsif (defined $exit_status) {
notify($ERRORS{'WARNING'}, 0, failed to cat /etc/hosts on
this management node, exit status: $exit_status,
output:\n . join(\n, @$output));
return;
}
else {
notify($ERRORS{'WARNING'}, 0, failed to run command to
cat /etc/hosts on this management node);
return;
}
Could you please save following code as a hosts-test.pl file and execute
it (perl hosts-test.pl).
I got this code from utils.pm's run_command funtion. This what generates
exit_code 255 in your case.
What output do you get?
#!/usr/bin/perl
$command = 'cat /etc/hosts';
if ($pid = open(COMMAND, $command 21 |)) {
# Capture the output of the command
@output = COMMAND;
# Save the exit status
$exit_status = $? 8;
if ($? == -1) {
print(Error: \$? is set to $?, setting exit status to 0,
Perl bug likely encountered);
$exit_status = 0;
}
# Close the command handle
close(COMMAND);
}
else {
print(Error: failed to execute command: $command, error:
$!);
exit 0;
}
print(\nOK: executed command: $command, pid: $pid, exit
status: $exit_status, output:\n\n@output);
Thanks.
On Mar 16, 2012, at 13:13 , Aaron Bryant wrote:
After seeing your suggestion, I have done the following changes to no
avail:
- Disabled Selinux
- Changed the syntax of the hosts file from IP Address - Alias -
Hostname, to IP Address - Hostname - Alias (Just to make sure this
wasn't causing a problem)
I can't seem to find any problems with permissions. I also could not
find any valid reason for the cat to fail, although directly after it
fails, it prints the output of the cat command in the log file.
The problem is still occurring even after the simple changes I have
made. Any additional suggestions?
On 2/28/2012 4:21 PM, Dmitri Chebotarov wrote:
Aaron
The problem seems to be with your /etc/hosts file.
'cat /etc/hosts' failed with exit status 255, when exit status 0 is
expected. B/c of this, vcl couldn't get private ip address and didn't
attempt to connect to the host. I cannot think of any valid reasons why
'cat /etc/hosts' would fail... Can you double-check syntax, permission,
selinux, ... ?
...
|10951|20:20|image| WARNING
|10951|20:20|image| 2012-02-28
13:32:34|10951|20:20|image|DataStructure.pm:get_computer_private_ip_address(1589)|failed
to cat /etc/hosts on this management node, exit status: 255, output:
|10951|20:20|image| 127.0.0.1 localhost localhost.localdomain
localhost4 localhost4.localdomain4
|10951|20:20|image| 192.168.0.101 1vsphere 1vsphere.upb.pitt.edu
...
On Feb 28, 2012, at 13:28 , Aaron Bryant wrote:
Greetings,
I completed installing Cygwin SSHD and I'm attempting to run the vcld
-setup command. My problem occurs in this step while creating a base
image. I am able to get through all of the prompts and start the
creation before the script crashes. I have checked the
'/var/log/vcld.log' log file and this is a portion of the output:
---
VCL::Module::Provisioning::VMware::vSphere_SDK
|10951|20:20|image| WARNING
|10951|20:20|image| 2012-02-28
13:32:34|10951|20:20|image|VMware.pm:initialize(273)|no methods are
available to control VM host vsphere, the
vSphere SDK cannot be used to control the VM host and the host OS
cannot be controlled via SSH
|10951|20:20|image| (
0) VMware.pm, initialize (line: 273
Re: Creating a base image
Yes, I have had no problems using SSH between the management node and the VMWare host. On 3/16/2012 1:39 PM, Mike Haudenschild wrote: Hi Aaron, The first thing I notice in the log output is this: 13:32:34|10951|20:20|image|VMware.pm:initialize(273)|no methods are available to control VM host vsphere, the vSphere SDK cannot be used to control the VM host and the host OS cannot be controlled via SSH Are you able to SSH from the management node to the VMWare host? ssh -i /etc/vcl/vcl.key VM host Regards, Mike Sent via iPhone
Re: Creating a base image
Hi Aaron, Do you recall if install_perl_libs.pl complained about any missing modules when you installed the management node code? I'm not sure if this applies to your situation, but in all of my VCL 2.2.1 installs I've had to make some adjustments to get all the needed PERL modules installed properly. (I was on CentOS 5.7.) You're not using the vSphere SDK, right? Do you have a username/password entered in the fields on the VM Host Profile configuration page? Regards, Mike -- *Mike Haudenschild* Education Systems Manager Longsight Group (740) 599-5005 x809 m...@longsight.com www.longsight.com On Tue, Mar 20, 2012 at 13:47, Aaron Bryant amb...@pitt.edu wrote: Yes, I have had no problems using SSH between the management node and the VMWare host. On 3/16/2012 1:39 PM, Mike Haudenschild wrote: Hi Aaron, The first thing I notice in the log output is this: 13:32:34|10951|20:20|image|VMware.pm:initialize(273)|no methods are available to control VM host vsphere, the vSphere SDK cannot be used to control the VM host and the host OS cannot be controlled via SSH Are you able to SSH from the management node to the VMWare host? ssh -i /etc/vcl/vcl.key VM host Regards, Mike Sent via iPhone
Re: Creating a base image
Up to this point, I have been following the documentation exactly, so I have configured the machine to use SSH and I have configured the VMhost using the second link below. Since your suggestion, I am attempting to work with the vsphere SDK. I am having trouble with some of the dependencies getting installed, but I feel that they will be finished soon. Is there any documentation on incorporating the VSphere SDK into the VCL Server? Aaron Bryant On 3/16/2012 3:02 PM, Aaron Coburn wrote: Given that your VMhost is called vsphere, is it safe to assume that you plan to use the vSphere API to access the host? If that is the case, you need to make sure that the vSphere SDK for perl is installed. According to your logfile, the perl libraries are either not installed or not in perl's path (i.e. @INC). If you intend to use the perl SDK, you can install it from here: http://www.vmware.com/support/developer/viperltoolkit/ (be sure to select the release corresponding to your VMware version) If you are not going to use the vSphere API, then make sure to read through this page as you configure your VMhost: https://cwiki.apache.org/confluence/display/VCL/VMware+Configuration Aaron -- Aaron Coburn Systems Administrator and Programmer Academic Technology Services, Amherst College (413) 542-5451 acob...@amherst.edu On Mar 16, 2012, at 1:13 PM, Aaron Bryant wrote: After seeing your suggestion, I have done the following changes to no avail: - Disabled Selinux - Changed the syntax of the hosts file from IP Address - Alias - Hostname, to IP Address - Hostname - Alias (Just to make sure this wasn't causing a problem) I can't seem to find any problems with permissions. I also could not find any valid reason for the cat to fail, although directly after it fails, it prints the output of the cat command in the log file. The problem is still occurring even after the simple changes I have made. Any additional suggestions? On 2/28/2012 4:21 PM, Dmitri Chebotarov wrote: Aaron The problem seems to be with your /etc/hosts file. 'cat /etc/hosts' failed with exit status 255, when exit status 0 is expected. B/c of this, vcl couldn't get private ip address and didn't attempt to connect to the host. I cannot think of any valid reasons why 'cat /etc/hosts' would fail... Can you double-check syntax, permission, selinux, ... ? ... |10951|20:20|image| WARNING |10951|20:20|image| 2012-02-28 13:32:34|10951|20:20|image|DataStructure.pm:get_computer_private_ip_address(1589)|failed to cat /etc/hosts on this management node, exit status: 255, output: |10951|20:20|image| 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 |10951|20:20|image| 192.168.0.101 1vsphere 1vsphere.upb.pitt.edu ... On Feb 28, 2012, at 13:28 , Aaron Bryant wrote: Greetings, I completed installing Cygwin SSHD and I'm attempting to run the vcld -setup command. My problem occurs in this step while creating a base image. I am able to get through all of the prompts and start the creation before the script crashes. I have checked the '/var/log/vcld.log' log file and this is a portion of the output: --- VCL::Module::Provisioning::VMware::vSphere_SDK |10951|20:20|image| WARNING |10951|20:20|image| 2012-02-28 13:32:34|10951|20:20|image|VMware.pm:initialize(273)|no methods are available to control VM host vsphere, the vSphere SDK cannot be used to control the VM host and the host OS cannot be controlled via SSH |10951|20:20|image| ( 0) VMware.pm, initialize (line: 273) |10951|20:20|image| (-1) Module.pm, new (line: 207) |10951|20:20|image| (-2) Module.pm, create_provisioning_object (line: 423) |10951|20:20|image| (-3) State.pm, initialize (line: 117) |10951| 20:20|image| (-4) Module.pm, new (line: 207) |10951|20:20|image| (-5) vcld, make_new_child (line: 564) |10951|20:20| image| WARNING |10951|20:20|image| 2012-02-28 13:32:34|10951|20:20|image| Module.pm:create_provisioning_object(431)|provisioning object could not be created, returning 0 |10951|20:20|image| ( 0) Module.pm, create_provisioning_object (line: 431) |10951|20:20|image| (-1) State.pm, initialize (line: 117) | 10951|20:20|image| (-2) Module.pm, new (line: 207) |10951|20:20|image| (-3) vcld, make_new_child (line: 564) |10951| - I have checked and am able to ssh between the management node and the virtual machines using key authentication. Please see the log file attached for more information. Thanks, Aaron Bryant Logfile.txt Thank you. - Dmitri Chebotarov dcheb...@gmu.edu 703-993-6175 - Logfile.txt
Re: Creating a base image
Hi Aaron, The first thing I notice in the log output is this: 13:32:34|10951|20:20|image|VMware.pm:initialize(273)|no methods are available to control VM host vsphere, the vSphere SDK cannot be used to control the VM host and the host OS cannot be controlled via SSH Are you able to SSH from the management node to the VMWare host? ssh -i /etc/vcl/vcl.key VM host Regards, Mike Sent via iPhone
Re: Creating a base image
Given that your VMhost is called vsphere, is it safe to assume that you plan to use the vSphere API to access the host? If that is the case, you need to make sure that the vSphere SDK for perl is installed. According to your logfile, the perl libraries are either not installed or not in perl's path (i.e. @INC). If you intend to use the perl SDK, you can install it from here: http://www.vmware.com/support/developer/viperltoolkit/ (be sure to select the release corresponding to your VMware version) If you are not going to use the vSphere API, then make sure to read through this page as you configure your VMhost: https://cwiki.apache.org/confluence/display/VCL/VMware+Configuration Aaron -- Aaron Coburn Systems Administrator and Programmer Academic Technology Services, Amherst College (413) 542-5451 acob...@amherst.edu On Mar 16, 2012, at 1:13 PM, Aaron Bryant wrote: After seeing your suggestion, I have done the following changes to no avail: - Disabled Selinux - Changed the syntax of the hosts file from IP Address - Alias - Hostname, to IP Address - Hostname - Alias (Just to make sure this wasn't causing a problem) I can't seem to find any problems with permissions. I also could not find any valid reason for the cat to fail, although directly after it fails, it prints the output of the cat command in the log file. The problem is still occurring even after the simple changes I have made. Any additional suggestions? On 2/28/2012 4:21 PM, Dmitri Chebotarov wrote: Aaron The problem seems to be with your /etc/hosts file. 'cat /etc/hosts' failed with exit status 255, when exit status 0 is expected. B/c of this, vcl couldn't get private ip address and didn't attempt to connect to the host. I cannot think of any valid reasons why 'cat /etc/hosts' would fail... Can you double-check syntax, permission, selinux, ... ? ... |10951|20:20|image| WARNING |10951|20:20|image| 2012-02-28 13:32:34|10951|20:20|image|DataStructure.pm:get_computer_private_ip_address(1589)|failed to cat /etc/hosts on this management node, exit status: 255, output: |10951|20:20|image| 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 |10951|20:20|image| 192.168.0.101 1vsphere 1vsphere.upb.pitt.edu ... On Feb 28, 2012, at 13:28 , Aaron Bryant wrote: Greetings, I completed installing Cygwin SSHD and I'm attempting to run the vcld -setup command. My problem occurs in this step while creating a base image. I am able to get through all of the prompts and start the creation before the script crashes. I have checked the '/var/log/vcld.log' log file and this is a portion of the output: --- VCL::Module::Provisioning::VMware::vSphere_SDK |10951|20:20|image| WARNING |10951|20:20|image| 2012-02-28 13:32:34|10951|20:20|image|VMware.pm:initialize(273)|no methods are available to control VM host vsphere, the vSphere SDK cannot be used to control the VM host and the host OS cannot be controlled via SSH |10951|20:20|image| ( 0) VMware.pm, initialize (line: 273) |10951|20:20|image| (-1) Module.pm, new (line: 207) |10951|20:20|image| (-2) Module.pm, create_provisioning_object (line: 423) |10951|20:20|image| (-3) State.pm, initialize (line: 117) |10951| 20:20|image| (-4) Module.pm, new (line: 207) |10951|20:20|image| (-5) vcld, make_new_child (line: 564) |10951|20:20| image| WARNING |10951|20:20|image| 2012-02-28 13:32:34|10951|20:20|image| Module.pm:create_provisioning_object(431)|provisioning object could not be created, returning 0 |10951|20:20|image| ( 0) Module.pm, create_provisioning_object (line: 431) |10951|20:20|image| (-1) State.pm, initialize (line: 117) | 10951|20:20|image| (-2) Module.pm, new (line: 207) |10951|20:20|image| (-3) vcld, make_new_child (line: 564) |10951| - I have checked and am able to ssh between the management node and the virtual machines using key authentication. Please see the log file attached for more information. Thanks, Aaron Bryant Logfile.txt Thank you. - Dmitri Chebotarov dcheb...@gmu.edu 703-993-6175 - Logfile.txt smime.p7s Description: S/MIME cryptographic signature
Re: Creating a base image
Hello Aaron Can you log in into your Vsphere Client ESXI 4.1 Server the one hosting the images Go to Configurations Under Software Click on Security Profile Click on Properties Under Remote Access make sure you have Remote Teach Support SSH is Running and Automatically Turned on You should check if you can ssh without a password from the base image to the management node but also and vice versa. Also did you add in the IP range into trusted hosts? -Alex On Tue, Feb 28, 2012 at 10:28 AM, Aaron Bryant amb...@pitt.edu wrote: Greetings, I completed installing Cygwin SSHD and I'm attempting to run the vcld -setup command. My problem occurs in this step while creating a base image. I am able to get through all of the prompts and start the creation before the script crashes. I have checked the '/var/log/vcld.log' log file and this is a portion of the output: --- VCL::Module::Provisioning::VMware::vSphere_SDK |10951|20:20|image| WARNING |10951|20:20|image| 2012-02-28 13:32:34|10951|20:20|image|VMware.pm:initialize(273)|no methods are available to control VM host vsphere, the vSphere SDK cannot be used to control the VM host and the host OS cannot be controlled via SSH |10951|20:20|image| ( 0) VMware.pm, initialize (line: 273) |10951|20:20|image| (-1) Module.pm, new (line: 207) |10951|20:20|image| (-2) Module.pm, create_provisioning_object (line: 423) |10951|20:20|image| (-3) State.pm, initialize (line: 117) |10951| 20:20|image| (-4) Module.pm, new (line: 207) |10951|20:20|image| (-5) vcld, make_new_child (line: 564) |10951|20:20| image| WARNING |10951|20:20|image| 2012-02-28 13:32:34|10951|20:20|image| Module.pm:create_provisioning_object(431)|provisioning object could not be created, returning 0 |10951|20:20|image| ( 0) Module.pm, create_provisioning_object (line: 431) |10951|20:20|image| (-1) State.pm, initialize (line: 117) | 10951|20:20|image| (-2) Module.pm, new (line: 207) |10951|20:20|image| (-3) vcld, make_new_child (line: 564) |10951| - I have checked and am able to ssh between the management node and the virtual machines using key authentication. Please see the log file attached for more information. Thanks, Aaron Bryant -- Thanks, Alex Patterson User Support Services Operating System Analyst California State University, East Bay
Re: Creating a base image
I have previously added each of the servers and clients into each others Know hosts to eliminate any problems there. I have discovered that I am able to use SSH key authentication between the Management node and the client, but not from the client back to the Management node. Password authentication will work for the SSH connection between the client and management node, but not key authentication. I have tried to copy the management node's private key, which I am assuming is /etc/vcl/vcl.key, to the client machine but to no avail. The client machine still prompts for a password when entering ssh Aaron On 2/28/2012 1:40 PM, Alexander Patterson wrote: Hello Aaron Can you log in into your Vsphere Client ESXI 4.1 Server the one hosting the images Go to Configurations Under Software Click on Security Profile Click on Properties Under Remote Access make sure you have Remote Teach Support SSH is Running and Automatically Turned on You should check if you can ssh without a password from the base image to the management node but also and vice versa. Also did you add in the IP range into trusted hosts? -Alex On Tue, Feb 28, 2012 at 10:28 AM, Aaron Bryantamb...@pitt.edu wrote: Greetings, I completed installing Cygwin SSHD and I'm attempting to run the vcld -setup command. My problem occurs in this step while creating a base image. I am able to get through all of the prompts and start the creation before the script crashes. I have checked the '/var/log/vcld.log' log file and this is a portion of the output: --- VCL::Module::Provisioning::VMware::vSphere_SDK |10951|20:20|image| WARNING |10951|20:20|image| 2012-02-28 13:32:34|10951|20:20|image|VMware.pm:initialize(273)|no methods are available to control VM host vsphere, the vSphere SDK cannot be used to control the VM host and the host OS cannot be controlled via SSH |10951|20:20|image| ( 0) VMware.pm, initialize (line: 273) |10951|20:20|image| (-1) Module.pm, new (line: 207) |10951|20:20|image| (-2) Module.pm, create_provisioning_object (line: 423) |10951|20:20|image| (-3) State.pm, initialize (line: 117) |10951| 20:20|image| (-4) Module.pm, new (line: 207) |10951|20:20|image| (-5) vcld, make_new_child (line: 564) |10951|20:20| image| WARNING |10951|20:20|image| 2012-02-28 13:32:34|10951|20:20|image| Module.pm:create_provisioning_object(431)|provisioning object could not be created, returning 0 |10951|20:20|image| ( 0) Module.pm, create_provisioning_object (line: 431) |10951|20:20|image| (-1) State.pm, initialize (line: 117) | 10951|20:20|image| (-2) Module.pm, new (line: 207) |10951|20:20|image| (-3) vcld, make_new_child (line: 564) |10951| - I have checked and am able to ssh between the management node and the virtual machines using key authentication. Please see the log file attached for more information. Thanks, Aaron Bryant
Re: Creating a base image
It sounds like the issue is related to the communication between the management node and the VMware host. That, at least, is what the attached logs reflect. It is also unclear whether you are trying to access the VM Host via the vSphere API or via SSH. If it is the former, make sure that the vSphere perl modules have been installed and that the vmprofile is properly set up. If it is the latter, make sure that the ssh port is open on the VM host (there are instructions for how to do this here: https://cwiki.apache.org/confluence/display/VCL/VMware+Configuration ) and that the mgmt node is able to login successfully via ssh. As for ssh key authentication between the mgmt node and VMs, I would recommend using the gen-node-key.sh script described at the bottom of this page: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=4589006 -- Aaron Coburn Systems Administrator and Programmer Academic Technology Services, Amherst College (413) 542-5451 acob...@amherst.edu On Feb 28, 2012, at 3:45 PM, Josh Thompson wrote: You don't want to be able to ssh from the image to the management node - in fact that's a bad idea because it would allow anyone making a reservation for the image to ssh to your management node. Unfortunately, I can't speak to what is causing your problem. Josh On Tuesday, February 28, 2012 3:34:42 PM Aaron Bryant wrote: I have previously added each of the servers and clients into each others Know hosts to eliminate any problems there. I have discovered that I am able to use SSH key authentication between the Management node and the client, but not from the client back to the Management node. Password authentication will work for the SSH connection between the client and management node, but not key authentication. I have tried to copy the management node's private key, which I am assuming is /etc/vcl/vcl.key, to the client machine but to no avail. The client machine still prompts for a password when entering ssh Aaron On 2/28/2012 1:40 PM, Alexander Patterson wrote: Hello Aaron Can you log in into your Vsphere Client ESXI 4.1 Server the one hosting the images Go to Configurations Under Software Click on Security Profile Click on Properties Under Remote Access make sure you have Remote Teach Support SSH is Running and Automatically Turned on You should check if you can ssh without a password from the base image to the management node but also and vice versa. Also did you add in the IP range into trusted hosts? -Alex On Tue, Feb 28, 2012 at 10:28 AM, Aaron Bryantamb...@pitt.edu wrote: Greetings, I completed installing Cygwin SSHD and I'm attempting to run the vcld -setup command. My problem occurs in this step while creating a base image. I am able to get through all of the prompts and start the creation before the script crashes. I have checked the '/var/log/vcld.log' log file and this is a portion of the output: -- - VCL::Module::Provisioning::VMware::vSphere_SDK |10951|20:20|image| WARNING |10951|20:20|image| 2012-02-28 13:32:34|10951|20:20|image|VMware.pm:initialize(273)|no methods are available to control VM host vsphere, the vSphere SDK cannot be used to control the VM host and the host OS cannot be controlled via SSH |10951|20:20|image| ( 0) VMware.pm, initialize (line: 273) |10951|20:20|image| (-1) Module.pm, new (line: 207) |10951|20:20|image| (-2) Module.pm, create_provisioning_object (line: 423) |10951|20:20|image| (-3) State.pm, initialize (line: 117) |10951| 20:20|image| (-4) Module.pm, new (line: 207) |10951|20:20|image| (-5) vcld, make_new_child (line: 564) | | |10951|20:20| image| WARNING |10951|20:20|image| 2012-02-28 13:32:34|10951|20:20|image| Module.pm:create_provisioning_object(431)|provisioning object could not be created, returning 0 |10951|20:20|image| ( 0) Module.pm, create_provisioning_object (line: 431) |10951|20:20|image| (-1) State.pm, initialize (line: 117) 10951|20:20|image| (-2) Module.pm, new (line: 207) |10951|20:20|image| (-3) vcld, make_new_child (line: 564) |10951| -- --- I have checked and am able to ssh between the management node and the virtual machines using key authentication. Please see the log file attached for more information. Thanks, Aaron Bryant - -- - --- Josh Thompson VCL Developer North Carolina State University my GPG/PGP key can be found at pgp.mit.edu All electronic mail messages in connection with State business which are sent
Re: Creating a base image
Aaron The problem seems to be with your /etc/hosts file. 'cat /etc/hosts' failed with exit status 255, when exit status 0 is expected. B/c of this, vcl couldn't get private ip address and didn't attempt to connect to the host. I cannot think of any valid reasons why 'cat /etc/hosts' would fail... Can you double-check syntax, permission, selinux, ... ? ... |10951|20:20|image| WARNING |10951|20:20|image| 2012-02-28 13:32:34|10951|20:20|image|DataStructure.pm:get_computer_private_ip_address(1589)|failed to cat /etc/hosts on this management node, exit status: 255, output: |10951|20:20|image| 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 |10951|20:20|image| 192.168.0.101 1vsphere 1vsphere.upb.pitt.edu ... On Feb 28, 2012, at 13:28 , Aaron Bryant wrote: Greetings, I completed installing Cygwin SSHD and I'm attempting to run the vcld -setup command. My problem occurs in this step while creating a base image. I am able to get through all of the prompts and start the creation before the script crashes. I have checked the '/var/log/vcld.log' log file and this is a portion of the output: --- VCL::Module::Provisioning::VMware::vSphere_SDK |10951|20:20|image| WARNING |10951|20:20|image| 2012-02-28 13:32:34|10951|20:20|image|VMware.pm:initialize(273)|no methods are available to control VM host vsphere, the vSphere SDK cannot be used to control the VM host and the host OS cannot be controlled via SSH |10951|20:20|image| ( 0) VMware.pm, initialize (line: 273) |10951|20:20|image| (-1) Module.pm, new (line: 207) |10951|20:20|image| (-2) Module.pm, create_provisioning_object (line: 423) |10951|20:20|image| (-3) State.pm, initialize (line: 117) |10951| 20:20|image| (-4) Module.pm, new (line: 207) |10951|20:20|image| (-5) vcld, make_new_child (line: 564) |10951|20:20| image| WARNING |10951|20:20|image| 2012-02-28 13:32:34|10951|20:20|image| Module.pm:create_provisioning_object(431)|provisioning object could not be created, returning 0 |10951|20:20|image| ( 0) Module.pm, create_provisioning_object (line: 431) |10951|20:20|image| (-1) State.pm, initialize (line: 117) | 10951|20:20|image| (-2) Module.pm, new (line: 207) |10951|20:20|image| (-3) vcld, make_new_child (line: 564) |10951| - I have checked and am able to ssh between the management node and the virtual machines using key authentication. Please see the log file attached for more information. Thanks, Aaron Bryant Logfile.txt Thank you. - Dmitri Chebotarov dcheb...@gmu.edu 703-993-6175 - signature.asc Description: Message signed with OpenPGP using GPGMail
