And maybe you should use lsetxattr and lgetxattr instead of the symlink resolving versions setxattr and getxattr
-- VirtFS mapped symlinks resolved wrong https://bugs.launchpad.net/bugs/646427 You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. Status in QEMU: New Bug description: I tried to map a folder with qemu-kvm qemu-kvm-0.13.0-rc1-3-gc9c2179 (this is v0.13.0-rc1-16667-gc9c2179). I mounted it first in passthrough mode and saw all symlinks as expected. Then I used mapped and noticed that the target of a symlink changed to the actual data inside the linked folder as target instead of the target filename. So for example if you have a file abc with the content "omg, this is important stuff" and a symlink lnkme -> abc then it wiill look inside the kvm with mounted 9p virtio (mapped) like that: lnkme -> omg, this is important stuff Another problem I noticed was that I cannot mount it (mapped or passthrough) using /etc/rc.local or /etc/fstab, but after login as root using mount /mnt or mount -t 9p -o trans=virtio host_share /mnt (the same stuff i tried inside /etc/rc.local) The only output on a failed mount in rc.local/fstab I get is [ 15.035920] device: '9p-1': device_add [ 15.038180] 9p: no channels available [ 15.038937] device: '9p-1': device_unregister [ 15.049123] device: '9p-1': device_create_release
