Xen users - Jul 2009 - grep: /proc/xen/capabilities: No such file or directory

I just setup a new laptop with
- Xen-unstable (http://xenbits.xensource.com/xen-unstable.git), 
installed via "make xen", "make install-xen", "make
tools", "make
install-tools"
- dom0 kernel 2.6.30-rc6-tip (from 
git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git, changed to 
bleeding edge via "git checkout origin/xen-tip/next  b xen tip/next
"),
installed via "make menuconfig" (enabled PAE, Xen paravirtualized
guest
support, Xen dom0 support), "make" and "make install", then
built initrd
image
- Debian lenny using only stable packages

So when I boot into Xen with 2.6.30-rc6-tip, everything works fine but 
xend is not running. Trying to start it ("/etc/init.d/xend restart") 
throws an error "grep: /proc/xen/capabilities: No such file or 
directory". The directory "/proc/xen" is actually there, but
empty. I
had the same problems with installing Xen-3.4-testing only a few days ago.

What is the problem?

/Best regards
  Andreas/


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

Andreas Sommer schrieb:
> So when I boot into Xen with 2.6.30-rc6-tip, everything works fine but
> xend is not running. Trying to start it ("/etc/init.d/xend
restart")
> throws an error "grep: /proc/xen/capabilities: No such file or
> directory". The directory "/proc/xen" is actually there, but
empty. I
> had the same problems with installing Xen-3.4-testing only a few days ago.
> 
This worgs with all Dom0 kernel:
if ! grep -q "xen" /sys/hypervisor/type

Stefan Kuhne



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

It seems like many Xen source files still rely on the /proc/xen file 
system. Thus changing or removing that check in /etc/init.d/xend does 
not make a difference - xend won''t start because it apparently needs 
stuff from /proc/xen ("Could not obtain handle on privileged command 
interface (2 = No such file or directory)" and similar errors).

So, are the current Xen-unstable and the 2.6.30-rc6-tip kernel 
compatible (or yet usable) at all?

Stefan Kuhne wrote:
> Andreas Sommer schrieb:
>
>   
>> So when I boot into Xen with 2.6.30-rc6-tip, everything works fine but
>> xend is not running. Trying to start it ("/etc/init.d/xend
restart")
>> throws an error "grep: /proc/xen/capabilities: No such file or
>> directory". The directory "/proc/xen" is actually there,
but empty. I
>> had the same problems with installing Xen-3.4-testing only a few days
ago.
>>
>>     
> This worgs with all Dom0 kernel:
> if ! grep -q "xen" /sys/hypervisor/type
>
> Stefan Kuhne

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

Okay I found the solution :-)

The kernel must be configured to create the compatibility mount point 
/proc/xen. And the following line must be added to /etc/fstab:

xenfs /proc/xen xenfs defaults 0 0

Hope this might help somebody else...



Andreas Sommer wrote:
> It seems like many Xen source files still rely on the /proc/xen file 
> system. Thus changing or removing that check in /etc/init.d/xend does 
> not make a difference - xend won''t start because it apparently
needs
> stuff from /proc/xen ("Could not obtain handle on privileged command 
> interface (2 = No such file or directory)" and similar errors).
>
> So, are the current Xen-unstable and the 2.6.30-rc6-tip kernel 
> compatible (or yet usable) at all?
>
> Stefan Kuhne wrote:
>> Andreas Sommer schrieb:
>>
>>   
>>> So when I boot into Xen with 2.6.30-rc6-tip, everything works fine
but
>>> xend is not running. Trying to start it ("/etc/init.d/xend
restart")
>>> throws an error "grep: /proc/xen/capabilities: No such file or
>>> directory". The directory "/proc/xen" is actually
there, but empty. I
>>> had the same problems with installing Xen-3.4-testing only a few
days ago.
>>>
>>>     
>> This worgs with all Dom0 kernel:
>> if ! grep -q "xen" /sys/hypervisor/type
>>
>> Stefan Kuhne
> ------------------------------------------------------------------------
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users

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

Hey Andreas!

Could you please elaborate on how to "to create the compatibility mount
point 
/proc/xen". I added the line of code you mentioned to /etc/fstab and the
problem still persists.

The current view of my system mounts are :
root@pbhat-acis:/home/pbhat# df -ah
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda5             141G  8.9G  125G   7% /
proc                     0     0     0   -  /proc
none                     0     0     0   -  /sys
none                     0     0     0   -  /sys/fs/fuse/connections
none                     0     0     0   -  /sys/kernel/debug
none                     0     0     0   -  /sys/kernel/security
udev                  1.9G  272K  1.9G   1% /dev
none                     0     0     0   -  /dev/pts
none                  1.9G  1.2M  1.9G   1% /dev/shm
none                  1.9G   92K  1.9G   1% /var/run
none                  1.9G     0  1.9G   0% /var/lock
none                  1.9G     0  1.9G   0% /lib/init/rw
binfmt_misc              0     0     0   -  /proc/sys/fs/binfmt_misc
gvfs-fuse-daemon      0.0K  0.0K  0.0K   -  /home/pbhat/.gvfs


Thanks !
Pr

Andreas Sommer wrote:
> 
> Okay I found the solution :-)
> 
> The kernel must be configured to create the compatibility mount point 
> /proc/xen. And the following line must be added to /etc/fstab:
> 
> xenfs /proc/xen xenfs defaults 0 0
> 
> Hope this might help somebody else...
> 
> 
> 
> Andreas Sommer wrote:
>> It seems like many Xen source files still rely on the /proc/xen file 
>> system. Thus changing or removing that check in /etc/init.d/xend does 
>> not make a difference - xend won''t start because it apparently
needs
>> stuff from /proc/xen ("Could not obtain handle on privileged
command
>> interface (2 = No such file or directory)" and similar errors).
>>
>> So, are the current Xen-unstable and the 2.6.30-rc6-tip kernel 
>> compatible (or yet usable) at all?
>>
>> Stefan Kuhne wrote:
>>> Andreas Sommer schrieb:
>>>
>>>   
>>>> So when I boot into Xen with 2.6.30-rc6-tip, everything works
fine but
>>>> xend is not running. Trying to start it ("/etc/init.d/xend
restart")
>>>> throws an error "grep: /proc/xen/capabilities: No such
file or
>>>> directory". The directory "/proc/xen" is
actually there, but empty. I
>>>> had the same problems with installing Xen-3.4-testing only a
few days
>>>> ago.
>>>>
>>>>     
>>> This worgs with all Dom0 kernel:
>>> if ! grep -q "xen" /sys/hypervisor/type
>>>
>>> Stefan Kuhne
>>
------------------------------------------------------------------------
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xensource.com
>> http://lists.xensource.com/xen-users
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
> 
-- 
View this message in context:
http://old.nabble.com/grep%3A--proc-xen-capabilities%3A-No-such-file-or-directory-tp24550003p26596609.html
Sent from the Xen - User mailing list archive at Nabble.com.


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