https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255086
--- Comment #8 from Andriy Gapon ---
Also interesting that pre-iflib vmxnet3 driver does not seem to hit this
problem even when MSI-X is enabled and used (and the blacklist is disabled).
--
You are receiving this mail because:
You are the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255086
--- Comment #7 from Andriy Gapon ---
For posterity, in comment #3 I suggested incorrect value for the tunable
resulting in a double negation.
The suggestion should be to set dev.vmx.0.iflib.disable_msix=1 in
/boot/loader.conf.
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255086
--- Comment #6 from i...@murrawhip.net ---
I was hit by this. I also can't upgrade from esxi 5.5. Just wanted to say that
setting ethernet0.intrMode to 2 has stopped my vms from crashing when dhclient
runs.
I don't know what the performance
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255086
--- Comment #5 from Andriy Gapon ---
Another option is to disable MSI-X for the network interface in the VMWare
configuration. There is (possibly undocumented) configuration option
ethernet%d.intrMode. It can be set to 2 to enable MSI inter
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255086
--- Comment #4 from Markus Wild ---
(In reply to Andriy Gapon from comment #3)
No, this doesn't work (same crash), and I'm on the last 5.5 version.
Can't upgrade due to license issues.
I've just found: https://reviews.freebsd.org/D22819
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255086
--- Comment #3 from Andriy Gapon ---
You may want to check if dev.vmx.0.iflib.disable_msix=0 works as a workaround.
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255086
--- Comment #2 from Andriy Gapon ---
It looks like you are hitting a bug in vmware.
I recall having a similar issue with 5.5 U1.
Try upgrading to the latest patch version or a newer version altogether.
--
You are receiving this mail becau
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255086
--- Comment #1 from Markus Wild ---
Just tried to add a vmxnet3 interface to the new VM that was configured
with 2 E1000 interfaces. As soon as I do
ifconfig vmx0 up
the whole VM resets, no panic string. I started the VM with verbose flag
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255086
Bug ID: 255086
Summary: 13.0-RELEASE installer reboots when trying to DHCP
vmx0 interface
Product: Base System
Version: 13.0-STABLE
Hardware: amd64
OS
