Bug 148486 - app-emulation/xen-tools: xend init script should test for xen enabled kernel
Bug#: 148486 Product:  Gentoo Linux Version: 2006.1 Platform: x86
OS/Version: Linux Status: RESOLVED Severity: enhancement Priority: P2
Resolution: FIXED Assigned To: aross@gentoo.org Reported By: mail@earthworm.de
Component: Ebuilds
URL: 
Summary: app-emulation/xen-tools: xend init script should test for xen enabled kernel
Keywords:  
Status Whiteboard: scheduled for -r4
Opened: 2006-09-21 03:48 0000
Description:   Opened: 2006-09-21 03:48 0000 
Hello everybody,

I added xend to my default runlevel. Now every time I boot my system with a
kernel that is not xen enabled I get really ugly output. Would be nice to have
the xend init script check if the kernel has Xen support.

------- Comment #1 From Christian Hesse 2006-09-21 03:49:41 0000 ------- 
Created an attachment (id=97622) [details]
patch to check if kernel is Xen enabled

------- Comment #2 From Robert S 2006-09-22 04:20:39 0000 ------- 
I fixed this by creating a new runlevel called "xen" which starts the xen and
xendomains daemons.  It also switches to the xorg-x11 opengl interface because
you can't install the nvidia driver with a xen kernel.  I choose the xen or
non-xen kernel using grub.  I think its better this way.

------- Comment #3 From Andrew Ross (RETIRED) 2006-09-22 08:01:25 0000 ------- 
While a Xen-specific runlevel is the preferred way of dealing with this,
there's no reason why we shouldn't make /etc/init.d/xend behave in a more
Gentoo-like way (ie. avoiding the python stack traces). The iptables init.d
script does a similar check for kernel-level support, which I'm taking as a
precedent.

------- Comment #4 From Andrew Ross (RETIRED) 2006-10-13 17:06:41 0000 ------- 
Fixed in app-emulation/xen-tools-3.0.2-r4, thanks.