After a lot of testing (restore from backups, clean install, e.t.c) i found that the cause of all crashes and problems is a conflict between Intel Parallel Studio XE 2013 and Vmware Workstation 9, it may affect also other versions. As soon i realized the problem i searched for other reports of the problem and found http://software.intel.com/en-us/forums/topic/328380. If Vmware Workstation 9 is installed alongside with Intel's Parallel Studio XE 2013 all the problems that are analyzed bellow will happen. I speculate that there is conflict between some hw-monitor driver and Vmware Workstation that leads to crashes.
Unfortunately just uninstalling Intel Parallel Studio XE 2013 will not fix the problem.
The most common error codes are:
vcpu-0| W110: MONITOR PANIC: vcpu-0:VMM fault 6: src=MONITOR rip=0xfffffffffc2c14a0 regs=0xfffffffffc008a60
vcpu-0| W110: MONITOR PANIC: vcpu-0:VMM fault 14: src=MONITOR rip=0xfffffffffc2c147e regs=0xfffffffffc008a40
vcpu-0| W110: MONITOR PANIC: vcpu-0:ASSERT vmcore/vmm/main/crosscall.c:690s
Also process inside linux VM's crash with SIGSEGV.
Original Post:
Guest crashes with error vcpu-0:VMM fault 14: src=MONITOR or vcpu-0:VMM fault 6: src=MONITOR
I am using Vmware Workstation 9 on a Dell XPS L502x laptop with Windows 7 Professional x64. The laptop specs are:
Intel Core i7-2670QM
16Gb RAM
Intel HD 3000
Nvidia GT 540m
Crucial M4 512GB SSD
Seagate Momentus 750GB
When try to boot a virtual machine configured with more than two 2 CPUS's, most of the times it crashes immediately with the one of the following error messages.
vcpu-0| W110: MONITOR PANIC: vcpu-0:VMM fault 6: src=MONITOR rip=0xfffffffffc2c14a0 regs=0xfffffffffc008a60
vcpu-0| W110: MONITOR PANIC: vcpu-0:VMM fault 14: src=MONITOR rip=0xfffffffffc2c147e regs=0xfffffffffc008a40
vcpu-0| W110: MONITOR PANIC: vcpu-0:ASSERT vmcore/vmm/main/crosscall.c:690s
In another virtual machine that is configured with 2-CPUS and running Centos 6.3 64-bit. Processes randomly receiver SIGSEGV and crash for ex.
bzi2 crash
bzip2: Caught a SIGSEGV or SIGBUS whilst compressing.
Possible causes are (most likely first):
(1) This computer has unreliable memory or cache hardware
(a surprisingly common problem; try a different machine.)
(2) A bug in the compiler used to create this executable
(unlikely, if you didn't compile bzip2 yourself.)
(3) A real bug in bzip2 -- I hope this should never be the case.
The user's manual, Section 4.3, has more info on (1) and (2).
If you suspect this is a bug in bzip2, or are unsure about (1)
or (2), feel free to report it to me at: jseward@bzip.org.
Section 4.3 of the user's manual describes the info a useful
bug report should have. If the manual is available on your
system, please try and read it before mailing me. If you don't
have the manual or can't be bothered to read it, mail me anyway.
In /var/log/messages, I see the following:
tpvmlpd2[3873]: readlink("/dev/vmwcomgw") failed with 2
I suspected that there is is a problem with the laptop's memory so i run memtest86 and laptops memory test and found no errors.
I tested also Vmware player and it has the same behaviour.
Any help appreciated!