Available article translations:

How to collect a memory dump for the Support and Development teams

  • Parallels Desktop for Mac Home Edition
  • Parallels Desktop for Mac Pro Edition


When troubleshooting issues where the whole virtual machine or a specific application inside it crash / hang, or when the virtual machine experiencing slow performance issue, you may need to collect a memory dump of a virtual machine at the moment the issue is reproduced. Such information may be very helpful for the Second Line Support and Development teams to investigate the issue.

Colleting a memory dump

For collecting a memory dump you don't need to touch a virtual machine at all. Just open Terminal on OS X and follow these instructions:

  1. Reproduce the issue (black screen issue or slow performance, as an example) and leave virtual machine in this state.
  2. Open Finder > Applications > Utilities > Terminal and type:

    prlctl list -a

    This will give you the list of all virtual machines. Please copy the virtual machine UUID (most likely this VM will be in running state) and in the Terminal window run the following command:

    prlctl internal UUID dbgdump --path ~/Desktop/

    where UUID is the unique ID of the virtual machine in question.

    example output:

    prlctl list -a
    {e91ee29c-a30e-40c0-a00b-211b475b5e0b}  running      -               Windows 7
    prlctl internal {e91ee29c-a30e-40c0a00b-211b475b5e0b} dbgdump --path ~/Desktop/
    Executing command 'dbgdump' ...


  3. Once the memory dump is generated, memory.dmp file will appear on the Desktop.

NOTE: Memory dump is a big file (same amount as VM's RAM) - please compress it before uploading (right-click on the file - Compress). Please upload (compressed archive with memory dump file) to the local share using the instructions in either of these KB articles:

KB 9082 Upload files with FileZilla

KB 9101 How to upload large files to a Parallels file share

NOTE: Before closing the virtual machine window generate a technical data report and send us the report ID number: KB 9058

1e5db16426987d561060acdf56d947b4 a9c6e0b6a5209e617a7c0dd5eace86cf f9b6a8d63f3437e0dca35c9704a9033c

Was this article helpful?
Tell us how we may improve it.
Yes No