Bug 729450
Summary: | Lots of: block I/O error in device 'virtio0': Input/output error (5) | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Richard W.M. Jones <rjones> |
Component: | qemu-kvm | Assignee: | Minchan Kim <minchan> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.2 | CC: | chayang, flang, juzhang, minchan, mkenneth, pholica, qzhang, rhod, tburke, virt-maint |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-11-29 12:27:14 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: | |||
Bug Depends On: | |||
Bug Blocks: | 691780 |
Description
Richard W.M. Jones
2011-08-09 18:59:43 UTC
Can youshow a proper testcase without that guestfish stuff? The full command I ran is listed right there in the build log I linked to. /usr/libexec/qemu-kvm \ -drive file=debian.img.tmp,cache=off,format=raw,if=virtio \ -nodefconfig \ -nodefaults \ -nographic \ -m 500 \ -no-reboot \ -device virtio-serial \ -serial stdio \ -chardev socket,path=/tmp/libguestfsoaZ5Tj/guestfsd.sock,id=channel0 \ -device virtserialport,chardev=channel0,name=org.libguestfs.channel.0 \ -kernel /tmp/.guestfs-250/kernel.30186 \ -initrd /tmp/.guestfs-250/initrd.30186 \ -append 'panic=1 console=ttyS0 udevtimeout=300 noapic acpi=off printk.time=1 cgroup_disable=memory selinux=0 guestfs_verbose=1 TERM=xterm ' \ -drive file=/tmp/.guestfs-250/root.30186,snapshot=on,if=virtio,cache=unsafe Hello, I've hit this on RHEL6.2-20110812.n.0 (guest) running on RHEL6.1 GA (host). My command is: qemu-kvm -monitor stdio -m 1024 -net tap -net nic,model=virtio -drive if=virtio,file=/srv/images/system1,boot=on -cdrom boot.iso -boot once=d And both systems were x86_64. Pavel, do these errors cause problems? For me, the guest appears to continue running regardless. There doesn't *appear* to be any actual disk corruption or stoppage, although the messages in 'dmesg' certainly look worrying. Can't see any real problem too, both systems seems to run fine for me. I have reproduced this issue with 2.6.32-131.21.1.el6.x86_64, qemu-kvm-0.12.1.2-2.160.el6_1.9.x86_64, lots of "block I/O error in device 'virtio0': Input/output error (5)" pops up when trying to boot a virtio-blk-pci image, but these errors seems wouldn't cause any corruption. Adding werror=stop to same cli, guest won't stop on block I/O error. But guest will stop on block I/O error if appending * rerror=stop* to same cli. So, it is a read error from this point of view. Hope this helps. Additional info: Can't reproduce this issue on rhel6.2 with same cli with 2.6.32-216.el6.x86_64, qemu-kvm-0.12.1.2-2.209.el6.x86_64 chayang, Then, could you close this bug? (In reply to comment #11) > chayang, > Then, could you close this bug? Sure, Closing this bug as CURRENTRELEASE due to Comment # 9,10 |