Ticket #4934 (reopened defect)
Cannot start VM bridged to a VLANs when another VM bridged to another VLAN is already running
|Reported by:||avok00||Owned by:|
|Version:||VirtualBox 3.0.4||Keywords:||VLAN, VERR_INTNET_INCOMPATIBLE_TRUNK|
|Cc:||2.2.4 - 3.06 B1||Guest type:||other|
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
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
- Status changed from new to closed
- Resolution set to fixed
- Status changed from closed to reopened
- Resolution fixed deleted