diff --git a/doc/howto/import_machines_to_instances.md b/doc/howto/import_machines_to_instances.md index aace09d154..6ffacbdacd 100644 --- a/doc/howto/import_machines_to_instances.md +++ b/doc/howto/import_machines_to_instances.md @@ -1,16 +1,16 @@ (import-machines-to-instances)= # How to import physical or virtual machines to Incus instances -Incus provides a tool (`incus-migrate`) to create an Incus instance based on an existing disk or image. +Incus provides a tool (`incus-migrate`) to create an Incus instance or volume based on an existing disk or image. 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. +It connects to a local or remote Incus server and creates a blank instance or volume, which you can configure during or after the migration. +The tool then copies the data from the disk or image that you provide. -`incus-migrate` can import images in `raw`, `qcow2`, and `vmdk` file formats. +`incus-migrate` can import images in `raw`, `qcow2`, `ova` and `vmdk` file formats. It can also directly download an image from a provided URL. ```{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. +If you want to configure a new instance during the migration process, set up the entities that you want your instance to use before starting the migration process. By default, the new instance will use the entities specified in the `default` profile. You can specify a different profile (or a profile list) to customize the configuration. @@ -20,7 +20,7 @@ You can also override {ref}`instance-options`, the {ref}`storage pool