xfs
[Top] [All Lists]

Re: vmware file locking problem:

To: Steve Lord <lord@xxxxxxx>
Subject: Re: vmware file locking problem:
From: pac@xxxxxxxxxxxxxx
Date: Wed, 16 May 2001 11:58:00 -0500
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <200105161529.f4GFTAf17647@jen.americas.sgi.com>; from lord@sgi.com on Wed, May 16, 2001 at 10:29:10AM -0500
References: <20010516101803.A32539@bistro.marx> <200105161529.f4GFTAf17647@jen.americas.sgi.com>
Reply-to: pac@xxxxxxxxxxxxxx
Sender: owner-linux-xfs@xxxxxxxxxxx
User-agent: Mutt/1.3.17i
> It appears that vmware has hardcoded filesystem recognition code, and
> it does not recognize xfs. The 0x58465342 number is the magic number
> out of the xfs superblock which is returned in f_type by statfs
>  'BSFX' or 'XFSB' on a little endian box.
> 
> I know there are people on the list who have vmware working on XFS,
> Tom Duffy being one of them. He is in California so you will have to
> wait a few hours....
 
 I fixed the problem. I misunderstood the definition of "config" file.
 My earlier failed attempt where to modify ~/.vmware/preferences
  and /path/to/vmware/data/nt4.cfg 

 Solution:
 
 0. Drink a strong cup of Expresso

 1. Add the following line to /etc/vmware/config: 
    host.FSSupportLocking1 = 0x58465342

 2. Start vmware

  -Phil C.
.---------------------------------------------------------
| P. A. Carinhas, Ph.D.        |  pac@xxxxxxxxxxxxxx      |
| Fortuitous Technologies Inc. |  http://fortuitous.com   |
| Linux Training Services      |  Tel : 1-512 467-2154    |
| Contract, In-house, & Onsite |  800 : 1-877 467-2154    |
 ---------------------------------------------------------

<Prev in Thread] Current Thread [Next in Thread>