2017-12-20 23:48 GMT+08:00 gordon chung :
>
>
> On 2017-12-20 10:06 AM, Jaze Lee wrote:
>> Yes, i notice it. But when there will be vcpu.*.time? Which libvirt version?
>> We use libvirt 3.2.0 and it does not have vcpu.*.time, so it will go
>> to fall back.
>
> i have:
>
> virsh # version
> Compiled
On 2017-12-20 10:06 AM, Jaze Lee wrote:
> Yes, i notice it. But when there will be vcpu.*.time? Which libvirt version?
> We use libvirt 3.2.0 and it does not have vcpu.*.time, so it will go
> to fall back.
i have:
virsh # version
Compiled against library: libvirt 3.2.0
Using library: libvirt 3.
2017-12-20 22:29 GMT+08:00 gordon chung :
>
>
> On 2017-12-20 03:14 AM, Jaze Lee wrote:
>> Hello,
>> We use ceilometer newton, and also master calculates cpu same as newton.
>> It is in
>> https://github.com/openstack/ceilometer/blob/master/ceilometer/compute/virt/libvirt/inspector.py#L183
On 2017-12-20 03:14 AM, Jaze Lee wrote:
> Hello,
> We use ceilometer newton, and also master calculates cpu same as newton.
> It is in
> https://github.com/openstack/ceilometer/blob/master/ceilometer/compute/virt/libvirt/inspector.py#L183
>
> I test with a two vcpu vm, and find usin
Hello,
We use ceilometer newton, and also master calculates cpu same as newton.
It is in
https://github.com/openstack/ceilometer/blob/master/ceilometer/compute/virt/libvirt/inspector.py#L183
I test with a two vcpu vm, and find using this method as line 183
we can not get cpu util 100, al
