> 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/virtual-machine-configuration-tasks/startup-and-shutdown-parameters.md).

# Startup & Shutdown Parameters

**--autostart** <**off** | **open-window** | **start-app** | **start-host** | **user-login**>

Sets the virtual machine autostart options:

**off**: The virtual machine is started manually.

**open-window**: The virtual machine starts when its window opens.

**start-app**: The virtual machine starts when Parallels Desktop starts.

**start-host**: The virtual machine is started automatically on the host boot.

**user-login**: The virtual machine is started automatically on user logon.

**--autostart-delay** <*n*>

Sets the delay of the virtual machine autostart on host boot to n seconds.

**--autostop** \<stop | suspend | shutdown>

Specifies what should happen to the virtual machine on host shutdown.

**--startup-view** <**same** | **window** | **coherence** | **fullscreen** | **modality** | **headless**>

Sets the virtual machine startup view options:

**same**: Same as the last time

**window**: Normal window

**coherence**: Coherence

**fullscreen**: Full screen

**modality**: Modality

**headless**: Headless

**--on-shutdown** <**window** | **close** | **quit**>

Sets the virtual machine shutdown options:

**window**: The virtual machine window stays open after the virtual machine is shut down.

**close**: The virtual machine window closes after the virtual machine is shut down.

**quit**: Parallels Desktop quits after the virtual machine is shut down.

**--on-window-close** <**suspend** | **shutdown** | **stop** | **ask** | **keep-running**>

Sets the virtual machine window close options:

**suspend**: The virtual machine is suspended after its window is closed.

**shutdown**: The virtual machine is shut down after its window is closed.

**stop**: The virtual machine is forcibly stopped after its window is closed.

**ask**: Ask the user what to do: suspend, shut down, or stop the virtual machine.

**keep-running**: The virtual machine is kept running after its window is closed.

**--pause-idle** <**on** | **off**>

Enables or disables pausing of an idle virtual machine.

**--undo-disks** <**off** | **discard** | **ask**>

Sets the virtual machine undo disks options:

**off**: Undo disks mech is off.

**discard**: Discard all changes made in the virtual machine after it is stopped.

**ask**: Ask the user what to do: apply changes or discard them after the virtual machine is stopped.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.parallels.com/landing/parallels-desktop-developers-guide/command-line-interface-utility/manage-virtual-machines-from-cli/virtual-machine-configuration-tasks/startup-and-shutdown-parameters.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.