Discuss the VirtualBox 7.2.2 release here

[galitsyn]

You can download the release here.
VirtualBox 7.2.2 is a maintenance release.

Changelog is here.

[vboxuser4242]

After upgrading to VirtualBox 7.2.2 (from 7.2.0), none of my virtual machines can start.

I always get this error:

Code: Select all

VM Name: Ubuntu

Driver name clash. Another driver with the same name as the one being registered exists. (VERR_PDM_DRIVER_NAME_CLASH).
Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {6ac83d89-6ee7-4e33-8ae6-b257b2e81be8}

Reboot of the host didn't help.

Completely uninstalling VirtualBox, rebooting and then performing a clean re-install of VirtualBox 7.2.2 didn't help either.

Any help, please

VBox.log

(42.37 KiB) Downloaded 556 times

[merced]

The changelog mentioned that "Windows Guest Additions: Fixed issue when installation was failing on Windows XP SP2 64-bit (issue ​github:gh-142)". However I still got the "The VirtualBox Guest Additions cannot be installed on this version of Windows" error unfortunately when I tried to install it on Windows Server 2003 x64 R2. The error is the same as I mentioned in my reply to the topic "Discuss the VirtualBox 7.2.0 release here" in Aug 16.

[MaxF]

Autodownload of Guest Addtions ISO does not work. After actually downloading the ISO into iso.tmp file in ~/.VirtualBox directory, GUI complains about some file not found on the server, tmp file never gets renamed into iso.
If I manually rename the file, gui still can't find it when I select mount Guest Additions in the main menu. How does this work? Why virtualbox can not find a file when it's there?

[George Bouras]

all vms are crashing at boot with VERR_PDM_DRIVER_NAME_CLASH
go back to 7.2.0

[galitsyn]

After upgrading to VirtualBox 7.2.2 (from 7.2.0), none of my virtual machines can start.

I always get this error:

Code: Select all

VM Name: Ubuntu

Driver name clash. Another driver with the same name as the one being registered exists. (VERR_PDM_DRIVER_NAME_CLASH).
Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {6ac83d89-6ee7-4e33-8ae6-b257b2e81be8}

Reboot of the host didn't help.

Completely uninstalling VirtualBox, rebooting and then performing a clean re-install of VirtualBox 7.2.2 didn't help either.

Any help, please


VBox.log

Extension Pack in log is 7.2.0. Host package and Extension pack must be of the same version. Does it happen if you update it?

[edufissure]

me too

Should be and updated tutorial of how to install VB in Ubuntu 24.04 withoud headaches....as the mate said before only you have to write: sudo apt install virtualbox or virtualbox-7.1

Now i tried to install VB from scratch ( in a new computer): i had headache with USB permissions, headache downloading extension pack ( the link didnt work on top of the web,can be any download button in gui or first time installing a message similar to: No extension pack found. Its recommended to use usb... Do you want to install it ?),headache with Kvm, and another headache i cant remember right now...

So can you put it in the easy way ?

Thanks

ps: sources.list is not the preferred way right now, it should create a virtualbox.list or virutalbox.sources instead---

[ant]

Still nothing about the new releases in https://www.virtualbox.org/pipermail/vbox-announce/ mailing list.

[nixuser]

For me the VERR_PDM_DRIVER_NAME_CLASH problem was fixed by updating the extensions to 7.2.2.

On another note, on a Fedora 42 Linux host, if I go to Media and select Optical disks then try to add an ISO image, VirtualBox 7.2.2 locks up. I end up having to kill the app. Anyone else seeing this on Linux? It's not happening to me on Win10.

[MaxF]

Trying to work with some excel documents with 3d acceleration enabled crashes VM (Fedora 42 host, Windows 11 guest), I created bug report: https://github.com/VirtualBox/virtualbox/issues/225

[MaxF]

If I enter fullscreen mode (Fedora 42 host, any linux guest), mouse buttons stop working. Cursor moves, VM works, but button input is not detected for both guest and host. Mouse input recovers only after VM shutdown.

[wzis]

I have a MacOS 11 VM on Windows 11 VirtualBox VM, it was running well in VBox 7.1.11 and 7.0.26, but after updated to 7.2.2, the VM could not boot up, the screen become empty.

[granada29]

I have a MacOS 11 VM on Windows 11 VirtualBox VM, it was running well in VBox 7.1.11 and 7.0.26, but after updated to 7.2.2, the VM could not boot up, the screen become empty.

You should post this in a more appropriate forum, along with a zipped log showing the error. Please bear in mind that there is no support for running a macOS VM on anything other than a genuine Apple Mac computer.

[tgp1994]

Could someone please clarify what the status is of the 7.2.x branch versus the 7.1.x branch? Is 7.2 considered a stable upgrade path from 7.1? Is there another 7.1.x release planned in the near future?

[multiOS]

Currently 7.1.xx and 7.2.x Versions are being actively supported as shown on the Old Builds compilation page - https://www.virtualbox.org/wiki/Download_Old_Builds- and 'known' fixes are usually available on the Test Builds page pending the next maintenance releases - https://www.virtualbox.org/wiki/Testbuilds - The Test Builds for 7.2.x are currently being shown as 'Develpopment snanphots'