Opened 11 years ago
Last modified 10 years ago
#11534 closed defect
vnic VID property is misteriously zeroed on Solaris 11.1 after VM start — at Initial Version
| Reported by: | sscdvp | Owned by: | |
|---|---|---|---|
| Component: | network | Version: | VirtualBox 4.2.8 |
| Keywords: | Cc: | ||
| Guest type: | all | Host type: | Solaris |
Description
I use VB 4.2.8
On Solaris 11.1 SRU1.4 VID property for vnic interface is zeroed after VM start. ORACLE VB uses that vnic interface. vnic created on the base of dot1Q trunk. The same problem was observed for vlan interfaces too.
How to reproduce:
- dladm create-vnic -l net0 -v 998 v4vid998link0
- dladm show-vnic
LINK OVER SPEED MACADDRESS MACADDRTYPE VID upv4vid201link0 net0 100 2:8:20:5b:23:4c random 201 upv4vid9link0 net0 100 2:8:20:a1:96:5f random 9 upv4vid944link0 net0 100 2:8:20:85:4b:6 random 944 v4vid998link0 net0 100 8:0:27:d1:fe:fe random 998
- Create VM in ORACLE Virtualbox.
- Add network "bridged adapter" v4vid998link0
- Start VM
- dladm show-vnic
LINK OVER SPEED MACADDRESS MACADDRTYPE VID upv4vid201link0 net0 100 2:8:20:5b:23:4c random 201 upv4vid9link0 net0 100 2:8:20:a1:96:5f random 9 upv4vid944link0 net0 100 2:8:20:85:4b:6 random 944 v4vid998link0 net0 100 8:0:27:d1:fe:fe fixed 0
- No IP conectivity in VM.
Workaround:
After VM start restore VID setting: dladm modify-vnic -v 998 v4vid998link0 That helps to restore IP connectivity for that VM.
NOTE 1: the issue appears for the first time after VM started. VM reboot process doesn't affect IP connectivity. Only VM poweroff makes the issue to appear again. NOTE 2: vlan interfaces are affected by the issue too. NOTE 3: Seen the problem in 4.1.x and 4.2.x builds.
