[9p] chown: changing ownership of 'xxx': Operation not permitted

[nulllpoint]

Description

I read the issuse #231 , has it been solved now?

I use podman by lima-vm, container is mysql/mysql-server, it need chown mysql:mysql xxx, but when use -v mapping host's dir , propmpt chown: changing ownership of 'xxx': Operation not permitted
macos version: 12.6
lima version: 0.13.0
qemu version: 7.1.0
lima's yaml config:

mountType: 9p
mounts:
- location: "/Users/xxx/lima_workspace/podman"
  writable: true
  9p:
    cache: mmap

mysql docker hub:

docker hub : https://hub.docker.com/r/mysql/mysql-server
fetch cmd: docker pull mysql/mysql-server:8.0.21

I also try to use chown directly in lima-vm, neither.

[xxx@lima-test test]$ sudo groupadd test
[xxx@lima-test test]$ sudo useradd -g test test
[xxx@lima-test test]$ ll
drwxr-xr-x. 4 xxx games 128 Nov 16 08:55 mysql
drwxrwxr-x. 2 xxx games  64 Nov 16 08:48 test
[xxx@lima-test test]$ chown test:test test
chown: changing ownership of 'test': Operation not permitted

[AkihiroSuda]

lima/examples/default.yaml

Lines 74 to 78 in c3e82cc

	9p:
	# Supported security models are "passthrough", "mapped-xattr", "mapped-file" and "none".
	# "mapped-xattr" and "mapped-file" are useful for persistent chown but incompatible with symlinks.
	# 🟢 Builtin default: "none" (since Lima v0.13)
	securityModel: null

securityModel: "mapped-xattr" enables chown, but incompatible with symlinks

[nulllpoint]

lima/examples/default.yaml

Lines 74 to 78 in c3e82cc

	9p:
	# Supported security models are "passthrough", "mapped-xattr", "mapped-file" and "none".
	# "mapped-xattr" and "mapped-file" are useful for persistent chown but incompatible with symlinks.
	# 🟢 Builtin default: "none" (since Lima v0.13)
	securityModel: null

securityModel: "mapped-xattr" enables chown, but incompatible with symlinks

Thank you for your reply, but it still seems to be unresolved.
That is my lima.conf, pass the limactl validate

mountType: "9p"
mounts:
- location: "/Users/xxx/lima_workspace/test"
  writable: true
  9p:
    cache: "mmap"
    securityModel: "mapped-xattr"
- location: "/tmp/lima"
  writable: true

---

The above is useful. When I recreated lima's vm, the problem was solved,
This problem has bothered me for almost two days, hahhhh....
Great lima vm !!!