How to reproduce:
Trying to install new 13.0-RELEASE vm on vmware 5.5 using disc ISO:
- VM is configured for 16GB, 4 cores, 2 vmxnet3 interfaces
- installer starts from ISO:
- configure auto-ZFS
- change swap to 16GB
- select stripe on the single disk (da0)
- confirm and let the installer set up the disk
- when the network installer starts and asks whether to configure vmx0:
- configure ipv4
- configure using DHCP
=> VM reboots, no panic, no additional information. Console window goes
black and the VM eventually reboots. I don't see any error in vmware
When I try the same process using 2 E1000 interfaces, it works fine.
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
on, no change.
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 may want to check if dev.vmx.0.iflib.disable_msix=0 works as a workaround.
(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
If I revert this and boot with the release-kernel minus this change,
vmx works fine. How can I achieve the same result without patching the
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 interrupts or to 1 to enable legacy interrupts only.
In any case, a VMWare crash is a VMWare bug.
It should not crash no matter what a guest does.