[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] kernel-ml + recent xen on el6: xenbus_dev_shutdown errors solved


  • To: "xen-users@xxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxx>
  • From: Mark Pryor <tlviewer@xxxxxxxxx>
  • Date: Mon, 15 Oct 2012 15:39:29 -0700 (PDT)
  • Delivery-date: Mon, 15 Oct 2012 22:41:33 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=CcZIM21E4n4iVBzzA5UsiZAv38E2wXRODp5SeAYG+THVf2fxnJigbbhR1iwl+sHyST81btqL+olq3x+ga+mZhN9NiW1FXM7kc0plecvm4qgx3jQel6kUZks5XZ6jE9mr0gsFEDgbXMm3+WcPQm388lWUsYX4IsfgptqIsFJkh5I=;
  • List-id: Xen user discussion <xen-users.lists.xen.org>

List,

Install a headless or minimal Centos 6 without kernel or kernel-firmware.
Setup the elrepo-kernel repo and use package kernel-ml and kernel-ml-firmware.

For xen, use CRCau or Mayoung repo as long as the packages follow the FC17 
breakdown:
sudo rpm -qa | grep xen
xen-licenses-4.1.3-4.el6.x86_64
xen-doc-4.1.3-4.el6.x86_64
xen-libs-4.1.3-4.el6.x86_64
xen-hypervisor-4.1.3-4.el6.x86_64
xen-runtime-4.1.3-4.el6.x86_64
xen-4.1.3-4.el6.x86_64



We will use only 3 of the xen services, but verify the sequence/runlevels first.

for i in xencommons xenconsoled xenstored xend xendomains; do
chkconfig --del $i

done

check the sequence numbers and runlevels and edit the init scripts in 
/etc/init.d if necessary. The meta
data is set in the header of the init script:

--------------- snip startup and kill sequence numbers ------------

sudo ls  /etc/rc6.d/ | grep xen
K00xencommons
K01xendomains
K02xend
[tlviewer@c6dom0 ~]$ sudo ls  /etc/rc3.d/ | grep xen
S96xencommons
S98xend
S99xendomains
------------------------------- snip ---------------------

------------------ chkconfig runlevels ---------------

xencommons      0:off   1:off   2:on    3:on    4:on    5:on    6:off
xend            0:off   1:off   2:off   3:on    4:on    5:on    6:off
xendomains      0:off   1:off   2:off   3:on    4:on    5:on    6:off
------------------ snip -------------------------

then
for i in xencommons xend xendomains; do
chkconfig --add $i
done

You will get xenbus_dev_shutdown errors unless you populate with at least one 
domU

/etc/xen/auto

The reason for the error is no lockfile is written to 

/var/lock/subsys/

So if you test be shell commands only, you get these errors on shutdown.


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.