Opened 7 months ago
Closed 4 months ago
#22072 closed defect (fixed)
fedora 40 kernel panic if virtualbox is running a bridged VM when podman runs => fixed in svn/7.0.x x>18
| Reported by: | Derek Schrock | Owned by: | |
|---|---|---|---|
| Component: | network | Version: | VirtualBox-7.0.18 |
| Keywords: | Cc: | ||
| Guest type: | Linux | Host type: | Linux |
Description
With 7.0.16 and 7.0.18 on Fedora 40 x86_64 if I have a vbox VM running where it has a bridged adapter then run a rootless container (don't know about rootful) podman-run the system will kernel panic 99% of the time.
If the same VM is ran with a NAT interface everything is fine. I have also tried two different interfaces on the host that use a different driver (e1000e and bnx2).
See attached vmcore-dmesg.txt from kdump.
Don't know who is to blame here kernel, vbox, or podman.
Attachments (2)
Change History (5)
by , 7 months ago
| Attachment: | vmcore-dmesg-e1000e.txt added |
|---|
comment:1 by , 6 months ago
A couple extra points of info. podman rootless container with slirp4netns doesn't have the same issue. So this is limited to podman with patsa (default in 5.0).
A simpler test case (in some cases) is to run pasta when you have a vbox vm with bridged interface. This is the the second MAC address in the vmcore dmesg files.
[ 3524.139008] VBoxNetFlt: attached to 'enp0s31f6' / 18:66:da:4a:21:24 ... [ 3579.996939] VBoxNetFlt: attached to 'enp0s31f6' / f2:80:9c:5d:a0:e4
3524.139008 vbox VBoxNetFlt attaching to physical host interface.
3579.996939 vbox VBoxNetFlt trying to attach to the pasta created interface.
comment:3 by , 4 months ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
| Summary: | fedora 40 kernel panic if virtualbox is running a bridged VM when podman runs → fedora 40 kernel panic if virtualbox is running a bridged VM when podman runs => fixed in svn/7.0.x x>18 |
Closing as 'fixed' based on reporter feedback.
bridged host e1000e kernel panic