How To Get A Memory Dump From A PVS Target Device

How To Get A Memory Dump From A PVS Target Device

book

Article ID: CTX322727

calendar_today

Updated On:

Description

When Troubleshooting Provisioning Services Target problems gathering a memory dump may be required.  In some cases a Kernel dump is sufficient to identify the problem.  In other cases a full system dump may be unavoidable and necessary.  Once your vDisk registry has been updated you can now wait for the crash to happen or trigger the dump using, for example, Sysinternals NotMyFault .  See additional resources section for more trigger methods.

Instructions

Enable Kernel Memory Dump

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl
CrashDumpEnabled = 7

Enable Full Memory Dump

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl
CrashDumpEnabled = 1
DumpFileSize = 0




 

Environment

Caution! Using Registry Editor incorrectly can cause serious problems that might require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Be sure to back up the registry before you edit it.

Additional Information

Additional Considerations:

1. The cache disk must be large enough to accommodate the kernel or full memory dump which is approx 1/3 the size of RAM or 2X RAM respectively.  Keep in mind that Windows Event logs and pagefile may already be consuming some of this disk space.  This may require expanding the cache drive or replacing it altogether with a larger disk at the admin's discretion.

2. See the "Tips To Generate Memory Dumps" section for NotMyFault, keyboard and NMI among other triggers.  Here is how to trigger the dump when running Citrix Hypervisor .

3.  VMware Hypervisor users can use the method outlined here or by suspending a virtual machine as defined in CTX125086

 

Powered by Wolken Software