You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@vcl.apache.org by Melba Lopez <mi...@gmail.com> on 2009/04/06 22:16:51 UTC
xp image power on fail
When trying to reserve a newly created xp image, it is unable to power on.
Going through the logs, I notice a warning of /etc/vcl/winxp_blade.key file
missing. The instructions on the wiki do not specify this file anywhere and
was curious if it should. Is there something I missed in imaging this xp
image?
Here is the log:
Warning: Identity file /etc/vcl/winxp_blade.key not accessible: No such file
or directory.
2009-04-07 00:04:46|31614|vcld:main(166)|lastcheckin time updated for
management node 1: 2009-04-07 00:04:46
2009-04-07 00:04:58|31614|vcld:main(166)|lastcheckin time updated for
management node 1: 2009-04-07 00:04:58
2009-04-07 00:05:10|31614|vcld:main(166)|lastcheckin time updated for
management node 1: 2009-04-07 00:05:10
2009-04-07 00:05:22|31614|vcld:main(166)|lastcheckin time updated for
management node 1: 2009-04-07 00:05:22
2009-04-07 00:05:34|31614|vcld:main(166)|lastcheckin time updated for
management node 1: 2009-04-07 00:05:34
2009-04-07 00:05:46|16674|166:33|new|vcld:REAPER(770)|setting $? to 0, exit
status: 0
2009-04-07 00:05:46|16674|166:33|new|vcld:REAPER(770)|setting $? to 0, exit
status: 0
2009-04-07 00:05:46|16674|166:33|new|esx.pm:load(258)|adapter= buslogic
2009-04-07 00:05:46|31614|vcld:main(166)|lastcheckin time updated for
management node 1: 2009-04-07 00:05:46
2009-04-07 00:05:46|16674|166:33|new|esx.pm:load(300)|wrote vmxarray to
/mnt/vcl/inuse/windowsxp-bl2/esx3-windowsxp-v0.vmx
2009-04-07 00:05:49|16674|166:33|new|vcld:REAPER(770)|setting $? to 0, exit
status: 0
2009-04-07 00:05:49|16674|166:33|new|esx.pm:load(321)|Registered:
|16674|166:33|new| Register of VM 'windowsxp-bl2' successfully completed
under host esxibl2.preloads.private
2009-04-07 00:05:49|16674|166:33|new|esx.pm:load(330)|Power on command:
/usr/lib/vmware-viperl/apps/vm/vmcontrol.pl --server
'esxibl2.preloads.private' --vmname windowsxp-bl2 --operation poweron
--username vcl --password 'd834jfhd734jgfhf7'
2009-04-07 00:05:58|31614|vcld:main(166)|lastcheckin time updated for
management node 1: 2009-04-07 00:05:58
2009-04-07 00:05:59|16674|166:33|new|vcld:REAPER(770)|setting $? to 0, exit
status: 0
2009-04-07 00:05:59|16674|166:33|new|esx.pm:load(333)|Powered on: VM
'windowsxp-bl2' can't be powered on
|16674|166:33|new| SOAP Fault:
|16674|166:33|new| -----------
|16674|166:33|new| Fault string: The attempted operation cannot be performed
in the current state (Powered Off).
|16674|166:33|new| Fault detail: InvalidPowerState=HASH(0xb46f78c)
2009-04-07 00:06:00|16674|166:33|new|esx.pm:load(349)|deviceinfo->summary:
VirtualPCNet32=HASH(0xd3e705c)->deviceinfo->summary
2009-04-07 00:06:00|16674|166:33|new|esx.pm:load(350)|virtualswitch0:
Management
2009-04-07 00:06:00|16674|166:33|new|esx.pm:load(349)|deviceinfo->summary:
VirtualPCNet32=HASH(0xd388abc)->deviceinfo->summary
2009-04-07 00:06:00|16674|166:33|new|esx.pm:load(350)|virtualswitch0:
Management
2009-04-07 00:06:00|16674|166:33|new|vcld:REAPER(770)|setting $? to 0, exit
status: 0
2009-04-07 00:06:10|31614|vcld:main(166)|lastcheckin time updated for
management node 1: 2009-04-07 00:06:10
--
Melba Lopez
milopez@gmail.com
Re: xp image power on fail
Posted by Aaron Peeler <aa...@ncsu.edu>.
It doesn't need to be a soft link - I think Brian was just describing what
he did. You can list any readable path in the those variables in vcld.conf
The documentation is still a work in progress - we are far from done on
this part.
Some things that are changing with regards to the vcld.conf. The goal is to
move the majority of the variables to the management node table.
Currently you can populate the 'keys' field of the management node table
with the full path of where the key is.
Aaron
--On April 7, 2009 9:45:20 AM -0400 Melba Lopez <mi...@gmail.com> wrote:
> Hi Brian,
> Was this soft link supposed to exist beforehand? if not, should the wiki
> state to do this step? I created a soft link like you suggested and it
> fixed that "missing file" error I was seeing, but the vm still won't
> power on after deployment.
>
>
> On Tue, Apr 7, 2009 at 9:00 AM, Brian Bouterse <bm...@ncsu.edu> wrote:
>
>> I haven't gotten windows working with the esx.pm provisioning engine
>> either, but here are a few things to consider. Do you have a
>> public/private key pair in your /etc/vcl/ directory?
>>
>> VCL Keys are configured in vcld.conf with lines that look like these:
>>
>> IDENTITY_blade_linux=/etc/vcl/bladelinuxkey_id_rsa
>> IDENTITY_solaris_lab=/etc/vcl/solaris_lab.key
>> IDENTITY_linux_lab=/etc/vcl/linux_lab.key
>> IDENTITY_blade_win=/etc/vcl/winxp_blade.key
>>
>> Usually in my installations I create symbolic links in the /etc/vcl/
>> directory for things like winxp_blade.key pointing to the
>> /root/.ssh/id_rsa If you did such a thing for winxp_blade.key, the
>> public key corresponding to /root/.ssh/id_rsa needs to be placed in the
>> windows vm in your cygwin area which provides windows with SSH. If the
>> private key is named id_rsa, usually the public key is in the same
>> directory and named id_rsa.pub
>>
>> Best,
>> Brian
>>
>>
>> Brian Bouterse
>> Secure Open Systems Initiative
>> 919.698.8796
>>
>>
>>
>>
>>
>> On Apr 6, 2009, at 4:16 PM, Melba Lopez wrote:
>>
>> When trying to reserve a newly created xp image, it is unable to power
>> on.
>>> Going through the logs, I notice a warning of /etc/vcl/winxp_blade.key
>>> file
>>> missing. The instructions on the wiki do not specify this file anywhere
>>> and
>>> was curious if it should. Is there something I missed in imaging this
>>> xp image?
>>>
>>> Here is the log:
>>>
>>> Warning: Identity file /etc/vcl/winxp_blade.key not accessible: No such
>>> file
>>> or directory.
>>> 2009-04-07 00:04:46|31614|vcld:main(166)|lastcheckin time updated for
>>> management node 1: 2009-04-07 00:04:46
>>> 2009-04-07 00:04:58|31614|vcld:main(166)|lastcheckin time updated for
>>> management node 1: 2009-04-07 00:04:58
>>> 2009-04-07 00:05:10|31614|vcld:main(166)|lastcheckin time updated for
>>> management node 1: 2009-04-07 00:05:10
>>> 2009-04-07 00:05:22|31614|vcld:main(166)|lastcheckin time updated for
>>> management node 1: 2009-04-07 00:05:22
>>> 2009-04-07 00:05:34|31614|vcld:main(166)|lastcheckin time updated for
>>> management node 1: 2009-04-07 00:05:34
>>> 2009-04-07 00:05:46|16674|166:33|new|vcld:REAPER(770)|setting $? to 0,
>>> exit
>>> status: 0
>>> 2009-04-07 00:05:46|16674|166:33|new|vcld:REAPER(770)|setting $? to 0,
>>> exit
>>> status: 0
>>> 2009-04-07 00:05:46|16674|166:33|new|esx.pm:load(258)|adapter= buslogic
>>> 2009-04-07 00:05:46|31614|vcld:main(166)|lastcheckin time updated for
>>> management node 1: 2009-04-07 00:05:46
>>> 2009-04-07 00:05:46|16674|166:33|new|esx.pm:load(300)|wrote vmxarray to
>>> /mnt/vcl/inuse/windowsxp-bl2/esx3-windowsxp-v0.vmx
>>> 2009-04-07 00:05:49|16674|166:33|new|vcld:REAPER(770)|setting $? to 0,
>>> exit
>>> status: 0
>>> 2009-04-07 00:05:49|16674|166:33|new|esx.pm:load(321)|Registered:
>>> | 16674|166:33|new| Register of VM 'windowsxp-bl2' successfully
>>> | completed
>>> under host esxibl2.preloads.private
>>> 2009-04-07 00:05:49|16674|166:33|new|esx.pm:load(330)|Power on command:
>>> /usr/lib/vmware-viperl/apps/vm/vmcontrol.pl --server
>>> 'esxibl2.preloads.private' --vmname windowsxp-bl2 --operation poweron
>>> --username vcl --password 'd834jfhd734jgfhf7'
>>> 2009-04-07 00:05:58|31614|vcld:main(166)|lastcheckin time updated for
>>> management node 1: 2009-04-07 00:05:58
>>> 2009-04-07 00:05:59|16674|166:33|new|vcld:REAPER(770)|setting $? to 0,
>>> exit
>>> status: 0
>>> 2009-04-07 00:05:59|16674|166:33|new|esx.pm:load(333)|Powered on: VM
>>> 'windowsxp-bl2' can't be powered on
>>>
>>> | 16674|166:33|new| SOAP Fault:
>>> | 16674|166:33|new| -----------
>>> | 16674|166:33|new| Fault string: The attempted operation cannot be
>>> performed
>>> in the current state (Powered Off).
>>> | 16674|166:33|new| Fault detail: InvalidPowerState=HASH(0xb46f78c)
>>> 2009-04-07 00:06:00|16674|166:33|new|esx.pm:
>>> load(349)|deviceinfo->summary:
>>> VirtualPCNet32=HASH(0xd3e705c)->deviceinfo->summary
>>> 2009-04-07 00:06:00|16674|166:33|new|esx.pm:load(350)|virtualswitch0:
>>> Management
>>> 2009-04-07 00:06:00|16674|166:33|new|esx.pm:
>>> load(349)|deviceinfo->summary:
>>> VirtualPCNet32=HASH(0xd388abc)->deviceinfo->summary
>>> 2009-04-07 00:06:00|16674|166:33|new|esx.pm:load(350)|virtualswitch0:
>>> Management
>>> 2009-04-07 00:06:00|16674|166:33|new|vcld:REAPER(770)|setting $? to 0,
>>> exit
>>> status: 0
>>> 2009-04-07 00:06:10|31614|vcld:main(166)|lastcheckin time updated for
>>> management node 1: 2009-04-07 00:06:10
>>>
>>> --
>>> Melba Lopez
>>> milopez@gmail.com
>>>
>>
>>
Re: xp image power on fail
Posted by Melba Lopez <mi...@gmail.com>.
Hi Brian,
Was this soft link supposed to exist beforehand? if not, should the wiki
state to do this step? I created a soft link like you suggested and it fixed
that "missing file" error I was seeing, but the vm still won't power on
after deployment.
On Tue, Apr 7, 2009 at 9:00 AM, Brian Bouterse <bm...@ncsu.edu> wrote:
> I haven't gotten windows working with the esx.pm provisioning engine
> either, but here are a few things to consider. Do you have a public/private
> key pair in your /etc/vcl/ directory?
>
> VCL Keys are configured in vcld.conf with lines that look like these:
>
> IDENTITY_blade_linux=/etc/vcl/bladelinuxkey_id_rsa
> IDENTITY_solaris_lab=/etc/vcl/solaris_lab.key
> IDENTITY_linux_lab=/etc/vcl/linux_lab.key
> IDENTITY_blade_win=/etc/vcl/winxp_blade.key
>
> Usually in my installations I create symbolic links in the /etc/vcl/
> directory for things like winxp_blade.key pointing to the /root/.ssh/id_rsa
> If you did such a thing for winxp_blade.key, the public key corresponding
> to /root/.ssh/id_rsa needs to be placed in the windows vm in your cygwin
> area which provides windows with SSH. If the private key is named id_rsa,
> usually the public key is in the same directory and named id_rsa.pub
>
> Best,
> Brian
>
>
> Brian Bouterse
> Secure Open Systems Initiative
> 919.698.8796
>
>
>
>
>
> On Apr 6, 2009, at 4:16 PM, Melba Lopez wrote:
>
> When trying to reserve a newly created xp image, it is unable to power on.
>> Going through the logs, I notice a warning of /etc/vcl/winxp_blade.key
>> file
>> missing. The instructions on the wiki do not specify this file anywhere
>> and
>> was curious if it should. Is there something I missed in imaging this xp
>> image?
>>
>> Here is the log:
>>
>> Warning: Identity file /etc/vcl/winxp_blade.key not accessible: No such
>> file
>> or directory.
>> 2009-04-07 00:04:46|31614|vcld:main(166)|lastcheckin time updated for
>> management node 1: 2009-04-07 00:04:46
>> 2009-04-07 00:04:58|31614|vcld:main(166)|lastcheckin time updated for
>> management node 1: 2009-04-07 00:04:58
>> 2009-04-07 00:05:10|31614|vcld:main(166)|lastcheckin time updated for
>> management node 1: 2009-04-07 00:05:10
>> 2009-04-07 00:05:22|31614|vcld:main(166)|lastcheckin time updated for
>> management node 1: 2009-04-07 00:05:22
>> 2009-04-07 00:05:34|31614|vcld:main(166)|lastcheckin time updated for
>> management node 1: 2009-04-07 00:05:34
>> 2009-04-07 00:05:46|16674|166:33|new|vcld:REAPER(770)|setting $? to 0,
>> exit
>> status: 0
>> 2009-04-07 00:05:46|16674|166:33|new|vcld:REAPER(770)|setting $? to 0,
>> exit
>> status: 0
>> 2009-04-07 00:05:46|16674|166:33|new|esx.pm:load(258)|adapter= buslogic
>> 2009-04-07 00:05:46|31614|vcld:main(166)|lastcheckin time updated for
>> management node 1: 2009-04-07 00:05:46
>> 2009-04-07 00:05:46|16674|166:33|new|esx.pm:load(300)|wrote vmxarray to
>> /mnt/vcl/inuse/windowsxp-bl2/esx3-windowsxp-v0.vmx
>> 2009-04-07 00:05:49|16674|166:33|new|vcld:REAPER(770)|setting $? to 0,
>> exit
>> status: 0
>> 2009-04-07 00:05:49|16674|166:33|new|esx.pm:load(321)|Registered:
>> |16674|166:33|new| Register of VM 'windowsxp-bl2' successfully completed
>> under host esxibl2.preloads.private
>> 2009-04-07 00:05:49|16674|166:33|new|esx.pm:load(330)|Power on command:
>> /usr/lib/vmware-viperl/apps/vm/vmcontrol.pl --server
>> 'esxibl2.preloads.private' --vmname windowsxp-bl2 --operation poweron
>> --username vcl --password 'd834jfhd734jgfhf7'
>> 2009-04-07 00:05:58|31614|vcld:main(166)|lastcheckin time updated for
>> management node 1: 2009-04-07 00:05:58
>> 2009-04-07 00:05:59|16674|166:33|new|vcld:REAPER(770)|setting $? to 0,
>> exit
>> status: 0
>> 2009-04-07 00:05:59|16674|166:33|new|esx.pm:load(333)|Powered on: VM
>> 'windowsxp-bl2' can't be powered on
>>
>> |16674|166:33|new| SOAP Fault:
>> |16674|166:33|new| -----------
>> |16674|166:33|new| Fault string: The attempted operation cannot be
>> performed
>> in the current state (Powered Off).
>> |16674|166:33|new| Fault detail: InvalidPowerState=HASH(0xb46f78c)
>> 2009-04-07 00:06:00|16674|166:33|new|esx.pm:
>> load(349)|deviceinfo->summary:
>> VirtualPCNet32=HASH(0xd3e705c)->deviceinfo->summary
>> 2009-04-07 00:06:00|16674|166:33|new|esx.pm:load(350)|virtualswitch0:
>> Management
>> 2009-04-07 00:06:00|16674|166:33|new|esx.pm:
>> load(349)|deviceinfo->summary:
>> VirtualPCNet32=HASH(0xd388abc)->deviceinfo->summary
>> 2009-04-07 00:06:00|16674|166:33|new|esx.pm:load(350)|virtualswitch0:
>> Management
>> 2009-04-07 00:06:00|16674|166:33|new|vcld:REAPER(770)|setting $? to 0,
>> exit
>> status: 0
>> 2009-04-07 00:06:10|31614|vcld:main(166)|lastcheckin time updated for
>> management node 1: 2009-04-07 00:06:10
>>
>> --
>> Melba Lopez
>> milopez@gmail.com
>>
>
>
--
Melba Lopez
milopez@gmail.com
Re: xp image power on fail
Posted by Brian Bouterse <bm...@ncsu.edu>.
I haven't gotten windows working with the esx.pm provisioning engine
either, but here are a few things to consider. Do you have a public/
private key pair in your /etc/vcl/ directory?
VCL Keys are configured in vcld.conf with lines that look like these:
IDENTITY_blade_linux=/etc/vcl/bladelinuxkey_id_rsa
IDENTITY_solaris_lab=/etc/vcl/solaris_lab.key
IDENTITY_linux_lab=/etc/vcl/linux_lab.key
IDENTITY_blade_win=/etc/vcl/winxp_blade.key
Usually in my installations I create symbolic links in the /etc/vcl/
directory for things like winxp_blade.key pointing to the /root/.ssh/
id_rsa If you did such a thing for winxp_blade.key, the public key
corresponding to /root/.ssh/id_rsa needs to be placed in the windows
vm in your cygwin area which provides windows with SSH. If the
private key is named id_rsa, usually the public key is in the same
directory and named id_rsa.pub
Best,
Brian
Brian Bouterse
Secure Open Systems Initiative
919.698.8796
On Apr 6, 2009, at 4:16 PM, Melba Lopez wrote:
> When trying to reserve a newly created xp image, it is unable to
> power on.
> Going through the logs, I notice a warning of /etc/vcl/
> winxp_blade.key file
> missing. The instructions on the wiki do not specify this file
> anywhere and
> was curious if it should. Is there something I missed in imaging
> this xp
> image?
>
> Here is the log:
>
> Warning: Identity file /etc/vcl/winxp_blade.key not accessible: No
> such file
> or directory.
> 2009-04-07 00:04:46|31614|vcld:main(166)|lastcheckin time updated for
> management node 1: 2009-04-07 00:04:46
> 2009-04-07 00:04:58|31614|vcld:main(166)|lastcheckin time updated for
> management node 1: 2009-04-07 00:04:58
> 2009-04-07 00:05:10|31614|vcld:main(166)|lastcheckin time updated for
> management node 1: 2009-04-07 00:05:10
> 2009-04-07 00:05:22|31614|vcld:main(166)|lastcheckin time updated for
> management node 1: 2009-04-07 00:05:22
> 2009-04-07 00:05:34|31614|vcld:main(166)|lastcheckin time updated for
> management node 1: 2009-04-07 00:05:34
> 2009-04-07 00:05:46|16674|166:33|new|vcld:REAPER(770)|setting $? to
> 0, exit
> status: 0
> 2009-04-07 00:05:46|16674|166:33|new|vcld:REAPER(770)|setting $? to
> 0, exit
> status: 0
> 2009-04-07 00:05:46|16674|166:33|new|esx.pm:load(258)|adapter=
> buslogic
> 2009-04-07 00:05:46|31614|vcld:main(166)|lastcheckin time updated for
> management node 1: 2009-04-07 00:05:46
> 2009-04-07 00:05:46|16674|166:33|new|esx.pm:load(300)|wrote vmxarray
> to
> /mnt/vcl/inuse/windowsxp-bl2/esx3-windowsxp-v0.vmx
> 2009-04-07 00:05:49|16674|166:33|new|vcld:REAPER(770)|setting $? to
> 0, exit
> status: 0
> 2009-04-07 00:05:49|16674|166:33|new|esx.pm:load(321)|Registered:
> |16674|166:33|new| Register of VM 'windowsxp-bl2' successfully
> completed
> under host esxibl2.preloads.private
> 2009-04-07 00:05:49|16674|166:33|new|esx.pm:load(330)|Power on
> command:
> /usr/lib/vmware-viperl/apps/vm/vmcontrol.pl --server
> 'esxibl2.preloads.private' --vmname windowsxp-bl2 --operation poweron
> --username vcl --password 'd834jfhd734jgfhf7'
> 2009-04-07 00:05:58|31614|vcld:main(166)|lastcheckin time updated for
> management node 1: 2009-04-07 00:05:58
> 2009-04-07 00:05:59|16674|166:33|new|vcld:REAPER(770)|setting $? to
> 0, exit
> status: 0
> 2009-04-07 00:05:59|16674|166:33|new|esx.pm:load(333)|Powered on: VM
> 'windowsxp-bl2' can't be powered on
>
> |16674|166:33|new| SOAP Fault:
> |16674|166:33|new| -----------
> |16674|166:33|new| Fault string: The attempted operation cannot be
> performed
> in the current state (Powered Off).
> |16674|166:33|new| Fault detail: InvalidPowerState=HASH(0xb46f78c)
> 2009-04-07 00:06:00|16674|166:33|new|esx.pm:load(349)|deviceinfo-
> >summary:
> VirtualPCNet32=HASH(0xd3e705c)->deviceinfo->summary
> 2009-04-07 00:06:00|16674|166:33|new|esx.pm:load(350)|virtualswitch0:
> Management
> 2009-04-07 00:06:00|16674|166:33|new|esx.pm:load(349)|deviceinfo-
> >summary:
> VirtualPCNet32=HASH(0xd388abc)->deviceinfo->summary
> 2009-04-07 00:06:00|16674|166:33|new|esx.pm:load(350)|virtualswitch0:
> Management
> 2009-04-07 00:06:00|16674|166:33|new|vcld:REAPER(770)|setting $? to
> 0, exit
> status: 0
> 2009-04-07 00:06:10|31614|vcld:main(166)|lastcheckin time updated for
> management node 1: 2009-04-07 00:06:10
>
> --
> Melba Lopez
> milopez@gmail.com