[solved] Virtual machines do not start anymore after kernel update (from 5 to 6)

[sgrue]

Hi there,

I'm facing troubles do start my Virtual Machines using the current Manjaro LTS kernel 6.1.31. Before with LTS kernel 5 it worked. I updated all the packages so now i have Virtual Box 7.0.8 running.
When I try to start a VM, no matter if it's of an existing system or I create a new one with an ISO image to boot from, the Window appears that the VM is starting - and then nothing happens any more. I need to kill the task then - when I try it a second time, the system will not even properly reboot or shutdown anymore, as it will wait for the vboxservice to stop forever.

Attached there is my VBox.log, but I does not contain much information...
VirtualBox: 7.0.8 r156879
Manjaro Linux, LTS kernel 6.1.31
VM: previously working win 10 64 bit, or just a new one that shall start from the ISO image
Assigned 4 CPUs and 4GB of memory to them. Host system is 12 core Intel i7-1265u, 32Gb memory (Dell Latitude 5430)

Any advise what I could try to resolve this?

I already did reinstallation of VirtualBox with the corresponding virtualbox-host-modules without success.

thanks a lot!
regards
Sg

[pepicheck]

Same issue after updates on Fedora 38, kernel 6.3.4. But that is not because of kernel, as it works before on 6.3.3 and testing kernel, seems like more connected to new mesa, qt5 libs or selinux. Is there a way how to get proper logs as it seems pretty empty? Nothing useful.

[sgrue]

Same issue after updates on Fedora 38, kernel 6.3.4. But that is not because of kernel, as it works before on 6.3.3 and testing kernel, seems like more connected to new mesa, qt5 libs or selinux. Is there a way how to get proper logs as it seems pretty empty? Nothing useful.

Well, if you can guide me how to get a better log, I'm happy to upload them!

[pepicheck]

in ~/.config/VirtualBox/VBoxSVC.log are another logs but nothing useful too:


00:00:00.128487 nspr-2 ExtPack: Created cloud provider 'OCI' (hrc=NS_OK)
00:00:00.128508 nspr-2 VirtualBox: object created
00:00:05.132900 main VirtualBox: object deletion starts
00:00:05.132937 main ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={ad47ad09-787b-44ab-b343-a082a3f2dfb1} aComponent={MediumWrap} aText={Medium '/home/pstourac/VirtualBox VMs/Fedora CSB/Fedora CSB.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:00:05.133048 main ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={ad47ad09-787b-44ab-b343-a082a3f2dfb1} aComponent={MediumWrap} aText={Medium '/home/pstourac/VirtualBox VMs/Fedora WS 38/Fedora WS 38-disk1.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:00:05.133137 main ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={ad47ad09-787b-44ab-b343-a082a3f2dfb1} aComponent={MediumWrap} aText={Medium '/home/pstourac/VirtualBox VMs/RHEL 8 MainLine/RHEL 8 MainLine.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:00:05.133176 main ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={ad47ad09-787b-44ab-b343-a082a3f2dfb1} aComponent={MediumWrap} aText={Medium '/home/pstourac/VirtualBox VMs/RHEL 9 MainLine/RHEL 9 MainLine.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:00:05.133215 main ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={ad47ad09-787b-44ab-b343-a082a3f2dfb1} aComponent={MediumWrap} aText={Medium '/home/pstourac/VirtualBox VMs/RHEL_CSB_7.9/Klon RHEL_CSB_7.8-disk1.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:00:05.133291 main ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={ad47ad09-787b-44ab-b343-a082a3f2dfb1} aComponent={MediumWrap} aText={Medium '/home/pstourac/VirtualBox VMs/RHEL_CSB_8.7/RHEL_CSB_8.0.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:00:05.133334 main ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={ad47ad09-787b-44ab-b343-a082a3f2dfb1} aComponent={MediumWrap} aText={Medium '/home/pstourac/VirtualBox VMs/Windows10/Windows10.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:00:05.133380 main ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={ad47ad09-787b-44ab-b343-a082a3f2dfb1} aComponent={MediumWrap} aText={Medium '/home/pstourac/VirtualBox VMs/Windows10_CSB/Windows10_CSB.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:00:05.133421 main ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={ad47ad09-787b-44ab-b343-a082a3f2dfb1} aComponent={MediumWrap} aText={Medium '/home/pstourac/VirtualBox VMs/Windows11_CSB/Windows11_CSB.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:00:05.133616 main HostDnsMonitor: shutting down ...
00:00:05.133893 main HostDnsMonitor: shut down
00:00:05.144744 Watcher ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={7682d5eb-f00e-44f1-8ca2-99d08b1cd607} aComponent={VirtualBoxWrap} aText={The object is not ready}, preserve=false aResultDetail=0
00:00:05.144827 main VirtualBox: object deleted

[sgrue]

Well, found that logfile, i post it here - maybe someone finds some useful information in it?

[pepicheck]

The last error is pretty much same as mine.

[scottgus1]

Very often, when a new Linux kernel comes out, a new Virtualbox version might need to come out, too. I've no idea if this is the case in this topic's problem, but it has happened before in the recent past.

[pepicheck]

Do not think it is related to kernel, as I have different version, and it worked for me for quite a while at 6.3.x already. More I am suspecting latest mesa or qt6.

[pepicheck]

Just some testing, downgrading packages, and finally, it is kernel issue. 6.2.14 and 6.2.9 works, 6.3.4 VirtualBox 7.0.8 not, tested also 6.1.44. same behaviour

[scottgus1]

Interesting, thanks for the tests! A Bugtracker ticket may help the devs be aware of this, if they aren't already.

[sgrue]

Just some testing, downgrading packages, and finally, it is kernel issue. 6.2.14 and 6.2.9 works, 6.3.4 VirtualBox 7.0.8 not, tested also 6.1.44. same behaviour

Very interesting, i just tested kernel 6.2.16 which also does not work. But switching back to my old LTS kernel 5.15.114 it does work again.

[pepicheck]

Hae created bugtracker, more informations I can easily provide, tested also 7.0.9 latest testbuild, same.

[fth0]

FWIW, the provided log files do not indicate any real problem. You could provide a (zipped) SYSLOG (or similar) from your host OS here (and the core dump for galitsyn in your ticket 21698).

[pepicheck]

So, for me, the workaround in https://www.virtualbox.org/ticket/21698#comment:7 worked

[marmel]

So, for me, the workaround in https://www.virtualbox.org/ticket/21698#comment:7 worked

Virtualbox 7.0.8 still does not yet support IBT in modern kernels, see:

• Forum Thread: ​viewtopic.php?f=7&t=108948

• Bug Tracker: https://www.virtualbox.org/ticket/21435