From: Paolo Bonzini <pbonzini@redhat.com>
To: "Jérémy Fanguède" <j.fanguede@virtualopensystems.com>,
"QEMU Developers" <qemu-devel@nongnu.org>
Cc: VirtualOpenSystems Technical Team <tech@virtualopensystems.com>,
kvmarm@lists.cs.columbia.edu
Subject: Re: [Qemu-devel] ARM: PCI devices emulation broken with KVM due to cache issue
Date: Thu, 16 Apr 2015 18:02:27 +0200 [thread overview]
Message-ID: <552FDD13.4090006@redhat.com> (raw)
In-Reply-To: <CAGE1QJoXVDP_O0W9dRCsN+FBW3BEYn5gqiCvGh07CfadNp2kHw@mail.gmail.com>
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.
Paolo
next prev parent reply other threads:[~2015-04-16 16:02 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 [this message]
2015-04-17 9:29 ` Christoffer Dall
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=552FDD13.4090006@redhat.com \
--to=pbonzini@redhat.com \
--cc=j.fanguede@virtualopensystems.com \
--cc=kvmarm@lists.cs.columbia.edu \
--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).