Seems to be a kind of deadlock -
the opensue Maillist archive stops in march 2020 - I found no informations about paravirt 15.2 upgrade
the update stops on 15.1 and the upgrade procedure from 15.1 to 15.2 have no new patches.
It seems i have no chance to upgrade the pv 15.1 to 15.2 nor 15.3 -

But i made two new Dom-U Installations on the
Dom0 Leap 15.2 5.3.18-lp152.66-default

a 15.3 beta fullwirt -> works

And:
a 15.3 paravirt -
with the same Oops:

Code:
[    4.091626] systemd[1]: Started Journal Service.
[    4.125250] systemd-journald[336]: Received client request to flush runtime journal.
[    4.224568] input: PC Speaker as /devices/platform/pcspkr/input/input0
[    4.251696] xen_netfront: Initialising Xen virtual ethernet driver
[    4.265339] Console: switching to colour frame buffer device 100x37
[    4.265856] printk: console [tty0] disabled
[    4.265859] printk: console [tty0] enabled
[    4.275263] cryptd: max_cpu_qlen set to 1000
[    4.311487] AVX2 version of gcm_enc/dec engaged.
[    4.311487] AES CTR mode by8 optimization enabled
[    4.331505] input: Xen Virtual Keyboard as /devices/virtual/input/input1
[    4.331739] input: Xen Virtual Pointer as /devices/virtual/input/input2
[    4.579821] BUG: unable to handle page fault for address: ffffc90040243818
[    4.579846] #PF: supervisor read access in kernel mode
[    4.579861] #PF: error_code(0x0000) - not-present page
[    4.579876] PGD 7dbe0067 P4D 7dbe0067 PUD fd34067 PMD 7d5b3067 PTE 0
[    4.579895] Oops: 0000 [#1] SMP NOPTI
[    4.579908] CPU: 1 PID: 401 Comm: systemd-udevd Tainted: G                  N 5.3.18-47-default #1 SLE15-SP3
[    4.579936] RIP: e030:pmc_core_probe+0x139/0x390 [intel_pmc_core]
the different to pv 15.2 Oops:
the pv 15.3 beta do not stop the boot process and go on through

The problem is:
due to certificates, encryption, must have https and the standard 'always patch' paradicmas there is no longer the
option to let good running systems alive - even if they running stabil and solid as a rock?

everything new? - uff..

maybe there is a kernel grub boot param in 15.2 to let the boot process go throug the Oops (yes...outch)
and then try to patch to 15.3? hopefully the oops will patched than later in 15.3 ...
this feels like toothache

Any suggestions?

!!!Stay healthy!!!!