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.
Bug 986223 - win2008r2 guest BSOD after repeadly "system_powerdown" while booting guest
Summary: win2008r2 guest BSOD after repeadly "system_powerdown" while booting guest
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm
Version: 7.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Yvugenfi@redhat.com
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 986252 1047413
TreeView+ depends on / blocked
 
Reported: 2013-07-19 09:22 UTC by langfang
Modified: 2014-01-14 14:55 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 986252 1047413 (view as bug list)
Environment:
Last Closed: 2014-01-14 14:55:54 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
BSOD (11.77 KB, image/png)
2013-07-19 09:27 UTC, langfang
no flags Details

Description langfang 2013-07-19 09:22:41 UTC
Description of problem:

win2008r2 guest BSOD after repeadly "system_powerdown" while booting guest 

Version-Release number of selected component (if applicable):

Host:
# uname -r 
2.6.32-398.el6.x86_64
# rpm -q qemu-kvm
qemu-kvm-0.12.1.2-2.378.el6.x86_64

Guest:
win2008r2-64

How reproducible:

90%
Steps to Reproduce:
1.Boot guest
 /usr/libexec/qemu-kvm -M rhel6.5.0 -cpu Opteron_G3 -m 32G -smp 16,sockets=2,cores=8,threads=1 -enable-kvm -usb  -name win2008r2-64 -uuid `uuidgen` -rtc base=localtime,clock=host,driftfix=slew  -boot menu=on -drive file=/root/win2008r2-64-virtio.qcow2,if=none,id=drive-ide0-1-0,format=qcow2 -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=1 -vnc :11 -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 -serial unix:/tmp/ttyS0,server,nowait -qmp tcp:0:4445,server,nowait -monitor unix:/tmp/monitor-unix,nowait,server -monitor stdio

2.Repeadly "system_powerdown" while booting guest 
(qemu)system_powerdown
(qemu)system_powerdown
(qemu)system_powerdown
....
...
....
Actual results:

BSOD--->see attachment 

Expected results:

guest work well ,not hit BSOD

Additional info:
1)Tried rhel6.4 guest not hit the problem
2)Tried win7 guest ,hit same problem

Comment 1 langfang 2013-07-19 09:27:22 UTC
Created attachment 775709 [details]
BSOD

Comment 3 langfang 2013-07-19 09:52:19 UTC
Seabios versiopn:

# rpm -q seabios
seabios-0.6.1.2-28.el6.x86_64

Addtional info: no dump file

Comment 5 langfang 2013-07-30 02:22:43 UTC
  Test this bug on physical machine, and keeping hitting the physical power button during boot. Not hit BSOD.


thanks

Comment 7 Yvugenfi@redhat.com 2014-01-14 14:55:54 UTC
Looks like a crash in MS system service which is dependent on other service that either was not started or was already shutdown due to shutdown event.


Note You need to log in before you can comment on or make changes to this bug.