All of lore.kernel.org
 help / color / mirror / Atom feed
From: Launchpad Bug Tracker <1836501@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1836501] Re: cpu_address_space_init fails with assertion
Date: Tue, 18 Feb 2020 04:17:24 -0000	[thread overview]
Message-ID: <158199944493.16509.12519423294109067577.malone@loganberry.canonical.com> (raw)
In-Reply-To: 156313770910.15255.7682693906978508241.malonedeb@soybean.canonical.com

[Expired for QEMU because there has been no activity for 60 days.]

** Changed in: qemu
       Status: Incomplete => Expired

-- 
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:
  Expired

Bug description:
  qemu-system-arm does not start with version >= 2.6 and KVM enabled.

    cpu_address_space_init: Assertion `asidx == 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 -kernel vmlinuz -initrd initrd.gz -dtb vexpress-v2p-ca15-tc1.dtb -device virtio-blk-device,drive=inst-blk -drive file=PATHTOFILE,id=inst-blk,if=none,format=raw -append "vga=normal rw console=ttyAMA0" -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


  parent reply	other threads:[~2020-02-18  4:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-14 20:55 [Qemu-devel] [Bug 1836501] [NEW] cpu_address_space_init fails with assertion Lutz
2019-07-15  8:49 ` [Qemu-devel] [Bug 1836501] " Peter Maydell
2019-07-15  8:57 ` Peter Maydell
2019-07-15  9:13 ` Peter Maydell
2019-07-15  9:57 ` Peter Maydell
2019-07-15 10:31 ` Lutz
2019-07-16 15:20 ` Peter Maydell
2019-07-16 20:17 ` Lutz
2019-07-17  5:44 ` Lutz
2019-07-18 14:25 ` Peter Maydell
2019-07-31  9:27 ` Alex Bennée
2019-12-19 15:16 ` Peter Maydell
2020-02-18  4:17 ` Launchpad Bug Tracker [this message]
2021-02-22  5:35 ` Ravishankar
2021-02-22  5:48 ` Ravishankar
2021-02-22 13:58 ` Peter Maydell

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=158199944493.16509.12519423294109067577.malone@loganberry.canonical.com \
    --to=1836501@bugs.launchpad.net \
    --cc=qemu-devel@nongnu.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.