Re: vm-basic-pci demo is not working for arm64

Mohamed Dawod <[email protected]> Wed, 23 Oct 2024 12:52:08 +0300

Newsgroups	gmane.comp.micro-kernel.l4.devel
Message-ID	<CADFpuP+VMJ1O1yzYwJQAE=Kx0uL2_uSbTOdXttU4vgXQgMr1bQ@mail.gmail.com>

Hi,

Thanks Philipp for your patience and valuable support.

I changed the areas where the RAM should be placed in the memory node of
the device tree and it worked.
Now, I want to test the pci bus by connecting a virtio-blk-pci device via
qemu to be mounted on /dev/vda
to do that, I run qemu using the following options :

*$ qemu-system-aarch64 -kernel
> /home/dawod/workspace/l4re-snapshot-24.08.0/build_aarch64/l4/images/l4re_VM-basic-pci.elf
> -serial stdio -M virt,virtualization=true,iommu=smmuv3 -cpu cortex-a57 -m
> 4096 --display none -drive
> if=none,file=/home/dawod/storage/disk.rootfs.ext4,format=raw,id=disk0
> -device virtio-blk-pci,drive=disk0*


but the VM hangs in the booting stage while trying to create the /dev/vda
block device which will be responsible for handling the added disk.
*please* *find attached a text log from the serial console * :
vm-blk-pci.log
<https://mail.google.com/mail/u/0?ui=2&ik=b05e32a9ef&attid=0.1&permmsgid=msg-a:r-4942377897740831663&view=att&disp=safe&realattid=f_m2lp0t191>

[image: image.png]


Many Thanks,
Regards



On Tue, Oct 22, 2024 at 6:54 PM Philipp Eppelt <
[email protected]> wrote:

> Hi Mohamed,
>
> I'm happy to see you resolved the issue.
> If possible, please prefer a text log from the serial console over a
> picture,
> because the text log is longer and thus provides more information about
> the
> booted system.
>
> uvmm show this error, when memory regions overlap. In this case RAM and
> the intc
> device overlap. The intc device is specified in the device tree you passed
> to uvmm.
> Here, the device tree does not contain explicit RAM regions, so uvmm sets
> up the
> default RAM region, which spans the area starting at zero up to the size
> of the
> RAM you configured in the ned script.
> In this case, RAM covers the area [      0: fff'ffff] (256MB).
> The itc device wants to allocate the area [0x0800'0000 : 0x0800'ffff]
> which is
> contained within the already existing RAM allocation. Thus the error
> message.
>
> You have two options, either specify the areas where the RAM should be
> placed in
> the memory node of the device tree or move the intc device such that it
> doesn't
> overlap. For this setup this means above 0x1000'0000.
>
>
> Cheers
> Philipp
>
>
> Am 22.10.24 um 09:36 schrieb Mohamed Dawod:
> > I upgraded L4 version to 24.08 instead of 23.10 because 24.08 contains
> the
> > missing virt-arm_virt-64_pci.dts file.
> > I'm building for arm64 and when I run the demo VM-basic-pci, I got the
> following
> > error !
> > I didn't change anything in the dts/dtb or ned scripts excepting the
> typo of
> >
> >       overlay = "-drom/virt-pci.dtbo"
> >
> >
> > What is the problem here ?
> >
> > image.png
> >
> > On Mon, Oct 21, 2024 at 11:35 AM Philipp Eppelt <
> [email protected]
> > <mailto:[email protected]>> wrote:
> >
> >     Hi Mohamed,
> >
> >     can you please check your arm64 build tree and look into the folder
> >     'assets/dtb/'? There should be links to all the .dtb files of uvmm.
> The link of
> >     the file in question on my machine is:
> >
> >
>  [...]/.build-arm64/pkg/uvmm/configs/dts/OBJ-arm64_armv8a-std-l4f/virt-arm_virt-64_pci.dtb
> >
> >     If the file is missing in the linked folder, please check the
> corresponding
> >     source directory:
> >
> >     <src>/pkg/uvmm/configs/dts/
> >
> >     If virt-arm_virt-64_pci.dts isn't in there, you can download it from
> our
> >     development version of L4Re on github and recompile the uvmm package.
> >
> >
> https://github.com/kernkonzept/uvmm/blob/master/configs/dts/virt-arm_virt-64_pci.dts
> <
> https://github.com/kernkonzept/uvmm/blob/master/configs/dts/virt-arm_virt-64_pci.dts
> >
> >
> >     If the file is there, please check that '<arm64-build>/assets'
> directory is in
> >     your MODULE_SEARCH_PATH.
> >
> >     Let me know, if this solves the missing file problem.
> >
> >     Cheers,
> >     Philipp
> >
> >
> >
> >     Am 20.10.24 um 09:20 schrieb Mohamed Dawod:
> >      > Thanks Matthias
> >      > I'm going to fix the typo of *virt-pci.dtbo*.
> >      > What about the missing file *dtb/virt-arm_virt-64_pci.dtb *?
> >      >
> >      >
> >      > On Tue, Oct 15, 2024 at 11:58 PM Matthias Lange
> >     <[email protected] <mailto:
> [email protected]>
> >      > <mailto:[email protected]
> >     <mailto:[email protected]>>> wrote:
> >      >
> >      >     Hi Mohamed,
> >      >
> >      >     On [15-10-2024 16:59], Mohamed Dawod wrote:
> >      >      > Hi,
> >      >      > I was trying to run the L4 demo *vm-basic-pci* for *arm64*
> using
> >     the command
> >      >      > $ make qemu E=vm-basic-pci
> >      >      > but It didn't work because of the missing 2 files :
> >      >      > * virt-arm_virt-64_pci.dtb : which is requested by the
> >     *modules.list* file
> >      >      > in the line :
> >      >      >
> >      >      > > module[arch=arm64,fname=virt-pci.dtb]
> >       dtb/virt-arm_virt-64_pci.dtb
> >      >      >
> >      >      > * virt-pci.dtbo : which is requested by the
> *vm-basic-pci.cfg* by the
> >      >      > configuration
> >      >      >
> >      >      > > if (L4.Info.arch() == "arm64") then
> >      >      > >    dt = "-drom/.fdt"
> >      >      > >    overlay = "*-drom/virt-pci.dtbo*"
> >      >
> >      >     This is actually a typo. Please change this line to
> >      >
> >      >        overlay = "-drom/virt-pci.dtb"
> >      >
> >      >     Best,
> >      >     Matthias.
> >      >
> >      >      > > else
> >      >      > >    dt = "-drom/virt-pci.dtb"
> >      >      > >    overlay = ""
> >      >      > > end
> >      >      >
> >      >      >
> >      >      > I searched for both files in the whole
> *l4re-snapshot-23.10.1*
> >     directory
> >      >      > but I couldn't find them
> >      >      > Where can I find those necessary files to run
> *vm-basic-pc*i demo?
> >      >      >
> >      >      > Thanks in advance,
> >      >      > Regards
> >      >      >
> >      >      > --
> >      >      > Mohamed Dawod
> >      >      > *Software Engineer,* Cairo Egypt
> >      >      >
> >      >      > --
> >      >      >
> >      >      >
> >      >      > *Driving Innovation! Visit our website www.avelabs.com
> >     <http://www.avelabs.com>
> >      >     <http://www.avelabs.com <http://www.avelabs.com>>
> >      >      > <http://www.avelabs.com/ <http://www.avelabs.com/>
> >     <http://www.avelabs.com/ <http://www.avelabs.com/>>>*, to read
> Avelabs
> >      >     Confidentiality Notice, follow
> >      >      > this link: http://www.avelabs.com/email/disclaimer.html
> >     <http://www.avelabs.com/email/disclaimer.html>
> >      >     <http://www.avelabs.com/email/disclaimer.html
> >     <http://www.avelabs.com/email/disclaimer.html>>
> >      >      > <http://www.avelabs.com/email/disclaimer.html
> >     <http://www.avelabs.com/email/disclaimer.html>
> >      >     <http://www.avelabs.com/email/disclaimer.html
> >     <http://www.avelabs.com/email/disclaimer.html>>>
> >      >      >
> >      >
> >      >      > _______________________________________________
> >      >      > l4-hackers mailing list -- [email protected]
> >     <mailto:[email protected]>
> >      >     <mailto:[email protected]
> >     <mailto:[email protected]>>
> >      >      > To unsubscribe send an email to
> >     [email protected]
> >     <mailto:[email protected]>
> >      >     <mailto:[email protected]
> >     <mailto:[email protected]>>
> >      >
> >      >
> >      >     --
> >      >     Get started with L4Re in 3 days - register now for our
> workshop in
> >     October!
> >      >
> >      >     Visit
> https://www.kernkonzept.com/workshop-getting-started-with-l4re
> >     <https://www.kernkonzept.com/workshop-getting-started-with-l4re>
> >      >     <
> https://www.kernkonzept.com/workshop-getting-started-with-l4re
> >     <https://www.kernkonzept.com/workshop-getting-started-with-l4re>>
> to learn
> >      >     more.
> >      >
> >      >     --
> >      >     Matthias Lange                      phone: +49 (0) 351-41 888
> 614
> >      >     Customer Engineer Specialist        web:
> https://www.kernkonzept.com
> >     <https://www.kernkonzept.com>
> >      >     <https://www.kernkonzept.com <https://www.kernkonzept.com>>
> >      >
> >      >     Kernkonzept GmbH
> >      >     Buchenstraße 16b
> >      >     01097 Dresden
> >      >
> >      >     Geschäftsführer: Dr.-Ing. Michael Hohmuth
> >      >     Registergericht: Amtsgericht Dresden
> >      >     Handelsregister: HRB 31129
> >      >
> >      >     You might not be working when I am and that's ok! Please make
> sure to
> >     only
> >      >     reply when it suits you. Mails can wait.
> >      >
> >      >
> >      >
> >      > *Driving Innovation! Visit our website www.avelabs.com
> >     <http://www.avelabs.com>
> >      > <http://www.avelabs.com/ <http://www.avelabs.com/>>*, to read
> Avelabs
> >     Confidentiality Notice, follow this
> >      > link: http://www.avelabs.com/email/disclaimer.html
> >     <http://www.avelabs.com/email/disclaimer.html>
> >      > <http://www.avelabs.com/email/disclaimer.html
> >     <http://www.avelabs.com/email/disclaimer.html>>
> >      >
> >      > _______________________________________________
> >      > l4-hackers mailing list -- [email protected]
> >     <mailto:[email protected]>
> >      > To unsubscribe send an email to
> [email protected]
> >     <mailto:[email protected]>
> >
> >     --
> >     [email protected] <mailto:
> [email protected]> -
> >     Tel. 0351-41 883 221
> >     http://www.kernkonzept.com <http://www.kernkonzept.com>
> >
> >     Kernkonzept GmbH.  Sitz: Dresden.  Amtsgericht Dresden, HRB 31129.
> >     Geschäftsführer: Dr.-Ing. Michael Hohmuth
> >     _______________________________________________
> >     l4-hackers mailing list -- [email protected]
> >     <mailto:[email protected]>
> >     To unsubscribe send an email to
> [email protected]
> >     <mailto:[email protected]>
> >
> >
> >
> > *Driving Innovation! Visit our website www.avelabs.com
> > <http://www.avelabs.com/>*, to read Avelabs Confidentiality Notice,
> follow this
> > link: http://www.avelabs.com/email/disclaimer.html
> > <http://www.avelabs.com/email/disclaimer.html>
>
> --
> [email protected] - Tel. 0351-41 883 221
> http://www.kernkonzept.com
>
> Kernkonzept GmbH.  Sitz: Dresden.  Amtsgericht Dresden, HRB 31129.
> Geschäftsführer: Dr.-Ing. Michael Hohmuth
>

-- 


*Driving Innovation! Visit our website www.avelabs.com 
<http://www.avelabs.com/>*, to read Avelabs Confidentiality Notice, follow 
this link: http://www.avelabs.com/email/disclaimer.html 
<http://www.avelabs.com/email/disclaimer.html>

_______________________________________________
l4-hackers mailing list -- [email protected]
To unsubscribe send an email to [email protected]

image.png (image/png, 73.5 KB) - not displayed

vm-blk-pci.log (text/x-log, 18.9 KB)

L4 Bootstrapper
  Build: #58 Wed Oct 23 12:36:56 EEST 2024, 12.2.1 20221203 [releases/gcc-12 revision c03cb4b762aceeba95da918b042583af0d9f6030]
  RAM: 0000000040000000 - 000000013fffffff: 4194304kB
  Total RAM: 4096MB
  Scanning fiasco
  Scanning sigma0
  Scanning moe
  Moving up to 13 modules behind 41100000
  moving module 12 { 427f0000-4290dc01 } -> { 428da000-429f7c01 } [1170434]
  moving module 11 { 4145c000-427ef9ff } -> { 41546000-428d99ff } [20527616]
  moving module 10 { 4145b000-4145b389 } -> { 41545000-41545389 } [906]
  moving module 09 { 41369000-4145ab7f } -> { 41453000-41544b7f } [990080]
  moving module 08 { 41368000-41368464 } -> { 41452000-41452464 } [1125]
  moving module 07 { 41147000-413678d7 } -> { 41231000-414518d7 } [2230488]
  moving module 06 { 41145000-41146218 } -> { 4122f000-41230218 } [4633]
  moving module 05 { 410bc000-411443ff } -> { 411a6000-4122e3ff } [558080]
  moving module 04 { 410a0000-410bb507 } -> { 4118a000-411a5507 } [111880]
  moving module 03 { 4109f000-4109f827 } -> { 41189000-41189827 } [2088]
  moving module 02 { 4106d000-4109e9bf } -> { 41157000-411889bf } [203200]
  moving module 01 { 41067000-4106cc67 } -> { 41151000-41156c67 } [23656]
  moving module 00 { 41016000-41066737 } -> { 41100000-41150737 } [329528]
  Loading fiasco
  found node 0 kernel info page (via ELF) at 0x40003000
  Loading sigma0
  Loading moe
  found node 0 kernel options (via ELF) at 0x40004000
  Sigma0 config    node: 0   ip:406003f4
  Roottask config  node: 0   ip:40641834
Regions of list 'regions'
    [ 40000000,  40000fff] {     1000} Root   mbi_rt
    [ 40001000,  40005847] {     4848} Kern   fiasco
    [ 40200000,  4040dfff] {   20e000} Kern   fiasco
    [ 40600000,  40609477] {     9478} Sigma0 sigma0
    [ 40640000,  4067c917] {    3c918} Root   moe
    [ 40f00000,  40ffffff] {   100000} Root   dtb
    [ 41015200,  41015b79] {      97a} Boot   modinfo
    [ 41189000,  429f7c01] {  186ec02} Root   Module
  Starting kernel fiasco at 40001198
Hello from Startup::stage2
Reserved 246 MiB as kernel memory.
GICv2
Number of IRQs available at this GIC: 288
Detecting PSCI ...
Detected PSCI v0.2
PSCI: TOS: Not present or not required.
ARM generic timer: freq=62500000 interval=62500 cnt=6407068
IOMMU: Initialize
SERIAL ESC: allocated IRQ 33 for serial uart
Not using serial hack in slow timer handler.
Welcome to the L4Re Microkernel!
L4Re Microkernel on arm-64
Rev: unknown compiled with gcc 12.2.1 20221203 [releases/gcc-12 revision c03cb4b762aceeba95da918b042583af0d9f6030] for QEMU Virtual Platform    []
Build: #2 Tue Oct 22 09:39:54 EEST 
Calibrating timer loop...
Timer calibration done.
MDB: use page size: 32
MDB: use page size: 30
MDB: use page size: 21
MDB: use page size: 12
SIGMA0: Hello!
  KIP @ 40003000
  allocated 4KB for maintenance structures
SIGMA0: Dump of all resource maps
RAM:------------------------
[4:RWX:40000000;40000fff]
[0:RWX:40006000;401fffff]
[0:RWX:4040e000;405fffff]
[0:RWX:4060a000;4063ffff]
[4:RWX:40640000;4067cfff]
[0:RWX:4067d000;40efffff]
[4:---:40f00000;40ffffff]
[0:RWX:41000000;41188fff]
[4:RWX:41189000;429f7fff]
[0:RWX:429f8000;1309fffff]
IOMEM:----------------------
[0:RW-:0;3fffffff]
[0:RW-:140000000;ffffffffffffffff]
MOE: Hello world
MOE: Fiasco mapdb not available! Memory cannot be given back!
MOE: found 3913948 KByte free memory
MOE: found RAM from 40006000 to 130a00000
MOE: allocated 3850 KByte for the page array @0x4067d000
MOE: virtual user address space [0-ffffffffff]
MOE: cmdline: moe rom/vm-basic-pci.cfg
MOE: rom name space cap -> [C:103000]
MOE: rwfs name space cap -> [C:105000]
  ROMFS: [41189000-41189828] [C:107000] vm-basic-pci.cfg
  ROMFS: [4118a000-411a5508] [C:109000] l4re
  ROMFS: [411a6000-4122e400] [C:10b000] ned
  ROMFS: [4122f000-41230219] [C:10d000] vmm.lua
  ROMFS: [41231000-414518d8] [C:10f000] io
  ROMFS: [41452000-41452465] [C:111000] pci.io
  ROMFS: [41453000-41544b80] [C:113000] uvmm
  ROMFS: [41545000-4154538a] [C:115000] virt-pci.dtb
  ROMFS: [41546000-428d9a00] [C:117000] linux
  ROMFS: [428da000-429f7c02] [C:119000] ramdisk.cpio.gz
  ROMFS: [40f00000-41000000] [C:11b000] .fdt
MOE: Starting: rom/ned rom/vm-basic-pci.cfg
MOE: loading 'rom/ned'
Ned says: Hi World!
Ned: loading file: 'rom/vm-basic-pci.cfg'
VMM: FATAL: Failed to determine command control attributes, CLI interface may be disabled
IO      | Io service
VMM[]: Created VCPU 0 @ 16000
VMM[GIC]: create ARM GICv2
IO      | Ready. Waiting for request.
VMM[vbus]: Showing vbus contents:
VMM[vbus]: L4ICU with 0 resources
VMM[vbus]: PCI with 0 resources
VMM[vbus]: pci_bus[1] with 5 resources
VMM[vbus]:  PIN_: 0x000000000024-0x000000000024 IRQ flags=3
VMM[vbus]:  BAR0: 0x000000000000-0x00000000001f Port flags=0
VMM[vbus]:  BAR1: 0x000010088000-0x000010088fff Mem flags=3
VMM[vbus]:  BAR4: 0x000010080000-0x000010083fff Mem flags=3
VMM[vbus]:  ROM_: 0x000010000000-0x00001007ffff Mem flags=3
VMM[vbus]: pci_bus[2] with 4 resources
VMM[vbus]:  PIN_: 0x000000000025-0x000000000025 IRQ flags=3
VMM[vbus]:  BAR0: 0x000000000080-0x0000000000ff Port flags=0
VMM[vbus]:  BAR1: 0x000010089000-0x000010089fff Mem flags=3
VMM[vbus]:  BAR4: 0x000010084000-0x000010087fff Mem flags=3
VMM[ASM]: Can not assign KDMA space to vBus (-2). No DMA capable devices configured.
VMM[main]: Hello out there.
VMM[ASM]: Sys Info:
	vBus:            1
	DMA devs:        0
	IO-MMU:          1
	Identity forced: 0
	DMA phys addr:   0
	DT dma-ranges:   0
VMM[ASM]: Operating mode: No DMA
VMM[ram]: RAM not set up for DMA.
VMM[ram]: RAM: @ 0x80000000 size=0xc0000000
VMM[ram]: RAM: VMM local mapping @ 0xc2000000
VMM[ram]: RAM: VM offset=0x42000000
VMM[main]: Loading kernel...
VMM[file]: load: @ 0x80000000
VMM[file]: copy in: to offset 0x0-0x13939ff
VMM[loader]: Linux kernel detected
Command line: console=hvc0 root=/sbin/init rw
VMM[main]: Loading ram disk...
VMM[ram]: load: rom/ramdisk.cpio.gz -> 0x13fe00000
VMM[file]: load: @ 0x13fe00000
VMM[file]: copy in: to offset 0xbfe00000-0xbff1dc01
VMM[main]: Loaded ramdisk image rom/ramdisk.cpio.gz to 13fe00000 (size: 0011dc02)
VMM[]: [email protected],virtiocap: capability net is invalid.
VMM[vm]: Device creation for virtual device virtio_net@10000 failed. Disabling device.
VMM[]: Create virtual console
VMM[guest]: New mmio mapping: @ 8000000 10000
VMM[GIC]: GIC [email protected] update: Adjusting GICC size from 10000 to 1000
VMM[GIC]: GIC [email protected] update: Stripping superfluous entries
VMM[guest]: New mmio mapping: @ 8010000 1000
VMM[guest]: New mmio mapping: @ 30020000 100
VMM[psci]: Register PSCI device: smc mode
VMM[guest]: New mmio mapping: @ 9020000 18
VMM[PCIe ctl]: Creating PCIe host bridge
VMM[PCIe ctl]: PCIe host bridge pcie@10000000 refers to invalid MSI controller: MSI parent is not an MSI controller
VMM[Pci_window_alloc]: Init PCI window with range [0x3eff0000, 0x3effffff IO]
VMM[Pci_window_alloc]: Init PCI window with range [0x10000000, 0x3efeffff MMIO32]
VMM[Pci_window_alloc]: Init PCI window with range [0x1000000000, 0x10ffffffff MMIO64]
VMM[PCI hbr]: Scanning PCI devices...
VMM[PCI hbr]: Found PCI device: name='pci_bus[1]', vendor/device=1af4:1000
VMM[PCI dev]:   bar[0] addr=0x0 size=0x20 type=io
VMM[PCI dev]:   bar[1] addr=0x10088000 size=0x1000 type=mmio32 (non-prefetchable)
VMM[PCI dev]:   bar[4] addr=0x10080000 size=0x4000 type=mmio64 (prefetchable)
VMM[Pci_bridge_windows]: [IO] allocated [0x3eff0000, 0x3eff001f]
VMM[HW PCI dev]:   bar[0] hw_addr=0x0 map_addr=0x3eff0000 size=0x20 type=io
VMM[Pci_bridge_windows]: [MMIO32] allocated [0x10000000, 0x10000fff]
VMM[HW PCI dev]:   bar[1] hw_addr=0x10088000 map_addr=0x10000000 size=0x1000 type=mmio32 (non-prefetchable)
VMM[Pci_bridge_windows]: [MMIO64] allocated [0x1000000000, 0x1000003fff]
VMM[HW PCI dev]:   bar[4] hw_addr=0x10080000 map_addr=0x1000000000 size=0x4000 type=mmio64 (prefetchable)
VMM[PCI dev]: Expansion ROM addr reg(0x30) as read from hardware: 0x0, size 0x0 (from hardware: 0x0)
VMM[HW PCI dev]: No MSI-X controller available for MSI-X device pci_bus[1] (devid=1).
VMM[DsAccMgr]: Attached memory [0x10088000, 0x10088fff] to 0x23000
VMM[irq_svr]: Irq 0x24 will be unmasked directly
VMM[PCIe ctl]:   IRQ mapping: 36 -> 36
VMM[PCI bus]: Registering PCI device 00:01.0
VMM[PCI hbr]: Found PCI device: name='pci_bus[2]', vendor/device=1af4:1001
VMM[PCI dev]:   bar[0] addr=0x80 size=0x80 type=io
VMM[PCI dev]:   bar[1] addr=0x10089000 size=0x1000 type=mmio32 (non-prefetchable)
VMM[PCI dev]:   bar[4] addr=0x10084000 size=0x4000 type=mmio64 (prefetchable)
VMM[Pci_bridge_windows]: [IO] allocated [0x3eff0080, 0x3eff00ff]
VMM[HW PCI dev]:   bar[0] hw_addr=0x80 map_addr=0x3eff0080 size=0x80 type=io
VMM[Pci_bridge_windows]: [MMIO32] allocated [0x10001000, 0x10001fff]
VMM[HW PCI dev]:   bar[1] hw_addr=0x10089000 map_addr=0x10001000 size=0x1000 type=mmio32 (non-prefetchable)
VMM[Pci_bridge_windows]: [MMIO64] allocated [0x1000004000, 0x1000007fff]
VMM[HW PCI dev]:   bar[4] hw_addr=0x10084000 map_addr=0x1000004000 size=0x4000 type=mmio64 (prefetchable)
VMM[PCI dev]: Expansion ROM addr reg(0x30) as read from hardware: 0x0, size 0x0 (from hardware: 0x0)
VMM[HW PCI dev]: No MSI-X controller available for MSI-X device pci_bus[2] (devid=2).
VMM[DsAccMgr]: Attached memory [0x10089000, 0x10089fff] to 0x25000
VMM[irq_svr]: Irq 0x25 will be unmasked directly
VMM[PCIe ctl]:   IRQ mapping: 37 -> 37
VMM[PCI bus]: Registering PCI device 00:02.0
VMM[PCI bus]: Registering PCI device 00:00.0
VMM[guest]: New mmio mapping: @ 4010000000 10000000
VMM[PCIe ctl]: Created & registered the PCIe host bridge
VMM[pl031]: Register Pl031 device
VMM[guest]: New mmio mapping: @ 9010000 1000
VMM[]: Create virtual pl011 console
VMM[guest]: New mmio mapping: @ 9000000 1000
VMM[]: flash@0: Failed to get property 'l4vmm,dscap': FDT_ERR_NOTFOUND
VMM[CFI]: Missing 'l4vmm,dscap' property!
VMM[vm]: Device creation for virtual device flash@0 failed. Disabling device.
VMM[Timer]: Guest timer frequency is 62500000
using (2/125), (8589934/29) to calculate timeouts
VMM[ioproxy]: No corresponding IO resource for 'virtio_mmio@a000000'.reg[0] (0xa000000-0xa0001ff).
VMM[vm]: Device creation for virtio_mmio@a000000 failed. Disabling device.
VMM[ioproxy]: No corresponding IO resource for 'virtio_mmio@a000200'.reg[0] (0xa000200-0xa0003ff).
VMM[vm]: Device creation for virtio_mmio@a000200 failed. Disabling device.
VMM[ioproxy]: No corresponding IO resource for 'virtio_mmio@a000400'.reg[0] (0xa000400-0xa0005ff).
VMM[vm]: Device creation for virtio_mmio@a000400 failed. Disabling device.
VMM[ioproxy]: No corresponding IO resource for 'virtio_mmio@a000600'.reg[0] (0xa000600-0xa0007ff).
VMM[vm]: Device creation for virtio_mmio@a000600 failed. Disabling device.
VMM[ioproxy]: No corresponding IO resource for 'virtio_mmio@a000800'.reg[0] (0xa000800-0xa0009ff).
VMM[vm]: Device creation for virtio_mmio@a000800 failed. Disabling device.
VMM[ioproxy]: No corresponding IO resource for 'virtio_mmio@a000a00'.reg[0] (0xa000a00-0xa000bff).
VMM[vm]: Device creation for virtio_mmio@a000a00 failed. Disabling device.
VMM[ioproxy]: No corresponding IO resource for 'virtio_mmio@a000c00'.reg[0] (0xa000c00-0xa000dff).
VMM[vm]: Device creation for virtio_mmio@a000c00 failed. Disabling device.
VMM[ioproxy]: No corresponding IO resource for 'virtio_mmio@a000e00'.reg[0] (0xa000e00-0xa000fff).
VMM[vm]: Device creation for virtio_mmio@a000e00 failed. Disabling device.
VMM[ioproxy]: No corresponding IO resource for 'virtio_mmio@a001000'.reg[0] (0xa001000-0xa0011ff).
VMM[vm]: Device creation for virtio_mmio@a001000 failed. Disabling device.
VMM[ioproxy]: No corresponding IO resource for 'virtio_mmio@a001200'.reg[0] (0xa001200-0xa0013ff).
VMM[vm]: Device creation for virtio_mmio@a001200 failed. Disabling device.
VMM[ioproxy]: No corresponding IO resource for 'virtio_mmio@a001400'.reg[0] (0xa001400-0xa0015ff).
VMM[vm]: Device creation for virtio_mmio@a001400 failed. Disabling device.
VMM[ioproxy]: No corresponding IO resource for 'virtio_mmio@a001600'.reg[0] (0xa001600-0xa0017ff).
VMM[vm]: Device creation for virtio_mmio@a001600 failed. Disabling device.
VMM[ioproxy]: No corresponding IO resource for 'virtio_mmio@a001800'.reg[0] (0xa001800-0xa0019ff).
VMM[vm]: Device creation for virtio_mmio@a001800 failed. Disabling device.
VMM[ioproxy]: No corresponding IO resource for 'virtio_mmio@a001a00'.reg[0] (0xa001a00-0xa001bff).
VMM[vm]: Device creation for virtio_mmio@a001a00 failed. Disabling device.
VMM[ioproxy]: No corresponding IO resource for 'virtio_mmio@a001c00'.reg[0] (0xa001c00-0xa001dff).
VMM[vm]: Device creation for virtio_mmio@a001c00 failed. Disabling device.
VMM[ioproxy]: No corresponding IO resource for 'virtio_mmio@a001e00'.reg[0] (0xa001e00-0xa001fff).
VMM[vm]: Device creation for virtio_mmio@a001e00 failed. Disabling device.
VMM[ioproxy]: No corresponding IO resource for 'virtio_mmio@a002000'.reg[0] (0xa002000-0xa0021ff).
VMM[vm]: Device creation for virtio_mmio@a002000 failed. Disabling device.
VMM[ioproxy]: No corresponding IO resource for 'virtio_mmio@a002200'.reg[0] (0xa002200-0xa0023ff).
VMM[vm]: Device creation for virtio_mmio@a002200 failed. Disabling device.
VMM[ioproxy]: No corresponding IO resource for 'virtio_mmio@a002400'.reg[0] (0xa002400-0xa0025ff).
VMM[vm]: Device creation for virtio_mmio@a002400 failed. Disabling device.
VMM[ioproxy]: No corresponding IO resource for 'virtio_mmio@a002600'.reg[0] (0xa002600-0xa0027ff).
VMM[vm]: Device creation for virtio_mmio@a002600 failed. Disabling device.
VMM[ioproxy]: No corresponding IO resource for 'virtio_mmio@a002800'.reg[0] (0xa002800-0xa0029ff).
VMM[vm]: Device creation for virtio_mmio@a002800 failed. Disabling device.
VMM[ioproxy]: No corresponding IO resource for 'virtio_mmio@a002a00'.reg[0] (0xa002a00-0xa002bff).
VMM[vm]: Device creation for virtio_mmio@a002a00 failed. Disabling device.
VMM[ioproxy]: No corresponding IO resource for 'virtio_mmio@a002c00'.reg[0] (0xa002c00-0xa002dff).
VMM[vm]: Device creation for virtio_mmio@a002c00 failed. Disabling device.
VMM[ioproxy]: No corresponding IO resource for 'virtio_mmio@a002e00'.reg[0] (0xa002e00-0xa002fff).
VMM[vm]: Device creation for virtio_mmio@a002e00 failed. Disabling device.
VMM[ioproxy]: No corresponding IO resource for 'virtio_mmio@a003000'.reg[0] (0xa003000-0xa0031ff).
VMM[vm]: Device creation for virtio_mmio@a003000 failed. Disabling device.
VMM[ioproxy]: No corresponding IO resource for 'virtio_mmio@a003200'.reg[0] (0xa003200-0xa0033ff).
VMM[vm]: Device creation for virtio_mmio@a003200 failed. Disabling device.
VMM[ioproxy]: No corresponding IO resource for 'virtio_mmio@a003400'.reg[0] (0xa003400-0xa0035ff).
VMM[vm]: Device creation for virtio_mmio@a003400 failed. Disabling device.
VMM[ioproxy]: No corresponding IO resource for 'virtio_mmio@a003600'.reg[0] (0xa003600-0xa0037ff).
VMM[vm]: Device creation for virtio_mmio@a003600 failed. Disabling device.
VMM[ioproxy]: No corresponding IO resource for 'virtio_mmio@a003800'.reg[0] (0xa003800-0xa0039ff).
VMM[vm]: Device creation for virtio_mmio@a003800 failed. Disabling device.
VMM[ioproxy]: No corresponding IO resource for 'virtio_mmio@a003a00'.reg[0] (0xa003a00-0xa003bff).
VMM[vm]: Device creation for virtio_mmio@a003a00 failed. Disabling device.
VMM[ioproxy]: No corresponding IO resource for 'virtio_mmio@a003c00'.reg[0] (0xa003c00-0xa003dff).
VMM[vm]: Device creation for virtio_mmio@a003c00 failed. Disabling device.
VMM[ioproxy]: No corresponding IO resource for 'virtio_mmio@a003e00'.reg[0] (0xa003e00-0xa003fff).
VMM[vm]: Device creation for virtio_mmio@a003e00 failed. Disabling device.
VMM[ioproxy]: No corresponding IO resource for 'pl061@9030000'.reg[0] (0x9030000-0x9030fff).
VMM[vm]: Device creation for pl061@9030000 failed. Disabling device.
VMM[ioproxy]: No corresponding IO resource for 'smmuv3@9050000'.reg[0] (0x9050000-0x906ffff).
VMM[vm]: Device creation for smmuv3@9050000 failed. Disabling device.
VMM[ioproxy]: No corresponding IO resource for 'pmu' IRQ 23.
VMM[vm]: Device creation for pmu failed. Disabling device.
VMM[ioproxy]: No corresponding IO resource for 'v2m@8020000'.reg[0] (0x8020000-0x8020fff).
VMM[vm]: Device creation for v2m@8020000 failed. Disabling device.
VMM[ram]: Cleaning caches for device tree [181ffd000-181fff3b0] ([13fffd000])
VMM[vmmap]: VM map:
VMM[vmmap]:  [ 8000000: 800ffff]: Dist_v2
VMM[vmmap]:  [ 8010000: 8010fff]: Gicc
VMM[vmmap]:  [ 9000000: 9000fff]: Pl011_mmio
VMM[vmmap]:  [ 9010000: 9010fff]: Pl031
VMM[vmmap]:  [ 9020000: 9020017]: Qemu_fw_if_mmio
VMM[vmmap]:  [30020000:300200ff]: Virtio_console_mmio
VMM[vmmap]:  [80000000:13fffffff]: Ram
VMM[vmmap]:  [4010000000:401fffffff]: Pci_bus_cfg_ecam
VMM[main]: Populating RAM of virtual machine
VMM[mmio]: 	Mapping [GICC] -> [8010000 - 8010fff]
VMM[mmio]: 	Mapping [22000 - 220ff] -> [30020000 - 300200ff]
VMM[mmio]: 	Mapping [c2000000 - 181ffffff] -> [80000000 - 13fffffff]
VMM[]: reschedule(): Initiating cpu startup for cap 0x419000/core 0
VMM[guest]: Powered up cpu0 [0x24620]
VMM[]: Starting Cpu0 @ 0x80000000 in 64Bit mode (handler @ 1078e70, stack: 801ffbb0, task: 420000, mpidr: 80000000 (orig: 80000000)
VMM[]: 80b73708: msr PMUSERENR_EL0 = 00000000 (ignored)
VMM[guest]: Invalid read from 0x8020008, ip 0xffffffc008e54870! Ignoring...
VMM[]: ffffffc008015a0c: msr OSDLR_EL1 = 00000000 (ignored)
VMM[]: ffffffc008015a10: msr OSLAR_EL1 = 00000000 (ignored)
VMM[]: ffffffc0080309dc: msr DBGBCR0_EL1 = 00000000 (ignored)
VMM[]: ffffffc008030a5c: msr DBGBVR0_EL1 = 00000000 (ignored)
VMM[]: ffffffc0080309d4: msr DBGBCR1_EL1 = 00000000 (ignored)
VMM[]: ffffffc008030a54: msr DBGBVR1_EL1 = 00000000 (ignored)
VMM[]: ffffffc0080309cc: msr DBGBCR2_EL1 = 00000000 (ignored)
VMM[]: ffffffc008030a4c: msr DBGBVR2_EL1 = 00000000 (ignored)
VMM[]: ffffffc0080309c4: msr DBGBCR3_EL1 = 00000000 (ignored)
VMM[]: ffffffc008030a44: msr DBGBVR3_EL1 = 00000000 (ignored)
VMM[]: ffffffc0080309bc: msr DBGBCR4_EL1 = 00000000 (ignored)
VMM[]: ffffffc008030a3c: msr DBGBVR4_EL1 = 00000000 (ignored)
VMM[]: ffffffc0080309b4: msr DBGBCR5_EL1 = 00000000 (ignored)
VMM[]: ffffffc008030a34: msr DBGBVR5_EL1 = 00000000 (ignored)
VMM[]: ffffffc0080308dc: msr DBGWCR0_EL1 = 00000000 (ignored)
VMM[]: ffffffc00803095c: msr DBGWVR0_EL1 = 00000000 (ignored)
VMM[]: ffffffc0080308d4: msr DBGWCR1_EL1 = 00000000 (ignored)
VMM[]: ffffffc008030954: msr DBGWVR1_EL1 = 00000000 (ignored)
VMM[]: ffffffc0080308cc: msr DBGWCR2_EL1 = 00000000 (ignored)
VMM[]: ffffffc00803094c: msr DBGWVR2_EL1 = 00000000 (ignored)
VMM[]: ffffffc0080308c4: msr DBGWCR3_EL1 = 00000000 (ignored)
VMM[]: ffffffc008030944: msr DBGWVR3_EL1 = 00000000 (ignored)
VMM[HW PCI dev]: Register MSI-X MMIO table: [0x10000000, 0x1000002f]
VMM[HW PCI dev]: Register MMIO region in MSI-X bar: [0x10000030, 0x10000fff]
VMM[HW PCI dev]: Register MMIO region: [0x1000000000, 0x1000003fff], vbus base 0x10080000
VMM[HW PCI dev]: Register MSI-X MMIO table: [0x10001000, 0x1000101f]
VMM[HW PCI dev]: Register MMIO region in MSI-X bar: [0x10001020, 0x10001fff]
VMM[HW PCI dev]: Register MMIO region: [0x1000004000, 0x1000007fff], vbus base 0x10084000
VQ[0x21110]: num=256 d:0x1421e8000 a:0x1421e9000 u:0x1421ea000
VQ[0x21158]: num=256 d:0x1421ec000 a:0x1421ed000 u:0x1421ee000
[    2.416955] cacheinfo: Unable to detect cache hierarchy for CPU 0
[    2.458225] brd: module loaded
[    2.466080] virtio_blk virtio2: [vda] 22922 512-byte logical blocks (11.7 MB/11.2 MiB)