[virt-tools-list] virt-install cpuset=auto error

[yupzhang]

There is a bug about cpuset=auto *Bug 834495* 
<https://bugzilla.redhat.com/show_bug.cgi?id=834495> -virt-install 
--cpuset=auto breaks [ASSIGNED]

Thanks
yuping
On 07/21/2012 04:40 PM, Jared wrote:
> Hi.
>
> I'm trying to create new KVM images using the --cpuset=auto option "to
> automatically determine the optimal cpu pinning using numa data" (from the
> man page).  Problem is, I can't get this to work.  The following always
> appears in my virt-install.log file when creating a new image:
>
> DEBUG (cli:833) Not setting cpuset: unsupported operand type(s) for *:
> 'NoneType' and 'int'
>
> I'm pretty sure I do have NUMA support properly configured and enabled and
> all of that, but unfortunately I don't have a great deal of experience with
> this stuff yet, so I can't guarantee that this isn't a user problem.
>
> I've primarily been following the advice in this guide:
>
> http://berrange.com/posts/2010/02/12/controlling-guest-cpu-numa-affinity-in-libvirt-with-qemu-kvm-xen/
>
> When I run the nodeinfo and capabilities commands, I do get the appropriate
> NUM cell(s) and topology output as shown in his examples.  Similarly for
> freecell, memtune, numatune, and all the other related commands I could find
> discussed on the internet.  However, no matter what I try, I can't get
> virt-install to do the auto pinning for me.
>
> Is there anything else I could be missing?  Some library or process
> dependency outside of libvirt that I'm missing?  or could this be just a bug?
>
> Would appreciate any guidance in troubleshooting and identifying the
> problem.  I've been working on this off-and-on for a couple nights now and
> have had no luck.
>
> Thanks.
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/virt-tools-list/attachments/20120723/d3f5e635/attachment.htm>