Bug 461784

Summary:	xend initscript needs to check for existance of /proc/xen/capabilities
Product:	Red Hat Enterprise Linux 5	Reporter:	Jay Turner <jturner>
Component:	xen	Assignee:	Xen Maintainance List <xen-maint>
Status:	CLOSED DUPLICATE	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	low	Docs Contact:
Priority:	low
Version:	5.3	CC:	clalance, srevivo
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-09-10 15:44:24 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jay Turner 2008-09-10 15:35:35 UTC

Description of problem:
I noticed today that with xen-3.0.3-71.el5, we're enabling the xend service by default, but if you are booting up a system with a non-xen kernel, you'll get the following when the xend service attempts to start:

grep: /proc/xen/capabilities: No such file or directory

The initscript should probably check for the existence of the file before attempting to grep through it.

Version-Release number of selected component (if applicable):
3.0.3-71.el5

How reproducible:
Always

Steps to Reproduce:
1. Attempt to start the xend service under a non-xen kernel

Comment 1 Chris Lalancette 2008-09-10 15:44:24 UTC

This is another instance of the problems that are affecting bz 461658, although the symptoms are very different.  Basically, we are now showing a /proc/xen directory on bare-metal where we shouldn't.  This is a kernel bug.  I'll close this as a dup.

Chris Lalancette

*** This bug has been marked as a duplicate of bug 461658 ***