Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

doc/howto: Clarify support for QCOW2 and VMDK images #1274

Closed
wants to merge 1 commit into from
Closed

doc/howto: Clarify support for QCOW2 and VMDK images #1274

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion doc/howto/import_machines_to_instances.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,16 @@ You can run the tool on any Linux machine.
It connects to an Incus server and creates a blank instance, which you can configure during or after the migration.
The tool then copies the data from the disk or image that you provide to the instance.

`incus-migrate` can import images in `raw`, `qcow2`, and `vmdk` file formats.
`incus-migrate` from Incus 6.0 LTS and up to Incus 6.4 can only import images in the `raw` file format.
If you have images in the `qcow2` or `vmdk` file formats, you need to convert them first to the `raw` file format using the external tool `qemu-img`.
In this example the QCOW2 image is converted to the `raw` file format.
```
qemu-img convert -f vmdk -O raw image.vmdk image.img
```

```{note}
Since Incus 6.5, the `incus-migrate` tool is able to directly use images in both the `qcow2` and `vmdk` file format.
```

```{note}
If you want to configure your new instance during the migration process, set up the entities that you want your instance to use before starting the migration process.
Expand Down
Loading