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

["James Harper" <james.harper@xxxxxxxxxxxxxxxx>]

My setup is:

Server1 - running vanilla debian install + vblade export. vblade is a
userspace app so the kernel doesn't need anything special. A single
partition is being exported, and while it is being used via lvm on the
xen machines, Server1 itself knows nothing about lvm.

Xen1 & Xen2 - running xen 2.0.6 with AoE compiled in. Boot via the
network as they are diskless. Both run lvm on /dev/etherd/e0.0. I need
to take care never to mount the same volume in more than one place. Bad
things happen if I do that (unfortunately I know this from experience!).
My volume names in lvm are things like 'mail-root', 'mail2-root',
'mail-swap', etc. the xen0 domains export those volumes to the other
domains. The other domains don't use AoE directly. Migration works well
as both xen machines can see all the lvm volumes.

One of the xen machines has a 1Gb network adapter and a 100Mb adapter.
The 1G has no ip address and is simply used for AoE. The other network
adapter uses vlan's to service 3 other networks.

The other xen machine has only two 100Mb adapters but is otherwise
configured much the same.

Hope that tells you what you want to know!

James

> -----Original Message-----
> From: Kristinn Soffanias Runarsson [mailto:soffanias@xxxxxxxxx]
> Sent: Monday, 25 July 2005 10:37
> To: James Harper
> Cc: Jeb Campbell; xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] AOE (Ata over ethernet) troubles on xen 2.0.6
> 
> Hi James, could you explain this setup in some detail?
> 
> Bestestest regards from Iceland
> 
> -soffi-
> 
> 
> On 7/23/05, James Harper <james.harper@xxxxxxxxxxxxxxxx> wrote:
> > 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.
> >


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel