Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Setting watchdog's action to 'dump', then start the guest, watchdog's action will be moved to 'pause' automatically.
Version-Release number of selected component:
libvirt-1.3.3-2.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1.Add watchdog device and set action to 'dump':
...
<watchdog model='i6300esb' action='dump'/>
...
2.Start the guest:
#virsh start rhel7.1
3.Check the active xml:
#virsh dumpxml rhel7.1 | grep -A5 watchdog
<watchdog model='i6300esb' action='pause'>
<alias name='watchdog0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
</watchdog>
...
4.Turn the watchdog on in the guest, after some seconds, the guest becomes paused status and no dump file in the auto dump path:
#echo 1 > /dev/watchdog
check the guest status after some seconds:
#virsh list
Id Name State
----------------------------------------------------
2 rhel7.1 paused
Actual results:
When start the guest, the watchdog's action moved from 'dump' to 'pause' automatically.
Expected results:
1.In step3, the watchdog's action should be still 'dump';
2.In step4, should generate dump file in auto dump path and guest still be running;
Additional info:
It works correctly with libvirt-1.2.17-13.el7.x86_64
This was already fixed upstream:
commit a91177c8f7b432e67d2e232650d7debbbfc694da
Author: Cole Robinson <crobinso>
Date: Wed Apr 13 11:20:19 2016 -0400
qemu: command: don't overwrite watchdog dump action
The watchdog cli refactoring in 4666b762 dropped the temporary variable
we use to convert to action=dump to action=pause for the qemu cli, and
stored the converted value in the domain structure. Our other watchdog
handling code then treated it as though the user requested action=pause,
which broke action=dump handling.
Revive the temporary variable to fix things.
v1.3.3-130-ga91177c
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.
https://rhn.redhat.com/errata/RHSA-2016-2577.html
Description of problem: Setting watchdog's action to 'dump', then start the guest, watchdog's action will be moved to 'pause' automatically. Version-Release number of selected component: libvirt-1.3.3-2.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1.Add watchdog device and set action to 'dump': ... <watchdog model='i6300esb' action='dump'/> ... 2.Start the guest: #virsh start rhel7.1 3.Check the active xml: #virsh dumpxml rhel7.1 | grep -A5 watchdog <watchdog model='i6300esb' action='pause'> <alias name='watchdog0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </watchdog> ... 4.Turn the watchdog on in the guest, after some seconds, the guest becomes paused status and no dump file in the auto dump path: #echo 1 > /dev/watchdog check the guest status after some seconds: #virsh list Id Name State ---------------------------------------------------- 2 rhel7.1 paused Actual results: When start the guest, the watchdog's action moved from 'dump' to 'pause' automatically. Expected results: 1.In step3, the watchdog's action should be still 'dump'; 2.In step4, should generate dump file in auto dump path and guest still be running; Additional info: It works correctly with libvirt-1.2.17-13.el7.x86_64