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: Thu, 25 Mar 2010 19:38:31 -0700	[thread overview]
Message-ID: <9f975f341003251938mbc288f6r9528dfd37f01d7ac@mail.gmail.com> (raw)
In-Reply-To: <20100324072947.GE1878@reaktio.net>


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

I could not get anything out of it.  Attached is the xend file.

can you please let me know?

Thanks



On Wed, Mar 24, 2010 at 12:29 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote:

> On Tue, Mar 23, 2010 at 03:46:15PM -0700, kishore kumar wrote:
> >    which init-script?
> >
>
> /etc/init.d/xend
>
> -- Pasi
>
> >    On Tue, Mar 23, 2010 at 3:11 PM, Pasi Kärkkäinen <[1]pasik@iki.fi>
> wrote:
> >
> >      On Tue, Mar 23, 2010 at 02:42:32PM -0700, kishore kumar wrote:
> >      >    Any suggestions on this please??
> >      >
> >
> >      "xend: command not found" sounds like there's something wrong
> >      with your xen tools installation.
> >
> >      Do you actually have xend installed?
> >
> >      Also please read the lines 53, 40, and 45 from the init-script
> >      to see what's on those lines.
> >
> >      -- Pasi
> >
> >      >    On Tue, Mar 23, 2010 at 1:30 PM, kishore kumar
> >      <[1][2]bodkekumar@gmail.com>
> >      >    wrote:
> >      >
> >      >      cat /proc/xen/capabilities gives me
> >      >
> >      >      control_d
> >      >      /etc/init.d/xend start  gives me
> >      >
> >      >      mount: xenfs already mounted or /proc/xen busy
> >      >      mount: according to mtab, none is already mounted on
> /proc/xen
> >      >      /etc/init.d/xend: line53: xend: command not found
> >      >      /etc/init.d/xend: line40: xend: command not found
> >      >      /etc/init.d/xend: line45: xend: command not found
> >      >      On Tue, Mar 23, 2010 at 1:16 PM, Pasi Kärkkäinen
> >      <[2][3]pasik@iki.fi>
> >      >      wrote:
> >      >
> >      >        On Tue, Mar 23, 2010 at 01:11:14PM -0700, kishore kumar
> wrote:
> >      >        >    Yes.  I see below in /proc/xen after mount
> >      >        >
> >      >        >    capabilities
> >      >        >    privcmd
> >      >        >    xenbus
> >      >        >    xsd_kva
> >      >        >    xsd_port.
> >      >        >
> >      >
> >      >        Looks ok.. What does "cat /proc/xen/capabilities" say ?
> >      >
> >      >        Does "/etc/init.d/xend start" work?
> >      >
> >      >        -- Pasi
> >      >        >    On Tue, Mar 23, 2010 at 1:05 PM, Pasi Kärkkäinen
> >      >        <[1][3][4]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][4][5]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][3][5][6]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][4][6][7]
> 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][5][7][8]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][6][8][9]
> http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> >      >        >      >      >    2. mailto:[6][7][9][10]pasik@iki.fi
> >      >        >      >
> >      >        >      > References
> >      >        >      >
> >      >        >      >    Visible links
> >      >        >      >    1. [8][10][11]
> http://2.6.32.10/kernel/drivers/xen
> >      >        >      >    2. mailto:[9][11][12]pasik@iki.fi
> >      >        >      >    3.
> >      >        >
> >      >
> >      [10][12][13]
> http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> >      >        >      >    4. mailto:[11][13][14]pasik@iki.fi
> >      >        >      >    5.
> >      >        >
> >      >
> >      [12][14][15]
> http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> >      >        >      >    6. mailto:[13][15][16]pasik@iki.fi
> >      >        >
> >      >        > References
> >      >        >
> >      >        >    Visible links
> >      >        >    1. mailto:[16][17]pasik@iki.fi
> >      >        >    2. [17][18]http://2.6.32.10/kernel/drivers/xen
> >      >        >    3. mailto:[18][19]pasik@iki.fi
> >      >        >    4.
> >      >
> >       [19][20]
> http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> >      >        >    5. mailto:[20][21]pasik@iki.fi
> >      >        >    6.
> >      >
> >       [21][22]
> http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> >      >        >    7. mailto:[22][23]pasik@iki.fi
> >      >        >    8. [23][24]http://2.6.32.10/kernel/drivers/xen
> >      >        >    9. mailto:[24][25]pasik@iki.fi
> >      >        >   10.
> >      >
> >       [25][26]
> http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> >      >        >   11. mailto:[26][27]pasik@iki.fi
> >      >        >   12.
> >      >
> >       [27][28]
> http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> >      >        >   13. mailto:[28][29]pasik@iki.fi
> >      >
> >      > References
> >      >
> >      >    Visible links
> >      >    1. mailto:[30]bodkekumar@gmail.com
> >      >    2. mailto:[31]pasik@iki.fi
> >      >    3. mailto:[32]pasik@iki.fi
> >      >    4. [33]http://2.6.32.10/kernel/drivers/xen
> >      >    5. mailto:[34]pasik@iki.fi
> >      >    6.
> >      [35]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> >      >    7. mailto:[36]pasik@iki.fi
> >      >    8.
> >      [37]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> >      >    9. mailto:[38]pasik@iki.fi
> >      >   10. [39]http://2.6.32.10/kernel/drivers/xen
> >      >   11. mailto:[40]pasik@iki.fi
> >      >   12.
> >      [41]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> >      >   13. mailto:[42]pasik@iki.fi
> >      >   14.
> >      [43]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> >      >   15. mailto:[44]pasik@iki.fi
> >      >   16. mailto:[45]pasik@iki.fi
> >      >   17. [46]http://2.6.32.10/kernel/drivers/xen
> >      >   18. mailto:[47]pasik@iki.fi
> >      >   19.
> >      [48]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> >      >   20. mailto:[49]pasik@iki.fi
> >      >   21.
> >      [50]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> >      >   22. mailto:[51]pasik@iki.fi
> >      >   23. [52]http://2.6.32.10/kernel/drivers/xen
> >      >   24. mailto:[53]pasik@iki.fi
> >      >   25.
> >      [54]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> >      >   26. mailto:[55]pasik@iki.fi
> >      >   27.
> >      [56]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> >      >   28. mailto:[57]pasik@iki.fi
> >
> > References
> >
> >    Visible links
> >    1. mailto:pasik@iki.fi
> >    2. mailto:bodkekumar@gmail.com
> >    3. mailto:pasik@iki.fi
> >    4. mailto:pasik@iki.fi
> >    5. http://2.6.32.10/kernel/drivers/xen
> >    6. mailto:pasik@iki.fi
> >    7. http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> >    8. mailto:pasik@iki.fi
> >    9. http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> >   10. mailto:pasik@iki.fi
> >   11. http://2.6.32.10/kernel/drivers/xen
> >   12. mailto:pasik@iki.fi
> >   13. http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> >   14. mailto:pasik@iki.fi
> >   15. http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> >   16. mailto:pasik@iki.fi
> >   17. mailto:pasik@iki.fi
> >   18. http://2.6.32.10/kernel/drivers/xen
> >   19. mailto:pasik@iki.fi
> >   20. http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> >   21. mailto:pasik@iki.fi
> >   22. http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> >   23. mailto:pasik@iki.fi
> >   24. http://2.6.32.10/kernel/drivers/xen
> >   25. mailto:pasik@iki.fi
> >   26. http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> >   27. mailto:pasik@iki.fi
> >   28. http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> >   29. mailto:pasik@iki.fi
> >   30. mailto:bodkekumar@gmail.com
> >   31. mailto:pasik@iki.fi
> >   32. mailto:pasik@iki.fi
> >   33. http://2.6.32.10/kernel/drivers/xen
> >   34. mailto:pasik@iki.fi
> >   35. http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> >   36. mailto:pasik@iki.fi
> >   37. http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> >   38. mailto:pasik@iki.fi
> >   39. http://2.6.32.10/kernel/drivers/xen
> >   40. mailto:pasik@iki.fi
> >   41. http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> >   42. mailto:pasik@iki.fi
> >   43. http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> >   44. mailto:pasik@iki.fi
> >   45. mailto:pasik@iki.fi
> >   46. http://2.6.32.10/kernel/drivers/xen
> >   47. mailto:pasik@iki.fi
> >   48. http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> >   49. mailto:pasik@iki.fi
> >   50. http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> >   51. mailto:pasik@iki.fi
> >   52. http://2.6.32.10/kernel/drivers/xen
> >   53. mailto:pasik@iki.fi
> >   54. http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> >   55. mailto:pasik@iki.fi
> >   56. http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> >   57. mailto:pasik@iki.fi
>

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

[-- Attachment #2: xend --]
[-- Type: application/octet-stream, Size: 1545 bytes --]

#!/bin/bash
#
# xend		Script to start and stop the Xen control daemon.
#
# Author:       Keir Fraser <keir.fraser@cl.cam.ac.uk>
#
# chkconfig: 2345 98 01
# description: Starts and stops the Xen control daemon.
### BEGIN INIT INFO
# Provides:          xend
# Required-Start:    $syslog $remote_fs
# Should-Start:
# Required-Stop:     $syslog $remote_fs
# Should-Stop:
# Default-Start:     3 4 5
# Default-Stop:      0 1 2 6
# Default-Enabled:   yes
# Short-Description: Start/stop xend
# Description:       Starts and stops the Xen control daemon.
### END INIT INFO

if   test "x$1" = xstart && \
     test -d /proc/xen && \
   ! test -d /proc/xen/capabilities && \
     grep '	xenfs$' /proc/filesystems >/dev/null && \
   ! grep '^xenfs ' /proc/mounts >/dev/null;
then
	mount -t xenfs xenfs /proc/xen
fi

if ! grep -q "control_d" /proc/xen/capabilities ; then
	exit 0
fi

# Wait for Xend to be up
function await_daemons_up
{
	i=1
	rets=10
	xend status
	while [ $? -ne 0 -a $i -lt $rets ]; do
	    sleep 1
	    echo -n .
	    i=$(($i + 1))
	    xend status
	done
}

case "$1" in
  start)
	mkdir -p /var/lock/subsys
	touch /var/lock/subsys/xend
	xend start
	await_daemons_up
	;;
  stop)
	xend stop
	rm -f /var/lock/subsys/xend
	;;
  status)
	xend status
	;;
  reload)
        xend reload
        ;;
  restart|force-reload)
	xend restart
	await_daemons_up
	;;
  *)
	# do not advertise unreasonable commands that there is no reason
	# to use with this device
	echo $"Usage: $0 {start|stop|status|restart|reload|force-reload}"
	exit 1
esac

exit $?


[-- Attachment #3: 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-26  2:38 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
2010-03-23 20:16             ` [Xen-users] " 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 [this message]
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=9f975f341003251938mbc288f6r9528dfd37f01d7ac@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).