On Tue, Dec 25, 2007 at 03:37:58PM +0900, Nobuhiro Itou wrote: > Hi > > As well as virt-install, I want to set the cpu pinning > at the time of creating domain with virt-manager. > And, because virtinst changeset 320 was committed, > I add the allocation setting of pCPU to virt-manager. > > some notes are follows: > - This feature works with changeset of virtinst is 320 or later. > - The specification about the CPU pin parameter follows that of virt-install. > - This function can be used only for xen hypervisor. > - When 1 pCPU in xen hypervisor, this function is disabled. I appreciate your work on this patch, however, IMHO this is not something we should add to the new VM wizard. The need to pin CPUs at install time has a tiny niche scenario of usefullness. For most people pinning CPUs is a bad idea as they will make worse decisions that the hypervisor/OS schedular. The more features we add to the 'new VM wizard', the more complex the user interaction becomes. Our goal for virt-manager is to provide UI which targets the most commonly used features only and explicitly leave out features only used in a niche use cases, thus keeping the app simple to use. IMHO, pinning CPUs at install time is just not a feature which is critical enough to justify in the new VM wizard. I *would* however welcome a patch to the 'Virtual Machine Details' dialog where you can currently adjust the number of vCPUs. It would make sense to be able to have UI for pinning vCPUs of an existing domain in this part of the UI. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| _______________________________________________ et-mgmt-tools mailing list et-mgmt-tools@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/et-mgmt-tools
