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.
Created attachment 1137723[details]
seabios log, both win2008 sp2 and r2 attach
Description of problem:
Seabios show terminate and cannot boot to win2008 r2 os after many system_reset
Version-Release number of selected component (if applicable):
qemu-kvm-rhev-0.12.1.2-2.490.el6
seabios-0.6.1.2-30.el6
How reproducible:
Steps to Reproduce:
1. Boot guest with:
/usr/libexec/qemu-kvm \
-name 'virt-tests-vm1' \
-machine rhel6.6.0 \
-nodefaults \
-vga std \
-device AC97,bus=pci.0,addr=03 \
-chardev socket,id=qmp_id_qmpmonitor1,path=/tmp/monitor-qmpmonitor1-20160307-181400-9qrGGc2N,server,nowait \
-mon chardev=qmp_id_qmpmonitor1,mode=control \
-chardev socket,id=qmp_id_catch_monitor,path=/tmp/monitor-catch_monitor-20160307-181400-9qrGGc2N,server,nowait \
-mon chardev=qmp_id_catch_monitor,mode=control \
-device pvpanic,ioport=0x505,id=idhGmfit \
-chardev socket,id=serial_id_serial0,path=/tmp/serial-serial0-20160307-181400-9qrGGc2N,server,nowait \
-device isa-serial,chardev=serial_id_serial0 \
-chardev socket,id=seabioslog_id_20160307-181400-9qrGGc2N,path=/tmp/seabios-20160307-181400-9qrGGc2N,server,nowait \
-device isa-debugcon,chardev=seabioslog_id_20160307-181400-9qrGGc2N,iobase=0x402 \
-device ich9-usb-ehci1,id=usb1,addr=1d.7,multifunction=on,bus=pci.0 \
-device ich9-usb-uhci1,id=usb1.0,multifunction=on,masterbus=usb1.0,addr=1d.0,firstport=0,bus=pci.0 \
-device ich9-usb-uhci2,id=usb1.1,multifunction=on,masterbus=usb1.0,addr=1d.2,firstport=2,bus=pci.0 \
-device ich9-usb-uhci3,id=usb1.2,multifunction=on,masterbus=usb1.0,addr=1d.4,firstport=4,bus=pci.0 \
-device virtio-scsi-pci,id=virtio_scsi_pci0,bus=pci.0,addr=04 \
-drive id=drive_image1,if=none,cache=none,snapshot=off,aio=native,format=qcow2,file=/home/autotest/client/tests/virt/shared/data/images/win2008-r2-64-virtio-scsi.qcow2 \
-device scsi-hd,id=image1,drive=drive_image1 \
-m 16384 \
-smp 8,maxcpus=8,cores=4,threads=1,sockets=2 \
-cpu 'SandyBridge',hv_relaxed,hv_relaxed \
-drive id=drive_cd1,if=none,snapshot=off,aio=native,media=cdrom,file=/home/autotest/client/tests/virt/shared/data/isos/windows/winutils.iso \
-device scsi-cd,id=cd1,drive=drive_cd1 \
-device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1 \
-vnc :0 \
-rtc base=localtime,clock=host,driftfix=slew \
-boot order=cdn,once=c,menu=off,strict=off \
-enable-kvm
2. During guest boot, do system_reset in qmp every 10 seconds, and do 20 times
3.
Actual results:
Seabios show terminate and cannot boot to win2008 r2. Seabios log show in the end:
2016-03-07 18:19:08: Booting from 0000:7c00
2016-03-07 18:19:14: In resume (status=10)
2016-03-07 18:27:24: (Process terminated with status 0)
Expected results:
Boot to win2008 r2 normally.
Additional info:
This issue is reproduced by automation test and failed rate is 4/5.Only win2008 r2 has this problem, no such issue with win2008 sp2.
windows 2008 sp2 version:
en_windows_server_2008_datacenter_enterprise_standard_sp2_x86_dvd_342333.iso
windows 2008 r2 version:
en_windows_server_2008_r2_standard_enterprise_datacenter_and_web_with_sp1_x64_dvd_617601.iso
Hi,
> 2016-03-07 18:19:14: In resume (status=10)
Hmm, strange. Appearently seabios thinks it is resuming from S3,
so it doesn't take the normal boot path bot jumps to whatever address
it thinks is the resume vector.
/me wonders what win2008r2 is doing there ...
What happens if you system_reset again in hanging state?
Hi,
(In reply to Gerd Hoffmann from comment #3)
> Hi,
>
> > 2016-03-07 18:19:14: In resume (status=10)
>
> Hmm, strange. Appearently seabios thinks it is resuming from S3,
> so it doesn't take the normal boot path bot jumps to whatever address
> it thinks is the resume vector.
>
> /me wonders what win2008r2 is doing there ...
>
> What happens if you system_reset again in hanging state?
This issue is reproduced by automation test, test case name is system_reset_bootable. Test case sends system_reset to qemu every 10 seconds and repeat 10 times of the action. From the boot failed log I attached, when 1st "in resume" happen, subsequent system_reset will incur "in resume" too.
Hmm, no success reproducing so far.
With reset every 10 seconds you are probably resetting while windows waits in the the boot menu (where windows asks whenever you want do a normal boot or safe mode)? Except for the first reset of course ...
I assume this is a fresh install?
Does it reproduce on RHEL-7?
Created attachment 1145830[details]
screenshot of time before the 10 second
(In reply to Gerd Hoffmann from comment #6)
> Hmm, no success reproducing so far.
>
> With reset every 10 seconds you are probably resetting while windows waits
> in the the boot menu (where windows asks whenever you want do a normal boot
> or safe mode)? Except for the first reset of course ...
Observe from remote-viewer, exclude first reset, remote-viewer represent a boot progress bar before the 10 second in normal case. No prompt for boot mode selection. Upload a screenshot of time before the 10 second. When issue happens, remote-viewer stays representing a whole blank window.
>
> I assume this is a fresh install?
>
Case test stress system_reset with a fresh installed Windows 2008 r2 guest.
> Does it reproduce on RHEL-7?
Repeat 10 times test,not reproduce this issue on rhel 7.2 with kernel 3.10.0-373.el7.x86_64 and qemu qemu-kvm-rhev-2.3.0-31.el7_2.11.x86_64 and seabios seabios-1.9.1-1.el7.x86_64.
Created attachment 1137723 [details] seabios log, both win2008 sp2 and r2 attach Description of problem: Seabios show terminate and cannot boot to win2008 r2 os after many system_reset Version-Release number of selected component (if applicable): qemu-kvm-rhev-0.12.1.2-2.490.el6 seabios-0.6.1.2-30.el6 How reproducible: Steps to Reproduce: 1. Boot guest with: /usr/libexec/qemu-kvm \ -name 'virt-tests-vm1' \ -machine rhel6.6.0 \ -nodefaults \ -vga std \ -device AC97,bus=pci.0,addr=03 \ -chardev socket,id=qmp_id_qmpmonitor1,path=/tmp/monitor-qmpmonitor1-20160307-181400-9qrGGc2N,server,nowait \ -mon chardev=qmp_id_qmpmonitor1,mode=control \ -chardev socket,id=qmp_id_catch_monitor,path=/tmp/monitor-catch_monitor-20160307-181400-9qrGGc2N,server,nowait \ -mon chardev=qmp_id_catch_monitor,mode=control \ -device pvpanic,ioport=0x505,id=idhGmfit \ -chardev socket,id=serial_id_serial0,path=/tmp/serial-serial0-20160307-181400-9qrGGc2N,server,nowait \ -device isa-serial,chardev=serial_id_serial0 \ -chardev socket,id=seabioslog_id_20160307-181400-9qrGGc2N,path=/tmp/seabios-20160307-181400-9qrGGc2N,server,nowait \ -device isa-debugcon,chardev=seabioslog_id_20160307-181400-9qrGGc2N,iobase=0x402 \ -device ich9-usb-ehci1,id=usb1,addr=1d.7,multifunction=on,bus=pci.0 \ -device ich9-usb-uhci1,id=usb1.0,multifunction=on,masterbus=usb1.0,addr=1d.0,firstport=0,bus=pci.0 \ -device ich9-usb-uhci2,id=usb1.1,multifunction=on,masterbus=usb1.0,addr=1d.2,firstport=2,bus=pci.0 \ -device ich9-usb-uhci3,id=usb1.2,multifunction=on,masterbus=usb1.0,addr=1d.4,firstport=4,bus=pci.0 \ -device virtio-scsi-pci,id=virtio_scsi_pci0,bus=pci.0,addr=04 \ -drive id=drive_image1,if=none,cache=none,snapshot=off,aio=native,format=qcow2,file=/home/autotest/client/tests/virt/shared/data/images/win2008-r2-64-virtio-scsi.qcow2 \ -device scsi-hd,id=image1,drive=drive_image1 \ -m 16384 \ -smp 8,maxcpus=8,cores=4,threads=1,sockets=2 \ -cpu 'SandyBridge',hv_relaxed,hv_relaxed \ -drive id=drive_cd1,if=none,snapshot=off,aio=native,media=cdrom,file=/home/autotest/client/tests/virt/shared/data/isos/windows/winutils.iso \ -device scsi-cd,id=cd1,drive=drive_cd1 \ -device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1 \ -vnc :0 \ -rtc base=localtime,clock=host,driftfix=slew \ -boot order=cdn,once=c,menu=off,strict=off \ -enable-kvm 2. During guest boot, do system_reset in qmp every 10 seconds, and do 20 times 3. Actual results: Seabios show terminate and cannot boot to win2008 r2. Seabios log show in the end: 2016-03-07 18:19:08: Booting from 0000:7c00 2016-03-07 18:19:14: In resume (status=10) 2016-03-07 18:27:24: (Process terminated with status 0) Expected results: Boot to win2008 r2 normally. Additional info: This issue is reproduced by automation test and failed rate is 4/5.Only win2008 r2 has this problem, no such issue with win2008 sp2. windows 2008 sp2 version: en_windows_server_2008_datacenter_enterprise_standard_sp2_x86_dvd_342333.iso windows 2008 r2 version: en_windows_server_2008_r2_standard_enterprise_datacenter_and_web_with_sp1_x64_dvd_617601.iso