-
Bug
-
Resolution: Done
-
Minor
-
None
-
None
-
Low
-
rhel-sst-virtualization-storage
-
ssg_virtualization
-
3
-
False
-
-
None
-
None
-
None
-
RegressionOnly
-
None
What were you trying to do that didn't work?
The error info of virtiofsd is not clear when the shared directory does not exist. It indicates that "Error creating sandbox", users maybe confused of how does it have anyting to do with sandbox.
Please provide the package NVR for which bug is seen:
virtiofsd-1.10.1-1.el9.x86_64
qemu-kvm-8.2.0-4.el9
kernel-5.14.0-425.el9.x86_64
How reproducible:
100%
Steps to reproduce
#/usr/libexec/virtiofsd --socket-path /home/test.sock --shared-dir /home/xxxxx/ --cache auto
Note:
The shared directory /home/xxxxx/ does not exist.
Expected results
More clear info like qemu-kvm below to specify that "Could not open '/home/xxxxxx/': No such file or directory"
#/usr/libexec/qemu-kvm -hda ./test.img
qemu-kvm: -hda ./test.img: Could not open './test.img': No such file or directory
Actual results
/usr/libexec/virtiofsd --socket-path /home/test.sock --shared-dir /home/xxxx/ --cache auto
[2024-02-28T07:42:18Z ERROR virtiofsd] Error creating sandbox: No such file or directory (os error 2)
- is blocked by
-
RHEL-47989 Rebase virtiofsd to latest version for RHEL 9.5
- Closed
- links to