[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug 1673957] Re: virtfs: mapped-xattr on mount point

From: Thomas Huth
Subject: [Bug 1673957] Re: virtfs: mapped-xattr on mount point
Date: Tue, 10 Nov 2020 03:21:11 -0000

Thanks for your answer! ... since this is not reproducible anymore, I'm
closing the ticket now.

** Changed in: qemu
       Status: Incomplete => Won't Fix

You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

  virtfs: mapped-xattr on mount point

Status in QEMU:
  Won't Fix

Bug description:
    -virtfs local,path="/tmp",security_model=mapped-xattr,mount_tag="shared2"
  in the qemu command line,
    shared2 on /mnt/testbis type 9p 
  in the guest mount points, and
    tmpfs on /tmp type tmpfs (rw,nosuid,nodev)
  in the host mount points (with CONFIG_TMPFS_XATTR=y according to zgrep 
/proc/config.gz), running qemu as user "vm-test", trying to "touch a" in 
/mnt/testbis on the VM fails with "Operation not supported". In addition, no 
file or directory actually present in the host's /tmp can be seen in the 
guest's /mnt/testbis.

  When trying to replace "/tmp" with "/tmp/aaa" on the host, with
  /tmp/aaa owned by root:root, still running qemu as vm-test, trying to
  run "ls" in the guest's /mnt/testbis fails with the weird "ls: reading
  directory '.': Cannot allocate memory", while the directory is empty.

  After a "chown vm-test /tmp/aaa", the guest can list the files
  (despite the permissions already allowing it to do so before), but
  still not write new files: "cannot touch 'b': Operation not

  Do you have a pointer as to what is happening?

  PS: complete setup is running all this inside a qemu VM that I use for
  testing, I guess it shouldn't matter but saying it just in case

To manage notifications about this bug go to:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]