similar to: Possible VCPU hotplug bug

--- mlutils/unix_utils-c.c | 15 +++++++++++++++ mlutils/unix_utils.ml | 5 +++++ mlutils/unix_utils.mli | 9 +++++++++ 3 files changed, 29 insertions(+) diff --git a/mlutils/unix_utils-c.c b/mlutils/unix_utils-c.c index 3309961..8acf039 100644 --- a/mlutils/unix_utils-c.c +++ b/mlutils/unix_utils-c.c @@ -77,6 +77,7 @@ extern value guestfs_int_mllib_mkdtemp (value val_pattern); extern value

My dom0 is uing Centos 5.2 x64. I have just upgraded Xen from 3.3.0 to 3.3.1. After upgraded, I find that I cannot hotplug additional vcpu anymore. I have a domU "linux1" which is a paravirtualized vm with centos 5.2. I try to "xm vcpu-set linux1 4", it does not have any error message, but those vcpu cannot be displayed. I also tried to add vcpu using "virsh setvcpus

When hotplug hvm vcpu by ''xm vcpu-set'' command, if it add/remove many vcpus by 1 ''xm vcpu-set'' command, it has a bug that it cannot add/remove all vcpus that want to be added/removed. This patch is to fix the bug. It delays trigger sci until all xenstore cpu node status are watched. Signed-off-by: Liu, Jinsong <jinsong.liu@intel.com>

hi, i386 vcpu hotplug seems to work reliably but x86_64 does not and i think i have discovered why. in x86-64, a cpu within a domu can be removed with vcpu-set but subsequent calls do nothing. after xenwatch_thread grabs the event triggered by the write to the store, it calls the registered handler and never comes back. eventually, __cpu_die in drivers/xen/core/smpboot.c spins while waiting

Please see the three patches that fix the ACPI AML and QEMU race. They have been Ack-ed by both George (for inclusion in Xen 4.3) and by Stefano. They should be candidates for back-port in older hypervisors. Konrad Rzeszutek Wilk (3): piix4acpi, xen, vcpu hotplug: Split the notification from the changes. piix4acpi, xen: Clarify that the qemu_set_irq calls just do an IRQ pulse.

On Fri, Feb 14, 2020 at 16:05:00 +0100, Lentes, Bernd wrote: > Hi, > > i'm playing a bit around with vcpus. > My guest is Windows 10 1903. > This is the excerpt from the config: > ... > <vcpu placement='static' current='2'>4</vcpu> > <vcpus> > <vcpu id='0' enabled='yes' hotpluggable='no'/> >

On 05/28/2013 01:24 AM, Dennis Chen wrote: > Hi, > > We know that there is a command "setvcpus" in virsh used to "change > number of virtual CPUs", now we just have the need to change vcpu count > dynamically for a running VM, so I tried this command (the vcpu count is > 2 in the VM xml file), below is the result: > > virsh # setvcpus 3 --count 4 >

Hi, i'm playing a bit around with vcpus. My guest is Windows 10 1903. This is the excerpt from the config: ... <vcpu placement='static' current='2'>4</vcpu> <vcpus> <vcpu id='0' enabled='yes' hotpluggable='no'/> <vcpu id='1' enabled='yes' hotpluggable='yes'/> <vcpu id='2'

Hi, We know that there is a command "setvcpus" in virsh used to "change number of virtual CPUs", now we just have the need to change vcpu count dynamically for a running VM, so I tried this command (the vcpu count is 2 in the VM xml file), below is the result: virsh # setvcpus 3 --count 4 error: invalid argument: requested vcpus is greater than max allowable vcpus for the

This patch adds new control messages for vcpu hotplug events. Via the xm vcpu_hotplug sub-program, VCPUS in domains can be enabled/disabled when CONFIG_HOTPLUG_CPU is enabled in the target domain''s kernel. Currently there is nothing that tracks whether a VCPU is up or down. My previous [1]patch added a new per-VCPU flag (VCPUF_down) which could be used to keep track of which VCPUS are

Hi, The xm vcpu-set command is able to set zero to the number of VCPU of a domain. Therefore I think that it is a natural result that the xm start command fails. But I think that a xm vcpu-set command must fail usually. # xm list Name ID Mem VCPUs State Time(s) Domain-0 0 942 2 r----- 75.2 vm1

----- On Feb 15, 2020, at 12:47 AM, Marc Roos M.Roos@f1-outsourcing.eu wrote: > Would you mind sharing your xml? I have strange high host load on idle > windows guest/domain <domain type='kvm'> <name>pathway</name> <uuid>8235e5ae-0756-4286-5407-9fa02d372046</uuid> <description>Pathway Studio Dietrich</description> <memory

On Tue, Mar 03, 2015 at 03:48:02AM -0500, Chen Hanxiao wrote: > Signed-off-by: Chen Hanxiao <chenhanxiao@cn.fujitsu.com> > + if (compresslevel >= 0) { > + snprintf (compresslevel_s, sizeof compresslevel_s, "%d", compresslevel); > + ADD_ARG (argv, i, "-c"); > + ADD_ARG (argv, i, compresslevel_s); > + } Because compresslevel is an optional

Hi, I don''t understand something about the vcpu-set function. My configuration: *memory = 2048 cpu = ''1-2'' maxvcpu = 4 vcpus = 1* When the DomU is running, and when i try to set 2 or 3 vpcu i get the error : xm vcpu-set domain_name 2 *Error: Cannot set vcpus greater than max vcpus on running domain Usage: xm vcpu-set <Domain> <vCPUs> Set the number of

Hello, after installing many guest systems I realised that three of them need more than one core. So I changed the config file with vcpus=2 But that doesn''t help and the command xm vcpu-set ... doesn''t change the actual number of vcpus either. It is weird that the dom0 appears as many as the number of cores if I use "xm vcpu-list": Name

Hi, I don''t want to hijack this thread. But as I lately posted a question which mainly was about weight and cap and this fits in perfectly (and also you seem to be an expert here), I repeat it below. In the meantime I saw an academic article Ludmilla Cherkasova et al. from which I understood that you have to careful that a Dom0 doesn''t get too much weight, as otherwise

Hello all ;) Tell I have a Xeon server with 4 vcpus If on this box I have some guets, tell 10, what is the best solutions : - Set all guests to 1 vcpu ? - Set all guests to 4 vcpus ? I well understand that if I set a guest with 4 vcpus and all others only with one vpcus, then the one with 4 vcpus will have more "cpu time" available than others guests. But in case I''d like

On Sun, Sep 15, 2019 at 12:21:08PM +0200, info@layer7.net wrote: >Hi folks! > >i created a server with this XML file: > ><domain type='lxc'> > <name>lxctest1</name> > <uuid>227bd347-dd1d-4bfd-81e1-01052e91ffe2</uuid> > <metadata> > <libosinfo:libosinfo

Support the vcpu_is_preempted() functionality under KVM. This will enhance lock performance on overcommitted hosts (more runnable vcpus than physical cpus in the system) as doing busy waits for preempted vcpus will hurt system performance far worse than early yielding. Use one field of struct kvm_steal_time to indicate that if one vcpu is running or not. unix benchmark result: host: kernel

On 06/01/2013 03:16 PM, Dennis Chen wrote: > On 05/29/2013 04:28 AM, Eric Blake wrote: >> On 05/28/2013 02:24 PM, Eric Blake wrote: >> >>>> So the question is: is there any method I can't find yet to change the >>>> vcpu count of a running vm dynamically? >>> Wait for newer qemu and libvirt, or else pitch in and help write >>> patches.