Thank you Javi and Eric for the pointers. I disabled iptables and it worked perfectly.

Best,
--Hari

On 4/1/13 12:24 PM, Javi Legido wrote:

Hi.

In case that you didn't did it already, and assuming TCP as transport protocol, maybe you can try a 'tpdump -i any' and grepping by IP address of 'source' machine on 'destination' machine to make sure that there's connectivity between machines.

Regards.

Javier

El 01/04/2013 18:18, "Hari Pyla" <ha...@vt.edu <mailto:ha...@vt.edu>> escribió:

    Thank you for the prompt response Eric. I restarted the domain and
    the error disappeared.
    Now I have the following error.

    [user@n0 ~]$ virsh --c qemu:///system migrate --verbose
    Fedora-17-x86_64-1 qemu+ssh://n1/system

    error: unable to connect to server at 'n1:49157': No route to host

    or

    [user@n0 ~]$ virsh --connect qemu:///system migrate --live
    Fedora-17-x86_64-1 qemu+ssh://n1/system tcp://n1 --unsafe --verbose

    error: unable to connect to server at 'n1:49158': No route to host

    On both the nodes n0 and n1 I've disabled SELinux and I've opened
    ports from 49152:49215. Any ideas on what is causing this error.

    Thanks,
    --Hari


    On 4/1/13 12:02 PM, Eric Blake wrote:

        On 04/01/2013 09:53 AM, Hari Pyla wrote:

            Hi,
              I am trying to migrate a VM from one node to another and
            I get the
            following error message.

            [user@n0 ~]$ virsh --c qemu:///system migrate --verbose
            Fedora-17-x86_64-1 qemu+ssh://n1/system

            error: XML error: missing security model when using
            multiple labels

            On both the src and dest nodes, I've disabled SELinux and
            I have the
            following libvirt version installed

            $virsh --connect qemu:///system version --daemon
            Compiled against library: libvirt 0.10.2
            Using library: libvirt 0.10.2
            Using API: QEMU 0.10.2
            Running hypervisor: QEMU 0.12.1
            Running against daemon: 0.10.2

        The error message sounds a lot like this bug:
        https://bugzilla.redhat.com/show_bug.cgi?id=923946

        If it is the same, then upgrading both libvirt to the
        just-released
        1.0.4 should fix the problem.


    _______________________________________________
    libvirt-users mailing list
    libvirt-users@redhat.com <mailto:libvirt-users@redhat.com>
    https://www.redhat.com/mailman/listinfo/libvirt-users


_______________________________________________
libvirt-users mailing list
libvirt-users@redhat.com
https://www.redhat.com/mailman/listinfo/libvirt-users

Reply via email to