From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.7 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 54095C7618F for ; Tue, 16 Jul 2019 20:26:40 +0000 (UTC) Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 2897D20659 for ; Tue, 16 Jul 2019 20:26:40 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 2897D20659 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=bugs.launchpad.net Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Received: from localhost ([::1]:52156 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hnU23-0006H6-G7 for qemu-devel@archiver.kernel.org; Tue, 16 Jul 2019 16:26:39 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:38172) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hnU1t-0005rk-0P for qemu-devel@nongnu.org; Tue, 16 Jul 2019 16:26:30 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hnU1r-00076z-Lq for qemu-devel@nongnu.org; Tue, 16 Jul 2019 16:26:28 -0400 Received: from indium.canonical.com ([91.189.90.7]:37528) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hnU1r-00074D-Ee for qemu-devel@nongnu.org; Tue, 16 Jul 2019 16:26:27 -0400 Received: from loganberry.canonical.com ([91.189.90.37]) by indium.canonical.com with esmtp (Exim 4.86_2 #2 (Debian)) id 1hnU1o-0000hd-IZ for ; Tue, 16 Jul 2019 20:26:24 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id 660382E80D2 for ; Tue, 16 Jul 2019 20:26:24 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Tue, 16 Jul 2019 20:17:21 -0000 From: Lutz <1836501@bugs.launchpad.net> To: qemu-devel@nongnu.org X-Launchpad-Notification-Type: bug X-Launchpad-Bug: product=qemu; status=Confirmed; importance=Undecided; assignee=None; X-Launchpad-Bug-Tags: arm X-Launchpad-Bug-Information-Type: Public X-Launchpad-Bug-Private: no X-Launchpad-Bug-Security-Vulnerability: no X-Launchpad-Bug-Commenters: pmaydell skandal X-Launchpad-Bug-Reporter: Lutz (skandal) X-Launchpad-Bug-Modifier: Lutz (skandal) References: <156313770910.15255.7682693906978508241.malonedeb@soybean.canonical.com> Message-Id: <156330824201.26415.10688053586527573163.malone@wampee.canonical.com> X-Launchpad-Message-Rationale: Subscriber (QEMU) @qemu-devel-ml X-Launchpad-Message-For: qemu-devel-ml Precedence: bulk X-Generated-By: Launchpad (canonical.com); Revision="19009"; Instance="launchpad-lazr.conf" X-Launchpad-Hash: fbdcba826e4a887d3fde829d71c9b3698bf59e48 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 91.189.90.7 Subject: [Qemu-devel] [Bug 1836501] Re: cpu_address_space_init fails with assertion X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.23 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Bug 1836501 <1836501@bugs.launchpad.net> Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" My test setup is now Debian Buster with qemu-system-arm 3.1 and a host with KVM-enabled Kernel 4.9.61 on Odroid XU4. Following results: -------- qemu-system-arm -M vexpress-a15 -smp 2 -m 512 -kernel vmlinuz -initrd initr= d.gz -dtb vexpress-v2p-ca15-tc1.dtb -device virtio-blk-device,drive=3Dinst-= blk -drive file=3DPATHTOFILE,id=3Dinst-blk,if=3Dnone,format=3Draw -append "= vga=3Dnormal rw console=3DttyAMA0" -nographic -enable-kvm Still not working as above, so it doesn't seem to be fixed for 3.1. -------- qemu-system-arm -M vexpress-a15,secure=3Doff -smp 2 -m 512 -kernel vmlinuz = -initrd initrd.gz -dtb vexpress-v2p-ca15-tc1.dtb -device virtio-blk-device,= drive=3Dinst-blk -drive file=3DPATHTOFILE,id=3Dinst-blk,if=3Dnone,format=3D= raw -append "vga=3Dnormal rw console=3DttyAMA0" -nographic -enable-kvm No errors but no output at all, can switch to qemu monitor, but don't know = if system is running -------- Option 1 and Option 2 both start the Debian installer as expected WITHOUT t= he parameter -enable-kvm I did also tests with the virt board as recommended. With the parameter -en= able-kvm none of the different virt-* boards did output anything to the con= sole, without KVM the virt-boards did start. = virt-2.6 and virt-2.7 did boot into the installer without KVM. Any more recent version (2.8, 2.9, 2.10, 3.0 and 3.1) returned "Unable to handle kernel paging request at virtual address 0109ed30" (address is changing) during the init process. With different guest memory sizes the paging error occurred at a different init step. Conclusion: 1) EL3 feature does still seem to be enabled in qemu 3.1 (Debian) even for = KVM-enabled guests. 2) Any recommendation for a support forum to discuss my trouble with the mi= ssing console output when enabling KVM and the paging problems with the rec= ent virt boards outside this bug report? -- = You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1836501 Title: cpu_address_space_init fails with assertion Status in QEMU: Confirmed Bug description: qemu-system-arm does not start with version >=3D 2.6 and KVM enabled. cpu_address_space_init: Assertion `asidx =3D=3D 0 || !kvm_enabled()' failed. Hardware is Odroid XU4 with Exynos with 4.9.61+ Tested with Debian Stretch (9) or Buster (10). Without KVM it is running fine but slow. I'm operating Debian Jessie with qemu 2.1 for a long time with KVM virtualization working flawlessly. When I upgraded to Stretch I ran into the trouble described before. I tried Debian Stretch and Buster with all Kernels provided by the Board manufacturer (Hardkernel). It seems to be related to the feature introduced in Version 2.6: https://wiki.qemu.org/ChangeLog/2.6 - Support for a separate EL3 address space KVM is enabled, so I assume the adress space index asidx to be causing the assert to fail. dmesg | grep -i KVM [ 0.741714] kvm [1]: 8-bit VMID [ 0.741721] kvm [1]: IDMAP page: 40201000 [ 0.741729] kvm [1]: HYP VA range: c0000000:ffffffff [ 0.742543] kvm [1]: Hyp mode initialized successfully [ 0.742600] kvm [1]: vgic-v2@10484000 [ 0.742924] kvm [1]: vgic interrupt IRQ16 [ 0.742943] kvm [1]: virtual timer IRQ60 Full command line is: qemu-system-arm -M vexpress-a15 -smp 2 -m 512 -cpu host -enable-kvm -kern= el vmlinuz -initrd initrd.gz -dtb vexpress-v2p-ca15-tc1.dtb -device virtio-= blk-device,drive=3Dinst-blk -drive file=3DPATHTOFILE,id=3Dinst-blk,if=3Dnon= e,format=3Draw -append "vga=3Dnormal rw console=3DttyAMA0" -nographic Is there anything to do to understand, if this is a hardware related failure or probably just a missing parameter? Regards Lutz To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1836501/+subscriptions