qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Bharata B Rao <bharata@linux.vnet.ibm.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: aarcange@redhat.com, quintela@redhat.com, liang.z.li@intel.com,
	qemu-devel@nongnu.org, luis@cs.umu.se, amit.shah@redhat.com,
	pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH v8 00/54] Postcopy implementation
Date: Wed, 30 Sep 2015 19:58:17 +0530	[thread overview]
Message-ID: <20150930142817.GA10885@in.ibm.com> (raw)
In-Reply-To: <20150930105304.GD2627@work-vm>

On Wed, Sep 30, 2015 at 11:53:04AM +0100, Dr. David Alan Gilbert wrote:
> * Bharata B Rao (bharata@linux.vnet.ibm.com) wrote:
> > On Mon, Sep 28, 2015 at 05:51:39PM +0100, Dr. David Alan Gilbert (git) wrote:
> > > From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
> > > 
> > >   This is the 8th cut of my version of postcopy.
> > > 
> > > The userfaultfd linux kernel code is now in the upstream kernel
> > > tree, and so 4.3-rc3 can be used without modification.
> > > 
> > > This qemu series can be found at:
> > > https://github.com/orbitfp7/qemu.git
> > > on the wp3-postcopy-v8 tag
> > > 
> > > 
> > > Testing status:
> > >   * Tested heavily on x86
> > >   * Smoke tested on aarch64 (so it does work on different page sizes)
> > >   * Power is unhappy for me (but gets further than the htab problem
> > >     v7 used to have) (I get a kvm run failed)
> > 
> > Seems to be completing successfully on Power. But it takes 2min for the
> > migration status to transition from setup to active.
> > 
> > Host: 4.3.0-rc3+
> > Guest: 4.3.0-rc3+
> > QEMU: wp3-postcopy-v8 of your tree.
> > 
> > # ./ppc64-softmmu/qemu-system-ppc64 --enable-kvm --nographic -machine pseries -m 8G,slots=32,maxmem=32G -device virtio-blk-pci,drive=rootdisk -drive file=/home/bharata/F20-snap1,if=none,cache=none,id=rootdisk,format=qcow2 -vga none -net nic,model=virtio -net user -redir tcp:2000::22 -smp 16,maxcpus=32 -serial pty
> > 
> > (qemu) migrate_set_capability x-postcopy-ram on
> > (qemu) migrate -d tcp:localhost:4444
> > (qemu) info migrate
> > capabilities: xbzrle: off rdma-pin-all: off auto-converge: off zero-blocks: off compress: off events: off x-postcopy-ram: on 
> > Migration status: setup
> > total time: 0 milliseconds
> > 
> > same status for around 2min...
> 
> That's interesting; I saw that behaviour on my aarch64 box, but not on
> my power box or on x86.  Can you try using tcp:127.0.0.1:4444 to force
> ipv4 (that fixed it for me on aarch64).  On the aarch box I found that
> it still happened with head of tree qemu and so decided it wasn't my
> postcopy world; I'm assuming what's happening is that it's trying
> to connect to the IPv6 address, timing out and then trying IPv4.

Yes, s/localhost/127.0.0.1 helps.

> 
> Great; is the guest happy?

Yes, survived a reboot, postcopy migration back to the original host
and then a reboot.

Regards,
Bharata.

  reply	other threads:[~2015-09-30 14:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1443459153-10965-1-git-send-email-dgilbert@redhat.com>
2015-09-30 10:25 ` [Qemu-devel] [PATCH v8 00/54] Postcopy implementation Bharata B Rao
2015-09-30 10:53   ` Dr. David Alan Gilbert
2015-09-30 14:28     ` Bharata B Rao [this message]
2015-09-30 16:14       ` Dr. David Alan Gilbert
2015-10-01  3:04         ` Bharata B Rao
2015-10-02  9:03           ` Dr. David Alan Gilbert
2015-10-05  4:38 ` Bharata B Rao
2015-10-05  9:34   ` Dr. David Alan Gilbert
     [not found] ` <1443459153-10965-2-git-send-email-dgilbert@redhat.com>
     [not found]   ` <87oaftx1nw.fsf@neno.neno>
2015-10-20 11:54     ` [Qemu-devel] [PATCH v8 01/54] Add postcopy documentation Juan Quintela
     [not found] ` <1443459153-10965-5-git-send-email-dgilbert@redhat.com>
     [not found]   ` <87h9llx1lq.fsf@neno.neno>
2015-10-20 11:55     ` [Qemu-devel] [PATCH v8 04/54] Move configuration section writing Juan Quintela
     [not found] ` <1443459153-10965-7-git-send-email-dgilbert@redhat.com>
     [not found]   ` <87d1w9x1ho.fsf@neno.neno>
2015-10-20 11:56     ` [Qemu-devel] [PATCH v8 06/54] Rename mis->file to from_src_file Juan Quintela
     [not found] ` <1443459153-10965-10-git-send-email-dgilbert@redhat.com>
     [not found]   ` <874mhlx108.fsf@neno.neno>
2015-10-20 11:57     ` [Qemu-devel] [PATCH v8 09/54] Add QEMU_MADV_NOHUGEPAGE Juan Quintela
     [not found] ` <1443459153-10965-11-git-send-email-dgilbert@redhat.com>
     [not found]   ` <87zizdvm9m.fsf@neno.neno>
2015-10-20 11:58     ` [Qemu-devel] [PATCH v8 10/54] migration/ram.c: Use RAMBlock rather than MemoryRegion Juan Quintela
     [not found] ` <1443459153-10965-14-git-send-email-dgilbert@redhat.com>
     [not found]   ` <87vba1vm6n.fsf@neno.neno>
2015-10-20 11:58     ` [Qemu-devel] [PATCH v8 13/54] Move dirty page search state into separate structure Juan Quintela
     [not found] ` <1443459153-10965-18-git-send-email-dgilbert@redhat.com>
     [not found]   ` <87r3kpvl9x.fsf@neno.neno>
2015-10-20 11:59     ` [Qemu-devel] [PATCH v8 17/54] Return path: socket_writev_buffer: Block even on non-blocking fd's Juan Quintela
2015-09-29  8:37 [Qemu-devel] [PATCH v8 00/54] Postcopy implementation Dr. David Alan Gilbert (git)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150930142817.GA10885@in.ibm.com \
    --to=bharata@linux.vnet.ibm.com \
    --cc=aarcange@redhat.com \
    --cc=amit.shah@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=liang.z.li@intel.com \
    --cc=luis@cs.umu.se \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).