From f992e2328a064af2d9894c7e3f178d4faf73c29a Mon Sep 17 00:00:00 2001 From: Rostyslav Yatsyshyn Date: Tue, 14 Jul 2026 15:28:20 +0300 Subject: [PATCH] Document OpenNebula allocation error handling Signed-off-by: Rostyslav Yatsyshyn --- content/software/migration_from_vmware/oneswap.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/software/migration_from_vmware/oneswap.md b/content/software/migration_from_vmware/oneswap.md index 8cda9ade..5f679778 100644 --- a/content/software/migration_from_vmware/oneswap.md +++ b/content/software/migration_from_vmware/oneswap.md @@ -593,6 +593,8 @@ The missing VirtIO ISO warning is informational and does not stop the conversion The prechecks can be skipped with `--skip-prechecks`. +If OpenNebula fails to allocate an Image or VM Template during the import phase, OneSwap reports the full error returned by the OpenNebula API and stops the current conversion. It does not continue with an invalid object ID or wait for an Image that was not created. Converted local disks are preserved according to the existing failed-conversion cleanup behavior. + #### Network mapping For each NIC of the source VM, OneSwap looks for an OpenNebula Virtual Network whose `VCENTER_NETWORK_MATCH` attribute matches the name of the vCenter network the NIC is attached to. If no network matches, the OpenNebula Virtual Network ID passed with `--network` is used as a fallback (a comma-separated list of IDs, one per NIC, can also be passed). The NIC addresses copied from vCenter can be controlled with: