VirtualBox

Ticket #9334 (closed defect: fixed)

Opened 3 years ago

Last modified 3 years ago

Multiple VMs with Bridged Adapter to the same Host Link Aggregation Interface

Reported by: npooch Owned by:
Priority: major Component: network
Version: VirtualBox 4.0.12 Keywords:
Cc: nikolas.pooch@… Guest type: other
Host type: Solaris

Description

I have a Link Aggregation interface aggr1:

key: 1 (0x0001) policy: L4      address: 0:21:28:6b:24:dd (auto)
           device       address                 speed           duplex  link    state
           igb1         0:21:28:6b:24:dd          100   Mbps    full    up      attached
           e1000g1      0:15:17:d2:7:8    100   Mbps    full    up      attached

I've successfully used this interface to attach a bridged network adapter in one VM. However if I try to start a second VM with a bridged network adapter to the same aggregation interface on the same host, this second VM fails with:

00:00:13.018 IntNet#0: szNetwork={HostInterfaceNetworking-aggr1 - Link Aggregation Interface} enmTrunkType=3 szTrunk={aggr1} fFlags=0x8000 cbRecv=325632 cbSend=196608 fIgnoreConnectFailure=false
00:00:13.018 VMSetError: /export/home/vbox/tinderbox/4.0-sol-rel/src/VBox/Devices/Network/DrvIntNet.cpp(1694) int drvR3IntNetConstruct(PDMDRVINS*, CFGMNODE*, uint32_t); rc=VERR_INTNET_FLT_IF_BUSY
00:00:13.018 VMSetError: Failed to open/create the internal network 'HostInterfaceNetworking-aggr1 - Link Aggregation Interface'
00:00:13.018 PDM: Failed to construct 'pcnet'/0! VERR_INTNET_FLT_IF_BUSY (-3601) - The networking interface to filter was busy (used by someone).
00:00:13.030 VMSetError: /export/home/vbox/tinderbox/4.0-sol-rel/src/VBox/VMM/VMMR3/VM.cpp(354) int VMR3Create(uint32_t, const VMM2USERMETHODS*, void (*)(VM*, void*, int, const char*, unsigned int, const char*, const char*, __va_list_tag*), void*, int (*)(VM*, void*), void*, VM**); rc=VERR_INTNET_FLT_IF_BUSY
00:00:13.030 VMSetError: Unknown error creating VM
00:00:13.031 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={515e8e8d-f932-4d8e-9f32-79a52aead882} aComponent={Console} aText={Failed to open/create the internal network 'HostInterfaceNetworking-aggr1 - Link Aggregation Interface' (VERR_INTNET_FLT_IF_BUSY).
00:00:13.031 Unknown error creating VM (VERR_INTNET_FLT_IF_BUSY)}, preserve=false
00:00:13.060 Power up failed (vrc=VERR_INTNET_FLT_IF_BUSY, rc=NS_ERROR_FAILURE (0X80004005))

Using a physical interface like e100g0 does work as expected with multiple VMS using a bridge. Is this a problem with VirtualBox or a problem in the Solaris OS? This is

SunOS solarishost 5.10 Generic_142901-03 i86pc i386 i86pc

Thanks

Change History

comment:1 Changed 3 years ago by ramshankar

Could you attach the syslog (/var/adm/messages) file?

Are you running the VMs from the same user account?

comment:2 Changed 3 years ago by npooch

Could you attach the syslog (/var/adm/messages) file?

Nothing is logged at the time time tested. I've seen following regarding vboxdrv in messages, but don't think it has anything to do with this issue:

Jul 28 12:06:43 solarishost vboxdrv: [ID 456520 kern.notice] NOTICE: vbi_internal_alloc() failure for 2097152 bytes
Jul 28 12:13:56 solarishost last message repeated 2 times

Tests we're done at Jul 28 13:57..

Are you running the VMs from the same user account?

Not at first, so I've tried it with the same account. The behaviour is the same, regardless of the user account. However the logs are different:

The logs above are from a session with the same user account.

Under a different user:

00:00:23.338 IntNet#0: szNetwork={HostInterfaceNetworking-aggr1 - Link Aggregation Interface} enmTrunkType=3 szTrunk={aggr1} fFlags=0x8000 cbRecv=325632 cbSend=196608 fIgnoreConnectFailure=false
00:00:23.338 VMSetError: /export/home/vbox/tinderbox/4.0-sol-rel/src/VBox/Devices/Network/DrvIntNet.cpp(1694) int drvR3IntNetConstruct(PDMDRVINS*, CFGMNODE*, uint32_t); rc=VERR_INTNET_FLT_IF_BUSY
00:00:23.338 VMSetError: Failed to open/create the internal network 'HostInterfaceNetworking-aggr1 - Link Aggregation Interface'
00:00:23.338 VMSetError: /export/home/vbox/tinderbox/4.0-sol-rel/src/VBox/Devices/Network/DevE1000.cpp(5927) int e1kConstruct(PDMDEVINS*, int, CFGMNODE*); rc=VERR_INTNET_FLT_IF_BUSY
00:00:23.338 VMSetError: Failed to attach the network LUN
00:00:23.338 PDM: Failed to construct 'e1000'/0! VERR_INTNET_FLT_IF_BUSY (-3601)
 - The networking interface to filter was busy (used by someone).
00:00:23.354 VMSetError: /export/home/vbox/tinderbox/4.0-sol-rel/src/VBox/VMM/VMMR3/VM.cpp(354) int VMR3Create(uint32_t, const VMM2USERMETHODS*, void (*)(VM*, void*, int, const char*, unsigned int, const char*, const char*, __va_list_tag*), void*, int (*)(VM*, void*), void*, VM**); rc=VERR_INTNET_FLT_IF_BUSY
00:00:23.354 VMSetError: Unknown error creating VM
00:00:23.354 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={515e8e8d-f932-4d8e-9f32-79a52aead882} aComponent={Console} aText={Failed to open/create the internal network 'HostInterfaceNetworking-aggr1 - Link Aggregation Interface' (VERR_INTNET_FLT_IF_BUSY).
00:00:23.354 Failed to attach the network LUN (VERR_INTNET_FLT_IF_BUSY).
00:00:23.354 Unknown error creating VM (VERR_INTNET_FLT_IF_BUSY)}, preserve=false
00:00:23.381 Power up failed (vrc=VERR_INTNET_FLT_IF_BUSY, rc=NS_ERROR_FAILURE (0X80004005))

In both cases VMR3Create seems to be the initiator.

comment:3 Changed 3 years ago by npooch

Seems to be fixed in 4.1 series. In 4.1.2 it's working fine.

comment:4 Changed 3 years ago by frank

  • Status changed from new to closed
  • Resolution set to fixed

Thanks for the feedback!

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use