On 05/28/2014 02:13 AM, Chris Friesen wrote:
>
> I've got a libvirt-created instance where I've been messing with affinity, and
> now something is strange.
>
> I did the following in python:
>
>>>> import libvirt
>>>> conn=libvirt.open("qemu:///system")
>>>> dom = conn.lookupByName('instance-00000027')
>>>> dom.vcpus()
> ([(0, 1, 528150000000L, 2), (1, 1, 548070000000L, 3)], [(False, False, True,
> False), (False, False, True, False)])
>
> I'm totally confused by that "3". It's supposed to represent the physical cpu
> that virtual cpu 1 is running on. But cpu 3 isn't even in the allowable
> affinity map for vcpu 1.
>
Do you get the same value via 'virsh vcpuinfo'? It's the virsh command that
uses the same API (virDomainGetVcpus).
Jan
Attachment:
signature.asc
Description: OpenPGP digital signature
-- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list