Red Hat Bugzilla – Bug 212444
fence_xvmd reboot does not work
Last modified: 2009-04-16 18:36:20 EDT
Description of problem:
The 'reboot' operation for xen fencing does not work. This has two causes:
(a) libvirt does not have a guaranteed immediate synchronous reboot option. The
only "reboot" operation it has is worthless, because it is equivalent to a
soft-shutdown / init 6 / ACPI soft-powerdown event. Supposedly, this could be
implemented with the xen 3.0.3 APIs, but it does not appear to be in libvirt, at
least not according to the documentation here:
(b) xend unlinks the temporary images set up by pygrub, making the
virDomainGetXMLDesc() information about the kernel and initrd.
A solution to (b) above is to kill the entire <os> tag. Here's an example XML
desc from virDomainGetXMLDesc:
<domain type='xen' id='10'>
<cmdline>ro root=/dev/VolGroup00/LogVol00 console=xvc0 rhgb quiet</cmdline>
<disk type='file' device='disk'>
<driver name='tap' type='aio'/>
All we need to do is blank-out the <os> tag and all children, and it will fall
back to pygrub.
Created attachment 139524 [details]
makes reboot work
GA Blocker request - Xen hasn't been stable enough during this cycle to address
some of the interesting scenarios, so wouldn't hold up beta2 for this support.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux release. Product Management has requested further review
of this request by Red Hat Engineering. This request is not yet committed for
inclusion in release.
Created attachment 139532 [details]
Use 'reboot' as default instead of 'off' since reboot works; requires above patch
Fails initial testing with the updating library so marking it FAILS_QA
Created attachment 142630 [details]
handle 0.1.9 status from libvirt (VIR_DOMAIN_SHUTOFF) as a successful operation
incremental; requires previous 2 patches
Lon: This should have been in modified for weeks.
A package has been built which should help the problem described in
this bug report. This report is therefore being closed with a resolution
of CURRENTRELEASE. You may reopen this bug report if the solution does
not work for you.
Moving all RHCS ver 5 bugs to RHEL 5 so we can remove RHCS v5 which never existed.