On 2 Feb 2010, at 0807h, Andy Kurth wrote:

> The problem has to do with SSH checking the known_hosts file.  Try adding the 
> following to /etc/ssh/ssh_config before the "Host *" section:
> Host vmguest-* vmhost-* 10.*
>   UserKnownHostsFile /dev/null
>   StrictHostKeyChecking no
> This will cause SSH to ignore the known_hosts file for your VMs and VM hosts 
> on the private network.  The host keys change often as computers are 
> reloaded. Adjust the Host line to match your computer naming convention and 
> private IP addresses.

Yay!  The above addition, tweaked for our setup, did the trick.  No more SSH 

Now, I'm sorry to say, I've got a whole new group of warnings, starting with:

2010-02-03 10:37:35|2273|1:13|image|utils.pm:run_ssh_command(6180)|executing 
SSH command on vmguest-1:
|2273|1:13|image| /usr/bin/ssh -i /etc/vcl/vcl.key  -l root -p 22 -x vmguest-1 
'$SYSTEMROOT/System32/cmd.exe /c "mkdir \"C:/Cygwin/home/root/VCL\""' 2>&1

|2273|1:13|image| ---- WARNING ---- 
|2273|1:13|image| 2010-02-03 
10:37:35|2273|1:13|image|Windows.pm:create_directory(831)|failed to create 
directory on vmguest-1: C:/Cygwin/home/root/VCL, exit status: 126, output:
|2273|1:13|image| bash: C:\WINDOWS/System32/cmd.exe: Bad address
|2273|1:13|image| ( 0) utils.pm, notify (line: 737)
|2273|1:13|image| (-1) Windows.pm, create_directory (line: 831)
|2273|1:13|image| (-2) Windows.pm, copy_capture_configuration_files (line: 5908)
|2273|1:13|image| (-3) Windows.pm, pre_capture (line: 179)
|2273|1:13|image| (-4) Version_5.pm, pre_capture (line: 85)
|2273|1:13|image| (-5) vmware.pm, capture (line: 1202)
|2273|1:13|image| (-6) image.pm, process (line: 162)

...and followed by other warnings that appear to be consequences of this one, 
and ending with failure.

The mix of slashes and a backslash in "C:\WINDOWS/System32/cmd.exe" looks wrong 
to me, and it seems connected to $SYSTEMROOT, but that's as far as I can take 

Hoping the end of this tunnel arrives soon...



Terry McGuire
Junior Analyst, Research Support Group
Academic Information & Communication Technologies (AICT)
University of Alberta
Edmonton, Alberta, Canada  T6G 2H1
Phone:  780-492-9422

This communication is intended for the use of the recipient to which it is 
addressed, and may contain confidential, personal, and/or privileged 
information.  Please contact us immediately if you are not the intended 
recipient of this communication.  If you are not the intended recipient of this 
communication, do not copy, distribute, or take action on it.  Any 
communication received in error, or subsequent reply, should be deleted or 

Reply via email to