In the GitHub thread, Andrew Cooper, a Xen developer reported that it's a Xen and OpenBSD issue at the same time. I got the issue because of a new Xen version, here is his answer:
--- I'm fairly sure it was broken in Xen 4.15 by https://lore.kernel.org/xen-devel/0c8043e3-07aa-6242-19bd-07b04f574...@suse.com/, a series committed over my objections concerning the correctness of the changes. It appears it was to shut up Linux, which makes different and equally dubious model specific assumptions about the availability of certain MSRs. - It is buggy for Linux to declare TSCFREQSEL missing to be a firmware bug - it may legitimately be so due to levelling. - It's buggy for Xen to advertise the bit like that - because it's not levelled and not part of the migration stream. - It's buggy for OpenBSD to perform any model-specific checks without first checking for !hypervisor. - And it's probably buggy for Xen to state "TSC counts at the P0 frequency" without giving the P0 frequency, but the jury is still out on this final point because there's no possible way the guest is going to get to see Pstate information. --- On Fri, 2023-09-08 at 14:54 +0200, Solène Rapenne wrote: > hi, > > OpenBSD started to crash in a VM running under Qubes OS after they > upgraded something in their emulation stack, other OS still work > AFAIK. > I don't know if it's an OpenBSD issue, I already reported it upstream > on > GitHub but I thought this may be useful to report the issue here as > well > => https://github.com/QubesOS/qubes-issues/issues/8502 > > When trying to boot cd73.iso from 7.3 amd64 or cd73.iso from a > snapshot > of today, there is a panic trap type 4 (see 7.3-error.png). > > When trying to boot a previously installed OpenBSD that's running a > snapshot from end August, I get a different error (see current.png): > > kernel: protection fault trap, code=0 > Stopped at tsc_identify+0xdf: rdmsr > > I found a related bug on bugs@ but it was a combination of AMD CPU + > vmm > bug https://marc.info/?t=166721638200001&r=1&w=2 > > My hypervisor with the issue has a Ryzen 5 5600X, I tried on a i5- > 7300U > without any issue.
