I guess I'm too late. Thanks for the response anyway. So, let me getinto the point right away.
+What's the virtualisation host you're trying this out on?
KVM.
+Which version of libvirt is it running?
Compiled against library: libvir 0.8.3
Using library: libvir 0.8.3
Using API: QEMU 0.8.3
Running hypervisor: QEMU 0.9.1
+ What guest OS's have you tried with?
Thanks,
Joe
On Thu, Jan 20, 2011 at 11:34 AM, Justin Clift <jclift@xxxxxxxxxx> wrote:
On 18/01/2011, at 9:25 PM, joe fu wrote:Hi Joe,
> I'm checked out my /proc/cpuinfo file and I'm finding the following changes.
>
> Physical ID : 0
> Siblings : 1
> core id :0
> cpu cores :1
> apicid :0
> initial apicid:0
>
> This is what I noticed when I edited the vm with this ...
> <cpu>
> <topology sockets='1' cores='2' threads='4'/>
> </cpu>
Looking at the same part of the XML description as you did:
http://libvirt.org/formatdomain.html#elementsCPU
You're right, in that it shows we have some kind of capacity to process that info.
Some questions that might help us find the answer:
+ What's the virtualisation host you're trying this out on?
i.e. KVM/Xen/vSphere/ESX/VirtualBox/etc
+ Which version of libvirt is it running?
+ What guest OS's have you tried with?
Regards and best wishes,
Justin Clift
