Hi,
I am trying to save a snapshot, and later load that. When I give -loadvm on the commandline, it gives me disk errors. If I then do a loadvm from the monitor, it works fine. I also tried to start qemu with -S so that it does not do anything, and then did a loadvm from the monitor - I got the same set of errors. But a subsequent loadvm from the monitor works without any problems.
The command line I used is: qemu-system-arm -machine vexpress-a9 -m 1024 -nographic -net nic -net user -append "console=ttyAMA0,115200n8 rw root=/dev/mmcblk0p2 rootwait physmap.enabled=0" -kernel vmlinuz-3.4.2-3.fc17.armv7hl -initrd
initramfs-3.4.2-3.fc17.armv7hl.img -sd new.qcow2.img
My qemu version is 1.2.1, I also get same error on 1.1.2
The errors are as follows:
SD: CMD25 in a
wrong state
SD: CMD13 in a wrong state
[ 96.442672] mmcblk0: error -110 sending status command, retrying^M
SD: CMD13 in a wrong state
[ 96.470039] mmcblk0: error -110 sending status command, retrying^M
SD: CMD13 in a wrong state
[ 96.470585] mmcblk0: error -110 sending status command, aborting^M
SD: CMD13 in a wrong state
SD: CMD13 in a wrong state
SD: CMD13 in a wrong state
SD: CMD13 in a wrong state
[ 96.472772] Buffer I/O error on device mmcblk0p2, logical block 8363^M
[ 96.473237] lost page write due to I/O error on mmcblk0p2^M
[ 96.476352] JBD2: Detected IO errors while flushing file data on mmcblk0p2-8^M
[ 96.477154] Aborting journal on device mmcblk0p2-8.^M
[ 96.479177] EXT4-fs error (device mmcblk0p2) in ext4_reserve_inode_write:4356: Journal has aborted^M
[ 96.480681] Buffer I/O error on
device mmcblk0p2, logical block 131072^M
[ 96.481088] lost page write due to I/O error on mmcblk0p2^M
[ 96.481673] JBD2: Error -5 detected when updating journal superblock for mmcblk0p2-8
96.477154] Aborting journal on device mmcblk0p2-8.^M
[ 96.479177] EXT4-fs error (device mmcblk0p2) in ext4_reserve_inode_write:4356: Journal has aborted^M
[ 96.480681] Buffer I/O error on device mmcblk0p2, logical block 131072^M
[ 96.481088] lost page write due to I/O error on mmcblk0p2^M
[ 96.481673] JBD2: Error -5 detected when updating journal superblock for mmcblk0p2-8.^M
[ 96.486142] Buffer I/O error on device mmcblk0p2, logical block 0^M
[ 96.486531] lost page write due to I/O error on mmcblk0p2^M
[ 96.487917] EXT4-fs (mmcblk0p2): previous I/O error to superblock detected^M
[ 96.488510] Buffer I/O
error on device mmcblk0p2, logical block 0^M
[ 96.488888] lost page write due to I/O error on mmcblk0p2^M
[ 96.489414] EXT4-fs error (device mmcblk0p2): ext4_journal_start_sb:328: Detected aborted journal^M
[ 96.489999] EXT4-fs (mmcblk0p2): Remounting filesystem read-only^M
[ 96.490384] EXT4-fs (mmcblk0p2): previous I/O error to superblock detected^M
[ 96.490929] Buffer I/O error on device mmcblk0p2, logical block 0^M
[ 96.491302] lost page write due to I/O error on mmcblk0p2^M
[ 96.975322] mmc0: card 4567 removed^M
[ 96.982952] journal commit I/O error^M
[ 96.983237] journal commit I/O error^M
[ 96.995900] journal commit I/O error^M
[ 96.996167] journal commit I/O error^M
[ 96.996408] journal commit I/O error^M
[ 96.996644] journal commit I/O
error^M
[ 96.996878] journal commit I/O error^M
and so on...
I use the disk image:
http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-vexpress-mmcblk0.img.xz
and then converted it to qcow2 format using qemu-img convert.
I tried it out on a versatilepb board and it worked fine - no errors. (commandline:
qemu-system-arm -M versatilepb -kernel vmlinuz-2.6.26-2-versatile
-initrd initrd.img-2.6.26-2-versatile -hda
debian_lenny_armel_desktop.qcow2 -append "root=/dev/sda1")
Thanks a lot!
regards,
Shijesta |
|