Discuss the VirtualBox 7.1.0_BETA1 release here

[galitsyn]

You can download the release here.
Changelog is here.

[pheitman57]

After installing VirtualBox 7.1 BETA, I am unable to use Bridged Networking. No adapters show up under the Name field. I have uninstalled and reinstalled making sure that bridged networking is selected to be installed. Without bridged networking I am unable to use VirtualBox 7.1 because I use the VMs to host servers in my home network (ssh for one).

Note that I was interested in 7.1 because I have been having problems running Ubuntu 24.04 on 7.0.20. It works great on 7.1 except for this network issue.

[granada29]

I tried this release on an M1 Mac Mini running macOS Sequoia Beta.

1. Double click the extensions pack file caused VirtualBox Manager to crash.
2. Run VirtualBox Manager and install the extensions pack works fine.
3. Running an ARM64 Debian VM works well and Guest Additions installed properly.
4. Unable to run Intel VMs (tried Debian Linux and Windows 11) as they are now incorrect architecture.

Will the ability to run Intel VMs be restored or are they no longer going to be supported?

[aeichner]

The x86-on-arm feature is still not performant enough to be meant for everyday use, especially for heavy desktop operating systems like Windows or Ubuntu (or any other graphical Linux distribution for that matter). Older guests and text mode operation should work okayish if you don't expect performance miracles. You can enable running x86 guests by issuing the following command:

Code: Select all

VBoxManage setextradata global "VBoxInternal2/EnableX86OnArm" 1

But please don't report any issues with that as it is completely unsupported at the moment.
Admin edit: Note that if you put this in place it will make the "Developer Preview" marker appear in the GUI. Oh, and the command was subtly wrong initially. Fixed.

[Daniel Miller]

I recently tried out VirtualBox 7.1.0_BETA1 and it's shaping up to be a solid upgrade. The performance improvements are noticeable, with faster VM startup times and smoother operation compared to previous versions. The updated UI is more modern and intuitive, making it easier to manage virtual machines. However, since it’s a beta release, there are a few quirks and bugs here and there. Overall, it's a promising step forward, offering better hardware support and a more stable experience. Just keep in mind it’s not the final version, so some issues might still be present

[Dösbaddel]

After installing VirtualBox 7.1 BETA, I am unable to use Bridged Networking.

Can confirm. The Bridged Networking driver doesn't seem to be installed despite being selected during installation.

[quizerti]

I'm seeing unreasonably high CPU usage on my Windows 10 host when running Windows 10/11 guests. The CPU usage on the host machine doesn't seem to want to go below 32%, even when the guest is idle and has single % CPU utilisation figure shown in the guest's Task Manager in Windows.

As I type this, I have a Windows 10 headless machine running in the background at almost idle (<10% CPU) and it's chewing up 33% of my 7th gen i5. Normally this would settle down after a minute or two, but this isn't the case with the current beta.

[OllieW]

I've already tested many of the development snapshots available on the VirtualBox Testbuilds homepage and I'm happy to see some new logos in the BETA1 release now..

I'm using the macOS/Intel build on macOS 14.5 Sonoma and at least one thing that is broken (at least with the Microsoft Windows Server 2025 Release Preview build 26100 and the most actual Insider Preview build 26257 with the BETA1 guest additions) is the Drag&Drop feature leading to the following error in the guest OS

Code: Select all

Drag and drop operation from guest to host failed.

The guest was not able to retrieve the drag and drop data within time.

Result Code:VBOX_E_DND_ERROR (0X80BB0011)
Component:GuestWrap
Interface:IGuest {00892186-a4af-4627-b21f-fc561ce4473c}

and the following error report in the host OS

Code: Select all

-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Process:               VirtualBoxVM [21473]
Path:                  /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM
Identifier:            org.virtualbox.app.VirtualBoxVM
Version:               7.1.0 (7.1.0)
Code Type:             X86-64 (Native)
Parent Process:        VBoxSVC [21260]
Responsible:           VirtualBox [21258]
User ID:               501

Date/Time:             2024-07-28 15:01:52.0474 +0200
OS Version:            macOS 14.5 (23F79)
Report Version:        12
Anonymous UUID:        0216678E-5F54-BEB3-6316-648013072E38

Sleep/Wake UUID:       A4BE56E2-0789-4D46-BB1F-6BA07F53AD27

Time Awake Since Boot: 280000 seconds
Time Since Wake:       6663 seconds

System Integrity Protection: enabled

Crashed Thread:        0

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x000000000000001e
Exception Codes:       0x0000000000000001, 0x000000000000001e

Termination Reason:    Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process:   exc handler [21473]

after a second Drag&Drop action followed by a hard reboot of the guest OS

[0x4C3DD]

I have a laptop, that runs on AMD processor & Nvidia GPU, so I was wondering if there would be a setting, where I can choose whether to use the integrated graphics or the discrete one? My laptop doesn't have a MUX switch.

PS, the logo aint that pleasant to the eyes, and the colour scheme also seems based on VMware.

[multiOS]

macOS (Intel) and macOSARM versions (Cosmetic Issues)

1. VirtualBox Manager Display

BETA1 seem to be able to cope with macOS's light and dark modes, displaying normally, but if the mode selected is 'Auto' the following display appears during daylight hours:

Screenshot 2024-07-28 at 16.59.35.png (157.83 KiB) Viewed 7117 times

2. There are no new VirtualBoxLogo.icns files in the macOS builds, only a png file, so the 'old' VirtualBox Icon is still in use. EDIT: This is corrected in Development Snapshot - development revision 164292

[QwertyChouskie]

Hearing about a "modernized" GUI, I was disappointed to see that VirtualBox is still using the old and IMHO ugly "Fusion" Qt style. Switching to the Breeze Qt style would go a long way to making VirtualBox actually look like a modern program.

Also, FWIW, the logo is too abstract for me to recognize it as "VB". The "V" I can kinda see, the "B" is basically indecipherable to my eyes.

[PseudoSpock]

Unable to build Guest Additions on Arch for arm64 VM.

Code: Select all

                   -`                    censored@Archy 
                  .o+`                   ------------- 
                 `ooo/                   OS: Arch Linux ARM aarch64 
                `+oooo:                  Host: linux,dummy-virt 
               `+oooooo:                 Kernel: 6.9.12-2-aarch64-ARCH 
               -+oooooo+:                Uptime: 39 mins 
             `/:-:++oooo+:               Packages: 1295 (pacman) 
            `/++++/+++++++:              Shell: bash 5.2.26 
           `/++++++++++++++:             Resolution: 1280x800 
          `/+++ooooooooooooo/`           DE: Plasma 6.1.2 
         ./ooosssso++osssssso+`          WM: kwin 
        .oossssso-````/ossssss+`         Theme: Windows-7-2.1 [GTK2/3] 
       -osssssso.      :ssssssso.        Icons: We10X-black-dark [GTK2/3] 
      :osssssss/        osssso+++.       Terminal: konsole 
     /ossssssss/        +ssssooo/-       Terminal Font: FiraCode Nerd Font 12 
   `/ossssso+/:-        -:/+osssso+-     CPU: (4) 
  `+sso+:-`                 `.-/+oso:    GPU: 00:00.0 VMware Device 0406 
 `++:.                           `-/+/   Memory: 1289MiB / 15963MiB 
 .`                                 `/

Sorry for the domain name, thought it was funny when I built it back when covid started, but here is the failed build log 'vboxadd-setup.log'.

Hrmm, I'm not able to link externally to the log file, but it's rudely long to paste here... Let me know where I can send it to, please.

Thank you for making this build, I am certainly hoping to get off of UTM.

Some additional notes:

* Enabling 3d reliably crashes the VM after it posts, before it moves on to booting.
* I am able to set the video memory in the overview slider up from 128 to 256.
* Plasma 6 desktop, using wayland in the VM, pretty performant, despite the no 3D and no addons.
* I added widevine and tested youtube video. The videos freeze after two or three pretty slow frames.
* Snapshots working (taking them, haven't tried reverting to them yet).
* Mouse feels like it's native. Thank you for that!!! On UTM it's ALWAYS sluggish and requires extremes to get it to do anything.
* Please move host key to the right control key, like on other systems, as default.

[Shmu26]

Good performance and good looks on a Arch host with KDE, and a Win10 x64 guest.
The wayland support for clipboard sharing got me back to VirtualBox, away from Qemu with Virt-Manager.

My only complaint is the .run file to install it was a little tricky to download. Using Google Chrome, I needed to right-click and choose "save as", which gave me a file with a .txt extension. It's easy enough to change the extension back to .run, and I probably didn't even need to do that, but it took a while to figure out which hoops to jump through.

[Byroniac]

After installing VirtualBox 7.1 BETA, I am unable to use Bridged Networking.

Can confirm. The Bridged Networking driver doesn't seem to be installed despite being selected during installation.

Also, Host-Only Networking is not working or not available for me. Perhaps it has something to do with being on an AMD Ryzen 7945HX processor? Not sure. Fortunately, all I need is NAT networking (works great) with some forwarded ports. But obviously, I would prefer that the other two networking modes also worked.

EDIT: Well, I feel dumb now. After remembering a blurb I read somewhere with the Beta announcement, I installed the VirtualBox Extension Pack and I can do Bridged and Host-Only Networking now, I think. So, in other words, the functionality is available but now more restricted by license (Personal Usage License Agreement, I think?), so heads up to anyone interested.

EDIT 2: Nope, still can't do either one.

[dadw2grls]

UPDATE: Issue turned out to be bad memory. Memtest86 identified the problem.

High Disk IO Freezes Host

It doesn't matter if the high disk IO is on host or guest, as long as the guest running is Windows 10 and it's writing files to the host - the host will freeze. Ctl-Alt-F1, F2, or F3 does nothing. Mouse doesn't move, keyboard doesn't respond. Have to power cycle.

If I try the same thing with a linux guest (Linux Mint Cinnamon 22) no issues at all with the host freezing.

I had iotop running and at the time of freeze it was showing current disk read of 251.11 M/s, and disk write of 32.82 M/s

Host is clean install of Ubuntu 24.04 with latest updates
Guest is a fresh install of Windows 10 Pro with latest updates with guest addtions installed

Host Details
11th Gen Intel® Core™ i7-11700K × 16 with 32GB RAM
Two NVME's (1TB ext4 and 2TB ntfs), and one 8TB hard drive (ext4)
Using VirtualBox 7.1 Beta but the same thing happens with 7.0.20

I'm not sure how to troubleshoot further as nothing is recorded in dmesg, syslog, or journalctl.

How I tested:
1) Host-to-host copy of 38K files (1TB) from nvme to hdd - runs fine no freeze
2) Windows 10 guest running with no file activity and have performing host-to-host copy of 38K files to hdd - runs fine no freeze
3) Windows 10 guest running with BlueIris NVR running (sustained 6MB/sec file write) and host performing host-to-host copy of 38K files to hdd - system freezes in a few minutes
4) Windows 10 guest running only performing large volume file copy to host - system freezes in a few minutes

I also tried tests writing to nvme instead of the hdd - system freezes

Thank you