yersterday virtualbox was working fine, since last update when i start a virtual machine (a new one or existing one) i have a windows with starting virtual machine which hangs infinitly and nothing in the logs.
Here are the logs of the vm:
00:00:02.556390 VirtualBox VM 7.0.8_SUSE r156879 linux.amd64 (no date no time) release log
00:00:02.556394 Log opened 2023-06-12T09:07:41.168981000Z
00:00:02.556395 Build Type: release
00:00:02.556398 OS Product: Linux
00:00:02.556399 OS Release: 6.3.6-1-default
00:00:02.556401 OS Version: #1 SMP PREEMPT_DYNAMIC Mon Jun 5 07:58:35 UTC 2023 (f583ba4)
00:00:02.556433 DMI Product Name: MS-7D43
00:00:02.556443 DMI Product Version: 1.0
00:00:02.556449 Firmware type: UEFI
00:00:02.556684 Secure Boot: Enabled
00:00:02.556733 Host RAM: 64143MB (62.6GB) total, 61441MB (60.0GB) available
00:00:02.556738 Executable: /usr/lib/virtualbox/VirtualBoxVM
00:00:02.556738 Process ID: 3233
00:00:02.556739 Package type: LINUX_64BITS_GENERIC (OSE)
00:00:02.559292 Installed Extension Packs:
00:00:02.559302 None installed!
00:00:02.560830 Console: Machine state changed to 'Starting'
00:00:02.561245 Qt version: 5.15.9
00:00:02.561288 X11 Window Manager code: 3
00:00:02.575076 SUP: seg #0: R 0x00000000 LB 0x00065000
00:00:02.575110 SUP: seg #1: R X 0x00065000 LB 0x001a0000
00:00:02.575119 SUP: seg #2: R 0x00205000 LB 0x0006e000
00:00:02.575126 SUP: seg #3: RW 0x00273000 LB 0x0002eae8
00:00:02.581284 GUI: Show mini-toolbar for window #0
00:00:02.619085 GUI: Adjust mini-toolbar for window #0
00:00:02.619219 GUI: Resize mini-toolbar for window #0 to 1920x1080
00:00:02.619445 GUI: Move mini-toolbar for window #0 to 0x0
00:00:02.637847 X Server details: vendor: The X.Org Foundation, release: 12101008, protocol version: 11.0, display string: :0
00:00:02.637880 Using XKB for keycode to scan code conversion```
I have no idea where it's comming, no problems in logs.
Does anybody have the problem / or do you have any idea ?
Regards,
VGIb
OK i found the answer, excuse me for beeing not precise.
The kernel which works is the 6.3.4 , the one which does not is the 6.3.6.
The link i share, is the problem: it’s seems that ibt has been activated on opensuse kernel, which implies that virtualobox get in infinite loop (since the time there should have been a readable warning message on virtualbox side ).
@larryr it depend of your processor, ibt is a technology for securing intel processor, it’s available only if you have a version processor greater than 11.
I’m not an expert, i’m not sure it’s on every intel processor since version 11.
No sign of IBT in the Kernel …
OK – I removed all the Oracle VirtualBox Server packages from the client and, also the links in /usr/lib/systemd/system/multi-user.target.wants/ – there’s only a vboxguest installed on the Leap 15.5 client.
So i’m sorry, but bugzilla ask me to log again (since i’m already log on) and when i log again, he’ll tell me that my email address already exists …
I’ll try tomoiroow promise (i change the password of my account which didn’t work today, seems there may be a batch problem).
@susejunky , they speek a lot of this, and there seems to be the problem since months.
In the virtualbox forum they say that this feature is well known but not activate in lot of linux distribution.
So i wonder if the open suse activate it on kernel 6.3.6 (since the problem seems to be according to the virtualbox forum for opensuse 15.4 too, maybe a kernel compile script ).
If so why ? this is not a major kernel linux update ?
Or is this a kernel bug ( the ibt was working fine , but since there may be a kernel bug fix in 6.3 and 15.4 Leap kernel it doesn’t work anymore ).
I’ll promise when i access to bugzilla i write a bug record, to investigate (since the problem may not be an open suse problem, it could be a virtualbox one / or kernel one).
Yes, but, you seem to be running Oracle VirtualBox on a Redmond (Windows 11) host operating system and –
You’re trying to run Linux as a guest operating system.
As demonstrated above –
Using openSUSE Leap 15.4 as the Oracle VirtualBox host operating system and then –
Installing openSUSE Leap 15.5 as guest operating system on that host operating system –
Functions perfectly well and, as expected …
The issue is possibly caused by –
Oracle VirtualBox executing on a Redmond host operating system …
As far as I understand the virtualbox problem discussed in this thread has two key components:
The CPU in use must support IBT (which to my knowledge is true for intel Tiger Lake CPUs or later).
CONFIG_X86_KERNEL_IBT=y must be set in the kernel config (as far as I know this is the case with openSUSE kernel 6.3.6 or later).
I do not know
whether IBT needs to be disabled in an openSUSE guest system with kernel 6.3.6 or later (when the host system runs on a CPU >= intel Tiger Lake).
what happens when the host system is MS Windows 10/11 (running on a CPU >= intel Tiger Lake) and the guest is an openSUSE system with kernel 6.3.6 or later.
All my CPUs are intel Kaby Lake or older and do not support IBT therefor I cannot run any tests.