[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] reporting 9pfs init errors
From: |
Aneesh Kumar K.V |
Subject: |
Re: [Qemu-devel] reporting 9pfs init errors |
Date: |
Tue, 26 Aug 2014 11:35:00 +0530 |
User-agent: |
Notmuch/0.18.1 (http://notmuchmail.org) Emacs/24.3.91.1 (x86_64-unknown-linux-gnu) |
Michael Tokarev <address@hidden> writes:
> Hello.
>
> I've a bugreport against debian qemu package which basically
> states that 9pfs does not work. After some digging it turned
> out to be error reporting problem, plain and simple. The
> error message is:
>
> qemu-system-x86_64: -device
> virtio-9p-pci,id=fs0,fsdev=fsdev-fs0,mount_tag=pwk,bus=pci.0,addr=0x7:
> Virtio-9p Failed to initialize fs-driver with id:fsdev-fs0 and export
> path:/home/stevie/Documents/PWK
> qemu-system-x86_64: -device
> virtio-9p-pci,id=fs0,fsdev=fsdev-fs0,mount_tag=pwk,bus=pci.0,addr=0x7: Device
> initialization failed.
> qemu-system-x86_64: -device
> virtio-9p-pci,id=fs0,fsdev=fsdev-fs0,mount_tag=pwk,bus=pci.0,addr=0x7: Device
> 'virtio-9p-pci' could not be initialized
>
> and the actual problem is that the path is not accessible from
> libvirt-spawned qemu due to permission denied (EPERM) error
> returned from statfs() call.
I have run into that issue once and really wanted to improve the error
handling during startup. I guess we have better error handling during
runtime, ie, file system related errors are correctly mapped and
send to guest. We could definitely imporve our init error handling.
-aneesh