qemu-ppc
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-ppc] Freescale qemu kvm and virtio


From: Scott Wood
Subject: Re: [Qemu-ppc] Freescale qemu kvm and virtio
Date: Fri, 13 Dec 2013 19:56:29 -0600

On Thu, 2013-12-12 at 16:39 -0600, Scott Wood wrote:
> On Thu, 2013-12-12 at 14:12 -0800, Florian Chazal wrote:
> > Hi guys,
> > 
> > 
> > I try to virtualize my system running on freescale p4040 (baremetal)
> > on top of a p4080 + kvm :
> > Every thing seems to work fine till I do intesive I/O in my VM : 
> > qemu-system-ppc -enable-kvm -name kvm1 -serial tcp::4444,server,telnet -m 
> > 1024 -M ppce500 -nographic -netdev tap,id=tap0,script=no,vhost=on -device  
> > e1000,netdev=tap0 -kernel 
> > /home/root/uImage--3.8-r14.3-p4080ds-20131211202743.bin -initrd 
> > /home/root/rootfs-goodArch.cpio.gz -append "root=dev/vda1 init=sbin/init 
> > console=ttyS0,115200 3" -drive 
> > file=/media/sda1/d4-fromscratch-v0.8.4.img,if=virtio
> > QEMU waiting for connection on: telnet::0.0.0.04444,server
> > QEMU 1.4.0 monitor - type 'help' for more information
> > (qemu) status
> > unknown command: 'status'
> > (qemu) info status
> > VM status: running
> > (qemu) EXT3-fs (sda1): error in ext3_reserve_inode_write: IO failure
> > EXT3-fs error (device sda1): ext3_new_block: block(1542) >= blocks count(0) 
> > - block_group = 0, es == eff1a400
> > EXT3-fs (sda1): error in ext3_reserve_inode_write: IO failure
> > EXT3-fs (sda1): error in ext3_orphan_add: IO failure
> > EXT3-fs (sda1): error in ext3_reserve_inode_write: IO failure
> > EXT3-fs (sda1): error in ext3_orphan_add: IO failure
> > EXT3-fs (sda1): error in ext3_reserve_inode_write: IO failure
> > EXT3-fs error (device sda1): ext3_new_block: block(1545) >= blocks count(0) 
> > - block_group = 0, es == eff1a400
> > EXT3-fs (sda1): error in ext3_reserve_inode_write: IO failure
> > EXT3-fs (sda1): error in ext3_orphan_add: IO failure
> > 
> > 
> > My qcow2 image is on a usb key and after this happens, the usb key
> > file system is remounted by the host in readonly mode due to ext3
> > journal corruption.
> > 
> > 
> > I tried the following thingto use io throttle with virtio bps/iops
> > option => limiting  bps to 500000 everything was slow as expected but
> > then I got a different qemu error
> > 
> > (qemu) Unable to handle kernel paging request for data at address 0xffbc8be4
> > Faulting instruction address: 0xc048e774
> 
> Bare addresses are not useful without the vmlinux they came from -- do
> you have a full crash dump with symbol names?  Though if the crash is in
> the filesystem code, you'll need to report it to the appropriate
> filesystem list. 
> 
> As for the above ext3 errors, given the message "IO failure" it may be a
> hardware problem.
> 
> What kernel are you using?  What U-Boot?
> 
> Do you have all relevant errata worked around, especially USB errata?
> There's a USB erratum that basically says high speed mode can't be used
> except on specially screened chips.

Sorry, I need to correct this -- that erratum (A-005275) does not apply
to p4040.  There could be a different erratum causing this, though.

-Scott





reply via email to

[Prev in Thread] Current Thread [Next in Thread]