Re: SDK can not connect to VMWare
It looks like the MAC addresses aren't configured for your VM computers
in the VCL database. This is required. When VCL creates the VM it sets
MAC address to the database value. I looked at the documentation on the
following page and noticed some problems:
https://cwiki.apache.org/confluence/display/VCL/Further+steps+if+using+only+VMWare
VM computers cannot currently be added individually. You must use the
add multiple computers option. I have updated this page. I would
suggest adding multiple VMs as described on this page, being sure to
populate the MAC addresses. You may also manually add MAC addresses to
the existing VM computer entries in the database. The
computer.eth0macaddress and computer.eth1macaddress values need to be set.
-Andy
On 2/16/2011 5:16 PM, Mauricio César Ramírez Torres wrote:
Thank you, now I can advance from this point, but now I have another
problem, when the image capture process attempts to restore the virtual
machine have problems calling the MAC, you'll have some idea why this
happens?
2011-02-15
18:13:17|29129|2:2|reload|utils.pm:insertloadlog(3933)|inserted
computer=3, transfervm, copied vmwarelinux-LinCent5-v0 to LinCent
2011-02-15 18:13:17|29129|2:2|reload|VMware.pm:get_vm_ram(3307)|image
ram setting is too low: 0 MB, 512 MB will be used
2011-02-15
18:13:17|29129|2:2|reload|VMware.pm:get_vm_os_configuration(3211)|retrieved
default VM configuration for OS: linux-x86
|29129|2:2|reload| : {
|29129|2:2|reload| : ethernet-virtualDev = vlance,
|29129|2:2|reload| : guestOS = otherlinux,
|29129|2:2|reload| : scsi-virtualDev = busLogic
|29129|2:2|reload| : }
|29129|2:2|reload| WARNING
|29129|2:2|reload| 2011-02-15
18:13:17|29129|2:2|reload|DataStructure.pm:_automethod(764)|corresponding data
has not been initialized for get_computer_eth0_mac_address:
$self-request_data-{reservation}{2}{computer}{eth0macaddress}
|29129|2:2|reload| ( 0) utils.pm, notify (line: 630)
|29129|2:2|reload| (-1) DataStructure.pm, _automethod (line: 764)
|29129|2:2|reload| (-2) Autoload.pm, __ANON__ (line: 80)
|29129|2:2|reload| (-3) VMware.pm, prepare_vmx (line: 1171)
|29129|2:2|reload| (-4) VMware.pm, load (line: 341)
|29129|2:2|reload| (-5) new.pm, reload_image (line: 687)
|29129|2:2|reload| (-6) new.pm, process (line: 282)
|29129|2:2|reload| WARNING
|29129|2:2|reload| 2011-02-15
18:13:17|29129|2:2|reload|VMware.pm:load(342)|failed to prepare vmx file
for LinCent on VM host: vclesx.nextdata.com.mx
|29129|2:2|reload| ( 0) utils.pm, notify (line: 630)
|29129|2:2|reload| (-1) VMware.pm, load (line: 342)
|29129|2:2|reload| (-2) new.pm, reload_image (line: 687)
|29129|2:2|reload| (-3) new.pm, process (line: 282)
|29129|2:2|reload| (-4) vcld, make_new_child (line: 595)
|29129|2:2|reload| (-5) vcld, main (line: 342)
|29129|2:2|reload| WARNING
|29129|2:2|reload| 2011-02-15
18:13:17|29129|2:2|reload|new.pm:reload_image(692)|vmwarelinux-LinCent5-v0
failed to load on LinCent, returning
|29129|2:2|reload| ( 0) utils.pm, notify (line: 630)
|29129|2:2|reload| (-1) new.pm, reload_image (line: 692)
|29129|2:2|reload| (-2) new.pm, process (line: 282)
|29129|2:2|reload| (-3) vcld, make_new_child (line: 595)
|29129|2:2|reload| (-4) vcld, main (line: 342)
2011-02-15
18:13:17|29129|2:2|reload|utils.pm:insertloadlog(3933)|inserted
computer=3, loadimagefailed, vmwarelinux-LinCent5-v0 failed to load on
LinCent
|29129|2:2|reload| WARNING
|29129|2:2|reload| 2011-02-15
18:13:17|29129|2:2|reload|new.pm:process(329)|failed to load LinCent
with vmwarelinux-LinCent5-v0
|29129|2:2|reload| ( 0) utils.pm, notify (line: 630)
|29129|2:2|reload| (-1) new.pm, process (line: 329)
|29129|2:2|reload| (-2) vcld, make_new_child (line: 595)
|29129|2:2|reload| (-3) vcld, main (line: 342)
2011-02-15
18:13:17|29129|2:2|reload|DataStructure.pm:get_computer_state_name(2227)|attempting
to retrieve current state of computer LinCent from the database
2011-02-15
18:13:17|29129|2:2|reload|DataStructure.pm:get_computer_state_name(2258)|retrieved
current state of computer LinCent from the database: reloading
2011-02-15
18:13:17|29129|2:2|reload|DataStructure.pm:_automethod(786)|data
structure updated:
$self-request_data-{reservation}{2}{computer}{state}{name}
|29129|2:2|reload| computer_state_name = reloading
2011-02-15 18:13:17|29129|2:2|reload|utils.pm:mail(1247)|SUCCESS --
Sending mail To: mrami...@cft.com.mx, PROBLEM -- State.pm
|29129|2:2|reload| CRITICAL
|29129|2:2|reload| 2011-02-15
18:13:17|29129|2:2|reload|State.pm:reservation_failed(287)|reservation
failed on LinCent: process failed after trying to load or make available
|29129|2:2|reload| ( 0) utils.pm, notify (line: 630)
|29129|2:2|reload| (-1) State.pm, reservation_failed (line: 287)
|29129|2:2|reload| (-2) new.pm, process (line: 332)
|29129|2:2|reload| (-3) vcld, make_new_child (line: 595)
|29129|2:2|reload| (-4) vcld, main (line: 342)
On 16/02/11 15:21, Andy Kurth wrote:
The image capture problem is occurring when
Re: Errors with network cards
Have you been able to resolve this? It seems like you were able to get
the image capture to complete based on other messages to this list. If
you're still having this problem, please send the ipconfig /all output
from the computer you're attempting to capture.
-Andy
On 2/14/2011 2:09 PM, Mauricio César Ramírez Torres wrote:
I'm out of ideas again, I could solve my problem of the path, but now
when I start to create the image I marked some errors in the NIC, but I
do not understand what the problem, the first error indicates that there
is no NIC using the IP I'm giving, but if it exists, though it does by
DHCP, should be fixed?? second thing that strikes me is that it marks
error because the second NIC is not enabled, in theory this is what will
the public IP, but right now I do not want to enable, there is a problem
if I dont have the 2 cards enabled??; the 2 must have a fixed IP?? or
may be dynamic IP's??.
Regards and as always thank you very much.
ECENT LOG ENTRIES FOR THIS PROCESS:
2011-02-14
12:32:05|19426|1:1|image|State.pm:initialize(128)|VCL::Module::Provisioning::VMware::VMware
provisioner object created
2011-02-14 12:32:05|19426|1:1|image|State.pm:initialize(142)|attempting
to load OS module: VCL::Module::OS::Windows::Version_5::XP
2011-02-14
12:32:05|19426|1:1|image|State.pm:initialize(148)|VCL::Module::OS::Windows::Version_5::XP
module loaded
2011-02-14 12:32:05|19426|1:1|image|Module.pm:new(134)|constructor
called, class=VCL::Module::OS::Windows::Version_5::XP
2011-02-14
12:32:05|19426|1:1|image|Module.pm:new(156)|VCL::Module::OS::Windows::Version_5::XP
object created
2011-02-14
12:32:05|19426|1:1|image|State.pm:initialize(151)|VCL::Module::OS::Windows::Version_5::XP
OS object created
2011-02-14 12:32:05|19426|1:1|image|State.pm:initialize(166)|returning 1
2011-02-14 12:32:05|19426|1:1|image|vcld:make_new_child(592)|VCL::image
object created and initialized
2011-02-14 12:32:06|19426|1:1|image|utils.pm:mail(1247)|SUCCESS --
Sending mail To: mrami...@cft.com.mx, VCL IMAGE Creation Started:
vmwarewinxp-winSEV5-v0
2011-02-14
12:32:08|19426|1:1|image|vSphere_SDK.pm:get_file_info(1937)|searching
for matching file paths: base directory path: '[nfsesx]
vmwarewinxp-winSEV5-v0', search pattern: 'vmwarewinxp-winSEV5-v0.vmdk'
2011-02-14
12:32:08|19426|1:1|image|vSphere_SDK.pm:get_file_info(1948)|base
directory does not exist: '[nfsesx] vmwarewinxp-winSEV5-v0'
2011-02-14
12:32:08|19426|1:1|image|vSphere_SDK.pm:find_files(1705)|matching file
count: 0
2011-02-14
12:32:08|19426|1:1|image|vSphere_SDK.pm:file_exists(1577)|file does not
exist: [nfsesx] vmwarewinxp-winSEV5-v0/vmwarewinxp-winSEV5-v0.vmdk
2011-02-14
12:32:08|19426|1:1|image|VMware.pm:does_image_exist(2940)|image does not
exist in the non-persistent directory on the VM host, checking the image
repository
2011-02-14
12:32:08|19426|1:1|image|VMware.pm:get_repository_vmdk_base_directory_path(2650)|retrieved
repository path from the VM profile: /mnt/nfsesx
2011-02-14 12:32:08|19426|1:1|image|utils.pm:run_command(9082)|executed
command: find /mnt/nfsesx/vmwarewinxp-winSEV5-v0 -iname
vmwarewinxp-winSEV5-v0.vmdk, pid: 19438, exit status: 0, output:
2011-02-14
12:32:08|19426|1:1|image|VMware.pm:does_image_exist(2967)|image does not
exist in image repository:
/mnt/nfsesx/vmwarewinxp-winSEV5-v0/vmwarewinxp-winSEV5-v0.vmdk
2011-02-14 12:32:08|19426|1:1|image|image.pm:process(148)|image
vmwarewinxp-winSEV5-v0 does not exist in the repository
2011-02-14
12:32:08|19426|1:1|image|DataStructure.pm:_automethod(786)|data
structure updated: $self-request_data-{reservation}{1}{image}{lastupdate}
|19426|1:1|image| image_lastupdate = 2011-02-14 12:32:08
2011-02-14
12:32:08|19426|1:1|image|DataStructure.pm:_automethod(786)|data
structure updated:
$self-request_data-{reservation}{1}{imagerevision}{datecreated}
|19426|1:1|image| imagerevision_date_created = 2011-02-14 12:32:08
2011-02-14 12:32:08|19426|1:1|image|image.pm:process(164)|calling
provisioning module's capture() subroutine
2011-02-14 12:32:08|19426|1:1|image|utils.pm:run_command(9070)|$? is set
to -1, setting exit status to 0, Perl bug likely encountered
2011-02-14 12:32:08|19426|1:1|image|utils.pm:nmap_port(2699)|port 22 is
open on winSEV
2011-02-14 12:32:08|19426|1:1|image|utils.pm:nmap_port(2707)|port 24 is
closed on winSEV
2011-02-14 12:32:09|19426|1:1|image|OS.pm:is_ssh_responding(430)|winSEV
is responding to SSH, port 22: open, port 24: closed
2011-02-14 12:32:09|19426|1:1|image|utils.pm:nmap_port(2699)|port 22 is
open on winSEV
2011-02-14 12:32:09|19426|1:1|image|utils.pm:nmap_port(2707)|port 24 is
closed on winSEV
2011-02-14 12:32:10|19426|1:1|image|OS.pm:is_ssh_responding(430)|winSEV
is responding to SSH, port 22: open, port 24: closed
2011-02-14 12:32:11|19426|1:1|image|Windows.pm:is_64_bit(7709)|32-bit
Windows OS detected, PROCESSOR_IDENTIFIER: x86 Family 6 Model 44
Stepping 2, GenuineIntel
2011-02-14
12:32:11|19426|1:1|image|Windows.pm:get_system32_path(7753)|32-bit
Windows OS installed on
