You are not logged in.
Pages: 1
Topic closed
Hi all,
I have a Windows 10 and a Windows 11 guest VMs. I am using the same command line to launch both. On Windows 10 I can read/write into the built-in SMB share at \\10.0.2.4\qemu while Windows 11 cannot find that location. I have an Internet connection on both VMs. Here is my starting command line:
qemu-system-x86_64 -enable-kvm -vga none -device qxl-vga,vgamem_mb=32 -device virtio-serial-pci -spice port=5930,disable-ticketing=on \
-device virtserialport,chardev=spicechannel0,name=com.redhat.spice.0 -chardev spicevmc,id=spicechannel0,name=vdagent -display spice-app \
-device ich9-usb-ehci1,id=usb \
-device ich9-usb-uhci1,masterbus=usb.0,firstport=0,multifunction=on \
-device ich9-usb-uhci2,masterbus=usb.0,firstport=2 \
-device ich9-usb-uhci3,masterbus=usb.0,firstport=4 \
-chardev spicevmc,name=usbredir,id=usbredirchardev1 -device usb-redir,chardev=usbredirchardev1,id=usbredirdev1 \
-chardev spicevmc,name=usbredir,id=usbredirchardev2 -device usb-redir,chardev=usbredirchardev2,id=usbredirdev2 \
-chardev spicevmc,name=usbredir,id=usbredirchardev3 -device usb-redir,chardev=usbredirchardev3,id=usbredirdev3 \
-nic user,id=nic0,smb=<share_path> \
-smp cores=4,threads=2,sockets=1 \
-m 8G -cpu host,hv_relaxed,hv_spinlocks=0x1fff,hv_vapic,hv_time windows.imgI have followed the wiki's instructions and made sure NetBIOS protocol is enabled, and just to be sure I have turned off the Windows Defender firewall with same results.
In Windows 11 I get a pop up message with "Windows can't find \\10.0.2.4\qemu. Check the spelling and try again."
I should mention that my Windows 11 is not activated. I couldn't get Windows 10 to upgrade to Windows 11 on its own so I did a new Windows 11 installation, but my OEM license key did not work for Win 11.
Thank you for the help and please let me know what other data I can post here to help diagnose the situation.
Last edited by leandroaveiro (2025-02-05 19:17:57)
Offline
I gave trying to make this work and instead I set up a regular smb share and access it over \\10.0.2.2. Still puzzled though as to why the same command line works with Win 10 and not Win 11.
Offline
Possibly there are differences in add/remove windows features in Win10 and Win11. Something esoteric might be enabled in 10 and not 11.
Offline
I met the same problem as you when my guest machine is windows 11 lot ltsc. But I made it connected using \\10.0.2.2\share when my host ran a normal smb server while \\10.0.2.4\qemu still failed.
and what I have done to my success on windows 10 ltsc 2021 is as followings:
1. control panel --> programs --> programs and features --> turn windos features on or off --> SMB 1.0/CIFS File Sharing Support
2. control panel --> network and sharissmng center --> change advanced sharing settings --> turn on network discovery & turn on file and printer sharing
3. gpedit.msc --> computer config --> administrative templates --> network
--> Lanman workstation --> enable insecure guest logons
4. reboot
Offline
I met the same problem as you when my guest machine is windows 11 lot ltsc. But I made it connected using \\10.0.2.2\share when my host ran a normal smb server while \\10.0.2.4\qemu still failed.
and what I have done to my success on windows 10 ltsc 2021 is as followings:
1. control panel --> programs --> programs and features --> turn windos features on or off --> SMB 1.0/CIFS File Sharing Support
2. control panel --> network and sharissmng center --> change advanced sharing settings --> turn on network discovery & turn on file and printer sharing
3. gpedit.msc --> computer config --> administrative templates --> network
--> Lanman workstation --> enable insecure guest logons
4. reboot
a different error message appeared and the following powershell command solved it:
Set-SmbClientConfiguration -RequireSecuritySignature $false
Last edited by mtxn (2026-01-02 04:42:16)
Offline
Moderator Note
Please don't necro-bump
Closing this thread.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Pages: 1
Topic closed