I am seeing the following error on my SLES9 SP2 RC3 ES7000 x86_64 box
while trying to start xend.
SLES9SP2RC3-x86-64:~/xen/vm # Traceback (most recent call last):
File
"/root/xen/xen-unstable.hg/dist/install/usr/lib64/python/xen/xend/xensto
re/xsobj.py", line 328, in introduceDomain
db.introduceDomain(dom, page, evtchn, path)
File
"/root/xen/xen-unstable.hg/dist/install/usr/lib64/python/xen/xend/xensto
re/xsnode.py", line 465, in introduceDomain
self.store.introduceDomain(dom, page, evtchn, path)
File
"/root/xen/xen-unstable.hg/dist/install/usr/lib64/python/xen/xend/xensto
re/xsnode.py", line 370, in introduceDomain
self.getxs().introduce_domain(dom, page, evtchn.port1, path)
RuntimeError: (22, ''Invalid argument'')
If I do an "xm list" after this I am able to see Dom0
SLES9SP2RC3-x86-64:~/xen/vm # xm list
Name Id Mem(MB) CPU VCPU(s) State Time(s)
Domain-0 0 507 0 1 r---- 83.7
When I try to start a VM I get the following error.
SLES9SP2RC3-x86-64:~/xen/vm # xm create vm1
Using config file "vm1".
Error: Error creating domain: ''NoneType'' object has no
attribute
''getRemotePort''
I did a clean rebuild but this continues to happen. Any idea why this is
happening?
Aravindh
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Puthiyaparambil, Aravindh wrote:> I am seeing the following error on my SLES9 SP2 RC3 ES7000 x86_64 box > while trying to start xend. > > SLES9SP2RC3-x86-64:~/xen/vm # Traceback (most recent call last): > File >"/root/xen/xen-unstable.hg/dist/install/usr/lib64/python/xen/xend/xensto> re/xsobj.py", line 328, in introduceDomain > db.introduceDomain(dom, page, evtchn, path) > File >"/root/xen/xen-unstable.hg/dist/install/usr/lib64/python/xen/xend/xensto> re/xsnode.py", line 465, in introduceDomain > self.store.introduceDomain(dom, page, evtchn, path) > File >"/root/xen/xen-unstable.hg/dist/install/usr/lib64/python/xen/xend/xensto> re/xsnode.py", line 370, in introduceDomain > self.getxs().introduce_domain(dom, page, evtchn.port1, path) > RuntimeError: (22, ''Invalid argument'') > > > If I do an "xm list" after this I am able to see Dom0 > > SLES9SP2RC3-x86-64:~/xen/vm # xm list > Name Id Mem(MB) CPU VCPU(s) State Time(s) > Domain-0 0 507 0 1 r---- 83.7 > > When I try to start a VM I get the following error. > > SLES9SP2RC3-x86-64:~/xen/vm # xm create vm1 > Using config file "vm1". > Error: Error creating domain: ''NoneType'' object has no attribute > ''getRemotePort'' > > I did a clean rebuild but this continues to happen. Any idea why this > is happening?Did you check the error message on the console?> > Aravindh >Jun --- Intel Open Source Technology Center _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Oops I meant to post that too. This is what I see on the console. (XEN) DOM0: (file=mm.c, line=1055) Bad L1 flags 800000 Aravindh> -----Original Message----- > From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel- > bounces@lists.xensource.com] On Behalf Of Nakajima, Jun > Sent: Friday, August 19, 2005 5:30 PM > To: Puthiyaparambil, Aravindh; xen-devel@lists.xensource.com > Subject: RE: [Xen-devel] Error starting xend > > Puthiyaparambil, Aravindh wrote: > > I am seeing the following error on my SLES9 SP2 RC3 ES7000 x86_64box> > while trying to start xend. > > > > SLES9SP2RC3-x86-64:~/xen/vm # Traceback (most recent call last): > > File > > >"/root/xen/xen-unstable.hg/dist/install/usr/lib64/python/xen/xend/xensto> > re/xsobj.py", line 328, in introduceDomain > > db.introduceDomain(dom, page, evtchn, path) > > File > > >"/root/xen/xen-unstable.hg/dist/install/usr/lib64/python/xen/xend/xensto> > re/xsnode.py", line 465, in introduceDomain > > self.store.introduceDomain(dom, page, evtchn, path) > > File > > >"/root/xen/xen-unstable.hg/dist/install/usr/lib64/python/xen/xend/xensto> > re/xsnode.py", line 370, in introduceDomain > > self.getxs().introduce_domain(dom, page, evtchn.port1, path) > > RuntimeError: (22, ''Invalid argument'') > > > > > > If I do an "xm list" after this I am able to see Dom0 > > > > SLES9SP2RC3-x86-64:~/xen/vm # xm list > > Name Id Mem(MB) CPU VCPU(s) State Time(s) > > Domain-0 0 507 0 1 r---- 83.7 > > > > When I try to start a VM I get the following error. > > > > SLES9SP2RC3-x86-64:~/xen/vm # xm create vm1 > > Using config file "vm1". > > Error: Error creating domain: ''NoneType'' object has no attribute > > ''getRemotePort'' > > > > I did a clean rebuild but this continues to happen. Any idea whythis> > is happening? > > Did you check the error message on the console? > > > > > Aravindh > > > > Jun > --- > Intel Open Source Technology Center > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Puthiyaparambil, Aravindh wrote:> Oops I meant to post that too. This is what I see on the console. > > (XEN) DOM0: (file=mm.c, line=1055) Bad L1 flags 800000This means non-NX/XD support is not complete yet. Can you figure out who in xenlinux made that request? If you can look at the return address of the hypercall, you can tell who it is. Jun --- Intel Open Source Technology Center> > Aravindh > >> -----Original Message----- >> From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel- >> bounces@lists.xensource.com] On Behalf Of Nakajima, Jun >> Sent: Friday, August 19, 2005 5:30 PM >> To: Puthiyaparambil, Aravindh; xen-devel@lists.xensource.com >> Subject: RE: [Xen-devel] Error starting xend >> >> Puthiyaparambil, Aravindh wrote: >>> I am seeing the following error on my SLES9 SP2 RC3 ES7000 x86_64 >>> box while trying to start xend. >>> >>> SLES9SP2RC3-x86-64:~/xen/vm # Traceback (most recent call last): >>> File >>> >> >"/root/xen/xen-unstable.hg/dist/install/usr/lib64/python/xen/xend/xensto>>> re/xsobj.py", line 328, in introduceDomain >>> db.introduceDomain(dom, page, evtchn, path) >>> File >>> >> >"/root/xen/xen-unstable.hg/dist/install/usr/lib64/python/xen/xend/xensto>>> re/xsnode.py", line 465, in introduceDomain >>> self.store.introduceDomain(dom, page, evtchn, path) File >>> >> >"/root/xen/xen-unstable.hg/dist/install/usr/lib64/python/xen/xend/xensto>>> re/xsnode.py", line 370, in introduceDomain >>> self.getxs().introduce_domain(dom, page, evtchn.port1, path) >>> RuntimeError: (22, ''Invalid argument'') >>> >>> >>> If I do an "xm list" after this I am able to see Dom0 >>> >>> SLES9SP2RC3-x86-64:~/xen/vm # xm list >>> Name Id Mem(MB) CPU VCPU(s) State Time(s) >>> Domain-0 0 507 0 1 r---- 83.7 >>> >>> When I try to start a VM I get the following error. >>> >>> SLES9SP2RC3-x86-64:~/xen/vm # xm create vm1 >>> Using config file "vm1". >>> Error: Error creating domain: ''NoneType'' object has no attribute >>> ''getRemotePort'' >>> >>> I did a clean rebuild but this continues to happen. Any idea why >>> this is happening? >> >> Did you check the error message on the console? >> >>> >>> Aravindh >>> >> >> Jun >> --- >> Intel Open Source Technology Center >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xensource.com >> http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Nakajima, Jun wrote:>Puthiyaparambil, Aravindh wrote: > > >>Oops I meant to post that too. This is what I see on the console. >> >>(XEN) DOM0: (file=mm.c, line=1055) Bad L1 flags 800000 >> >> > > >I am seeing that message, too, on a RHEL 4 box. It is happening at boot, in my case, as soon as the login screen is displayed. Red Hat Enterprise Linux AS release 4 (Nahant) Kernel 2.6.12-xen0 on an i686 lamb5 login: (XEN) DOM0: (file=mm.c, line=1055) Bad L1 flags 80000000 (XEN) (XEN) DOM0: (file=mm.c, line=1055) Bad L1 flags 80000000 (XEN) (XEN) DOM0: (file=mm.c, line=1055) Bad L1 flags 80000000 (XEN) (XEN) DOM0: (file=mm.c, line=1055) Bad L1 flags 80000000 (XEN) (XEN) DOM0: (file=mm.c, line=1055) Bad L1 flags 80000000 (XEN) (XEN) DOM0: (file=mm.c, line=1055) Bad L1 flags 80000000 (XEN) (XEN) DOM0: (file=mm.c, line=1055) Bad L1 flags 80000000 (XEN)>This means non-NX/XD support is not complete yet. Can you figure out who >in xenlinux made that request? If you can look at the return address of >the hypercall, you can tell who it is. > >Jun >--- >Intel Open Source Technology Center > > > >>Aravindh >> >> >> >>>-----Original Message----- >>>From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel- >>>bounces@lists.xensource.com] On Behalf Of Nakajima, Jun >>>Sent: Friday, August 19, 2005 5:30 PM >>>To: Puthiyaparambil, Aravindh; xen-devel@lists.xensource.com >>>Subject: RE: [Xen-devel] Error starting xend >>> >>>Puthiyaparambil, Aravindh wrote: >>> >>> >>>>I am seeing the following error on my SLES9 SP2 RC3 ES7000 x86_64 >>>>box while trying to start xend. >>>> >>>>SLES9SP2RC3-x86-64:~/xen/vm # Traceback (most recent call last): >>>>File >>>> >>>> >>>> >"/root/xen/xen-unstable.hg/dist/install/usr/lib64/python/xen/xend/xensto > > >>>>re/xsobj.py", line 328, in introduceDomain >>>> db.introduceDomain(dom, page, evtchn, path) >>>> File >>>> >>>> >>>> >"/root/xen/xen-unstable.hg/dist/install/usr/lib64/python/xen/xend/xensto > > >>>>re/xsnode.py", line 465, in introduceDomain >>>> self.store.introduceDomain(dom, page, evtchn, path) File >>>> >>>> >>>> >"/root/xen/xen-unstable.hg/dist/install/usr/lib64/python/xen/xend/xensto > > >>>>re/xsnode.py", line 370, in introduceDomain >>>> self.getxs().introduce_domain(dom, page, evtchn.port1, path) >>>>RuntimeError: (22, ''Invalid argument'') >>>> >>>> >>>>If I do an "xm list" after this I am able to see Dom0 >>>> >>>>SLES9SP2RC3-x86-64:~/xen/vm # xm list >>>>Name Id Mem(MB) CPU VCPU(s) State Time(s) >>>>Domain-0 0 507 0 1 r---- 83.7 >>>> >>>>When I try to start a VM I get the following error. >>>> >>>>SLES9SP2RC3-x86-64:~/xen/vm # xm create vm1 >>>>Using config file "vm1". >>>>Error: Error creating domain: ''NoneType'' object has no attribute >>>>''getRemotePort'' >>>> >>>>I did a clean rebuild but this continues to happen. Any idea why >>>>this is happening? >>>> >>>> >>>Did you check the error message on the console? >>> >>> >>> >>>>Aravindh >>>> >>>> >>>> >>>Jun >>>--- >>>Intel Open Source Technology Center >>> >>>_______________________________________________ >>>Xen-devel mailing list >>>Xen-devel@lists.xensource.com >>>http://lists.xensource.com/xen-devel >>> >>> > > > >_______________________________________________ >Xen-devel mailing list >Xen-devel@lists.xensource.com >http://lists.xensource.com/xen-devel > > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
I am sure this a stupid question :-) But how do I look at the return address of the hypercall in question (do_mmu_update)? By looking at the stack? Won''t that be the Xen stack rather than the Guest stack? Aravindh> -----Original Message----- > From: Nakajima, Jun [mailto:jun.nakajima@intel.com] > Sent: Friday, August 19, 2005 5:44 PM > To: Puthiyaparambil, Aravindh; xen-devel@lists.xensource.com > Subject: RE: [Xen-devel] Error starting xend > > Puthiyaparambil, Aravindh wrote: > > Oops I meant to post that too. This is what I see on the console. > > > > (XEN) DOM0: (file=mm.c, line=1055) Bad L1 flags 800000 > > This means non-NX/XD support is not complete yet. Can you figure outwho> in xenlinux made that request? If you can look at the return addressof> the hypercall, you can tell who it is. > > Jun > --- > Intel Open Source Technology Center > > > > > Aravindh > > > >> -----Original Message----- > >> From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel- > >> bounces@lists.xensource.com] On Behalf Of Nakajima, Jun > >> Sent: Friday, August 19, 2005 5:30 PM > >> To: Puthiyaparambil, Aravindh; xen-devel@lists.xensource.com > >> Subject: RE: [Xen-devel] Error starting xend > >> > >> Puthiyaparambil, Aravindh wrote: > >>> I am seeing the following error on my SLES9 SP2 RC3 ES7000 x86_64 > >>> box while trying to start xend. > >>> > >>> SLES9SP2RC3-x86-64:~/xen/vm # Traceback (most recent call last): > >>> File > >>> > >> > > >"/root/xen/xen-unstable.hg/dist/install/usr/lib64/python/xen/xend/xensto> >>> re/xsobj.py", line 328, in introduceDomain > >>> db.introduceDomain(dom, page, evtchn, path) > >>> File > >>> > >> > > >"/root/xen/xen-unstable.hg/dist/install/usr/lib64/python/xen/xend/xensto> >>> re/xsnode.py", line 465, in introduceDomain > >>> self.store.introduceDomain(dom, page, evtchn, path) File > >>> > >> > > >"/root/xen/xen-unstable.hg/dist/install/usr/lib64/python/xen/xend/xensto> >>> re/xsnode.py", line 370, in introduceDomain > >>> self.getxs().introduce_domain(dom, page, evtchn.port1, path) > >>> RuntimeError: (22, ''Invalid argument'') > >>> > >>> > >>> If I do an "xm list" after this I am able to see Dom0 > >>> > >>> SLES9SP2RC3-x86-64:~/xen/vm # xm list > >>> Name Id Mem(MB) CPU VCPU(s) State Time(s) > >>> Domain-0 0 507 0 1 r---- 83.7 > >>> > >>> When I try to start a VM I get the following error. > >>> > >>> SLES9SP2RC3-x86-64:~/xen/vm # xm create vm1 > >>> Using config file "vm1". > >>> Error: Error creating domain: ''NoneType'' object has no attribute > >>> ''getRemotePort'' > >>> > >>> I did a clean rebuild but this continues to happen. Any idea why > >>> this is happening? > >> > >> Did you check the error message on the console? > >> > >>> > >>> Aravindh > >>> > >> > >> Jun > >> --- > >> Intel Open Source Technology Center > >> > >> _______________________________________________ > >> Xen-devel mailing list > >> Xen-devel@lists.xensource.com > >> http://lists.xensource.com/xen-devel >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> Puthiyaparambil, Aravindh wrote: > > Oops I meant to post that too. This is what I see on the console. > > > > (XEN) DOM0: (file=mm.c, line=1055) Bad L1 flags 800000 > > This means non-NX/XD support is not complete yet. Can you > figure out who in xenlinux made that request? If you can look > at the return address of the hypercall, you can tell who it is.After the above printk do a "show_guest_stack()" Ian _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> > (XEN) DOM0: (file=mm.c, line=1055) Bad L1 flags 800000 > > This means non-NX/XD support is not complete yet. Can you figure out > who in xenlinux made that request? If you can look at the return > address of the hypercall, you can tell who it is.direct_remap_area_pages() [arch/xen/x86_64/mm/ioremap.c] is the xenlinux function that is making the request. There are two HYPERVISOR_mmu_update() calls. It is happening on the second call (line 457). Hope this helps. Aravindh _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Puthiyaparambil, Aravindh wrote:>>> (XEN) DOM0: (file=mm.c, line=1055) Bad L1 flags 800000 >> >> This means non-NX/XD support is not complete yet. Can you figure out >> who in xenlinux made that request? If you can look at the return >> address of the hypercall, you can tell who it is. > > direct_remap_area_pages() [arch/xen/x86_64/mm/ioremap.c] is the > xenlinux function that is making the request. There are two > HYPERVISOR_mmu_update() calls. It is happening on the second call > (line 457). > > Hope this helps. > AravindhCan you try this patch? diff -r 4adaea8679cf linux-2.6-xen-sparse/arch/xen/x86_64/mm/ioremap.c --- a/linux-2.6-xen-sparse/arch/xen/x86_64/mm/ioremap.c Mon Aug 22 06:45:10 2005 +++ b/linux-2.6-xen-sparse/arch/xen/x86_64/mm/ioremap.c Mon Aug 22 09:40:47 2005 @@ -442,7 +442,7 @@ * __direct_remap_area_pages(). */ v->val = (machine_addr & PAGE_MASK) | pgprot_val(prot); - + v->val &= __supported_pte_mask; machine_addr += PAGE_SIZE; address += PAGE_SIZE; v++; Jun --- Intel Open Source Technology Center _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jun, That patch did the trick. Let''s hope this completes the non-NX/XD support. I am now able to run without the rm_nx patch on the ES7000 x86_64 (with my clustered APIC kludge). Thanks, Aravindh> -----Original Message----- > From: Nakajima, Jun [mailto:jun.nakajima@intel.com] > Sent: Monday, August 22, 2005 12:44 PM > To: Puthiyaparambil, Aravindh; xen-devel@lists.xensource.com > Cc: Vessey, Bruce A; Subrahmanian, Raj; Davis, Jason; Magolan, John F; > Koren, Bradley J > Subject: RE: [Xen-devel] Error starting xend > > Puthiyaparambil, Aravindh wrote: > >>> (XEN) DOM0: (file=mm.c, line=1055) Bad L1 flags 800000 > >> > >> This means non-NX/XD support is not complete yet. Can you figureout> >> who in xenlinux made that request? If you can look at the return > >> address of the hypercall, you can tell who it is. > > > > direct_remap_area_pages() [arch/xen/x86_64/mm/ioremap.c] is the > > xenlinux function that is making the request. There are two > > HYPERVISOR_mmu_update() calls. It is happening on the second call > > (line 457). > > > > Hope this helps. > > Aravindh > > Can you try this patch? > > diff -r 4adaea8679cf linux-2.6-xen-sparse/arch/xen/x86_64/mm/ioremap.c > --- a/linux-2.6-xen-sparse/arch/xen/x86_64/mm/ioremap.c Mon Aug22> 06:45:10 2005 > +++ b/linux-2.6-xen-sparse/arch/xen/x86_64/mm/ioremap.c Mon Aug22> 09:40:47 2005 > @@ -442,7 +442,7 @@ > * __direct_remap_area_pages(). > */ > v->val = (machine_addr & PAGE_MASK) | pgprot_val(prot); > - > + v->val &= __supported_pte_mask; > machine_addr += PAGE_SIZE; > address += PAGE_SIZE; > v++; > > Jun > --- > Intel Open Source Technology Center_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
With changset 6774:4d899a738d59 I am getting the following error on x86_64 Xen when trying to start xend. Exception starting xend: name ''server'' is not defined Aravindh Puthiyaparambil Windows Server Platforms Tredyffrin E240 Phone 610-648-2416 NET2 x385-2416 E-Mail: aravindh.puthiyaparambil@unisys.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
I no longer see this issue with changeset: 6789:fe5b84a24d43 Aravindh ________________________________ From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Puthiyaparambil, Aravindh Sent: Tuesday, September 13, 2005 12:38 PM To: xen-devel@lists.xensource.com Cc: Koren, Bradley J; Subrahmanian, Raj; Vessey, Bruce A Subject: [Xen-devel] Error starting Xend With changset 6774:4d899a738d59 I am getting the following error on x86_64 Xen when trying to start xend. Exception starting xend: name ''server'' is not defined Aravindh Puthiyaparambil _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel