From 74d7824660633ae57725b9887bfe5df01984c027 Mon Sep 17 00:00:00 2001 From: Karl Cardenas Date: Tue, 24 Sep 2024 16:28:13 -0700 Subject: [PATCH] docs: feedback from Tyler --- .../create-manage-vm/advanced-topics/migrate-vm-kubevirt.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) 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 bb15271954..2faf714348 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,8 +22,10 @@ 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. -- When using , the Network Attachment - Definition (NAD) used must match the same name assigned to the migration. Otherwise, the migration will fail. +- 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. ## Prerequisites