FreeBSD SMP kernels cause problems on VMWare
Submitted by Bram Schoenmakers on 18 July, 2008 - 16:08.
This entry is quite simple: don't use SMP FreeBSD kernels on a VMWare virtual machine. This gives many problems, illustrated with this snippet from dmesg:
pid 5856 (sh), uid 1001: exited on signal 11
pid 5894 (sed), uid 0: exited on signal 11 (core dumped)
pid 6919 (uname), uid 0: exited on signal 11 (core dumped)
pid 7854 (sh), uid 0: exited on signal 11 (core dumped)
pid 7948 (uname), uid 1001: exited on signal 11
pid 7953 (pkg_info), uid 0: exited on signal 11 (core dumped)
pid 10432 (pkg_version), uid 0: exited on signal 11 (core dumped)
pid 10893 (uname), uid 0: exited on signal 11 (core dumped)
pid 11223 (pkg_info), uid 0: exited on signal 11 (core dumped)
pid 12771 (sh), uid 0: exited on signal 11 (core dumped)
pid 12787 (grep), uid 0: exited on signal 11 (core dumped)
pid 13334 (sed), uid 0: exited on signal 11 (core dumped)
pid 13709 (sh), uid 0: exited on signal 11 (core dumped)
pid 14278 (true), uid 0: exited on signal 11 (core dumped)
pid 14309 (sh), uid 0: exited on signal 11 (core dumped)
pid 14543 (true), uid 0: exited on signal 11 (core dumped)
pid 14592 (sh), uid 0: exited on signal 11 (core dumped)
pid 14668 (sh), uid 0: exited on signal 11 (core dumped)
pid 14926 (sh), uid 0: exited on signal 11 (core dumped)
pid 16524 (sh), uid 0: exited on signal 11 (core dumped)
pid 17441 (pkg_info), uid 0: exited on signal 11 (core dumped)
pid 18025 (sh), uid 0: exited on signal 11 (core dumped)
pid 20264 (sh), uid 0: exited on signal 11 (core dumped)
pid 20475 (id), uid 0: exited on signal 11 (core dumped)
pid 20623 (sort), uid 0: exited on signal 11 (core dumped)
pid 5894 (sed), uid 0: exited on signal 11 (core dumped)
pid 6919 (uname), uid 0: exited on signal 11 (core dumped)
pid 7854 (sh), uid 0: exited on signal 11 (core dumped)
pid 7948 (uname), uid 1001: exited on signal 11
pid 7953 (pkg_info), uid 0: exited on signal 11 (core dumped)
pid 10432 (pkg_version), uid 0: exited on signal 11 (core dumped)
pid 10893 (uname), uid 0: exited on signal 11 (core dumped)
pid 11223 (pkg_info), uid 0: exited on signal 11 (core dumped)
pid 12771 (sh), uid 0: exited on signal 11 (core dumped)
pid 12787 (grep), uid 0: exited on signal 11 (core dumped)
pid 13334 (sed), uid 0: exited on signal 11 (core dumped)
pid 13709 (sh), uid 0: exited on signal 11 (core dumped)
pid 14278 (true), uid 0: exited on signal 11 (core dumped)
pid 14309 (sh), uid 0: exited on signal 11 (core dumped)
pid 14543 (true), uid 0: exited on signal 11 (core dumped)
pid 14592 (sh), uid 0: exited on signal 11 (core dumped)
pid 14668 (sh), uid 0: exited on signal 11 (core dumped)
pid 14926 (sh), uid 0: exited on signal 11 (core dumped)
pid 16524 (sh), uid 0: exited on signal 11 (core dumped)
pid 17441 (pkg_info), uid 0: exited on signal 11 (core dumped)
pid 18025 (sh), uid 0: exited on signal 11 (core dumped)
pid 20264 (sh), uid 0: exited on signal 11 (core dumped)
pid 20475 (id), uid 0: exited on signal 11 (core dumped)
pid 20623 (sort), uid 0: exited on signal 11 (core dumped)
Because of this, many complex commands like portmaster and compile jobs fail because of all these crashing processes. Switching back to a GENERIC kernel solved these problems.