From: "Michael R. Hines" <mrhines@linux.vnet.ibm.com>
To: Chegu Vinod <chegu_vinod@hp.com>
Cc: Karen Noel <knoel@redhat.com>,
Juan Jose Quintela Carreira <quintela@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel qemu-devel <qemu-devel@nongnu.org>,
Orit Wasserman <owasserm@redhat.com>,
"Michael R. Hines" <mrhines@us.ibm.com>,
Anthony Liguori <anthony@codemonkey.ws>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v6 00/11] rdma: migration support
Date: Thu, 09 May 2013 18:45:10 -0400 [thread overview]
Message-ID: <518C26F6.5080009@linux.vnet.ibm.com> (raw)
In-Reply-To: <518C2135.306@hp.com>
Some more followup questions below to help me debug before I start
digging in.......
On 05/09/2013 06:20 PM, Chegu Vinod wrote:
Setting aside the mlock() freezes for the moment, let's first fix your
crashing
problem on the destination-side. Let's make that a priority before we fix
the mlock problem.
When the migration "completes", can you provide me with more detailed
information
about the state of QEMU on the destination?
Is it responding?
What's on the VNC console?
Is QEMU responding?
Is the network responding?
Was the VM idle? Or running an application?
Can you attach GDB to QEMU after the migration?
> /usr/local/bin/qemu-system-x86_64 \
> -enable-kvm \
> -cpu host \
> -name vm1 \
> -m 131072 -smp 10,sockets=1,cores=10,threads=1 \
> -mem-path /dev/hugepages \
Can you disable hugepages and re-test?
I'll get back to the other mlock() issues later after we at least first
make sure the migration itself is working.....
next prev parent reply other threads:[~2013-05-09 22:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-03 23:28 [Qemu-devel] [PATCH v6 00/11] rdma: migration support Chegu Vinod
2013-05-09 17:20 ` Michael R. Hines
2013-05-09 22:20 ` Chegu Vinod
2013-05-09 22:45 ` Michael R. Hines [this message]
2013-06-02 4:09 ` Michael R. Hines
2013-06-06 23:51 ` Chegu Vinod
2013-06-07 5:38 ` Michael R. Hines
2013-05-10 7:58 ` Paolo Bonzini
-- strict thread matches above, loose matches on Subject: below --
2013-04-24 19:00 mrhines
2013-04-24 21:50 ` Paolo Bonzini
2013-04-24 23:48 ` Michael R. Hines
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=518C26F6.5080009@linux.vnet.ibm.com \
--to=mrhines@linux.vnet.ibm.com \
--cc=anthony@codemonkey.ws \
--cc=chegu_vinod@hp.com \
--cc=knoel@redhat.com \
--cc=mrhines@us.ibm.com \
--cc=mst@redhat.com \
--cc=owasserm@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.