I am running win7 and os12.1 in a dual boot configuration and in addition have two fat32 partitions for data storage.
I seldom boot the win7 system and would like to be able to eliminate it completely however there are a few ‘must have’ applications.
I installed Virtual Box with a win7 guest system and it appears to be working except cannot access shared folders on the host system.
The fat32 partitions indicated as windows drives ‘e’ & ‘d’ were selected and show in VB as shared folders but when running the quest win7 they cannot be found.
It seems to me I have identified the folders as described in the VB documentation and cannot find any additional instructions.
Is there anything else that needs to be done beyond identifying the shared folders?
On 02/10/2012 02:06 PM, zuser wrote:
>
> I am running win7 and os12.1 in a dual boot configuration and in
> addition have two fat32 partitions for data storage.
> I seldom boot the win7 system and would like to be able to eliminate it
> completely however there are a few ‘must have’ applications.
>
> I installed Virtual Box with a win7 guest system and it appears to be
> working except cannot access shared folders on the host system.
> The fat32 partitions indicated as windows drives ‘e’& ‘d’ were
> selected and show in VB as shared folders but when running the quest
> win7 they cannot be found.
>
> It seems to me I have identified the folders as described in the VB
> documentation and cannot find any additional instructions.
> Is there anything else that needs to be done beyond identifying the
> shared folders?
I don’t know about Windows 7, but it works with XP. You need to install the
VirtualBox Extensions for your version of VB. Then in the VB GUI, select the
Shared Folders", click the + icon, and add the Linux path you wish to share.
Check the Auto-mount box, and it should be there in the available disks.
Extensions are installed and shared folders are set to automount with full access.
When I run win7 as a vm and open windows explorer, there is no indication of the shared folders or network connections.
Windows Explorer shows only c: drive
On 02/11/2012 09:16 AM, zuser wrote:
>
> Extensions are installed and shared folders are set to automount with
> full access.
> When I run win7 as a vm and open windows explorer, there is no
> indication of the shared folders or network connections.
> Windows Explorer shows only c: drive
I guess that is a Win 7 problem. As I said, XP works fine, and by implication,
so does openSUSE 12.1. It would be in the network connections section.
What do you mean by “no indication of network connections”? The vm should be able to access the host as well as the Internet through the host (in both NAT and bridge modes). The other problems are not specific to virtualization, as already said.
> Extensions are installed and shared folders are set to automount with
> full access.
> When I run win7 as a vm and open windows explorer, there is no
> indication of the shared folders or network connections.
> Windows Explorer shows only c: drive
It would, until you actually create a drive mapping you won’t see the
shared folders show up as a drive letter.
Even in XP, I had to issue a NET USE command (or do the GUI equivalent)
to get access to the shared drives through a drive letter.
The partition I want to mount shows as windows\F in Settings under VirtualBox Manager.
All partitions are shown to auto mount but none do.
Attempts to manual mount returns result “The network path was not found”
[quote="hendersj
[Chapter"]
(http://www.virtualbox.org/manual/ch04.html#sf_mount_manual) explains the
manual mount options. I do see the docs there for automatic mounting,
but didn’t play with that. Try the manual option and see how that works
for you.
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at openSUSE Forums FAQ
[/quote]
> The partition I want to mount shows as windows\F in Settings under
> VirtualBox Manager.
> All partitions are shown to auto mount but none do.
> Attempts to manual mount returns result “The network path was not found”
What exactly did you type, and what’s the name of the path that you
shared in the host?
> 1st: net use x: \vboxsvr\F
>
> then: net use x: \vboxsvr\windows\F
>
> then: net use x: \vboxsvr\Machine Folders\F
>
> All in turn returned “System error 53, The network path was not found”
>
> My hd has multiple partitions, “F” being an extended partition,
> formatted FAT32.
What is your host operating system? “F” as an extended partition makes
me think that it’s a Windows host rather than a Linux host.
Also, what is the path that’s in the shared folders configuration for the
virtualbox settings?
> Notebook is setup to dual boot win7 (as purchased) and openSUSE 12.1,
> both 64 bit.
> Host is openSUSE and guest win7 ultimate.
>
> In VM, under settings: under Name - F under Path - /windows/F
So it sounds like you have in your Linux system an “F” partition (which
is used on the system’s Windows install - not in the VM, but the system
itself) that is mounted. So if you type:
mount
You see an entry there for /windows/F that is mounted as NTFS or fat32,
correct?
Correct, no problem accessing from either win7(on hdd) or openSUSE.
Shows in “System Information” as /windows/F as you stated.
Last night I booted Mint in Virtualbox and same issue, no indication of shared folders.
[QUOTE=hendersj;
So it sounds like you have in your Linux system an “F” partition (which
is used on the system’s Windows install - not in the VM, but the system
itself) that is mounted.
So if you type:
mount
You see an entry there for /windows/F that is mounted as NTFS or fat32,
correct?
> Correct, no problem accessing from either win7(on hdd) or openSUSE.
> Shows in “System Information” as /windows/F as you stated.
>
> Last night I booted Mint in Virtualbox and same issue, no indication of
> shared folders.
First, it should be noted
If you really are running openSUSE 12.1, that is very, very long past support. It’s never a good idea to do any virtualization on top of a HostOS that is out of date and unsupported, there are numerous security issues besides the point that nothing released recently is expected to work on an unsupported OS.
If you don’t know for sure what version of openSUSE you’re running the following will return both the openSUSE version and your kernel version
uname -a
So, prepare for the possibility that there won’t be a solution to your existing situation unless and until you upgrade to a currently supported OS.
**Current recommended supported openSUSE **
openSUSE 13.1 evergreen will be supported for a few more months as of today
openSUSE 13.2 and LEAP 42.1 are the currently main supported versions of openSUSE
Now, a few suggestions…
I strongly recommend you don’t configure a shared folder name as a single letter. There is too much possibility to confuse that sharename with Windows drive letters, both on the HostOS and again if you decide to map the share to a drive in the Guest. I recommend instead something descriptive for what will be found in the share, and without spaces or special characters.
It’s unclear whether you have installed VBox Extensions for the HostOS which are optional in this case because it’s not absolutely required to create Shared Folders and Guest Additions in each Guest which are absolutely required. Note that both VBox Extensions and Additions are very specific to the version of Virtualbox you have installed, and need to be re-kernel modules with any kernel upgrade (although dkms can update your VBox kernel modules automatically as needed).
When you install any kind of virtualization on an openSUSE HostOS, I always recommend updating your system with the following command before installing, and I recommend running it again whenever you run into glitches. Updating manually can solve a multitude of problems.
zypper update
You need to describe exactly the commands you used to mount your shared folders.
In a Windows Guest, you should be able to simply browse to your Virtualbox folders as a Network Share
VBox Shared Folders in an openSUSE Guest requires some special work to create folders with proper permissions that don’t exist by default. Previous Forum threads describe what you need to do,