The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    HowTo: Speed up Shared Folder Access Time in VirtualBox with Windows Guest

    Discussion in 'Linux Compatibility and Software' started by theZoid, Sep 30, 2009.

  1. theZoid

    theZoid Notebook Savant

    Reputations:
    1,338
    Messages:
    5,202
    Likes Received:
    22
    Trophy Points:
    206
    If you are suffered by accessing shared folders too slow, try this:

    1. if your vm is running Windows,
    2. if your share folder name is like that : "\\vboxsvr\<share fodler>"
    3. if you install windows in disk c of your vm
    4. please modify c:\windows\system32\drivers\etc\hosts
    5. modify the line "127.0.0.1 localhost" to "127.0.0.1 localhost vboxsvr"
    6. reboot vm, and you can see there's a lot of improvement.

    Made an incredible difference for me. FWIW :)
     
  2. Pitabred

    Pitabred Linux geek con rat flail!

    Reputations:
    3,300
    Messages:
    7,115
    Likes Received:
    3
    Trophy Points:
    206
    Interesting... I'd think that calling itself the vboxhost would break things. 127.0.0.1 should point only to the machine, IE, the virtual machine, and not the virtualbox host.
     
  3. theZoid

    theZoid Notebook Savant

    Reputations:
    1,338
    Messages:
    5,202
    Likes Received:
    22
    Trophy Points:
    206
    Have you tried it? It really cured my 'sluggishness' problem access my /home from XP. I don't understand why though....any explanation?
     
  4. Pitabred

    Pitabred Linux geek con rat flail!

    Reputations:
    3,300
    Messages:
    7,115
    Likes Received:
    3
    Trophy Points:
    206
    I don't have any sluggishness problems with my mapped drive, so I'm not about to break my hosts file ;) I'm just talking from a networking perspective, it doesn't make sense.
     
  5. theZoid

    theZoid Notebook Savant

    Reputations:
    1,338
    Messages:
    5,202
    Likes Received:
    22
    Trophy Points:
    206
    PITA, for an FYI, this sluggishness seems to be a common complaint on the Ubuntu forums....with regard to my XP virtual machine hosts file, broken is as broken does :) Shared file access is dramatically improved for me. Please be so kind to explain; you're a coder and I'm not, I'm just trying learn something here :) I think we're missing something here.
     
  6. Pitabred

    Pitabred Linux geek con rat flail!

    Reputations:
    3,300
    Messages:
    7,115
    Likes Received:
    3
    Trophy Points:
    206
    127.0.0.1 is called the loopback address. When you say "vboxhost" should resolve to 127.0.0.1, that means that the virtual machine should look at itself when trying to find the drive. It may be because of the way that VirtualBox intercepts mapped drive accesses and such that this works, but in general, any time you access 127.x.x.x you are accessing only your own machine (ie, the virtual machine), and you can't get to anything else. That's the whole point of the loopback.

    What may be different between our systems is that I have the Sun Virtualbox 3.0 version installed, not the open-source version.
     
  7. theZoid

    theZoid Notebook Savant

    Reputations:
    1,338
    Messages:
    5,202
    Likes Received:
    22
    Trophy Points:
    206
    Thanks for info....I have Jaunty 9.04 x64 and VB PUEL ed. 3.0.6.....man, all I know is the procedure above was being used on Ubuntu forums, and damned if it didn't make a world of difference :confused: :D I'll study that some when I get more time.....