Re: [libvirt] [PATCH 0/5] qemu: report actual vcpu state in virVcpuInfo

2016-07-29 Thread Viktor Mihajlovski
On 29.07.2016 08:30, Peter Krempa wrote: > > So I was testing the data reported from the monitor while doing some > work on othe vCPU hotplug series and found that for x86 the halted state > is reported if the CPU is idle and thus halted. This state it therefore > almost always reported when the

Re: [libvirt] [PATCH 0/5] qemu: report actual vcpu state in virVcpuInfo

2016-07-29 Thread Peter Krempa
On Mon, Jul 18, 2016 at 07:56:36 +0200, Peter Krempa wrote: > On Thu, Jul 14, 2016 at 16:35:37 +0200, Viktor Mihajlovski wrote: > > Currently, the virVcpuInfo returned by virDomainGetVcpus() will always > > report a state of VIR_VCPU_RUNNING for each defined domain vcpu even if > > the vcpu is

Re: [libvirt] [PATCH 0/5] qemu: report actual vcpu state in virVcpuInfo

2016-07-17 Thread Peter Krempa
On Thu, Jul 14, 2016 at 16:35:37 +0200, Viktor Mihajlovski wrote: > Currently, the virVcpuInfo returned by virDomainGetVcpus() will always > report a state of VIR_VCPU_RUNNING for each defined domain vcpu even if > the vcpu is currently in the halted state. > > As the monitor interface is in fact

[libvirt] [PATCH 0/5] qemu: report actual vcpu state in virVcpuInfo

2016-07-14 Thread Viktor Mihajlovski
Currently, the virVcpuInfo returned by virDomainGetVcpus() will always report a state of VIR_VCPU_RUNNING for each defined domain vcpu even if the vcpu is currently in the halted state. As the monitor interface is in fact reporting the accurate state, it is rather easy to transport this