WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-bugs

[Xen-bugs] [Bug 1760] New: xendomains stop is not called on dom0 reboot

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1760] New: xendomains stop is not called on dom0 reboot on CentOS
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Thu, 14 Apr 2011 09:17:45 -0700
Delivery-date: Thu, 14 Apr 2011 09:17:56 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1760

           Summary: xendomains stop is not called on dom0 reboot on CentOS
           Product: Xen
           Version: 3.0.3
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Unspecified
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: bernd@xxxxxxxxxx


/etc/init.d/xendomains is not called when switching to runlevel 6 for certain
configurations. It should be called with argument "stop". When calling the
script manually with that argument, it works as expected. 

Reason: The SysV Init mechanism on RedHat Linux executes the /etc/rc6.d/K*
scripts only if a corresponding lockfile is found in /var/lock/subsys.
The start() function in /etc/init.d/xendomains only creates that file under
certain configurations, but not in all cases.

How to reproduce:
Set up xendomains without any domains in /etc/xen/auto and the following
settings in /etc/sysconfig/xendomains:
XENDOMAINS_MIGRATE=""
XENDOMAINS_SAVE=""
XENDOMAINS_SHUTDOWN="--halt --wait"
XENDOMAINS_AUTO_ONLY=false

Manually start a domU. Reboot dom0. 

Expected behavior: xendomains should shutdown domU.
Experienced behavior: xendomains is not called at all, because the lock file is
missing. 

Environment:
CentOs 5.5
xen.x86_64                        3.0.3-120.el5_6.1
xen-libs.x86_64                   3.0.3-120.el5_6.1


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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

<Prev in Thread] Current Thread [Next in Thread>