qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Christoffer Dall <christoffer.dall@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Jérémy Fanguède" <j.fanguede@virtualopensystems.com>,
	"VirtualOpenSystems Technical Team" <tech@virtualopensystems.com>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	kvmarm@lists.cs.columbia.edu
Subject: Re: [Qemu-devel] ARM: PCI devices emulation broken with KVM due to cache issue
Date: Fri, 17 Apr 2015 11:29:10 +0200	[thread overview]
Message-ID: <20150417092910.GI6186@cbox> (raw)
In-Reply-To: <552FDD13.4090006@redhat.com>

On Thu, Apr 16, 2015 at 06:02:27PM +0200, Paolo Bonzini wrote:
> 
> 
> On 16/04/2015 17:54, Jérémy Fanguède wrote:
> > The guest kernel driver of the lsi device fails to enable it correctly
> > with a cache error:
> > [...]
> > sym53c8xx 0000:00:01.0: enabling device (0100 -> 0103)
> > sym0: <895a> rev 0x0 at pci 0000:00:01.0 irq 54
> > sym0: No NVRAM, ID 7, Fast-40, LVD, parity checking
> > CACHE TEST FAILED: chip wrote 2, host read 1.
> > sym0: CACHE INCORRECTLY CONFIGURED.
> > sym0: giving up ...
> > [...]
> 
> Note that this is just a failure in the driver self-test.  It has
> nothing to do with the processor cache (though there are other problems
> with PCI and the processor cache in KVM mode).
> 
> Do not use this QEMU device.  The emulation is incomplete and it's slow.
>  Use virtio-scsi or megasas instead.  Still, I'm not sure that would
> work with KVM; as far as I know, most work on the ARM PCI host bridge
> was done using UEFI firmware.
> 
I've been running a number of tests lately using virtio-net-pci and
virtio-blk-pci on XGene at it works like a charm.

-Christoffer

  reply	other threads:[~2015-04-17  9:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-16 15:54 [Qemu-devel] ARM: PCI devices emulation broken with KVM due to cache issue Jérémy Fanguède
2015-04-16 16:02 ` Paolo Bonzini
2015-04-17  9:29   ` Christoffer Dall [this message]
2015-04-17 13:48     ` Jérémy Fanguède
2015-04-17 14:06       ` Christoffer Dall

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150417092910.GI6186@cbox \
    --to=christoffer.dall@linaro.org \
    --cc=j.fanguede@virtualopensystems.com \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=tech@virtualopensystems.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).