Errors during VM2000 startup
 | On SU x86, the startup of the monitor system is continued even if an error occurs when initializing VM2000 operation. |
| Form | Message: VMS50xx...,STARTUP TERMINATED |
| Cause | Detected error in VM2000 startup as described in message VMS50xx |
| Diagnostic materials | CONSLOG file; SLED of the system as a whole |
| Response | Correct error and reload VM2000 |
Errors in the VM2000 hypervisor (SU /390)
| On SU x86, the Xen hypervisor controls all virtual machines, see "Errors in the carrier system (SU x86)". |
Abnormal VM2000 hypervisor termination also terminates the operation of all the guest systems and of VM2000. If an automatic restart in the monitor system is not set, VM2000 and the monitor system must be reloaded manually. If an automatic restart in the monitor system is set, VM2000 and the monitor system are reloaded automatically (see "Automatic restart following VM2000 hypervisor termination (SU /390)"). After the monitor system has started up, the VMs must be set up again and the guest systems restarted.
| Form | Message: VMS00xxExceptions: messages VMS0017, VMS0018, VMS0021, VMS0023 through VMS0027 and VMS0000 |
| Cause | The VM2000 hypervisor recognizes a system error (described in message VMS00xx) and terminates VM2000. |
| Diagnostic materials | CONSLOG file; SLED of the system as a whole |
| Response | Reload VM2000 / automatic restart |
Exception: abnormal system termination in the monitor system
| Form | Message: VMS0018 |
| Cause | Abnormal system termination in the monitor system. A restart option is not set or the restart function has failed. At least one guest system is still active. |
| Diagnostic materials | CONSLOG file |
| Response | Shutdown for all guest systems or attempt to restart the monitor system via SVP |
Exception: error in a CPU
| Form | Message: VMS0017 and VMS0021 |
| Cause | The real CPU was detached implicitly due to a hardware or software error. |
| Diagnostic materials | CONSLOG file; automatic VMDUMP (see "VMDUMP utility routine") |
| Response | Respond to message VMS0021. Contact customer support. Check CPU and attach again, if applicable, if no hot spare CPU is available. |
| Form | Message: VMS0023 and VMS0024 |
| Cause | A hot spare CPU was attached following CPU failure. |
| Diagnostic materials | None |
| Response | Respond to message VMS0024. Contact customer support. Repair defective CPU. |
Exception: CPU pool reconfiguration after a CPU error
| Form | Message: VMS0025, VMS0026 or VMS0027 |
| Cause | Owing to a CPU error a CPU, a VM or a VM group had to be assigned to another CPU pool. |
| Diagnostic materials | None |
Response | Check CPU pools and reorganize if applicable. |
Exception: other errors
If any other errors that have not yet been described occur in the VM2000 hypervisor, an automatic VMDUMP is created and output. It should be forwarded to customer support for diagnosis.
A special message is not issued.
Errors in the VM2000 monitor or in $VMCONS
| Form | case a) | System dump of a system task | |
case b) | Message issued on the BS2000 console of the monitor system or in the ADMIN dialog of the monitor VM
where: | ||
| (&00): | Name of the VM2000 module in which the error was detected | ||
| ###(&01): | Flag in VM2000 module (&00) | ||
| (&02): | More detailed error information | ||
| Cause | case a) | Program error in a system task | |
| case b) | Internal inconsistency detected or serious VM2000 error | ||
| Diagnostic materials | case a) | CONSLOG file of the monitor system; system dump | |
| case b) | CONSLOG file of the monitor system; automatic VMDUMP, if created (see "VMDUMP utility routine") | ||
| Response | Continue with VM2000 operation. The affected system task is continued from a restart point (see "Restarting a task after an error in a system task of VM2000"). It may be necessary to terminate the affected VM by means of /DELETE-VM and to establish $VMCONS connections again. | ||