I sincerely thank everyone who provided feedback - it was incredibly
detailed and helpful. In the meantime, I discovered an alternative
approach to achieving a shared setup by using:
Windows VirtIO Drivers (https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers)
+
Virtiofs (https://virtio-fs.gitlab
On Sun, 2025-01-19 at 18:29 -0800, ToddAndMargo via users wrote:
> Tip: if you are sharing between Windows machines,
> share on the oldest OS, not the newest. M$ acts
> like a jerk sharing from a new machine to an older
> machine.
I always tweaked the parameter that determined who would be master
On 1/19/25 7:05 AM, Earl Ramirez wrote:
And got nowhere trying SMB.
I had similar headache with a windows VM on Fedora host and permitting
SMB on firewalld libvirt zone resolved the issue
Hi Earl,
I have Windows qemu-kvm virtual machines with my Fedora 41
host Samba (cifs) sharing wi
On 1/19/25 2:03 AM, Tim via users wrote:
And is this consistent in describing when you share a resource, and how
networking is described?
Superficially, yes. But all kind of stuff pop up to
annoy you. And it is not always straight forward.
But far easier than Samba initially. Certainly very
> And got nowhere trying SMB.
>
I had similar headache with a windows VM on Fedora host and permitting SMB
on firewalld libvirt zone resolved the issue
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le..
Tim:
>> Which versions of Windows have you discovered have that backwards?
ToddAndMargo:
> All of them. The problem is the user only see the words "public"
> and "private". They do not read the description of either as
> they do not understand such "geek" speak. M$ does adequately
> describe w
On 1/18/25 11:02 PM, Tim via users wrote:
Which versions of Windows have you discovered have that backwards?
All of them. The problem is the user only see the words "public"
and "private". They do not read the description of either as
they do not understand such "geek" speak. M$ does adequa
On Sat, 2025-01-18 at 08:00 -0800, ToddAndMargo via users wrote:
> M$ has a bizarre way of stating such:
>
> Private: a hazardous environment with lots of
> potential bad guys on the same network.
> You are a network island and can see no
> network resour
On 1/18/25 8:00 AM, ToddAndMargo via users wrote:
In the registry, first identiry the {} from
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\NetworkList\Profiles\
Then switch "catagory" to the type of network you want. For example:
if {} was {162BD447-E8
On 1/17/25 5:33 AM, Paul Smith wrote:
Dear Fedora Users,
I’m encountering an issue where I cannot access a Samba shared folder
from a Windows 10 guest running on a host configured with virt-manager
+ QEMU/KVM. Here are the details of the situation:
--> Host Configuration and Status
The Samba s
Dear Fedora Users,
I’m encountering an issue where I cannot access a Samba shared folder
from a Windows 10 guest running on a host configured with virt-manager
+ QEMU/KVM. Here are the details of the situation:
--> Host Configuration and Status
The Samba shared folder is accessible from the host
11 matches
Mail list logo
