similar to: (no subject)

I have made all these changes in my Ubuntu desktop. I have also enabled passwordless login for ssh at destination. But still, everytime i run into the same problem. On Thu, Mar 24, 2016, 4:05 PM Michal Privoznik <mprivozn@redhat.com> wrote: > On 24.03.2016 11:23, nidhi d wrote: > > From the auth log at the destination: > > Failed password for <user> from <ip>

Libvirt version as per virsh --version 1.2.2 Xen version as per xl info 4.4.2 I am working with xl toolstack On Mar 30, 2016 11:09 PM, "Jim Fehlig" <jfehlig@suse.com> wrote: > nidhi d wrote: > > When i tried > > > > virsh migrate <vm> xen+ssh://user@remote/system > > > > I get the error > > > > This function is not supported by

How is the traffic different when using the tunnelled option rather than ssh without tunnelling? On Wed, Mar 23, 2016, 5:14 PM Michal Privoznik <mprivozn@redhat.com> wrote: > On 22.03.2016 10:28, nidhi d wrote: > > How is tunnelled option specified during migratiion different than an > > ordinary ssh connection specified as:- virsh migrate vmName > >

>From the auth log at the destination: Failed password for <user> from <ip> port <no> ssh2 On Thu, Mar 24, 2016, 3:50 PM Michal Privoznik <mprivozn@redhat.com> wrote: > On 23.03.2016 14:47, nidhi d wrote: > > I tried using tunnelled mode for vm migration, but migration failed with > > the error > > > > Permission

I tried using tunnelled mode for vm migration, but migration failed with the error Permission denied(publickey,password):Connection reset by peer I have enabled passwordless ssh login at the destination. Also i am able to connect to the destination using using qemu+ssh. On Wed, Mar 23, 2016, 6:59 PM Michal Privoznik <mprivozn@redhat.com> wrote: > On 23.03.2016 14:13, nidhi d wrote:

When i tried virsh migrate <vm> xen+ssh://user@remote/system I get the error This function is not supported by the connection driver:virDomainMigrate3

How is tunnelled option specified during migratiion different than an ordinary ssh connection specified as:- virsh migrate vmName qemu+ssh://user@remotesys/system?

On 23.03.2016 14:13, nidhi d wrote: > How is the traffic different when using the tunnelled option rather than > ssh without tunnelling? There are two migration streams here: 1) libvirt (used to transfer libvirt's internal state of domain onto the other side) 2) qemu (used to transfer qemu's internal state of domain onto the other side) specifying bare qemu+ssh:/// makes libvirt

Is the migration of xen vms implemented in libvirt? Using virsh migrate xen+ssh ?

On 24.03.2016 11:23, nidhi d wrote: > From the auth log at the destination: > Failed password for <user> from <ip> port <no> ssh2 There's your answer. Libvirt really requires pubkey instead of passwd auth. http://wiki.libvirt.org/page/SSHSetup Michal

On 29.03.2016 06:42, nidhi d wrote: > Is the migration of xen vms implemented in libvirt? Using virsh migrate > xen+ssh ? > According to: http://libvirt.org/hvsupport.html yes. There's the basic (v1) migration. Michal

On 23.03.2016 14:47, nidhi d wrote: > I tried using tunnelled mode for vm migration, but migration failed with > the error > > Permission denied(publickey,password):Connection reset by peer > > I have enabled passwordless ssh login at the destination. Also i am able to > connect to the destination using using qemu+ssh. Maybe the destination ssh is denying spawning a

nidhi d wrote: > When i tried > > virsh migrate <vm> xen+ssh://user@remote/system > > I get the error > > This function is not supported by the connection driver:virDomainMigrate3 What version of libvirt and Xen are you using? And wrt to Xen, are you using the xm/xend or xl/libxl toolstacks? Regards, Jim

On 22.03.2016 10:28, nidhi d wrote: > How is tunnelled option specified during migratiion different than an > ordinary ssh connection specified as:- virsh migrate vmName > qemu+ssh://user@remotesys/system? > > virsh migrate --tunelled ... Michal

On 09/10/2013 12:03 PM, Arun Viswanath wrote: > Hi All, > I'm need to simulate libvirt API's say to mock the libvirt API > responses. (Actually I need to simulate qemu API's response). Because of my > project needs I need to write this simulated libvirt server in Java. I > believe the simulated libvirt can be written as java RPC which should > capable to receive

Hi All, Sorry, I do not know to reply the previous message directly, so I have to manually copy them here. I have two questions about the following issue? 1. I follow the instructions blew to migrate a vm with snapshots. When I perform 'virsh snapshot-create --redefine $dom file' on the destination.' I got an error saying that "no domain with matching name $dom". I'm

Hi Eric, Thanks for your response. I like to know how test driver works. In the libvirt.org for test driver it is mentioned as "It can start with a pre-configured default config, or be given a path to an alternate config". Is the config is an xml file where we mentioned some dummy data so that the test driver will return it as response. If yes then where can I find this dummy file? As

Hi All, I'm trying to migrate from an NT4 domain to samba-3... sorry this is so long... when I run the "net rpc vampire" I get errors for users and machines in uppercase or contain uppercase chars. I'm in a test env before I go live! I'm on a gentoo distro w/ shadow. useradd FOO errors, this might be the culprit... I set up some dummy accts and made them members of

Hi Michal, By the way, I noticed ipv6 loopback IP addresses in your pcap. As I normally try to capture on nic where migration carried out, I thought of checking with you if your wireshark could dissect libvirt RPC in such pcap too (captured on a nic) ?. During migration, I do not see any traffic on loopback and I think it is expected, but thinking how you get those captured ?. Any

Hi Michal, Thank you for your suggestion. My apologies that I took sometime to get back on further confirmation. Regrettably, my tshark is still unable to find libvirt payload inside packet capture, though it lists libvirt as a possible filter. # rpm -ql libvirt-wireshark-1.2.9.3-2.fc21.x86_64 /usr/lib64/wireshark/plugins/1.12.5/libvirt.so As I used wireshark 1.12.6 version, I