Ok, in trying to get my overall problem solved, valid answers to me may
include completely alternative ways of accomplishing my task. BTW, all
discussion below is on linux.
We have a SR152x with a array being exported that is 2.2t after ext3
formatting. This is mounted to a machine we use for VMWare Server such
that we can store some of our guests on the drive.
Well, we decided we would like to export some of this space back to our
guests without creating more virtual drives. BTW we have multiple VMWare
servers and don't want to rely on the guest being on a specific machine
to get access to drive space.
Anyways, this seems like a great thing to use flat files and vblade to
export the file back to the network for any vmware guest to connect to.
Problem I am experiencing is that when I connect vblade to eth1(vmnet2)
neither the vmware server hosting the vblade app nor any guests on that
server see the exported drive. The guests on the other vmware server can
see it fine. This has been tested with vblade-11 distributed by Debian
and vblade-14 from sf.
I was able to do some hacking around with sockaddr_ll.sll_pkttype in the
dial function in linux.c such that I could get the local vmware server
to see the exported drive, but not any of the guests.
I do know that guests with a bridged network interface with the outside
interface can see the SR and use it fine, so I know aoe can traverse
I am not certain if there is something more that could be done to the
socket or binding to make it more available to vmware, or if I will need
to go searching into their network driver to find a fault.
Also willing to explore other methods of getting at the storage that
don't include NFS or SAMBA/CIFS. Would have loved a clustered FS that
didn't think kernel panic was a good way of dealing with split brain.
From: Ed L. Cashin <ecashin@co...> - 2007-12-13 14:20:11
On Wed, Dec 12, 2007 at 04:13:35PM -0600, critch wrote:
> Ok, in trying to get my overall problem solved, valid answers to me may
> include completely alternative ways of accomplishing my task. BTW, all
> discussion below is on linux.
Hello. Would you mind please including version numbers for the VMware
and Linux kernel software that is involved?
Ed L Cashin <ecashin@...>