Discuss the VirtualBox 7.0.2 release

This is for discussing general topics about how to use VirtualBox.
Liz389
Posts: 14
Joined: 22. Oct 2022, 16:49
Primary OS: MS Windows 10
VBox Version: OSE other
Guest OSses: Windows 7, Vista, 2000

Re: Discuss the VirtualBox 7.0.2 release

Post by Liz389 »

scottgus1 wrote:
Liz389 wrote:is anybody actually looking into this? Are any more information required? When can we expect this will be repaired to the working state
I very strongly doubt that the devs have abandoned Virtualbox. It usually takes several minor version releases until a major version becomes stable enough.

If you want stable Virtualbox for important VMs that must stay running, stay on 6.1. If you want to provide data for helping get 7.0 going, keep trying 7.0.
Yes, I absolutely want to help getting version 7.0 into working state. That's why I have provided detailed information about the broken graphics output that I get in Windows 7 and Windows Vista guests.

To make it very clear: The exactly same VM on the exactly same host system works perfectly fine in version 6.1.40. After upgrade to 7.0(.2) it becomes broken/unusable :cry:

Please see here for all the details that I have provided:
* viewtopic.php?f=2&t=107519
* viewtopic.php?f=1&t=107493&start=30#p526317

Developers should compare what has changed in code between version 6.1.40 and 7.0.2 regarding the graphics output. That change obviously was wrong and must be reverted to the working state :!:

I mean, this is not some "Beta" version that were are talking about here. It is the current "stable" release of VirtualBox! It should not have such serious bugs, especially it should not break things that have been working.

But, so far, the bug was neither confirmed by the developers — do they already know the bug? are they working on it? — nor any additional details/information was requested from me :oops: :evil:

BTW: I have provided the logs that were requested, but it says "Not downloaded yet". So nobody actually looked at the logs ???
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.2 release

Post by fth0 »

Liz389 wrote:Developers should compare what has changed in code between version 6.1.40 and 7.0.2 regarding the graphics output.
That's quite easy, and the answer is: Everything! The previous VMSVGA 3D implementation (Direct3D 9 compatible) has been completely replaced by a new VMSVGA 3D implementation (DirectX 11 compatible). Since this is one of the major features of VirtualBox 7, which took several years of development, it should be obvious that there will be no way back. If you prefer the old implementation currently works better for you, simply use VirtualBox 6.1.40.
Liz389 wrote:So nobody actually looked at the logs ???
Could be. For example, I didn't look at the logs because I don't expect them to indicate the cause of the error. The same will probably hold true for the VirtualBox developers. Besides that, I think you weren't the first user to report the issue. Nonetheless, I recognize that you made some effort when you reported it.

Edit:
Replaced stroke through text by underlined text above.
Last edited by fth0 on 30. Oct 2022, 12:08, edited 1 time in total.
Armando
Posts: 101
Joined: 26. May 2012, 06:50

Re: Discuss the VirtualBox 7.0.2 release

Post by Armando »

Liz389 wrote: ... this is not some "Beta" version that were are talking about here. It is the current "stable" release of VirtualBox! ...
It has to be remembered, however, that the very "latest", newly released version of any software, is obviously more likely to bear some potentially "problematic" innovation.
It is no coincidence, I guess, that when introducing a new VBox "branch" (7.x, in this case) the previous one continues, for a while, to be the subject of development and support, so that those who absolutely need stability for critical uses can continue to operate in conditions of minimum risk, while the new branch gets consolidated (maybe I'm wrong, but I assume that's the purpose).
fth0 wrote: ... If you prefer the old implementation, simply use VirtualBox 6.1.40. ...
Actually, IMHO, talking about preference would make sense when comparing two versions that work differently, but still both work.
If one of the two simply doesn't work, totally preventing the use of VMs which run great with the other, then there is very little to "prefer".


Anyway, I think that all of this can be considered quite "normal", especially when a new version brings quite heavy technical changes.
Perhaps the developers could have waited a little longer before releasing, but it is also true that in this way, "using" the users (also) as... testers, any significant problems get highlighted (and hopefully solved) earlier.
And I think this is definitely a "price" we can accept to pay for such a powerful and useful piece of software. :]
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Discuss the VirtualBox 7.0.2 release

Post by scottgus1 »

Armando's thoughts on the state of 7.0 are spot on, Liz. I've said the same thing: 7.0 is still very new with tons of changes, and these bugs need to get caught.

FWIW a poster in the Beta subforum also asked why the devs haven't responded much to reported bugs and logs. The response was that they were looking, but not responding as much as in previous beta releases. This response level cuts both ways. We might not ostensibly hear a dev response to every one of our reports, but the devs are coding more and fixing more bugs too.
Armando wrote:"using" the users (also) as... testers, any significant problems get highlighted (and hopefully solved) earlier.
And I think this is definitely a "price" we can accept to pay for such a powerful and useful piece of software. :]
Spot on again. And free, we might add. We do get this program for free, so we have to take what we get. And we do help the devs find bugs when we use the free software and report the bugs. There's millions of computers in the "wild" with hundreds of thousands of configurations. The devs can't test all these configurations. So they rely on our bug reports to help them get a better product. It's all part of the FOSS experience.

6.1 is stable. 7.0 isn't yet, wont be for some more versions. Fact of life and just the way it is for now.
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.2 release

Post by Paddy Landau »

When I close a guest machine and take a snapshot, the first time I do so, it shows, "Current state (changed)". I have to take a snapshot a second time for it to show just "Current state".

This used to happen on VB version 6 if I took a snapshot before the guest had completely shut down. But, on VB version 7, it always happens, even if I wait several minutes after the guest has shut down.

What is the story here?

Host: Ubuntu Linux 22.04
Guests: All guests, including Ubuntu Linux 22.04, Pop!_OS 22.04, Windows 11
Hasty
Posts: 2
Joined: 30. Oct 2022, 22:43

VirtualBox 7.0.2 crashes in MacOs Ventura

Post by Hasty »

I need help. I have MacOs Ventura and I have an ISO file for Kali Linux. Once I mount the image and adjust the settings. I get this log. Please help.


00:00:00.604726
00:00:00.604726 [/USB/USBProxy/GlobalConfig/] (level 3)
00:00:00.604727
00:00:00.604727 ********************* End of CFGM dump **********************
00:00:00.604807 HM: HMR3Init: Falling back on IEM
00:00:00.605265 CPUM: No hardware-virtualization capability detected
00:00:00.605270 CPUM: fXStateHostMask=0x0; initial: 0x0; host XCR0=0x0
00:00:00.605973 CPUM: Using CPU DB entry 'Intel Core i7-6700K' (INTEL 0x6/0x5e/0x3 Intel_Core7_Skylake)
00:00:00.606032 CPUM: MXCSR_MASK=0xffff
00:00:00.606046 CPUM: Failed to query microcode revision. rc=VERR_SUP_DRIVERLESS
00:00:00.606067 CPUM: MSR fudge: 0x00000001 IA32_P5_MC_TYPE
00:00:00.606070 CPUM: MSR fudge: 0x00000017 IA32_PLATFORM_ID
00:00:00.606072 CPUM: MSR fudge: 0x0000001b IA32_APIC_BASE
00:00:00.606074 CPUM: MSR fudge: 0x0000008b BIOS_SIGN
00:00:00.606076 CPUM: MSR fudge: 0x000000fe IA32_MTRRCAP
00:00:00.606078 CPUM: MSR fudge: 0x00000179 IA32_MCG_CAP
00:00:00.606080 CPUM: MSR fudge: 0x0000017a IA32_MCG_STATUS
00:00:00.606082 CPUM: MSR fudge: 0x000001a0 IA32_MISC_ENABLE
00:00:00.606092 CPUM: MSR fudge: 0x000001d9 IA32_DEBUGCTL
00:00:00.606094 CPUM: MSR fudge: 0x000001db P6_LAST_BRANCH_FROM_IP
00:00:00.606096 CPUM: MSR fudge: 0x000001dc P6_LAST_BRANCH_TO_IP
00:00:00.606097 CPUM: MSR fudge: 0x000001dd P6_LAST_INT_FROM_IP
00:00:00.606099 CPUM: MSR fudge: 0x000001de P6_LAST_INT_TO_IP
00:00:00.606101 CPUM: MSR fudge: 0x00000277 IA32_PAT
00:00:00.606103 CPUM: MSR fudge: 0x000002ff IA32_MTRR_DEF_TYPE
00:00:00.606105 CPUM: MSR fudge: 0x00000400 IA32_MCi_CTL_STATUS_ADDR_MISC
00:00:00.606108 CPUM: MSR fudge: 0xc0000103 AMD64_TSC_AUX
00:00:00.606118 CPUM: SetGuestCpuIdFeature: Enabled SYSENTER/EXIT
00:00:00.606120 CPUM: SetGuestCpuIdFeature: Enabled SYSCALL/RET
00:00:00.606122 CPUM: SetGuestCpuIdFeature: Enabled PAE
00:00:00.606134 CPUM: SetGuestCpuIdFeature: Enabled LAHF/SAHF
00:00:00.606136 CPUM: SetGuestCpuIdFeature: Enabled NX
00:00:00.606138 CPUM: SetGuestCpuIdFeature: Enabled LONG MODE
00:00:00.606630 PGM: Host paging mode: AMD64+PGE+NX
00:00:00.606635 PGM: PGMPool: cMaxPages=1280 (u64MaxPages=1058)
00:00:00.606639 PGM: pgmR3PoolInit: cMaxPages=0x500 cMaxUsers=0xa00 cMaxPhysExts=0xa00 fCacheEnable=true
00:00:00.646119 GUI: UIMediumEnumerator: Medium-enumeration finished!
00:00:00.922665 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:00.929369 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenWorkAreaResized: Screen 0 work area is formally resized to: 0x25 x 1440x799
00:00:01.061485 TM: cTSCTicksPerSecond=24 012 306 (0x16e6612) enmTSCMode=1 (VirtTSCEmulated)
00:00:01.061491 TM: cTSCTicksPerSecondHost=24 012 306 (0x16e6612)
00:00:01.061492 TM: TSCTiedToExecution=false TSCNotTiedToHalt=false
00:00:01.062977 EMR3Init: fIemExecutesAll=true fGuruOnTripleFault=true
00:00:01.063471 IEM: TargetCpu=CURRENT, Microarch=Intel_Core7_Skylake aidxTargetCpuEflFlavour={1,1}
00:00:01.064069 GIM: Using provider 'KVM' (Implementation version: 0)
00:00:01.064086 CPUM: SetGuestCpuIdFeature: Enabled Hypervisor Present bit
00:00:01.064126 AssertLogRel /Users/vbox/tinderbox/mac-rel/src/VBox/VMM/VMMR3/GIMKvm.cpp(302) int gimR3KvmInit(PVM): RT_SUCCESS_NP(rc)
00:00:01.064136 VERR_UNSUPPORTED_CPU (-1002) - Unsupported CPU.
00:00:01.191139 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.191146 VMSetError: Unsupported CPU.
00:00:01.192078 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.192233 Console: Machine state changed to 'PoweredOff'
00:00:01.194585 Power up failed (vrc=VERR_UNSUPPORTED_CPU, rc=NS_ERROR_FAILURE (0X80004005))
00:00:01.488837 GUI: UIMachineViewNormal::resendSizeHint: Restoring guest size-hint for screen 0 to 800x600
00:00:01.488890 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.488941 GUI: Aborting startup due to power up progress issue detected...
00:00:01.502562 GUI: UICommon: Commit data request...
00:00:01.517193 GUI: UICommon: Handling aboutToQuit request..
00:00:02.210709 GUI: UICommon: aboutToQuit request handled!

Regards
JKelly
Posts: 7
Joined: 9. Jun 2016, 03:43

Re: Discuss the VirtualBox 7.0.2 release

Post by JKelly »

Testing 7.02 with existing VM

Underlying HOST hardware - AMD Ryzen 5800X and Nvidia 3700 with current drivers on WIN10 Pro

WINDOWS VM (using 6 or 8GB of memory for 64 bit guests)
Win 11 - Transparency issues with display driver (both 6.1.38 and 7.0.2), must turn 3D acceleration OFF to use VM. Works fine with 3d acceleration off.
With 3d acceleration on, display often is unusable because of black text on black background (Notepad) or too much transparency. Starts easily though.
Win 10 (64 and 32) - Transparency issues with display driver (both 6.1.38 and 7.0.2), must turn 3d acceleration OFF to use VM, Works fine with 3d acceleration off
Win 8.1 (64 and 32) - Transparency issues with display driver (both 6.1.38 and 7.0.2), must turn 3d acceleration OFF to use VM
Win 7(64) - Transparency issues with display driver (using either VB 6.1.38 and 7.0.2 display drivers), must turn 3d acceleration OFF to use VM,
With 3d acceleration off, some Win7 programs do not work No issues if revert to VB 6.1.38 and 6.1.40 on Host.
Win XP/Pro - No issues, works fine, did not update the display driver to VB 7.0.2. Don't know why XP/Home crashes and XP/Pro does not.
Win XP/Home - VM will not start, immediate crash at loading screen - works fine with VB 6.1.38 and 6.1.40, without updating the display driver
Win 2000 - VM will not start, immediate crash at loading screen - works fine with VB 6.1.38 and 6.1.40, without updating the display driver
Win 98SE - VM will not start, immediate crash at loading screen. VDI file is corrupted when shutdown - old VDI file works fine with VB 6.1.38 and 6.1.40.

UBUNTU VM
Ubuntu 22.04 - works fine with no issues when 3d acceleration turned on.
Linux Mint 21 - works fine with no issues when 3d acceleration turned on.
Ubuntu 22.10 - this new release has issues with sound because of Ubuntu change to Pulse?? I don't think the sound issue is due to VB.

TPM testing in VB 7.0.2 - using my hardware with a real TPM (Ver, 2.0 and Ver. 1.2) for the host machines.

TPM Ver 2.0 - VB 7.0.2 uses IBM software emulation of a TPM.
Win 10 (64) - works fine, but VB emulation (not a VB issue) means that drive encryption does not work (Windows demands that Hyper-V be turned on with a Microsoft account)
Win 8.1 (64) - driver won't start (Code 10)

TPM Ver 1.2 - VB 7.0.2 uses IBM software emulation of a TPM - tested with a Host machines: TPM version 2.0 and TPM version 1.2
Win 10 - immediate crash with VB starts, writes to an invalid memory location
Win 8.1 (64 and 32) - immediate crash with VB starts, writes to an invalid memory location

John
Katapult
Posts: 2
Joined: 7. Nov 2022, 18:02

Re: Discuss the VirtualBox 7.0.2 release

Post by Katapult »

Hello, I am a simple user of virtualbox and I would like to contribute to a bug that I have encountered since the clean installation on my Mac computer running under the Ventura system and VirtualBox version 7.0.2 With Ubuntu LTS 22.10.

I can't connect any USB device. I always get an error. I saw on the forum that in previous versions, you had to connect your device by selecting USB 1 mode, I tried, it doesn't work, not even in USB2, not even in USB3... I hope you You can try to correct this problem, because everything worked perfectly when I ran on the previous version of the operating system and with version 6 of the virtual box.
ciamaulex
Posts: 9
Joined: 22. Nov 2017, 13:57
Primary OS: MS Windows 7
VBox Version: PUEL
Guest OSses: Windows XP, Windows 7, Windows 2016, Debian

Re: Discuss the VirtualBox 7.0.2 release

Post by ciamaulex »

Hi, just wanted to give a positive note to developers: on my system, 7.0.2 works very well.

No issues at all with XP and Win7.
Some trouble with Win11:
- initially, enabling 3D acceleration would freeze the system randomly. Had to disable it
- after last updates (KB5018341, KB5018496, KB5020622, KB5019980) the situation seems opposite: random freezing without 3D acceleration, no freezing when active

I just disabled all power saving options, activated dark mode (which makes transparent stuff more readable until the transparency effects are fixed) and in web browser, turned off "Use graphics acceleration when available".
Now it's almost perfect.
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.2 release

Post by Paddy Landau »

ciamaulex wrote:Some trouble with Win11:
- initially, enabling 3D acceleration would freeze the system randomly. Had to disable it
- after last updates (KB5018341, KB5018496, KB5020622, KB5019980) the situation seems opposite: random freezing without 3D acceleration, no freezing when active
Thank you for this. I also initially had to disable 3D, but now have frequent freezing.

To see if the freezing goes away, I re-enabled 3D. But it's a mess! The display is at times unreadable. For example, I cannot read anything in Notepad, whether I enable dark mode or not, and whether I enable transparency effects or not.

This is a real shame. I have to use Windows with 3D disabled, and take a snapshot every few minutes (!) because it freezes so frequently! I'm lucky that so little of my work is in Windows.
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.2 release

Post by fth0 »

Several issues of VirtualBox 7.0.2r154219 have been fixed in the VirtualBox test builds 7.0.3r154539 and newer.

Additionally, several issues of VirtualBox 6.1.40r154048 have been fixed in the VirtualBox test builds 6.1.41r154521 and newer.
gskoczylas
Posts: 1
Joined: 12. Nov 2022, 18:17

Re: Discuss the VirtualBox 7.0.2 release

Post by gskoczylas »

I'm currently using VirtualBox 6.1.40, and I wanted to try version 7.0.2. However, as I have seen quite a few posts in various forums about various problems with this version of the software, so I wanted to try it out first. This might be a bit crazy, but I've heard noise that you can install VirtualBox inside other VirtualBox.

I ran my Windows 10 Professional VM in VirtualBox 6, took a snapshot and wanted to install VirtualBox 7. After running the installer, I saw a message that I needed to install some C++ libraries. It took me a while to find where to download the libraries from, but I finally found and installed them.

I tried again to install VB7. At first, it was going well, but then I saw a message that I didn't have python-core installed. I was able to continue installing, but the message warned that I would then have to configure it manually. In this situation, I stopped installing and started looking for how to install python-core.

I quickly found that I had to run the command “pip install python-core”. As far as I know, in order to have a “pip” program, I have to install “Python”.

I first installed the latest version of “Python”. There were no problems.

I then executed the command “pip install python-core” in character mode. It failed, unfortunately. The program displayed a message that it could not find something. As I had no idea what the issue was this time, so that's where my VirtualBox 7 adventure ended for now. I decided to wait until an installer was available to install VB7 for the average person.

Perhaps the source of these issues was that I was installing VB7 in a VB6 VM. If not, then — in my opinion — the installer should be more refined, that is, it should install everything it needs by itself, rather than forcing users to install a whole chain of related programs and libraries.
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.2 release

Post by fth0 »

FWIW, you only need the Python installation if you want to write Python programs to handle VMs, so it's perhaps a question of better wording, and you can ignore this warning.

Regarding the Microsoft Visual C++ Runtime, see my explanation in WH - Microsoft Visual C++ 2019 Redistributable.
Ptero-4
Posts: 2
Joined: 16. Nov 2019, 01:32

Re: Discuss the VirtualBox 7.0.2 release

Post by Ptero-4 »

MaxPF wrote:
mjf wrote:WindowsXP VM won't start

VirtualBox 7.0.2 can't start my rarely used WindowsXP VM. It shows a startup screen but then stops and reports 'Aborted'. No trouble with VirtualBox 6.1.
This isn't limited to Windows XP. It also happens with Windows 2000.

I'm running 7.0.2 on a Linux host (RHEL 9.0). I've had this Windows 2000 guest since v5.x.x, and most recently it ran perfectly fine on v6.1.40. I never ran v7.0.0, so I cannot say whether it would run on that. On 7.0.2 the virtual machine only gets past the very initial start (white bar at bottom scrolling from left to right, for anyone who remembers a WIn2K bootup sequence), and then freezes on a black screen. Normally, the screen goes blank momentarily and then the Windows 2000 splash screen comes up. It never gets to that point on 7.0.2.

Perhaps it is a problem with 32 bit guests?
I'm using VB 7.0.2 on Xubuntu 22.04. Windows NT 4.0, 2k, XP, 8, 8.1 and 10 work properly and the GA install and work properly with 3D accel. The ones that "just happen" to not work unless you disable 3D accel are the 2 ones that have the Aero Glass feature (Vista and 7).
legajius
Posts: 2
Joined: 8. Nov 2022, 19:36

Re: Discuss the VirtualBox 7.0.2 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: :roll: :roll:
Attachments
redhat-2022-11-08-12-10-18.log
Log de ejecución
(85.18 KiB) Downloaded 3 times
Post Reply