Cannot use host network in 2.1.0

[stevie_davies]

Am running 2.1.0 in Ubuntu 8.10. Guest OS is Windows XP. Guest OS used to boot in 2.0.6 using the vbox0 interface bridged to br0 using brctl.

I changed the guest to use the new host networking feature, so have configured the adapter 1 to use pcnet interface attaced to host interface. Under host interfaces eth0 is present, and highlighted.

When I try to boot the Guest I get the following:

Failed to open/create the internal network 'HostInterfaceNetworking-eth0' (VERR_PERMISSION_DENIED).
Unknown error creating VM (VERR_PERMISSION_DENIED).

In log I see:

00:00:01.319 IntNet#0: szNetwork={HostInterfaceNetworking-eth0} enmTrunkType=3 szTrunk={eth0} fFlags=0x0 cbRecv=223232 cbSend=36864
00:00:01.319 PDM: Failed to construct 'pcnet'/0! VERR_PERMISSION_DENIED (-10) - Permission denied.
00:00:01.432 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={e3c6d4a1-a935-47ca-b16d-f9e9c496e53e} aComponent={Console} aText={Failed to open/create the internal network 'HostInterfaceNetworking-eth0' (VERR_PERMISSION_DENIED).
00:00:01.432 Unknown error creating VM (VERR_PERMISSION_DENIED)} aWarning=false, preserve=false
00:00:01.439 Power up failed (vrc=VERR_PERMISSION_DENIED, rc=NS_ERROR_FAILURE (0X80004005))
00:01:00.841 VRDP: TCP server closed.

[Frank Mehnert]

Please could you attach the whole log file? Thank you!

[Frank Mehnert]

Btw, there is a known issue that you cannot start more than one VMs attached to the same host interface (there is a workaround for this problem). I just want to rule out this problem.

[Mario Gomez]

Hi !

I'm have the same problem with Fedora 8, Virtual Box 2.1.0 (Windows XP Professional)

Only can use one VM's with Host Interface the another VM can't run.

:S

Same solution ?

[Jason Grant]

I'm experiencing this issue too; i.e. I cannot run multiple VMs on the same host.

My host is CentOS 5.2 and I am trying to run multiple CentOS and Fedora guests. Here is one of the guests.

Is there a ticket for the "known issue" referenced above? Also, what is the workaround?

Thanks,

Jason.

[demo@ci ~]$ VBoxManage showvminfo demo
VirtualBox Command Line Management Interface Version 2.1.2
(C) 2005-2009 Sun Microsystems, Inc.
All rights reserved.

Name:            demo
Guest OS:        Fedora
UUID:            f87f089f-d0e0-4d89-a9e3-003e8626c071
Config file:     /home/demo/.VirtualBox/Machines/demo/demo.xml
Memory size:     512MB
VRAM size:       1MB
Boot menu mode:  message and menu
ACPI:            on
IOAPIC:          on
PAE:             on
Time offset:     0 ms
Hardw. virt.ext: on
Nested Paging:   off
VT-x VPID:       off
State:           powered off (since 2009-01-23T01:59:36.000000000)
Monitor count:   1
3D Acceleration: off
Floppy:          empty
SATA:            disabled
IDE Controller:  PIIX4
Primary master:  /home/demo/vbox/UMarket_rel3.vdi (UUID: 08c6e043-ccc5-4395-a9b4-ef7f11af57d9)
DVD:             empty
NIC 1:           MAC: 080027B8A386, Attachment: Host Interface 'eth0', Cable connected: on, Trace: off (file: none), Type: Am79C973, Reported speed: 0 Mbps
NIC 2:           disabled
NIC 3:           disabled
NIC 4:           disabled
NIC 5:           disabled
NIC 6:           disabled
NIC 7:           disabled
NIC 8:           disabled
UART 1:          disabled
UART 2:          disabled
Audio:           disabled (Driver: Unknown, Controller: Unknown)
Clipboard Mode:  Bidirectional
VRDP:            disabled
USB:             disabled

USB Device Filters:

<none>

Shared folders:  <none>

Guest:

Statistics update:                   disabled

[Jason Grant]

Hi Frank,

I am still keen to start more than one VM on the same host interface.

On the 13th, you mentioned that a workaround exits, however I cannot find a description of this. I'm hopeful that you can provide some more detail on this workaround.

Thanks for any tips,

Jason.

[Jason Grant]

Also, I think the ticket subject should be changed to include 2.1.2, since this issue does not just apply to 2.1.0.

[Aleksey Ilyushin]

Does everyone experience this problem while starting several VMs under different user accounts or under the same one?

[Jason Grant]

This appears to be resolved in 2.1.4. I'm running two VMs in host mode under the same user account on a CentOS 5.2 box, and networking seems to be OK. The VMs are also CentOS 5.2, and they booted using DHCP with no problems.

[Frank Mehnert]

Thanks for the feedback!

[Vardan]

Hi,

Sorry if I am posting to a wrong ticket. I have HP laptop running Vista 64bit, installed VirtualBox 2.1.4 and added XP as a guest. Within Vista(host) I can copy files to shared directory (which is c:\program files\sun\virtualbox\share") and I can read within my VirtualBox gues account (i.e. XP) but when I try to write back to the shared directory so I can read from Vista doesn't allow me. I've tried to share the folder to all allowing full access but it doesn't work, I can not copy from guest to host share folder. Also I have enabled a usb in a guest but would like to able to access a usb drive from Vista but I can not see the drive under my computer.

Any help I would appreciate.

Thanks an advance.

Regards

Vardan

[rf]

Hi all, hope we can help others with the way we use to solve the above discussed problem.

Problem:

When: User-1 has a running VM with bridged network Interface-A (i.e. eth0, br0, whatsoever) Then: User-2 can not start another one VM with bridged networking Interface-A

Errormessage like:

Failed to open/create the internal network 'HostInterfaceNetworking-eth0' (VERR_PERMISSION_DENIED). Unknown error creating VM (VERR_PERMISSION_DENIED).

VirtualBox Versions:

This problem was true for us in all versions of VirtualBox 2 up to 2.2.2. (we still use this)

Remark:

The solution given in ticket #2852 with VBoxManage setextradata VM_NAME VBoxInternal/Devices/pcnet/0/LUN#0/Config/RestrictAccess 0 / VBoxManage setextradata VM_NAME VBoxInternal/Devices/pcnet/0/LUN#0/Config/RestrictAccess false did not work for us

Now one possible solution we use since months:

For each user that want start a VM make tap-devices bridged to your desired network interface, i.e. tapuser1 and tapuser2. You can use "tunctl" for this. We use Fedora FC10 and made us a patch to the ifup-eth/ifdown-eth scripts (Type="Tap") In the upcoming FC11 seems to be included a very similar patch, so we will use this in future. In VirtualBox the User1 in his VM now selects the bridged interface "tapuser1", and the User2 in his VM similarly the "tapuser2".

Just to complete the idea here excerpts of the patches and some example network interface files: /etc/sysconfig/network-scripts/ifup-eth: @@ -54,16 +54,6 @@

fi

fi

+if [ "${TYPE}" = "Tap" ]; then + if [ ! -x /usr/sbin/tunctl ]; then + echo $"TUN/TAP support not available: tunctl not found" + exit 1 + fi + if [ ! -d /sys/class/net/${DEVICE} ]; then

+ /usr/sbin/tunctl -g ${GROUP} -t ${DEVICE}

exit 1

+ fi +fi +

if [ "${TYPE}" = "Bridge" ]; then

if [ ! -x /usr/sbin/brctl ]; then

echo $"Bridge support not available: brctl not found"

/etc/sysconfig/network-scripts/ifdown-eth: @@ -144,12 +144,4 @@

fi

fi

+if [ "${TYPE}" = "Tap" ]; then + if [ ! -x /usr/sbin/tunctl ]; then + echo $"TUN/TAP support not available: tunctl not found" + elif [ ! -d /sys/class/net/${DEVICE} ]; then + /usr/sbin/tunctl -d ${DEVICE} + fi +fi +

exit $retcode

/etc/sysconfig/network-scripts/ifcfg-br0: # Bridge device DEVICE=br0 TYPE=Bridge ...

/etc/sysconfig/network-scripts/ifcfg-eth0: ... BRIDGE=br0

/etc/sysconfig/network-scripts/ifcfg-tapuser1: # TAP device DEVICE=tapuser1 TYPE=Tap GROUP=vboxusers ... BRIDGE=br0

/etc/sysconfig/network-scripts/ifcfg-tapuser2: # TAP device DEVICE=tapuser2 TYPE=Tap GROUP=vboxusers ... BRIDGE=br0

Hope this helps :-)