WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 		  
Home Products Support Community News
 
   
 

xen-devel

[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: [Xen-users] Starting xend: grep: /proc/xen/capabilities: No such fil

from [Pasi Kärkkäinen] [Permanent Link][Original]
To: kishore kumar <bodkekumar@xxxxxxxxx>
Subject: Re: [Xen-users] Starting xend: grep: /proc/xen/capabilities: No such file or directory
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Wed, 24 Mar 2010 09:29:47 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 24 Mar 2010 00:31:10 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <9f975f341003231546o2c6a9ab4g67a07cc6069ad878@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <9f975f341003231243g4dfb12ffn1ca428c8fc22379c@xxxxxxxxxxxxxx> <20100323195113.GX1878@xxxxxxxxxxx> <9f975f341003231304x54120858lf1a7d878bfcdfe2d@xxxxxxxxxxxxxx> <20100323200558.GA1878@xxxxxxxxxxx> <9f975f341003231311o3d60501eg259c6724451cd738@xxxxxxxxxxxxxx> <20100323201604.GB1878@xxxxxxxxxxx> <9f975f341003231330v6fa12cd9w4ed92be92b1410df@xxxxxxxxxxxxxx> <9f975f341003231442i6d135398x853ea7431b7dc672@xxxxxxxxxxxxxx> <20100323221104.GD1878@xxxxxxxxxxx> <9f975f341003231546o2c6a9ab4g67a07cc6069ad878@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17) 
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@xxxxxx> 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@xxxxxxxxx>
>      >    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@xxxxxx>
>      >      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@xxxxxx> 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@xxxxxx> 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@xxxxxx> 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@xxxxxx
>      >        >      >
>      >        >      > References
>      >        >      >
>      >        >      >    Visible links
>      >        >      >    1. [8][10][11]http://2.6.32.10/kernel/drivers/xen
>      >        >      >    2. mailto:[9][11][12]pasik@xxxxxx
>      >        >      >    3.
>      >        >
>      >
>      [10][12][13]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
>      >        >      >    4. mailto:[11][13][14]pasik@xxxxxx
>      >        >      >    5.
>      >        >
>      >
>      [12][14][15]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
>      >        >      >    6. mailto:[13][15][16]pasik@xxxxxx
>      >        >
>      >        > References
>      >        >
>      >        >    Visible links
>      >        >    1. mailto:[16][17]pasik@xxxxxx
>      >        >    2. [17][18]http://2.6.32.10/kernel/drivers/xen
>      >        >    3. mailto:[18][19]pasik@xxxxxx
>      >        >    4.
>      >
>       [19][20]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
>      >        >    5. mailto:[20][21]pasik@xxxxxx
>      >        >    6.
>      >
>       [21][22]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
>      >        >    7. mailto:[22][23]pasik@xxxxxx
>      >        >    8. [23][24]http://2.6.32.10/kernel/drivers/xen
>      >        >    9. mailto:[24][25]pasik@xxxxxx
>      >        >   10.
>      >
>       [25][26]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
>      >        >   11. mailto:[26][27]pasik@xxxxxx
>      >        >   12.
>      >
>       [27][28]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
>      >        >   13. mailto:[28][29]pasik@xxxxxx
>      >
>      > References
>      >
>      >    Visible links
>      >    1. mailto:[30]bodkekumar@xxxxxxxxx
>      >    2. mailto:[31]pasik@xxxxxx
>      >    3. mailto:[32]pasik@xxxxxx
>      >    4. [33]http://2.6.32.10/kernel/drivers/xen
>      >    5. mailto:[34]pasik@xxxxxx
>      >    6.
>      [35]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
>      >    7. mailto:[36]pasik@xxxxxx
>      >    8.
>      [37]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
>      >    9. mailto:[38]pasik@xxxxxx
>      >   10. [39]http://2.6.32.10/kernel/drivers/xen
>      >   11. mailto:[40]pasik@xxxxxx
>      >   12.
>      [41]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
>      >   13. mailto:[42]pasik@xxxxxx
>      >   14.
>      [43]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
>      >   15. mailto:[44]pasik@xxxxxx
>      >   16. mailto:[45]pasik@xxxxxx
>      >   17. [46]http://2.6.32.10/kernel/drivers/xen
>      >   18. mailto:[47]pasik@xxxxxx
>      >   19.
>      [48]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
>      >   20. mailto:[49]pasik@xxxxxx
>      >   21.
>      [50]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
>      >   22. mailto:[51]pasik@xxxxxx
>      >   23. [52]http://2.6.32.10/kernel/drivers/xen
>      >   24. mailto:[53]pasik@xxxxxx
>      >   25.
>      [54]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
>      >   26. mailto:[55]pasik@xxxxxx
>      >   27.
>      [56]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
>      >   28. mailto:[57]pasik@xxxxxx
> 
> References
> 
>    Visible links
>    1. mailto:pasik@xxxxxx
>    2. mailto:bodkekumar@xxxxxxxxx
>    3. mailto:pasik@xxxxxx
>    4. mailto:pasik@xxxxxx
>    5. http://2.6.32.10/kernel/drivers/xen
>    6. mailto:pasik@xxxxxx
>    7. http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
>    8. mailto:pasik@xxxxxx
>    9. http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
>   10. mailto:pasik@xxxxxx
>   11. http://2.6.32.10/kernel/drivers/xen
>   12. mailto:pasik@xxxxxx
>   13. http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
>   14. mailto:pasik@xxxxxx
>   15. http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
>   16. mailto:pasik@xxxxxx
>   17. mailto:pasik@xxxxxx
>   18. http://2.6.32.10/kernel/drivers/xen
>   19. mailto:pasik@xxxxxx
>   20. http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
>   21. mailto:pasik@xxxxxx
>   22. http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
>   23. mailto:pasik@xxxxxx
>   24. http://2.6.32.10/kernel/drivers/xen
>   25. mailto:pasik@xxxxxx
>   26. http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
>   27. mailto:pasik@xxxxxx
>   28. http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
>   29. mailto:pasik@xxxxxx
>   30. mailto:bodkekumar@xxxxxxxxx
>   31. mailto:pasik@xxxxxx
>   32. mailto:pasik@xxxxxx
>   33. http://2.6.32.10/kernel/drivers/xen
>   34. mailto:pasik@xxxxxx
>   35. http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
>   36. mailto:pasik@xxxxxx
>   37. http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
>   38. mailto:pasik@xxxxxx
>   39. http://2.6.32.10/kernel/drivers/xen
>   40. mailto:pasik@xxxxxx
>   41. http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
>   42. mailto:pasik@xxxxxx
>   43. http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
>   44. mailto:pasik@xxxxxx
>   45. mailto:pasik@xxxxxx
>   46. http://2.6.32.10/kernel/drivers/xen
>   47. mailto:pasik@xxxxxx
>   48. http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
>   49. mailto:pasik@xxxxxx
>   50. http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
>   51. mailto:pasik@xxxxxx
>   52. http://2.6.32.10/kernel/drivers/xen
>   53. mailto:pasik@xxxxxx
>   54. http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
>   55. mailto:pasik@xxxxxx
>   56. http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
>   57. mailto:pasik@xxxxxx

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: [Xen-devel] Cannot access memory beyond end of bootstrap direct-map area, Florian Wagner
Next by Date:  [Xen-community] Storage testing help, Leena M.
Previous by Thread:  Re: [Xen-users] Starting xend: grep: /proc/xen/capabilities: No such file or directory, kishore kumar
Next by Thread:  Re: [Xen-users] Starting xend: grep: /proc/xen/capabilities: No such file or directory, kishore kumar
Indexes:  [Date] [Thread] [Top] [All Lists]
 
   

Copyright , Citrix Systems Inc. All rights reserved. Legal and Privacy