VirtualBox

Changes between Initial Version and Version 30 of Ticket #21097


Ignore:
Timestamp:
Nov 8, 2022 9:59:14 PM (18 months ago)
Author:
bird
Comment:

Thanks for tracking this down fth0! I've corrected the woolly error checking logic for all the buggy d2i calls I could find as well as applying the same level of paranoia to the other d2i calls. Also found a i2d call with possibly incorrect error checking. Applied fixes to 6.1.x and 7.0.x (trunk).

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #21097

    • Property Summary Automatic update of VB and Failed to open a session for the virtual machine Ubuntu → Automatic update of VBox and Failed to open a session for the virtual machine Ubuntu => fixed in SVNsvn

  • Ticket #21097 – Description

    initial v30  
    11Few weeks ago, when I had updated VirtualBox, I had faced an error with opening a session for the virtual machine (guest OS is Ubuntu).
    2 Found a suggestion that VB version 6.1.32 is good and I had downgraded the VB and everything works fine, I can start a session for the VM.
     2Found a suggestion that VBox version 6.1.32 is good and I had downgraded the VBox and everything works fine, I can start a session for the VM.
    33I had turned off the automatic update of VirtualBox, but few times since then, VirtualBox was updated automatically to the newest version.
    44
    5 For some, unknown to me reason, I can't use the newest VB version, but my VB keep upgrading even when automatic update is turned off.
    6 What is the solution? Should I downgrade my VB every day?
     5For some, unknown to me reason, I can't use the newest VBox version, but my VBox keep upgrading even when automatic update is turned off.
     6What is the solution? Should I downgrade my VBox every day?

© 2023 Oracle
Contact – Privacy policy – Terms of Use