I recently upgraded from 1.0.1 to 1.0.3. Now if vmware-server crashes hard whenever I try to run mythtv on my system. The real problem is that my host system needs reset when this happens. It won't even shutdown normally. It is reproducible every time.
I don't even have to be running a VM for the core dump to happen. While starting, I press F2 and am inside the BIOS. I get out of this window and start mythtv, as soon as mythtv window appears boom! core dump.
What could possibly cause this behavior? One thing is certain that the guest kernel is not involved. And it happens only with respect to interaction with the mythtv (and hence the kernel driver pvrusb2, which drives the WinTV PVR USB2 device).
The kernel is gentoo-sources-2.6.21-r2 on x86_64.
The log file shows this:
May 26 21:20:23: vcpu-0| VMSAMPLE32: cs=0x1b2a, eip=0x43a
May 26 21:20:24: vcpu-0| VMSAMPLE32: cs=0x1b2a, eip=0x43a
May 26 21:20:25: vcpu-0| VMSAMPLE32: cs=0x1b2a, eip=0x43a
May 26 21:20:26: vcpu-0| VMSAMPLE32: cs=0x1b2a, eip=0x43a
May 26 21:20:27: vcpu-0| VMSAMPLE32: cs=0x1b2a, eip=0x43a
May 26 21:20:28: vcpu-0| VMSAMPLE32: cs=0x173c, eip=0xe1e
May 26 21:20:28: vcpu-0| maxStackDepth(0) = 3212
May 26 21:20:29: vcpu-0| VMSAMPLE32: cs=0xf000, eip=0x44c3
May 26 21:20:30: vcpu-0| VMSAMPLE32: cs=0x1b2a, eip=0x43a
May 26 21:20:31: vcpu-0| VMSAMPLE32: cs=0xf000, eip=0x44bb
May 26 21:20:31: vcpu-0| MONITOR PANIC: vcpu-0:DoubleFault @ 0x4020:0x8a3b4 (0x8e3c,0x1cc28e3c)
May 26 21:20:31: vcpu-0| Core dump with build build-44356
May 26 21:20:31: vcpu-0| Writing monitor corefile "/mnt/raid-vol/vmware/linux-vm64/vmware-core.gz"
May 26 21:20:31: vcpu-0| CoreDump: dumping core with superuser privileges
May 26 21:20:31: vcpu-0| Beginning monitor coredump
May 26 21:20:32: vcpu-0| End monitor coredump
May 26 21:20:32: vcpu-0| Writing anonymous pages at pos: 401000
May 26 21:20:32: vcpu-0| Msg_Post: Error
May 26 21:20:32: vcpu-0| \[msg.log.monpanic.beta] *** VMware Server internal monitor error ***
May 26 21:20:32: vcpu-0| vcpu-0:DoubleFault @ 0x4020:0x8a3b4 (0x8e3c,0x1cc28e3c)
May 26 21:20:32: vcpu-0| There is a problem in this version of VMware Server.
May 26 21:20:32: vcpu-0| We rely on your feedback to improve the quality of our product.
Please submit a support request that describes the problem at our Web page
"http://www.vmware.com/info?id=8". Do not forget to attach the log file (/mnt/raid-vol/vmware/linux-vm64/vmware.log) and the core file
(/mnt/raid-vol/vmware/linux-vm64/vmware-core.gz).
May 26 21:20:32: vcpu-0| To collect files to submit to VMware support, run vm-support-lx.
May 26 21:20:32: vcpu-0| We appreciate your feedback,
May 26 21:20:32: vcpu-0| -- the VMware Server team.
May 26 21:20:32: vcpu-0| \----
May 26 21:20:32: vcpu-0| POST(no connection): *** VMware Server internal monitor error ***
May 26 21:20:32: vcpu-0| vcpu-0:DoubleFault @ 0x4020:0x8a3b4 (0x8e3c,0x1cc28e3c)
May 26 21:20:32: vcpu-0| There is a problem in this version of VMware Server.
May 26 21:20:32: vcpu-0| We rely on your feedback to improve the quality of our product.
Please submit a support request that describes the problem at our Web page
"http://www.vmware.com/info?id=8". Do not forget to attach the log file
(/mnt/raid-vol/vmware/linux-vm64/vmware.log) and the core file
(/mnt/raid-vol/vmware/linux-vm64/vmware-core.gz).
May 26 21:20:32: vcpu-0| To collect files to submit to VMware support, run vm-support-lx.
May 26 21:20:32: vcpu-0| We appreciate your feedback,
May 26 21:20:32: vcpu-0| -- the VMware Server team.
May 26 21:20:32: vcpu-0|
May 26 21:20:32: vcpu-0| Exiting vcpu-0
