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 15:53:30 -0700 [thread overview]
Message-ID: <20040705225330.GK18863@pathfinder> (raw)
In-Reply-To: <E1BhZqy-0008JF-00@mta1.cl.cam.ac.uk>
On Mon, Jul 05, 2004 at 09:14:15PM +0100, Ian Pratt wrote:
> You can, in principle, export anything that dom0 sees as a block
> device e.g. sda7, nbd0, vg0 as a block device in another domain
> e.g. sda1, hda1.
What about loop devices? Should they work? This lookup_raw_partn()
exception (in 1.2) might be what threw me off:
xendev1:~# dd if=/dev/zero of=/tmp/d0 bs=1M count=100
100+0 records in
100+0 records out
xendev1:~# losetup /dev/loop0 /tmp/d0
xendev1:~# xc_vd_tool.py initialise /dev/loop0 4
Formatting for virtual disks
Device: /dev/loop0
Extent size: 4MB
Traceback (most recent call last):
File "/usr/bin/xc_vd_tool.py", line 53, in ?
rc = XenoUtil.vd_format(dev, extent_size)
File "/usr/lib/python2.2/site-packages/XenoUtil.py", line 261, in vd_format
part_info = lookup_raw_partn(partition)[0]
TypeError: unsubscriptable object
> Hence, you should be able to implement the equivalent of Xen 1.2
> VDs just by using Linux's existing LVM mechanism.
I'm trying to picture how this would work -- LVM volume groups on top of
the dom0 VBDs, and then xc.vbd_create() to assign LVM logical volumes to
other domains?
> The current tools don't quite allow the full set of functionality
> that Xen implements, but adding support for LVM partitions should be
> easy.
What's missing?
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 22:53 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
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 [this message]
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=20040705225330.GK18863@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.