(SOLVED) Cannot start VM bridged to a VLANs
Posted: 9. Sep 2009, 10:19
Cannot start VM bridged to a VLANs when another VM bridged to another VLAN is already running.
Windows Vista Business 64bit host SP2
I have 3 VLANs on an Intel PRO/1000 MT Desktop Adapter lan card.
I have installed the Intel Proset drivers for the NIC v14.3
They enable me to have each VLAN with its own virtual NIC in the form of for example: Intel(R) PRO/1000 MT Desktop Adapter - VLAN : VLAN2018 (The only way to use VLAN in Windows I know of)
If I start a virtual machine bridged to one of the Virtual VLAN NICs it is OK, everything is working
I can also start more virtual machines bridged to the same Virtual VLAN NIC
But the problem is when I try to start a virtual machine bridged to a different Virtual VLAN NIC,
while those VMs bridged to first Virtual VLAN NIC are still running.
I get a crash with message: VERR_INTNET_INCOMPATIBLE_TRUNK
Detailed message from logs: The network already exists with a different trunk configuration.
567 00:00:00.855 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={9511bc54-15ee-4ddf-808e-472aba03809c} aComponent={Console} aText={Failed to open/create the internal network 'HostInterfaceNetworking-Intel(R) PRO/1000 MT Desktop Adapter - VLAN : VLAN3024' (VERR_INTNET_INCOMPATIBLE_TRUNK).
I tried Virtual Box version 2.2.4-47978 and also latest beta 3.0.6_BETA1-51790 still the same
The only difference is that 2.2.4 locks up hard after a couple of VLAN crashes and I need to reboot my host.
For example:
start VM1 bridged to VLAN1 - OK
start VM2 bridged to VLAN1 - OK
start VM3 bridged to VLAN2 - CRASH!!!
Other example:
start VM1 bridged to VLAN1 - OK
start VM2 bridged to VLAN1 - OK
stop VM1 and VM2
start VM3 bridged to VLAN2 - OK
I submitted a bug: http://www.virtualbox.org/ticket/4934
Anyone has this same problem? Any workarounds?
Windows Vista Business 64bit host SP2
I have 3 VLANs on an Intel PRO/1000 MT Desktop Adapter lan card.
I have installed the Intel Proset drivers for the NIC v14.3
They enable me to have each VLAN with its own virtual NIC in the form of for example: Intel(R) PRO/1000 MT Desktop Adapter - VLAN : VLAN2018 (The only way to use VLAN in Windows I know of)
If I start a virtual machine bridged to one of the Virtual VLAN NICs it is OK, everything is working
I can also start more virtual machines bridged to the same Virtual VLAN NIC
But the problem is when I try to start a virtual machine bridged to a different Virtual VLAN NIC,
while those VMs bridged to first Virtual VLAN NIC are still running.
I get a crash with message: VERR_INTNET_INCOMPATIBLE_TRUNK
Detailed message from logs: The network already exists with a different trunk configuration.
567 00:00:00.855 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={9511bc54-15ee-4ddf-808e-472aba03809c} aComponent={Console} aText={Failed to open/create the internal network 'HostInterfaceNetworking-Intel(R) PRO/1000 MT Desktop Adapter - VLAN : VLAN3024' (VERR_INTNET_INCOMPATIBLE_TRUNK).
I tried Virtual Box version 2.2.4-47978 and also latest beta 3.0.6_BETA1-51790 still the same
The only difference is that 2.2.4 locks up hard after a couple of VLAN crashes and I need to reboot my host.
For example:
start VM1 bridged to VLAN1 - OK
start VM2 bridged to VLAN1 - OK
start VM3 bridged to VLAN2 - CRASH!!!
Other example:
start VM1 bridged to VLAN1 - OK
start VM2 bridged to VLAN1 - OK
stop VM1 and VM2
start VM3 bridged to VLAN2 - OK
I submitted a bug: http://www.virtualbox.org/ticket/4934
Anyone has this same problem? Any workarounds?