From: Jeb Campbell <jebc@c4solutions.net>
To: xen-devel@lists.xensource.com
Subject: AOE (Ata over ethernet) troubles on xen 2.0.6
Date: Fri, 22 Jul 2005 10:50:41 -0500 [thread overview]
Message-ID: <42E115D1.1060204@c4solutions.net> (raw)
I understand that all work is going into xen3, but I had wanted to note
that aoe (drivers/block/aoe) is giving me trouble on xen 2.0.6 (so we
can keep and eye on xen3).
Specifically I can't see nor export AOE devices. As a quick background
on AOE, it is not IP (not routable, etc), but works with broadcasts and
packets to MAC addresses (see http://www.coraid.com).
(for anyone who wants to test or play)
In my dom0 (w/ aoe module), I installed aoetools and vblade (
http://aoetools.sourceforge.net ). aoetools are not necessary, but
nice. vblade lets you export a block device to the network.
I exported an lvm device (worked fine on non xen machine) with:
vblade 2 0 eth0 (2 is shelf number and 0 is slot number -- can be anything).
If I export from non-xen, it shows up on other machines as
/dev/etherd/e2.0, but the xen machine can't see it when others export
either. (Note, vblades from your own machine don't show up in your
/dev/etherd/ -- only on other hosts)
As this is dom0, I'm not sure why the aoe module is not seeing the
packets (unless the bridge is messing it up). Any tips for debugging
this would be appreciated -- I don't really care if we get this working
in xen2, but I think this is important for xen3.
Thanks for your time,
--
Jeb Campbell
jebc@c4solutions.net
next reply other threads:[~2005-07-22 15:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-22 15:50 Jeb Campbell [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-23 6:13 AOE (Ata over ethernet) troubles on xen 2.0.6 James Harper
2005-07-25 0:36 ` Kristinn Soffanias Runarsson
2005-07-25 1:16 James Harper
2005-07-25 14:42 ` Jeb Campbell
2005-07-25 15:27 ` Avi Kivity
2005-07-25 15:01 ` Mark Williamson
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=42E115D1.1060204@c4solutions.net \
--to=jebc@c4solutions.net \
--cc=xen-devel@lists.xensource.com \
/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.