1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

VirtualBox how to mount share folder

Discussion in 'Installing and Upgrading FreeBSD' started by a129878, Mar 19, 2010.

  1. a129878

    a129878 New Member

    Messages:
    27
    Thanks Received:
    0
    XP Host - FreeBSD_8 Guest
    How can I mount my XP shared folder in the FreeBSD guest ?
    Most every thing else works in this set up.
    XP = Uptodate
    VBx = 314
    FreeBSD = 8.0-RELEASE #0 Nov 21 15:48:17
     
  2. Zare

    Zare Member

    Messages:
    386
    Thanks Received:
    53
    FreeBSD doesn't have guest additions drivers. Here's an simple workaround which basically does what "shared folders" do when you have guest additions installed;

    - make sure that your VirtualBox network is in bridge mode for FreeBSD guest.
    - make sure that your FreeBSD can ping Windows XP.
    - make sure that it can resolve XP's hostname, try pinging it by hostname
    - if not, add an entry into /etc/hosts
    - add another user in your XP system, grant him some privileges on the directory you want to share,

    now, as root on your FreeBSD guest do something like this

    Code:
    mount_smbfs //user@xp_box/SHARED /mnt/xp
    


    ...where of course, user is XP user that has some rights on the share, SHARED is the windows share name, and /mnt/xp is target directory. It will ask you for your user password, and that should be it.

    Basically, when in bridge networking mode, vbox host and guests are like computers on the same physical network.
     
    a129878 thanks for this.
  3. SirDice

    SirDice Moderator Staff Member Moderator

    Messages:
    17,630
    Thanks Received:
    2,386
  4. a129878

    a129878 New Member

    Messages:
    27
    Thanks Received:
    0
    I did go through all that, but erroneously dismissed it as FreeBSD hosting VBx.
    Now comes the problem I have not cracked yet with FreeBSD.
    My FreeBSD's have no access to the internet (Corporate policy, not mine)
    Klik the ref of "virtualbox-ose-additions-3.1.51.r25618_2 " and then I am stuck, as this seems to present just change history and not the iso/whatever.

    I find this a more general problem in knowing how to take a port element and put it on my FreeBSD system as though the internet were there.
     
  5. a129878

    a129878 New Member

    Messages:
    27
    Thanks Received:
    0
    Well - all that went OK till I got:-
    Code:
     mount_smbfs: cant get server address: syserr=Op TO.

    My command line:-
    Code:
     mount_smbfs //a129878@xp/Rt /mnt

    'xp' pings OK
    'Rt' is from VBoxMange show info:-
    Shared folders:
    Code:
      Name: 'Rt', Host path: 'C:\Documents and Settings\A129878\My Documents\Rt' (machine mapping), writable


    The man pages look horrrrific !

    Boy - the cutting edge or what.
     
  6. vermaden

    vermaden Well-Known Member

    Messages:
    2,364
    Thanks Received:
    678
    @a129878

    After You install the guest additions in your FreeBSD guest system, You will be able to use vboxsf:

    # mount -t vboxsf VBoxSharedFolderName /mnt
     
  7. rossiya

    rossiya New Member

    Messages:
    32
    Thanks Received:
    5
    Use the Tools

    How about using builtins tar and nc?
     
  8. rden

    rden New Member

    Messages:
    38
    Thanks Received:
    4
    vermaden, what's the magic

    Hi vermaden,

    I've installed VBox on XP, and followed the wiki instructions to install the guest additions. But there ain't no mount -t vboxsf

    How did you manage it?
     
  9. a129878

    a129878 New Member

    Messages:
    27
    Thanks Received:
    0
    I did not bother with trying to get XP hosting FreeBSD guest to see the XP world.
    I use the free open source winscp (http://winscp.net/eng/index.php) after setting
    sshd_enable="yes"' in /etc/rc.conf.
    This works fine and also gives putty (http://putty.very.rulez.org/download.html), ssh, access to the FreeBSD service, so I rearely need to use the console(s).
    Another advantage in using Winscp is that I can use the same skills to access a full PC FreeBSD as (and at the saem time) as my Virtual Box.
    One big advantage in using Putty is that of coloured windows with much larger screens.
     
  10. rden

    rden New Member

    Messages:
    38
    Thanks Received:
    4
    Depends on needs, for me copying files between platforms has never been an issue.

    In my own case I really wanted the ability to open files cross-platform, (mostly files living in Windows world opened with *nix tools) - reducing the need to physically copy the files back and forth.

    VirtualBox/VMware (tried both) solved the need to reboot between platforms (on a single laptop) but until recently still needed to copy files back and forth, (via USB stick or similar). (-- Fixed that with smb).

    Why? My job (that is the one that feeds my kids) often involves raw data inspection and conversion - you still can't beat 'nixens ability to quickly examine and elegantly modify files of any type. (Yes there are many good win/dos tools out there, but coming from multiple sources are rarely uniform in interface and too often gui-based -- making it hard / sometimes impossible to build an automated sequence of operations as easily as a shell script or quick 'n dirty C-prog).

    But also must have the Windows platform for reports, proposals, presentations etc. Ooo still way lags on MS office; and with the bulk of my company being on Win cant be making a doc, usually with embedded items, look good in ooo (or similar including google office for those dumb enough to trust it) only to have it look like crap (or simply fail) when my manager opens it in MSword.

    Finally stability: when it comes to virtulisation my own testing proved FreeBSD on XP is the king (1. despite being only 32 bit XP beats W7 under load, 2. as to nix guests (again under load) FBSD thrashed linux). Would like to reverse that but nix (including linux) hosted windows guests (and wine too) is still way too freaky -- having [my] emulation sh_t itself intermittently (or at the tail end) of an allnighter is last thing I need