The reason why this is happening is that on line 1093 in
XendDomainInfo.py, "1" is being treated as an int. My python skills are
weak. How can I cast it as a long or unsigned long? I tried using long()
and "0x1L". Both don't seem to be working.
XendDomainInfo.py: 1093 xc.domain_pincpu(self.domid, 0, 1 << cpu)
Thanks,
Aravindh
> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-devel-
> bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Puthiyaparambil, Aravindh
> Sent: Friday, October 21, 2005 5:49 PM
> To: Kamble, Nitin A; xen-devel
> Subject: RE: [Xen-devel] Unable to bring up x86_64 UP DomU on
processor
> #32
>
> Nitin,
>
> Thanks for the lead. This is what /var/log/xend-debug.log says:
>
> OverflowError: signed integer is greater than maximum
> mainInfo.create(config)
> File
>
"/root/xen/xen-unstable.hg/dist/install/usr/lib64/python/xen/xend/XendDo
> mainInfo.py", line 147, in create
> vm.initDomain()
> File
>
"/root/xen/xen-unstable.hg/dist/install/usr/lib64/python/xen/xend/XendDo
> mainInfo.py", line 1093, in initDomain
> xc.domain_pincpu(self.domid, 0, 1 << cpu)
> OverflowError: signed integer is greater than maximum
> cpus = self.vm.getVCpuCount())
> error: (0, 'Error')
> Failed allocation for dom 19: 893952 pages order 0 addr_bits 0
>
> Aravindh
>
> > -----Original Message-----
> > From: Kamble, Nitin A [mailto:nitin.a.kamble@xxxxxxxxx]
> > Sent: Friday, October 21, 2005 5:38 PM
> > To: Puthiyaparambil, Aravindh; xen-devel
> > Subject: RE: [Xen-devel] Unable to bring up x86_64 UP DomU on
> processor
> > #32
> >
> > That's Good to know. Then this should be easy to fix. Probably the
> > python code (xm, xend) has some issue.
> > You can look at /var/log/xen* files to see what is the reason of
the
> > error.
> >
> > Thanks & Regards,
> > Nitin
> >
>
------------------------------------------------------------------------
> > -----------
> > Open Source Technology Center, Intel Corp
> >
> > >-----Original Message-----
> > >From: Puthiyaparambil, Aravindh
> > >[mailto:aravindh.puthiyaparambil@xxxxxxxxxx]
> > >Sent: Friday, October 21, 2005 2:35 PM
> > >To: Kamble, Nitin A; xen-devel
> > >Subject: RE: [Xen-devel] Unable to bring up x86_64 UP DomU on
> processor
> > #32
> > >
> > >Nitin,
> > >
> > >When I don't specify "cpu=n", the domain does come up on CPU #32.
> > >
> > >Name ID VCPU CPU State Time(s)
CPU
> > Map
> > >Domain-0 0 0 0 r-- 80.1
> > >0xffffffffffffffff
> > >vm1 1 0 31 r-- 7.6
> > >0xffffffffffffffff
> > >
> > >
> > >But shouldn't I be able to specify "cpu=31"?
> > >
> > >Thanks,
> > >Aravindh
> > >
> > >> -----Original Message-----
> > >> From: Kamble, Nitin A [mailto:nitin.a.kamble@xxxxxxxxx]
> > >> Sent: Friday, October 21, 2005 5:16 PM
> > >> To: Puthiyaparambil, Aravindh; xen-devel
> > >> Subject: RE: [Xen-devel] Unable to bring up x86_64 UP DomU on
> > >processor
> > >> #32
> > >>
> > >> Aravindh,
> > >> By default Domains are assigned highest least loaded cpu. So
> domU
> > >> should get the CPU 31 as a default if you don't specify cpu=n
> option.
> > >>
> > >> What do you see if you don't specify the "cpu=n"?
> > >>
> > >> Thanks & Regards,
> > >> Nitin
> > >>
> >
>
>-----------------------------------------------------------------------
> > -
> > >> -----------
> > >> Open Source Technology Center, Intel Corp
> > >>
> > >> >-----Original Message-----
> > >> >From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-devel-
> > >> >bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Puthiyaparambil,
> Aravindh
> > >> >Sent: Friday, October 21, 2005 2:11 PM
> > >> >To: xen-devel
> > >> >Subject: [Xen-devel] Unable to bring up x86_64 UP DomU on
> processor
> > >#32
> > >> >
> > >> >I am running x86_64 Xen on an ES7000 with 32 logical processors.
I
> > am
> > >> >trying to force a DomU to come up on CPU #32 by specifying
> "cpu=31"
> > >in
> > >> >the DomU configuration file. "xm" gives me the following error
> > >message:
> > >> >
> > >> >"Error: Error creating domain: signed integer is greater than
> > >maximum"
> > >> >
> > >> >I am able to do "cpu=30" successfully.
> > >> >
> > >> >Is this a bug? Should I be opening up a bug report?
> > >> >
> > >> >BTW, this does NOT happen on x86_32 PAE.
> > >> >
> > >> >Aravindh
> > >> >
> > >> >_______________________________________________
> > >> >Xen-devel mailing list
> > >> >Xen-devel@xxxxxxxxxxxxxxxxxxx
> > >> >http://lists.xensource.com/xen-devel
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home