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:
windows 2008 R2 guest BSOD with '-no-kvm'

Version-Release number of selected component (if applicable):
qemu-kvm-rhev-1.5.3-18.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1. boot windows 2008 R2 guest with '-no-kvm'
# /usr/libexec/qemu-kvm -nodefaults -M pc -m 4G -cpu Opteron_G3 -smp 4,cores=2,threads=2,sockets=1 -boot menu=on -monitor stdio -rtc base=localtime,clock=host,driftfix=slew -qmp tcp:0:5555,server,nowait -vga qxl -drive file=/home/win2008r2.qcow2_v3,format=qcow2,id=guest-img,if=none,werror=stop,rerror=stop -device ide-hd,drive=guest-img,id=os-disk -spice disable-ticketing,port=5931 -no-kvm

Actual results:
BSOD

Expected results:
guest can boot success

Additional info:

Created attachment 822785 [details]
screen shot

http://www.geoffchappell.com/studies/windows/km/bugchecks/5d.htm

Upstream reports:
https://bugs.launchpad.net/qemu/+bug/921208
http://lists.nongnu.org/archive/html/qemu-devel/2013-11/msg01063.html

Paolo,
What is your call?

Not a bug.

Paolo, How comes?
It should be fixable.
Are you saying that it is not needed? Could be, but it doesn't look good.
Can it happen to an innocent Libvirt user?

More precisely, not a bug as far as we are concerned.  We do not support TCG except for the very specific case of running libguestfs, I think?

It is fixable, but I have no idea whether it is easy or hard because I have no experience.

It can happen if you use 'qemu' instead of 'kvm' as the virtualization technology.  Perhaps we should add a "taint" flag to libvirt for domains that are not running under KVM and have qemu-kvm in the emulator name.