From: Avi Kivity <avi@redhat.com>
To: Thomas Besser <thomas.besser@kit.edu>
Cc: kvm@vger.kernel.org
Subject: Re: Live migration stops working...
Date: Tue, 18 Aug 2009 14:20:31 +0300 [thread overview]
Message-ID: <4A8A8E7F.9040909@redhat.com> (raw)
In-Reply-To: <h6dgrg$67c$1@ger.gmane.org>
On 08/18/2009 09:14 AM, Thomas Besser wrote:
> Avi Kivity wrote:
>
>> On 08/17/2009 04:57 PM, Thomas Besser wrote:
>>
>>> After "migrate -d tcp:192.168.0.2:4444" info says "migration completed",
>>> but "incoming" kvm machine dies.
>>>
>> What do you mean exactly by "dies"?
>>
> I'm starting the 'waiting' kvm process like this:
>
> /usr/bin/kvm -name testbench -vnc :5 -net
> nic,vlan=0,model=virtio,macaddr=00:08:15:00:09:95 -net
> tap,vlan=0,ifname=tap05,script=no -m 256 -drive
> file=/vm/testbench/testbench.raw,if=virtio,boot=on -daemonize -vga std -k
> de -tdf -incoming tcp:0:4444
>
> The resulting kvm process which is waiting for the incoming migration isn't
> there anymore after the migration command on the 'source' host.
>
Please run without -daemonize and capture stdio output, monitor output,
and/or core dump.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-08-18 11:20 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 [this message]
2009-08-18 12:07 ` Thomas Besser
2009-08-18 12:32 ` Avi Kivity
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=4A8A8E7F.9040909@redhat.com \
--to=avi@redhat.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 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.