VirtualBox

Opened 18 months ago

Last modified 10 months ago

#21697 new defect

Broken cross-compatibility between the VBox and Additions in 6.1.45 r157688 and 7.0.9 r157689

Reported by: boxer01 Owned by:
Component: guest additions/x11/graphics Version: VirtualBox-7.0.8
Keywords: Cc:
Guest type: Windows Host type: Windows

Description

The Issue: in or after forementioned versions, one couldn't run the VM in one version of VBox with Guest Additions from another VBox version (so no chance to run VM in VBox 7 with Additions from VBox 6.1 and vice verse).

This makes updating / changing version more difficult. Previously, one could just start the 6.1 VM with 6.1 Additions in VBox 7 and then just update the Additions. But now we have a black screen in this case. And the exception, if one try to run 7.0 VM with 7.0 Additions in VBox 6.1 to downgrade. The exception is:

GIM: HyperV: Guest indicates a fatal condition! P0=0x3b P1=0xc0000005 P2=0xfffff80530ce6a0a P3=0xffff810d5ae1a780 P4=0x0

.

Therefore, one have to go to the safe mode to update the Additions, which is more steps than we have before in such case.

I think we had such issues in the first Betas of 7.0, see the forum. As usual, I put my logs here, for both versions.

Attachments (5)

VBox_7&6_uncompat_logs.7z (58.8 KB ) - added by boxer01 18 months ago.
Logs from VBox 6.1 and 7.0
VBox_7.0.9-158223_to_6145-158243.7z (121.9 KB ) - added by boxer01 17 months ago.
Log with crash on guest additions downgrade from 7.0.9-158223 to 6.1.45-158243
VBox_7.0.9-158223_vid.7z (124.2 KB ) - added by boxer01 17 months ago.
Log with black screen in 7.0.9-158223
VBox_61_7_logs_05082023.7z (256.2 KB ) - added by boxer01 16 months ago.
Logs from 6.1.47-158685 and 7.0.11-158681
VBox_LOgs_18082023.7z (123.6 KB ) - added by boxer01 16 months ago.
Fresh logs from new versions

Download all attachments as: .zip

Change History (24)

by boxer01, 18 months ago

Attachment: VBox_7&6_uncompat_logs.7z added

Logs from VBox 6.1 and 7.0

comment:1 by boxer01, 18 months ago

Do we need the same ticket with 6.1.44 version?

comment:2 by boxer01, 18 months ago

Good news, partly. With the current 1577xx / 1578xx test builds, I get at least backward compatibility with 7.x additions under VBox 6.1.45. I still have these problems with 6.1.45 additions under VBox 7.0.9, so I have to cause the safe mode. Otherwise, the screen is dark, and I can't update the additions in both current 7.x versions (7.0.9 and 7.0.97)

BTW, the all links to the test build are gone

comment:3 by boxer01, 17 months ago

Still here in 7.0.9-158223 and 6.1.45-158243.

The backward compatibility is here, I still can use 7.0 guest additions under the VBox 6.1.45. But if I try to downgrade the guest additions from 7.0.9 to 6.1.45 version - I still get the exception and VM reboot. It is a different exception now, but still this is troubling.

In case of 6.1 guest additions under VBox 7, there is still a black screen, so I have to cause the safe mode with crashing the VM.

I put my current logs for both versions.

by boxer01, 17 months ago

Log with crash on guest additions downgrade from 7.0.9-158223 to 6.1.45-158243

by boxer01, 17 months ago

Attachment: VBox_7.0.9-158223_vid.7z added

Log with black screen in 7.0.9-158223

comment:4 by boxer01, 16 months ago

Current versions (6.1.47-158685 and 7.0.11-158681). Downgrading Guest Additions from 7 to 6.1 in VBox 6.1 - reboot before the end of the process. Then everything works OK.

Starting the VM with Guest Additions 6.1 in VBox 7, can't resize the screen to full-screen. Only have 800x600 before installing Guest Additions from 7.0.

Afterward, everything was OK.

by boxer01, 16 months ago

Attachment: VBox_61_7_logs_05082023.7z added

Logs from 6.1.47-158685 and 7.0.11-158681

comment:5 by boxer01, 16 months ago

Still here in 7.0.11-158811 and 6.1.47-158777. The backward compatibility is here, I still can use 7.0 guest additions under the VBox 6.1.

When downgrading to 6.1 - still restart before the end of installation. Then everything is OK. Starting VBox 7.0 with 6.1 additions - the black screen is here, as at the very beginning. After safe mode installation - reboot after the first restart after installation.

by boxer01, 16 months ago

Attachment: VBox_LOgs_18082023.7z added

Fresh logs from new versions

comment:6 by boxer01, 15 months ago

Still here in 7.0.11-159210 and 6.1.47-159049.

comment:7 by boxer01, 14 months ago

Still here in 7.0.11-159359.

comment:8 by boxer01, 14 months ago

Still here in 7.0.11-159409.

comment:9 by boxer01, 14 months ago

Still here in 7.0.12-159484 and 6.1.48-159471.

comment:10 by Dmitrii Grigorev, 14 months ago

Hello Boxer. Thank you for the report.

I've tried to reproduce the issue using the following steps:

  1. Start Windows 10 VM without GA using VBox 7.0.12, the VM was created with VBox 7.0.10.
  2. Install 6.1.48 GA into the VM
  3. Install 7.0.12 GA into the VM (over 6.1.48 GA)
  4. Install 6.1.48 GA into the VM (over 7.0.12 GA)

All the four steps cause no problems.

The two differences could matter here:

  1. I've created the VM using VBox 7.0.10
  2. The "3D acceleration" is disabled in the VM

Could you provide more detailed steps to reproduce the issue?

With best regards, Dmitrii

Last edited 14 months ago by Dmitrii Grigorev (previous) (diff)

comment:11 by boxer01, 14 months ago

You forgot to change the VBox version, too. So here is my step-by-step explanation:

  1. Install VBox 7.0.12 and create or load a VM; install GA 7.0.12 in it.
  2. Remove VBox 7.0.12 and install 6.1.48 instead; load the same VM; downgrade the 7.0.12 GAs to the 6.1.48 GAs → at the end of the process, you have a direct VM reboot instead of the dialog asking for a reboot; but the GAs are properly installed. This direct reboot could be eliminated?
  3. Now remove the VBox 6.1.48 and install the VBox 7.0.12 once again; load the same VM and see that there is a black screen; provoke the safe mode by resting the VM at least two times; from the safe mode, one can upgrade the GAs from 6.1.48 to 7.0.12 → the black screen and the need for a safe mode could be eliminated?

One can also do the 6.1.48 VBox part first and the 7.0.12 part second. This would change the sequence, but the results would remain the same.

comment:12 by boxer01, 14 months ago

Still here in 7.0.13-159587 and 6.1.49-159590.

comment:13 by boxer01, 14 months ago

Still here in 7.0.13-159676 and 6.1.49-159643.

comment:14 by boxer01, 13 months ago

Still here in 7.0.13-160152 and 6.1.49-160139.

comment:15 by boxer01, 12 months ago

Still here in 7.0.97-160458 and 6.1.49-160457.

comment:16 by boxer01, 11 months ago

Happy New Year, everybody! ;-)

This is still an issue for versions 7.0.13-160845, 7.0.13-161031, 7.0.97-160850, 7.0.97-161032 and 6.1.49-160545 or 6.1.49-161009.

comment:17 by boxer01, 11 months ago

Still here in 7.0.14-161095 and 6.1.50-161033.

comment:18 by boxer01, 10 months ago

Still here in 7.0.15-161311 and 6.1.51-161130.

comment:19 by boxer01, 10 months ago

Could be closed because 6.1.x is out of support.

Note: See TracTickets for help on using tickets.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette