similar to: libvirt-ext transport

Hi, I would like to use the ext transport mode to migrate VMs between two hosts, but I didn't find any documentation about the ext interface. I have successfully migrate a vm with a programm that passes it's incomming messages through the network to libvirts socket on the target server. But the external program on the source side didn't get the connection URI or the server address or

2015-04-02 12:04 GMT+02:00 <Dhaval_Shah1@dell.com>: > Hi all, > > > > I am using libvirt 1.1.1. I can successfully able to connect with Qemu > driver but when I am trying to connect to the windows Hyper-V using virsh, I > am getting failure. > > > > [root@localhost hyperv]# virsh version > > Compiled against library: libvirt 1.1.1 > > Using

Hi all, I am using libvirt 1.1.1. I can successfully able to connect with Qemu driver but when I am trying to connect to the windows Hyper-V using virsh, I am getting failure. [root@localhost hyperv]# virsh version Compiled against library: libvirt 1.1.1 Using library: libvirt 1.1.1 Using API: QEMU 1.1.1 Running hypervisor: QEMU 1.5.3 When I am doing virsh to connect to hype-V I am getting

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:

>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

Hi, On a Fedora 18, I try to launch a VM with QEMU-GlusterFS native integration. I have enable fedora-virt-preview repo, and gluster-alpha3 repo. Below the list of installed package : glusterfs-3.4.0-0.3.alpha3.fc18.x86_64 glusterfs-devel-3.4.0-0.3.alpha3.fc18.x86_64 glusterfs-fuse-3.4.0-0.3.alpha3.fc18.x86_64 glusterfs-server-3.4.0-0.3.alpha3.fc18.x86_64

Hi, I want to use libvirt for windows but when i try to launch virsh it gives an error message saying "*error: invalid argument in transport methods unix, ssh and ext are not supported under Windows"* The version which I downloaded is libvirt-0.8.8.exe. I want to connect to two virtualization techniques --- *Virtualbox* and *VMWare* If libvirt is not supported on windows then is there

Oh to bad. I am currently working on some hybrid solution having mesos as an orchestrator combined with some kvm/qemu vm's. dcos does not allow this, and I wondered maybe if your kubernetes was limiting your options there also. -----Original Message----- Cc: libvirt-users Subject: RE: EXT: Re: KVM/QEMU Memory Ballooning Unfortunaltly it is not way what we can apply, due to the containers

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

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

Hello, I am working on live migration of virtual machine using xen and kvm.If i use qemu+ssh:///system then is the transport protocol used during live migration tcp or ssh?I mean i want to evaluate the performance of transport protocil during live migration using wireshark and netperf tool,so using this command will show tcp performance? Orelse i will have to use qemu+tcp:/// ?

What about running tasks/containers directly on the host? -----Original Message----- To: Daniel P. Berrangé Cc: libvirt-users@redhat.com Subject: RE: EXT: Re: KVM/QEMU Memory Ballooning Hi Daniel, Thank you very much for the quick answer. Now it is clear how this memballooning driver works, and how it can be managed manually. I really appreciate your answer. Regards, Csongor -----Original

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

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>

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

Hi libvirts, I'm playing with libvirt on Windows (downloaded the x64 msi) but I'm stuck at the following: virsh # net-edit default error: failed to connect to the hypervisor error: invalid argument: transport methods unix, ssh and ext are not supported under Windows Can someone shed some light on what transport method I should use? Any help is appriciated. P.S. I'm not

Hi, For backing chain that all images are iscsi network disk type , such as iscsi://ip/iqn../0(base image) <-iscsi://ip/iqn../1(active image). Currently, 'qemu-img info --backing-chain' command can display correct backing file info, but after starting guest with the active image in backing chain, it don't include the related <backingStore> element in dumpxml. So,

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 > >

On 2013-07-09 09:40, Vijay Bellur wrote: >> Hi, I'm trying to use qemu native glusterfs integration with libvirt. It's all working well from the qemu side, but libvirt fails to start a domain with a gluster drive or attach a drive. I have exactly the same error as this person: https://www.redhat.com/archives/libvirt-users/2013-April/msg00204.html [1] I use qemu 1.5.1 with glusterfs

On Wed, Mar 25, 2020 at 06:03:47PM +0100, john doe wrote: > Hi libvirts, > > I'm playing with libvirt on Windows (downloaded the x64 msi) but I'm > stuck at the following: > > virsh # net-edit default > error: failed to connect to the hypervisor > error: invalid argument: transport methods unix, ssh and ext are not > supported under Windows Libvirt has two