Comment # 6 on bug 1212209 from Stuart Nettleton

(In reply to Larry Finger from comment #5)
> The vbox kernel modules loaded OK. I'm not sure what is causing the problem.
> Did you try to start a VM during the time covered by that dmesg output?

The dmesg was taken immediately after a fresh boot (although following a hard
reboot after VirtualBox froze the screen).

> Is this a rev 11+ CPU? What does 'hwinfo --cpu' show for any one of the
> CPUs? If it is, then you may be hit by the ibt  problem. Follow the
> instructions in
> https://forums.opensuse.org/t/virtualbox-fails-to-start-on-newest-cpus-with-
> 6-3-6-kernel-how-to-fix-until-oracle-finds-a-fix/166879 for a workaround.

localhost:~ # hwinfo --cpu
01: None 00.0: 10103 CPU                                        
  [Created at cpu.462]
  Unique ID: rdCR.j8NaKXDZtZ6
  Hardware Class: cpu
  Arch: X86-64
  Vendor: "GenuineIntel"
  Model: 6.183.1 "13th Gen Intel(R) Core(TM) i9-13900HX"
  Features:
fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,ht,tm,pbe,syscall,nx,pdpe1gb,rdtscp,lm,constant_tsc,art,arch_perfmon,pebs,bts,rep_good,nopl,xtopology,nonstop_tsc,cpuid,aperfmperf,tsc_known_freq,pni,pclmulqdq,dtes64,monitor,ds_cpl,vmx,est,tm2,ssse3,sdbg,fma,cx16,xtpr,pdcm,sse4_1,sse4_2,x2apic,movbe,popcnt,tsc_deadline_timer,aes,xsave,avx,f16c,rdrand,lahf_lm,abm,3dnowprefetch,cpuid_fault,epb,ssbd,ibrs,ibpb,stibp,ibrs_enhanced,tpr_shadow,vnmi,flexpriority,ept,vpid,ept_ad,fsgsbase,tsc_adjust,bmi1,avx2,smep,bmi2,erms,invpcid,rdseed,adx,smap,clflushopt,clwb,intel_pt,sha_ni,xsaveopt,xsavec,xgetbv1,xsaves,split_lock_detect,avx_vnni,dtherm,arat,pln,pts,hwp,hwp_notify,hwp_act_window,hwp_epp,hwp_pkg_req,hfi,umip,pku,ospke,waitpkg,gfni,vaes,vpclmulqdq,rdpid,movdiri,movdir64b,fsrm,md_clear,serialize,arch_lbr,ibt,flush_l1d,arch_capabilities
  Clock: 1800 MHz
  BogoMips: 4838.40
  Cache: 36864 kb
  Units/Processor: 128
  Config Status: cfg=no, avail=yes, need=no, active=unknown

> If this does not resolve your problem, what symptoms are you seeing for
> kernel 6.3.6?

VirtualBox starts the manager fine, once the VM launch sequence is started the
computer screen freezes and only a manual shutdown using the power button is
possible

I will investigate the ibt fix, however its strange that the previous kernel
has no issues in launching a VM ... so it initially seems more like a kernel
issue than a cpu-issue