HP BL680c XenServer Virtual Machine Installation 4.1.0 - Page 41

Appendix C. Troubleshooting VM problems, C.1. VM crashes, C.1.1. Linux VMs, C.1.2. Windows VMs

Page 41 highlights

Appendix C. Troubleshooting VM problems If you experience odd behavior, application crashes, or have other issues, this chapter is meant to help you solve the problem if possible and, failing that, describes where the application logs are located and other information that can help your XenServer Solution Provider and Citrix track and resolve the issue. Troubleshooting of installation issues is covered in the XenServer Installation Guide. Troubleshooting of XenServer Host issues is covered in the XenServer Administrator's Guide. Note We recommend that you follow the troubleshooting information in this chapter solely under the guidance of your XenServer Solution Provider or Citrix Support. Citrix provides two forms of support: you can receive free self-help support via the Support site, or you may purchase our Support Services and directly submit requests by filing an online Support Case. Our free web-based resources include product documentation, a Knowledge Base, and discussion forums. C.1. VM crashes If you are experiencing VM crashes, it's possible that a kernel crash dump might help identify the problem. If the crash is reproducible, follow this procedure to send the dumps to Citrix. C.1.1. Linux VMs For Linux VMs, the crashdump behavior can be controlled through the actions-after-crash parameter. The following are the possible values: Value Description preserve leave the VM in a paused state (for analysis) coredump_and_restart record a core dump, then reboot the VM coredump_and_destroyrecord a core dump, leave VM halted restart no core dump, just reboot VM (this is the default) destroy no coredump, leave VM halted Procedure C.1. To enable saving of Linux VM crash dumps 1. On the XenServer Host, determine the UUID of the desired VM using the command: xe vm-list name-label= params=uuid --minimal 2. Change the actions-after-crash value using the xe vm-param-set; for example: xe vm-param-set uuid= actions-after-crash=coredump_and_restart C.1.2. Windows VMs 36

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44

36
Appendix C. Troubleshooting VM
problems
If you experience odd behavior, application crashes, or have other issues, this chapter is meant
to help you solve the problem if possible and, failing that, describes where the application logs
are located and other information that can help your XenServer Solution Provider and Citrix track
and resolve the issue.
Troubleshooting of installation issues is covered in the
XenServer Installation Guide
. Trou-
bleshooting of XenServer Host issues is covered in the
XenServer Administrator's Guide
.
Note
We recommend that you follow the troubleshooting information in this chapter solely
under the guidance of your XenServer Solution Provider or Citrix Support.
Citrix provides two forms of support: you can receive free self-help support via the
Support site
, or
you may
purchase our Support Services
and directly submit requests by filing an online Support
Case. Our free web-based resources include product documentation, a Knowledge Base, and
discussion forums.
C.1. VM crashes
If you are experiencing VM crashes, it's possible that a kernel crash dump might help identify the
problem. If the crash is reproducible, follow this procedure to send the dumps to Citrix.
C.1.1. Linux VMs
For Linux VMs, the crashdump behavior can be controlled through the
actions-after-crash
parameter. The following are the possible values:
Value
Description
preserve
leave the VM in a paused state (for analysis)
coredump_and_restart
record a core dump, then reboot the VM
coredump_and_destroy
record a core dump, leave VM halted
restart
no core dump, just reboot VM (this is the default)
destroy
no coredump, leave VM halted
Procedure C.1. To enable saving of Linux VM crash dumps
1.
On the XenServer Host, determine the UUID of the desired VM using the command:
xe vm-list name-label=
<name>
params=uuid --minimal
2.
Change the
actions-after-crash
value using the
xe vm-param-set
; for example:
xe vm-param-set uuid=<vm_uuid> actions-after-crash=coredump_and_restart
C.1.2. Windows VMs