From: "Eric Van Hensbergen" <ericvh@gmail.com>
To: weigelt@metux.de,
"Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Cc: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] xen -> direct 9p channel
Date: Wed, 7 May 2008 09:22:55 -0500 [thread overview]
Message-ID: <a4e6962a0805070722o5c0c0109ue821604ec0d3d0e2@mail.gmail.com> (raw)
In-Reply-To: <20080507140529.GB30633@nibiru.local>
This was done in the context of an internal IBM project with a now
ancient version of Xen. There was some share memory support added to
Inferno so it could act as a server. Until recently these were
available in my home machine's Inferno repository. A system reinstall
later and those public repositories are gone, but I should still have
the code in my IBM repositories.
However -- the better approach here would be to use virtio, but I'm
not what the current Xen stance is on virtio. All that being said,
you'd probably be better off looking at KVM or lguest versus Xen for
Plan 9 hosting (which support virtio).
-eric
On Wed, May 7, 2008 at 9:05 AM, Enrico Weigelt <weigelt@metux.de> wrote:
>
> Hi folks,
>
> I've found some discussions about an direct 9P channel in xen
> (so all devices can be served from dom0 via 9P, w/o hw emulation).
> Does anyone know some bit more about this ?
>
> cu
> --
> ---------------------------------------------------------------------
> Enrico Weigelt == metux IT service - http://www.metux.de/
> ---------------------------------------------------------------------
> Please visit the OpenSource QM Taskforce:
> http://wiki.metux.de/public/OpenSource_QM_Taskforce
> Patches / Fixes for a lot dozens of packages in dozens of versions:
> http://patches.metux.de/
> ---------------------------------------------------------------------
>
>
prev parent reply other threads:[~2008-05-07 14:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 14:05 Enrico Weigelt
2008-05-07 14:12 ` ron minnich
2008-05-07 14:22 ` Eric Van Hensbergen [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=a4e6962a0805070722o5c0c0109ue821604ec0d3d0e2@mail.gmail.com \
--to=ericvh@gmail.com \
--cc=9fans@9fans.net \
--cc=9fans@cse.psu.edu \
--cc=weigelt@metux.de \
/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).