Dear All,
With the most recent versions of VirtualBox, the shared folder is not working properly as before.
My guest machine is running Windows 7, and the shared folder works fine during some time. However, after some time, the connection to the shared folder gets lost. Are other people experiencing the same? Any workaround?
Thanks in advance,
Paul
On Fri, 2019-02-08 at 17:11 +0000, Paul Smith wrote:
Dear All,
With the most recent versions of VirtualBox, the shared folder is not working properly as before.
My guest machine is running Windows 7, and the shared folder works fine during some time. However, after some time, the connection to the shared folder gets lost. Are other people experiencing the same? Any workaround?
Not with VB, but I recently spent a week tracking down an issue with KVM/QEMU which turned out to be caused by an interaction between my VPN and the firewall. Even if you don't have a VPN, start by checking your firewall settings, including the zone the guest network is in. If the shared folder uses SMB you need to enable that service (and of course make sure Samba is running on the host system).
poc
On Fri, Feb 8, 2019 at 6:56 PM Patrick O'Callaghan pocallaghan@gmail.com wrote:
With the most recent versions of VirtualBox, the shared folder is not working properly as before.
My guest machine is running Windows 7, and the shared folder works fine during some time. However, after some time, the connection to the shared folder gets lost. Are other people experiencing the same? Any workaround?
Not with VB, but I recently spent a week tracking down an issue with KVM/QEMU which turned out to be caused by an interaction between my VPN and the firewall. Even if you don't have a VPN, start by checking your firewall settings, including the zone the guest network is in. If the shared folder uses SMB you need to enable that service (and of course make sure Samba is running on the host system).
Thanks, Patrick, but if it was something related with the firewall, the shared folder would never work -- and it works for some time (several minutes). Do not you agree?
Paul
On 2/9/19 1:11 AM, Paul Smith wrote:
Dear All,
With the most recent versions of VirtualBox, the shared folder is not working properly as before.
My guest machine is running Windows 7, and the shared folder works fine during some time. However, after some time, the connection to the shared folder gets lost. Are other people experiencing the same? Any workaround?
Thanks in advance,
I've not used shared folders recently mostly because I don't use Windows guests all that much.
I've just enabled it and connected my Windows 10 guest and it has been working just fine after one hour.
I'm using VirtualBox-6.0-6.0.4_128413_fedora29-1 direct from Oracle and that VBbox Guest tools has been installed on the guest.
On Sat, 2019-02-09 at 00:38 +0000, Paul Smith wrote:
On Fri, Feb 8, 2019 at 6:56 PM Patrick O'Callaghan pocallaghan@gmail.com wrote:
With the most recent versions of VirtualBox, the shared folder is not working properly as before.
My guest machine is running Windows 7, and the shared folder works fine during some time. However, after some time, the connection to the shared folder gets lost. Are other people experiencing the same? Any workaround?
Not with VB, but I recently spent a week tracking down an issue with KVM/QEMU which turned out to be caused by an interaction between my VPN and the firewall. Even if you don't have a VPN, start by checking your firewall settings, including the zone the guest network is in. If the shared folder uses SMB you need to enable that service (and of course make sure Samba is running on the host system).
Thanks, Patrick, but if it was something related with the firewall, the shared folder would never work -- and it works for some time (several minutes). Do not you agree?
That's very similar to what I experienced, but in fact it did turn out to be a combination of the firewall and the VPN. See the (long) thread at:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/...
Of course your case may be completely different, but it's worth checking your firewall settings just in case.
poc
On 2/9/19 6:00 PM, Patrick O'Callaghan wrote:
Of course your case may be completely different, but it's worth checking your firewall settings just in case.
I do not think the shared folder function of VirtualBox uses the network.
I see no traffic between host and guest if I accesses the shared folders on the guest.
Also, if I set the FW on the host to "Block all Network Traffic" I get this on the host
[egreshko@meimei ~]$ ping cnn.com ping: cnn.com: Name or service not known
Yet, I can still access the shared folders on the host from the guest.
On Sat, 2019-02-09 at 19:29 +0800, Ed Greshko wrote:
On 2/9/19 6:00 PM, Patrick O'Callaghan wrote:
Of course your case may be completely different, but it's worth checking your firewall settings just in case.
I do not think the shared folder function of VirtualBox uses the network.
I think you're right (I wonder if this is a potential attack vector?). It's been a while since I've used VB. Libvirt has something called filesystem passthrough which I've never been able to figure out, so I just use NFS or Samba.
poc
On Sat, Feb 9, 2019 at 12:16 PM Patrick O'Callaghan pocallaghan@gmail.com wrote:
Of course your case may be completely different, but it's worth checking your firewall settings just in case.
I do not think the shared folder function of VirtualBox uses the network.
I think you're right (I wonder if this is a potential attack vector?). It's been a while since I've used VB. Libvirt has something called filesystem passthrough which I've never been able to figure out, so I just use NFS or Samba.
Thanks for your answers, Patrick and Ed. I am now suspecting that the cause the problem is not VirtualBox, but Windows 7, since there are plenty of complaints on the Internet regarding file explorer freezing...
In my case, inside Windows, the shared file is identified as a
Network drive.
Paul
On 2/9/19 8:24 PM, Paul Smith wrote:
Thanks for your answers, Patrick and Ed. I am now suspecting that the cause the problem is not VirtualBox, but Windows 7, since there are plenty of complaints on the Internet regarding file explorer freezing...
In my case, inside Windows, the shared file is identified as a
Network drive.
Yes, it appears as a network drive. However, it is "faked" and the "Guest Additions" need to be installed on the guest for them to work.
On 2/9/19 8:15 PM, Patrick O'Callaghan wrote:
I wonder if this is a potential attack vector?
I don't think so as I believe it is done by one of the kernel modules and the requirement that the Guest Additions package needs to be installed on the guest.
On Sat, 2019-02-09 at 21:25 +0800, Ed Greshko wrote:
On 2/9/19 8:15 PM, Patrick O'Callaghan wrote:
I wonder if this is a potential attack vector?
I don't think so as I believe it is done by one of the kernel modules and the requirement that the Guest Additions package needs to be installed on the guest.
I meant in the sense that it's a channel not mediated by the firewall, but I can't say I've thought it through.
poc
On Sat, Feb 9, 2019 at 3:04 PM Patrick O'Callaghan pocallaghan@gmail.com wrote:
I wonder if this is a potential attack vector?
I don't think so as I believe it is done by one of the kernel modules and the requirement that the Guest Additions package needs to be installed on the guest.
I meant in the sense that it's a channel not mediated by the firewall, but I can't say I've thought it through.
I have just downgraded VirtualBox from 6.0.4 to 5.2.26, and the problem I reported here seems to have disappeared.
Paul
-
Ed Greshko -
Patrick O'Callaghan -
Paul Smith