xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: kishore kumar <bodkekumar@gmail.com>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: xen-devel@lists.xensource.com, xen-users@lists.xensource.com
Subject: Re: Starting xend: grep: /proc/xen/capabilities: No such file or directory
Date: Tue, 23 Mar 2010 13:11:14 -0700	[thread overview]
Message-ID: <9f975f341003231311o3d60501eg259c6724451cd738@mail.gmail.com> (raw)
In-Reply-To: <20100323200558.GA1878@reaktio.net>


[-- Attachment #1.1: Type: text/plain, Size: 4602 bytes --]

Yes.  I see below in /proc/xen after mount

capabilities
privcmd
xenbus
xsd_kva
xsd_port.

On Tue, Mar 23, 2010 at 1:05 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote:

> On Tue, Mar 23, 2010 at 01:04:34PM -0700, kishore kumar wrote:
> >    attached is the screen shot.
> >
> >    I did
> >    cd /lib/modules/[1]2.6.32.10/kernel/drivers/xen
> >      modprobe xen-evtchn
> >
> >    and then did
> >
> >    mount -t xenfs none  /proc/xen.
> >
> >    But still the same problem.
> >
>
> Does the mount succeed? Is there anything under /proc/xen?
>
> -- Pasi
>
> >    On Tue, Mar 23, 2010 at 12:51 PM, Pasi Kärkkäinen <[2]pasik@iki.fi>
> wrote:
> >
> >      On Tue, Mar 23, 2010 at 12:43:16PM -0700, kishore kumar wrote:
> >      >    I have the Xen 3.4.3.rc4 installed alone with
> >      >
> >      >    make xen
> >      >
> >      >    make stubdom,
> >      >
> >      >    make tools
> >      >
> >      >    make install-xen
> >      >    make install-tools
> >      >    make install-stubdom
> >      >
> >      >
> >      >    and pulled dom 0 kernel from
> >      >
> >      >    git clone
> >      git://[1][3]git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
>  >      >    and compiled the kernel.
> >      >
> >      >    modified the grub.conf as below
> >      >
> >      >    title       xen/pvops (2.6.32.10)
> >      >    root         (hd0,0)
> >      >    kernel       /xen.gz loglvl=all guest_loglvl=all sync_console
> >      >    console_to_ring com1=115200,8n1 console=vga,com1 lapic=debug
> >      >    apic_verbosity=debug apic=debug iommu=1 msi=1
> >      >    module       /vmlinuz-2.6.32.10 ro
> root=/dev/VolGroup01/LogVol00
> >      >    console=hvc0 earlyprintk=xen nomodeset initcall_debug debug
> >      loglevel=10
> >      >    module       /initrd-2.6.32.10.img
> >      >
> >      >    and rebooted the machine.  I hope this is a Xen+ dom0. Please
> >      correct me
> >      >    if I am wrong here.
> >      >
> >      >    After reboot I see
> >      >    Starting xend:  grep: /proc/xen/capabilities: No such file or
> >      directory
> >      >
> >      >    I added none /proc/xen xenfs defaults 0 0  in /etc/fstab file
> and
> >      >    rebooted.  still the same problem.
> >      >
> >      >    Is there anything else that needs to be done?
> >      >
> >
> >      So is that version of xend automatically loading xen-evtchn.ko
> driver
> >      module?
> >      Try loading the module with "modprobe xen-evtchn" and then try
> mounting
> >      the /proc/xen.
> >      >    Am I booted with Xen+dom0 or just the linux kernel?
> >      >
> >
> >      Most probably to Xen+dom0, if you chose the grub entry you pasted
> above.
> >
> >      -- Pasi
> >      >    My uname -a is
> >      >
> >      >    Linux localhost.localdomain 2.6.32.10
> >      >
> >      >    Thanks
> >      >
> >      >
> >      >    On Tue, Mar 23, 2010 at 12:23 AM, Pasi Kärkkäinen
> >      <[2][4]pasik@iki.fi> wrote:
> >      >
> >      >      On Mon, Mar 22, 2010 at 05:00:41PM -0700, kishore kumar
> wrote:
> >      >      >    Hi all,
> >      >      >
> >      >      >    I see the below message after I install xen3.4.3-rc4 and
> >      pvops dom
> >      >      0
> >      >      >    kernel 2.6.32.10 and reboot the machine.
> >      >      >
> >      >      >    Starting xend:  grep: /proc/xen/capabilities: No such
> file
> >      or
> >      >      directory
> >      >      >
> >      >      >    I did below steps too.
> >      >      >
> >      >      >    step 1:  insmod xen-evtchn.ko
> >      >      >    step 2: Added none /proc/xen xenfs defaults 0 0  in
> >      /etc/fstab
> >      >      file.
> >      >      >
> >      >      >    Is there something that I am missing here?
> >      >
> >      >      Well then actually mount /proc/xen :)
> >      >      (or reboot).
> >      >
> >      >      Also did you verify you've actually rebooted to Xen+dom0?
> >      >      -- Pasi
> >      >
> >      > References
> >      >
> >      >    Visible links
> >      >    1. [5]
> http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> >      >    2. mailto:[6]pasik@iki.fi
> >
> > References
> >
> >    Visible links
> >    1. http://2.6.32.10/kernel/drivers/xen
> >    2. mailto:pasik@iki.fi
> >    3. http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> >    4. mailto:pasik@iki.fi
> >    5. http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> >    6. mailto:pasik@iki.fi
>
>
>

[-- Attachment #1.2: Type: text/html, Size: 6502 bytes --]

[-- Attachment #2: Type: text/plain, Size: 137 bytes --]

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

  reply	other threads:[~2010-03-23 20:11 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-23  0:00 Starting xend: grep: /proc/xen/capabilities: No such file or directory kishore kumar
2010-03-23  7:23 ` [Xen-users] " Pasi Kärkkäinen
2010-03-23 19:43   ` kishore kumar
2010-03-23 19:51     ` Pasi Kärkkäinen
2010-03-23 20:04       ` kishore kumar
2010-03-23 20:05         ` [Xen-users] " Pasi Kärkkäinen
2010-03-23 20:11           ` kishore kumar [this message]
2010-03-23 20:16             ` Pasi Kärkkäinen
2010-03-23 20:30               ` kishore kumar
2010-03-23 21:42                 ` kishore kumar
2010-03-23 22:11                   ` Pasi Kärkkäinen
2010-03-23 22:46                     ` kishore kumar
2010-03-24  7:29                       ` Pasi Kärkkäinen
2010-03-26  2:38                         ` kishore kumar
2010-03-26  6:58                           ` Pasi Kärkkäinen
2010-03-26 16:46                             ` kishore kumar
2010-03-26 17:26                               ` [Xen-users] " Pasi Kärkkäinen
2010-03-26 18:12                                 ` kishore kumar
2010-03-26 18:17                                   ` Pasi Kärkkäinen
2010-03-26 21:04                                     ` kishore kumar
     [not found]                                       ` <20100326213743.GR1878@reaktio.net>
     [not found]                                         ` <9f975f341003261504t30f400f0j5ee8401405f660cf@mail.gmail.com>
     [not found]                                           ` <20100327095913.GS1878@reaktio.net>
2010-03-30 18:33                                             ` kishore kumar
2010-03-30 19:51                                               ` Pasi Kärkkäinen
2010-03-30 21:09                                                 ` kishore kumar
2010-03-29 16:57 ` [Xen-devel] " Pasi Kärkkäinen

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=9f975f341003231311o3d60501eg259c6724451cd738@mail.gmail.com \
    --to=bodkekumar@gmail.com \
    --cc=pasik@iki.fi \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-users@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).