Windows 10 virtual machine crash at boot since virtualbox update to version 7.1.0

Discussions about using Windows guests in VirtualBox.
Post Reply
zBox_55
Posts: 4
Joined: 24. Nov 2024, 20:00

Windows 10 virtual machine crash at boot since virtualbox update to version 7.1.0

Post by zBox_55 »

Dear Forum,

I am on an Arch-linux-based host and since the update to virtualbox version 7.1.0, my windows 10 guest virtual machine (vm) crashes at boot. In the meanwhile, my distribution rolled out the virtualbox update to version 7.1.2. Unfortunately, it did not bring any change to my problem.

In the logs, the only error message I could detect is:

Code: Select all

00:00:02.931179 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={6ac83d89-6ee7-4e33-8ae6-b257b2e81be8} aComponent={ConsoleWrap} aText={The VBoxGuestPropSvc service call failed with the error VERR_HGCM_SERVICE_NOT_FOUND}, preserve=false aResultDetail=-2900
...
00:00:03.158570 HM:   VM-entry Xcpt error-code optional = false
...
00:00:02.412647 TM: GIP - CPU: iCpuSet=0x0 idCpu=0x0 idApic=0x0 iGipCpu=0x1 i64TSCDelta=0 enmState=3 u64CpuHz=1992006437(*) cErrors=0
00:00:02.412652 TM: GIP - CPU: iCpuSet=0x1 idCpu=0x1 idApic=0x2 iGipCpu=0x7 i64TSCDelta=0 enmState=3 u64CpuHz=1992006702(*) cErrors=0
00:00:02.412657 TM: GIP - CPU: iCpuSet=0x2 idCpu=0x2 idApic=0x4 iGipCpu=0x4 i64TSCDelta=0 enmState=3 u64CpuHz=1992006614(*) cErrors=0
00:00:02.412661 TM: GIP - CPU: iCpuSet=0x3 idCpu=0x3 idApic=0x6 iGipCpu=0x3 i64TSCDelta=0 enmState=3 u64CpuHz=1992006676(*) cErrors=0
00:00:02.412666 TM: GIP - CPU: iCpuSet=0x4 idCpu=0x4 idApic=0x1 iGipCpu=0x0 i64TSCDelta=0 enmState=3 u64CpuHz=1992006693(*) cErrors=0
00:00:02.412670 TM: GIP - CPU: iCpuSet=0x5 idCpu=0x5 idApic=0x3 iGipCpu=0x6 i64TSCDelta=0 enmState=3 u64CpuHz=1992006704(*) cErrors=0
00:00:02.412674 TM: GIP - CPU: iCpuSet=0x6 idCpu=0x6 idApic=0x5 iGipCpu=0x5 i64TSCDelta=0 enmState=3 u64CpuHz=1992006702(*) cErrors=0
00:00:02.412690 TM: GIP - CPU: iCpuSet=0x7 idCpu=0x7 idApic=0x7 iGipCpu=0x2 i64TSCDelta=0 enmState=3 u64CpuHz=1992006227(*) cErrors=0
Any thoughts if this might play a role concerning my problem?

The other thing is that, since I cannot boot and log in to Win 10, I cannot install the guest additions relating to the (updated) vbox version. Is there a way to install guest additions outside of the guest vm?

Thanks in advance for any help.

Regards, zBox_55
klaus
Oracle Corporation
Posts: 1576
Joined: 10. May 2007, 14:57

Re: Windows 10 virtual machine crash at boot since virtualbox update to version 7.1.0

Post by klaus »

Suspect you'd need the fix which went into 7.1.4... Windows was tripping over CPUID/MSR reporting.
zBox_55
Posts: 4
Joined: 24. Nov 2024, 20:00

Re: Windows 10 virtual machine crash at boot since virtualbox update to version 7.1.0

Post by zBox_55 »

@klaus
Thank you for your answer. Recently, I could update to version 7.1.4. Unfortunately, the problem is still unchanged. I attached the corresponding log file. Any ideas related to that are appreciated. Thanks so much.
Last edited by zBox_55 on 7. Dec 2024, 17:53, edited 3 times in total.
klaus
Oracle Corporation
Posts: 1576
Joined: 10. May 2007, 14:57

Re: Windows 10 virtual machine crash at boot since virtualbox update to version 7.1.0

Post by klaus »

Sorry about the confusion I created. The fix I meant didn't make it for 7.1.4 and is so far purely in the test builds.

The last log file you provided is unfortunately rather unhelpful - I'd rather have a current, complete VBox.log for a 'crash'.
zBox_55
Posts: 4
Joined: 24. Nov 2024, 20:00

Re: Windows 10 virtual machine crash at boot since virtualbox update to version 7.1.0

Post by zBox_55 »

@klaus:

Thank you for the answer.
klaus wrote: 2. Dec 2024, 23:00 Sorry about the confusion I created. The fix I meant didn't make it for 7.1.4 and is so far purely in the test builds.
Related to that, is already clear in which upcoming update the fix will be implemented in?
klaus wrote: 2. Dec 2024, 23:00 The last log file you provided is unfortunately rather unhelpful - I'd rather have a current, complete VBox.log for a 'crash'.
But this was the only log file (?) related to that vm session. The error messages in that file are:

Code: Select all

(...)
00:00:00.037540 DCon01   NetIfAdpCtlOut: VBoxNetAdpCtl: Error while retrieving link speed for wlp2s0: VBoxNetAdpCtl: ioctl failed: Operation not supported
(...)
00:00:00.058100 DCon01   ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX} aComponent={SystemPropertiesWrap} aText={Cannot determine default Guest Additions ISO location. Most likely they are not available}, preserve=false aResultDetail=0
(...)
00:00:01.229916 DCon05   ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX} aComponent={RecordingSettingsWrap} aText={Recording not started}, preserve=false aResultDetail=0
00:00:01.269638 DCon03   NetIfAdpCtlOut: VBoxNetAdpCtl: Error while retrieving link speed for wlp2s0: VBoxNetAdpCtl: ioctl failed: Operation not supported
00:00:01.404415 DCon03   ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX} aComponent={RecordingSettingsWrap} aText={Recording not started}, preserve=false aResultDetail=0
00:00:01.541405 DCon03   ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) aIID={XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX} aComponent={MediumWrap} aText={Property 'CRYPT/KeyId' does not exist}, preserve=false aResultDetail=0
00:00:01.542386 DCon03   ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) aIID={XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX} aComponent={MediumWrap} aText={Property 'CRYPT/KeyId' does not exist}, preserve=false aResultDetail=0
(...)
00:00:01.561947 DCon01   ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX} aComponent={RecordingSettingsWrap} aText={Recording not started}, preserve=false aResultDetail=0
(...)
00:00:17.137983 main     VirtualBox: object deletion starts
00:00:17.166011 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX} aComponent={MediumWrap} aText={Medium '/home/xx/VirtualBox VMs/Win10Pro_70/Win10Pro_70.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:00:17.166732 main     HostDnsMonitor: shutting down ...
00:00:17.166817 main     HostDnsMonitor: shut down
00:00:17.177706 Watcher  ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX} aComponent={VirtualBoxWrap} aText={The object is not ready}, preserve=false aResultDetail=0
00:00:17.177805 main     VirtualBox: object deleted
Any ideas on these error messages?
klaus
Oracle Corporation
Posts: 1576
Joined: 10. May 2007, 14:57

Re: Windows 10 virtual machine crash at boot since virtualbox update to version 7.1.0

Post by klaus »

Again - VBox.log for the affected VM. Not VBoxSVC.log.

This is in the Logs directory inside the VM directory (which is by default inside the 'VirtualBox VMs' directory). See https://docs.oracle.com/en/virtualizati ... debug-info
zBox_55
Posts: 4
Joined: 24. Nov 2024, 20:00

Re: Windows 10 virtual machine crash at boot since virtualbox update to version 7.1.0

Post by zBox_55 »

@klaus:
klaus wrote: 6. Dec 2024, 01:46 VBox.log for the affected VM. Not VBoxSVC.log.

This is in the Logs directory inside the VM directory (which is by default inside the 'VirtualBox VMs' directory). See https://docs.oracle.com/en/virtualizati ... debug-info
Thank you for the advice. Here we go:
Attachments
VBox.log.zip
(22.38 KiB) Downloaded 13 times
klaus
Oracle Corporation
Posts: 1576
Joined: 10. May 2007, 14:57

Re: Windows 10 virtual machine crash at boot since virtualbox update to version 7.1.0

Post by klaus »

Unfortunately no hint... just some audio volume changes before the VBox.log file ends.
zBox_55
Posts: 4
Joined: 24. Nov 2024, 20:00

Re: Windows 10 virtual machine crash at boot since virtualbox update to version 7.1.0

Post by zBox_55 »

@klaus:

As mentioned in my first post, in an earlier log file of the crashed VM the following error message was shown:

Code: Select all

00:00:01.205927 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx} aComponent={ConsoleWrap} aText={The VBoxGuestPropSvc service call failed with the error VERR_HGCM_SERVICE_NOT_FOUND}, preserve=false aResultDetail=-2900
This sounds similar to this issue:
viewtopic.php?p=542859

In the other thread the problem was seen as related to a guest addition issue. The solution, as I understood, was to update the guest additions. In fact, the installed guest additions in this VM of mine are not up to date, because I was not able to update due the VM not booting.

Is there any way to update the guest additions, if I cannot log into the guest VM?
Post Reply