How to make a common area shared by Windows & Opensuse ?

Opensuse 12.3
KDE 4.10.5
Windows XP lol

I am trying to get Windows XP to work in VirtualBox.
The problem I have is that I need to download a network adapter driver for Windows and I always struggle with this. Previously I had downloaded it to a Cd.
I need a common area that both systems could read and write to.
I tried it with a USB Drive formatted to FAT 32, but, within Windows, when I selected, “have disk”, I could not see the USB drive.
So, is there a way to set up a common area accessible by both OSes ?

thanks

On Thu, 14 Nov 2013 21:36:01 +0000, hextejas wrote:

> Opensuse 12.3 KDE 4.10.5 Windows XP lol
>
> I am trying to get Windows XP to work in VirtualBox.
> The problem I have is that I need to download a network adapter driver
> for Windows and I always struggle with this. Previously I had downloaded
> it to a Cd.
> I need a common area that both systems could read and write to.
> I tried it with a USB Drive formatted to FAT 32, but, within Windows,
> when I selected, “have disk”, I could not see the USB drive.
> So, is there a way to set up a common area accessible by both OSes ?
>
> thanks

Use the “shared folder” feature of VirtualBox. That doesn’t require a
working network connection in the VM - just the VirtualBox guest tools be
installed.

Jim


Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

On 11/14/2013 04:07 PM, Jim Henderson wrote:
> On Thu, 14 Nov 2013 21:36:01 +0000, hextejas wrote:
>
>> Opensuse 12.3 KDE 4.10.5 Windows XP lol
>>
>> I am trying to get Windows XP to work in VirtualBox.
>> The problem I have is that I need to download a network adapter driver
>> for Windows and I always struggle with this. Previously I had downloaded
>> it to a Cd.
>> I need a common area that both systems could read and write to.
>> I tried it with a USB Drive formatted to FAT 32, but, within Windows,
>> when I selected, “have disk”, I could not see the USB drive.
>> So, is there a way to set up a common area accessible by both OSes ?
>>
>> thanks
>
> Use the “shared folder” feature of VirtualBox. That doesn’t require a
> working network connection in the VM - just the VirtualBox guest tools be
> installed.

The shared folder works very well; however, you should not need to install a
network driver in the virtual version of XP. For my XP VMs, I select the
PCnet-FAST III virtual hardware in NAT mode. I have never had to install any
drivers in the VM.

On Thu, 14 Nov 2013 22:14:58 +0000, Larry Finger wrote:

> On 11/14/2013 04:07 PM, Jim Henderson wrote:
>> On Thu, 14 Nov 2013 21:36:01 +0000, hextejas wrote:
>>
>>> Opensuse 12.3 KDE 4.10.5 Windows XP lol
>>>
>>> I am trying to get Windows XP to work in VirtualBox.
>>> The problem I have is that I need to download a network adapter driver
>>> for Windows and I always struggle with this. Previously I had
>>> downloaded it to a Cd.
>>> I need a common area that both systems could read and write to.
>>> I tried it with a USB Drive formatted to FAT 32, but, within Windows,
>>> when I selected, “have disk”, I could not see the USB drive.
>>> So, is there a way to set up a common area accessible by both OSes ?
>>>
>>> thanks
>>
>> Use the “shared folder” feature of VirtualBox. That doesn’t require a
>> working network connection in the VM - just the VirtualBox guest tools
>> be installed.
>
> The shared folder works very well; however, you should not need to
> install a network driver in the virtual version of XP. For my XP VMs, I
> select the PCnet-FAST III virtual hardware in NAT mode. I have never had
> to install any drivers in the VM.

Oh, yes, good point, Larry - the AMD PCNet driver is installed with the
VirtualBox guest tools, IIRC.

Jim


Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

The shared folder works very well; however, you should not need to install a
network driver in the virtual version of XP. For my XP VMs, I select the
PCnet-FAST III virtual hardware in NAT mode. I have never had to install any
drivers in the VM.

I was hoping that I wouldn’t have to mess around with drivers and such, but it looks like I will.
So, methinks both solutions sound good.
Do you do the selecting of the PC-net in VirtualBox or Windows ?

On 11/14/2013 05:06 PM, hextejas wrote:
>
>>
>>
>> The shared folder works very well; however, you should not need to
>> install a
>> network driver in the virtual version of XP. For my XP VMs, I select the
>> PCnet-FAST III virtual hardware in NAT mode. I have never had to install
>> any
>> drivers in the VM.
>
> I was hoping that I wouldn’t have to mess around with drivers and such,
> but it looks like I will.
> So, methinks both solutions sound good.
> Do you do the selecting of the PC-net in VirtualBox or Windows ?

In the “Oracle VM VirtualBox Manager” screen, click on Network, expand the
Advanced tab, and select the adapter you want.

I got the network working as you suggested by using the PC Net attachment. I saw that there was a PCnet-FAST II and a PCnet-FAST III.

Without knowing why, I picked the II so maybe I will go back and try the III to see if there is any difference.

Re the shared folder, my reading at VirtualBox says it is supported for Windows 2000 and later.
Did you get it working with XP ?

On 11/16/2013 03:46 PM, hextejas wrote:
>
> I got the network working as you suggested by using the PC Net
> attachment. I saw that there was a PCnet-FAST II and a PCnet-FAST III.
>
> Without knowing why, I picked the II so maybe I will go back and try the
> III to see if there is any difference.
>
> Re the shared folder, my reading at VirtualBox says it is supported for
> Windows 2000 and later.
> Did you get it working with XP ?

Yes, I did.

I also read that the shared folder would automatically show up in Windows explorer. Was that your experience or did you have to go thru the mapping of a network drive like net use x: \vboxsvr\home\sharedfolder ?

I think I tried the net use but got an error.

On Sun, 17 Nov 2013 01:26:02 +0000, hextejas wrote:

> I also read that the shared folder would automatically show up in
> Windows explorer. Was that your experience or did you have to go thru
> the mapping of a network drive like net use x:
> \vboxsvr\home\sharedfolder ?
>
> I think I tried the net use but got an error.

I’ve always just used:

net use f: \vboxsrv\sharename

From in the Windows VM.

It’s supposed to be able to automap the drive (on startup) but I’ve never
seen that actually work myself.

Jim


Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

Well, I cannot figure this out.
I was trying to see what I could see by using VBoxManage and mostly I got pages and pages trying to explain where I was going wrong. Sheesh.
Even the examples leave a lot to be desired,

1st off I was trying to see if I could get a status/listing of the running virtual machines. Seems easy enough huh. Well it was all down hill from there.

Plus I was not sure what the name of the virtual machine was. I think it is the instance of Windows XP that I started.
Anyhow, these are what I got.

Corky-PC:~ # VBoxManage showvminfo "Windows XP"
VBoxManage: error: Could not find a registered machine named 'Windows XP'
VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBox, interface IVirtualBox, callee nsISupports
VBoxManage: error: Context: "FindMachine(Bstr(VMNameOrUuid).raw(), machine.asOutParam())" at line 2610 of file VBoxManageInfo.cpp

<<<<<<<<<<<<< I started Windows here. >>>>>>>>>>>>>>>>>>>>>

Corky-PC:~ # VBoxManage showvminfo "Corky-PC"
VBoxManage: error: Could not find a registered machine named 'Corky-PC'
VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBox, interface IVirtualBox, callee nsISupports
VBoxManage: error: Context: "FindMachine(Bstr(VMNameOrUuid).raw(), machine.asOutParam())" at line 2610 of file VBoxManageInfo.cpp

Corky-PC:~ # VBoxManage list vms
Corky-PC:~ # 

Entries 1 and 2 are my fumbling attempts to figure out the VM name.
The last one indicates that I have no VM running but Windows was in fact running.

I need to figure these out before I can dream of a shared folder.

Are you running VBoxManage in the host or in the guest?
The commands you posted you have to run in the host. And you don’t have to have the guest running.
For your VM’s name you can of course just have a look in the VirtualBox GUI… :wink:
http://wstaw.org/m/2013/11/17/VirtualBox.png

They are being run in an openSuse command window. And I don’t know the proper word for it,
I ran as su - if that made a difference. Hence the #.

and I am pretty sure that the VM name is “Corky-PC” in that that is what is shown in the GUI, with the green background.

Plus, why is it that the VBoxManage list vms shows nothing running ?

Run the command as your vboxuser!

That seemed to solve that bit, and thank you hank.

Now onward as to why I can’t map to the shared folder.
Apparently the VBox side is set up correctly so I am guessing the problem lies within Windows XP.

Nope, it seems that I need the Guest addons and I thought I had them.

Shared folders:  

Name: 'Shared', Host path: '/home/hexdump/Desktop/Shared' (machine mapping), writable
Name: 'Shared2', Host path: '/home/hexdump/Desktop/Shared' (machine mapping), writable

VRDE Connection:    not active
Clients so far:     0

Video capturing:    not active
Capture screens:    0
Capture file:       /home/hexdump/VirtualBox VMs/Corky-PC/Corky-PC.webm
Capture dimensions: 1024x768
Capture rate:       512 kbps
Capture FPS:        25

Guest:

Configured memory balloon size:      0 MB

Correct, you need the Guest Additions.

Installing them is as easy as choosing “Devices”->“Install Guest Additions…” in the VM window’s menu and then running the setup program in Windows (should start automatically I think, I have no WinXP guest handy to check).

How odd.
I used Yast to install the guest additions and, for me, it was a bit startling !

I think I recompiled the kernel in order to incorporate them and that is something that I usually stay away from. In fact I have never done it before.
When I went back into Yast to see what I had incorporated, it was:

VirtualBox-guest-tools
VirtualBox-kmp-default

and another odd item was that VirtualBox 4.3.2-90405 shows in red.

I still cannot map to the shared folder plus VirtualBox says that I do not have the guest tools installed.
It also says to try installing them again ! Which means a recompile. No thanks, I think I will mail a CD. rotfl!

On 11/17/2013 01:56 PM, hextejas wrote:
>
> hank_se;2598346 Wrote:
>> Run the command as your vboxuser!
>
> That seemed to solve that bit, and thank you hank.
>
> Now onward as to why I can’t map to the shared folder.
> Apparently the VBox side is set up correctly so I am guessing the
> problem lies within Windows XP.
>
>
> Code:
> --------------------
> Shared folders:
>
> Name: ‘Shared’, Host path: ‘/home/hexdump/Desktop/Shared’ (machine mapping), writable
> Name: ‘Shared2’, Host path: ‘/home/hexdump/Desktop/Shared’ (machine mapping), writable
>
> VRDE Connection: not active
> Clients so far: 0
>
> Video capturing: not active
> Capture screens: 0
> Capture file: /home/hexdump/VirtualBox VMs/Corky-PC/Corky-PC.webm
> Capture dimensions: 1024x768
> Capture rate: 512 kbps
> Capture FPS: 25
>
> Guest:
>
> Configured memory balloon size: 0 MB

When you pull down the “Devices” menu item while running XP in a VM, does the
shared folder exist? If not, you heed to set it up in the Configuration Manager.
If the shared folder exists, then open Windows Explorer. Under the Tools menu
item, you should see “Map Network Drive”. Configure it exactly the same as you
would any network folder in Windows.

Did my messing around in Yast break anything and should I undo it ?

Since when do you have Yast in Windows? rotfl!

So you installed the guest additions on the openSUSE host. You have to install the Guest Additions in the guest of course. :wink:

Your install doesn’t break anything though, they are just useless on the host.
So you should uninstall them again.

And apparently you now have kernel-desktop and kernel-default? Then better uninstall kernel-default as well.