Discuss the VirtualBox 7.1.0_BETA1 release here

[Byroniac]

Also, the Soft Keyboard applet cannot be closed. I can spawn multiple instances, none of which can be closed. I think I've had this problem in previous VirtualBox versions but forgot as it wasn't really an issue. I just happened to be trying to do something in particular that brought this up again.

[Byroniac]

Also, the Soft Keyboard applet cannot be closed. I can spawn multiple instances, none of which can be closed. I think I've had this problem in previous VirtualBox versions but forgot as it wasn't really an issue. I just happened to be trying to do something in particular that brought this up again.

Soft keyboard instances persist after stopping VM, so I did an End Task on them and VM shows aborted.

[Byroniac]

Also, the Soft Keyboard applet cannot be closed. I can spawn multiple instances, none of which can be closed. I think I've had this problem in previous VirtualBox versions but forgot as it wasn't really an issue. I just happened to be trying to do something in particular that brought this up again.

Soft keyboard instances persist after stopping VM, so I did an End Task on them and VM shows aborted.

What triggers the problem is if I start the Soft Keyboard in VM Full Screen, then resize VM guest display to window. I can shutdown the VM, and it will show Powered Off. I can then close VirtualBox. The Soft Keyboard persists. If I force End Task on it to get it to finally close, then the VM will show aborted when I finally go back into VirtualBox.

EDIT: Sorry, I forgot to mention that I am on Windows 11 24H2 Insider Preview, so this bug may be particular to my environment, but I thought I have seen similar behavior in VirtualBox before, though I cannot remember for sure.

[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.

Sorry to quote my own post, but I've not seen anybody else mention this issue. Am I the only one seeing high CPU usage? If so, why might that be and what can I do to find the cause?

[birdie]

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.

Sorry to quote my own post, but I've not seen anybody else mention this issue. Am I the only one seeing high CPU usage? If so, why might that be and what can I do to find the cause?

I don't know, dude, maybe someone actually did: viewtopic.php?t=111997

No idea why everyone has decided to post their issues in this thread. It used to be that people created separate threads for Beta/RC issues.

[quizerti]

I don't know, dude, maybe someone actually did: viewtopic.php?t=111997

No idea why everyone has decided to post their issues in this thread. It used to be that people created separate threads for Beta/RC issues.

Thanks for reply and taking the time to share that link with me. I think perhaps the title of the thread is making people, such as myself, post their problems here. Maybe it should have been stated that we should create separate threads with our problems.

[klaus]

Yes, with this Beta we decided to use the same posting structure as with usual releases. Clearly not so ideal when everything ends up in this thread (which was intended to absorb the usual flood of "tiny glitch here, small quirk there" post, not to handle more significant issues like the one with soft keyboard which may need multiple posts and some discussion)

[haruna]

Edit: I know this is an unsupported feature, but I just want to know how can I rescue my x86 'virtual machine' since there is a testing environment inside my VM and I can't launch it anymore in the this BETA and the latest nightly build.

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 "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.

I'm sorry but how can I enable this feature?
If I run this command directly, I will get

Code: Select all

% VBoxManage setextradata "VBoxInternal2/EnableX86OnArm" 1
VBoxManage: error: Could not find a registered machine named 'VBoxInternal2/EnableX86OnArm'
VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBoxWrap, interface IVirtualBox, callee nsISupports
VBoxManage: error: Context: "FindMachine(Bstr(a->argv[0]).raw(), machine.asOutParam())" at line 1420 of file VBoxManageMisc.cpp

If I try to enable the "VBoxInternal2/EnableX86OnArm" per VM, for example

Code: Select all

VBoxManage setextradata XP "VBoxInternal2/EnableX86OnArm" 1

It responds nothing, but I can't launch my VM. I will always get something like

Code: Select all

Callee RC:
VBOX_E_PLATFORM_ARCH_NOT_SUPPORTED (0X80BB0012)

[Stickybit]

Hi all

Looking to be a fine upgrade this one.

My findings so far:

Windows 7 / Windows 10 guest hanging restart / shutdown issue (introduced round 7.0.14 I think) seems to have jumped to this new version.

Best regards, Stickybit

[klaus]

Sorry, that post was wrong (now fixed). It must be global extradata, per-VM extradata doesn't work in this case.

Edit: I know this is an unsupported feature, but I just want to know how can I rescue my x86 'virtual machine' since there is a testing environment inside my VM and I can't launch it anymore in the this BETA and the latest nightly build.

...

I'm sorry but how can I enable this feature?
If I run this command directly, I will get

Code: Select all

% VBoxManage setextradata "VBoxInternal2/EnableX86OnArm" 1
VBoxManage: error: Could not find a registered machine named 'VBoxInternal2/EnableX86OnArm'
VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBoxWrap, interface IVirtualBox, callee nsISupports
VBoxManage: error: Context: "FindMachine(Bstr(a->argv[0]).raw(), machine.asOutParam())" at line 1420 of file VBoxManageMisc.cpp

If I try to enable the "VBoxInternal2/EnableX86OnArm" per VM, for example

Code: Select all

VBoxManage setextradata XP "VBoxInternal2/EnableX86OnArm" 1

It responds nothing, but I can't launch my VM. I will always get something like

Code: Select all

Callee RC:
VBOX_E_PLATFORM_ARCH_NOT_SUPPORTED (0X80BB0012)

[haruna]

Oh! Thank you! It works!

Sorry, that post was wrong (now fixed). It must be global extradata, per-VM extradata doesn't work in this case.

Edit: I know this is an unsupported feature, but I just want to know how can I rescue my x86 'virtual machine' since there is a testing environment inside my VM and I can't launch it anymore in the this BETA and the latest nightly build.

...

I'm sorry but how can I enable this feature?
If I run this command directly, I will get

Code: Select all

% VBoxManage setextradata "VBoxInternal2/EnableX86OnArm" 1
VBoxManage: error: Could not find a registered machine named 'VBoxInternal2/EnableX86OnArm'
VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBoxWrap, interface IVirtualBox, callee nsISupports
VBoxManage: error: Context: "FindMachine(Bstr(a->argv[0]).raw(), machine.asOutParam())" at line 1420 of file VBoxManageMisc.cpp

If I try to enable the "VBoxInternal2/EnableX86OnArm" per VM, for example

Code: Select all

VBoxManage setextradata XP "VBoxInternal2/EnableX86OnArm" 1

It responds nothing, but I can't launch my VM. I will always get something like

Code: Select all

Callee RC:
VBOX_E_PLATFORM_ARCH_NOT_SUPPORTED (0X80BB0012)

[Air Force One]

Sorry to quote my own post, but I've not seen anybody else mention this issue. Am I the only one seeing high CPU usage? If so, why might that be and what can I do to find the cause?

I can confirm exactly the same behavior on my combination, which is the same as yours. I posted about this in the separate thread about this high performance in the current beta.

[FranceBB]

Also, despite saying "Virtualbox has been installed successfully", installing using the .run script leads to a few errors which are quite scary, like

/tmp/selfgz3309020136/routines.sh: line 408: 36576 Segmentation fault (core dumped)

OS: Fedora 40 x64

Full logs here:

Code: Select all

[FranceBB@router-localhost Downloads]$ sudo ./VirtualBox-7.1.0_BETA1-164294-Linux_amd64.run
Verifying archive integrity...  100%   MD5 checksums are OK. All good.
Uncompressing VirtualBox for Linux installation  100%  
VirtualBox Version 7.1.0_BETA1 r164294 (2024-08-07T14:41:16Z) installer
Removing previous installation of VirtualBox 7.0.20 r163906 from /opt/VirtualBox
Installing VirtualBox to /opt/VirtualBox
Python found: python2.7, installing bindings...
Traceback (most recent call last):
  File "./vboxapisetup.py", line 41, in <module>
    sys.exit(setup.main())
  File "vboxapi/setup.py", line 306, in main
  File "vboxapi/setup.py", line 137, in testVBoxAPI
  File "/opt/VirtualBox/sdk/bindings/xpcom/python/xpcom/client/__init__.py", line 381, in __getattr__
    return getattr(interface, attr)
  File "/opt/VirtualBox/sdk/bindings/xpcom/python/xpcom/client/__init__.py", line 467, in __getattr__
    return XPTC_InvokeByIndex(self._comobj_, method_index, args)
xpcom.Exception: 0x80004005 (Operation failed (NS_ERROR_FAILURE))
Python found: python3.6, installing bindings...
Python found: python3.11, installing bindings...
Python found: python3.12, installing bindings...
/tmp/selfgz3309020136/routines.sh: line 408: 36576 Segmentation fault      (core dumped) $SHELL -c "cd ${PYTHON_INSTALLER_PATH} && ${PYTHON_BIN} ./vboxapisetup.py install                    --record $CONFIG_DIR/python-$CONFIG_FILES"

VirtualBox has been installed successfully.

You will find useful information about using VirtualBox in the user manual
  /opt/VirtualBox/UserManual.pdf
and in the user FAQ
  http://www.virtualbox.org/wiki/User_FAQ

We hope that you enjoy using VirtualBox.

You have new mail in /var/spool/mail/FranceBB
[FranceBB@router-localhost Downloads]$ 

[111andre111]

I tried to use Display `VMSVGA` and `Enable 3D Acceleration`, just for fun.

That's not working at the moment.

For me it ends up with an exception in `dxvk-cs` on a Silicon Mac and the only thing I realized that Virtualbox uses a really old MoltenVK driver:

00:00:01.181842   Driver : MoltenVK 0.2.2017

However the most recent vulkan SDK 1.3.290.0 using vulkaninfo shows `MoltenVK 1.2.9` which is a lot newer.
So I tried to replace just for fun `libMoltenVK.dylib` with the newer one, but that ended in another crash, which makes me think it would rather need more as it's delivered with the Virtualbox release.
But probably it would be worth exploring that path.
It would be great probably for some UI Desktop machines, but it's not a big deal at least for me.


Another issue I realized is the configuration for kickstart unattended installation of VMs.
For instance if I use following command:

VBoxManage unattended install <vm> --iso=<isoname of linux>.iso --start-vm=gui --script-template=config/ks.cfg --post-install-template=config/post.sh --extra-install-kernel-parameters='net.ifnames=0 biosdevname=0 inst.gpt inst.stage2=hd:LABEL=CENTOS quiet'

I end up with errors:

VBoxManage: info: Using values:
                           isoPath = /Volumes/.../<isoname>.iso
                              user = vboxuser
                          password = changeme
                     user-password = changeme
                    admin-password = 
                      fullUserName = 
                        productKey = 
                  additionsIsoPath = /Applications/VirtualBox.app/Contents/MacOS/VBoxGuestAdditions.iso
             installGuestAdditions = false
              validationKitIsoPath = 
            installTestExecService = false
                            locale = en_US
                           country = US
                          timeZone = Europe/Berlin
                             proxy = 
                          hostname = <hostname>.myguest.virtualbox.org
       packageSelectionAdjustments = 
                 auxiliaryBasePath = /Volumes/<...>/Unattended-<uuid-
                        imageIndex = 1
                scriptTemplatePath = /Users/.../config/ks.cfg
     postInstallScriptTemplatePath = /Users/.../config/post.sh
                postInstallCommand = 
      extraInstallKernelParameters = net.ifnames=0 biosdevname=0 inst.gpt inst.stage2=hd:LABEL=CENTOS quiet
                          language = en-US
                  detectedOSTypeId = Oracle_64
                 detectedOSVersion = 8.7.0
                  detectedOSFlavor = 
               detectedOSLanguages = en-US
                   detectedOSHints = 
VBoxManage: info: Waiting for VM '<vmname>' to power on...
VBoxManage: error: VISO: Error setting name '/ks.cfg' on '/Volumes/.../Unattended-<uuid>-ks.cfg': VERR_ALREADY_EXISTS (VERR_ALREADY_EXISTS).
VBoxManage: error: VD: error VERR_ALREADY_EXISTS opening image file '/Volumes/.../Unattended-<uuid>-aux-iso.viso' (VERR_ALREADY_EXISTS).
VBoxManage: error: Failed to open image '/Volumes/.../Unattended-<uuid>-aux-iso.viso' in read-only mode (VERR_ALREADY_EXISTS).
VBoxManage: error: PIIX3 cannot attach drive to the Primary Master (VERR_ALREADY_EXISTS)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole

Is there any idea how to fix this? I did a lot of tests, but nothing succeeded.
Before the `unattended` command the directory is definitely empty, so I don't have any clue why the `VERR_ALREADY_EXISTS` error.

Apart from that = thanks a lot and keep up the good work.

[Stickybit]

For the Windows version "list bridgedifs" returns an empty result:

C:\Windows\System32>"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" list bridgedifs
C:\Windows\System32>

Best regards, Stickybit