Discuss the VirtualBox 7.0.0 release

This is for discussing general topics about how to use VirtualBox.
dmkav
Posts: 2
Joined: 18. Oct 2022, 20:47

Re: Discuss the VirtualBox 7.0.0 release

Post by dmkav »

Unable to use existing or create new Windows 10 client on macOS Catalina (10.15.7). Both were setup to boot using EFI, which I read in Reddit is an issue with v7.

Below are the logged errors from one phase of testing. The full log for this (VB Log 1) and one other scenario are attached (VB Log 2).

Code: Select all

00:00:01.808013 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={6ac83d89-6ee7-4e33-8ae6-b257b2e81be8} aComponent={ConsoleWrap} aText={The VBoxGuestPropSvc service call failed with the error VERR_HGCM_SERVICE_NOT_FOUND}, preserve=false aResultDetail=-2900
00:00:01.901499 VMSetError: /Users/vbox/tinderbox/mac-rel/src/VBox/VMM/VMMR3/VM.cpp(336) int VMR3Create(uint32_t, PCVMM2USERMETHODS, PFNVMATERROR, void *, PFNCFGMCONSTRUCTOR, void *, PVM *, PUVM *); rc=VERR_NEM_MAP_PAGES_FAILED
00:00:01.901535 VMSetError: NEM failed to map page(s) into the VM.
00:00:01.903200 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={6ac83d89-6ee7-4e33-8ae6-b257b2e81be8} aComponent={ConsoleWrap} aText={NEM failed to map page(s) into the VM. (VERR_NEM_MAP_PAGES_FAILED)}, preserve=false aResultDetail=-6806
00:00:01.903519 Console: Machine state changed to 'PoweredOff'
00:00:01.907840 Power up failed (vrc=VERR_NEM_MAP_PAGES_FAILED, rc=NS_ERROR_FAILURE (0X80004005))
00:00:01.917575 GUI: UIMachineViewNormal::resendSizeHint: Restoring guest size-hint for screen 0 to 926x673
00:00:01.917698 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={4680b2de-8690-11e9-b83d-5719e53cf1de} aComponent={DisplayWrap} aText={The console is not powered up (setVideoModeHint)}, preserve=false aResultDetail=0
00:00:01.917759 GUI: Aborting startup due to power up progress issue detected...
00:00:01.953177 GUI: UICommon: Handling aboutToQuit request..
00:00:03.318033 GUI: UICommon: aboutToQuit request handled!
Attachments
VBox2.log
VB 7 Log 2
(29.51 KiB) Downloaded 27 times
VBox.log
VB 7 Log 1
(29.77 KiB) Downloaded 13 times
lordavatar1234
Posts: 7
Joined: 22. Sep 2017, 20:05

Re: Discuss the VirtualBox 7.0.0 release

Post by lordavatar1234 »

Unable to use existing or create new Windows 10 client on macOS Catalina (10.15.7). Both were setup to boot using EFI, which I read in Reddit is an issue with v7.

Below are the logged errors from one phase of testing. The full log for this (VB Log 1) and one other scenario are attached (VB Log 2).
Dunno about that. My EFI boot Windows 10 VMs operate just fine on Virtual Box 7. That being said, both your VBox log files include the following lines -

00:00:01.715600 HM: HMR3Init: Attempting fall back to NEM: Driverless mode
00:00:01.718664 NEM: info: Found optional import Hypervisor!hv_capability.
00:00:01.719160 NEM: info: Found optional import Hypervisor!hv_vm_space_create.
00:00:01.719187 NEM: info: Found optional import Hypervisor!hv_vm_space_destroy.
00:00:01.719200 NEM: info: Found optional import Hypervisor!hv_vm_map_space.
00:00:01.719209 NEM: info: Found optional import Hypervisor!hv_vm_unmap_space.
00:00:01.719215 NEM: info: Found optional import Hypervisor!hv_vm_protect_space.
00:00:01.719223 NEM: info: Found optional import Hypervisor!hv_vcpu_set_space.
00:00:01.719236 NEM: info: Found optional import Hypervisor!hv_vcpu_run_until.
00:00:01.719244 NEM: info: Found optional import Hypervisor!hv_vcpu_get_exec_time.
00:00:01.719253 NEM: info: Found optional import Hypervisor!hv_vmx_vcpu_read_shadow_vmcs.
00:00:01.719260 NEM: info: Found optional import Hypervisor!hv_vmx_vcpu_write_shadow_vmcs.
00:00:01.719266 NEM: info: Found optional import Hypervisor!hv_vmx_vcpu_set_shadow_access.
00:00:01.719379 NEM: info: Failed to import Hypervisor!hv_vmx_vcpu_get_cap_write_vmcs: VERR_SYMBOL_NOT_FOUND
00:00:01.719471 NEM: info: Failed to import Hypervisor!hv_vcpu_enable_managed_msr: VERR_SYMBOL_NOT_FOUND
00:00:01.719544 NEM: info: Failed to import Hypervisor!hv_vcpu_set_msr_access: VERR_SYMBOL_NOT_FOUND
00:00:01.719581 NEM: cMachTimePerNs=1 (TimeInfo.numer=1 TimeInfo.denom=1)
00:00:01.720356 NEM: Successfully created ASID: 1
00:00:01.720496 NEM:
00:00:01.720497 NEM: NEMR3Init: Turtle execution mode is active!
00:00:01.720497 NEM: Note! VirtualBox is not able to run at its full potential in this execution mode.
00:00:01.720497 NEM:
00:00:01.720624 CPUM: No hardware-virtualization capability detected


Ergo you are running Virtual Box on a Host without available VT-x / AMD-v acceleration, or if your cpu supports it, said VT-x / AMD-v acceleration is being used by some other hypervisor. This is known to cause all kinds of problems with Virtual Box, going back to the Virtual Box 5.x builds, including but not limited to, data corruption in said VMs.
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Discuss the VirtualBox 7.0.0 release

Post by mpack »

lordavatar1234 wrote: VT-x / AMD-v acceleration is being used by some other hypervisor. This is known to cause all kinds of problems with Virtual Box, going back to the Virtual Box 5.x builds, including but not limited to, data corruption in said VMs.[/color]
I don't recall lack of VT-x/AMD-v ever causing corruption problems in VirtualBox. All that happens is that VirtualBox refuses to run the VM. If some other VT-x using software has enabled the feature and not cleaned up properly when shutting down then you might get a guru meditation - again, no corruption.

Anyway in this case VirtualBox has found the MacOS Hypervisor API, so I don't see a problem with that. And it means that VT-x is present, enabled and working otherwise said API would not be working.

The error is VERR_NEM_MAP_PAGES_FAILED which sounds like a memory error. And indeed when I check the log provided I see:
00:00:01.411138 Host RAM: 16384MB (16.0GB) total, 7727MB (7.5GB) available
...
00:00:01.482149 RamSize <integer> = 0x0000000200000000 (8 589 934 592, 8.0 GiB)
00:00:01.482476 VRamSize <integer> = 0x0000000010000000 (268 435 456, 256.0 MiB)
On a Windows host I would recommend reducing VM RAM to 6GB (6144MB). On a MacOS host... I'm not entirely sure how much free RAM it likes, but you can certainly start with 6GB.

Reduce CPU cores to 2 as well.

IMO, this is pilot error. The only thing that makes this v7 specific is that v7 tries to use the MacOS hypervisor API. But the configuration errors would have caused problems (i.e. not always running cleanly) in past versions.
Paddy Landau
Posts: 43
Joined: 22. Jul 2012, 16:47
Primary OS: Ubuntu other
VBox Version: PUEL
Guest OSses: Ubuntu, Windows, other Linux

Snapshot needs to be taken twice

Post by Paddy Landau »

Whenever I take a snapshot, I need to do it twice. For example:
  • I start VirtualBox.
  • I start my guest, run updates, and close it down normally.
  • I press "Take+" to take a snapshot, name it and press OK.
  • The snapshot is saved, but the current state reads "Current State (changed)".
  • I (again) press "Take+" to take a snapshot, name it and press OK.
  • This time, the new snapshot is saved, and the current state reads only "Current State".
This used to happen only if I took a snapshot too quickly, because the guest hadn't had time to close down properly. But now, it always happens, even if I close down the guest and wait several minutes before taking the first snapshot. I've also tried running sync prior to saving the snapshot, and that didn't help.

More information:
  • VirtualBox 7.0.0 r153978 (Qt5.15.3)
  • Host: Linux Ubuntu 22.04
  • Guest: Linux Ubuntu 22.04 (this also happened with Windows 11)
Graveen
Posts: 7
Joined: 25. Nov 2018, 13:07

Re: Discuss the VirtualBox 7.0.0 release

Post by Graveen »

Hi,

More or less , the only issue i had was to uninstall VirtualBox 6.1.40, then reinstall VirtualBox 7. In place installation of VirtualBox 7 was throwing errors when starting VMs (sorry, i did not save them). Everything is working fine with my guests (Debian 11 + Win 10) after reinstall.

There is a feature i'm missing; when closing a vm, you could check a box telling to restore latest snapshot. And it was damn efficient !
Oh, everything works, i can manually restore latest snapshot, but it takes time (and i had to deny doing a new snapshot).

Now, this option is gonen is there a way to reenable it ?

Thank you vm !
adrian_vg
Posts: 12
Joined: 18. Mar 2015, 10:36

Re: VirtualBox 7.0.0 clipboard

Post by adrian_vg »

galitsyn wrote:
adrian_vg wrote:
Mario TT wrote:Mod edit: originally posted in "Windows Guests".

Hello.

I just upgraded to VirtualBox 7.0.0 and verified that I have a problem with the clipboard. I installed Quest Additions 7.0.0 and I have the clipboard enabled bidirectionally, yet if I try to copy a long text the copy-paste does not work. I have checked that this happens with text longer than 2048 characters (if it has less characters the copy-paste works correctly). Does anyone have the same problem or do you know if this is a more general problem?
I have reinstalled Guest Additions and have not been able to get the clipboard to work properly. Any ideas what might be happening?

Thanks in advance to everyone.
Just installed Virtualbox 7.0 and ran into the clipboard issue, again.
Bidirectional is enabled on the vm.
Extentions is installed.

Virtualbox is running on a Kubuntu Desktop 22.04 and the vm is running Ubuntu Server 22.04 with no GUI, just the CLI/terminal.
Can't copy anything to or from the vm terminal, long or short texts.

I've had this issue for years, ever since Virtualbox 6 was released IIRC.

How can this still be an issue so many years on?
Not trying to diss a free software that is also a very good one, but copy and paste is kind of a crucial feature in any IT environment.
Hi adrian_vg,

Can it be a case if host or guest is running in Wayland environment? Pure Wayland is not yet supported (only guest screen resize can work with some compositors). Clipboard sharing in XWayland or X11 should work though.
You mean my host?
The below implies xorg I think.

Code: Select all

adrian_vg@lanfear2:~$ echo $XDG_SESSION_TYPE
x11
The guests are terminal-only server installs, no GUI/DE at all, just a boring black screen with green text.
Am not sure, but neither a Wayland or X11 environment should be needed in those cases.
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Discuss the VirtualBox 7.0.0 release

Post by mpack »

mpack wrote: The error is VERR_NEM_MAP_PAGES_FAILED which sounds like a memory error.
The devs report fixing a bug that causes this on MacOS hosts. The fix is included in yesterdays 7.0.2 release.
Paddy Landau
Posts: 43
Joined: 22. Jul 2012, 16:47
Primary OS: Ubuntu other
VBox Version: PUEL
Guest OSses: Ubuntu, Windows, other Linux

Re: VirtualBox 7.0.0 clipboard

Post by Paddy Landau »

adrian_vg wrote:The guests are terminal-only server installs, no GUI/DE at all
That's your problem. Copy and paste require Guest Additions to be running in a GUI. They won't work in a console-only environment. Even if you're logged into a GUI, and press Ctrl+Alt+F3 to get a console, it won't work in the console.
adrian_vg
Posts: 12
Joined: 18. Mar 2015, 10:36

Re: VirtualBox 7.0.0 clipboard

Post by adrian_vg »

Paddy Landau wrote:
adrian_vg wrote:The guests are terminal-only server installs, no GUI/DE at all
That's your problem. Copy and paste require Guest Additions to be running in a GUI. They won't work in a console-only environment. Even if you're logged into a GUI, and press Ctrl+Alt+F3 to get a console, it won't work in the console.
Oh, that's by design then?
Didn't realize that!

Thanks for the info. :!:

In hindsight, it'd be really cool if copy-paste to-from a terminal would work as well.
For now it's a major bummer though. :(
fth0
Volunteer
Posts: 5668
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: Discuss the VirtualBox 7.0.0 release

Post by fth0 »

Paddy Landau wrote:Copy and paste require Guest Additions to be running in a GUI.
To be more precise, the VirtualBox Guest Additions require an X11 clipboard (in the Linux case). If the Linux guest uses Wayland instead of X11, they require XWayland, which provides an X11 clipboard.
Paddy Landau
Posts: 43
Joined: 22. Jul 2012, 16:47
Primary OS: Ubuntu other
VBox Version: PUEL
Guest OSses: Ubuntu, Windows, other Linux

Re: Discuss the VirtualBox 7.0.0 release

Post by Paddy Landau »

fth0 wrote:To be more precise, the VirtualBox Guest Additions require an X11 clipboard (in the Linux case). If the Linux guest uses Wayland instead of X11, they require XWayland, which provides an X11 clipboard.
My host is Ubuntu 22.04 on X.Org (XDG_SESSION_TYPE = x11), and my guest Ubuntu 22.04 on Wayland (XDG_SESSION_TYPE = wayland). Copy-and-paste works. So, I don't think that XWayland is required on the guest.
fth0
Volunteer
Posts: 5668
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: Discuss the VirtualBox 7.0.0 release

Post by fth0 »

Paddy Landau wrote:I don't think that XWayland is required on the guest.
Did you check that XWayland isn't running? I don't know the details, but I thought that many Linux distributions additionally run XWayland in Wayland sessions.
Paddy Landau
Posts: 43
Joined: 22. Jul 2012, 16:47
Primary OS: Ubuntu other
VBox Version: PUEL
Guest OSses: Ubuntu, Windows, other Linux

Re: Discuss the VirtualBox 7.0.0 release

Post by Paddy Landau »

fth0 wrote:Did you check that XWayland isn't running? I don't know the details, but I thought that many Linux distributions additionally run XWayland in Wayland sessions.
Thank you for that. I thought that Wayland and XWayland were mutually exclusive, but it appears that I was wrong. You are correct: Ubuntu 22.04 does indeed have XWayland installed. My bad.
haktivist3838
Posts: 1
Joined: 22. Oct 2022, 09:45

Re: Discuss the VirtualBox 7.0.0 release

Post by haktivist3838 »

I deleted a file, this is the last situation
I reinstalled but it didn't work
please help me


********
A differencing image of snapshot {ca10732e-f023-42f8-87b2-86d55044636a} could not be found. Could not find an open hard disk with UUID {45f3a4a3-ff6c-428d-be76-4fc6a0d3ef8b}.
Result Code:
E_FAIL (0X80004005)
Component:
SnapshotMachine
Interface:
IMachine {300763af-5d6b-46e6-aa96-273eac15538a}
*********
Attachments
rr2.png
rr2.png (46.96 KiB) Viewed 8265 times
rr1.png
rr1.png (36.98 KiB) Viewed 8265 times
Pipo
Posts: 3
Joined: 22. Oct 2022, 13:45

Host: Mac Intel, Guest: Win11, freezes with guest additions

Post by Pipo »

Hi,
I upgraded from latest 6.x to 7.0.0, and all existing VMs (Win10, CentOS 7, MacOS High Sierra) are running fine. I tried the new Win11 capabilites and installed it with default settings except using bridged network adapter, 4 cores, 8 GB RAM.
Host is Intel Mac 27" / 2020, with 40 GB of RAM and 8 core i7, OSX 12.6.
Guest is Windows 11 Pro 22H2 (error occured too with 22H1).
The error occurs with both VirtualBox 7.0.0 and 7.0.2.
Windows 11 installation works ok, Windows 11 Pro runs for hours without Guest Additions.
When I install Guest Additions (I have to do this manually after clicking Devices/Install Guest Additions ISO Image while it is working automatically on the existing Windows 10 VM) and reboot, the VM always freezes after 1 to 5 minutes. Only Power Off is possible.
I found similar error reported for Win 11 on Linux hosts.
Regards, Michael
Attachments
Windows 11-2022-10-22-14-09-15.log.zip
(40.72 KiB) Downloaded 14 times
Locked