Hello,
i've setup VMware Server 1.0.3 on a new Fedora Core 7
machine (AMD X86_64) and try to install Centos 5.0 as one guest system.
I power on the machine, the centos install routine begin and then suddenly the following massage appears:
<!- logfile->
Jul 07 09:00:16: vcpu-0| MONITOR PANIC: vcpu-0:DoubleFault @ 0x4020:0x55cb4 (0x73108000,0x2848)
Jul 07 09:00:16: vcpu-0| Core dump with build build-44356
Jul 07 09:00:16: vcpu-0| Writing monitor corefile "/vms/Centos5/vmware-core.gz"
Jul 07 09:00:16: vcpu-0| CoreDump: dumping core with superuser privileges
Jul 07 09:00:16: vcpu-0| Beginning monitor coredump
Jul 07 09:00:16: vcpu-0| End monitor coredump
Jul 07 09:00:16: vcpu-0| Writing anonymous pages at pos: 401000
Jul 07 09:00:17: vcpu-0| Monitor Panic. Last Disk I/O was to the MBR
Jul 07 09:00:17: vcpu-0| Msg_Post: Error
Jul 07 09:00:17: vcpu-0| \[msg.log.monpanic] *** VMware Server internal monitor error ***
Jul 07 09:00:17: vcpu-0| vcpu-0:DoubleFault @ 0x4020:0x55cb4 (0x73108000,0x2848)
<!-- logfile -->
<!-- screen message -->
\*** VMware Server internal monitor error ***
vcpu-0:DoubleFault @ 0x4020:0x55cb4 (0x73108000,0x2848)
Please report this problem 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=%2Fvms%2FCentos5%2Fvmware%2Elog&coreLocation=%2Fvms%2FCentos5%2Fvmware%2Dcore%2Egz". Please provide us with the log file (/vms/Centos5/vmware.log) and the core file (/vms/Centos5/vmware-core.gz).
If the problem is repeatable, please set 'Logging level' to 'Debug' in the Misc panel of Virtual Machine Settings. Then reproduce the incident and file it according to the instructions.
To collect files to submit to VMware support, run vm-support.
We will respond on the basis of your support entitlement.
We appreciate your feedback,
-- the VMware Server team.
<!--- screen massage --->
Now the only way to reset the host is an hardware reset.
The same thing happens on an guest setup with fedora core 7.
An preinstall Windows XP guest - build on another VMWare Server instance - starts without any problems...
Has anyone the same problems?