All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jacob Gorm Hansen <jacob@melon.dk>
To: Xen-devel@lists.sourceforge.net
Cc: eric@diku.dk, eske@diku.dk
Subject: Truly Autonomous Migration
Date: Fri, 12 Nov 2004 01:03:06 +0100	[thread overview]
Message-ID: <4193FDBA.5070800@melon.dk> (raw)

hi,

I just had my first success at self-migrating a domain across two hosts, 
with absolutely no involvement from Xen or Domain0. On the sending side 
I have a self-migrating XenLinux 2.4, migrated by a small userspace 
process inside it, which reads a checkpoint from /dev/checkpoint and 
writes it to a TCP socket.

On the receiving side I have a small (the kernel binary is 25952 bytes) 
TCP stack and server in an unprivileged domain.  It receives the 
checkpoint, fixes up the pagetables, and jumps to the incoming data, 
which resumes there and has now been live-migrated to the new host.

Apart from the coolness-factor of being able to checkpoint and migrate 
oneself without outside involvement (as well as some performance 
benefits of not having to run with shadow page tables, though it has 
been a while since I made any direct comparisons against Ian's stuff), 
this to me seems to be good news for security.  If a machine can run 
without any privileged code facing the network, the attack surface and 
thus risk of compromise is greatly reduced.

I will make binaries available tomorrow, if anyone is interested in 
playing with this?  (Guess not, but at least I am having fun with this ;-))

Best,
Jacob


-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click

             reply	other threads:[~2004-11-12  0:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-12  0:03 Jacob Gorm Hansen [this message]
2004-11-15 18:35 ` Truly Autonomous Migration Tim Freeman
2004-11-16 13:12   ` Jacob Gorm Hansen

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=4193FDBA.5070800@melon.dk \
    --to=jacob@melon.dk \
    --cc=Xen-devel@lists.sourceforge.net \
    --cc=eric@diku.dk \
    --cc=eske@diku.dk \
    /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.