From 19e67a2c7e27099f5ac8778bf80cfbc1e9ae438b Mon Sep 17 00:00:00 2001 From: Philipp Schuster Date: Mon, 29 Jun 2026 14:14:17 +0200 Subject: [PATCH] vmm: streamline migration related API error variants Receiving a migration happens inside the VMM thread, which blocks the API until a migration was received. On the other hand, sending a migration is actually just a dispatch operation. We adjust the wording to improve clarity of the error messages. On-behalf-of: SAP philipp.schuster@sap.com Signed-off-by: Philipp Schuster --- vmm/src/api/mod.rs | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/vmm/src/api/mod.rs b/vmm/src/api/mod.rs index df5157a00..f0a0367ed 100644 --- a/vmm/src/api/mod.rs +++ b/vmm/src/api/mod.rs @@ -199,12 +199,13 @@ pub enum ApiError { #[error("The vsock device could not be added to the VM")] VmAddVsock(#[source] VmError), - /// Error starting migration receiver - #[error("Error starting migration receiver")] + /// Error while receiving a migration, either because the receiver could not + /// be started or because the migration failed mid-operation. + #[error("Error receiving migration")] VmReceiveMigration(#[source] MigratableError), - /// Error starting migration sender - #[error("Error starting migration sender")] + /// Error while dispatching the migration worker (thread). + #[error("Error dispatching the migration worker")] VmSendMigration(#[source] MigratableError), /// Error triggering power button