similar to: Is tunnelled "managed direct" live migration actually possible?

Dear All I try to migration a kvm guest os to another host failed server: ubuntu 11.04 server virsh:migrate --live --tunnelled vm1 qemu+ssh://192.168.10.3/system error:Requested operation is not valid:cannot perform tunnelled migration without using peer2peer flag

On Wed, Aug 29, 2018 at 4:55 AM, Daniel P. Berrangé <berrange@redhat.com> wrote: > On Tue, Aug 28, 2018 at 05:07:18PM -0400, David Vossel wrote: > > Hey, > > > > Over in KubeVirt we're investigating a use case where we'd like to > perform > > a live migration within a network namespace that does not provide > libvirtd > > with network access.

On Wed, Sep 12, 2018 at 6:59 AM, Martin Kletzander <mkletzan@redhat.com> wrote: > On Mon, Sep 10, 2018 at 02:38:48PM -0400, David Vossel wrote: > >> On Wed, Aug 29, 2018 at 4:55 AM, Daniel P. Berrangé <berrange@redhat.com> >> wrote: >> >> On Tue, Aug 28, 2018 at 05:07:18PM -0400, David Vossel wrote: >>> > Hey, >>> > >>>

Hi, I am running libvirt 0.8.6 on qemu (kvm, really) 0.12.5. I have noticed that while a live migration is running, I cannot do anything else with libvirt -- even 'virsh list' blocks without output until the migration is almost done. (At that point 'virsh list' will dump a final screen showing the VM I just migrated as 'running'; the next run of 'virsh

On Mon, Sep 10, 2018 at 02:38:48PM -0400, David Vossel wrote: >On Wed, Aug 29, 2018 at 4:55 AM, Daniel P. Berrangé <berrange@redhat.com> >wrote: > >> On Tue, Aug 28, 2018 at 05:07:18PM -0400, David Vossel wrote: >> > Hey, >> > >> > Over in KubeVirt we're investigating a use case where we'd like to >> perform >> > a live

On Fri, Sep 14, 2018 at 6:55 PM David Vossel <dvossel@redhat.com> wrote: > > > On Wed, Sep 12, 2018 at 6:59 AM, Martin Kletzander <mkletzan@redhat.com> > wrote: > >> On Mon, Sep 10, 2018 at 02:38:48PM -0400, David Vossel wrote: >> >>> On Wed, Aug 29, 2018 at 4:55 AM, Daniel P. Berrangé <berrange@redhat.com >>> > >>> wrote:

Hi, when I try to use such API: virDomainPtr <http://www.libvirt.org/html/libvirt-libvirt.html#virDomainPtr> virDomainMigrate (virDomainPtr <http://www.libvirt.org/html/libvirt-libvirt.html#virDomainPtr> domain, virConnectPtr <http://www.libvirt.org/html/libvirt-libvirt.html#virConnectPtr> dconn, unsigned long flags, const char * dname, const char * uri,

Hi all, We are working on nova live-migration using Ceph and trying to work around the problem where vm migration fails if name resolution is not enabled in a cluster. See the link, https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization_Host_Configuration_and_Guest_Installation_Guide/App_Migration_Address.html We have managed to work around this by setting

Hey, Over in KubeVirt we're investigating a use case where we'd like to perform a live migration within a network namespace that does not provide libvirtd with network access. In this scenario we would like to perform a live migration by proxying the migration through a unix socket to a process in another network namespace that does have network access. That external process would live

On Fri, Apr 03, 2015 at 10:13:38AM +0200, Kashyap Chamarthy wrote: > On Fri, Apr 03, 2015 at 10:08:21AM +0200, Kashyap Chamarthy wrote: > > Migration without --p2p works just fine, ie. the below works: > > > > > > $ virsh migrate --verbose --copy-storage-all \ > > --live cvm1 qemu+ssh://kashyapc@devstack3/system > > Migration: [100 %] >

On Thu, Jun 11, 2015 at 07:28:10PM +0200, Dominique Ramaekers wrote: > Hi, > > I'm experimenting with the migration function of virsh. I'm doing the > migrate with following commands: > > virsh migrate --life --persistent --copy-storage-all --verbose > --abort-on-error domain qemu+ssh://root@destination/system virsh > migrate-setmaxdowntime domain 20000 > >

Hi, I'm experimenting with the migration function of virsh. I'm doing the migrate with following commands: virsh migrate --life --persistent --copy-storage-all --verbose --abort-on-error domain qemu+ssh://root@destination/system virsh migrate-setmaxdowntime domain 20000 However sometimes at the end of the migration, the guest isn't started on the destination host. So I'm left

[moderator note: I'm forwarding a stripped down version of the original mail which was rejected in the moderator queue. I stripped the 3.3 megabyte .tar.bz2 of the log file attachment, which is inappropriate for a technical list. Either trim the log to the relevant portion, or host the log externally and have your list email merely give a URL of the externally-hosted file] >

Hi, I'm having a hard time to figure how to perform Xen live migration using the python API with the same rate of success than virt-manager. # virsh version Compiled against library: libvir 0.8.3 Using library: libvir 0.8.3 Using API: Xen 3.0.1 Running hypervisor: Xen 3.2.0 The goal is to have the migration done in only one call, including a definition in the remote xend and undefinition

Hi all. I'm just new to libvirt. Looking page here http://libvirt.org/drvxen.html , there are examples of connection URIs to Xen. xen:/// (local access, direct) xen+unix:/// (local access, via daemon) xen://example.com/ (remote access, TLS/x509) xen+tcp://example.com/ (remote access, SASl/Kerberos) xen+ssh://root@example.com/

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:/// ?

Dear All? I try to migrate a kvm guset os from Host A to Host B,but failed ================================================ Host OS : Ubuntu 11.04 server Using libvirt 0.8.8 Using API:QEMU 0.8.8 Running hypervisor:QEMU 0.14.0 =============================================== virsh migrate --live winxp quem+ssh://192.168.10.3/system root at

Hello I have a question about live migration when libvirt requires sasl authentication. I have managed to configure remote access for user nova with sasl enabled (credentials stored in auth.conf - https://review.openstack.org/#/c/12706/). It looks like live migration do not use these credentials at all. What is more it thinks that sasl is not not configured: 2013-07-01 09:49:09.317+0000: 17997:

Migration without --p2p works just fine, ie. the below works: $ virsh migrate --verbose --copy-storage-all \ --live cvm1 qemu+ssh://kashyapc@devstack3/system Migration: [100 %] Result: - On the source host, the guest is shut off - On the destination host, the guest is live migratied successfully Migration with "--p2p" fails, a simple test below:

I am trying to work out what all the options are for migrating a KVM machine to another KVM machine, without using shared storage. The documentation is not quite verbose and not intuitive, so I'm hoping someone can explain this to me. The man pages show this syntax: migrate optional --live --p2p --direct --tunnelled --persistent --undefinesource --suspend --copy-storage-all --copy-storage-inc