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.
Description of problem: virtio.exe quit during running iozone test on the shared directory iozone.exe -az -g 1g -y 32k -i 0 -i 1 -f Z:\zzz -b C:\yyy Version-Release number of selected component (if applicable): qemu-kvm-6.1.0-6.el9.x86_64 kernel-5.14.0-5.el9.x86_64 winfsp1.7.20172 virtio-win-prewhql-0.1-214 How reproducible: 100% Steps to Reproduce: 1.start virtiofsd on host # /usr/libexec/virtiofsd --socket-path=/tmp/sock1 -o source=/home/test,cache=none 2.boot up win2019 guest with virtiofs device -chardev socket,id=char0,path=/tmp/sock1 \ -device vhost-user-fs-pci,chardev=char0,tag=myfs_11,bus=pci.11,queue-size=1024,id=dev_virtiofs_fs \ -object memory-backend-file,id=mem,size=4G,mem-path=/dev/shm,share=on \ -numa node,memdev=mem \ 3.install winfsp and virtiofs driver on guest 4.submit iozone test. C:\Program Files (x86)\Benchmarks\Iozone3_414>iozone.exe -az -g 1g -y 32k -i 0 -i 1 -f Z:\zzz -b C:\yyy Actual results: 1)iozone fail 4096 256 55691 57316 83605 86866 4096 512 87909 82914 125441 137321 4096 1024 112109 116315 158892 154755 4096 2048 123702 123650 219642 224457 4096 4096 119555 127790 Error reading block 0 fed00000 read: Permission denied 2)virtiofs.exe quit on guest. *** Read: BytesTransferred: 32768 virtiofs[TID=0a54]: FFFFE68B19620E50: <<Read IoStatus=0[32768] virtiofs[TID=0a54]: FFFFE68B168ECE50: >>Read 0000000000000000:000001B452C07BF0, Address=000001B452BB0000, Offset=0:f000, Length=32768, Key=0 *** Read: Offset: 61440 Length: 32768 *** Read: fh: 21 nodeid: 342 *** VirtFsFuseRequest: >>req: 15 unique: 9119 len: 32808 *** VirtFsFuseRequest: <<len: 32784 error: 0 unique: 9119 *** Read: BytesTransferred: 32768 virtiofs[TID=0a54]: FFFFE68B168ECE50: <<Read IoStatus=0[32768] virtiofs[TID=0a54]: FFFFE68B16818E50: >>Read 0000000000000000:000001B452C07BF0, Address=000001B4549A0000, Offset=0:0, Length=4194304, Key=0 *** Read: Offset: 0 Length: 4194304 *** Read: fh: 21 nodeid: 342 *** VirtFsFuseRequest: >>req: 15 unique: 9120 len: 4194344 *** VirtFsFuseRequest: <<len: 0 error: 0 unique: 0 *** VirtFsFuseRequest: Bytes Returned: 0 Expected: 4194320 virtiofs[TID=1038]: FFFFE68B18CAAE50: >>Create [UTB--C] "\zzz", FILE_OPEN, CreateOptions=214040, FileAttributes=0, Security=NULL, AllocationSize=0:0, AccessToken=0000000000000264[PID=a84], DesiredAccess=0, GrantedAccess=80, ShareAccess=7 *** GetSecurityByName: "\zzz" *** VirtFsFuseRequest: >>req: 1 unique: 9121 len: 44 *** VirtFsFuseRequest: <<len: 144 error: 0 unique: 9121 *** SubmitLookupRequest: nodeid=342 ino=3721811