From b4be406f5738bbc49073e20650030a59d0008c68 Mon Sep 17 00:00:00 2001 From: Karl Cardenas <29551334+karl-cardenas-coding@users.noreply.github.com> Date: Thu, 26 Sep 2024 09:30:02 -0700 Subject: [PATCH] docs: apply suggestions from code review Co-authored-by: caroldelwing --- .../create-manage-vm/advanced-topics/migrate-vm-kubevirt.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs-content/vm-management/create-manage-vm/advanced-topics/migrate-vm-kubevirt.md b/docs/docs-content/vm-management/create-manage-vm/advanced-topics/migrate-vm-kubevirt.md index 2faf714348..806e9c2529 100644 --- a/docs/docs-content/vm-management/create-manage-vm/advanced-topics/migrate-vm-kubevirt.md +++ b/docs/docs-content/vm-management/create-manage-vm/advanced-topics/migrate-vm-kubevirt.md @@ -22,7 +22,7 @@ from VMware vSphere to Palette VMO. - Only VMs whose operating systems are included under [`virt-v2v` supported guest systems](https://libguestfs.org/virt-v2v-support.1.html) can be migrated. -- The network type , requires a Network +- The network type requires a Network Attachment Definition (NAD) to exist in the migration target namespace in the destination cluster. The NAD name must also match the name assigned to the migration. The migration name is assigned during the wizard, which is started by the Palette CLI's `vmo migrate-vm` command.