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....
Steve
> Quoting from Zao Yang (zyang@xxxxxxxxxx):
> ---------------------------------------------------
>
> my home directory and the .vmware directory are on a XFS
> filesystem. when I start vmware 2.0.3, it complains about not being able
> to detect if file locking is supported on the filesystem. it wants me to
> put the following line in the configuration file:
>
> host.FSSupportLocking1 = 0x58465342
>
> I tried that. but vmware still complains with same message.
>
> vmware used to work when my home directory is on ext2 filesystem.
>
> I also tried vmware 2.0.4 and had same problem. does anyone know where
> the problems might be, and if vmware supports XFS?
>
> --------------------------------------------------------------
>
> I run vmware 2.0.4 and have the same trouble. Any ideas?
> I had my vmware on Reiser before XFS and it worked ok.
> Thanks,
>
> -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 |
> ---------------------------------------------------------
|