Re: xp image power on fail
I've updated the VCL-130 JIRA ticket with the following: The solution to be implemented in the esx.pm module is a check to see if a virtual machine's RAM = 0. If it is then return a friendly, but critical error message. This should solve the user confusion problem, and the provisioning engine doesn't try to compensate for misconfiguration in other areas of the system. Best, Brian Brian Bouterse Secure Open Systems Initiative 919.698.8796 On Apr 9, 2009, at 3:52 PM, Aaron Peeler wrote: I sort of disagree, but can understand your view point. My viewpoint is from user complaints and tracing through logs as to why their image didn't load. So it was easier to sanity check the image creator(the user) input values instead of pointing out to users, why their image broke. Maybe the web front end for the image profile does not except '0' or allow below a certain value? I think some level of sanity checking is needed somewhere. -A --On April 9, 2009 3:25:14 PM -0400 Andrew Brown wrote: I agree. Ideally, I like to keep systems as generalized as possible, and that means not doing anything unnecessary and not making any unnecessary assumptions. One such assumption being that there is some kind of minimum ram amount for images that VCL supports. A ram size of 0 is obviously an error, so I wouldn't be against a check for 0 values and failing in that case... but the system already does just that, it's just vmware that does the check, not VCL. -Andrew On Thu, Apr 9, 2009 at 3:17 PM, Brian Bouterse wrote: If an installation's configuration (in this case the RAM metadata for an image) isn't properly setup, should the provisioning system compensate for that? I submit to the community that a provisioning engine should take the values handed to it, provision them, and that is all. If the values handed to the provisioning engine don't make sense (like a ram size of 0) then the provisioning engine should cause an error. What do you think? Best, Brian Brian Bouterse Secure Open Systems Initiative 919.698.8796 On Apr 9, 2009, at 1:01 PM, Aaron Peeler wrote: Also that might be an improvement for the esx.pm to set the default to 512MB if it's less than 512. Created JIRA issue VCL-130 < https://issues.apache.org/jira/browse/VCL-130> here's the snippet from the vmware.pm module. It's not perfect(doesn't account for assigning too much ram) but it might help: # check for memory settings my $dynamicmemvalue = "512"; if (defined($vmclient_imageminram)) { # preform some sanity check if (($dynamicmemvalue < $vmclient_imageminram) && ($vmclient_imageminram < $vmhost_RAM)) { $dynamicmemvalue = $vmclient_imageminram; notify($ERRORS{'OK'}, 0, "setting memory to $dynamicmemvalue"); } else { notify($ERRORS{'WARNING'}, 0, "image memory value $vmclient_imageminram out of the expected range in host machine $vmhost_RAM setting to 512"); } } --On April 9, 2009 12:41:33 PM -0400 Wayne Schildhauer < wschi...@linux.vnet.ibm.com> wrote: I found it. The image data in the database had 0 instead of 512. It seems like we looked at everything but the most obvious Wayne F. Schildhauer IBM Corporation Research Triangle Park, NC - Original Message - From: "Wayne Schildhauer" To: "vcl-dev" Sent: Wednesday, 08 April, 2009 18:22 Subject: xp image power on fail I am sorry for the naive question to come, but we figured out why our Windows XPs VMs are not powering on. In the deployed vmx file on ESXi, esx3-windowsxp-v0.vmx, memsize = 0: !/usr/bin/vmware config.version = "8" virtualHW.version = "4" memsize = "0" displayName = "windowsxp-bl1" guestOS = "other" This causes VMware ESXi to panic the VM with an ASSERT failure. Our master configuration file shows it being 512 MB (memsize = "512"), and the slots appear to be configured for 512 MB as well. I suspect that memsize is not getting initialized, rather than overwritten, but I cannot trace where the object that is being given to esx.pm is originally generated. Perhaps in the reservation? ThanksWayne Aaron Peeler OIT Advanced Computing College of Engineering-NCSU 919.513.4571 http://vcl.ncsu.edu Aaron Peeler OIT Advanced Computing College of Engineering-NCSU 919.513.4571 http://vcl.ncsu.edu
Re: xp image power on fail
I sort of disagree, but can understand your view point. My viewpoint is from user complaints and tracing through logs as to why their image didn't load. So it was easier to sanity check the image creator(the user) input values instead of pointing out to users, why their image broke. Maybe the web front end for the image profile does not except '0' or allow below a certain value? I think some level of sanity checking is needed somewhere. -A --On April 9, 2009 3:25:14 PM -0400 Andrew Brown wrote: I agree. Ideally, I like to keep systems as generalized as possible, and that means not doing anything unnecessary and not making any unnecessary assumptions. One such assumption being that there is some kind of minimum ram amount for images that VCL supports. A ram size of 0 is obviously an error, so I wouldn't be against a check for 0 values and failing in that case... but the system already does just that, it's just vmware that does the check, not VCL. -Andrew On Thu, Apr 9, 2009 at 3:17 PM, Brian Bouterse wrote: If an installation's configuration (in this case the RAM metadata for an image) isn't properly setup, should the provisioning system compensate for that? I submit to the community that a provisioning engine should take the values handed to it, provision them, and that is all. If the values handed to the provisioning engine don't make sense (like a ram size of 0) then the provisioning engine should cause an error. What do you think? Best, Brian Brian Bouterse Secure Open Systems Initiative 919.698.8796 On Apr 9, 2009, at 1:01 PM, Aaron Peeler wrote: Also that might be an improvement for the esx.pm to set the default to 512MB if it's less than 512. Created JIRA issue VCL-130 < https://issues.apache.org/jira/browse/VCL-130> here's the snippet from the vmware.pm module. It's not perfect(doesn't account for assigning too much ram) but it might help: # check for memory settings my $dynamicmemvalue = "512"; if (defined($vmclient_imageminram)) { # preform some sanity check if (($dynamicmemvalue < $vmclient_imageminram) && ($vmclient_imageminram < $vmhost_RAM)) { $dynamicmemvalue = $vmclient_imageminram; notify($ERRORS{'OK'}, 0, "setting memory to $dynamicmemvalue"); } else { notify($ERRORS{'WARNING'}, 0, "image memory value $vmclient_imageminram out of the expected range in host machine $vmhost_RAM setting to 512"); } } --On April 9, 2009 12:41:33 PM -0400 Wayne Schildhauer < wschi...@linux.vnet.ibm.com> wrote: I found it. The image data in the database had 0 instead of 512. It seems like we looked at everything but the most obvious Wayne F. Schildhauer IBM Corporation Research Triangle Park, NC - Original Message - From: "Wayne Schildhauer" To: "vcl-dev" Sent: Wednesday, 08 April, 2009 18:22 Subject: xp image power on fail I am sorry for the naive question to come, but we figured out why our Windows XPs VMs are not powering on. In the deployed vmx file on ESXi, esx3-windowsxp-v0.vmx, memsize = 0: !/usr/bin/vmware config.version = "8" virtualHW.version = "4" memsize = "0" displayName = "windowsxp-bl1" guestOS = "other" This causes VMware ESXi to panic the VM with an ASSERT failure. Our master configuration file shows it being 512 MB (memsize = "512"), and the slots appear to be configured for 512 MB as well. I suspect that memsize is not getting initialized, rather than overwritten, but I cannot trace where the object that is being given to esx.pm is originally generated. Perhaps in the reservation? ThanksWayne Aaron Peeler OIT Advanced Computing College of Engineering-NCSU 919.513.4571 http://vcl.ncsu.edu Aaron Peeler OIT Advanced Computing College of Engineering-NCSU 919.513.4571 http://vcl.ncsu.edu
Re: xp image power on fail
I agree. Ideally, I like to keep systems as generalized as possible, and that means not doing anything unnecessary and not making any unnecessary assumptions. One such assumption being that there is some kind of minimum ram amount for images that VCL supports. A ram size of 0 is obviously an error, so I wouldn't be against a check for 0 values and failing in that case... but the system already does just that, it's just vmware that does the check, not VCL. -Andrew On Thu, Apr 9, 2009 at 3:17 PM, Brian Bouterse wrote: > If an installation's configuration (in this case the RAM metadata for an > image) isn't properly setup, should the provisioning system compensate for > that? I submit to the community that a provisioning engine should take the > values handed to it, provision them, and that is all. If the values handed > to the provisioning engine don't make sense (like a ram size of 0) then the > provisioning engine should cause an error. What do you think? > > Best, > Brian > > Brian Bouterse > Secure Open Systems Initiative > 919.698.8796 > > > > > > On Apr 9, 2009, at 1:01 PM, Aaron Peeler wrote: > > Also that might be an improvement for the esx.pm to set the default to >> 512MB if it's less than 512. Created JIRA issue VCL-130 < >> https://issues.apache.org/jira/browse/VCL-130> >> >> here's the snippet from the vmware.pm module. It's not perfect(doesn't >> account for assigning too much ram) but it might help: >> >> #check for memory settings >> my $dynamicmemvalue = "512"; >> if (defined($vmclient_imageminram)) { >>#preform some sanity check >>if (($dynamicmemvalue < $vmclient_imageminram) && >> ($vmclient_imageminram < $vmhost_RAM)) { >>$dynamicmemvalue = $vmclient_imageminram; >>notify($ERRORS{'OK'}, 0, "setting memory to >> $dynamicmemvalue"); >>} >>else { >>notify($ERRORS{'WARNING'}, 0, "image memory value >> $vmclient_imageminram out of the expected range in host machine $vmhost_RAM >> setting to 512"); >>} >> } >> >> >> >> --On April 9, 2009 12:41:33 PM -0400 Wayne Schildhauer < >> wschi...@linux.vnet.ibm.com> wrote: >> >> I found it. The image data in the database had 0 instead of 512. It >>> seems like we looked at everything but the most obvious >>> >>> Wayne F. Schildhauer >>> IBM Corporation >>> Research Triangle Park, NC >>> >>> - Original Message - From: "Wayne Schildhauer" >>> >>> To: "vcl-dev" >>> Sent: Wednesday, 08 April, 2009 18:22 >>> Subject: xp image power on fail >>> >>> >>> I am sorry for the naive question to come, but we figured out why our >>>> Windows XPs VMs are not powering on. In the deployed vmx file on ESXi, >>>> esx3-windowsxp-v0.vmx, memsize = 0: >>>> >>>> !/usr/bin/vmware >>>> config.version = "8" >>>> virtualHW.version = "4" >>>> memsize = "0" >>>> displayName = "windowsxp-bl1" >>>> guestOS = "other" >>>> >>>> >>>> >>>> This causes VMware ESXi to panic the VM with an ASSERT failure. >>>> >>>> Our master configuration file shows it being 512 MB (memsize = "512"), >>>> and the slots appear to be configured for 512 MB as well. I suspect >>>> that memsize is not getting initialized, rather than overwritten, but I >>>> cannot trace where the object that is being given to esx.pm is >>>> originally generated. Perhaps in the reservation? >>>> >>>> ThanksWayne >>>> >>>> >>> >> >> >> Aaron Peeler >> OIT Advanced Computing >> College of Engineering-NCSU >> 919.513.4571 >> http://vcl.ncsu.edu >> > >
Re: xp image power on fail
If an installation's configuration (in this case the RAM metadata for an image) isn't properly setup, should the provisioning system compensate for that? I submit to the community that a provisioning engine should take the values handed to it, provision them, and that is all. If the values handed to the provisioning engine don't make sense (like a ram size of 0) then the provisioning engine should cause an error. What do you think? Best, Brian Brian Bouterse Secure Open Systems Initiative 919.698.8796 On Apr 9, 2009, at 1:01 PM, Aaron Peeler wrote: Also that might be an improvement for the esx.pm to set the default to 512MB if it's less than 512. Created JIRA issue VCL-130 <https://issues.apache.org/jira/browse/VCL-130 > here's the snippet from the vmware.pm module. It's not perfect(doesn't account for assigning too much ram) but it might help: #check for memory settings my $dynamicmemvalue = "512"; if (defined($vmclient_imageminram)) { #preform some sanity check if (($dynamicmemvalue < $vmclient_imageminram) && ($vmclient_imageminram < $vmhost_RAM)) { $dynamicmemvalue = $vmclient_imageminram; notify($ERRORS{'OK'}, 0, "setting memory to $dynamicmemvalue"); } else { notify($ERRORS{'WARNING'}, 0, "image memory value $vmclient_imageminram out of the expected range in host machine $vmhost_RAM setting to 512"); } } --On April 9, 2009 12:41:33 PM -0400 Wayne Schildhauer > wrote: I found it. The image data in the database had 0 instead of 512. It seems like we looked at everything but the most obvious Wayne F. Schildhauer IBM Corporation Research Triangle Park, NC - Original Message ----- From: "Wayne Schildhauer" To: "vcl-dev" Sent: Wednesday, 08 April, 2009 18:22 Subject: xp image power on fail I am sorry for the naive question to come, but we figured out why our Windows XPs VMs are not powering on. In the deployed vmx file on ESXi, esx3-windowsxp-v0.vmx, memsize = 0: !/usr/bin/vmware config.version = "8" virtualHW.version = "4" memsize = "0" displayName = "windowsxp-bl1" guestOS = "other" This causes VMware ESXi to panic the VM with an ASSERT failure. Our master configuration file shows it being 512 MB (memsize = "512"), and the slots appear to be configured for 512 MB as well. I suspect that memsize is not getting initialized, rather than overwritten, but I cannot trace where the object that is being given to esx.pm is originally generated. Perhaps in the reservation? ThanksWayne Aaron Peeler OIT Advanced Computing College of Engineering-NCSU 919.513.4571 http://vcl.ncsu.edu
Re: xp image power on fail
Yes - dynamically configured slots is on the roadmap - somewhere... :) Since the vmx file is being built at load time, the place holder is there. Just need to fill in the part where the provisioning modules analyzes the available capacity of the hypervisor server, the image profile needs, and maybe even the requesting user's past usage of requested image(if feasible). -A --On April 9, 2009 2:23:11 PM -0400 Wayne Schildhauer wrote: Thanks Aaron. I have not looked at the code extensively. However, it seems like the slot value would be interesting as well at that point. (You can tell that was the first thing at which we looked.) I am not sure if that could be pulled in or if it is appropriate to do so. Having said that, I hope pre-configured slots go away at some point. :-) Wayne F. Schildhauer IBM Corporation Research Triangle Park, NC - Original Message - From: "Aaron Peeler" To: Sent: Thursday, 09 April, 2009 13:01 Subject: Re: xp image power on fail Also that might be an improvement for the esx.pm to set the default to 512MB if it's less than 512. Created JIRA issue VCL-130 <https://issues.apache.org/jira/browse/VCL-130> here's the snippet from the vmware.pm module. It's not perfect(doesn't account for assigning too much ram) but it might help: # check for memory settings my $dynamicmemvalue = "512"; if (defined($vmclient_imageminram)) { # preform some sanity check if (($dynamicmemvalue < $vmclient_imageminram) && ($vmclient_imageminram < $vmhost_RAM)) { $dynamicmemvalue = $vmclient_imageminram; notify($ERRORS{'OK'}, 0, "setting memory to $dynamicmemvalue"); } else { notify($ERRORS{'WARNING'}, 0, "image memory value $vmclient_imageminram out of the expected range in host machine $vmhost_RAM setting to 512"); } } --On April 9, 2009 12:41:33 PM -0400 Wayne Schildhauer wrote: I found it. The image data in the database had 0 instead of 512. It seems like we looked at everything but the most obvious Wayne F. Schildhauer IBM Corporation Research Triangle Park, NC - Original Message - From: "Wayne Schildhauer" To: "vcl-dev" Sent: Wednesday, 08 April, 2009 18:22 Subject: xp image power on fail I am sorry for the naive question to come, but we figured out why our Windows XPs VMs are not powering on. In the deployed vmx file on ESXi, esx3-windowsxp-v0.vmx, memsize = 0: !/usr/bin/vmware config.version = "8" virtualHW.version = "4" memsize = "0" displayName = "windowsxp-bl1" guestOS = "other" This causes VMware ESXi to panic the VM with an ASSERT failure. Our master configuration file shows it being 512 MB (memsize = "512"), and the slots appear to be configured for 512 MB as well. I suspect that memsize is not getting initialized, rather than overwritten, but I cannot trace where the object that is being given to esx.pm is originally generated. Perhaps in the reservation? ThanksWayne Aaron Peeler OIT Advanced Computing College of Engineering-NCSU 919.513.4571 http://vcl.ncsu.edu Aaron Peeler OIT Advanced Computing College of Engineering-NCSU 919.513.4571 http://vcl.ncsu.edu
Re: xp image power on fail
Thanks Aaron. I have not looked at the code extensively. However, it seems like the slot value would be interesting as well at that point. (You can tell that was the first thing at which we looked.) I am not sure if that could be pulled in or if it is appropriate to do so. Having said that, I hope pre-configured slots go away at some point. :-) Wayne F. Schildhauer IBM Corporation Research Triangle Park, NC - Original Message - From: "Aaron Peeler" To: Sent: Thursday, 09 April, 2009 13:01 Subject: Re: xp image power on fail Also that might be an improvement for the esx.pm to set the default to 512MB if it's less than 512. Created JIRA issue VCL-130 <https://issues.apache.org/jira/browse/VCL-130> here's the snippet from the vmware.pm module. It's not perfect(doesn't account for assigning too much ram) but it might help: #check for memory settings my $dynamicmemvalue = "512"; if (defined($vmclient_imageminram)) { #preform some sanity check if (($dynamicmemvalue < $vmclient_imageminram) && ($vmclient_imageminram < $vmhost_RAM)) { $dynamicmemvalue = $vmclient_imageminram; notify($ERRORS{'OK'}, 0, "setting memory to $dynamicmemvalue"); } else { notify($ERRORS{'WARNING'}, 0, "image memory value $vmclient_imageminram out of the expected range in host machine $vmhost_RAM setting to 512"); } } --On April 9, 2009 12:41:33 PM -0400 Wayne Schildhauer wrote: I found it. The image data in the database had 0 instead of 512. It seems like we looked at everything but the most obvious Wayne F. Schildhauer IBM Corporation Research Triangle Park, NC - Original Message ----- From: "Wayne Schildhauer" To: "vcl-dev" Sent: Wednesday, 08 April, 2009 18:22 Subject: xp image power on fail I am sorry for the naive question to come, but we figured out why our Windows XPs VMs are not powering on. In the deployed vmx file on ESXi, esx3-windowsxp-v0.vmx, memsize = 0: !/usr/bin/vmware config.version = "8" virtualHW.version = "4" memsize = "0" displayName = "windowsxp-bl1" guestOS = "other" This causes VMware ESXi to panic the VM with an ASSERT failure. Our master configuration file shows it being 512 MB (memsize = "512"), and the slots appear to be configured for 512 MB as well. I suspect that memsize is not getting initialized, rather than overwritten, but I cannot trace where the object that is being given to esx.pm is originally generated. Perhaps in the reservation? ThanksWayne Aaron Peeler OIT Advanced Computing College of Engineering-NCSU 919.513.4571 http://vcl.ncsu.edu
Re: xp image power on fail
Also that might be an improvement for the esx.pm to set the default to 512MB if it's less than 512. Created JIRA issue VCL-130 <https://issues.apache.org/jira/browse/VCL-130> here's the snippet from the vmware.pm module. It's not perfect(doesn't account for assigning too much ram) but it might help: #check for memory settings my $dynamicmemvalue = "512"; if (defined($vmclient_imageminram)) { #preform some sanity check if (($dynamicmemvalue < $vmclient_imageminram) && ($vmclient_imageminram < $vmhost_RAM)) { $dynamicmemvalue = $vmclient_imageminram; notify($ERRORS{'OK'}, 0, "setting memory to $dynamicmemvalue"); } else { notify($ERRORS{'WARNING'}, 0, "image memory value $vmclient_imageminram out of the expected range in host machine $vmhost_RAM setting to 512"); } } --On April 9, 2009 12:41:33 PM -0400 Wayne Schildhauer wrote: I found it. The image data in the database had 0 instead of 512. It seems like we looked at everything but the most obvious Wayne F. Schildhauer IBM Corporation Research Triangle Park, NC - Original Message - From: "Wayne Schildhauer" To: "vcl-dev" Sent: Wednesday, 08 April, 2009 18:22 Subject: xp image power on fail I am sorry for the naive question to come, but we figured out why our Windows XPs VMs are not powering on. In the deployed vmx file on ESXi, esx3-windowsxp-v0.vmx, memsize = 0: !/usr/bin/vmware config.version = "8" virtualHW.version = "4" memsize = "0" displayName = "windowsxp-bl1" guestOS = "other" This causes VMware ESXi to panic the VM with an ASSERT failure. Our master configuration file shows it being 512 MB (memsize = "512"), and the slots appear to be configured for 512 MB as well. I suspect that memsize is not getting initialized, rather than overwritten, but I cannot trace where the object that is being given to esx.pm is originally generated. Perhaps in the reservation? ThanksWayne Aaron Peeler OIT Advanced Computing College of Engineering-NCSU 919.513.4571 http://vcl.ncsu.edu
Re: xp image power on fail
I found it. The image data in the database had 0 instead of 512. It seems like we looked at everything but the most obvious Wayne F. Schildhauer IBM Corporation Research Triangle Park, NC - Original Message - From: "Wayne Schildhauer" To: "vcl-dev" Sent: Wednesday, 08 April, 2009 18:22 Subject: xp image power on fail I am sorry for the naive question to come, but we figured out why our Windows XPs VMs are not powering on. In the deployed vmx file on ESXi, esx3-windowsxp-v0.vmx, memsize = 0: !/usr/bin/vmware config.version = "8" virtualHW.version = "4" memsize = "0" displayName = "windowsxp-bl1" guestOS = "other" This causes VMware ESXi to panic the VM with an ASSERT failure. Our master configuration file shows it being 512 MB (memsize = "512"), and the slots appear to be configured for 512 MB as well. I suspect that memsize is not getting initialized, rather than overwritten, but I cannot trace where the object that is being given to esx.pm is originally generated. Perhaps in the reservation? ThanksWayne
xp image power on fail
I am sorry for the naive question to come, but we figured out why our Windows XPs VMs are not powering on. In the deployed vmx file on ESXi, esx3-windowsxp-v0.vmx, memsize = 0: !/usr/bin/vmware config.version = "8" virtualHW.version = "4" memsize = "0" displayName = "windowsxp-bl1" guestOS = "other" This causes VMware ESXi to panic the VM with an ASSERT failure. Our master configuration file shows it being 512 MB (memsize = "512"), and the slots appear to be configured for 512 MB as well. I suspect that memsize is not getting initialized, rather than overwritten, but I cannot trace where the object that is being given to esx.pm is originally generated. Perhaps in the reservation? ThanksWayne
Re: xp image power on fail
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 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 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 Lo
Re: xp image power on fail
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 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 >> milo...@gmail.com >> > > -- Melba Lopez milo...@gmail.com
Re: xp image power on fail
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 milo...@gmail.com
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 milo...@gmail.com