From: Steve Traugott <stevegt@TerraLuna.Org>
To: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: QLogic Fibre Channel HBA Support
Date: Mon, 5 Jul 2004 11:24:26 -0700 [thread overview]
Message-ID: <20040705182426.GG18863@pathfinder> (raw)
In-Reply-To: <E1BhDww-0002nj-00@mta1.cl.cam.ac.uk>
On Sun, Jul 04, 2004 at 09:50:57PM +0100, Ian Pratt wrote:
> > I'd need to use the iSCSI in domain 0 approach (other people's
> > guests...), haven't tried it due to lack of hardware targets, didn't get
> > warm fuzzies from Ardistech's code -- you've had no problems with it
> > though?
>
> I've mainly used a NetApp filer h/w target, so I haven't really
> got enough experience to says whether the Ardistech code is
> stable or not. There's always enbd, nbd, gnbd which are all
> simple enough to believe that they work...
I can see how that works using initrd to mount *nbd as root in guest
domains, but what about using *nbd in dom0 and then allocating that as
VDs to the other domains? Is that supposed to work? I remember
something about needing physical raw partitions for VBDs, at least under
1.2. Am I missing something?
(For anyone curious, if using *nbd I would need to keep it in dom0,
rather than in each guest, for both security and maintainability. For a
public Xenoserver, uid 0 on the guests is assumed to be untrusted.)
Steve
--
Stephen G. Traugott (KG6HDQ)
UNIX/Linux Infrastructure Architect, TerraLuna LLC
stevegt@TerraLuna.Org
http://www.stevegt.com -- http://Infrastructures.Org
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
next prev parent reply other threads:[~2004-07-05 18:24 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-04 8:38 QLogic Fibre Channel HBA Support Steve Traugott
2004-07-04 9:02 ` Keir Fraser
2004-07-04 19:47 ` Steve Traugott
2004-07-04 9:11 ` Ian Pratt
2004-07-04 20:31 ` Steve Traugott
2004-07-04 20:50 ` Ian Pratt
2004-07-05 18:24 ` Steve Traugott [this message]
2004-07-05 18:48 ` Wim Coekaerts
2004-07-05 20:22 ` Ian Pratt
2004-07-05 20:14 ` Ian Pratt
2004-07-05 22:53 ` Steve Traugott
2004-07-05 23:23 ` Ian Pratt
2004-07-05 9:40 ` Niraj Tolia
2004-07-05 10:11 ` Ian Pratt
-- strict thread matches above, loose matches on Subject: below --
2004-07-05 4:39 Brian Wolfe
[not found] <200407050431.i654VV130769@roton.TerraLuna.Org>
2004-07-05 18:33 ` Steve Traugott
2004-07-05 20:19 ` Ian Pratt
2004-07-05 22:02 ` Steve Traugott
2004-07-05 18:54 Brian Wolfe
[not found] <200407051852.i65IqL124320@roton.TerraLuna.Org>
2004-07-05 22:12 ` Steve Traugott
2004-07-06 3:40 Brian Wolfe
[not found] <200407060323.i663Nl107730@roton.TerraLuna.Org>
2004-07-06 5:06 ` Steve Traugott
2004-07-06 6:22 ` Keir Fraser
2004-07-06 7:26 ` Ian Pratt
2004-07-06 12:53 ` Steve Traugott
2004-07-06 13:31 ` Ian Pratt
2004-07-06 13:59 ` Steve Traugott
2004-07-06 14:21 ` Ian Pratt
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=20040705182426.GG18863@pathfinder \
--to=stevegt@terraluna.org \
--cc=Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.sourceforge.net \
/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.