Skip to content

Commit

Permalink
Doc: Changes to the import of a Windows VM (#14074)
Browse files Browse the repository at this point in the history
I slightly reworded the section related to the import of a Windows VM
from a foreign hypervisor to better clarify that the steps described are
optional
  • Loading branch information
tomponline authored Sep 13, 2024
2 parents bf6cd59 + e01a74f commit e6a6119
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions doc/howto/import_machines_to_instances.md
Original file line number Diff line number Diff line change
Expand Up @@ -47,8 +47,8 @@ The tool can also inject the required VIRTIO drivers into the image:
* Download [`rhsrvany.exe` and `pnp_wait.exe`](https://github.com/rwmjones/rhsrvany?tab=readme-ov-file#binary-releases), and place them in the `/usr/share/virt-tools/` directory.

````{tip}
If you want to convert a Windows VM from a foreign hypervisor manually,
you must install both the required Windows drivers (as described above) and `virt-v2v` (>= 2.3.4).
The `lxd-migrate` command with the `--conversion=format,virtio` option automatically converts the image and injects the VIRTIO drivers during the conversion.
However, if you want to manually convert a Windows VM from a foreign hypervisor, you must install both the required Windows drivers (as described above) and `virt-v2v` (>= 2.3.4).
<details>
<summary>Expand to see how to convert your Windows VM using <code>virt-v2v</code></summary>
Expand Down

0 comments on commit e6a6119

Please sign in to comment.