VirtualBox

Opened 7 years ago

Closed 6 years ago

#17475 closed defect (worksforme)

connect to bridge cause panic

Reported by: Meno Abels Owned by:
Component: network/hostif Version: VirtualBox 5.2.6
Keywords: kernel bridge Cc:
Guest type: other Host type: other

Description (last modified by Valery Ushakov)

Hello,

there are a lot of open issues about bridge but non of them seams to match to my problems. I use private bridges like the automatic created dockerbridge on linux or on macos a small script like this: 

ifconfig bridge0 create
ifconfig bridge0 10.24.1.1/24 up
ifconfig bridge0 inet6 fd00::10:24:1:1/64 up
sysctl net.inet.ip.forwarding=1

than i use the bridge device from virtualbox like: 

<Network>
  <Adapter slot="0" enabled="true" MACAddress="0800273B3B52" type="82540EM">
    <DisabledModes>
      <InternalNetwork name="intnet"/>
      <NATNetwork name="NatNetwork"/>
    </DisabledModes>
    <BridgedInterface name="br0"/>
  </Adapter>
</Network>

now on both platforms linux as macos the host system is send to kernel stalls(panics). This behavior was occures since Version 5. My setups works perfect on VirutualBox 4. I would like to provide some crashlogs but on both platforms there is nothing written in to the log files and i not started to invest more time into it. On macos the OS Crashscreen is shown an reboot is triggered. On linux the system stop's and sysrq seams not work either.

Is there any chance to get this feature back working?

thx in advance

meno

Attachments (1)

Screen Shot 2018-01-29 at 14.25.19.png​ (131.7 KB ) - added by Meno Abels 7 years ago.
Bridge Setup

Download all attachments as: .zip

Change History (19)

comment:1 by Valery Ushakov, 7 years ago

Description: modified (diff)

I assume the examples are copied from different machines and that br0 and bridge0 are the same bridge.

When you say this started with version 5, what is the actual version you tried? Have you upgraded from version 4 straight to 5.2.6 (or have you just left the bug tracker's default unchanged)?

comment:2 by Meno Abels, 7 years ago

Yes the bridge is abstract it's about to connect to an existing bridge device respecting the different implementation of the OS.

I discovered this crashes on the move from 4.x to 5.0. Usally i follow with my work machine the actual versions on the date release of them.

Last edited 7 years ago by Meno Abels (previous) (diff)

comment:3 by Valery Ushakov, 7 years ago

Have you tried using a host-only interface and then adding it to the bridge.

Bridging a VM directly to a bridge interface has other issues, e.g. with checksum optimizations. E.g. a VM bridged to lxcbr0 currently can't talk to an LXC container on the same bridge unless you turn off checksum offloading in the container.

comment:4 by Valery Ushakov, 7 years ago

Also, can you try to bring up your typical setup without forwarding enabled and then enable forwarding as the very last step (when a bridged VM is already running).

comment:5 by Meno Abels, 7 years ago

I just tried the host-only approach, no crash but also not working, it looks like that i'm not able to configure a host-only interface without an dhcp server and if i configure my guest by hand the packets will not passed to the bridge.

ifconfig brxxxx addm vboxnet0

and than look on brxxx with traffic from vboxnet0 but is seams not working.

the disabling of the dhcp is a different topic but i tried to switch the checkbox in the "Host Network Manager" which not result in the disabling off the dhcpserver.

I tested only on macos, i won't like to crash my linux host which is somewhere in the cloud

Meno

comment:6 by Valery Ushakov, 7 years ago

I can't seem to reproduce the crash you are seeing. Please, provide exact steps to reproduce it.

comment:7 by Meno Abels, 7 years ago

This crash is on macos with my bridge setup and two running linux guest doing some network io

Meno 

Anonymous UUID:       8410B5D5-D3CB-62D4-52B4-714A45295477

Wed Jan 24 11:09:51 2018

*** Panic Report ***
panic(cpu 2 caller 0xffffff800376f2e9): Kernel trap at 0xffffff800368c8b7, type 14=page fault, registers:
CR0: 0x0000000080010033, CR2: 0x0000000000000048, CR3: 0x000000023691712d, CR4: 0x00000000001627e0
RAX: 0xffffff802bda84f0, RBX: 0x0000000000000000, RCX: 0x0000000009000000, RDX: 0xffffff8003e9a468
RSP: 0xffffff91f7eb34c0, RBP: 0xffffff91f7eb34e0, RSI: 0xffffff8004047460, RDI: 0xffffff8003e9a468
R8:  0x0000000000000000, R9:  0xffffff802bda84f0, R10: 0x0000000000000005, R11: 0xffffff8003fe03b8
R12: 0xffffff81e42a5700, R13: 0xffffff8027dc9008, R14: 0xffffff8003e9a468, R15: 0x0000000000000246
RFL: 0x0000000000010046, RIP: 0xffffff800368c8b7, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x0000000000000048, Error code: 0x0000000000000000, Fault CPU: 0x2, PL: 2, VF: 0

Backtrace (CPU 2), Frame : Return Address
0xffffff91f7eb2f70 : 0xffffff80036505f6 
0xffffff91f7eb2fc0 : 0xffffff800377d604 
0xffffff91f7eb3000 : 0xffffff800376f0f9 
0xffffff91f7eb3080 : 0xffffff8003602120 
0xffffff91f7eb30a0 : 0xffffff800365002c 
0xffffff91f7eb31d0 : 0xffffff800364fdac 
0xffffff91f7eb3230 : 0xffffff800376f2e9 
0xffffff91f7eb33b0 : 0xffffff8003602120 
0xffffff91f7eb33d0 : 0xffffff800368c8b7 
0xffffff91f7eb34e0 : 0xffffff80038f6520 
0xffffff91f7eb3550 : 0xffffff80038f608c 
0xffffff91f7eb35d0 : 0xffffff7f86a86f56 
0xffffff91f7eb3640 : 0xffffff7f86a865ef 
0xffffff91f7eb3690 : 0xffffff91f8a0f444 
0xffffff91f7eb3790 : 0xffffff91f8a09c33 
0xffffff91f7eb3830 : 0xffffff91f8a082a6 
0xffffff91f7eb38d0 : 0xffffff91f895a982 
0xffffff91f7eb3940 : 0xffffff91f895892f 
0xffffff91f7eb39c0 : 0xffffff7f86a07e46 
0xffffff91f7eb3a50 : 0xffffff7f86a07890 
0xffffff91f7eb3a90 : 0xffffff7f86a19acf 
0xffffff91f7eb3b50 : 0xffffff80038c856a 
0xffffff91f7eb3b80 : 0xffffff80038bd3ef 
0xffffff91f7eb3c00 : 0xffffff80038af25b 
0xffffff91f7eb3e00 : 0xffffff8003af29eb 
0xffffff91f7eb3e30 : 0xffffff8003b444ec 
0xffffff91f7eb3f40 : 0xffffff8003bfb3e8 
0xffffff91f7eb3fa0 : 0xffffff8003602906 
      Kernel Extensions in backtrace:
         org.virtualbox.kext.VBoxDrv(5.2.6)[C32CCC8B-7E44-3974-BEC0-9C1FA570690D]@0xffffff7f86a06000->0xffffff7f86a68fff
         org.virtualbox.kext.VBoxNetFlt(5.2.6)[552BD757-0D66-3F90-9A20-C6C7881F4A2F]@0xffffff7f86a85000->0xffffff7f86a89fff
            dependency: org.virtualbox.kext.VBoxDrv(5.2.6)[C32CCC8B-7E44-3974-BEC0-9C1FA570690D]@0xffffff7f86a06000

BSD process name corresponding to current thread: VirtualBoxVM

Mac OS version:
17C205

Kernel version:
Darwin Kernel Version 17.3.0: Thu Nov  9 18:09:22 PST 2017; root:xnu-4570.31.3~1/RELEASE_X86_64
Kernel UUID: 87641697-A3DD-30C4-B010-E65ECE57550B
Kernel slide:     0x0000000003200000
Kernel text base: 0xffffff8003400000
__HIB  text base: 0xffffff8003300000
System model name: MacBookPro11,1 (Mac-189A3D4F975D5FFC)

System uptime in nanoseconds: 1198050976447
last loaded kext at 276628911269: com.paragon-software.lvm-for-mac	1 (addr 0xffffff7f86a9f000, size 159744)
last unloaded kext at 473107753197: com.apple.filesystems.msdosfs	1.10 (addr 0xffffff7f86a90000, size 61440)
loaded kexts:
org.virtualbox.kext.VBoxNetAdp	5.2.6
org.virtualbox.kext.VBoxNetFlt	5.2.6
org.virtualbox.kext.VBoxUSB	5.2.6
com.intel.kext.intelhaxm	6.0.3
org.virtualbox.kext.VBoxDrv	5.2.6
com.paragon-software.filesystems.extfs	320.0.11
it.unbit.foohid	1
com.nomachine.driver.nxau	4.1.b2
com.apple.driver.AGPM	110.23.24
com.apple.driver.ApplePlatformEnabler	2.7.0d0
com.apple.driver.X86PlatformShim	1.0.0
com.apple.filesystems.autofs	3.0
com.apple.driver.AppleUpstreamUserClient	3.6.4
com.apple.driver.AppleHDA	280.12
com.apple.driver.AudioAUUC	1.70
com.apple.driver.AppleGraphicsDevicePolicy	3.16.21
com.apple.AGDCPluginDisplayMetrics	3.16.2
com.apple.driver.AppleHV	1
com.apple.iokit.IOUserEthernet	1.0.1
com.apple.iokit.IOBluetoothSerialManager	6.0.2f2
com.apple.driver.pmtelemetry	1
com.apple.Dont_Steal_Mac_OS_X	7.0.0
com.apple.driver.AppleIntelHD5000Graphics	10.3.0
com.apple.driver.eficheck	1
com.apple.driver.AppleBacklight	170.10.2
com.apple.driver.AppleThunderboltIP	3.1.1
com.apple.driver.AppleLPC	3.1
com.apple.driver.AppleIntelSlowAdaptiveClocking	4.0.0
com.apple.driver.AppleMCCSControl	1.5.3
com.apple.driver.AppleSMCLMU	211
com.apple.driver.AppleIntelFramebufferAzul	10.3.0
com.apple.driver.AppleOSXWatchdog	1
com.apple.driver.AppleCameraInterface	6.01.2
com.apple.driver.AppleUSBCardReader	439.30.4
com.apple.driver.AppleUSBTCButtons	254
com.apple.driver.AppleUSBTCKeyboard	254
com.apple.filesystems.apfs	748.31.8
com.apple.filesystems.hfs.kext	407.30.1
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless	1.0.0d1
com.apple.BootCache	40
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib	1.0.0
com.apple.driver.AppleAHCIPort	329
com.apple.driver.AirPort.BrcmNIC	1220.28.1a3
com.apple.driver.AppleSmartBatteryManager	161.0.0
com.apple.driver.AppleRTC	2.0
com.apple.driver.AppleACPIButtons	6.1
com.apple.driver.AppleHPET	1.8
com.apple.driver.AppleSMBIOS	2.1
com.apple.driver.AppleACPIEC	6.1
com.apple.driver.AppleAPIC	1.7
com.apple.nke.applicationfirewall	183
com.apple.security.TMSafetyNet	8
com.apple.security.quarantine	3
com.apple.IOBufferCopyEngineTest	1
com.apple.iokit.IOUSBUserClient	900.4.1
com.apple.kext.triggers	1.0
com.apple.driver.DspFuncLib	280.12
com.apple.kext.OSvKernDSPLib	526
com.apple.driver.AppleGraphicsControl	3.16.21
com.apple.driver.AppleSSE	1.0
com.apple.AppleGPUWrangler	3.16.2
com.apple.driver.AppleBacklightExpert	1.1.0
com.apple.iokit.IONDRVSupport	517.22
com.apple.driver.X86PlatformPlugin	1.0.0
com.apple.driver.IOPlatformPluginFamily	6.0.0d8
com.apple.iokit.IOSlowAdaptiveClockingFamily	1.0.0
com.apple.driver.AppleSMBusController	1.0.18d1
com.apple.AppleGraphicsDeviceControl	3.16.21
com.apple.iokit.IOAcceleratorFamily2	376.6
com.apple.iokit.IOSurface	209.2.2
com.apple.driver.AppleHDAController	280.12
com.apple.iokit.IOGraphicsFamily	517.22
com.apple.iokit.IOHDAFamily	280.12
com.apple.iokit.IOAudioFamily	206.5
com.apple.vecLib.kext	1.2.0
com.apple.iokit.IOSerialFamily	11
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport	6.0.2f2
com.apple.iokit.IOBluetoothHostControllerUSBTransport	6.0.2f2
com.apple.iokit.IOBluetoothHostControllerTransport	6.0.2f2
com.apple.iokit.IOBluetoothFamily	6.0.2f2
com.apple.driver.usb.AppleUSBHub	1.2
com.apple.driver.AppleUSBMultitouch	261
com.apple.driver.usb.IOUSBHostHIDDevice	1.2
com.apple.driver.usb.networking	5.0.0
com.apple.driver.usb.AppleUSBHostCompositeDevice	1.2
com.apple.filesystems.hfs.encodings.kext	1
com.apple.iokit.IOAHCIBlockStorage	301.20.1
com.apple.iokit.IOAHCIFamily	288
com.apple.driver.AppleThunderboltDPInAdapter	5.0.2
com.apple.driver.AppleThunderboltDPAdapterFamily	5.0.2
com.apple.driver.AppleThunderboltPCIDownAdapter	2.1.3
com.apple.driver.AppleThunderboltNHI	4.5.6
com.apple.iokit.IOThunderboltFamily	6.6.3
com.apple.iokit.IO80211Family	1200.12.2
com.apple.driver.mDNSOffloadUserClient	1.0.1b8
com.apple.driver.corecapture	1.0.4
com.apple.driver.usb.AppleUSBXHCIPCI	1.2
com.apple.driver.usb.AppleUSBXHCI	1.2
com.apple.driver.usb.AppleUSBHostPacketFilter	1.0
com.apple.iokit.IOUSBFamily	900.4.1
com.apple.driver.AppleUSBHostMergeProperties	1.2
com.apple.driver.AppleEFINVRAM	2.1
com.apple.driver.AppleEFIRuntime	2.1
com.apple.iokit.IOHIDFamily	2.0.0
com.apple.iokit.IOSMBusFamily	1.1
com.apple.security.sandbox	300.0
com.apple.kext.AppleMatch	1.0.0d1
com.apple.iokit.IOBufferCopyEngineFamily	1
com.apple.driver.DiskImages	480.30.2
com.apple.driver.AppleFDEKeyStore	28.30
com.apple.driver.AppleEffaceableStorage	1.0
com.apple.driver.AppleKeyStore	2
com.apple.driver.AppleUSBTDM	439.30.4
com.apple.driver.AppleMobileFileIntegrity	1.0.5
com.apple.iokit.IOUSBMassStorageDriver	140.30.1
com.apple.iokit.IOSCSIBlockCommandsDevice	404.30.2
com.apple.iokit.IOSCSIArchitectureModelFamily	404.30.2
com.apple.iokit.IOStorageFamily	2.1
com.apple.driver.AppleCredentialManager	1.0
com.apple.driver.KernelRelayHost	1
com.apple.iokit.IOUSBHostFamily	1.2
com.apple.driver.usb.AppleUSBCommon	1.0
com.apple.driver.AppleBusPowerController	1.0
com.apple.driver.AppleSEPManager	1.0.1
com.apple.driver.IOSlaveProcessor	1
com.apple.iokit.IOReportFamily	31
com.apple.iokit.IOTimeSyncFamily	650.5
com.apple.iokit.IONetworkingFamily	3.4
com.apple.driver.AppleACPIPlatform	6.1
com.apple.driver.AppleSMCRTC	1.0
com.apple.driver.AppleSMC	3.1.9
com.apple.iokit.IOPCIFamily	2.9
com.apple.iokit.IOACPIFamily	1.4
com.apple.kec.pthread	1
com.apple.kec.corecrypto	1.0
com.apple.kec.Libm	1

EOF
Model: MacBookPro11,1, BootROM MBP111.0142.B00, 2 processors, Intel Core i7, 2,8 GHz, 16 GB, SMC 2.16f68
Graphics: Intel Iris, Intel Iris, Built-In
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343147533641465238412D50422020
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343147533641465238412D50422020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x112), Broadcom BCM43xx 1.0 (7.77.37.5.1a3)
Bluetooth: Version 6.0.2f2, 3 services, 18 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
Network Service: Apple USB Ethernet Adapter, Ethernet, en3
Serial ATA Device: APPLE SSD SD0256F, 251 GB
USB Device: USB 3.0 Bus
USB Device: Internal Memory Card Reader
USB Device: Apple Internal Keyboard / Trackpad
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
USB Device: Yubikey 4 OTP+U2F+CCID
Thunderbolt Bus: MacBook Pro, Apple Inc., 17.2

in reply to:  7 comment:8 by Valery Ushakov, 7 years ago

Replying to fastandfearless:

This crash is on macos with my bridge setup [...]

But what is your bridge setup? Please, provide description, so that we can try to reproduce it locally.

comment:9 by Meno Abels, 7 years ago

Hi,

as i wrote before: 

sudo ifconfig bridge0 create
sudo ifconfig bridge0 10.24.1.1/24 up
sudo ifconfig bridge0 inet6 fd00::10:24:1:1/64 up
sudo sysctl net.inet.ip.forwarding=1

thats it on macosx

comment:10 by Valery Ushakov, 7 years ago

Does that bridge contains any host interfaces? Where does the forwarding comes into it? Do you use the bridge only for VMs and then route VMs traffic to the outside world? In the latter is the case, why do you need to bridge to a bridge instead of just talking to the VMs via host-only?

by Meno Abels, 7 years ago

Attachment: Screen Shot 2018-01-29 at 14.25.19.png​ added

Bridge Setup

in reply to:  10 ; comment:11 by Meno Abels, 7 years ago

Replying to vushakov:

Does that bridge contains any host interfaces? Where does the forwarding comes into it? Do you use the bridge only for VMs and then route VMs traffic to the outside world? In the latter is the case, why do you need to bridge to a bridge instead of just talking to the VMs via host-only?

See the a attached picture:

And: i'm doing nat on macos and start a dnsmasq as dhcp, but this is not needed in my other setup where i just have another interface put into that bridge(on linux), and it crashes in the same why: 

pfctl -f - <<RULES
nat on en0 proto {tcp udp icmp} from 10.24.1.0/24 to !10.24.1.0/24  -> (en0)
RULES
pfctl -e
nohup /usr/local/sbin/dnsmasq \
  --dhcp-range=10.24.1.100,10.24.1.200 \
  --dhcp-leasefile=/Users/menabe/dhcp-lease.file \
  --interface=bridge0 \
  -d \
  -z \
  --log-dhcp \
  --listen-address=0.0.0.0 &
}}}[[Image()]]
Version 0, edited 7 years ago by Meno Abels (next)

in reply to:  11 ; comment:12 by Valery Ushakov, 7 years ago

Replying to fastandfearless:

Replying to vushakov:

Does that bridge contains any host interfaces? Where does the forwarding comes into it? Do you use the bridge only for VMs and then route VMs traffic to the outside world? In the latter is the case, why do you need to bridge to a bridge instead of just talking to the VMs via host-only?

See the a attached picture:

That picture just shows that you bridge the VM to bridge0. I was asking about the host's bridge0 interface itself.

Also, from the comment:7 I gather that the crash is not immediate. The VMs can run for a while before the crash happens, right?

in my other setup where i just have another interface put into that bridge (on linux), and it crashes in the same way

What do you mean by "another interface"? Second VM bridged to the same host's bridge interface? A real host interface?

in reply to:  12 comment:13 by Meno Abels, 7 years ago

Replying to vushakov:

Replying to fastandfearless:

Replying to vushakov:

Does that bridge contains any host interfaces? Where does the forwarding comes into it? Do you use the bridge only for VMs and then route VMs traffic to the outside world? In the latter is the case, why do you need to bridge to a bridge instead of just talking to the VMs via host-only?

See the a attached picture:

That picture just shows that you bridge the VM to bridge0. I was asking about the host's bridge0 interface itself.

Also, from the comment:7 I gather that the crash is not immediate. The VMs can run for a while before the crash happens, right?

in my other setup where i just have another interface put into that bridge (on linux), and it crashes in the same way

What do you mean by "another interface"? Second VM bridged to the same host's bridge interface? A real host interface?

The host bridge is generate with this: 

sudo ifconfig bridge0 create
sudo ifconfig bridge0 10.24.1.1/24 up
sudo ifconfig bridge0 inet6 fd00::10:24:1:1/64 up
sudo sysctl net.inet.ip.forwarding=1

and the nat and dnsmasq which i said before.

Both VM run on the same bridge, and it is enough to start a ping to 10.24.1.1 and just wait a small while.

comment:14 by Valery Ushakov, 7 years ago

I tried this on El Capitan (10.11.6) and I can't reproduce it. I don't have dnsmasq installed, so I just configured the guests statically. Both guests can successfully talk to the outside world through PF's NAT.

in reply to:  14 comment:15 by Meno Abels, 7 years ago

Replying to vushakov:

I tried this on El Capitan (10.11.6) and I can't reproduce it. I don't have dnsmasq installed, so I just configured the guests statically. Both guests can successfully talk to the outside world through PF's NAT.

I use 10.13.3 High Sierra and it could be that this problem is not related to virualbox 4.x to 5.x update on my site it could be also related to my high sierra update.

Sorry for the possible misleading information. I hope i get today an linux host to reproduce the problem on them also.

comment:16 by breadncup, 6 years ago

I have a same issue with this. I’m on High Sierra as a host and run a virtualbox for ubuntu. Now, as soon as I set up the network as bridged, it went to the same kernel panic.

It’s very easy to reproduce.

  1. Get High Sierra MacOSX.
  2. Set up netowrk as Bridged network not NAT in the VM.
  3. Start the vm

It will crash immediately.

in reply to:  16 comment:17 by breadncup, 6 years ago

Nevermind.

It does not happen anymore.

Thanks,

Replying to breadncup:

I have a same issue with this. I’m on High Sierra as a host and run a virtualbox for ubuntu. Now, as soon as I set up the network as bridged, it went to the same kernel panic.

It’s very easy to reproduce.

  1. Get High Sierra MacOSX.
  2. Set up netowrk as Bridged network not NAT in the VM.
  3. Start the vm

It will crash immediately.

comment:18 by Valery Ushakov, 6 years ago

Resolution: → worksforme
Status: new → closed

Thanks for the update.

Note: See TracTickets for help on using tickets.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette