From: Avi Kivity <avi@redhat.com>
To: Thomas Besser <thomas.besser@kit.edu>
Cc: kvm@vger.kernel.org, Anthony Liguori <aliguori@us.ibm.com>
Subject: Re: Live migration stops working...
Date: Tue, 18 Aug 2009 15:32:29 +0300 [thread overview]
Message-ID: <4A8A9F5D.6090205@redhat.com> (raw)
In-Reply-To: <h6e5im$1kt$1@ger.gmane.org>
On 08/18/2009 03:07 PM, Thomas Besser wrote:
> Avi Kivity wrote:
>
>> On 08/18/2009 09:14 AM, Thomas Besser wrote:
>>
>> Please run without -daemonize and capture stdio output, monitor output,
>> and/or core dump.
>>
> Output from the starting shell:
> Guest moved used index from 23 to 3995
>
>
virtio issue. What's the guest kernel version?
> Because the whole kvm process dies no vnc output can be captured. Or did you
> mean something else with "monitor output"?
>
The monitor where you issue the migrate command (unless you're using a
management application like virt-manager or virsh).
> Howto produce more debug informations (i.e. core dump)?
>
'ulimit -c unlimited' before running qemu. But in this case you won't
get a dump since qemu exited cleanly.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-08-18 12:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-17 13:57 Live migration stops working Thomas Besser
2009-08-17 15:01 ` Avi Kivity
2009-08-17 17:15 ` Stephane Bakhos
2009-08-17 18:03 ` Avi Kivity
2009-08-17 18:12 ` Stephane Bakhos
2009-08-17 19:12 ` Andre Przywara
2009-08-18 8:11 ` Live migration stops working... (SEGFAULT) Stephane Bakhos
2009-08-18 12:12 ` Avi Kivity
2009-08-19 5:54 ` Stephane Bakhos
2009-08-18 6:14 ` Live migration stops working Thomas Besser
2009-08-18 11:20 ` Avi Kivity
2009-08-18 12:07 ` Thomas Besser
2009-08-18 12:32 ` Avi Kivity [this message]
2009-08-18 13:05 ` Thomas Besser
2009-08-18 13:28 ` Thomas Besser
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=4A8A9F5D.6090205@redhat.com \
--to=avi@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=thomas.besser@kit.edu \
/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).