Discuss the VirtualBox 7.2.6 release here

[galitsyn]

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

Changelog is here.

[OliverL]

The installer does not start on Windows on Arm.

[gpbraz]

Hello,
just upgraded from 7.2.4 to 7.2.6 (Win11 25H2 Host)

Almalinux 10.1 VM started without any problem but all my Win11 25H2 guests don't start:

• the screen stays black
  • there is never any virtual HDD activity
    • there is a few CPU activity (no hint about what it does since HDD activity is absent)
    but the Windows VMs never begin to start.
    
    Already tried to:
    • uninstall 7.2.4</list>
      • reboot</list>
        • install 7.2.6</list>
          • reboot</list>
            
            but this doesn't solve the problem.
            
            Could someone please help me?
            
            Thanks in advance

[gpbraz]

Found the culprit, post here so it can be useful for others:

Core isolation was enabled (and Virtulbox 7.2.4 was working with it enabled) on the host.

Disabling it and rebooting solved the problem

Best Wishes

[AndyCot]

Does it fix the network issues posted since the 7.2.0 release in the forum?

[OreCutter]

Bad bug:

The 7.2.6 Guest additions prevent any changes to the display resolution of at least Windows 10 clients. Where resolution would normally be selected (right-click on Desktop, select "Display settings") the drop down under "Resolution is greyed out. Tested on multiple Windows 10 and 11 boxes running 7.2.6 guest additions with several Windows 10 VM images the work fine under 7.2.4.

If guest additions are left at version 7.2.4 the resolution can still be changed. The problem only appears after upgrading them to 7.2.6.

[FranceBB]

Unfortunately there's still a problem with NAT on Windows XP Professional x86. I've reported it here: https://github.com/VirtualBox/virtualbox/issues/167

My host is Fedora 42 x64.

Pinging and resolving the domains works (i.e ICMP/DNS succeeds) but visiting websites doesn't (i.e TCP traffic HTTP/HTTPS) as it times out across all network adapters (Virtio, Intel PRO/1000 MT Desktop, PCNet Fast III). There's definitely something that changed in the NAT engine between version 7.1.x and 7.2.x in how it handles TCP segmentation or handshakes that causes some issues on XP.

Since telnet google.com 80 works (connecting to a blank screen), the 3-way TCP handshake is succeeding. The failure only occurs when the guest tries to send a data payload (like an HTTP GET or TLS Client Hello), which likely triggers the segmentation logic that is currently broken. In other words, what I think is happening is that small packets pass, but any packet requiring segmentation by the NAT engine is dropped.

[AndyCot]

Why does Oracle "Discuss the VirtualBox 7.2.6 release here" wen they do not reply to questions?

Oracle != volunteers and super users and other long term Vb gurus.

[multiOS]

@AndyCot

I have seen occasional comments/follow up questions on specific issues from Devs, but suspect the main purpose is so that they have one key feedback thread to 'listen to'. as they simply don't have the time available to monitor all forum discussion threads/posts.

I have also noticed that the GitHub VirtualBox Issues 'page' seems to be busier than the 'old' Bugtracker reporting system was and, we have, of course, 'lost' the long-term services of those key Volunteer Forum Moderators who often did do a lot of background work on pulling issues together, maintaing the 'How to" Guides etc.

[gabo]

Windows 11 Home 25H2 host with win11 Pro 25H2 guest.

Networking, NAT/Bridged/NAT Network on guest still does not work. I have to run a virtio adapter in the guest to make it work. And that only works if I have IPv6 enabled even though I'm not using IPv6. And the virtio adapter doesn't work if I set it to NAT, only if it's set to either bridged or NAT Network.

[HKaufmann]

VirtualBox 7.2.6 is a maintenance release.

Can I install version 7.2.6 over version 7.1.6 without destroying my VMs?
Use Linux-Mint 22.3.

Greetings Holger

[ciamaulex]

Found the culprit, post here so it can be useful for others:

Core isolation was enabled (and Virtulbox 7.2.4 was working with it enabled) on the host.

Disabling it and rebooting solved the problem

Best Wishes

This may be interesting. I had the same symptoms, checked Core isolation on my PC and found three settings of which only the first is disabled (memory integrity). I am reluctant to disable the rest because it's the company laptop and before disabling stuff I'd better check it's really safe. Any hope this will be fixed? Or should I disable "Vulnerable drivers" or "LSA Protection", or both?

Thanks

[KloCZ2]

Strange thing with 7.2.6 VBox:

* host (older Intel Xeon X5650, x86_64 level 2) is Fedora 42, kernel 6.18.X

* guest VM is Fedora 42/kernel 6.18 as well (guest is running some java applications with decent/average load).

When I upgraded host from 7.1.14 to 7.2.6, guest VM is aborting after 10-20 hours of run with this last line in VBox.log :

Code: Select all

Event: forcefully unregistering passive event listener 00007f42700014a0 due to excessive queue size

No matter, whether on guest are older 7.1.14 or newer 7.2.6 GuestAdditions, it's still aborting in the same way.

Downgrade to the VBox 7.1 line (the newest 7.1.16) solved this issue, it looks like (this guest is running several days without any problems).

[gpbraz]

I noticed that there have been two Windows versions of Virtualbox 7.2.6:

the initial release was VirtualBox-7.2.6-172322-Win.exe, 115 MB

and the actual one is VirtualBox-7.2.6a-172322-Win.exe, 169 MB

Is there some changelog between them?

Thanks in advance

[Galactic]

I noticed that there have been two Windows versions of Virtualbox 7.2.6:

the initial release was VirtualBox-7.2.6-172322-Win.exe, 115 MB

and the actual one is VirtualBox-7.2.6a-172322-Win.exe, 169 MB

Is there some changelog between them?

The main difference appears to be ARM files included in the new installer. And while all the other files appear to have been rebuilt too, I'm not sure if there are any substantive differences. Since the build number wasn't incremented, I hope not.