similar to: Question about managing migration transfers

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:

On 28/02/14 11:43, Paolo Bonzini wrote: > Il 28/02/2014 11:41, Joaquim Barrera ha scritto: >>> >> >> Thanks for the answer. Something is still not clear to me. Are we in >> front of a bug (that means, something that could be fixed) or is this >> behaviour somehow expected for some reason? More and more tests I am >> doing, I get allways the same throughput

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

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.

I have three servers set up as in this diagram: http://libvirt.org/migration.html#flowmanageddirect My control application has separate libvirt connections to both the source and destination nodes. I want to migrate entirely over those connections, not involving any third (peer-to-peer) connection between nodes (a third connection isn't possible because of firewalls and SSH keys). Is

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. In this scenario we would like to perform a live > migration by proxying the migration through a unix socket to a process in

On 24/02/14 23:26, Paolo Bonzini wrote: >> Thanks for raising this. >> >> I noticed that mirror_run() does not throttle the first loop where it >> populates the dirty bitmap using bdrv_is_allocated_above(). > This is on purpose. Does it causes a noticeable stall in the guest? > >> The main >> copy loop does take the speed limit into account but perhaps

Hi all, As I am doing some tests with qemu, I realized that the way it does 'migrate -i tcp:DEST:444' is not the same as 'libvirt migrate --copy-storage-inc'. Basically qemu uses the same stream as RAM migration and libvirt takes advantage of NBD transfer. With virsh migrate-setspeed I observed that one can only control the transfer throughput of RAM, but not disk

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

Hello everyone, Can somebody point where I can find the code where libvirt makes the decision to complete a live migration? I mean, at some point syncronising the VM state, it has to decide that the delta left to be migrate is low enough to achieve downtime 0, so libvirt finishes the migration. This "low enough" must be defined somewhere in the code, but I am unable to find it.

On Fri, Feb 14, 2014 at 11:58:56AM +0100, Michal Privoznik wrote: > On 14.02.2014 10:40, Joaquim Barrera wrote: > > Hi all, > > > > As I am doing some tests with qemu, I realized that the way it does > > 'migrate -i tcp:DEST:444' is not the same as 'libvirt migrate > > --copy-storage-inc'. Basically qemu uses the same stream as RAM > >

On 14.02.2014 10:40, Joaquim Barrera wrote: > Hi all, > > As I am doing some tests with qemu, I realized that the way it does > 'migrate -i tcp:DEST:444' is not the same as 'libvirt migrate > --copy-storage-inc'. Basically qemu uses the same stream as RAM > migration and libvirt takes advantage of NBD transfer. > > With virsh migrate-setspeed I observed

Il 28/02/2014 11:41, Joaquim Barrera ha scritto: >> > > Thanks for the answer. Something is still not clear to me. Are we in > front of a bug (that means, something that could be fixed) or is this > behaviour somehow expected for some reason? More and more tests I am > doing, I get allways the same throughput chart: unlimited bandwidth when > syncronizing the disk, and

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

Hi libvirt support, Can you please give me some example of how to use "virsh migrate --live" with p2p option including both source host and target host? I try to get some info from your website, but no info with migrate. [root at vmoactive02 qemu]# virsh help migrate NAME migrate - migrate domain to another host SYNOPSIS migrate [--live] [--p2p] [--direct]

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

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

On Wed, Jun 01, 2016 at 03:55:37PM +0200, Peter Krempa wrote: > On Wed, Jun 01, 2016 at 11:59:29 +0200, Marc-Aurèle Brothier - Exoscale wrote: > > Hi, > > > > I'm facing a strange issue while doing a migration from an hypervisor to another one. The migration takes for ever to start moving the memory. > > The VM had no workload what so ever, just a basic ubuntu

Hello everybody! /(First I need to apologize becase I mussunderstood the prupose of libvirt-list and I sent this mail there instead of this list)/ I would like to introduce myself, as this is my first contact with libvirt mailing list (although I've been reading quite a lot of documentation). My name is Joaquim Barrera, from Barcelona, Catalonia. I am a computer engineer and recently I