Xen cannot work when xenstored's tdb is corrupt. When that happens somehow (e.g. bug 215994), even reboot doesn't recover from it. It could: there is no state in tdb that needs to be persisted across reboots.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
Fix is upstream, cset 16323:468a30d74bd6.
Fix built for QA $ brew latest-pkg dist-5E-qu-candidate xen Build Tag Built by ---------------------------------------- -------------------- ---------------- xen-3.0.3-43.el5 dist-5E-qu-candidate berrange * Thu Jan 3 2008 Daniel P. Berrange <berrange> - 3.0.3-43.el5 - Delete xenstored TDB upon startup (rhbz #356461)
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2008-0305.html