Hi,

I have attached the log of both virsh -c ssh://root@192.168.1.40 & virsh -c xen+ssh://root@192.168.1.40

On 11.08.16 14:14, Anantha Raghava wrote:

Hi,

Tested this with different combinations:

a. from VDSM host, both "ssh root@192.168.1.40" and "sudo -u vdsm ssh
root@192.168.1.40" commands are logging in without asking for password and I
can run all xe commands without any glitch without modifications to default
xen server firewall or SELinux rules.

b. With firewall enabled and SELinux set to enforcing or permissive or
disabled, I run "virsh -c ssh://root@192.168.1.40". And the command is
resulting in two errors:

    error: filed to connect to the hypervisor
    error: unable to connect to the server at '192.168.1.40:16514' : No
route to the host.

c. With firewall disabled and SELinux set to Enforcing or permissive or
disabled, I run "virsh -c ssh://192.168.1.40". And the command is resulting
in two errors

error: filed to connect to the hypervisor
    error: unable to connect to the server at '192.168.1.40:16514' :
Connection refused

Good tests,
We need to figure out why libvirt refuse the connection,
try to debug virsh by running:

$ export LIBVIRT_LOG_OUTPUTS="1:file:/tmp/libvirt_client.log"
$ export LIBVIRT_DEBUG=1
$ virsh -c virsh -c ssh://192.168.1.40

and examing /tmp/libvirt_client.log file

-- 

Thanks & Regards,


Anantha Raghava

eXza Technology Consulting & Services

Ph: +91-9538849179, E-mail: raghav@exzatechconsulting.com
<mailto:raghav@exzatechconsulting.com>

URL: http://www.exzatechconsulting.com <http://www.exzatechconsulting.com/>

/*Support No.: +91-7829774584 */



DISCLAIMER:
This e-mail communication and any attachments may be privileged and
confidential to eXza Technology Consulting & Services, and are intended only
for the use of the recipients named above If you are not the addressee you
may not copy, forward, disclose or use any part of it. If you have received
this message in error, please delete it and all copies from your system and
notify the sender immediately by return e-mail. Internet communications
cannot be guaranteed to be timely, secure, error or virus-free. The sender
does not accept liability for any errors or omissions.


Do not print this e-mail unless required. Save Paper & trees.

On Thursday 11 August 2016 12:20 PM, Shahar Havivi wrote:

On 10.08.16 19:40, Anantha Raghava wrote:

Hello Richard / Shahar,

I installed and enabled nc on Xen Server host. Now the " ...... sh: nc:
command not found: Input/output error" is gone. Communication is
established. However I am still getting two specific errors:

VDSM ovirt_engine command failed: End of file while reading data: :
Input/Output error

&

Failed to retrieve VMs Information from the external server
xen+ssh://root@192.168.1.40

I am receiving the same error when I run virsh -c
xen+ssh://root@192.168.1.40

Screen shot is attached for quick reference.

Is it something to do with firewall / ip tables on xen server or libvirtd
host?

Hi,
You don't need to try it on oVirt when 'virsh -c' doesn't work since oVirt try
to connect via libvirt libraries (same as virsh) before it called virt-v2v.

Did you follow all the steps in the wiki?
Are you able to ssh to the Xen server from the vdsm machine that you try to
run virsh without password? (ssh root@192.168.1.40)

-- 

Thanks & Regards,

Anantha Raghava


Do not print this e-mail unless required. Save Paper & trees.

On Wednesday 10 August 2016 06:04 PM, Anantha Raghava wrote:

Hi,

Let me try this and post the results here.

Regards,
Ananth

On 10 Aug 2016 15:28, "Richard W.M. Jones" <rjones@redhat.com
<mailto:rjones@redhat.com>> wrote:

     On Wed, Aug 10, 2016 at 09:45:52AM +0300, Shahar Havivi wrote:
     > On 10.08.16 06:45, Anantha Raghava wrote:
     > > Hi,
     > >
     > > I even attempted to run command virsh -c
     xen+ssh://root@xenhost and I get
     > > error "/*error: End of file reading data: sh: nc: command not
     found:
     > > Input/output error"*/
     > First you need to be able to login via virsh (before trying to
     import via
     > oVirt).
     >
     > I never encounter this error before,
     > I guess that nc is netcat...,
     > try to install nmap-ncat:
     > $ dnf info nmap-ncat
     >
     > Adding Richard which may have more input.

     Yes, you need to install 'nc' on the *target* (Xen) machine.

     This is because libvirt's ssh transport uses nc:
     https://libvirt.org/guide/html/Application_Development_Guide-Architecture-Transports.html
     <https://libvirt.org/guide/html/Application_Development_Guide-Architecture-Transports.html>

     Rich.

     --
     Richard Jones, Virtualization Group, Red Hat
     http://people.redhat.com/~rjones <http://people.redhat.com/%7Erjones>
     Read my programming and virtualization blog: http://rwmj.wordpress.com
     virt-builder quickly builds VMs from scratch
     http://libguestfs.org/virt-builder.1.html
     <http://libguestfs.org/virt-builder.1.html>