Description of problem: Xendomains failed to start when there is no guest image in /var/lib/xen/save for restore and no guest configure file in /etc/xen/auto. In fact, according to /tools/examples/init.d/xendomains, nothing will do in this condition. I think this may be not graceful enough, may mislead our users. Version-Release number of selected component (if applicable): xen-3.0.3-129.el5 How reproducible: 100% Steps to Reproduce: 1. shutdown all the guest 2. empty /var/lib/xen/save 3. empty /etc/xen/auto 4. $ /etc/inti.d/xendomains restart 5. $ /etc/inti.d/xendomains status Actual results: On step 5: Checking for xendomains:[unused] [FAILED] Expected results: On step 5: Checking for xendomains:[running] [ OK ]
Verified with xen-3.0.3-135.el5. The output of 'service xendomains status' has been improved, no 'FAILED' message display when there is nothing to be done with xendomains. [root@localhost ~]# rpm -q xen xen-3.0.3-135.el5 [root@localhost ~]# /etc/init.d/xendomains restart Shutting down Xen domains:[root@localhost ~]# /etc/init.d/xendomains status xendomains is stopped [root@localhost ~]# touch /var/lock/subsys/xendomains [root@localhost ~]# /etc/init.d/xendomains status Checking for xendomains:[running] [ OK ]
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2012-0160.html