Hi, Jan I think you should use 0.2.1 at this moment. libvirt cannot handle Xen-hypervisor-domctl correctly on 0.2.2. But Xen-hypervisor-sysctl works fine. This problem recognized in two weeks ago, but I have no time to investigate this issue.
Thanks Atsushi SAKAI Jan Michael <[EMAIL PROTECTED]> wrote: > Cheers libvirt, > > I've tested the CLI virsh with my recent compiled version of libvirt > and version 0.1.9. In Version 0.2.2 vcpuinfo provides wrong > information. In version 0.1.9 only the values for VCPU and CPU are > wrong. Do you have any idea why? > > See the test results below. > > Jan > > > xm vcpu-list > Name ID VCPUs CPU State Time(s) CPU > Affinity > Domain-0 0 0 0 r-- 95463.9 any cpu > Domain-0 0 1 - --p 55.6 any cpu > stornode 6 0 1 -b- 2036.1 1 > worknode 5 0 1 -b- 2073.9 1 > > > virsh vcpuinfo (0,5,6) in version 0.2.2 > - Domain-0 > VCPU: 0 > CPU: 0 > State: blocked > CPU time: 0.0s > CPU Affinity: -- > > - worknode > virsh # vcpuinfo 5 > VCPU: 0 > CPU: 0 > State: blocked > CPU time: 4.3s > CPU Affinity: -- > > - stornode > VCPU: 0 > CPU: 0 > State: blocked > CPU time: 4.3s > CPU Affinity: -- > > > > virsh vcpuinfo (0,5,6) in version 0.1.9 > - Domain-0 > VCPU: 0 > CPU: 0 > State: running > CPU time: 95466.7s > CPU Affinity: yy > > - worknode > VCPU: 0 > CPU: 1 > State: blocked > CPU time: 2074.2s > CPU Affinity: -y > > - stornode > VCPU: 0 > CPU: 1 > State: blocked > CPU time: 2036.5s > CPU Affinity: -y > > -- > Libvir-list mailing list > Libvir-list@redhat.com > https://www.redhat.com/mailman/listinfo/libvir-list -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
