Michael Tokarev <m...@tls.msk.ru> writes: > Rehashing an old thread again... > > 28.02.2013 21:25, M. Mohan Kumar wrote: >> Michael Tokarev <m...@tls.msk.ru> writes: >> >> >>> 28.02.2013 17:55, M. Mohan Kumar wrote: >>>> Michael Tokarev <m...@tls.msk.ru> writes: >>>> >>>> Hi, >>>> >>>> Please try mounting with -oversion=9p2000.L >>>> >>>> With qemu-1.4.0 and 9p2000.L, I could not recreate this issue. ie not >>>> getting Unknown error during directory listing. >>> >>> Yes, with 9p2000.L it works fine, both reported >>> issues are gone. >>> >>>> I am using Guest kernel 3.8.0-rc5+. >>> >>> But do you see my original error, with the default mount version? >>> (I'm using 3.2 guest kernel if that matters, and it is also 32bits, >>> which should not matter). >> Yes, with default mount option, i am getting same error. > > So, is there any intention to fix that for the default mount > options? Or should the corresponding protocol be just marked > as broken and qemu to refuse its usage? I think it is either > one or another, -- either fix or drop, that is, keeping > known-broken behavor isn't exactly the right thing.
I am trying to reproduce this. I guess there is some part of config i am missing I have export path /tmp/ and is exported via -virtfs local,path=/tmp/,mount_tag=v_tmp,security_model=mapped-file There is not .virtfs_metadata directory in /tmp/ in /tmp/ i have test/test2 with ls -ald test/test2 dr-xr-xr-x 2 kvaneesh kvaneesh 4096 May 20 15:20 test/test2 Now i am mounting the same via mount -t 9p -oversion=9p2000.u,ro v_tmp /mnt root@qemu-guest:~# ls -al /mnt/test/test2/ total 8 dr-xr-xr-x 2 virtfs virtfs 4096 May 20 15:20 . drwxr-xr-x 3 virtfs virtfs 4096 May 20 15:00 .. -r--r--r-- 1 virtfs virtfs 0 May 20 15:20 k Any idea what i am missing ? -aneesh
