Discuss the VirtualBox 7.0.0 release

This is for discussing general topics about how to use VirtualBox.
Pipo
Posts: 3
Joined: 22. Oct 2022, 13:45

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

Post by Pipo »

Quoting myself:
Pipo wrote: Windows 11 installation works ok, Windows 11 Pro runs for hours without Guest Additions.
When I install Guest Additions and reboot, the VM always freezes after 1 to 5 minutes. Only Power Off is possible.
When I install the 6.1.38 Guest Additions instead of the 7.0.0 or 7.0.2 GA on that Win11 Guest, it runs fine. No freeze anymore so far.
I found this workaround in a post for freezing Win11 guests on a Linux host.
Ato
Posts: 1
Joined: 22. Oct 2022, 18:33

Re: Discuss the VirtualBox 7.0.0 release

Post by Ato »

Hi eveybody.

With VirtualBox 7.0.0 on two macOS 12.6 hosts I am unable to attach any(!) USB storage device on any Linux guest. This is independent of guest additions installed or not. Every attempt results in a `VERR_SHARING_VIOLATION` error like this one:

Code: Select all

Failed to attach the USB device TS-RDF5 Transcend [0033] to the virtual machine AlmaLinux8.
Failed to create a proxy device for the USB device. (Error: VERR_SHARING_VIOLATION).
Result Code:
NS_ERROR_FAILURE (0X80004005)
Component:
ConsoleWrap
Interface:
IConsole {6ac83d89-6ee7-4e33-8ae6-b257b2e81be8}
The good old VirtualBox 6.1.40 worked just fine with exactly the same guests.

I have already tried granting VirtualBox full "Accessibility", "Full Drive Access", "Input Monitoring" and "Files and Folders" but no luck. Can anybody please indicate to me what might be going wrong with VirtualBox 7.0.0?

Cheers,
Thomas

Edit:
Changing the USB controller from xHCI to OHCI+EHCI results in a different error message:

Code: Select all

Failed to attach the USB device TS-RDF5 Transcend [0033] to the virtual machine AlmaLinux8.
Failed to create a proxy device for the USB device. (Error: VERR_PDM_NO_USB_PORTS).
Result Code:
NS_ERROR_FAILURE (0X80004005)
Component:
ConsoleWrap
Interface:
IConsole {6ac83d89-6ee7-4e33-8ae6-b257b2e81be8}
Last edited by Ato on 24. Oct 2022, 14:57, edited 1 time in total.
Anakunda
Posts: 45
Joined: 25. Dec 2010, 13:33
Primary OS: MS Windows 7
VBox Version: OSE self-compiled
Guest OSses: Windows XP

Re: Discuss the VirtualBox 7.0.0 release

Post by Anakunda »

VBox 7 is getting better and better. After thursday's update I'm even not able to launch any guest OS:

Image

This should be stabilized quickly.
(Reinstalling VirtualBox as the error message suggests did not fix my issues)
Attachments
error.png
error.png (12.77 KiB) Viewed 4662 times
Graveen
Posts: 7
Joined: 25. Nov 2018, 13:07

Re: Discuss the VirtualBox 7.0.0 release

Post by Graveen »

Graveen wrote: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 !
Bump !

No idea on how to restore latest snapshot on close ?
fth0
Volunteer
Posts: 5661
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 »

Graveen wrote:No idea on how to restore latest snapshot on close ?
See the two posts of klaus in viewtopic.php?f=15&t=106910#p524226.
Graveen
Posts: 7
Joined: 25. Nov 2018, 13:07

Re: Discuss the VirtualBox 7.0.0 release

Post by Graveen »

fth0 wrote:
Graveen wrote:No idea on how to restore latest snapshot on close ?
See the two posts of klaus in viewtopic.php?f=15&t=106910#p524226.
Thank you VM ! I didn't see that thread :)
Hasty
Posts: 2
Joined: 30. Oct 2022, 22:43

Re: Discuss the VirtualBox 7.0.0 release

Post by Hasty »

I have macOS Montenery and I got this log. I need help with this. Please help as I am a beginner.
log is as follows:

[/USB/USBProxy/GlobalConfig/] (level 3)
00:00:00.789378
00:00:00.789378 ********************* End of CFGM dump **********************
00:00:00.789470 HM: HMR3Init: Falling back on IEM
00:00:00.789683 CPUM: No hardware-virtualization capability detected
00:00:00.789688 CPUM: fXStateHostMask=0x0; initial: 0x0; host XCR0=0x0
00:00:00.790151 CPUM: Using CPU DB entry 'Intel Core i7-6700K' (INTEL 0x6/0x5e/0x3 Intel_Core7_Skylake)
00:00:00.790225 CPUM: MXCSR_MASK=0xffff
00:00:00.790240 CPUM: Failed to query microcode revision. rc=VERR_SUP_DRIVERLESS
00:00:00.790276 CPUM: MSR fudge: 0x00000001 IA32_P5_MC_TYPE
00:00:00.790281 CPUM: MSR fudge: 0x00000017 IA32_PLATFORM_ID
00:00:00.790283 CPUM: MSR fudge: 0x0000001b IA32_APIC_BASE
00:00:00.790285 CPUM: MSR fudge: 0x0000008b BIOS_SIGN
00:00:00.790287 CPUM: MSR fudge: 0x000000fe IA32_MTRRCAP
00:00:00.790290 CPUM: MSR fudge: 0x00000179 IA32_MCG_CAP
00:00:00.790292 CPUM: MSR fudge: 0x0000017a IA32_MCG_STATUS
00:00:00.790294 CPUM: MSR fudge: 0x000001a0 IA32_MISC_ENABLE
00:00:00.790296 CPUM: MSR fudge: 0x000001d9 IA32_DEBUGCTL
00:00:00.790298 CPUM: MSR fudge: 0x000001db P6_LAST_BRANCH_FROM_IP
00:00:00.790300 CPUM: MSR fudge: 0x000001dc P6_LAST_BRANCH_TO_IP
00:00:00.790302 CPUM: MSR fudge: 0x000001dd P6_LAST_INT_FROM_IP
00:00:00.790305 CPUM: MSR fudge: 0x000001de P6_LAST_INT_TO_IP
00:00:00.790307 CPUM: MSR fudge: 0x00000277 IA32_PAT
00:00:00.790309 CPUM: MSR fudge: 0x000002ff IA32_MTRR_DEF_TYPE
00:00:00.790311 CPUM: MSR fudge: 0x00000400 IA32_MCi_CTL_STATUS_ADDR_MISC
00:00:00.790314 CPUM: MSR fudge: 0xc0000103 AMD64_TSC_AUX
00:00:00.790327 CPUM: SetGuestCpuIdFeature: Enabled SYSENTER/EXIT
00:00:00.790329 CPUM: SetGuestCpuIdFeature: Enabled SYSCALL/RET
00:00:00.790331 CPUM: SetGuestCpuIdFeature: Enabled PAE
00:00:00.790343 CPUM: SetGuestCpuIdFeature: Enabled LAHF/SAHF
00:00:00.790345 CPUM: SetGuestCpuIdFeature: Enabled NX
00:00:00.790347 CPUM: SetGuestCpuIdFeature: Enabled LONG MODE
00:00:00.790518 PGM: Host paging mode: AMD64+PGE+NX
00:00:00.790523 PGM: PGMPool: cMaxPages=1280 (u64MaxPages=1058)
00:00:00.790525 PGM: pgmR3PoolInit: cMaxPages=0x500 cMaxUsers=0xa00 cMaxPhysExts=0xa00 fCacheEnable=true
00:00:00.895036 GUI: UIMediumEnumerator: Medium-enumeration finished!
00:00:01.175118 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.193047 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenWorkAreaResized: Screen 0 work area is formally resized to: 0x25 x 1440x801
00:00:01.226100 GUI: UIMediumEnumerator: Medium-enumeration finished!
00:00:01.258330 TM: cTSCTicksPerSecond=24 013 797 (0x16e6be5) enmTSCMode=1 (VirtTSCEmulated)
00:00:01.258332 TM: cTSCTicksPerSecondHost=24 013 797 (0x16e6be5)
00:00:01.258333 TM: TSCTiedToExecution=false TSCNotTiedToHalt=false
00:00:01.258517 EMR3Init: fIemExecutesAll=true fGuruOnTripleFault=true
00:00:01.258729 IEM: TargetCpu=CURRENT, Microarch=Intel_Core7_Skylake aidxTargetCpuEflFlavour={1,1}
00:00:01.258916 GIM: Using provider 'KVM' (Implementation version: 0)
00:00:01.258927 CPUM: SetGuestCpuIdFeature: Enabled Hypervisor Present bit
00:00:01.258959 AssertLogRel /Users/vbox/tinderbox/mac-rel/src/VBox/VMM/VMMR3/GIMKvm.cpp(302) int gimR3KvmInit(PVM): RT_SUCCESS_NP(rc)
00:00:01.258963 VERR_UNSUPPORTED_CPU (-1002) - Unsupported CPU.
00:00:01.385444 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_UNSUPPORTED_CPU
00:00:01.385448 VMSetError: Unsupported CPU.
00:00:01.386078 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={6ac83d89-6ee7-4e33-8ae6-b257b2e81be8} aComponent={ConsoleWrap} aText={Unsupported CPU. (VERR_UNSUPPORTED_CPU)}, preserve=false aResultDetail=-1002
00:00:01.386288 Console: Machine state changed to 'PoweredOff'
00:00:01.387869 Power up failed (vrc=VERR_UNSUPPORTED_CPU, rc=NS_ERROR_FAILURE (0X80004005))
00:00:01.677306 GUI: UIMachineViewNormal::resendSizeHint: Restoring guest size-hint for screen 0 to 800x600
00:00:01.677364 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.677410 GUI: Aborting startup due to power up progress issue detected...
00:00:01.692265 GUI: UICommon: Commit data request...
00:00:01.703823 GUI: UICommon: Handling aboutToQuit request..
00:00:02.212024 GUI: UICommon: aboutToQuit request handled!

Please guide
stephanecharette
Volunteer
Posts: 300
Joined: 10. Nov 2007, 22:03
Primary OS: Ubuntu other
VBox Version: PUEL
Guest OSses: Ubuntu-64bit, Windows
Location: Kelowna, British Columbia, Canada
Contact:

Re: Discuss the VirtualBox 7.0.0 release

Post by stephanecharette »

Hasty wrote:I have macOS Montenery and I got this log. I need help with this. Please help as I am a beginner.
log is as follows:

00:00:00.789683 CPUM: No hardware-virtualization capability detected
00:00:00.789688 CPUM: fXStateHostMask=0x0; initial: 0x0; host XCR0=0x0
00:00:00.790151 CPUM: Using CPU DB entry 'Intel Core i7-6700K' (INTEL 0x6/0x5e/0x3 Intel_Core7_Skylake)
00:00:01.258963 VERR_UNSUPPORTED_CPU (-1002) - Unsupported CPU.
00:00:01.385444 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_UNSUPPORTED_CPU
00:00:01.385448 VMSetError: Unsupported CPU.
00:00:01.386078 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={6ac83d89-6ee7-4e33-8ae6-b257b2e81be8} aComponent={ConsoleWrap} aText={Unsupported CPU. (VERR_UNSUPPORTED_CPU)}, preserve=false aResultDetail=-1002
00:00:01.387869 Power up failed (vrc=VERR_UNSUPPORTED_CPU, rc=NS_ERROR_FAILURE (0X80004005))
Lots of references to "unsupported CPU" in your log. But I know nothing about Macs and difference between the 3 big hardware architectures and how that impacts which version of VB can run.
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 »

Unpinning this topic. Discussion continues in the Discuss the 7.0.2 release topic.
dmkav
Posts: 2
Joined: 18. Oct 2022, 20:47

Re: Discuss the VirtualBox 7.0.0 release

Post by dmkav »

dmkav wrote: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.
See ticket #21128.
legajius
Posts: 2
Joined: 8. Nov 2022, 19:36

Re: Discuss the VirtualBox 7.0.0 release

Post by legajius »

Después de actualizar a Virtual Box 7.0 mis VM Windows 10 y Windows 11 abortan, también pasa con Linux Red Hat.
1. intente varias veces y abortó, inclusive no alcanzaban a hacer el boot del sistema operativo
2. hice copia de los discos con un nuevo VM, pero después de unos minutos también tuve crash del sistema operativo.
3. Tengo un VM Linux Red Hat 7 y ha fallado, adjunto archivo con el log de la VM
4. Actualicé el extension pack.
5. estoy creando un nuevo VM en Windows 10. es muy lento llevo 20 minutos intentando crear un VM
6. Tengo Windows 11
- Edición: Windows 11 Pro
- Versión: 22H2
- Se instaló él: 21/‎09/‎2022
- Compilación del SO: 22621.755
- Experiencia: Windows Feature Experience Pack 1000.22636.1000.0
- 32 GB RAM
- 1 TB SSD


Creo que me voy a descargar una versión anterior y seguir con versión 6, hasta que la plataforma sea estable.
:roll: :roll: :roll: :roll:
Attachments
redhat-2022-11-08-12-10-18.log
(85.18 KiB) Downloaded 5 times
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 »

This is the 7.0.0 topic, your log is from 7.0.2.

In fact I'm going to lock this topic to prevent repeats of that.
Locked