You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@vcl.apache.org by Michael Jinks <mj...@uchicago.edu> on 2012/06/14 22:01:03 UTC
next issue, Re: Image capture hitch
On Thu, Jun 14, 2012 at 02:37:40PM -0400, Josh Thompson wrote:
>
> You're hitting a bug in 2.2.1. If you go to Manage Computers->Computer
> Utilities, you can set the VM to the available state successfully.
Thanks. I had looked around a little for another way to do it but
missed that.
Now I'm a little further and hitting a new problem. I can start the
capture process, but the capture process fails. I don't have a
successful instance to compare against, so I'm not sure exactly where
the salient problem is, but I notice this in the log:
[...]
2012-06-14
14:15:57|25286|3:3|image|Module.pm:create_mn_os_object(335)|management
node OS object has already been created, address: 3fc9dc8, returning 1
2012-06-14
14:15:57|25286|3:3|image|Module.pm:new(200)|VCL::Module::Provisioning::VMware::VIM_SSH
object created for computer vcl-linux-template-1, address: 432a330
2012-06-14 14:15:57|25286|3:3|image|VIM_SSH.pm:initialize(126)|VIM
executable is not available on the VM host, output:
|25286|3:3|image| bash: vim-cmd: command not found
|25286|3:3|image| bash: vmware-vim-cmd: command not found
[...]
That's strange, because when I ssh from my management node to the ESX
machine, I see:
~ # which vim-cmd
/bin/vim-cmd
I also notice that during "vcld -setup", it never asks which hypervisor
is running the VM we want to capture, so how does it know where to ssh
to run vim-cmd? ...And that makes me wonder, is it connecting to the
wrong host to do the capture?
It isn't connecting to the VM itself, at least not according to logs on
that machine.
So I'm confused.
Re: next issue, Re: Image capture hitch
Posted by Dmitri Chebotarov <dc...@gmu.edu>.
Michael
To answer 2nd part of your question about which hypervisor vcld uses:
During 'vcld --setup' you enter computer name which you are capturing the image from.
This computer is registered in VCL with Provisioning Engine 'VMware' (under Manage Computers -> Edit Computer Information:)
The same computers is assigned to a VM host (under Virtual Hosts).
This is how 'vcld --setup' knows what hypervisor/host to use for capture - you will see it on the step where you select image OS, before the list of OSs.
--
Thank you,
Dmitri Chebotarov
Virtual Computing Lab Systems Engineer, TSD - Ent Servers & Messaging
223 Aquia Building, Ffx, MSN: 1B5
Phone: (703) 993-6175
Fax: (703) 993-3404
On Thursday, June 14, 2012 at 16:01 , Michael Jinks wrote:
> On Thu, Jun 14, 2012 at 02:37:40PM -0400, Josh Thompson wrote:
> >
> > You're hitting a bug in 2.2.1. If you go to Manage Computers->Computer
> > Utilities, you can set the VM to the available state successfully.
> >
>
>
> Thanks. I had looked around a little for another way to do it but
> missed that.
>
> Now I'm a little further and hitting a new problem. I can start the
> capture process, but the capture process fails. I don't have a
> successful instance to compare against, so I'm not sure exactly where
> the salient problem is, but I notice this in the log:
>
> [...]
> 2012-06-14
> 14:15:57|25286|3:3|image|Module.pm:create_mn_os_object(335)|management
> node OS object has already been created, address: 3fc9dc8, returning 1
> 2012-06-14
> 14:15:57|25286|3:3|image|Module.pm:new(200)|VCL::Module::Provisioning::VMware::VIM_SSH
> object created for computer vcl-linux-template-1, address: 432a330
> 2012-06-14 14:15:57|25286|3:3|image|VIM_SSH.pm:initialize(126)|VIM
> executable is not available on the VM host, output:
> |25286|3:3|image| bash: vim-cmd: command not found
> |25286|3:3|image| bash: vmware-vim-cmd: command not found
> [...]
>
> That's strange, because when I ssh from my management node to the ESX
> machine, I see:
>
> ~ # which vim-cmd
> /bin/vim-cmd
>
> I also notice that during "vcld -setup", it never asks which hypervisor
> is running the VM we want to capture, so how does it know where to ssh
> to run vim-cmd? ...And that makes me wonder, is it connecting to the
> wrong host to do the capture?
>
> It isn't connecting to the VM itself, at least not according to logs on
> that machine.
>
> So I'm confused.
Fixed, Re: next issue, Re: Image capture hitch
Posted by Michael Jinks <mj...@uchicago.edu>.
On Thu, Jun 14, 2012 at 03:01:03PM -0500, Michael Jinks wrote:
>
> [...]
> 2012-06-14
> 14:15:57|25286|3:3|image|Module.pm:create_mn_os_object(335)|management
> node OS object has already been created, address: 3fc9dc8, returning 1
> 2012-06-14
> 14:15:57|25286|3:3|image|Module.pm:new(200)|VCL::Module::Provisioning::VMware::VIM_SSH
> object created for computer vcl-linux-template-1, address: 432a330
> 2012-06-14 14:15:57|25286|3:3|image|VIM_SSH.pm:initialize(126)|VIM
> executable is not available on the VM host, output:
> |25286|3:3|image| bash: vim-cmd: command not found
> |25286|3:3|image| bash: vmware-vim-cmd: command not found
> [...]
There were two problems here. One was that I hadn't finised the steps
in the "further steps if using VMware" doc, under "Assign a VM to a
Virtual Host".
The other was that my ESX machine doesn't store VM's under the default
path listed in the "VMware ESX - local storage" VM profile. Fixed that,
now going to try it again.
Bit by bit...
--
Michael Jinks :: mjinks@uchicago.edu :: 773-469-9688
University of Chicago IT Services