On Tue, Apr 14, 2009 at 09:53:51PM +0200, Gerrit Slomma wrote: > vcpuinfo returns a wrong value for kvm with libvirt 0.6.2: > Furthermore even when pinning all - in my case both - vCPUs of the > domain to the second CPU of the node virsh reports the first cpu as the > assigned cpu. > > virsh # vcpupin rr019v3 0 1 > virsh # vcpuinfo rr019v3 > VCPU: 0 > CPU: 0 > Status: laufend > CPU-Affinität: -y > > VCPU: 1 > CPU: 0 > Status: laufend > CPU-Affinität: -y > > > Watching at the code in virsh.c i am a little bit on my wits end where > virVcpuInfoPtr is defined as i am no c-programmer - only some java on my > side. Unfortunately the answer is rather simple. We never fill in any value for the 'cpu' field of virVcpuInfo for QEMU/KVM guests, which means the 'CPU:' line should by virsh will always be zero. We need to fix this in the QEMU driver. Regards, Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| -- Libvir-list mailing list Libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list