Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 1710299[details]
virtio-fs logs
Description of problem:
as $subject
Version-Release number of selected component (if applicable):
qemu-kvm-5.0.0-2.module+el8.3.0+7379+0505d6ca
kernel-4.18.0-227.el8.x86_64
seabios-1.13.0-1.scrmod+el8.3.0+7493+a5e196a4.x86_64
virtio-win-prewhql-186
How reproducible:
100%
Steps to Reproduce:
1. start virtiofsd daemon on host
#/usr/libexec/virtiofsd --socket-path=/tmp/vhostqemu2 -o source=/home/virtiofs_test3 -o cache=none -d
2. boot up win832 guest with virtiofs device.
-m 4096 \
-object memory-backend-file,id=mem,size=4G,mem-path=/dev/shm112,share=on \
-numa node,memdev=mem \
-chardev socket,id=char0,path=/tmp/vhostqemu2 \
-device vhost-user-fs-pci,chardev=char0,tag=myfs2,bus=pci.7 \
3. install winfsp tool and virtiofs driver in guest
4. copy winfsp-x86.dll(winfsp program provided) and virtiofs.exe to the same dir
5. run virtiofs.exe in the dir.
virtiofs.exe -d -1 -D -
6. open computer in guest and see a new virtioFS(z:) volume is shown.
7. try to open z:\
Actual results:
failed to open z:\
error:
Z:\ refers to a location that is unavailable
Expected results:
Can open the shared file system and do write/read operation
Additional info:
Update viriofsd debug log, event viewer log and virtiofs.exe debug log in attachment.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (virtio-win bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHEA-2020:4840
Created attachment 1710299 [details] virtio-fs logs Description of problem: as $subject Version-Release number of selected component (if applicable): qemu-kvm-5.0.0-2.module+el8.3.0+7379+0505d6ca kernel-4.18.0-227.el8.x86_64 seabios-1.13.0-1.scrmod+el8.3.0+7493+a5e196a4.x86_64 virtio-win-prewhql-186 How reproducible: 100% Steps to Reproduce: 1. start virtiofsd daemon on host #/usr/libexec/virtiofsd --socket-path=/tmp/vhostqemu2 -o source=/home/virtiofs_test3 -o cache=none -d 2. boot up win832 guest with virtiofs device. -m 4096 \ -object memory-backend-file,id=mem,size=4G,mem-path=/dev/shm112,share=on \ -numa node,memdev=mem \ -chardev socket,id=char0,path=/tmp/vhostqemu2 \ -device vhost-user-fs-pci,chardev=char0,tag=myfs2,bus=pci.7 \ 3. install winfsp tool and virtiofs driver in guest 4. copy winfsp-x86.dll(winfsp program provided) and virtiofs.exe to the same dir 5. run virtiofs.exe in the dir. virtiofs.exe -d -1 -D - 6. open computer in guest and see a new virtioFS(z:) volume is shown. 7. try to open z:\ Actual results: failed to open z:\ error: Z:\ refers to a location that is unavailable Expected results: Can open the shared file system and do write/read operation Additional info: Update viriofsd debug log, event viewer log and virtiofs.exe debug log in attachment.