Created attachment 569854 [details] call trace Description of problem: Version-Release number of selected component (if applicable): How reproducible: sometime Steps to Reproduce: 1. run dd in guest for i in `seq 1000`; do dd if=/dev/zero of=/tmp/file bs=1M count=1024; done 2. [root@localhost ~]# touch test touch test touch: cannot touch `test': Read-only file system 3. Actual results: Expected results: Additional info: 1. guest kernel: 2.6.18-308.el5 2. df [root@localhost ~]# df df Filesystem 1K-blocks Used Available Use% Mounted on /dev/mapper/VolGroup00-LogVol00 16220072 3718980 11663872 25% / /dev/vda1 101086 12848 83019 14% /boot tmpfs 2021628 0 2021628 0% /dev/shm 3. cmd /usr/libexec/qemu-kvm -name 308_249 -monitor stdio -serial unix:/tmp/serial-20120313-002624-AuCO,server,nowait -drive file=/images/RHEL-Server-5.8-64-virtio.qcow2,index=0,if=virtio,media=disk,cache=none,boot=on,format=qcow2 -net nic,vlan=0,model=virtio,macaddr=90:0a:90:76:45:00 -net tap,vlan=0,script=/home/autotest-devel/client/tests/kvm/scripts/qemu-ifup-switch -m 4096 -smp 2,cores=1,threads=1,sockets=2 -cpu qemu64,+sse2 -soundhw ac97 -vnc :1 -rtc-td-hack -M rhel5.6.0 -boot c -no-kvm-pit-reinjection -usbdevice table 4. call trace (attached)
(In reply to comment #0) > Created attachment 569854 [details] > call trace > > Description of problem: > > > Version-Release number of selected component (if applicable): kvm-83-249.el5 2.6.18-308.el5
Created attachment 569862 [details] fs checking error
Kevin, Is it worth verifying on a native (non-virt) installation?
Suqin, what does qemu-img check say? Does the same happen with IDE or SCSI disks? And is "sometimes" more like 50% or more like 5%? Ronen, if you can get us some real virtio-blk hardware, that would be cool. ;-)
Oh, I only see now that this is RHEL 5. So the next obvious question would be if you can observe the same on RHEL 6.
#qemu-img check RHEL-Server-5.8-64-virtio.qcow2 No errors were found on the image. issue always happen if the images installed (fresh installed)on host AMD 4450B, but don't happen if the image installed on other host when I report this bug. will try with ide/virtio (do I need to test scsi? it's not supported on rhel5)
No, SCSI is not required, IDE should be good enough. Does it happen with RHEL 6 guests as well?
Hi kevin, re-test it, don't reproduce it until now (both rhel5 and rhel6 guests) but it's easy to reproduce with the backup image(fresh installed when I report this bug) both ide and virtio. you can get image here http://fileshare.englab.nay.redhat.com/pub/section2/kvm/shuang/image/shuang.bak
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux release for currently deployed products. This request is not yet committed for inclusion in a release.
Since it's been difficult to reproduce this problem with a fresh install, I recommend closing it as WONTFIX or WORKSFORME on RHEL5.
I agree, closing.