Xen project Mailing List

[Xen-users] xen 4.1.1 (src) requires expert on debian

To: "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>

Date: Wed, 27 Jul 2011 15:54:46 -0700 (PDT)

Delivery-date: Wed, 27 Jul 2011 15:55:51 -0700

Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=Z2U1sMWsTyox0d8TTqbEjTmOuIl/uY5bBrhpe4IjdfEd92Mnt2HpfZH2rlAy4TXMpzdcOR1DhPz4e/J9v8tKoTdh2Fs3TBA7TV7nM51DrkYQcfn8/h9S81bgVgbb3vYguczMujm34eX+lrsVVihN9sZ4TjtMdb7KVlvFkXY+29c=;

List-id: Xen user discussion <xen-users.lists.xensource.com>

List,

my subject is a bit of exageration. In the ##xen channel on freenode.net far too often when the Debian 6+ user tries to install xen 4.1.1 from source they never get the services to start properly.

When you look at the headers of the init scripts, they are still setup as Redhat template.

All xen services must be up by Runlevel 2, not 3.

------------- init.d/xend -------------

### BEGIN INIT INFO
# Provides:          xend
# Required-Start:    $syslog $remote_fs xenstored
# Should-Start:
# Required-Stop:     $syslog $remote_fs xenstored
# Should-Stop:
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: Start/stop xend
# Description:       Starts and stops the Xen control daemon.
### END INIT INFO
------------------ snip --------------

only 2 lines were changed. This header is parsed by the update-rc.d script.

Another approach is to manually create symlinks in /etc/rc1.d and /etc/rc2.d

(for debian)

/etc/rc1.d

S02xencommons

/etc/rc2.d

S02xend

S03xendomains

(for ubuntu)

/etc/rc2.d

S20xencommons

S21xend

S22xendomains

Its tragic that debian users (which should be elite linux level) would give up using 4.1.1 because of a few bad symlinks.

Mark

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