Hallo,
klar können wir Dir das sagen:
Virtual Machine Panics with Bug Number 10095 or 1319
Question
My virtual machine shut down unexpectedly and reported bug number 10095 (bugNr=10095) or 1319 (bugNr=1319). What can I do?
Answer
The following sections describe conditions under which this problem can occur and possible workarounds:
Running the Virtual Machine on a Multiprocessor Host
Running the Virtual Machine on a Windows Host that has a Defective ACPI Timer
Running the Virtual Machine on an IBM x440 Server and Derivative Systems
Backing Up the Host
Running Windows Update on the Host
Running Microsoft Index Server on the Host
If this problem occurs on your host under conditions not described in these sections, please request support from VMware at
www.vmware.com/requestsupport.
Running the Virtual Machine on a Multiprocessor Host
If you are running the virtual machine on a multiprocessor host, verify that the processors have the same CPU speeds. Intel does not support multiprocessor systems when the processors run at different speeds. Thus, VMware cannot support multiprocessor systems unless the CPUs have the same speeds. For more information about Intel multiprocessors, see
support.intel.com/support/processors/dp1.htm
Running the Virtual Machine on a Windows Host that has a Defective ACPI Timer
Some versions of the Windows HAL (hardware abstraction layer) use the ACPI timer on your computer's motherboard to implement certain timekeeping functions. On a few machines, this timer is defective, which can cause bug 10095 or 1319 to occur in VMware products. To learn more about this defect and to download a test program that checks whether your machine has it, go to the VeriTest Web site at
www.etestinglabs.com/bi/cont2000/200012/perfcnt.asp.
If your machine has the defect, you can work around it by replacing your Windows HAL with one that does not use the ACPI feature. If you have a single-processor machine with the defect, VMware recommends you change the HAL to the MPS Uniprocessor PC HAL or the Standard PC HAL. If you have a multiprocessor with the defect, VMware recommends changing to the MPS Multiprocessor PC HAL.
To change the HAL, you should upgrade your host operating system. For information on how to do this for the Windows 2000 host, see Microsoft Knowledge Base article 237556. Go to support.microsoft.com/default.aspx?scid=kb;EN-US;237556.
Running the Virtual Machine on an IBM x440 Server and Derivative Systems with a Windows Host Operating System
IBM x440 servers (and derivative systems from Fujitsu Siemens or NEC, for example) running a Windows host operating system with a HAL provided by Microsoft can cause this bug to occur, as can an IBM HAL with a version earlier than 1.8.
To work around this issue, VMware recommends you install the IBM HAL, version 1.8 or later. You can download the HAL from IBM's Web site. Go to
www.ibm.com and search for HAL in the Support and downloads section.
To determine what HAL you are running, complete the following steps.
On the host, search for a file called HAL.DLL. It is generally found in C:\WINNT\SYSTEM32.
Right click HAL.DLL and select Properties.
Click the Version tab. The version information for your host's HAL appears here.
For example, on a single CPU Windows system, HAL.DLL from Microsoft might display the following information:
File Version: 5.0.2195.xxxx
Product Version: 5.00.2195.xxxx
The IBM v1.8 HAL displays
File Version: 1.8.0.0
Product Version: 1.8
Backing Up the Host
Suspend all virtual machines when you back up your host.
Running Windows Update on the Host
Suspend all virtual machines when you run Windows Update on your host.
Running Microsoft Index Server on the Host
Suspend all virtual machines when you run Microsoft Index Server on your host.
Hartmut Schaumburg
