From mboxrd@z Thu Jan 1 00:00:00 1970 From: David F Barrera Subject: Re: Error starting xend Date: Fri, 19 Aug 2005 16:53:01 -0500 Message-ID: <430654BD.60806@us.ibm.com> References: <7F740D512C7C1046AB53446D3720017304ED17BA@scsmsx402.amr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <7F740D512C7C1046AB53446D3720017304ED17BA@scsmsx402.amr.corp.intel.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Nakajima, Jun" Cc: xen-devel@lists.xensource.com, "Puthiyaparambil, Aravindh" List-Id: xen-devel@lists.xenproject.org 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 > > >