virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: James Morris <jmorris@namei.org>, Don Mullis <dwm@meer.net>,
	Tony Breeds <tony@bakeyournoodle.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Cc: virtualization <virtualization@lists.osdl.org>
Subject: lhype progress...
Date: Thu, 16 Nov 2006 21:36:16 +1100	[thread overview]
Message-ID: <1163673377.9585.15.camel@localhost.localdomain> (raw)

Hi all,

	Some of you know I've been working on a trivial in-kernel hypervisor to
demonstrate paravirt_ops.  The good news is that it works!  (And not
just for me!)  The bad news is that I haven't written any documentation
and now I'm going to be offline (moving to a farm) for several weeks.

	Nonetheless, if you're the kind of person who wants to poke around with
hypervisors, no doubt you can figure it out.  Tony Breeds might even
write a HOWTO.  There's certainly a lot to be done (see FIXMEs in the
code for example).  Console device, block device and inter-domain
networking all work.  From here it should be easy 8)

	So, you can download the patch "lhype.patch" from the paravirt
mercurial patch queue.  It should apply by itself to a recent -mm tree.

	http://ozlabs.org/~rusty/paravirt

Thanks, and have fun playing!
Rusty.

             reply	other threads:[~2006-11-16 10:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-16 10:36 Rusty Russell [this message]
2006-11-17  0:45 ` lhype progress James Morris
2006-11-27 23:37   ` [PATCH] lhype: Add TLS support James Morris
2006-11-29  5:37     ` Rusty Russell
2006-11-30  0:50       ` Rusty Russell
2006-12-07 16:37         ` James Morris

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=1163673377.9585.15.camel@localhost.localdomain \
    --to=rusty@rustcorp.com.au \
    --cc=dwm@meer.net \
    --cc=jmorris@namei.org \
    --cc=sfr@canb.auug.org.au \
    --cc=tony@bakeyournoodle.com \
    --cc=virtualization@lists.osdl.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;
as well as URLs for NNTP newsgroup(s).