this issue occurred again. So reopen this bug.
I use upstream kvm.git ef7c782ea and qemu-kvm.git 44755ea36.
The host is rhel6.1 with lastest kvm and qemu-kvm installed, and its file
system type is ext4.
here's the dmesg info in rhel5u5 guest after being restored.
-----------------------------------------log--------------------------------------
hda: status error: status=0x00 { }
ide: failed opcode was: unknown
hda: drive not ready for command
hda: status error: status=0x00 { }
ide: failed opcode was: unknown
hda: drive not ready for command
hda: status error: status=0x00 { }
ide: failed opcode was: unknown
hda: drive not ready for command
hda: status error: status=0x00 { }
ide: failed opcode was: unknown
hda: drive not ready for command
ide0: reset: master: error (0x00?)
hda: status error: status=0x00 { }
ide: failed opcode was: unknown
hda: drive not ready for command
hda: status error: status=0x00 { }
ide: failed opcode was: unknown
hda: drive not ready for command
hda: status error: status=0x00 { }
ide: failed opcode was: unknown
hda: drive not ready for command
hda: status error: status=0x00 { }
ide: failed opcode was: unknown
hda: drive not ready for command
ide0: reset: master: error (0x00?)
end_request: I/O error, dev hda, sector 32991
end_request: I/O error, dev hda, sector 32999
end_request: I/O error, dev hda, sector 33007
end_request: I/O error, dev hda, sector 4465351
Buffer I/O error on device hda1, logical block 558161
Aborting journal on device hda1.
lost page write due to I/O error on hda1
end_request: I/O error, dev hda, sector 4465359
Buffer I/O error on device hda1, logical block 558162
lost page write due to I/O error on hda1
end_request: I/O error, dev hda, sector 13447
Buffer I/O error on device hda1, logical block 1673
lost page write due to I/O error on hda1
__journal_remove_journal_head: freeing b_committed_data
journal commit I/O error
ext3_abort called.
EXT3-fs error (device hda1): ext3_journal_start_sb: Detected aborted journal
Remounting filesystem read-only
** Project changed: qemu => qemu-kvm
** Changed in: qemu-kvm
Status: Fix Released => New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/739088
Title:
I/O errors after "Save/Restore"
Status in qemu-kvm:
New
Bug description:
qemu-kvm commit: b73357ecd2b14c057134cb71d29447b5b988c516
( Author: Marcelo Tosatti <mtosa...@redhat.com> Date: Wed Mar 16
17:04:16 2011 -0300)
kvm commit: a72e315c509376bbd1e121219c3ad9f23973923f
After restoring from saved img, some I/O errors appear in dmesg and
file system is read-only. I'm sure that the guest runs normally
before saving. See the pictures attached in detail.
Reproduce steps:
----------------
1.create a guest:
qemu-img create -b /share/xvs/img/app/ia32e_SMP.img -f qcow2
/root/test0320.img
qemu-system-x86_64 -m 256 -net
nic,macaddr=00:16:3e:06:8a:08,model=rtl8139 -net tap,script=/etc/kvm/qemu-ifup
-hda /root/test0320.img
2.save the guest:
on qemu monitor: migrate "exec:dd of=/root/test-save.img"
3.quit from qemu:
"q" command on qemu monitor
4.restore from img just saved:
qemu-system-x86_64 -m 256 -net
nic,macaddr=00:16:3e:06:8a:08,model=rtl8139 -net tap,script=/etc/kvm/qemu-ifup
-incoming=/roo/test-save.img
5.see dmesg in restored guest, you'll find some I/O errors. And run some
commands such as "ps", "touch","reboot" and so on. Then some I/O errors
appear.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu-kvm/+bug/739088/+subscriptions
