Re: Upgrade issues. VM won't start.
Matthias Lange <[email protected]> Fri, 9 May 2025 18:57:43 +0200
| Newsgroups | gmane.comp.micro-kernel.l4.devel |
|---|---|
| Message-ID | <aB40B3DDVtU0mQVw@hyperion> |
Hi Richard, On [08-05-2025 17:16], Richard Clark wrote: > Adam, >=20 > Same crash with just one vm. > Yes, -cpu host. > Intel 12th Gen i3-1220P=20 Can you send me (to my personal email) an exportpack of your setup? You can create the exportpack in your build directory with make exportpack EXPORTPACKTARGETDIR=3D/path/to/dir E=3D<YOUR_ENTRY> Then archive /path/to/dir and send it to me please. Best, Matthias. >=20 >=20 > Richard >=20 >=20 > -----Original Message----- > From: Adam Lackorzynski <[email protected]>=20 > Sent: Thursday, May 8, 2025 11:19 AM > To: Richard Clark <[email protected]>; [email protected].= tu-dresden.de > Cc: Bud Wykoff <[email protected]>; Douglas Schafer <douglas= [email protected]> > Subject: Re: Upgrade issues. VM won't start. >=20 > Hi Richard, >=20 > is it working with just one VM? And is it QEMU with "-cpu host"? And if y= es, what's the host CPU if I may ask? >=20 >=20 >=20 > Adam >=20 > On Mon May 05, 2025 at 13:01:55 +0000, Richard Clark wrote: > > Adam, > >=20 > > I did another ham sync, rebuilt fiasco, rebuilt l4, rebuilt my=20 > > natives, and it's a little better? Now the VMs crash, but at least the = > > system keeps running and I can seem my natives printing even after both= VMs are halted. > > So at least the whole system doesn't crash any more. Just the VMs. > >=20 > > Again, yes, Debian Linux on QEMU with kvm and six cores.=20 > > Cores 0 and 1 are for L4 and natives, cores 2 and 3 are for vm1, cores = 4 and 5 are for vm2. > >=20 > > Please see attached! > >=20 > >=20 > > Richard > >=20 > >=20 > >=20 > >=20 > > -----Original Message----- > > From: Adam Lackorzynski <[email protected]> > > Sent: Sunday, May 4, 2025 11:11 AM > > To: Richard Clark <[email protected]>;=20 > > [email protected] > > Cc: Bud Wykoff <[email protected]>; Douglas Schafer=20 > > <[email protected]> > > Subject: Re: Upgrade issues. VM won't start. > >=20 > > Richard, > >=20 > > is that setup running on Linux QEMU+KVM? If yes, we recently (really a = few days ago) fixed an issue in this virtualized setup (wrt to performance = counter handling). It's on GH since Friday I believe. > > Otherwise please provide me you fiasco binary, such that I can look up > > fffffffff006a176 as this will point to the location that triggered the = issue. > >=20 > > Thanks, Adam > >=20 > > On Sun May 04, 2025 at 13:14:00 +0000, Richard Clark wrote: > > > Adam, > > >=20 > > > So I have been using version 23.10.1, built as per the download=20 > > > page, and have gotten a couple VMs to ping eachother and give me a=20 > > > login prompt. I finally realized I was missing the virtio_switch=20 > > > package and grabbed it from github and put it where it is supposed=20 > > > to go. Of course, being a version mismatch now, it did not compile.=20 > > > I decide to bite the bullet and do an upgrade (always a mistake) and = > > > use the new build process given with the new website. That went=20 > > > smoothly! I install ham, run it, etc, everything builds, I update my = local scripts and links to use the new environment variables instead of bei= ng hardcoded, and it all builds and looks good. Except that it doesn't run.= The VMs get a memory exception and kick into jdb. > > >=20 > > > I have not changed any of my .cfg or .list files. The VMs and ramdisk= s are untouched. > > > My local (L4 native) processes start and appear to run. But the VMs c= rash for some reason. > > > Even the device tree is unchanged. I also tried a newly built linux (= as opposed to a prebuilt) and that failed as well. > > >=20 > > > Is there some reason for this new crash between version 23.10.1 and t= he latest version from github? > > > I've attached the VM startup output from both the old and new runs so= you can take a look. > > >=20 > > > I'm so close... I see the IP configuration parameter and how to set u= p lwip and virtio_switch.... > > > Then my natives should be able to talk directly to my linuxes. > > >=20 > > >=20 > > > Your help is greatly appreciated! > > >=20 > > >=20 > > > Richard > > >=20 > >=20 > > > vm1 | VMM: Created VCPU 0 @ 17000 > > > vm1 | VMM[vmbus]: 'vbus' capability not found. Hardware access no= t possible for VM. > > > vm1 | VMM[main]: Hello out there. > > > vm1 | VMM[ASM]: Sys Info: > > > vm1 | vBus: 0 > > > vm1 | DMA devs: 0 > > > vm1 | IO-MMU: 0 > > > vm1 | Identity forced: 0 > > > vm1 | DMA phys addr: 0 > > > vm1 | DT dma-ranges: 0 > > > vm1 | VMM[ASM]: Operating mode: No DMA > > > vm1 | VMM[ram]: RAM not set up for DMA. > > > vm2 | VMM: Created VCPU 0 @ 17000 > > > vm2 | VMM[vmbus]: 'vbus' capability not found. Hardware access no= t possible for VM. > > > vm2 | VMM[main]: Hello out there. > > > vm2 | VMM[ASM]: Sys Info: > > > vm2 | vBus: 0 > > > vm2 | DMA devs: 0 > > > vm2 | IO-MMU: 0 > > > vm2 | Identity forced: 0 > > > vm1 | VMM[ram]: RAM: @ 0x0 size=3D0x20000000 > > > vm2 | DMA phys addr: 0 > > > vm1 | VMM[ram]: RAM: VMM local mapping @ 0x1000000 > > > vm2 | DT dma-ranges: 0 > > > vm1 | VMM[ram]: RAM: VM offset=3D0x1000000 > > > vm2 | VMM[ASM]: Operating mode: No DMA > > > vm1 | VMM[main]: Loading kernel... > > > vm2 | VMM[ram]: RAM not set up for DMA. > > > vm1 | VMM[loader]: Linux kernel detected > > > vm1 | VMM[file]: load: @ 0xfc400 > > > vm1 | VMM[file]: copy in: to offset 0xfc400-0xba989f > > > vm1 | VMM[main]: Loading ram disk... > > > vm1 | VMM[ram]: load: rom/ramdisk1-amd64.rd -> 0x1fc00000 > > > vm1 | VMM[file]: load: @ 0x1fc00000 > > > vm1 | VMM[file]: copy in: to offset 0x1fc00000-0x1fffffff > > > vm1 | VMM[main]: Loaded ramdisk image rom/ramdisk1-amd64.rd to 1f= c00000 (size: 00400000) > > > vm1 | VMM[PIC]: Hello, Legacy_pic > > > vm2 | VMM[ram]: RAM: @ 0x0 size=3D0x20000000 > > > vm2 | VMM[ram]: RAM: VMM local mapping @ 0x1000000 > > > vm2 | VMM[ram]: RAM: VM offset=3D0x1000000 > > > vm2 | VMM[main]: Loading kernel... > > > vm1 | VMM: acpi_platform: Failed to get property 'l4vmm,pwrinput'= : FDT_ERR_NOTFOUND > > > vm2 | VMM[loader]: Linux kernel detected > > > vm1 | VMM: Creating Acpi_platform > > > vm2 | VMM[file]: load: @ 0xfc400 > > > vm2 | VMM[file]: copy in: to offset 0xfc400-0xba989f > > > vm1 | VMM[ACPI]: Acpi timer @ 0xb008 > > > vm1 | VMM[RTC]: Hello from RTC. Irq=3D8 > > > vm2 | VMM[main]: Loading ram disk... > > > vm1 | VMM[uart_8250]: Create virtual 8250 console > > > vm2 | VMM[ram]: load: rom/ramdisk2-amd64.rd -> 0x1fc00000 > > > vm2 | VMM[file]: load: @ 0x1fc00000 > > > vm2 | VMM[file]: copy in: to offset 0x1fc00000-0x1fffffff > > > vm2 | VMM[main]: Loaded ramdisk image rom/ramdisk2-amd64.rd to 1f= c00000 (size: 00400000) > > > vm1 | VMM: l4rtc.l4vmm,rtccap: capability rtc is invalid. > > > vm1 | VMM[RTC]: l4vmm,rtccap not valid. Will not have wallclock t= ime. > > > vm1 | VMM[vm]: Device creation for virtual device l4rtc failed. D= isabling device. > > > vm1 | VMM: isa_debugport.l4vmm,vcon_cap: capability debug is inva= lid. > > > vm1 | VMM[vm]: Device creation for virtual device isa_debugport f= ailed. Disabling device. > > > vm2 | VMM[PIC]: Hello, Legacy_pic > > > vm1 | VMM[PCI bus]: Creating host bridge > > > vm1 | VMM[Pci_window_alloc]: Init PCI window with range [0x6000, = 0xffff IO] > > > vm1 | VMM[Pci_window_alloc]: Init PCI window with range [0xaa0000= 00, 0xaaffffff MMIO32] > > > vm1 | VMM[Pci_window_alloc]: Init PCI window with range [0x300000= 000, 0x3ffffffff MMIO64] > > > vm1 | VMM[PCI bus]: Registering PCI device 00:00.0 > > > vm2 | VMM: acpi_platform: Failed to get property 'l4vmm,pwrinput'= : FDT_ERR_NOTFOUND > > > vm2 | VMM: Creating Acpi_platform > > > vm1 | VMM[guest]: New mmio mapping: @ b0000000 10000000 > > > vm1 | VMM[PCI bus]: Created & Registered the PCI host bridge > > > vm2 | VMM[ACPI]: Acpi timer @ 0xb008 > > > vm2 | VMM[RTC]: Hello from RTC. Irq=3D8 > > > vm1 | VMM[VIO Cons]: Create virtual PCI console > > > vm2 | VMM[uart_8250]: Create virtual 8250 console > > > vm1 | VMM[Pci_bridge_windows]: [MMIO32] allocated [0xaa000000, 0x= aa001fff] > > > vm1 | VMM[Virt PCI dev]: bar[0] addr=3D0x0 size=3D0x2000 type= =3Dmmio32 (non-prefetchable) > > > vm1 | VMM[Pci_bridge_windows]: [IO] allocated [0x6000, 0x607f] > > > vm1 | VMM[Virt PCI dev]: bar[1] addr=3D0x0 size=3D0x80 type=3Dio > > > vm2 | VMM: l4rtc.l4vmm,rtccap: capability rtc is invalid. > > > vm2 | VMM[RTC]: l4vmm,rtccap not valid. Will not have wallclock t= ime. > > > vm1 | VMM[PCI bus]: Registering PCI device 00:01.0 > > > vm2 | VMM[vm]: Device creation for virtual device l4rtc failed. D= isabling device. > > > vm1 | VMM[VIO Cons]: Console: 0x186b0 > > > vm1 | VMM[VIO proxy]: Creating proxy > > > vm2 | VMM: isa_debugport.l4vmm,vcon_cap: capability debug is inva= lid. > > > vm2 | VMM[vm]: Device creation for virtual device isa_debugport f= ailed. Disabling device. > > > vm1 | VMM[Pci_bridge_windows]: [MMIO32] allocated [0xaa002000, 0x= aa003fff] > > > vm1 | VMM[Virt PCI dev]: bar[0] addr=3D0x0 size=3D0x2000 type= =3Dmmio32 (non-prefetchable) > > > vm1 | VMM[Pci_bridge_windows]: [IO] allocated [0x6080, 0x60ff] > > > vm1 | VMM[Virt PCI dev]: bar[1] addr=3D0x0 size=3D0x80 type=3Dio > > > p2p | Registering dataspace from 0x0 with 524288 KiB, offset 0x0 > > > p2p | PORT[0x15d70]: DMA guest [0-1fffffff] local [600000-205fff= ff] offset 0 > > > vm2 | VMM[PCI bus]: Creating host bridge > > > p2p | register client: host IRQ: 420010 config DS: 41d000 > > > vm2 | VMM[Pci_window_alloc]: Init PCI window with range [0x6000, = 0xffff IO] > > > vm2 | VMM[Pci_window_alloc]: Init PCI window with range [0xaa0000= 00, 0xaaffffff MMIO32] > > > vm2 | VMM[Pci_window_alloc]: Init PCI window with range [0x300000= 000, 0x3ffffffff MMIO64] > > > vm2 | VMM[PCI bus]: Registering PCI device 00:00.0 > > > vm1 | VMM[PCI bus]: Registering PCI device 00:02.0 > > > vm1 | VMM[VIO proxy]: Creating proxy > > > vm1 | VMM: [email protected],virtiocap: capability qdrv is inva= lid. > > > vm1 | VMM[vm]: Device creation for virtual device virtio_disk@2 f= ailed. Disabling device. > > > vm2 | VMM[guest]: New mmio mapping: @ b0000000 10000000 > > > vm1 | VMM: [email protected],dscap: capability bios_code is inva= lid. > > > vm2 | VMM[PCI bus]: Created & Registered the PCI host bridge > > > vm1 | VMM[ROM]: Missing 'l4vmm,dscap' property! > > > vm1 | VMM[vm]: Device creation for virtual device rom@ffc84000 fa= iled. Disabling device. > > > vm2 | VMM[VIO Cons]: Create virtual PCI console > > > vm1 | VMM: [email protected],dscap: capability bios_vars is inva= lid. > > > vm1 | VMM[CFI]: Missing 'l4vmm,dscap' property! > > > vm1 | VMM[vm]: Device creation for virtual device nvm@ffc00000 fa= iled. Disabling device. > > > vm2 | VMM[Pci_bridge_windows]: [MMIO32] allocated [0xaa000000, 0x= aa001fff] > > > vm2 | VMM[Virt PCI dev]: bar[0] addr=3D0x0 size=3D0x2000 type= =3Dmmio32 (non-prefetchable) > > > vm2 | VMM[Pci_bridge_windows]: [IO] allocated [0x6000, 0x607f] > > > vm2 | VMM[Virt PCI dev]: bar[1] addr=3D0x0 size=3D0x80 type=3Dio > > > vm2 | VMM[PCI bus]: Registering PCI device 00:01.0 > > > vm1 | VMM: Created VCPU 1 @ 23000 > > > vm2 | VMM[VIO Cons]: Console: 0x186b0 > > > vm1 | VMM[ram]: Cleaning caches for device tree [20bfe000-20bffb8= 0] ([1fbfe000]) > > > vm2 | VMM[VIO proxy]: Creating proxy > > > vm1 | VMM: reschedule(): Initiating cpu startup for cap 0x418000/= core 0 > > > vm2 | VMM[Pci_bridge_windows]: [MMIO32] allocated [0xaa002000, 0x= aa003fff] > > > vm2 | VMM[Virt PCI dev]: bar[0] addr=3D0x0 size=3D0x2000 type= =3Dmmio32 (non-prefetchable) > > > vm2 | VMM[Pci_bridge_windows]: [IO] allocated [0x6080, 0x60ff] > > > vm2 | VMM[Virt PCI dev]: bar[1] addr=3D0x0 size=3D0x80 type=3Dio > > > p2p | Registering dataspace from 0x0 with 524288 KiB, offset 0x0 > > > p2p | PORT[0x15e80]: DMA guest [0-1fffffff] local [20600000-405f= ffff] offset 0 > > > p2p | register client: host IRQ: 420010 config DS: 41e000 > > > vm1 | VMM[ACPI]: Initialize legacy BIOS ACPI tables. > > > vm2 | VMM[PCI bus]: Registering PCI device 00:02.0 > > > vm1 | VMM: Zeropage @ 0x1000, Kernel @ 0xfc400 > > > vm2 | VMM[VIO proxy]: Creating proxy > > > vm1 | VMM: Cmd_line: console=3Dhvc0 ramdisk_size=3D10000 root=3D/= dev/ram0 rw > > > vm2 | VMM: [email protected],virtiocap: capability qdrv is inva= lid. > > > vm1 | VMM: cmdline check: console=3Dhvc0 ramdisk_size=3D10000 roo= t=3D/dev/ram0 rw > > > vm2 | VMM[vm]: Device creation for virtual device virtio_disk@2 f= ailed. Disabling device. > > > vm1 | VMM[vmmap]: VM map: > > > vm1 | VMM[vmmap]: [ 0:1fffffff]: Ram > > > vm1 | VMM[vmmap]: [b0000000:bfffffff]: Pci_bus_cfg_ecam > > > vm2 | VMM: [email protected],dscap: capability bios_code is inva= lid. > > > vm1 | VMM[vmmap]: [fec00000:fec00fff]: Ioapic > > > vm2 | VMM[ROM]: Missing 'l4vmm,dscap' property! > > > vm1 | VMM[vmmap]: [fee00000:fee00fff]: Lapic_access_handler > > > vm2 | VMM[vm]: Device creation for virtual device rom@ffc84000 fa= iled. Disabling device. > > > vm1 | VMM[main]: Populating guest physical address space > > > vm1 | VMM[mmio]: Mapping [1000000 - 20ffffff] -> [0 - 1fffffff] > > > vm2 | VMM: [email protected],dscap: capability bios_vars is inva= lid. > > > vm1 | VMM[vmmap]: IOport map: > > > vm2 | VMM[CFI]: Missing 'l4vmm,dscap' property! > > > vm1 | VMM[vmmap]: [ 20: 21]: PIC > > > vm2 | VMM[vm]: Device creation for virtual device nvm@ffc00000 fa= iled. Disabling device. > > > vm1 | VMM[vmmap]: [ 40: 43]: PIT > > > vm1 | VMM[vmmap]: [ 61: 61]: PIT port 61 > > > vm1 | VMM[vmmap]: [ 70: 71]: RTC > > > vm1 | VMM[vmmap]: [ a0: a1]: PIC > > > vm1 | VMM[vmmap]: [ 3f8: 3ff]: UART 8250 > > > vm1 | VMM[vmmap]: [ 510: 51b]: Firmware interface > > > vm1 | VMM[vmmap]: [ cf8: cff]: PCI bus cfg > > > vm1 | VMM[vmmap]: [1800:1808]: ACPI platform > > > vm2 | VMM: Created VCPU 1 @ 23000 > > > vm1 | VMM[vmmap]: [b008:b008]: ACPI Timer > > > vm2 | VMM[ram]: Cleaning caches for device tree [20bfe000-20bffb8= 0] ([1fbfe000]) > > > vm1 | VMM[guest]: Starting VMM @ 0x100000 > > > vm2 | VMM: reschedule(): Initiating cpu startup for cap 0x418000/= core 0 > > > vm1 | VMM[Cpu_dev]: [ 0] Reset called > > > vm1 | VMM[Cpu_dev]: [ 0] Resetting vCPU. > > > vm1 | VMM: Hello clock source for vCPU 0 > > >=20 > > > -----------------------------------------------------------------= ---- =20 > > > CPU 2 [fffffffff006a176]: General Protection (ERR=3D0000000000000= 000) > > > CPU(s) 0-5 entered JDB > > > jdb:=20 > > >=20 >=20 > > Created vcon channel: vm1 [426010] > > cons>=20 > > Created vcon channel: vm2 [427010] > > cons>=20 > > vm1 | VMM: Created VCPU 0 @ 17000 > > vm1 | VMM[vmbus]: 'vbus' capability not found. Hardware access not = possible for VM. > > vm1 | VMM[main]: Hello out there. > > vm1 | VMM[ASM]: Sys Info: > > vm1 | vBus: 0 > > vm1 | DMA devs: 0 > > vm1 | IO-MMU: 0 > > vm1 | Identity forced: 0 > > vm1 | DMA phys addr: 0 > > vm1 | DT dma-ranges: 0 > > vm1 | VMM[ASM]: Operating mode: No DMA > > vm1 | VMM[ram]: RAM not set up for DMA. > > vm2 | VMM: Created VCPU 0 @ 17000 > > vm2 | VMM[vmbus]: 'vbus' capability not found. Hardware access not = possible for VM. > > vm2 | VMM[main]: Hello out there. > > vm1 | VMM[ram]: RAM: @ 0x0 size=3D0x20000000 > > vm1 | VMM[ram]: RAM: VMM local mapping @ 0x1000000 > > vm1 | VMM[ram]: RAM: VM offset=3D0x1000000 > > vm2 | VMM[ASM]: Sys Info: > > vm2 | vBus: 0 > > vm1 | VMM[main]: Loading kernel... > > vm2 | DMA devs: 0 > > vm2 | IO-MMU: 0 > > vm2 | Identity forced: 0 > > vm2 | DMA phys addr: 0 > > vm2 | DT dma-ranges: 0 > > vm2 | VMM[ASM]: Operating mode: No DMA > > vm1 | VMM[loader]: Elf image detected > > vm2 | VMM[ram]: RAM not set up for DMA. > > vm1 | VMM[bin]: Copy in ELF binary section @0x1000000 from 0x200000= /0x18aef10 > > vm1 | VMM[bin]: Copy in ELF binary section @0x2a00000 from 0x1c0000= 0/0x814000 > > vm1 | VMM[bin]: Copy in ELF binary section @0x3214000 from 0x260000= 0/0x2ece8 > > vm1 | VMM[bin]: Copy in ELF binary section @0x3243000 from 0x264300= 0/0x288000 > > vm1 | VMM[main]: Loading ram disk... > > vm1 | VMM[ram]: load: rom/ramdisk1-amd64.rd -> 0x1fc00000 > > vm1 | VMM[file]: load: @ 0x1fc00000 > > vm1 | VMM[file]: copy in: to offset 0x1fc00000-0x1fffffff > > vm1 | VMM[main]: Loaded ramdisk image rom/ramdisk1-amd64.rd to 1fc0= 0000 (size: 00400000) > > vm2 | VMM[ram]: RAM: @ 0x0 size=3D0x20000000 > > vm2 | VMM[ram]: RAM: VMM local mapping @ 0x1000000 > > vm2 | VMM[ram]: RAM: VM offset=3D0x1000000 > > vm2 | VMM[main]: Loading kernel... > > vm1 | VMM[PIC]: Hello, Legacy_pic > > vm2 | VMM[loader]: Elf image detected > > vm2 | VMM[bin]: Copy in ELF binary section @0x1000000 from 0x200000= /0x18aef10 > > vm2 | VMM[bin]: Copy in ELF binary section @0x2a00000 from 0x1c0000= 0/0x814000 > > vm2 | VMM[bin]: Copy in ELF binary section @0x3214000 from 0x260000= 0/0x2ece8 > > vm2 | VMM[bin]: Copy in ELF binary section @0x3243000 from 0x264300= 0/0x288000 > > vm2 | VMM[main]: Loading ram disk... > > vm1 | VMM: acpi_platform: Failed to get property 'l4vmm,pwrinput': = FDT_ERR_NOTFOUND > > vm2 | VMM[ram]: load: rom/ramdisk2-amd64.rd -> 0x1fc00000 > > vm2 | VMM[file]: load: @ 0x1fc00000 > > vm2 | VMM[file]: copy in: to offset 0x1fc00000-0x1fffffff > > vm1 | VMM: Creating Acpi_platform > > vm2 | VMM[main]: Loaded ramdisk image rom/ramdisk2-amd64.rd to 1fc0= 0000 (size: 00400000) > > vm1 | VMM[ACPI]: Acpi timer @ 0xb008 > > vm1 | VMM[RTC]: Hello from RTC. Irq=3D8 > > vm1 | VMM[uart_8250]: Create virtual 8250 console > > vm1 | VMM: l4rtc.l4vmm,rtccap: capability rtc is invalid. > > vm1 | VMM[RTC]: l4vmm,rtccap not valid. Will not have wallclock tim= e. > > vm2 | VMM[PIC]: Hello, Legacy_pic > > vm1 | VMM[vm]: Device creation for virtual device l4rtc failed. Dis= abling device. > > vm1 | VMM: isa_debugport.l4vmm,vcon_cap: capability debug is invali= d. > > vm1 | VMM[vm]: Device creation for virtual device isa_debugport fai= led. Disabling device. > > vm2 | VMM: acpi_platform: Failed to get property 'l4vmm,pwrinput': = FDT_ERR_NOTFOUND > > vm2 | VMM: Creating Acpi_platform > > vm1 | VMM[PCI bus]: Creating host bridge > > vm2 | VMM[ACPI]: Acpi timer @ 0xb008 > > vm1 | VMM[Pci_window_alloc]: Init PCI window with range [0x6000, 0x= ffff IO] > > vm1 | VMM[Pci_window_alloc]: Init PCI window with range [0xaa000000= , 0xaaffffff MMIO32] > > vm2 | VMM[RTC]: Hello from RTC. Irq=3D8 > > vm1 | VMM[Pci_window_alloc]: Init PCI window with range [0x30000000= 0, 0x3ffffffff MMIO64] > > vm2 | VMM[uart_8250]: Create virtual 8250 console > > vm1 | VMM[PCI bus]: Registering PCI device 00:00.0 > > vm1 | VMM[guest]: New mmio mapping: @ b0000000 10000000 > > vm1 | VMM[PCI bus]: Created & Registered the PCI host bridge > > vm1 | VMM[VIO Cons]: Create virtual PCI console > > vm2 | VMM: l4rtc.l4vmm,rtccap: capability rtc is invalid. > > vm2 | VMM[RTC]: l4vmm,rtccap not valid. Will not have wallclock tim= e. > > vm2 | VMM[vm]: Device creation for virtual device l4rtc failed. Dis= abling device. > > vm2 | VMM: isa_debugport.l4vmm,vcon_cap: capability debug is invali= d. > > vm2 | VMM[vm]: Device creation for virtual device isa_debugport fai= led. Disabling device. > > vm1 | VMM[Pci_bridge_windows]: [MMIO32] allocated [0xaa000000, 0xaa= 001fff] > > vm1 | VMM[Virt PCI dev]: bar[0] addr=3D0x0 size=3D0x2000 type=3Dm= mio32 (non-prefetchable) > > vm1 | VMM[Pci_bridge_windows]: [IO] allocated [0x6000, 0x607f] > > vm1 | VMM[Virt PCI dev]: bar[1] addr=3D0x0 size=3D0x80 type=3Dio > > vm1 | VMM[PCI bus]: Registering PCI device 00:01.0 > > vm1 | VMM[VIO Cons]: Console: 0x186b0 > > vm1 | VMM[VIO proxy]: Creating proxy > > vm2 | VMM[PCI bus]: Creating host bridge > > vm1 | VMM[Pci_bridge_windows]: [MMIO32] allocated [0xaa002000, 0xaa= 003fff] > > vm1 | VMM[Virt PCI dev]: bar[0] addr=3D0x0 size=3D0x2000 type=3Dm= mio32 (non-prefetchable) > > vm1 | VMM[Pci_bridge_windows]: [IO] allocated [0x6080, 0x60ff] > > vm1 | VMM[Virt PCI dev]: bar[1] addr=3D0x0 size=3D0x80 type=3Dio > > p2p | Registering dataspace from 0x0 with 524288 KiB, offset 0x0 > > vm2 | VMM[Pci_window_alloc]: Init PCI window with range [0x6000, 0x= ffff IO] > > vm2 | VMM[Pci_window_alloc]: Init PCI window with range [0xaa000000= , 0xaaffffff MMIO32] > > vm2 | VMM[Pci_window_alloc]: Init PCI window with range [0x30000000= 0, 0x3ffffffff MMIO64] > > p2p | PORT[0x15d70]: DMA guest [0-1fffffff] local [600000-205fffff= ] offset 0 > > vm2 | VMM[PCI bus]: Registering PCI device 00:00.0 > > vm2 | VMM[guest]: New mmio mapping: @ b0000000 10000000 > > vm2 | VMM[PCI bus]: Created & Registered the PCI host bridge > > p2p | register client: host IRQ: 420010 config DS: 41d000 > > vm2 | VMM[VIO Cons]: Create virtual PCI console > > vm1 | VMM[PCI bus]: Registering PCI device 00:02.0 > > vm1 | VMM[VIO proxy]: Creating proxy > > vm1 | VMM: [email protected],virtiocap: capability qdrv is invali= d. > > vm1 | VMM[vm]: Device creation for virtual device virtio_disk@2 fai= led. Disabling device. > > vm2 | VMM[Pci_bridge_windows]: [MMIO32] allocated [0xaa000000, 0xaa= 001fff] > > vm2 | VMM[Virt PCI dev]: bar[0] addr=3D0x0 size=3D0x2000 type=3Dm= mio32 (non-prefetchable) > > vm2 | VMM[Pci_bridge_windows]: [IO] allocated [0x6000, 0x607f] > > vm1 | VMM: [email protected],dscap: capability bios_code is invali= d. > > vm2 | VMM[Virt PCI dev]: bar[1] addr=3D0x0 size=3D0x80 type=3Dio > > vm1 | VMM[ROM]: Missing 'l4vmm,dscap' property! > > vm1 | VMM[vm]: Device creation for virtual device rom@ffc84000 fail= ed. Disabling device. > > vm2 | VMM[PCI bus]: Registering PCI device 00:01.0 > > vm2 | VMM[VIO Cons]: Console: 0x186b0 > > vm1 | VMM: [email protected],dscap: capability bios_vars is invali= d. > > vm1 | VMM[CFI]: Missing 'l4vmm,dscap' property! > > vm1 | VMM[vm]: Device creation for virtual device nvm@ffc00000 fail= ed. Disabling device. > > vm2 | VMM[VIO proxy]: Creating proxy > > vm2 | VMM[Pci_bridge_windows]: [MMIO32] allocated [0xaa002000, 0xaa= 003fff] > > vm2 | VMM[Virt PCI dev]: bar[0] addr=3D0x0 size=3D0x2000 type=3Dm= mio32 (non-prefetchable) > > vm2 | VMM[Pci_bridge_windows]: [IO] allocated [0x6080, 0x60ff] > > vm2 | VMM[Virt PCI dev]: bar[1] addr=3D0x0 size=3D0x80 type=3Dio > > p2p | Registering dataspace from 0x0 with 524288 KiB, offset 0x0 > > vm1 | VMM: Created VCPU 1 @ 23000 > > vm1 | VMM[ram]: Cleaning caches for device tree [20bfe000-20bffb80]= ([1fbfe000]) > > vm1 | VMM: reschedule(): Initiating cpu startup for cap 0x418000/co= re 0 > > p2p | PORT[0x15e80]: DMA guest [0-1fffffff] local [20600000-405fff= ff] offset 0 > > p2p | register client: host IRQ: 420010 config DS: 41e000 > > vm2 | VMM[PCI bus]: Registering PCI device 00:02.0 > > vm2 | VMM[VIO proxy]: Creating proxy > > vm2 | VMM: [email protected],virtiocap: capability qdrv is invali= d. > > vm2 | VMM[vm]: Device creation for virtual device virtio_disk@2 fai= led. Disabling device. > > vm2 | VMM: [email protected],dscap: capability bios_code is invali= d. > > vm2 | VMM[ROM]: Missing 'l4vmm,dscap' property! > > vm2 | VMM[vm]: Device creation for virtual device rom@ffc84000 fail= ed. Disabling device. > > vm2 | VMM: [email protected],dscap: capability bios_vars is invali= d. > > vm2 | VMM[CFI]: Missing 'l4vmm,dscap' property! > > vm2 | VMM[vm]: Device creation for virtual device nvm@ffc00000 fail= ed. Disabling device. > > vm1 | VMM[ACPI]: Initialize legacy BIOS ACPI tables. > > vm1 | VMM: Zeropage @ 0x1000, Kernel @ 0x1000000 > > vm1 | VMM: Cmd_line: console=3Dhvc0 ramdisk_size=3D10000 root=3D/de= v/ram0 rw > > vm2 | VMM: Created VCPU 1 @ 23000 > > vm1 | VMM: Elf guest zeropage: dtb 0x1fbfdff0, entry 0x1000000 > > vm2 | VMM[ram]: Cleaning caches for device tree [20bfe000-20bffb80]= ([1fbfe000]) > > vm1 | VMM: cmdline check: console=3Dhvc0 ramdisk_size=3D10000 root= =3D/dev/ram0 rw > > vm2 | VMM: reschedule(): Initiating cpu startup for cap 0x418000/co= re 0 > > vm1 | VMM[vmmap]: VM map: > > vm1 | VMM[vmmap]: [ 0:1fffffff]: Ram > > vm1 | VMM[vmmap]: [b0000000:bfffffff]: Pci_bus_cfg_ecam > > vm1 | VMM[vmmap]: [fec00000:fec00fff]: Ioapic > > vm1 | VMM[vmmap]: [fee00000:fee00fff]: Lapic_access_handler > > vm1 | VMM[main]: Populating guest physical address space > > vm1 | VMM[mmio]: Mapping [1000000 - 20ffffff] -> [0 - 1fffffff] > > vm1 | VMM[vmmap]: IOport map: > > vm1 | VMM[vmmap]: [ 20: 21]: PIC > > vm1 | VMM[vmmap]: [ 40: 43]: PIT > > vm1 | VMM[vmmap]: [ 61: 61]: PIT port 61 > > vm1 | VMM[vmmap]: [ 70: 71]: RTC > > vm1 | VMM[vmmap]: [ a0: a1]: PIC > > vm1 | VMM[vmmap]: [ 3f8: 3ff]: UART 8250 > > vm1 | VMM[vmmap]: [ 510: 51b]: Firmware interface > > vm1 | VMM[vmmap]: [ cf8: cff]: PCI bus cfg > > vm1 | VMM[vmmap]: [1800:1808]: ACPI platform > > vm1 | VMM[vmmap]: [b008:b008]: ACPI Timer > > vm1 | VMM[guest]: Starting VMM @ 0x1000000 > > vm1 | VMM[Cpu_dev]: [ 0] Reset called > > vm1 | VMM[Cpu_dev]: [ 0] Resetting vCPU. > > vm2 | VMM[ACPI]: Initialize legacy BIOS ACPI tables. > > vm2 | VMM: Zeropage @ 0x1000, Kernel @ 0x1000000 > > vm2 | VMM: Cmd_line: console=3Dhvc0 ramdisk_size=3D10000 root=3D/de= v/ram0 rw > > vm2 | VMM: Elf guest zeropage: dtb 0x1fbfdff0, entry 0x1000000 > > vm1 | VMM: Hello clock source for vCPU 0 > > vm2 | VMM: cmdline check: console=3Dhvc0 ramdisk_size=3D10000 root= =3D/dev/ram0 rw > > vm2 | VMM[vmmap]: VM map: > > vm2 | VMM[vmmap]: [ 0:1fffffff]: Ram > > vm2 | VMM[vmmap]: [b0000000:bfffffff]: Pci_bus_cfg_ecam > > vm2 | VMM[vmmap]: [fec00000:fec00fff]: Ioapic > > vm2 | VMM[vmmap]: [fee00000:fee00fff]: Lapic_access_handler > > vm2 | VMM[main]: Populating guest physical address space > > vm2 | VMM[mmio]: Mapping [1000000 - 20ffffff] -> [0 - 1fffffff] > > vm2 | VMM[vmmap]: IOport map: > > vm2 | VMM[vmmap]: [ 20: 21]: PIC > > vm1 | VMM: VM-entry failure due to invalid guest state: > > vm1 | Exit reason raw: 0x80000021 > > vm1 | Exit qualification: 0x0 > > vm2 | VMM[vmmap]: [ 40: 43]: PIT > > vm1 | IP: 0x100001e > > vm2 | VMM[vmmap]: [ 61: 61]: PIT port 61 > > vm1 | Instruction error: 0x0 > > vm2 | VMM[vmmap]: [ 70: 71]: RTC > > vm1 | Entry exception error: 0x0 > > vm2 | VMM[vmmap]: [ a0: a1]: PIC > > vm1 | VMM: [ 0]: Exit at guest IP 0x100001e SP 0x1a03f4e with 0x80= 000021 (Qual: 0x0) > > vm1 | VMM: [ 0]: Unhandled exit reason: VM-entry failure due to in= valid guest state (33) > > vm1 | VMM: FATAL: [ 0]: Failure in VMM -38 > > vm2 | VMM[vmmap]: [ 3f8: 3ff]: UART 8250 > > vm1 | VMM: FATAL: [ 0] RAX 0x2213fe9 > > vm2 | VMM[vmmap]: [ 510: 51b]: Firmware interface > > vm1 | RBX 0x0 > > vm2 | VMM[vmmap]: [ cf8: cff]: PCI bus cfg > > vm1 | RCX 0xc0000101 > > vm2 | VMM[vmmap]: [1800:1808]: ACPI platform > > vm1 | RDX 0x2213fea > > vm2 | VMM[vmmap]: [b008:b008]: ACPI Timer > > vm1 | RSI 0x1000 > > vm2 | VMM[guest]: Starting VMM @ 0x1000000 > > vm1 | RDI 0x1000 > > vm2 | VMM[Cpu_dev]: [ 0] Reset called > > vm1 | RSP 0x0 > > vm2 | VMM[Cpu_dev]: [ 0] Resetting vCPU. > > vm1 | RBP 0x0 > > vm1 | R8 0x0 > > vm1 | R9 0x0 > > vm1 | R10 0x0 > > vm1 | R11 0x0 > > vm1 | R12 0x0 > > vm1 | R13 0x0 > > vm1 | R14 0x0 > > vm1 | R15 0x0 > > vm1 | RIP 0x100001e > > vm1 | vCPU RIP 0x1000000 > > vm1 | VMM: FATAL: [ 0] VM instruction error: 0x0 > > vm1 | VMM: FATAL: VM entered a fatal state. Halting. > > vm2 | VMM: Hello clock source for vCPU 0 > > vm2 | VMM: VM-entry failure due to invalid guest state: > > vm2 | Exit reason raw: 0x80000021 > > vm2 | Exit qualification: 0x0 > > vm2 | IP: 0x100001e > > vm2 | Instruction error: 0x0 > > vm2 | Entry exception error: 0x0 > > vm2 | VMM: [ 0]: Exit at guest IP 0x100001e SP 0x1a03f4e with 0x80= 000021 (Qual: 0x0) > > vm2 | VMM: [ 0]: Unhandled exit reason: VM-entry failure due to in= valid guest state (33) > > vm2 | VMM: FATAL: [ 0]: Failure in VMM -38 > > vm2 | VMM: FATAL: [ 0] RAX 0x2213fe9 > > vm2 | RBX 0x0 > > vm2 | RCX 0xc0000101 > > vm2 | RDX 0x2213fea > > vm2 | RSI 0x1000 > > vm2 | RDI 0x1000 > > vm2 | RSP 0x0 > > vm2 | RBP 0x0 > > vm2 | R8 0x0 > > vm2 | R9 0x0 > > vm2 | R10 0x0 > > vm2 | R11 0x0 > > vm2 | R12 0x0 > > vm2 | R13 0x0 > > vm2 | R14 0x0 > > vm2 | R15 0x0 > > vm2 | RIP 0x100001e > > vm2 | vCPU RIP 0x1000000 > > vm2 | VMM: FATAL: [ 0] VM instruction error: 0x0 > > vm2 | VMM: FATAL: VM entered a fatal state. Halting. > _______________________________________________ > l4-hackers mailing list -- [email protected] > To unsubscribe send an email to [email protected] --=20 Matthias Lange phone: +49 (0) 351-41 888 614 Customer Engineer Specialist web: https://www.kernkonzept.com Kernkonzept GmbH Buchenstra=DFe 16b 01097 Dresden Gesch=E4ftsf=FChrer: 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. _______________________________________________ l4-hackers mailing list -- [email protected] To unsubscribe send an email to [email protected]