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:
An integer overflow in qemu's implementation of the i6300esb watchdog timer means that if the guest programs a sufficiently large timeout time (but still within the range the device is supposed to support), the watchdog will trigger immediately, potentially killing the guest.
Version-Release number of selected component (if applicable):
qemu-kvm-rhev-2.2.0-5.el7.ppc64
How reproducible:
100%, with correct configuraiton
Steps to Reproduce:
1. Create a qemu guest including the i6300esb watchdog device. For example the following qemu command line is suitable:
qemu-system-x86_64 \
-machine pc \
-enable-kvm \
-m 2048 \
-no-user-config \
-nodefaults \
-vga std \
-chardev stdio,id=charmonitor,mux=on,signal=off \
-mon chardev=charmonitor,id=monitor \
-rtc base=utc \
-boot strict=on \
-drive file=DISKIMAGE.qcow2,if=none,id=drive0,format=qcow2 \
-device virtio-blk-pci,drive=drive0,id=blk0,bootindex=1 \
-netdev user,id=net0 \
-device virtio-net-pci,netdev=net0 \
-device i6300esb,id=watchdog0 -watchdog-action pause
2. Install a Linux guest under this qemu
3. Log into the guest, unload the i6300esb driver:
# rmmod i6300esb
4. Reload the i6300esb driver with an altered heartbeat module parameter:
# modprobe i6300esb heartbeat=2046
5. Open the watchdog device, for example with:
# python
>>> open("/dev/watchdog")
Actual results:
As soon as the watchdog device is opened, the watchdog immediately triggers, pausing the guest (with the example qemu command line above).
Expected results:
Watchdog does not trigger for ~2046 seconds, as specified by the heartbeat parameter.
Additional info:
This bug probably affects qemu-kvm (not RHEV) and RHEL6 as well, though I haven't tested so far.
Tested this issue with qemu-kvm-rhev-2.3.0-2 both on x86_64 and ppc64le host.
The watchdog timer did not fire immediately, but not fire on time either.
Details:
# modprobe -r i6300esb; modprobe i6300esb heartbeat=2046
# dmesg | grep -i i6300
...
[ 35.981953] i6300esb: initialized (0xffffc900003ba000). heartbeat=2046 sec (nowayout=0)
# cat wd.py
import time
wd = open('/dev/watchdog', 'rw')
wd.close()
for i in range(1, 2049):
time.sleep(1)
print i
# python wd.py
1
2
...
257
258 <- watchdog fired (VM paused)
Comment 6 looks like a real bug, but a different and less serious one from this one.
I think we can still verify this, and file comment 6 as a new bug.
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/RHBA-2015-2546.html
Description of problem: An integer overflow in qemu's implementation of the i6300esb watchdog timer means that if the guest programs a sufficiently large timeout time (but still within the range the device is supposed to support), the watchdog will trigger immediately, potentially killing the guest. Version-Release number of selected component (if applicable): qemu-kvm-rhev-2.2.0-5.el7.ppc64 How reproducible: 100%, with correct configuraiton Steps to Reproduce: 1. Create a qemu guest including the i6300esb watchdog device. For example the following qemu command line is suitable: qemu-system-x86_64 \ -machine pc \ -enable-kvm \ -m 2048 \ -no-user-config \ -nodefaults \ -vga std \ -chardev stdio,id=charmonitor,mux=on,signal=off \ -mon chardev=charmonitor,id=monitor \ -rtc base=utc \ -boot strict=on \ -drive file=DISKIMAGE.qcow2,if=none,id=drive0,format=qcow2 \ -device virtio-blk-pci,drive=drive0,id=blk0,bootindex=1 \ -netdev user,id=net0 \ -device virtio-net-pci,netdev=net0 \ -device i6300esb,id=watchdog0 -watchdog-action pause 2. Install a Linux guest under this qemu 3. Log into the guest, unload the i6300esb driver: # rmmod i6300esb 4. Reload the i6300esb driver with an altered heartbeat module parameter: # modprobe i6300esb heartbeat=2046 5. Open the watchdog device, for example with: # python >>> open("/dev/watchdog") Actual results: As soon as the watchdog device is opened, the watchdog immediately triggers, pausing the guest (with the example qemu command line above). Expected results: Watchdog does not trigger for ~2046 seconds, as specified by the heartbeat parameter. Additional info: This bug probably affects qemu-kvm (not RHEV) and RHEL6 as well, though I haven't tested so far.