> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/parallels-desktop-developers-guide/command-line-interface-utility/manage-virtual-machines-from-cli/miscellaneous/generating-a-problem-report.md).

# Generating a Problem Report

**prlctl problem-report** <*vm\_id* | *vm\_name*>

<**-d**, **--dump** | **-s**, **--send** \[**--proxy** \[*user* \[**:***password*] *@proxyhost* \[*:port*]]] \[**--no-proxy**]>

Generates a problem report. If the **-s**, **--send** option is specified, the report is sent to Parallels. Otherwise, it is dumped to stdout.

#### Parameters

**-d**, **--dump**

If included, the report is displayed on the screen. You can pipe the output to a file and then send it to the Parallels technical support.

**-s**, **--send**

If this option is included (instead of **-d**, **--dump**), the report is sent to Parallels. You can specify additional optional parameters, which are described below.

**--proxy** *user*:*password*@proxyhost:port

If you use a proxy server to connect to the Internet, include the **--proxy** parameter and specify the proxy server information. The problem report will be sent to Parallels through this proxy server.

**--no-proxy**

Do not use a proxy server to send the problem report. This is the default behavior, so you can include or omit this parameter.

#### Optional Parameters

**--name** <*user\_name*>

Inserts the specified user name into the report.

**--email** <*user\_e-mail*>

Inserts the specified e-mail address into the report.

**--description** <*problem\_description*>

Inserts the specified free-form description into the report.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.parallels.com/landing/parallels-desktop-developers-guide/command-line-interface-utility/manage-virtual-machines-from-cli/miscellaneous/generating-a-problem-report.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.