This seems to be an ESXi bug.

Exact same error being reported here.  I've followed their suggested
settings and was no longer able to produce the kernel panic.

https://bugzilla.kernel.org/show_bug.cgi?id=191201

Reply via email to