Hi,
Is there any other way I could allocate sockets, cores and threads to my
virtual machine? I looked over the virsh man page and I didn't find anything
that talks about sockets, threads and cores.
I edited the vm xml file and added this...
<cpu>
<topology sockets='1' cores='2' threads='1'/>
</cpu>
Saw this in the libvirt documents, http://libvirt.org/formatdomain.html
Setting this up shows me a single core in my vm, but I don't see any sockets
and threads. Can somebody tell me how to do it in a right way so that I see
all sockets, cores and threads allocated in my vm.
Thanks
joe
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://listman.redhat.com/archives/libvirt-users/attachments/20110118/e4773e08/attachment.htm>
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>
Thanks
Joe
On Tue, Jan 18, 2011 at 2:50 PM, joe fu <joefuu10 at gmail.com> wrote:
>
> Hi,
>
> Is there any other way I could allocate sockets, cores and threads to my
> virtual machine? I looked over the virsh man page and I didn't find
anything
> that talks about sockets, threads and cores.
> I edited the vm xml file and added this...
>
> <cpu>
> <topology sockets='1' cores='2'
threads='1'/>
> </cpu>
>
> Saw this in the libvirt documents, http://libvirt.org/formatdomain.html
>
> Setting this up shows me a single core in my vm, but I don't see any
> sockets and threads. Can somebody tell me how to do it in a right way so
> that I see all sockets, cores and threads allocated in my vm.
>
> Thanks
> joe
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://listman.redhat.com/archives/libvirt-users/attachments/20110118/e3d8a5fe/attachment.htm>
Maybe Matching Threads
- Can I configure cores instead of CPU's
- 'virsh capabilities' on Debian Wheezy-amd64 reports different cpu to Wheezy-i386 (on same hardware)
- libvirt does not show same CPU Model as /proc/cpuinfo for CPU Model info.
- Re: 'virsh capabilities' on Debian Wheezy-amd64 reports different cpu to Wheezy-i386 (on same hardware)
- Re: 'virsh capabilities' on Debian Wheezy-amd64 reports different cpu to Wheezy-i386 (on same hardware)