Crash after update to 20.7 on xen 4.11(debian)

[amw]

After update from 20.1 to 20.7 domU crash. Also tried a fresh installation from iso. The machine crash after configuring network devices.

Thank you for help.

[amw]

Figured out some more information. Hope there is someone who can help....

Configuration:
OPNsense hvm with 5 type=vif devices to the bridges. Debian 10.6 with xen 4.11.4
20.1 work fine on 20.7 on some devices the error:

[20201017T14:36:11.788Z]  D0           w event   /local/domain/63/device/vif/3/request-multicast-control FFFF88802BA3AD90
[20201017T14:36:11.788Z]  D63          error     EINVAL

happens when bringing up the devices in OPNsense after sysctl.

[His.Dudeness]

Hi,
I don't know if it's related but my OPNsense VM (on Xen with XCP-ng 7.6) didn't like the upgrade from 20.1.9_1 to 20.7 either.
It crashes during boot after the update...  :-\

I reverted to the last snapshot before upgrade and now it's working again.

cheers
Michael

[marcelmah]

I have the same, but only when I add more then 5 networks (so it works fine with only 4 networks).
Because how Xen (we use XCP-ng) works with VLAN's we require 7 networks.

[amw]

Does anyone have a solution for this problem?

[marcelmah]

Hi,

I created a screencap of a OPNsense 20.1 VM with more then 4 NIC's and one of OPNsense 20.7 with 4 NIC's running.

I then add a NIC and reboot the VM, it then ends up in a kernel panic. If I force shutdown the VM and remove the 5th NIC all is fine again(after some automatic filesystem fixes at next boot).

You can view the video on YouTube:
https://www.youtube.com/watch?v=qh6KTYLYya8

Upgrading from the 20.1 to 20.7 ends up in the kernel panic.

I hope someone can identify (and fix) the problem.
I assume it has to do with he XN drivers for the network interfaces where the need for more then 4 NIC's comes from because the lack of VLAN support. In this case I can't use option 2 for VLAN's because I don't have any free network ports (you can't use the management NIC).

This also happens without the plugin os-xen, no difference.

Oh please note the IP ranges you see 130.62.x.x are internal ranges even though they're officially not... don't ask.

[kalpin]

This issue exactly I have now. If I remove the 5th interface then OpnSense is working. Any solutions ?

[marcelmah]

I added a new physical nic with 4 ports and user passthrough. This way I can also manage the VLAN natively in OPNsense.