On Wed, 1 Apr 2020 11:45:22 +0100 Jonathan Cameron <[email protected]> wrote:
> On Tue, 31 Mar 2020 11:59:13 -0700 > Richard Henderson <[email protected]> wrote: > > > On 3/31/20 8:33 AM, Jonathan Cameron wrote: > > > Just wondering if there are any known issues with this? > > > > Nope. It works for me. > > Can you give us any more details. > > > > Unfortunately not a lot more to add. > > I ran some sanity checks that it wasn't something else looking like > an issue in these patches. > > All with 5.6 kernel and 5.0.0 rc0 qemu > > 1) sve=off but VHE still on. failed. > 2) sve=off + VH bit not set. fine but obviously no VHE. > (dance with SVE required because of kernel checks for SVE before > allowing no VHE kvm). > 3) above tests run on mainline qemu just after VHE patches applied > (just in case we have a regression from some other change). No > change. 4) EDK2 for the guest. Synchronous exception. (works fine > with no VHE) 0x00..05F9B2208 This one may be something since fixed in edk2. I did a fresh build of the current tree and it goes away. > > I do get an additional error sometimes such as the ld.so one here. > > [ 16.539375] Run /sbin/init as init process > Inconsistency detected by ld.so: rtld.c: 721: init_tls: Assertion `i > == GL(dl_tls_max_dtv_idx)' failed! [ 17.780596] Kernel panic - not > syncing: Attempted to kill init! exitcode=0x00007f00 [ 17.847709] > CPU: 0 PID: 1 Comm: init Not tainted 5.6.0 #356 [ 17.897260] > Hardware name: linux,dummy-virt (DT) [ 17.940007] Call trace: > [ 17.962297] dump_backtrace+0x0/0x190 > [ 17.993897] show_stack+0x1c/0x28 > [ 18.022382] dump_stack+0xb4/0xfc > [ 18.050781] panic+0x160/0x35c > [ 18.077469] do_exit+0x9a4/0xa08 > [ 18.105510] do_group_exit+0x48/0xa8 > [ 18.136073] __arm64_sys_exit_group+0x1c/0x20 > [ 18.173677] el0_svc_common.constprop.0+0x70/0x168 > [ 18.218659] do_el0_svc+0x28/0x88 > [ 18.247154] el0_sync_handler+0x10c/0x180 > [ 18.281379] el0_sync+0x140/0x180 > [ 18.310684] Kernel Offset: 0x2a67dcc00000 from 0xffff800010000000 > [ 18.362474] PHYS_OFFSET: 0xfffff79400000000 > [ 18.398314] CPU features: 0x40012,20c0a238 > [ 18.433416] Memory Limit: none > [ 18.463648] ---[ end Kernel panic - not syncing: Attempted to kill > init! exitcode=0x00007f00 ]--- Seems I can get away with an initrd, but not a qcow2 based disk image. Not that this necessarily helps much with working out what is going wrong! Jonathan > > > Jonathan > > > > > > r~ >
