﻿ticket,summary,version,guest,created,modified,_changetime,_description,_reporter
21325,Enhancement: enable high refresh rates (frame rates?) in guests,VirtualBox-7.0.4,Windows,2022-12-06T02:47:35Z,2022-12-06T02:47:35Z,2022-12-06T02:47:35Z,"From what I understand, VirtualBox caps the refresh rate (or frame rate - not sure which terminology is correct) of the guest's display to 60Hz, and attempting to force any refresh rates higher than that is pointless.

This results in a very noticeable drop in smoothness when using the guest operating system on a host machine with a high refresh rate.

Simple tasks such as dragging or resizing GUI windows are noticeably laggier than on the host OS.

For example, I'm using a Windows host on a monitor which supports 200Hz. The host OS feels far, far more responsive and enjoyable to use than any of the guest machines.

I am not a VirtualBox developer so I don't know the technical details, but it would be great if it was possible to allow VirtualBox guests to output higher refresh/frame rates, up to and including the refresh rate set on the host OS.",Jenkins1
21146,"Buttons,transparent list background and startmenu are garbaged with 3d acceleration in win10 guest.",VirtualBox 7.0.0,Windows,2022-10-13T16:32:45Z,2022-10-27T21:16:02Z,2022-10-27T21:16:02Z,"When 3d acceleration is enabled{
Buttons,transparent list background and other UI elements in Win10 Settings are garbaged.
Start Menu sometimes turns white.
}",ebk
21129,Graphic bug when I enable aero effects on Windows 7,VirtualBox 7.0.0,Windows,2022-10-11T18:31:58Z,2022-10-11T18:35:27Z,2022-10-11T18:35:27Z,When I enable Aero effects on the latest version of VirtualBox the Aero graphics are poor after installing the VirtualBox Guest Additions,Sorecchione07
19222,Guest OS Windows 7 have 0x116 BSOD,VirtualBox 6.1.0,other,2020-01-14T10:00:04Z,2020-06-15T02:07:49Z,2020-06-15T02:07:49Z,"play online video with chrome. and then open applications which consume a lot of system resource. we will find 0x116 BSOD easily.

while reboot, OS will hang windows logo. re-start it. have no minidump .
i will upload kernel dump if needed.",ramboliu
18529,Heavy graphics activity in GUI locks VM,VirtualBox 6.0.4,Windows,2019-03-29T13:31:35Z,2019-07-17T14:45:53Z,2019-07-17T14:45:53Z,"I'm running Windows7 as a guest with MacOS as host. I've noticed that since some versions back, heavy graphics activity inside the guest causes extremely high CPU usage, bringing the guest to a crawl. The guest becomes unuseable slow and after some seconds the entire VM-Windows locks up and no longer redraws; interestingly this only affects the GUI, the VM itself continues running (I can see it's network-traffic).

""Heavy graphics activity"" in this context seems to be anything that causes lots of redraws. This includes simple GUI-animations, videos, or anything else which causes fast redraws inside the guest. 

Since the VM-logs show nothing of interest, I did acquire a CPU usage profile while a simple program inside the VM hammers it with window-redraws. It seems the redraws cause an event-storm in VirtualBox's Cocoa implementation: While the VM crawls and ultimately locks, the VirtualBox-process spends all of it's CPU-time inside the QEventLoop, specifically CGContextDrawImage.

My semi-educated guess is that the event-loop drowns in redraw requests which take much longer to process on the host than to generate in the guest.

I've attached the profile taken while VirtualBox is locked up.

Disabling 2D-Acceleration fixes the lockup.",ebfe
18409,Guru Meditation -2701 (VERR_VMM_RING0_ASSERTION) after experimental WDDM video driver installation.,VirtualBox 6.0.4,Windows,2019-02-05T07:41:44Z,2019-02-05T07:41:44Z,2019-02-05T07:41:44Z,"I have Windows 7 x86 guest on Windows 8 x64 host. Because of my issues (#18359) with SVGA adapter driver (not the current version is used even if current version of non-WDDM driver was previously installed) I tried the new approach. The new version of experimental (WDDM) driver was installed before the switch from the VGA to SVGA, after the non-experimental driver was already installed previously from the safe mode boot. As a result after the required restart of the guest OS I got the guru meditation. 

Side note: I installed the experimental driver in the normal mode, I didn’t boot the OS in the safe mode,because for the experimental drivers this isn’t a requirement. Other note: if I install the experimental driver (I say no to the standard one after activating the Direct3D support during the guest addition installation) in the safe mode, I have no issues with my desktop Java application, [https://forums.virtualbox.org/viewtopic.php?f=2&t=85458 TV Browser]. They appear as soon as I installed them in normal OS boot mode.",boxer01
18359,Wrong driver in the Windows 7 guest after the switch to the VBox SVGA adapter.,VirtualBox 6.0.2,Windows,2019-01-25T07:13:14Z,2019-02-05T07:25:49Z,2019-02-05T07:25:49Z,"I have a Windows 7 guest on the Windows 8 host. Because it’s new, after the test with an old VGA adapter I tested the new VBox SVGA adapter. After the first start the new device was automatically detected and installed. I have had to reboot the guest and after the reboot the new driver was active and I even had the Windows Aero activated.

Because of the problem I already posted in the forum (if I activate the experimental WDDM driver, my only Java desktop program, the TV Browser, has big skinning issues and becomes unusable) I usually install a regular driver with non-experimental Direct3D support only (Virtual Box Graphics Adapter). I have to boot my guest in safe mode for installation because of this. But time after time I test the experimental one. So after the reboot I found that the device name is “Virtual Box Graphics Adapter for Windows Vista and 7” now and beside the working Aero I also have the already mentioned issues in my Java program. More important: the driver version is 5.2.1 and it’s from the end of the year 2017. This was probably the last time I tested the experimental Aero supported drivers.

So I have to boot in safe mode once again, re-install the guest additions, but this time I answered “no” in the dialog about installing the regular Direct3D drivers and not the experimental WDDM ones. It looks for me, that by activating SVGA adapter the other device is simulated and under Windows 7 and Vista the Aero WDDM driver is used. And if one doesn’t install or re-install the additions explicitly, the wrong version of the drivers are used.

This was my experience from my test of original 6.0 release from December 2018. As I tested the 6.0.2 release, the new device was also detected and the driver was also installed. But this was probably once again not the newest one, so after the reboot I had the BSOD on the boot, more then once. Therefore, I have to repeat the additions installation and this way probably renew the Aero WDDM driver as well. After that the BSOD was gone, but I got the same situation with Aero and Java program as I already had before.",boxer01
18966,[VBoxSVGA with WDDM] Graphics corruption,VirtualBox 6.0.12,Linux,2019-09-26T06:51:59Z,2020-02-12T12:55:08Z,2020-02-12T12:55:08Z,"Corrupt display of various elements in GUI / dialog boxes when using VBoxSVGA and Aero in Windows 7 guest on Linux host.

No problem using VBoxVGA / WDDM.",Thomas S.
18907,Guest display will not size correctly,VirtualBox 6.0.12,Windows,2019-09-04T19:33:39Z,2019-09-04T19:33:39Z,2019-09-04T19:33:39Z,"Guest Additions icon does not appear on taskbar
Guest Additions Service is running normally
Seamless Mode and Auto-resize Guest Display are both greyed out

VirtualBox 6.0
Version 6.0.12 r133076 (Qt5.6.2)

Guest Additions Installed
Version 6.0.12.0

Host
Win10 Pro
Version 1809
OS Build 17763.615
System Type: 64 bit operating system, x64 based processor

Host Graphics
Intel UHD Graphics 620
Driver Version 23.20.16.4849

Guest
Win10 Pro 64
Version 1809
OS Build 17763.615
System Type: 64 bit operating system, x64 based processor

Guest Graphics
VirtualBox Graphics Adapter (WDDM)
Driver Version 6.0.12.0
",JTC
15817,Display with Windows 10 guest and OSX host is corrupted,VirtualBox 5.1.4,Windows,2016-08-18T08:01:01Z,2016-09-26T09:38:03Z,2016-09-26T09:38:03Z,"I have installed Windows 10 on my retina MacBook Pro and on my (non retina) iMac. Unfortunately with the latest release of VirtualBox the display on a Windows host is corrupted.

Specifically, when I start typing or I perform any mouse-related gui-event activity (i.e. press a button, select some text), then the square area that takes part of this activity is grayed out. Note that only the ""refresh"" part of the screen is damaged, not the whole screen.

If for example VB loose focus and gains it again (i.e. when the display is forced to redisplay/redraw) then the visual returns to normal.

As an example I attach a screenshot. I have clicked on the language button of the Windows login screen at the bottom, where a pop-up appears to select languages as well as on the text field to write the username. For these actions, all partially redrawn screen sections are completely grayed out, making the interface totally unusable.",terataki
17144,Direct3D11.1 crashes,VirtualBox 5.1.28,Windows,2017-10-07T10:38:48Z,2017-10-07T10:38:48Z,2017-10-07T10:38:48Z,"Dear Sirs!

I have a platform:
Host is a Windows 10 Creators Update.
Virutal PC has Windows 8.1 Up to Date.
DirectX applications are crashing in this configuration.
It is possible to create a Direct3D11.1 and its Context.
Releasing the device throws an hardware exception (bad pointer).
I can not use the DXDiag.exe, it crashes also.

[[Image(https://www.kubera.info/ms/2017-10-07.png)]]",kubera
16843,"WDDM driver does not validate custom video resolutions, causing graphics freeze on boot",VirtualBox 5.1.22,Windows,2017-06-19T01:11:11Z,2017-11-14T10:55:32Z,2017-11-14T10:55:32Z,"See investigation on [https://forums.virtualbox.org/viewtopic.php?f=7&t=83489 this forum post]

For some reason (possibly the tiling WM resize bug on Linux) the custom/transient display resolution can be set to a very small size (e.g. 400x191) and this small size is saved to the registry in Windows. Once the WDDM driver is installed, Windows will try to add this mode to the target modes in the VidPn framework. This fails and the boot sequence appears to freeze on the Windows splash screen, rendering the VM unusable.

A workaround is to install the Guest additions in safe mode, then edit the registry keys storing the custom resolution to be a larger size, e.g. 800x600. See the attached image.

Reproduced on both OSE and non-OSE versions of Virtualbox, 5.1.22 with corresponding extpack and Guest Additions ISO installed.

I have attached the boot log when the problem occurs. ",machfour
16574,Win7 Pro lockup using WDDM and Aeroglass Decorations,VirtualBox 5.1.18,Windows,2017-03-16T23:49:30Z,2017-06-19T09:50:09Z,2017-06-19T09:50:09Z,"All,

  I have openSuSE x86_64 host and Win7 32-bit guest. I experience regular lockups (guest and host) when using WDDM and Aero on Win7. The strange part is when the Win7 crashes or locks up, it will also lock the host desktop (kde3, i3 or fluxbox). I know that WDDM is experimental, but given then number of ""Hey, I'm using it and it works great"" howtos and tutorials, I would expect it to be a bit more reliable than I am seeing.

  I have the virtualbox.org rpms and extension packs installed, along with the guest additions, e.g.:

Oracle_VM_VirtualBox_Extension_Pack-5.1.18.vbox-extpack
VirtualBox-5.1-5.1.18_114002_openSUSE132-1.x86_64.rpm
VBoxGuestAdditions_5.1.18.iso

  I am running the guest on hp_8670W laptop, i7, quad core, hardware virtualization, 8G of ram. Guest is allocated 1 CPU, 2560M Ram, 256M Ram to display with 3D and 2D video acceleration checked.

  The lockups are semi random. Enabling Aero works fine. The desktop looks great, but anywhere from 30 seconds to 5 minutes later, all CPU/Network/etc. indicators in the status bar go red and the guest is locked. The mouse and keyboard are also trapped in the guest and the host desktop is locked (well, left without any input devices) as well.

  When I reinstall the guest additions, removing WDDM, and drop back to the basic Win7 Pro desktop, all is fine. I can run all day/night without issue. (64M Ram for display, 2D acceleration, no 3D.)

  I'm not sure where the bug is, but I would sure like to help get it fixed.",drankinatty
14731,"Fedora 22 Host, Windows 7 Guest: switch to seamless turns windows objects into a dark shadow",VirtualBox 5.0.6,Windows,2015-10-22T09:12:30Z,2016-03-25T23:33:36Z,2016-03-25T23:33:36Z,"Hello,

 in the following configuration:
- Lenovo T440p
- VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06)
- VirtualBox 5.0.8 (but it occurs with any 5.x - it was ok with 4.x)
- Host: Fedora 22, kernel 4.2.3-200.fc22.x86_64
- Guest: Windows 7 (you can reproduce with Oracle OBI7.3), 4GB ram, 256M video memory

I experience this behaviour:
- (optional) Set the host desktop background to blue and the guest to yellow to have good contrast
- Switch to full screen (successful)
- Switch to seamless mode (unsuccessful)
  - because the windows bar and the windows start menu appear in black
  - windows is unusable
  - you can send ctrl-alt-canc and switch off the guest

I have a video capture I can send.
Thanks.",Billamay77
14961,"Windows 10 Guest: ""vboxvideow8"" is stopped on login, screen resolution drops",VirtualBox 5.0.12,Windows,2015-12-22T08:27:47Z,2016-03-04T18:30:52Z,2016-03-04T18:30:52Z,"This is similar to #14957 but it still happens with VirtualBox 5.0.12

When starting the VM, the guest (Windows 10/1511) shows the start sreen in the expected screen resolution.[[BR]]
After clicking on screen to get the login fields (user name and password), the screen resolution drops to 1024*768 - after the login it can be increased somewhat, but the automatic adjustment of the guest does not work.[[BR]]
In the system log is an entry that ""VBoxVideoW8"" does not respond anymore and was deactivated by Windows.
",Feuerfloh
14134,"WDDM driver exposes only 384 MB VRAM, at least 512 MB needed (and 12 GB available!)",VirtualBox 4.3.28,other,2015-05-18T18:52:29Z,2015-06-14T19:54:28Z,2015-06-14T19:54:28Z,"How does the WDDM driver determine the amount of VRAM to expose?

Our CAD software (Autodesk Fusion 360) checks for at least 512 MB VRAM. The WDDM driver presents only 384 MB VRAM so the CAD software reverts to software rendering.

The physical hardware has 12 GB VRAM (NVIDIA Titan X). Is it possible to tweak the WDDM implementation to provide more VRAM?

Host is Ubuntu 4.0.0-040000-generic and guest is Windows 7 x64 SP1.

Thanks",Drew Robson
14231,"Unscaled HighDPI Output Graphics Corruption (OSX Host, Win10 Guest, VB5RC2)",,Windows,2015-06-30T08:07:24Z,2020-01-20T14:25:17Z,2020-01-20T14:25:17Z,"When ""Use Unscaled HighDPI Output"" is enabled on a Windows 10 Guest graphics corruption occurs. It jumps between rendering the native resolution (2560x1600) and scaling/cropping it to 1/4 that. Mouse movement affects the graphical glitches. Guest additions are installed, Paravirt interface is Hyper-V and 2d+3d acceleration are enabled.

Guest: Windows 10
Host: Mac OSX 10.10.4
Virtualbox: 5RC2 (occurred in RC1 too)

",Benjamin Roberts
