The posted log is incomplete and does not show a Guru Meditation. Was it possibly copied while the error window was still open? If so, the log will be complete when all windows for the VM including error windows are closed.
This appears to be the first level of nesting, based on the real PC DMI info:
00:00:04.744707 DMI Product Name: ZenBook UX425EA_UX425EA
00:00:04.748913 DMI Product Version: 1.0
The VM looks good as a by-itself VM, but not too well provisioned as a nesting VM:
00:00:04.949571 NumCPUs <integer> = 0x0000000000000002 (2)
00:00:04.949573 RamSize <integer> = 0x0000000100000000 (4 294 967 296, 4.0 GiB)
00:00:04.949770 VRamSize <integer> = 0x0000000001000000 (16 777 216, 16.0 MiB)
The host has 4 cores and 16GB RAM, 9.9GB available RAM at the logged run. More RAM may be OK in the first VM so the second VM can have some, but probably only one processor in the second VM. (You might be able to squeeze 3 processors in the first VM, so the second VM can have 2.)
The big moose on campus is a missing host CPU feature that is needed for decent nested VMs:
00:00:06.243678 VMX - Virtual-Machine Extensions = 1 (1)
00:00:06.243684 Ept - Extended Page Tables = 1 (1)
00:00:06.243686 UnrestrictedGuest - Unrestricted guest = 1 (1)
00:00:06.243688 VmcsShadowing - VMCS shadowing = 0 (0)
Without that, this nested VM project may be dead on arrival.
FWIW if the second level of VM is a Docker, that may not work as a nested VM.