3 Jun
2014
3 Jun
'14
2:55 p.m.
Ok, then I think you should find the lack of this API is non-fatal in Icehouse / Juno now. You're perfectly right, this error is non-fatal anymore. With the full machine virt does Parallels have a separate process or thread for each vCPU, and if so can we identify the PIDs for the vCPUs to let us do proper pCPU<->vCPU mapping & reporting. Every vCPU uses its own thread. A proper mapping pCPU<->vCPU is not available at the moment. Due to distributed architecture of our product, implementation of this feature may take some efforts. Is it really necessary to have this mapping?
-- Regards, Alexander Burluka