
17 May
2012
17 May
'12
4:24 p.m.
On 05/17/2012 02:42 PM, Doron Fediuck wrote: > Hi All, > Currently the VDSM has a CPU pinning hook. > We'd like to add better support of it into the engine itself. > Here's a design draft to cover it: http://www.ovirt.org/wiki/Features/Design/cpu-pinning > > Please review and comment if needed. Hi, I have a number of comments: 1. Will the user have any indication for the maximum amount of vCPU's? 2. What happens if a VM is already configured with the same CPU pin info? Will this be shared? 3. Would it possible to extend this to limit the MHz of CPU that can be allocated to a VM? 5. If the VM has more than one core, will each core have to be mapped? 6. "similar to the existing hook Shahar wrote" - can you please put a link the the hook that Shahar wrote. :) This will be helpful for those of us unfamiliar with it. 7. Why will live migration not be supported? What is the gap to have this type of support? Thanks Gary > Thanks!