[vbox-dev] [PATCH] Fix for Guest "OS type" future-compatibility

Alexey Eromenko al4321 at gmail.com
Fri May 8 09:58:11 UTC 2015

To test it:
You can edit *.vbox VM config file to OS type = "Windows11_64",
something that doesn't exist, and with my patch VBox will be able to
change VM settings and start VM.

On Fri, May 8, 2015 at 1:08 AM, Alexey Eromenko <al4321 at gmail.com> wrote:
> Hi,
> Today if I revert to older VirtualBox (to 4.3.20) from newer (v5.0
> BETA), I lose access to certain VMs, such as "Windows 10", because it
> has a new guest OS type ID.
> Those VMs become "inaccessible" for no good reason. I can understand a
> VM becoming "inaccessible" if hard disk new format is coming or a disk
> image is lacking, but Guest OS type ?
> My patch allows to recognize and start VMs with future guest OS type
> IDs. They will revert to "unknown" OS type.
> This is particularly useful in combination with "vbox-unattended"
> patch, that adds new OS types every now and then, but also for Oracle
> VirtualBox itself.
> I have tested it together with VirtualBox GUI and with VBoxManage commands.
> Plus tested OVF, Import / Export appliance.
> --
> -Alexey Eromenko "Technologov"

-Alexey Eromenko "Technologov"

More information about the vbox-dev mailing list