Bug 727034
Summary: | [WHQL][viostor]winxpsp3 32 bit guest exited with "virtio: trying to map MMIO memory" error | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Sibiao Luo <sluo> |
Component: | virtio-win | Assignee: | Vadim Rozenfeld <vrozenfe> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 6.2 | CC: | bcao, gvenkat, juzhang, mdeng, michen, rhod |
Target Milestone: | rc | Keywords: | TestBlocker |
Target Release: | 6.2 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | virtio-block | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Do not document.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2011-12-06 21:17:43 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Sibiao Luo
2011-08-01 05:38:54 UTC
add testblocker keyword ,it blocks QE to run virtio block whql test . additional info : only occurs with winxp 32 bit guest . Please verify with the latest drivers from: http://download.devel.redhat.com/brewroot/packages/virtio-win-prewhql/0.1/15/win/virtio-win-prewhql-0.1.zip Thank you, Vadim. Hi Vadim, Actually,QE have already begun to verify the bug while hitting an issue at step 3.Boot the guest with virtio-blk-pci. After system disk was changed from 'ide' to 'virtio' the guest could not boot up successfully.It should be a new bug and it will be reported just a moment. Now we are tying another way to verify this bug.Thank you very much. Best regards, Min (In reply to comment #5) > Hi Vadim, > Actually,QE have already begun to verify the bug while hitting an issue at > step 3.Boot the guest with virtio-blk-pci. > After system disk was changed from 'ide' to 'virtio' the guest could not > boot up successfully.It should be a new bug and it will be reported just a > moment. > Now we are tying another way to verify this bug.Thank you very much. > > Best regards, > Min Hi Min, Did you use the latest driver installing the system at stage 1? Thank you, Vadim. (In reply to comment #6) > Hi Min, > Did you use the latest driver installing the system at stage 1? > Thank you, > Vadim. I make a floppy which newest viostor driver for winxp in it .QE will try to make whether it is work Hi, I have tried two mothods to verify with the latest drivers,and the issue didn't reproduc on the virtio-win-prewhql-0.1-15.But there is a new bug(Bug 730223). First mothods: 1.Boot guest with IDE driver with the floppy of virtio-win-1.3.3-0.el6. eg:/usr/libexec/qemu-kvm -m 2G -smp 2 -cpu cpu64-rhel6,+x2apic -usbdevice tablet -drive file=winxp-new.raw,format=raw,if=none,id=drive-virtio0,cache=none,werror=stop,rerror=stop -device ied-drive,drive=drive-virtio0,id=virtio-blk-pci0 -netdev tap,id=hostnet0,script=/etc/qemu-ifup -device rtl8139,netdev=hostnet0,mac=00:11:1c:16:73:35 -boot c -uuid 5395b4ef-f341-4d6c-87ca-94291c7cd200 -rtc-td-hack -no-kvm-pit-reinjection -chardev socket,id=111a,path=/tmp/monitor-winxp-blk-sluo,server,nowait -mon chardev=111a,mode=readline -name winxp-blk-sluo-13 -spice disable-ticketing,port=5966 -vga qxl -drive file=disk1.raw,format=raw,if=none,id=drive-virtio1,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio1,id=virtio-blk-pci1 -drive file=disk2.raw,format=raw,if=none,id=drive-virtio2,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio2,id=virtio-blk-pci2 -drive file=disk3.raw,format=raw,if=none,id=drive-virtio3,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio3,id=virtio-blk-pci3 -drive file=disk4.raw,format=raw,if=none,id=drive-virtio4,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio4,id=virtio-blk-pci4 -monitor stdio -drive file=/usr/share/virtio-win/virtio-win-1.3.3.vfd,if=none,id=f1,format=raw,cache=none -global isa-fdc.driveA=f1 2.update the data disk to latest driver(virtio-win-prewhql-0.1-15) http://download.devel.redhat.com/brewroot/packages/virtio-win-prewhql/0.1/15/win/virtio-win-prewhql-0.1.zip 3.shut down the guest and change ide-driver to virtio-blk-pci for system disk 4.boot guest successfully. Second mothods: 1.make a floppy which is the newest viostor driver(virtio-win-prewhql-0.1-15) for winxp 1.Boot guest with virtio-blk-pci with the floppy of virtio-win-prewhql-0.1-15 eg:/usr/libexec/qemu-kvm -m 2G -smp 2 -cpu cpu64-rhel6,+x2apic -usbdevice tablet -drive file=xpbug.raw,format=raw,if=none,id=drive-virtio0,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio0,id=virtio-blk-pci0 -netdev tap,id=hostnet0,script=/etc/qemu-ifup -device rtl8139,netdev=hostnet0,mac=00:11:1c:16:23:35 -boot dc -uuid a89628ba-c3d5-435f-97f5-e566d42942eb -rtc-td-hack -no-kvm-pit-reinjection -chardev socket,id=111a,path=/tmp/monitor-winxp-blk-sluo,server,nowait -mon chardev=111a,mode=readline -name winxp-blk-sluo-13 -spice disable-ticketing,port=5965 -vga qxl -drive file=disk1.raw,format=raw,if=none,id=drive-virtio1,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio1,id=virtio-blk-pci1 -drive file=disk2.raw,format=raw,if=none,id=drive-virtio2,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio2,id=virtio-blk-pci2 -drive file=disk3.raw,format=raw,if=none,id=drive-virtio3,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio3,id=virtio-blk-pci3 -drive file=disk4.raw,format=raw,if=none,id=drive-virtio4,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio4,id=virtio-blk-pci4 -monitor stdio -drive file=/virtio_viostor.img,if=none,id=f1,format=raw,cache=none -global isa-fdc.driveA=f1 -cdrom en_windows_xp_professional_with_service_pack_3_x86_cd_x14-80428.iso 2.install the the latest driver with four data disks from the floppy. 3.shut down the guest and then boot guest successfully. Based on comment #9 ,move status to Verified. Please note that this bug has been reported in many other distros as well including my report for opensuse. Please see https://bugs.launchpad.net/qemu/+bug/818673 https://bugzilla.novell.com/show_bug.cgi?id=704537 One thing that might help in reproducing the bug is to know that this crash happens for me only on the first boot of the guest after a reboot of the host. The subsequent start of the guest works with no problems. Any attempts to reproduce this problem must be after a reboot of the host to be sure. (there may be other software restarts/resets that might show the problem but a host reboot is a reliable way of reproducing the problem). Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Do not document. 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-2011-1542.html |