Emily J. Ratliff <firstname.lastname@example.org> -
1. Feature Overview:
Feature Id: 
a. Name of Feature: Backport Intel watchdog emulation
b. Feature Description
Backport Intel watchdog emulation in upstream qemu to 5.4 kvm
2. Feature Details:
Arch Specificity: Both
Delivery Mechanism: Backport
Request Type: Driver - Feature from Upstream
d. Upstream Acceptance: Accepted
Sponsor Priority 2
f. Severity: Medium
IBM Confidential: no
Code Contribution: 3rd party code
g. Component Version Target: qemu 0.11
3. Business Case
Increase the RAS capabilities of KVM virtualization solutions by allowing guest OSes to use an
emulated watchdog that can take action when the GuestOS encounters a critical error.
4. Primary contact at Red Hat:
5. Primary contacts at Partner:
Project Management Contact:
Stephanie Glass, email@example.com, 512-838-9284
Ryan Harper, firstname.lastname@example.org
Warren Grunbok II, email@example.com
Can you please answer the https://bugzilla.redhat.com/show_bug.cgi?id=518284#c2 question?
We do not see Comment 2...
What is the target release?
Flag set = 6.0.0?
Target release = 5.5
In the description =
"Backport Intel watchdog emulation in upstream qemu to 5.4 kvm"
btw: isn't this device fully upstream in qemu 0.12? If that's the case, then it will just work out of the box.
Dor is correct that it's upstream in qemu for a very
It's also now in libvirt 0.7.3, so you can add watchdogs
to your guests by doing:
<watchdog model='i6300esb' />
I'm not sure if IBM require the libvirt functionality
as well. We may need to backport this if so.
Red Hat Enterprise Linux 6.0 is now available and should resolve
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.