Whereas Xen3''s "xm list" used to provide a list of which physical CPU each domain had last been running on, it now has only a field "VCPUs" with (I presume) the number of VCPUs allocated to that domain. Would I be correct to understand that the only way for me to know even a snapshot of the physical-CPU/domain mapping is to engage in pinning? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I believe ''xm vcpu-list'' gives that info in Xen3 :- # xm vcpu-list Name ID VCPU CPU State Time(s) CPU Affinity Domain-0 0 0 0 r-- 2217.7 0 jlink 7 0 1 -b- 1391.2 0 db01 8 0 1 -b- 420.6 0 web01 9 0 1 -b- 334.6 0 pg8test 10 0 0 --- 1241.0 0 David. Charles Duffy wrote:> Whereas Xen3''s "xm list" used to provide a list of which physical CPU > each domain had last been running on, it now has only a field "VCPUs" > with (I presume) the number of VCPUs allocated to that domain. > > Would I be correct to understand that the only way for me to know even a > snapshot of the physical-CPU/domain mapping is to engage in pinning? > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > >-- David Brain - Bandwidth.com mailto:dbrain@bandwidth.com (919) 297 1078 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users