Can't capture a Win XP image
Hi everyone,
Because of the problems I was having with repeatedly updating an image, I
decided to build one image (Windows XP) with all of the necessary applications
already installed BEFORE trying to capture it into the VCL.
It didn't take long before I received a "Problem" email. Can someone help me
troubleshoot this? We didn't have any troubles capturing Windows XP images
before.
Here's the error I get (more of the log below):
Can't locate object method "execute" via package
"VCL::Module::OS::Windows::Version_5::XP" at
/usr/local/vcl/bin/../lib/VCL/Module/Provisioning/VMware/vmware_cmd.pm line 101.
Thanks,
Adam
---
RECENT LOG ENTRIES FOR THIS PROCESS:
|8993|223:223|image| (-5) Module.pm, new (line: 207)
2012-07-02
14:36:40|8993|223:223|image|VMware.pm:get_vmhost_datastructure(1190)|created
DataStructure object for VM host: vmwg0-120-62
2012-07-02
14:36:40|8993|223:223|image|VMware.pm:get_vmhost_os_object(1232)|attempting to
load VM host OS module: VCL::Module::OS::Windows::Version_5::XP
2012-07-02 14:36:40|8993|223:223|image|VMware.pm:get_vmhost_os_object(1238)|VM
host OS module loaded: VCL::Module::OS::Windows::Version_5::XP
2012-07-02
14:36:40|8993|223:223|image|Module.pm:create_mn_os_object(335)|management node
OS object has already been created, address: 202b9670, returning 1
2012-07-02
14:36:40|8993|223:223|image|Module.pm:new(196)|VCL::Module::OS::Windows::Version_5::XP
object created for image vmwarewinxp-WinXPFullBase75-v0, address: 20b05c00
2012-07-02 14:36:40|8993|223:223|image|VMware.pm:get_vmhost_os_object(1244)|VM
host OS object created: VCL::Module::OS::Windows::Version_5::XP
2012-07-02
14:37:00|8993|223:223|image|OS.pm:is_ssh_responding(401)|vmwg0-120-62 is
responding to SSH, port 22: open, port 24: closed
2012-07-02 14:37:00|8993|223:223|image|VMware.pm:initialize(254)|OS on VM host
vmwg0-120-62 will be controlled using a VCL::Module::OS::Windows::Version_5::XP
OS object
|8993|223:223|image| WARNING
|8993|223:223|image| 2012-07-02
14:37:00|8993|223:223|image|DataStructure.pm:_automethod(812)|corresponding
data has not been initialized for get_vmhost_computer_id:
$self->request_data->{reservation}{223}{computer}{vmhost}{computerid}
|8993|223:223|image| ( 0) DataStructure.pm, _automethod (line: 812)
|8993|223:223|image| (-1) Autoload.pm, __ANON__ (line: 80)
|8993|223:223|image| (-2) VMware.pm, get_vmhost_datastructure (line: 1161)
|8993|223:223|image| (-3) VMware.pm, get_vmhost_api_object (line: 1282)
|8993|223:223|image| (-4) VMware.pm, initialize (line: 265)
|8993|223:223|image| (-5) Module.pm, new (line: 207)
|8993|223:223|image| WARNING
|8993|223:223|image| 2012-07-02
14:37:00|8993|223:223|image|DataStructure.pm:_automethod(812)|corresponding
data has not been initialized for get_vmhost_profile_image_id:
$self->request_data->{reservation}{223}{computer}{vmhost}{vmprofile}{imageid}
|8993|223:223|image| ( 0) DataStructure.pm, _automethod (line: 812)
|8993|223:223|image| (-1) Autoload.pm, __ANON__ (line: 80)
|8993|223:223|image| (-2) VMware.pm, get_vmhost_datastructure (line: 1162)
|8993|223:223|image| (-3) VMware.pm, get_vmhost_api_object (line: 1282)
|8993|223:223|image| (-4) VMware.pm, initialize (line: 265)
|8993|223:223|image| (-5) Module.pm, new (line: 207)
2012-07-02
14:37:00|8993|223:223|image|VMware.pm:get_vmhost_datastructure(1190)|created
DataStructure object for VM host: vmwg0-120-62
2012-07-02
14:37:00|8993|223:223|image|VMware.pm:get_vmhost_api_object(1293)|attempting to
load VMware control module: VCL::Module::Provisioning::VMware::vSphere_SDK
2012-07-02
14:37:00|8993|223:223|image|VMware.pm:get_vmhost_api_object(1299)|loaded VMware
control module: VCL::Module::Provisioning::VMware::vSphere_SDK
2012-07-02 14:37:00|8993|223:223|image|Module.pm:new(172)|set 'vmhost_data' key
for VCL::Module::Provisioning::VMware::vSphere_SDK object from arguments
2012-07-02 14:37:00|8993|223:223|image|Module.pm:new(172)|set 'vmhost_os' key
for VCL::Module::Provisioning::VMware::vSphere_SDK object from arguments
2012-07-02
14:37:00|8993|223:223|image|Module.pm:create_mn_os_object(335)|management node
OS object has already been created, address: 202b9670, returning 1
2012-07-02
14:37:00|8993|223:223|image|Module.pm:new(200)|VCL::Module::Provisioning::VMware::vSphere_SDK
object created for computer vmwg0-120-62, address: 20b32390
2012-07-02 14:37:00|8993|223:223|image|vSphere_SDK.pm:initialize(1826)|vSphere
SDK for Perl does not appear to be installed on this managment node, unable to
load VMware vSphere SDK Perl modules
2012-07-02
14:37:00|8993|223:223|image|VMware.pm:get_vmhost_api_object(1313)|API object
could not be created: VCL::Module::Provisioning::VMware::vSphere_SDK
|8993|223:223|image| WARNING
|8993|223:223|image| 2012-07-02
14:37:00|8993|223:223|image|DataStructure.pm:_automethod(812)|corresponding
data has not been initialized for get_vmhost_computer_id:
$self->request_data->{reservation}{223}{
Re: VCL: public/private IP discrepency?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday, June 26, 2012 8:27:07 AM Michael Jinks wrote: > It > looks like Aaron got it right when he directed me to the configuration > settings for the management node, where public-side IP configuration is > set to "Static", that apparently means "set the public IP to match the > listed value for the private IP", clearly not what we want. My question > now is what to do instead; how to get a static (or effectively static, > i.e. predictable) IP address for deployed machines without using that > setting. Michael, VCL always needs fixed DHCP on the private network. For the public network, "static" means that once sshd is up on a node on the private interface, VCL will connect to the node across the private network and set the public IP on the public interface to what is in the database at computer.IPaddress (the public address) for that node. It should not be setting the public address to what is in the database at computer.privateIPaddress. Prior to 2.3 (unreleased), you can only set the private address of a node when you initially add it, and only using the "add multiple computers" part of the site (hint: you can actually add a single computer using the "add multiple" pages). For any nodes you already have in the database, you will need to change the private IP address directly in the database if so desired. So, you should be able to obtain your goal using the "static" setting. Josh - -- - --- 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 to or received by this account are subject to the NC Public Records Law and may be disclosed to third parties. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (GNU/Linux) iEYEARECAAYFAk/x7ZkACgkQV/LQcNdtPQONfwCfc/YYO1M/hb3gt6nd46xjplPj UakAn12OzufWWJ7A/VF10vPfYNoDdnwU =gzEk -END PGP SIGNATURE-
Re: RPM-ing VCL 2.2.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Everett, I'd definitely like to see rpms for installing VCL. Josh On Friday, June 29, 2012 9:24:03 AM Everett Toews wrote: > Does anyone on the VCL core dev team have an interest in this? Should we > create a JIRA issue for it? > > Regards, > Everett > > On Mon, Jun 25, 2012 at 5:00 PM, Curtis C. wrote: > > Hi All, > > > > I've been working on an initial spec file for VCL 2.2.1. Currently I > > believe all the dependencies, CPAN modules included, can be obtained > > from the EPEL and RPMForge repositories. If the project is going to > > support RHEL and CentOS only then providing a RPM could allow you to > > remove the requirement to run (and maintain) the perl libs install > > script. > > > > Still a bit more work to do, but I thought I would send it along > > before I get too far to find out if anyone has > > suggestions/comments/criticisms. :) > > > > You can see it here: > > https://github.com/cybera/rpmspecs/blob/master/vcl.spec > > > > Right now it creates 3 packages: a main doc package (just contains the > > sql files right now), a web package, and a management node package. > > > > One question I have is about the: > > > > use VMware::Vix::Simple; > > use VMware::Vix::API::Constants > > > > in the VIX_API.pm file. Those libraries are not, AFAIK, distributed > > with VCL and the official install docs don't ask to have them > > installed either. But the rpmbuild process picks those modules up as > > requirements. > > > > Thanks, > > Curtis. - -- - --- 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 to or received by this account are subject to the NC Public Records Law and may be disclosed to third parties. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (GNU/Linux) iEYEARECAAYFAk/x6aIACgkQV/LQcNdtPQMR2QCfaC+Z2pMsgSqzz9VF+TTtsvoy o6oAn04jjYZJqKL6Uq+2JjJiTVSwNzB+ =1SdY -END PGP SIGNATURE-
Re: Problem to create Base Image - VCL 2.2
Zapata Are you using VCL 2.2 or VCL 2.2.1? Thanks. On Jul 2, 2012, at 12:02 , Dmitri Chebotarov wrote: > > Hmm... I'm not sure why it fails when cannot locate any drivers (.inf > files). > I checked mine Windows VMs and they don't have anything under > c:/cygwin/home/root/VCL/Drivers folder and yet I was able to capture the > image. > > May be someone else has an idea. > > Thanks. > > On Jul 2, 2012, at 11:40 , Zapata Vivas Darío wrote: > >> Dmitri >> >> Thanks, I corrected the problem with language. Now I have the next error >> logs: >> >> 2012-07-02 >> 09:32:13|8053|44:44|image|Windows.pm:get_driver_inf_paths(8726)|attempting >> to locate driver .inf paths matching any class >> 2012-07-02 >> 09:32:13|8053|44:44|image|utils.pm:run_ssh_command(5442)|executing SSH >> command on lab-template1: >> |8053|44:44|image| /usr/bin/ssh -i /etc/vcl/vcl.key -l root -p 22 -x >> lab-template1 '/usr/bin/grep.exe -Eirl --include="*.[iI][nN][fF]" ".*" >> C:/Cygwin/home/root/VCL/Drivers' 2>&1 >> 2012-07-02 >> 09:32:16|8053|44:44|image|Windows.pm:get_driver_inf_paths(8750)|found 0 >> driver .inf paths, grep output: >> |8053|44:44|image| WARNING >> |8053|44:44|image| 2012-07-02 >> 09:32:16|8053|44:44|image|Windows.pm:set_device_path_key(8794)|failed to >> locate driver .inf paths >> |8053|44:44|image| ( 0) utils.pm, notify (line: 630) >> |8053|44:44|image| (-1) Windows.pm, set_device_path_key (line: 8794) >> |8053|44:44|image| (-2) Windows.pm, prepare_post_load (line: 3490) >> |8053|44:44|image| (-3) 7.pm, pre_capture (line: 177) >> |8053|44:44|image| (-4) VMware.pm, capture (line: 485) >> |8053|44:44|image| (-5) image.pm, process (line: 165) >> |8053|44:44|image| (-6) vcld, make_new_child (line: 595) >> |8053|44:44|image| WARNING >> |8053|44:44|image| 2012-07-02 >> 09:32:16|8053|44:44|image|Windows.pm:prepare_post_load(3491)|failed to set >> the DevicePath registry key >> |8053|44:44|image| ( 0) utils.pm, notify (line: 630) >> |8053|44:44|image| (-1) Windows.pm, prepare_post_load (line: 3491) >> |8053|44:44|image| (-2) 7.pm, pre_capture (line: 177) >> |8053|44:44|image| (-3) VMware.pm, capture (line: 485) >> |8053|44:44|image| (-4) image.pm, process (line: 165) >> |8053|44:44|image| (-5) vcld, make_new_child (line: 595) >> |8053|44:44|image| (-6) vcld, main (line: 342) >> |8053|44:44|image| WARNING >> |8053|44:44|image| 2012-07-02 >> 09:32:16|8053|44:44|image|7.pm:pre_capture(178)|capture preparation failed, >> failed to run prepare post_load >> |8053|44:44|image| ( 0) utils.pm, notify (line: 630) >> |8053|44:44|image| (-1) 7.pm, pre_capture (line: 178) >> |8053|44:44|image| (-2) VMware.pm, capture (line: 485) >> |8053|44:44|image| (-3) image.pm, process (line: 165) >> |8053|44:44|image| (-4) vcld, make_new_child (line: 595) >> |8053|44:44|image| (-5) vcld, main (line: 342) >> |8053|44:44|image| WARNING >> |8053|44:44|image| 2012-07-02 >> 09:32:16|8053|44:44|image|VMware.pm:capture(486)|failed to complete OS >> module's pre_capture tasks >> |8053|44:44|image| ( 0) utils.pm, notify (line: 630) >> |8053|44:44|image| (-1) VMware.pm, capture (line: 486) >> |8053|44:44|image| (-2) image.pm, process (line: 165) >> |8053|44:44|image| (-3) vcld, make_new_child (line: 595) >> |8053|44:44|image| (-4) vcld, main (line: 342) >> |8053|44:44|image| WARNING >> |8053|44:44|image| 2012-07-02 >> 09:32:16|8053|44:44|image|image.pm:process(169)|vmwarewin7-lab0545-v0 image >> failed to be captured by provisioning module >> |8053|44:44|image| ( 0) utils.pm, notify (line: 630) >> |8053|44:44|image| (-1) image.pm, process (line: 169) >> |8053|44:44|image| (-2) vcld, make_new_child (line: 595) >> |8053|44:44|image| (-3) vcld, main (line: 342) >> 2012-07-02 09:32:16|8053|44:44|image|utils.pm:mail(1247)|SUCCESS -- Sending >> mail To: dario.zap...@anahuac.mx, PROBLEM -- image.pm >> |8053|44:44|image| CRITICAL >> |8053|44:44|image| 2012-07-02 >> 09:32:16|8053|44:44|image|image.pm:reservation_failed(393)|vmwarewin7-lab0545-v0 >> image creation failed >> |8053|44:44|image| ( 0) utils.pm, notify (line: 630) >> |8053|44:44|image| (-1) image.pm, reservation_failed (line: 393) >> |8053|44:44|image| (-2) image.pm, process (line: 170) >> |8053|44:44|image| (-3) vcld, make_new_child (line: 595) >> |8053|44:44|image| (-4) vcld, main (line: 342) >> 2012-07-02 09:32:17|8053|44:44|image|utils.pm:mail(1247)|SUCCESS -- Sending >> mail To: root@localhost, VCL -- NOTICE DELAY Image Creation lab05 >> 2012-07-02 09:32:17|8053|44:44|image|utils.pm:mail(1247)|SUCCESS -- Sending >> mail To: dario.zap...@anahuac.mx, VCL -- NOTICE FAILED Image Creation lab05 >> 2012-07-02 >> 09:32:17|8053|44:44|image|utils.pm:update_request_state(2049)|request 44 >> state updated to: maintenance, laststate to: image >> 2012-07-02 >> 09:32:17|8053|44:44|image|image.pm:reservation_failed(445)|request state set >> to maintenance, laststate to image >> 2012-07-02 >> 09:32:17|8053|44:44|image
Re: Problem to create Base Image - VCL 2.2
Hmm... I'm not sure why it fails when cannot locate any drivers (.inf files). I checked mine Windows VMs and they don't have anything under c:/cygwin/home/root/VCL/Drivers folder and yet I was able to capture the image. May be someone else has an idea. Thanks. On Jul 2, 2012, at 11:40 , Zapata Vivas Darío wrote: > Dmitri > > Thanks, I corrected the problem with language. Now I have the next error > logs: > > 2012-07-02 > 09:32:13|8053|44:44|image|Windows.pm:get_driver_inf_paths(8726)|attempting to > locate driver .inf paths matching any class > 2012-07-02 09:32:13|8053|44:44|image|utils.pm:run_ssh_command(5442)|executing > SSH command on lab-template1: > |8053|44:44|image| /usr/bin/ssh -i /etc/vcl/vcl.key -l root -p 22 -x > lab-template1 '/usr/bin/grep.exe -Eirl --include="*.[iI][nN][fF]" ".*" > C:/Cygwin/home/root/VCL/Drivers' 2>&1 > 2012-07-02 > 09:32:16|8053|44:44|image|Windows.pm:get_driver_inf_paths(8750)|found 0 > driver .inf paths, grep output: > |8053|44:44|image| WARNING > |8053|44:44|image| 2012-07-02 > 09:32:16|8053|44:44|image|Windows.pm:set_device_path_key(8794)|failed to > locate driver .inf paths > |8053|44:44|image| ( 0) utils.pm, notify (line: 630) > |8053|44:44|image| (-1) Windows.pm, set_device_path_key (line: 8794) > |8053|44:44|image| (-2) Windows.pm, prepare_post_load (line: 3490) > |8053|44:44|image| (-3) 7.pm, pre_capture (line: 177) > |8053|44:44|image| (-4) VMware.pm, capture (line: 485) > |8053|44:44|image| (-5) image.pm, process (line: 165) > |8053|44:44|image| (-6) vcld, make_new_child (line: 595) > |8053|44:44|image| WARNING > |8053|44:44|image| 2012-07-02 > 09:32:16|8053|44:44|image|Windows.pm:prepare_post_load(3491)|failed to set > the DevicePath registry key > |8053|44:44|image| ( 0) utils.pm, notify (line: 630) > |8053|44:44|image| (-1) Windows.pm, prepare_post_load (line: 3491) > |8053|44:44|image| (-2) 7.pm, pre_capture (line: 177) > |8053|44:44|image| (-3) VMware.pm, capture (line: 485) > |8053|44:44|image| (-4) image.pm, process (line: 165) > |8053|44:44|image| (-5) vcld, make_new_child (line: 595) > |8053|44:44|image| (-6) vcld, main (line: 342) > |8053|44:44|image| WARNING > |8053|44:44|image| 2012-07-02 > 09:32:16|8053|44:44|image|7.pm:pre_capture(178)|capture preparation failed, > failed to run prepare post_load > |8053|44:44|image| ( 0) utils.pm, notify (line: 630) > |8053|44:44|image| (-1) 7.pm, pre_capture (line: 178) > |8053|44:44|image| (-2) VMware.pm, capture (line: 485) > |8053|44:44|image| (-3) image.pm, process (line: 165) > |8053|44:44|image| (-4) vcld, make_new_child (line: 595) > |8053|44:44|image| (-5) vcld, main (line: 342) > |8053|44:44|image| WARNING > |8053|44:44|image| 2012-07-02 > 09:32:16|8053|44:44|image|VMware.pm:capture(486)|failed to complete OS > module's pre_capture tasks > |8053|44:44|image| ( 0) utils.pm, notify (line: 630) > |8053|44:44|image| (-1) VMware.pm, capture (line: 486) > |8053|44:44|image| (-2) image.pm, process (line: 165) > |8053|44:44|image| (-3) vcld, make_new_child (line: 595) > |8053|44:44|image| (-4) vcld, main (line: 342) > |8053|44:44|image| WARNING > |8053|44:44|image| 2012-07-02 > 09:32:16|8053|44:44|image|image.pm:process(169)|vmwarewin7-lab0545-v0 image > failed to be captured by provisioning module > |8053|44:44|image| ( 0) utils.pm, notify (line: 630) > |8053|44:44|image| (-1) image.pm, process (line: 169) > |8053|44:44|image| (-2) vcld, make_new_child (line: 595) > |8053|44:44|image| (-3) vcld, main (line: 342) > 2012-07-02 09:32:16|8053|44:44|image|utils.pm:mail(1247)|SUCCESS -- Sending > mail To: dario.zap...@anahuac.mx, PROBLEM -- image.pm > |8053|44:44|image| CRITICAL > |8053|44:44|image| 2012-07-02 > 09:32:16|8053|44:44|image|image.pm:reservation_failed(393)|vmwarewin7-lab0545-v0 > image creation failed > |8053|44:44|image| ( 0) utils.pm, notify (line: 630) > |8053|44:44|image| (-1) image.pm, reservation_failed (line: 393) > |8053|44:44|image| (-2) image.pm, process (line: 170) > |8053|44:44|image| (-3) vcld, make_new_child (line: 595) > |8053|44:44|image| (-4) vcld, main (line: 342) > 2012-07-02 09:32:17|8053|44:44|image|utils.pm:mail(1247)|SUCCESS -- Sending > mail To: root@localhost, VCL -- NOTICE DELAY Image Creation lab05 > 2012-07-02 09:32:17|8053|44:44|image|utils.pm:mail(1247)|SUCCESS -- Sending > mail To: dario.zap...@anahuac.mx, VCL -- NOTICE FAILED Image Creation lab05 > 2012-07-02 > 09:32:17|8053|44:44|image|utils.pm:update_request_state(2049)|request 44 > state updated to: maintenance, laststate to: image > 2012-07-02 09:32:17|8053|44:44|image|image.pm:reservation_failed(445)|request > state set to maintenance, laststate to image > 2012-07-02 > 09:32:17|8053|44:44|image|utils.pm:update_computer_state(2091)|computer 9 > state updated to: maintenance > 2012-07-02 > 09:32:17|8053|44:44|image|image.pm:reservation_failed(453)|lab-template1 > state set to maintenance > 2012-07-02 09:32:17|8053|44:
