|
Hello All, We have constructed a virtual lab that uses multiple instances of VirtualBox across multiple blade servers. We provide virtual networking between these virtual machines using Crossbow virtual NICs tagged on certain Vlans. For the most part this works very well, however occasionally we find that a virtual machine will not start. From the log file we see this output. 00:00:00.217 IntNet#0: szNetwork={HostInterfaceNetworking-labvnic360} enmTrunkType=3 szTrunk={labvnic360} fFlags=0x0 cbRecv=223232 cbSend=36864 00:00:00.217 VMSetError: /export/home/vbox/tinderbox/3.1-sol-rel/src/VBox/Devices/Network/DrvIntNet.cpp(1071) int drvIntNetConstruct(PDMDRVINS*, CFGMNODE*, uint32_t) 00:00:00.217 VMSetError: Failed to open/create the internal network 'HostInterfaceNetworking-labvnic360' 00:00:00.217 VMSetError: /export/home/vbox/tinderbox/3.1-sol-rel/src/VBox/Devices/Network/DevE1000.cpp(5044) int e1kConstruct(PDMDEVINS*, int, CFGMNODE*) 00:00:00.217 VMSetError: Failed to attach the network LUN 00:00:00.217 PDM: Failed to construct 'e1000'/0! VERR_INTNET_INCOMPATIBLE_TRUNK (-3603) - The network already exists with a different trunk configuration. 00:00:00.234 VMSetError: /export/home/vbox/tinderbox/3.1-sol-rel/src/VBox/VMM/VM.cpp(323) int VMR3Create(uint32_t, void (*)(VM*, void*, int, const char*, unsigned int, const char*, const char*, __va_list_tag*), void*, int (*)(VM*, void*), void*, VM**) 00:00:00.234 VMSetError: Unknown error creating VM 00:00:00.238 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={6375231a-c17c-464b-92cb-ae9e128d71c3} aComponent{Console} aText={Failed to open/create the internal network 'HostInterfaceNetworking-labvnic360' (VERR_INTNET_INCOMPATIBLE_TRUNK). 00:00:00.238 Failed to attach the network LUN (VERR_INTNET_INCOMPATIBLE_TRUNK). 00:00:00.238 Unknown error creating VM (VERR_INTNET_INCOMPATIBLE_TRUNK)} aWarning=false, preserve=false 00:00:00.243 Power up failed (vrc=VERR_INTNET_INCOMPATIBLE_TRUNK, rc=NS_ERROR_FAILURE (0X80004005)) dladm show-vnic on the host blade shows the following output: r...@virtlab-x6250e:~# dladm show-vnic LINK OVER SPEED MACADDRESS MACADDRTYPE VID labvnic294 aggr1 1000 8:0:27:0:1:26 fixed 555 labvnic323 aggr1 1000 8:0:27:0:1:43 fixed 555 labvnic326 aggr1 1000 8:0:27:0:1:46 fixed 555 labvnic319 aggr1 1000 8:0:27:0:1:3f fixed 555 labvnic324 aggr1 1000 8:0:27:0:1:44 fixed 555 labvnic320 aggr1 1000 8:0:27:0:1:40 fixed 555 labvnic355 aggr1 1000 8:0:27:0:1:63 fixed 555 labvnic334 aggr1 1000 8:0:27:0:1:4e fixed 555 labvnic333 aggr1 1000 8:0:27:0:1:4d fixed 555 labvnic348 aggr1 1000 8:0:27:0:1:5c fixed 555 labvnic360 aggr1 1000 8:0:27:0:1:68 fixed 555 r...@virtlab-x6250e:~# According to the manual the only limitation with using Crossbow with VirtualBox is that the MAC address of the Crossbow NIC should be the same as the VirtualBox NIC which we do. Are we doing something wrong or have we hit a bug in VirtualBox / Crossbow? Thanks in advance for your help. Many thanks Robin Ridler --
|
------------------------------------------------------------------------------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb
_______________________________________________ VBox-users-community mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/vbox-users-community
