Bug 915540
| Summary: | [whql][virtio-win]win server 2012 guest hang during MPE job | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Mike Cao <bcao> | ||||
| Component: | virtio-win | Assignee: | Yvugenfi <yvugenfi> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 6.4 | CC: | acathrow, bcao, bsarathy, juzhang, kzhang, lijin, michen | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: |
Do not document. There was no Windows 2012 support in previous release. This bug was found on internal version.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-11-22 00:04:04 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Mike Cao
2013-02-26 02:29:56 UTC
Created attachment 702578 [details]
screenshot
I tried to use (qemu)inject-nmi ,but no idea why failed to generate a BSOD at that stage. (In reply to comment #2) > I tried to use (qemu)inject-nmi ,but no idea why failed to generate a BSOD > at that stage. Hi Mike, Do you have NMICrashDump enabled in the registry? Best regards, Vadim. (In reply to comment #3) > (In reply to comment #2) > > I tried to use (qemu)inject-nmi ,but no idea why failed to generate a BSOD > > at that stage. > Hi Mike, > Do you have NMICrashDump enabled in the registry? > Best regards, > Vadim. Yes I did .after (qemu)system_reset ,then (qemu)inject-nmi works to me . while it does not help when guest hang Can you try to ran MPE test with Realtech device? Looks like e1000 hang on boot. (In reply to comment #5) > Can you try to ran MPE test with Realtech device? Looks like e1000 hang on > boot. Tried ,Still hit the exactly same issue . I will try to copy 2 fresh image to re-test Hi Mike, I understand you passed WHQL on Windows Server 2012. Is this bug still an issue? Best regards, Yan. (In reply to comment #8) > Hi Mike, > > I understand you passed WHQL on Windows Server 2012. > > Is this bug still an issue? > > Best regards, > Yan. it passed on on build 54 ,but failed on the newer version build . as it is not 100% reproducible ,we can say it is not a blocker ,but it is a bug . Based on above ,Re-assign this issue . QE test the bug via build 61. Version-Release number of selected component (if applicable): * Red Hat Enterprise Linux Server release 6.4 (Santiago) * kernel-2.6.32-369.el6.x86_64 * qemu-img-rhev-0.12.1.2-2.359.el6.x86_64 * virtio-win-prewhql-0.1-61 * spice-server-0.12.0-12.el6.x86_64 * seabios-0.6.1.2-27.el6.x86_64 * vgabios-0.6b-3.7.el6.noarch Steps to Reproduce: 1.Start VM running NDIS MPE job /usr/libexec/qemu-kvm -m 6G -smp 8,cores=8 -cpu cpu64-rhel6,+x2apic -usb -device usb-tablet -drive file=win2012-nic1.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,sndbuf=0,id=hostnet0,vhost=on,script=/etc/qemu-ifup-private,downscript=no -device virtio-net-pci,netdev=hostnet0,mac=00:23:43:22:32:21,bus=pci.0,addr=0x4,id=virtio-net-pci0 -netdev tap,sndbuf=0,id=hostnet2,script=/etc/qemu-ifup,downscript=no -device e1000,netdev=hostnet2,mac=00:22:45:13:41:12,bus=pci.0,addr=0x6 -uuid c1750585-9665-4977-bb0b-a6d7e6478f91 -no-kvm-pit-reinjection -chardev socket,id=111a,path=/tmp/monitor-win2012-nic1,server,nowait -mon chardev=111a,mode=readline -vnc :1 -vga cirrus -name win20124-nic1-61-HCK -rtc base=localtime,clock=host,driftfix=slew -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 -monitor stdio Actual results: job finished successfully Expected results: job could finish successfully so the issues has been fixed on build 61 ,thanks! Move stauts to VERIFIED according to comment #10 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-1729.html |