All of lore.kernel.org
 help / color / mirror / Atom feed
From: David F Barrera <dfbp@us.ibm.com>
To: "Nakajima, Jun" <jun.nakajima@intel.com>
Cc: xen-devel@lists.xensource.com, "Puthiyaparambil,
	Aravindh" <aravindh.puthiyaparambil@unisys.com>
Subject: Re: Error starting xend
Date: Fri, 19 Aug 2005 16:53:01 -0500	[thread overview]
Message-ID: <430654BD.60806@us.ibm.com> (raw)
In-Reply-To: <7F740D512C7C1046AB53446D3720017304ED17BA@scsmsx402.amr.corp.intel.com>



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
>
>  
>

  reply	other threads:[~2005-08-19 21:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-19 21:43 Error starting xend Nakajima, Jun
2005-08-19 21:53 ` David F Barrera [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-09-13 18:30 Error starting Xend Puthiyaparambil, Aravindh
2005-09-13 16:37 Puthiyaparambil, Aravindh
2005-08-22 17:24 Error starting xend Puthiyaparambil, Aravindh
2005-08-22 16:43 Nakajima, Jun
2005-08-22 16:17 Puthiyaparambil, Aravindh
2005-08-19 22:20 Ian Pratt
2005-08-19 22:17 Puthiyaparambil, Aravindh
2005-08-19 21:30 Puthiyaparambil, Aravindh
2005-08-19 21:29 Nakajima, Jun
2005-08-19 21:21 Puthiyaparambil, Aravindh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=430654BD.60806@us.ibm.com \
    --to=dfbp@us.ibm.com \
    --cc=aravindh.puthiyaparambil@unisys.com \
    --cc=jun.nakajima@intel.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.