#22386 closed defect (duplicate)
Ubuntu 24.04 kernel panic on VBox >= v7.1.6
Reported by: | ksr-yasuda | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox-7.1.8 |
Keywords: | Cc: | ||
Guest type: | Linux | Host type: | other |
Description (last modified by )
Ubuntu 24.04.2 LTS image, that runs on VBox v7.1.4 successfully,
is caught in kernel panic on boot on VBox v7.1.6 and v7.1.8.
Attachments (7)
Change History (21)
by , 3 weeks ago
Attachment: | dmesg.1.gz added |
---|
by , 3 weeks ago
Attachment: | dmesg.4.gz added |
---|
comment:1 by , 3 weeks ago
comment:2 by , 3 weeks ago
Description: | modified (diff) |
---|
comment:3 by , 3 weeks ago
Host is Windows 11 Pro 24H2.
PS C:\Users\yasuda> cmd /v Microsoft Windows [Version 10.0.26100.3775] (c) Microsoft Corporation. All rights reserved.
Hyper-V is disabled.
PS C:\Users\yasuda> get-windowsoptionalfeature -online -featurename microsoft-hyper-v FeatureName : Microsoft-Hyper-V DisplayName : Hyper-V プラットフォーム Description : 仮想マシンとそのリソースの作成および管理に使用できるサービスを提供します。 RestartRequired : Possible State : Disabled CustomProperties :
comment:4 by , 3 weeks ago
Resolution: | → duplicate |
---|---|
Status: | new → closed |
Hi ksr-yasuda,
Please note, there is no kernel panic in the log. It is kernel warning. Tick is a duplicate of #22218.
by , 3 weeks ago
Attachment: | VirtualBox_v7.1.6_Ubuntu_24.04.1_KernelPanic_20250129_090951.png added |
---|
comment:5 by , 2 weeks ago
Then, could you give me any advice for the screenshot?
It was at the kernel panic of Ubuntu 24.04.1 on VBox v7.1.6.
It crashes in boot sequence, and the log is unscrollable.
It's just what I could only have captured.
comment:6 by , 2 weeks ago
Hi ksr-yasuda,
Please try to collect kernel log following these instructions and attach it here.
by , 2 weeks ago
Attachment: | VBox_7_1_8_Ubuntu_24_04_2.log.gz added |
---|
comment:8 by , 2 weeks ago
Hi ksr-yasuda,
There are number of "general protection fault" errors in dmesg, however I cannot immediately say what is the reason for them. Could you please also attach VBox.log, maybe it has more additional details?
by , 2 weeks ago
Attachment: | VBox.log.2 added |
---|
by , 2 weeks ago
Attachment: | VBox.log.3 added |
---|
comment:10 by , 2 weeks ago
Hi ksr-yasuda,
Does the issue with guest kernel panic persist if you install matching version of Extension Pack?
comment:11 by , 2 weeks ago
At my first try for VBox v7.1.6, it had still happened.
Not checked for v7.1.8, yet.
But, of course as you know,
I can update extension pack into the host VBox, though,
cannot into the guest Ubuntu, that won't start up.
comment:12 by , 2 weeks ago
Guest Additions can stay on the same version at this point. However, host installation version and Extension Pack one must match, this is requirement. When versions do not match it might result in unpredictable behavior such as VM process crashes etc, so please update to the matching version.
comment:13 by , 2 weeks ago
Please also note that the amount of RAM assigned to VM is close to available free memory on host. I'd suggest to decrease VM RAM or add more RAM to the host. This likely is not the cause of guest kernel panic, but important thing to keep in mind.
by , 2 weeks ago
Attachment: | VBox_7_1_8_Ubuntu_24_04_2_WithExtPack_7_1_8_20250425_090122.zip added |
---|
comment:14 by , 2 weeks ago
Got logs with Extension Pack v7.1.8.
It certainly crashes.
Please also note that the amount of RAM assigned to VM is close to available free memory on host.
Is that so?
I assign 6GB for VM for now (also confirmed 8GB. Probably available more).
While VM is running (on VBox v7.1.4),
host physical memory usage is about 12 - 13 GB of 16 GB, as Windows task manager says.
It would have some more GB memory free.
I've thought you might rather suggest to apply more memory for VM.
Attached dmesg logs, that would be in the crashes.
Could these help?