From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:54468) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YimFR-0005ws-CZ for qemu-devel@nongnu.org; Thu, 16 Apr 2015 12:02:43 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YimFN-000479-7k for qemu-devel@nongnu.org; Thu, 16 Apr 2015 12:02:37 -0400 Received: from mail-wg0-x22b.google.com ([2a00:1450:400c:c00::22b]:36123) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YimFM-00046x-TS for qemu-devel@nongnu.org; Thu, 16 Apr 2015 12:02:33 -0400 Received: by wgsk9 with SMTP id k9so85806532wgs.3 for ; Thu, 16 Apr 2015 09:02:32 -0700 (PDT) Sender: Paolo Bonzini Message-ID: <552FDD13.4090006@redhat.com> Date: Thu, 16 Apr 2015 18:02:27 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Subject: Re: [Qemu-devel] ARM: PCI devices emulation broken with KVM due to cache issue List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: =?UTF-8?B?SsOpcsOpbXkgRmFuZ3XDqGRl?= , QEMU Developers Cc: VirtualOpenSystems Technical Team , kvmarm@lists.cs.columbia.edu 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