virsh: allow async vcpu options to reach drivers

Do not reject setvcpu --enable --async or setvcpus --guest --async in virsh.

For setvcpu, async only affects live unplug and is documented as having no
effect when enabling vCPUs. For setvcpus, guest+async is a driver-visible flag
combination; drivers should decide whether they can support it. Keep virsh
validation limited to API-level constraints and let drivers report unsupported
combinations.

Signed-off-by: Akash Kulhalli <akash.kulhalli@oracle.com>
Reviewed-by: Peter Krempa <pkrempa@redhat.com>
This commit is contained in:
Akash Kulhalli authored and Peter Krempa committed 2026-06-10 11:12:27 +02:00
1 parent 09d6f9fa5d
commit 1ab6d18bee
1 file changed
-2
-2
View File
@@ -7773,7 +7773,6 @@ cmdSetvcpus(vshControl *ctl, const vshCmd *cmd)
VSH_EXCLUSIVE_OPTIONS_VAR(current, live);
VSH_EXCLUSIVE_OPTIONS_VAR(current, config);
VSH_EXCLUSIVE_OPTIONS_VAR(guest, config);
VSH_EXCLUSIVE_OPTIONS_VAR(async, guest);
VSH_REQUIRE_OPTION_VAR(maximum, config);
@@ -7946,7 +7945,6 @@ cmdSetvcpu(vshControl *ctl, const vshCmd *cmd)
VSH_EXCLUSIVE_OPTIONS("current", "live");
VSH_EXCLUSIVE_OPTIONS("current", "config");
VSH_EXCLUSIVE_OPTIONS("async", "enable");
if (config)
flags |= VIR_DOMAIN_SETVCPU_AFFECT_CONFIG;