VMWare virtual machine running NetBSD crashes with "Flexible" network interface

[Jason Mitchell <jmitchel%bigjar.com@localhost>]

Hello,

   I've experienced this problem on both the free version of VMWare 
running under Linux and VMWare ESX server. With the Flexible network 
driver and a virtual IDE hard disk, a VMWare machine running NetBSD will 
just "go away" under a combination of high network and disk load. 
There's no crash, the virtual machine just goes "power's off"

   The fix for this problem is to use the e1000 driver. The free Linux 
version doesn't show this as an option, unless you select "Other 
(64-bit)" as the OS type. This works even if you're running the 32-bit 
version of VMWare. I figured I should post this here in case someone 
else runs in to the same problem. I'm attaching the VMWare crash info below.

Jason M.

Sep 22 04:07:33.342: vcpu-0| Core dump with build build-175625
Sep 22 04:07:33.441: vcpu-0| Writing monitor corefile 
"/vmfs/volumes/4a1c6645-8d
a19ecc-0f2a-0022192f8d1d/New Virtual Machine/vmware-core.gz"
Sep 22 04:07:33.441: vcpu-0| CoreDump: dumping core with superuser 
privileges
Sep 22 04:07:33.504: vcpu-0| Saving busmem frames
Sep 22 04:07:33.506: vcpu-0| Saving anonymous memory
Sep 22 04:07:33.508: vcpu-0| Beginning monitor coredump
Sep 22 04:07:33.688: vcpu-0| End monitor coredump
Sep 22 04:07:33.688: vcpu-0| Beginning extended monitor coredump
Sep 22 04:07:33.688: vcpu-0| Writing anonymous pages at pos: 401000
Sep 22 04:07:34.264: vcpu-0| Writing monitor corefile 
"/vmfs/volumes/4a1c6645-8d
a19ecc-0f2a-0022192f8d1d/New Virtual Machine/vmware64-core.gz"
Sep 22 04:07:34.264: vcpu-0| CoreDump: dumping core with superuser 
privileges
Sep 22 04:07:34.289: vcpu-0| VMK Stack for vcpu 0 is at 0x4100c6701000
Sep 22 04:07:34.289: vcpu-0| Saving busmem frames
Sep 22 04:07:34.291: vcpu-0| Saving anonymous memory
Sep 22 04:07:34.293: vcpu-0| Beginning monitor coredump
Sep 22 04:07:35.324: vcpu-0| End monitor coredump
Sep 22 04:07:35.325: vcpu-0| Beginning extended monitor coredump
Sep 22 04:07:35.325: vcpu-0| Writing anonymous pages at pos: 4008000
Sep 22 04:07:37.555: vcpu-0| Msg_Post: Error
Sep 22 04:07:37.555: vcpu-0| [msg.log.monpanic] *** VMware ESX internal 
monitor
error ***
Sep 22 04:07:37.555: vcpu-0| vcpu-0:NOT_IMPLEMENTED 
devices/net/vlance_shared.c:
705
Sep 22 04:07:37.555: vcpu-0| [msg.log.monpanic.report] Please report 
this proble
m by selecting menu item Help > VMware on the Web > Request Support, or 
by going
to the Web page 
"http://www.vmware.com/info?id=8&logFile=%2fvmfs%2fvolumes%2f4a
1c6645%2d8da19ecc%2d0f2a%2d0022192f8d1d%2fNew%20Virtual%20Machine%2fvmware%2elog 

&coreLocation=%2fvmfs%2fvolumes%2f4a1c6645%2d8da19ecc%2d0f2a%2d0022192f8d1d%2fNe 

w%20Virtual%20Machine%2fvmware%2dcore%2egz%2c%20%2fvmfs%2fvolumes%2f4a1c6645%2d8 

da19ecc%2d0f2a%2d0022192f8d1d%2fNew%20Virtual%20Machine%2fvmware64%2dcore%2egz". 

Please provide us with the log file 
(/vmfs/volumes/4a1c6645-8da19ecc-0f2a-00221
92f8d1d/New Virtual Machine/vmware.log) and the core file(s) 
(/vmfs/volumes/4a1c
6645-8da19ecc-0f2a-0022192f8d1d/New Virtual Machine/vmware-core.gz, 
/vmfs/volume
s/4a1c6645-8da19ecc-0f2a-0022192f8d1d/New Virtual 
Machine/vmware64-core.gz, /vmf
s/volumes/4a1c6645-8da19ecc-0f2a-0022192f8d1d/New Virtual 
Machine/vmware-vmx-zdu
mp.010).
Sep 22 04:07:37.555: vcpu-0| [msg.log.monpanic.serverdebug] If the 
problem is re
peatable, please set 'Use Debug Monitor' to 'Yes' in the 'Misc' section 
of the C
onfigure Virtual Machine Web page. Then reproduce the incident and file 
it accor
ding to the instructions.
Sep 22 04:07:37.556: vcpu-0| [msg.log.monpanic.vmSupport.vmx86] To 
collect data
to submit to VMware support, run "vm-support".
Sep 22 04:07:37.556: vcpu-0| [msg.log.monpanic.entitlement] We will 
respond on t
he basis of your support entitlement.
Sep 22 04:07:37.556: vcpu-0| [msg.log.monpanic.finish] We appreciate 
your feedba
ck,
Sep 22 04:07:37.556: vcpu-0|   -- the VMware ESX team.
Sep 22 04:07:37.556: vcpu-0| ----------------------------------------
Sep 22 04:07:37.579: vcpu-0| Exiting vcpu-0
Sep 22 04:07:37.659: vmx| VTHREAD watched thread 4 "vcpu-0" died
Sep 22 04:07:38.559: mks| VTHREAD watched thread 0 "vmx" died