If I connect virt-viewer at the same time that I start the vm, and quickly, before Windows 10 starts, I activate the share, it appears normally and I can use the same.
However, if the vm Windows 10 is fully started when I open virt-viewer, I need to restart the vm to get the share to work. Otherwise, it won't work -not even if I manually run the bat file-.
Is there any way to force the vm to load the share independently of virt-viewer? Or to default virt-viewer to load the share for a specific vm?
If I connect virt-viewer at the same time that I start the vm, and quickly, before Windows 10 starts, I activate the share, it appears normally and I can use the same.
However, if the vm Windows 10 is fully started when I open virt-viewer, I need to restart the vm to get the share to work. Otherwise, it won't work -not even if I manually run the bat file-.
Is there any way to force the vm to load the share independently of virt-viewer? Or to default virt-viewer to load the share for a specific vm?