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:
Creating a file on a folder in shared volume, and then try to create symbolic link for the file, it shows "The parameter is incorrect."
Version-Release number of selected component (if applicable):
qemu-kvm-6.0.0-29.module+el8.5.0+12386+43574bac.x86_64
kernel-4.18.0-329.el8.x86_64
virtio-win-prewhql-0.1-207
How reproducible:
100%
Steps to Reproduce:
1.boot up win10-64 guest with virtiofs device
(host)# /usr/libexec/virtiofsd --socket-path=/tmp/socket1 -o source=/home/test
(host)/usr/libexec/qemu-kvm \
-object memory-backend-file,size=4G,mem-path=/dev/shm,share=yes,id=mem-mem1 \
-smp 24,maxcpus=24,cores=12,threads=1,dies=1,sockets=2 \
-numa node,memdev=mem-mem1,nodeid=0 \
-chardev socket,id=char_virtiofs_fs,path=/tmp/socket1 \
-device vhost-user-fs-pci,id=vufs_virtiofs_fs,chardev=char_virtiofs_fs,tag=myfs,queue-size=1024,bus=pcie_extra_root_port_0 \
2.install virtiofs driver and winfsp installer in guest.
3.start virtiofs service via run virtiofs.exe and get a new Z: volume
4.creat folder in z: and create a file in that folder
Z:\>md folder
Z:\>echo test > folder\a.txt
Z:\>echo test > b.txt
5.create symbolic links for the folder and file
Z:\>mklink /d folder-link folder
symbolic link created for folder-link <<===>> folder
Z:\>type folder-link\a.txt
test
Z:\>mklink b-link b.txt
symbolic link created for b-link <<===>> b.txt
Z:\>type b-link
test
Z:\>cd folder
Z:\folder>mklink a-link a.txt
The parameter is incorrect.
Actual results:
can't create symbolic links for the file in a folder
Expected results:
can create symbolic links for a file in a folder.
Additional info:
Comment 1Yvugenfi@redhat.com
2022-10-18 11:21:53 UTC
Verify this bug on virtio-win-prewhql-228.
Verify steps:
A:\>md folder
A:\>cd folder
A:\folder>mklink a-link a.txt
symbolic link created for a-link <<===>> a.txt
----->Success to make symbolic link for files in sub-folder of mounted volume.
Thanks all.
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/RHBA-2023:2451
Description of problem: Creating a file on a folder in shared volume, and then try to create symbolic link for the file, it shows "The parameter is incorrect." Version-Release number of selected component (if applicable): qemu-kvm-6.0.0-29.module+el8.5.0+12386+43574bac.x86_64 kernel-4.18.0-329.el8.x86_64 virtio-win-prewhql-0.1-207 How reproducible: 100% Steps to Reproduce: 1.boot up win10-64 guest with virtiofs device (host)# /usr/libexec/virtiofsd --socket-path=/tmp/socket1 -o source=/home/test (host)/usr/libexec/qemu-kvm \ -object memory-backend-file,size=4G,mem-path=/dev/shm,share=yes,id=mem-mem1 \ -smp 24,maxcpus=24,cores=12,threads=1,dies=1,sockets=2 \ -numa node,memdev=mem-mem1,nodeid=0 \ -chardev socket,id=char_virtiofs_fs,path=/tmp/socket1 \ -device vhost-user-fs-pci,id=vufs_virtiofs_fs,chardev=char_virtiofs_fs,tag=myfs,queue-size=1024,bus=pcie_extra_root_port_0 \ 2.install virtiofs driver and winfsp installer in guest. 3.start virtiofs service via run virtiofs.exe and get a new Z: volume 4.creat folder in z: and create a file in that folder Z:\>md folder Z:\>echo test > folder\a.txt Z:\>echo test > b.txt 5.create symbolic links for the folder and file Z:\>mklink /d folder-link folder symbolic link created for folder-link <<===>> folder Z:\>type folder-link\a.txt test Z:\>mklink b-link b.txt symbolic link created for b-link <<===>> b.txt Z:\>type b-link test Z:\>cd folder Z:\folder>mklink a-link a.txt The parameter is incorrect. Actual results: can't create symbolic links for the file in a folder Expected results: can create symbolic links for a file in a folder. Additional info: