https://bugzilla.suse.com/show_bug.cgi?id=1212209 https://bugzilla.suse.com/show_bug.cgi?id=1212209#c2 Larry Finger <Larry.Finger@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |snettlet@gmail.com Flags| |needinfo?(snettlet@gmail.co | |m) --- Comment #2 from Larry Finger <Larry.Finger@gmail.com> --- After booting kernel 6.3.6-1, run the command 'sudo dmesg > dmesg.txt', and attach file dmesg.txt to this bug report. -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1212209 https://bugzilla.suse.com/show_bug.cgi?id=1212209#c4 --- Comment #4 from Stuart Nettleton <snettlet@gmail.com> --- (In reply to Larry Rainey from comment #1)

It works fine for me - you probably failed to add it to the secure boot. It appears that every new kernel has a new signature - try it with secure boot disabled.

In VirtualBox Manager, for the machine Settings, System tab, Enable Secure Boot is unchecked, and Enable EFI is checked. Thanks -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1212209 https://bugzilla.suse.com/show_bug.cgi?id=1212209#c6 --- Comment #6 from Stuart Nettleton <snettlet@gmail.com> --- (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 -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1212209 https://bugzilla.suse.com/show_bug.cgi?id=1212209#c8 Stuart Nettleton <snettlet@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #8 from Stuart Nettleton <snettlet@gmail.com> --- Thanks ... this is resolved with the new ibt workaround -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1212209 https://bugzilla.suse.com/show_bug.cgi?id=1212209#c10 Larry Finger <Larry.Finger@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dev.dorrejo@gmail.com --- Comment #10 from Larry Finger <Larry.Finger@gmail.com> --- *** Bug 1212191 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1212209 https://bugzilla.suse.com/show_bug.cgi?id=1212209#c15 --- Comment #15 from Stuart Nettleton <snettlet@gmail.com> --- (In reply to Marcus Meissner from comment #14)

openSUSE-RU-2023:0194-1: An update that has two recommended fixes can now be installed.

Category: recommended (important) Bug References: 1212209,1212761 CVE References: JIRA References: Sources used: openSUSE Leap 15.4 (src): virtualbox-7.0.10-lp154.2.35.1, virtualbox-kmp-7.0.10-lp154.2.35.1

Marcus ... I get a different failure now on Tumbleweed 6.4.4-1-default (64-bit) with VirtualBox 7.0.10-1.1 ... the VM launch progress bar starts and then aborts ... this is without ibt=off ... -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1212209 https://bugzilla.suse.com/show_bug.cgi?id=1212209#c17 --- Comment #17 from Stuart Nettleton <snettlet@gmail.com> --- Markus ... I'm not sure what I'm missing here ... for me the virtual box instance of Windows fails immediately after the progress bar ... whether I use or don't use ibt=off ... am I awaiting a new virtual box in the Suse repos? At the moment my system is: 13th Gen Intel® Core™ i9-13900HX, Tumbleweed 6.4.8-1-default (64-bit), KDE 5.27.7, Wayland and VirtualBox 7.0.10-1.1-x86 from OpenSuse (and openSuse-Tumbleweed-Oss has the same version) -- You are receiving this mail because: You are the assignee for the bug.