External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2025-02-22 03:12:22 +00:00
Code Issues Packages Projects Releases Wiki Activity

Document behavior of setvcpus during guest boot

Browse Source 
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1088748

The hotplugged vcpus could fail to show up in the guest if
they were added during boot, see:
https://bugzilla.redhat.com/show_bug.cgi?id=807508

Also change arbitrary to arbitrarily.
This commit is contained in:
Ján Tomko 2014-04-23 13:01:24 +02:00
parent b396e602c9
commit 22a92eb0a7
2 changed files with 11 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
src/libvirt.c
View File

@ -9368,9 +9368,12 @@ virDomainSendProcessSignal(virDomainPtr domain,
*
* Dynamically change the number of virtual CPUs used by the domain.
* Note that this call may fail if the underlying virtualization hypervisor
* does not support it or if growing the number is arbitrary limited.
* does not support it or if growing the number is arbitrarily limited.
* This function may require privileged access to the hypervisor.
*
* Note that if this call is executed before the guest has finished booting,
* the guest may fail to process the change.
*
* This command only changes the runtime configuration of the domain,
* so can only be called on an active domain. It is hypervisor-dependent
* whether it also affects persistent configuration; for more control,
@ -9417,7 +9420,7 @@ virDomainSetVcpus(virDomainPtr domain, unsigned int nvcpus)
*
* Dynamically change the number of virtual CPUs used by the domain.
* Note that this call may fail if the underlying virtualization hypervisor
* does not support it or if growing the number is arbitrary limited.
* does not support it or if growing the number is arbitrarily limited.
* This function may require privileged access to the hypervisor.
*
* @flags may include VIR_DOMAIN_AFFECT_LIVE to affect a running
@ -9429,6 +9432,9 @@ virDomainSetVcpus(virDomainPtr domain, unsigned int nvcpus)
* is hypervisor-dependent on whether just live or both live and persistent
* state is changed.
*
* Note that if this call is executed before the guest has finished booting,
* the guest may fail to process the change.
*
* If @flags includes VIR_DOMAIN_VCPU_MAXIMUM, then
* VIR_DOMAIN_AFFECT_LIVE must be clear, and only the maximum virtual
* CPU limit is altered; generally, this value must be less than or

4
tools/virsh.pod
View File

@ -1743,7 +1743,9 @@ domain is next started.
If I<--live> is specified, the guest domain must be active, and the change
takes place immediately. Both the I<--config> and I<--live> flags may be
specified together if supported by the hypervisor.
specified together if supported by the hypervisor. If this command is run
before the guest has finished booting, the guest may fail to process
the change.
If I<--current> is specified, affect the current guest state.