[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] AOE (Ata over ethernet) troubles on xen 2.0.6

  • To: "Jeb Campbell" <jebc@xxxxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
  • Date: Sat, 23 Jul 2005 16:13:33 +1000
  • Delivery-date: Sat, 23 Jul 2005 06:12:10 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcWO1UmaF0/fqOMDTs2Qfnt9tHI05gAd/aQA
  • Thread-topic: [Xen-devel] AOE (Ata over ethernet) troubles on xen 2.0.6

For what it's worth, I'm using aoe presently without any problems, and
have been for quite a few months now. In my setup I have vblade running
on a server, with dom0's on two machines reading the same aoe device,
and exporting lvm partitions to the different domains as required. This
allows migration to work nicely.

> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-devel-
> bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Jeb Campbell
> Sent: Saturday, 23 July 2005 01:51
> To: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-devel] AOE (Ata over ethernet) troubles on xen 2.0.6
> I understand that all work is going into xen3, but I had wanted to
> 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
> on AOE, it is not IP (not routable, etc), but works with broadcasts
> 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
> in xen2, but I think this is important for xen3.
> Thanks for your time,
> --
> Jeb Campbell
> jebc@xxxxxxxxxxxxxxx
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.