Bug 455764

Summary:	No Error Output When Xen Started on Unpatched Kernel
Product:	Red Hat Enterprise Linux 5	Reporter:	Drew Faubion <dfaubion.umd>
Component:	xen	Assignee:	Xen Maintainance List <xen-maint>
Status:	CLOSED NOTABUG	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	low	Docs Contact:
Priority:	low
Version:	5.4
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-07-22 09:24:58 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 Drew Faubion 2008-07-17 16:58:08 UTC

Description of problem:
Attempting to start Xen on unpatched kernel results in script exiting with no
error output.

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


How reproducible: Very


Steps to Reproduce:
1.Install xen from yum.  Do not reboot or boot to a non-patched kernel.  
2.Run /sbin/service xend start
3.The script will exit with no output whatsoever.
  
Actual results: None


Expected results: Error message


Additional info: Should be easy to fix.

Comment 1 Bill Burns 2008-07-21 18:22:14 UTC

By non-patched kernel, do you mean you are running the non-Xen kernel?

Comment 2 Daniel Berrangé 2008-07-22 09:24:58 UTC

This is intentional behaviour. We want people to be able to easily reboot
between Xen and non-Xen kernel without having to turn initscripts on/off to get
rid of failures. It is fairly standard behaviour for initscripts to silently
exit if their pre-requisites aren't present.