Bug 542923
Summary: | Get segmentation fault when running with ide block on kvm-83-136.el5 | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Golita Yue <gyue> |
Component: | kvm | Assignee: | Kevin Wolf <kwolf> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | urgent | Docs Contact: | |
Priority: | urgent | ||
Version: | 5.5 | CC: | chellwig, michen, ovirt-maint, qzhang, tburke, virt-maint, ykaul |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | kvm-83-137.el5 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-03-30 07:52: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
Golita Yue
2009-12-01 08:32:26 UTC
No segmentation fault when start guest with virtio block: -drive file=/root/win28k-64-virtio.qcow2,if=virtio,boot=on No segmentation fault when running RHEL guest with virtio block. /usr/libexec/qemu-kvm -no-hpet -usbdevice tablet -rtc-td-hack -smp 2 -m 2G -drive file=/root/test190/rhel5.4-4k.qcow2,media=disk,if=virtio,index=0,boot=on -net nic,vlan=0,macaddr=10:1a:4a:10:20:4d,model=virtio -net tap,vlan=0,script=/etc/qemu-ifup -uuid `uuidgen` -cpu qemu64,+sse2 -boot c -balloon none -monitor stdio -vnc :10 -name 190host-4k Segmentation fault happened when using the following combination: kvm: kvm-83-136.el5 image cluster_size: Both 64k and 4k block: ide kvm-83-135.el5 does not have this problem. Is that reproducible? Anything special on this image? Did the guest managed to boot? Does qcow2 vs. raw make a difference? (In reply to comment #4) > Is that reproducible? Anything special on this image? Did the guest managed to > boot? Yes, it could be reproducible. Not special thing on this image. The guest could not boot up, this error happened during guest booting up. (In reply to comment #5) > Does qcow2 vs. raw make a difference? Try the following combination: guest raw/qcow2 ide/virtio segmentation-fault? boot-up? win2008 raw ide no yes rhel5u4 raw ide no yes win2003 qcow2 virtio no yes win2003 qcow2 ide yes no win2008 qcow2 ide yes no The segfault happens in bdrv_aio_flush_em, so I suspect it's related to Christoph's patch series that introduced this function in kvm-83-136.el5. It doesn't happen with raw because this implements an own aio_flush operation whereas qcow2 uses the default implementation. Not sure why virtio isn't affected, maybe old guest drivers that don't use flushing? Found the problem (a QCowAIOCB being interpreted as BlockDriverAIOCBSync), need to find the best way of fixing it now. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2010-0271.html |