... and after a 'system_reset' it actually booted. There was a time when I had to sysytem_reset this particular guest 2-3 times before succeeding, but it hasn't been happening for quite some time.
On Mon, 29 Mar 2021 at 12:03, Chavdar Ivanov <ci4...@gmail.com> wrote: > > Hi, > > However... some of my guests refuse to play ball: > ..... > Loading Linux 4.9.0-12-amd64 ... > Loading initial ramdisk ... > [ 0.140619] ..MP-BIOS bug: 8254 timer not connected to IO-APIC > [ 0.432176] Kernel panic - not syncing: IO-APIC + timer doesn't > work! Boot with apic=debug and send a report. Then try booting with > the 'noapic' option. > [ 0.432176] > [ 0.434698] CPU: 0 PID: 1 Comm: swapper/0 Not tainted > 4.9.0-12-amd64 #1 Debian 4.9.210-1+deb9u1 > [ 0.436125] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), > BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014 > [ 0.437990] 0000000000000000 ffffffff99136f6e 0000000000000000 > ffffb55ec0633e60 > [ 0.439282] ffffffff98f82f3c 0000000000000008 ffffb55ec0633e70 > ffffb55ec0633e08 > [ 0.440574] 524e301e9d3981be 0000000000000008 ffffb55ec0633e90 > 0000000000000000 > [ 0.441862] Call Trace: > [ 0.442278] [<ffffffff99136f6e>] ? dump_stack+0x66/0x88 > [ 0.443179] [<ffffffff98f82f3c>] ? panic+0xe4/0x242 > [ 0.443994] [<ffffffff99b577b4>] ? setup_IO_APIC+0x7ae/0x88f > [ 0.444932] [<ffffffff98e501a4>] ? clear_IO_APIC_pin+0x64/0x130 > [ 0.445910] [<ffffffff99b55ea4>] ? apic_bsp_setup+0xa2/0xaf > [ 0.446834] [<ffffffff99b539de>] ? native_smp_prepare_cpus+0x26e/0x2ec > [ 0.447910] [<ffffffff99b3efc3>] ? kernel_init_freeable+0xa4/0x1ec > [ 0.448930] [<ffffffff99410c20>] ? rest_init+0x80/0x80 > [ 0.449783] [<ffffffff99410c2a>] ? kernel_init+0xa/0x100 > [ 0.450667] [<ffffffff9941e337>] ? ret_from_fork+0x57/0x70 > [ 0.451702] ---[ end Kernel panic - not syncing: IO-APIC + timer > doesn't work! Boot with apic=debug and send a report. Then try > booting with the 'noapic' option. > [ 0.451702] > > > This is from a Debian machine, in use for a very long time... The > FreeBSD 12 guest I tried is still working fine. > > > Chavdar > > On Mon, 29 Mar 2021 at 10:57, Chavdar Ivanov <ci4...@gmail.com> wrote: > > > > Hi, > > > > One of the patches needs patching... I thought nvmm was upstreamed and > > we didn't need the patches for it? > > > > Index: patch-target_i386_nvmm_all.c > > =================================================================== > > RCS file: > > /cvsroot/pkgsrc/emulators/qemu/patches/patch-target_i386_nvmm_all.c,v > > retrieving revision 1.1 > > diff -u -r1.1 patch-target_i386_nvmm_all.c > > --- patch-target_i386_nvmm_all.c 6 Mar 2021 11:19:34 -0000 1.1 > > +++ patch-target_i386_nvmm_all.c 29 Mar 2021 09:55:19 -0000 > > @@ -1166,10 +1166,6 @@ > > + error_report("NVMM: Unable to fetch capability, error=%d", errno); > > + return -err; > > + } > > -+ if (qemu_mach.cap.version != 1) { > > -+ error_report("NVMM: Unsupported version %u", > > qemu_mach.cap.version); > > -+ return -EPROGMISMATCH; > > -+ } > > + if (qemu_mach.cap.state_size != sizeof(struct nvmm_x64_state)) { > > + error_report("NVMM: Wrong state size %u", > > qemu_mach.cap.state_size); > > + return -EPROGMISMATCH; > > > > On Mon, 29 Mar 2021 at 01:32, Chavdar Ivanov <ci4...@gmail.com> wrote: > > > > > > Hi, > > > > > > Have I missed something regarding nvmm? Since today's -current update, > > > I am getting > > > > > > qemu-system-x86_64: -accel nvmm: NVMM: Unsupported version 2 > > > qemu-system-x86_64: -accel nvmm: failed to initialize nvmm: Program > > > version wrong > > > > > > when I try to run any of my usual nvmm-accelerated guests (they work > > > without nvmm). > > > > > > I updated qemu to the latest available version - qemu-5.2.0nb4 - and > > > even ran the suggested atf tests: > > > > > > ➜ libnvmm atf-run | atf-report > > > Tests root: /usr/tests/lib/libnvmm > > > > > > t_io_assist (1/2): 1 test cases > > > io_assist: [0.013472s] Passed. > > > [0.013606s] > > > > > > t_mem_assist (2/2): 1 test cases > > > mem_assist: [0.012884s] Passed. > > > [0.013004s] > > > > > > Summary for 2 test programs: > > > 2 passed test cases. > > > 0 failed test cases. > > > 0 expected failed test cases. > > > 0 skipped test cases. > > > > > > Chavdar > > > > > > -- > > > ---- > > > > > > > > -- > > ---- > > > > -- > ---- -- ----