RE: [Xen-ia64-devel] New error trying to create a domain(usinglatestxend-unstable

["Duan, Ronghui" <ronghui.duan@xxxxxxxxx>]

Hi Keir,

The CS# 17131 which I write for bind guest to NUMA node via cpu affinity
missed one condition existing in some machines, where there aren't any
cpus but only memories. Under this condition it will fail to set
cpu_affinity because of none parameter. I cope with this condition in
the new patch and make a little change of the methods to find suitable
node to bind guest. When counting the VCPUs which have pinned to node, I
use an average count instead the original sum count of Vcpus pinning
cpus on certain node in case that there may be less cpus on some nodes
than others.

Sorry for triggering this bug and how do you think about the change?

>-----Original Message-----
>From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-ia64-devel-
>bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Duan, Ronghui
>Sent: Tuesday, March 18, 2008 6:00 PM
>To: Kayvan Sylvan; Masaki Kanno; xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>Subject: RE: [Xen-ia64-devel] New error trying to create a
>domain(usinglatestxend-unstable
>
>I see the info in your "xm info"
>>node_to_cpu            : node0:0-7
>>                         node1:no cpus
>>node_to_memory         : node0:0
>>                         node1:14081
>This is because your memory and CPU are on different nodes (bad
>performance, maybe you want to do any special test). But Xen's code
>doesn't init proper node_to_cpu information under this boundary
>condition. So when looking for cpus of certain nodes, it finds nothing.
>Need to fix this.
>
>>-----Original Message-----
>>From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
>[mailto:xen-ia64-devel-
>>bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Kayvan Sylvan
>>Sent: Tuesday, March 18, 2008 5:26 PM
>>To: Masaki Kanno; xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>>Subject: RE: [Xen-ia64-devel] New error trying to create a domain
>>(usinglatestxend-unstable
>>
>>Hmmm... Thank you.
>>
>>Adding "cpus=" allowed me to create the domain, but I don't understand
>why.
>>Can you explain it?
>>
>>The "xm info" output follows:
>>
>>host                   : superd3p2
>>release                : 2.6.18.8-xen
>>version                : #3 SMP Tue Mar 18 05:46:19 GMT 2008
>>machine                : ia64
>>nr_cpus                : 8
>>nr_nodes               : 2
>>cores_per_socket       : 2
>>threads_per_core       : 1
>>cpu_mhz                : 1598
>>hw_caps                :
>>00000000:00000000:00000000:00000000:00000000:00000000:00000000:0000000
0
>:
>>total_memory           : 16288
>>free_memory            : 14081
>>node_to_cpu            : node0:0-7
>>                         node1:no cpus
>>node_to_memory         : node0:0
>>                         node1:14081
>>xen_major              : 3
>>xen_minor              : 3
>>xen_extra              : -unstable
>>xen_caps               : xen-3.0-ia64 xen-3.0-ia64be hvm-3.0-ia64
>hvm-3.0-
>>ia64-sioemu
>>xen_scheduler          : credit
>>xen_pagesize           : 16384
>>platform_params        : virt_start=0xf000000000000000
>>xen_changeset          : Fri Mar 14 15:07:45 2008 -0600
>17209:8c921adf4833
>>cc_compiler            : gcc version 3.4.6 20060404 (Red Hat 3.4.6-3)
>>cc_compile_by          : root
>>cc_compile_domain      : invent.psi.com
>>cc_compile_date        : Tue Mar 18 01:17:19 GMT 2008
>>xend_config_format     : 4
>>
>>
>>________________________________________
>>From: Masaki Kanno [kanno.masaki@xxxxxxxxxxxxxx]
>>Sent: Tuesday, March 18, 2008 1:55 AM
>>To: Kayvan Sylvan; xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>>Subject: Re: [Xen-ia64-devel] New error trying to create a domain
>(using
>>latestxend-unstable
>>
>>Hi Kayvan,
>>
>>Could you define "cpus" into the domain configuration file?
>> e.g. cpus = "0-3"
>>
>>And could you show a result of xm info?
>>
>>Best regards,
>> Kan
>>
>>_______________________________________________
>>Xen-ia64-devel mailing list
>>Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>>http://lists.xensource.com/xen-ia64-devel
>
>_______________________________________________
>Xen-ia64-devel mailing list
>Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>http://lists.xensource.com/xen-ia64-devel

bind_guest.patch
Description: bind_guest.patch

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel