-
Bug
-
Resolution: Unresolved
-
Normal
-
rhel-9.5
-
virtio-win-1.9.48-0.el10
-
None
-
Moderate
-
1
-
rhel-virt-windows
-
ssg_virtualization
-
5
-
QE ack
-
False
-
False
-
-
None
-
Red Hat Enterprise Linux
-
RHEL-10.2 Pending
-
Pass
-
virtio-win-prewhql-0.1-283
-
New Test Coverage
-
-
x86_64
-
Windows
-
None
What were you trying to do that didn't work?
Create a virtiofs service and specify the mount point to X: in binpath, after starting the virtiofs service, the volume letter is still Z:.
So, there is a mismatch of the configuration in the registry and in CLI.
Please provide the package NVR for which bug is seen:
virtio-win-prewhql-0.1-255
kernel-5.14.0-437.el9.x86_64
seabios-bin-1.16.3-2.el9.noarch
edk2-ovmf-20240214-2.el9.noarch
qemu-kvm-core-8.2.0-11.el9_4.x86_64
virtiofsd-1.10.1-1.el9.x86_64
How reproducible:
always
Steps to reproduce
1. boot up a vm with a virtiofs device.
2. inside guest, install the Winfsp.msi and create a virtiofs service
sc create VFS-TEST-SVC binPath="C:\virtiofs.exe -t myfs1 -m x:" start=auto depend=VirtioFsDrv
[SC] CreateService SUCCESS
3. start VFS-TEST-SVC service and check the shared volume
Expected results
The volume should be the specified one, X:
Actual results
It's still z:
other info:
upstream issue: https://github.com/virtio-win/kvm-guest-drivers-windows/issues/1083
- links to
-
RHBA-2025:153011 virtio-win bug fix and enhancement update