public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Stuart Sheldon <stu@actusa.net>
To: kvm@vger.kernel.org
Subject: Re: Live Migration KVM-84 Stock Vanilla 2.6.28.7
Date: Mon, 16 Mar 2009 19:15:06 -0700	[thread overview]
Message-ID: <49BF07AA.9070709@actusa.net> (raw)
In-Reply-To: <49BEEAD1.7040406@actusa.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Update on this...

The 32bit guests migrate fine if they are under low load. It looks like
the 64bit guests consistently become unresponsive during the migration.

Stu


Stuart Sheldon wrote:
> Hey all,
> 
> I started testing live migration and seem to have his a snag... It
> appears to only occasionally work. Here is my setup:
> 
> 2 Identical Machines:
> Intel(R) Xeon(R) CPU  3050  @ 2.13GHz
> 8G Ram
> Debian Lenny 64bit
> Vanilla 2.6.28.7 kernel (loading kernel modules, not KVM-84 modules)
> KVM-84
> 
> Both machines are attached to an NFS server for the guest files.
> 
> Trying to transfer hosts using virtio for net and controller. Guests are
> running 2.6.28.7 with KVM enhancement stuff built in.
> 
> host started with:
> /usr/local/kvm/bin/qemu-system-x86_64 -name lenny64/1
> -m1024 -nographic -monitor telnet:localhost:5501,server,nowait
> -serial telnet:localhost:5601,server,nowait
> -drivefile=/home/lenny64/hdisc.img,if=virtio,cache=writeback,boot=on
> -
> -netnic,macaddr=52:54:00:12:00:01,model=virtio-nettap,ifname=tap1,script=/etc/kvm/kvm-ifup-br0
> 
> -daemonize
> 
> Migration Host Started With
> host started with:
> /usr/local/kvm/bin/qemu-system-x86_64 -name lenny64/1
> -m1024 -nographic -monitor telnet:localhost:5501,server,nowait
> -serial telnet:localhost:5601,server,nowait
> -drivefile=/home/lenny64/hdisc.img,if=virtio,cache=writeback,boot=on
> -
> -netnic,macaddr=52:54:00:12:00:01,model=virtio-nettap,ifname=tap1,script=/etc/kvm/kvm-ifup-br0
> 
> -daemonize -incoming tcp:0:4601
> 
> Execute migrate tcp:migrationhost:4601
> 
> Sometimes it moves without a problem, other times the migrated host
> hangs without reponse...
> 
> Let me know what I can do to help fix this feature, or if I'm doing
> something wrong...
> 
> Thanks in advance,
> 
> Stu Sheldon
> ACT USA
> 
> 
- --
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

- --
Though it's cold and lonely in the deep dark night
I can see paradise by the dashboard light
           -- Meatloaf - "Paradise by the Dashboard Light - Lyrics"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkm/B6oACgkQK69Y+xPZrWaXkgCgjJjkCgKH3sFbnjRP0LpOtyj1
bIQAnjaSNfLI/QufHDWfnq0aTrCF1ioN
=iiY9
-----END PGP SIGNATURE-----

      reply	other threads:[~2009-03-17  2:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-17  0:12 Live Migration KVM-84 Stock Vanilla 2.6.28.7 Stuart Sheldon
2009-03-17  2:15 ` Stuart Sheldon [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=49BF07AA.9070709@actusa.net \
    --to=stu@actusa.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