public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Bareiro <daniel-listas@gmx.net>
To: KVM General <kvm@vger.kernel.org>
Subject: Re: VM terminates when doing a live migration
Date: Sun, 22 May 2011 03:41:15 -0300	[thread overview]
Message-ID: <20110522064115.GC2699@defiant.freesoftware> (raw)
In-Reply-To: <Pine.LNX.4.64.1105212337400.14697@unix38.andrew.cmu.edu>

[-- Attachment #1: Type: text/plain, Size: 1902 bytes --]

Hi, Michael.

On Saturday, 21 May 2011 23:39:27 -0400,
Michael Stroucken wrote:

>> I'm doing some testing with KVM Live Migration. SS01 (VMHost) has
>> Debian GNU/Linux 6.0.1 and Defiant (VMHost) has Debian GNU/Linux
>> 5.0.8. Defiant has Linux 2.6.32-15~bpo50+1 and 0.12.5+dfsg-3~bpo50+2,
>> and SS01 has Linux 2.6.32-31 and 0.12.5+dfsg-5+squeeze1. Both
>> instalation are 32-bit, but the kernel in SS01 is amd64 and the
>> kernel in Defiant is 686.
>>
>> Migration from Defiant to SS01 is completed successfully, but when
>> trying to migrate a VM from SS01 to Defiant, the VM terminates
>> (segfault?). This is due to the difference in the kernel of each
>> VMHost?

> Can you try saving the vms state to a file on ss01 and restoring it on  
> defiant?

I tried following your suggestion but same thing happens:

ss01:~# kvm -m 256 -boot d -net nic,vlan=0,macaddr=52:54:67:92:9d:63 \
 -net tap -daemonize -vnc :15 -k es -localtime -cdrom \
 /mnt/systemrescuecd-x86-2.0.1.iso -monitor telnet:localhost:4055,server,nowait

ss01:~# telnet localhost 4055
Trying ::1...
Connected to localhost.
Escape character is '^]'.
QEMU 0.12.5 monitor - type 'help' for more information
(qemu) stop
(qemu) migrate_set_speed 4095m
(qemu) migrate "exec:gzip -c > STATEFILE.gz"
Connection closed by foreign host.

ss01:~# ps ax|grep systemrescuecd
26564 pts/0    S+     0:00 grep systemrescuecd


It appears that the 'migrate' command causes termination of the virtual
machine to these parameters as well.

> Do migrations between ss01 and another amd64 box work?

I have not tried a migration where both source and destination have the
same characteristics (i386 installation and amd64 kernel).


Thanks for your reply.

Regards,
Daniel
-- 
Fingerprint: BFB3 08D6 B4D1 31B2 72B9  29CE 6696 BF1B 14E6 1D37
Powered by Debian GNU/Linux Lenny - Linux user #188.598

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

      reply	other threads:[~2011-05-22  6:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-22  1:21 VM terminates when doing a live migration Daniel Bareiro
2011-05-22  3:39 ` Michael Stroucken
2011-05-22  6:41   ` Daniel Bareiro [this message]

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=20110522064115.GC2699@defiant.freesoftware \
    --to=daniel-listas@gmx.net \
    --cc=dbareiro@gmx.net \
    --cc=kvm@vger.kernel.org \
    /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