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:
The guest will hang while doing iozone for longevity testing on win2k8-64 guest with virtio-win drivers installed
Version-Release number of selected component (if applicable):
kernel-2.6.32-502.el6.x86_64
qemu-kvm-rhev-tools-0.12.1.2-2.445.el6.x86_64
qemu-kvm-rhev-0.12.1.2-2.445.el6.x86_64
qemu-kvm-rhev-debuginfo-0.12.1.2-2.445.el6.x86_64
seabios-0.6.1.2-28.el6.x86_64
spice-server-0.12.4-9.el6.x86_64
/usr/share/virtio-win/virtio-win-1.7.2.iso
rhev-guest-tools-iso-3.5-2
How reproducible:
try one time and reproduce one time
Steps to Reproduce:
1.boot up guest with the following
/usr/libexec/qemu-kvm -drive file=en_windows_server_2008_datacenter_enterprise_standard_sp2_x64_dvd_342336.iso,if=none,cache=unsafe,media=cdrom,format=raw,id=drive-ide0-0-0 -device ide-drive,id=ide0-0-0,drive=drive-ide0-0-0,bus=ide.0,unit=0,bootindex=1 -drive file=/usr/share/virtio-win/virtio-win-1.7.2.iso,if=none,cache=none,media=cdrom,format=raw,id=drive-ide0-0-2 -device ide-drive,id=ide0-0-2,drive=drive-ide0-0-2,bus=ide.1,unit=0 -drive file=/usr/share/virtio-win/virtio-win-1.7.2_x86.vfd,if=none,id=drive-fdc0-0-0,format=raw,cache=none -global isa-fdc.driveA=drive-fdc0-0-0 -drive file=win2k8-64.raw,if=none,cache=none,media=disk,format=raw,id=drive-ide0-0-1 -device virtio-blk-pci,id=ide1,drive=drive-ide0-0-1 -monitor stdio -vnc :4 -vga cirrus -usb -device usb-tablet,id=tablet1 -boot menu=on -chardev file,path=/root/console.log,id=serial1 -device isa-serial,chardev=serial1,id=s1 -cpu Penryn -smp 2 -m 2G -enable-kvm -device virtio-balloon-pci,id=balloon0 -device virtio-rng-pci,id=rng0 -drive file=test2864.raw,if=none,cache=none,media=disk,format=raw,id=drive-ide0-0-3 -device virtio-scsi-pci,id=scsi0 -device scsi-hd,bus=scsi0.0,drive=drive-ide0-0-3 -device virtio-serial-pci,id=virtio-serial0 -chardev socket,path=/tmp/tt2864,server,nowait,id=channel0 -chardev socket,id=charchannel0,path=com.redhat.rhevm.vdsm,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.rhevm.vdsm -chardev socket,id=charchannel1,path=org.qemu.guest_agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=org.qemu.guest_agent.0 -chardev spicevmc,id=charchannel2,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=3,chardev=charchannel2,id=channel2,name=com.redhat.spice.0 -netdev tap,id=hostnet0,script=/etc/qemu-ifup -device virtio-net-pci,netdev=hostnet0,id=net0,mac=54:35:05:60:e3:f1,bus=pci.0 -name win2k8-64-guest
2.install iozone within guest for almost two weeks
for /l %k in (1,1,10000000000000000000000000000000000000000000000) do c:\iozone\iozone.exe -az -b c:\aaaa -g 4g -y 32k -i 0 -i 1 done
3.
Actual results:
The guest hang please have a look and user could not login
Expected results:
User could login in
Additional info:
Generate DUMP file via NMI