From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:57832) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Wh2Vc-0004bV-AH for qemu-devel@nongnu.org; Sun, 04 May 2014 15:55:42 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Wh2VV-0007Kj-Jh for qemu-devel@nongnu.org; Sun, 04 May 2014 15:55:36 -0400 Received: from mail-la0-f50.google.com ([209.85.215.50]:58075) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Wh2VV-0007Kb-Cg for qemu-devel@nongnu.org; Sun, 04 May 2014 15:55:29 -0400 Received: by mail-la0-f50.google.com with SMTP id mc6so221933lab.23 for ; Sun, 04 May 2014 12:55:28 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20140504194531.GE1302@redhat.com> References: <1398956107-7411-1-git-send-email-peter.maydell@linaro.org> <20140504183036.GB12833@redhat.com> <20140504185851.GC1302@redhat.com> <20140504194531.GE1302@redhat.com> From: Peter Maydell Date: Sun, 4 May 2014 20:55:08 +0100 Message-ID: Content-Type: text/plain; charset=UTF-8 Subject: Re: [Qemu-devel] [PULL 00/10] target-arm queue List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Richard W.M. Jones" Cc: QEMU Developers , Anthony Liguori On 4 May 2014 20:45, Richard W.M. Jones wrote: > On Sun, May 04, 2014 at 08:36:20PM +0100, Peter Maydell wrote: >> OK, so you have a kernel (possibly just kernel config) problem >> here -- this means QEMU got EPERM trying to open /dev/kvm. > > Yes for some reason it was 0600. I set it to 0666. > >> This isn't going to work for aarch64 at the moment because: >> * KVM aarch64 currently requires '-cpu host' > > OK -- I will play with libguestfs to make sure it passes this flag, > and try again. It should in theory be possible to get -cpu cortex-a57 to work (though I haven't tried it so it's likely missing something trivial); however that will only work if your host CPU is actually a Cortex-A57. For any other host you'll need -cpu host. > Currently waiting for the host (which has panicked > again) to be rebooted manually. If your host has panicked that's a kernel bug :-) (or possibly a hardware bug if you're unlucky). If it does so reproducibly when you prod it with QEMU then you should probably retest with a recent kernel and report it to the kvm-arm mailing list. thanks -- PMM