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:
Running virtio serial "Common Scenario Stress With IO", the win2k8-32 image corrupted after 3 times attempt. Other guests are ok.
Every times I start to run, I copy a fresh backup win2k8-32-sp2 image with MS system update. But all failed. I can not get any log except the screenshot. Guest can not boot up again even though I boot it without the serial device.
Anyway, I will re-install a win2k8-32 guest and have a try.
Version-Release number of selected component (if applicable):
virtio-win-prewhql-0.1-6
kernel-2.6.32-120.el6.x86_64
qemu-kvm-0.12.1.2-2.148.el6.x86_64
How reproducible:
3/3
Steps to Reproduce:
1.Prepare whql test environment.
2.Run win2k8-32 serial whql testing "Common Scenario Stress With IO" job.
Cli:
/usr/libexec/qemu-kvm -m 6G -smp 4 -cpu cpu64-rhel6,+x2apic -usbdevice tablet -drive file=win2k8-32-serial.raw,format=raw,if=none,id=drive-ide0-0-0,werror=stop,rerror=stop,cache=none -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -netdev tap,id=hostnet0,script=/etc/qemu-ifup1 -device e1000,netdev=hostnet0,mac=00:10:20:3d:39:1c,bus=pci.0,addr=0x4,id=net0 -boot c -uuid 631bf1d8-2f02-4bb6-9f38-8076adc28620 -rtc-td-hack -no-kvm-pit-reinjection -monitor stdio -name win2k8-32-serial -vnc :10 -device virtio-serial-pci,id=virtio-serial0,max_ports=16,vectors=4,bus=pci.0 -chardev pty,id=channel0 -device virtserialport,chardev=channel0,name=org.linux-kvm.port.0,bus=virtio-serial0.0
3.
Actual results:
Guest got corrupted during testing.
Expected results:
Job could pass.
Additional info:
(In reply to comment #3)
> Hi, Qunfang
>
> Could you please try reproducing this problem with the same
> image and vioserial driver from virtio-win-1-1-16 package?
>
> Thank you,
> Vadim.
Ok, I will try.
Hi, Dor and Vadim
I re-install a new win2k8-32-sp2 guest and do system update. Then re-test the whql virtio serial "Common Scenario Stress With IO". It passed.
So, maybe the old backup image is copied for many times and has some problem? Not sure, I will change this bug's priority to medium and follow it.
If we never hit this issue in the following test, I will close it as NOTABUG.
Thanks
Qunfang
(In reply to comment #6)
> Hi, Dor and Vadim
> I re-install a new win2k8-32-sp2 guest and do system update. Then re-test the
> whql virtio serial "Common Scenario Stress With IO". It passed.
> So, maybe the old backup image is copied for many times and has some problem?
> Not sure, I will change this bug's priority to medium and follow it.
> If we never hit this issue in the following test, I will close it as NOTABUG.
>
> Thanks
> Qunfang
ok, let's wait a week and close it if it won't happens again