﻿ticket	summary	guest	version	created	modified	_changetime	_description	_reporter
17341	~30% keyboard strokes reach VM for vbox 5.2.2 only	Linux		2017-12-02T16:45:06Z	2017-12-02T16:45:06Z	2017-12-02T16:45:06Z	"Host: Debian GNU/Linux 9 amd64, Extension Pack 5.2.2 installed
VM: Debian GNU/Linux 8 amd64

When reverted vbox (and extension pack 5.2.0) to 5.2.0, keyboard strokes reach 100% back again.

(Can't select Version for the ticket, due to lact of 5.2.2 version string in popup menu)"	maestro
19043	XWayland breaks mouse behavior on Linux/Wayland Hosts	other	VirtualBox 6.0.14	2019-10-23T07:49:53Z	2022-05-12T17:28:40Z	2022-05-12T17:28:40Z	"On Arch Linux (5.3.7-arch1-1-ARCH), recent as of 2019/10/23 mouse behaviour is broken on a windows 10 host.
First mouse click in the guest (on an icon, however not at the background image) introduces this behaviour. Afterwards mouse clicks in guest and host system are not properly recognized anymore (on guest, GNOME seams to work correctly, however firefox, chromium, VirtualBox Manager and others don't). Keyboard function is correct.
As soon as the guest is powered off, mouse behaviour is normal in the host.

Changing mouse settings from PS/2 to tablet mode does not change the behaviour.

I could track the error down to the upgrade of usbutils-010 to usbutils-012. Downgrading usbutils to 010 solved the error

The log of the session is attached."	Cortex
19428	XP VM unexpected error	Windows	VirtualBox 5.2.34	2020-03-24T17:55:20Z	2020-03-24T17:55:20Z	2020-03-24T17:55:20Z	"Hello!
I just create a VM for Windows XP. Then i installed dotNET framework version 4.0 and the KB2836939 update (needed to install Daemontools lite).
You could see the attached log file.
Thanks for help!

NB: i'm french and have a very bad english..."	Hugo
18866	XNA Framework 4.0 unsupported by Windows XP Guest on Linux Host	Windows	VirtualBox 6.0.10	2019-08-25T12:52:43Z	2020-03-18T17:14:22Z	2020-03-18T17:14:22Z	"I was hoping that Vbox 6 would work with this. I knew that older versions of Vbox did not support it. I have been using VMware Player 12.1 for several years to achieve my requirement but that application is now too difficult for me to maintain through kernel changes and later versions of ""Player"" are no good to me for other reasons. So I went back to the latest VirtualBox and tried a couple of the graphics adapter settings and I have the Guest additions correctly installed etc.

The VM otherwise works fine and I can run ""dxdiag"" and see the spinning cube on the 3D tests so I know DirectX is working (well 8 & 9 are anyway - doesn't like 7). The ""repair"" option of the XNA installation program appears to work OK (installs DirectX 9.0c components) but the application wanting to use XNA will not start (it reports XNA is not fully supported).

The annoying thing is that the application I want to run is not a game and doesn't really need XNA for what it does but the program writers chose to use it anyway :-(

Can anyone help?"	Spiralgalaxy
15908	XBoxAutostart service starts and completes before NFS and iSCSI start	Linux	VirtualBox 5.1.4	2016-09-08T12:26:16Z	2018-06-14T04:19:55Z	2018-06-14T04:19:55Z	"I have a fresh install of Ubuntu 16.04 Server and VirtualBox 5.1. I have an Ubuntu guest created on an NFS mount with the storage attached to an iSCSI LUN on my NAS. Starting and stopping it manually works fine, but it does not start at boot.

Manually starting the guest works via any one of these commands:
* VBoxHeadless --startvm ""Ubuntu Server""
* sudo service vboxautostart-service restart
* vboxautostart --start --config /etc/vbox/autostart.cfg

The syslog shows the vboxautostart-service starting and completing before the NFS mounting and the iSCSI initiator daemon is ready.  With the help of the forum moderator Perryg, I added 'sleep 10' to the top of the /etc/default/virtualbox and the VM started and working as expected.

The vbox services with my install are started via S02vboxdrv and S03vboxautostart-service in the appropriate rc.d folders.

syslog
{{{
Sep  7 15:12:03 MyHost systemd[1]: Starting Authenticate and Authorize Users to Run Privileged Tasks...
Sep  7 15:12:03 MyHost vboxdrv.sh[2811]: vboxdrv.sh: Starting VirtualBox services.
...
Sep  7 15:12:03 MyHost vboxdrv.sh: Starting VirtualBox services.
...
Sep  7 15:12:03 MyHost kernel: [   14.354340] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel
Sep  7 15:12:03 MyHost kernel: [   14.359014] vboxdrv: Found 4 processor cores
...
Sep  7 15:12:03 MyHost kernel: [   14.378254] vboxdrv: TSC mode is Invariant, tentative frequency 1596300487 Hz
Sep  7 15:12:03 MyHost kernel: [   14.378258] vboxdrv: Successfully loaded version 5.1.4 (interface 0x00260000)
...
Sep  7 15:12:04 MyHost kernel: [   14.582075] VBoxNetFlt: Successfully started.
Sep  7 15:12:04 MyHost kernel: [   14.583189] VBoxNetAdp: Successfully started.
Sep  7 15:12:04 MyHost kernel: [   14.584579] VBoxPciLinuxInit
Sep  7 15:12:04 MyHost vboxdrv.sh: VirtualBox services started.
Sep  7 15:12:04 MyHost kernel: [   14.586318] vboxpci: IOMMU not found (not registered)
Sep  7 15:12:04 MyHost systemd[1]: Started VirtualBox Linux kernel module.
Sep  7 15:12:04 MyHost systemd[1]: Starting vboxautostart-service.service...
Sep  7 15:12:04 MyHost systemd[1]: Starting vboxballoonctrl-service.service...
Sep  7 15:12:04 MyHost vboxautostart-service.sh[3023]: vboxautostart-service.sh: Starting VirtualBox VMs configured for autostart.
Sep  7 15:12:04 MyHost vboxautostart-service.sh: Starting VirtualBox VMs configured for autostart.
Sep  7 15:12:04 MyHost systemd[1]: Starting vboxweb-service.service...
Sep  7 15:12:04 MyHost systemd[1]: Started vboxballoonctrl-service.service.
Sep  7 15:12:04 MyHost systemd[1]: Started vboxweb-service.service.
Sep  7 15:12:04 MyHost systemd[1]: Started vboxautostart-service.service.
...
Sep  7 15:12:10 MyHost systemd[1]: Starting iSCSI initiator daemon (iscsid)...
Sep  7 15:12:10 MyHost systemd[1]: Starting OpenBSD Secure Shell server...
Sep  7 15:12:10 MyHost systemd[1]: Started /etc/rc.local Compatibility.
Sep  7 15:12:10 MyHost iscsid: iSCSI logger with pid=3172 started!
Sep  7 15:12:10 MyHost systemd[1]: Started iSCSI initiator daemon (iscsid).
Sep  7 15:12:10 MyHost systemd[1]: Starting Login to default iSCSI targets...
Sep  7 15:12:10 MyHost iscsiadm[3180]: iscsiadm: No records found
Sep  7 15:12:10 MyHost systemd[1]: Started OpenBSD Secure Shell server.
Sep  7 15:12:10 MyHost systemd[1]: Started Login to default iSCSI targets.
Sep  7 15:12:10 MyHost systemd[1]: Reached target Remote File Systems (Pre).
Sep  7 15:12:10 MyHost systemd[1]: Mounting /mnt/nfs/myNas...
Sep  7 15:12:10 MyHost kernel: [   21.235486] FS-Cache: Loaded
Sep  7 15:12:10 MyHost kernel: [   21.247575] FS-Cache: Netfs 'nfs' registered for caching
Sep  7 15:12:10 MyHost kernel: [   21.258497] NFS: Registering the id_resolver key type
Sep  7 15:12:10 MyHost kernel: [   21.258505] Key type id_resolver registered
Sep  7 15:12:10 MyHost kernel: [   21.258506] Key type id_legacy registered
Sep  7 15:12:10 MyHost systemd[1]: Mounted /mnt/nfs/myNas.
}}}

Forum post: https://forums.virtualbox.org/viewtopic.php?f=7&t=79617"	Brian Duguid
14743	X11 guests: Invisible drag-and-drop window blocks mouse interaction	Linux	VirtualBox 5.1.6	2015-10-25T08:30:04Z	2021-08-13T05:36:14Z	2021-08-13T05:36:14Z	"I first noticed this in v5.0.6, but it just happened to me again in 5.0.8.  After several days of using a guest, all of a sudden mouse clicks no longer work.  Both left and right mouse clicks do nothing, as if the clicks are not making it to the guest.  Moving the mouse works.  Guest additions are installed.

When the clicks stop working, the mouse continues working correctly in the host and in other guests running on this host.

Rebooting the affected guest fixes the problem.

I looked through the log file, though I see nothing obvious.  In this case, the timestamps in the log indicate the guest was only running for 37 hours and 29 minutes.  I'd guess the problem started around 37 hours and 27 minutes.  I rebooted it a minute or so after it happened."	Stéphane Charette
16650	WXP VM crashs at startup after upgrade VB to 5.1.18 (raw mode)	Windows	VirtualBox 5.1.18	2017-04-12T12:37:17Z	2017-04-12T13:15:43Z	2017-04-12T13:15:43Z	"I have a WXP VM. It ocasionally broke.
I have upgrade VB to 5.1.18 version. I have upgrade also the extension pack.

VM start up crashes with error 

Not in text mode!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
emR3Debug: rc=VERR_REM_VIRTUAL_CPU_ERROR

My OS is Ubuntu 16.04"	EduardoNicolano
18988	Wrong time synchronization	Linux	VirtualBox 6.0.8	2019-10-07T18:06:47Z	2019-10-08T21:37:47Z	2019-10-08T21:37:47Z	"Hello,
I noticed that time is not running right when I'm offline (when I'm online, everything works).
For example: When I start virtual machine at 7:30 and I look to time after 10 minutes, on my host is 7:40, but on guest is 7:38. After next 10 minutes on host is 7:50 and on guest is 7:47...
Sync time settings on VirtualBox are default (I do no changes).

Thank you"	max-m
8555	Wrong resolution in full screen mode.	Windows	VirtualBox 4.0.4	2011-03-13T11:32:23Z	2011-07-12T09:21:04Z	2011-07-12T09:21:04Z	"I use external monitor connected to my notebook. This monitor has bigger resolution than notebook's screen. When I start virtualbox on this monitor and switch to full screen mode guest os takes height of notebook's screen and width of extarnal monitor (see screenshot). Turn off/turn on option ""Auto-resize Guiest Display"" in fullscreen mode nothing changes. To get correct resolution I shoud come back from fullscreen mode, turn off ""Auto-resize Guiest Display"", switch to fullscreen mode and turn on ""Auto-resize Guiest Display"" (see screenshot). Seamless mode also takes wrong display size (see screenshot). In normal mode I can't resize virtualbox window more then notebook's resolution. Maximize button normal in mode works fine."	Oksenchuk Dmitry
20928	Wrong IPC socket being deleted when VirtualBox is run via su on Linux, leading to possible disk corruption in VMs	all	VirtualBox 6.1.34	2022-05-05T13:10:54Z	2022-05-05T13:10:54Z	2022-05-05T13:10:54Z	"This is related to ticket #17029 which has the same symptoms, but I'm not sure if it is caused by the same issue.

!VirtualBox, via src/VBox/Installer/linux/VBox.sh, checks for the presence of a VBoxSVC process owned by the current user and will delete a user-specific directory in /tmp if no process is found. But the process check uses the ""whoami"" command to get the current username and the deletion uses the environment variables $LOGNAME or $USER. Certain implementations of su, such as the one from util-linux, does not update $LOGNAME or $USER when switching to the root user, but whoami will return ""root"". Thus, if a user named ""vmuser"" runs !VirtualBox through su, it will search for processes owned by root but delete the socket belonging to vmuser.

The removal of these files will then lead to bad side effects for VMs that were previously running, as future calls to !VirtualBox will create a new IPC socket in /tmp. When using this new socket, all VMs will be shown as being powered off when they might still be running. It is also possible to start another instance of a running VM, which leads to disk corruption when both instances attempt to write to the same disk image.

Not all implementations of su seem to behave in this way, and using sudo or ""sudo su"" can sometimes cause $LOGNAME and $USER to be changed to ""root"", mitigating the issue. Using su by itself seems to have the highest chance of triggering this bug.

Replication steps:
1. Start any VM using ""{{{vboxmanage startvm <VM_NAME> --type headless}}}"" (take a snapshot beforehand in case of disk corruption).
2. Check that two files called ""ipcd"" and ""lock"" are present using ""{{{ls -l /tmp/.vbox-$USER-ipc}}}"".
3. Try to start the same VM again, this should fail with a message that the VM is already locked by a session.
4. Switch to the root account using ""{{{su}}}"" and run ""{{{vboxmanage list vms}}}"".
5. Exit the root shell and run ""{{{ls -l /tmp/.vbox-$USER-ipc}}}"" again to see that the files from step !#2 are now missing.
6. Try to start the VM with the same command as in step !#1, this should now succeed.
7. Run ""{{{ps aux | grep -i vboxheadless}}}"" and see that there are now two processes started for the same VM.

The expected behavior would be that the files in /tmp/.vbox-$USER-ipc/ remain untouched and that step !#6 should refuse to start another VM instance.

While this issue only seems to occur when su does not update $LOGNAME and $USER, I'd argue that either whoami or $LOGNAME/$USER should be used instead of having a mix of both. While running !VirtualBox as root is not recommended, it would be nice if accidentally running ""{{{vboxmanage list vms}}}"" as root did not immediately break existing IPC sessions. I have attached a small patch to replace the use of whoami with $LOGNAME/$USER, and hereby make this modification available under the MIT license.

The !VirtualBox log files are unlikely to contain any relevant information about this bug since it occurs in the initial shell wrapper script, but I can attach them if needed. Here are the results of running the replication steps on an unpatched installation (tested on Ubuntu 22.04 using !VirtualBox 6.1.34):

{{{
$ vboxmanage startvm test_VM --type headless
Waiting for VM ""test_VM"" to power on...
VM ""test_VM"" has been successfully started.
$ ls -l /tmp/.vbox-$USER-ipc
total 4
srwx------ 1 vmuser vmuser 0 May  5 11:21 ipcd
-rw------- 1 vmuser vmuser 6 May  5 11:21 lock
$ vboxmanage startvm test_VM --type headless
VBoxManage: error: The machine 'test_VM' is already locked by a session (or being locked or unlocked)
VBoxManage: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MachineWrap, interface IMachine, callee nsISupports
VBoxManage: error: Context: ""LaunchVMProcess(a->session, sessionType.raw(), ComSafeArrayAsInParam(aBstrEnv), progress.asOutParam())"" at line 726 of file VBoxManageMisc.cpp
$ su
Password: 
# vboxmanage list vms
""<inaccessible>"" {7abbc342-2595-4b5d-b13b-4f57b7d4d367}
""<inaccessible>"" {26b6e251-e3c9-4004-a23e-30e5dd55f652}
""<inaccessible>"" {ed047e7d-83db-46b6-8d09-cd99f05f7362}
""<inaccessible>"" {2256db63-2e33-40fd-9182-7631a68a9e64}
""<inaccessible>"" {bf2390e8-3978-4363-9792-e370986ce5fc}
# exit
$ ls -l /tmp/.vbox-$USER-ipc
/usr/bin/ls: cannot access '/tmp/.vbox-vmuser-ipc': No such file or directory
$ vboxmanage startvm test_VM --type headless
Waiting for VM ""test_VM"" to power on...
VM ""test_VM"" has been successfully started.
$ ps aux | grep -i vboxheadless
vmuser     46799  2.2  0.6 1757468 431480 ?      Sl   11:38   0:01 /opt/VirtualBox/VBoxHeadless --comment test_VM --startvm a179e065-a0b4-4fc2-a55a-d59b599aad1e --vrde config
vmuser     47353 59.8  0.2 1482004 157324 ?      Sl   11:39   0:03 /opt/VirtualBox/VBoxHeadless --comment test_VM --startvm a179e065-a0b4-4fc2-a55a-d59b599aad1e --vrde config
}}}
"	Busan15
18806	Wrong GUI scaling on very large screen resolution ultrawidescreen triple monitors	all	VirtualBox 6.0.10	2019-08-02T23:41:59Z	2019-08-02T23:41:59Z	2019-08-02T23:41:59Z	"Hello,

I have a 3x1280x1024 screen.
I upgraded from 5.2.30 to 6.0.10 and now some part of the GUI are too large.

Prior to the upgrade, I could resize the main virtualbox window to 1280x1024 so that it fits one of my triple-monitors.
With 6.0.10, the main window can't be reduced horizontally to less than approximately 1600x1024. I think this is because the GUI elements are already collapsed to the non-overlapping minimum but they are still too large.

The guest window is too big too.
I used to set the guest screen to 1152x864 and I had space left around it.
Now with 6.0.10, the UI elements around the window are so big that it the same 1152x864 guest window is too tall for the screen and it even has to add (large) scrollbars to it.

The issue is prominent in the menus.
Also, the larger the monitor resolution, the more pixelated the guest preview.

If I set my screen resolution to a lower single monitor resolution (1280x1024) the issue is not present.
The issue is proportional to the wideness of the screen.
See the attached screenshots for comparison between different resolutions.

Host is Debian 8 Jessie 64bit.
Guest is irrelevant.

Regards."	www.olivierdierick.be
19835	Wrong guest screen resolution with host using 1920x1080	Windows	VirtualBox 6.1.10	2020-08-27T07:22:21Z	2020-09-07T10:28:26Z	2020-09-07T10:28:26Z	"Hello. I'm using VirtualBox 6.1.12 on a ArchLinux host (Kernel: x86_64 Linux 5.8.3-arch1-1, Resolution: 1920x1080), running an Windows 7 guest with the guest additions installed from the ISO, also in version 6.1.12. 

But in guest OS, the screen resolution  unable to identify the host's screen resolution 1920x1080.

Similar issue as https://www.virtualbox.org/ticket/19499"	zeno
17131	Wrong core count on THREADRIPPER system	all	VirtualBox 5.2.0 RC 1	2017-10-02T21:45:05Z	2019-05-26T19:48:58Z	2019-05-26T19:48:58Z	"On Fedora F26 host system Virtualbox only see 6 physical and 12 virtual cpu'es  on a system with Threadripper 1920x (12 physical and 24 virtual cpu's)

testet on 5.1.28 and 5.2.0 rc1 118201"	Knud
17094	Won't install on Ubuntu 16.04	all	VirtualBox 5.1.28	2017-09-18T10:51:24Z	2017-09-18T14:22:06Z	2017-09-18T14:22:06Z	"I downloaded the package for Ubuntu 16.04 from http://download.virtualbox.org/virtualbox/5.1.28/virtualbox-5.1_5.1.28-117968~Ubuntu~xenial_amd64.deb

By double-clicking on it it opens with Ubuntu Software Whatever, an ""install"" button shows up. That doesn't work, https://forums.virtualbox.org/viewtopic.php?f=1&t=84623&sid=255ddb223689adba4a433f51a9e7500d&p=401997#p401997it just shows a progress bar for a fraction of a second and then the button appears again, it does nothing, gives no error message. But that probably is a bug in Ubuntu.

So in a terminal I did:
{{{
$ sudo apt install ./virtualbox-5.1_5.1.28-117968-Ubuntu-xenial_amd64.deb 
}}}
And this is the output:

{{{
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Note, selecting 'virtualbox-5.1' instead of './virtualbox-5.1_5.1.28-117968-Ubuntu-xenial_amd64.deb'
The following packages were automatically installed and are no longer required:
  fonts-horai-umefont fonts-unfonts-core libgif7:i386
  libp11-kit-gnome-keyring:i386 linux-headers-4.4.0-79
  linux-headers-4.4.0-79-generic linux-headers-4.4.0-83
  linux-headers-4.4.0-83-generic linux-headers-4.4.0-89
  linux-headers-4.4.0-89-generic linux-headers-4.4.0-91
  linux-headers-4.4.0-91-generic linux-image-4.4.0-79-generic
  linux-image-4.4.0-83-generic linux-image-4.4.0-89-generic
  linux-image-4.4.0-91-generic linux-image-extra-4.4.0-79-generic
  linux-image-extra-4.4.0-83-generic linux-image-extra-4.4.0-89-generic
  linux-image-extra-4.4.0-91-generic linux-signed-image-4.4.0-79-generic
  linux-signed-image-4.4.0-83-generic linux-signed-image-4.4.0-89-generic
  linux-signed-image-4.4.0-91-generic ocl-icd-libopencl1:i386 odbcinst
  odbcinst1debian2 p11-kit-modules:i386 p7zip unixodbc wine-gecko2.21
  wine-gecko2.21:i386 wine-mono0.0.8 winetricks
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  libsdl-ttf2.0-0
The following NEW packages will be installed:
  libsdl-ttf2.0-0 virtualbox-5.1
0 upgraded, 2 newly installed, 0 to remove and 10 not upgraded.
Need to get 0 B/66,0 MB of archives.
After this operation, 163 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 /home/teo/Downloads/virtualbox-5.1_5.1.28-117968-Ubuntu-xenial_amd64.deb virtualbox-5.1 amd64 5.1.28-117968~Ubuntu~xenial [65,9 MB]
Preconfiguring packages ...
Selecting previously unselected package libsdl-ttf2.0-0:amd64.
(Reading database ... 454844 files and directories currently installed.)
Preparing to unpack .../libsdl-ttf2.0-0_2.0.11-3_amd64.deb ...
Unpacking libsdl-ttf2.0-0:amd64 (2.0.11-3) ...
Selecting previously unselected package virtualbox-5.1.
Preparing to unpack .../virtualbox-5.1_5.1.28-117968-Ubuntu-xenial_amd64.deb ...
Unpacking virtualbox-5.1 (5.1.28-117968~Ubuntu~xenial) ...
Processing triggers for systemd (229-4ubuntu19) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
Processing triggers for shared-mime-info (1.5-2ubuntu0.1) ...
Unknown media type in type 'all/all'
Unknown media type in type 'all/allfiles'
Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ...
Processing triggers for bamfdaemon (0.5.3~bzr0+16.04.20160824-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for mime-support (3.59ubuntu1) ...
Processing triggers for gnome-menus (3.13.3-6ubuntu3.1) ...
Setting up libsdl-ttf2.0-0:amd64 (2.0.11-3) ...
Setting up virtualbox-5.1 (5.1.28-117968~Ubuntu~xenial) ...
addgroup: The group `vboxusers' already exists as a system group. Exiting.
depmod: ERROR: could not open directory /lib/modules/3.19.0-30-generic: No such file or directory
depmod: FATAL: could not search modules: No such file or directory
depmod: ERROR: could not open directory /lib/modules/3.8.0-19-generic: No such file or directory
depmod: FATAL: could not search modules: No such file or directory
depmod: ERROR: could not open directory /lib/modules/4.2.0-30-generic: No such file or directory
depmod: FATAL: could not search modules: No such file or directory
Processing triggers for libc-bin (2.23-0ubuntu9) ...
}}}"	teo8976
16186	With Windows 10 guest and linux host, selecting VBox ‘Shared Clipboard – Bidirectional’ disables internal guest copy/paste functionality of all but text.	Windows	VirtualBox 5.1.8	2016-11-14T23:03:34Z	2016-11-15T00:13:06Z	2016-11-15T00:13:06Z	"With VBox ‘Shared Clipboard’ set to bidirectional it is not possible to copy Formulas within an Excel spread sheet. It appears to affect the Windows ‘copy’ functionality, only allowing text values onto the clipboard.

Host Gentoo Linux 64 bin KDE5 virtualbox 5.1.8 ; Guest Windows10 64 bit version 1607
Also tested against Windows 10 32 bit version 1607 and Windows 8.1 32 bit. Both are affected.

See attached document for steps to demonstrate and reproduce this issue."	normanb46
17364	With python3 find_machine always throws TypeError	other	VirtualBox 5.1.30	2017-12-11T10:05:22Z	2018-03-27T18:54:08Z	2018-03-27T18:54:08Z	"I've managed to compile VBox on openSUSE Tumbleweed with support for Python 3.6 (it required some minor patching. everything is here: https://build.opensuse.org/package/show/home:etamPL:virtualbox_python36/virtualbox)

Now this happens:
{{{
from virtualbox import VirtualBox
v = VirtualBox()
>>> v.find_machine(""testvm"")
Traceback (most recent call last):
  File ""/home/etam/.virtualenvs/vbox-test/lib/python3.6/site-packages/virtualbox/library_base.py"", line 195, in _call_method
    ret = method(*in_params)
  File ""<XPCOMObject method 'findMachine'>"", line 3, in findMachine
TypeError: internal error in PyXPCOM, parameter must be a bytes object

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File ""<stdin>"", line 1, in <module>
  File ""/home/etam/.virtualenvs/vbox-test/lib/python3.6/site-packages/virtualbox/library.py"", line 7280, in find_machine
    in_p=[name_or_id])
  File ""/home/etam/.virtualenvs/vbox-test/lib/python3.6/site-packages/virtualbox/library_base.py"", line 186, in _call
    return self._call_method(method, in_p=in_p)
  File ""/home/etam/.virtualenvs/vbox-test/lib/python3.6/site-packages/virtualbox/library_base.py"", line 212, in _call_method
    errobj.msg = getattr(exc, 'msg', getattr(exc, 'message'))
AttributeError: 'TypeError' object has no attribute 'message'
>>>
>>> v.find_machine(b""testvm"")
Traceback (most recent call last):
  File ""/home/etam/.virtualenvs/vbox-test/lib/python3.6/site-packages/virtualbox/library_base.py"", line 195, in _call_method
    ret = method(*in_params)
  File ""<XPCOMObject method 'findMachine'>"", line 3, in findMachine
TypeError: This parameter must be a unicode object

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File ""<stdin>"", line 1, in <module>
  File ""/home/etam/.virtualenvs/vbox-test/lib/python3.6/site-packages/virtualbox/library.py"", line 7280, in find_machine
    in_p=[name_or_id])
  File ""/home/etam/.virtualenvs/vbox-test/lib/python3.6/site-packages/virtualbox/library_base.py"", line 186, in _call
    return self._call_method(method, in_p=in_p)
  File ""/home/etam/.virtualenvs/vbox-test/lib/python3.6/site-packages/virtualbox/library_base.py"", line 212, in _call_method
    errobj.msg = getattr(exc, 'msg', getattr(exc, 'message'))
AttributeError: 'TypeError' object has no attribute 'message'
}}}

This is caused by PyObject_AsNSString function in src/libs/xpcom18a4/python/src/VariantUtils.cpp which first checks if object is a unicode string and then passes it to PyUnicode_AsPRUnichar, which checks if it's bytes object."	etam1024
16341	With 3D Enabled OpenGL apps fail to work in Stretch Client on Jessie Host	Linux	VirtualBox 5.1.12	2016-12-30T20:26:43Z	2017-01-20T21:03:13Z	2017-01-20T21:03:13Z	"Using the following as OpenGL Test Applications:  KDE Plasma (Stretch), glxgears(Stretch), QT5 Development Tools (Stretch & Download), blender (Stretch).

Toggled Setting: Settings/Display/3D Acceleration (3D_A) in VirtualBox Manager.
* When 3D_A “IS Enabled” VM Guest OpenGL test applications, “Do not work!”.
* When 3D_A “IS Not Enabled” VM Guest OpenGL test applications, “Do work!”.

Note: It would be nice to track this down before Stretch transitions to stable and have it included!

Virtualbox Version:
Jessie sources.list:
deb http://download.virtualbox.org/virtualbox/debian jessie contrib
Virtual Box Version 5.1.12 r112440 (Qt5.3.2)

Virtualbox Guest Additions Version:
VBoxGuestAdditions_5.1.12.iso

NVIDIA Driver Used:
NVIDIA-Linux-x86_64-375.26.run
Both: Titan Black (Kepler) & GTX-1060 (Pascal) showed the same results.

Host Kernel (uname -r):
3.16.0-4-amd64

Guest Kernel (uname -r):
4.8.0-2-amd64

Much work correctly:  In all the test, Jessie (host) neither hung nor needed to be rebooted;   One VM did not effect another;  VM Manager neither hung nor needed to be rebooted do to a failure; sharing worked (within VM KDE Plasma did not mount share correctly when 3D_A was not enalbed.);  copy/paste worked; issues on one VM did not impact other VMs; the base guest Linux kernel did not show instability even when there were failures ongoing; with 3D unchecked OpenGl applications seemed to work.  More testing is needed.

See attachment for more details or the links below where it is also posted to support the stretch alpha8 installation testing process.

Tests were conducted using Stretch Alpha8 Install process.

[https://lists.debian.org/debian-boot/2016/12/msg00275.html Related Post]
See Attachment: hkb_stretch_20161227_1000.pdf
"	Hal B.
17197	Windows XP SP3 blue screen (VBoxGuest.sys)	Windows	VirtualBox 5.2.0	2017-10-21T18:18:35Z	2017-10-27T20:26:20Z	2017-10-27T20:26:20Z	"After updating from VirtualBox 5.1 to 5.2, I updated the Guest Additions in safe mode, rebooted and logged in my Virtual Machine (Windows XP SP3 Professional with the Microsoft Extended Support). The login was fine, but I noticed that some programs were misbehaving like Team Viewer and everything was kinda laggy (not smooth). I turned the virtual machine off and on again, logged, same. I did some tests with Advanced Chromium (updated Chromium builds for XP) and Firefox 52 ERS and both were kinda slow. I then tried to open Aspera Connect and it worked fine. Avast was working fine. Disabling it and doing a fresh install of it didn't solve the issue, though. I then left my computer open during the night to download files from a TV Studio using Aspera (these master files were fine and virus free, for the records). Then I woke up, I went to work and I found out that my Virtual Machine had a blue screen caused by VBoxGuest.sys.

Host: Fedora Workstation 26, updated constantly.
CPU: Intel i7 6700HQ 4c/8th
RAM: 16 GB DDR4 (8x2)
GPU: NVIDIA 950M 4GB GDDR5
Hard Drive Host: Toshiba 1TB Sata III

Guest: Windows XP Professional SP3 x86 + Microsoft Premium Support + PAE
CPU: 8 cores (I know VBox works with cores and not with thread, in fact I shouldn't assign threads to the virtual machine, 'cause timing would be terrible, but I do it anyway 'cause benchmarks shows that it slightly increase performances. Anyway, limiting it to 4core didn't solve the issue).
RAM: 6 GB (read correctly as 6)
Hard Drive: Seagate SSHD 1TB Sata III (XP is installed on a Physical SSHD and I use it with the raw disk function. I also have no intention of migrating it into a virtual machine file. It's an install I've been working on flawlessly as programmer since 2001, which has been cloned several times to several different hard drives. It's like my baby).

Screenshot and VBox log file in attachment.
Thank you in advance."	FranceBB
18034	Windows XP Guest Random Aborting	Windows	VirtualBox 5.2.18	2018-10-06T16:06:28Z	2018-10-08T15:06:28Z	2018-10-08T15:06:28Z	"Hello,

I am running Ubuntu Linux 18.04 LTS with all the latest patches installed.

Linux xxxxxxx 4.15.0-34-generic #37-Ubuntu SMP Wed Aug 15 16:00:05 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

I installed Virtualbox/Extension Pack/Guest Additions from virtualbox.org; version 5.2.18 r124319 (Qt5 9.5)

When running a Windows XP guest, the machine randomly aborts. I have attached the Virtualbox log file. 

The aborting generally happens when running Lotus 123, which is a spreadsheet program. I have tried the standard ideas of turning off 3D/2D acceleration, but the crashes continue to happen. 

Any/All help is appreciated.

Thanks."	SloanUser
14075	"Windows VM crashes Debian host, NMI for unknown reason points to ""vboxdrv"""	Windows	VirtualBox 4.3.26	2015-04-24T10:28:03Z	2016-07-15T13:38:24Z	2016-07-15T13:38:24Z	"The first time the crash occurred was about a month ago, the host was running Debian 6 and latest (at that time) !VirtualBox. Since then, host was wiped and Debian 7 was installed with latest !VirtualBox 4.3.26. A crash occurred again recently and so I started investigating.

Crashes seem random. Windows VM was the only VM on the host at the time of the second crash, it was just applying Windows updates. Reverting to a previous copy of VM and reapplying the same Windows updates again did not cause the crash again. Nothing appears in the logs at the time of a crash (both Linux and !VirtualBox logs).

The suspect lines extracted from `dmesg`:
{{{
[50414.144741] warning: `VBoxHeadless' uses 32-bit capabilities (legacy support in use)
[50415.090400] EXT4-fs (md0): Unaligned AIO/DIO on inode 4194333 by AioMgr0-N; performance will be poor.
...
[63477.985050] Uhhuh. NMI received for unknown reason 31 on CPU 4.
[63477.985073] Do you have a strange power saving mode enabled?
[63477.985094] Dazed and confused, but trying to continue
[68728.724996] Uhhuh. NMI received for unknown reason 21 on CPU 7.
[68728.725021] Do you have a strange power saving mode enabled?
}}}

To trace NMI for unknown reason, I have enabled crash dump using ""kdump"", set ""kernel.unknown_nmi_panic=1"" and ""kernel.panic_on_unrecovered_nmi=1"" in ""/etc/sysctl.conf"", and let VM run with HeavyLoad from JAM Software (CPU, memory, file writes and disk access). This crash is now reproducible but it could take anywhere from 1 hour to 1 day of running a VM for a crash to occur.

Call trace from crash dump points to ""vboxdrv"":
{{{
[76034.059602] Uhhuh. NMI received for unknown reason 31 on CPU 3.
[76034.059686] Do you have a strange power saving mode enabled?
[76034.059766] Kernel panic - not syncing: NMI: Not continuing
[76034.059846] Pid: 19036, comm: EMT-4 Tainted: G           O 3.2.0-4-amd64 #1 Debian 3.2.65-1+deb7u2
[76034.059937] Call Trace:
[76034.060006]  <NMI>  [<ffffffff8134a53c>] ? panic+0x95/0x1a2
[76034.060157]  [<ffffffff81352056>] ? do_nmi+0x151/0x258
[76034.060235]  [<ffffffff813517a0>] ? nmi+0x20/0x30
[76034.060312]  <<EOE>>  [<ffffffffa03f97c6>] ? rtR0MemAllocEx+0x17e/0x1de [vboxdrv]
[76034.060470]  [<ffffffffa03f05a3>] ? supdrvIOCtlFast+0x75/0x79 [vboxdrv]
[76034.060555]  [<ffffffffa03ed2a9>] ? VBoxDrvLinuxIOCtl_4_3_26+0x43/0x1eb [vboxdrv]
[76034.060645]  [<ffffffff811087dd>] ? do_vfs_ioctl+0x459/0x49a
[76034.060728]  [<ffffffff81039aa2>] ? finish_task_switch+0x4e/0xb9
[76034.060809]  [<ffffffff8134fb09>] ? __schedule+0x5f9/0x610
[76034.060892]  [<ffffffff81108869>] ? sys_ioctl+0x4b/0x72
[76034.060970]  [<ffffffff81355f92>] ? system_call_fastpath+0x16/0x1b
}}}

Tested RAM with MemTest86 for days, no problems found. High CPU usage from Interrupts is observed inside the VM as described in Ticket #10611, it might be relevant.

Summary of host specs:
* BIOS: VT-x and VT-d enabled, HT disabled
* Motherboard: Intel Server Board S5520HCT
* CPU: 2 x Intel Xeon E5620, 2.4GHz, 8 cores in total
* RAM: 12 x 4GB (DDR3 1333MHz ECC Unbuffered)
* HD: 2 x 600GB WD VelociRaptor 10Krpm

VM configuration:
* OS: Windows 7 SP1 (with latest updates)
* vCPU: 4-7 (it seems the higher the number the higher the chances of a crash occurring sooner)
* vRAM: 8GB

Attached are various logs, crash analyses and hardware info."	Denis Kozlov
17332	Windows taskbar is not visible	Windows	VirtualBox 5.2.0	2017-11-30T06:16:22Z	2017-12-01T00:52:07Z	2017-12-01T00:52:07Z	I've installed Ubuntu 17.10 and VirtualBox 5.2.2 r119230 (Qt5.9.1) when I star run Windows 7 Ultimate as guest, the windows taskbar is not visible in seamless mode	pigus92
20309	Windows guests abort upon shutdown on linux hosts with segfault indicated in /var/log	Windows	VirtualBox 6.1.18	2021-04-20T22:56:06Z	2021-07-28T22:32:06Z	2021-07-28T22:32:06Z	"I have been seeing windows guests crash during shutdown then listing as ""aborted"" in the main Virtualbox control GUI.

Surveying /var/log/messages indicates segfaults in the shclipboard process.

audit[7775]: ANOM_ABEND auid=xxxx uid=xxxx gid=xxx ses=3 subj=kernel pid=xxxx comm=""ShClipboard"" exe=""/usr/lib/virtualbox/VirtualBoxVM"" sig=11 res=1
Apr 10 09:22:13 xwing kernel: ShClipboard[7839]: segfault at 20 ip 00007f5d5d68622a sp 00007f5d900bbd40 error 4 in libXt.so.6.0.0[7f5d5d668000+41000]

Similar segfaults have been observed by others in the forums. As noted by some, the Virtualbox logs do not indicate a problem at the time of the crash.
Shared Clipboard is DISABLED for the guests.  I do not make use of this feature and so turn it off for my guest machines.

Host: Fedora 32 Linux running kernel 5.11
Virtualbox installation via virtualbox.org site: Fedora repo and manually downloaded extension pack.

I've noticed the problem since upgrading from Virtualbox 5.2 to Virtualbox 6.x as part of an upgrade from Fedora 30 to Fedora 32 several months ago.

The problem has persisted through a recent upgrade to Virtualbox 6.20.

If I do not log into the Guest after booting the guest, but shut it down from the Guest login screen, the guest shuts down without crashing.  I'm assuming that this is related to engaging some part of the Guest additions services after logging into the guest.  Again, Shared Clipboard has been turned off in the guest's options within the Virtualbox control GUI.

As I understand it, the shared clipboard will run services on both the host and the guest to manage the data exchange.  It appears that something may trigger a poling of the clipboard from the host side during guest shutdown, independent of whether the service is running on the guest.


"	HDCompute
19066	Windows guest video driver causes ms office equation render overlapped letters	Windows	VirtualBox 6.0.12	2019-11-06T12:44:16Z	2019-11-07T06:30:05Z	2019-11-07T06:30:05Z	"I'm using vbox on Linux x86_64. Guest is Windows 7/XP 32bit.

Vbox guest additions' video driver causes Ms office Visio 2010/2007 render equation wrong (non-English version, using equation editor 3.0). While Word has no problem.

Disabling the video driver in Windows hardward management will avoid that issue.

In the log file, I started VM with video driver disabled. Since line 1473 I enabled driver."	BJ6hello
13047	Windows guest on linux host is very slow with guest additions	Windows	VirtualBox 4.3.12	2014-05-19T07:57:32Z	2014-11-25T17:20:26Z	2014-11-25T17:20:26Z	"I have installed VBox on an Archlinux x64 host (Manjaro).
The guest is Win 8.1 Update 1 x64. I use a Core2Duo 9500M having hardware virtualisation enabled.
With guest additions installed the guest becomes very slow oftentimes even unresponsive (often taking several seconds to draw a Window.) In the guest's task manager the CPU load is already 20-50% usage when system is shold be idle. It shows the system interrups process with 10-20% usage.
And just having Skype running without conversation for example, causes overall CPU usage of nearly 100%.

Without installing the guest additions the guest seems to be much faster and system interrups cause < 3% usage."	albion
20888	Windows guest hangs completely (possible cause: Split lock detected)	Windows	VirtualBox 6.1.32	2022-03-28T14:19:10Z	2022-03-28T14:19:10Z	2022-03-28T14:19:10Z	"I have a situation where a Windows 10 Professional guest reliably hangs when executing a particular program, the Office 365 installer. The host is VirtualBox 6.1.32_Debian r149290 on, well, Debian 11.3.

The kernel log shows the following:

{{{
[ 3898.986978] SUPR0GipMap: fGetGipCpu=0x1b
[ 3899.552857] vboxdrv: 00000000aeb9f67b VMMR0.r0
[ 3899.656486] vboxdrv: 00000000afb38562 VBoxDDR0.r0
[ 3899.740741] VMMR0InitVM: eflags=246 fKernelFeatures=0x0 (SUPKERNELFEATURES_SMAP=0)
[ 3916.929613] x86/split lock detection: #AC: ShFolders/7532 took a split_lock trap at address: 0x7efcbf042eaf
[ 6651.842406] tun: Universal TUN/TAP device driver, 1.6
[ 6815.856879] vboxdrv: 00000000bb3fe004 VMMR0.r0
[ 6815.948801] vboxdrv: 000000007f68d4c7 VBoxDDR0.r0
[ 6815.989381] VMMR0InitVM: eflags=246 fKernelFeatures=0x0 (SUPKERNELFEATURES_SMAP=0)
[ 6938.723256] Split lock detected
               : 0000 [#1] SMP NOPTI
[ 6938.723260] CPU: 4 PID: 9098 Comm: EMT Tainted: G           OE     5.10.0-13-amd64 #1 Debian 5.10.106-1
[ 6938.723261] Hardware name: Dell Inc. XPS 13 9310/0DMPXV, BIOS 3.4.0 12/14/2021
[ 6938.723266] RIP: 0010:0xffffc2e90460e770
[ 6938.723268] Code: 89 02 c3 cc cc cc cc 53 49 89 ca 49 89 d3 41 8b 1b 41 8b 4b 04 9c 41 8b 02 83 24 24 bf 83 e0 40 48 09 04 24 9d 8b 06 8b 56 04 <f0> 0f c7 0f 89 06 89 56 04 9c 41 5b 41 8b 02 83 e0 bf 41 83 e3 40
[ 6938.723269] RSP: 0018:ffffc2e903b879b8 EFLAGS: 00010206
[ 6938.723270] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
[ 6938.723271] RDX: 0000000000000000 RSI: ffffc2e903b879d8 RDI: ffff9ff67a3fccfc
[ 6938.723271] RBP: ffffc2e904238000 R08: ffffc2e903b878c8 R09: ffffc2e903b87980
[ 6938.723272] R10: ffffc2e903b879cc R11: ffffc2e903b879e8 R12: ffffc2e904238000
[ 6938.723273] R13: ffffc2e903b87ba8 R14: 0000000000000000 R15: ffffc2e904227000
[ 6938.723274] FS:  00007fc0682c3700(0000) GS:ffff9ffc2f700000(0000) knlGS:fffff800534ed000
[ 6938.723275] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 6938.723275] CR2: 0000000007a4b110 CR3: 000000075f4bc005 CR4: 0000000000772ee0
[ 6938.723276] PKRU: 55555554
[ 6938.723276] Call Trace:
[ 6938.723282]  ? update_load_avg+0x7a/0x5d0
[ 6938.723284]  ? dequeue_entity+0xc6/0x450
[ 6938.723285]  ? check_preempt_curr+0x29/0x60
[ 6938.723286]  ? ttwu_do_wakeup+0x17/0x130
[ 6938.723287]  ? try_to_wake_up+0x1d1/0x4f0
[ 6938.723289]  ? copy_from_kernel_nofault+0x1d/0xf0
[ 6938.723291]  ? process_fetch_insn+0x102/0x690
[ 6938.723294]  ? tomoyo_init_request_info+0x8f/0xb0
[ 6938.723296]  ? tomoyo_path_number_perm+0x66/0x1d0
[ 6938.723308]  ? VBoxHost_RTThreadCtxHookEnable+0x33/0x50 [vboxdrv]
[ 6938.723313]  ? supdrvIOCtlFast+0x66/0xb0 [vboxdrv]
[ 6938.723316]  ? VBoxDrvLinuxIOCtl_6_1_32+0x56/0x230 [vboxdrv]
[ 6938.723319]  ? __x64_sys_ioctl+0x83/0xb0
[ 6938.723321]  ? do_syscall_64+0x33/0x80
[ 6938.723322]  ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 6938.723323] Modules linked in: tun ctr ccm michael_mic hid_jabra usbhid uhid rfcomm cmac algif_hash algif_skcipher af_alg typec_displayport snd_usb_audio snd_usbmidi_lib snd_rawmidi snd_seq_device vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev mc bnep cdc_ether usbnet r8152 hid_sensor_als hid_sensor_trigger hid_sensor_iio_common mii industrialio_triggered_buffer kfifo_buf industrialio hid_sensor_hub snd_soc_skl_hda_dsp snd_soc_hdac_hdmi iTCO_wdt rtsx_pci_sdmmc qrtr_mhi intel_pmc_bxt iTCO_vendor_support hid_multitouch intel_ishtp_hid snd_soc_dmic mmc_core hid_generic watchdog mei_hdcp intel_rapl_msr dell_laptop dell_wmi dell_smbios dell_wmi_descriptor wmi_bmof dcdbas dell_smm_hwmon x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm snd_hda_codec_hdmi irqbypass crc32_pclmul snd_hda_codec_realtek snd_hda_codec_generic ghash_clmulni_intel intel_cstate intel_uncore joydev snd_sof_pci snd_sof_intel_byt
[ 6938.723355]  snd_sof_intel_ipc snd_sof_intel_hda_common snd_sof_xtensa_dsp qrtr pcspkr snd_sof ns snd_sof_intel_hda ath11k_pci snd_soc_hdac_hda snd_hda_ext_core mhi snd_soc_acpi_intel_match snd_soc_acpi ledtrig_audio efi_pstore ath11k snd_hda_intel snd_intel_dspcfg soundwire_intel soundwire_generic_allocation qmi_helpers snd_soc_core mac80211 snd_compress soundwire_cadence snd_hda_codec snd_hda_core snd_hwdep soundwire_bus snd_pcm snd_timer snd i2c_i801 i2c_smbus soundcore cfg80211 rtsx_pci libarc4 mei_me mei xhci_pci xhci_hcd hci_uart btqca nls_ascii btrtl nls_cp437 btbcm intel_lpss_pci btintel vfat intel_lpss fat bluetooth idma64 usbcore thunderbolt intel_ish_ipc tpm_crb intel_ishtp usb_common processor_thermal_device tpm_tis ucsi_acpi intel_rapl_common tpm_tis_core intel_soc_dts_iosf typec_ucsi tpm jitterentropy_rng typec rng_core drbg ansi_cprng wmi i2c_hid battery button ecdh_generic rfkill hid ecc int3403_thermal int340x_thermal_zone intel_pmc_core intel_hid int3400_thermal
[ 6938.723391]  sparse_keymap acpi_thermal_rel acpi_tad ac acpi_pad msr parport_pc ppdev lp parport fuse configfs efivarfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic dm_crypt dm_mod i915 i2c_algo_bit drm_kms_helper cec crc32c_intel drm aesni_intel nvme psmouse glue_helper nvme_core libaes crypto_simd cryptd evdev serio_raw t10_pi crc_t10dif crct10dif_generic crct10dif_pclmul crct10dif_common video
[ 6938.723410] ---[ end trace 595db24fab13b167 ]---
[ 6938.939179] RIP: 0010:0xffffc2e90460e770
[ 6938.939185] Code: 89 02 c3 cc cc cc cc 53 49 89 ca 49 89 d3 41 8b 1b 41 8b 4b 04 9c 41 8b 02 83 24 24 bf 83 e0 40 48 09 04 24 9d 8b 06 8b 56 04 <f0> 0f c7 0f 89 06 89 56 04 9c 41 5b 41 8b 02 83 e0 bf 41 83 e3 40
[ 6938.939187] RSP: 0018:ffffc2e903b879b8 EFLAGS: 00010206
[ 6938.939189] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
[ 6938.939190] RDX: 0000000000000000 RSI: ffffc2e903b879d8 RDI: ffff9ff67a3fccfc
[ 6938.939191] RBP: ffffc2e904238000 R08: ffffc2e903b878c8 R09: ffffc2e903b87980
[ 6938.939192] R10: ffffc2e903b879cc R11: ffffc2e903b879e8 R12: ffffc2e904238000
[ 6938.939193] R13: ffffc2e903b87ba8 R14: 0000000000000000 R15: ffffc2e904227000
[ 6938.939195] FS:  00007fc0682c3700(0000) GS:ffff9ffc2f700000(0000) knlGS:fffff800534ed000
[ 6938.939196] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 6938.939197] CR2: 0000000007a4b110 CR3: 000000075f4bc005 CR4: 0000000000772ee0
[ 6938.939198] PKRU: 55555554
}}}

As this is reproducible, I can supply you with more logs if needed (and if you tell me what informaton you need)."	Andreas Sewe
16101	Windows guest desktop refresh rate is assumed to be 60Hz	Windows	VirtualBox 5.1.8	2016-10-21T19:14:01Z	2016-11-28T18:29:38Z	2016-11-28T18:29:38Z	"Host: Lubuntu 16.04 x86-64, Nvidia binary driver
Guest: Windows XP SP3

The host desktop vertical refresh rate is 50Hz.

The XP guest emulated vertical refresh rate is 60Hz. For example, Display Properties -> Advanced -> Monitor tab allows only one setting for Screen refresh rate: 60 Hertz.

Programs running in the guest which calibrate their timing to the Windows desktop refresh rate ""see"" a refresh rate of 60Hz, not the host's actual 50Hz rate.

To fix that, perhaps the guest graphics driver could have other selectable refresh rates?"	Donuts
20986	Windows Guest Additions cause Linux host to crash	Windows	VirtualBox 6.1.34	2022-06-14T15:05:50Z	2022-06-28T19:47:36Z	2022-06-28T19:47:36Z	"When I install Guest Additions on my clean-build Windows 10 guest, the host crashes when the guest boots (approx. 5s after the windows logon screen appears).

Host OS: Oracle Linux 8.5, kernel: 5.4.17-2136.306.1.3.el8uek.x86_64
Guest OS: Windows 10 Pro 21H2 (19044.1708)

The guest is stable without GA installed and the host also runs a number of Linux guests with GA installed with no issue. Neither the host nor Linux guests have X installed.

I have tried the following config changes for the Windows guest but these do not resolve the problem:
* Use graphicscontroller VBoxVGA
* Use graphicscontroller VBoxSVGA
* Use mouse ps2
* Use BIOS firmware
* Disable USB
* Disable audio
* Disable hpet
* Disable vrde

Configuration below, log of post-install boot attached:

{{{
#!div style=""font-size: 80%""
Code highlighting:
  {{{#!python
  Name:                        WindowsTest
  Groups:                      /Test
  Guest OS:                    Windows 10 (64-bit)
  UUID:                        86d3768a-e344-4edd-b21c-3fb816ebe87d
  Config file:                 /vm/Test/WindowsTest/WindowsTest.vbox
  Snapshot folder:             /vm/Test/WindowsTest/Snapshots
  Log folder:                  /vm/Test/WindowsTest/Logs
  Hardware UUID:               86d3768a-e344-4edd-b21c-3fb816ebe87d
  Memory size:                 8192MB
  Page Fusion:                 enabled
  VRAM size:                   128MB
  CPU exec cap:                100%
  HPET:                        enabled
  CPUProfile:                  host
  Chipset:                     piix3
  Firmware:                    EFI
  Number of CPUs:              2
  PAE:                         enabled
  Long Mode:                   enabled
  Triple Fault Reset:          disabled
  APIC:                        enabled
  X2APIC:                      enabled
  Nested VT-x/AMD-V:           disabled
  CPUID Portability Level:     0
  CPUID overrides:             None
  Boot menu mode:              message and menu
  Boot Device 1:               HardDisk
  Boot Device 2:               DVD
  Boot Device 3:               Not Assigned
  Boot Device 4:               Not Assigned
  ACPI:                        enabled
  IOAPIC:                      enabled
  BIOS APIC mode:              APIC
  Time offset:                 0ms
  BIOS NVRAM File:             /vm/Test/WindowsTest/WindowsTest.nvram
  RTC:                         local time
  Hardware Virtualization:     enabled
  Nested Paging:               enabled
  Large Pages:                 enabled
  VT-x VPID:                   enabled
  VT-x Unrestricted Exec.:     enabled
  Paravirt. Provider:          Default
  Effective Paravirt. Prov.:   HyperV
  State:                       running (since 2022-06-14T10:49:28.498000000)
  Graphics Controller:         VBoxSVGA
  Monitor count:               1
  3D Acceleration:             disabled
  2D Video Acceleration:       disabled
  Teleporter Enabled:          disabled
  Teleporter Port:             0
  Teleporter Address:
  Teleporter Password:
  Tracing Enabled:             disabled
  Allow Tracing to Access VM:  disabled
  Tracing Configuration:
  Autostart Enabled:           disabled
  Autostart Delay:             0
  Default Frontend:            headless
  VM process priority:         default
  Storage Controller Name (0):            SATA
  Storage Controller Type (0):            IntelAhci
  Storage Controller Instance Number (0): 0
  Storage Controller Max Port Count (0):  30
  Storage Controller Port Count (0):      4
  Storage Controller Bootable (0):        on
  SATA (0, 0): /vm/Test/WindowsTest/Snapshots/{3169be53-ec9e-418e-b4bc-dca229bb8816}.vdi (UUID: 3169be53-ec9e-418e-b4bc-dca229bb8816)
  SATA (3, 0): Empty
  NIC 1:                       MAC: 08002727E34F, Attachment: Bridged Interface 'enp10s0f0', Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none
  NIC 2:                       disabled
  NIC 3:                       disabled
  NIC 4:                       disabled
  NIC 5:                       disabled
  NIC 6:                       disabled
  NIC 7:                       disabled
  NIC 8:                       disabled
  Pointing Device:             USB Tablet
  Keyboard Device:             PS/2 Keyboard
  UART 1:                      disabled
  UART 2:                      disabled
  UART 3:                      disabled
  UART 4:                      disabled
  LPT 1:                       disabled
  LPT 2:                       disabled
  Audio:                       enabled (Driver: ALSA, Controller: HDA, Codec: STAC9221)
  Audio playback:              enabled
  Audio capture:               disabled
  Clipboard Mode:              disabled
  Drag and drop Mode:          disabled
  Session name:                headless
  Video mode:                  1024x768x32 at 0,0 enabled
  VRDE:                        enabled (Address 192.168.1.1, Ports 3389, MultiConn: off, ReuseSingleConn: off, Authentication type: null)
  VRDE port:                   3389
  Video redirection:           disabled
  VRDE property               : TCP/Ports  = ""3389""
  VRDE property               : TCP/Address = ""192.168.1.1""
  VRDE property               : VideoChannel/Enabled = <not set>
  VRDE property               : VideoChannel/Quality = <not set>
  VRDE property               : VideoChannel/DownscaleProtection = <not set>
  VRDE property               : Client/DisableDisplay = <not set>
  VRDE property               : Client/DisableInput = <not set>
  VRDE property               : Client/DisableAudio = <not set>
  VRDE property               : Client/DisableUSB = <not set>
  VRDE property               : Client/DisableClipboard = <not set>
  VRDE property               : Client/DisableUpstreamAudio = <not set>
  VRDE property               : Client/DisableRDPDR = <not set>
  VRDE property               : H3DRedirect/Enabled = <not set>
  VRDE property               : Security/Method = <not set>
  VRDE property               : Security/ServerCertificate = <not set>
  VRDE property               : Security/ServerPrivateKey = <not set>
  VRDE property               : Security/CACertificate = <not set>
  VRDE property               : Audio/RateCorrectionMode = <not set>
  VRDE property               : Audio/LogPath = <not set>
  OHCI USB:                    disabled
  EHCI USB:                    disabled
  xHCI USB:                    enabled

  USB Device Filters:

  <none>

  Available remote USB devices:

  <none>

  Currently Attached USB Devices:

  <none>

  Bandwidth groups:  <none>

  Shared folders:<none>

  VRDE Connection:             not active
  Clients so far:              0

  Capturing:                   not active
  Capture audio:               not active
  Capture screens:             0
  Capture file:                /vm/Test/WindowsTest/WindowsTest.webm
  Capture dimensions:          1024x768
  Capture rate:                512kbps
  Capture FPS:                 25kbps
  Capture options:             ac_enabled=false

  Guest:

  Configured memory balloon size: 0MB
  OS type:                     Windows10_64
  Additions run level:         0

  Guest Facilities:

  No active facilities.

  Snapshots:

   Name: 220613 Clean (UUID: 0f5525d8-e007-47f4-8669-1925a2d396ac) *
  }}}
}}}"	techpost
4381	windows guest - linux host file permissions changed on shared folders -> Fixed in SVN	Windows	VirtualBox 3.0.6	2009-07-03T15:34:45Z	2016-03-05T01:44:13Z	2016-03-05T01:44:13Z	"I recently upgraded to 3.0.0. 

I have a number of EXT3 and EXT4 share folders which I access from a windows host via VirtualBox's shared folder handler.  When I access a file in one of the EXT folders it reads and writes to it the first time.  When I modify the file and re-save, or auto save it says it is read-only.  This primarily happens with Microsoft office related products.  [URL=""http://ubuntuforums.org/showthread.php?t=1202151]""]This Thread[/URL] was started by some one having the same problem in 2.2.4  It does not happen on NTFS shared folders.  "	Tvtech
16770	Windows failure to boot after VirtualBox hangs up	Windows	VirtualBox 4.1.2	2017-05-19T14:00:38Z	2017-05-19T14:00:38Z	2017-05-19T14:00:38Z	"When I connected to ubuntu server via x2go software,
where VirtualBox is usually running 
I have seen that VirtualBox hangs up, and then I kill it.
After this, Windows (guest system) fails to run (it freezez on Please wait when iitializing)."	sayfull
15895	Windows 7 Lights Out on Linux Mint (Mate) Host	Windows	VirtualBox 5.1.4	2016-09-07T02:50:28Z	2016-09-07T02:50:28Z	2016-09-07T02:50:28Z	"Hi all,

We have been running a Windows 7 VM for quite a while and since the update to 5.1 have an issue with this VM just stopping. No lock up or anything, just a random lights out, this seems to happen when using network services more often than not.

Attached are a couple of logs from when this has happened.

TIA.

"	FFH4500
13744	Windows 7 guest can't connect to the Internet - host Wifi/guest bridged network adapter	Windows	VirtualBox 4.3.20	2015-01-07T12:50:18Z	2015-04-28T05:00:39Z	2015-04-28T05:00:39Z	"Virtualbox: 4.3.20
Hosts: Ubuntu 14.04, 14.10, 15.04
Guest: Windows 7 Pro; network adapter: Tested all, including Virtio
VM Network connection: Bridged

I have a Windows 7 guest (VM) installed in VirtualBox host running Ubuntu 14.04. Other users have experienced this in hosts running Ubuntu 14.10 and 15.04 too. 

This is on a laptop so I have two networking adapters. 

The VM's internet access works fine if I activate the ethernet adapter on the host, regardless of the VM's NAT or Bridged connection type. 

When the host's active Internet connection is Wireless then the VM's internet access only works in NAT mode.  In bridged mode, the guest obtains an IP address, but can’t connect to the Internet.

I need to use the Bridged connection type in order to participate in the LAN's native IP network, not a host's NAT network. Thanks for any help in advance.

Similar bug tickets:
#12408
#11254
"	Pedro Serrano
17482	Windows 7 guest - Shared Folders empty	Windows	VirtualBox 5.2.6	2018-01-19T11:50:29Z	2018-02-01T12:40:51Z	2018-02-01T12:40:51Z	"Upgrading from Virtualbox 5.2.0 shared folders on windows 7 guest machine stops to play. 
VBOXSVR network resource is still visible but it's empty.
Adding ""homegroup"" on ""home network"" Windows configuration enable folders, but on machine restart stops again.

Host is Ubuntu 17.10."	pmonaco
16536	Windows 7 guest - cannot control-click to select items	Windows	VirtualBox 5.1.14	2017-03-07T15:32:44Z	2017-03-07T15:32:44Z	2017-03-07T15:32:44Z	"Hello,

Holding the left ctrl key and clicking into items to select them does not properly: After having selected 3 o 4 items, the selection is gone. It happens with Explorer and Groupwise (mail client).

If I disable 'Mouse Integration' it works properly.

I downgraded to 5.0.32 and now it works properly with 'Mouse Integration'

I think this is somewhat related to:
https://www.virtualbox.org/ticket/1766
https://www.virtualbox.org/ticket/15714

But and I'm not sure that was an OSX only issue since we have similar problems here with 5.1.14 running on Centos 6.8 with Win7 as a guest.

Regards, 

  Edgar

"	esaumell
14146	Windows 7 grant privileges dialoges mess up seamless mode	Windows	VirtualBox 4.3.18	2015-05-22T19:50:45Z	2015-05-22T19:50:45Z	2015-05-22T19:50:45Z	"On my Debian Jessie Gnome host with Windows 7 as guest it happens quite often that Windows ""grant privileges"" / ""admin permission"" fullscreen dialogs mess up the seamless mode.

When that happens host and guest desktops are kind of frozen and both partially visible. It is not possible to perform mouse clicks on both host and guest then. The only way to come back to a normal state is using the host shutdown key and waiting for the guest to close.

"	conceptdeluxe
14262	WIndows 7 64 bits guests crash on 32 bits Linux host with VirtualBox v5.0	Windows	VirtualBox 5.0.0	2015-07-11T13:27:33Z	2016-03-11T14:17:32Z	2016-03-11T14:17:32Z	"I just upgraded to VirtualBox v5.0 today (I previously tried v5.0RC1 and v5.0RC2 and did not run into any issue), from VirtualBox v4.3.28.

After upgrade (including VBox additions upgrade) I got *systematic* BSOD when attempting to run a Windows 7 64 bits guest from my Linux 32 bits host (the 64 bits guest is running fine when launched from a 64 bits Linux host).
I thirst thought it was because of the old VBox additions (v4.3.28) in the 64 bits guest, so I upgraded these while running the guest on the 64 bits Linux host, but even after the upgrade to additions v5.0 in the guest, the latter kept crashing on boot when launched from the 32 bits host.

I'm attaching 3 screen shots of the BSODs: there doesn't seem to be any common crash point (the VM simply crashes at a seemingly random time during the boot process).

For now, I reverted to VirtualBox v4.3.28 which runs all my guests systems (32 or 64 bits, Windows or Linux) just fine on 32 bits Linux hosts..."	dinosaur0
21242	Windows 11 screen freeze with CPUs 100% busy	Windows	VirtualBox-7.0.2	2022-11-06T16:10:57Z	2022-12-09T22:02:55Z	2022-12-09T22:02:55Z	"Linux-Host with Win11 as guest: After an upgrade from the latest Windows 10 to Windows 11 22H2 the screen and with this the complete guest freezes with no further actions possible (except PowerOff/reboot).
This happend twice (= always up to now) within 4 minutes after power on and login."	snoopy2601
21506	Windows 11 guest is freezing when trying to install an Windows Update	Windows	VirtualBox-7.0.6	2023-02-15T19:47:09Z	2023-02-15T19:47:09Z	2023-02-15T19:47:09Z	"I experienced permanently that Windows 11 as guest freezes (with 100% CPU load), and I have to shutdown the virtual machine and restart. 

Now I can reproduce the freezing: when Windows installs an update (in my case during installation of Windows 11 22H2, at 24%. The log is attached - I cannot see any indicators. 

How can I narrow down the cause of the freezing?"	Dr. Michael Hälsig
21135	Windows 11 guest hangs at startup on Linux host	Windows	VirtualBox 7.0.0	2022-10-12T17:57:09Z	2022-10-19T11:15:28Z	2022-10-19T11:15:28Z	"- Windows 11 Guest 
- VM was created with Virtual Box 6.38 (I think) set up registry to bypass TPM checks.

Updated Virtual Box to 7.0.

When starting guest OS, I can see Windows progress animation for a while and then it just freezes"	vagaus
19509	Windows 10 VM crashes after copy/paste text coming from Ubuntu 18.04 browser window	Windows	VirtualBox 6.1.6	2020-04-17T19:08:54Z	2020-06-03T22:59:02Z	2020-06-03T22:59:02Z	"It happened twice: I copied some text in a browser and intended to paste it in a Windows application. The whole VM disappeared and the VBox Manager indicated  ""Aborted"" (or similar). It might be Vbox, it might also be the Guest Additions, I can't tell."	D.Bugger
19609	Windows 10 Pro failed to work inside Ubuntu 20 VirtualBox	Windows	VirtualBox 6.1.6	2020-05-21T15:26:54Z	2020-05-24T23:07:02Z	2020-05-24T23:07:02Z	"I have a couple of Windows 10 Pro VMs that used to run perfectly on Ubuntu 18, at the time i upgrade they started to get BSOD always, some times before login screen, some time after... the error seems to be in some part of the Windows Kernel 
Host:
AMD® A6-4400m apu with radeon(tm) hd graphics × 2 
AMD® Aruba
RAM 5.1 GiB
HD: 500.1 GB
Ubuntu 20.04 LTS
64 bits
GNOME Version: 3.36.2

Virtual Box version: Versión 6.1.6_Ubuntu r137129

GuestOS:
Windows 10 PRO
VM Type: Windows 10 64 bit
Chipset: PIIX3
I/O APIC Enabled
1 CPU
Execution limit: 100%
Network Bridge adaptor over wireless LAN interface

"	Charlymoon
18344	Windows 10 Issues with VirtualBox 6 VBoxSVGA Graphics Controller	Windows	VirtualBox 6.0.2	2019-01-21T19:05:12Z	2019-05-03T20:44:38Z	2019-05-03T20:44:38Z	"I have setup a Windows 10 (1809 x64) VM on a linux host using VirtualBox 6.0.2. I have installed Guest Additions only (otherwise a clean Windows 10 installation. Everything seems to be working fine for a little while, then several strange things start happening. Most notably I am not able to run anything as administrator. When a UAC prompt should show the screen gets dark as normal, then instead of showing the UAC prompt I get an error dialog like the one below. This occurs when trying to run anything (not just the 7-Zip installer) as admin. When this starts happening I am no longer able to open the settings app (it opens the splash screen but immediately closes). Search also stops working in Cortona/Start. Some graphical glitches also start happening at this time.

[[Image(https://i.imgur.com/760eziG.png)]]

All of these issues stop when I switch the Graphics Controller from VBoxSVGA to VBoxVGA.

The host System used is a Dell Inspiron 15 5570 (Core i5, 16GB RAM). I have tried hosting with Linux Mint 19.1 and Windows 10. Always with VirtualBox 6.0.2."	Androprise
16542	Windows 10 Insider - Not booting correctly with GA Video Driver	Windows	VirtualBox 5.1.16	2017-03-09T08:52:37Z	2017-09-26T10:30:50Z	2017-09-26T10:30:50Z	"As reported in https://www.virtualbox.org/ticket/15973
Using Fedora 25.
Just upgraded to VirtualBox 5.1.16.
Installed GA 5.1.16
Guest Settings:
2D Acceleration enabled
3D Acceleration disabled

Windows 10 refuses to boot, with the Video driver installed. After two tries, using Basic Video Driver works.

Relevant lines from log file (also attached):

{{{
00:00:07.649607 RTC: period=0x200 (512) 64 Hz
00:00:07.689199 VBVA: InfoScreen: [0] @0,0 3840x2025, line 0x3c00, BPP 32, flags 0x1
00:00:07.689219 Display::handleDisplayResize: uScreenId=0 pvVRAM=00007f9078000000 w=3840 h=2025 bpp=32 cbLine=0x3C00 flags=0x1
00:00:07.689250 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=3840x2025, Sending to async-handler
00:00:07.689364 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=3840x2025
00:00:07.689375 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=3840x2025
00:00:07.689620 GUI: UIFrameBufferPrivate::performResize: Size=3840x2025, Directly using source bitmap content
00:00:07.694329 GIM: HyperV: Guest indicates a fatal condition! P0=0x7e P1=0xffffffffc0000005 P2=0xfffff807d604e92b P3=0xffff8c0106b45cd8 P4=0xffff8c0106b45510
00:00:09.134352 NAT: Link up
00:00:10.146743 AHCI#0: Reset the HBA
00:00:10.147380 AHCI#0: Port 0 reset
00:00:11.354005 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
00:00:20.399165 GIM: HyperV: Reset initiated through MSR
00:00:20.399202 Changing the VM state from 'RUNNING' to 'RESETTING'
}}}

Enabling 3D Acceleration gives a ""System Exception Thread not handled"" error."	bhahlen
18856	Windows 10 hangs with High CPU Usage after changing number of Cores	Windows	VirtualBox 6.0.10	2019-08-20T04:35:43Z	2019-08-20T04:35:43Z	2019-08-20T04:35:43Z	"A Guest Windows 10 (Latest patches Aug 2019) built with a single core fails after initial startup when the CPU cores are changed to anything above 1. The machine usually stops with a black screen and the twirling dots and almost never reaches the login screen. The CPU usage sits at 100%

Building a new machine with multiple cores works fine. This appears to be a similar bug to one reported with Version 5.X of Virtual Box.

Host is Linux (OpenSUSE). Tried on two hosts, XEON and Desktop I4. Both systems are successfully running many other VirtualBox hosts, both Windows and Linux.
"	Eric Belcher
15889	Windows 10 guest turned to abort state when 3D acceleration is enabled	Windows	VirtualBox 5.1.4	2016-09-06T06:38:10Z	2017-07-26T10:35:14Z	2017-07-26T10:35:14Z		Kaho Ng
20089	Windows 10 Guest slow down when a screen grabber is active on the host	Windows	VirtualBox 6.1.16	2020-12-09T10:26:06Z	2021-09-14T07:34:21Z	2021-09-14T07:34:21Z	"When a screen grabber (like Teamviewer, MS Teams screen sharing, Zoom screen sharing etc.) is active on the host machine (Linux Mint 20), the Guest VM will slowing down more and more and finally freeze. 

This is reproduceble in relation with screen grabbing. When a regulary Teamviewer or Teams session is active, the Guest is usable normally. From the moment when I activate any screen sharing, the guest is affected immediately.

At the moment the screen grabbing is ended, the guest is usable normally again."	Codehunter
20180	Windows 10 guest OS crashes with STATUS_DATATYPE_MISALIGNMENT exception	Windows	VirtualBox 6.1.18	2021-02-10T11:34:01Z	2021-07-26T23:09:42Z	2021-07-26T23:09:42Z	"My '''Windows 10 20H2''' guest OS keeps crashing and rebooting after a few minutes of uptime, even when left at idle with no user activity.
The amount of uptime before crash varies, from a couple of minutes to maybe 30'.

This is an extract of the VBox.log file with the exception (full log attached):

{{{
00:04:04.476177 GIM: HyperV: Guest indicates a fatal condition! P0=0x1e P1=0xffffffff80000002 P2=0xfffff80426ae4793 P3=0xffffbd0cd2c0237a P4=0x7010008004002001
00:04:04.476246 GIMHv: BugCheck 1e {ffffffff80000002, fffff80426ae4793, ffffbd0cd2c0237a, 7010008004002001}
00:04:04.476246 KMODE_EXCEPTION_NOT_HANDLED
00:04:04.476246 P1: ffffffff80000002 - exception code - STATUS_DATATYPE_MISALIGNMENT
00:04:04.476246 P2: fffff80426ae4793 - EIP/RIP
00:04:04.476247 P3: ffffbd0cd2c0237a - Xcpt param #0
00:04:04.476247 P4: 7010008004002001 - Xcpt param #1
00:04:07.226307 AHCI#0: Reset the HBA
00:04:07.226322 VD#0: Cancelling all active requests
00:04:07.226560 AHCI#0: Port 0 reset
00:04:07.227608 VD#0: Cancelling all active requests
00:04:07.367081 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
00:04:09.277149 VMMDev: Guest Log: VBoxGuest: BugCheck! P0=0x1e P1=0xffffffff80000002 P2=0xfffff80426ae4793 P3=0xffffbd0cd2c0237a P4=0x7010008004002001
}}}

The VM's guest OS was freshly installed from Microsoft's ISO. No third party AV software nor drivers installed.

My host setup:
* OS: Ubuntu 20.04.1
* Kernel: tested with 5.8.0-41-generic (Ubuntu) and 5.9.16-050916-generic (mainline)
* System: HP ProBook 650 G8
* CPU: 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz
* VirtualBox: tested with 6.1.16 (Ubuntu's repo) and 6.1.18 r142142 (Oracle's repo)

Conditions that do not cause a crash:
* running the VM in safe mode
* running the VM in a different host with Ubuntu 20.04.1, kernel 5.8, Virtualbox 6.1.18 r142142, CPU AMD Ryzen 9 3900X
* converting the VM's vdi file to qcow2 and running it with KVM

What have been tested without success (VM still crashes):
* running it with a different CPU profile, ""i7-6700K"" instead of ""host""
* uninstalling the VirtualBox Guest Additions
* changing the paravirtualization interface from ""Default"" to ""Legacy""

This issue has been discussed in this forum post: https://forums.virtualbox.org/viewtopic.php?f=7&t=101667

Searching the forums for similar problems led to these apparently relevant discussions, all with no solutions nor workarounds:
* https://forums.virtualbox.org/viewtopic.php?f=7&t=101280
* https://forums.virtualbox.org/viewtopic.php?f=7&t=101353
* https://forums.virtualbox.org/viewtopic.php?f=7&t=99789
"	hottobar
20453	Windows 10 guest on Ubuntu host is extremely slow if cpu > 1	Windows	VirtualBox 6.1.22	2021-07-11T19:16:08Z	2021-07-12T11:53:04Z	2021-07-12T11:53:04Z	"I upgraded to Virtualbox 6.1, and I noticed a **great** slowdown on my Windows 10 guest. I tried to play with the settings, and I see that if I put the numbers of cpu to 1, the guest is faster!

So I tried to downgrade to 5.2 and set the number of cores to a number greater of 1. I have no problem at all."	Marco Sulla
19709	Windows 10 guest on Linux host aborts with VMSVGA3d OpenGL error 0x501 if 3D acceleration is enabled	Windows	VirtualBox 6.1.10	2020-07-09T07:59:56Z	2021-01-19T17:33:39Z	2021-01-19T17:33:39Z	"Host is Ubuntu 20.04 with NVidia 440.100 drivers. Guest is Windows 10 version 1909. I enabled 3D acceleration to reduce high CPU usage on the host even if the guest was showing low CPU usage. After some time (an hour or so) the VM aborted with the error:

1:14:24.245508 VMSVGA3d: OpenGL error 0x501 (idActiveContext=0xffffeeee) on line 2331 glPixelStorei(GL_UNPACK_ALIGNMENT, pSave->iAlignment)
01:14:24.252162 VMSVGA3d: OpenGL error 0x501 (idActiveContext=0xffffeeee) on line 2331 glPixelStorei(GL_UNPACK_ALIGNMENT, pSave->iAlignment)
"	gwiesenekker
19669	Windows 10 Guest just crshed, no idea why	Windows	VirtualBox 6.1.10	2020-06-16T07:49:29Z	2020-06-16T09:24:58Z	2020-06-16T09:24:58Z	"Starting VirtualBox 6.1.6, then 6.1.8, and now 6.1.10, on a Ubuntu host, my Windows 10 Guest VM started crashing for some unknown reason. It happened once when I copied/pasted some text from the guest to the host, but this morning I didn't do anything special. Just editing something...

Sorry that I can't give more info.

I think I'll revert to 6.1.4 for the time being."	D.Bugger
19141	windows 10 guest hangs on linux 5.3.12 host	Windows	VirtualBox 6.0.14	2019-12-09T18:54:33Z	2020-02-13T20:46:32Z	2020-02-13T20:46:32Z	"I upgrade my linux host, the kernel upgraded from linux-5.1.16 to 5.3.12.
I started VirtualBox and resumed my windows guest.
I started typing in a browser window, and the guest stopped responding.
I saved the guest state and restarted, and got a windows bluescreen.

I restarted the VM, and the guest froze after login.
I restarted the VM, and again the guest froze.

I rebooted the host reverting back to linux 5.1.16.
I started my VM and have not had any issues since."	rc
18334	Windows 10 guest freeze or crash	Windows	VirtualBox 6.0.2	2019-01-19T09:11:43Z	2019-01-20T07:17:32Z	2019-01-20T07:17:32Z	"After update to VBox 6.0.2 a Windows 10 64bit guest always freezes or completely crashes when VBoxSVGA and 3D acceleration are chosen. It happens as soon as Skype for Business starts on the VM.

Additionally I've got problems with keyboard grabbing as well as graphics (Outlook 2016 moves cursor to and fro while typing with hardware acceleration off but Excel opens files only when it's off).

Disabling 3D acceleration in the VM settings seems to solve the problems.

My host runs on Linux Mint Cinnemon 19 with an nVidia graphics adapter using the proprietary graphics driver."	Mellon
15620	Windows 10 guest freeze on startup (Linux x64 host)	Windows	VirtualBox 5.1.0	2016-07-15T07:47:36Z	2016-07-20T05:35:14Z	2016-07-20T05:35:14Z	"I upgraded my VirtualBox installation from Version 5.0.24 to Version 5.1.0. When starting my Windows 10 VM it freezes on startup when the Windows logo with the rotating dots beneath it is shown. The operating system of the host is openSUSE Tumbleweed. I've attached the logfile of the VM if you need more informations i'll try to provide them...

kind regards,

Christoph"	happenpappen
17758	Windows 10 guest crashes when Settings are opened	Windows	VirtualBox 5.2.10	2018-05-11T09:57:54Z	2018-05-11T10:00:20Z	2018-05-11T10:00:20Z	A windows 10 guest is crashing when the Settings are selected from the start menu. The host is Fedora 28 64-bit.	Panos Kavalagios
19210	windows 10 guest crashes when exploring host shared folder	Windows	VirtualBox 6.0.10	2020-01-08T15:40:26Z	2021-06-17T13:24:14Z	2021-06-17T13:24:14Z	I have shared a folder from my linux host and boot a windows 10 pro (64-bit originally installed from M$ download site) guest vm to use windows explorer to view the files in the share which appears as Z: drive. I choose to change the sort column to view by modified date and I can no longer get a response from the win 10 guest. The next moment I see the vm rebooting. I can reproduce this behaviour each time. Linux 64 bit vbox 6.0.10 r132072 (Qt5.9.5) I have attached the logfile	captain cranium
20463	Windows 10 guest crashes on startup	Windows	VirtualBox 6.1.22	2021-07-19T05:53:26Z	2021-07-19T10:35:04Z	2021-07-19T10:35:04Z	"Host is Pop OS 21.04 with kernel 5.13.2-051302-generic from Ubuntus mainline kernels.

Usually this works just fine, my VM started just fine on kernel 5.13.1 but now with the update to .2 it crashes on startup. I did do a `sudo vboxconfig` after a new kernel update, this did not help.

The crash is as follows:

{{{
	Jul 19 07:37:44 pc1 vboxdrv.sh: Stopping VirtualBox services.
	Jul 19 07:37:44 pc1 vboxdrv.sh: VirtualBox services stopped.
	Jul 19 07:37:46 pc1 vboxdrv.sh: Starting VirtualBox services.
	Jul 19 07:37:46 pc1 vboxdrv.sh: Building VirtualBox kernel modules.
	Jul 19 07:37:50 pc1 vboxdrv.sh: VirtualBox kernel modules built.
	Jul 19 07:37:50 pc1 kernel: [  470.024094] vboxdrv: Found 32 processor cores
	Jul 19 07:37:50 pc1 kernel: [  470.041364] vboxdrv: TSC mode is Invariant, tentative frequency 3399987811 Hz
	Jul 19 07:37:50 pc1 kernel: [  470.041365] vboxdrv: Successfully loaded version 6.1.22 (interface 0x00300000)
	Jul 19 07:37:50 pc1 kernel: [  470.244020] VBoxNetFlt: Successfully started.
	Jul 19 07:37:50 pc1 vboxdrv.sh: VirtualBox services started.
	Jul 19 07:37:50 pc1 kernel: [  470.245483] VBoxNetAdp: Successfully started.
	Jul 19 07:37:51 pc1 kernel: [  470.914903] SUPR0GipMap: fGetGipCpu=0x3b
	Jul 19 07:37:52 pc1 gnome-shell[4732]: ../../../gobject/gsignal.c:2732: instance '0x56199cb9d210' has no handler with id '59274'
	Jul 19 07:37:52 pc1 kernel: [  471.454134] vboxdrv: 0000000000000000 VMMR0.r0
	Jul 19 07:37:52 pc1 kernel: [  471.555385] vboxdrv: 0000000000000000 VBoxDDR0.r0
	Jul 19 07:37:52 pc1 kernel: [  471.609014] VBoxNetFlt: attached to 'enp7s0' / a8:5e:45:11:96:76
	Jul 19 07:37:52 pc1 kernel: [  471.611471] vboxdrv: 0000000000000000 VBoxEhciR0.r0
	Jul 19 07:37:52 pc1 kernel: [  471.611804] VMMR0InitVM: eflags=246 fKernelFeatures=0x0 (SUPKERNELFEATURES_SMAP=0)
	Jul 19 07:37:52 pc1 kernel: [  471.643364] device enp7s0 entered promiscuous mode
	Jul 19 07:37:52 pc1 gnome-shell[4732]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x620018a specified for 0x620018c.
	Jul 19 07:38:13 pc1 kernel: [  492.433391] device enp7s0 left promiscuous mode
	Jul 19 07:38:13 pc1 kernel: [  492.458757] 
	Jul 19 07:38:13 pc1 kernel: [  492.458757] !!Assertion Failed!!
	Jul 19 07:38:13 pc1 kernel: [  492.458757] Expression: pCritSect->s.Core.NativeThreadOwner == hNativeSelf
	Jul 19 07:38:13 pc1 kernel: [  492.458757] Location  : /home/vbox/vbox-6.1.22/src/VBox/VMM/VMMAll/PDMAllCritSect.cpp(575) int PDMCritSectLeave(PPDMCRITSECT)
	Jul 19 07:38:13 pc1 kernel: [  492.458764] ffffad525034a000 <R3_STRING>: ffffffffffffffff != 00007f6f9c164640; cLockers=-1 cNestings=1
	Jul 19 07:38:13 pc1 kernel: [  492.489177] vboxnetflt: 0 out of 0 packets were not sent (directed to host)
	Jul 19 07:38:26 pc1 gnome-shell[4732]: ../../../gobject/gsignal.c:2732: instance '0x56199871a0a0' has no handler with id '61338'
	Jul 19 07:38:26 pc1 kernel: [  506.400406] vboxdrv: 0000000000000000 VMMR0.r0
	Jul 19 07:38:27 pc1 kernel: [  506.511297] vboxdrv: 0000000000000000 VBoxDDR0.r0
	Jul 19 07:38:27 pc1 kernel: [  506.553575] VBoxNetFlt: attached to 'enp7s0' / a8:5e:45:11:96:76
	Jul 19 07:38:27 pc1 kernel: [  506.556406] vboxdrv: 0000000000000000 VBoxEhciR0.r0
	Jul 19 07:38:27 pc1 kernel: [  506.556838] VMMR0InitVM: eflags=246 fKernelFeatures=0x0 (SUPKERNELFEATURES_SMAP=0)
	Jul 19 07:38:27 pc1 kernel: [  506.589360] device enp7s0 entered promiscuous mode

}}}"	robert21
20230	Windows 10 guest crashed when trying to paste image to guest	other	VirtualBox 6.1.18	2021-03-02T03:52:03Z	2021-03-02T03:58:24Z	2021-03-02T03:58:24Z	"When trying to paste image from Windows 10 guest to Linux host, the guest crashed.

I'm running linux test build version 6.1.19 r142946 (Qt5.6.1)

Steps before the crash:

1. Guest: Select and copy an image from the Windows Draw application
2. Host: In GIMP, select menu File -> New -> From clipboard
3. The guest crashed

Attached is the crash dump"	cooldog
17404	Windows 10 guest aborts on 5.2.4	Windows	VirtualBox 5.2.4	2017-12-27T15:41:25Z	2018-01-02T19:55:46Z	2018-01-02T19:55:46Z	After updating to 5.2.4 on CentOS7 my Windows 10 guest aborts frequently. This occurred every now and then on prior Virtualbox builds but is much more frequent on this version. I would be happy to provide any additional requested information on how to resolve but I am not sure what files you would like. I do use shared folders and recall in the past that was sometimes an issue.	jim.rather
21099	Windows 10 doen's work well with 3D acceleration enabled	Windows	VirtualBox 6.1.36	2022-09-08T13:41:56Z	2022-09-08T13:41:56Z	2022-09-08T13:41:56Z	With Windows 10, if 3D acceleration is enabled I have big graphic bugs and the VM can even reboot without a reason.	-RedHead-
15663	Windows 10 BSDO in VirtualBox 5.1	Windows	VirtualBox 5.1.0	2016-07-22T09:10:35Z	2016-07-22T09:10:35Z	2016-07-22T09:10:35Z	"I have tried several times to install Windows 10 x64 in VirtualBox 5.1 on a host Lenovo x61 laptop running Fedora 24 x64. The installation of Windows 10 crashes with a Sad Face and Blue screen. I have tried with Windows 10 1511 and Windows 10 1511_2 DVDs. I also tried windows 8.1 and this also failed with a BSOD. The only installation which finished successfully was of windows 7 SP1.

thanks for your products and keep up the good work"	dino.conti
16231	Windows 10 - Problem with brightness and 2D/3D	Windows	VirtualBox 5.1.10	2016-11-25T14:00:14Z	2016-11-25T14:00:14Z	2016-11-25T14:00:14Z	"Dear support,

I have fedora 24 server with Virtualbox 5.1.10. I hoped that with time and new releases of Virtualbox, Windows 10 problems would be resolved but now I have the following issue:
- I can't set up brightness of video
- Powerpoint with video is slow

With Windows 7/8 performance were good but with windows 10, system is in general slower.

My host is a Thikpad T540p with 6 GB memory, Bumblebee-neauveau for Intel with Nvidia GPU:
00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06)
01:00.0 VGA compatible controller: NVIDIA Corporation GK208M [GeForce GT 730M] (rev a1)

Windows 10 release is 1607 (Build 14393.447).

If I select 2d or 3d or disable both, nothing change... It seems better without flag in configuration.

Have you any advices?

I attache Vbox.log

Thanks in advance
Mario

"	santomar
16574	Win7 Pro lockup using WDDM and Aeroglass Decorations	Windows	VirtualBox 5.1.18	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
13658	Win7 64bit guest changing color scheme, nothing happens	Windows	VirtualBox 4.3.18	2014-11-29T06:19:23Z	2014-12-02T10:57:04Z	2014-12-02T10:57:04Z	"My configuration:

Laptop i74500U, 8gb + external monitor 1920x1080
Host: Fedora 20
Guest: Windows 7 64bit SP1 and recents updates"	par7133
18740	Win7 64 bit  guest crashes	Windows	VirtualBox 5.2.30	2019-07-03T04:46:31Z	2019-07-05T12:16:10Z	2019-07-05T12:16:10Z	"reproduction steps:
1. I start the virtual machine
2. A window appears in which windows 7 x64 starts to load
3. After 10-30 seconds the virtual machine window closes."	art
21431	Win11 guest freezes if VBoxSVGA is used.	Windows	VirtualBox-7.0.6	2023-01-25T16:19:18Z	2023-02-16T22:08:06Z	2023-02-16T22:08:06Z	"Win11 guest is very unstable if graphics adapter is set VBoxSVGA. It freezes totally very often. I can only see in the logs that guest is unresponsive. Disabling 3d acceleration does not help, only switching to VBoxVGA helps.

Operating System: Fedora Linux 37
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8
Kernel Version: 6.1.7-200.fc37.x86_64 (64-bit)
Graphics Platform: X11
Processors: 16 × Intel® Core™ i7-10870H CPU @ 2.20GHz
Memory: 15.4 ГиБ of RAM
Graphics Processor: Mesa Intel® UHD Graphics
Driver version: mesa 22.3.3
Manufacturer: Dell Inc.
Product Name: Dell G15 5510

Second graphics card is NVIDIA GeForce RTX 3060 Laptop (optimus) in offload mode
Driver 525.85.05
"	MaxF
18847	win10 guest on opensuse 15.1 host crashes on saving session	Windows	VirtualBox 6.0.10	2019-08-16T21:32:36Z	2019-08-17T09:19:18Z	2019-08-17T09:19:18Z	"When trying to save a session with a win10 guest vbox 6.0.10 crashes with segmentation fault after about 75% of the progress bar.
After rollback to vbox 6.0.8 everything works nicely.

With other guests (winxp, win7, opensuse) this problem did not occur. It is specific to this one w10 vmachine.
vbox does not provide a proper post mortem report when it crashes and says so."	andreas366
17114	Win10 guest hangs when USB attached	Windows	VirtualBox 5.1.28	2017-09-28T08:24:10Z	2018-01-10T19:56:07Z	2018-01-10T19:56:07Z	"When I attach a USB device to the Win10 guest, it ''sometimes'' causes total freeze of the system. That ''sometimes'' means like 1/10 to 1/50. I can only do hard power off, the system does not react on anything (I tried sending Ctrl+Alt+Del, sending the shutdown signal). The screen remains frozen (no BSOD or such). The integrated cursor moves normally and shows the Windows cursor, though.

I mostly experience the problem with USB device SEGGER J-Link Ultra [0100] (1366:0101), as I do need to attach it detach it quite frequently. I have it in the autoconnect filter. There was no problem with this device on my previous machine (Debian 8 64bit host, Win7 Pro 32bit guest, VirtualBox 4.3). Anyway, I don't think it's a problem of this particular device. Once or twice I experienced this behaviour without having the device attached to the computer.

I'm experiencing the problem since I upgraded my PC (new HW, new host system, new virtual system). I already updated all (host, vbox, guest) a couple of times, with no change.

Host: Debian 9 Stretch, 64bit, 16 GB RAM[[BR]]
Guest: Windows10 Pro, 64bit, 4 GB RAM[[BR]]
VBox: 5.1.28 r117968 linux.amd64 (Sep 13 2017 15:04:33), Guest Additions installed
"	ymanCZ
17555	"Win10 ""Display driver failed to start"" always if 3D accel is enabled (Linux host)"	Windows	VirtualBox 5.2.6	2018-02-20T01:39:00Z	2018-02-28T05:24:18Z	2018-02-28T05:24:18Z	"Linux 17.10 host using X.Org (not Wayland), Intel i7-8700K built-in graphics.

Every time the Win10 guest starts, a ""slide out"" notification says:

   ""Display driver failed to start""

(and the desktop can not be resized I'll attach a screen shot).

I've re-installed the Guest Additions multiple times and rebooted the host too.

Finally I tried disabling 3D Acceleration for the guest, and now it works okay.

I'll attach log files which might be useful.  LMK if you need other info.

"	Jim Avera
15559	Win-XP fails to start in normal/last-working-breakpoint 9 of 10 times	Windows	VirtualBox 5.0.22	2016-06-29T21:16:41Z	2016-07-10T18:30:25Z	2016-07-10T18:30:25Z	"Initiating Windows XP SP3 fails consistently before or during ""Welcome"" Screen. The VM works using all safe modes. (Terminal, GUI, GUI with Network). The VM (WIN XP reports: (see attachment) intelppm.sys DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS

On the rare occasion that the VM Win XP boots up, it runs normally, and then shuts down via the O/S shutdown command as expected. 

 "	winthrom
20534	Win server 2008 does not autostart after update to 6.1.22_Ubuntur144080	Windows	VirtualBox 6.1.22	2021-09-03T12:42:58Z	2021-09-06T08:47:03Z	2021-09-06T08:47:03Z	"L.S,

We have updated several Linux hosts and Virtualbox is updated in that proces to 6.1.22_Ubuntur144080. Win 10 vm's autostart, but win 2008 server vm's fail to autostart after the update. This is noted for all the Linux hosts (4) we have updated.

Regards,

August




"	AO
14205	Win guests on Dell laptops have black display for integrated webcam via passthrough	Windows	VirtualBox 4.3.28	2015-06-17T01:45:32Z	2015-06-17T01:45:32Z	2015-06-17T01:45:32Z	"As the original bug reported, #13728, was limited to different hardware and software, I created a new bug report.

Using Fedora 22 64bit host, and Win 8.1 guest, passthrough webcam produces a black screen/display on Dell Inspiron 15 5000 series.  

This is despite using the latest Virtualbox and Guest Additions.  No suggested fix has worked."	H0wdy
14036	Win 8.1 guest vm machine hangs with VBoxGuestAdditions	Windows	VirtualBox 4.3.26	2015-04-09T06:12:39Z	2015-04-09T07:16:18Z	2015-04-09T07:16:18Z	"I submitted a ticket #14030 few days ago, and get resolved when i applied diff_smap_4. 

But a new problem comes,I installed VBoxGuestAdditions to my Win 8.1 guest machine, reboot system. When i input the password and login to Win8.1,The VM Machine hangs.I killed the process and restart the win8.1 guest to safe mode,uninstall VBoxGuestAdditions and restart again, Guest is up and running.

I have tried this for several times, Guest machine will hang on logn as long as VBoxGuestAdditions installed.

"	fedvb
16851	Win 7 x64 Guest on Ubuntu 16.04 Host Freeze after ~4 Hours	Windows	VirtualBox 5.1.22	2017-06-21T18:34:27Z	2017-06-22T08:50:14Z	2017-06-22T08:50:14Z	"Have had a persistent problem for some time now (unsure when it started) whereby my Windows 7 x64 guest will completely lock up and is unresponsive.  VirtualBox console and other running non-Windows VMs do not seem to be affected.  The VirtualBox interface is still active and I can manipulate settings via the menu options in the GUI, but the guest OS GUI is frozen at the point it stopped working.

Saving State, then Restoring doesn't affect the outcome - only way to recover is to power off the guest VM and start it up again.

Reported this issue over in the forum (https://forums.virtualbox.org/viewtopic.php?f=7&t=82819) and was advised that this may be a rarely reproducible issue involving the NAT network subsystem and that logging a bugtrac ticket would be the best way to address this issue.

This appears to be the point at which the guest crashes (from Vbox.log):

{{{
00:26:21.080234 NAT: resolv.conf: nameserver 192.168.56.50
00:26:21.080254 NAT: resolv.conf: nameserver 127.0.1.1
00:26:21.080262 NAT: Adding domain name laptop
00:26:21.080264 NAT: DNS#0: 192.168.56.50
00:26:21.080266 NAT: DNS#1: 127.0.1.1
00:26:21.080269 NAT: DHCP offered IP address 10.0.2.15
00:26:22.688094 NAT: dnsproxy: timeout: req 00007f56d4071640 dnsgen 2 != 3 on socket 50 (udp) exp. in -427 state=SS_ISFCONNECTED f_(addr:port)=10.0.2.3:53 l_(addr:port)=10.0.2.15:50425 name=0.0.0.0:54045
03:01:30.079058 NAT: Can't allocate mbuf
03:01:38.957814 NAT: Link up
03:01:44.952776 NAT: Link up
03:01:50.966947 NAT: Link up
03:01:56.962828 NAT: Link up
03:02:02.966836 NAT: Link up
03:02:23.001524 NAT: Link up
03:02:29.001906 NAT: Link up
03:02:32.603387 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
}}}


Full vbox.log file attached.
Core dump is available, but may contain sensitive data so I'd prefer not to attach to this ticket.  Have an email out to Frank Mehnert, but would gladly take instruction from elsewhere on how to get this to interested parties, securely."	John Mackoy
11590	Win 7 VM slows down when presenting in GoToMeeting	Windows	VirtualBox 4.2.8	2013-03-13T22:24:02Z	2018-11-14T23:53:24Z	2018-11-14T23:53:24Z	"This bug has been on-going for me since the January time frame. The basic issue is that when using GoToMeeting in a Win7 VM, and if my VM is made the presenter, then graphics slow down to the point where the VM becomes unusably slow. The VM can be in a meeting with someone else presenting and it's fine. Only slow when the VM becomes the presenter. Slow means the cursor is unresponsive, gui interaction inside the Win 7 VM is very slow, cursor flicker. Pause the screen so that it's not being updated and the VM becomes fast again.

I've seen this problem on 3 Win 7 VMs, two on this machine and one on my laptop. Both hosts are Gentoo Linux 64-bit, mostly stable and completely up to date. 

Both machines can boot Win 7 natively and have not problems. VMWare running Win XP on the same machines has no problems.

I am going to attempt to attach a log file of the VM booting, starting Google Chrome, starting G2M, having the problems and then shutting down the VM."	Mark Knecht
13728	Win 7 Guest/Linux host - integrated webcam on Dell 5520 laptop - black display	Windows	VirtualBox 4.3.20	2015-01-03T07:18:04Z	2015-09-05T15:15:34Z	2015-09-05T15:15:34Z	"On a Dell 5520 laptop, Fedora 64 bit 21 host, Win 7 64 bit guest, the integrated webcam provides nothing but a black display on passthrough, but on direct connect, the video shows but very slow/choppy.

It works fine on host applications.

An external USB camera works fine passthrough on the same system.

Attached is log."	H0wdy
21295	Win 7 32b guest VM craash when installing guest additions 7.0.4	Windows	VirtualBox-7.0.4	2022-11-22T22:05:47Z	2022-11-22T22:23:21Z	2022-11-22T22:23:21Z	"Host:
Ubuntu 20.04.5 LTS
kernel 5.4.0-132
Wayland, Gnome 3.36.8

Guest:
Windows 7 (32bit)
Guest Additions 7.0.2 previously installed

Procedure:
Start guest VM; boot; login
From VM window menu -> Devices -> Insert Guest Additions CD image...
Start Guest additions installer from Windows Explorer
Install runs through until the graphics driver is installed.
Window resizes shortly to VGA (probably the 'uninstall' of the old driver) then goes back to previous resolution (probably when the new driver is enabled).
This is the moment when the VM crashes.
Reproducible.
This error is new in 7.0.4. It was not there in 7.0.2.
The Windows VM can be restarted normally after the abort and the guest additions appear to be installed, including the graphics driver. Vbox Task Bar App reports v7.0.4 installed.

Maye a duplicate to https://www.virtualbox.org/ticket/21123"	sunrider
13973	Win 10 x64 guest with Guest Additions crashed host xserver	Windows	VirtualBox 4.3.26	2015-03-21T15:10:35Z	2015-03-29T09:02:57Z	2015-03-29T09:02:57Z	"Host:
Linux Mint 17.1 x64.
X.Org v1:7.7+1ubuntu8.

Guest:
Windows 10 x64 Technical Preview 9926.

What I did:
1) Installed Win 10x64 English.
2) Installed Guest additions and asked to restart.
3) Tried to login to windows after the restart. Host froze and after ~1 min, X crashed. Attached pic shows what I see on tty7 (X tty after crash).

I'm guessing that something is wrong with the guest additions."	Tharbad
7405	When RDP to VM is terminated badly - VM still holds RDP session open	Windows	VirtualBox 3.2.8	2010-08-31T18:38:34Z	2015-08-13T17:32:44Z	2015-08-13T17:32:44Z	"Now my Vista machine is a piece on junk and likes to lock up. So it needs cold rebooting. The problem is that the vrdp tcp connection stays established on the Linux machine even after rebooting the vista machine. So I cannot reconnect back to my running VM and also have not been able to force it to disconnect. I've tried below with no success.
{{{
VBoxMange controlvm winxp_work vrdp  off
VBoxMange controlvm winxp_work vrdp  on
}}}

I see from netstat that the VM still thinks there is a RDP session established. Even when the keepalive timer times out - it just resets rather then closing the connection. Occasionally if I wait long enough - I can reconnect - but we are talking 15min plus.


Some details:
 1. Virtual Box installed (3.2.8r64453) on 64bit Linux host (amd64 all distro version).
 2. Win XP 32 bit guest installed with latest Virtual Box tools.
 3. VM started with ""VBoxHeadless -s winxp_work &""
 4. VBoxHeadless disown'ed from bash to stop it killing it if I close shell
 5. Access VM from Vista 64 via remote desktop
 6. Linux iceweasel 2.6.30.4-2 !#7 SMP Tue Aug 11 17:12:39 MDT 2009 x86_64 x86_64 x86_64 GNU/Linux
 7. Using a bridged interface

Does anyone have any ideas how I can convince the VM that the RDP session is over - or maybe I need to change some global tcp settings somewhere?
{{{
iceweasel:~ # netstat -ntap | grep VB
tcp        0      0 0.0.0.0:3389            0.0.0.0:*               LISTEN      26054/VBoxHeadless
tcp        0  49850 192.168.124.7:3389      192.168.124.3:1116      ESTABLISHED 26054/VBoxHeadless
iceweasel:~ # netstat -ntap --timer
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    Timer
...
tcp        0  49850 192.168.124.7:3389      192.168.124.3:1116      ESTABLISHED 26054/VBoxHeadless  on (95.16/9/0)
}}}"	Adrian
7804	When mounting shared host files with vboxsf, softlinks fail to be copied.	Linux	VirtualBox 3.2.12	2010-12-07T20:23:47Z	2010-12-07T20:23:47Z	2010-12-07T20:23:47Z	"Description:

A host OS Ubuntu 9.10 shares out files in a directory Engineering_85 as an OracleVirtualBox 'device'. A guest OS Ubuntu 9.10 mounts the host files, thus:

{{{ 
sudo mount -t vboxsf -o rw,gid=1000,uid=1000,dmode=0777,fmode=0777 Engineering_85  /home/ddade/mounts
}}} 
 
The mount is listed in the guest OS, thus: 

{{{
ddade@UbuntuBlade01:~/mounts/test/server/sql_performance$ ls -lt
ls: cannot access test_database: No such file or directory
ls: cannot access refresh_database: No such file or directory
ls: cannot access test_sql_performance: No such file or directory
total 24
-rwxrwxrwx 1 ddade ddade  578 2010-12-07 14:31 l.txt
-rwxrwxrwx 1 ddade ddade  518 2010-12-06 17:10 Jamfile
-rwxrwxrwx 1 ddade ddade 2717 2010-12-06 17:10 refresh_database.cpp
-rwxrwxrwx 1 ddade ddade  423 2010-12-06 17:10 run-me-first.sh
-rwxrwxrwx 1 ddade ddade 2170 2010-12-06 17:10 test_database.cpp
-rwxrwxrwx 1 ddade ddade 4093 2010-12-06 17:10 test_sql_performance.cpp
?????????? ? ?     ?        ?                ? refresh_database
?????????? ? ?     ?        ?                ? test_database
?????????? ? ?     ?        ?                ? test_sql_performance
}}}
 
Problem:
Links show up as ""No such file or directory"".  This is an error.  Linux 'inodes' that represent softlinks should be copied as directory entries (regular files).  It appears that OracleBox insists on following the links to their target.  

If the target does not actually exist, that is OK.  The link should be shared-out to the guest OS, and presented correctly as if the file were on the original (host) OS file system.

"	V
13380	When I try to look for updates I get Wrong SSL certificate format	other	VirtualBox 4.3.14	2014-09-12T08:36:40Z	2020-01-18T11:36:31Z	2020-01-18T11:36:31Z	"When I try to look for updates from the help menu I get ""The network operation failed with the following error : Wrong SSL certificate format"".
"	Mediaf
17909	weird time adjustment	Windows	VirtualBox 5.1.38	2018-08-02T08:39:40Z	2018-08-02T08:39:40Z	2018-08-02T08:39:40Z	"Hello. I use ""VirtualBox Graphical User Interface Version 5.1.38_Ubuntu r122592 © 2004-2018 Oracle Corporation (Qt5.5.1)"". And using Windows XP on it. I use my own program to track the accuracy of the time, and sometimes I notice that Windows is weirdly tuning the time. For example I attach today's graph of adjustment.

It can be seen that the detuning runs on some kind of sinusoid, and then at some point it goes out on a flat line. Then, when the detuning builds up, it for some reason again goes to the sinusoid of an unacceptably large amplitude, and then again sets the normal time. On the vertical axis - milliseconds. That is, during these sinusoid detuning reaches 15 seconds - it's terrible, I think. 

I tried to disable the vm module on WindowsXP, and the tuning is disabled, but the clipboard between vm and my machine stops working as well - thats not good.

So, I have a couple of questions:

1) Why is there such a strange sinusoid used in the time adjustment (which uses the SetSystemTimeAdjustment) instead of a rapidly decaying exponent?

2) can I disable this strange time adjustment without disabling the clipboard?

"	daybit
18725	WebCam passtrough doesn't properly pass format capabilities to guest GStreamer	Linux	VirtualBox 6.0.8	2019-06-25T07:19:42Z	2019-06-25T07:26:33Z	2019-06-25T07:26:33Z	"When attaching a webcam to a Guest OS using Devices->Webcams menu, resulting device in the Guest system reports following format capabilities to GStreamer:
{{{
...
0:00:00.206792405 15881  0x88fee00 INFO                    v4l2 gstv4l2object.c:1202:gst_v4l2_object_fill_format_list:<camerasrc-real-src-actual-src-v4l:src>   MJPG
0:00:00.207621489 15881  0x88fee00 INFO                    v4l2 gstv4l2object.c:4136:gst_v4l2_object_probe_caps:<camerasrc-real-src-actual-src-v4l:src> probed caps:
image/jpeg, width=(int)1280, height=(int)960, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 25/1, 20/1, 15/1, 10/1, 5/1 };
image/jpeg, width=(int)1280, height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 25/1, 20/1, 15/1, 10/1, 5/1 };
image/jpeg, width=(int)1184, height=(int)656, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 25/1, 20/1, 15/1, 10/1, 5/1 };
...
}}}
(continues in similar fashion with similar formats)


This results in webcam being incompatible with CameraBin pipeline:

{{{
0:00:00.208131863 15881  0x88fee00 INFO        GST_ELEMENT_PADS gstutils.c:1227:gst_element_get_compatible_pad:<src-crop> Could not find a compatible pad to link to camerasrc-real-src:src
0:00:00.208198762 15881  0x88fee00 INFO                GST_PADS gstutils.c:1035:gst_pad_check_link: trying to link camerasrc-real-src:src and src-crop:sink
0:00:00.209174846 15881  0x88fee00 INFO                GST_PADS gstpad.c:2378:gst_pad_link_prepare: trying to link camerasrc-real-src:src and src-crop:sink
0:00:00.209487092 15881  0x88fee00 INFO                GST_PADS gstpad.c:2434:gst_pad_link_prepare: caps are incompatible
0:00:00.209526143 15881  0x88fee00 INFO                GST_PADS gstpad.c:2529:gst_pad_link_full: link between camerasrc-real-src:src and src-crop:sink failed: no common format
0:00:00.209583393 15881  0x88fee00 INFO           GST_PARENTAGE gstbin.c:1799:gst_bin_remove_func:<camerasrc> removed child ""src-crop""
0:00:00.209642419 15881  0x88fee00 WARN                 default camerabingeneral.c:87:gst_camerabin_add_element_full:<camerasrc> error: linking src-crop failed
0:00:00.209701572 15881  0x88fee00 INFO        GST_ERROR_SYSTEM gstelement.c:2145:gst_element_message_full_with_details:<camerasrc> posting message: GStreamer error: negotiation problem.
}}}


While on guest system or when attaching as a regular USB device, it reports the following format capabilities:
{{{
...
0:00:00.213225446 15913  0x92dee00 INFO                    v4l2 gstv4l2object.c:1202:gst_v4l2_object_fill_format_list:<camerasrc-real-src-actual-src-v4l:src>   YUYV
0:00:00.213341622 15913  0x92dee00 INFO                    v4l2 gstv4l2object.c:4136:gst_v4l2_object_probe_caps:<camerasrc-real-src-actual-src-v4l:src> probed caps:
video/x-raw, format=(string)YUY2, width=(int)640, height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 15/1 };
video/x-raw, format=(string)YUY2, width=(int)352, height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 15/1 };
...
}}}

And everything works fine. This makes a webcam incompatible with any application that uses gstreamers' camerabin, for example, a Qt applications.

Attached are exempts from different logs, but there isn't much of interest except for what is provided.

This has been tested on two Host 64-bit machines running Arch Linux and Ubuntu 18.04, with 64-bit Ubuntu 18.04 Guest and another 32-bit Linux-based Guest OS. Results are identical."	SuperPrower
19510	Webcam Lenovo P50 doesn't work => insufficient information provided	Windows	VirtualBox 6.1.6	2020-04-17T21:42:51Z	2020-11-27T18:06:02Z	2020-11-27T18:06:02Z	"I have a Lenovo P50, with 64Gb RAM, 1.5TB disk. It runs KDE Neon (so Ubuntu 18.04 LTS under the hood). But I have the same problem on LMDE 3, LMDE 4, since VB 5.1.22.

On all systems, the linux app cheese works properly and displays the video stream from the camera. 

Windows clients have 2 webcams, and I can attach both to a client. The first does not result in a recognised device, the second does, but the video stream shows a blue rectangle. 

The laptop runs intel video and NVidia (MX1000 I think). Makes no difference, same effect. Audio is currently working perfectly, no detectable lag. VM performance is overall good. Windows VM's run with 2 cpu's, 8192MB Ram, virtio NIC and Hyper-V interface. No other issues. 

Under Linux the camera shows as 
{{{
Listing available devices:
  video0   Integrated Camera: Integrated C
    Media controller device: /dev/media0
    Entity 1: Integrated Camera: Integrated C. Type: 65537, Revision: 0, Flags: 1, Group-id: 0, Pads: 1, Links: 0
      Device node
      Entity: 1, Pad 0, Flags: 1
  video1   Integrated Camera: Integrated C
    Media controller device /dev/media1 doesn't exist
ERROR: Unable to list device entities: Invalid device or device cannot be opened. (Code: 5)
}}}

Cheese sees only 1 device. VB sees 2. 

VBManage list usbhost yields this for the camera
{{{
UUID:               ffc18e87-da01-4b0b-a446-71749f1d68e2
VendorId:           0x04f2 (04F2)
ProductId:          0xb52c (B52C)
Revision:           0.41 (0041)
Port:               7
USB version/speed:  2/High
Manufacturer:       Chicony Electronics Co.,Ltd.
Product:            Integrated Camera
SerialNumber:       0001
Address:            sysfs:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-8//device:/dev/vboxusb/001/003
Current State:      Busy
}}}

VBoxManage list webcams gives me:
{{{
Video Input Devices: 2
.1 ""Integrated Camera: Integrated C""
/dev/video0
.2 ""Integrated Camera: Integrated C""
/dev/video1
}}}

Attaching 1 from the menu doesn't do anything. Attaching 2 does, a webcam is detected, but a blue screen image is all I see.

An external USB webcam works perfectly. I am assuming it is related to the double entry, the client device detection seems to trigger on /dev/video1, rather than /dev/video0. The host seems to be indicating that /dev/video1 is not the one to use. 
"	ChrisMW
16843	WDDM driver does not validate custom video resolutions, causing graphics freeze on boot	Windows	VirtualBox 5.1.22	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
19841	WarpDrive doesn't work on VirtualBox 6.x anymore	Windows	VirtualBox 6.1.10	2020-08-28T20:57:13Z	2020-08-28T20:57:13Z	2020-08-28T20:57:13Z	"So in VirtualBox 5.x warp drive was working fine. When you make:

{{{
VBoxManage setextradata VM-name ""VBoxInternal/TM/WarpDrivePercentage"" 200
}}}

the time inside VM was going faster. But in VirtualBox 6.x it  doesn't work at all...

This happens because of this change:

{{{
    rc = CFGMR3QueryU32(pCfgHandle, ""TimerMillies"", &u32Millies);
    if (rc == VERR_CFGM_VALUE_NOT_FOUND)
        u32Millies = VM_IS_HM_ENABLED(pVM) ? 1000 : 10;
}}}

In 5.x default value of TimerMillies was 10 ms always (not 1 sec). But it is not the root of the problem.
The root lies near semaphore timeout calculation which trigger return from HLT. When WarpDrive is enabled this semaphore timeout calculated in wrong way."	gim
19533	wacom clicks not registered in virtualbox manager window	Linux	VirtualBox 6.1.6	2020-04-26T12:20:22Z	2020-05-07T16:12:20Z	2020-05-07T16:12:20Z	"Tested with virtualbox 6.1.6 on Ubuntu 20.04 and separately, by a different person, with virtualbox 6.0.14 on Ubuntu 19.10.

Both of us are unable to click within the virtualbox manager window, like create a new VM or import or export or access preferences, using wacom tablet (in my case Wacom Intuos Pen Tablet). 

For me up to a few days ago, when I was still running virtualbox 5.2.40 on Ubuntu 19.04 (and before on Ubuntu 18.04), this was not a problem. Upgrading to Ubuntu 20.04 means that python2 is no longer supported (which makes total sense) but now it looks like virtualbox manager has become unusable because it does not seem to register the mouse clicks. 

To clarify, when I hover over items in the virtualbox manager window the buttons seem to respond to the hovering, but when I click nothing happens. Clicking in any other program so far has not resulted into issues like this. Also interestingly I discovered today that when I import (using a regular mouse temporarily plugged in) several VMs that I am able to change the order of the VMs in the virtualbox manager window (sort/group them) but again not able to click them.

This may be similar or related to: https://www.virtualbox.org/ticket/11939
If so, this may be a regression bug.

And I also posted it here without reply so far:
https://forums.virtualbox.org/viewtopic.php?f=7&t=97881"	Jackg
19288	W2003 32 bit in VM stops responding in 6.0.16	Windows	VirtualBox 6.0.16	2020-02-05T14:50:20Z	2020-02-07T06:46:36Z	2020-02-07T06:46:36Z	"In the latest upgrade of VirtualBox 6.0 for Ubuntu my W2003 client stops responding after a while. I need to do a hard reset to get it back again. After hard reset it just runs again, mostly for a few hours.

This client has been running for even years I think without any problems. I downgraded to VirtualBox 6.0.14 and that seems to solve the issue."	NickGuus
19071	W10 Guest crash when watching youtube videos	Windows		2019-11-07T22:20:07Z	2019-12-05T09:40:51Z	2019-12-05T09:40:51Z	"Hi,

When I found 6.0.14 crashing, I tested with the latest nightly[1] and Extension[1.5].

My Host O/S is openSUSE Tumbleweed.  I am up to date[2].

The Guest O/S is an up to date W10 VM.

While watching a youtube video (any will do), the VM crashes.

The following errors are logged.  First, in /var/log/messages:

{{{
Nov  7 17:05:08 fuzzy kernel: EMT-1[28979]: segfault at 7fe0ee42d920 ip 00007fe21dd295ff sp 00007fe1ee42d898 error 4 in libc-2.30.so[7fe21dca6000+14d000]
Nov  7 17:05:08 fuzzy kernel: Code: a4 c3 80 fa 08 73 12 80 fa 04 73 1e 80 fa 01 77 26 72 05 0f b6 0e 88 0f c3 48 8b 4c 16 f8 48 8b 36 48 89 4c 17 f8 48 89 37 c3 <8b> 4c 16 fc 8b 36 89 4c 17 fc 89 37 c3 0f b7 4c 16 fe 0f b7 36 66
}}}

after, in VBoxSVC.log:

{{{
00:07:50.279667 main     Saving settings file ""/home/xyz/.VirtualBox/load_test/load_test.vbox"" with version ""1.15-linux""
00:07:50.742201 Watcher  Reaper: Pid 28941 (710d) was signalled: 11 (0xb)
00:07:55.284290 main     VirtualBox: object deletion starts
00:07:55.284327 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={ad47ad09-787b-44ab-b343-a082a3f2dfb1} aComponent={MediumWrap} aText={Medium '/home/xyz/.VirtualBox/w10/w10.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:07:55.284451 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={ad47ad09-787b-44ab-b343-a082a3f2dfb1} aComponent={MediumWrap} aText={Medium '/home/xyz/.VirtualBox/r-mobile/r-mobile.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:07:55.284533 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={ad47ad09-787b-44ab-b343-a082a3f2dfb1} aComponent={MediumWrap} aText={Medium '/home/xyz/.VirtualBox/load_test/load_test.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:07:55.743302 Watcher  ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={d0a0163f-e254-4e5b-a1f2-011cf991c38d} aComponent={VirtualBoxWrap} aText={The object is not ready}, preserve=false aResultDetail=0
00:08:00.315967 main     {00007ff38001ba80} HostPowerServiceLinux::~HostPowerServiceLinux: RTThreadWait() for 5000 ms failed with VERR_TIMEOUT
00:08:00.317272 main     VirtualBox: object deleted
}}}

Nothing is placed in VBox.log

Please let me know what other data is needed.  I am sure you need more.  ;)

'''References'''
1 - VirtualBox-6.0.15-134477-Linux_amd64.run
1.5 - Oracle_VM_VirtualBox_Extension_Pack-6.0.15-134477.vbox-extpack
2 - Tumbleweed version 20191104"	Pablo Sanchez
15653	VRDP not working after upgrading to 5.1	other	VirtualBox 5.1.0	2016-07-21T07:23:59Z	2016-12-20T18:37:34Z	2016-12-20T18:37:34Z	Host: Debian 8 (and Ubuntu 16.04). Updated from 5.0.26 to 5.1. Extension Pask updated. Firewall is not set, the ports are opened. Tested on the local (127.0.0.1) and remote connection.	Mik Foxi
17132	VRDP crashing guest machine	Windows	VirtualBox 5.1.28	2017-10-03T10:41:15Z	2017-10-03T14:07:02Z	2017-10-03T14:07:02Z	"Hello,

Have some problems with Win7/64 machines on Linux/64 host. There are several VM on one host with VRDP activated. Only 4-6 are running in parallel. The problem is a VM crashing when trying to use VRDP. Sometimes it happens with a first try, sometimes on one of the next. When crashed, VM does not give any messages in own log file, any clue in VBoxSVC.log, the only one is in /var/log/messages/kern.log

Oct  3 12:18:49 s07 kernel: [49758.816603] VRDP-IN[32682]: segfault at 0 ip           (null) sp 00007f83e6bfcb30 error 14 in VBoxHeadless[400000+25000]

When possible I'll try to catch core dump - it is productive machine, I'll be able to do so in the evening."	vinyl
15002	VRDP audio forwarding broken on Windows 10 RDP client	Windows	VirtualBox 5.0.12	2016-01-02T09:58:08Z	2016-04-10T23:40:52Z	2016-04-10T23:40:52Z	"Hey,

My host is a NAS-like CentOS 6 box with no attached monitor, no X server and no sound card. On it I spawn a bunch of lightweight bridged Windows machines for browser testing and connect to them from my desktop PC running Windows (gigabit LAN between the client and server).

This setup worked flawlessly with Virtualbox 4.3 and Windows 8.1. I've stopped using the VMs for a while and recently ressurected them with the following changes:

* Updated to Virtualbox 5
* Switched desktop to Windows 10

Since I did that, I'm getting choppy high pitched audio when connecting to the VMs (both before and after installing guest additions). The emulated chipset is Intel HDA and the driver is obviously Null as the host doesn't have a sound card. I originally thought this was an emulation issue, however:

* after doing some research about other issues about windows 10 clients being unable to connect in previous versions
* and reading on some other oracle website that VRDP only supports 22050 audio (not explicitly related to vbox, but pretty sure the V stands for the same thing),

I believe the issue is strictly related to the changes in the Windows 10 RDP client because:

1. playing back a realtime 22050hz stream on a 44100 output device would explain both symptoms (high pitch caused by the freq mismatch and choppiness caused by buffer underrun)
2. setting up a windows RDP server on a guest (tested on a win10 guest) and connecting to that works flawlessly

Unfortunately, I don't have a Windows 7 box to test this on, but I'm going to try some RDP-ception later today.
"	Radu Dan
20225	Voice synthesis software rhvoice doesn't work in VirtualBox	other	VirtualBox 6.1.18	2021-02-25T05:55:20Z	2021-02-25T05:55:20Z	2021-02-25T05:55:20Z	"I'm building voice synthesis web site, and using virtual box for my dev environment.

Also I'm using opensource voice synthesis software (RHvoices), it works fine in CLI mode, but when I try to make conversion via http interface virtual box sometimes generates error unable to handle page fault

I see http request

https://voxworker.com 127.0.0.1 - - [25/Feb/2021:12:18:58 +0600] ""POST /ru/ajax/convert HTTP/1.0"" 200 255 ""https://voxworker.com/ru"" ""Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.190 Safari/537.36""

Then I call Rhvoice software, and then I see Virtualbox error 

 1421.672335] BUG: unable to handle page fault for address: 00007efdf3ddc000
2	[ 1421.672340] #PF: supervisor read access in kernel mode
3	[ 1421.672341] #PF: error_code(0x0001) - permissions violation
4	[ 1421.672343] PGD 2a4afd067 P4D 2a4afd067 PUD 1fc9f2067 PMD 2aceb5067 PTE 80000002dbddc067
5	[ 1421.672346] Oops: 0001 [#1] SMP NOPTI

"	AlexBallov
9038	VNC Screen Repaint Delay	Linux	VirtualBox 4.0.8	2011-06-07T00:28:00Z	2011-06-07T00:28:00Z	2011-06-07T00:28:00Z	"If I reconnect to a system that has been online for a few hours, the screen is usually completely black. Clicking around on the screen slowly causes it to invalidate regions and cause paint updates. The host and guest systems are recent releases of ubuntu. This behavior occurs regardless of the VNC client used. It was not a problem in 3.2.12. The guest system has Guest additions 4.0.8 installed, but I have seen this behavior occur with guest additions 3.2.10 even on a 4.0.8 system.

This is NOT a screen saver - that is completed removed from the system and isn't even running as a process. Xorg doesn't report any issues on the guest. I have diff'd the FramebufferVNC code between 4.0.8 and 3.2.12 and there isn't any significant difference to explain this behavior. 

Also, the display is configured to never go to sleep in ubuntu."	kihjin
18300	VNC connect callback problem	other	VirtualBox 6.0.0	2019-01-11T09:14:53Z	2019-01-11T09:18:35Z	2019-01-11T09:18:35Z	"Hello.

This is code fragment of new vnc connect.
VirtualBox-6.0.0\src\VBox\ExtPacks\VNC\VBoxVNC.cpp:
{{{
enum rfbNewClientAction VNCServerImpl::rfbNewClientEvent(rfbClientPtr cl)
{
    VNCServerImpl *instance = static_cast<VNCServerImpl *>(cl->screen->screenData);

    /// @todo we need auth user here

    instance->mCallbacks->VRDECallbackClientConnect(instance->mCallback, (int)cl->sock);
    instance->uClients++;

    cl->clientGoneHook = clientGoneHook;
    return RFB_CLIENT_ACCEPT;
}
}}}

We can see that numbers of clients (part of IVRDEServerInfo) increase. Why dont call VRDECallbackProperty to fire VRDEServerInfoChangedEvent? I need to callback vnc connect situation by pyvbox:VBoxEventType.on_vrde_server_info_changed, but i cant, because IVRDEServerInfoChangedEvent not triggered.
"	Karlo Dipetrio
20552	VMSVGA extremely laggy keyboard input for Linux guests	Linux	VirtualBox 6.1.26	2021-09-16T11:20:30Z	2021-09-24T06:53:29Z	2021-09-24T06:53:29Z	"Pretty much all Linux guests with this video adapter have an extremely laggy and random keyboard input: while you're typing in any graphical terminal sometimes what you're typing instantly shows on the screen, sometimes there's a random delay for up to three seconds.

It's annoying and maddening.

Host OS: Fedora 33, Linux 5.14.3[[BR]]
Environment: XFCE with '''no''' compositing[[BR]]
CPU: Ryzen 7 5800X[[BR]]
Guest OS: any modern Linux OS without 3D acceleration

Changing the amount of video memory from default 16MB to 128MB makes the issue less pronounced but it's still there.

VBoxSVGA is more or less free from this issue. Keyboard input is not perfect (there's quite a considerable input lag) but at least it's not as bad as with VMSVGA."	Artem S. Tashkinov
19340	VMSVGA does not allow to resize guest display in GNU/Linux	Linux	VirtualBox 6.1.4	2020-02-23T17:52:24Z	2021-11-16T18:20:47Z	2021-11-16T18:20:47Z	"In this case the host and guest are same OS: 64-bit Linux Mint 19.3 MATE.

This error has been since VMSVGA came out and it seems that this is still not fixed. So it is not just VirtualBox 6.1.4 issue but much older one and exist in many former VirtualBox versions.

Graphics controller in VirtualBox machine settings
* in case of GNU/Linux by default VMSVGA 
* in case of MS Windows by default VBoxSVGA

'''The truth is that VMSVGA does not allow to resize guest display in GNU/Linux.''' I have to adjust display settings manually in Linux in order to resize display.
When using VBoxSVGA then guest resizing works in GNU/Linux but ''Invalid settings detected'' message is shown in virtual machine (VM) settings that suggest to use VMSVGA unless I have reason to not use. Well - currently I have reason as VMSVGA does not work properly.

Also in case of VBoxSVGA the resizing clutter appears - I need to maximize VM window and back in order to get guest display resizing work properly. This has to be done after every time I wake up my laptop from sleep or start the VM first time.

At the same time in case of MS Windows the VBoxSVGA is chosen by default which works also in case of MS Windows. Actually when to choose VMSVGA in case of MS Windows then you cannot start VM as it is considered invalid setting. Well - no need as VBoxSVGA works.

My proposal: either get VMSVGA to work properly in case of any supported guest OS or remove it permanently from VirtualBox."	Edmund Laugasson
15043	VMSetError for ACPI tables < 64k	other	VirtualBox 5.0.12	2016-01-19T14:12:57Z	2022-05-18T19:05:44Z	2022-05-18T19:05:44Z	"Hello,

I am trying to use a custom ACPI table with my VM without success. VirtualBox fails to start the VM (rc=VERR_TOO_MUCH_DATA) stating my ACPI table is too large.

The size of the DSDT I'm using is 59552 bytes. According to VirtualBox, the maximum size is 64k (65536 bytes). The log file is attached, see line 568.

This seems to be a bug where the size of GCPhysCur is (somehow) greater than 0x10000. See line 2744 of DevACPI.cpp.

*** To reproduce ***
1. Create a VM

2. Check the size of your DSDT
{{{
ls -l /sys/firmware/acpi/tables/ | grep DSDT
}}}

2. If less than 64k, go ahead and make a copy in your VM folder
{{{
sudo cp /sys/firmware/acpi/tables/DSDT /home/josh/VirtualBox\ VMs/win7x64sb1/DSDT
}}}

3. Change ownership and group of DSDT file
{{{
sudo chown josh:josh /home/josh/VirtualBox\ VMs/win7x64sb1/DSDT
}}}

4. Set extra data using VBoxManage
{{{
VBoxManage setextradata win7x64sb1 VBoxInternal/Devices/acpi/0/Config/CustomTable /home/josh/VirtualBox\ VMs/win7x64sb1/DSDT
}}}

5. Start the VM. You should see the error."	vbox_manage
19786	VMs won't run after testbuild 6.1.13-139554: driver version mismatch kernel 5.7.12	Windows	VirtualBox 6.1.10	2020-08-02T21:13:49Z	2020-08-02T21:13:49Z	2020-08-02T21:13:49Z	"All  builds from VB 6.1.12 through  test builds until 139554 work fine.  After 139554 VB test builds compile but VMs crash on startup with a kernel module message, give SVC log errors (no errs in the vmlogs).

Both 139683 and 139683 give the same errors.


VBoxSVC.log

00:00:05.638966 nspr-4   Support driver version mismatch: DriverVersion=0x2d0001 ClientVersion=0x2e0000 rc=VERR_VERSION_MISMATCH
00:00:06.113750 Watcher  ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={85632c68-b5bb-4316-a900-5eb28d3413df} aComponent={MachineWrap} aText={The virtual machine 'win7dpg' has terminated unexpectedly during startup with exit code 1 (0x1)}, preserve=false aResultDetail=0


I've tried removing and reinstalling the host modules,  building the VirtualBox...run, unloading and reloading the modules to no avail.

Not a big deal for me, but maybe important for developers to know (if not, my apologies).

Host: manjaro Linux updated daily, kernel 5.7.12 linux57-virtualbox-host-modules 6.1.12-4"	matthewls
18822	VMs with name lengths greater than 64 characters abort on start when using Pulseaudio. Have root cause and fix option <Regression>	all	VirtualBox 5.2.26	2019-08-08T15:35:59Z	2019-08-08T15:35:59Z	2019-08-08T15:35:59Z	"If a VM has a name length greater than 64 characters, and is using Pulseaudio, it will abort on startup with ""VERR_CFGM_NOT_ENOUGH_SPACE"" being thrown.

The root cause is:
Inside ""src/VBox/Devices/Audio/DrvHostPulseAudio.cpp"", in ""struct DRVHOSTPULSEAUDIO"", there is ""char                  szStreamName[64];"".

This ""szStreamName"" only appears to be used by Pulseaudio for display purposes, such as when running ""pavucontrol"". The comments above ""szStreamName"" read:
     * The stream (base) name; needed for distinguishing
     *  streams in the PulseAudio mixer controls if multiple
     *  VMs are running at the same time. */

So, when ""int rc2 = CFGMR3QueryString(pCfg, ""StreamName"", pThis->szStreamName, sizeof(pThis->szStreamName));"" is called inside of the ""drvHostPulseAudioConstruct"" function in that file, ""CFGMR3QueryString"" throws the above error, as String.cb is greater than 64 characters.

I have a local patch which is a hacky solution and not good enough for you guys -- it checks if ""StreamName"" is passed in in each call to ""CFGMR3QueryString"", and then does the following if it is too long -- but I got it to work just fine by ellpisizing (""..."") at the middle of the string like so, creating a 64 character string like Pulseaudio requires, which shows up correctly in ""pavcontrol"":
     * First 30 chracters of the VM name
     * 3 chracters for ""...""
     * Last 30 chracters of the VM name
     * 1 byte for '\0'
This is 64 characters total. In my patch, I simply change the contents of String.psz and String.cb, which is probably not the correct way to do it.

I would strongly suggest ellipsizing in the middle like this, since the first 64 characters of multiple VM clones could easily be the same, usually the last few characters/words are what is different when there are many clones/different versions of a VM running.
Another option could be the number them, but ellipsizing is probably better for the user.

This limitation did not exist when using Ubuntu 18.04/16.04, so I have marked it as a regression. I looked at the latest 6.0 source code, and it looks like this bug will still be present there.

I have many VMs with long and descriptive names past 64 characters, and I know others do too, that is a very useful feature to tell them apart at a glance (especially when using many clones, where checking each description is not realistic).
Please fix this for us users who let our VM names get out of control! It really helps workflow to be able to use such long names.

Reproducible: Always"	J_F
17711	VMs no longer start from saved state	Windows	VirtualBox 5.2.10	2018-04-25T11:23:17Z	2018-04-26T08:03:43Z	2018-04-26T08:03:43Z	"Since I've upgraded to 5.2.10r122088 (Ubuntu 16 LTS, Kernel: 4.4.0-121-generic), I'm no longer able to start my VMs from saved state:

{{{
Waiting for VM ""VM_W10"" to power on...
VBoxManage: error: The VM session was aborted
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component SessionMachine, interface ISession
}}}

The vbox log (attached) doesn't say much.
This happens on all ~150 vms across all 10 vbox hosts I have."	LennyHers
17598	VMs do not adapt to hi-res screen	Windows	VirtualBox 5.2.8	2018-03-06T23:31:27Z	2018-03-06T23:31:27Z	2018-03-06T23:31:27Z	"I have installed VirtualBox 5.2.8 on a Lenovo X1 Carbon 5th generation, which is running KUbuntu 17.10.1, which has a max screen resolution of 2560x1440.

Guest operating systems will not adapt to the resolution of the laptop screen (neither in terms of proportions, nor size). Guest additions are correctly installed.

All attempts to condition the behaviour of the VMs fail, and the desktop of the VMs appears small and surrounded by a black margin to the right and below.

I have (obviously) tried the File-Environment-Display settings, auto resize guest, VBoxManage setextradata, etc. but none of these works.

It is possible to increase the resolution a little, but this setting does not persist, and is never in line with the actual resolution. In the Win10 machine, the pointer is also misaligned, making it impossible to use.

Same behaviour with a previous installation, version 5.1.22 on KUbuntu 17.04.
"	JonPr
19197	vmdk not visible after shutdown	Linux	VirtualBox 5.2.34	2020-01-04T10:15:11Z	2020-01-04T14:29:46Z	2020-01-04T14:29:46Z	"Hi,

I have come acros a problem.
I downloaded mininet-vm from [1].
I opened virtualbox
I selected file
I selected import appliance
The vm booted
I shut down the vm
I closed virtualbox
I opened virtualbox again
I clicked on the ""Mininet-VM"" virtual machine
the prompt with initramfs appeared.
I closed the virtual machine by pressing x from the window
I right clicked the virtual machine
I selected properties
I went to storage
I reselected the vmdk for the VM which came with the mininet-vm from mininet download folder
it worked.

Thanks"	cric
20359	VM Windows 7 terminated	Windows	VirtualBox 6.1.22	2021-05-11T19:17:39Z	2021-05-12T12:58:41Z	2021-05-12T12:58:41Z	"My Windows 7 VM terminated on my Ubuntu 20.04 LTS host.

I attached the log file."	anno
19630	VM window size not restored after save-state (Ubuntu 20.04, VB 6.1.8)	Windows	VirtualBox 6.1.8	2020-05-30T03:00:52Z	2022-11-21T08:42:46Z	2022-11-21T08:42:46Z	"If the ""x"" close button on a VM is pressed, and ""Save state"" is selected, then when the VM is started up later, the desktop is much smaller (looks like a default small size -- possibly the same as the size of the startup splash window?)

VB Version 6.1.8 r137981 (Qt5.12.8)

Host: Ubuntu 20.04, X11 with gnome-shell 3.36.2, Intel built-in graphics (in i7-8700K cpu)

Guest: Windows 10 64-bit with latest GAs installed

FWIW, these are the same symptoms reported in [https://www.virtualbox.org/ticket/16593] ; that bug says it was fixed in 5.1.22

I'll attach before & after screen shots and VBox.log files.

STEPS TO REPRODUCE:
1.  Boot Win-10 VM, expand the VM window to a large size.
2.  Click the ""X"" window-manager icon to close the VM window
3.  Check ""Save state"", click OK
(VBox.log.1 was from the above)
4. In VB gui, click ""Start"" to restore the VM

Initially an image of the large VM window appears with the ""restoring..."" progress meter.
   
Then the VM window shrinks to a small size


(VBox.log is from step 4.)

"	Jim Avera
14222	VM window should not be brought to front when it becomes active in full-screen mode	Windows	VirtualBox 4.3.28	2015-06-25T19:43:32Z	2015-06-25T19:43:32Z	2015-06-25T19:43:32Z	"Using VirtualBox 4.3.28 on Lubuntu 14.10 x86-64 host.

I have the window manager (Openbox) configured so the window under the mouse pointer is automatically activated, but not brought to the front, when the pointer moves over it. (Clicking in a window does bring it to the front.)

That works fine with a VirtualBox VM which isn't in full-screen mode. However when a VM is in full-screen mode, the VM window is brought to the front as soon as it becomes active, even though it has not been clicked in.

That's quite annoying if I have Alt-Tabbed out of the VM and am using other programs, with the VM window appearing behind the other program windows. As I move the mouse pointer from one other program window to another, as it passes over part of the VM window, the VM window is brought to the front, obscuring the other program windows.

I think a better behaviour would be to only bring the VM window to the front when the user clicks in it."	Donuts
19593	VM window movement broken with Linux-Mate distros and Auto capture keyboard enabled	Windows	VirtualBox 6.1.8	2020-05-17T01:40:33Z	2020-07-02T19:59:57Z	2020-07-02T19:59:57Z	"Issue: The guest window doesn't resize and doesn't move. It is embedded in the upper left corner of the desktop. This problem was also found in version 6.1.6 (ticket 19496) and was not fix in version 6.1.8

Data:
ubuntu 20.04 LTS
Virtualbox Versión 6.1.8 r137981 (Qt5.12.8)
VirtualBox_Extension_Pack-6.1.8
Tested in Desktop Mate
kernel 5.4.0-29-generic
OpenGL version string: 4.6 
Mesa 20.2.0-devel"	maravento
16660	VM window freezes and process keeps running after manual savestate	Linux	VirtualBox 5.1.18	2017-04-17T11:47:58Z	2017-06-19T17:19:42Z	2017-06-19T17:19:42Z	"There are several vms on this host, usually running in full screen mode. One vm has been experiencing this issue where the full screen vm window freezes, usually after the vm has been running for one or more days. I haven't noticed that issue with other vms, however, most other vms don't run for weeks.

When it happens, the vm window is not updated anymore. It doesn't show the vm anymore. Instead, it shows whatever was there on the screen earlier. If there was another window above the frozen window and that other window is closed, it's still shown in the frozen vm window. If I switch workspaces back and forth, when I switch back to the workspace with the frozen vm window, the vm window (which is in full screen mode) shows the previous workspace.
For that reason, a screenshot wouldn't be helpful, as it would simply show whatever else was on the screen before the frozen vm window was activated.

This affects the vm window, i.e., the window that shows up when you start a vm in the VirtualBox gui. The affected vm itself is still running and can be accessed via ssh.

It is possible to suspend the vm using ""vboxmanage controlvm [NAME] savestate"", but the frozen vm window won't go away. It visually looks as if nothing had changed.
The vm process keeps running after the vm is suspended:
{{{
user     985 27147 64 00:02 ?        08:10:26 /usr/lib/virtualbox/VirtualBox --comment Fedora-1 --startvm 5c908c7b-bf32-4965-be4d-a11f5abdbf04 --no-startvm-errormsgbox
user    7016     1  0 Apr04 ?        00:38:56 /usr/lib/virtualbox/VBoxXPCOMIPCD
user   27123     1  0 Apr10 ?        00:22:27 /usr/lib/virtualbox/VirtualBox
user   27147     1  0 Apr10 ?        00:47:51 /usr/lib/virtualbox/VBoxSVC --auto-shutdown
}}}

If this process (985 in this example) is killed, the frozen window disappears and VirtualBox marks the vm as ""Aborted"". The saved state is lost.
I usually reset the vm to its last healthy state and start it again, which works fine every time. Until the vm window freezes again a few days later.

It's not clear what causes these freezes. I understand that this makes it very difficult to debug this, but I'm hoping this bug report helps someone else out there who is experiencing the same behavior.

Looking at the log (attached), it seems like two log entries are missing. These entries can be found at the end of the log files of other vms that were also suspended (without freeze):
{{{
12:07:58.276482 GUI: UIMediumEnumerator: Medium-enumeration finished!
12:07:58.551772 GUI: Passing request to close Runtime UI from machine-logic to UI session.
}}}




"	Philip Seeger
20785	VM will not start, Guru Meditation -79 (VERR_INVALID_STATE)	other	VirtualBox 6.1.22	2022-01-20T21:10:17Z	2022-01-21T20:55:33Z	2022-01-21T20:55:33Z	"Virtual machines will not start any more.
Both Windows and Ubuntu guests seem to be having the same project.
I am using VirtualBox 6.1.22_Ubuntu r144080 and I am running Ubuntu 20.04
Linux 5.13.0-27-lowlatency #29~20.04.1-Ubuntu SMP PREEMPT

Yesterday everything works fine and now machines wont start.
When exporting and importing a machine to a different host, the machine does start so it seems the issue is related to the virtual box host.

In the logfile I see:

00:00:04.713444 Display::handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0 flags=0x0
00:00:04.713532 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=720x400, Sending to async-handler
00:00:04.713611 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=720x400
00:00:04.713634 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=720x400
00:00:04.713659 GUI: UIFrameBufferPrivate::performResize: Size=720x400, Directly using source bitmap content
00:00:10.049433 PIT: mode=3 count=0x4dae (19886) - 60.00 Hz (ch=0)
00:00:10.069842 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'
00:00:10.069860 Console: Machine state changed to 'GuruMeditation'
00:00:10.070003 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:00:10.070003 !!
00:00:10.070004 !!         VCPU0: Guru Meditation -1701 (VERR_MM_HYPER_NO_MEMORY)
00:00:10.070037 !!
00:00:10.070063 !!
00:00:10.070063 !! {mappings, <NULL>}
00:00:10.070064 !!


I will attach the logfile to this ticket.

Any help is highly appreciated"	DeHouthakker
15691	VM stuck when restoring the session	Windows	VirtualBox 5.1.2	2016-07-26T08:56:18Z	2017-03-01T10:07:18Z	2017-03-01T10:07:18Z	A session that was restored has stuck the entire VM.	Panos Kavalagios
15513	VM stuck when attempting to open a Microsoft Office file from network	Windows	VirtualBox 5.0.22	2016-06-17T13:14:17Z	2017-09-15T08:50:52Z	2017-09-15T08:50:52Z	"When you try to open a document from a network share the entire VM is stuck. The log report:

00:12:18.795744 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago"	Panos Kavalagios
19074	"VM Stuck in ""offline snapshotting"" state"	Linux	VirtualBox 6.0.10	2019-11-08T19:05:39Z	2019-12-03T19:22:03Z	2019-12-03T19:22:03Z	"The active problem is that a VM is stuck in ""offline snapshotting"" state and I can't do anything with it.  I need a way to get it out of that state, hopefully without corrupting the VM along the way.

There is no relevant VM-specific log information.  Since it's an offline snapshot, the VM wasn't running at the time, so the most recent log ends with ""Machine state changed to 'PoweredOff'"".

There appears to be no relevant info in the ~/.config/VirtualBox log files either.  Just a bunch of messages about saving config files and the reaper running.

Here's how I got to where I am:
I'm working on a Perl+Curses TUI front-end for a headless !VirtualBox server. It uses the vboxwebsrv webservice via the `SOAP::Lite` package to interact with !VirtualBox. I am following the API documented in the latest SDK from Oracle (6.0.10).

When my scripts initiate a snapshot of a powered-off machine via `IMachine::takeSnapshot`, the VM then becomes stuck in ""offline snapshotting"" state (""stuck"" as in it's been in that state for over 2 months as of the time of this writing). This is what the script does:

1. Get an `ISession` object via `IWebSessionManager::getSessionObject`
2. Lock the session in Shared mode via `IMachine::lockMachine`
3. Get a mutable `IMachine` object with `ISession::getMachine`
4. Initiate the snapshot from the mutable `IMachine` object, getting an `IProgress` object, with `IMachine::takeSnapshot`
5. Start a modal window which periodically queries the `IProgress` interface for its status until `IProgress::complete` returns `true`

As I'm reviewing my code to write this, I note that it's possible that `ISession::unlockMachine` is being called before the `IProgres`s object reports success. Although the documentation implies that a session remains locked as long as it is busy even after a call to `ISession::unlockMachine`, I wonder if this may be causing !VirtualBox to do something bad resulting in the stuck ""offline snapshotting"" state.

Environment info:
* Host OS is Debian Buster 64-bit.
* Guest OS is Windows 7 Ultimate 32-bit.
* VBoxHeadless --version gives 6.0.10r132072.
VBox.log does not get anything written to it.
I'm happy to do whatever data collection is necessary to troubleshoot this; just let me know what I need to do."	Brian of the Pines
17389	VM starts, but UI stuck at creating process	other	VirtualBox 5.2.4	2017-12-21T21:53:09Z	2017-12-22T15:33:54Z	2017-12-22T15:33:54Z	"The selected VMs are started successfully, but the UI still displays the window about VBox starting a process for it.
If the VM is terminated, an error is displayed.
The result code is
{{{
Result Code: 
NS_ERROR_FAILURE (0x80004005)
}}}"	Thermi
19226	VM segfaults on copy with shared clipboard	Linux	VirtualBox 6.1.2	2020-01-15T10:30:50Z	2022-01-31T10:33:36Z	2022-01-31T10:33:36Z	"When using the shared clipboard, all running VMs in certain states crash whenever some input it copied on the host.

Steps to reproduce:
1. Start VM and login
2. Open libreoffice calc on host
3. Select and copy some cells
   => VM crashes

No messages are in the VBox log of the VM, but there are some in the journal of the host.
{{{
ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=2 pid=1559 comm=""ShClipboard"" exe=""/usr/lib/virtualbox/VirtualBoxVM"" sig=11 res=1
ShClipboard[1599]: segfault at 4 ip 00007fe97c14a1ae sp 00007fe95c199cf0 error 4 in VBoxSharedClipboard.so[7fe97c143000+8000]
Code: 89 c4 85 c0 78 50 48 8d 4d c0 ba 30 75 00 00 44 89 f6 4c 89 ff 67 e8 b1 c9 ff ff 41 89 c4 85 c0 78 34 48 8b 45 c0 48 8b 7b 08 <8b> 50 04 39 53 04 0f 46 53 04 48 8b 70 08 89 d2 ff 15 84 5c 00 00
audit: type=1701 audit(1579083656.742:64): auid=1000 uid=1000 gid=1000 ses=2 pid=1559 comm=""ShClipboard"" exe=""/usr/lib/virtualbox/VirtualBoxVM"" sig=11 res=1
}}}

The issue also occurs when copying from the guest, but I currently don't have a reproducer for that. Journal message on host:
{{{
SHCLX11[3662]: segfault at 8 ip 00007efc7073d3ea sp 00007efc71b6c8a0 error 4 in VBoxSharedClipboard.so[7efc70736000+8000]
}}}

Version used is 6.0.12, but the issue was also present in at least 6.1.0.
Host is running Arch Linux, guest is Kali Linux (haven't tested with other combinations)."	udine
16281	VM screen flickers during booting until I'm completely logged in on the win7 vm	Windows	VirtualBox 5.1.10	2016-12-12T10:01:17Z	2016-12-12T12:58:31Z	2016-12-12T12:58:31Z	"I'm running VirtualBox-5.1-5.1.10_112026_fedora25-1.x86_64 on Fedora 25 with win7 as guest. My problem: If booting the VM (full screen mode), the screen flickers rhythmically (about 1 Hz freqency)   until I'm completely logged in with my win 7 account.

Only a very few times the VM boots flawlessly.

This effect is new, no such effect on Fedora25 as host with my previous Vbox version
VirtualBox-5.1-5.1.8_111374_fedora24-1.x86_64. Going back to this version will help as workaround.

My current F25 kernel is 4.8.13-300.fc25.x86_64, but same problem with previous F25 kernels.

Anybody sees such effect too?

Any comments are welcome.

Kind regards

Joachim Backes"	backes
14204	VM screen flickers	Linux	VirtualBox 4.3.28	2015-06-16T20:29:22Z	2015-06-17T23:11:02Z	2015-06-17T23:11:02Z	"Virtual machine is constantly flickering and when I log in grey base coloured squares appear until I press in the higher left corner where dash is. But flickering is making working with VM impossible.

I am using Virtualbox 4.3.26. My host is Ubuntu 15.04 with custom NVIDIA driver (version 346.72) for Geforce GTX 960M. My guest is Ubuntu 14.04.02 LTS.

All details about this annoying regression are described and available here: https://forums.virtualbox.org/viewtopic.php?f=3&t=67823"	SamH
19295	"VM reset (""HeartbeatFlatlinedTimer"") under load"	Linux	VirtualBox 6.0.16	2020-02-07T04:23:25Z	2020-03-02T16:10:23Z	2020-03-02T16:10:23Z	"Since upgrading to 6.1.2, I'm seeing reboots during guest backup runs.

The guest is Linux 2.6.22.14-100 #1 SMP Wed Apr 8 18:07:54 EDT 2015 i686 i686 i386 GNU/Linux

Prior to the upgrade, this was never seen.

The backup is tar (some excludes) -czpf (NFS mountpoint) |tee (log) | grep -v (noise)

A full backup is about 75GB; the crashes generate between 3 and 40GB before the crash.

Log file attached.

The relevant log lines appear to be:

{{{
90:00:58.137957 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
90:01:56.653151 Reset initiated by keyboard controller
90:01:56.682588 Changing the VM state from 'RUNNING' to 'RESETTING'

}}}

Let me know if you need more info.

Is there a way to disable either the detection or the reset action until a fix is available?

I'd like to be able to complete a backup!

"	Timothe Litt
16450	VM locks up when setting --discard and --nonrotational and using fstrim	Linux	VirtualBox 5.1.14	2017-02-04T02:32:50Z	2020-03-21T16:49:41Z	2020-03-21T16:49:41Z	"I changed the settings of my Xubuntu VM to emulate an SSD:

{{{
VBoxManage storageattach Xubuntu --storagectl SATA --port 0 --discard on --nonrotational on
}}}

After that started the VM. Everything runs fine until running fstrim in the VM. First the VDI file is shrinked a bit, then VirtualBox starts continuously reading from host filesystem (I guess from the VDI file). After some time the VM guest OS reports storage problems (timeouts) in dmesg output. No access to emulated storage is possible after that, but VM continues to run (e.g. scrolling in windows, moving mouse, ...). See attached VM screenshots and VBox.log for details.

I already observed the same behavior with a Windows 10 VM which locked up in the same way, but then I did not record any logs or error information.

Problem seems to be similar to ticket #15509.

Host info: Kubuntu 16.10 64 Bit, VirtualBox 5.1.6 (installed from Kubuntu repository)

Guest info: Xubuntu 16.10 64 Bit, 1 SATA controller, 1 VDA file with dynamic size

Please tell if any more information is needed."	Motlib
16718	VM keeps keyboard when switching to host	Windows	VirtualBox 5.1.22	2017-05-02T11:19:26Z	2017-05-15T06:10:43Z	2017-05-15T06:10:43Z	I'm running a Windows 7 VM with guest addons installed in full screen mode on a Linux Mint Serena host. Mouse and keyboard integration are working well but whenever I minimize the VM to work on the host the keyboard keeps captured by the VM. I always have to click somewhere on the host screen to release the keyboard from the VM.	Mellon
15967	VM guest freezes	Windows	VirtualBox 5.1.6	2016-09-22T10:44:23Z	1970-01-01T00:00:00Z	1970-01-01T00:00:00Z	"I think it is the same as this one #15529

I'm Running Linux Mint 18, and Windows 10 (x64) in the virtual box.

The guest freezes, sometimes in the startup, sometimes after 3 hours, sometimes NOT...
"	Anders Dvinge
16445	VM gets stuck at online snapshotting	Linux	VirtualBox 5.1.12	2017-02-03T11:01:21Z	2017-02-03T11:01:21Z	2017-02-03T11:01:21Z	"In our backup script, we perform online snapshotting of headless VMs to ensure we get a consistent state with the following command:

{{{
vboxmanage snapshot $BCK_VM_UUID take
}}}

One of the VM got stuck in ""online snapshotting"" (as per vboxmanage) for 3h when we took action.

Host is latest update of Debian 8 (Jessie)[[BR]]
Guest is latest update of Ubuntu 16.04 LTS

Core dumps of the vboxheadless process and VBoxSVC are available on request (or via Klaus)."	Max D
13752	VM freezes after leaving Haiku operating system running for several hours	other	VirtualBox 4.3.18	2015-01-11T10:10:54Z	2015-08-31T07:30:40Z	2015-08-31T07:30:40Z	"This happens pretty regularly if I leave the VM running overnight.

I'm running the latest nightly builds of Haiku, if it matters (revision 48620 at the moment).

I'm attaching both the serial log output from the guest OS when the VM froze, and the VBox.log from the session that locked up.

The VM itself froze and did not offer me the option to power it off etc as usual."	jstressman
14505	VM desktop migrate to current desktop after wake up	Windows	VirtualBox 5.0.2	2015-08-27T07:36:17Z	2015-08-27T08:45:35Z	2015-08-27T08:45:35Z	"1. I have three virtual desktops (""workspaces"" in xfce terminology)
2. Usually I run VM's windows on ""VBOX"" desktop
3. When I switch to other ""workplace"" , hibernate computer an then wake it up, VM's desktop show at current workplace which is annoing "	Kamil Jońca
19988	VM crashes or restarts during package upgrade on FreeBSD guest	BSD	VirtualBox 6.1.16	2020-10-21T17:57:43Z	2021-03-26T21:01:07Z	2021-03-26T21:01:07Z	"Hi,

my host machine is Debian GNU/Linux 10.6 latest and up to date (21 Oct 2020). VirtualBox version is 6.1.16.

I have a FreeBSD guest - FreeBSD 12.1-RELEASE-p10 GENERIC.

When I try to upgrade packages on guest (FreeBSD) the virtual machine restarts or vanishes.

I could not reproduce the issue with previous versions of VirtualBox (6.1.x) or with Linux guest including VirtualBox 6.1.16.

There is a video.

https://www.youtube.com/watch?v=dqjWNC7nPX0

Kind regards
Georgi
"	Georgi
19321	VM crashes often on USB unplug/replug, also out of blue sky	Windows	VirtualBox 6.1.2	2020-02-19T13:14:15Z	2020-03-03T13:35:46Z	2020-03-03T13:35:46Z	"Hi,
this looks like a regression in 6.1.2 and 6.0.16 since I cannot duplicate with 6.0.14.
The VM simply disappears from the screen. Sometimes with no visible reason, but every few USB unplug/replug cycles. I found the USB part since I write some code that communicates to a USB device (CDC-ACM aka ComPort emulation). One of the actions does cause the device to reboot (on purpose).

Other times it sits in the background and when I want to open the VM window again, it is gone. Then sometimes it crashes immediately at start or shortly after. A host reboot brings it back to work (until it crashes randomly again).
Host and guest are running with latest updates.
H: Ubuntu 18.04, 5.3.0-40-generic
G: Win10-64, 19H2 (but also showed at 19h1)

I have not seen a crash with Linux guests, but do not use them often right now.

In the logs I did not find useful hints, I hope you do. Let me know when I can help with debugging.

There is a thread in the forum:
[https://forums.virtualbox.org/viewtopic.php?f=7&t=96829&p=470373#p470373]
"	ucrasher2
17361	VM Crash on Android USB (debug+tether) unplug	Linux	VirtualBox 5.2.0	2017-12-09T14:56:12Z	2017-12-26T09:35:51Z	2017-12-26T09:35:51Z	"Sometimes, when I unplug my Android device (LineageOS 7.1.2), the VM crashes.
VirtualBox 5.2.2 (it also crashed with VirtualBox 5.1.0).
Host and Guest are Ubuntu Server 17.10.
Host and Guest where rebooted only two days ago.
See crash dump attached.
When plugged, the Android device runs in USB Debug mode, with USB tethering enabled. The linux interface is set with ""allow-hotplug""."	flechaig
15669	VM crash during start (Intel Atom D525)	Windows	VirtualBox 5.1.2	2016-07-23T09:15:43Z	2017-07-18T18:36:36Z	2017-07-18T18:36:36Z	During start of Windows 2000 VM under Ubuntu 14.04 LTS crashes whereas it was working fine with 5.0.24.	PBT78
20762	VM crash after KVMS switch	Linux	VirtualBox 6.1.30	2022-01-07T02:17:10Z	2022-01-07T02:17:10Z	2022-01-07T02:17:10Z	"See [https://forums.virtualbox.org/viewtopic.php?f=7&t=104891&sid=51cd5f0216603e8bec8562fd1da4b3bc] for more information.

Environment:

I have multiple PCs connected by a keyboard-video-mouse-switch (KVMS, to clearly distinguish from kvm, the kernel virtualization subsystem).  The KVMS is a FJGear USB2.0 HDMI KVM model FJ-401HUA.  I will refer to these PCs as A, B, and C.  All 3 boxes are hosting Devuan Beowulf, and all VMs running on all boxes are running Devuan Beowulf Ascii, Beowulf, or Chimaera under virtualbox 6.1.30.  All hosts are running the latest virtualbox extensions, and guests are running the latest virtualbox guest additions.

Description of the Problem:

The problem is that switching between two of these boxes causes a VM running USB 3 to crash.  After an initial switch from A to B and back to A, one VM running USB 3 on A had crashed.  In one instance, switching a second time after this from A to B and back to A, all but one VM running USB 3 had crashed and even a VM running USB 2 had also crashed.  

Detail:

I run virtualbox on PCs A and B.   I use PC A for most of my regular activities; B and C are ""test"" boxes.  However, despite B being a testbox, I do have the VMs on B networked together with some of the VMs on A.  The 3 PCs are networked through an electronic ethernet switch.

The KVMS does work, although there is a bit of a wait for the video to re-sync after a switch.   The KVMS is capable up to 1920x1080, which matches my monitor's resolution.   Normally, I don't notice any peculiar behavior related to using the manual buttons on the face of the unit.  There are some messages logged after each switch, but they have never caused an issue until I changed the VM (the one that crashed) to USB 3.

I have attached the log for the crashed VM (see above link).  These logs were created by saving them from the log dialog box in the virtualbox GUI.  I have not modified them other than to obfuscate private information.  The logs are cut short for some reason, but it is NOT related to the obfuscation script.  I can save the logs again, from the GUI again, and the same results occur.   The line counts of the log files match before and after obfuscation.


"	Harry M
14375	VM apparently becomes inaccessible after shutdown	Windows	VirtualBox 5.0.0	2015-08-02T19:25:40Z	2015-08-02T19:25:40Z	2015-08-02T19:25:40Z	"Steps:[[BR]]

1) Start VM[[BR]]
2) Do some work[[BR]]
3) Shutdown[[BR]]
After that some VMs always show the state ""inaccessible"". It is possible to remove it. Later on it is not possible to add this VM due to an error:[[BR]]
VBoxManage registervm /u00/HDD/W764.2015/W764.2015.vbox
VBoxManage: error: Could not find an open hard disk with UUID {9d2e777b-dc39-40fc-b1b8-8661dd13bd84}[[BR]]
VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBoxWrap, interface IVirtualBox, callee nsISupports[[BR]]
VBoxManage: error: Context: ""OpenMachine(Bstr(a->argv[0]).raw(), machine.asOutParam())"" at line 85 of file VBoxManageMisc.cpp[[BR]]
[[BR]]

Workaround (not always working):[[BR]]
4) Use VBoxManage showhdinfo <virtualdisk vdi name>. (This command may produce no output, in this case registering VM is not possible.)[[BR]]
5) Add VM back if the previous command provided the information about vdi disk.[[BR]]
[[BR]]
After repeating steps 1-3 VM becomes inaccessible again.
"	zoman
19508	VM (not) terminated with exit code 0	all	VirtualBox 6.1.6	2020-04-17T17:42:15Z	2021-05-16T08:54:04Z	2021-05-16T08:54:04Z	"Host: Ubuntu 18.04 kernel 4.15.0-96-generic #97-Ubuntu SMP Wed Apr 1 03:25:46 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Guest: any, predominantly experienced the problem with Windows guests

The problem is not willingly reproducible, but occurs on average in 1 of 20 (estimated) VM startups.

Problem description:

The VM starts correctly without any problems. While it is up and running for a considerable but variable time (experienced between 1 minute and 3 hours), the VBox Manager pops up a child window for the VM: 'Creating process for virtual machine ""[machine name]"" (GUI/Qt) ... (1/2)' with progress bar stuck at 0%. See attachment.

The VM continues to be operable as if nothing happens.

If nothing is done about the popup window: The VM is killed at some point in time further on without any notice. VM status in VBox Manager is ""aborted"" then.

If the guest operating system is shutdown ordinarily, the VM is closed and a VirtualBox Error popup window is opened ""Failed to open a session for the virtual machine [machine name]."" with detail ""The virtual machine [machine name] has terminated unexpectedly during startup with exit code 0 (0x0)."" and ""Result Code: NS_ERROR_FAILURE (0x80004005)"" and ""Component: MachineWrap"" and ""Interface: Machine {[hex codes]}"". See attachment.

VM log shows no obscurities. See attachment.

I suspect that the error appeared with kernel 4.15.0-96 or maybe already with kernel 4.15.0-91.
The error was already present in VBox 6.1.4. I did not see it with 6.1.2 (I believe)."	sunrider
8769	VLAN tagged packets mangled on bridged adapter	other	VirtualBox 4.0.6	2011-04-22T22:05:14Z	2013-01-14T13:43:24Z	2013-01-14T13:43:24Z	"A guest that is bridged to a physical adapter on which VLAN tagged packets (ethertype 0x8100) are received, the packets arrive in the guest without the VLAN tag.

I will attach a Wireshark packet decode of a frame as seen from the host and the guest for review."	Kevin Otte
16719	Virtualization not working without VT-x in the newer versions (5)	Windows	VirtualBox 5.1.22	2017-05-02T15:39:05Z	2017-06-05T08:14:25Z	2017-06-05T08:14:25Z	"After upgrading VBox from 4.3 to 5.1.20 (the latest version), my Windows VM has failed to start, along with VBox showing the following error message:

''Invalid parameter. (VERR_INVALID_PARAMETER)''[[BR]]
Result Code: NS_ERROR_FAILURE (0x80004005)[[BR]]
Component: ConsoleWrap[[BR]]
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

This issue is specific to the version 5 of VBox, because this error didn't occur at all before the upgrade.

This is the log prior to the upgrade can be found [https://forums.virtualbox.org/download/file.php?id=25276&sid=e07968bd0f4d95599392179d071b8104 here].
The log resulted after the upgrade can be found [https://forums.virtualbox.org/download/file.php?id=25274&sid=e07968bd0f4d95599392179d071b8104 here].

This issue affects many users, and needs some action."	kaisbe
14327	virtualbox: VBox crashes when run with a screen reader	all	VirtualBox 4.3.18	2015-07-25T15:57:41Z	2015-10-29T20:14:44Z	2015-10-29T20:14:44Z	"* What led up to the situation?

I use Debian 8.0, Orca, MATE, qt-at-spi.

 * What exactly did you do (or not do) that was effective (or >>> ineffective)?

1. Run /usr/lib/virtualbox/VirtualBox
2. Go to Machines menu (alt-m)
3. With down arrow key, choose ""Configuration"" (or Settings)
4. Browse 1-2 tabs with down arrow keys
5. Press Escape >>>


* What was the outcome of this action?

I get a segfault

 >>> * What outcome did you expect instead?

Should back to the main Vbox window.


I reproduce from 4.3.18 to 5.0."	texou
15024	VirtualBox-GuruMeditation error in Ubuntu	Windows	VirtualBox 5.0.12	2016-01-11T08:33:01Z	2016-01-11T08:48:08Z	2016-01-11T08:48:08Z	"While working on my Virtual Machine Windows 8.1, I often get this error and my machine stops. The '''VirtualBox-Guru Meditation errors''' says-  ""A critical error has occurred while running the virtual machine and the machine execution has been stopped."""	minig
21299	VirtualBox-7.0.4 kernel module build fails on RHEL9.1 host => fixed in svn	all	VirtualBox-7.0.4	2022-11-23T11:03:08Z	2022-11-28T08:13:56Z	2022-11-28T08:13:56Z	"Upon updating from RHEL 9.0 kernel 5.14.0-70.26.1.el9_0.x86_64 (uname -rv = 5.14.0-70.26.1.el9_0.x86_64 #1 SMP PREEMPT) to RHEL9.1 kernel 5.14.0-162.6.1.el9_1.x86_64 (uname -rv = 5.14.0-162.6.1.el9_1.x86_64 #1 SMP PREEMPT_DYNAMIC), the kernel module build failed with the following message:

.....
/tmp/vbox.0/linux/VBoxNetFlt-linux.c: In function ‘vboxNetFltPortOsXmit’:
/tmp/vbox.0/linux/VBoxNetFlt-linux.c:2327:23: error: implicit declaration of function ‘netif_rx_ni’; did you mean ‘netif_rx’? [-Werror=implicit-function-declaration]
 2327 |                 err = netif_rx_ni(pBuf);
      |                       ^~~~~~~~~~~
      |                       netif_rx
.....

I have attached vbox-setup.log for the complete build output.

I have attempted to uninstall and reinstall VBox, to no avail. The kernel module builds fine on the previously installed kernel (5.14.0-70.26.1.el9_0.x86_64). Module build fails regardless of whether I update VBox after updating the kernel or vice versa.

I should note that VBox 7.0.2 also fails to build against the new 5.14.0-162.6.1.el9_1.x86_64 kernel with the exact same failure. So does VBox 6.1.40.

"	Hosstyle
20719	VirtualBox-6.1-6.1.31_148688_el7-1.x86_64.rpm fail to build on Kylin Linux Advanced Server V10	OSX Server	VirtualBox 6.1.30	2021-12-10T01:19:11Z	2021-12-13T10:08:50Z	2021-12-13T10:08:50Z	Installing VirtualBox-6.1-6.1.31_148688_el7-1.x86_64.rpm work fine, but sudo /sbin/vboxconfig fails with kernel-4.19.90-25.8.v2101.ky10.x86_64	Nuyoah
19989	VirtualBox-6.1-6.1.16_140961_fedora32-1.x86_64.rpm does not install on Fedora 33	Linux	VirtualBox 6.1.16	2020-10-22T01:16:38Z	2021-02-03T20:19:45Z	2021-02-03T20:19:45Z	"VirtualBox-6.1-6.1.16_140961_fedora32-1.x86_64.rpm does not install on Fedora 33 with following error:

Erreur : 
 Problème: conflicting requests
  - nothing provides python(abi) = 3.8 needed by VirtualBox-6.1-6.1.16_140961_fedora32-1.x86_64


Test build VirtualBox-6.1.15-140899-Linux_amd64.run installs and works fine on Fedora 33."	Didier
18930	VirtualBox-5.2.33-133021-Linux_x86.run hangs on lsmod	all	VirtualBox 5.2.32	2019-09-16T02:36:25Z	2019-09-16T02:36:25Z	2019-09-16T02:36:25Z	"Two copies of lsmod running in D state.  In 5.2.32 I get 100% cpu on modprobe vboxdrv.

Debian Buster 10, Linux honey14 4.19.0-5-686-pae #1 SMP Debian 4.19.37-5+deb10u2 (2019-08-08) i686 GNU/Linux

Skip to 6:20 to see install still hung, swapping screen(1) to htop(1) and back. https://www.youtube.com/watch?v=ze95E4xIvEk

Thanks!"	supaplextor
17532	virtualbox-5.2 depends on libfontconfig1 (>= 2.9.0); (Ubuntu 14.04 LTS)	other	VirtualBox 5.2.6	2018-02-07T21:11:20Z	2018-02-07T21:11:20Z	2018-02-07T21:11:20Z	"install of virtualbox-5.2_5.2.6-120293~Ubuntu~trusty_amd64 fails on fully upgraded 14.04 LTS[[BR]]
[[BR]] uname -a[[BR]]
Linux vm530.loc 3.2.0-68-generic #102-Ubuntu SMP Tue Aug 12 22:02:15 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux[[BR]]

[[BR]]
See attached installer log, summary follows:[[BR]]
[[BR]]
The following packages have unmet dependencies:[[BR]]
 virtualbox-5.2 : Depends: libfontconfig1 (>= 2.9.0) but[[BR]]
2.8.0-3ubuntu9.2 is to be installed[[BR]]
                  Recommends: libsdl-ttf2.0-0 but it is not going to be installed[[BR]]

E: Unable to correct problems, you have held broken packages."	AndreasFG
20907	VirtualBox window doesn't move or resize	Linux	VirtualBox 6.1.32	2022-04-22T15:58:43Z	2022-04-27T13:38:30Z	2022-04-27T13:38:30Z	"Versión 6.1.34 r150636 (Qt5.12.8)
host: Ubuntu Mate 20.04.4 x64
vm: Ubuntu Mate 22.04 x64

VirtualBox window doesn't move or resize. this is an old bug, which was fixed by checking the box ""Machine Windows: Raise Windows Under Mouse""

Currently this option, despite the fact that it still solves the problem, does so partially, that is, it works intermittently"	mrvst
15581	VirtualBox v5.0 fails on Linux v4.6 kernel host with floppy drive attached	Windows	VirtualBox 5.0.24	2016-07-07T12:59:12Z	2016-09-15T07:58:08Z	2016-09-15T07:58:08Z	"When I start VirtualBox (currently v5.0.24) on a Linux v4.6 system running on a computer with a floppy drive fitted (yes, I know, it's becoming rare, but I need floppy for file exchanges with my old computers), VirtualBox fails to start Windows guests if the floppy drive is empty or contains a write-protected floppy disk.

Here are VirtualBox's reports:

1.- No floppy disk in drive:
{{{
The floppy controller cannot attach to the floppy drive (VERR_DEV_IO_ERROR).

Code d'erreur : 
NS_ERROR_FAILURE (0x80004005)
Composant : 
ConsoleWrap
Interface : 
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
}}}
and in /var/log/messages:

{{{
Jul  7 14:42:58 localhost klogd: blk_update_request: I/O error, dev fd0, sector 0
Jul  7 14:42:58 localhost klogd: floppy: error -5 while reading block 0
Jul  7 14:42:58 localhost klogd: blk_update_request: I/O error, dev fd0, sector 0
Jul  7 14:42:58 localhost klogd: floppy: error -5 while reading block 0
Jul  7 14:42:58 localhost klogd: vboxdrv: ffffffffa0dbe020 VMMR0.r0
Jul  7 14:42:58 localhost klogd: vboxdrv: ffffffffa0071020 VBoxDDR0.r0
Jul  7 14:42:58 localhost klogd: vboxdrv: ffffffffa0002020 VBoxDD2R0.r0
Jul  7 14:42:58 localhost klogd: blk_update_request: I/O error, dev fd0, sector 0
Jul  7 14:42:58 localhost klogd: floppy: error -5 while reading block 0
Jul  7 14:42:58 localhost klogd: blk_update_request: I/O error, dev fd0, sector 0
Jul  7 14:42:58 localhost klogd: floppy: error -5 while reading block 0
}}}


2.- Write-protected floppy disk in drive:

{{{
The floppy controller cannot attach to the floppy drive (VERR_WRITE_PROTECT).

Code d'erreur : 
NS_ERROR_FAILURE (0x80004005)
Composant : 
ConsoleWrap
Interface : 
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
}}}

I'm also attaching the log for a failed start of a Windows 7 guest session, with no floppy disk in drive.

This issue doesn't happen with older kernels (OK at least up to Linux kernel v4.1)."	dinosaur0
16320	Virtualbox uses 100% of CPU when suspending PC	Linux	VirtualBox 5.0.24	2016-12-23T16:48:45Z	2016-12-23T16:48:45Z	2016-12-23T16:48:45Z	"Hello,
When I suspend the computer while virtualbox is running and then start it again, vboxheadless process use 100% of CPU.

This happens always, every single time.

Ubuntu 16.04

VB log: http://pastebin.com/1PQexHkQ "	Bonomon
8960	Virtualbox Unity Launcher Integration	Linux	VirtualBox 4.0.4	2011-05-24T23:41:59Z	2011-05-26T15:48:30Z	2011-05-26T15:48:30Z	"Hello,

I've created a bash script to integrate virtualbox to the Ubuntu unity panel (to list virtual machines with a right click).

The problem is updating the list, if virtualbox could do a simple check for list changes on each start, then this could auto-update.

Find it here: http://code.google.com/p/virtualbox-unity-launcher/

It's registered under the MIT license."	Daniel
20828	Virtualbox test build 7 Gest addition didn't install for W11 Linux host	Windows	VirtualBox 6.1.32	2022-02-14T19:18:15Z	2022-03-30T16:37:06Z	2022-03-30T16:37:06Z	"It follows this tread : https://forums.virtualbox.org/viewtopic.php?f=2&t=105264&p=513634#p513634
I had to install 6.1.32's Guest Additions instead the one included in Virtualbox Version 6.1.97 r149824 (Qt5.15.2)
How to debug it ?"	Alberto789
14449	"VirtualBox replaces the ""\"" to ""/"" in file names of disks on Linux"	all	VirtualBox 4.3.30	2015-08-15T18:18:07Z	2015-08-15T18:18:07Z	2015-08-15T18:18:07Z	"VirtualBox saves invalid filenames of disks in the virtual machine configuration file (.vbox): backslashes is replaced with slashes. The file attribute is in vbox /VirtualBox/Machine/MediaRegistry/HardDisks/HardDisk/location saved the wrong disk names.
In linux backslashes common names disks, for example, in the directory /dev/disk/by-partlabel/."	empty is reserved
17152	VirtualBox RC1 guest additions hang Poser 6 & 7 on startup under XP guest	Windows	VirtualBox 5.2.0 RC 1	2017-10-10T10:19:59Z	2017-10-18T22:59:06Z	2017-10-18T22:59:06Z	"Greetings,

I recently updated to VirtualBox v5.2.0 RC1 to give it a try and see if my VMs could still work fine in it. I was well inspired, since I found a show-stopper bug (at least for my needs).
So, I installed VirtualBox v5.2.0 RC1, the v5.2.0 RC1 extension pack, booted my Windows XP guest VM in fail-safe mode, installed the VirtualBox guest additions (which, strangely, identify themselves as being v5.2.0 Beta 3 additions, instead of RC1...) with DirectX support.

Once the VM rebooted, when I start Poser 6 or 7 (the only two versions I got) on a Windows XP (32 bits) guest running on a 64 bits Linux host, the program hangs shortly after starting, on the startup screen, and Windows reports the program as ""non responding"" in its title bar. After a few more seconds waiting, the window of the program turns white and it stays stuck forever like that.

I then reinstalled the v5.1.28 guest additions (still keeping VirtualBox v5.2.0 RC1) and found out that Poser then works fine again.

Probably an issue in DirectX support ?

VBox.log attached (in its state, just after launching Poser)."	dinosaur0
10534	Virtualbox overrides umask, making it unusable for shared setup	other	VirtualBox 4.1.14	2012-05-09T04:40:53Z	2019-03-13T11:08:00Z	2019-03-13T11:08:00Z	"I want to setup Virtualbox to use a common directory to be used by any user who sits at the console (using VBOX_USER_HOME and the machinefolder property). Problem: The VirtualBox tools (GUI or command line) ignore umask and use 0600 instead. The next user runs into ""permission denied"" problems.

This makes it impossible for us to deploy VirtualBox as a replacement for VMware.
"	Harri
8435	VirtualBox only works with floppy disk images which have a certain filename extension	other	VirtualBox 4.0.4	2011-02-25T15:38:34Z	2016-10-10T15:42:12Z	2016-10-10T15:42:12Z	"VirtualBox 4.0.4 seems to refuse to work with floppy disk images unless the image filename has a certain extension. For example, on selecting ""myfloppy.bin"" in the GUI, VirtualBox says:
  Failed to open the floppy image /home/user/myfloppy.bin.
  Could not get the storage format of the medium '/home/user/myfloppy.bin' (VERR_NOT_SUPPORTED).

  Result Code: 
  VBOX_E_IPRT_ERROR (0x80BB0005)
  Component: 
  Medium
  Interface: 
  IMedium {9edda847-1279-4b0a-9af7-9d66251ccc18}
  Callee: 
  IVirtualBox {d2de270c-1d4b-4c9e-843f-bbb9b47269ff}

However, if I rename the file to myfloppy.dsk, there is no problem. I suggest that the filename limitation be removed. (If the selected file is exactly 1474560 bytes long, it will be a raw floppy disk image.)

"	Donuts
20448	Virtualbox on Linux host kills keyboard when running Windows 10 virtual machine	Windows	VirtualBox 6.1.22	2021-07-06T10:25:29Z	2021-07-06T10:25:29Z	2021-07-06T10:25:29Z	"Hi all,

I have a pretty boring problem with virtualbox installed on Kali host and windows 10 as guest. When I use windows 10, after an indefinite time (sometimes immediately, sometimes after a few minutes of use), the touchpad or mouse stops working in both the host system and the guest system. More specifically, the keyboard works correctly, while the click of the touchpad or mouse does not work. The only way to fix this is to shut down the Windows virtual machine.

Does someone have the same issue and found a solution?"	fourteenminusone
15480	VirtualBox on Linux does not pass ausio when connected using localhost VRDP	Windows	VirtualBox 5.0.20	2016-06-06T03:56:49Z	2016-06-08T16:55:54Z	2016-06-08T16:55:54Z	"I have a headless Windows 10 VM running on VirtualBox 5.0.20 on an Arch Linux host. 

I make connections to the VM using FreeRDP and Remmina.

When making connections to localhost:<port> (on which I have configured for the headless access), I do '''not''' get any audio.

However, when I connect directly to the VM using RDP (port 3389) and set the audio to ""Local"", I get it loud and clear.

To be sure that this is not a VRDP artifact, I cloned the VM and ran it on a VirtualBox instance on a Windows Host. On Windows, I am ale to access the sound both ways.

There is a wontfix (https://www.virtualbox.org/ticket/10923). However, I think that the issues are slightly different. This case is specifically about a different way in which the VRDP has been implemented in Windows and Linux.




1.2.0-rcgit.11 (git n/a)
When connecting "	Sachin Garg
19816	VirtualBox not able to power-off any (currently-running) machines	Windows	VirtualBox 5.2.42	2020-08-16T17:34:33Z	2020-09-08T17:20:25Z	2020-09-08T17:20:25Z	"I am using cuckoo sandbox (version 2.0.7) to perform batch dynamic analysis on windows malware. My host system is Ubuntu 18.04 and I am running 10 Windows 7 VMs on parallel (headless).

The Cuckoo Sandbox application will stop a VM when it is done analysing a binary and will restore the specified snapshot. It will then power up the machine to start a new analysis.

After prolonged usage (around 4+ hours), one or more of the running VMs will become unresponsive and will not poweroff. The only solution I have is to restart the computer, as the virtualbox services will fail to reload.
(If I quit the cuckoo sandbox when one of the machines deadlocks, then all of the running machines will become unresponsive and keep running endlessly).

I am attaching the log of the VM that caused the issue most recently"	soutsos
18495	VirtualBox NAT alias option use-same-ports (--nataliasmode1=sameports) has no effect on Ubuntu 16.04 host OS	Linux	VirtualBox 6.0.4	2019-03-14T20:53:00Z	2019-03-14T20:53:00Z	2019-03-14T20:53:00Z	"== Steps to reproduce ==

    1. Create a VirtualBox VM as follows, accepting default values for anything not listed here:

        * Name: archlinux-2019.03.01-x86_64
        * Type: Linux
        * Version: Arch Linux (64-bit)

    2. Download archlinux-2019.03.01-x86_64.iso into the VM directory:

    {{{
cd 'VirtualBox VMs'/archlinux-2019.03.01-x86_64
curl -O http://mirrors.acm.wpi.edu/archlinux/iso/2019.03.01/archlinux-2019.03.01-x86_64.iso
    }}}

    3. Confirm the MD5 checksum. First, display the expected checksum:

    {{{
curl http://mirrors.acm.wpi.edu/archlinux/iso/2019.03.01/md5sums.txt
    }}}

    Verify on Linux:

    {{{
md5sum archlinux-2019.03.01-x86_64.iso
    }}}

    Verify on macOS:

    {{{
md5 archlinux-2019.03.01-x86_64.iso
    }}}

    4. Start the VM in VirtualBox, click '''Choose a virtual optical disk file''' (represented by a folder icon with an upward-pointing green arrow), and select the archlinux-2019.03.01-x86_64.iso file downloaded in Step 2.

    5. Boot the VM, selecting default options for everything.

    6. On the host (64-bit Ubuntu Xenial Xerus 16.04.6 LTS), find two unused privileged (port number less than 1024) ports; for example, the following command will return nothing if both ports 1022 and 1023 are free:

    {{{
netstat -Wa | grep -E '1022|1023'
    }}}

    7. On the guest (64-bit Arch Linux 2019.03.01), confirm that the first free port from Step 6 is also free on the guest:

    {{{
netstat -Wa | grep 1022
    }}}

    If this  command returns any output, repeat Steps 6 and 7 until you have found two free ports.

    8. On the host (64-bit Ubuntu Xenial Xerus 16.04.6 LTS), start listening on the second free port, the receiving port:

    {{{
sudo nc -l 1023
    }}}

    9. On the guest (64-bit Arch Linux 2019.03.01), open a connection to the receiving port on the host, originating the connection from the first free port, the sending port:

    {{{
nc -p 1022 ala-michaelk-lx1.corp.ad.wrs.com 1023
    }}}

    Replace `ala-michaelk-lx1.corp.ad.wrs.com` with the fully qualified domain name (FQDN) of the host, as returned by the `hostname -f` command.

    After running both `nc` commands, any text entered on the guest should appear on the host and vice versa.

    10. In another shell on host, look for connections to the receiving port:

    {{{
netstat -W | grep 1023
    }}}

    Initially observe that network address translation (NAT) has replaced the sending port (1022) with a random port (48946), as expected for `--nataliasmode1=default`:

    {{{
$ netstat -W | grep 1023
tcp        0      0 ala-michaelk-lx1.corp.ad.wrs.com:1023 ala-michaelk-lx1.corp.ad.wrs.com:48946 ESTABLISHED
tcp        0      0 ala-michaelk-lx1.corp.ad.wrs.com:48946 ala-michaelk-lx1.corp.ad.wrs.com:1023 ESTABLISHED
    }}}

    11. On the host (64-bit Ubuntu Xenial Xerus 16.04.6 LTS), close the connection by pressing Ctrl-D (EOF) in the shell running `nc`.

    12. Close the guest console window, select '''Save the machine state''', and click '''OK'''.

    13. On host, switch the VM to `--nataliasmode1=sameports`:

    {{{
VBoxManage modifyvm archlinux-2019.03.01-x86_64 --nataliasmode1=sameports
    }}}

    14. In VirtualBox, click '''Start''' to restore the VM.

    15. Repeat Steps 8–11.

== Expected ==

The port number for the sending port (1022) is preserved, as seen on host macOS Mojave Version 10.14.3:

{{{
inu:~ michael$ netstat -W | grep 1023
tcp4       0      0  inu.corp.ad.wrs.com.1023  inu.corp.ad.wrs.com.1022  ESTABLISHED
tcp4       0      0  inu.corp.ad.wrs.com.exp2  inu.corp.ad.wrs.com.1023  ESTABLISHED
}}}

== Observed ==

The port number for the sending port (1022) is replaced with a random port number, as seen on host 64-bit Ubuntu Xenial Xerus 16.04.6 LTS:

{{{
$ netstat -W | grep 1023
tcp        0      0 ala-michaelk-lx1.corp.ad.wrs.com:48972 ala-michaelk-lx1.corp.ad.wrs.com:1023 ESTABLISHED
tcp        0      0 ala-michaelk-lx1.corp.ad.wrs.com:1023 ala-michaelk-lx1.corp.ad.wrs.com:48972 ESTABLISHED
}}}
"	interfrastic
20728	VirtualBox Manager UI elements flicker with compositing disabled	other	VirtualBox 6.1.30	2021-12-14T23:26:06Z	2021-12-14T23:26:06Z	2021-12-14T23:26:06Z	"Since upgrading to 6.1.30, the manager UI (not the guest window) seems to flicker/lag when interacting with certain UI elements. Enabling compositing in xfwm4 fixes the issue.

System details:

{{{
user@host:~$ vboxmanage --version
6.1.30r148432
user@host:~$ cat /etc/*release
PRETTY_NAME=""Debian GNU/Linux bookworm/sid""
NAME=""Debian GNU/Linux""
ID=debian
HOME_URL=""https://www.debian.org/""
SUPPORT_URL=""https://www.debian.org/support""
BUG_REPORT_URL=""https://bugs.debian.org/""
user@host:~$ uname -a
Linux host 5.14.0-2-amd64 #1 SMP Debian 5.14.9-2 (2021-10-03) x86_64 GNU/Linux
user@host:~$ lspci -k | grep -A3 VGA
00:02.0 VGA compatible controller: Intel Corporation CometLake-U GT2 [UHD Graphics] (rev 02)
	Subsystem: Lenovo UHD Graphics
	Kernel driver in use: i915
	Kernel modules: i915
user@host:~$ xfwm4 --version
	This is xfwm4 version 4.16.1 (revision 5f61a84ad) for Xfce 4.16
	Released under the terms of the GNU General Public License.
	Compiled against GTK+-3.24.24, using GTK+-3.24.30.

	Build configuration and supported features:
	- Startup notification support:                 Yes
	- XSync support:                                Yes
	- Render support:                               Yes
	- Xrandr support:                               Yes
	- Xpresent support:                             Yes
	- X Input 2 support:                            No
	- Embedded compositor:                          Yes
	- Epoxy support:                                Yes
	- KDE systray proxy (deprecated):               No
user@host:~$ xfconf-query -c xfwm4 -p /general/use_compositing
false
user@host:~$ sudo X -version
[sudo] password for user: 

X.Org X Server 1.20.11
X Protocol Version 11, Revision 0
Build Operating System: linux Debian
Current Operating System: Linux host 5.14.0-2-amd64 #1 SMP Debian 5.14.9-2 (2021-10-03) x86_64
Kernel command line: BOOT_IMAGE=/vmlinuz-5.14.0-2-amd64 root=/dev/mapper/host--vg-root ro quiet
Build Date: 13 April 2021  04:07:31PM
xorg-server 2:1.20.11-1 (https://www.debian.org/support) 
Current version of pixman: 0.40.0
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
user@host:~$ 
}}}

Video of issue attached. (Apologies for phone camera video. Recording the window with `ffmpeg -f x11grab ...` makes the issue disappear.)

Same issue on latest v6.1.31 test build."	adsr
19082	VirtualBox Manager scaled *down*, when a mix of HiDPI and non-HiDPI screens are attached	all	VirtualBox 6.0.14	2019-11-13T13:39:07Z	2020-12-06T07:48:12Z	2020-12-06T07:48:12Z	"Steps to reproduce:
1. Set up a machine with a mix of HiDPI and non-HiDPI screens
2. Start virtualbox
3. Observe failure

Expected result: The GUI of virtualbox looks normal
Also acceptable: The GUI is scaled up for the HiDPI screen

Observed behavior:
The GUI of virtualbox is scaled *down* by roughly a factor of two. Making the text hard to read even on a low-resolution screen. The virtual machines themselves are not impacted.

My setup:
VirtualBox Version is 6.0.14 r133895 (Qt5.6.1) on Debian 10 Buster. The device is a Lenovo T490 notebook, with an internal 14"" 1920x1080 (HiDPI) screen. The behavior is observed when attaching a low-res 1920*1200 external display, but not when attaching a HiDPI 3840*2160 display. The behavior occurs both with the Debian-Package, and with the distribution-agnostic installation. I am not aware of any custom configuration on my system that might impact this.

Additional notes:
I have posted about this on the forums here: [https://forums.virtualbox.org/viewtopic.php?f=7&t=95297]. There are descriptions of similar behavior (may or may not be the same issue) here: [https://forums.virtualbox.org/viewtopic.php?f=7&t=92965]; and here: [https://forums.virtualbox.org/viewtopic.php?f=7&t=88116]. All of these are recent. I first observed this behavior after installing an update using apt, however I do not know which version I had before that, sorry.

Temporary workaround:
Virtualbox can be forcibly scaled up by setting QT_SCALE_FACTOR=2, however this cannot be set globally, as it will break all other Qt-based applications. Also when this bug is not triggered (b/c only low-res or HiDPI screens are attached) the extra scaling will make everything unusably big.

Is there any log files that I should post to help reproduce this?"	Nuvanda
19805	VirtualBox Manager hijacks Linux desktop	all	VirtualBox 6.1.10	2020-08-10T11:55:23Z	2020-08-10T11:55:23Z	2020-08-10T11:55:23Z	"If I remove or rename the virtual disk file of a virtual machine and then start VirtualBox Manager it goes into an endless loop redisplaying an error message box ""Failed to open the medium with the following ID: ...""

The message box redisplays itself in a loop and cannot be closed. Besides that it steals the desktop focus so it is impossible to do anything else. Cannot even kill the process or close down the host machine in a proper way! Have to push power button to reboot!

It is OK to display the error message ONCE! It is unacceptable to hijack the desktop!

VirtualBox 6.1.12
Ubuntu 18.04 host
Guest is Windows 10 but it probably does not matter(?).
"	ele
16130	VirtualBox Manager fonts+colors messed up on Linux host	all	VirtualBox 5.1.4	2016-10-30T16:52:35Z	2018-03-16T18:35:45Z	2018-03-16T18:35:45Z	"At version 5.1-5.1.4, the UI in VirtualBox Manager seriously degraded in both text clarity and coloring.   At version 5.1-5.1.2, there were no issues but at 5.1-5.1.4 through -5.1.8, the problem is present.  All versions mentioned were tested on a fully updated CentOS 7 install.  Pictures attached of -5.1.2 vs -5.1.4
"	ChrisE
20137	virtualbox manager does not work properly wit 4k monitors on Ubunto 20.04	Linux	VirtualBox 6.1.16	2021-01-19T22:08:43Z	2021-01-19T22:11:37Z	2021-01-19T22:11:37Z	"When installed on a Ubuntu 20.04, virtualbox 6.1.16 runs as empty gray window. The method to fix it is to change scaling in displays settings from 200% to 100% or run it using the ""run_scaled"" script.
Also making the window smaller helps to an extent.

the same problem is related to running virtual machine window. With 200% scaling it has numerous graphical artifacts that prevent normal operation."	Lacek
15635	VirtualBox Manager 5.1.0 r108711 ignores system font on XFCE 14.04	all	VirtualBox 5.1.0	2016-07-18T13:02:17Z	2016-08-10T10:59:21Z	2016-08-10T10:59:21Z	"Host system - Linux XFCE 14.04 LTS
VirtualBox Manager 5.1.0 r108711

Problem VirtualBox Manager uses some font, but not the system.

To reproduce, change system fort to Verdana for instance and start VirtualBox Manager. Font in VirtualBox Manager will be different.

Other application doesn't have this problem.

Thank you.
"	macachuto
17864	VirtualBox kernel modules do not build on Fedora 28	all	VirtualBox 5.2.14	2018-07-11T06:26:13Z	2018-07-24T15:44:33Z	2018-07-24T15:44:33Z	"VirtualBox-5.2-5.2.12_122591_fedora26-1.x86_64

Issuing /sbin/vboxconfig fails.

There's multiple files being complained about containing the line
IPAddressDeny=any (""File /usr/lib/systemd/system/systemd-logind.service:36 configures an IP firewall (IPAddressDeny=any), but the local system does not support BPF/cgroup based firewalling""):

systemd-machined.service
systemd-udevd.service
systemd-journald.service
systemd-logind.service

Finally (and after commenting out IPAddressDeny=any for debugging purposes in named files) it still fails:
{{{
(...)
  gcc -Wp,-MD,/tmp/vbox.0/.SUPR0IdcClient.o.d  -nostdinc -isystem /usr/lib/gcc/x86_64-redhat-linux/8/include -I./arch/x86/include -I./arch/x86/include/generated  -I./include -I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi -I./include/generated/uapi -include ./include/linux/kconfig.h -include ./include/linux/compiler_types.h -D__KERNEL__ -DCONFIG_CC_STACKPROTECTOR -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -Werror-implicit-function-declaration -Wno-format-security -std=gnu89 -fno-PIE -DCC_HAVE_ASM_GOTO -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel -funit-at-a-time -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1 -DCONFIG_AS_SSSE3=1 -DCONFIG_AS_CRC32=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -DCONFIG_AS_AVX512=1 -DCONFIG_AS_SHA1_NI=1 -DCONFIG_AS_SHA256_NI=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern -mindirect-branch-register -DRETPOLINE -fno-delete-null-pointer-checks -Wno-frame-address -Wno-format-truncation -Wno-format-overflow -Wno-int-in-bool-context -O2 --param=allow-store-data-races=0 -Wframe-larger-than=2048 -fstack-protector-strong -Wno-unused-but-set-variable -Wno-unused-const-variable -fvar-tracking-assignments -g -pg -mfentry -DCC_USING_FENTRY -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fno-merge-all-constants -fmerge-constants -fno-stack-check -fconserve-stack -Werror=implicit-int -Werror=strict-prototypes -Werror=date-time -Werror=incompatible-pointer-types -Werror=designated-init -fmacro-prefix-map=./= -Wno-packed-not-aligned -include /tmp/vbox.0/include/VBox/SUPDrvMangling.h -fno-pie -I/lib/modules/4.17.3-200.fc28.x86_64/build/include -I/tmp/vbox.0/ -I/tmp/vbox.0/include -I/tmp/vbox.0/r0drv/linux -D__KERNEL__ -DMODULE -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX -DRT_WITH_VBOX -DVBOX_WITH_HARDENING -DRT_ARCH_AMD64  -DMODULE  -DKBUILD_BASENAME='""SUPR0IdcClient""' -DKBUILD_MODNAME='""vboxpci""' -c -o /tmp/vbox.0/SUPR0IdcClient.o /tmp/vbox.0/SUPR0IdcClient.c
  gcc -Wp,-MD,/tmp/vbox.0/.SUPR0IdcClientComponent.o.d  -nostdinc -isystem /usr/lib/gcc/x86_64-redhat-linux/8/include -I./arch/x86/include -I./arch/x86/include/generated  -I./include -I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi -I./include/generated/uapi -include ./include/linux/kconfig.h -include ./include/linux/compiler_types.h -D__KERNEL__ -DCONFIG_CC_STACKPROTECTOR -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -Werror-implicit-function-declaration -Wno-format-security -std=gnu89 -fno-PIE -DCC_HAVE_ASM_GOTO -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel -funit-at-a-time -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1 -DCONFIG_AS_SSSE3=1 -DCONFIG_AS_CRC32=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -DCONFIG_AS_AVX512=1 -DCONFIG_AS_SHA1_NI=1 -DCONFIG_AS_SHA256_NI=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern -mindirect-branch-register -DRETPOLINE -fno-delete-null-pointer-checks -Wno-frame-address -Wno-format-truncation -Wno-format-overflow -Wno-int-in-bool-context -O2 --param=allow-store-data-races=0 -Wframe-larger-than=2048 -fstack-protector-strong -Wno-unused-but-set-variable -Wno-unused-const-variable -fvar-tracking-assignments -g -pg -mfentry -DCC_USING_FENTRY -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fno-merge-all-constants -fmerge-constants -fno-stack-check -fconserve-stack -Werror=implicit-int -Werror=strict-prototypes -Werror=date-time -Werror=incompatible-pointer-types -Werror=designated-init -fmacro-prefix-map=./= -Wno-packed-not-aligned -include /tmp/vbox.0/include/VBox/SUPDrvMangling.h -fno-pie -I/lib/modules/4.17.3-200.fc28.x86_64/build/include -I/tmp/vbox.0/ -I/tmp/vbox.0/include -I/tmp/vbox.0/r0drv/linux -D__KERNEL__ -DMODULE -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX -DRT_WITH_VBOX -DVBOX_WITH_HARDENING -DRT_ARCH_AMD64  -DMODULE  -DKBUILD_BASENAME='""SUPR0IdcClientComponent""' -DKBUILD_MODNAME='""vboxpci""' -c -o /tmp/vbox.0/SUPR0IdcClientComponent.o /tmp/vbox.0/SUPR0IdcClientComponent.c
  gcc -Wp,-MD,/tmp/vbox.0/linux/.SUPR0IdcClient-linux.o.d  -nostdinc -isystem /usr/lib/gcc/x86_64-redhat-linux/8/include -I./arch/x86/include -I./arch/x86/include/generated  -I./include -I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi -I./include/generated/uapi -include ./include/linux/kconfig.h -include ./include/linux/compiler_types.h -D__KERNEL__ -DCONFIG_CC_STACKPROTECTOR -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -Werror-implicit-function-declaration -Wno-format-security -std=gnu89 -fno-PIE -DCC_HAVE_ASM_GOTO -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel -funit-at-a-time -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1 -DCONFIG_AS_SSSE3=1 -DCONFIG_AS_CRC32=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -DCONFIG_AS_AVX512=1 -DCONFIG_AS_SHA1_NI=1 -DCONFIG_AS_SHA256_NI=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern -mindirect-branch-register -DRETPOLINE -fno-delete-null-pointer-checks -Wno-frame-address -Wno-format-truncation -Wno-format-overflow -Wno-int-in-bool-context -O2 --param=allow-store-data-races=0 -Wframe-larger-than=2048 -fstack-protector-strong -Wno-unused-but-set-variable -Wno-unused-const-variable -fvar-tracking-assignments -g -pg -mfentry -DCC_USING_FENTRY -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fno-merge-all-constants -fmerge-constants -fno-stack-check -fconserve-stack -Werror=implicit-int -Werror=strict-prototypes -Werror=date-time -Werror=incompatible-pointer-types -Werror=designated-init -fmacro-prefix-map=./= -Wno-packed-not-aligned -include /tmp/vbox.0/include/VBox/SUPDrvMangling.h -fno-pie -I/lib/modules/4.17.3-200.fc28.x86_64/build/include -I/tmp/vbox.0/ -I/tmp/vbox.0/include -I/tmp/vbox.0/r0drv/linux -D__KERNEL__ -DMODULE -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX -DRT_WITH_VBOX -DVBOX_WITH_HARDENING -DRT_ARCH_AMD64  -DMODULE  -DKBUILD_BASENAME='""SUPR0IdcClient_linux""' -DKBUILD_MODNAME='""vboxpci""' -c -o /tmp/vbox.0/linux/SUPR0IdcClient-linux.o /tmp/vbox.0/linux/SUPR0IdcClient-linux.c
   ./tools/objtool/objtool orc generate  --module --no-fp  --retpoline ""/tmp/vbox.0/SUPR0IdcClientComponent.o"";
  if [ ""-pg"" = ""-pg"" ]; then if [ /tmp/vbox.0/SUPR0IdcClientComponent.o != ""scripts/mod/empty.o"" ]; then ./scripts/recordmcount  ""/tmp/vbox.0/SUPR0IdcClientComponent.o""; fi; fi;
   ./tools/objtool/objtool orc generate  --module --no-fp  --retpoline ""/tmp/vbox.0/linux/SUPR0IdcClient-linux.o"";
   ./tools/objtool/objtool orc generate  --module --no-fp  --retpoline ""/tmp/vbox.0/SUPR0IdcClient.o"";
  if [ ""-pg"" = ""-pg"" ]; then if [ /tmp/vbox.0/linux/SUPR0IdcClient-linux.o != ""scripts/mod/empty.o"" ]; then ./scripts/recordmcount  ""/tmp/vbox.0/linux/SUPR0IdcClient-linux.o""; fi; fi;
  if [ ""-pg"" = ""-pg"" ]; then if [ /tmp/vbox.0/SUPR0IdcClient.o != ""scripts/mod/empty.o"" ]; then ./scripts/recordmcount  ""/tmp/vbox.0/SUPR0IdcClient.o""; fi; fi;
   ./tools/objtool/objtool orc generate  --module --no-fp  --retpoline ""/tmp/vbox.0/VBoxPci.o"";
  if [ ""-pg"" = ""-pg"" ]; then if [ /tmp/vbox.0/VBoxPci.o != ""scripts/mod/empty.o"" ]; then ./scripts/recordmcount  ""/tmp/vbox.0/VBoxPci.o""; fi; fi;
In file included from /tmp/vbox.0/r0drv/linux/the-linux-kernel.h:80,
                 from /tmp/vbox.0/linux/VBoxPci-linux.c:31:
In function ‘strncpy’,
    inlined from ‘vboxPciLinuxDevDetachHostDriver’ at /tmp/vbox.0/linux/VBoxPci-linux.c:436:9,
    inlined from ‘vboxPciOsDevInit’ at /tmp/vbox.0/linux/VBoxPci-linux.c:645:14:
./include/linux/string.h:246:9: warning: ‘__builtin_strncpy’ specified bound 64 equals destination size [-Wstringop-truncation]
  return __builtin_strncpy(p, q, size);
         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   ./tools/objtool/objtool orc generate  --module --no-fp  --retpoline ""/tmp/vbox.0/linux/VBoxPci-linux.o"";
  if [ ""-pg"" = ""-pg"" ]; then if [ /tmp/vbox.0/linux/VBoxPci-linux.o != ""scripts/mod/empty.o"" ]; then ./scripts/recordmcount  ""/tmp/vbox.0/linux/VBoxPci-linux.o""; fi; fi;
  ld -m elf_x86_64 -z max-page-size=0x200000   -r -o /tmp/vbox.0/vboxpci.o /tmp/vbox.0/linux/VBoxPci-linux.o /tmp/vbox.0/VBoxPci.o /tmp/vbox.0/SUPR0IdcClient.o /tmp/vbox.0/SUPR0IdcClientComponent.o /tmp/vbox.0/linux/SUPR0IdcClient-linux.o 
make -f ./scripts/Makefile.modpost
  find /tmp/vbox.0/.tmp_versions -name '*.mod' | xargs -r grep -h '\.ko$' | sort -u | sed 's/\.ko$/.o/' | scripts/mod/modpost   -i ./Module.symvers -I /tmp/vbox.0/Module.symvers  -o /tmp/vbox.0/Module.symvers -S  -w  -s -T -
  gcc -Wp,-MD,/tmp/vbox.0/.vboxpci.mod.o.d  -nostdinc -isystem /usr/lib/gcc/x86_64-redhat-linux/8/include -I./arch/x86/include -I./arch/x86/include/generated  -I./include -I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi -I./include/generated/uapi -include ./include/linux/kconfig.h -include ./include/linux/compiler_types.h -D__KERNEL__ -DCONFIG_CC_STACKPROTECTOR -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -Werror-implicit-function-declaration -Wno-format-security -std=gnu89 -fno-PIE -DCC_HAVE_ASM_GOTO -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel -funit-at-a-time -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1 -DCONFIG_AS_SSSE3=1 -DCONFIG_AS_CRC32=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -DCONFIG_AS_AVX512=1 -DCONFIG_AS_SHA1_NI=1 -DCONFIG_AS_SHA256_NI=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern -mindirect-branch-register -DRETPOLINE -fno-delete-null-pointer-checks -Wno-frame-address -Wno-format-truncation -Wno-format-overflow -Wno-int-in-bool-context -O2 --param=allow-store-data-races=0 -Wframe-larger-than=2048 -fstack-protector-strong -Wno-unused-but-set-variable -Wno-unused-const-variable -fvar-tracking-assignments -g -pg -mfentry -DCC_USING_FENTRY -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fno-merge-all-constants -fmerge-constants -fno-stack-check -fconserve-stack -Werror=implicit-int -Werror=strict-prototypes -Werror=date-time -Werror=incompatible-pointer-types -Werror=designated-init -fmacro-prefix-map=./= -Wno-packed-not-aligned -include /tmp/vbox.0/include/VBox/SUPDrvMangling.h -fno-pie -I/lib/modules/4.17.3-200.fc28.x86_64/build/include -I/tmp/vbox.0/ -I/tmp/vbox.0/include -I/tmp/vbox.0/r0drv/linux -D__KERNEL__ -DMODULE -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX -DRT_WITH_VBOX -DVBOX_WITH_HARDENING -DRT_ARCH_AMD64  -DKBUILD_BASENAME='""vboxpci.mod""' -DKBUILD_MODNAME='""vboxpci""' -DMODULE  -c -o /tmp/vbox.0/vboxpci.mod.o /tmp/vbox.0/vboxpci.mod.c
  ld -r -m elf_x86_64 -z max-page-size=0x200000 -T ./scripts/module-common.lds --build-id  -o /tmp/vbox.0/vboxpci.ko /tmp/vbox.0/vboxpci.o /tmp/vbox.0/vboxpci.mod.o ;  true
make V=1 CONFIG_MODULE_SIG= -C /lib/modules/4.17.3-200.fc28.x86_64/build SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 INSTALL_MOD_PATH= INSTALL_MOD_DIR=misc modules_install
test -e include/generated/autoconf.h -a -e include/config/auto.conf || (		\
echo >&2;							\
echo >&2 ""  ERROR: Kernel configuration is invalid."";		\
echo >&2 ""         include/generated/autoconf.h or include/config/auto.conf are missing."";\
echo >&2 ""         Run 'make oldconfig && make prepare' on kernel src to fix it."";	\
echo >&2 ;							\
/bin/false)
mkdir -p /lib/modules/4.17.3-200.fc28.x86_64/misc
make -f ./scripts/Makefile.modinst
  mkdir -p /lib/modules/4.17.3-200.fc28.x86_64/misc ; cp /tmp/vbox.0/vboxpci.ko /lib/modules/4.17.3-200.fc28.x86_64/misc ; true /lib/modules/4.17.3-200.fc28.x86_64/misc/vboxpci.ko ; scripts/sign-file ""sha256"" ""certs/signing_key.pem"" certs/signing_key.x509 /lib/modules/4.17.3-200.fc28.x86_64/misc/vboxpci.ko || true && true /lib/modules/4.17.3-200.fc28.x86_64/misc/vboxpci.ko
At main.c:160:
- SSL error:02001002:system library:fopen:No such file or directory: crypto/bio/bss_file.c:74
- SSL error:2006D080:BIO routines:BIO_new_file:no such file: crypto/bio/bss_file.c:81
sign-file: certs/signing_key.pem: No such file or directory
  /bin/sh ./scripts/depmod.sh /sbin/depmod 4.17.3-200.fc28.x86_64 """"
}}}
After updating to VirtualBox-5.2-5.2.14_123301_fedora26-1.x86_64 there's an empty vbox-install.log after issuing /sbin/vboxconfig, vbox-setup.log shows:

Building the main VirtualBox module.
Building the net filter module.
Building the net adaptor module.
Building the PCI pass-through module.

No information on why it failed to build."	ThygWedd
18936	VirtualBox ignores LIBGL_DRI3_DISABLE=1	all	VirtualBox 5.2.32	2019-09-17T12:48:02Z	2019-09-17T12:48:02Z	2019-09-17T12:48:02Z	"Hello

Shell environment variable LIBGL_DRI3_DISABLE= is used to disable DRI3 on X Server.
Before VBox switched to libQt5*VBox.so it worked.
Now this envvar is ignored.
Please, fix.

Best regards
"	waltk
7187	VirtualBox huge log file harvesting disk	Windows	VirtualBox 3.2.6	2010-07-17T17:57:34Z	2020-09-03T22:36:03Z	2020-09-03T22:36:03Z	"Using VirtualBox 3.2.6 r633112, Ubuntu 10.04 as host and Windows XP Professional as guest, I had problems starting a program (Mach3) inside Windows, I didn't open after three attempts but continued working with Firefox and other programs, after some time, I received an Ubuntu system message indicating my hard disk had very few available space, this surprised me since I was supposed to be using just 20 GB (for both Ubuntu and virtual WinXP) from my 160 GB disk. I forced VBox down and searched for the problem, I found four VBox log files in the Logs directory for my VM, two had sizes of 30 GB and 90 GB!

I'm not sure whether such a huge log file should be useful for debugging, but guess VBox could emit an alert when these logs grow too much so that the user can pay attention and take some actions before the host system becomes unresponsive.
"	José Jorge
19582	VirtualBox host, memory management issue, unable to release unused memory of guest	Linux	VirtualBox 6.1.6	2020-05-14T10:42:00Z	2020-05-18T15:23:13Z	2020-05-18T15:23:13Z	"I have a workstation with 32 GB installed memory.

I create a new Debian virtual machine, and allocate 16 GB to it. When I boot the machine, it only take less than 800 MB memory. As the virtual machine running, especially for heavy tasks. The memory occupation increase. But when I end those tasks, the memory usage of guest machine's OS suddenly reduce, but the memory occupation of virtual machine on host RAM, still keep as the memory upper bound. 

I believe that it is the problem of VirtualBox, because even if I reboot (not same as power off and boot) the virtual machine, the RAM usage still keep as Maximum.

I hope VirtualBox can add ability to automatically release unused guest memory."	stl0hello
17800	virtualbox gui is not that accessible	all	VirtualBox 5.2.12	2018-06-04T11:14:25Z	2018-06-04T11:14:25Z	2018-06-04T11:14:25Z	"hey there,
the virtualbox gui is not that accessible compared to what it used to be
i'm unable to read the name of the virtual machines when arrowing up and down the list of machines, or locate the place to create snapshotts for the sillected vm, when I am in the settings dylog box, the catagorys such as mutherbord, audio, basic shared folders is not announsed any more.
host arch linux running the latest version of virtualbox.
I use orca the screen reader to navigate around.
I realize that you are really bizy  people I would be greatful if you could look in to this.
stepps to reproduce,
1.
launch orca the screen reader.
2.
launch virtualbox.
3 try navigateing up and down the list of vms and settings dylog boxes.
what should happen,
all catagorys should be announced when navigateing using arrow keys, the names of vms should be spoken currently this is not the case,
i'm no longer able to create snappshots.
thanks"	maj
20812	VirtualBox GUI doesn't work well with dark themes	other	VirtualBox 6.1.32	2022-02-05T17:32:23Z	2022-02-05T17:32:23Z	2022-02-05T17:32:23Z	VirtualBox GUI doesn't work well with dark themes. Some parts of the GUI are dark and some are light, but the worst are light fonts on light background. Please see attachment.	XorOrNor
16750	VirtualBox GUI Crashed when cloning after upgrading to latest version	Windows	VirtualBox 5.1.22	2017-05-11T14:21:19Z	2017-06-02T14:21:45Z	2017-06-02T14:21:45Z	"We upgrade the servers to CentOS Linux 6.9 2.6.32-696.1.1.el6.x86_64 with VirtualBox 5.1.22_115126_el6-1

Now when we try to clone a machine it crashes the GUI.  All machines show ""aborted"" though they are running fine and each states the VirtualBox Critical Error.  I'm attaching the error here."	Tomqwe
20014	VirtualBox GUI broken after update from 5.2.44 to 6.1.14	Linux	VirtualBox 6.1.14	2020-11-02T15:50:37Z	2020-11-02T15:56:52Z	2020-11-02T15:56:52Z	After struggling all day trying to keep 5.2.44 working with VVV, I decided to try updating to 6.1.14.  As a result, when I open up the VirtualBox Manager GUI, I get this broken display.  The contents are in the incorrect location and aren't clickable.  If I expand the window, all of the content disappears.  Luckily, I don't need to use the configuration tools there at the moment but this will be a problem for me quite soon.	artlytic_dave
17246	VirtualBox Guest Additions Fails to start	Linux	VirtualBox 5.2.0	2017-11-05T18:24:07Z	2017-11-05T18:24:07Z	2017-11-05T18:24:07Z	"VirtualBox Guest Additions: Starting.
/etc/rc.d/init.d/vboxadd: line 255: : No such file or directory
"	PresidentTrump
20704	VirtualBox Guest Additions 6.1.30 error during install	Windows	VirtualBox 6.1.30	2021-12-02T05:19:08Z	2022-02-21T22:16:51Z	2022-02-21T22:16:51Z	"Hello
I got an error during the install of the VirtualBox Guest Additions.
Host = Linux Mageia 64 bits
Guest = windows XP 32 bits
The error is:
2148081673 - Failed to calculate strong name from 'C:\Program Files\Oracle\VirtualBox Guest Additions\VBoxGuest.cat'. Check if catalog is valid and if file is in the same directory as the INF.

It occurs since the 6.1.28 release.
6.1.26 is ok

Attached is the install_drivers.log

"	courgette
17449	Virtualbox general protection fault	Windows	VirtualBox 5.2.4	2018-01-11T02:47:33Z	2018-02-21T18:14:32Z	2018-02-21T18:14:32Z	I am running Virtualbox on Gentoo 64 bit OS kernel linux-4.14.13 and am getting general protection fault while running the VM and Virtualbox crashes.	adimanav
17488	virtualbox freezing the my system linux mint 18.3	Linux	VirtualBox 5.1.20	2018-01-21T23:22:45Z	2018-01-23T10:38:07Z	2018-01-23T10:38:07Z	"i try many time to solve this issue but no way to solve it because that i need your help kindly , i was trying to install Linux Kali in my system guest (Linux mint 18.3) and after i finish form all the setting a start the vm image suddenly the system is freezing 
and the only way to re-start all things is by re-start my guest system 
and i can't provide you with the screen-shoot because the system is freezing 
kindly your support 
my regards 
"	astrokinght
19480	VirtualBox freezes when Windows 7/10 guests reboot/reset after restoring online snapshots if GA is installed	Windows	VirtualBox 6.1.4	2020-04-12T06:34:06Z	2020-04-12T07:20:54Z	2020-04-12T07:20:54Z	"Host information:

- Arch Linux
- linux 5.6.3.arch1-1
- virtualbox 6.1.4-6
- virtualbox-guest-iso 6.1.4-1

Guest Information (both are reproducible)

- Windows 7 SP1
- Windows 10 LTSC 2019, Build Number 17763.1131

Steps to reproduce:

1. Cold boot the guest VM;
2. Take a online snapshot ""Snapshot 1"";
3. Shutdown the machine and restore to ""Snapshot 1"";
4. Boot the guest VM from ""Snapshot 1"" (directly into the Windows desktop);
5. Reboot/Reset the guest VM;
6. The VM resets, and shows a brief Windows Vista-style loading progress bar, and the VirtualBox (on host machine) freezes before crashing.

Notes:

- I have tried Windows 7 and Windows 10 guests (as decribed above), both are reproducible.
- If Guest Addition is not installed / uninstalled, the bug does not occur.
- If guest VM is cold booted (e.g. after step 4, instead of resetting/rebooting it, just shutdown and boot it), the bug does not occur.

Side note (may not relate to this bug):

After VB freezes/crashes, the RAM for guest VM is simply ""taken away"" from the host and cannot be recovered without a reboot of the host -- My host has 32 GB RAM, and each time a guest with 4 GB RAM crashes, there are 4 GB of RAM taken away from the host. After 7 crashes, 28 GB RAM are taken away from the host. I tried to shutdown Xorg server and there are only a few running processes left (none of them are VirtualBox), the host system still reports there are ~30 GB RAM used (top, htop, free... not cache/buffer, just ""used""). I have to reboot the host system to recover the RAM."	wzyboy
11862	VirtualBox freezes on btrfs / add check for COW	Windows	VirtualBox 4.2.12	2013-06-13T06:33:15Z	2019-06-26T07:52:50Z	2019-06-26T07:52:50Z	"On a linux machine with btrfs filesystem, installation of a guest goes just fine but at first restart the guest freezes with popup showing ""20%"" during launch phase.
Installing the same machine on XFS, no problems at all.
I've seen similar reports, but with slightly different behaviours and declared fixed.
host machine: linux 3.9.5 x86_64 (gentoo)
guests: W8/W7 64bit
attached: vbox.log of failed session"	Fabio Coatti
20433	Virtualbox freeze	Windows	VirtualBox 6.1.22	2021-06-28T08:31:13Z	2021-06-28T09:08:44Z	2021-06-28T09:08:44Z	"During working with VirtualBox and Windows 7, the guest freeze. Only by killing the process can solve the problem.

I attached the log."	anno
21177	VirtualBox for Linux - Enter doesn't work for Power off	all	VirtualBox-7.0.2	2022-10-21T12:22:35Z	2022-10-22T10:52:09Z	2022-10-22T10:52:09Z	"Under Linux press right Ctrl + Q, select ""Power Off the machine"", press ""Enter"" (on the keyboard), nothing will happen (the radio button will flash once).

The OK button seems to be bound to the radio list and cannot be activating using the keyboard.

That's a bug."	Artem S. Tashkinov
19477	Virtualbox fatal error while using DisplayLink	all	VirtualBox 6.1.4	2020-04-11T16:10:54Z	2020-04-11T16:10:54Z	2020-04-11T16:10:54Z	"Hi,

I hope you are well in this unprecedented situation and thank you for all your hard works in this crisis.

I recently started using Wavlink Universal USB 3.0 and install the driver from https://www.displaylink.com/downloads/ubuntu

Whenever I plug it to the laptop and run the Virtualbox with a normal user, it shows the error below:


{{{
Gdk-Message: 16:26:10.843: VirtualBox: Fatal IO error 0 (Success) on X server :0
}}}

and when I run it with root access:


{{{
Qt WARNING: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
Qt WARNING: The X11 connection broke: Maximum allowed requested length exceeded (code 4)
XIO:  fatal IO error 2 (No such file or directory) on X server "":0""
      after 681 requests (681 known processed) with 0 events remaining.
}}}

But when I disconnect the DisplayLink, it shows the UI and it works.

Here are the details of ubuntu:


{{{
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.4 LTS
Release:	18.04
Codename:	bionic
Linux 5.3.0-46-generic #38~18.04.1-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux
}}}"	navid_gh
20466	Virtualbox Extension Pack upgrade is unnecessarily convulted on Ubuntu	all	VirtualBox 6.1.24	2021-07-21T09:31:46Z	2021-07-21T09:31:46Z	2021-07-21T09:31:46Z	"after upgrading the VirtualBox installation I need to follow the the following dialogs/procedure to upgrade the Extension Pack:
1. You have an old version... click Download
2. Are you sure you want to download... click Download
3. Do you wish to install ... click Install
4. An older version is already installed... click Upgrade
5. PUEL license agreement... read license to the bottom, click I Agree
6. Authentication is needed... enter admin pass
7. Successfully installed... click OK
8. Do you want to delete ... click Delete
This is frankly annoying and unnecessary.

This should be reduced to:
1. You have installed a new version of VirtualBox. You need to upgrade the Extension Pack. If you wish to do it, accept the PUEL license by entering the admin password. The package will be downloaded, installed. The old package is unusable, thus will be deleted.

Thanks for considering the change!"	OM617
13407	VirtualBox Extension pack fails to install due to missing privileges	Windows	VirtualBox 4.3.16	2014-09-16T15:14:07Z	2015-08-03T03:15:45Z	2015-08-03T03:15:45Z	"I have tried upgrading the VirtualBox Extension Pack, but both removing the existing extension as well as adding a new one failed with my user privileges. The UI reported an error related to the SHELL variable instead of missing privileges and did not attempt to raise privileges (by asking for the password) to write to a directory.

See log for details:

{{{
00:03:16.930642 ExtPackInst ExtPack: Executing '/usr/lib64/virtualbox/VBoxExtPackHelperApp''install' '--base-dir' '/usr/lib64/virtualbox/ExtensionPacks' '--cert-dir' '/usr/lib64/virtualbox/ExtPackCertificates' '--name' 'Oracle VM VirtualBox Extension Pack' '--tarball' '/home/rbu/Downloads/Oracle_VM_VirtualBox_Extension_Pack-4.3.16-95972.vbox-extpack' '--sha-256' '93b01ac2c575388ea6ae994450907c24e30a788c271ae9ff18512a06f28d9abd'
00:03:16.955177 ExtPackInst ExtPack: enmReason=1 iStatus=127 stderr='The value for the SHELL variable was not found the /etc/shells file
00:03:16.955191 ExtPackInst 
00:03:16.955192 ExtPackInst This incident has been reported.
00:03:16.955194 ExtPackInst '
00:03:16.955231 ExtPackInst ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={3295e6ce-b051-47b2-9514-2c588bfe7554} aComponent={ExtPackManager} aText={The installer failed with exit code 127: The value for the SHELL variable was not found the /etc/shells file
00:03:16.955246 ExtPackInst 
00:03:16.955248 ExtPackInst This incident has been reported.}, preserve=false

}}}
"	rbu
21015	virtualbox does not load audio driver in guest win 10	Windows	VirtualBox 6.1.34	2022-07-02T00:25:49Z	2022-07-02T21:34:19Z	2022-07-02T21:34:19Z	"virtualbox does not load audio driver in guest win 10

Host: Ubuntu Mate 22.04 x64
Guest: Windows 10 Pro x64 21H2 19044.1766

"	mrvst
19992	VirtualBox does not install on Fedora 32	all	VirtualBox 6.1.16	2020-10-22T14:39:52Z	2020-10-28T14:36:49Z	2020-10-28T14:36:49Z	"uname -a: Linux master-1.fios-router.home 5.8.15-201.fc32.x86_64 #1 SMP Thu Oct 15 15:56:44 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Installed: kernel-devel.x86_64 ver 5.8.15-201.fc32
           kernel-headers.x86_64 ver 5.8.11-200.fc32
           VirtualBox-6.1.x86_64 ver 6.1.16_140961_fedora32-1
           gcc.x66_64 ver 10.2.1-5.fc32
All packages installed via dnf from the appropriate repositories.

vboxconfig fails. Log:
Building the main VirtualBox module.
Building the net filter module.
Building the net adaptor module.
Building the PCI pass-through module.
Error building the module:
make: *** No rule to make target 'install'.  Stop.

I suspect that the underlying cause is that the version of kernel-headers doesn't match the exact version of the kernel. However, the fedora-32 repositories don't contain a package named kernel-headers-5.8.15; kernel-headers-5.8.11 is the most recent. Any other info you need? Any suggestions?"	rws
11562	VirtualBox does not honour regular/shareable disks while cloning.	Linux	VirtualBox 4.2.6	2013-03-05T07:35:57Z	2013-03-05T07:35:57Z	2013-03-05T07:35:57Z	"Linked copy doesn't clone any disks. Full copy clones all disks, even when they are shareable. It would be cool to have third clone option, that clones all regular disks and uses shareable disks with the same properties and from the same location, like the source VM.
For example, it would be convenient for Oracle RAC emulation setup."	sknaumov
15547	Virtualbox destroy encrypted discs when delete online snapshots	Linux	VirtualBox 5.0.22	2016-06-26T15:20:55Z	2016-07-14T17:25:07Z	2016-07-14T17:25:07Z	"I tested this on several servers, and the results are 100% reproducible.

I found 3 ways to destroy the encrypted discs:

First:
 1. Encrypt the discs of an VM and start the S.O 
 2. Take a online snapshot
 3. Remove the snapshot with VM turned on.
 4. Restart the VM
=> The discs are destroyed and the S.O can't start.

Second:
 1. Encrypt the discs of an VM 
 2. Take a offline snapshot
 3. Start the VM
 4. Remove the snapshot with VM turned on.
 5. Restart the VM
=> The discs are destroyed and the S.O can't start.

Third:
 1. Encrypt the discs of an VM and start the S.O 
 2. Take a online snapshot
 3. Pause the VM
 4. Remove the snapshot with VM paused.
 5. Resume the VM
 6. Restart VM
=> The discs are destroyed and the S.O can't start.

I was tried to find a way to make a automatic backup of an encrypted VM, without need the save the key on the backup script to start vm again, and hard crash the discs off the VM.

The log of the VM on the first case as attached, and a screenshot of it after the restart.

It was tested with the last 5.0.22 VirtualBox Release and I dont found other tickts about this defect.

Thanks for you guys that develop this great program.  "	Law
19897	Virtualbox depends on deprecated pyhton version	Windows	VirtualBox 6.1.14	2020-09-18T15:16:08Z	2020-10-23T09:35:53Z	2020-10-23T09:35:53Z	"Debian testing can't install the current python version 2.7.18 without deinstall Virtualbox.
The installed virtualbox packet is 6.1.14-140239~Ubuntu~eoan.
It is planned to update the python dependancies to the current versions?

--------------- snip -------------------------------------
axel@graf-zahl:~$ apt-get -s dist-upgrade
HINWEIS: Dies ist nur eine Simulation!
         apt-get benötigt root-Privilegien für die reale Ausführung.
         Behalten Sie ebenfalls in Hinterkopf, dass die Sperren deaktiviert
         sind, verlassen Sie sich also bezüglich des reellen aktuellen
         Status der Sperre nicht darauf!
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.       
Statusinformationen werden eingelesen.... Fertig
Paketaktualisierung (Upgrade) wird berechnet... Fertig
Die folgenden Pakete wurden automatisch installiert und werden nicht mehr benötigt:
  libpython-stdlib libsdl-ttf2.0-0 python-minimal
Verwenden Sie »apt autoremove«, um sie zu entfernen.
Die folgenden Pakete werden ENTFERNT:
  python virtualbox-6.1
Die folgenden Pakete sind zurückgehalten worden:
  libpython2-stdlib python2 python2-minimal
0 aktualisiert, 0 neu installiert, 2 zu entfernen und 3 nicht aktualisiert.
Remv virtualbox-6.1 [6.1.14-140239~Ubuntu~eoan]
Remv python [2.7.16-1]
axel@graf-zahl:~$ 
--------------- snap -------------------------------------
"	DanielDuesentrieb
18843	VirtualBox crashes with Skype and Windows 10 guest	Windows	VirtualBox 6.0.10	2019-08-16T08:27:29Z	2019-08-16T08:27:29Z	2019-08-16T08:27:29Z	"Ubuntu 18.04 Host

VirtualBox Version 6.0.10 r132072 (Qt5.9.5).

Sound works fine. Can watch Youtube and use ""Sound Recorder"".

Joining a conference call with Skype also works, everyone can hear each other.

Tried to set ICH AC97 driver (uninstall multimedia driver in Device Manager, reinstall guest additions, reboot) but could not get Windows 10 to recognize it.

VirtualBox window invariably disappears after anything from a few seconds up to around 5 minutes.

The issue is easy to reproduce.

The issue was taken up on forum before filing this ticket:

https://forums.virtualbox.org/viewtopic.php?f=7&t=94305

Attached same log here.  It was edited for privacy."	hapless_user
20107	VirtualBox crashes with hardened memory allocator Hardened Malloc on the host	all	VirtualBox 6.1.16	2020-12-29T12:53:04Z	2020-12-29T12:53:04Z	2020-12-29T12:53:04Z	"When using hardened memory allocator [https://github.com/GrapheneOS/hardened_malloc Hardened Malloc] on the host operating system Debian `buster` VBoxSVC crashes after arround 30 minutes even during inactivity.

{{{
A critical error has occurred while running the virtual machine and the machine execution should be stopped.

For help, please see the Community section on https://www.virtualbox.org or your support contract. Please provide the contents of the log file VBox.log, which you can find in the virtual machine log directory, as well as a description of what you were doing when this error happened. Note that you can also access the above file by selecting Show Log from the Machine menu of the main VirtualBox window.

Press OK to power off the machine.
}}}

VirtualBox VM log:

{{{
all OK
no more log entries for 30 minutes while VM is working OK
then the only new log additions are these:
00:18:45.237389 VirtualBoxClient: detected unresponsive VBoxSVC (rc=NS_ERROR_CALL_FAILED)
00:19:16.904964 VirtualBoxClient: detected working VBoxSVC (rc=NS_OK)
}}}

VBoxSVC.log

{{{
tail -f ~/.config/VirtualBox/VBoxSVC.log
}}}

{{{
all OK
no more log entries for 30 minutes while VM is working OK
no new log entry after crash
The log ends there after crash then becomes
~/.config/VirtualBox/VBoxSVC.log.1
}}}

Will a [https://www.virtualbox.org/wiki/Core_dump VirtualBox core dump] be required? Or something else? Is this a bug you would be interested in fixing or out of scope?

Hardened Malloc installed inside the VM is functional. Hardened Malloc on the host crashes VirtualBox after a while.

Could you please make VirtualBox compatible with Hardened Malloc?

VirtualBox compatibility with [https://github.com/GrapheneOS/hardened_malloc/issues/89#issuecomment-522236117 Hardened Malloc might be usable to reveal some memory corruption bugs] inside VirtualBox."	adrelanos
16765	Virtualbox crashes whit device in DFU mode attached to USB	Linux	VirtualBox 5.1.22	2017-05-17T23:12:20Z	2017-05-17T23:19:19Z	2017-05-17T23:19:19Z	"I work with a device that needs to be rebooted in DFU mode in order to be updated. This device is already connected to the VM with JTAG and UART connections through USB connectors. So far so good, I can see the devices, read data on serial port, list the devices using lsusb, udev rules are properly applied, everything works fine. My problem happens when I reboot the device and remove the jumper that puts the device in DFU mode. As soon as the device boots the VM freezes and goes to an Aborted state. 

I'm using Virtualbox + vagrant but I was also able to reproduce this issue using a pure Virtualbox machine. Issue is also reproducible with older versions of Virtualbox. Host runs on Ubuntu 14.04 and guests are Ubuntu 14.04 and Ubuntu 16.04.

I went through tutorials and forums posts trying to get it to work but I was not able to find a solution and I really need it working as it is a blocker to use virtual machines on my environment. 

Attached are Virtualbox log and core dump.   "	carlosavj
19691	Virtualbox crashes when not used	Windows	VirtualBox 6.1.10	2020-06-30T09:10:01Z	2020-06-30T09:26:45Z	2020-06-30T09:26:45Z	"I got several crashes, at seemlingly random time, but alwys when I was not working on gest, but on host.

Log is the same :
ShClipboard[95831]: segfault at 4 ip 00007f6cc00252c0 sp 00007f6cb2818d00 error 4 in VBoxSharedClipboard.so[7f6cc001e000+8000]
(same ip, sp and address in VBoxSharedClipboard for all crashes).
"	erwan
18090	Virtualbox crashes on taking a snapshot	Linux	VirtualBox 5.2.20	2018-10-31T12:32:55Z	2018-10-31T23:23:29Z	2018-10-31T23:23:29Z	"I've just installed ubuntu 18.04.1 64bit on VirtualBox 5.2.20.
The installation was the minimal version of ubuntu, everything else at default settings.
My host is Ubuntu 18.04.1 64 bit, too.

After the installation I ran update and upgrade.
I installed gcc, perl, make and build-essential.

Then I ran the guest additions.

The system runs stable and without problems so far. But if I try to make a snapshot, the machine crashes reproducably.
I'm taking the snapshot while the machine is running. The window closes and the state of the machine is changed to ""aborted"".
No snapshot is taken.

Here is the logfile:
https://pastebin.com/f1dqGkxV"	lhk
13720	Virtualbox Crashes in r600_dri.so Mesa Graphics Driver When Running Ubuntu Guest With Guest Additions Installed	Linux	VirtualBox 4.3.20	2014-12-27T22:25:00Z	2015-01-12T22:47:14Z	2015-01-12T22:47:14Z	"On installing guest additions on a Ubuntu 14.10 guest and rebooting, the guest and virtualbox crash immediately _after_ the _login_ screen (i.e. after entering the password and Unity starts setting itself up). Subsequently, every reboot crashes at the same point and only un-installation of the guest additions can work around the problem.

The crash is always reproducible. Debugging details including a coredump, stack trace and register information will be found attached to this bug report.

The system in question is running the 64 bit version of Virtualbox 4.3.20 (4.3.20-96996~Ubuntu~raring) on a 64 bit Ubuntu 14.04 system running kernel 3.8.1.

The system runs the free Radeon drivers. The card is an AMD Radeon Evergreen (REDWOOD) PCI ID: 1002:68c1 (Dell Mobility Radeon HD 5650).

I am using this PPA for the MESA drivers: https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers but the crash is reproducible with the stock Ubuntu 14.04 MESA drivers and has been for a while (see the next paragraph).

I have been seeing this problem over the last several (I'd say 3 or 4) iterations of Virtualbox as well as the last 2 iterations of the OS (Currently Ubuntu 14.04 but previously 12.04), and across a wide range of kernels.

Further debugging information (including a Stack Trace e.t.c.) is attached but here are the basics:

- The crash occurs due to Signal 11 in r600_dri.so
- Summary Segv Analysis:
{{{ 
Segfault happened at: 0x7f3ef00ed1bd <_mesa_MultiModeDrawArraysIBM+93>:        
mov    (%r15,%rbx,1),%esi
 PC (0x7f3ef00ed1bd) ok
 source ""(%r15,%rbx,1)"" (0x00000030) not located in a known VMA region (needed r
eadable region)!
 destination ""%esi"" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
}}}
- The kernel has the following traps message in its log after the crash:
{{{
ShCrOpenGL[24186]: segfault at 30 ip 00007ff0902eb1bd sp 00007ff0918afa80 error 4 in r600_dri.so[7ff09016e000+7b8000]
}}}

Exactly the same crash occurs with the most recent Guest Additions ""test build"" (Guest Additions, revision 97191), but with the same (un-updated) version of Virtualbox.

See attached files for further debugging information."	marete
17694	Virtualbox choppy sound issue with Genymotion on Linux	Linux	VirtualBox 5.2.10	2018-04-18T04:24:02Z	2018-04-20T08:49:21Z	2018-04-20T08:49:21Z	"There are known sound issues with Genymotion using Virtualbox since Virtualbox version 5.1x and newer, the audio becomes kind of choppy and the virtual machines have performing issues.

In Virtualbox 5.0.26 (up to 5.0.40 in my pc) it worked perfectly. After 5.1 the issue began.

I already tried setting all the audio combinations in Virtualbox (alsa and pulse with all available audio controllers) but the issue remains.

I have done this procedure https://www.virtualbox.org/wiki/AudioDebug and will be attaching a zip file containing the VBox.log file and 3 wav files."	pemartins
18669	Virtualbox causes a leak in cursors as reported by xrestop	Linux	VirtualBox 6.0.8	2019-05-23T03:49:50Z	2019-07-17T13:44:52Z	2019-07-17T13:44:52Z	"I am seeing ""cursors"" as reported by xrestop constanly increasing, which I believe is leading to a leak in X11 which slowly but surely eats up all memory, forcing me to restart.

This has been happening for at least all of the 6.0 branch of virtualbox, but maybe earlier.

After searching, I found a similar comment suggesting the same thing:

https://www.virtualbox.org/ticket/15892?cversion=0&cnum_hist=14#comment:14

I graphed it out over a day or so, and I could see that it was constantly increasing whenever I was using the VM, but remained stable otherwise (graph attached).  It never went down.

I've attached a small screenshot video (for whatever reason, it seems gnome screenshot didn't actually capture the cursor... but you can see the link highlighting and the cursors value constantly increasing).

I would note it happens only the cursor switch when *not* in capture mode (i.e., turn off mouse integration and you can switch the cursor as much as you like and it never increases on the host).  Maybe for someone skilled in the art that could help pinpoint which library this is related to?

I am currently running 6.0.8 on Fedora 30, but as mentioned it has been happening before that and the original bug was in the 5.1 series.

I've filed https://bugzilla.redhat.com/show_bug.cgi?id=1713162 too

"	iwienand
19957	Virtualbox can't co-exist with python3 on Ubuntu 20.10 (even though python2 is also installed)	other	VirtualBox 6.1.14	2020-10-10T18:31:05Z	2020-10-28T22:45:09Z	2020-10-28T22:45:09Z	"It seems that 20.10 defaults to python3 and wants to install python-is-python3, which pulls in the latest version of dh-python, which in turn can't co-exist with Oracle's Virtualbox-6.1 and wants to uninstall it.

I don't mind having _both_ python2 and python3 installed. But as of right now I can have either python-is-python3, and not be able to do a complete upgrade since virtualbox-6.1 will be uninstalled, or python-is-python2, in which case I cripple 20.10's python3 install, since I won't get dh-python and python-six.

Can the devs do something about this?

Faidros
"	Faidros
16446	Virtualbox can only use one core with isolcpus	Linux	VirtualBox 5.1.14	2017-02-03T11:16:19Z	2017-02-06T13:59:27Z	2017-02-06T13:59:27Z	"On our server we installed ''isolcpus'' to dedicate our cpus for special tasks. Unfortunately it is not possible to assign virtualbox for more than one core with 

{{{
taskset -c 4,5,6,7 VBoxManage starvm ""[vm_name]"" --type headless
}}}

If we start the virtual machine only with 

{{{
VBoxManage starvm ""[vm_name]"" --type headless
}}}

the virtual machine runs on core 0-3.

After we uninstalled isolcpus we can use ''taskset'' to assign certain cpus."	seide
15935	VirtualBox breaking Unity's Compiz Scale Plugin	Windows	VirtualBox 5.1.6	2016-09-15T15:09:13Z	2016-09-15T15:09:13Z	2016-09-15T15:09:13Z	"My setup: Ubuntu 16.04 host, Win8 64bit guest.

On the host when I enable the Compiz Scale plugin in CompizConfig Settings Manager and give it a window binding (say the top of the screen initiates the plugin) everything works except when Virtualbox is the active window. When Virtualbox is the active window it ""steals"" the mouse movement when moving to the top of the screen and leaves the desktop in a bad state. The scale plugin is now broken (it no longer triggers) until I manually switch to a different active application then re-initiate the scale plugin via the mouse at the top of the screen. After that it works fine again until I try to trigger it with VirtualBox being the active window. If, however, I press the host key (right ctrl in my case) before I move the cursor to the top of the screen it initiates the Scale plugin as expected.

On previous versions of VirtualBox this all worked. Not exactly sure what version this started happening in unfortunately.

This is quite hard to explain, but it is 100% reproducible on my machine. I've tried everything from clearing all gnome settings, clearing all compiz settings, etc.

Let me know if you need any more information."	shockwave
21476	Virtualbox 7.x wrong Guest Additions info at Runtime Information	Linux	VirtualBox-7.0.6	2023-02-08T15:29:10Z	2023-02-09T15:34:17Z	2023-02-09T15:34:17Z	"I noticed Virtualbox 7.x wrong Guest Additions info at Runtime Information. It is something i am seeing for a long time now (7.x and back 6.x).

    
{{{
sudo VBoxControl guestproperty enumerate
}}}


reports the right version though, but Machine -> Session Information -> Runtime Information' is reporting 6.0.0 r127566 for a long time now, in all my linux guests on linux hosts; no matter what kernel or linux version of Fedora i use or have used.
My windowsVM does report the right version btw.
There are no other GA files on the guest machines but 7.0.6"	Richard E van der Luit
21291	Virtualbox 7.04: Windows 11 guest hangs with hyper-V paravirtualization enabled	Windows	VirtualBox-7.0.4	2022-11-21T12:23:54Z	2023-02-11T00:15:35Z	2023-02-11T00:15:35Z	"Running Virtualbox 7.04 on a linux host (ubuntu 22.04). Machine is a laptop with an Intel Core i7-10510U CPU and Intel integrated graphics.

I am trying to use a Windows 11 guest.

If I set the paravirtualization interface to ""default"" or Hyper-V (which I guess is the default when windows 11 guest type is selected), then the Windows 11 guest hangs quite frequently. In fact, trying to start word is enough to systematically hang the guest OS. If I set the paravirtualization interface to KVM (which I guess is something that Win11 cannot talk to), then I have no hangs.

I do not know if this is relevant, but I have the latest Virtio drivers for paravirtualized SCSI and network interface installed in Windows.

Any clue?"	sercallegar
21233	VirtualBox 7.0.x 3D acceleration produces artifacts with Windows guest	Windows	VirtualBox-7.0.2	2022-11-02T15:09:49Z	2022-12-18T12:01:25Z	2022-12-18T12:01:25Z	"Using a Linux (manjaro) host with Intel Haswell graphics and X11 (not Wayland).

Just upgraded from 6.1 to 7.0 and tried to use a Windows 11 guest known to work well with 6.1.

- Initially the Windows 11 guest was not even starting;
- Disabling 3D acceleration made it start;
- Updating the Guest Additions allowed to re-enable 3D acceleration without boot failures however, there are all sort of visual artifacts and prominently, characters become unreadable.

I suspect this may be triggered by my specific graphics card or graphics stack."	sercallegar
21198	VirtualBox 7.0.2, Window 7 64bit guest, Linux host, 3D openGL not working with any video driver in guest additions	Windows	VirtualBox-7.0.2	2022-10-24T06:50:29Z	2022-10-24T06:50:29Z	2022-10-24T06:50:29Z	"I suppose this is a continuation of the problem that started with the driver re-write after 6.0. In 6.0 it used to work, in 6.1 it stopped, and in 7.0 there was an attempt to fix it but still not working.

3D OpenGL does not work at all in any software package. (Tried VBoxVGA, VMSVGA, all default to VBoxSVGA)

---------------
Host is Ubuntu 20.04 

output of glxinfo | grep 'version':

server glx version string: 1.4

client glx version string: 1.4

GLX version: 1.4

OpenGL core profile version string: 4.6.0 NVIDIA 470.141.03

OpenGL core profile shading language version string: 4.60 NVIDIA

OpenGL version string: 4.6.0 NVIDIA 470.141.03

OpenGL shading language version string: 4.60 NVIDIA

OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 470.141.03

OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

    GL_EXT_shader_implicit_conversions, GL_EXT_shader_integer_mix, 

---------------
DXDIAG output on Windows 7 64 bit guest:


Display Devices

          Card name: VirtualBox Graphics Adapter (WDDM)
       Manufacturer: Oracle Corporation
          Chip type: 
           DAC type: 
         Device Key: Enum\PCI\VEN_80EE&DEV_BEEF&SUBSYS_040515AD&REV_00
     Display Memory: 3583 MB
   Dedicated Memory: 2303 MB
      Shared Memory: 1279 MB
       Current Mode: 1920 x 1080 (32 bit) (60Hz)
       Monitor Name: Generic Non-PnP Monitor
      Monitor Model: unknown
         Monitor Id: 
        Native Mode: unknown
        Output Type: HD15
        Driver Name: VBoxDispD3D.dll,VBoxDX.dll,VBoxDX.dll
Driver File Version: 7.00.0002.4219 (English)
     Driver Version: 7.0.2.4219
        DDI Version: 11
       Driver Model: WDDM 1.0
  Driver Attributes: Final Retail
   Driver Date/Size: 10/19/2022 15:10:54, 411360 bytes
        WHQL Logo'd: Yes
    WHQL Date Stamp: 
  Device Identifier: {D7B78E0E-FDAF-11CF-6666-0724AFC2CA35}
          Vendor ID: 0x80EE
          Device ID: 0xBEEF
          SubSys ID: 0x040515AD
        Revision ID: 0x0000
 Driver Strong Name: oem49.inf:Model.NTamd64.6.0:VBoxVideo:7.0.2.4219:pci\ven_80ee&dev_beef
     Rank Of Driver: 00F82001
        Video Accel: 
   Deinterlace Caps: {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,X8R8G8B8) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY 
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,X8R8G8B8) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY 
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
       D3D9 Overlay: Not Supported
            DXVA-HD: Not Supported
       DDraw Status: Enabled
         D3D Status: Enabled
         AGP Status: Enabled

---------------

All the 3d CAD legacy programs I am trying to work, either default to software openGL or display nothing.

I tried running the openGL diagnostic program called glview from here https://realtech-vr.com/home/glview, it also displays the same behaviour (does not show anything but garbage).

All the legacy programs run fine on the same Windows 7 natively (non virtualised)

Any suggestions for a fix or a meaningful work around? Tnx.
"	tiras_dude_o
21448	VirtualBox 7 VM Freezes or UI glitches	Windows	VirtualBox-7.0.6	2023-01-30T15:54:14Z	2023-02-14T08:39:15Z	2023-02-14T08:39:15Z	"Using VirtualBox VM 7.0.6 (guest additions installed) with an Ubuntu 22.04 LTS host and Win 11 guest, with an nvidia RTX 3080 Ti (and attaching log).

If I use the above combination I get frequent VM freezes (even if I leave it for hours).  This happens regularly especially  when I launch a browser (both MS edge and firefox exhibited this behaviour). The only way to recover is with a ""power off"" of the VM.

I have read in the forums (second post here: https://forums.virtualbox.org/viewtopic.php?f=2&t=107371) that this happens with VB7 and the solution for it is to enable 3D acceleration in the settings. I do that and the VM stops freezing BUT ...

The UI is almost unusable as it is broken in multiple ways (even when switching transparency off): broken borders, broken backgrounds, flickering, fonts looks rough, buttons disappear, etc etc etc.  For example when I launch MS Office, I get an empty (white) panel and nothing else. This is certainly related to 3D acceleration as when I set a regedit key (DisableHardwareAcceleration to 1) to disable 3D hardware acc. for office 365, this starts working normally.  But the rest of the OS still suffers from the visual glitches.

Let me know if you require any more info.



"	Jean-Paul Ebejer
19496	Virtualbox 6.1.6 guest screen resize broken	Linux	VirtualBox 6.1.6	2020-04-15T21:42:27Z	2022-09-20T20:23:32Z	2022-09-20T20:23:32Z	"
The virtualbox 6.1.6 update seems to be okay, but if the matching guest additions is applied to the guest, the auto-resize or resize to any resolution is unavailable.  I applied guest additions to several hosts before discovering this issue, including Centos-6, Centos-7, Centos-8, kali linux, and OracleLinux-8.  Guests that have not gotten the update seem to be working fine.

Matt"	Wheaties
21116	VirtualBox 6.1.38 keeps crashing	Windows	VirtualBox 6.1.38	2022-10-02T18:40:21Z	1970-01-01T00:00:00Z	1970-01-01T00:00:00Z	"I frequently get my VirtualBox instance to crash. The OS the virtualbox guest is running is Windows 10. The host VirtualBox is running on is Fedora 35.

I've attached my logs like the gui pop-up requests."	Brad Walker
20277	VirtualBox 6.1.18 freezes when trying to start a Ubuntu installation from CD image	Linux	VirtualBox 6.1.18	2021-03-27T12:01:51Z	2021-03-29T05:33:31Z	2021-03-29T05:33:31Z	"Host:

vbox-cloud ➤ uname -a                                                          
Linux paag-EliteBook 5.4.0-70-generic #78-Ubuntu SMP Fri Mar 19 13:29:52 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

VirtualBox:

vbox-cloud ➤ vboxmanage --version                                              
6.1.16r140961

How to reproduce the *freeze*:

Define a VM with 4G RAM, 40G HDD (in fact anything that can run Ubuntu 20.04)
Define the VM to run with 2 vcpus (this is the critical stuff)
Attach the Ubuntu 20.04 live image to the CDROM in the VM
Boot the VM and watch it freeze VirtualBox
"	paaguti-u
19896	virtualbox 6.1.14 X Debian guest X keyboard X webcam X fullscreen VM	Linux	VirtualBox 6.1.14	2020-09-18T14:32:37Z	2020-09-22T14:57:56Z	2020-09-22T14:57:56Z	"Hello

I found a very strange issue on Virtualbox 6.1.14 running on Ubuntu 18.04 host, Debian GNU/Linux bullseye (testing) guest using Gnome 3.30 desktop (or KDE Plasma 5.17) and a Logitech HD webcam C270 on fullscreen VM.

If enable webcam device on virtualbox toolbar, the keyboard is lost.

It also happens with Debian GNU/Linux 10.5 buster VM.

BUT this problem does not happen when using windowed VM.

What additional info should I collect?

Regards.

Andre Felipe"	afmachado
19344	VirtualBox 6.1.14 install fails on RedHat family	other	VirtualBox 6.1.4	2020-02-24T11:29:57Z	2020-02-29T07:46:02Z	2020-02-29T07:46:02Z	"Can not install VirtualBox using the repository:

{{{
# cat /etc/yum.repos.d/virtualbox.repo
[virtualbox]
name=Yum Repository
baseurl=http://download.virtualbox.org/virtualbox/rpm/fedora/$releasever/$basearch
enabled=1
fastestmirror_enabled=0
gpgcheck=1
gpgkey=https://www.virtualbox.org/download/oracle_vbox.asc

#  dnf install -y VirtualBox-6.1
[...]
Error: Transaction test error:
  file /usr/bin/VBox conflicts between attempted installs of VirtualBox-6.1-6.1.4_136177_fedora31-1.x86_64 and VirtualBox-5.2-5.2.38_136252_fedora29-1.x86_64
[...]
}}}

The same problem appears with several distros (Fedora 30, Fedora 29, CentOS 7.7) and with several versions of the package (VirtualBox-6.1-6.1.4, VirtualBox-6.1-6.1.2, VirtualBox-6.0-6.0.18)

Looks like VirtualBox-5.2 is attempted to be installed alongside VirtualBox-6.x, as a dependency, and both packages clashes.

Seems very similar to issue #18924"	luisg.muniz
19860	VirtualBox 6.1.13 (testbuild) tiggers BLUE SCREEN on Windows when UAC Required	Windows	VirtualBox 6.1.10	2020-09-04T16:21:32Z	2020-09-04T16:21:32Z	2020-09-04T16:21:32Z	"Host: Archlinux with Linux 5.8.5
VirtualBox: 6.1.13 testbuild (build=139989, sdkbuild=139990)
Guest: Windows 7 32-bit (run headless, accessed via rdesktop)
Guest Additions: version=6.1.13-139990

Blue Screen is triggered each time User Account Control Activated to allow changes to windows.

This problem seems to be triggered by Windows 7 User Account Control (UAC). I can't even install simple updates to PuTTY, etc. without 6.1 causing a BLUE screen and reboot. This is triggered any time you are prompted to allow a change to your computer with UAC. The UAC dialog is displayed and the remainder of the screen is darkened. After choosing ""Yes"" to allow the change, the darken background is not removed from any open windows and about 5 seconds later BLUE SCREEN, and the Virtualbox 6.1 reboot screen is shown. 

This will occur if you simply attempt to start the command prompt with ""Run As Administrator"". I have 3 Minidumps collected if needed and the Event Viewer reports the critical error as ""Kernel Power"" (which doesn't look very useful)

As a test, I disabled UAC completely and attempted the updates to PuTTY again. With UAC disable, there is no problem. I can update software as normal without the Blue Screen on 6.1. So the bug in 6.1 causing the BLUE SCREEN crash is triggered any time elevated privileges are needed and UAC is activated. 

I have run this same VM for 5+ years and never had any problem with the 5.1 or 5.2 Virtualbox branches. There is something new in 6.1 that triggers a crash when Windows UAC is activated. 

Let me know if the Minidumps will be of any use or if there is other documentation I can provide and I'm happy to attach them.
"	drankinatty
19429	VirtualBox 6.1 + Whonix 15 = Aborted	Linux	VirtualBox 6.1.4	2020-03-24T18:12:00Z	2020-04-12T14:15:03Z	2020-04-12T14:15:03Z	"Hello everyone! I have been using Whonix 14 for a long time and everything have been working fine but unfortunately I need some soft as libreoffice which I can't download there because Whonix 14 isn't supported. I had to upgrade it. I should note that I used VirtualBox 5.3 with Whonix 14. I decided to make new one from scratch. Downloaded Whonix 15 and import it. I faced with the problem that clipboard didn't work. I decided download new version of VirtulBox = 6.1 This is solved the problem with clipboard but I faced with the bigger problem instead . Now after some time (different time ) VM just close without any reason and in main window of virtulbox I see the title ""Aborted"" . I have several VMs (Whonix 15, Whonix 15, Whonix 14) which usually work together (multiply workstation) and what is strange that one of them work normal (whonix 15) but the other two often crash together in one time. The difference between two whonix 15 is that in one installed psi+ v0.16 . I paid attention to version on psi+ special because it's the version for jessie, some plugins in it work better than in new one. Maybe is that the reason? One more thing I want to note is that I am not cloned first Workstation 15 when I made second Workstation 15 , I just imported all machines again from OVA and then delete second gateway which I didn't need , leaving the second workstation 15.

Info about host

System:    Host: user Kernel: 4.15.0-91-generic x86_64 bits: 64 gcc: 7.4.0
           Desktop: Cinnamon 3.8.9 (Gtk 3.22.30-1ubuntu4) dm: lightdm Distro: Linux Mint 19 Tara
CPU:       Quad core Intel Core i7-8550U (-MT-MCP-) arch: Kaby Lake rev.10 cache: 8192 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 15936
           clock speeds: min/max: 400/4000 MHz 1: 1900 MHz 2: 1900 MHz 3: 1900 MHz 4: 1900 MHz
           5: 1900 MHz 6: 1900 MHz 7: 1900 MHz 8: 1900 MHz
Graphics:  Card-1: Intel UHD Graphics 620 bus-ID: 00:02.0 chip-ID: 8086:5917
           Card-2: NVIDIA GP108M [GeForce MX150] bus-ID: 01:00.0 chip-ID: 10de:1d12
           Display Server: x11 (X.Org 1.19.6 ) drivers: modesetting,nouveau (unloaded: fbdev,vesa)
           Resolution: 1920x1080@60.05hz
           OpenGL: renderer: Mesa DRI Intel UHD Graphics 620 (Kabylake GT2)
           version: 4.5 Mesa 19.2.8 (compat-v: 3.0) Direct Render: Yes
Audio:     Card Intel Sunrise Point-LP HD Audio driver: snd_hda_intel bus-ID: 00:1f.3 chip-ID: 8086:9d71
           Sound: Advanced Linux Sound Architecture v: k4.15.0-91-generic
Partition: ID-1: / size: 901G used: 452G (53%) fs: ext4 dev: /dev/dm-1
           ID-2: /boot size: 705M used: 368M (57%) fs: ext4 dev: /dev/nvme0n1p2
           ID-3: swap-1 size: 17.02GB used: 0.70GB (4%) fs: swap dev: /dev/dm-3"	CatJump
18619	VirtualBox 6.0.6 VM guest boot hangs with customized Fedora 30 Remix	Linux	VirtualBox 6.0.6	2019-05-03T20:32:07Z	2019-05-03T21:46:33Z	2019-05-03T21:46:33Z	"I am creating a customized 64bit Fedora 30 Remix called Untochat. It is a Live Linux that allows you to install to harddisk, too. Live image boots fine with VirtualBox and installation to (virtual) VDI disks succeeds as well. But when booting the newly installed Untochat9 from disk, the boot never reaches graphical login screen.

The problem is deterministic, but I am unable to debug this myself. To reproduce the problem, Untochat ISO image (1.4GB) can be downloaded from:

  https://kolttonen.fi/iso/untochat9.iso

My main host is stock Fedora 30, but the same problem occurs on host MacOS Mojave 10.14, too.

Using libvirt + qemu + kvm on Fedora 30 host, everything works fine, so I suspect this could be a bug in VirtualBox 6.0.6. "	KaleviKolttonen
19084	Virtualbox 6.0.12 crash when running Windows guest	Windows	VirtualBox 6.0.12	2019-11-14T00:43:05Z	2019-11-14T00:43:05Z	2019-11-14T00:43:05Z	"Hi I build Virtualbox from source against custom Linux kernel 4.19.72

	./configure  --build-headless --build-libxml2 --enable-vnc --disable-hardening --disable-docs \
	 --disable-udptunnel --disable-devmapper --disable-dbus --disable-alsa --disable-pulse --disable-java \
	--with-linux=/root/linux-stable

and I got the following crash when running Windows7 VM

00:00:00.199497 SUP: Loaded VMMR0.r0 (/usr/lib/virtualbox/VMMR0.r0) at 0xXXXXXXXXXXXXXXXX - ModuleInit at XXXXXXXXXXXXXXXX and ModuleTerm at XXXXXXXXXXXXXXXX
00:00:00.199566 SUP: VMMR0EntryEx located at XXXXXXXXXXXXXXXX and VMMR0EntryFast at XXXXXXXXXXXXXXXX
00:00:00.208481 
00:00:00.208484 !!Assertion Failed!!
00:00:00.208485 Expression: pVM->offVMCPU == RT_UOFFSETOF(VM, aCpus)
00:00:00.208488 Location : /root/trunk/3rd/src/VirtualBox-6.0.12/src/VBox/VMM/VMMR3/VM.cpp(595) int vmR3CreateU(PUVM, uint32_t, PFNCFGMCONSTRUCTOR, void*)
00:00:00.208528 Stack :
00:00:00.208530 00007f1fc0df12b4 VBoxRT.so + 0x1832b4


Would you please tell me what may be wrong for pVM->offVMCPU == RT_UOFFSETOF(VM, aCpus) ?

thanks
rob"	robhuang
18890	VirtualBox 6.0.10, VM window - black color gets transparent with Xwayland	all	VirtualBox 6.0.10	2019-09-01T18:55:38Z	2019-09-01T18:55:38Z	2019-09-01T18:55:38Z	"Hello,

I'm running VirtualBox 6.0.10 on Gentoo Linux with Xwayland as native Wayland support for VBox is not ready yet. When any VM starts in windowed mode everything that is black in that VM gets transparent (other colors are semi-transparent, if not white). When VM goes full screen the issue mostly disappears - sometimes black fonts get transparent. Changing graphics adapter type in VM settings, toggling 2D/3D acceleration and installing VM guests doesn't change anything."	Hubert Kromer
18808	VirtualBox 6.0.10 Segmentation fault in openSUSE 13.2	other	VirtualBox 6.0.10	2019-08-03T06:43:53Z	2019-08-03T06:43:53Z	2019-08-03T06:43:53Z	"VirtualBox 6.0.10 has segmentation fault in openSUSE 13.2, immediately on startup.[[BR]]
VirtualBox-6.0-6.0.10_132072_openSUSE132-1.x86_64.rpm[[BR]]

Syslog shows:[[BR]]
ug 03 12:16:11 trinity.cgl kernel: UINetworkReplyP[7796]: segfault at 7f4a3a4d1550 ip 00007f4a02fba22e sp 00007f4a03ffe328 error 7 in libkdecore.so.5.14.9[7f4a02f1b000+2b3000][[BR]]
Aug 03 12:18:43 trinity.cgl kernel: UINetworkReplyP[7903]: segfault at 7fa643541550 ip 00007fa62059222e sp 00007fa6217f9328 error 7 in libkdecore.so.5.14.9[7fa6204f3000+2b3000][[BR]]
Aug 03 12:21:23 trinity.cgl kernel: UINetworkReplyP[8062]: segfault at 7f0b1d4f9550 ip 00007f0aef24222e sp 00007f0b048e9328 error 7 in libkdecore.so.5.14.9[7f0aef1a3000+2b3000]

user@trinity:/usr/lib64> rpm -qi  libkdecore4-4.14.9-27.1.x86_64[[BR]]
Name        : libkdecore4[[BR]]
Version     : 4.14.9[[BR]]
Release     : 27.1[[BR]]
Architecture: x86_64[[BR]]
Install Date: Sat 20 Feb 2016 12:32:55 PM SGT[[BR]]
Group       : System/GUI/KDE[[BR]]
Size        : 3034361[[BR]]
License     : LGPL-2.1+[[BR]]
Signature   : RSA/SHA256, Tue 26 Jan 2016 06:53:58 PM SGT, Key ID b88b2fd43dbdc284[[BR]]
Source RPM  : kdelibs4-4.14.9-27.1.src.rpm[[BR]]
Build Date  : Tue 26 Jan 2016 06:46:52 PM SGT[[BR]]
Build Host  : cloud107[[BR]]
Relocations : (not relocatable)[[BR]]
Packager    : http://bugs.opensuse.org[[BR]]
Vendor      : openSUSE[[BR]]
URL         : http://www.kde.org[[BR]]
Summary     : KDE Core Libraries[[BR]]
Description :[[BR]]
This package contains the core libraries of the K Desktop Environment.[[BR]]

This package is absolutely necessary for using KDE applications.[[BR]]
Distribution: openSUSE 13.2[[BR]]
user@trinity:/usr/lib64>[[BR]]

Version 6.0.8 seems to be working fine and I am now using it, having removed version 5.2.0 which i was using previously.[[BR]]

This issue is probably identical to the one identifed in Ticket #18767:[[BR]]
https://www.virtualbox.org/ticket/18767"	CHIN_Gim_Leong
18767	VirtualBox 6.0.10 segfaults at startup on CentOS 7.6	other	VirtualBox 6.0.10	2019-07-18T01:08:56Z	2019-07-26T14:41:50Z	2019-07-26T14:41:50Z	"{{{
> VirtualBox
Segmentation fault
>
}}}
Kernel logs this:

UINetworkReplyP[15063]: segfault at 2ad601cd1550 ip 00002ad629dc4f7e sp 00002ad6296ee2f8 error 7 in libkdecore.so.5.14.8[2ad629d20000+2b9000]

My understanding is that 6.0.10 now somehow manages to load libkdecore.so.5.14.8 which is from KDE4. (I'm not using KDE4, I just have some KDE programs installed.)

First guess is it's triggered from here:

[https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Frontends/VirtualBox/src/net/UINetworkReply.cpp]

Downgrading to 6.0.8 makes Virtualbox work again."	gottschalk_maria
18304	VirtualBox 6.0 crashes on Ubuntu 18.10	other	VirtualBox 6.0.0	2019-01-11T21:15:19Z	2019-01-12T21:05:58Z	2019-01-12T21:05:58Z	"VirtualBox 6.0 crashes immediately after launching on fresh Ubuntu 18.10 host (ASUS N551JW laptop)

{{{
$ virtualbox
Gdk-Message: 21:32:35.060: VirtualBox: Fatal IO error 2 (No such file or directory) on X server :0.

$ sudo virtualbox
Qt WARNING: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
Qt WARNING: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
Qt WARNING: The X11 connection broke: Maximum allowed requested length exceeded (code 4)
XIO:  fatal IO error 2 (No such file or directory) on X server "":0""
      after 612 requests (612 known processed) with 0 events remaining.
}}}

My installation process:

{{{
wget -q https://www.virtualbox.org/download/oracle_vbox_2016.asc -O- | sudo apt-key add -
wget -q https://www.virtualbox.org/download/oracle_vbox.asc -O- | sudo apt-key add -
sudo add-apt-repository ""deb [arch=amd64] http://download.virtualbox.org/virtualbox/debian $(lsb_release -cs) contrib""
sudo apt-get update
sudo apt-get install virtualbox-6.0 -y
}}}
"	kipc
18609	VirtualBox 6 feels/runs/works a lot slower than VirtualBox 5.2	all	VirtualBox 6.0.6	2019-04-28T06:15:29Z	2019-04-28T06:15:29Z	2019-04-28T06:15:29Z	"I wonder why VirtualBox 6.0 is quite slower than VirtualBox 5.2 in many regards:

* it's a lot slower to launch: VBox 5.2 launches pretty much instantly, 6.0 takes 2-3 seconds.
* it takes additional time to launch guest OSes: I see no delay in VBox 5.2, while 6.0 takes a second or two.

My hardware:
 * SSD disk 500MB/sec read/write (it doesn't even matter, since consecutive launches impose the same delays when everything is cached)
 * 16GB DDR3 800MHz RAM in dual channel mode
 * Intel Core i5 2500
 * OS: Fedora 30 with XFCE, without any fancy features like desktop compositing. I also see the same slowness under CentOS 6.x x86_64."	Artem S. Tashkinov
17322	VirtualBox 5.2.x guest additions hang Poser 6 & 7 on startup under XP guest	Windows	VirtualBox 5.2.0	2017-11-28T15:51:27Z	2017-11-28T15:51:27Z	2017-11-28T15:51:27Z	"I already reported this issue under [https://www.virtualbox.org/ticket/17152 Ticket #17152] (for 5.2RC), but 5.2.0 was released shortly after and it looks like that ticket got overlooked/ignored entirely, so I'm opening a new ticket for VirtualBox v5.2, since the bug is still there...

With VirtualBox v5.2.2 and its extension pack installed, and after booting my Windows XP guest VM (with corresponding v5.2.2 guest additions installed), when I start Poser 6 or 7 (the only two versions I got) on a Windows XP (32 bits) guest running on a 64 bits Linux host, the program hangs shortly after starting, on the startup screen, and Windows reports the program as ""non responding"" in its title bar. After a few more seconds waiting, the window of the program turns white and it stays stuck forever like that.

If I reinstall the v5.1.30 guest additions (still keeping VirtualBox v5.2.0 and its extension pack) Poser then works fine again.

Probably an issue in DirectX support ?
"	dinosaur0
17414	Virtualbox 5.2.4 crashed	Windows	VirtualBox 5.2.4	2018-01-03T14:28:41Z	2018-01-03T14:28:41Z	2018-01-03T14:28:41Z	"On Fedora 27 with:

VirtualBox-5.2-5.2.4_119785_fedora26-1.x86_64

a crash has occurred. The logs and gdb info of the core are attached."	Panos Kavalagios
18429	VirtualBox 5.2.26 fails to build due to VBoxFUSE	Linux	VirtualBox 5.2.26	2019-02-11T16:39:36Z	2019-02-12T10:57:52Z	2019-02-12T10:57:52Z	"Hello,

I'm using a fairly ancient system (Slackware 14.2), but the following is a bug I encountered building VirtualBox, and a patch that enabled me to build it successfully.

While trying to compile, I encountered this error:

{{{
  CXX     VBoxFUSE - {C}/VBoxFUSE.cpp
/tmp/SBo/VirtualBox-5.2.26/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp:112:5: error: 'PVBOXHDD' does not name a type
     PVBOXHDD                pDisk;
     ^
/tmp/SBo/VirtualBox-5.2.26/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp: In function 'bool vboxfuseNodeDestroy(PVBOXFUSENODE, bool)':
/tmp/SBo/VirtualBox-5.2.26/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp:200:29: error: 'VBOXFUSEFLATIMAGE {aka struct VBOXFUSEFLATIMAGE}' has no member named 'pDisk'
             if (pFlatImage->pDisk)
                             ^
}}}

After searching through the source code, and scouring the internet, I could not find a reference to '''PVBOXHDD''' anywhere.

Finally I found a very old copy of vdfuse ([https://github.com/vasi/vdfuse/blob/7e10fc7aeeffae251042055bc55fb83a09120156/include/VBox/vd.h]) which defined '''PVBOXHDD''' as '''VBOXHDD''', and I found further details that revealed '''VBOXHDD''' could be referenced here as '''PVDISK'''.

I created the following patch:

{{{
--- /tmp/SBo/VirtualBox-5.2.26/src/VBox/ImageMounter/VBoxFUSE-old/VBoxFUSE.cpp      2018-10-15 10:31:04.000000000 -0400
+++ /tmp/SBo/VirtualBox-5.2.26/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp   2019-02-11 11:31:30.587919884 -0500
@@ -53,6 +53,7 @@
 #include <iprt/initterm.h>
 #include <iprt/stream.h>
 
+#define PVBOXHDD PVDISK
 
 /*********************************************************************************************************************************
 *   Structures and Typedefs                                                                                                      *
}}}

And upon continuing my build, it succeeded."	peterwwillis
18091	virtualbox 5.2.20 fails to compile with glibc 2.26 because xlocale.h was removed	all	VirtualBox 5.2.20	2018-10-31T13:51:06Z	2018-10-31T13:51:06Z	2018-10-31T13:51:06Z	"As of glibc 2.26 the file xlocale.h is no longer provided as it was never intended to be there as it's a subset of locale.h

see also this article: https://ahelpme.com/linux/compiling/glibc-2-26-and-failure-to-compile-because-of-xlocale-h/

please fix source code so no awkward symnlinks are necessary in order to build Virtualbox."	marcelser
17377	VirtualBox 5.2.2 issues on Xubuntu 16.04 x64	Linux	VirtualBox 5.2.2	2017-12-18T18:36:47Z	2017-12-21T09:45:06Z	2017-12-21T09:45:06Z	"Hi,

Last night I uninstalled VirtualBox 5.1.30 from my Xubuntu 16.04 x64 system, deleting all relative files and I did a brand new 5.2.2 installation from scratch. The new installation is facing two issues:

1. It doesn't use the system GTK theme whereas 5.1.30 did. All other GTK, QT4 and QT5 apps do use it, since the system is correctly configured for this.

2. Shared folder auto-mount doesn't work on Xubuntu 16.04 x64 guests whereas it works fine on Windows guests. On Xubuntu guests I have to mount it manually using ""mount -t vboxsf -o uid=1000,gid=1000 shareName /media/sfPublic"". This command mounts it correctly with read/write access.

Thank you.

p.s. The guest additions have been installed of course, using ""sh ./VBoxLinuxAdditions.run""."	StormLord
17987	VirtualBox 5.2.18 vulnerable to spectre/meltdown despite microcode being installed	Linux	VirtualBox 5.2.18	2018-09-13T13:30:33Z	2021-01-04T18:10:22Z	2021-01-04T18:10:22Z	"'''How to reproduce:'''

A host running Debian stretch.
Using VirtualBox version 5.2.18.
A guest running Debian stretch.

Host using stretch-backports with get access to newer microcode. (Old versions are incapable to show spectre/meltdown fixed.)

spectre-meltdown-checker being installed on host and in guest from stretch-backports. (Old versions are incapable to show spectre/meltdown fixed.)

{{{
sudo su -c ""echo -e 'deb http://http.debian.net/debian stretch-backports main contrib non-free' > /etc/apt/sources.list.d/backports.list""
}}}
{{{
sudo apt-get update
}}}
{{{
sudo apt-get -t stretch-backports install spectre-meltdown-checker
}}}

Suppose microcode being installed.

Intel:

{{{
sudo apt-get -t stretch-backports install intel-microcode
}}}

Amd:

{{{
sudo apt-get -t stretch-backports install amd64-microcode
}}}

Suppose running spectre-meltdown-checker on the host looks fine.

{{{
sudo spectre-meltdown-checker --paranoid ; echo $?
}}}

By fine I mean exit code 0 and not showing ""vulnerable"".

Suppose using all VirtualBox spectre/meltdown defense options.

{{{
VBoxManage modifyvm vm-name --ibpb-on-vm-entry on
}}}
{{{
VBoxManage modifyvm vm-name --ibpb-on-vm-exit on
}}}
{{{
VBoxManage modifyvm vm-name --spec-ctrl on
}}}
{{{
VBoxManage modifyvm vm-name --l1d-flush-on-sched off
}}}

(These options were introduced in VirtualBox version 5.2.18.)

'''Expected result:'''

spectre-meltdown-checker in guest VM saying ""all fine"".

{{{
sudo spectre-meltdown-checker --paranoid ; echo $?
}}}

By fine I mean exit code 0 and not showing ""vulnerable"".

'''Actual result:'''

spectre-meltdown-checker reporting vulnerable.

'''Questions:'''

Can you reproduce the same issue?

Were all necessary steps performed to protect the guest from spectre/meltdown?

Is this a VirtualBox issue or false-positive in spectre-meltdown-checker?

([https://forums.virtualbox.org/viewtopic.php?f=7&t=89395 Previously posted in VirtualBox forum].)"	adrelanos
17226	Virtualbox 5.2 crashed	Windows	VirtualBox 5.2.0	2017-10-31T09:28:17Z	2017-10-31T09:28:17Z	2017-10-31T09:28:17Z	The VM has crashed. The log and dump information are attached.	Panos Kavalagios
16021	VirtualBox 5.1.x on Windows 2012 and Windows 2016 do not guest additions.	Windows	VirtualBox 5.1.6	2016-10-03T18:13:11Z	2016-10-25T13:17:56Z	2016-10-25T13:17:56Z	"Извините, что на русском. Вообщем проблема такая: В качестве хостовой машины - Ubuntu 16.04. Запускаю серверные платформы - Windows 2012 Standard и Windows 2016 Standard. Устанавливаю гостевые дополнения - все ставится, но после перезагрузки - сервис запускается, а вот програмка VBoxTray.exe стартует, висит 1-2 минуты и выгружается.
Взял из старых дополнений (от VirtualBox 5.0.26) VBoxTray.exe и заменил им новую, и все заработало. Но это конечно не правильно.
Интиересно, что у меня есть образ Windows 2012 с SQL 2008. Вот в нем работает и от VirtualBox 5.1.6.
Что нужно для нормальной работы дополнений?"	Sergey
16120	VirtualBox 5.1.8r111374 aborts Debian guest after random period - NAT?	Linux	VirtualBox 5.1.8	2016-10-26T21:56:41Z	2016-11-22T08:28:23Z	2016-11-22T08:28:23Z	"I have a Debian Jessie guest running on a Arch host. After a seemingly random period of time, the guest will transition to the ""aborted"" state. I am yet to observe it happening, I normally notice after I find my VirtualBox guest has disappeared after a few hours. 

I think it's possible that this is associated with an older ticket. Sorry if I have not formatted this ticket correctly, this is my first time doing so.

I will provide any information you require, please ask.



"	sam.4325224
15830	virtualbox 5.1.4 on debian 8 crashed while plugging/unplugging usb phone in flashing mode	Windows	VirtualBox 5.1.4	2016-08-19T19:52:42Z	2016-08-19T20:11:58Z	2016-08-19T20:11:58Z	"my virtualbox Version 5.1.4 r110228 (Qt5.3.2)
 on debian 8 crashed while plugging/unplugging usb phone in flashing mode. Here is the log:


"	tim43263246
16883	Virtualbox 5.1.22 crashes ethernet card on Ubuntu 16.04 64bit	Linux	VirtualBox 5.1.22	2017-07-07T13:53:10Z	2017-07-26T13:13:51Z	2017-07-26T13:13:51Z	"I have a stock install of Ubuntu 16.04 64bit (Unity desktop) on my laptop.
As an addition there is virtualbox 5.1.22 installed from official Oracle repository and vagrant 1.9.5.

Whenever I start any virtual machine ethernet card just crashes.

Steps to reproduce:

mkdir -pv ~/foo
cd ~/foo
vagrant init bento/ubuntu-16.04
vagrant up

"	kiklop74
16265	Virtualbox 5.1.10 on Ubuntu 6.10 running on Mac Pro 3,1 incorrectly assumes hyperthreading	all	VirtualBox 5.1.10	2016-12-05T01:43:20Z	2016-12-05T11:31:42Z	2016-12-05T11:31:42Z	"When running the Oracle 5.1.10 deb of Virtualbox-5.1 (5.1.10) on Ubuntu 6.10 installed on a MacPro 3,1 running on Harpertown processors, the Processor tab incorrectly assumes that Hyperthreading is available on that processor and shows 16 CPUs being available on a dual quad-core system.

"	howarth
14323	Virtualbox 5.0: Blackscreen in fullscreen mode with i3wm host.	all	VirtualBox 5.1.4	2015-07-24T15:54:29Z	2020-11-19T13:25:26Z	2020-11-19T13:25:26Z	"Hello,

ISSUE:
It seems that VirtualBox update don't handle the fullscreen mode when host is using i3wm as Window manager. When hitting host+F keys, the screen become black and the only way to go back is to click icon on the bottom bar (Host+F was not responding when in fullscreen mode).

INVESTIGATION:
The issue was not present on the last virtualbox update (4.3.24 on ArchLinux). To be sure that the problem came from the window manager, I launched virtualbox on the same machine using XFCE as window manager and everything was fine. 
I have tested it with multiple VMs: Slitaz, Debian 8, Windows server 2012, Windows 7. Each time with updated guest additions tools.
"	y0no
14629	VirtualBox 5.0.4-102546~Unbuntu~trusty Crashes when running more then 2 Windows Vm's	Windows	VirtualBox 5.0.4	2015-09-23T22:53:02Z	2015-09-25T13:59:57Z	2015-09-25T13:59:57Z	When running multiple Windows Vm's at the same time the system will become unresponsive requiring a physical restart. disk usage appears to spike.    	skiingshark
15092	virtualbox 5.0.14 linux host failed seamless mode with windows 10 guest	Windows	VirtualBox 5.0.14	2016-01-29T17:55:51Z	2021-07-28T17:04:02Z	2021-07-28T17:04:02Z	"Windows 10.0.10586 guests run perfectly well in windowed and full screen modes but not in seamless mode. The command to enter seamless works, but after the window disappears as if entering seamless mode, it switches to one similar to  full screen with a transparent band at the top showing the Linux desktop.  
Windows 7 works perfectly in all modes. I've observed the same behavior in every release of VB5 and W10 I've tried starting at 5.0.1. I've tried changing compositing between OpenGL and Xrender on the host, enabling and disabling 3D and 2D on the guest, nothing helps.

This may not be a critical bug, but it keeps me using w7 guests for real work--seamless mode is key.

The host runs an AMD-FX-9370 CPU, GeForce GTX 960, 32GB RAM, NVidia 361.18 drivers, Linux kernel 4.4, Mint 17.3 KDE with X server 1.17.1. 

I've attached the latest log showing startup and switches between modes.
"	matthewls
14280	VirtualBox 5.0 regression: full screen mode with composite manager works incorrectly	Windows	VirtualBox 5.0.0	2015-07-15T01:02:45Z	2015-07-15T12:35:15Z	2015-07-15T12:35:15Z	"Just upgraded to VirtualBox 5.0 (host: Ubuntu 14.04 amd64, guest: Windows).
Relevant extension pack and guest additions installed.

PROBLEM:
When switching to full screen mode, the VM screen resizes all right to fill the screen,
but the screen is dimmed (brightess is reduced). Looks similar to the effect when you
pause the VM, but not quite.

INVESTIGATION:
I narrowed down the problem to compton, a compositor for X11.
When compton is killed, the fullscreen mode works fine.

Previously, with VirtualBox 4.3.30 (and many versions before that), fullscreen mode used to work
correctly with compton."	coriolan
16164	VirtualBox 5.0 causes lost interrupts / disk stalls on a Linux system	Linux	VirtualBox 5.0.28	2016-11-07T07:11:16Z	2016-11-07T07:11:16Z	2016-11-07T07:11:16Z	"The host system is an 8-core AMD 64-bit system with 32 GB of RAM, a 128 GB SSD drive and a 1 TB regular rotating disk drive. The operating system is Linux Mint 18; kernel is Ubuntu's 

Linux AlgoCompSynth 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:12:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

VirtualBox is 5.0.28 r111378 directly from Oracle's download page. I've tried this with 5.1 and it's worse.

In normal use - creating a virtual machine, exporting to an OVA, etc., sometimes the system will freeze for a second or two, then pick up where it left off. It only does this when I'm using VirtualBox.

I dug through kernel ""dmesg"" output and found out what's happening. 


{{{
[  +0.418779] vboxdrv: ffffffffc0835020 VMMR0.r0
[  +0.108599] vboxdrv: ffffffffc0930020 VBoxDDR0.r0
[  +0.003241] vboxdrv: ffffffffc0006020 VBoxDD2R0.r0
[  +0.056406] vboxpci: created IOMMU domain ffff8808170fec20
[Nov 6 22:38] ata1: lost interrupt (Status 0x58)
[  +0.000029] ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[  +0.000007] ata1.01: failed command: READ DMA
[  +0.000009] ata1.01: cmd c8/00:01:00:e8:d9/00:00:00:00:00/f7 tag 0 dma 512 in
                       res 40/00:00:00:4f:c2/00:00:00:00:00/10 Emask 0x4 (timeout)
[  +0.000005] ata1.01: status: { DRDY }
[  +0.000023] ata1: soft resetting link
[  +0.184530] ata1.00: configured for UDMA/33
[  +0.007848] ata1.01: configured for UDMA/33
[  +0.000018] ata1: EH complete
[  +0.019241] ata1.00: Enabling discard_zeroes_data
[  +0.156301] ata1.00: Enabling discard_zeroes_data


}}}
I've seen this happen on both the SSD and the rotating disk - whichever VirtualBox is using at the time."	znmebznmeb
4214	VirtualBox 2.2.4 and bonded host interface with guest bridge networking	other	VirtualBox 2.2.4	2009-06-11T08:31:59Z	2015-08-13T17:06:54Z	2015-08-13T17:06:54Z	"My host has two Gigabit NICs. It runs on 64 Bit Ubuntu 8.0.4.2 Server. I have bonded the two interface to become bond0.

I created another guest using 32 Bit Ubuntu 8.0.4.2 Server and configured it to be bridged with bond0.

It seems to work for a while, but halfway through the guest networking stops responding (could not ping to the network gateway or access the Internet from the guest). The host network works well as I was accessing the guest through remote desktop."	John Huong
21438	"VirtualBox ""forgetting"" that an instance is running -> data corruption"	Linux	VirtualBox-7.0.6	2023-01-28T00:08:07Z	2023-01-28T08:54:30Z	2023-01-28T08:54:30Z	"I have seen this many times.

I'm not sure how to reproduce this, but something must be fundamentally broken if this is can happen, so you should be able to figure this out my looking at the code.

Here is what happens.

I am working with guests.
Suddenly, _something_ happens, which leaves the guest running, but gives VirtualBox the impression that it is not running any more.

So VirtualBox thinks that it's switched off.

This happens with both the GUI and if I use VBoxManager list runningvms.

Since it thinks it's off, clicking on it will start it again.

What happens then is that we get two instances running, with both having read-write access to the same underlying storage devices.

You can how this ends: with tears, blood and of course irrecoverable data corruption. (Two OSs writing to the same file system at the same time...)

This is messed up beyond words.

I am attaching a screenshot, which shows two instances of the UI, running on the same host, with the same user.

One shows the guest on, the other shows it off.

The only difference is that I have launched the other instance of the GUI a bit later, but there was no configuration change. There is no reason why would it show a different status.

You can also see the output of list runningvms on the same screenshot. (Empty.)

Btw the actual guest is only visible on the screen, which is showing another data corruption bug with virtio-scsi, about which I will open a separate bug report.
"	csillag
18798	Virtual machine windows 10 auto restart  when click on one folder in shared disk (internal disk host or USB)	Windows	VirtualBox 6.0.10	2019-07-31T17:52:49Z	2019-08-16T06:59:35Z	2019-08-16T06:59:35Z	"* I'm working with a zip compressed file at a shared disk (on host is a USB DIsk 4 TB)
* Try expand, and crash
* Try another, and crash.
* Move to other shared folder (in host is a internal disk 3TB)
* Uncompressed well.
* After click on folder Setup, crash other time.
"	Abdelkarim Mateos Sánchez
15014	Virtual Machine returns duplicate network packets (host SLES 12, guest Win Server 2008, VirtualBox 5.0.4)	Windows	VirtualBox 5.0.4	2016-01-07T09:17:59Z	2016-04-23T22:04:55Z	2016-04-23T22:04:55Z	"Hello,

the virtual machine with Win Server 2008 and static IP address connected to host machine with SLES 12 via bridged network interface returns duplicate network packets.

First I noticed it when sending ping requests to the virtual machine from another host in the network. The ping returns DUPs. Then I started wireshark on hosting machine and I tested the issue also with netcat: sending simple echo from the virtual machine results to double response received by netcat in my laptop. The wireshark clearly shows that the virtual machine sends back duplicate packets for ICMP, UDP and (testing with SNMP traps) also for TCP protocols.

Would you know whether the higher releases of the virtualbox fix this problem? 

Best rgards
mca0001"	mca0001
15809	Virtual machine not runing	other	VirtualBox 5.1.2	2016-08-17T11:19:04Z	2016-08-17T13:23:46Z	2016-08-17T13:23:46Z	(removed pasted VBox.log content)	SerhiiNI
20582	Virtual Machine cannot be started with Linux host kernel 5.14	Windows	VirtualBox 6.1.26	2021-09-28T13:57:41Z	2021-11-29T09:15:40Z	2021-11-29T09:15:40Z	"""Starting..."" dialog running forever.
{{{
# uname -s -r -v -m -p -i -o
Linux 5.14.0-1-amd64 #1 SMP Debian 5.14.6-3 (2021-09-28) x86_64 unknown unknown GNU/Linux
}}}

Relevant dmesg follows:

{{{
[ 4357.923819] SUPR0GipMap: fGetGipCpu=0x2b
[ 4364.025402] usb 5-2: reset high-speed USB device number 2 using xhci_hcd
[ 4364.754742] BUG: unable to handle page fault for address: ffffb205c8289dc0
[ 4364.754750] #PF: supervisor write access in kernel mode
[ 4364.754754] #PF: error_code(0x0003) - permissions violation
[ 4364.754756] PGD 800100000067 P4D 800100000067 PUD 80010019f067 PMD 80010645d067 PTE 80011b390161
[ 4364.754761] Oops: 0003 [#1] SMP NOPTI
[ 4364.754765] CPU: 11 PID: 18408 Comm: EMT Tainted: P           OE     5.14.0-1-amd64 #1  Debian 5.14.6-3
[ 4364.754769] Hardware name: Gigabyte Technology Co., Ltd. X470 AORUS ULTRA GAMING/X470 AORUS ULTRA GAMING-CF, BIOS F41 07/22/2019
[ 4364.754772] RIP: 0010:0xffffb205c8289dc0
[ 4364.754775] Code: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <00> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 4364.754779] RSP: 0018:ffffb205c39b7e20 EFLAGS: 00010286
[ 4364.754781] RAX: ffffb205c8289dc0 RBX: ffffb205c8407010 RCX: ffffb205c8209000
[ 4364.754784] RDX: ffffb205c8289040 RSI: 0000000000000000 RDI: ffff8df1fb85cfd0
[ 4364.754785] RBP: ffffb205c39b7ea0 R08: 0000000000000001 R09: 0000000000000001
[ 4364.754787] R10: ffffffffc0eba560 R11: 0000000000000070 R12: 0000000000000024
[ 4364.754789] R13: ffffb205c8407010 R14: 0000000000000000 R15: ffff8df1fb85cfd0
[ 4364.754791] FS:  00007ff5c095f640(0000) GS:ffff8df7feac0000(0000) knlGS:0000000000000000
[ 4364.754793] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 4364.754795] CR2: ffffb205c8289dc0 CR3: 000080026c12c000 CR4: 00000000003506e0
[ 4364.754798] Call Trace:
[ 4364.754803]  ? supdrvIOCtl+0x3462/0x38b0 [vboxdrv]
[ 4364.754829]  VBoxDrvLinuxIOCtl_6_1_26+0x13c/0x230 [vboxdrv]
[ 4364.754850]  __x64_sys_ioctl+0x83/0xb0
[ 4364.754855]  do_syscall_64+0x3b/0xc0
[ 4364.754861]  entry_SYSCALL_64_after_hwframe+0x44/0xae
[ 4364.754865] RIP: 0033:0x7ff5e904d957
[ 4364.754868] Code: 3c 1c 48 f7 d8 4c 39 e0 77 b9 e8 24 ff ff ff 85 c0 78 be 4c 89 e0 5b 5d 41 5c c3 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e1 94 0c 00 f7 d8 64 89 01 48
[ 4364.754871] RSP: 002b:00007ff5c095dbd8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
[ 4364.754874] RAX: ffffffffffffffda RBX: 00007ff5a41e1390 RCX: 00007ff5e904d957
[ 4364.754876] RDX: 00007ff5a41e1390 RSI: 0000000000005684 RDI: 0000000000000007
[ 4364.754877] RBP: 00007ff5c095dbe0 R08: 0000000000000000 R09: 0000000000000000
[ 4364.754879] R10: 00007ff5e8ead220 R11: 0000000000000246 R12: 00007ff5d1260b4f
[ 4364.754881] R13: 00007ff5c095e040 R14: 00007ff5c095dd40 R15: 0000000000000000
[ 4364.754883] Modules linked in: tun(E) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) rfkill(E) intel_rapl_msr(E) intel_rapl_common(E) nvidia_drm(POE) edac_mce_amd(E) uinput(E) nvidia_modeset(POE) kvm_amd(E) kvm(E) irqbypass(E) uvcvideo(E) videobuf2_vmalloc(E) snd_usb_audio(E) videobuf2_memops(E) snd_hda_codec_realtek(E) videobuf2_v4l2(E) ghash_clmulni_intel(E) nvidia(POE) snd_hda_codec_generic(E) joydev(E) videobuf2_common(E) snd_usbmidi_lib(E) ledtrig_audio(E) aesni_intel(E) snd_rawmidi(E) snd_hda_codec_hdmi(E) videodev(E) snd_seq_device(E) crypto_simd(E) hid_sony(E) snd_hda_intel(E) mc(E) cryptd(E) ff_memless(E) snd_intel_dspcfg(E) snd_intel_sdw_acpi(E) snd_hda_codec(E) snd_hda_core(E) snd_hwdep(E) drm_kms_helper(E) snd_pcm(E) rapl(E) cec(E) snd_timer(E) rc_core(E) snd(E) wmi_bmof(E) soundcore(E) ccp(E) pcspkr(E) sp5100_tco(E) sg(E) watchdog(E) rng_core(E) k10temp(E) evdev(E) acpi_cpufreq(E) parport_pc(E) ppdev(E) lp(E) parport(E) drm(E) fuse(E) configfs(E) ip_tables(E) x_tables(E)
[ 4364.754936]  autofs4(E) ext4(E) crc16(E) mbcache(E) jbd2(E) crc32c_generic(E) sd_mod(E) hid_lg_g15(E) hid_generic(E) usbhid(E) hid(E) mxm_wmi(E) xhci_pci(E) nvme(E) ahci(E) xhci_hcd(E) libahci(E) nvme_core(E) igb(E) t10_pi(E) crc32_pclmul(E) crc_t10dif(E) dca(E) crc32c_intel(E) crct10dif_generic(E) crct10dif_pclmul(E) ptp(E) libata(E) usbcore(E) pps_core(E) gpio_amdpt(E) i2c_piix4(E) i2c_algo_bit(E) scsi_mod(E) usb_common(E) crct10dif_common(E) wmi(E) gpio_generic(E) button(E)
[ 4364.754968] CR2: ffffb205c8289dc0
[ 4364.754970] ---[ end trace e8bbd62475d00fd4 ]---
[ 4364.754972] RIP: 0010:0xffffb205c8289dc0
[ 4364.754974] Code: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <00> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 4364.754977] RSP: 0018:ffffb205c39b7e20 EFLAGS: 00010286
[ 4364.754979] RAX: ffffb205c8289dc0 RBX: ffffb205c8407010 RCX: ffffb205c8209000
[ 4364.754981] RDX: ffffb205c8289040 RSI: 0000000000000000 RDI: ffff8df1fb85cfd0
[ 4364.754982] RBP: ffffb205c39b7ea0 R08: 0000000000000001 R09: 0000000000000001
[ 4364.754984] R10: ffffffffc0eba560 R11: 0000000000000070 R12: 0000000000000024
[ 4364.754985] R13: ffffb205c8407010 R14: 0000000000000000 R15: ffff8df1fb85cfd0
[ 4364.754987] FS:  00007ff5c095f640(0000) GS:ffff8df7feac0000(0000) knlGS:0000000000000000
[ 4364.754989] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 4364.754991] CR2: ffffb205c8289dc0 CR3: 000080026c12c000 CR4: 00000000003506e0
}}}"	deltree
15374	Virtual HDD becomes unavailable for guest : with AHCI#0: Port x reset	Linux	VirtualBox 5.0.14	2016-05-01T14:23:43Z	2020-06-10T12:34:49Z	2020-06-10T12:34:49Z	"It looks a like #9975 in symptoms but with linux/linux host/guest and no windows involved. Also errors logs are not as much verbose.

The guest runs find for a (what looks like) random duration ranging from a few weeks to one year then without clear causes one virtual disk becomes unavailable and creates sda i/o errors on guest with one only line in the Vbox.log file :

{{{
1900:51:41.454153 AHCI#0: Port 2 reset
}}}

A kill $pid + VboxManage startvm restores every thing to normal until next time.

I have seen this behavior on virtualbox version back to 4.3.6r91406 and up to 5.0.14.
When the crash occurs, system load on host isn't particularly high, i/o aren't particularly high neither on host or guest.
I've seen it on SATA rotative disks in RAID 1 and 5, SATA SSD disks raid 1

Guests linux kernels ranges from 2.6.18 up to 3.2.x
Guest hosts are Linux debian 6.0 7.0 or 8.0
All vdi files are used as SATA controled drives


I keep a log of crashed VMs to try discovering common criteria to narrow it down, but nothing really jump to the eye beside :

- low load/low i/o VMs don't seam to crash
- On some host server  with different hardware I never had any crash

I know my report is quite poor in details, but I'll try to keep it updated. During the mean time is there a way to make those ""virtual disk reset"" more verbose ?



"	sylvain Gplservice
19486	virtual disk name extention is added to perious extension	Windows	VirtualBox 6.1.4	2020-04-14T09:47:24Z	2020-04-14T09:47:24Z	2020-04-14T09:47:24Z	"VirtualBox Graphical User Interface
Version 6.1.4 r136177 (Qt5.9.5)

Ubuntu 18.04.4 LTS

1. Start to create new virtual machine in expert mode.
2. Reach the step of creation virtual disk.
3. Change multiple times file type of the disk. And notice to its extension.

Expected: replacement of current extension to new extension.
Real behavior: new file extension is added to the end of full file name. We have multiply exensions."	Marat-sh
20294	Virtual disk automatic resize/growth failing.	Linux	VirtualBox 6.1.18	2021-04-08T18:40:30Z	2021-05-19T16:55:55Z	2021-05-19T16:55:55Z	"Hi,

When the vitual hdd is defined during VM creation, I selected a dynamically allocated VDI. As far as I can tell, the size selected will be the maximum size of the hdd on the host and that less space will be allocated initially and extended as needed during guest operation. Correct?

My situation is a VM with a dynamically allocated hdd of 384GB. Right now it's at 45GB or so but is trying to extend the size. The guest is reporting disk problems and out of space problems and has now changed one partition to read only. What I think is happening is that the guest has a code path which Virtual Box intercepts, does some magic to add space, restart the operation. This is apparently NOT happening. The path through Virtual Box may or may not be trying to handle this situation but then appears to let the error(s) continue through the guest OS (5.12.0-0.rc5.180.fc35.x86_64).

Here's what the host thinks of the partition where the VDI is located:

{{{
Filesystem                         1K-blocks        Used   Available  Really_Available Use% Mount_Point
/dev/sda8                         1735405656   485065980  1250569508        1250339676  28% /export/home
}}}

The guest thinks it's VDI is:

{{{
Filesystem     1K-blocks     Used Available Use% Mounted on
/dev/sda2        1992552   164592   1706720   9% /
/dev/sda7       65478188 14001584  48104780  23% /usr
/dev/sda1        1992552   149816   1721496   9% /boot
/dev/sda8      184666464 19495796 155717356  12% /export/home
/dev/sda5       65478188   751092  61355272   2% /var
/dev/sda6       65478188   936844  61169520   2% /opt
}}}

Which is considerably less than 384GB.

Additionally, the guest is throwing numerous messages like these:

{{{
[   23.180382] 06:32:17.603879 main     VBoxService 6.1.18_Fedora r142142 (verbosity: 0) linux.amd64 (Mar  2 2021 00:00:00
) release log
               06:32:
[   23.184678] 06:32:17.610514 main     OS Product: Linux
[   23.189518] 06:32:17.614980 main     OS Release: 5.12.0-0.rc5.180.fc35.x86_64
[   23.192546] 06:32:17.617869 main     OS Version: #1 SMP Mon Mar 29 15:30:36 UTC 2021
[   23.197236] 06:32:17.620938 main     Executable: /usr/sbin/VBoxService
               06:32:17.620942 main     Process ID: 591
               06:32:17.620944 main     Pa
[   23.202542] 06:32:17.628117 main     6.1.18_Fedora r142142 started. Verbose level = 0
[   23.208141] 06:32:17.633605 main     vbglR3GuestCtrlDetectPeekGetCancelSupport: Supported (#1)
[   40.487920] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
[   40.488885] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s3: link becomes ready
[ 7841.824091] systemd[1]: systemd v248-1.fc35 running in system mode. (+PAM +AUDIT +SELINUX -APPARMOR +IMA +SMACK +SECCOM
P +GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 +PWQU
ALITY +P11KIT +QRENCODE +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified)
[ 7841.825374] systemd[1]: Detected virtualization oracle.
[ 7841.825631] systemd[1]: Detected architecture x86-64.
[ 7872.660143] ata1.00: exception Emask 0x0 SAct 0x1ffff800 SErr 0x0 action 0x6 frozen
[ 7872.661528] ata1.00: failed command: WRITE FPDMA QUEUED
[ 7872.662445] ata1.00: cmd 61/00:58:c8:89:2b/0a:00:12:00:00/40 tag 11 ncq dma 1310720 ou
                        res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 7872.664910] ata1.00: status: { DRDY }
[ 7872.665671] ata1.00: failed command: WRITE FPDMA QUEUED
[ 7872.666963] ata1.00: cmd 61/00:60:c8:93:2b/0a:00:12:00:00/40 tag 12 ncq dma 1310720 ou
                        res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
}}}


and:

{{{
[ 7872.721207] ata1.00: status: { DRDY }
[ 7872.721577] ata1.00: failed command: READ FPDMA QUEUED
[ 7872.722023] ata1.00: cmd 60/08:e0:10:7a:0d/00:00:17:00:00/40 tag 28 ncq dma 4096 in
                        res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 7872.723230] ata1.00: status: { DRDY }
[ 7872.723607] ata1: hard resetting link
[ 7873.036871] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 7873.038028] ata1.00: configured for UDMA/133
[ 7873.038418] ata1.00: device reported invalid CHS sector 0
[ 7873.038850] ata1.00: device reported invalid CHS sector 0
[ 7873.039295] ata1.00: device reported invalid CHS sector 0
[ 7873.039725] ata1.00: device reported invalid CHS sector 0
[ 7873.040250] ata1.00: device reported invalid CHS sector 0
[ 7873.040691] ata1.00: device reported invalid CHS sector 0
[ 7873.041133] ata1.00: device reported invalid CHS sector 0
[ 7873.041646] ata1.00: device reported invalid CHS sector 0
}}}


and:

{{{
[49175.522760] EXT4-fs (sda8): failed to convert unwritten extents to written extents -- potential data loss!  (inode 2621957, error -30)
[49175.526567] EXT4-fs (sda8): failed to convert unwritten extents to written extents -- potential data loss!  (inode 2621958, error -30)
[49175.530010] EXT4-fs (sda8): failed to convert unwritten extents to written extents -- potential data loss!  (inode 2621961, error -30)
}}}

Of course there are more of all of these messages available in a file. I'm not sure how I would attach a file to this mailing list though.

Can someone take a look at all this and render some assistance please?

Best regards,

George...



VirtualBox Graphical User Interface

Version 6.1.19 r143581 (Qt5.6.1)"	George R. Goffe
18060	virtual computer disk removes	Windows	VirtualBox 5.2.20	2018-10-18T11:47:33Z	2018-10-18T11:52:52Z	2018-10-18T11:52:52Z	"after a wile de virtual computer disk removes it self from the settings.
And need to reinitialize from the disk section menu. 
Like the data setting are removed.
"	Nadvt
20084	Virtual Box issues with kernel 5.9.12-lp152.50-preempt?	Solaris	VirtualBox 6.1.16	2020-12-07T13:56:46Z	2021-04-02T05:22:04Z	2021-04-02T05:22:04Z	"Hi, folks,

I am encountering problems when using the kernel version described in the summary. I am running opensuse-Linux 15.2 as host and Solaris 11.4 as guest. (an image provided by Oracle) Installation of VirtualBox 6.1.16 goes fine, just booting the Solaris virtual machine doesn´t happen, it just hangs when reaching 20%. Any ideas? 

Yours,

Reinhard"	Reinardo
16702	Virtual Box in Full screen mode can't switch to other virtual desktop	Linux	VirtualBox 5.1.20	2017-04-26T18:09:37Z	2017-09-22T08:19:46Z	2017-09-22T08:19:46Z	"I am running Linux Mint 18.1 x64 and noticed after upgrading VirtualBox from 5.1.18 to 5.1.20 that when I enter VBOx full screen mode running Ubuntu 16.04 Desktop with fallback installed as guest that I can't switch to other virtual screen using keyboard shortcuts. My short cut was ""Control+Alt+ArrowKeys. This used to work in 5.1.18. When I exit full screen mode and just maximize VBox window it still works. Something I noticed that when in full screen mode when I try to switch virtual screens with above keyboards shortcuts I see for split of a second ""sliding"" like it is trying to do so but then it snaps back to VirtualBox on same screen. So my setup is 3x3 virtual screen setup. So if I enter full screen mode (first row third column) and try to switch to left I see for split of a second 2nd desktop about 5% or it before it snaps back to VirtualBox. I also see Mint 3x3 preview window overlay ed over Virtual box indications all configured screens. But I can switch. I have fairly recent update but this starts happening after Virtual box upgrade. I did reinstall guest tools as well"	oxoocoffee
19713	Virtual Box Booting Issue	Linux	VirtualBox 5.2.34	2020-07-10T10:25:01Z	2020-07-10T10:30:32Z	2020-07-10T10:30:32Z	"
I am Using using Ubuntu version :  Ubuntu 18.04.4 LTS
                Virtual Box Version : 5.2.34

While start using iso file from my local after Windows logo system got hanged everytime
Could you suggest and help to resolve the issue."	Ujjal
21270	VIRTUAL BOX 7.0.2  Bug	Windows	VirtualBox-7.0.2	2022-11-14T21:16:07Z	2022-11-14T21:16:07Z	2022-11-14T21:16:07Z	In windows 10 Host when you have more than one virtual machines (Linux machines on my case) and you have put them on shell startup in order to boot them automaticaly one of them crashes on boot and blocks the state of this machine (not all the times)	Tasos Skarpathakis
13657	Virtual Box 4.3.20 Linux Guest Addition slow a Win64 guest down	Windows	VirtualBox 4.3.20	2014-11-29T05:19:34Z	2014-11-29T05:19:34Z	2014-11-29T05:19:34Z	"I follow my post about the problems of the graphic driver on Windows guest to advise that finally the new VirtualBox 4.3.20 Linux Guest Addition is buggy. Installed on a Windows 7 64bit guest the system
slow completely down becoming hardly usable.

My configuration:

Laptop i74500U, 8gb + external monitor 1920x1080
Host: Fedora 20
Guest: Windows 7 64bit SP1 and recents updates

At the moment I downgraded to version 4.3.18, and all is magically back running."	par7133
17199	Virtual appliance of Debian Stretch 32 bit fsails to boot on a native  64 bit	Linux	VirtualBox 5.1.30	2017-10-22T12:19:57Z	2017-10-22T12:22:08Z	2017-10-22T12:22:08Z	"Failed to open a session for the virtual machine Debian 32bit.

Unresolved (unknown) host platform error. (VERR_UNRESOLVED_ERROR).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

"	flipper88
19871	virtio-nic has been removed?	all	VirtualBox 6.1.14	2020-09-08T18:35:29Z	2020-09-08T18:54:04Z	2020-09-08T18:54:04Z	"There is no more virtio-nic option in the gui of the open source version on Fedora Linux 32 and existing machines with a virtio-nic do error out on startup:
{{{
Invalid network adapter type '6' for slot '0' (VERR_INVALID_PARAMETER).

Codice di uscita:
NS_ERROR_FAILURE (0x80004005)
Componente: 
ConsoleWrap
Interfaccia: 
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

}}}
"	_ReD_
19870	virtio-nic has been removed?	all	VirtualBox 6.1.14	2020-09-08T18:25:04Z	2020-09-08T18:53:36Z	2020-09-08T18:53:36Z	"There is no more virtio-nic option in the gui on Linux (Fedora 32) and machines with a virtio-nic error out on startup:
{{{
Invalid network adapter type '6' for slot '0' (VERR_INVALID_PARAMETER).

Codice di uscita:
NS_ERROR_FAILURE (0x80004005)
Componente: 
ConsoleWrap
Interfaccia: 
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

}}}
"	_ReD_
15952	virtio slow and have unstable performance when VM have >1 vCPU	Linux	VirtualBox 5.1.6	2016-09-18T19:38:55Z	2016-10-08T10:33:16Z	2016-10-08T10:33:16Z	"
Hi.

I have DL380 G7, with latest CentOS 6. Also, kernel is upgraded to kernel-lt - 3.10.x. Host have 2 NIC's enabled (configured).

I'm using latest VirtualBox 5.1.x.

Test scenario involves two VM's, and both of them are attached to both host NIC's (bridge). In VM's, both vNIC are set as virtio, and vCPU is set to 1. VM's are Centos 6 also.

Everything works ok - i'm getting >140Mbytes/s on all interfaces (eth0<->eth0 and eth1<->eth1 from VM to VM).

Now, on one of those VM's, increase number of vCPU to 2. Things now start to behave erratic.

For a short time, eth0<->eth0 is ok, and then starts to fluctuate widely - from ~100Kb/s to 50Mb/s. At the same time eth1<->eth1 stays >140Mb/s.

In rare occasion, eth0 can work ok, eth1 poorly.

Changing one of interfaces with Intel (so only one vNIC is virtio) makes things work stable - if eth0 was switched to Intel, it is >20Mb/s, while eth1 stays >140Mb/s.

From this, i would conclude that there is some kind of race condition with virtio when VM uses vCPU>1.

Also, i do not know how to debug this furtherer. Please advise.

Regards,

H."	Hrvoje
16812	VINF_EM_TRIPLE_FAULT (Win 10 guest on Linux Mint 18.1)	Windows	VirtualBox 5.1.22	2017-06-05T01:05:17Z	2017-06-05T01:05:17Z	2017-06-05T01:05:17Z	After the guest Windows OS performed software updates, VirtualBox logged a VINF_EM_TRIPLE_FAULT error.   	chonak
14422	Video playback in Windows guest badly compromised, as seen in Chrome and Firefox (but not VLC Video player!)	Windows	VirtualBox 5.0.0	2015-08-10T10:28:02Z	2015-08-10T11:13:56Z	2015-08-10T11:13:56Z	"Environment is:

Machine: Thinkpad Yoga laptop with I7-4600U processor and Intel HD Graphics 4400.

Host: Debian 8.0 AMD64 latest (XFCE4 window manager, though should have no effect)

Guest: Windows 8.1 64bit pro , with 2D and 3D acceleration enabled in VirtualBox.

VirtualBox: 5.0

Installed the ""guest additions"" in the guest.

Problem description:


(A)

Playing any YouTube video (e.g. https://www.youtube.com/watch?v=1Y0kX7dfGKU ), in any resolution (even 144px!),

 * lags so bad that viewing is unbearable,

 * very clear vertical sync problem (i.e. half new frame on upper part of screen, half old frame on lower part of screen), and

 * the audio output is stuttering (indicating CPU overuse).

So it looks like video presentation is unaccelerated!


(B)
Installing VLC player and making it use the ""Direct2D video output"" rendering backend, produces *excellent* video playback though!

If I only knew how to switch the web browsers into this video output mode!

(There is a slight vertical sync but that's fine.)


(B.2)
In VLC, using the ""DirectX"" backend shows a black window though!

(B.3)
In VLC, using the ""Direct3D"" or ""OpenGL"" backend crashes VLC though - it just exits and there's no crash report dialog box or alike!

(B.4)
In VLC, using the ""Windows GDI"" backend produces the same video display experience as in (A), i.e. stuttering video and audio - this indicates that (A) is made completely without acceleration?

(B.5)
In VLC, using the ""OpenGL (experimental)"" backend gives no output.

(C)
The video in (A) was HTML5 video playback. Also trying Flash video playback on http://www.adobe.com/devnet/flash/articles/vidtemplate-engage-with-flash.html gives some kind of stuttering in the video and audio playback, while not nearly as bad as in (A), it's still very laggy.


"	mik_
18323	Video Memory Expanding to 256 MB Fail	Linux	VirtualBox 6.0.2	2019-01-17T14:21:34Z	2019-01-19T21:27:44Z	2019-01-19T21:27:44Z	"Can no longer extend video memory to 256MB using the command line:

VBoxManange modifyvm ""vm name"" --vram 256

This creates an error upon boot up and stops boot.

Legacy machines created in VirtualBox 5.2 seem to work fine with this mod when installed on VB 6.0."	andrewf
15995	Video corruption with gengradd.dll from OS/2 guest additions	other	VirtualBox 5.1.6	2016-09-28T02:56:54Z	2016-09-28T02:56:54Z	2016-09-28T02:56:54Z	"When using the OS/2 guest additions video driver (gengradd.dll) mouse artifacts are left on the screen from selected applications (generally when mouse pointer changes while moving across other dynamic content).

I have seen this for some time (VBox 4?), and continue to see it on:

VirtualBox-5.1-5.1.6_110634_openSUSE132-1.x86_64

with the latest additions installed.

Screenshots attached.

Rolling back to the default gengradd.dll installed with the guest OS, no corruption is seen."	Lewis Rosenthal
13073	Video Captures are Blank / Green	Linux	VirtualBox 4.3.12	2014-05-29T03:13:47Z	2016-09-08T21:53:55Z	2016-09-08T21:53:55Z	"When using the Video Capture in Vbox, nothing is recorded. There is only a ""Green Screen"".

Guest Additions are installed

libvpx is installed

This occurs with or without 3D Acceleration enabled.

Host: Ubuntu Gnome 14.04, Virtualbox 4.3.12 r93733
Guest: Lubuntu 14.04"	Hashpling
13806	Video capture in Linux does not work (small file with empty green .webm video)	Linux	VirtualBox 4.3.20	2015-02-03T13:47:40Z	2015-06-18T12:53:37Z	2015-06-18T12:53:37Z	"I know similar bug reports are made but problem still exist and is not solved like I noticed on some bug report comments.

Host: 64-bit Ubuntu 14.04.1 LTS with 3.18.5 generic kernel.

Using ATI-AMD graphics card HD 7770 series on host:
    $ lspci -vnn | grep VGA
    01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X] [1002:683d] (prog-if 00 [VGA controller])

Also guest additions are installed in guests and 3D acceleration enabled from settings. Did not help. Still I get small .webm file with empty green video.

I tried also classic Gnome fallback - I mean I turned Unity off but still no help. I tried with or without guest additions - no help. Certainly also from settings I turned 3D acceleration on and off.
I am running 64-bit Ubuntu 14.04.1 LTS and guest systems are Kubuntu 14.04.1 LTS, Lubuntu 14.04.1 LTS, Xubuntu 14.04.1 LTS Ubuntu Mate 14.04.1 LTS. I tried both 32-bit and 64-bit guests - same problem.
I also tried different video players - VLC, SMPlayer, Totem, Xine - always blank green video and that's it"	Edmund Laugasson
14177	Very slow command line operations on long uptime	all	VirtualBox 4.3.28	2015-06-05T13:18:01Z	2015-06-06T18:16:06Z	2015-06-06T18:16:06Z	"I've a server where I'm trying to run a lot of virtual machines (25-30), with somewhat long uptime (some weeks) and what I see is a constant increase of the slowness of VBoxManage operations.

For example, on a fresh start the command ""VBoxManage list runningvms"" employs only 0.2 seconds but day after day the execution time rises and after some weeks the same command can employ even 60 seconds to complete.

This in turn gives problem with applications like phpvirtualbox that is unable to even reach the main screen (supposedly) due to various timeouts.

The only way to solve the problem is to shutdown all the machines, stop the vbox service, and restart it."	Alex
15924	Very large audio delay in Windows XP guest while CPU loaded at 100%	Windows	VirtualBox 5.1.6	2016-09-13T13:25:05Z	2018-02-13T10:17:48Z	2018-02-13T10:17:48Z	"I discovered a new bug in VirtualBox v5.1 that did not happen in v5.0 and older versions.

When running a Windows XP SP3 guest on a Linux host (with sound configured for ALSA on the host side and AC97 on the guest side), I get very long delays in games (1 to 3 seconds !) between the moment the sound is triggered and the moment it gets played: the higher the load on the CPU, the longer the delay.

Turning on HPET on the guest doesn't change anything...

I'm attaching a log of a short session when I started the VM and a game in it, clicked on menu items (which produce sounds at each click), got the delays each time, and shut down the game and the VM."	dinosaur0
19007	VERR_PGM_HANDLER_NOT_FOUND	Windows	VirtualBox 6.0.12	2019-10-13T07:05:28Z	2020-02-29T06:30:29Z	2020-02-29T06:30:29Z	"Running 4 VirtualBox (Version 6.0.12 r133076 (Qt5.6.1)) instances on Fedora host with 40Gb RAM.
2 Windows Server 2016 instances were doing updates.
Both crashed with VERR_PGM_HANDLER_NOT_FOUND"	YoungJules
18219	VERR_NOT_SUPPORTED for a valid ISO image	Linux	VirtualBox 6.0.0	2018-12-21T15:17:07Z	2022-10-21T12:47:37Z	2022-10-21T12:47:37Z	"Both VirtualBox 6.0 and 5.2.22 don't accept this ISO image:

http://mirror.ppa.trinitydesktop.org/trinity/cdimages/ubuntu/tde-ubuntu-14.04-desktop-latest-amd64.iso

The error is:

Failed to open the disk image file /tmp/tde-ubuntu-14.04-desktop-latest-amd64.iso.

Could not get the storage format of the medium '/tmp/tde-ubuntu-14.04-desktop-latest-amd64.iso' (VERR_NOT_SUPPORTED).


{{{
Result Code: VBOX_E_IPRT_ERROR (0x80BB0005)
Component: MediumWrap
Interface: IMedium {4afe423b-43e0-e9d0-82e8-ceb307940dda}
Callee: IVirtualBox {9570b9d5-f1a1-448a-10c5-e12f5285adad}
Callee RC: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)
}}}


"	Artem S. Tashkinov
17820	VERR_INTERRUPTED errors from guest control service during ptrace debugging	Linux	VirtualBox 5.1.38	2018-06-14T12:17:38Z	2018-06-25T09:14:07Z	2018-06-25T09:14:07Z	"VBoxService should cleanly handle interrupted syscalls. When receiving an error with errno=EINTR, the syscall should be retried.

We have a service that performs an anti-virus scan of running processes, which attaches to processes as a debugger to inspect memory to check for injected malware. Every time a scan is performed an error is reported by the Guest control service:

{{{
May 31 09:36:37 rhel74 kernel: 186:39:59.180297 control  Error: Getting host message failed with VERR_INTERRUPTED
}}}


After a few scans (17?) the Guest control service aborts:

{{{
May 31 09:41:10 rhel74 kernel: 186:44:32.414453 control  Error: Getting host message failed with VERR_INTERRUPTED
May 31 09:41:10 rhel74 kernel: 186:44:32.414591 control  Error: Too many failed attempts in a row to get next message, bailing out
May 31 09:41:10 rhel74 kernel: 186:44:32.414636 control  Guest control service stopped
May 31 09:41:10 rhel74 kernel: 186:44:32.414667 control  Guest control worker returned with rc=VERR_INTERRUPTED
}}}

The error can be reproduced with gdb by attaching to the running VBoxService process:


{{{
[root@rhel69 pair]# tail -f /var/log/messages &
[1] 4714
[root@rhel69 pair]# May 31 13:44:00 rhel69 kernel: 00:00:00.000152 main     Log opened 2018-05-31T12:44:00.767090000Z
May 31 13:44:00 rhel69 kernel: 00:00:00.000266 main     OS Product: Linux
May 31 13:44:00 rhel69 kernel: 00:00:00.000307 main     OS Release: 2.6.32-696.3.2.el6.x86_64
May 31 13:44:00 rhel69 kernel: 00:00:00.000355 main     OS Version: #1 SMP Wed Jun 7 11:51:39 EDT 2017
May 31 13:44:00 rhel69 kernel: 00:00:00.000388 main     Executable: /opt/VBoxGuestAdditions-5.1.38/sbin/VBoxService
May 31 13:44:00 rhel69 kernel: 00:00:00.000390 main     Process ID: 4698
May 31 13:44:00 rhel69 kernel: 00:00:00.000391 main     Package type: LINUX_64BITS_GENERIC
May 31 13:44:00 rhel69 kernel: 00:00:00.001758 main     5.1.38 r122592 started. Verbose level = 0
May 31 13:44:00 rhel69 vboxadd-service.sh: VirtualBox Guest Addition service started.
May 31 13:44:01 rhel69 kernel: 00:02:52.579824 main     Ended.

[root@rhel69 pair]# gdb -p `pidof VBoxService` -batch -ex quit
Missing separate debuginfo for /opt/VBoxGuestAdditions-5.1.38/sbin/VBoxService
[New LWP 4710]
[New LWP 4709]
[New LWP 4708]
[New LWP 4707]
[New LWP 4706]
[New LWP 4705]
[New LWP 4704]
[Thread debugging using libthread_db enabled]
0x0000003f5ca0f585 in sigwait () from /lib64/libpthread.so.0
A debugging session is active.

	Inferior 1 [process 4703] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]
May 31 13:45:55 rhel69 kernel: 00:01:54.476487 control  Error: Getting host message failed with VERR_INTERRUPTED
[root@rhel69 pair]# 
[root@rhel69 pair]# kill %1
[root@rhel69 pair]# 
[1]+  Terminated              tail -f /var/log/messages
[root@rhel69 pair]# 
}}}

It looks like VBoxService is failing to handle interrupted system calls correctly.


From http://man7.org/linux/man-pages/man2/ptrace.2.html :
(Programs which do not expect such ""stray"" EINTR errors may behave in an unintended way upon an strace(1) attach.)


I presume VBoxService is waiting on a syscall, such as poll() and receives an EINTR error when the process is interrupted. The error is recoverable, and the call should just be retried in this case, but it looks like the error is being treated as a problem and isn't silently/cleanly recovered.


VBox guest attributes:


{{{

￼
Runtime attributes


Screen Resolution

800x600x32 @0,0
VM Uptime

1d 03:48:55
Clipboard Mode

Disabled
Drag and Drop Mode

Disabled
VT-x/AMD-V

Active
Nested Paging

Active
Unrestricted Execution

Active
Paravirtualization Interface

KVM
Guest Additions

5.1.38 r122592
Guest OS Type

Linux 2.6 / 3.x / 4.x (64-bit)
Remote Desktop Server Port

Not Available
}}}

"	Tim@…
18721	vdi disk got filled up and now VirtualBox refuses to revert to an earlier snapshot	Linux	VirtualBox 5.2.18	2019-06-22T14:31:49Z	2019-06-22T21:39:05Z	2019-06-22T21:39:05Z	"Hello,

I am running VritualBox 5.2.18, host OS being Ubuntu 18.04 and guest being Mint 19. 

In Mint I have a riscv/rocket-chip environment setup in order to simulate behavior of a processor and observe its output waveforms, given the input in the form of c/assembly programs. Once I had installed the Mint OS I created a snapshot, and then again, once I had setup the environment, I created another snapshot and only then moved on to run different simulations.

The output waveform files do tend to get big, so my VDI is 110 GB fixed-size. Nevertheless, yesterday the simulation went on and on, and the output waveform file simply filled the whole VDI, completely. 

That I conclude from this is the message I get when I try turning the VM in its current state:


{{{
An error has occurred during virtual machine execution! The error details are shown below. You may try to correct the error and resume the virtual machine execution.

The I/O cache encountered an error while updating data in medium &quot;ahci-0-0&quot; (rc=VERR_DISK_FULL). Make sure there is enough free space on the disk and that the disk is working properly. Operation can be resumed afterwards.

Error ID: BLKCACHE_IOERR
Severity: Non-Fatal Error
}}}


So, ok - it makes sense: the file got to big, filled up the disk, the VM can't boot. Ok, no problem there. However, once I tried bringing back the snapshot (either one of them), I get:


{{{
Failed to restore the snapshot intenuser of the virtual machine rockettest.

Result Code: VBOX_E_FILE_ERROR (0x80BB0004)
}}}


And this, definitely, is not ok - it brings me into a terrible position, as it completely destroys the work on setting up everything.

I tried increasing size of the VDI, but for some reason - I am not allowed to type in the new size (image attached - 1).

VirtualBox does allow me to enter the new size for a snapshot (image attached - 2), but once I click Apply, that leads to a new error:


{{{
Failed to resize the storage unit of the hard disk /media/aleksandar/Elements/VirtualMachines/rockettest/Snapshots/{814f10d6-c461-4860-be1c-4da0540701b3}.vdi from 100.00 GB to 120.00 GB.

Could not resize medium '/media/aleksandar/Elements/VirtualMachines/rockettest/Snapshots/{814f10d6-c461-4860-be1c-4da0540701b3}.vdi' (VERR_DISK_FULL).

Result Code: VBOX_E_FILE_ERROR (0x80BB0004)
Component: MediumWrap
Interface: IMedium {4afe423b-43e0-e9d0-82e8-ceb307940dda}
}}}


Please help."	dndrdm
16263	VDE networking support seems not to be present	other	VirtualBox 5.0.24	2016-12-03T22:26:40Z	2016-12-03T23:06:23Z	2016-12-03T23:06:23Z	"Hi,

I am trying to use my vbox in conjunction with VDE switch.
Checked in the docs, that it should be compiled with --enable-vde flag to make it effective so that in interface's properties I will be able to choose VDE next to other native options.

I got virtualbox sources for Ubuntu 16.04 and I can see the VDE flag is set to 1 by default. Recompiled it for the formality and installed those packages, still there is no VDE option present.

Can you guys confirm you still support VDE?"	maq123
19621	vboxwebsrv is not connected to port 18083	other	VirtualBox 6.1.8	2020-05-25T15:32:22Z	2020-05-25T15:32:22Z	2020-05-25T15:32:22Z	"in version 6.1.4 no problems
in version 6.1.6 & 6.1.8 
ss -lntu | grep 18083  no response
ps aux | grep 18083    no response

running Head-Less-Server with Leap 15.1 and
5.5.0-1.g3f183bf-default #1 SMP Mon Jan 27 08:34:09 UTC 2020 (3f183bf) x86_64 x86_64 x86_64 GNU/Linux

Let me know if you need additional infos
hgf_m "	hgf_m
18870	vboxwebsrv IPerformanceCollector.queryMetricsData failed.	other	VirtualBox 6.0.8	2019-08-26T19:40:16Z	2019-08-26T19:40:16Z	2019-08-26T19:40:16Z	"I use java 12.0.2.
IPerformanceCollector.queryMetricsData failed with exception:
TEST listHostInfo(org.virtualbox.vboxjws.test.ClientTest) <<< ERROR: java.lang.reflect.InvocationTargetException
java.lang.AssertionError: java.lang.reflect.InvocationTargetException
	at org.virtualbox_6_0.Helper.wrap(Helper.java:62)
	at org.virtualbox_6_0.IPerformanceCollector.queryMetricsData(IPerformanceCollector.java:350)
	at org.virtualbox.vboxjws.test.ClientTest.listHostInfo(ClientTest.java:212)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:567)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
	at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at junit.framework.JUnit4TestAdapter.run(JUnit4TestAdapter.java:38)
	at junit.framework.TestSuite.runTest(TestSuite.java:252)
	at junit.framework.TestSuite.run(TestSuite.java:247)
	at aQute.junit.Activator.test(Activator.java:326)
	at aQute.junit.Activator.automatic(Activator.java:220)
	at aQute.junit.Activator.run(Activator.java:176)
	at aQute.launcher.Launcher.lambda$serviceChanged$2(Launcher.java:1433)
	at aQute.launcher.Launcher.launch(Launcher.java:387)
	at aQute.launcher.Launcher.run(Launcher.java:144)
	at aQute.launcher.Launcher.main(Launcher.java:122)
	at aQute.launcher.pre.EmbeddedLauncher.executeWithRunPath(EmbeddedLauncher.java:154)
	at aQute.launcher.pre.EmbeddedLauncher.findAndExecute(EmbeddedLauncher.java:119)
	at aQute.launcher.pre.EmbeddedLauncher.main(EmbeddedLauncher.java:51)
Caused by: java.lang.reflect.InvocationTargetException
	at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:500)
	at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:481)
	at org.virtualbox_6_0.Helper.wrap(Helper.java:44)
	... 34 more
Caused by: java.lang.AssertionError
	at org.virtualbox_6_0.ObjectRefManager.registerObj(VirtualBoxManager.java:225)
	at org.virtualbox_6_0.IUnknown.<init>(IUnknown.java:41)
	... 40 more
"	akabanov
16297	vboxweb and vboxbaloonctrl service scripts depend on 'killall', which is not installed by default on CentOS7	other	VirtualBox 5.1.10	2016-12-16T16:35:39Z	2016-12-16T16:35:39Z	2016-12-16T16:35:39Z	The scripts /usr/lib/virtualbox/vboxballoonctrl-service.sh and /usr/lib/virtualbox/vboxweb-service.sh use the 'killall' command to stop the services, but by default it is not installed on CentOS 7 (and by inference, RHEL 7 as well). This can easily be resolved by adding 'psmisc' to the required packages for the EL7 RPM.	Joshua Megerman
16166	vboxusers group disappeared after last update	Windows	VirtualBox 5.1.8	2016-11-07T17:46:56Z	2016-11-22T17:45:58Z	2016-11-22T17:45:58Z	"Hi,

I recently upgraded to VirtualBox 5.1.8 r111374 (Qt5.6.1) from the previous version, on my Ubuntu 14.04 host. The guest is Windows 7. I also have the proper guest addition and extension pack.

After this upgrade VirtualBox can't detect any USB flash drives connected to my computer. After digging into this a bit, I realized that the vboxusers group has disappeared from my computer! I tried reinstalling the extension pack but had no luck.

Everything else seems to be working fine.

"	mau17
16309	VBoxtray and VBoxservice sometimes block  windows 7 guest responsiveness	Windows	VirtualBox 5.0.30	2016-12-20T16:46:44Z	2016-12-20T23:32:31Z	2016-12-20T23:32:31Z	"Since this fall my windows 7-64 guest occasionally stops responding to mic, mouse, and keyboard input and seems to hang. This typically happens when the host and guest interact, as in a drag-and-drop, or when two windows programs that both interact with the host seem to tangle (e.g. word and dragon naturally speaking). In fact the guest is not hung, as it's fully responsive to sending the ctrl-alt-delete signal and starting the task manager--which shows the same minimal responsiveness. I've ""solved"" the problem using VBoxManager guestcontrol to taskkill vboxtray or vboxservice, which I then restart inside the guest. 
Host: Linux Mint17.3x64 KDE fully patched, kernel 4.4.39

Log file attached."	matthewls
20931	VBoxSVGA-3d,host gpu memory leak	Windows	VirtualBox 6.1.34	2022-05-06T08:03:47Z	2022-05-17T18:07:12Z	2022-05-17T18:07:12Z	"I use VBoxSVGA device and open 3D accelerate.
I tried to open and close the chrome browser repeatedly, then I use nvidia-smi to see host gpu memory,I found that the gpu memory leaked.
I print pState->papSurfaces ,Lots of host surface are not released.

host
ubuntu-18.04 kernel-5.4.0-107-generic
virtualbox-6.1.34

guest
windows7x64,windows10x64
chrome-100.0.4896.127"	lumory
18277	VBoxSVGA not showing correct resolutions	Windows	VirtualBox 6.0.0	2019-01-04T10:25:21Z	2019-03-02T19:11:12Z	2019-03-02T19:11:12Z	"Host with Xubuntu 18.04 dual monitor: 1920x1080 and 2560x1080
Guest with Windows 10 registered and update and dual monitor enabled.VBox additions updated to 6.0.

In VirtualBox with VBoxVGA all works fine.

When changed to VBoxSVGA second monitor not showing correct resolution 2560x1080 in the list of supported resolutions. No problem with main 1920x1080 monitor."	vicsanc
18912	VBOXSvga : lots of flickering with Windows Guests on Linux Hosts	Windows	VirtualBox 6.0.12	2019-09-07T07:34:12Z	2020-06-11T11:34:16Z	2020-06-11T11:34:16Z	"Hi,

I tried the VBOXSvga driver with 3D support for the following guests :
- Windows VISTA
- Windows 7
- Windows 8
- Windows 10

I notice a lot of bugs, like Skype displaying a black window and more importantly transparency bugs and flickering. If I disable 3D support Skype remains buggy but flickering disappears. Now if I revert to VBoxVGA w/ 3D support enabled all is fine.

My host is as follows :
- Intel Core i7 4790
- 32 GB RAM
- NVidia GeForce 2070 SUPER w/ driver 430.40
- Debian Buster AMD64

I enabled the following environment variable as a workaround to the flickering bug we had w/ NVidia driver :
CR_RENDER_FORCE_PRESENT_MAIN_THREAD=0

Perhaps is it the culprit, or is it something else ?"	gojul
18914	VBoxSVGA 3D rendering problems	Windows	VirtualBox 6.0.12	2019-09-09T06:45:35Z	2021-06-10T00:15:31Z	2021-06-10T00:15:31Z	"VBox 6.0.12[[BR]]

Host: {{{Ubuntu 16.04; 4.15.0-60-generic #67~16.04.1-Ubuntu}}}[[BR]]

Guest: Win10(64) Version 19.03 (OS Build 18362.329)[[BR]]

MS Outlook for Office 365 MSO (16.0.11929.20234) 64-bit[[BR]]


Guest: VBoxSVGA, 2D enabled, 3D enabled, Guest Additions 6.0.12

MS Outlook window is rendered with black/white/grey boxes. Window is responsive, e.g. can close the application by clicking at the top right corner, where the 'X' close widget should be.

Problem disappears when disabling 3D in VM settings."	sunrider
18699	VBoxSVGA 3D acceleration issue on windows 7 guest.	Windows	VirtualBox 6.0.8	2019-06-08T08:22:17Z	2019-06-08T14:38:49Z	2019-06-08T14:38:49Z	"Problem:
No 3D acceleration on windows 7 guest with VBoxSVGA adapter.

i posted all info here: [https://forums.virtualbox.org/viewtopic.php?f=7&t=93460]
"	navarobot
18115	VBoxSVC segfault when ending Windows guest	Windows	VirtualBox 5.2.20	2018-11-07T20:37:50Z	2020-03-08T20:03:39Z	2020-03-08T20:03:39Z	"When cleanly shutting down Windows guests (on a CentOS Host), which were started with:
 VBoxManage startvm MACHINENAME -type vrdp

I see afterwards in the Linux syslog this kind of crash:
 VBoxSVC[5805]: segfault at 0 ip           (null) sp 00007ffc9097f068 error 14 in VBoxSVC[400000+4de000]

The crash is reproducible, and has been there since a long time (all of 5.2.x VirtualBox versions)."	Helge Deller
6947	VBoxSharedClipBoardClass blocks when copying from host.  (XP guest, CentOS host)	Windows	VirtualBox 3.2.4	2010-06-09T06:52:12Z	2015-05-20T13:56:50Z	2015-05-20T13:56:50Z	"Since several versions ago, I have been experiencing clipboard blocking problems.

When copying contents (most of the cases, they are formatted texts), VBoxSharedClipBoardClass blocks, or locks up, so that the application in the guest stops responding.

I recently found that killing the virtual box service in the guest machine will return control back to the guest application, but the clipboard sharing between guest and host will be lost.  Restarting the virtual box service on the guest does not help regain the sharing.

The problem happens at some time, I still cannot reproduce it at will."	afante
20308	vboxsf module (GA 6.0.24) fails to compile on latest ubuntu-16.04 kernel	Linux	VirtualBox 6.0.22	2021-04-20T17:48:10Z	2021-04-20T18:32:33Z	2021-04-20T18:32:33Z	"Attempting to build the vboxsf module for Guest Additions 6.0.24 fails on the latest ubuntu-16.04 kernel (`4.4.0-209-generic #241`).
{{{
vagrant@ubuntu-16:~$ uname -a
Linux ubuntu-16 4.4.0-209-generic #241-Ubuntu SMP Tue Apr 13 01:06:06 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
}}}

Snipped output from attempting to build the module manually with `build_in_tmp` (full log attached):
{{{
=== Building 'vboxsf' module ===
make[1]: Entering directory '/tmp/vbox.0/vboxsf'
make V= CONFIG_MODULE_SIG= CONFIG_MODULE_SIG_ALL= -C /lib/modules/4.4.0-209-generic/build M=/tmp/vbox.0/vboxsf SRCROOT=/tmp/vbox.0/vboxsf -j2 modules
make[2]: Entering directory '/tmp/vbox.0/vboxsf'
make[2]: warning: -jN forced in submake: disabling jobserver mode.
  CC [M]  /tmp/vbox.0/vboxsf/vfsmod.o
  CC [M]  /tmp/vbox.0/vboxsf/dirops.o
  CC [M]  /tmp/vbox.0/vboxsf/lnkops.o
  CC [M]  /tmp/vbox.0/vboxsf/regops.o
  CC [M]  /tmp/vbox.0/vboxsf/utils.o
/tmp/vbox.0/vboxsf/utils.c: In function 'vbsf_inode_setattr':
/tmp/vbox.0/vboxsf/utils.c:812:10: error: implicit declaration of function 'inode_change_ok' [-Werror=implicit-function-declaration]
     rc = inode_change_ok(pInode, iattr);
          ^
cc1: some warnings being treated as errors
scripts/Makefile.build:288: recipe for target '/tmp/vbox.0/vboxsf/utils.o' failed
make[3]: *** [/tmp/vbox.0/vboxsf/utils.o] Error 1
make[3]: *** Waiting for unfinished jobs....
Makefile:1472: recipe for target '_module_/tmp/vbox.0/vboxsf' failed
make[2]: *** [_module_/tmp/vbox.0/vboxsf] Error 2
make[2]: Leaving directory '/usr/src/linux-headers-4.4.0-209-generic'
/tmp/vbox.0/vboxsf/Makefile-footer.gmk:117: recipe for target 'vboxsf' failed
make[1]: *** [vboxsf] Error 2
make[1]: Leaving directory '/tmp/vbox.0/vboxsf'
Makefile:48: recipe for target 'vboxsf' failed
make: *** [vboxsf] Error 1
}}}

It looks like a recent kernel update (https://ubuntu.com/security/notices/USN-4916-1) involving some CVE fixes also backported the migration from `inode_change_ok` to `setattr_prepare`.
That migration has previously broken Guest Addition compilation at least a couple times for other distros (https://www.virtualbox.org/ticket/17299, https://www.virtualbox.org/ticket/18697).
There are some existing IFDEFs in `VBox/Additions/linux/sharedfolders/utils.c` related to those previous issues:
{{{
#if (RTLNX_VER_RANGE(3,16,39,  3,17,0)) || RTLNX_VER_MIN(4,9,0) || (RTLNX_VER_RANGE(4,1,37,  4,2,0))
# if RTLNX_VER_MIN(5,12,0)
    rc = setattr_prepare(ns, dentry, iattr);
# else
    rc = setattr_prepare(dentry, iattr);
# endif
#else
    rc = inode_change_ok(pInode, iattr);
#endif
}}}
but they don't cover this case yet since it's a 4.4.0 series kernel.
"	jonahbull
16417	vboxsf crashes process or VM in case of many file stat operations on shared vboxsf file system in a short time	Linux	VirtualBox 5.1.14	2017-01-23T08:42:05Z	2017-07-20T17:23:49Z	2017-07-20T17:23:49Z	"We use a vagrant based toolchain to automatically generate VMs for executing unit tests. They run on Ubuntu 16.04 LTS 64-bit hosts, and the VMs themselves contain various different older and newer Linux distributions. We use current VirtualBox 5.1.14 and also the 5.1.14 guest tools.

Quite a significant percentage (10-20%) of our VM deployments was not successful. In case of ""default"" paravirtualization using KVM, the whole VM freezes, and the VBox.log file just says:

{{{
00:00:42.027263 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
}}}

If using the ""minimal"" paravirtualization, VM operation continues, just the unit test process itself dies (see log below). This happens consistently at the same place where there are many stat() calls made to get the ctime information of many thousands of (empty) cache files on a shared vboxsf file system, before outdated files are supposed to be cleaned up. If I remove this code part, the error does not occur any more. Therefore my (uneducated) assumption is that it could be related to running many stat operations in a short time. Here's the stack trace as found in /var/log/kern.log in the instance.

{{{
Jan 21 22:23:14 vagrant kernel: [    8.021389] vboxsf: Successfully loaded version 5.1.14 (interface 0x00010004)
Jan 21 22:23:14 vagrant kernel: [    8.328536] VBoxService 5.1.14 r112924 (verbosity: 0) linux.amd64 (Jan 16 2017 17:38:46) release log
Jan 21 22:23:14 vagrant kernel: [    8.328536] 00:00:00.000093 main     Log opened 2017-01-21T22:23:14.323839000Z
Jan 21 22:23:14 vagrant kernel: [    8.328566] 00:00:00.000154 main     OS Product: Linux
Jan 21 22:23:14 vagrant kernel: [    8.328578] 00:00:00.000170 main     OS Release: 3.16.0-4-amd64
Jan 21 22:23:14 vagrant kernel: [    8.328589] 00:00:00.000182 main     OS Version: #1 SMP Debian 3.16.39-1 (2016-12-30)
Jan 21 22:23:14 vagrant kernel: [    8.328614] 00:00:00.000193 main     Executable: /opt/VBoxGuestAdditions-5.1.14/sbin/VBoxService
Jan 21 22:23:14 vagrant kernel: [    8.328614] 00:00:00.000194 main     Process ID: 1028
Jan 21 22:23:14 vagrant kernel: [    8.328614] 00:00:00.000195 main     Package type: LINUX_64BITS_GENERIC
Jan 21 22:23:14 vagrant kernel: [    8.329284] 00:00:00.000860 main     5.1.14 r112924 started. Verbose level = 0
Jan 21 22:27:01 vagrant kernel: [  233.348410] VBOXGUEST_IOCTL_HGCM_CALL: 64 Failed. rc=-228.
Jan 21 22:27:01 vagrant kernel: [  233.348430] general protection fault: 0000 [#1] SMP 
Jan 21 22:27:01 vagrant kernel: [  233.348461] Modules linked in: vboxsf(O) nfsd auth_rpcgss oid_registry nfs_acl nfs lockd fscache sunrpc vboxvideo(O) ttm drm_kms_helper ppdev drm evdev vboxguest(O) crc32_pclmul i2c_piix4 pcspkr i2c_core serio_raw aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd parport_pc battery processor parport video thermal_sys ac button autofs4 ext4 crc16 mbcache jbd2 dm_mod sg sd_mod crc_t10dif crct10dif_generic ata_generic crct10dif_pclmul crct10dif_common crc32c_intel e1000 psmouse ata_piix libata scsi_mod
Jan 21 22:27:01 vagrant kernel: [  233.348614] CPU: 1 PID: 1925 Comm: otrs.UnitTest.p Tainted: G           O  3.16.0-4-amd64 #1 Debian 3.16.39-1
Jan 21 22:27:01 vagrant kernel: [  233.348661] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
Jan 21 22:27:01 vagrant kernel: [  233.348689] task: ffff8800797bcce0 ti: ffff88007bdcc000 task.ti: ffff88007bdcc000
Jan 21 22:27:01 vagrant kernel: [  233.348718] RIP: 0010:[<ffffffffa02666c1>]  [<ffffffffa02666c1>] VGDrvCommonIoCtl+0x261/0x1bf0 [vboxguest]
Jan 21 22:27:01 vagrant kernel: [  233.348763] RSP: 0018:ffff88007bdcfb98  EFLAGS: 00010282
Jan 21 22:27:01 vagrant kernel: [  233.348784] RAX: 00000000ffffff1c RBX: 0000a0007bdcfc84 RCX: 0000000000000001
Jan 21 22:27:01 vagrant kernel: [  233.348813] RDX: 0000000000000000 RSI: 000000000000002f RDI: ffff88007bdcf9a0
Jan 21 22:27:01 vagrant kernel: [  233.348842] RBP: 5f7c81f4149bd010 R08: 000000000000000a R09: 00000000000001c0
Jan 21 22:27:01 vagrant kernel: [  233.348870] R10: 0000000000000000 R11: ffff88007bdcf6be R12: 0000b00000000000
Jan 21 22:27:01 vagrant kernel: [  233.348898] R13: 1b3eed7500000000 R14: 5f7c81f4149bd064 R15: 5f7c81f4149bd010
Jan 21 22:27:01 vagrant kernel: [  233.348927] FS:  00007ff073ca7700(0000) GS:ffff88007fd00000(0000) knlGS:0000000000000000
Jan 21 22:27:01 vagrant kernel: [  233.348958] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan 21 22:27:01 vagrant kernel: [  233.348981] CR2: 00007ffec82d3ff8 CR3: 000000007bcd8000 CR4: 00000000000406e0
Jan 21 22:27:01 vagrant kernel: [  233.349008] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Jan 21 22:27:01 vagrant kernel: [  233.349033] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Jan 21 22:27:01 vagrant kernel: [  233.349072] Stack:
Jan 21 22:27:01 vagrant kernel: [  233.349082]  001041ed149bd010 000003e900000000 00000002000003e9 013aa00300000902
Jan 21 22:27:01 vagrant kernel: [  233.349114]  0000000000000000 0000000000000000 ffff880023350880 0000006c00000004
Jan 21 22:27:01 vagrant kernel: [  233.349147]  ffff88007bdcfbfc 0000a00000020830 ffff88007b0c6000 ffffffffa03f877c
Jan 21 22:27:01 vagrant kernel: [  233.349178] Call Trace:
Jan 21 22:27:01 vagrant kernel: [  233.349194]  [<ffffffffa03f877c>] ? sf_stat+0x5c/0x110 [vboxsf]
Jan 21 22:27:01 vagrant kernel: [  233.349219]  [<ffffffffa03f88b0>] ? sf_inode_revalidate+0x80/0xd0 [vboxsf]
Jan 21 22:27:01 vagrant kernel: [  233.349246]  [<ffffffff811b5192>] ? __inode_permission+0x22/0xb0
Jan 21 22:27:01 vagrant kernel: [  233.349269]  [<ffffffff811b58e6>] ? link_path_walk+0x256/0x870
Jan 21 22:27:01 vagrant kernel: [  233.349292]  [<ffffffff811c281a>] ? __d_lookup+0x7a/0x150
Jan 21 22:27:01 vagrant kernel: [  233.349979]  [<ffffffffa03f8914>] ? sf_dentry_revalidate+0x14/0x20 [vboxsf]
Jan 21 22:27:01 vagrant kernel: [  233.350641]  [<ffffffff811b47de>] ? lookup_fast+0x25e/0x2b0
Jan 21 22:27:01 vagrant kernel: [  233.351302]  [<ffffffff811b6055>] ? path_lookupat+0x155/0x780
Jan 21 22:27:01 vagrant kernel: [  233.351927]  [<ffffffffa03fa6ee>] ? VbglR0SfCreate+0x7e/0xa0 [vboxsf]
Jan 21 22:27:01 vagrant kernel: [  233.352603]  [<ffffffff811b66a6>] ? filename_lookup+0x26/0xc0
Jan 21 22:27:01 vagrant kernel: [  233.353267]  [<ffffffff811ba8e4>] ? user_path_at_empty+0x54/0x90
Jan 21 22:27:01 vagrant kernel: [  233.353855]  [<ffffffff810ed71e>] ? from_kgid_munged+0xe/0x20
Jan 21 22:27:01 vagrant kernel: [  233.354431]  [<ffffffff811af53a>] ? cp_new_stat+0x13a/0x160
Jan 21 22:27:01 vagrant kernel: [  233.354976]  [<ffffffff811af0e6>] ? vfs_fstatat+0x46/0x90
Jan 21 22:27:01 vagrant kernel: [  233.355536]  [<ffffffff811af57a>] ? SYSC_newstat+0x1a/0x40
Jan 21 22:27:01 vagrant kernel: [  233.356067]  [<ffffffff8151adcd>] ? system_call_fast_compare_end+0x10/0x15
Jan 21 22:27:01 vagrant kernel: [  233.356577] Code: 01 b9 ff ff ff ff 48 89 da 4c 89 d6 4c 89 ef e8 b6 df ff ff 41 89 c7 0f 1f 00 48 83 c4 40 44 89 f8 5b 41 5c 41 5d 41 5e 41 5f 5d <c3> 66 0f 1f 44 00 00 49 83 f8 17 0f 86 34 0c 00 00 48 8d 83 00 
Jan 21 22:27:01 vagrant kernel: [  233.358611] RIP  [<ffffffffa02666c1>] VGDrvCommonIoCtl+0x261/0x1bf0 [vboxguest]
Jan 21 22:27:01 vagrant kernel: [  233.359118]  RSP <ffff88007bdcfb98>
Jan 21 22:27:01 vagrant kernel: [  233.359636] ---[ end trace 54b9778e1a5d744b ]---
}}}

For reference, here's the Perl code that is used to cleanup the (empty cache files):

{{{
my $Wanted = sub {

    # Skip nonregular files and directories.
    return if ( !-f $File::Find::name );
    my $Stat = File::stat::stat($File::Find::name);
    if ( $Stat && ( time() - $Stat->ctime() > $CacheTTLSeconds ) ) {    ## no critic
        unlink $File::Find::name;    # Don't die here, this could be removed in the background by another process too.
    }
};
File::Find::find( $Wanted, $CacheDir );
}}}

Less often, a similar error occurs during the vagrant provisioning of the instances, where we copy the source code of our project from the /vagrant shared vboxsf folder into the VM. Here just a simple ""cp -r"" is used during the deployment. It could be the same problem:

{{{
==> default: Copying OTRS code to /opt/otrs
==> default: cp: cannot stat â/vagrant/Sources/otrs/var/httpd/htdocs/js/thirdparty/ckeditor-4.5.6/plugins/mathjax/lang/cy.jsâ: Protocol error
}}}

Please let me know if I should try to provide additional information, and thanks a lot for taking a look at this."	mrtngrnr
6600	VBoxService.exe does not terminate in os/2 guest	other	VirtualBox 3.1.6	2010-04-27T00:00:43Z	2010-12-06T04:22:48Z	2010-12-06T04:22:48Z	"When shutting down an os/2 guest, the Guest Addition VBoxService.exe does not terminate when it receives a Close signal. This prevents os/2 from continuing its shutdown procedure since it is waiting for VBoxService.exe to end. Deadlock.


"	James Moe
20790	vboxnetx adapters are having a wrong broadcast address	Linux	VirtualBox 6.1.32	2022-01-24T18:22:39Z	2022-02-01T13:11:49Z	2022-02-01T13:11:49Z	"If I create a hostonly adapter (e.g. vboxnet2) having the following IPV4 parameters:

Address: 10.10.10.1
Netmask: '''255.255.252.0'''

I expect the following result in my host:
# ip addr
6: vboxnet2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 0a:00:27:00:00:02 brd ff:ff:ff:ff:ff:ff
    inet 10.10.10.1/22 '''brd 10.10.11.255''' scope global vboxnet2

and NOT (see brd value)

6: vboxnet2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 0a:00:27:00:00:02 brd ff:ff:ff:ff:ff:ff
    inet 10.10.10.1/22 '''brd 10.10.10.255''' scope global vboxnet2

It seems that there is an error creating the broadcast value on the HOST."	gabrymark26
16695	VBoxNetNAT refuses connections for port-forwarding after one day or two	all	VirtualBox 5.1.20	2017-04-25T09:28:42Z	2017-04-25T12:17:09Z	2017-04-25T12:17:09Z	"I started using NAT network since several months ago.  My setup is quite simple: Linux host (CentOS 7.3) running two Windows 7 guests.  All guests use NAT network with static IPs.  Port-forwarding is configured on the NAT network.


{{{
NAT network: 10.0.2.1/24
Guest 1 IP: 10.0.2.11
Guest 2 IP: 10.0.2.12
Forward 1: <host_ip>:5911 <--> 10.0.0.11:5900
Forward 2: <host_ip>:5912 <--> 10.0.0.12:5900
}}}


Everything work great, until, after some time, maybe one day or two, connections to host port 2211/2212 got rejected.  One solution I find is to restart guest OS, sometime more than once, until the port-forward is normal again.

During the whole process (good --> bad --> restart --> good again), I can see that port 2211/2212 are always bound by process /usr/lib/virtualbox/VBoxNetNAT, and its pid never changed.

When connections are rejected on port 5911 and 5912, guests can connect to each other's 5900 port, which rules out guests failures.

Another observation is, sometimes the restart of one guest OS can solve problems for all guests.
"	Steve Sun
9166	vboxnet0 doesn't count traffic correctly (Linux host)	Windows	VirtualBox 4.0.10	2011-07-07T18:17:47Z	2015-04-28T04:17:29Z	2015-04-28T04:17:29Z	"On a Linux box with VirtualBox 4.0.10 installed and with a Windows XP virtual machine with default settings.

'''ifconfig vboxnet0''' does not show the reality :

{{{
[root@fedora15 ~]# ifconfig vboxnet0
vboxnet0  Link encap:Ethernet  HWaddr 0A:00:27:00:00:00
          inet adr:192.168.56.1  Bcast:192.168.56.255  Masque:255.255.255.0
          adr inet6: fe80::800:27ff:fe00:0/64 Scope:Lien
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1193 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:1000
          RX bytes:0 (0.0 b)  TX bytes:274935 (268.4 KiB)
}}}

I've transferred much more than 268.4 KiB and obviously received some data.

Problem can also be seen with ""tcpdump"" which shows traffic only in one direction and ""bwm-ng"" which doesn't show any traffic at all.

This ticket is related to this post http://forums.virtualbox.org/viewtopic.php?f=7&t=38499 and to a conversation I've had on IRC where I've been told to fill in a bug report.

The Linux host is a Fedora 15 up to date (07/07/2011).
Windows VM is also up to date.
"	a_i_
21148	VBoxManage: error: Invalid command 'hostonlynet'	other	VirtualBox 7.0.0	2022-10-14T11:51:07Z	2022-10-14T19:58:33Z	2022-10-14T19:58:33Z	"
The hostonlynet command is in the documentation but cannot be executed.

{{{
bash$ VBoxManage | grep hostonlynet
. . .
  VBoxManage hostonlynet add <--name=netname> [--id=netid] <--netmask=mask>
  VBoxManage hostonlynet modify <--name=netname | --id=netid> [--lower-ip=address]
  VBoxManage hostonlynet remove <--name=netname | --id=netid>

bash$ vboxmanage hostonlynet
. . .
VBoxManage: error: Invalid command 'hostonlynet'
}}}
"	mug896
15783	VBoxManage: error: Error starting guest session (current status is: starting)	Windows	VirtualBox 5.1.2	2016-08-12T09:32:41Z	2016-08-12T09:32:41Z	2016-08-12T09:32:41Z	"After upgrade from 5.0.26 to 5.1.2 we can not use our automated run sequences controlled by several VBoxManage guestcontrol <vm> run commands, because some of them are returned with the error message:

VBoxManage: error: Error starting guest session (current status is: starting)

This seems to occur not at the first launch of a guestcontrol command after starting the VM, but at one of the following. For example one of such sequence is:

{{{
> VBoxManage snapshot ${VM} restore ""${RestoreSnapshot}""
> VBoxManage  sharedfolder add ${VM} --name RunExecution --hostpath ${HostRunExecutionDirectory}/${BID} --automount
> VBoxManage startvm ""${VM}""  --type headless
> VBoxManage guestproperty get ""${VM}"" ""/VirtualBox/GuestInfo/Net/0/V4/IP""
> VBoxManage controlvm ""${VM}"" setvideomodehint 1920 1080 32
> VBoxManage guestcontrol ${VM} run --username ${VmUser} --password ${VmPassword} --wait-stdout -- \
  ""c:\windows\system32\xcopy.exe"" ""${RunExecutionDirectory}\\runtime-uitest"" ""C:\\runtime-uitest\\"" /r /y /s /i
('''failed''') > VBoxManage guestcontrol ${VM} run --no-wait-stdout --no-wait-stderr \
  --username ${VmUser} --password ${VmPassword} -- ""C:\Windows\system32\cmd.exe"" /c \
  ""${RunExecutionDrive} & cd ${RunExecutionDirectory} & ${RunExecutable} /param:dummy=dummy ""
}}}

Host: 
openSUSE 13.2 Linux r06268 3.16.7-7-desktop #1 SMP PREEMPT Wed Dec 17 18:00:44 UTC 2014 (762f27a) x86_64 x86_64 x86_64 GNU/Linux
VirtualBox-5.1-5.1.2_108956_openSUSE132-1.x86_64
Oracle_VM_VirtualBox_Extension_Pack-5.1.2-108956.vbox-extpack


Guests: 
Windows 7 Professional SP1 64 Bit
Windows Server 2012 R2 Standard
Oracle VM VirtualBox Guest Additions 5.1.2

Until solved we downgrade to 5.0.26.

"	rklehm
13516	VBoxManage stucks on long operations	Linux	VirtualBox 4.3.18	2014-10-16T12:32:58Z	2014-11-06T16:27:08Z	2014-11-06T16:27:08Z	"Host OS: openSUSE 13.1 or Fedora 20 or RHEL7
Guest OS: any linux I've tried so far.

Steps to reproduce:

1. Import provided OVA file at least 3 times, avoid spaces in VM name. Provided OVA is simple Fedora-20 install, cleaned from garbage, installed openjdk build dependencies and VBox guest additions, nothing special.

2. Change shared folder path to existing writable folder, but leave ""shared"" as name of share.

3. Install mercurial, run following command:
{{{ hg clone 'http://hg.openjdk.java.net/jdk8u/jdk8u/' && cd 'jdk8u' && bash get_source.sh }}}

4. Download jdk-7u67-linux-i586.tar.gz from http://java.sun.com

5. Start all imported VMs, does not matter headless or not.

6. Open number of terminals and run following command in each one of them, change path to jdk8u source, path to jdk-7u67 and name of VM:
{{{
while true; do bash vm-build.sh \
--with-major=8 \
--with-src=/home/user/src/jdk8u \
--with-tag=jdk8u20-b26 \
--with-boot-jdk=/home/user/jdk-7u67-linux-i586.tar.gz \
--with-vm=""Fedora-20-i586-test1"" ; done
}}}
7. Watch the output from time to time, it usually stucks during make pretty soon on at least 1 of the running VMs, usually during first or second iteration.


OVA file and 2 scripts:
https://drive.google.com/folderview?id=0B5Kp-cB1sXJrRDd6RlRwOGxLTTg&usp=sharing"	indifferent
15570	VBoxManage showvminfo fails to find machines	all	VirtualBox 5.0.24	2016-07-04T23:02:09Z	2016-07-04T23:16:24Z	2016-07-04T23:16:24Z	"Created VM ""W7"", then: 

# VBoxManage showvminfo W7
VBoxManage: error: Could not find a registered machine named 'W7'
VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBoxWrap, interface IVirtualBox, callee nsISupports
VBoxManage: error: Context: ""FindMachine(Bstr(VMNameOrUuid).raw(), machine.asOutParam())"" at line 2719 of file VBoxManageInfo.cpp

Added more VMs and problem persists."	Pierre Fortin
11489	vboxmanage showhdinfo does not work with relative pathes	all	VirtualBox 4.2.4	2013-02-13T22:22:35Z	2013-02-22T14:32:50Z	2013-02-22T14:32:50Z	"vboxmanage showhdinfo seems to be broken in 4.2.4 & 4.2.6[[BR]]

Some of my VDI disk :
{{{
virtualbox@gateway:~$ vboxmanage list hdds | grep vSRV001
Location:    /home/virtualbox/VirtualBox VMs/vSRV001/vSRV001-001.vdi
Usage:       vSRV001 (UUID: 30740f89-b026-466f-9b78-9cd8000e0f0d)

}}}

This works :

{{{
virtualbox@gateway:~$ vboxmanage showhdinfo ""/home/virtualbox/VirtualBox VMs/vSRV001/vSRV001-001.vdi""
UUID:                 f6c75dcf-682b-4396-9e49-54202f465afe
Accessible:           yes
Logical size:         20480 MBytes
Current size on disk: 14461 MBytes
Type:                 normal (base)
Storage format:       VDI
Format variant:       dynamic default
In use by VMs:        vSRV001 (UUID: 30740f89-b026-466f-9b78-9cd8000e0f0d)
Location:             /home/virtualbox/VirtualBox VMs/vSRV001/vSRV001-001.vdi
}}}

If I try using a . to refer from the current directory:
{{{
virtualbox@gateway:~$ pwd
/home/virtualbox
virtualbox@gateway:~$ vboxmanage showhdinfo ""./VirtualBox VMs/vSRV001/vSRV001-001.vdi""
VBoxManage: error: Cannot register the hard disk '/home/virtualbox/./VirtualBox VMs/vSRV001/vSRV001-001.vdi' {f6c75dcf-682b-4396-9e49-54202f465afe} because a hard disk '/home/virtualbox/VirtualBox VMs/vSRV001/vSRV001-001.vdi' with UUID {f6c75dcf-682b-4396-9e49-54202f465afe} already exists
VBoxManage: error: Details: code NS_ERROR_INVALID_ARG (0x80070057), component VirtualBox, interface IVirtualBox, callee nsISupports
VBoxManage: error: Context: ""OpenMedium(Bstr(pszFilenameOrUuid).raw(), enmDevType, enmAccessMode, fForceNewUuidOnOpen, pMedium.asOutParam())"" at line 178 of file VBoxManageDisk.cpp
}}}

But this would work:
{{{
virtualbox@gateway:~$ pwd
/home/virtualbox
virtualbox@gateway:~$ vboxmanage showhdinfo ""VirtualBox VMs/vSRV001/vSRV001-001.vdi""
UUID:                 f6c75dcf-682b-4396-9e49-54202f465afe
Accessible:           yes
Logical size:         20480 MBytes
Current size on disk: 14461 MBytes
Type:                 normal (base)
Storage format:       VDI
Format variant:       dynamic default
In use by VMs:        vSRV001 (UUID: 30740f89-b026-466f-9b78-9cd8000e0f0d)
Location:             /home/virtualbox/VirtualBox VMs/vSRV001/vSRV001-001.vdi
}}}

I understand the check to find if the disk has a corresponding UUID but the path check seems off to me."	Max D
20246	vboxmanage modifymedium lock not released immediately	other	VirtualBox 6.1.18	2021-03-11T22:43:53Z	2021-03-11T22:43:53Z	2021-03-11T22:43:53Z	"This is a host only issue.

Sometimes the lock of a medium during vboxmanage is still in effect after the command has completed. This is especially when the host cpu is heavily loaded. The following seems to work with a sleep trick. (Delay the next command, so the lock is released.)

vboxmanage modifymedium ""$parentmedium"" --compact && sleep 10s && touch -r ""$parentmedium"" ""${parentmedium}.stamp""

vboxmanage storageattach ""${parentvm}"" --storagectl ""${storagename}"" --port ${storageport} --device ${storagedevice} --type hdd --medium emptydrive && sleep 10s

vboxmanage modifymedium ""${parentmedium}"" --type immutable && sleep 10s

Example: https://github.com/nipatriknilsson/vboxcloneimmutable
"	Mrpn
18144	VBoxManage list usbhost fails to correctly identify USB Reader	Windows	VirtualBox 5.2.22	2018-11-22T08:38:36Z	2018-11-30T00:34:21Z	2018-11-30T00:34:21Z	"Here is the output of various commands that might be useful. My report and comments are disclosed below.

{{{
$ uname -a
Linux wangwq-mint 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64 GNU/Linux
}}}


{{{
$ sudo lsusb -vv -d 0000:a180
[sudo] wangwq 的密码：

Bus 001 Device 008: ID 0000:a180  
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x0000 
  idProduct          0xa180 
  bcdDevice            1.00
  iManufacturer           1 NARI
  iProduct                2 Sgchip Smart Card Reader
  iSerial                 0 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength          338
    bNumInterfaces          4
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              200mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass        11 Chip/SmartCard
      bInterfaceSubClass      0 
      bInterfaceProtocol      0 
      iInterface              3 Sgchip Dual Reader ICC 
      ChipCard Interface Descriptor:
        bLength                54
        bDescriptorType        33
        bcdCCID              1.10  (Warning: Only accurate for version 1.0)
        nMaxSlotIndex           0
        bVoltageSupport         7  5.0V 3.0V 1.8V 
        dwProtocols             3  T=0 T=1
        dwDefaultClock       4800
        dwMaxiumumClock      8000
        bNumClockSupported      0
        dwDataRate          10752 bps
        dwMaxDataRate      412903 bps
        bNumDataRatesSupp.      0
        dwMaxIFSD             254
        dwSyncProtocols  00000007  2-wire 3-wire I2C
        dwMechanical     00000000 
        dwFeatures       000207B2
          Auto configuration based on ATR
          Auto clock change
          Auto baud rate change
          Auto PPS made by CCID
          CCID can set ICC in clock stop mode
          NAD value other than 0x00 accepted
          Auto IFSD exchange
          Short APDU level exchange
        dwMaxCCIDMsgLen       271
        bClassGetResponse    echo
        bClassEnvelope       echo
        wlcdLayout           none
        bPINSupport             0 
        bMaxCCIDBusySlots       1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval              32
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass        11 Chip/SmartCard
      bInterfaceSubClass      0 
      bInterfaceProtocol      0 
      iInterface              4 Sgchip Dual Reader PICC
      ChipCard Interface Descriptor:
        bLength                54
        bDescriptorType        33
        bcdCCID              1.10  (Warning: Only accurate for version 1.0)
        nMaxSlotIndex           0
        bVoltageSupport         7  5.0V 3.0V 1.8V 
        dwProtocols             2  T=1
        dwDefaultClock       4000
        dwMaxiumumClock      4000
        bNumClockSupported      0
        dwDataRate          10752 bps
        dwMaxDataRate      250000 bps
        bNumDataRatesSupp.      0
        dwMaxIFSD             256
        dwSyncProtocols  00000000 
        dwMechanical     00000000 
        dwFeatures       00020040
          Auto parameter negotation made by CCID
          Short APDU level exchange
        dwMaxCCIDMsgLen       271
        bClassGetResponse      00
        bClassEnvelope         00
        wlcdLayout           none
        bPINSupport             0 
        bMaxCCIDBusySlots       1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval               2
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x04  EP 4 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x84  EP 4 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        2
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass        11 Chip/SmartCard
      bInterfaceSubClass      0 
      bInterfaceProtocol      0 
      iInterface              5 Sgchip Dual Reader SAM 
      ChipCard Interface Descriptor:
        bLength                54
        bDescriptorType        33
        bcdCCID              1.10  (Warning: Only accurate for version 1.0)
        nMaxSlotIndex           0
        bVoltageSupport         2  3.0V 
        dwProtocols             3  T=0 T=1
        dwDefaultClock       3580
        dwMaxiumumClock     14320
        bNumClockSupported      0
        dwDataRate           9600 bps
        dwMaxDataRate     2703401 bps
        bNumDataRatesSupp.      0
        dwMaxIFSD             252
        dwSyncProtocols  00000000 
        dwMechanical     00000000 
        dwFeatures       000100BA
          Auto configuration based on ATR
          Auto voltage selection
          Auto clock change
          Auto baud rate change
          Auto PPS made by CCID
          TPDU level exchange
        dwMaxCCIDMsgLen       271
        bClassGetResponse    echo
        bClassEnvelope       echo
        wlcdLayout           none
        bPINSupport             0 
        bMaxCCIDBusySlots       1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x85  EP 5 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval               2
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x06  EP 6 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x86  EP 6 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        3
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass        11 Chip/SmartCard
      bInterfaceSubClass      0 
      bInterfaceProtocol      0 
      iInterface              6 Sgchip Dual Reader SAM2
      ChipCard Interface Descriptor:
        bLength                54
        bDescriptorType        33
        bcdCCID              1.10  (Warning: Only accurate for version 1.0)
        nMaxSlotIndex           0
        bVoltageSupport         2  3.0V 
        dwProtocols             3  T=0 T=1
        dwDefaultClock       3580
        dwMaxiumumClock     14320
        bNumClockSupported      0
        dwDataRate           9600 bps
        dwMaxDataRate     2703401 bps
        bNumDataRatesSupp.      0
        dwMaxIFSD             252
        dwSyncProtocols  00000000 
        dwMechanical     00000000 
        dwFeatures       000100BA
          Auto configuration based on ATR
          Auto voltage selection
          Auto clock change
          Auto baud rate change
          Auto PPS made by CCID
          TPDU level exchange
        dwMaxCCIDMsgLen       271
        bClassGetResponse    echo
        bClassEnvelope       echo
        wlcdLayout           none
        bPINSupport             0 
        bMaxCCIDBusySlots       1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x07  EP 7 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x87  EP 7 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
Device Status:     0x0000
  (Bus Powered)
}}}


{{{
$ sudo VBoxManage list -l usbhost
Host USB Devices:

UUID:               4a8de244-7a20-4628-b37b-ccf8dc8d5eb3
VendorId:           0x147e (147E)
ProductId:          0x1002 (1002)
Revision:           0.72 (0072)
Port:               2
USB version/speed:  1/Full
Manufacturer:       UPEK
Product:            TouchStrip Fingerprint Sensor      
Address:            sysfs:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3//device:/dev/vboxusb/001/004
Current State:      Captured

UUID:               2d39f89a-f8da-491e-8fdd-83194944aaf9
VendorId:           0x093a (093A)
ProductId:          0x2510 (2510)
Revision:           1.0 (0100)
Port:               1
USB version/speed:  1/Low
Manufacturer:       PixArt
Product:            USB Optical Mouse
Address:            sysfs:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2//device:/dev/vboxusb/003/002
Current State:      Busy

UUID:               38696f50-c6ad-4b9c-8953-48d5beda95bd
VendorId:           0x04f2 (04F2)
ProductId:          0xb2ea (B2EA)
Revision:           5.24 (0524)
Port:               5
USB version/speed:  2/High
Manufacturer:       Chicony Electronics Co., Ltd.
Product:            Integrated Camera
Address:            sysfs:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6//device:/dev/vboxusb/001/006
Current State:      Busy

}}}


{{{
$ dmesg
...
[13121.127104] usb 1-1.2: new full-speed USB device number 8 using ehci-pci
[13121.243283] usb 1-1.2: New USB device found, idVendor=0000, idProduct=a180
[13121.243287] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[13121.243290] usb 1-1.2: Product: Sgchip Smart Card Reader
[13121.243292] usb 1-1.2: Manufacturer: NARI

}}}


I have properly working Virtualbox and full list of USB devices available inside Windows guest OS. The problem I face is that a specific USB serial device 0000:a180 is not properly exposed by ""VBoxManage list -l usbhost"" and respectively not properly passed-through to Windows guest. All other devices are properly passed-through.

"	XiaoQ
15534	VBoxManage hostonlyif ipconfig vboxnet1 --dhcp leads to error	Linux	VirtualBox 5.0.22	2016-06-19T20:56:24Z	2016-07-13T19:51:07Z	2016-07-13T19:51:07Z	"Host type: Debian jessie amd64

Trying to configure vboxnet1 to use dhcp after creating it leads to the following error:

{{{
VBoxManage: error: Code NS_ERROR_NOT_IMPLEMENTED (0x80004001) - Not implemented (extended info not available)
VBoxManage: error: Context: ""EnableDynamicIPConfig()"" at line 210 of file VBoxManageHostonly.cpp 
}}}

Steps to reproduce:
* create hostonlyif with ''VBoxManage hostonlyif create''
* call ''VBoxManage hostonlyif ipconfig vboxnet1 --dhcp''  (replace vboxnet1 by the name you get from V''BoxManage list hostonlyifs'' after creating it.

Using the VBoxNetworkName: ( HostInterfaceNetworking-vboxnet1 ) instead of vboxnet1 did not change anything.

"	manschenk
17792	vboxmanage guestcontrol run --exe doesn't display any output	Linux	VirtualBox 5.2.12	2018-05-31T00:23:33Z	2018-05-31T09:19:03Z	2018-05-31T09:19:03Z	"Hello,

== 
The vboxmanage guestcontrol run/start doesn't show any information on the standard output. ==
 
I have tried with the --wait-stdout and/or --wait-stderr but nothing change.
Sessions seems to be created but I even obtain acore dumped while watching operation.
Here my details :

What I do :
{{{
[fredmj@Lagrange ~]$ vboxmanage --nologo guestcontrol ""CENTOS7.TMP"" --verbose run --exe ""/bin/ls"" --username fredmj --password dummyPass --wait-stdout

}}}


{{{
[fredmj@Lagrange ~]$ vboxmanage guestcontrol CENTOS7.TMP watch
Session ID=1 ""[12121] VBoxManage Guest Control [CENTOS7.TMP] - start"" unregistered
Session ID=2 ""[12154] VBoxManage Guest Control [CENTOS7.TMP] - start"" unregistered
Session ID=3 ""[12186] VBoxManage Guest Control [CENTOS7.TMP] - run"" unregistered
Session ID=1 ""[12806] VBoxManage Guest Control [CENTOS7.TMP] - run"" registered
Process ""/bin/ls"" registered
Process PID=15554 ""/bin/ls"" changed status to [started]
Process PID=15554 ""/bin/ls"" changed status to [successfully terminated]
Session ID=1 ""[12806] VBoxManage Guest Control [CENTOS7.TMP] - run"" unregistered
Erreur de segmentation (core dumped)

}}}


My configuration:

{{{
[fredmj@Lagrange ~]$ cat /etc/redhat-release 
CentOS Linux release 7.5.1804 (Core)
}}}
 


{{{
[fredmj@Lagrange ~]$ vboxmanage --version
5.2.12r122591
}}}



{{{
[fredmj@Lagrange ~]$ vboxmanage showvminfo CENTOS7.TMP
Name:            CENTOS7.TMP
Groups:          /BuildingBlocksLab
Guest OS:        Red Hat (64-bit)
UUID:            f415d3d3-cc35-488a-82d4-a9dbfd529cca
Config file:     /home/fredmj/VirtualBox VMs/BuildingBlocksLab/CENTOS7.TMP/CENTOS7.TMP.vbox
Snapshot folder: /home/fredmj/VirtualBox VMs/BuildingBlocksLab/CENTOS7.TMP/Snapshots
Log folder:      /home/fredmj/VirtualBox VMs/BuildingBlocksLab/CENTOS7.TMP/Logs
Hardware UUID:   f415d3d3-cc35-488a-82d4-a9dbfd529cca
Memory size:     1024MB
Page Fusion:     off
VRAM size:       16MB
CPU exec cap:    100%
HPET:            off
Chipset:         piix3
Firmware:        BIOS
Number of CPUs:  1
PAE:             on
Long Mode:       on
Triple Fault Reset: off
APIC:            on
X2APIC:          on
CPUID Portability Level: 0
CPUID overrides: None
Boot menu mode:  message and menu
Boot Device (1): Floppy
Boot Device (2): DVD
Boot Device (3): HardDisk
Boot Device (4): Not Assigned
ACPI:            on
IOAPIC:          on
BIOS APIC mode:  APIC
Time offset:     0ms
RTC:             UTC
Hardw. virt.ext: on
Nested Paging:   on
Large Pages:     off
VT-x VPID:       on
VT-x unr. exec.: on
Paravirt. Provider: Default
Effective Paravirt. Provider: KVM
State:           running (since 2018-05-30T23:32:13.661000000)
Monitor count:   1
3D Acceleration: off
2D Video Acceleration: off
Teleporter Enabled: off
Teleporter Port: 0
Teleporter Address: 
Teleporter Password: 
Tracing Enabled: off
Allow Tracing to Access VM: off
Tracing Configuration: 
Autostart Enabled: off
Autostart Delay: 0
Default Frontend: 
Storage Controller Name (0):            IDE
Storage Controller Type (0):            PIIX4
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0):  2
Storage Controller Port Count (0):      2
Storage Controller Bootable (0):        on
Storage Controller Name (1):            SATA
Storage Controller Type (1):            IntelAhci
Storage Controller Instance Number (1): 0
Storage Controller Max Port Count (1):  30
Storage Controller Port Count (1):      2
Storage Controller Bootable (1):        on
IDE (1, 0): Empty
SATA (0, 0): /home/fredmj/VirtualBox VMs/BuildingBlocksLab/CENTOS7.TMP/CENTOS7.TMP.vdi (UUID: 92b5d7ab-8cac-41cf-ae63-98c5d51205c9)
SATA (1, 0): /usr/share/virtualbox/VBoxGuestAdditions.iso (UUID: 3cc8e4fb-e56e-4eb6-a214-d1be7ca16272)
NIC 1:           MAC: 080027A06520, Attachment: Bridged Interface 'wlp2s0', Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none
NIC 2:           disabled
NIC 3:           disabled
NIC 4:           disabled
NIC 5:           disabled
NIC 6:           disabled
NIC 7:           disabled
NIC 8:           disabled
Pointing Device: PS/2 Mouse
Keyboard Device: PS/2 Keyboard
UART 1:          disabled
UART 2:          disabled
UART 3:          disabled
UART 4:          disabled
LPT 1:           disabled
LPT 2:           disabled
Audio:           enabled (Driver: PulseAudio, Controller: AC97, Codec: AD1980)
Audio playback:  disabled
Audio capture: enabled
Clipboard Mode:  disabled
Drag and drop Mode: disabled
Session name:    headless
Video mode:      800x600x32 at 0,0 enabled
VRDE:            disabled
USB:             enabled
EHCI:            disabled
XHCI:            disabled

USB Device Filters:

<none>

Available remote USB devices:

<none>

Currently Attached USB Devices:

<none>

Bandwidth groups:  <none>

Shared folders:  <none>

VRDE Connection:    not active
Clients so far:     0

Capturing:          not active
Capture audio:      not active
Capture screens:    0
Capture file:       /home/fredmj/VirtualBox VMs/BuildingBlocksLab/CENTOS7.TMP/CENTOS7.TMP.webm
Capture dimensions: 1024x768
Capture rate:       512 kbps
Capture FPS:        25
Capture options:    ac_enabled=false

Guest:

Configured memory balloon size:      0 MB
OS type:                             Linux26_64
Additions run level:                 2
Additions version:                   5.2.12 r122591


Guest Facilities:

Facility ""VirtualBox Base Driver"": active/running (last update: 2018/05/30 21:35:01 UTC)
Facility ""VirtualBox System Service"": active/running (last update: 2018/05/30 21:35:03 UTC)
Facility ""Seamless Mode"": not active (last update: 2018/05/30 21:35:01 UTC)
Facility ""Graphics Mode"": not active (last update: 2018/05/30 21:35:01 UTC)

}}}

"	Frédéric MARIE-JOSEPH
17057	VBoxManage freezes	Windows	VirtualBox 5.1.26	2017-09-06T07:17:59Z	2018-08-27T12:44:32Z	2018-08-27T12:44:32Z	"Since the latest release of vbox (5.1.26), vboxmanage suddenly freezes. I'm able to run vboxmanage from command line (e.g. vboxmanage --version) but it appears that it is no longer able to communicate with the virtual machines. e.g.

{{{
VBoxManage showvminfo TEST-W10
VBoxManage controlvm TEST-W10 screenshotpn /tmp/test.png
etc...
}}}

Running these commands will not return anything (the command ""freezes"" and I have to hit CTRL+C to aboard it). This happens every 1-3 days.

The VMs are still running (and I can connect to them via vbox RDP), but I'm not able to control them on the host anymore (via vboxmanage). The only way to get it running again is to kill all VMs (killall VBoxHeadless) and do a complete reboot of the system.


{{{
OS:
Distributor ID:	Ubuntu
Description:	Ubuntu 16.04.3 LTS
Release:	16.04
Codename:	xenial


Kernel:
Linux X 4.4.0-93-generic #116-Ubuntu SMP Fri Aug 11 21:17:51 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

VBox:
5.1.26

Virtual Additions:
None

}}}
"	LennyHers
18571	Vboxmanage export / import not working - invalid 'ovf:id' attribute	Linux	VirtualBox 5.2.28	2019-04-18T06:58:57Z	2019-04-19T08:05:40Z	2019-04-19T08:05:40Z	"I'm running am Ubuntu 18.04.2 LTS Server with Virtualbox 5.2.28

Exporting an virtual machine with command line works without any reported error. Result is an *.ova file.

Importing this machine with the command vboxmanage import file.ova ends with this error:

root@nono2018:~# vboxmanage import 20210417_ADC2.ova
0%...
Progress state: VBOX_E_FILE_ERROR
VBoxManage: error: Appliance read failed
VBoxManage: error: Error reading ""/root/20210417_ADC2.ova"": missing or invalid 'ovf:id' attribute in operating system section element, line 18
VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component ApplianceWrap, interface IAppliance
VBoxManage: error: Context: ""RTEXITCODE handleImportAppliance(HandlerArg*)"" at line 307 of file VBoxManageAppliance.cpp

If I open the *.ova file with a editor, i can see
<Section xsi:type=""ovf:OperatingSystemSection_Type"" ovf:id=""-1160446143"">

Why is the ovf:id negativ?

Any suggestion to solve the problem?

Regards
Michael"	Curval1230
13275	VBoxManage does not set hostonly adapter name	Linux	VirtualBox 4.3.14	2014-08-11T11:53:49Z	2014-10-18T09:07:02Z	2014-10-18T09:07:02Z	"I've got a script that creates VM's for me and one of the lines is this one:
VBoxManage modifyvm ""$VM"" --nic2 hostonly --hostonlyadapter1 'vboxnet0'

I can see the adapter in the network section in the GUI, however the name is blank. To populate the name I need to use the GUI and enter Settings, Network, applicable adapter and press Ok. I.e. I do not need to change anything, just press Ok for the hostonly adapter to have the name set."	Onkelringnes
16437	VBoxManage controlvm savestate fails with NS_ERROR_FAILURE (0x80004005)	Linux	VirtualBox 5.1.14	2017-01-31T13:27:07Z	2017-01-31T14:09:22Z	2017-01-31T14:09:22Z	"When I call 
{{{
VBoxManage controlvm bosh-lite_default_1485866280659_36137 savestate
}}}
from a bash script I get the following error:


{{{
VBoxManage controlvm bosh-lite_default_1485866280659_36137 savestate
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...
Progress state: NS_ERROR_FAILURE
VBoxManage: error: Failed to save machine state
VBoxManage: error: Code NS_ERROR_FAILURE (0x80004005) - Operation failed (extended info not available)
VBoxManage: error: Context: ""RTEXITCODE handleControlVM(HandlerArg*)"" at line 276 of file VBoxManageControlVM.cpp

}}}

'''Environment:'''

VBoxManage: Oracle VM VirtualBox Command Line Management Interface Version 5.1.14

Host operating system: CentOS Linux release 7.2.1511 (Core)

Guest operating system: Ubuntu 14.04.4 LTS"	acho-bacho
6132	VBoxManage confuses VM names starting with dash character (-) with command line option names	Linux	VirtualBox 3.1.2	2010-02-04T14:22:48Z	2010-02-04T14:22:48Z	2010-02-04T14:22:48Z	"When playing with VBoxManage I created a VM with name ""--ostype"" (by mistake - there was an error in my shell script that invoked VBoxManage)

I found that I cannot delete this VM with ""unregistervm"". All other VBoxManage commands also failed with the message ""unknown option: --ostype"" when I specified ""--ostype"" as VM name.

Putting the name in various kinds of quotes did not help, so eventually I had to manually edit !VirtualBox.xml to remove the VM.

Apparently, VBoxManage confuses VM names starting with dash character (-) with command line option names. !VirtualBox GUI does not have such problem."	xlogger
20208	vboxmanage clonevm crashes VBoxSVC	all	VirtualBox 6.1.18	2021-02-19T17:36:18Z	2021-02-19T17:36:18Z	2021-02-19T17:36:18Z	"I'm trying to run a script [1] to clone VirtualBox VMs. I run these three examples given at the link in parallel. They are all started almost simultaneously.

During the run when the first has finished (ubuntu focal mate), the other ones gets warnings of that they need to shutdown. 

If I still run them all to the end the following happens:

1) ""Ubuntu Mate Focal"" finishes. 'vboxmanage clonevm ""${parentvm}"" --name ""${childvm}"" --register' writes the new instance to disk, but does not appear in the Manager list. No errors reported.

2) ""Kali Linux"" and ""Shellter"" still running. They got a log entry saying:

01:57:46.655025 VirtualBoxClient: detected unresponsive VBoxSVC (rc=NS_ERROR_CALL_FAILED)

01:58:16.598405 VirtualBoxClient: detected unresponsive VBoxSVC (rc=NS_ERROR_CALL_FAILED)

A popup at each of the two instances tells the instance needs to finish. I ignore these messages and let them run to the end.

3) After the remaining scripts are finished, data from them also appears on disk but not in the Manager. All three are written correctly.

4) After killing (both with SIGTERM) the manager and the server, starting the manager again all appears in the list and can be run.

Bug entry message from VBoxSVC is:
---
Log created: 2021-02-19T02:06:16.959798000Z
Process ID:  2620270 (0x27fb6e)
Parent PID:  1 (0x1)
Executable:  /usr/lib/virtualbox/VBoxSVC
Arg[0]: /usr/lib/virtualbox/VBoxSVC
Arg[1]: --auto-shutdown
AddRef: illegal refcnt=3221225469 state=2
---

All logs attached.

[1] https://github.com/nipatriknilsson/vboxcloneimmutable
"	Mrpn
17570	vboxmanage cli - Segmentation fault	Linux	VirtualBox 5.2.6	2018-02-27T13:06:22Z	2018-06-14T12:42:52Z	2018-06-14T12:42:52Z	"I'm running CentOS 7 on a dedicated server. And was running a single Linux Guest deployed via VBOX and Vbox-web. Since last year mid Oct I have not been able to use this setup any more. All commands result in segmentation fault.

I have updated Vbox , OS, all packages, rebooted the server. All without any result.
{{{
root@dedi ~ # cat /etc/centos-release
CentOS Linux release 7.4.1708 (Core) 
}}}
{{{
root@dedi ~ # rpm -qa | grep VirtualBox
VirtualBox-5.2-5.2.6_120293_el7-1.x86_64
}}}

dmesg results in the below being logged
{{{
[746521.108089] vboxwebsrv[20856]: segfault at c ip 00007fac8d5fdb65 sp 00007ffe6872ea78 error 6 in libcrypto.so.1.0.2k[7fac8d58d000+234000]
[747035.697541] VBoxManage[23082]: segfault at 9 ip 00007fe6f8fb7b65 sp 00007ffed3c10ec8 error 6 in libcrypto.so.1.0.2k[7fe6f8f47000+234000]
[747292.271164] VBoxManage[24094]: segfault at 9 ip 00007f7eb7d20b65 sp 00007ffe5c8262b8 error 6 in libcrypto.so.1.0.2k[7f7eb7cb0000+234000]
[747329.919469] vboxwebsrv[24204]: segfault at c ip 00007f90a5595b65 sp 00007fff96e61938 error 6 in libcrypto.so.1.0.2k[7f90a5525000+234000]
}}}"	ahurjui
19703	VBoxManage and VirtualBox Manager lock up	all	VirtualBox 6.0.22	2020-07-06T10:18:37Z	2020-07-06T10:26:57Z	2020-07-06T10:26:57Z	"On 4.15.0-108-generic my VirtualBox works fine. Upgrading to 4.15.0-109-generic seems to be a problem for managing Virtual Machines on Virtualbox 6.022 r137980.

VBoxManage as well as VirtualBox Manager seem to lock up when using that version. Virtual Machines just run, until you try to shut them down.

VirtualBox Manager doesn't update the screen anymore. VBoxManage just hangs. Only reboot seems to solve the issue.

I reverted back from 108 to 109 and everything seems to be okay again.

Not 100% sure if it is this upgrade, but it appears so. Thought I better report."	NickGuus
17529	VBoxManage and Guest Additions 5.x.y: Can't communicate with FreeBSD Guests	BSD	VirtualBox 5.2.6	2018-02-06T11:32:10Z	2021-03-18T09:37:39Z	2021-03-18T09:37:39Z	"I've been trying to get FreeBSD to work with VBoxManage for a while (in fact for several years, since 9.3).

This is the result of testing VirtualBox 5.2.6 on Ubuntu with FreeBSD-11.1-RELEASE-amd64 as guest. 

{{{
$ VBoxManage guestcontrol freebsd-11.1-amd64 --username root --password 2Hard2Crack stat /tmp --verbose
Creating guest session as user 'root'...
Waiting for guest session to start...
VBoxManage: error: The specified user was not able to logon on guest
VBoxManage: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005), component GuestSessionWrap, interface IGuestSession, callee nsISupports
VBoxManage: error: Context: ""WaitForArray(ComSafeArrayAsInParam(aSessionWaitFlags), 30 * 1000, &enmWaitResult)"" at line 938 of file VBoxManageGuestCtrl.cpp
Closing guest session ...
}}}

Guest Additions were installed with pkg:
{{{
[root@freebsd ~]# pkg install -y virtualbox-ose-additions
[root@freebsd ~]# sysrc vboxguest_enable=""YES""
vboxguest_enable: NO -> YES
[root@freebsd ~]# sysrc vboxservice_enable=""YES""
vboxservice_enable: NO -> YES
[root@freebsd ~]# reboot
}}}

Guest Additions kernel module is loaded in Guest:
{{{
[root@freebsd ~]# VBoxService --version
5.2.4r119758
[root@freebsd ~]# kldstat|grep vbox
 3    1 0xffffffff8221f000 2eacb    vboxguest.ko
}}}"	Jonas Almroth
17490	VBoxManage and Guest Additions 5.2.x: Can't communicate with Linux Guests	Linux	VirtualBox 5.2.6	2018-01-22T13:41:36Z	2018-08-29T02:14:05Z	2018-08-29T02:14:05Z	"VirtualBox was updated from 5.0.32 (very stable version) to 5.2.4 and later 5.2.6.

All VM:s are provisioned through VBoxManage, but with Guest Additions 5.2.x on Linux guests, the VBoxManage processes just hang. Windows guests work fine, though.

So, with VirtualBox 5.2.6 and Guest Additions Version:

5.2.0-Hangs

5.2.2-Hangs

5.2.4-Hangs

5.2.6-Hangs

5.2.7-120349-Hangs

5.1.30-Works!"	Jonas Almroth
17644	VBoxHeadless crash	Linux	VirtualBox 5.2.8	2018-03-28T13:02:23Z	2018-04-23T15:29:29Z	2018-04-23T15:29:29Z	"Hi everyone.

Since our VirtualBox upgrade (5.0.40 -> 5.2.8), we started seeing some VBoxHeadless process disappearing. 

Crash file attached.

We'll be glad to help you in any way we can to fix investigate the issue.
"	srats
16999	VBoxDrv: Too many CPUs (288) for the GIP (max 256)	other	VirtualBox 5.1.26	2017-08-11T09:36:05Z	2017-08-12T04:36:54Z	2017-08-12T04:36:54Z	"The initialization  here:

{{{
include/iprt/types.h:# define RTCPUSET_MAX_CPUS      256
}}}

and the check : 

{{{
    /*
     * Check the CPU count.
     */
    cCpus = RTMpGetArraySize();
    if (   cCpus > RTCPUSET_MAX_CPUS
#if RTCPUSET_MAX_CPUS != 256
        || cCpus > 256 /* ApicId is used for the mappings */
#endif
        )
    {
        SUPR0Printf(""VBoxDrv: Too many CPUs (%u) for the GIP (max %u)\n"", cCpus, RT_MIN(RTCPUSET_MAX_CPUS, 256));
        return VERR_TOO_MANY_CPUS;
    }

}}}

in file src/VBox/HostDrivers/Support/SUPDrvGip.cpp  prevents installation of virtualbox on (Linux) server with > 256 cores.

"	okkhoy
17683	vboxdrv.sh: failed: modprobe vboxpci failed with linux 4.15 (centos7) -> fixed after (not in) 5.1.36	other	VirtualBox 5.1.34	2018-04-13T10:06:03Z	2018-04-18T15:46:01Z	2018-04-18T15:46:01Z	"centos7  update kernel to 4.15.11 elrepo ,and vbox install have some problems with ""vboxpci: 

Unknown symbol vfs_write (err 0)""
{{{
uname -a
Linux crmdev205 4.15.11-1.el7.elrepo.x86_64 #1 SMP Mon Mar 19 11:46:06 EDT 2018 x86_64 x86_64 

x86_64 GNU/Linux


 ./VirtualBox-5.1.34-121010-Linux_amd64.run 
Verifying archive integrity... All good.
Uncompressing VirtualBox for Linux installation.............
VirtualBox Version 5.1.34 r121010 (2018-02-26T15:29:57Z) installer
Removing previous installation of VirtualBox 5.1.32 r120294 from /opt/VirtualBox
Installing VirtualBox to /opt/VirtualBox
Python found: python, installing bindings...
vboxdrv.sh: failed: modprobe vboxpci failed. Please use 'dmesg' to find out why.

There were problems setting up VirtualBox.  To re-start the set-up process, run
  /sbin/vboxconfig
as root.

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.

[root@crmdev205 soft]# dmesg | tail -f 
[1746570.104013] vboxdrv: Successfully loaded version 5.1.34 (interface 0x002a0000)
[1746570.312366] VBoxNetFlt: Successfully started.
[1746570.318263] VBoxNetAdp: Successfully started.
[1746570.321467] vboxpci: Unknown symbol vfs_write (err 0)
[1747176.620175] vboxdrv: Found 32 processor cores
[1747176.635978] vboxdrv: TSC mode is Invariant, tentative frequency 1999998028 Hz
[1747176.635979] vboxdrv: Successfully loaded version 5.1.34 (interface 0x002a0000)
[1747176.840965] VBoxNetFlt: Successfully started.
[1747176.844354] VBoxNetAdp: Successfully started.
[1747176.846577] vboxpci: Unknown symbol vfs_write (err 0)
}}}"	zw
18771	vboxdrv.sh does not attempt to build modules on Fedora if Secure Boot is enabled	other	VirtualBox 6.0.10	2019-07-18T14:28:35Z	2019-07-18T16:48:12Z	2019-07-18T16:48:12Z	"When running vboxdrv.sh with Secure Boot enabled it exits with the message ""You must sign these kernel modules before using VirtualBox..."" before checking if the modules have been built."	thomasfedb
21435	Vboxdrv module triggers IBT protection. VM's fail to start	all	VirtualBox-7.0.6	2023-01-26T15:14:43Z	2023-01-26T15:14:43Z	2023-01-26T15:14:43Z	"This has been a problem for a while: The vboxdrv triggers IBT (indirect branch tracking) protection on modern Intel cpu's. This causes the VM to refuse to load.

Disabling IBT (booting the kernel with `ibt=off`) will make the problem disappear, but the protections are there for a reason. IBT is enabled by default on Arch Linux, but I believe IBT will be enabled by default in the upcoming 6.2 linux kernel release for Intel CPU's from the 11th generation up to the current (13th) gen. More and more CPU's will be affected.

A full log from trying to start a VM is attached. Though it is very short, nothing more happens. Also attached is dmesg output showing the protection being triggered in the kernel when starting a VM.

A bug report was also made filed with the kernel (https://bugzilla.kernel.org/show_bug.cgi?id=216102) and in Arch (https://bugs.archlinux.org/task/75481), but the latter suggested to file a bug with Virtualbox, which is what I'm doing now. Please let me know if I can provide more information.

Thanks!"	bepaald
14106	vboxdrv initscript $SHUTDOWN fix	all	VirtualBox 4.3.26	2015-05-11T12:23:28Z	2015-05-11T12:23:28Z	2015-05-11T12:23:28Z	"I experienced issues when shutting down VM's with the provided init scripts especially if they are not subject to the autostart service when setting the variable $SHUTDOWN_USERS as documented in /etc/init.d/vboxdrv:
Either VboxXPCOMIPCD is not running any more and gives me error messages or the kernel modules cannot be unloaded properly because VboxXPCOMIPCD is still running when using
{{{
 service vboxdrv stop
}}}
.

So I've done the following to /etc/init.d/vboxdrv:
* checking whether VboxXPIPCD ist still alive before trying to determine the status of running vms or trying to unload the kernel modules in stop_vms() and dmnstatus()
* enhancing the way the script waits for an ACPI shutdown with a configurable $SHUTDOWN_ACPI_TIMEOUT in stop_vms()
* provide a failover method $SHUTDOWN_ACPI_ACTION_FAILURE if ACPI shutdown is not successful (poweroff or savestate) in stop_vms()



{{{
254a255,278
> # the following is optional:
> #   SHUTDOWN_ACPI_TIMEOUT
> #     how long to wait for acpi shutdown of all vms
> #   SHUTDOWN_ACPI_ACTION_FAILURE=poweroff
> #   SHUTDOWN_ACPI_ACTION_FAILURE=savestate
> #     select failure action rather than terminating,
> #     defaults to poweroff
> 
> poweroff_vms() {
>     begin_msg ""Powering off remaining VMs""
>     for v in $1; do
>         $VBOXMANAGE --nologo controlvm $v poweroff
>     done
>     succ_msg
> }
> 
> savestate_vms() {
>     begin_msg ""Powering off remaining VMs""
>     for v in $1; do
>         $VBOXMANAGE --nologo controlvm $v savestate
>     done
>     succ_msg
> }
> 
258,282c282,323
<     for i in $SHUTDOWN_USERS; do
<         # don't create the ipcd directory with wrong permissions!
<         if [ -d /tmp/.vbox-$i-ipc ]; then
<             export VBOX_IPC_SOCKETID=""$i""
<             VMS=`$VBOXMANAGE --nologo list runningvms | sed -e 's/^"".*"".*{\(.*\)}/\1/' 2>/dev/null`
<             if [ -n ""$VMS"" ]; then
<                 if [ ""$SHUTDOWN"" = ""poweroff"" ]; then
<                     begin_msg ""Powering off remaining VMs""
<                     for v in $VMS; do
<                         $VBOXMANAGE --nologo controlvm $v poweroff
<                     done
<                     succ_msg
<                 elif [ ""$SHUTDOWN"" = ""acpibutton"" ]; then
<                     begin_msg ""Sending ACPI power button event to remaining VMs""
<                     for v in $VMS; do
<                         $VBOXMANAGE --nologo controlvm $v acpipowerbutton
<                         wait=30
<                     done
<                     succ_msg
<                 elif [ ""$SHUTDOWN"" = ""savestate"" ]; then
<                     begin_msg ""Saving state of remaining VMs""
<                     for v in $VMS; do
<                         $VBOXMANAGE --nologo controlvm $v savestate
<                     done
<                     succ_msg
---
>     #see whether we can contact ipcd to avoid error message
>     if pgrep VBoxXPCOMIPCD>/dev/null; then
>         for i in $SHUTDOWN_USERS; do
>             # don't create the ipcd directory with wrong permissions!
>             if [ -d /tmp/.vbox-$i-ipc ]; then
>                 export VBOX_IPC_SOCKETID=""$i""
>                 VMS=`$VBOXMANAGE --nologo list runningvms | sed -e 's/^"".*"".*{\(.*\)}/\1/' 2>/dev/null`
>                 if [ -n ""$VMS"" ]; then
>                     if [ ""$SHUTDOWN"" = ""poweroff"" ]; then
>                         poweroff_vms $VMS
>                     elif [ ""$SHUTDOWN"" = ""acpibutton"" ]; then
>                         begin_msg ""Sending ACPI power button event to remaining VMs""
>                         for v in $VMS; do
>                             $VBOXMANAGE --nologo controlvm $v acpipowerbutton
>                         done
>                         succ_msg
>                         if [ -n ""$SHUTDOWN_ACPI_TIMEOUT"" ];then
>                             wait=$SHUTDOWN_ACPI_TIMEOUT
>                         else
>                             wait=30
>                         fi
>                         begin_msg ""Waiting for $wait seconds for VM shutdown""
>                         c=0
>                         while [ -n ""`$VBOXMANAGE --nologo list runningvms`"" ] && [ $c -le $wait ]; do
>                             echo -n '.'
>                             sleep 1
>                             c=$(($c+1))
>                         done
>                         VMS=`$VBOXMANAGE --nologo list runningvms | sed -e 's/^"".*"".*{\(.*\)}/\1/' 2>/dev/null`
>                         if [ -n ""$VMS"" ];then
>                             fail_msg
>                             if [ -z ""$SHUTDOWN_ACPI_ACTION_FAILURE"" ] || [ ""$SHUTDOWN_ACPI_ACTION_FAILURE"" = ""poweroff"" ] ;then
>                                 poweroff_vms $VMS
>                             elif [ ""$SHUTDOWN_ACPI_ACTION_FAILURE"" = ""savestate"" ]; then
>                                 savestate $VMS
>                             fi
>                         else
>                             succ_msg
>                         fi
>                     elif [ ""$SHUTDOWN"" = ""savestate"" ]; then
>                         savestate_vms $VMS
>                     fi
284a326,338
>         done
>         begin_msg 'waiting for XPCOMIPCD to stop '
>         timeout=20
>         c=0
>         while pgrep VBoxXPCOMIPCD>/dev/null && [ $c -le $timeout ] ; do
>             echo -n '.'
>             sleep 1
>             c=$(($c+1))
>         done
>         if pgrep VBoxXPCOMIPCD>/dev/null;then
>             fail_msg
>         else
>             succ_msg
286,291d339
<     done
<     # wait for some seconds when doing ACPI shutdown
<     if [ ""$wait"" -ne 0 ]; then
<         begin_msg ""Waiting for $wait seconds for VM shutdown""
<         sleep $wait
<         succ_msg
378,387c426,437
<         for i in $SHUTDOWN_USERS; do
<             # don't create the ipcd directory with wrong permissions!
<             if [ -d /tmp/.vbox-$i-ipc ]; then
<                 export VBOX_IPC_SOCKETID=""$i""
<                 VMS=`$VBOXMANAGE --nologo list runningvms | sed -e 's/^"".*"".*{\(.*\)}/\1/' 2>/dev/null`
<                 if [ -n ""$VMS"" ]; then
<                     echo ""The following VMs are currently running:""
<                     for v in $VMS; do
<                        echo ""  $v""
<                     done
---
>         if pgrep VBoxXPCOMIPCD>/dev/null; then
>             for i in $SHUTDOWN_USERS; do
>                 # don't create the ipcd directory with wrong permissions!
>                 if [ -d /tmp/.vbox-$i-ipc ]; then
>                     export VBOX_IPC_SOCKETID=""$i""
>                     VMS=`$VBOXMANAGE --nologo list runningvms | sed -e 's/^"".*"".*{\(.*\)}/\1/' 2>/dev/null`
>                     if [ -n ""$VMS"" ]; then
>                         echo ""The following VMs are currently running:""
>                         for v in $VMS; do
>                             echo ""  $v""
>                         done
>                     fi
389,390c439,440
<             fi
<         done
---
>             done
>         fi
}}}

See also https://forums.virtualbox.org/viewtopic.php?f=9&t=67546 for a better formatted diff."	old_man
20851	VBoxDispD3D.dll Crash Trying to run Flutter programs	Windows	VirtualBox 6.1.26	2022-02-25T12:29:36Z	2022-11-28T14:19:42Z	2022-11-28T14:19:42Z	"I'm trying to build a Flutter app that can run on both Windows and Linux. I'm trying to use my Windows VM to compile the Windows version, but it crashes as it tries to launch even the default program.

I initially thought it was a Flutter problem and opened a ticket here:
https://github.com/flutter/flutter/issues/99101

To reproduce, you need to install Flutter:
https://docs.flutter.dev/get-started/install/windows

I simply created a template program using
flutter create testwin
cd testwin
flutter run

This is the error message I get when I try to debug with Visual Studio:
Unhandled exception at 0x00007FFC63716A3D (VBoxDispD3D.dll) in testwin.exe: 0xC0000094: Integer division by zero.


"	Digitaleagle
20032	vboxautostart-service (auto-start) ignores guest settings and blocks guest VMs audio output.	Windows	VirtualBox 6.1.16	2020-11-11T18:07:00Z	2020-11-11T18:07:00Z	2020-11-11T18:07:00Z	"Spent quite awhile tracking the culprit for this!

Running 6.1.16 (appears in recent older versions as well.)

Using a Linux Mint 20 Host, Windows 7 guest although tested with a Linux Mint 20 guest and it has issue as well. 

Started 2 different VMs using the following command

VBoxManage modifyvm xxxxx --autostart-enabled on --autostop-type acpishutdown --autostart-delay xx

Rebooted Host - everything launches correctly HOWEVER Windows Guest has NO AUDIO even though VM setting has Audio enabled. (With correct selections)

Issuing the following command: 

systemctl disable vboxautostart-service

Thereby disabling Autostart service

And rebooting and starting the VMs via script with the command:

vboxmange startvm xxxxx

Correctly allows guest audio.

There are a couple of annoying assumtions with Autostart as well. It FORCES headless (and audioless) operation of the client. Why? The Autostart feature should have a --type option as with the vboxmange startvm command (enhancement request)

Thank you for an otherwise great product and your attention to these issues.


"	Vm User
18086	vboxa uthentication segfaults SQW01	other	VirtualBox 5.2.20	2018-10-27T04:54:52Z	2018-11-10T11:18:47Z	2018-11-10T11:18:47Z	"When using the VirtualBox web service to login, the authentication backend segfaults after a successful login. In order to be able to login again, I have to restart the web service. This has been happening for several releases of VirtualBox now.

I see the following in dmesg

[147969.086688] SQW01[17397]: segfault at 7f9e6da76700 ip 00007f9e6da76700 sp 00007f9e6e3366f8 error 14 in libcap-ng.so.0.0.0[7f9e6d8ee000+200000]
[147969.086705] Code: Bad RIP value.
[147969.213300] SQW01[17400]: segfault at 7f9e6da76700 ip 00007f9e6da76700 sp 00007f9e6e3366b8 error 14 in libcap-ng.so.0.0.0[7f9e6d8ee000+200000]
[147969.213310] Code: Bad RIP value.
[148328.226581] SQW01[17517]: segfault at 7f4f596ec700 ip 00007f4f596ec700 sp 00007f4f59fac6f8 error 14 in libcap-ng.so.0.0.0[7f4f59564000+200000]
[148328.226597] Code: Bad RIP value.
[148328.349869] SQW01[17520]: segfault at 7f4f596ec700 ip 00007f4f596ec700 sp 00007f4f59fac6b8 error 14 in libcap-ng.so.0.0.0[7f4f59564000+200000]
[148328.349879] Code: Bad RIP value.


I'm currently running VirtualBox-5.2-5.2.20_125813_fedora26-1.x86_64 on Fedora 28. 
"	oddsocks
20097	VBOX_E_OBJECT_NOT_FOUND (0x80BB0001) error	Windows	VirtualBox 6.1.16	2020-12-19T05:39:16Z	2020-12-19T06:18:13Z	2020-12-19T06:18:13Z	"The VM-B works properly in Windows 10,
The VM-B is a link-clone VM of another VM-A.
I moved my working space '''from Windows to Linux''' in recently.
[[Image(https://i.loli.net/2020/12/19/UrqvuKlEnOZQbRT.png)]]

I installed newest VirtualBox on my Linux Desktop.
And the '''VM-A is working properly,''' (import from *.vbox file)
But the VM-B give an error message VBOX_E_OBJECT_NOT_FOUND.
[[Image(https://i.loli.net/2020/12/19/vIt5o8ZPUHVFubW.png)]]

And I tried register the seprated disk image for VM-B,
then VM-B works fine!
But the error VBOX_E_OBJECT_NOT_FOUND showns again when I restart VirtualBox.
I need register the seprated disk again to let it works.
[[Image(https://i.loli.net/2020/12/19/ijwGykchT7L4npN.png)]]


Linux OS: UOS V20 [Deepin V20 Commerical Version]
VirtalBox: 6.1.16 r140961 (Qt5.11.3)


i tried:
* remove old vbox file for VM-B and recreate it.
* import vbox file for VM-B again.
but no use.

Regards,
Pekaikon Norckon"	dfc643
19696	VBOX_E_IPRT_ERROR 0x80BB0005 when cloning a vm that is in savestate	Linux	VirtualBox 6.1.10	2020-07-02T18:24:28Z	2020-07-02T18:24:28Z	2020-07-02T18:24:28Z	"Cloning a VM that is in ""savestate"" can issue a VBOX_E_IPRT_ERROR 0x80BB0005 error.
{{{
[vbox@vm001 vms]$ vboxmanage --version
6.1.10r138449
}}}
Change machine to ""savestate""
{{{
[vbox@vm001 vms]$ vboxmanage controlvm t1 savestate
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
}}}
Try to clone the machine (note this is all on local disk. No NFS/SMB mounts)
{{{
[vbox@vm001 vms]$ vboxmanage clonevm t1 --mode all --basefolder /mnt/lv001-r0/backup/vms --name t1-20200702-112825-vbbu
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...
Progress state: VBOX_E_IPRT_ERROR
VBoxManage: error: Clone VM failed
VBoxManage: error: Code VBOX_E_IPRT_ERROR (0x80BB0005) - Runtime subsystem error (extended info not available)
VBoxManage: error: Context: ""RTEXITCODE handleCloneVM(HandlerArg*)"" at line 610 of file VBoxManageMisc.cpp
}}}
As you can see, the clone fails with ""VBOX_E_IPRT_ERROR (0x80BB0005)"".

Now we do the same thing, but poweroff the vm before doing the clone.
Let's resume the VM from the savestate above.
{{{
[vbox@vm001 vms]$ vboxmanage startvm t1 --type headless
Waiting for VM ""t1"" to power on...
VM ""t1"" has been successfully started.
}}}
Poweroff the VM
{{{
[1803 vbox@scvm001 vms]$ vboxmanage controlvm t1 poweroff       
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
}}}
and rerun the clone...
{{{
[vbox@vm001 vms]$ vboxmanage clonevm t1 --mode all --basefolder /mnt/lv001-r0/backup/vms --name t1-20200702-112825-vbbu
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Machine has been successfully cloned as ""t1-20200702-112825-vbbu""
}}}
The clone runs sucessfully to completion.

Virtualbox user forum thread for reference: https://forums.virtualbox.org/viewtopic.php?f=7&t=98881"	guideloom
17561	VBOX_E_FILE_ERROR	Linux	VirtualBox 5.1.28	2018-02-22T19:40:22Z	2018-02-23T18:14:15Z	2018-02-23T18:14:15Z	"VirtualBox-5.1.x86_64 on Red Hat Enterprise Linux Server release 6.6
2.6.32-504.el6.x86_64
/VirtualBox-5.1-5.1.28_117968_el6-1.x86_64

We have a process we have been using for years where we take a Virtual Machine image and convert it to an OVA.  We recently took a new Virtual Machine image for the input because of the Spectre and Meltdown SV's so we need an updated VM image.   The size of the image changed slightly, that is about all I can tell.

I cannot find any documentation or reference that explains what this message means.

/opt/VirtualBox/VBoxManage export VBOX_8_56_07_SHELL --output /ds2/templates/vboxshell.23492/VBOX_8_56_07_SHELL.ova --vsys 0 --product 'XXX VBox Shell Appliance' --vendor XXX --version 8.56.07
0%...10%...20%...30%...40%...50%...60%...70%...
Progress state: VBOX_E_FILE_ERROR
VBoxManage: error: Appliance write failed
VBoxManage: error: File not accessible or erroneous file contents
VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component Appliance, interface IAppliance
VBoxManage: error: Context: ""int handleExportAppliance(HandlerArg*)"" at line 1121 of file VBoxManageAppliance.cpp
"	lno184
18183	vbox-dkms  modules (vboxnetadp vboxdrv) compilation error  against kernel 4.20.0-rc6 -> fixed after (not in) 5.2.22	other	VirtualBox 5.2.22	2018-12-15T07:19:27Z	2018-12-19T16:49:57Z	2018-12-19T16:49:57Z	"I am on ArchLinux and decided to to use the [https://aur.archlinux.org/packages/linux-mainline mainline kernel] ie ""vanilla"" with [https://aur.archlinux.org/packages/linux-mainline-headers/ mainline-headers]. That is currently [https://git.kernel.org/torvalds/t/linux-4.20-rc6.tar.gz 4.20.0-rc6-mainline] and noticed these compilation failures:

{{{
$ cat /var/lib/dkms/vboxhost/5.2.22_OSE/build/make.log
DKMS make.log for vboxhost-5.2.22_OSE for kernel 4.20.0-rc6-mainline (x86_64)
Sat Dec 15 17:29:02 ACDT 2018
make: Entering directory '/usr/lib/modules/4.20.0-rc6-mainline/build'
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxnetflt/linux/VBoxNetFlt-linux.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxnetadp/linux/VBoxNetAdp-linux.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxnetflt/VBoxNetFlt.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxnetadp/VBoxNetAdp.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxnetflt/SUPR0IdcClient.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/linux/SUPDrv-linux.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxpci/linux/VBoxPci-linux.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxpci/VBoxPci.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxnetflt/SUPR0IdcClientComponent.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxnetflt/linux/SUPR0IdcClient-linux.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxpci/SUPR0IdcClient.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxpci/SUPR0IdcClientComponent.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxpci/linux/SUPR0IdcClient-linux.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/SUPDrv.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/SUPDrvGip.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/SUPDrvSem.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/SUPDrvTracer.o
/var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxnetadp/linux/VBoxNetAdp-linux.c:132:6: error: ‘const struct ethtool_ops’ has no member named ‘get_settings’; did you mean ‘get_strings’?
     .get_settings       = vboxNetAdpEthGetSettings,
      ^~~~~~~~~~~~
      get_strings
/var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxnetadp/linux/VBoxNetAdp-linux.c:132:27: error: initialization of ‘int (*)(struct net_device *)’ from incompatible pointer type ‘int (*)(struct net_device *, struct ethtool_cmd *)’ [-Werror=incompatible-pointer-types]
     .get_settings       = vboxNetAdpEthGetSettings,
                           ^~~~~~~~~~~~~~~~~~~~~~~~
/var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxnetadp/linux/VBoxNetAdp-linux.c:132:27: note: (near initialization for ‘gEthToolOpsVBoxNetAdp.get_regs_len’)
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:291: /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxnetadp/linux/VBoxNetAdp-linux.o] Error 1
make[1]: *** [scripts/Makefile.build:516: /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxnetadp] Error 2
make[1]: *** Waiting for unfinished jobs....
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/SUPLibAll.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/alloc-r0drv.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/initterm-r0drv.o
  LD [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxpci/vboxpci.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/memobj-r0drv.o
  LD [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxnetflt/vboxnetflt.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/mpnotification-r0drv.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/powernotification-r0drv.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/linux/assert-r0drv-linux.o
/var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/.tmp_SUPDrvTracer.o: warning: objtool: .text+0x7: indirect jump found in RETPOLINE build
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/linux/alloc-r0drv-linux.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/linux/initterm-r0drv-linux.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/linux/memuserkernel-r0drv-linux.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/linux/mp-r0drv-linux.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/linux/mpnotification-r0drv-linux.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/linux/process-r0drv-linux.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/linux/rtStrFormatKernelAddress-r0drv-linux.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/linux/semevent-r0drv-linux.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/linux/semeventmulti-r0drv-linux.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/linux/semfastmutex-r0drv-linux.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/linux/semmutex-r0drv-linux.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/linux/spinlock-r0drv-linux.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/linux/thread-r0drv-linux.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/linux/thread2-r0drv-linux.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/linux/threadctxhooks-r0drv-linux.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/linux/time-r0drv-linux.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/linux/timer-r0drv-linux.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/generic/semspinmutex-r0drv-generic.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/common/alloc/alloc.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/common/checksum/crc32.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/common/checksum/ipv4.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/common/checksum/ipv6.o
/var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/linux/time-r0drv-linux.c: In function ‘VBoxHost_RTTimeNow’:
/var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/linux/time-r0drv-linux.c:175:5: error: implicit declaration of function ‘ktime_get_real_ts’; did you mean ‘ktime_get_real_ns’? [-Werror=implicit-function-declaration]
     ktime_get_real_ts(&Ts);
     ^~~~~~~~~~~~~~~~~
     ktime_get_real_ns
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:291: /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/linux/time-r0drv-linux.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [scripts/Makefile.build:516: /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv] Error 2
make: *** [Makefile:1565: _module_/var/lib/dkms/vboxhost/5.2.22_OSE/build] Error 2
make: Leaving directory '/usr/lib/modules/4.20.0-rc6-mainline/build'
}}}"	Tyler A
15874	VBOX session crashes - aborted - on NAT: DHCP offered IP address. Fixed in the past, reintroduced.	Windows	VirtualBox 5.1.4	2016-09-01T15:02:53Z	2016-10-27T14:05:46Z	2016-10-27T14:05:46Z	"Hallo

Running Windows 7 guest, hosted in VBox 5.1.4 under Fedora 24. Same problem on RHEL6 and RHEL7.

Session of VM randomly crashes without notice, getting status '''ABORTED'''. No obvious errors in neither Windows not Linux logs. In VBox log, after every crash there is this single message as last one:

'''NAT: DHCP offered IP address 10.0.2.15'''

I've seen same problem beeing solved in much older version of VBox: https://www.virtualbox.org/ticket/13874

I guess the error got reintroduced along the VBox evolution.

Could you please check and fix according to previous solution?

Thanks a lot"	Flamestring
16403	VBox on linux host randomly power off.	Windows	VirtualBox 5.1.10	2017-01-19T07:44:24Z	2017-01-23T15:55:09Z	2017-01-23T15:55:09Z	"I have a problem like https://www.virtualbox.org/ticket/10831/.
I start two Windows2012R2 virtual machines headless on console CentOS7.1.
Sometimes vms randomly crash (not both simultaneously). 

"	Nika
18653	"VBox fails to download ""VirtualBox Guest Additions"" disk image since 6.0.0"	Windows	VirtualBox 6.0.8	2019-05-17T08:01:57Z	2020-02-20T09:12:01Z	2020-02-20T09:12:01Z	"Hi
Since around upgrading to VirtualBox 6.0.0 (valid up to 6.0.8), VBox fails to download ""VirtualBox Guest Additions"" disk image since 6.0.0.
When clicking over ""Insert Guest Additions CD Image..."" in the ""Device"" menu, it always ends with the following:
""The network operation failed with the following error: 
During network request: Unknown reason.""

(BTW when it was working, this meant clicking too many times on ""OK"" just to get through, once should be enough)"	vtt
17373	vbox driver does not compile with kernel 4.14.5	Linux	VirtualBox 5.1.30	2017-12-15T17:36:32Z	2017-12-15T17:36:32Z	2017-12-15T17:36:32Z	"Hello,

I try a 4.14.5 kernel and the Vbox driver does not compile.
The trace is included.

Regards

JP P"	jppo
17721	Vbox crashes under heavy disk IO	other	VirtualBox 5.2.10	2018-04-30T20:38:04Z	2022-12-20T22:04:05Z	2022-12-20T22:04:05Z	"Host: Fedora 27 3 HDDs in raid 5 (soft)
Guest: eCS 2 

During the weekly scrub of the host raid, Vbox crashes every time,
with this error in the log:

57:08:52.378736 PIIX3 IDE: guest issued command 0xca while controller busy
57:26:55.455873 PIIX3 IDE: guest issued command 0xca while controller busy
57:26:57.205541 PIIX3 ATA: execution time for ATA command 0xca was 9 seconds
57:26:57.205570 
57:26:57.205570 !!Assertion Failed!!
57:26:57.205571 Expression: ReqType == ATA_AIO_RESET_ASSERTED || ReqType == ATA_AIO_RESET_CLEARED || ReqType == ATA_AIO_ABORT || pCtl->uAsyncIOState == ReqType
57:26:57.205571 Location  : /home/vbox/vbox-5.2.10/src/VBox/Devices/Storage/DevATA.cpp(5429) int ataR3AsyncIOThread(RTTHREAD, void*)
57:26:57.205587 I/O state inconsistent: state=0 request=1
57:26:57.205602 PIIX3 IDE: guest issued command 0xca while controller busy
 
"	Yoda
16233	Vbox bridge loses outer QinQ tag	Linux	VirtualBox 5.1.10	2016-11-25T20:03:58Z	2017-04-24T16:13:18Z	2017-04-24T16:13:18Z	"Virtualox bridge loses outer QinQ tag if bridged with Linux TAP interface

Steps to reproduce:

 1. Install OS Linux on PC.
 In my case: Ubuntu 14.04.5
 kernel 4.2.0-42-generic X86_64

 2. Install !VirtualBox (in my case ver. 5.1.10 !r112026 (Qt5.6.1)) from [http://download.virtualbox.org/virtualbox/5.1.10/virtualbox-5.1_5.1.10-112026~Ubuntu~trusty_amd64.deb here]

 3. Download and install guest Linux OS.
 In my case Ubuntu 16.04.01 from [http://releases.ubuntu.com/16.04/ubuntu-16.04.1-server-i386.iso here]

 4. On host system create tap interface:
{{{
ip tuntap add dev tap10 mode tap
ip link set dev tap10 up
}}}
 5. In guest VM netwrok settings set network adapter to ""bridge"" mode to interface tap10
{{{
vboxmanage modifyvm TESTVM --nic2 bridged
vboxmanage modifyvm TESTVM --bridgeadapter2 tap10
}}}
	
 All other network settings may be set to default. I tried to change the ""adapter type"" and ""promiscuous mode"". Their change does not change the result. 
	
 6. Create QINQ subinterface on host interface tap10 with inner vlan 2000 and outer vlan 100 and set ip address (type of protocol 802.1q or 802.1ad not important. This change does not change the result):
{{{
ip link add link tap10 tap10.100 type vlan proto 802.1q id 100
ip link set up tap10.100
ip link add link tap10.100 tap10.100.2000 type vlan proto 802.1q id 2000
ip link set up tap10.100.2000
ip addr add 10.11.12.1/24 dev tap10.100.2000
}}}
	
 7. Start up guest VM and determine which interface bridged with tap10
	In my case this is a '''enp0s8'''
 8. Create QINQ subinterface on VM interface which bridged with tap10 with inner vlan 2000 and outer vlan 100 and set ip address (type of protocol 802.1q or 802.1ad not important. This change does not change the result):
{{{
ip link set up enp0s8
ip link add link enp0s8 enp0s8.100 type vlan proto 802.1q id 100
ip link set up enp0s8.100
ip link add link enp0s8.100 enp0s8.100.2000 type vlan proto 802.1q id 2000
ip link set up enp0s8.100.2000
ip addr add 10.11.12.2/24 dev enp0s8.100.2000
}}}
 9. start watch for traffic on host PC on tap10 interface:
{{{
tcpdump -i tap10 -vvv -e
}}}
 for creating pcap file
{{{
tcpdump -i tap10 -vvv -e -w qinqPC.pcap
}}}
	
 10. start watch for traffic in guest VM on ""physical"" interface:
{{{
tcpdump -i enp0s8 -vvv -e
}}}
 for creating pcap file
{{{
tcpdump -i enp0s8 -vvv -e -w qinqVM.pcap
}}}
	
 11. Try to ping 10.11.12.2 from 10.11.12.1 (Host PC => Guest VM)
{{{
ping 10.11.12.2
}}}
	
 12. You should get the following results:[[BR]]
 on physical PC (tap10):
{{{
21:22:06.345997 f6:4e:f0:31:76:45 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 50: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.2 tell 10.11.12.1, length 28
21:22:07.346093 f6:4e:f0:31:76:45 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 50: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.2 tell 10.11.12.1, length 28
21:22:08.346032 f6:4e:f0:31:76:45 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 50: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.2 tell 10.11.12.1, length 28
}}}
 on VM (enp0s8):
{{{
21:30:21.737754 f6:4e:f0:31:76:45 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 64: vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.2 tell 10.11.12.1, length 46
21:30:22.738035 f6:4e:f0:31:76:45 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 64: vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.2 tell 10.11.12.1, length 46
21:30:23.737981 f6:4e:f0:31:76:45 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 64: vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.2 tell 10.11.12.1, length 46
}}}

As seen, on VM side is missing outer vlan (vlan 100)

If a try to ping from VM to PC the outer vlan in right place only in ARP request. In ARP reply (PC -> VM) the outer vlan is missing.
on physical PC:
{{{
21:35:12.342498 08:00:27:5d:26:01 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 64: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.1 tell 10.11.12.2, length 42
21:35:12.342501 08:00:27:5d:26:01 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 64: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.1 tell 10.11.12.2, length 42
21:35:12.342521 f6:4e:f0:31:76:45 (oui Unknown) > 08:00:27:5d:26:01 (oui Unknown), ethertype 802.1Q (0x8100), length 50: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Reply 10.11.12.1 is-at f6:4e:f0:31:76:45 (oui Unknown), length 28
21:35:13.343489 08:00:27:5d:26:01 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 64: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.1 tell 10.11.12.2, length 42
21:35:13.343495 08:00:27:5d:26:01 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 64: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.1 tell 10.11.12.2, length 42
21:35:13.343516 f6:4e:f0:31:76:45 (oui Unknown) > 08:00:27:5d:26:01 (oui Unknown), ethertype 802.1Q (0x8100), length 50: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Reply 10.11.12.1 is-at f6:4e:f0:31:76:45 (oui Unknown), length 28
}}}

on VM:
{{{
21:35:10.614413 08:00:27:5d:26:01 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 50: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.1 tell 10.11.12.2, length 28
21:35:10.614556 f6:4e:f0:31:76:45 (oui Unknown) > 08:00:27:5d:26:01 (oui Unknown), ethertype 802.1Q (0x8100), length 64: vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Reply 10.11.12.1 is-at f6:4e:f0:31:76:45 (oui Unknown), length 46
21:35:11.615368 08:00:27:5d:26:01 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 50: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.1 tell 10.11.12.2, length 28
21:35:11.615549 f6:4e:f0:31:76:45 (oui Unknown) > 08:00:27:5d:26:01 (oui Unknown), ethertype 802.1Q (0x8100), length 64: vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Reply 10.11.12.1 is-at f6:4e:f0:31:76:45 (oui Unknown), length 46
21:35:12.615063 08:00:27:5d:26:01 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 50: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.1 tell 10.11.12.2, length 28
}}}


It does not look as a TAP bug. If a try to bridge two tap interface via linux bridge, and create QINQ subinterfaces for each of them, this problem does not appear.

PCAP-s from VM and PC (qinqVM.pcap and qinqPC.pcap) in attachement.

Thanks in advance!"	Arc
16527	vbox autostart-enable on deletes the autostart file /etc/vbox/[user].start	Linux	VirtualBox 5.1.14	2017-03-02T17:54:12Z	2017-03-02T18:14:39Z	2017-03-02T18:14:39Z	"it looks like the problems with autostart at ubuntu are somehow logical issues
I wasn't able to bring the vms in autostart mode. all files and folders are fine. But the ...-enabled on reports nothing and the enabled-off showed VERR_FILE_NOT_FOUND

a sudo touch [username].start at /etc/vbox/ followed by sudo chown [user] [user].start changed the the behavior that ..-enabled off doesnt fail.

but after a enabled on the .start script is lost. So something must be wrong there.

Ubuntu 16.04.04 VBOX 5.1.14"	bba_fan
17528	vbox always aborts KDE sesssion shutdown when machine is running	Windows	VirtualBox 5.2.6	2018-02-06T03:05:37Z	2022-02-07T21:32:30Z	2022-02-07T21:32:30Z	"This is the same as ticket 12195 which was marked closed without resolution. That ticket suggest reopening with a more recent version of VirtualBox if still relevant.

I'm using VirtualBox 5.2.6r120293 on a Linux Slackware64 14.2 host and Windows 7 guest. When I log out (KDE) I run a script shutting down the VM. Despite this, I get a message, ""KDE Workspace / Logout canceled by '/opt/VirtualBox/VirtualBox' and I have to re-logout to actually log out.

If I shutdown the VM manually, then logout, it works OK."	mfoley
13653	VBox > 4.3.14 has flicker / slow redrawing of UI elements (regression)	Windows	VirtualBox 4.3.20	2014-11-28T14:17:51Z	2020-06-27T22:29:48Z	2020-06-27T22:29:48Z	"Host: Fedora 20 x86_64
Host video card: NVIDIA 9500 (driver 340.58)
Guest: Windows 7 x86_64

Any VirtualBox newer than 4.3.14 causes UI elements to flicker or slow / not redraw when the mouse hovers over them when 3D support is enabled and the 3D driver is installed.

VBox guest additions version does not matter. I can have 4.3.20 guest additions installed on 4.3.14 and no flickering occurs, but upgrading the host binaries to 4.3.16, 4.3.18, or 4.3.20 will induce UI flickering. It causes 3D / Aero to be unusable.

Also see: https://forums.virtualbox.org/viewtopic.php?f=7&t=64424&p=305456"	Michael
20296	vbox 6.1.18: virt-install cause vm crash (guru meditation)	Linux	VirtualBox 6.1.18	2021-04-09T10:01:26Z	2021-04-09T12:23:55Z	2021-04-09T12:23:55Z	"I met a critical vbox error that I would like to report.

I reproduced this problem on 2 different vbox hypervisors.

== Facts ==
* hypervisor is running ubuntu 20.04 LTS (up to date) + vbox 6.1.18
* nested vt-x is enabled
* guest is running ubuntu 20.04 LTS (up to date, installed manually from ubuntu-20.04.2.0-desktop-amd64.iso)
* guest is running qemu/kvm (installed from ubuntu distro)

== Reproducer ==
* apt install qemu-kvm virtinst virt-manager libguestfs-tools bridge-utils
* cd /tmp && wget https://dl-cdn.alpinelinux.org/alpine/v3.13/releases/x86_64/alpine-standard-3.13.4-x86_64.iso
* virt-install --connect qemu:///system --virt-type kvm --name alpine --ram 512  --vcpus 1  --disk path=/dev/vmvg/vm --cdrom=/tmp/alpine-standard-3.13.4-x86_64.iso --network none --graphics none --arch x86_64 --os-type=generic --cpu host --noautoconsole
"	Arnaud Veron
18624	Vbox 6.0.6 build failure on Linux with gcc 9.1.0	other	VirtualBox 6.0.6	2019-05-07T01:21:14Z	2019-07-23T17:00:06Z	2019-07-23T17:00:06Z	"Building vbox 6.0.6 on Linux with gcc 9.1.0 results in

{{{
kBuild: Compiling VBoxSVC - /home/bero/abf/virtualbox/BUILD/VirtualBox-6.0.6/src/VBox/Main/src-server/PerformanceImpl.cpp
/usr/include/c++/9.1.0/limits: In static member function ‘static constexpr double std::numeric_limits<double>::max()’:
/usr/include/c++/9.1.0/limits:1743:44: error: unable to find numeric literal operator ‘operator""""-0.0L’
 1743 |       max() _GLIBCXX_USE_NOEXCEPT { return __DBL_MAX__; }
      |                                            ^~~~~~~~~~~
/usr/include/c++/9.1.0/limits:1743:44: note: use ‘-fext-numeric-literals’ to enable more built-in suffixes
In file included from /usr/include/c++/9.1.0/bits/uniform_int_dist.h:35,
                 from /usr/include/c++/9.1.0/bits/stl_algo.h:66,
                 from /usr/include/c++/9.1.0/algorithm:62,
                 from /home/bero/abf/virtualbox/BUILD/VirtualBox-6.0.6/src/VBox/Main/src-server/PerformanceImpl.cpp:44:
/usr/include/c++/9.1.0/limits:1743:57: error: body of ‘constexpr’ function ‘static constexpr double std::numeric_limits<double>::max()’ not a return-statement
 1743 |       max() _GLIBCXX_USE_NOEXCEPT { return __DBL_MAX__; }
      |                                                         ^
/usr/include/c++/9.1.0/limits: In static member function ‘static constexpr double std::numeric_limits<double>::lowest()’:
/usr/include/c++/9.1.0/limits:1747:35: error: unable to find numeric literal operator ‘operator""""-0.0L’
 1747 |       lowest() noexcept { return -__DBL_MAX__; }
      |                                   ^~~~~~~~~~~
/usr/include/c++/9.1.0/limits:1747:35: note: use ‘-fext-numeric-literals’ to enable more built-in suffixes
/usr/include/c++/9.1.0/limits:1747:48: error: body of ‘constexpr’ function ‘static constexpr double std::numeric_limits<double>::lowest()’ not a return-statement
 1747 |       lowest() noexcept { return -__DBL_MAX__; }
      |                                                ^
kmk: *** [/home/bero/abf/virtualbox/BUILD/VirtualBox-6.0.6/kBuild/footer-pass2-compiling-targets.kmk:277: /home/bero/abf/virtualbox/BUILD/VirtualBox-6.0.6/out/linux.amd64/release/obj/VBoxSVC/src-server/PerformanceImpl.o] Error 1
}}}

While the error message looks like a problem in <limits> itself, the limits header works perfectly elsewhere (may be related to PCH usage in vbox?)"	berolinux
17209	VB Unusably slow	Windows	VirtualBox 5.1.28	2017-10-25T12:52:51Z	2017-10-25T13:51:20Z	2017-10-25T13:51:20Z	"I had been using VB 3.x and 4.x for years, years ago. It has always been slow but it used to be almost usable.

Now I have upgraded to 5.1.28 and it's unusably slow. Even the application's menus on the host are unresponsive (to the point you even lose clicks on the menus, e.g. the Machine or Devices menu.

I did view->Take screenshot and it took more than a minute for the popup to appear. That's just an example.

My host is ubuntu (on an i7 processor with 4GB RAM) and the guest is Windows 7. Both 64bit.

I am using the very same computer and the same host and guest OS (and the same VM) that I was using years ago with VB 3.x and 4.x and it is WAY slower.

It's pathetic."	teo8976
21347	VB systemd unit persistently rebuilding kernel modules with secureboot	all	VirtualBox-7.0.4	2022-12-19T09:50:31Z	2023-01-19T01:49:28Z	2023-01-19T01:49:28Z	"In Debian, the kernel source script `extract-module-sig.pl` is not available in the kernel modules build/scripts directory. The VirtualBox systemd unit script relies on this script to determine whether the VB kernel modules are appropriately signed if it detects that secureboot is enabled. Since it can't find the script, it believes there is something wrong with the modules, and rebuilds them every time the service starts (at least on every boot), regardless of whether they were correctly signed. This means that every time I reboot my machine, VirtualBox refuses to operate until I go back and sign the newly-built kernel modules.

System: Debian Bullseye
VB installed with the deb distributed by the download.virtualbox.org repository."	lxop
20017	VB installation failing in linux kernel drivers installation	other	VirtualBox 6.1.16	2020-11-04T18:13:31Z	2020-11-06T08:08:19Z	2020-11-06T08:08:19Z	"Host is a Debian 10.
Kernel is 5.9.3.

Compilation of modules located in /usr/src/vboxhost-6.1.16 fail during the install stage.
It is the vboxpci driver.

I checked its content and it seems there has been some cleaning there (all Makefile*) files, etc.

I have managed to bypass that failure to install and all other drivers get installed
(I just renamed the vboxpci to vboxpci.del in order to be bypassed).

I can run VirtualBox but then (my guess is that) VT-d, for the guest machines, cannot be enabled.


Regards,
Josep"	jepjepus
20607	VB host kernel drivers fail to build on CentOS 8 Stream kernel 4.18.0-338	all	VirtualBox 6.1.26	2021-10-15T14:29:51Z	2021-10-15T19:24:24Z	2021-10-15T19:24:24Z	"Building the host kernel drivers succeeds with with CentOS 8 Stream kernel 4.18.0-315.el8.x86_64 and earlier, but fails with kernel 4.18.0-338.el8.x86_64.  The issue appears to be related to issues #19644 (which relates to a newer base kernel version) and #20488 (which relates to the Guest Additions, not the host drivers), both associated with the symbol `map_vm_area` no longer being exported by the kernel.

This was initially observed with VirtualBox 6.0, but it still occurs with VirtualBox 6.1.26, as installed via the official VirtualBox-6.1-6.1.26_145957_el8-1.x86_64 RPM.

The relevant excerpts from /var/log/vbox-setup.log appear to be:
{{{
   ./tools/objtool/objtool orc generate  --module --no-fp  --retpoline ""/tmp/vbox.0/r0drv/.tmp_alloc-r0drv.o"";
   ./tools/objtool/objtool orc generate  --module --no-fp  --retpoline ""/tmp/vbox.0/r0drv/.tmp_initterm-r0drv.o"";
  gcc -Wp,-MD,/tmp/vbox.0/r0drv/linux/.alloc-r0drv-linux.o.d  -nostdinc -isystem /usr/lib/gcc/x86_64-redhat-linux/8/include -I./arch/x86/include -I./arch
/x86/include/generated   -I./include/drm-backport -I./include -I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi -I./include/
generated/uapi -include ./include/linux/kconfig.h -include ./include/linux/compiler_types.h -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs
 -fno-strict-aliasing -fno-common -fshort-wchar -Werror-implicit-function-declaration -Wno-format-security -std=gnu89 -fno-PIE -DCC_HAVE_ASM_GOTO -mno-ss
e -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup
 -mtune=generic -mno-red-zone -mcmodel=kernel -funit-at-a-time -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FX
SAVEQ=1 -DCONFIG_AS_SSSE3=1 -DCONFIG_AS_CRC32=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -DCONFIG_AS_AVX512=1 -DCONFIG_AS_SHA1_NI=1 -DCONFIG_AS_SHA256_NI=1 -
DCONFIG_TPAUSE=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern -mindirect-branch-register -fno-jump-tables -fno-
delete-null-pointer-checks -Wno-frame-address -Wno-format-truncation -Wno-format-overflow -Wno-int-in-bool-context -O2 --param=allow-store-data-races=0 -
Wframe-larger-than=2048 -fstack-protector-strong -Wno-unused-but-set-variable -Wno-unused-const-variable -g -gdwarf-4 -pg -mrecord-mcount -mfentry -DCC_U
SING_FENTRY -fno-inline-functions-called-once -Wdeclaration-after-statement -Wno-pointer-sign -Wno-stringop-truncation -fno-strict-overflow -fno-merge-al
l-constants -fmerge-constants -fno-stack-check -fconserve-stack -Werror=implicit-int -Werror=strict-prototypes -Werror=date-time -Werror=incompatible-poi
nter-types -Werror=designated-init -fmacro-prefix-map=./= -Wno-packed-not-aligned -include /tmp/vbox.0/include/VBox/SUPDrvMangling.h -fno-omit-frame-poin
ter -fno-pie -Wno-declaration-after-statement -I./include -I/tmp/vbox.0/ -I/tmp/vbox.0/include -I/tmp/vbox.0/r0drv/linux -D__KERNEL__ -DMODULE -DRT_WITHO
UT_PRAGMA_ONCE -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX -DRT_WITH_VBOX -DVBOX_WITH_HARDENING -DSUPDRV_WITH_RELEASE_LOGGER -DVBOX_WITHOUT_EF
LAGS_AC_SET_IN_VBOXDRV -DIPRT_WITHOUT_EFLAGS_AC_PRESERVING -DVBOX_WITH_64_BITS_GUESTS -DCONFIG_VBOXDRV_AS_MISC -DRT_ARCH_AMD64  -DMODULE  -DKBUILD_BASENA
ME='""alloc_r0drv_linux""' -DKBUILD_MODNAME='""vboxdrv""' -c -o /tmp/vbox.0/r0drv/linux/.tmp_alloc-r0drv-linux.o /tmp/vbox.0/r0drv/linux/alloc-r0drv-linux.c
}}}
[...]
{{{
/tmp/vbox.0/r0drv/linux/alloc-r0drv-linux.c: In function ‘rtR0MemAllocExecVmArea’:
/tmp/vbox.0/r0drv/linux/alloc-r0drv-linux.c:204:14: error: implicit declaration of function ‘map_vm_area’; did you mean ‘get_vm_area’? [-Werror=implicit-function-declaration]
         if (!map_vm_area(pVmArea, PAGE_KERNEL_EXEC,
              ^~~~~~~~~~~
              get_vm_area
}}}
[...]
{{{
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:316: /tmp/vbox.0/r0drv/linux/alloc-r0drv-linux.o] Error 1
make[2]: *** Waiting for unfinished jobs....
}}}
[...]
{{{
make[1]: *** [Makefile:1571: _module_/tmp/vbox.0] Error 2
make: *** [/tmp/vbox.0/Makefile-footer.gmk:117: vboxdrv] Error 2
}}}
"	jcbollinger
16870	VB 5.1.22 Aborts and issues running Outlook 2016 on Windows 10 Guest	Windows	VirtualBox 5.1.22	2017-07-03T16:10:36Z	2017-10-10T16:45:53Z	2017-10-10T16:45:53Z	"I get sudden aborts of VB 5.1.22 r115126 running a windows 10 guest on a Linux Mint 18.1 Cinnamon 3.2.7 machine.

First, I must run Outlook 2016 in safe mode ""outlook.exe /safe"" or outlook will immediately go into ""Not Responding"" and never recover.  This is Outlook connected to company Exchange server and Windows 10 guest is joined to domain.

Typically see crash when copying items from host to paste into new email open in guest.

Nothing in Oracle VB logs to indicate why the crash happens, and not seeing anything relevant in Linux logs."	Paul Allen
16466	VB 5.1.14 (linux host / win7 guest) fails concurrent audio/video input from integrated USB device (Logitech C920 webcam); separate devices work OK	Windows	VirtualBox 5.1.14	2017-02-08T16:04:46Z	2020-04-23T20:46:18Z	2020-04-23T20:46:18Z	"I've a desktop with VB 5.1.14 installed
{{{
	VBoxManage --version
		5.1.14r112924
}}}
and running
{{{
	VBoxManage list runningvms
		""Win7_64"" {71...e9}
}}}
on linux/64 host
{{{
	VBoxManage list hostinfo
		Host Information:

		Host time: 2017-02-08T15:13:41.459000000Z
		Processor online count: 4
		Processor count: 4
		Processor online core count: 4
		Processor core count: 4
		Processor supports HW virtualization: yes
		Processor supports PAE: yes
		Processor supports long mode: yes
		Processor supports nested paging: yes
		Processor#0 speed: 3010 MHz
		Processor#0 description: AMD Phenom(tm) II X4 945 Processor
		Processor#1 speed: 3010 MHz
		Processor#1 description: AMD Phenom(tm) II X4 945 Processor
		Processor#2 speed: 3010 MHz
		Processor#2 description: AMD Phenom(tm) II X4 945 Processor
		Processor#3 speed: 3010 MHz
		Processor#3 description: AMD Phenom(tm) II X4 945 Processor
		Memory size: 16030 MByte
		Memory available: 2423 MByte
		Operating system: Linux
		Operating system version: 4.9.8-2.gaf90696-default
}}}
with up-to-date extpack installed
{{{
	VBoxManage list extpacks
		Extension Packs: 1
		Pack no. 0:   Oracle VM VirtualBox Extension Pack
		Version:      5.1.14
		Revision:     112924
		Edition:
		Description:  USB 2.0 and USB 3.0 Host Controller, Host Webcam, VirtualBox RDP, PXE ROM, Disk
		VRDE Module:  VBoxVRDP
		Usable:       true
		Why unusable:
}}}
The host runs PulseAudio.

I have two devices attached and functional in the host, an integrated (audio + video) webcam, and a standalone microphone
{{{
	lsusb | egrep -i ""Logitech|Telex""
		Bus 001 Device 011: ID 046d:082d Logitech, Inc. HD Pro Webcam C920
		Bus 001 Device 010: ID 0562:0002 Telex Communications, Inc. Telex Microphone

	hwinfo --usb
		...
		11: USB 00.1: 0000 Unclassified device
		  [Created at usb.122]
		  Unique ID: xnLL.dxozCEIXKDA
		  Parent ID: k4bc.029GFTetOb3
		  SysFS ID: /devices/pci0000:00/0000:00:05.0/0000:03:00.0/usb1/1-4/1-4:1.1
		  SysFS BusID: 1-4:1.1
		  Hardware Class: unknown
		  Model: ""Logitech HD Pro Webcam C920""
		  Hotplug: USB
		  Vendor: usb 0x046d ""Logitech, Inc.""
		  Device: usb 0x082d ""HD Pro Webcam C920""
		  Revision: ""0.11""
		  Serial ID: ""60F274DF""
		  Driver: ""uvcvideo""
		  Driver Modules: ""uvcvideo""
		  Speed: 480 Mbps
		  Module Alias: ""usb:v046Dp082Dd0011dcEFdsc02dp01ic0Eisc02ip00in01""
		  Config Status: cfg=new, avail=yes, need=no, active=unknown
		  Attached to: #24 (Hub)

		12: USB 00.0: 0401 Multimedia audio controller
		  [Created at usb.122]
		  Unique ID: cLrx.qTkEoUPZciD
		  Parent ID: k4bc.029GFTetOb3
		  SysFS ID: /devices/pci0000:00/0000:00:05.0/0000:03:00.0/usb1/1-2/1-2:1.0
		  SysFS BusID: 1-2:1.0
		  Hardware Class: sound
		  Model: ""Telex Microphone""
		  Hotplug: USB
		  Vendor: usb 0x0562 ""Telex Communications, Inc.""
		  Device: usb 0x0002 ""Telex Microphone""
		  Revision: ""1.00""
		  Serial ID: ""XXXXX""
		  Driver: ""snd-usb-audio""
		  Driver Modules: ""snd_usb_audio""
		  Speed: 12 Mbps
		  Module Alias: ""usb:v0562p0002d0100dc00dsc00dp00ic01isc01ip00in00""
		  Driver Info #0:
		    Driver Status: snd_usb_audio is active
		    Driver Activation Cmd: ""modprobe snd_usb_audio""
		  Config Status: cfg=new, avail=yes, need=no, active=unknown
		  Attached to: #24 (Hub)
		...
}}}
In the host, under PulseAudio routing, the webcam &/or the standalone mic can be used by linux native apps separately &/or concurrently.  No issues.

In VB, Audio settings are set to
{{{
	Audio
		HostDriver: PulseAudio
		Constroller: Intel HD Audio
}}}
The VM sees the mic & webcam on the host as
{{{
	VBoxManage list usbhost
		...
		UUID:               24651a23-221b-45e4-bddf-00bbfc1ce03a
		VendorId:           0x0562 (0562)
		ProductId:          0x0002 (0002)
		Revision:           1.0 (0100)
		Port:               1
		USB version/speed:  1/Full
		Manufacturer:       Telex Communications, Inc.
		Product:            Telex USB microphone
		SerialNumber:       XXXXX
		Address:            sysfs:/sys/devices/pci0000:00/0000:00:05.0/0000:03:00.0/usb1/1-2//device:/dev/vboxusb/001/010
		Current State:      Captured
		...
		UUID:               272cd013-38e7-4515-af01-9c8f2aebbbd0
		VendorId:           0x046d (046D)
		ProductId:          0x082d (082D)
		Revision:           0.17 (0017)
		Port:               3
		USB version/speed:  2/High
		Manufacturer:       Logitech, Inc.
		Product:            HD Pro Webcam C920
		SerialNumber:       60F274DF
		Address:            sysfs:/sys/devices/pci0000:00/0000:00:05.0/0000:03:00.0/usb1/1-4//device:/dev/vboxusb/001/011
		Current State:      Busy
}}}
The VM runs Win7/64 with SP1 + latest ConvenienceRollup & all updates.


I'm attempting to get the VM to use ONLY the Logitech C920, for BOTH audio / video input source.

'''[CASE_1]'''

device selection state @ VM 'Devices'
{{{
	Devices
		USB
			[ ] Telex Communications, Inc. Telex USB microphone [0100]
			[ ] Logitech, Inc. HD Pro Webcam C920 [0011]
		Webcams
			[X] HD Pro Webcam C920
}}}
MS using Virtual Audio Device'Sound' > 'Recording'
{{{
	Microphone
	High Definition Audio Device
	Default Device
}}}
@ Microsoft Setup Wizard

there is NO detected audio input at all.


'''[CASE_2]'''

changing device selection state @ VM 'Devices' to
{{{
	Devices
		USB
			[X] Telex Communications, Inc. Telex USB microphone [0100]
			[ ] Logitech, Inc. HD Pro Webcam C920 [0011]
		Webcams
			[X] HD Pro Webcam C920
}}}
MS using Virtual Audio Device'Sound' > 'Recording'
{{{
	Microphone
	High Definition Audio Device
	Default Device
}}}
now @ Microsoft Setup Wizard, audio IS detected from the Telex.

and, testing further, 'separate device' audio & video work
{{{
	WebCam video INPUT from the C920      ---> WORKS
	MIC    audio INPUT from the Telex     ---> WORKS
}}}
So, this is a working config for , e.g., WebEx use in the VM

'''[CASE_3]'''

changing device selection state @ VM 'Devices' to
{{{
	Devices
		USB
			[ ] Telex Communications, Inc. Telex USB microphone [0100]
			[X] Logitech, Inc. HD Pro Webcam C920 [0011]
}}}
automatically forces the change
{{{
		Webcams
			No WebCams detected
}}}
In this config

MS using Virtual Audio Device'Sound' > 'Recording'
{{{
	Microphone
	High Definition Audio Device
	Default Device
}}}
now @ Microsoft Setup Wizard, audio IS detected from the C920.

but there is NO detected/usable video input."	PGNd
16993	Various widgets without labels for accessibility	all		2017-08-09T20:13:54Z	2017-08-10T15:44:38Z	2017-08-10T15:44:38Z	"Hi,

While Oracle assertions are for accessibility introducing VBox beta, I can say we are far from it. Beyond bugs I have submitted about crashes and I confirm with this release, a lot of buttons do not have any label on their widgets, hence a screen reader cannot tell what the button does. Filling the label area sends to qt-t-spi what an assistive technology needs to work properly.

Here is an examples:
- Main window: once opened, press tab twice. The focus reaches, respectively, on two buttons without labels, and ths screen reader just says ""Button""
"	texou
20500	V6.1.26 with Windows 10 2019 LTSC as guest	Windows	VirtualBox 6.1.26	2021-08-12T09:23:54Z	2021-08-12T09:45:13Z	2021-08-12T09:45:13Z	"With last version 6.1.26 ""Auto-resize Guest Display"" doesn't work anymore."	-RedHead-
15228	Using Ubuntu 14.04 host and Windows 7 guest only max. 12582911 bytes can be transferred via shared clipboard	Windows	VirtualBox 5.0.16	2016-03-09T19:00:13Z	2016-03-09T19:00:13Z	2016-03-09T19:00:13Z	"I'm using an Ubuntu 14.04 (fully updated) host and a Windows 7 guest (fully updated). The guest has the new (5.0.16) Guest Additions, which was installed using Windows Safe Mode (so I could install basic 3D acceleration as well).

If I open a random text file of 12582911 bytes (eg. in Notepad) in the guest OS, select it's entire contents and copy it to the (shared) clipboard, then I can paste this into gedit in the host OS.

If I add a single character to the end of the file (so it becomes 12582912 bytes long) and do the same, I cannot paste the clipboards contents into eg. gedit in the host OS.

And of course: anything below 12582911 bytes works too and anything above 12582912 bytes doesn't work. :-)

I tried various apps in the guest (Notepad, Wordpad, Notepad++, Total Commander) to open the text file and copy it's contents to the shared clipboard. And I tried various apps in the host OS too to paste the contents of the clipboard. All showed the same symptom.

I created the test text file in linux using this command (I used unix2dos to convert the text file to DOS/Windows line endings so eg. Notepad won't die on me):
{{{
dd if=/dev/urandom bs=12M count=1 | base64 - | unix2dos | dd bs=1 count=12582911 of=test.txt
}}}

It's contents can still be transferred from guest to host via shared clipboard, but if you add only a single extra character to it, the clipboard transfer fails.

Nothing appears in VB's log or in the host's logs (eg. syslog). Neither when the clipboard transfer works, nor when it doesn't.

In the VM I've ""Shared Clipboard"" set to ""bidirectional""."	muzso
18901	Using serial host device make guest boot hang	Windows	VirtualBox 6.0.10	2019-09-03T14:26:38Z	2020-01-30T16:05:48Z	2020-01-30T16:05:48Z	"I'm using the serial host device since a long time.
Using Fedora (from 20 now 30) host and XP host (because of sortware only running on Windows XP using serial device)
Until VB 5.12, everything worked thing.
But now, after update to Fedora 30, I had to update to the last VirtuaBox release (6.0.10).
My guest does not boot anymore (it hangs)
If i uncheck serial port, it boots.
If I keep serial port and disable it, My guest Boots, serial COM is visible but unsuable (which is normal).

VBox.log is showing this : (see file attached)
 Failed to change parameters to 9600,EVEN,7,1 -> VERR_DEV_IO_ERROR
 Failed to change parameters to 1200,EVEN,7,1 -> VERR_DEV_IO_ERROR

"	cderenne
17439	Using Intel Realsense SR300 camera causes VM Abort	Linux	VirtualBox 5.2.4	2018-01-09T15:50:27Z	2018-01-09T15:50:27Z	2018-01-09T15:50:27Z	"1- guest
1.1 - Linux vagrant 4.4.0-87-generic #110-Ubuntu SMP Tue Jul 18 12:55:35 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
1.2 - 
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 16.04.3 LTS
Release:	16.04
Codename:	xenial

2- install librealsense in vm:

{{{
# if the realsense ubuntu repository was not added add it to ubuntu source list.
if [ ! -f /etc/apt/sources.list.d/realsense-public.list ]; then
    echo 'deb http://realsense-hw-public.s3.amazonaws.com/Debian/apt-repo xenial main' | tee /etc/apt/sources.list.d/realsense-public.list
    apt-key adv --keyserver keys.gnupg.net --recv-key 7DCC6F0F
fi

# make sure you have kernel headers installed, otherwise realsense dkms will not patch the kernel.
apt-get -y install linux-headers-`uname -r`

apt-get -y update
apt-get -y upgrade

apt-get install -y realsense-uvcvideo # kernel patch to support the camera
apt-get install -y librealsense2-utils # demos for the camera 
}}}

3- Plug the camera, and connect to the guest
3.1 - execute the command

{{{
rs-pointcloud
}}}

4- After some seconds the camera vm aborts.

Note: Same setup was tested with VMWare Palyer 14, and vm does not crashes, and the rs-pointcloud application works despite some delays."	mjscosta
4728	using host share for my documents in windows is slow but mapped drive isn't	Windows	VirtualBox 3.0.4	2009-08-09T02:53:10Z	2009-08-23T21:24:11Z	2009-08-23T21:24:11Z	"Weird issue found.

If you change my documents location to your mapped virtual share and use the my documents link to get there it is very slow upwards of 10 seconds to open sometimes longer.

If you create a link to the mapped drive on the desktop it is much faster. Here is where it gets weird. If you change the icon for the shortcut to the mapped drive to the standard folder icon it becomes slow again!

told you it was weird!"	Richard
15465	User Interface shows up on wrong screen	Windows	VirtualBox 5.0.20	2016-05-31T12:59:28Z	2016-05-31T12:59:28Z	2016-05-31T12:59:28Z	I have a configuration with 3 displays. Display 1 shows the ubuntu desktop, display 2 and 3 are running the virtual machine with windows 7. On startup i get a messagebox from virtualbox that one of my serial ports could not be opened (this is another bug). When this happens, usually the GUI in Fullscreen mode is not on the lower side of the displays but somewhere on the first display. When I switch between fullscreen and windowed mode and vice versa everything is ok after that.	audia3
19818	Use portable sched_yield() rather than pthread_yield()	Linux	VirtualBox 6.1.10	2020-08-17T18:56:10Z	2020-08-20T18:20:12Z	2020-08-20T18:20:12Z	"The sched_yield() call is the standard and portable routine.  Current calls to pthread_yield() in Virtualbox sources (host and guests) should be replaced by calls to sched_yield().  If sched_yield() is not available on a platform, then the build tools (including those for the Guest Additions) could arrange to use a shim routine that calls pthread_yield().  

This would be helpful in supporting platforms that do provide support for non-portable libraries and routines."	Harry M
8279	Use FreeRDP instead of rdesktop	other	VirtualBox 4.0.2	2011-02-05T18:35:53Z	2012-03-11T08:52:55Z	2012-03-11T08:52:55Z	"In the Linux version, a modified version of rdesktop is included. The rdesktop project has been dead for quite some time now, at least I haven't seen many changes and improvements recently.
Even though rdesktop works, freeRDP is more active in development and has more features currently.

I got to this after looking for a better RDP client for Linux than tsclient with rdesktop and found Remmina, which uses freeRDP as backend. FreeRDP can be found at www.freerdp.com and their SourceForge site https://sourceforge.net/projects/freerdp/. It supports most features of the latest Remote Desktop Protocol, works with VRDP since version 0.7.4 (it's currently at 0.8.2, released November 12) and allows you to include new features in VRDP without breaking the shipped VRDP client (rdesktop-vrdp).

Please evaluate this new RDP client and include it in the next major version if you decide to include it."	Sasquatch
8985	Use 'addgroup' instead of 'groupadd' in installer	other	VirtualBox 4.0.8	2011-05-29T05:57:03Z	2014-02-27T17:32:49Z	2014-02-27T17:32:49Z	"When testing one of the generic Linux builds (e.g. 'VirtualBox-4.0.8-71778-Linux_x86.run') on a minimal distribution that lacks the 'groupadd' command the 'vboxusers' group will not be created.

Example: TinyCoreLinux, which is based on BusyBox (download: http://distro.ibiblio.org/tinycorelinux/3.x/release/tinycore-current.iso, currently at version 3.6)

The issue could be easily avoided if on those systems in 'install.sh' a command like ""addgroup -S $GROUPNAME"" instead of ""groupadd $GROUPNAME"" would be executed.

After checking a few of the ""big"" (or should one rather say ""bloated"") distributions (e.g. Natty Narwhal or FC-14) I've realized that not all are having 'addgroup' in their base, so first a check of the availability of the respective command would be required."	maronz
18591	USBIP from/to NAS Sinology not working any more	Windows	VirtualBox 5.2.28	2019-04-21T17:22:35Z	2020-01-13T12:17:10Z	2020-01-13T12:17:10Z	"Hi,
I've using Oracle VirtualBox on Linux Mint 18.04 host for over a year, to run a Windows XP printing through USBIP on a 3D printer plugged onto a Synology 216j with VirtualHere USBIP server.

Everything worked fine until Version 5.2.26 r128414 (Qt5.6.1).

After upgrading to 5.2.28, my XP could still see USBIP ports but the Up! 3D application under XP could not see the printer as connected.

After upgrading to virtualbox 6.0, the VM could not see the USBIP port.

Coming back to 5.2.26 make it work again.

Best regards,
Jean-Marc"	Jean-Marc au Boulot
19714	USB Port filter should use Linux USB bus id instead of a random number	all	VirtualBox 6.1.10	2020-07-10T22:18:01Z	2020-07-14T09:15:33Z	2020-07-14T09:15:33Z	"On Linux the ""port"" field in the ""USB Filter"" should ideally use the physical bus id instead of a random number.[[BR]]
In my use case I'd like to create an USB filter limited to a specific physical USB port. If the user e.g. puts some random USB memory stick into this specific physical USB port, it should show up in the VM. For that it would be necessary to have a USB filter which can refer to a unique ""port"", which the current implementation can not guarantee.[[BR]]
[[BR]]
E.g. currently I see this on my machine:[[BR]]
{{{
UUID:               9b7430c2-c602-49d8-84e9-ffbb3a22bce0
VendorId:           0x04d9 (04D9)
ProductId:          0x1133 (1133)
Revision:           2.16 (0216)
Port:               1
USB version/speed:  1/Low
Manufacturer:       Holtek Semiconductor, Inc.
Address:            sysfs:/sys/devices/pci0000:00/0000:00:1d.1/usb3/3-2//device:/dev/vboxusb/003/002
Current State:      Busy

UUID:               191cbe8f-442d-4f5e-9552-c0b0cd7bf119
VendorId:           0x046a (046A)
ProductId:          0x0023 (0023)
Revision:           0.50 (0050)
Port:               1
USB version/speed:  2/Low
Manufacturer:       Cherry GmbH
Product:            CyMotion Master Linux Keyboard G230
Address:            sysfs:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-2//device:/dev/vboxusb/002/002
Current State:      Busy
}}}

As you can see in the example above, both USB ports have ""Port: 1"" and thus they are not uniquely identifyable. So it would be more useful to instead refer the ""Port"" field to ""3-2"" for the first entry, and to ""2-2"" in the second entry (see the ""Address"" field).
"	Helge Deller
17602	USB passthrough problem, when flashing embedded system using PSOC Creator.	Windows	VirtualBox 5.2.6	2018-03-07T10:07:56Z	2018-04-30T14:42:56Z	2018-04-30T14:42:56Z	"I have a problem with PSOC Creator. I'm using usb passthrough to pass cypress development board to Windows 10 on virtual machine. 

My host machine is Arch Linux. I've set up usb filter, and device is correctly recognized on guest machine, but when i try to program the board or connect debugger, PSOC Creator application hangs until i disconnect and reconnect usb cable. Then this error shows up: ""There was an error while programming the device: failed to reacquire the device.""

Trying several times, sometimes it works, sometimes it gets stuck and I need to reconnect device. But most of the time it doesn't work.

I have disabled auto suspend for this device.

If you need some extra information about the system please tell me, I will try to provide them."	morali
20652	USB passthrough fails for Linux hosts and Windows VM with 6.1.28	Windows	VirtualBox 6.1.28	2021-11-08T03:45:07Z	2021-11-23T05:01:03Z	2021-11-23T05:01:03Z	"With version 6.1.28 running on a Linux Host and a Windows 7 or 10 guest, some USB passthrough operations fail.

This was first reported at https://bugzilla.opensuse.org/show_bug.cgi?id=1192338 where the reporter noted that he could not attach an iPhone to iTunes through his Windows 10 VM on an openSUSE Leap 15.3 host. He also notes that when the VM is closed, there is no power on the USB port until he reboots.

I further tested using an RTL8188EUS Wifi dongle passed through to a Windows 7 or 10 guest from an openSUSE Tumbleweed host. In this case, the Windows software creates a network device, but is unable to complete setting it up. This operation worked with 6.1.26.

I tested my setup using the Oracle binary RPM for openSUSE Leap 15. It had the same problem."	Larry Finger
19993	USB MIDI on Windows 2000 SP4	Windows	VirtualBox 6.1.14	2020-10-22T18:20:52Z	2020-10-22T18:20:52Z	2020-10-22T18:20:52Z	"Hello All,

when I connect YAMAHA MIDI Keyboard to Windows 2000 host via USB the system crashes during the PnP phase. When it enters the:

""Found New Hardware - USB Audio Device"" the BSOD appears with:

STOP 0x0000001E ...
KMODE_EXCEPTION_NOT_HANDLED
Address BCEA7A90 base at BCEA3000, DateStamp 3803cad4 - usbaudio.sys
... etc.

I tried almost everything from switching to USB 1.0, changing the Sound Card to SoundBlaster etc.
The Host is Debian 10 (buster) the version of VirtualBox is 6.1.14.

I updated the VirtualBox Guest Add-ons to latest version. Turned off VT-x all leads to BSOD.

Thanks in advance"	unun
13877	USB microscope camera on windows guest : bandwidth error	Windows	VirtualBox 4.3.18	2015-02-21T16:22:03Z	2015-02-21T16:22:03Z	2015-02-21T16:22:03Z	"Guest : Windows XP
Host : Ubuntu 14.04 64 bits
VirtualBox 4.3.10 with extension and additions

I use a professionnal camera (Toupcam) on a microscope connected to USB port of the host. It works on the host.
On the windows guest, with a specific application (Toupview) the camera is detected but when I ask a preview I get an error : the USB bandwidth is not sufficient...
USB 2.0 is activated in VBox and other USB devices work.

An idea ? Thanks."	arverne73
14875	USB ISO packets get stuck in VB 5.X	Windows	VirtualBox 5.0.10	2015-11-29T00:11:42Z	2017-12-12T10:12:43Z	2017-12-12T10:12:43Z	"Hello VB,

After having used 4.X with great pleasure for a long time to debug Windows USB issues in Linux (Fedora), i have hit a snag in the 5.X series.

The problem is always the same. If i start streaming ISO packets they get stuck after a very short while. In the early 5.X builds the entire VM would implode, but now it just hangs the USB stream until i unplug the device.
There is some kind of bug in the 5.X USB implementation. If its the VB drivers in Linux or the virtual drivers in Windows is not clear to me.

Has anyone else seen this problem? I have tried all combinations of options i could think of but the problem persists.

I have attached a Wireshark trace that shows the problem up until the hang. Note that when this happens the *entire* USB freezes up, not just the ISO packets.

Thanks,

/pedro"	donpedro
18149	USB headset disconnection on windows host freezes linux guest	Linux	VirtualBox 5.2.22	2018-11-23T13:11:05Z	2019-01-10T18:02:43Z	2019-01-10T18:02:43Z	"After disconnecting a USB headset (sennheiser mb 660 uc ms) in the host system, the vm freezes (i.e. is no longer responsive to clicks or any other form of interaction including network access). The VirtualBox GUI is no longer responsive either. Repeatedly clicking in the guest window eventually causes it to abort and the VirtualBox GUI becomes responsive again.

Host: Windows 7 x86_64
Guest: Arch linux x86_64

"	oksijun
7773	USB does not work with NIS or LDAP login	other	VirtualBox 3.2.10	2010-11-29T11:29:03Z	2010-11-29T11:29:03Z	2010-11-29T11:29:03Z	"When users are authenticated via NIS or LDAP and uid and gid are provided via NIS or LDAP ordinary users can not mount USB devices in guests onless the provided uid and/or gid are identical on the host and the provided uid and gid from NIS or LDAP.

The problem is that when a user is installing Virtualbox the installation script apparently scans the local group and passwd files and if user and group vbox* is not found then these users and groups are created locally and the information created is used in the following installation process."	Michael Rasmussen
21267	USB devices are not recognized in the guest machine	Windows	VirtualBox 6.1.40	2022-11-12T17:44:04Z	2022-11-13T16:10:00Z	2022-11-13T16:10:00Z	"My USB devices are simply not recognized / detected if I connect them to any USB ports. All of them were successfully detected in previous versions of vbox. And yes, all USB devices I am trying to detect are added to USB devices filters in vbox settings. I have also tried to alternatively enable USB Controller 1.1, 2.0 or 3.0 Without success. 
In the host machine (linux Ubuntu 22) all USB devices are successfully detected. So the problem is only with the guest machine (Windows 10) or the vbox 6.1.40 respectively"	rsm37turb
21312	USB Device unknown	Windows	VirtualBox-7.0.4	2022-11-25T05:53:03Z	2022-12-13T15:33:13Z	2022-12-13T15:33:13Z	Windows7 x64 is installed on the guest system, after applying the VirtualBox 7.0.x update, there were problems with the USB device enumerator. If the memory on the guest system is less than 2068Mb, then everything works (found out experimentally). If you set more memory (2068Mb or more), then when connecting USB devices (barcode scanner, smartphone, etc.), error Code 43 occurs and the device manager identifies the equipment as USB/Unknown.	CrayZD
17572	USB device named incorrectly	Windows	VirtualBox 5.0.40	2018-02-27T18:43:20Z	2018-03-02T08:49:28Z	2018-03-02T08:49:28Z	"Hi All,

Really odd behaviour we are getting from our VMs. We have 3 VMs running windows 7 and each has a dongle that grants access to proprietary software. 2 dongles grant access to HASP software and 1 grants access to Windfarmer. These usb devices are incorrectly named in Virtual box which is causing some confusion, We can only use Windfarmer software when one of the ""HASP"" dongles is connected and vice versa.

Not sure how/when this began happening or why. This would be a purely aesthetic problem but the two HASP dongles are identical and cannot be distinguished between each other using the USB filter so occasional they are assigned to the incorrect VM which means we have to manually fix it.

Logs attached.  





"	DanitDan
16852	USB Barcode Scanner not working properly under Windows Virtualbox	Windows	VirtualBox 5.0.20	2017-06-22T06:31:25Z	2017-06-22T06:31:25Z	2017-06-22T06:31:25Z	"'''Environment:''' Using a Linux host with Virtualbox 5.0.20 and a Windows 7 Prof. guest. [[BR]]

USB 3.0 XHCI activated. [[BR]] [[BR]]


There is a USB Barcode Scanner (Datalogic Powerscan) connected
and installed.
For some reasons, the scanner is not working proberly. 
It works correct for 5-10 times of scanning
and then it drops a couple of characters out for the next scan.
It correctly scans into Linux - without any error.

''It must be a reason of the Virtualbox USB Handling.''

'''If i open wireshark with USBPcap installed and start to sniff the USB ports the problem is solved, as long as the Wireshark is running.'''
See attached File for more information of scans.

There are already 2 Tickets of this problem, years ago but without any solution

[https://www.virtualbox.org/ticket/11671 Ticket 11671][[BR]]

[https://www.virtualbox.org/ticket/11772 Ticket 11772]


"	itsbasti
19869	USB audio interface Scarlett 4i4 3GEN no output sound	Windows	VirtualBox 6.1.14	2020-09-08T17:42:16Z	2022-04-12T11:56:35Z	2022-04-12T11:56:35Z	"First of all i have a question: if you have a linux host with windows 10 guest, where should i post for bugs/problems in the forum of linux hosts or in the windows guests ?
Said this, i have an scarlet4i4 focusrite 3gen audio interface, after several tries and problems i get it to setup and make it work.... but i have no output sound in my speakers.

Seems that the setup is correct and in windows works, but some kind the sound gets lost from output of the guest 



"	edufissure
21225	USB	Windows	VirtualBox 6.1.38	2022-10-31T19:56:56Z	2022-11-04T12:30:09Z	2022-11-04T12:30:09Z	"USB is shown as working just fine when defining the Guest VM xppro
however, when xppro is run and accessing Devises the USB section is grayed out.

Running Linux Mint 20 Ulyssa"	buz
15467	Upgrade to Windows 10 fails	Windows	VirtualBox 5.0.20	2016-05-31T14:10:25Z	2016-06-12T12:21:25Z	2016-06-12T12:21:25Z	"The upgrade from Windows 7 (64 Bit) to Windows 10  with the upgrade tool 'GWX' isn't possible.
Please see attached screenshot.

BS: Ubuntu 16.04 64 Bit"	Josef Latt
17259	Upgrade 5.1.28 to 5.2 headless guest can no longer be accesses, video performace degraded	Windows	VirtualBox 5.2.0	2017-11-10T05:43:40Z	2017-11-15T06:18:24Z	2017-11-15T06:18:24Z	"Upgrade from 5.1.28 to 5.2 (Arch x86_64 host) leaves headless Win7 guests unable to capture mouse or keyboard regardless of host-key use until virtualbox is started on host machine and guest launched via gui interface and windows guest addtions updated from 5.1.28 to 5.2.

PUEL from VirtualBox-5.2.0-118431-Linux_amd64.run with Oracle_VM_VirtualBox_Extension_Pack-5.2.0.vbox-extpack

This is unexpected new behavior. The expected result is that following update, the headless client can be started and accessed as normal remotely via rdesktop and guest additions updated from within headless guest as has been the case with all prior 5.1.X updates. 

An update to 5.2 on the host will leave Win7 (and probably others) unable to access the headless guests remotely. There is no way to have the mouse or keyboard captured when first accessing a headless Win7 guest remotely after the 5.2 update on the host. The login screen is displayed and visible, but there is no way to interact with it -- with or without host-key use (currently the default rt-control)

When virtualbox is started on the host machine, prior guest additions are ignored and prior setvideomodehint resolution and color depths settings are ignored. The default capture host-key dialog is shown as if no prior guest additions are present.

If the incompatibility between 5.1.2X guest additions and 5.2 is a known issue, this should be clearly stated in the changelog as it impacts remote headless guest access that guest users cannot correct without access to the host machine.

Secondly, after 5.2 guest additions are installed from the host, and the guest and virtualbox shut down, the guest can then be restarted headless and access remotely. setvideomodehint on the host must be reset to restore 32bit display color depth for remote access. Video performance within the headless guest is degraded compared to 5.1.28 with lagging window moves within the Win7 guest and artifacts at the window corners on repaint that were not present in 5.1.28. (this is with 2D accell only, no 3D or aero active)

Please let me know what additional information you may need to help with this bug and I'll be happy to provide it."	drankinatty
17210	Updated to VB 5.2.0; install failed	Linux	VirtualBox 5.2.0	2017-10-25T22:08:28Z	2017-10-25T22:08:28Z	2017-10-25T22:08:28Z	"I have tried to upgrade VirtualBox to 5.2.0 but the installation failed. Then I tried the ""latest
test (dev?) build (VirtualBox-5.2.1-118468-Linux_amd64.run) but the installation has again failed.

I must be doing something wrong since I am almost continually getting this error (see the enclosed log).

Am I doing something wrong? The error log suggests various versions of ""libelf"" but Fedora 28 (rawhide) doesn't
have any of these packages and as far as I know, never has.

Any help you can give me about this problem would be greatly appreciated.

Regards,

George...
"	George R. Goffe
13613	Update vboxadd and vboxadd-service startup scripts for LFS 7.6	Linux	VirtualBox 4.3.18	2014-11-13T06:29:27Z	2014-11-13T06:29:27Z	2014-11-13T06:29:27Z	"Since /etc/rc.d/init.d/functions is removed in LFS 7.6, the existing vboxadd and vboxadd-service startup scripts will not work.
That means those scripts have to be updated."	hykwok
21328	Update to 7.0.4 seems to crash after lacking 6.1.38?	Windows	VirtualBox-7.0.4	2022-12-09T18:27:06Z	2022-12-13T15:53:52Z	2022-12-13T15:53:52Z	"I loved Virtual Box and did neglect updating-problems. My favorite forum does not have a clue why 7.0.4 fails as follows:

{{{
BuschBo:~> VirtualBox 
libGL error: MESA-LOADER: failed to open nouveau: /usr/lib64/dri/nouveau_dri.so: Kann die Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht gefunden (search paths /usr/lib64/dri, suffix _dri)
libGL error: failed to load driver: nouveau
Qt WARNING: QObject::connect: No such signal UITabBar::currentChanged(int)
Qt WARNING: QObject::connect: No such signal UITabBar::tabMoved(int,int)
Qt WARNING: QObject::connect: No such signal UITabBar::tabBarClicked(int)
Qt WARNING: QObject::connect: No such signal UITabBar::tabBarDoubleClicked(int)
/usr/bin/VirtualBox: Zeile 70:  9312 Speicherzugriffsfehler  (Speicherabzug geschrieben) LD_LIBRARY_PATH=""/usr/lib/virtualbox${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}"" /usr/lib/virtualbox/VirtualBox6 $@

BuschBo:~> systemctl status vboxdrv.service
● vboxdrv.service - VirtualBox Linux kernel module
     Loaded: loaded (/usr/lib/virtualbox/vboxdrv.sh; disabled; vendor preset: disabled)
     Active: active (exited) since Fri 2022-12-09 18:45:05 CET; 34min ago

BuschBo:~> uname -a
Linux BuschBo 5.14.21-150400.24.33-default #1 SMP PREEMPT_DYNAMIC Fri Nov 4 13:55:06 UTC 2022 (76cfe60) x86_64 x86_64 x86_64 GNU/Linux

BuschBo:~> zypper se -si virtualbox vbox
Repository-Daten werden geladen...
Installierte Pakete werden gelesen...

S  | Name                   | Type  | Version                                   | Arch   | Repository
---+------------------------+-------+-------------------------------------------+--------+-----------------------
i+ | virtualbox             | Paket | 7.0.4-lp154.2.20.2                        | x86_64 | Main Update Repository
i  | virtualbox-kmp-default | Paket | 7.0.4_k5.14.21_150400.24.33-lp154.2.20.2  | x86_64 | Main Update Repository
i  | virtualbox-kmp-default | Paket | 6.1.38_k5.14.21_150400.24.21-lp154.2.15.1 | x86_64 | Main Update Repository
i  | virtualbox-qt          | Paket | 7.0.4-lp154.2.20.2                        | x86_64 | Main Update Repository

BuschBo:~> zypper lr -d
#  | Alias                       | Name                                                                                        | Enabled   | GPG Check       | Refresh        | Priority  | Type   | URI                                                                                                                                                                              | Serv->
---+-----------------------------+---------------------------------------------------------------------------------------------+-----------+-----------------+----------------+-----------+--------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------
 1 | openSUSE-Leap-15.4-1        | openSUSE-Leap-15.4-1                                                                        | Nein      | ----            | ----           |   99      | rpm-md | hd:/?device=/dev/disk/by-id/usb-SanDisk_Ultra_05019bbc553237f7fd551958a91e01fe4ded604716e4280b429924ea2772cd6d46f90000000000000000000010702a2300961a10815581071ea825d9-0:0-part2 | 
 2 | repo-backports-debug-update | Update repository with updates for openSUSE Leap debuginfo packages from openSUSE Backports | Nein      | ----            | ----           |   99      | NONE   | http://download.opensuse.org/update/leap/15.4/backports_debug/                                                                                                                   | 
 3 | repo-backports-update       | Update repository of openSUSE Backports                                                     | Ja        | (r ) Ja         | Ja             |   99      | rpm-md | http://download.opensuse.org/update/leap/15.4/backports/                                                                                                                         | 
 4 | repo-debug                  | Debug Repository                                                                            | Nein      | ----            | ----           |   99      | NONE   | http://download.opensuse.org/debug/distribution/leap/15.4/repo/oss/                                                                                                              | 
 5 | repo-debug-non-oss          | Debug Repository (Non-OSS)                                                                  | Nein      | ----            | ----           |   99      | NONE   | http://download.opensuse.org/debug/distribution/leap/15.4/repo/non-oss/                                                                                                          | 
 6 | repo-debug-update           | Update Repository (Debug)                                                                   | Nein      | ----            | ----           |   99      | NONE   | http://download.opensuse.org/debug/update/leap/15.4/oss/                                                                                                                         | 
 7 | repo-debug-update-non-oss   | Update Repository (Debug, Non-OSS)                                                          | Nein      | ----            | ----           |   99      | NONE   | http://download.opensuse.org/debug/update/leap/15.4/non-oss/                                                                                                                     | 
 8 | repo-non-oss                | Non-OSS Repository                                                                          | Ja        | (r ) Ja         | Ja             |   99      | rpm-md | http://download.opensuse.org/distribution/leap/15.4/repo/non-oss/                                                                                                                | 
 9 | repo-oss                    | Main Repository                                                                             | Ja        | (r ) Ja         | Ja             |   99      | rpm-md | http://download.opensuse.org/distribution/leap/15.4/repo/oss/                                                                                                                    | 
10 | repo-sle-debug-update       | Update repository with debuginfo for updates from SUSE Linux Enterprise 15                  | Nein      | ----            | ----           |   99      | NONE   | http://download.opensuse.org/debug/update/leap/15.4/sle/                                                                                                                         | 
11 | repo-sle-update             | Update repository with updates from SUSE Linux Enterprise 15                                | Ja        | (r ) Ja         | Ja             |   99      | rpm-md | http://download.opensuse.org/update/leap/15.4/sle/                                                                                                                               | 
12 | repo-source                 | Source Repository                                                                           | Nein      | ----            | ----           |   99      | NONE   | http://download.opensuse.org/source/distribution/leap/15.4/repo/oss/                                                                                                             | 
13 | repo-update                 | Main Update Repository                                                                      | Ja        | (r ) Ja         | Ja             |   99      | rpm-md | http://download.opensuse.org/update/leap/15.4/oss                                                                                                                                | 
14 | repo-update-non-oss         | Update Repository (Non-Oss)                                                                 | Ja        | (r ) Ja         | Ja             |   99      | rpm-md | http://download.opensuse.org/update/leap/15.4/non-oss/                                                                                                                           | 
}}}"	Christiann
18255	Update to 6.0.0 caused my Windows 10 image not to resolute anymore the 2 monitors.	Windows	VirtualBox 5.2.22	2018-12-31T17:11:54Z	2019-01-02T11:21:33Z	2019-01-02T11:21:33Z	"Host : Ubuntu 16.04
Host System: NVIDIA Graphics, i7 core, 24 GB RAM
VirtualBox Client: Windows 10
worked with VirtualBox 5.2
Issues that the second screen has only 1280x1024 instead of 1600 x1200

That was working before I run the machine today.I have not worked for month with the target.

An update to 5.2.22 was announced. I clicked it away. Then I got the small issue mentioned above. I decided to do the update. On the homepage 6.0 was announced instead of 5.2.22. So I downloaded the deb-File for 16.04. Ubuntu Software Center could not install it. Old version has been still installed at this time. But then followed the instructions on the page and downloaded and installed it by command line adding the repo for it.

After starting my Windows 10  machine, there was only two very small VGA screens left. After trying to reinstall the vboxguestadditions, there was only one screen left at least with 1280x1024 resultion.

There have been errors installing the guest additions they stuck installing some driver fro VBoxVideoW8 for a ""hardware that is currently not present"". Please see the log.

How can I rescue my windows copy. Because I think something was messed up during installation of VB 6.0 or the guest additions. I meanwhile deleted the vbox in /usr/share/virtualbox but after reinstallation error stays stable. I am not able to continue working on my projects
.

In the end I deinstalled 6.0 and get me a copy of 5.2.22.

Please help save my work, because last time it all worked perfectly!

Best regards
Peter
"	peddanet
21193	Update build instruction page	other	VirtualBox-7.0.2	2022-10-22T17:26:27Z	2022-10-22T17:26:27Z	2022-10-22T17:26:27Z	"The wiki page (https://www.virtualbox.org/wiki/Linux%20build%20instructions) containing the build instruction seems to be a bit out of date.

The instructions for a Linux host are missing at least 
the reference to `glslang`, `liblzf` and maybe others.
gcc-3.3.3 might still work, but nowadays, `gcc-12.2.0` is recent.
What about Java versions beyond JDK6, how to use newer JDKs (9, 11, 17 or even newer) than JDK8?
"	Moody
21451	Upcoming problem for Fedora 38 rpms	all	VirtualBox-7.0.6	2023-02-01T02:26:58Z	2023-02-01T02:26:58Z	2023-02-01T02:26:58Z	"Fedora 38 (currently Rawhide - but due to be released in April) has tightened the security on the crypto on the rpm packages. While we until only few day ago could use your released Fedora36 packages on even rawhide, that is no longer possible, because your signing mechanism is now outdated.

This is just a heads up for Fedora 38 release in april - it should not affect current Fedora 35/36/37 releases.

Please read this blogpost from nirik about the changes:
https://www.scrye.com/wordpress/nirik/2023/01/31/error-rpmdbnextiterator-skipping-in-fedora-38/

"	Yoda
20233	Unwanted conversion dynamic to fixed disk	Windows	VirtualBox 6.1.18	2021-03-04T10:07:46Z	2021-03-08T12:40:05Z	2021-03-08T12:40:05Z	"Hello!

I'm unsure about this is a bug or a feature, but I'm very confused about it:

I have a VM with a fixed VDI. This is explicitly what I want to have for some performance issues on Linux host. When I clone this VM via Ctrl-O, I wondering that the clone has an dynamic VDI, I didnt like that behavior. 

But really really bad is: The source VM is also converted to a dynamic VDI. Therefore I must go to the vboxmanage modifyvm twice (for source and target VM) and convert it back to fixed. These steps consumes unneccessarily space on my SSD.

Please make an selection in the GUI which target disk type is wanted. And much more important: Please leave the source VM unchanged!

Thanks and Greets!"	Codehunter
20339	Unpinned toolbar minimized when navigating sub menues	Windows	VirtualBox 6.1.22	2021-05-05T08:05:42Z	2021-05-05T08:05:42Z	2021-05-05T08:05:42Z	"If the toolbar isn't pinned it disappears few seconds after clicking on a sub menu. This is annoying when searching for an selection that you don't know exactly where it is located or if accidentally clicking the neighboring menu by mistake.

Reproduce:
1) Start a guest (any guest, doesn't matter what OS)
2) Disable pinning on VirtualBox toolbar
3) Click on any Menu, let's take [Help] as an example.
4) Try to highlight (i.e. NOT selecting/clicking) [Help] -> [About VirtualBox...] -> (back to top again) -> [Devices] -> [Audio]  and do this *without* clicking the mouse again.

Result:
Toolbar will disappear approximately one second after [Help] is clicked, making navigating between different top menus impossible without  having to raise the toolbar again (done by clicking somewhere outside the now ""floating"" Help-sub menu and then moving mouse back to toolbar.

Expected result:
Toolbar remains active until any sub menu selection is selection is activated/clicked"	utforskaren
16059	Unpaused hidden vms are crashing in i3-wm when removing host-screen	all	VirtualBox 5.1.6	2016-10-11T14:32:27Z	2017-07-21T15:18:20Z	2017-07-21T15:18:20Z	"I'm running virtualbox on archlinux with the i3 window manager (all installed via pacman). Furthermore I'm working with two monitors on my host, thus using two screen outputs.  Since updating virtualbox from version 5.0.22-1 to 5.1.6-1 (i3-wm stood in newest available verion 4.11-1) the following error was introduced:

If I store the virtual-guest GUI-representations in an tabbed i3-container (thus only the guest behind the active tab is displayed and the other ones are kept hidden behind their tabs) and remove one of my two outputs via „xrandr --output <OUTPUT> --off“, i3 (as always) starts to merge all workspaces to the remaining monitor. Unfortunately all vms which were awake and hidden behind a inactive (meaning not displayed) i3 tab are crashed afterwards. 

The logfiles carry no information about the crashing reason, meaning both, the crashed and survived ones, whose which moved (or had to be moved) to another output and those which stayed (or should have stayed) on the remaining one, they all contain this lines in their logfile:

00:02:03.886456 GUI: UIMachineLogic: Host-screen count changed
00:02:04.014195 GUI: UIMachineViewNormal::adjustGuestScreenSize: Adjust guest-screen size if necessary.
00:02:04.014233 GUI: UIMachineLogic: Host-screen available-area changed
00:02:04.045512 GUI: UIMachineLogic: Host-screen geometry changed
00:02:04.045641 GUI: UIMachineViewNormal::adjustGuestScreenSize: Adjust guest-screen size if necessary.
00:02:04.045655 GUI: UIMachineLogic: Host-screen available-area changed

Is there a way to tune the logging amount for this purpose? Here is my output of

vboxmanage debugvm testvm show logdbg-settings    
Debug logger settings:
                    VBOX_LOG=all=0x0
              VBOX_LOG_FLAGS=enabled unbuffered uself overwrite abs hex
  

One possible workaround is to pause all vms, another is to keep all vms visible on a focused workspace while removing one output. Furthermore while working with two monitors the workspaces can be moved between them without causing a crash of the hidden and unpaused vms.

This is a quite strange but easy reproducible behavior. For testing purposes I set up new vms without virtual HDs just running into BIOS-settings and they crashed too.

Could be related to: https://www.virtualbox.org/ticket/15863 
"	1337
16144	"Unhelpful feedback ""DrvVD: Configuration error: keys incorrect at level 0"""	Linux	VirtualBox 5.1.8	2016-11-03T17:16:38Z	2016-11-03T17:55:34Z	2016-11-03T17:55:34Z	"Starting a VM which formerly worked fine fails due to
{{{
    DrvVD: Configuration error: keys incorrect at level 0 (VERR_PDM_DRVINS_UNKNOWN_CFG_VALUES).
    AHCI: Failed to attach drive to Port0 (VERR_PDM_DRVINS_UNKNOWN_CFG_VALUES).


    Fehlercode:
    NS_ERROR_FAILURE (0x80004005)
    Komponente:
    ConsoleWrap
    Interface:
    IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
}}}
displayed in dialog after start. It'd be helpful to know what failure occurred for what reason and what are useful steps to proceed. It looks like an error in the configuration file, but it's just too useless to guess if you could improve the feedback.

experienced on Ubuntu 16.10 host with Gentoo guest"	krichter
16634	Unexpected opening of a subwindow causes annoyance	Windows	VirtualBox 5.1.18	2017-04-02T01:55:28Z	2017-04-02T01:55:28Z	2017-04-02T01:55:28Z	"If I'm staring a VM I'm noticing that sometimes after a few seconds a subwindow with the text ""Starting virtual machine ..."" and a progress bar is appearing. Since the subwindow opens delayed I have encountered the issue that it claims the focus and switches to it if I'm already working on another window which is annoying. Maybe there is a way to solve this issue."	Sworddragon
17627	Unconditional upscaling of display on HIDPI systems	Windows	VirtualBox 5.2.6	2018-03-19T09:34:40Z	2018-04-06T06:41:39Z	2018-04-06T06:41:39Z	"When using VirtualBox on systems with HiDPI screens, VirtualBox unconditionally scales the VM display using the system-wide scale factor - despite a scale-factor of 100% is selected in the VM settings.

This leads to several consequences:
* Text is barely readable (glyphs simply can't be simply upscaled using whole-screen image scaling)
* The guest OS is presented a lower resolution than the host's monitor would be capable of, so even HiDPI-aware guest OSs have to run in super-ugly upscaled mode.

please see:
https://forums.virtualbox.org/viewtopic.php?f=7&t=86809
https://forums.virtualbox.org/viewtopic.php?f=7&t=87184"	Linuxhippy2
17335	unattended install uses wrong path for UnattendedTemplates dir	all	VirtualBox 5.2.0	2017-11-30T15:14:26Z	2019-02-07T00:18:48Z	2019-02-07T00:18:48Z	"This is for VirtualBox 5.2.2 (that version wasn't available as a selection)

* Host OS:  CentOS 7.4 (all updates current)
* Version:  VirtualBox-5.2-5.2.2_119230_el7-1.x86_64

When trying to use the new ""unattended install"", it fails, presumably because it's trying to find the UnattendedTemplates directory in the wrong location:

{{{
$ vboxmanage unattended install centos7 --iso /iso/CentOS-7-x86_64-Minimal-1708.iso
VBoxManage: info: Preparing unattended installation of RedHat_64 in machine 'centos7' (62f5cf05-2814-4ba8-95f3-4d51a94f5507).
VBoxManage: error: Failed to open '/usr/share/virtualbox/UnattendedTemplates/redhat67_ks.cfg' (VERR_FILE_NOT_FOUND)
VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component UnattendedWrap, interface IUnattended, callee nsISupports
VBoxManage: error: Context: ""Prepare()"" at line 1643 of file VBoxManageMisc.cpp
}}}

The UnattendedTemplates directory appears to be in a different location when installing via RPM:

{{{
$ rpm -ql VirtualBox-5.2 | grep UnattendedTemplates
/usr/lib/virtualbox/UnattendedTemplates
/usr/lib/virtualbox/UnattendedTemplates/debian_postinstall.sh
/usr/lib/virtualbox/UnattendedTemplates/debian_preseed.cfg
/usr/lib/virtualbox/UnattendedTemplates/fedora_ks.cfg
/usr/lib/virtualbox/UnattendedTemplates/ol_ks.cfg
/usr/lib/virtualbox/UnattendedTemplates/redhat67_ks.cfg
/usr/lib/virtualbox/UnattendedTemplates/redhat_postinstall.sh
/usr/lib/virtualbox/UnattendedTemplates/ubuntu_preseed.cfg
/usr/lib/virtualbox/UnattendedTemplates/win_nt5_unattended.sif
/usr/lib/virtualbox/UnattendedTemplates/win_nt6_unattended.xml
/usr/lib/virtualbox/UnattendedTemplates/win_postinstall.cmd
}}}

If I create a symlink from `/usr/share/virtualbox/UnattendedTemplates` to `/usr/lib/virtualbox/UnattendedTemplates`, then the unattended installation succeeds.



"	Greg Bailey
14263	Unable to start Windows 10 64 build 10162 (preview) guest under i686 Linux host: The digital signature for this file couldn't be verified	Windows	VirtualBox 5.0.0	2015-07-11T16:04:41Z	2015-09-02T09:02:00Z	2015-09-02T09:02:00Z	"I have troubles trying to run the preview of Windows 10 64 build 10162 (Windows10_InsiderPreview_x64_EN-US_10162.iso) under Linux (i686 PAE) using VirtualBox 5.0.

When I try to boot my Windows 10 64 guest I see this error message:

Recovery

Your PC/Device needs to be repaired

The digital signature for this file couldn't be verified.

Error code: 0xc0000428

My ISO file is correct (verified using SHA1 hash: 31346458255afeac1afeed5c4c61f15d57708b9b)

My host is: Linux 4.1.0 i686 PAE, 16GB of RAM
My guest is: Windows 10 64

People with a totally different HW configuration also have this problem.

This is a cross post from here: https://forums.virtualbox.org/viewtopic.php?f=2&t=68840"	Artem S. Tashkinov
21427	Unable to resize screen on Windows 10 guest with 3D acceleration enabled	Windows	VirtualBox-7.0.6	2023-01-22T15:58:57Z	2023-01-22T15:58:57Z	2023-01-22T15:58:57Z	"When I use the View menu with 3D acceleration disabled it allows me to choose a different resolution (1600x900) and it changes both the resolution itself and the value in Windows ""Display Settings"", which presumably is the expected behaviour. However, with 3D acceleration enabled it reverts to the previous setting when I try to set it and the resolution is unchanged even after a reboot."	Harold Hare
21426	Unable to resize screen on Windows 10 guest with 3D acceleration enabled	Windows	VirtualBox-7.0.6	2023-01-22T15:49:04Z	2023-01-22T15:49:04Z	2023-01-22T15:49:04Z		Harold Hare
16744	Unable to open virtual machines after upgrading	all	VirtualBox 5.1.22	2017-05-08T15:52:45Z	2017-05-08T16:30:44Z	2017-05-08T16:30:44Z	"Host: Linux Mint Sarah
Guests: Multiple (xenial xerus + Windows)


Immediately after upgrading VB, I get the following error on attempting to open any of the machines:

************

RTR3InitEx failed with rc=-1912 (rc=-1912)
The VirtualBox kernel modules do not match this version of VirtualBox
Fallo al abrir una sesión para la máquina virtual jvr.

The virtual machine 'jvr' has terminated unexpectedly during startup with exit code 1 (0x1).

Código Resultado: NS_ERROR_FAILURE (0x80004005)
Componente: MachineWrap
Interfaz: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}

**************

I'm aware there are some posts on the Internet about it, but the information is not clear to me. Any help would be appreciated!



"	kalevala
16432	Unable to open sqlite database on shared folder	Linux	VirtualBox 5.1.14	2017-01-28T15:32:50Z	2018-08-22T16:43:17Z	2018-08-22T16:43:17Z	"When attempting to open an sqlite database on a shared folder it fails with ""Error: disk I/O error""

If I copy that same database from the shared folder locally to the VM then the open succeeds.
{{{
jlmcgraw@mate1604:~$ sqlite3 /media/sf_Shared_Folder/Recordings.db 
 SQLite version 3.14.1 2016-08-11 18:53:32
 Enter "".help"" for usage hints.
 sqlite> .tables
 
 Error: disk I/O error
 sqlite> .q

jlmcgraw@mate1604:~$ cp /media/sf_Shared_Folder/Recordings.db .

jlmcgraw@mate1604:~$ sqlite3 Recordings.db 
 SQLite version 3.14.1 2016-08-11 18:53:32
 Enter "".help"" for usage hints.

 sqlite> .tables
 ZDATABASEPROPERTY  ZRECORDING         Z_MODELCACHE     
 ZENTITYREVISION    Z_METADATA         Z_PRIMARYKEY     

 sqlite> .q
}}}"	jlm
18904	Unable to install VirtualBox on Debian 10 Buster	all	VirtualBox 6.0.10	2019-09-04T11:59:32Z	2019-10-07T14:12:26Z	2019-10-07T14:12:26Z	"Hello.

Today I tried to upgrade my VirtualBox to the latest version.
I powered off my vms and started the update.
Now, all the versions I try to install (testbuilds included) fail on compiling.
The host is older. No Secure Boot, no EFI, just plain old BIOS and MBR.
OS: Debian 10 Buster almost headless (LXDE installed, but it doesn't start on boot and I almost never use it).

Errors on install:
vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why

dmesg:
[  360.630491] vboxdrv: loading out-of-tree module taints kernel.
[  360.630672] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel
[  360.630887] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000e65fb879, val ffffffffc0ab74cf
[  474.533886] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000e65fb879, val ffffffffc0ab74cf
[ 2230.385340] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000e65fb879, val ffffffffc0ab74cf
[ 4321.446054] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 0000000058cb242c, val ffffffffc0b734cf
[ 4468.860093] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000e65fb879, val ffffffffc0ab74cf
[ 4912.527732] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000e65fb879, val ffffffffc0ab74cf
[ 4946.446931] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000e65fb879, val ffffffffc0ab74cf
[ 5099.180792] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 0000000058cb242c, val ffffffffc0b734cf
[ 5657.446078] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000e65fb879, val ffffffffc0ab75af
[ 6310.679083] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000751064cb, val ffffffffc0ab792f
[ 7275.790717] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000e65fb879, val ffffffffc0ab74cf

I tried the Fedora 29/30 fix, with no luck.

Please help... I'd hate to reinstall and fall back to Stretch.

If you need more details, please let me know.

Thank you."	baltzatu
18343	Unable to import OVA with error NS_ERROR_INVALID_ARG	Linux	VirtualBox 6.0.2	2019-01-21T15:13:38Z	2022-07-23T07:02:26Z	2022-07-23T07:02:26Z	"$ vboxmanage import packer_cache/31bc31daafd70a05b35eef0741b96f878b356b4721385a42056d02b946cc22d2.ova
{{{
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interpreting /var/lib/jenkins/tsenay/packer-core-os-builder/packer_cache/31bc31daafd70a05b35eef0741b96f878b356b4721385a42056d02b946cc22d2.ova...
OK.
Disks:
  vmdisk1       41943040000     -1      http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized       rhel-75-x86_64-core-os-disk001.vmdk     -1      -1

Virtual system 0:
 0: Suggested OS type: ""RedHat_64""
    (change with ""--vsys 0 --ostype <type>""; use ""list ostypes"" to list all possible values)
 1: Suggested VM name ""rhel-75-x86_64-core-os""
    (change with ""--vsys 0 --vmname <name>"")
 2: Suggested VM group ""/""
    (change with ""--vsys 0 --group <group>"")
 3: Suggested VM settings file name ""/home/ldapccs/tsenay/VirtualBox VMs/rhel-75-x86_64-core-os/rhel-75-x86_64-core-os.vbox""
    (change with ""--vsys 0 --settingsfile <filename>"")
 4: Suggested VM base folder ""/home/ldapccs/tsenay/VirtualBox VMs""
    (change with ""--vsys 0 --basefolder <path>"")
 5: Description ""packer-core-os-image Virtual Machine""
    (change with ""--vsys 0 --description <desc>"")
 6: Number of CPUs: 2
    (change with ""--vsys 0 --cpus <n>"")
 7: Guest memory: 2048 MB
    (change with ""--vsys 0 --memory <MB>"")
 8: Network adapter: orig NAT, config 3, extra slot=0;type=NAT
 9: IDE controller, type PIIX4
    (disable with ""--vsys 0 --unit 9 --ignore"")
10: IDE controller, type PIIX4
    (disable with ""--vsys 0 --unit 10 --ignore"")
11: Hard disk image: source image=rhel-75-x86_64-core-os-disk001.vmdk, target path=rhel-75-x86_64-core-os-disk001.vmdk, controller=9;channel=0
    (change target path with ""--vsys 0 --unit 11 --disk path"";
    disable with ""--vsys 0 --unit 11 --ignore"")
0%...10%...20%...30%...40%...50%...
Progress state: NS_ERROR_INVALID_ARG
VBoxManage: error: Appliance import failed
VBoxManage: error: Code NS_ERROR_INVALID_ARG (0x80070057) - Invalid argument value (extended info not available)
VBoxManage: error: Context: ""RTEXITCODE handleImportAppliance(HandlerArg*)"" at line 957 of file VBoxManageAppliance.cpp
}}}"	tsenay
20133	Unable to delete or add extensions	all	VirtualBox 6.1.16	2021-01-18T14:54:54Z	2021-01-18T14:54:54Z	2021-01-18T14:54:54Z	"When I try to remove an extension package, I have this error:

Failed to uninstall the Extension Pack Oracle VM VirtualBox Extension Pack.
Result Code: NS_ERROR_FAILURE (0x80004005)

When I want to add an extension package, clicks are inactive in the selection window.
Terminal says:
Qt WARNING: QWidgetWindow(0x558d168d1a20, name=""UIGlobalSettingsExtensionWindow"") must be a top level window.
Qt WARNING: We got some errors while running testparm ""Error loading services.""
Qt WARNING: We got some errors while running 'net usershare info'
Qt WARNING: ""Can't load /etc/samba/smb.conf - run testparm to debug it\n""
Qt WARNING: No node found for item that was just removed: QUrl(""file:///home/redhead/.Xauthority"")
Qt WARNING: QWidgetWindow(0x558d16db92b0, name=""UIGlobalSettingsExtensionWindow"") must be a top level window.

And if I click directly on the extension package, I have this error:
Failed to install the Extension Pack /home/redhead/Téléchargements/Oracle_VM_VirtualBox_Extension_Pack-6.1.16.vbox-extpack.
Result Code: NS_ERROR_FAILURE (0x80004005)











"	-RedHead-
17612	Unable to create RAWDISK vmdk which includes extended partition	other	VirtualBox 5.2.8	2018-03-10T13:09:40Z	2020-03-04T10:10:45Z	2020-03-04T10:10:45Z	"System is dual boot between Windows 7 Professional and Debian 9. 
The bare-metal Windows 7 system is installed on a 256GB SSD which has the 
system reserved partition, Windows system partition and two data partitions, one of which is a logical partition. 

Debian has VirtualBox 5.2.8 installed and a separate instance of Windows 7 is installed within a virtual machine which requires RAW DISK access to the two data partitions mentioned above. 

Issuing parted from Debian shows the following (correct) partition structure for the drive,


{{{
Disk /dev/sdb: 256GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type      File system  Flags
 1      1049kB  106MB   105MB   primary   ntfs         boot
 2      107MB   41.3GB  41.2GB  primary   ntfs
 3      41.3GB  68.1GB  26.8GB  primary   ntfs
 4      68.1GB  256GB   188GB   extended               lba
 5      68.2GB  256GB   188GB   logical   ntfs 
}}}
 

Issuing the VBoxManage listpartitons -rawdisk command does not give the same results, as shown below.


{{{
VBoxManage internalcommands listpartitions -rawdisk /dev/sdb
Number  Type   StartCHS       EndCHS      Size (MiB)  Start (Sect)
1       0x07  0   /32 /33  12  /223/19           100         2048
2       0x07  13  /0  /52  1022/254/63         39290       208896
3       0x07  1022/254/63  1022/254/63         25600     80674816 

}}}

It does not appear to have recognised the extended/logical partition 
structure and has also calculated partition 3 as the size of the whole drive.

Attempts to create a RAW DISK vmdk just referencing relative partitions 3 and 5 give the following warning message :


{{{
VBoxManage internalcommands createrawvmdk -filename ""/disk/VM System/Raw Disks/Windows Data.vmdk"" -rawdisk ""/dev/sdb"" -partitions 3,5 -relative
VBoxManage: warning: It is not possible (and necessary) to explicitly give access to the extended partition 5. If required, enable access to all logical partitions inside this extended partition.
RAW host disk access VMDK file /disk/VM System/Raw Disks/Windows Data.vmdk created successfully. 

}}}

Whilst the VMDK is created it does not map the logical partition correctly. When seen from within the Windows 7 guest, the 175GB logical partition shows up as free space."	Feline
15793	Unable to change order of inaccessible VMs in list	all	VirtualBox 5.1.2	2016-08-14T19:35:57Z	2016-08-15T05:43:56Z	2016-08-15T05:43:56Z	"Lubuntu 16.04 x86-64 host.

The VirtualBox Manager GUI shows a list of available VMs on the left side. You can drag-and-drop VMs to change the order of the list.

However VMs which are shown as Inaccessible can't be moved.

Also, with an inaccessible VM at the top of the list, I couldn't manage to drag another (accessible) VM above it."	Donuts
17974	Unable to burn Audio CD	Windows	VirtualBox 5.2.18	2018-09-09T15:04:04Z	2018-09-09T15:04:04Z	2018-09-09T15:04:04Z	"Hello,

I am running Ubuntu Linux 18.04 LTS with all the latest patches installed.

Linux xxxxxxx 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 16:00:05 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

I installed Virtualbox/Extension Pack/Guest Additions from virtualbox.org; version 5.2.18 r124319 (Qt5 9.5)

My machine has a DVD/RW drive that is connected to the Windows 7 guest via Passthrough.

I am able to burn data discs, but cannot burn audio discs. I checked the Virtualbo releases, and as of version 4.2 the changelog says that audio cd burning is supported.

How can I get this working correctly?

I have attached a log file from right after burning an audio cd fails.

I purchased a Virtualbox Enterprise license on CDW so that this ticket may receive priority attention since I am a paying customer. Please feel free to call me via the information on my account if you need any confirmation of the CDW purchase.

Thank you in advance."	SloanUser
16423	Unable to boot after converting .vmdk to .vdi	Linux	VirtualBox 5.1.12	2017-01-24T19:17:48Z	2017-01-26T23:06:27Z	2017-01-26T23:06:27Z	"Host: Arch Linux x86_64 with 4.8.13-1-ARCH

After converting a 50GB vmdk file to vdi using the command below, I wasn't able to boot the virtual machine with the newly created vdi file because of a ""fatal error: no bootable medium found"" 

{{{
VBoxManage clonemedium --format VDI actual.vmdk new.vdi
}}}

The conversion went well though. You will find my ''actual.vmdk'' file attached to this post, alongside 2MB of my ''actual-flat.vmdk'', as requested by an IRC user on #vbox."	closingin
21022	unable paste screenshot to windows guest	Windows	VirtualBox 6.1.32	2022-07-15T16:47:40Z	2022-07-18T08:50:47Z	2022-07-18T08:50:47Z	"host: ubuntu22.04
guest: windows10

unable to paste screenshot to windows, which is all good on ubuntu21.10 host and windows10 guest, I tried all the solutions I can find in google, 
still not working

sometimes, can't paste plain text too"	walkerjun
19950	UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated: 0x0 1920x1173	Linux	VirtualBox 6.1.14	2020-10-09T14:43:52Z	2020-11-05T16:34:20Z	2020-11-05T16:34:20Z	"Recently I migrated my multi-boot system from an i7-6700 to a Ryzen 9 3900XT.[[BR]]
Since then when VB is started under Slackware Current64 all VM's fail to start, whereas when VB is started under Xubuntu 20.04.1 these VM's start as expected.[[BR]]
The failure occurs very early in the start sequence: the big ""starting arrow"" remains shown and the system freezes all over. A hard restart is required.[[BR]]

From the VBox.log's it seems that the Slackware problem is:

{{{
GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated:[[BR]]
 Screen 0 work area is actually resized to: 0x0 x 1920x1173
}}}


whereas the Xubuntu VBox.log reads:


{{{
GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated:[[BR]]
 Screen 0 work area is actually resized to: 0x25 x 1920x1150
}}}


Note the ""0x0"" versus ""0x25"".[[BR]]

As via symlinks the VB settings and VM definitions are shared between the sundry Linux instances an error like a ""leftover"" file definition is highly unlikely.[[BR]]

Some other differences beween the VBox.logs are:[[BR]]
-- Xubuntu kernel 5.4.0-48-generic, Slackware 5.8.14-burdi64;[[BR]]
-- Xubuntu VB QT version 5.12.6, Slackware 5.6.1;[[BR]]
-- Xubuntu X release 12008000, Slackware 12009000;[[BR]]
-- Xubuntu loads a VMMR0.so, Slackware does not.[[BR]]

I started out with VB 6.1.14-140239. For Slackware I then tested VB testbuild 6.1.15-6.1.15-140809 asis with kernel 5.8.14-burdi64 and the same testbuild but patched (see #19845) with kernel 5.9.0-rc8-burdi64.[[BR]]
However the problem persists ...


 "	burdi01
19489	UI garbled when run through SSH	other	VirtualBox 6.1.4	2020-04-14T18:01:53Z	2020-04-14T18:01:53Z	2020-04-14T18:01:53Z	"When using SSH to log into a machine to run VirtualBox, the UI is garbled. Version 6.0.18 works correctly. To duplicate, run 'ssh -X localhost', log in, and run VirtualBox.

Attached are screen shots. "	Larry998
17149	UI breaks as soon as a VM is created or added built with QT 5.9.2	all	VirtualBox 5.1.28	2017-10-09T17:40:54Z	2017-10-11T17:03:30Z	2017-10-11T17:03:30Z	"UI starts fine prior to addition or creation of any VM. As some as a VM is created or added, the UI crashes and continues to crash until configuration is deleted.

Qt FATAL: ASSERT failure in QCoreApplication::sendEvent: ""Cannot send events to objects owned by a different thread. Current thread 0x0x26cba40. Receiver '' (of type 'UITaskMediumEnumeration') was created in thread 0x0x22e65d0"", file kernel/qcoreapplication.cpp, line 563

Thread 18 ""UIThreadWorker"" received signal SIGABRT, Aborted.
[Switching to Thread 0x7f056bfff700 (LWP 19353)]
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
51      ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1  0x00007f05a1ed9930 in __GI_abort () at abort.c:89
#2  0x00007f059c86f657 in QMessageLogger::fatal(char const*, ...) const () from /usr/lib64/libQt5Core.so.5
#3  0x00007f059c86a4ea in qt_assert_x(char const*, char const*, char const*, int) () from /usr/lib64/libQt5Core.so.5
#4  0x00007f059ca41686 in QCoreApplicationPrivate::checkReceiverThread(QObject*) () from /usr/lib64/libQt5Core.so.5
#5  0x00007f0597aad848 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5
#6  0x00007f059ca41d07 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5
#7  0x00007f059ca77f2c in QObject::setProperty(char const*, QVariant const&) () from /usr/lib64/libQt5Core.so.5
#8  0x00007f059df826d0 in UITaskMediumEnumeration::run (this=0x24b7170)
    at /var/tmp/portage/app-emulation/virtualbox-5.1.28/work/VirtualBox-5.1.28/src/VBox/Frontends/VirtualBox/src/medium/UIMediumEnumerator.cpp:65
#9  0x00007f059df5adca in UITask::start (this=0x24b7170)
    at /var/tmp/portage/app-emulation/virtualbox-5.1.28/work/VirtualBox-5.1.28/src/VBox/Frontends/VirtualBox/src/globals/UIThreadPool.cpp:298
#10 UIThreadWorker::run (this=0x26cba40)
    at /var/tmp/portage/app-emulation/virtualbox-5.1.28/work/VirtualBox-5.1.28/src/VBox/Frontends/VirtualBox/src/globals/UIThreadPool.cpp:322
#11 0x00007f059c8843d0 in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5
#12 0x00007f05a245e867 in start_thread (arg=0x7f056bfff700) at pthread_create.c:456
#13 0x00007f05a1f9c9cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97
"	ekigwana
19351	Ubunutu 18.04 kernel 5.4.0 suplibOsInit VERR_VM_DRIVER_NOT_INSTALLED ENOENT	Linux	VirtualBox 6.1.4	2020-02-26T21:18:23Z	2020-02-26T21:29:56Z	2020-02-26T21:29:56Z	"Failure to start vm, error seems to be independend on the image
Bug is reproducible with 
'''host info'''
❯ uname --a  
Linux incbook 5.4.0-050400rc7-generic #201911102031 SMP Mon Nov 11 01:34:23 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

''secure boot disabled''

'''virtalbox install'''
https://www.virtualbox.org/wiki/Linux_Downloads
version for bionic, 
VirtualBox Graphical User Interface
Version 6.1.4 r136177 (Qt5.9.5)

'''image independent'''
reproducible with latest dsl image from https://sourceforge.net/projects/virtualboximage/files/Damn Small/4.4.10/dsl-4.4.10-x86.7z/download?use_mirror=netcologne

'''Error message'''

Failed to open a session for the virtual machine dsl-4.4.10-x86.

The virtual machine 'dsl-4.4.10-x86' has terminated unexpectedly during startup with exit code 1 (0x1).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}



Kernel driver not installed (rc=-1908)

The VirtualBox Linux kernel driver is either not loaded or not set up correctly. Please try setting it up again by executing

'/sbin/vboxconfig'

as root.

If your system has EFI Secure Boot enabled you may also need to sign the kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load them. Please see your Linux system's documentation for more information.

where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT. 

'''attempts to fix/reinstall don't help'''

❯ sudo /sbin/vboxconfig          
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: failed: Look at /var/log/vbox-setup.log to find out what went wrong.

There were problems setting up VirtualBox.  To re-start the set-up process, run
  /sbin/vboxconfig
as root.  If your system is using EFI Secure Boot you may need to sign the
kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load
them. Please see your Linux system's documentation for more information.

"	rtychko
19104	Ubuntu18.04 NS_ERROR_FAILURE	other	VirtualBox 6.0.14	2019-11-22T07:39:07Z	2021-05-08T02:10:10Z	2021-05-08T02:10:10Z	"Failed to open a session for the virtual machine ss.

The virtual machine 'ss' has terminated unexpectedly during startup because of signal 6.

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {5047460a-265d-4538-b23e-ddba5fb84976}

"	wendaotao
18812	Ubuntu virtual machine fails to start	Linux	VirtualBox 6.0.10	2019-08-05T05:11:06Z	2019-08-05T05:11:06Z	2019-08-05T05:11:06Z		bobocc
11104	Ubuntu Quantal package: migrate from libpython2.7 to libpython3	other	VirtualBox 4.2.2	2012-10-22T12:38:53Z	2012-10-26T09:39:46Z	2012-10-26T09:39:46Z	"Ubuntu 12.10 Quantal comes with Python 3 as default: https://wiki.ubuntu.com/Python/3

The 4.2.2-81494~Ubuntu~quantal package still depends on libpython2.7. Please consider switching to libpython3.2 or libpython3.3."	ilf
15772	Ubuntu Mini ToolBar causes problems	Windows	VirtualBox 5.1.2	2016-08-09T15:48:58Z	2016-09-09T14:30:41Z	2016-09-09T14:30:41Z	"I observed this issue for a while now but it got worse either with the latest VirtualBox updates or with upgrading from Ubuntu 14.04 to 16.04.

When the Mini ToolBar is activated for a VM there are two overlays being created by VirtualBox (each for every display see screenshot). These overlays seem to cause some problems:

sometimes they menus render on the wrong place on the display (only happens if menu is at the bottom)

sometimes unity (ubuntu's launcher) consumes clicks from the VM

since VirtualBox 5.1. when I switch Ubuntu workspace it instantly switches back to the workspace where the VM is running which is a show stopper for me

my workaround at the moment is to switch of the Mini ToolBar"	ÄxxlForce
20450	Ubuntu Linux host hissing audio after starting ubuntu server guest.	Linux	VirtualBox 6.1.22	2021-07-07T00:08:14Z	2021-07-07T00:08:14Z	2021-07-07T00:08:14Z	"Host - Ubuntu Desktop Linux 20.04.2 LTS amd64 
Guest - 20.04.02 Server Linux amd64

To stop the interference in the host machine's audio it is necessary to disable the audio in the guest (virtual machine).

Interferences were observed in Google Chrome and Mozilla Firefox browsers.


[[Image(https://i.stack.imgur.com/geK0R.png)]]"	Carlos Henrique
20449	Ubuntu Linux host hissing audio after starting ubuntu server guest.	Linux	VirtualBox 6.1.22	2021-07-07T00:07:42Z	2021-07-07T00:07:42Z	2021-07-07T00:07:42Z	"Host - Ubuntu Desktop Linux 20.04.2 LTS amd64 
Guest - 20.04.02 Server Linux amd64

To stop the interference in the host machine's audio it is necessary to disable the audio in the guest (virtual machine).

Interferences were observed in Google Chrome and Mozilla Firefox browsers.


[[Image(https://i.stack.imgur.com/geK0R.png)]]"	Carlos Henrique
18650	Ubuntu Issues	Linux	VirtualBox 6.0.8	2019-05-15T22:45:57Z	2019-05-23T08:21:01Z	2019-05-23T08:21:01Z	"Good Evening,

I just wanted to raise an issue I have with Ubuntu on VirtualBox. I have tried increasing the memory, changing from dynamic to fixed memory, changing CPUs as well as changing various advanced settings.

I tried on a different laptop and it worked fine with 18.04, I exported the appliance and importing it onto this laptop failed. The only difference is that Hyper-V is not installed on the other laptop though it is on this. I saw there may be an issue with Hyper-V but I use both VirtualBox and Hyper-V.

I'd just like to raise this as a defect, and also this has been an issue on the current version and the base 6.0.0"	MitchB
17467	Ubuntu host does not start after 5.2.6 GUest Additions installed	Linux	VirtualBox 5.2.6	2018-01-17T15:22:13Z	2018-01-18T21:46:15Z	2018-01-18T21:46:15Z	I upgraded VirtualBox to 5.2.6 on my Ubuntu 16.04 host and also installed Guest Additons 5.2.6 on Ubuntu 16.04 guest. Then I powered off guest. Now, when starting guest it just does not start. I can see Ubuntu starts running but then it gets stuck somewhere...	SamH
17479	Ubuntu host does not start after 5.1.32 Guest Additions installed	Linux	VirtualBox 5.1.32	2018-01-18T16:46:36Z	2018-02-28T15:03:15Z	2018-02-28T15:03:15Z	"The issue is the same as in https://www.virtualbox.org/ticket/17467 in 5.1.32: Ubuntu starts, but then stops at some moment after upgrading VirtualBox from 5.1.30 in 16.04 host to 5.1.32 and the guest additions to 5.1.32. The guest OS is 16.04 as well.
The only way to load the system is to uncheck the option ""Enable 3D Acceleration"".
All features (with unchecked ""Enable 3D Acceleration"") work: buffer, sharing folders etc.
There was a recent update of mesa library from 17.2.2 to 17.2.4 at the same time of 5.1.30->5.1.32, can they be related?"	ar123
14113	Ubuntu guest loses keyboard sporadically	Linux	VirtualBox 4.3.28	2015-05-13T21:23:30Z	2015-12-01T02:14:40Z	2015-12-01T02:14:40Z	"Host: ubuntu 14.04
Guest: ubuntu 12.04

Sporadically guest loses keyboard, xev doesn't show keyboard events, etc. The only way to fix this issue is to restart guest. Save/reload doesn't help.

I'm using the Microsoft Remote Desktop (Win7) as client. If I close it and reconnect to the guest the keyboard still doesn't work."	DO
19574	Ubuntu 20.04 LTS, VM ICONS INVISIBLE	all	VirtualBox 6.1.6	2020-05-09T03:21:11Z	2020-05-30T09:20:52Z	2020-05-30T09:20:52Z	I am using a Linux Ubuntu 20.04 LTS host, and when I start a VM, the icon is invisible in the ubuntu dock, the only way to make it visible is by moving the program to another workspace, or locking and unlocking the host.	saikotwolf
20515	Ubuntu 20.04 host hangs if I copy/paste clipboard to Win10 guest	Windows	VirtualBox 6.1.26	2021-08-20T09:50:46Z	2021-10-20T17:55:02Z	2021-10-20T17:55:02Z	"I have a host with Ubuntu 20.04 and standard Gnome (I did not change anything as to  the UI)  and Windows 10 as guest. 

Shared clipboard is set to ""bidirectional"".  

At the beginning everything work fine, but after 10-20 clipboard copy/paste operations, everything starts to hang: I can't click anywhere, first guest OS freezes (so that I can't even restart it), then in a minute or two host OS freezes and becomes non-responsive. This reproduces many times.  

If I switch off the clipboard exchange - everything will be OK for many days long, but as soon as I switch it on - I get that problems. 

Guest additions in the guest VM are aligned with the host - the same version.

At the end of the log I have this - maybe it will help. 
Also I am ready to provide any help for VirtualBox engineers - feel free to contact me to ibobak at gmail dot com and send any custom VirtualBox binaries with additional logging, whatever. 


19:13:53.112366 ************** End of Guest state at power off ***************
19:13:53.204746 PDMR3PowerOff: 92 351 469 ns run time
19:13:53.204759 Changing the VM state from 'POWERING_OFF' to 'OFF'
19:13:53.205148 Console: Machine state changed to 'Stopping'
19:13:53.205558 Console::powerDown(): A request to power off the VM has been issued (mMachineState=Stopping, InUninit=0)
19:14:08.186578 Shared Clipboard: Converting VBox formats 0x1 to 'STRING' for X11 (idxFmtX11=4, fmtX11=2) failed, rc=VERR_TIMEOUT
19:14:38.186794 Shared Clipboard: Converting VBox formats 0x1 to 'STRING' for X11 (idxFmtX11=4, fmtX11=2) failed, rc=VERR_TIMEOUT
19:15:08.187232 Shared Clipboard: Converting VBox formats 0x1 to 'UTF8_STRING' for X11 (idxFmtX11=1, fmtX11=3) failed, rc=VERR_TIMEOUT
19:15:38.187862 Shared Clipboard: Converting VBox formats 0x1 to 'text/plain;charset=utf-8' for X11 (idxFmtX11=3, fmtX11=3) failed, rc=VERR_TIMEOUT
19:16:08.188045 Shared Clipboard: Converting VBox formats 0x1 to 'text/plain;charset=utf-8' for X11 (idxFmtX11=3, fmtX11=3) failed, rc=VERR_TIMEOUT
19:16:38.188318 Shared Clipboard: Converting VBox formats 0x1 to 'STRING' for X11 (idxFmtX11=4, fmtX11=2) failed, rc=VERR_TIMEOUT
19:17:08.188778 Shared Clipboard: Converting VBox formats 0x1 to 'UTF8_STRING' for X11 (idxFmtX11=1, fmtX11=3) failed, rc=VERR_TIMEOUT
19:17:38.189030 Shared Clipboard: Converting VBox formats 0x1 to 'UTF8_STRING' for X11 (idxFmtX11=1, fmtX11=3) failed, rc=VERR_TIMEOUT
19:17:38.189275 Shared Clipboard: Converting VBox formats 0x1 to 'INVALID' for X11 (idxFmtX11=0, fmtX11=0) failed, rc=VERR_NOT_SUPPORTED
19:17:38.189315 Shared Clipboard: Converting VBox formats 0x1 to 'INVALID' for X11 (idxFmtX11=0, fmtX11=0) failed, rc=VERR_NOT_SUPPORTED



"	Ihor_Bobak
17425	Ubuntu 18.04 xcb not found... but found.	all	VirtualBox 5.2.4	2018-01-06T15:38:01Z	2018-11-09T00:01:34Z	2018-11-09T00:01:34Z	"Attempting to start virtualbox produces the following error:

------------------------------
08:56:19 evil@sager ~» virtualbox
Qt FATAL: This application failed to start because it could not find or load the Qt platform plugin ""xcb""
in """".

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.

Reinstalling the application may fix this problem.
Aborted (core dumped)
----------------------------------

Oddly the message lists xcb as an available plugin.

Attempting to run VirtualBox as root, and to force the library path (P=/usr/lib/virtualbox; sudo LD_LIBRARY_PATH=$P:$P/plugins/platforms $P/VirtualBox) produces the same error as seen above.

Running ldd, there appear to be no missing dependencies for any of the virtualbox libraries or libqxc

----------------------------------
09:06:47 evil@sager ~» ldd /usr/lib/virtualbox/*.so | grep not
09:06:50 evil@sager ~» 

09:25:32 evil@sager ~» ldd /usr/lib/virtualbox/components/*.so | grep not
09:26:17 evil@sager ~»

09:04:44 evil@sager ~» ldd /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so | grep not
09:05:44 evil@sager ~» 
----------------------------------

Only the extension pack VNC files, which I wouldn't think would be necessary to start the GUI show anything not found:

----------------------------------
09:29:23 evil@sager ~» ldd /usr/lib/virtualbox/ExtensionPacks/VNC/linux.amd64/*.so | grep not
        VBoxRT.so => not found
        VBoxRT.so => not found
09:29:40 evil@sager ~»
----------------------------------

What I've tried:

1.  apt uninstalling (with --purge) virtualbox* and re-installing.  Same results.

2.  apt uninstalling (with --purge) virtualbox* and backleveling to v5.1.  Same results.

3.  apt uninstalling (with --purge) virtualbox* and re-installing using the latest deb downloaded from your site rather than the artful repo.  Same results.

4. sudo ln -s /usr/lib/x86_64-linux-gnu/qt5/plugins /usr/lib/virtualbox/plugins  (same results)

5. sudo ln -s /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms /usr/lib/virtualbox/platforms  (same results)

6. sudo ln -s /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so /usr/lib/virtualbox/libqxcb.so  (same results)

7. Re-installed _all_ of the Qt5 libraries and rebooting.  Same results.

8. Running a trace (I will attach it to the ticket).  Line 1313 is where it loads libqxcb.so.


I'm not having any issues with any other Qt5 applications on this system - and even use it to develop Qt5 apps.  Any help figuring this out would be appreciated."	3vi1J
19570	Ubuntu 18.04 guest crashes regularly	Linux	VirtualBox 6.1.6	2020-05-07T12:48:44Z	2020-05-29T14:58:22Z	2020-05-29T14:58:22Z	"Guest: Ubuntu 18.04
Host: Ubuntu 18.04

This guest is actively (7 days a week) used since VirtualBox 5.x, no crashes were observed. After upgrading VirtualBox to 6.1.6 guest gets terminated with 'Aborted' state at least once a week, usually during text editing."	Andriy
16118	Ubuntu 16.04.1 crash of UI	other	VirtualBox 5.1.8	2016-10-26T14:45:16Z	2017-09-14T04:10:20Z	2017-09-14T04:10:20Z	"Trying to troubleshoot a crash with 5.1.8 r111374 (Qt 5.5.1) on my colleague's system.

He can create virtual machines and generally click all items in the menus. The moment he comes to File > Preferences the application crashes. It's not 100%, but close to.

I already tried with an empty .config/VirtualBox, didn't matter. I am positive it is a small thing, as I have an (near) identical setup with no problems.

Attached the core dump. Attached VBoxSVC.log.

dpkg --list output wrt Qt 5 libs:

|| libqt5core5a:amd64        || 5.5.1+dfsg-16ubuntu7.1 ||
|| libqt5dbus5:amd64         || 5.5.1+dfsg-16ubuntu7.1 ||
|| libqt5feedback5:amd64     || 5.0~git20130529-0ubuntu13 ||
|| libqt5gui5:amd64          || 5.5.1+dfsg-16ubuntu7.1 ||
|| libqt5multimedia5:amd64   || 5.5.1-4ubuntu2 ||
|| libqt5network5:amd64      || 5.5.1+dfsg-16ubuntu7.1 ||
|| libqt5opengl5:amd64       || 5.5.1+dfsg-16ubuntu7.1 ||
|| libqt5organizer5:amd64    || 5.0~git20140515~29475884-0ubuntu20 ||
|| libqt5positioning5:amd64  || 5.5.1-3ubuntu1 ||
|| libqt5printsupport5:amd64 || 5.5.1+dfsg-16ubuntu7.1 ||
|| libqt5qml5:amd64          || 5.5.1-2ubuntu6 ||
|| libqt5quick5:amd64        || 5.5.1-2ubuntu6 ||
|| libqt5quicktest5:amd64    || 5.5.1-2ubuntu6 ||
|| libqt5sql5:amd64          || 5.5.1+dfsg-16ubuntu7.1 ||
|| libqt5sql5-sqlite:amd64   || 5.5.1+dfsg-16ubuntu7.1 ||
|| libqt5svg5:amd64          || 5.5.1-2build1 ||
|| libqt5test5:amd64         || 5.5.1+dfsg-16ubuntu7.1 ||
|| libqt5webkit5:amd64       || 5.5.1+dfsg-2ubuntu1 ||
|| libqt5widgets5:amd64      || 5.5.1+dfsg-16ubuntu7.1 ||
|| libqt5x11extras5:amd64    || 5.5.1-3build1 ||
|| libqt5xml5:amd64          || 5.5.1+dfsg-16ubuntu7.1 ||
"	asmodai
17707	Ubuntu 16.04 guest fails to start after upgrade to VirtualBox 5.2.10	Linux	VirtualBox 5.2.10	2018-04-23T08:19:03Z	2018-04-23T15:25:29Z	2018-04-23T15:25:29Z	"Ubuntu 16.04 guest fails to start after upgrade to VirtualBox 5.2.10. Please see he video capture: https://drive.google.com/open?id=1aZfyoduWR4IvysM6UQdDePNEVMWjQEHE

One more detail: I was able to start the guest after upgrade to VirtualBox 5.2.10 . I installed guest additions. And the thing is not working any more... Same as last time. Something is broken with guest additions.

I tried to disable 3D acceleration. It does not help..."	SamH
14538	Ubuntu 15.04 Desktop - vboxautostart does not work on boot (no output)	other	VirtualBox 5.0.2	2015-09-03T16:05:51Z	2016-04-29T22:55:16Z	2016-04-29T22:55:16Z	"Hello,

While trying to get vboxautostart working on Ubuntu (GNOME) Desktop 15.04, I've encountered a problem where vboxautostart does not function correctly on boot. It does nothing upon system boot, however restarting it manually ""systemctl restart vboxautostart-service"" after logging in makes it start VMs correctly.

Since the default init.d file provided does not log anything to journald(syslog), I've had to modify it to remove the ""--background"" flags.

After doing that, this is what I get:

On system boot:
{{{
Sep 03 23:56:01 workstation1 systemd[1]: Starting LSB: VirtualBox autostart service...
Sep 03 23:56:01 workstation1 vboxautostart-service[1154]: Starting VirtualBox VMs configured for autostartOracle VM Vir
Sep 03 23:56:01 workstation1 vboxautostart-service[1154]: (C) 2015 Oracle Corporation
Sep 03 23:56:01 workstation1 vboxautostart-service[1154]: All rights reserved.
Sep 03 23:56:01 workstation1 systemd[1]: Started LSB: VirtualBox autostart service.
}}}

If I restart the service manually after logging in:
{{{
Sep 03 23:56:57 workstation1 systemd[1]: Starting LSB: VirtualBox autostart service...
Sep 03 23:56:57 workstation1 vboxautostart-service[3633]: Starting VirtualBox VMs configured for autostartOracle VM Vir
Sep 03 23:56:57 workstation1 vboxautostart-service[3633]: (C) 2015 Oracle Corporation
Sep 03 23:56:57 workstation1 vboxautostart-service[3633]: All rights reserved.
Sep 03 23:56:57 workstation1 vboxautostart-service[3633]: VirtualBox Autostart 5.0.2 r102096 linux.amd64 (Aug 13 2015 1
Sep 03 23:56:57 workstation1 vboxautostart-service[3633]: 00:00:00.000347 main     Log opened 2015-09-03T...
Sep 03 23:56:57 workstation1 vboxautostart-service[3633]: 00:00:00.000348 main     Build Type: release
Sep 03 23:56:57 workstation1 vboxautostart-service[3633]: 00:00:00.000349 main     OS Product: Linux
Sep 03 23:56:57 workstation1 vboxautostart-service[3633]: 00:00:00.000350 main     OS Release: 3.19.0-26-generic
Sep 03 23:56:57 workstation1 vboxautostart-service[3633]: 00:00:00.000350 main     OS Version: #28-Ubuntu SMP Tue Aug 11 14:16:32 UTC 2015
Sep 03 23:56:57 workstation1 vboxautostart-service[3633]: 00:00:00.000363 main     DMI Product Name: All Series
Sep 03 23:56:57 workstation1 vboxautostart-service[3633]: 00:00:00.000366 main     DMI Product Version: System Version
Sep 03 23:56:57 workstation1 vboxautostart-service[3633]: 00:00:00.000416 main     Host RAM: 15957MB total, 14919MB available
Sep 03 23:56:57 workstation1 vboxautostart-service[3633]: 00:00:00.000417 main     Executable: /usr/lib/virtualbox/VBoxAutostart
Sep 03 23:56:57 workstation1 vboxautostart-service[3633]: 00:00:00.000418 main     Process ID: 3640
Sep 03 23:56:57 workstation1 vboxautostart-service[3633]: 00:00:00.000418 main     Package type: LINUX_64BITS_UBUNTU_14_04
Sep 03 23:56:57 workstation1 vboxautostart-service[3633]: 00:00:00.000426 main     Setting up ...
Sep 03 23:56:57 workstation1 vboxautostart-service[3633]: 00:00:00.004796 main     Waiting for VM ""..."" to power on...
Sep 03 23:56:57 workstation1 vboxautostart-service[3633]: 00:00:00.189850 main     VM ""..."" has been successfully started.
Sep 03 23:56:57 workstation1 vboxautostart-service[3633]: 00:00:00.190933 main     Waiting for VM ""..."" to power on...
Sep 03 23:56:57 workstation1 vboxautostart-service[3633]: 00:00:00.336516 main     VM ""..."" has been successfully started.
Sep 03 23:56:57 workstation1 vboxautostart-service[3633]: 00:00:00.336995 main     Shutting down ...
Sep 03 23:56:57 workstation1 systemd[1]: Started LSB: VirtualBox autostart service.
}}}

As you can see, the VBoxAutoStart executable outputs and does nothing during the boot sequence, however restarting the service manually works as expected.

Has anyone else encountered the problem and how would I be able to further debug this issue?"	Michael Yoo
14251	Ubuntu 14.04 guest additions breaks touchscreen cursor	Linux	VirtualBox 4.3.28	2015-07-09T08:19:47Z	2015-10-05T07:30:04Z	2015-10-05T07:30:04Z	"Hardware: Microsoft surface Pro 3
VirtualBox 4.3.28 
Guest Additions Installed
Host : Ubuntu 14.04
Guest : Ubuntu 14.04

Hello,

After installation of the Guest Additions on the Linux guest, the Touchscreen does not work properly in Guest OS (Ubuntu 14.04).
The mouse works fine I get the cursor but I cannot control the cursor position with Touchscreen, I have already tried to calibrate the Touchscreen (xinput, calibrate Touchscreen…) but it seems like having no effects.

For information, Without the guest addition there is no problem of cursor position, I get the good positions of the Touchscreen cursor but the click doesn’t work, and with the Guest additions installed I lost the positions of the Touchscreen cursor but the click still works.

Can someone help with this issue ?
"	drdr_skilled
15977	Ubuntu 14.04 crash when open windows 7 guest machine	Windows	VirtualBox 5.1.6	2016-09-23T09:05:36Z	2016-09-23T09:05:36Z	2016-09-23T09:05:36Z	"Hi everybody,
my ubuntu 14.04.1 with kernel 4.4.0-38-generic #57 crash when i try to open a windows 7 guest machine. i just installed gcc ver. 5.4.1 20160904
watch in other forum... but the problem persist.
New guest addition installed.

Guest machine was installed with VBox 4.xx, and ubuntu kernel 3.16.xx.

When host crash i can only move the mouse on desktop.
Ubuntu 14.04.1 with KDE  4.13.2

What do i do to resolve?

Sorry for my easy English."	zipp0
16067	typing OS name in vbox GUI in russian layout - just garbage	all	VirtualBox 5.1.6	2016-10-13T17:28:16Z	2016-10-13T17:28:16Z	2016-10-13T17:28:16Z	"VirtualBox 5.1.x - all versions
Host type: Debian Linux with LXDE desktop
When I create VM or change its name in VBox GUI using Russian keyboard layout I get strange garbage and I can't delete this symbols.

But I have no problems with VirtualBox 5.0.x and VirtualBox 4.x GUI"	amiasnikov
19488	Trying to start a new instance of Ubuntu Server	Linux	VirtualBox 6.1.4	2020-04-14T15:58:38Z	2020-04-14T16:31:10Z	2020-04-14T16:31:10Z	"00:00:34.744960 GIM: KVM: Resetting MSRs
00:00:34.748351 Changing the VM state from 'DESTROYING' to 'TERMINATED'
00:00:34.756082 Console: Machine state changed to 'PoweredOff'
00:00:35.281071 GUI: Passing request to close Runtime UI from machine-logic to UI session.
00:00:35.757520 GUI: UIMachineViewNormal::resendSizeHint: Restoring guest size-hint for screen 0 to 800x600
00:00:35.757592 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={4680b2de-8690-11e9-b83d-5719e53cf1de} aComponent={DisplayWrap} aText={The console is not powered up}, preserve=false aResultDetail=0
00:00:35.757701 GUI: Aborting startup due to invalid machine state detected: 1"	larka06
16143	Trouble attaching Intel HD 530 from linux host to win7 guest via PCI passthrough.	Windows	VirtualBox 5.1.8	2016-11-03T16:36:20Z	2016-11-03T16:36:20Z	2016-11-03T16:36:20Z	I have an intel 6600k with HD 530 graphics. z170 chipset.  I have a GTX 1070 running my arch linux host displays.  I would like to use PCI passthrough to attach the intel graphics to the win7 guest.  So I ran the modifyvm --pciattach command with no errors and booted up the guest.  Windows detected the new hardware and downloaded and installed the HD 530 driver.  In device manager, it says the device could not start because there are not enough resources. So I tried disabling the virtualbox display adapter and rebooting.  However when I rebooted, it hard locked my host.  I could not even use the magic sysrq shortcuts to reboot.  I tried two more times shutting down and rebooting the guest, but it hard locks the host every time. I wanted to do further testing to try to get the guest to enable and use the HD 530 card, but I don't want to risk losing data from the hard lockups, so I have stopped testing and detached the device.	walmartshopper12
14149	Trivial macro bug in SDK in bindings/c/include/VBoxCAPI_v4_3.h	all	VirtualBox 4.3.28	2015-05-25T07:22:41Z	2015-05-29T15:56:53Z	2015-05-29T15:56:53Z	"The definition for the IVirtualBox_CreateMachine macro is missing the GroupSize parameter. It needs to have the parameter added, and then needs to forward it to CreateMachine.

Without this change, code that uses the macro won't compile.

Here's a diff, in case it helps.

{{{
diff a/bindings/c/include/VBoxCAPI_v4_3.h b/bindings/c/include/VBoxCAPI_v4_3.h
--- a/third_party/VirtualBoxSDK/sdk/bindings/c/include/VBoxCAPI_v4_3.h
+++ b/third_party/VirtualBoxSDK/sdk/bindings/c/include/VBoxCAPI_v4_3.h
@@ -4266,7 +4266,7 @@ struct IVirtualBoxVtbl
 #define IVirtualBox_get_GenericNetworkDrivers(p, aGenericNetworkDrivers) ((p)->lpVtbl->GetGenericNetworkDrivers(p, aGenericNetworkDrivers))
 #define IVirtualBox_GetGenericNetworkDrivers(p, aGenericNetworkDrivers) ((p)->lpVtbl->GetGenericNetworkDrivers(p, aGenericNetworkDrivers))
 #define IVirtualBox_ComposeMachineFilename(p, aName, aGroup, aCreateFlags, aBaseFolder, aFile) ((p)->lpVtbl->ComposeMachineFilename(p, aName, aGroup, aCreateFlags, aBaseFolder, aFile))
-#define IVirtualBox_CreateMachine(p, aSettingsFile, aName, aGroups, aOsTypeId, aFlags, aMachine) ((p)->lpVtbl->CreateMachine(p, aSettingsFile, aName, aGroups, aOsTypeId, aFlags, aMachine))
+#define IVirtualBox_CreateMachine(p, aSettingsFile, aName, aGroupSize, aGroups, aOsTypeId, aFlags, aMachine) ((p)->lpVtbl->CreateMachine(p, aSettingsFile, aName, aGroupSize, aGroups, aOsTypeId, aFlags, aMachine))
 #define IVirtualBox_OpenMachine(p, aSettingsFile, aMachine) ((p)->lpVtbl->OpenMachine(p, aSettingsFile, aMachine))
 #define IVirtualBox_RegisterMachine(p, aMachine) ((p)->lpVtbl->RegisterMachine(p, aMachine))
 #define IVirtualBox_FindMachine(p, aNameOrId, aMachine) ((p)->lpVtbl->FindMachine(p, aNameOrId, aMachine))
}}}"	pwnall
20078	Trend FDE Post Login Fault	other	VirtualBox 6.1.16	2020-12-04T16:23:04Z	2020-12-04T16:23:04Z	2020-12-04T16:23:04Z	"I used to be about to create a Windows 10 Pro x64 VM, install Trend Full Disk Encryption however in recent versions of vbox 6.1.14 and 6.1.16 the virtual box runs into a critical error just after I login to the Trend FDE preboot screen.

Attached are all the logs that are generated by vBox."	cg-sis
19454	Transfer of large files from guest to host causes hang	Windows	VirtualBox 6.1.4	2020-04-01T18:48:28Z	2020-04-01T18:48:28Z	2020-04-01T18:48:28Z	"Host: Windows 10, Guest: Debian
Mount shared folder on from host.
Write large (>10GB) file.
Processes on guest will begin to hang.
Attempt to reboot may hang as well."	eng3
21296	TPM not working without UEFI/SecureBoot	Windows	VirtualBox-7.0.4	2022-11-23T10:07:41Z	2022-11-23T10:07:41Z	2022-11-23T10:07:41Z	When TPM is enabled, Windows cannot start it if not starting from UEFI/SecureBoot, there should be a warning when enabling it to prevent this invalid configuration	DidiKo
17619	tools (guest additions) and drivers don't build on SL7	Windows	VirtualBox 5.2.8	2018-03-13T05:30:03Z	2018-03-16T02:04:08Z	2018-03-16T02:04:08Z	"Hi,
With updated kernel in SL7 (and I assume CentOS7 and RHEL7) 3.10.0-693.21.1.el7.x86_64 drivers (and tools on linux guest) no longer compile.
Looks like it is due to REPTOLINE kernel changes.

make V=1 CONFIG_MODULE_SIG= -C /lib/modules/3.10.0-693.21.1.el7.x86_64/build SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 -j12 modules
arch/x86/Makefile:166: *** CONFIG_RETPOLINE=y, but not supported by the compiler. Toolchain update recommended.. Stop.
make: *** [vboxdrv] Error 2

I can reboot in previous kernel as a workaround.

Thanks,

GZU"	GZU
18200	tinytext in UI elements when on different screens	all	VirtualBox 6.0.0	2018-12-18T23:08:55Z	2020-02-06T10:07:21Z	2020-02-06T10:07:21Z	"I'm on a three monitor setup, one 1920x1080, and two 1900x1200. Gnome on Oracle Linux 7.5. 


When Moving the Virtualbox Manager to the (slightly) higher resolution screen, the font size shrinks drastically.

In addition, the menubar elements attached to guest machines ('File Machine View Input...') also become extremely small.
"	ronabop
20826	tinycore 1.4 crashes VirtualBox	Linux	VirtualBox 6.1.32	2022-02-13T12:05:01Z	2022-10-21T12:52:40Z	2022-10-21T12:52:40Z	"Steps to reproduce:

DL http://tinycorelinux.net/archive/tinycore_1.4.iso and use it.

Start a VM."	Artem S. Tashkinov
17549	Themes and UI elements missing after installing Guest Additions	Linux	VirtualBox 5.2.6	2018-02-18T17:43:50Z	2018-02-18T18:12:42Z	2018-02-18T18:12:42Z	"Host: Debian 8 / jessie
Guest: Ubuntu 16.04.3 LTS (Xenial)

After installing Guest Additions on the guest, all of the the theming is gone, all of the icons are blank / x-ed out.  See attachment."	VeHav2GoVeeper
18351	The VM session was aborted	Windows	VirtualBox 6.0.2	2019-01-23T02:04:28Z	2019-02-10T03:55:53Z	2019-02-10T03:55:53Z	"I'm using virtualbox6.0.0 on Ubuntu18.10 and run Windows XP as guest os, every time it throw error when I restore a sleep session:

The VM session was aborted.

返回 代码: 
NS_ERROR_FAILURE (0x80004005)
组件: 
SessionMachine
界面: 
ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}

I have upgrade to 6.0.2, but not fix.
"	shada
18412	The Virtual Machine Won't Start Unless Run Headless Start	Windows	VirtualBox 6.0.4	2019-02-05T13:08:15Z	2019-02-05T13:08:15Z	2019-02-05T13:08:15Z	"Hi,
When trying to boot a virtual machine clicking on Start button it crashes with the an error, see attached screenshot. Also attached a log file.

If the files are not attached it is due to I do not see how to attach them.

Thanks
Kiko"	kiko
21081	The mouse crashes with VirtualBox 6.1 and Debian 11 with kernel 5.18	Windows	VirtualBox 6.1.36	2022-08-28T03:02:23Z	2022-08-28T16:41:02Z	2022-08-28T16:41:02Z	"Hi, I'm using Linux Debian 11 (Bullseye) with Kernel 5.18 for compatibility with my new laptop, it doesn't work with a kernel < 5.18.
I have virtualized a windows 10 image with VirtualBox 6.1.36 r152435 (Qt5.15.2)
My problem is when I run a Banco de Sabadell application inside windows 10 to generate bank receipts, the mouse crashes.
I run this application on another laptop with another kernel 5.10 and it works.

The virtualbox error message is as follows:
ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={10cd08d0-e8b8-4838-b10c-45ba193734c1} aComponent={MouseWrap} aText={Could not send the mouse event to the virtual mouse (VERR_PDM_NO_QUEUE_ITEMS)}, preserve=false aResultDetail=-2807

Thanks!"	capi
16043	The guest mouse cursor have big black shadow bellow	Linux	VirtualBox 5.1.6	2016-10-07T09:51:09Z	2016-10-07T09:51:09Z	2016-10-07T09:51:09Z	The guest mouse cursor have big, fat, black shadow bellow. The problem exists both in Windows XP and Windows 7 guests. If I turn off mouse integration, the problem disappears.	mozo
9041	The example python script src/VBox/Frontends/VBoxShell/vboxshell.py	other	VirtualBox 4.0.4	2011-06-07T12:24:55Z	2011-06-09T09:10:18Z	2011-06-09T09:10:18Z	"The example python script src/VBox/Frontends/VBoxShell/vboxshell.py, has the ability to save screen-shots. When no file-name for a screen-shot the takeScreenshot function writes the screen-shot to ""/tmp/screenshot.png"".
Potentially ""/tmp/screenshot.png"" could be a symbolic link to another file. The other file would be over-written if a user saved a screen-shot without specifying the file-name."	ra
17843	The display with Screen Factor larger than 100% produces offsets in the display of some graphics	Windows	VirtualBox 5.2.12	2018-06-28T21:23:34Z	2018-06-28T21:23:34Z	2018-06-28T21:23:34Z	"When using screen factor of 100% the display of the graphics present in an Excel sheet are OK. (see screenshot 100% attached)
When using screen factor of say 125% the graphics in this Excel sheet are partially offsetted ! (see screenshot 125% attached)

Is this an issue with the way these graphics are handled by Excel, meaning that in such case there is nothing that can be done about that, or rather is there anything the virtual machine can do to fix this ?

Details : screenshots taken in fullscreen 1920x1080, on Excel 2003 running in XP, on Ubuntu 18.04 host.  "	Lucien
1930	The ability to exclude selected USB devices in the setup.	Windows	VirtualBox 1.6.4	2008-08-09T13:06:43Z	2016-10-24T15:19:14Z	2016-10-24T15:19:14Z	"I have been using VirtualBox for a couple of months now. I have had a couple of occasions where I have attempted to mount a USB flash key by doing a right mouse click selection on the icon in the lower right side of the virtual machine screen, only to accidentally select my USB mouse. This resulted in the inability to use the mouse in either the host system or virtual machine causing me to have to dump out of the GUI with a <alt><ctrl><backspace>. (not good)

Could you please include a feature in the virtual machine setup where I can 'hide' certain devices from the icon right mouse click selection, so as to prevent the accidental selection of devices that are already available to the virtual machine, and to prevent what work out to be something that disables of the system.

If you have any questions on what I am talking about please feel free to email me.

Walt Williams
Boulder, Colorado, USA"	Walt L. Williams
20811	Test build release not installing on Linux	all		2022-02-04T15:09:33Z	2022-02-04T16:50:57Z	2022-02-04T16:50:57Z	"''Test build v.'': 6.1.33 r149712 (Qt5.6.1)
''Host'' Fedora 35; Gnome 41 on X.org

''Note'': Previous installation v. 6.1.32, whose source repository was RPMfusion,  did work as intended. All components related to Virtualbox were dully removed as instructed before the installation of that test build release.

Installation not operational; What follows' won't fix it.


{{{
# /sbin/vboxconfig
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
This system is currently not set up to build kernel modules.
Please install the Linux kernel ""header"" files matching the current kernel
for adding new hardware support to the system.
This system is currently not set up to build kernel modules.
Please install the Linux kernel ""header"" files matching the current kernel
for adding new hardware support to the system
}}}
"	Ricky Tigg
18626	Tabs moving to new window after inactivity	Windows	VirtualBox 6.0.6	2019-05-07T13:59:43Z	2019-05-23T06:42:26Z	2019-05-23T06:42:26Z	I think the trackpad on my laptop has a glitch.  This doesn't happen during host operation.  When I let my laptop idle for a bit, and then come back, as soon as I touch the touchpad, all internet tabs, except the first one, move to a new window.  At first I thought it was closing them all, but then I realized I had multiple firefox windows open, when I didn't open any new windows.  I don't know what's going on.  I tried searching for a solution and came up empty.	adamgfloro
20883	System doesn't boot up	all	VirtualBox 6.1.32	2022-03-26T17:19:26Z	2022-03-26T17:19:26Z	2022-03-26T17:19:26Z	When I try to launch a guest the system doesn't boot up and I get a black screen.	ar1234a
17639	synced folder not working  (Ubuntu 16.04 hosting debian/stretch64 9.4.0 )	Linux	VirtualBox 5.2.8	2018-03-26T12:42:23Z	2018-03-29T08:35:23Z	2018-03-29T08:35:23Z	"When setting up a VM via '''Vagrant 2.0.1''' using '''VirtualBox 5.2.8''' and guest additions 5.2.8, touching a file in the default synced folder /vagrant does not make that file appear on the host side.

a similar test works fine for a guest of type ""ubuntu/xenial64 v20180215.0.0"".

how to reproduce: create following Vagrantfile (also attached):


{{{
Vagrant.configure(""2"") do |config|

      config.vm.box = ""debian/stretch64"" # or generic/debian9
      config.vm.box_version = ""9.4.0""
      config.ssh.insert_key = false

      config.vm.network ""private_network"", ip: ""192.168.33.10""
end
}}}

and the run following script from the hos:

{{{
#!/usr/bin/env bash

# to run from tools/vagrant/

set -x
set -e
set -u

GUEST=${1:-""default""} #$1    # name from `vagrant status`

export VERSION=5.2.8   # must be equal to the VirtualBox version!
export URL=""http://download.virtualbox.org/virtualbox/""$VERSION""/VBoxGuestAdditions_""$VERSION"".iso""

time vagrant ssh $GUEST << HERE

set -e
set -x

sudo bash

apt-get update

apt-get install -y dkms build-essential

apt-get install -y linux-headers-amd64 linux-headers-4.9.0-4-amd64

apt-get install -y module-assistant

cd /opt/

wget -c $URL -O vb.iso
mount vb.iso -o loop /mnt

cd /mnt/
sh ./VBoxLinuxAdditions.run --nox11

cd /opt
sudo rm *.iso

lsmod | grep vboxguest || echo ""*** something went wrong while attempting to install the guest additions""

HERE


}}}

touch a file in /vagrant

observe that the file does not appear in the host location.

"	axd
15792	Switching between Guided and Expert modes in Create Virtual Machine window loses settings	all	VirtualBox 5.1.2	2016-08-14T19:27:15Z	2018-11-25T21:27:10Z	2018-11-25T21:27:10Z	"I noticed a small problem when creating a VM using the GUI. Lubuntu 16.04 x86-64 host.

Click New, then when the Create Virtual Machine window appears type something in the Name field and change the Type and Version fields.

Click Expert Mode. The name and OS fields get reset to the default blank and Microsoft Windows / Windows 7 (64-bit). Similarly you can change those then click Guided Mode, and those fields reset again."	Donuts
21176	Switching between Expert & Guided modes resets all the data	all	VirtualBox-7.0.2	2022-10-21T12:20:48Z	2022-10-21T12:20:48Z	2022-10-21T12:20:48Z	"This is a very annoying bug.

Start creating a VM in guided mode. At the first step switch to Expert Mode. All the data you've entered will be instantly lost. It's the same vice versa.

Please fix."	Artem S. Tashkinov
13970	Switch desktop defect	Linux	VirtualBox 4.3.26	2015-03-20T09:46:09Z	2015-03-20T09:46:09Z	2015-03-20T09:46:09Z	"On Linux Mint Mate, I have a two-monitor linux VM, and when I boot up, it starts with just one window. The second window is launched a few second later.
If in the meantime, I change desktop (using ctrl-alt right or left, for example), the first window stays in the starting desktop, but the second one is opened in the second desktop.

Would be great if they were opened both in the same desktop.

Thank you."	malarittu
15185	Support to use mounted devices	Windows	VirtualBox 5.0.14	2016-02-28T07:26:06Z	2016-02-28T07:26:06Z	2016-02-28T07:26:06Z	For example if I'm mounting an USB drive on my Linux host and then starting with VirtualBox a guest that has this USB device in the filters registered the USB device gets unmounted on my host. Maybe VirtualBox can also support to use these devices on the guests without unmounting them on the host.	Sworddragon
11486	Support passthrought of TRIM commands to raw partitions	all	VirtualBox 4.2.6	2013-02-13T13:27:11Z	2017-04-29T14:31:38Z	2017-04-29T14:31:38Z	"Since VirtualBox 4.2 it appears that the AHCI virtual controller supports the ATA TRIM command.

However, only the VDI image file backend actually implements it, where it is used to detect unused blocks so that the image file size can be reduced (if using a dynamic image). The rest of backends do not seem to use it for anything.

My request is for the RAW block device backend to send TRIM/DISCARD commands to the backing block device upon receiving a TRIM command from the guest. 

This would enable e.g. Windows guests on raw partitions (via VMDK's partitionedDevice) sending TRIM commands to a backing SSD device, thereby increasing performance and SSD longevity. 

Unlike discard support for VDI images, this should not involve any extra bookkeeping (""discard"" commands can be sent to the raw block device mostly ""as is"", no need to cluster them)."	javispedro
19625	Super key and Alt-tab get captured by Ubuntu 20.04 Host not Windows 10 guest on 6.1.8	Windows	VirtualBox 6.1.8	2020-05-27T03:22:24Z	2020-06-02T02:29:21Z	2020-06-02T02:29:21Z	"Similar to the closed #10842 I am seeing the Ubuntu 20.04 host capture both the Super/Windows key (always) as well as Alt-tab.

I am seeing this on Ubuntu 20.04 immediately after upgrading from 18.04.

I have this version of Virtualbox installed  https://download.virtualbox.org/virtualbox/6.1.8/virtualbox-6.1_6.1.8-137981~Ubuntu~eoan_amd64.deb.

I am using a Windows 10 Virtualbox guest. When I press the ""Windows/Super"" key the Ubuntu unity menu responds when the Windows 10 virtualbox should respond. The unity desktop also seems to capture ""Alt-Tab"" but other ""Alt"" commands do respond in the Windows virtualbox."	kendonb
6576	Suggestion for improving the usermanual: Hostonly connection  should mention routing.	Linux	VirtualBox 3.1.6	2010-04-22T15:09:46Z	2010-05-04T14:14:20Z	2010-05-04T14:14:20Z	"I used virtualbox before version 2.0, and now I need it in a production case.

The guest will need to provide services to the outside world, and I need control through firewall/forwarding rules as to which ones it will be providing. Moreover, I cannot freely chose IP addresses and things like that (there is a shortage, you know. :-) ). 

Anyway, back in the old days I configured it in a way that the manual mentioned: ""difficult"", but for me it was a snap: IP routing is easy for me. So I now wanted to use something similar. The list of options for the guest network card is now larger than what I remember from the old days. So I read the section on networking, and couldn't find the option I  wanted. 

I tried a random few, and ended up with ""host only"", which I think should mention the option of using routing from the guest to the outside world. This would've made my experience with the new version a lot easier: I could've selected the right option right away. "	Roger Wolff
16781	Strange handling of encryption keys in case of encrypted media vs. encrypted VM.	Linux	VirtualBox 5.1.22	2017-05-24T14:48:07Z	2017-05-24T18:11:11Z	2017-05-24T18:11:11Z	"I have created a new medium and encrypted it according the docs[1] WITHOUT attaching it to a VM first. This succeeded and made me wonder where the encryption keys got saved? According to some blog posts and because of tests I made before with encryption on VM level, those should be saved in the XML config of a VM, but in my case I didn't have a VM the media was attached to. I had a look in the global configuration file of the user running the VBoxManage command as well and didn't find any keys.

So where should the keys be saved if only a new medium was created and encrypted, e.g. using VBoxManage, WITHOUT attaching that medium to a VM before encryption?

Afterwards I attached the newly created, encrypted media to some test VM and at some point recognized keys in the XML config of the test VM. Did some testing and stuff and removed the medium from the test VM again to attach it to another VM. But looking at the config of the first test VM, the keys of the re-attached medium is still present there, not in the VM where the medium is currently attached to. Additionally, it is really ONLY attached to the new VM, not the former test VM anymore.

Shouldn't the keys now be part of the one and only VM the medium is attached to? I'm supposed to backup the keys for all media, but how should I do that reliably if I can't be sure where the keys are actually stored? In my case the first VM was for test purposes, the second for production. What happens if I delete the test VM now, still containing the keys of my encrypted medium, even if it's not attached anymore?

I couldn't find any more detailed documentation about where VirtualBox stores the keys when and if/how/when those parts of the config are moved in case of attaching and removing encrypted media from VMs. Looking at how important those keys are, I strongly suggest adding some paragraphs to the docs how to deal with those and what VirtualBox does automatically. Or not at all, because in my case it doesn't seem to move case around as expected...

[1]: https://www.virtualbox.org/manual/ch09.html#diskencryption-encryption"	Thorsten Schöning
20108	Strange freeze in Linux host	Linux	VirtualBox 6.1.16	2020-12-30T08:36:15Z	2021-02-12T15:41:47Z	2021-02-12T15:41:47Z	"I get a repeatable hang of the VM and the GUI with the following sequence:

1.- get https://cloud-images.ubuntu.com/bionic/current/bionic-server-cloudimg-amd64.vmdk

2.- Create a new VM, 4G of RAM, the vmdk disk and _2_ vCPUs

3.- Start the VM

At one point in the boot process, the VM will stop producing output and when you try to stop it, the GUI will get blocked.

In parallel, I'm investigating why I can't assign 2 vCPUs to the VM using this image, but I'm worried that I can't just kill the VM and that the GUI gets blocked when I try so.

For the host:

uname -a                                                          
Linux paag-EliteBook 5.4.0-58-generic #64-Ubuntu SMP Wed Dec 9 08:16:25 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
"	paaguti-u
18436	Strange behavior for Full-screen minimize/restore on host screen 2	Windows	VirtualBox 6.0.4	2019-02-13T17:05:55Z	2019-02-13T17:05:55Z	2019-02-13T17:05:55Z	"If my VB guest session is on host screen 2, a minimize/restore sequence will display the VM guest on host screen 1, while the full-screen menu will correctly be displayed on host screen 2.

The issue can subsequently be resolved by using the menu to switch to host screen 1 and then back to host screen 2 once again.

My configuration:[[BR]]
Virtualbox 6.0.4 and 5.2.26, No video acceleration[[BR]]
Host:  Ubuntu 18.04 running X Windows/GNOME[[BR]]
Video: NVidia 415.27 driver, dual monitors[[BR]]
Guest: Windows 10 (1809)
"	John JJ
20786	Strange audio related VM lockups	all	VirtualBox 6.1.32	2022-01-21T03:29:23Z	2022-04-28T20:50:24Z	2022-04-28T20:50:24Z	"I am experiencing lockups related to audio playback in VirtualBox. To clarify, lockup means that Virtualbox locks up, not the guest; pressing the reset button in virtualbox does nothing. The window will not close unless I issue a ""killall VirtualBoxVM"", but the UI remains mostly responsive. This has been happening since around 6.1.24. 6.1.22 is the latest version that works fine. On the host, I am using ALSA without pulseaudio. I normally use a very customized asoundrc file, but even without my special ALSA configs, the issue still occurs. 

On a WinXP guest, I am experiencing a complete freeze when attempting to move the volume slider and sometimes audio playback causes a freeze. 

On a Ubuntu 16.04 guest (kernel 4.4), audio playback happens too fast/slow sporadically. When this happens, I see lines like these in dmesg on the guest.
[    9.025442] snd_intel8x0 0000:00:05.0: intel8x0_measure_ac97_clock: measured 55894 usecs (2880 samples)
[    9.025446] snd_intel8x0 0000:00:05.0: clocking to 44715
When that value (44715) is below 48k, audio is slow. When above, it's fast. Rebooting the VM seems to randomly change this ""clocking to ..."" value. Also, occasionally, after a long audio playback session with google chrome + youtube the VirtualBox instance will hang on shutdown (VM guest shuts down, but window remains open)."	li200
18964	storageattach --hotpluggable while running makes disk unremovable	other	VirtualBox 5.2.32	2019-09-25T17:36:26Z	2020-01-24T03:41:58Z	2020-01-24T03:41:58Z	"Machine `w10` is running. I do:
gsovetov@gsovetov:~$ VBoxManage storageattach w10 --storagectl SATA --port 4 --type hdd --medium po.vdi --hotpluggable on
VBoxManage: error: The machine is not mutable (state is Running)
VBoxManage: error: Details: code VBOX_E_INVALID_VM_STATE (0x80bb0002), component SessionMachine, interface IMachine, callee nsISupports
VBoxManage: error: Context: ""SetHotPluggableForDevice(Bstr(pszCtl).raw(), port, device, TRUE)"" at line 901 of file VBoxManageStorageController.cpp
}}}

I expect it to complete successfully as I explicitly enable hot-plugging when actually hot-plugging. But it's not all.

The biggest problem is that the disk get irreversibly associated with the VM! Neither attaching the disk again to this or another VM, nor `closemedium`, nor Release/Remove in Virtual Media Manager after unregistering the VM help.

{{{
gsovetov@gsovetov:~$ VBoxManage storageattach w10 --storagectl SATA --port 4 --type hdd --medium po.vdi 
VBoxManage: error: Cannot attach medium '/home/gsovetov/po.vdi' {47bb8284-7df3-42db-8132-c7d1248ee59d}: medium is already associated with the current state of machine uuid {490c11af-e66f-45fa-9e7d-f9f8ed156169}!
VBoxManage: error: Details: code VBOX_E_OBJECT_IN_USE (0x80bb000c), component MediumWrap, interface IMedium, callee nsISupports
VBoxManage: error: Context: ""AttachDevice(Bstr(pszCtl).raw(), port, device, DeviceType_HardDisk, pMedium2Mount)"" at line 776 of file VBoxManageStorageController.cpp
}}}

{{{
gsovetov@gsovetov:~$ VBoxManage showvminfo w10 --machinereadable | grep -iE 'storage|sata'
storagecontrollername0=""SATA""
storagecontrollertype0=""IntelAhci""
storagecontrollerinstance0=""0""
storagecontrollermaxportcount0=""30""
storagecontrollerportcount0=""8""
storagecontrollerbootable0=""on""
""SATA-0-0""=""/home/gsovetov/VirtualBox VMs/w10/Snapshots/{e27504b0-359a-4caf-bbaa-6770cc83fff1}.vdi""
""SATA-ImageUUID-0-0""=""e27504b0-359a-4caf-bbaa-6770cc83fff1""
""SATA-1-0""=""none""
""SATA-2-0""=""none""
""SATA-3-0""=""none""
""SATA-4-0""=""none""
""SATA-5-0""=""none""
""SATA-6-0""=""none""
""SATA-7-0""=""none""
}}}

{{{
gsovetov@gsovetov:~$ VBoxManage list hdds | grep -C5 po

UUID:           47bb8284-7df3-42db-8132-c7d1248ee59d
Parent UUID:    base
State:          created
Type:           normal (base)
Location:       /home/gsovetov/po.vdi
Storage format: VDI
Capacity:       100 MBytes
Encryption:     disabled

}}}

{{{
gsovetov@gsovetov:~$ VBoxManage showmediuminfo po.vdi 
UUID:           47bb8284-7df3-42db-8132-c7d1248ee59d
Parent UUID:    base
State:          created
Type:           normal (base)
Location:       /home/gsovetov/po.vdi
Storage format: VDI
Format variant: dynamic default
Capacity:       100 MBytes
Size on disk:   2 MBytes
Encryption:     disabled
In use by VMs:  w10 (UUID: 490c11af-e66f-45fa-9e7d-f9f8ed156169)
}}}

{{{
gsovetov@gsovetov:~$ VBoxManage unregistervm w10  
gsovetov@gsovetov:~$ VBoxManage showmediuminfo po.vdi 
UUID:           47bb8284-7df3-42db-8132-c7d1248ee59d
Parent UUID:    base
State:          created
Type:           normal (base)
Location:       /home/gsovetov/po.vdi
Storage format: VDI
Format variant: dynamic default
Capacity:       100 MBytes
Size on disk:   2 MBytes
Encryption:     disabled
VBoxManage: error: Could not find a registered machine with UUID {490c11af-e66f-45fa-9e7d-f9f8ed156169}
VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBoxWrap, interface IVirtualBox, callee nsISupports
VBoxManage: error: Context: ""FindMachine(machineIds[i], pMachine.asOutParam())"" at line 1375 of file VBoxManageDisk.cpp
gsovetov@gsovetov:~$ VBoxManage closemedium /home/gsovetov/po.vdi
VBoxManage: error: Medium '/home/gsovetov/po.vdi' cannot be closed because it is still attached to 1 virtual machines
VBoxManage: error: Details: code VBOX_E_OBJECT_IN_USE (0x80bb000c), component MediumWrap, interface IMedium, callee nsISupports
VBoxManage: error: Context: ""Close()"" at line 1648 of file VBoxManageDisk.cpp
}}}

The only way to detach it is to power off all VMs, wait for VBoxSVC to terminate, then manually remove the record from XML file, then run GUI and open Virtual Media Manager and remove the disk there."	georgesovetov
18778	STM32CubeIDE GDB start-up fails in VirtualBox with Ubuntu guests	Linux	VirtualBox 6.0.6	2019-07-21T19:39:47Z	2019-07-21T19:39:47Z	2019-07-21T19:39:47Z	"
I have tested all supported Ubuntu versions listed in UM2563 when installed as a VirtualBox guest
and STM32CubeIDE is installed in the guest operating system (Ubuntu 14.04, 16.04, 18.04).
Also Linux Mint Mate 19.1 and 19 are tested with similar results as VirtualBox guests.

VirtualBox versions is:

VirtualBox 6.0
VirtualBox Graphical User Interface
Version 6.0.6 r130049 (Qt5.9.5)
Copyright © 2019 Oracle Corporation and/or its affiliates. All rights reserved.

VirtualBoxGuestAdditions VBox_GAs_6.0.6 is installed.
Oracle VM VirtualBox Extension Pack 6.0.8r130620 is installed in Oracle VM VirtualBox Manager.

THE ISSUE IS:
============

Only an unmodified code generated as a STM32Project.
All have the same behaviour where installation and compilation succeed but GDB start-up fails with the message:

Could not determine GDB version using command: /opt/st/stm32cubeide_1.0.2/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.7-2018-q2-update.linux64_1.0.0.201904181610/tools/bin/arm-none-eabi-gdb --version

This is consistent in all Ubuntu versions and same with IDE versions 1.0.1 and 1.0.2.

When running the same command in a terminal session the response is as follows:

xxxxx@ubuntu1604base:~$ /opt/st/stm32cubeide_1.0.2/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.7-2018-q2-update.linux64_1.0.0.201904181610/tools/bin/arm-none-eabi-gdb --versionGNU gdb (GNU Tools for STM32 7-2018-q2-update.20190328-1800) 8.1.0.20180315-git
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type ""show copying""
and ""show warranty"" for details.
This GDB was configured as ""--host=x86_64-linux-gnu --target=arm-none-eabi"".
Type ""show configuration"" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type ""help"".
Type ""apropos word"" to search for commands related to ""word"".

When installed without virtualisation (in Linux Mint 19.1 Mate only) everything works as expected (no errors).

"	mnu
17720	State/Powered off since ??	Windows	VirtualBox 5.2.10	2018-04-30T09:30:00Z	2018-05-03T14:17:06Z	2018-05-03T14:17:06Z	"So this is not a bug, but I guess a ""feature request"". If I copy a VM between machines, usually via rsync, I notice that the State (if the VM was off would state ""Powered off since.."") listed in a vboxmanage showvminfo is from the local machine not the machine that I copied it from. Even if I have copied all of the files from the VMs folder from another machine.

However, if I have copied the files, yet remove the VM from VirtualBox (while choosing not to remove the files) and then add the VM back, it has the correct date/time of when it was powered off on the original machine. 

So I am wondering if it got that information from the VM files that were copied, how can that information be locally updated to indicate that?"	jim.rather
16714	starting with 5.1.20 the mini toolbar does not appear	all	VirtualBox 5.1.22	2017-05-01T07:08:40Z	2017-05-08T15:10:25Z	2017-05-08T15:10:25Z	"I run arch linux x86_64 curently kernel is 4.10.11-1-ARCH #1 SMP. If I run  5.1.18 then guests have the mini toolbar showing at the top. If I run 5.1.20 then I lose alsa sound and the mini toolbar does not appear. If I run 5.1.22 then alsa sound is restored, but the mini toolbar is not showing.

In the guest setup user interface I have both show in seamless and appear at top picked.

I use openbox as window manager and slim as login manager."	replabrobin
7009	Starting VM with Intel-VT enabled freezes system	other	VirtualBox 3.2.10	2010-06-15T21:35:34Z	2018-03-21T06:23:27Z	2018-03-21T06:23:27Z	"When starting a VM on my laptop with Intel-VT enabled, the host freezes immediatly.
As workarround I can disable VT in BIOS.

I experience the problem with:
VirtualBox-3.2.4 and 3.1
Fedora-12 and Fedora-13 + rawhide-2.6.34

Because the system freezes immediatly after starting the VM, log files are empty.
I'll attach a log file generated when VT was disabled."	Linuxhippy
16253	Starting vm hides itself and all apps on 2 desktops	Linux	VirtualBox 5.1.10	2016-12-01T14:58:40Z	2016-12-02T02:53:25Z	2016-12-02T02:53:25Z	"Host is Dell M6800 running Mageia 5 Linux, KDE4(with 8 desktops).
On desktop 3, running VB, I install/updatee Mageia 6-RC, then reboot to test -- it minimizes ALL apps, as if I clicked host's Show Desktop, on desktop 3 _and_ 4...
Via the taskbar, I can restore (un-minimize) the apps; but when I do this on the started vm, it minimizes all the apps again.  All I can do with this running vm is to power it off which then restores all the minimized apps on both desktops. No idea how this vm could impact 2 desktops on host...

Screenshot of no visible apps would not help...  :)"	Pierre Fortin
18488	standard tty control sequences ignored in all VM's	Linux	VirtualBox 6.0.4	2019-03-11T19:58:49Z	2019-03-24T00:24:35Z	2019-03-24T00:24:35Z	"Running ubuntu 15.04 Server as well as newer Ubuntu Server VM's as well as RH and Suse within VMs.  When using terminal the typical control sequences (ctrl+c, ctrl+v, ctrl+d, etc) are ignored.  The ctrl portion is eaten/suppressed and the following letter is displayed.   When I run showkey and repeat those the ctrl portion is ignored.  On the host os showkey shows the correct values.  I've even tried a different usb keyboard to make sure it wasn't that.
Trying to run and work on a tty without these controls is extremely frustrating.
I've been researching for almost a week now without any results.   Please address? Thanks"	bobmct
20480	SSM: Giving up: Too many passes! (1048576)	Windows	VirtualBox 6.1.10	2021-07-29T11:29:33Z	2021-08-27T21:05:58Z	2021-08-27T21:05:58Z	"We use Virtualbox to make crash-consistent backups of VMs. The script does basically:
- Take snapshot
- Clone snapshot to backupfolder
- Delete snapshot

In some cases (we believe it might be 'busy Windows servers running databases') the backup takes longer than normal. The next day it will take even longer, until after a few days the whole snapshot-taking will fail:

VBoxManage: error: Failed to take snapshot
VBoxManage: error: Failed to save the machine state to '/mnt/path/to/file.sav' (VERR_SSM_TOO_MANY_PASSES)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole
VBoxManage: error: Context: ""RTEXITCODE handleSnapshot(HandlerArg*)"" at line 483 of file VBoxManageSnapshot.cpp


A subtract of the logfile does show the problem 'building up' over several days. As soon as the problem exists (and the snapshot fails and keeps failing) it will not go away until we reboot the host:

20:58:09.224319 SSM: Step 1 completed after pass 77.
44:58:12.823156 SSM: Step 1 completed after pass 66.
68:58:11.413950 SSM: Step 1 completed after pass 68.
92:58:12.074819 SSM: Step 1 completed after pass 66.
116:58:13.100936 SSM: Step 1 completed after pass 71.
140:58:17.220420 SSM: Step 1 completed after pass 76.
164:58:16.008601 SSM: Step 1 completed after pass 67.
188:58:17.074839 SSM: Step 1 completed after pass 67.
212:58:17.135282 SSM: Step 1 completed after pass 69.
236:58:17.638284 SSM: Step 1 completed after pass 66.
260:58:18.045740 SSM: Step 1 completed after pass 68.
284:58:18.171871 SSM: Step 1 completed after pass 67.
308:58:17.953139 SSM: Step 1 completed after pass 66.
332:58:18.609908 SSM: Step 1 completed after pass 69.
356:58:19.043087 SSM: Step 1 completed after pass 67.
380:58:45.760012 SSM: Step 1 completed after pass 397.
405:00:09.558703 SSM: Step 1 completed after pass 1598.
429:01:14.283550 SSM: Step 1 completed after pass 2457.
453:16:20.819291 SSM: Step 1 completed after pass 14096.
498:30:29.200112 SSM: Step 1 completed after pass 964826.
549:39:38.213154 SSM: Giving up: Too many passes! (1048576)
549:39:47.451837 SSM: Failed to save the VM state to '/mnt/path/to/file.sav' (file deleted): VERR_SSM_TOO_MANY_PASSES
597:35:18.928754 SSM: Giving up: Too many passes! (1048576)
597:35:40.379878 SSM: Failed to save the VM state to '/mnt/path/to/file.sav' (file deleted): VERR_SSM_TOO_MANY_PASSES

We observed that the .sav-file is growing really big before failing.

The whole VBox.log is attached, as well as the relevant commands of our bash-script."	AO
7419	SSH tunnel headless mode	other	VirtualBox 3.1.8	2010-09-02T19:54:43Z	2010-09-04T08:27:30Z	2010-09-04T08:27:30Z	Emulation of a Headless Virtual Machine through Supression of any standard Drawn Display, where I would perform all operations through an ssh tunnel.	shiny
18425	Spontanious guest hanging after rollback	Linux	VirtualBox 6.0.4	2019-02-11T08:55:10Z	2019-02-11T08:55:10Z	2019-02-11T08:55:10Z	"After a number of rollbacks to a certain live snapshot the guest (Ubuntu Server 16.04) seems to restore its state but becomes totally unresponsive. It just hangs on the prompt, the video doesn't change at all (even the cursor doesn't blink), and pressing any keyboard keys doesn't have any effect. Htop also shows that one of the cores is loaded 100% with the VBoxHeadless process. You may reboot the guest forcefully and it starts just fine. It's just I have to do a lot of rollbacks to live snapshots automatically that this occasional freeze bugs me big time.

P.S. If that makes any difference - I'm doing headless start instead of normal start

P.S.S. Bug seems to be very occasional - once in a few dozen times maybe
"	CIDJEY
18342	Sound totally broken for Windows XP guest under Linux host	Windows	VirtualBox 6.0.2	2019-01-21T13:13:43Z	2021-12-14T00:11:36Z	2021-12-14T00:11:36Z	"I just updated to VirtualBox v6.0.2 and noticed immediately that audio got totally, utterly broken and non-functional (even going up to crash programs using sounds) for my Windows XP guest under my Linux host.

Sound was working beautifully with v6.0.0 (*) and I reverted to it...

Note that the version of the extpack (6.0.0 or 6.0.2) installed (both in VirtualBox and in the guest OS) does not seem to matter: it's broken at VirtualBox level itself, apparently.

This is a showstopper bug: pretty please, fix it quickly !

Attaching relevant logs to this ticket.


----------
(*) after bad sound lag issues in the late v5.2 releases, akin to what I encountered with even older releases and reported in this ticket: https://www.virtualbox.org/ticket/15924 )"	dinosaur0
16720	Sound randomly stops working until vm restarted (Fedora vm on Debian host running VirtualBox 5.1.18)	Linux	VirtualBox 5.1.18	2017-05-02T19:41:59Z	2019-04-18T20:53:26Z	2019-04-18T20:53:26Z	"It happens very often that the sound stops working after a vm has been running for more than a day.

To clarify: ""Sound stops working"" means just that. For example, an audio file would be played in VLC and no sound would be produced (volume settings have not been changed).

There's a hint that it must have something to do with VirtualBox: After restarting the vm, it works again. It's not even necessary to restart the guest system. The vm can be suspended while VLC is running, it's then immediately resumed and as soon as it's running again, the sound is working again, the music played by VLC will come out.

This is an annoying bug because the vm has to be suspended/resumed all the time and sometimes that's not possible when certain connections should no be disrupted.

Nothing is logged in VBox.log. Host audio driver is PulseAudio, audio controller is ICH AC97 (default settings). Guest OS is Fedora 25. Host OS is Debian 8. VirtualBox 5.1.18."	Philip Seeger
16042	Sound lag. The sound and present actions walk past each other. Arch Linux host, Windows guest	Windows	VirtualBox 5.1.6	2016-10-07T09:40:35Z	2016-10-22T16:10:53Z	2016-10-22T16:10:53Z	"Since month or two when I take an action sound lags behind. I use heavily GuitarPro 4 and when I press Play, the program start playing as the cursor moves around the notes, but the sound lags behind and the playback  starts approximately 2 seconds after the pressing. When I want to stop playing, the moving cursor, which shows which note is being played at the moment, stops immediately but the sound actually stops after 2 seconds. 

This lag is presented everywhere - for example start a browser and watch video on YouTube - sound and picture walk past each other and the synchronization is lost.

This happens on Arch Linux host and Windows XP, Windows 7 and Windows 10 guests. There is no difference between the different guests. All of the guests have the latest Virualbox Guest Additions 5.1.6 installed.

There has been a discussion about this in https://bbs.archlinux.org/viewtopic.php?id=217686.

Here you are a reference video of the problem:

https://youtu.be/gej7gMwAQug

So the program is completely useless for I don't know which note playing at the moment."	mozo
18879	Sound issues since 5.2.20 - Win98+Fifa98	Windows	VirtualBox 6.0.10	2019-08-29T15:06:03Z	2019-12-17T00:03:47Z	2019-12-17T00:03:47Z	"Hi,
I used to use a Virtualbox for quite some time on a private system to emulate Windows 98 SE with Fifa98 RTWC [2].
That was going fine but somewhen throughout last year I list sound.
First I thought it would be my messing with the system, but whatever I did it did not return.
After a while I did full re-install my system back to the last perfectly working virtualbox version (and a new OS install of the older Ubuntu 16.04).

Then I used the upstream downloads [3] to essentially do a version bisect when it was broken and found it.
6.0.10 (known bad)
5.2_5.2.32-132073 - fail
5.2_5.2.28-130011 - fail
5.2_5.2.20-125813 - fail
5.2_5.2.18-124319 - ok
5.2_5.2.16-123759 - ok
5.2_5.2.14-123301 - ok
5.2_5.2.4-119785 - dkms error on install
5.5.2_2.0-118431 - dkms error on install
5.1_5.1.38-122592 - ok (known good)

It is not that sound would be broken totally, e.g. windows startup sound works and playing wav files. But when starting the game sound fails (no error message). Back out of the game Windows sound works still.

I think this uses DX5 for sound, but I'm not sure.

I tried to replace the (virtual) sound card from soundblaster to AC97 but that didn't help either.

I wonder what debug data I could collect for you to get this understood and fixed at the head of 6.x series so that I can upgrade again?

P.S. I started this in the Ubuntu tracker at [1], but after the debugging we did I guess it is time to reach out here.

[1]: https://en.wikipedia.org/wiki/FIFA:_Road_to_World_Cup_98
[2]: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1840749
[3]: https://www.virtualbox.org/wiki/Downloads"	cpaelzer
15910	Sound delay	Windows	VirtualBox 5.1.4	2016-09-08T14:24:51Z	2016-12-10T07:56:16Z	2016-12-10T07:56:16Z	"After upgrading to VirtualBox 5.1.x and installing the anniversary update of Windows 10 (on the guest) I'm noticing sound delays of about ~1 second and that accessing files on the shared folder causes it often to lock up (seems to be a race condition). The latter causes related applications (like any browser and the Windows explorer) to hang and Windows is mostly not able anymore to cleanly shutdown.

I'm not sure if the issues are caused by Windows (at least a clean reinstall did not solve them) or VirtualBox but to go sure I have created this ticket. In the attachments is the VBox.log of a session where both issues got reproduced. Also there is a testcase for the lockup issue (testcase.css and testcase.html) which needs to be put into a shared folder and testcase.html needs then to be opened with any browser (for example Google Chrome). Keeping F5 pressed to cause Chrome to reload the testcase multiple times should cause the race condition to appear after a few seconds (noticeable by not seeing the green circle on Virtual Box's shared folder symbol anymore and Chrome trying to load the site for an infinite amount of time)."	Sworddragon
17956	Sort button in the context menu	all	VirtualBox 5.2.16	2018-08-26T00:10:15Z	2018-08-26T00:10:15Z	2018-08-26T00:10:15Z	"Can you please move the sort button in the context menu away from the bottom of the menu, or at least make it prompt the user?

In KDE 5 I keep triggering it by accident when I nudge my mouse while right-clicking a VM near the bottom of the list in the left sidebar, and I'm tired of rearranging my VMs all the time."	Rmb1
19949	Some VirtualBox EFI Boot Menu entries do nothing when booting from ISO	Linux	VirtualBox 6.1.14	2020-10-08T19:51:51Z	2020-10-08T19:51:51Z	2020-10-08T19:51:51Z	"Description:

With the exception of EFI Shell entry, none of the other choices in the EFI Boot Menu actually launch an EFI binary.  I've tried this with several different ISO images with the same result.  Usually, however, I can navigate using the EFI shell to the EFI binary and launch it manually.

Steps to reproduce (example):

(Using VirtualBox 6.1 on Devuan Ascii 2.1)
Download recent copy of Devuan ISO (devuan.org)
Create brand new EFI VM (with appropriate bitness)
""Insert"" the downloaded copy of Devuan ISO in the CD drive
Start the VM -- the EFI shell will appear
Exit the EFI Shell
Select the Boot Menu option in the EFI UI
Try to launch the entries in the Boot Menu (the EFI Shell entry will work; try others)

Expected Outcome:   Grub menu appears

Actual Outcome:  Nothing happens; the user is left in the EFI UI

Additional Information:

Adelie Linux (adelielinux.org) and Devuan experience this issue, regardless of 32 or 64 bitness, and regardless of which variation of these distros are used.  Other distros have not been tested for EFI install extensively.
"	Harry M
20255	Solaris 11.4 gnome continuous restarting - application 'org.gnome.Shell.desktop' killed by signal 11	Solaris	VirtualBox 6.1.18	2021-03-16T12:17:31Z	2021-03-18T14:18:08Z	2021-03-18T14:18:08Z	Guest created from Oracle Solaris 11.4 VM Template for Oracle VM VirtualBox	Andrew Belousoff
3348	Small icons/treeview for guest list	Linux	VirtualBox 2.1.2	2009-02-15T20:56:25Z	2016-01-13T06:34:55Z	2016-01-13T06:34:55Z	"See also http://forums.virtualbox.org/viewtopic.php?t=14385

I propose a text-only, or small icons version of the guest VM list, as you can only get about 16 guests into a 1280x1024 desktop with the VirtualBox window maximised (smaller icons for the rest of the GUI and unsnapping status/toolbars would help here too).

How about an expand/collapse system (Qt4 Tree widget?) so you could have a folder for Windows, a folder for Linux, a folder for Solaris etc.

Also how about a way to change the sort order - at the moment its alphabetical, how about being able to sort by OS or last access date?

I think a good idea would be to make the guest list more like Nautilus or Windows Explorer, treating the guests like files/folders."	sej7278
17879	Slow traffic on Bridged network interface when using anything but virtio-net	Linux	VirtualBox 5.2.16	2018-07-20T18:42:15Z	2018-07-20T18:48:38Z	2018-07-20T18:48:38Z	"Hi,

I'm noticing my network interfaces on my VM is very slow 300-400KB/s when using any of these network intefaces:

PCnet-PCI II (Am79C970A)
PCnet-FAST III (Am79C973)
Intel PRO/1000 MT Deesktop (82540EM)
Intel PRO/1000 T Server (82543GC)
Intel PRO/1000 MT Server (82545EM) - couldn't bring network up

When I used:

Paravirtualized Network (virtio-net)

I saw the normal speeds ie 3-4MB/s which is what I should be getting.

The virtual machine is a Debian 9 (Stretch)

Linux virtualmachine 4.9.0-7-amd64 #1 SMP Debian 4.9.110-1 (2018-07-05) x86_64 GNU/Linux


 ii  virtualbox-guest-dkms             5.2.10-dfsg-6~bpo9+1           all          x86 virtualization solution - guest addition module source for dkms
ii  virtualbox-guest-utils            5.2.10-dfsg-6~bpo9+1           amd64        x86 virtualization solution - non-X11 guest utilities
ii  virtualbox-guest-x11              5.2.10-dfsg-6~bpo9+1           amd64        x86 virtualization solution - X11 guest utilities

The host is Archlinux (latest updates 2018-07-20) ie:

Linux host 4.17.6-1-ARCH #1 SMP PREEMPT Wed Jul 11 19:14:29 UTC 2018 x86_64 GNU/Linux

The virtual machine currently has:

Base Memory: 2048MB
Chipset:     PIIX3
Enable I/O APIC = yes
Proceessor(s) = 4
Execution Cap = 100%
PAE/NX = false
Paravirtulization Interface: Default
VT-x/AMD-V = yes
Nested Paging = yes
Video Memory 128MB

Network:

Bridged Adaptor, on VLAN 2. (VLAN is set inside of the virtual machine).
Has dual stack IPv4 & IPv6 ie NAT IPv6 addressss and IPv6 GLA address.

The version of VirtualBox that ArchLinux has at the moment is 5.2.16 r123745"	Tyler A
18582	Slow startup	Linux	VirtualBox 6.0.6	2019-04-19T10:11:04Z	2019-06-07T06:38:42Z	2019-06-07T06:38:42Z	"Ever since VB 6.x, start up process of the VM is extremely slow. However, if performing multiple mouse clicks in a quick succession (10+) during the process, start up will perform almost in normal speed.

Virtual Machine is Android x86 project, version 8.1-r1"	blubber
17746	"Slow I/O when ""Use Host I/O Cache"" is switched on"	Linux	VirtualBox 5.2.10	2018-05-09T09:29:56Z	2018-07-29T15:08:38Z	2018-07-29T15:08:38Z	"I installed VirtualBox 5.2 and when I/O cache is switched on, I/O is very slow.

Steps to reproduce:

1. Create a virtual machine with Debian or Ubuntu
2. Switch ""Use Host I/O Cache"" on, on SATA controller.
3. Try to upgrade existing packages or install new in the virtial machine. I have spinning disks on my host computer and they become noisy and IO speed is between 900KB/s and 1.3 MB/s during installation or upgrade of packages. I had no such problem with VirtualBox 5.1."	Georgi
18982	Skype for Business in Win10 guest unusable graphical glitches on Linux host with VBoxSVGA	Windows	VirtualBox 6.0.12	2019-10-04T17:11:19Z	2020-02-11T14:32:25Z	2020-02-11T14:32:25Z	"Hi, I'm running Win10 1903 on an openSUSE Tumbleweed host with VirtualBox 6.0.12 and integrated Intel graphics. I tried both the Xorg Intel driver as well as the X modesetting driver, and they both act the same. When I switch from VBoxVGA to VBoxSVGA due to the deprecation warning, Skype for Business (October 1, 2019, update KB4484102) becomes unusable due to major graphical glitches. Almost the whole window, including the window border and controls is either white or black. I am attaching a screenshot.

I tried updating the guest additions inside Win10, as well as the extension pack on the host, and it makes no difference. I have 2D and 3D acceleration enabled, which I definitely need for my workload in the Win10 guest.

Please do not deprecate VBoxVGA until VBoxSVGA becomes a reliable alternative.

Thanks."	sb56637
19413	Silent fail of inotify_add_watch	all	VirtualBox 6.1.4	2020-03-18T10:13:21Z	2020-03-18T10:13:21Z	2020-03-18T10:13:21Z	"To watch new USB devices, ''VBoxSVC'' use ''inotify_add_watch'' on ''/dev/vboxusb''. If ''inotify_add_watch'' fails, USB redirection will silently fail (no log nor warnings).

''inotify_add_watch'' may fail if the limit of watches is already reached. The limit is quite low on a default stable debian install (8192) and several modern text editors use a lot of watches to... watch directories and subdirectories.

Step to reproduce the problem:
1] make sure that VBoxSVC isn't running
2] check that the limit is not too high ''cat /proc/sys/fs/inotify/max_user_watches'', if it is, just temporarily decrease it: ''echo 1000 | sudo tee /proc/sys/fs/inotify/max_user_watches''
3] drain all the watches (for example by executing ''inotifywatch -r'' on a folder with a lot of subfolders.
4] run ''VBoxSVC'', you may ''strace'' it to make sure that ''inotify_add_watch'' fails
5] run ''VBoxManage list usbhost''
6] observe that ''inotify_add_watch'' fails in ''VBoxSVC'' and that ''VBoxManage list usbhost'' returns nothing.
7] [optionnal] use this script to check who's using all the watches: https://raw.githubusercontent.com/fatso83/dotfiles/master/utils/scripts/inotify-consumers

''VBoxSVC'' should return an error that ''VBoxManage list usbhost'' and VirtualBox gui client could display to easily diagnose the problem and maybe hint on a solution (kill the process using all the watches or increase the limit).

There may be other use of ''inotify_add_watch'' in the VBox codebase and there may be other code path to check (for example, there is also a restriction on the number of inotify **instances**, cf. ''/proc/sys/fs/inotify/max_user_instances'', that may cause ''inotify_init'' to fail). "	elvanderb
7142	SHUTDOWN=acpibutton fails to wait for shutdown of headless/vrdp guest with parrallel boot activated on host	other	VirtualBox 3.2.6	2010-07-08T12:31:37Z	2012-11-29T16:24:51Z	2012-11-29T16:24:51Z	"Hello,

I am running Virtualbox vrdp type virtual machines on a server.
These are started and stopped with the acpipowerbutton (and a wait until all vms are stopped) command on host startup and shutdown.
I use a custom init script for this, but while investigating the problem I used the functionality of the entry ""SHUTDOWN=acpibutton"" in /etc/default/virtualbox and it shows exactly the same behaviour:
The VM is not shutting down gracefully, but stopped abruptly, when the host is shutting down. Moreover multiple times I lost data on that stopped VMs (they worked well, just ""forgot"" some recent activities like VCS commits...).

For my script I found the problem to be the fact that Debian (Squeeze) recently activated parrallel execution of initscripts. I suspect the sendsigs script at fault, as it sends KILL signals to all remaining running processes. Though I solved that problem for me by adding $all to Required-Start and Required-Stop, so the VMs start and stop after respectively before all other scripts, which is what I want.
I think it's the same with SHUTDOWN=acpibutton option of the virtualbox init script.

I migrated my machines from VMWare Server, I had no problems with the equivalent shutdown option there.
"	ddehnhard
7288	Shared Folders: on windows guest, linux host. case-sensitive directoryes, but not files.	Windows	VirtualBox 3.2.6	2010-08-09T09:12:43Z	2010-09-22T12:28:31Z	2010-09-22T12:28:31Z	"
example of bug:

    Microsoft Windows XP [Version 5.1.2600][[BR]]
    (C) Microsoft Corporation 1985-2001.[[BR]]
    C:\> net use S: \vboxsvr\user[[BR]]
    S:\TEMP> mkdir tst[[BR]]
    S:\TEMP> mkdir TST[[BR]]
    Subdirectory or file TST already exists. ''<---- normal for WinXP. case insensitive''[[BR]]
    S:\TEMP> mkdir TST\SECOND[[BR]]
    The system can not find the path specified. '''<---- abnormal. case sensitive ! '''[[BR]]
    S:\TEMP> mkdir tst\SECOND[[BR]]
    S:\TEMP> echo 123> TST\SECOND\file '''<---- abnormal. case sensitive ! '''[[BR]]
    Can not find the file specified.[[BR]]
    S:\TEMP> echo 123> tst\SECOND\file[[BR]]
    S:\TEMP> echo 123>> tst\SECOND\FILE ''<---- normal. case insensitive''[[BR]]
    S:\TEMP> erase tst\SECOND\FILE ''<---- normal. case insensitive.''  '''bug does not affect the files, only directories!!! '''[[BR]]


shared folder placed on XFS partition of host.

i found similar ticket [http://www.virtualbox.org/ticket/437 437], but is associated with a very old version of vbox

Why are the directory names are case-sensitive, but filenames not? How to fix?"	Jury
13930	"Shared folders: ""umount -f"" required"	Linux	VirtualBox 4.3.24	2015-03-06T12:53:56Z	2015-03-06T12:53:56Z	2015-03-06T12:53:56Z	"Host: openSUSE 13.1 (64bit)
Guest: openSUSE 13.2 (64bit)"	robert spitzenpfeil
18322	Shared folders hang while R/W access	Windows	VirtualBox 6.0.2	2019-01-17T13:07:17Z	2019-08-29T07:37:09Z	2019-08-29T07:37:09Z	"Host `lsb_release -a` is 
{{{
Distributor ID: Debian
Description:    Debian GNU/Linux 8.11 (jessie)
Release:        8.11
Codename:       jessie
}}}


I'm using shared folders in Windows 7 x86 guest and Mentor Expedition PCB hangs if I try to open project, placed on shared disk.

This behavior is not observed if I replace guest additions with version 5.2.22. Versions 6.0.0 and 6.0.2 show exactly the same behavior.

Other read/write operations doesn't show any problem (at this time).

I've tried to investigate hanging I/O operation in Expedition PCB and with the Process Monitor (Sysinternals) found, that last unfinished call was '''QueryDirectory'''. This event description from ProcMon is

{{{
Date & Time:	17.01.2019 14:58:38
Event Class:	File System
Operation:	QueryDirectory
Result:	
Path:	\Device\VBoxMiniRdr\VBOXSVR\VM_Shared\KiberLock-NET\20190115\KibLck-NET_v1p0\PCB\.lck_dir\*.lckreq
TID:	4996
Duration:	
Filter:	*.lckreq
}}}

Call stack (reported by ProcMon) is

{{{
0	fltmgr.sys	FltRequestOperationStatusCallback + 0xe8f	0xca0b3df7	C:\Windows\system32\drivers\fltmgr.sys
1	fltmgr.sys	FltGetIrpName + 0xc56	0xca0b6d38	C:\Windows\system32\drivers\fltmgr.sys
2	fltmgr.sys	FltGetIrpName + 0x116f	0xca0b7251	C:\Windows\system32\drivers\fltmgr.sys
3	fltmgr.sys	FltGetIrpName + 0x162e	0xca0b7710	C:\Windows\system32\drivers\fltmgr.sys
4	ntkrnlpa.exe	IofCallDriver + 0x64	0xe323c117	C:\Windows\system32\ntkrnlpa.exe
5	ntkrnlpa.exe	NtSetEvent + 0x2c1	0xe3439f12	C:\Windows\system32\ntkrnlpa.exe
6	ntkrnlpa.exe	NtQueryDirectoryFile + 0x5b	0xe3444528	C:\Windows\system32\ntkrnlpa.exe
7	ntkrnlpa.exe	ZwYieldExecution + 0xf4e	0xe3242b8e	C:\Windows\system32\ntkrnlpa.exe
8	ntdll.dll	NtQueryDirectoryFile + 0xc	0x77825acc	C:\Windows\System32\ntdll.dll
9	KernelBase.dll	FindFirstFileExW + 0x276	0x7598b355	C:\Windows\System32\KernelBase.dll
10	KernelBase.dll	FindFirstFileA + 0x4a	0x7599a956	C:\Windows\System32\KernelBase.dll
11	xf_Os.dll	xf_Os.dll + 0x4f3d	0x10004f3d	C:\MentorGraphics\7.9.5EE\SDD_HOME\common\win32\lib\xf_Os.dll
}}}

And another similar hang event from ProcMon and another process, tried to call the '''WriteFile''':

{{{
Date & Time:	17.01.2019 16:02:08
Event Class:	File System
Operation:	WriteFile
Result:	
Path:	\Device\VBoxMiniRdr\VBOXSVR\VM_Shared\KIBERLOCK-NET\20190115\KIBLCK-NET_V1P0\database\cdbsvr\log\2019-01-17 16.02.07-1536\2019.01.17.txt
TID:	2648
Duration:	
Offset:	6,109
Length:	82
Priority:	Normal
}}}

Call stack is very similar to the '''QueryDirectory''' one:
{{{
0	fltmgr.sys	FltRequestOperationStatusCallback + 0xe8f	0xca0b3df7	C:\Windows\system32\drivers\fltmgr.sys
1	fltmgr.sys	FltGetIrpName + 0xc56	0xca0b6d38	C:\Windows\system32\drivers\fltmgr.sys
2	fltmgr.sys	FltGetIrpName + 0x116f	0xca0b7251	C:\Windows\system32\drivers\fltmgr.sys
3	fltmgr.sys	FltGetIrpName + 0x162e	0xca0b7710	C:\Windows\system32\drivers\fltmgr.sys
4	ntkrnlpa.exe	IofCallDriver + 0x64	0xe323c117	C:\Windows\system32\ntkrnlpa.exe
5	ntkrnlpa.exe	NtSetEvent + 0x2c1	0xe3439f12	C:\Windows\system32\ntkrnlpa.exe
6	ntkrnlpa.exe	NtWriteFile + 0x6fe	0xe3480994	C:\Windows\system32\ntkrnlpa.exe
7	ntkrnlpa.exe	ZwYieldExecution + 0xf4e	0xe3242b8e	C:\Windows\system32\ntkrnlpa.exe
8	ntdll.dll	ZwWriteFile + 0xc	0x7782659c	C:\Windows\System32\ntdll.dll
9	KernelBase.dll	WriteFile + 0x5f	0x759875ad	C:\Windows\System32\KernelBase.dll
10	kernel32.dll	WriteFile + 0x4e	0x768d56e4	C:\Windows\System32\kernel32.dll
11	msvcr90.dll	lseeki64 + 0x56b	0x71cc99ad	C:\Windows\winsxs\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\msvcr90.dll
12	msvcr90.dll	write + 0x9f	0x71cc9d37	C:\Windows\winsxs\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\msvcr90.dll
13	msvcr90.dll	fdopen + 0x1c0	0x71c8fea2	C:\Windows\winsxs\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\msvcr90.dll
14	msvcr90.dll	fflush_nolock + 0x1c	0x71c8fef0	C:\Windows\winsxs\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\msvcr90.dll
15	msvcr90.dll	fflush + 0x30	0x71c90030	C:\Windows\winsxs\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\msvcr90.dll
16	iCDBNetServer.exe	iCDBNetServer.exe + 0x47fe6d	0x87fe6d	C:\MentorGraphics\7.9.5EE\SDD_HOME\common\win32\bin\iCDBNetServer.exe

}}}


"	makc
3458	Shared Folders failing on access	Windows	VirtualBox 2.1.4	2009-03-01T09:08:51Z	2011-05-28T16:46:15Z	2011-05-28T16:46:15Z	"Ubuntu 8.10 64-Bit host, Windows XP SP3 32-Bit guest.

When accessing shared files on the shared folder, often the shared folders file access fails. This includes directory browsing, file access, file deletion, or other operations. Other times, the access works fine. The issue appears random - but generally occurs after inactivity. Shared folders have been shared as a Mapped Drive under XP.

I have disabled the Mapped Drive timeout (http://support.microsoft.com/kb/297684 = ""net config server /autodisconnect:-1""), and have also added 'vboxsvr' to the hosts file as 127.0.0.1 to try to solve the problem - no success.

Accessing files returns ""unknown error occurred while accessing [file]"".
Refreshing the directory after this failure results in ""E:\ is not accessible. The request is not supported.""
Refreshing the directory after a 'timeout', then the directory is displayed, and files are accessible again.

Logfile attached immediately after this issue occurred. VM was still running and active.

"	Robert
16572	shared folders can not be mount	Linux	VirtualBox 5.1.16	2017-03-16T06:32:30Z	2017-03-23T11:14:28Z	2017-03-23T11:14:28Z	"I use Linux Mint LMDE2 (Jessie) as Host with some Linux Guests.

Since VirtualBox 5.1.16 can shared folders not be mounted on the guests.
Until Version 5.1.14 its well done.
(5.1.18 don't work too) 

I gone back to 5.1.14 and it works fine."	Alex175
3340	Shared folder file creation/deletion not permitted on sub-folders, WinXP SP3 Guest	Windows	VirtualBox 2.1.2	2009-02-14T19:13:20Z	2010-09-07T04:11:34Z	2010-09-07T04:11:34Z	"Shared folder issues with Virtualbox 2.1.2 running in a ubuntu 8.10 box, with a WinXP SP3 guest.

The guest can access the shared folder: it shows up in ""My Network Neighbourhood"" and it shows as \VBOXSVR\MYFOLDER

Using the File Explorer in the guest, I can select files, and do Copy/Paste to obtain a copy of the file. I can delete files with no issue.

However, when attempting to do the same in a sub-folder (e.g.: in \VBOXSVR\MYFOLDER\MISC), then I get an error message:

""Cannot copy file: cannot read from the source file or disk""

or if I attempt to delete a file I get:

""Cannot delete file: cannot read from the source file or disk""

I can edit files in sub-folders with no problems. I just can not do file operations on them.

In Linux, the folder I am sharing is in an EXT3 partition. I double checked Permissions and they look all right and they look the same for the root of the folder and its sub-folders:

/media/sda6/MYFOLDER: drwxrwx---

/media/sda6/MYFOLDER/MISC: drwxrwx--- 

Note: if I map the shared folder to a Drive (say X:), the same problem occurs (but the error messages are slighly different).

I believe this started happening with VBox 2.0"	Ari
18616	Shared Folder error when using reposync	Linux	VirtualBox 6.0.6	2019-05-02T02:51:55Z	2019-05-07T05:39:21Z	2019-05-07T05:39:21Z	"I have a couple of VMs (specifically CentOS6 and CentOS7) that I use to sync repositories for a disconnected network. EPEL, Cloudera, MySQL, etc. I keep these VMs pretty lean and but mount Shared Folders to a USB so that I can transfer the files. I download the files in the repos directly to the Shared Folder. For example to update the EPEL6 repository. I cd into a directory on the Shared Folder and use the command, reposync -n -d -r epel6. Since 6.0.6 this causes errors. To test it I tried a created a new directory and here is a sample output from one of the first attempted download:

[jrather@localhost sat]$ reposync -n -d -r epel6
[epel6: 1     of 12532 ] Downloading Packages/2/2048-cli-0.9.1-1.el6.x86_64.rpm
Could not retrieve package 2048-cli-0.9.1-1.el6.x86_64. Error was failure: Packages/2/2048-cli-0.9.1-1.el6.x86_64.rpm from epel6: [Errno 256] No more mirrors to try.

I get errors on every file. If I try the command within a directory on the VM (for example, /tmp or my user's home directory) everything is fine. It is only with the Shared Folder or trying to write to it. This error occurs with the CentOS7 guest too. I have tried it from both CentOS7 host and Ubuntu 18.04 host both with Guest Additions installed. I have also tried using a physical disk for the Shared Folder instead of USB drive with the same results. This used to work fine with 6.0.4 and previous versions.

I am not sure what else to submit but would be more than happy to if instructed."	jim.rather
9219	Shared Folder Enhancement	other	VirtualBox 4.0.12	2011-07-17T21:35:30Z	2011-07-18T06:52:38Z	2011-07-18T06:52:38Z	"Would it be possible to implement a feature for Windows guests in the Shared Folders to allow a user to define the drive letter for the auto-mount to use when mapping the shared folder? This could also be useful for Linux guests being able to set where you want the shared folder to be mounted.

Thanks!"	TheShiv
13986	Shared folder accessible after removed from list of shared folders	all	VirtualBox 4.3.26	2015-03-25T16:00:08Z	2015-03-25T16:00:08Z	2015-03-25T16:00:08Z	"When removing a 'permanent' shared folder while it is mounted, it is removed from the list of shared folders but it's still fully accessible in the VM. There is a pop up warning that this will result in 'broken shared folder', which only offers to click 'OK'. The folder is even accessible after rebooting the guest system and host system. Tested this with Linux and Windows guest systems.

Steps to reproduce:
1. Add shared folder in shared folder settings, check 'Make Permanent'
2. Mount shared folder in guest system
3. Remove shared folder in shared folder settings"	A_Dombeck
16487	Shared Folder /copying an overwriting modified text file causes error on Ubuntu 16 guest	Linux	VirtualBox 5.1.14	2017-02-16T03:10:30Z	2017-02-16T03:10:30Z	2017-02-16T03:10:30Z	"== Summary ==
*copying an overwriting modified text file causes error on Ubuntu 16 guest
after overwriting, file contains invalid characters. (can be check with Ubuntu's gedit) and sometimes missing characters.
One thing I found weird is, if you open the modified file in the shared folder from guest, it doesn't contain any invalid characters. Invalid character problem only rise when the file is overwritten to the folder in guest env.

*copying an overwritten text file steps can be found under 'How to reproduce the problem'

== How to reproduce the problem ==
1. (host OR guest) create a text file from the host shared folder
2. (guest) copy the shared file to any folder
3. (host) modify the file and save (if you modify the file from guest, it won't happen)
4. (guest) copy the modified file and overwrite it

== Attach a (full) log file ==
see the attached log file

Thank you for the great SW!"	haku
20585	Shared Clipboard, guest win10 aborted, or host ubuntu cliboard hangs	Windows	VirtualBox 6.1.26	2021-09-30T01:41:22Z	2021-10-27T09:14:57Z	2021-10-27T09:14:57Z	"Host: Ubuntu 20.04
Guest: Windows 10
Shared clipboard: bidirectional

each time I copy text from pdf files opened in acrobat 2017 in the guest win 10, the host clipboard will hang. (VBox.log)

If I copy texts several times, the guest aborted. (VBox.log.2)

This problem starts at least from VB 6.0"	MaxChen
20366	Shared clipboard stops working on vm reboot when started headless => Fixed in SVN	Linux	VirtualBox 6.1.22	2021-05-13T21:37:44Z	2021-10-15T08:49:38Z	2021-10-15T08:49:38Z	"my setup and testing:

Running Virtualbox 6.1.22 on Ubuntu Server 20.04 with extension pack.  Ubuntu is fully patched.  I connect via RDP to VM console.

If I start a VM headless, shared clipboard works without issues.  Once I reboot the VM, shared clipboard stops working.

I have tested a Windows 10 VM and Mint Mate VM and both have the same issue.

I tested the freerdp client (compiled the latest source) and the Microsoft RDP client and get the same results.


I also installed Mint Mate on my test PC, then VirtualBox on that, and get the same result if I start the vm using vboxheadless.

I have attached log file from a test vm."	thedisbo1125
15715	Shared Clipboard not working with Windows 10	Windows	VirtualBox 5.1.2	2016-07-30T15:09:07Z	2016-07-30T15:09:07Z	2016-07-30T15:09:07Z	"I have VirtalBox 5.1.2 with a Windows 10 guest. 

After updating (in the guest) the Guest Additions to version 5.1.2 the shared clipboard isn't working anymore. If I re-install the Guest Additions 5.0.26 the shared clipboard works. 

So I assume it's a problem in the Guest Additions. (With the Guest Additions 5.1.0 the clipboard isn't working either.)

Specs:

Host: openSUSE 13.2 (64-Bit), VirtualBox 5.1.2

Guest: Windows 10 (version 1511, 64 Bit)"	tischuer
20808	shared clipboard does not work with Wayland	Windows	VirtualBox 6.1.32	2022-02-03T15:17:36Z	2022-02-03T15:47:13Z	2022-02-03T15:47:13Z	On Fedora 35 host with Win10Guest the shared clipboard works with X11, but not with Wayland.	JoKalliauer
16252	Share clipboard cause host copy and paste stuck	Windows	VirtualBox 5.1.10	2016-12-01T12:52:43Z	2016-12-02T17:15:48Z	2016-12-02T17:15:48Z	"Guest XP: Shared Clipboard is set to bidirectional

After a while (or one or more hour),  the copy and paste in host is not stable. If you select some text in google Chrome and copy, the page of Chrome suspended, even crash whole chrome.

when shutdown the guest, end program dialog: VBoxSharedClipboardClass

If the guest XP is shutdown, host clipboard works fluently.

If the disable the Shared Clipboard of guest, host clipboard works great.

Thus, I suppose that the problem is in the guest addition of virtualbox."	maxchen
18942	Severe UI rendering issues with QT 5.13.1	Windows	VirtualBox 6.0.12	2019-09-18T08:36:24Z	2019-10-27T21:30:23Z	2019-10-27T21:30:23Z	"After recent upgrade to QT 5.13.1 (probably on or around 15/09/2019) on SuSE Tumbleweed VirtualBox started behaving incorrectly when used on two monitors setup with enabled OS level UI scaling (1.6). Issue happens only on one of the monitors. I am using X11 Plasma with KDE.

When VirtualBox is launched the main window is displayed properly, however when it is resized to full screen (or majority of the screen) severe rendering issues start to show up. The top level menu (File/Machine/Help) disappears, the VM list disappears etc (please refer to the screenshot). 

When a VM is started and is displayed in full screen only part of the screen of the guest is visible (see screenshot).

When VBox windows are moved to the other display and are maximized everything is OK again.

Out of curiosity I tested the latest VBox beta version (VirtualBox-6.0-6.1.0_BETA1_133315_openSUSE150) and the issue is there too.
"	karolbe
15179	Severe time drift in guest OS	Linux	VirtualBox 5.0.14	2016-02-25T15:18:02Z	2017-03-27T18:51:09Z	2017-03-27T18:51:09Z	"Installed ubuntu 14 lts guest on centos7 virtualbox Version 5.0.14 r105127

ubuntu guest has latest version: 5.0.14r105127

everything is standard and updated.

Problem is that time drift is so extreme that i run into trouble.

the guest loses about 10 seconds every 15 minutes!

i already tried setting a ntp daemon.. but it does nothing.. also adding a crontab with ntpdate does nothing.

also adding --timesync-set-start --timesync-set-on-restore 1 --timesync-set-threshold 5000 to /etc/init.d/vboxadd-service does not help.


"	geegee
18094	Several bug on sound	Windows	VirtualBox 5.2.18	2018-11-01T17:04:57Z	2018-11-01T20:00:33Z	2018-11-01T20:00:33Z	"When i have played a sound and i stopped the playing,
this guest machine and host machine random freeze.

Can you solve this bug please ?
I join log .
"	Sizy458
8947	Serial port raw mode should use O_APPEND for the file	other	VirtualBox 4.0.8	2011-05-23T02:51:16Z	2016-08-22T09:41:00Z	2016-08-22T09:41:00Z	"When setting a serial port to output to a file, the file should be opened with the O_APPEND flag. This allows the user to insert markers into the file (using ""echo marker >> file"" from the host machine) that will not be overwritten by virtualbox.

This change should literally be a one-liner.

Shachar"	Shachar Shemesh
20154	Segmentation fault when running 5.10.x kernel as guest	Linux	VirtualBox 6.1.18	2021-01-25T14:22:00Z	2021-04-30T15:42:33Z	2021-04-30T15:42:33Z	"Running an up to date Ubuntu 20.04 as a guest upgraded to use the 5.10.9 Linux kernel using the instructions contained here as a guide.

Installed  VBoxGuestAdditions-6.1.18 which installed successfully.

Rebooted. Reboot fails  with segmentation fault.

"	Alex Kempshall
18679	Segmentation fault on startup up of `VirtualBox` under sway-wm using Wayland	other	VirtualBox 6.0.8	2019-05-29T10:13:08Z	2019-07-01T08:55:37Z	2019-07-01T08:55:37Z	"Hi,

// ENVIRONMENT & VERSIONS:

I am using sway as wayland compositor on an archlinux system. sway is started with the following environment variables:
   QT_QPA_PLATFORM=wayland
   QT_WAYLAND_DISABLE_WINDOWDECORATION=""1""
   QT_WAYLAND_FORCE_DPI=100
   QT_PLUGIN_PATH=/usr/lib/kde4/plugins/
   QT_AUTO_SCREEN_SCALE_FACTOR=0
   QT_QPA_PLATFORMTHEME=gtk3

community/virtualbox 6.0.8-2 [installed]
community/virtualbox-host-dkms 6.0.8-2 [installed]
extra/qt5-wayland 5.12.3-1 (qt qt5) [installed]

// PROBLEM

VirtualBox segfaults everytime:

 VirtualBox
[1]    8016 segmentation fault (core dumped)  VirtualBox

Please let me know if I can provide anything else.

Tormen"	tormen
16310	Segmentation fault in VirtualBox	Linux	VirtualBox 5.1.10	2016-12-20T19:14:15Z	2017-05-15T15:18:55Z	2017-05-15T15:18:55Z	"Hi there! My VirtualBox crash and can not use it!

There are the step to reproduce the step:
1) create a new VM
2) start it
3) when prompted for iso click on the browse icon
HERE IT CRASH!

Can you help me, please?
What can I check?
Which logs do you need?

Thanks,
Marco"	marco.fortina
17749	Segmentation fault in libQt5Widgets.so when trying to open preferences	Linux	VirtualBox 5.2.0	2018-05-10T06:31:13Z	2018-05-10T09:31:42Z	2018-05-10T09:31:42Z	"When I open Preferences (File->Preferences) a dialog window appears and then application crashes.

GUI is an package virtualbox-qt (5.1.34-dfsg-0ubuntu1.16.04.2) from Linux Mint's repository. In syslog I see messages like this:

""kernel: [ 6494.722842] VirtualBox[954]: segfault at 28000002c ip 00007fe52d0277b1 sp 00007ffd04fb9380 error 4 in libQt5Widgets.so.5.5.1[7fe52cbfe000+659000]""

I tried reinstall all it but it not helps. Application I have downloaded directly from virtualbox.org works fine. Seems, its GUI doesnt use qt.

My version Linux is Mint 18.3 x64

"	akerka
16351	Segfault on Wayland, QTBUG-55583	other	VirtualBox 5.1.12	2017-01-03T15:19:08Z	2017-01-03T15:19:08Z	2017-01-03T15:19:08Z	"The GUI would often crash with this error on Wayland (I am on Fedora 25, but other people reported it on Arch as well):

{{{
(VirtualBox:13367): Gdk-WARNING **: gdkwindow-x11.c:5573 drawable is not a native X11 window
zsh: segmentation fault  virtualbox
}}}

For instance, trying to add the extension pack always leads to this crash, when clicking on the file system browsing arrow.

The issue has been patched in QT : http://zashikiro.hateblo.jp/entry/2016/11/28/005916

Several reports do exist all around (http://zashikiro.hateblo.jp/entry/2016/11/28/005916), but I guess this must be fixed upstream.

"	phocean
19560	Segfault on vm start when 3d acceleration is enabled	all	VirtualBox 6.1.6	2020-05-05T16:54:31Z	2020-05-17T15:36:07Z	2020-05-17T15:36:07Z	"Host: Fedora 32 x86_64
VirtualBox 6.1.6 rpmfusion

VirtualBoxVM segfaults on start if 3d acceleration is enabled (Windows guest with VBoxSVGA driver or Linux guest with VMSVGA). I managed to get some backtrace:
#0  0x00007f0afb2f7bb7 in ShaderInitLib () at /usr/lib64/virtualbox/VBoxSVGA3D.so
#1  0x00007f0b185e8abd in vmsvga3dPowerOn(PDMDEVINSR3*, VGAState*, VGASTATER3*) () at /usr/lib64/virtualbox/VBoxDD.so
#2  0x00007f0b185d5ae9 in vmsvgaR3PowerOn(PDMDEVINSR3*) () at /usr/lib64/virtualbox/VBoxDD.so
#3  0x00007f0b185603d4 in vgaR3PowerOn(PDMDEVINSR3*) () at /usr/lib64/virtualbox/VBoxDD.so
#4  0x00007f0b48d4a387 in PDMR3PowerOn () at /usr/lib64/virtualbox/components/VBoxVMM.so
#5  0x00007f0b48d96e68 in vmR3PowerOn(VM*, VMCPU*, void*) () at /usr/lib64/virtualbox/components/VBoxVMM.so
#6  0x00007f0b48da0814 in vmmR3EmtRendezvousCommon(VM*, VMCPU*, bool, unsigned int, int (*)(VM*, VMCPU*, void*), void*) () at /usr/lib64/virtualbox/components/VBoxVMM.so
#7  0x00007f0b48da441e in VMMR3EmtRendezvousFF () at /usr/lib64/virtualbox/components/VBoxVMM.so
#8  0x00007f0b48d9c33d in vmR3EmulationThreadWithId(RTTHREADINT*, UVMCPU*, unsigned int) () at /usr/lib64/virtualbox/components/VBoxVMM.so
#9  0x00007f0b6b9d8044 in rtThreadMain () at /usr/lib64/virtualbox/VBoxRT.so
#10 0x00007f0b6ba8e66e in rtThreadNativeMain(void*) () at /usr/lib64/virtualbox/VBoxRT.so
#11 0x00007f0b6bd7a432 in start_thread () at /app/lib64/libpthread.so.0
#12 0x00007f0b6bca19d3 in clone () at /app/lib64/libc.so.6

VBoxTestOGL shows success
"	Max Fedotov
19031	Segfault on Fedora 30.	all	VirtualBox 6.0.12	2019-10-19T17:44:04Z	2020-02-09T17:18:58Z	2020-02-09T17:18:58Z	"I am running Fedora 30 on a machine with 128 GB RAM and a GeForce RTX 2080 video card. I recently upgraded to a very high resolution and large monitor (49"" 5120x1440). Since then, virtualbox will not start.

When I run on the commandline, I get the following error, before any graphical interface is displayed (i.e., before I can even try to boot a guest OS):


{{{
% virtualbox
(VirtualBox:33239): librsvg-WARNING **: 10:36:43.169: cannot render on a cairo_t with a failure status (status=""invalid value (typically too big) for the size of the input (surface, pattern, etc.)"")
Segmentation fault (core dumped)
}}}

I've used the Fedora package manager to make sure I have the most recent version available through that source (VirtualBox-6.0.12). 

"	mopomi
19652	Segfault in vmsvgaR3PortReportMonitorPositions (vboxvga)	Linux	VirtualBox 6.1.10	2020-06-10T07:10:01Z	2020-06-10T07:31:31Z	2020-06-10T07:31:31Z	"Linux with 4.2.0 kernel (Astra Linux 1.5) crashes VM upon login with legacy vboxvga controller. Host: Fedora 32, guest: Astra Linux 1.5

{{{
#0  0x00007f0aeb03ad7e in vmsvgaR3PortReportMonitorPositions(PDMIDISPLAYPORT*, unsigned int, RTPOINT*) () from /usr/lib64/virtualbox/VBoxDD.so
No symbol table info available.
#1  0x00007f0b325a79b8 in Display::i_handleUpdateMonitorPositions(unsigned int, RTPOINT*) () from /usr/lib64/virtualbox/components/VBoxC.so
No symbol table info available.
#2  0x00007f0b325ca018 in vmmdevUpdateMonitorPositions(PDMIVMMDEVCONNECTOR*, unsigned int, RTPOINT*) () from /usr/lib64/virtualbox/components/VBoxC.so
No symbol table info available.
#3  0x00007f0aeaffe7b1 in vmmdevRequestHandler(PDMDEVINSR3*, void*, unsigned short, unsigned int, unsigned int) () from /usr/lib64/virtualbox/VBoxDD.so
No symbol table info available.
#4  0x00007f0b38310922 in IOMIOPortWrite () from /usr/lib64/virtualbox/components/VBoxVMM.so
No symbol table info available.
#5  0x00007f0b38208be2 in IOMR3ProcessForceFlag () from /usr/lib64/virtualbox/components/VBoxVMM.so
No symbol table info available.
#6  0x00007f0b381ff4e5 in emR3HighPriorityPostForcedActions () from /usr/lib64/virtualbox/components/VBoxVMM.so
No symbol table info available.
#7  0x00007f0b38202ef2 in emR3HmExecute () from /usr/lib64/virtualbox/components/VBoxVMM.so
No symbol table info available.
#8  0x00007f0b38200c4e in EMR3ExecuteVM () from /usr/lib64/virtualbox/components/VBoxVMM.so
No symbol table info available.
#9  0x00007f0b382635f0 in vmR3EmulationThreadWithId(RTTHREADINT*, UVMCPU*, unsigned int) () from /usr/lib64/virtualbox/components/VBoxVMM.so
No symbol table info available.
#10 0x00007f0b54e17f14 in rtThreadMain () from /usr/lib64/virtualbox/VBoxRT.so
No symbol table info available.
#11 0x00007f0b54ece55e in rtThreadNativeMain(void*) () from /usr/lib64/virtualbox/VBoxRT.so
No symbol table info available.
#12 0x00007f0b551b9432 in start_thread () from /app/lib64/libpthread.so.0
No symbol table info available.
#13 0x00007f0b550e09d3 in clone () from /app/lib64/libc.so.6
No symbol table info available.
}}}
"	Max Fedotov
14626	segfault Host Ubuntu 15.04 64bit on libQtGui.so, Client Windows 8.1 64bit	Windows	VirtualBox 5.0.4	2015-09-23T12:57:33Z	2015-09-24T07:36:45Z	2015-09-24T07:36:45Z	"Working nicely on Ubuntu 15.04 (64bit), then after 1 hour it crashes:

[61110.818729] VirtualBox[2470]: segfault at 0 ip 00007fcf16f168f4 sp 00007ffcb35f3720 error 6 in libQtGui.so.4.8.6[7fcf16bc8000+aac000]"	jabenitezg2
18497	Segfault due to audio driver	Windows	VirtualBox 6.0.4	2019-03-15T15:04:17Z	2019-05-18T14:48:15Z	2019-05-18T14:48:15Z	"Windows guest is crashing within minutes after starting. The crash is reproducible on Ubuntu 18.10 and 19.04 (daily build). Also reproducible in current test build of virtualbox.
Issue occurs when:
1. Audio output is enabled and host driver / audio controller combination results in valid sound within guest os.
2. Virtualbox guest additions are installed. 

Audio input does not seem to effect the problem. Disabling microphone in hard- or software has no difference.

Logs:

Output in syslog:
{{{
Mar 15 15:37:32 m-7223 kernel: [ 3061.086031] EMT-3[28881]: segfault at 7f4a46dfcfec ip 00007f4a8b7b9594 sp 00007f4a46efb8c8 error 4 in libc-2.29.so[7f4a8b655000+173000]
Mar 15 15:37:32 m-7223 kernel: [ 3061.086048] Code: 0e 88 0f c3 c5 fa 6f 06 c5 fa 6f 4c 16 f0 c5 fa 7f 07 c5 fa 7f 4c 17 f0 c3 48 8b 4c 16 f8 48 8b 36 48 89 4c 17 f8 48 89 37 c3 <8b> 4c 16 fc 8b 36 89 4c 17 fc 89 37 c3 0f b7 4c 16 fe 0f b7 36 66
}}}

No relevant log in (guest) windows event viewer.
Audio debug logs and VBox.log are attached."	06b7e
11577	Secure Boot doesn't allow 'vboxdrv' module to load (now works for Ubuntu and Debian 10+ hosts)	all	VirtualBox 4.2.8	2013-03-10T18:16:18Z	2022-06-01T09:54:37Z	2022-06-01T09:54:37Z	"Host - Fedora 18 64 bit
Bios has Secure Boot enabled.

When I try to start any machine it says:


{{{
Kernel driver not installed (rc=-1908)

The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing

'/etc/init.d/vboxdrv setup'

as root. If it is available in your distribution, you should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary.
}}}


{{{
[user@localhost ~]$ sudo /etc/init.d/vboxdrv setup
[sudo] password for user: 
Stopping VirtualBox kernel modules                         [  OK  ]
Uninstalling old VirtualBox DKMS kernel modules            [  OK  ]
Trying to register the VirtualBox kernel modules using DKMS[  OK  ]
Starting VirtualBox kernel modules                         [FAILED]
  (modprobe vboxdrv failed. Please use 'dmesg' to find out why)

}}}


{{{
[user@localhost ~]$ sudo modprobe vboxdrv
modprobe: ERROR: could not insert 'vboxdrv': Required key not available
}}}
"	Quickbooks Office
16012	Second Monitor disappears	Windows	VirtualBox 5.1.6	2016-10-02T15:59:30Z	2016-10-02T16:44:02Z	2016-10-02T16:44:02Z	"Second monitor goes black a couple times a day. Unknown trigger. Can be brought back from black screen by pressing Ctrl-F twice (in and out of fullscreen) or by going into the Windows guest resolution properties and slightly adjusting the alignment of the monitor and applying.

Black screen is still in Guest realm as meta windows key still launches guest start menu in the working 1st monitor.

Host Ubuntu 14.04
Guest Windows 7

Very similar to defect #15448 but that one has Host as Win 10, and talks about the taskbar in the host not showing the correct number of instances. In my case in fullscreen the correct number of instances are shown in the host taskbar."	msorel
15499	seamless mode works only on laptop screen	Windows	VirtualBox 5.0.20	2016-06-10T17:40:19Z	2016-06-10T17:40:19Z	2016-06-10T17:40:19Z	"I have found that using seamless mode in Fedora and Ubuntu will result in the screen going seamless on the laptop's display only. I have three screens - the laptop screen and two external monitors (via a docking station) in that order:
    laptop screen <--> lcd panel 1 <--> lcd panel 2

I have set my ""middle"" monitor (lcd panel 1) to be the main window however no matter what I do I've not found a way to go seamless and have the seamless display on the monitor of my choosing.

An interesting note is that the desktop manager ""cinnamon"" - DOES work properly. I can move the non-seamless window to whichever screen I choose, use HOST+l to go seamless and it'll be seamless on the monitor that the non-maximized guest OS was on. (this does have some interesting quirks too but it works > 90% of the time pefectly)

It's been a bug for as long as I've used virtualbox (a long time) and I've seen the bug all through the later 4.x and now in the 5.x product.

"	dovholuk
20317	Seamless Mode Windows 10	Windows	VirtualBox 6.1.18	2021-04-23T06:32:08Z	2021-04-23T06:32:08Z	2021-04-23T06:32:08Z	"I am running OpenSuse Leap 15.1 as the host and Windows 10 Pro as a guest. If my guest operating system Windows 10 switches to Seamless Mode Host + L, only windows that are not integrated Windows applications are displayed correctly. The taskbar disappears when, for example, I click Start. Windows windows are only visible if an application that is not provided for Windows is open on the desktop and serves as a background. My VirtualBox version is 6.1.18 r142142 (Qt5.12.7).
Guest additions and the current Extensions Pack are also installed.
As a guest I also have a Windos7 Pro operating system and everything works perfectly!"	Compaq
8192	seamless mode problems when moving/minimizing guest's windows	Windows	VirtualBox 4.0.2	2011-01-26T23:29:38Z	2011-01-26T23:29:38Z	2011-01-26T23:29:38Z	"Host: Ubuntu 11.04
Guest: Windows XP SP3

Host system is dual-head (two 1680x1050 LCD panels), Compiz disabled (by selecting ""None"" for Visual Effects in the Appearance Preferences panel).

VBox is configured for 2 virtual monitors. Windows reports 2 monitors as it should, and is configured to extend desktop onto the second monitor.

I normally run this VM in seamless mode. Works well most of the time. Sometimes when I move or minimize a guest window, there is a rectangular area left behind (same size as the moved/minimized guest window) showing the guest's desktop background. This area will cover up host windows if the guest window was on top of them.

This does not happen all the time. Seems to happen more often on second monitor, but does happen on first monitor sometimes.

In order to recover, I usually have to switch out of seamless mode and back in. Sometimes moving around other guest windows or clicking in another guest window will fix it.
"	Chuck Cox
13534	Seamless mode on secondary monitor mimics resolution of primary monitor since 4.3.18	Windows	VirtualBox 4.3.18	2014-10-21T09:32:40Z	2015-05-28T11:52:52Z	2015-05-28T11:52:52Z	"After upgrading from 4.3.16-95972 to 4.3.18 r96516 I'm facing a (for me) severe usage problem with seamless mode in combination with my multi-monitor setup.

=== MY SETUP ===
A laptop (15"" 1600x900) with a large monitor (24"" 1920x1200) as secondary monitor. I would run a Win guest on the large, secondary screen in seamless mode, so my Cinnamon taskbars & menus are on my laptop screen, my Win7 bar is on the bottom of my 2nd monitor.

=== THE PROBLEM ===
As of 4.3.18 the seamless mode mimics the height of the primary monitor (900px) though taking the whole width. Fullscreen mode still works as expected and takes up the whole secondary screen. 

More oddly, in seamless mode the 900px frame is positioned somewhere in the middle of the screen giving my a flying taskbar and VBox Toolbar.

I always faced a problem that the VBox Toolbar menues appears with a vertical offset to the actual toolbar hover (something like 300px below). But I think this is rather a Gtk issue which I can tackle.

Downgrading restored the seamless mode for me."	vBen
9353	Seamless mode is broken on Linux host with Openbox and composite manager	other	VirtualBox 4.1.0	2011-07-30T18:36:12Z	2011-07-30T18:43:07Z	2011-07-30T18:43:07Z	"Seamless mode is completely broken with any composite manager enabled while using Openbox. I have tried using compiz as its own wm and seamless mode works fine on the same machine. 

What happens is that the rest of the screen shades/seems to be overlayed by VB when entering seamless mode. I am attaching a screenshot as that explains things best. Moving a window just causes it to be smeared within its own outline. Switching desktops and coming back will clear up the screen but only till the next time one needs to interact with the window.

I am using kernel 2.6.39 on an Archlinux x64 host. The guest is Windows xp. Both 3d and 2d are disabled for the guest. I am also attaching the vbox log in case it has something useful to show. "	rsk02
19150	Seamless mode hides mini ToolBar	Windows	VirtualBox 6.1.0	2019-12-12T21:02:11Z	2019-12-12T21:02:11Z	2019-12-12T21:02:11Z	"This bug goes back to VB 5.2, if memory serves.  It was fixed in 6.1 RC1, so I thought ""great!"", but in the 6.1 release, the problem has returned.

On Solaris, Linux, and FreeBSD (BSD using the OSE release) hosts, when a VMs is in seamless mode (like Win 7 and these same Linux/UNIX variants), the VB mini ToolBar is hidden behind the guest's toolbar if they are on the same edge of the screen.  There is no way to bring it forward, even if you set your guest to auto-hide its toolbar.

Attached log is from Windows 7, but it also happens with other guests that have a desktop that works well with seamless mode, like MATE or Gnome2.

This also happens if I use 6.1.0 with the 6.1.0RC1 guest additions."	bq
2720	Seamless mode has issues on dual head hosts	Windows	VirtualBox 3.0.2	2008-12-06T12:51:56Z	2016-04-06T23:23:28Z	2016-04-06T23:23:28Z	"I'm using 2 monitors, configured via xrandr --output VGA --below LVDS.
When switching on seamless mode, vbox hides and I see black screen, (no any output), but I can press Home+L - and return to previous mode."	Maksim Melnikau
18711	SCSI port 7 can not be used	Linux	VirtualBox 5.2.30	2019-06-15T08:59:45Z	2019-06-16T13:34:02Z	2019-06-16T13:34:02Z	"[root@rac01-priv ~]# lsscsi -d
[0:0:0:0]    disk    ATA      VBOX HARDDISK    1.0   /dev/sda [8:0]
[2:0:0:0]    disk    VBOX     HARDDISK         1.0   /dev/sdb [8:16]
[2:0:1:0]    disk    VBOX     HARDDISK         1.0   /dev/sdc [8:32]
[2:0:2:0]    disk    VBOX     HARDDISK         1.0   /dev/sdd [8:48]
[2:0:3:0]    disk    VBOX     HARDDISK         1.0   /dev/sde [8:64]
[2:0:4:0]    disk    VBOX     HARDDISK         1.0   /dev/sdf [8:80]
[2:0:5:0]    disk    VBOX     HARDDISK         1.0   /dev/sdg [8:96]
[2:0:6:0]    disk    VBOX     HARDDISK         1.0   /dev/sdh [8:112]
[2:0:8:0]    disk    VBOX     HARDDISK         1.0   /dev/sdi [8:128]
[2:0:9:0]    disk    VBOX     HARDDISK         1.0   /dev/sdj [8:144]
[2:0:10:0]   disk    VBOX     HARDDISK         1.0   /dev/sdk [8:160]

As you can see, when I attach disks to SCSI controller, I can never use the 7th one:  [2:0:7:0]. My OS is oracle linux 7.6"	Nil
14899	Screen resolution defaults to 1024x768 and not to the selected before the reboot	Windows	VirtualBox 5.0.10	2015-12-04T13:07:37Z	2015-12-04T13:07:37Z	2015-12-04T13:07:37Z	"Dear Support,

A guest Windows 7 system defaults to 1024x768 screen resolution and not to the previously selected before the reboot. It is not clear under what circumstances the resolution is not kept between the reboots. It is not reproduced all the time."	Panos Kavalagios
10620	screen locks in host OS, despite actively working in fullscreen guest OS	Windows	VirtualBox 4.1.14	2012-05-29T16:48:22Z	2017-03-20T18:17:18Z	2017-03-20T18:17:18Z	"I am running Ubuntu 12.04 (64 bit) as the host OS and Windows 7 (64 bit) as the guest OS (in fullscreen mode). If I work long enough in the Windows 7 environment and then go back to my host OS (using cube rotate in compiz), the host OS presents my desktop for 1-2 seconds and then locks the screen with a password lock screen. Once I enter my password, the screen is then unlocked and I can proceed to work in Ubuntu.

This is easily repeatable and was not the case when running Windows XP (32 bit) as a guest OS on Ubuntu 10.04 (64 bit host OS). Previous releases kept the host OS from locking, despite working in the guest OS. If no actions were taking place in the guest OS, then the host OS would lock, after the predetermined time period for locking a screen would pass."	sf_basilix
19960	Screen distorted Windows7 guest on Kubuntu 18.04 host	Windows	VirtualBox 6.1.14	2020-10-12T04:10:31Z	2020-10-12T04:10:31Z	2020-10-12T04:10:31Z	"After upgrading to 6.1.12 found guest display distorted. Had to downgrade back to 6.1.10.
However, have now also found the same problem in 6.1.14 and 6.1.15.  --> see attached screenshots.
This is on Lenovo T430s running Kubuntu 18.04 as the host.
Guest: Windows7 Home Premium

The interesting thing is even after downgrading back to 6.1.10 the problem still appeared until Extension pack 6.1.10 was re-installed. - During installation screen flickered and reverted back to normal operation."	KarlS
20997	Scancode returned by int15h call in BIOS keyboard handler(int09h) is ignored.	other	VirtualBox 5.2.34	2022-06-21T09:50:25Z	2022-06-21T09:50:25Z	2022-06-21T09:50:25Z	"Keyboard scancode is handled as below:[[BR]]
'''in int09_handler''' ( src/VBox/Devices/PC/BIOS/orgs.asm )[[BR]]
(step1) get a scancode from keyboard hardware.[[BR]]
(step2) execute pusha(save the scancode in al into the stack).[[BR]]
(step3) call int15h(ah=04fh) to be able to modify the scancode.[[BR]]
(step4) call _int09_function to process the scancode.[[BR]]
[[BR]]
'''in int09_function''' ( src/VBox/Devices/PC/BIOS/keyboard.c )[[BR]]
(step5) get the scancode from the stack saved at (step2)[[BR]]
[[BR]]
So, the scancode modified at (step3) is ignored.[[BR]]
[[BR]]
Here is the code snippet(from VirtualBox-6.1.34.tar.bz2):[[BR]]
{{{
[src/VBox/Devices/PC/BIOS/orgs.asm]
  int09_handler:
          ...
          in      al, KBC_DATA  ;(step1)
          push    ds
          DO_pusha      ;<===(step2) save scancode in AL
          cld
          mov     ah, 4Fh
          stc
          int     15h   ; (step3)
          ...
  int09_process_key:
          push    es
          C_SETUP
          call    _int09_function ; (step4)

[src/VBox/Devices/PC/BIOS/keyboard.c]
  void BIOSCALL int09_function(uint16_t ES, uint16_t DI, uint16_t SI, uint16_t BP, uint16_t SP,
                               uint16_t BX, uint16_t DX, uint16_t CX, uint16_t AX)
  {
    ...
    scancode = GET_AL();  // <===(step5) get scancode from the stack

[src/VBox/Devices/PC/BIOS/biosint.h]
  #define BIOSCALL    __cdecl
  #define GET_AL() ( AX & 0x00ff )

}}}
"	Yamu
17317	scaled mode in ubuntu 17.10	Linux	VirtualBox 5.2.0	2017-11-27T15:25:10Z	2017-11-27T15:25:10Z	2017-11-27T15:25:10Z	"Depending on the state (seems scaled first). when going back to normal mode, the VM 
is not responsive to keystrokes.  They appear to buffer, when returning to scaled mode 
they will then show up.

Speculation is on the new WM that comes with 171.0

Saw with with 5.1.28, 5.2.0 and 5.2.2"	chad
20247	save machine state to disk and when resume the window is the smallest possible	Windows	VirtualBox 6.1.18	2021-03-11T22:57:46Z	2021-03-11T22:57:46Z	2021-03-11T22:57:46Z	"When you close a virtualbox window you are asked how you want to close it. If I ""save the state"" of the vm to disk and then some time in the future resumes the machine...

Windows guest: ... often when the host cpu is heavily loaded the window becomes the smallest possible (640x480) upon resume. I need manually select the window size I want. The faulty window size is otherwise saved and used during next cold start of the guest.

Linux/Windows guests: The preview in the Virtualbox Manager became strange for the Linux guest. So did the windows preview too, but since the window (for the windows guest) resized this was temporarily.

Mainly a windows' guest type error.


"	Mrpn
12495	Sampling profiling method not usable in Visual Studio 2013	Windows	VirtualBox 4.3.4	2013-12-16T16:59:36Z	2016-10-30T10:56:59Z	2016-10-30T10:56:59Z	"Windows 7 Enterprise SP1 x86 guest (VM from Microsoft's http://modern.ie/ site), Lubuntu 11.10 x86-64 host. Laptop CPU Intel Core 2 Duo T8100. VM is set to use one CPU core.

I installed Visual Studio 2013 and am trying to use its profiling feature. However the ""sampling"" mode doesn't work. I can launch the executable to be profiled, but on exiting it Visual Studio reports that no samples were captured.

This bug report is to suggest that support for whichever CPU performance counters or timer hardware that Visual Studio profiling uses, be added to VirtualBox.

I found an MSDN blog post about profiliing in virtual environments:
http://blogs.msdn.com/b/mgoldin/archive/2010/01/09/visual-studio-profiler-in-virtual-environment.aspx
That mentions VS 2010, so I assume VS 2012 and VS 2013 have the same issue. According to that post, Visual Studio has specific support for VMWare, Virtual PC and Hyper-V VMs.
""Visual Studio profiler usage on virtual machines was limited so far, as it didn’t support Sampling mode in such environment. I’m glad to note that in Visual Studio 2010 you can sample your applications inside of virtual machines. VMs could be created using either VPC, VMWare of Hyper-V technologies. 
Some hardware is not virtualized, though, and CPU performance counters (that are used by profiler) are, unfortunately, in the list. To overcome the issue, we used a different approach that targets each VM-vendor specifically, and timers that are used in virtual world are not the same as on a raw hardware. Some functionality, however, suffers from lack of CPU performance counters virtualization.""

Also a comment at
   http://serverfault.com/questions/194585/visual-studio-profiler-in-virtual-machine 
mentions that profiling uses the Local APIC timer.
"	Donuts
9723	same disk boots with fullDevice, but not with partitionedDevice	Linux	VirtualBox 4.1.2	2011-10-08T20:53:59Z	2011-10-08T20:53:59Z	2011-10-08T20:53:59Z	"i've recently started to use vbox with debian stable, don't remember which version, and then switched to debian unstabe because of unsupported hw. with that vbox got upgraded to 4.1.2_Debian r38459

what i'm doing and what used to work before this:
 - i boot/attach the physical disk to the guest
 - to avoid screwing up the boot fs, i replace its FLAT entry to ZERO in the vmdk file

after the upgrade it stopped working: grub hangs before it could bring up the menu. so, while searching for a workaround, i switched to using the whole disk, and then everything works fine. but just now i f***d up my hypervisor, because vbox opened a warning window and grabbed my keyboard and i couldn't get to grub within the default 5 secs, and it booted the already booted linux... ARGH!

the command i use to create the virtual disk:
VBoxManage internalcommands createrawvmdk -filename /opt/virtualbox-images/sda.vmdk -rawdisk /dev/disk/by-id/ata-KINGSTON_SNVP325S2256GB_30LS10FHT74Z -partitions 1,2,3,5,6,7

i'm attaching my current, edited version of the vmdk, but the same happens with the original, unedited one.

one unusual thing is that my partitions in the partition table are not in disk layout order."	attila.lendvai
15905	Running Windows 10 as a guest in Xubuntu 16.04.1 host freezes the machine (3D-related)	Windows	VirtualBox 5.1.4	2016-09-08T08:24:46Z	2017-08-17T15:12:28Z	2017-08-17T15:12:28Z	"While attempting to boot a Windows 10 guest on Xubuntu 16.04.1 host, as soon as the Windows logo and the dots running in a circle appear, the whole system hangs. Nothing can be done except pressing the physical power button to shut down the machine.

At first I thought this is related to https://www.virtualbox.org/ticket/13795, but that ticket tells the problem has been fixed already for 5.0.2 and my version is 5.1.4 directly from vbox repository.

I found somewhere that adding `nosmap` to kernel parameters would work, and once I managed to boot the guest system up. Today it didn't help.

I'm attaching the VBox.log, hopefully it helps. In it you will see that guest additions are from an older version. The guest OS was used in an older version (Ubuntu repository version 5.0.24-dfsg-0ubuntu1.16.04.1), but it shouldn't affect this as during the aforementioned time I managed to run the system, it informed me about this but didn't prevent the usage at all.

My setup:

{{{
jaska@ardbeg:~ 11:15:31 $ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 16.04.1 LTS
Release:	16.04
Codename:	xenial

jaska@ardbeg:~ 11:16:37 $ uname -a
Linux ardbeg 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:01:55 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

jaska@ardbeg:~ 11:17:42 $ apt-cache policy virtualbox-5.1
virtualbox-5.1:
  Installed: 5.1.4-110228~Ubuntu~xenial
  Candidate: 5.1.4-110228~Ubuntu~xenial
  Version table:
 *** 5.1.4-110228~Ubuntu~xenial 500
        500 http://download.virtualbox.org/virtualbox/debian xenial/contrib amd64 Packages
        100 /var/lib/dpkg/status
}}}"	astraljava
16070	Running Virtualbox over a VNC connection	Windows	VirtualBox 5.1.6	2016-10-14T17:37:58Z	2016-10-21T15:21:23Z	2016-10-21T15:21:23Z	"Attempting to run a VirtualBox guest over a VNC connection to a Linux host (xfce4 desktop for remote VNC session; Mint 18 / cinnamon desktop for native login). After completing the Windows 7 guest splash screen, the guest session aborts. When logged directly into the host system (no VNC), the guest boots up without issue. The guest can be started remotely in headless mode, and accessed through the emulated RDP interface.  So I believe this has something to do with the guest video/display settings interfacing correctly with VNC or the underlying X-session?
Virtualbox .log file is  attached to this ticket.  Core dump file is available through the dropbox link below:
https://www.dropbox.com/s/b7a799cktnp8trn/core.W7TestMachine-2016-10-13-23-33-47?dl=0"	otobyt
17155	Running VirtualBox on Ubuntu 17.04 with guest Ubuntu 16.04 crashes VM during apt-get update	Linux	VirtualBox 5.1.28	2017-10-11T09:43:03Z	2017-10-12T12:41:54Z	2017-10-12T12:41:54Z	"I setup a pretty empty VM of Ubuntu 16.04 inside of a host 17.04 running VirtualBox.

When executing the command `sudo apt-get update` the VM crashes and goes into ""aborted"" state.  There appears to be no work-around, and nothing in the apt logs of interest.

Seems similar to this StackOverflow post:
https://stackoverflow.com/questions/30889170/vagrant-enters-aborted-state-during-apt-get-update

The process to create my VM is using Packer, extending a base image from:
https://app.vagrantup.com/box-cutter/boxes/ubuntu1604

and then running a few file copy commands, and then finally ""sudo apt-get update"" and partway through the update the VM vanishes, and is in ""Aborted"" state.

The same VM builds fine on Mac OSX as the host, but fails when Ubuntu is the host.  
"	apatrida
15487	Running Linux guest caused udisksd to fail host mounts	Linux	VirtualBox 5.0.20	2016-06-07T14:57:47Z	2016-06-07T15:30:18Z	2016-06-07T15:30:18Z	"Running a Linux guest (freshly installed Mageia 5) to help gather data for a Mageia 5 bug report dealing with installation.  Left the VM running overnight, and this morning was trying to mount some HDs, only to see /var/log/messages such as this:

Jun  7 10:17:39 prf kernel: EXT4-fs (sdb7): mounted filesystem with ordered data mode. Opts: (null)
Jun  7 10:05:24 prf udisksd[1666]: Error statting /dev/sdc5\040(deleted): No such file or directory
Jun  7 10:05:24 prf udisksd[1666]: Error statting /dev/sde5\040(deleted): No such file or directory
Jun  7 10:05:24 prf udisksd[1666]: Error statting /dev/sdc5\040(deleted): No such file or directory
Jun  7 10:05:24 prf udisksd[1666]: Error statting /dev/sde5\040(deleted): No such file or directory
Jun  7 10:05:24 prf systemd[1]: Unit mnt-hd.mount entered failed state.

The mount command on the host appeared to work (no error reported on konsole).

Shut down the guest and host mounts started working again with no other interaction...
Restarting guest to see if this is repeatable...  [not yet]

Looks like I will have to leave guest running for a while to see if this repeats.

"	Pierre Fortin
16835	rtlogFlush: Potential null pointer dereference	all	VirtualBox 5.1.22	2017-06-16T13:36:42Z	2017-06-21T12:12:33Z	2017-06-21T12:12:33Z	"Function rtlogFlush() in vboxguest/common/log/log.c performs a paronoid check:
{{{
    /*
     * If the ring buffer is active, the other destinations are only written
     * to when the ring buffer is flushed by RTLogFlush().
     */
    if (   (pLogger->fDestFlags & RTLOGDEST_RINGBUF)
        && pLogger->pInt
        && pLogger->pInt->pszRingBuf /* paraoia */)
    {
        rtLogRingBufWrite(pLogger->pInt, pLogger->achScratch, pLogger->offScratch);
        pLogger->offScratch = 0; /* empty the buffer. */
    }
    else ... 
}}}   
This implies that pLogger->pInt could be NULL (even if this is an unlikely paranoid case). In the else path we have the following code that dereferences pLogginer->pInt and hence we may have a NULL pointer deference:
{{{
        if (pLogger->pInt->pfnFlush)
            pLogger->pInt->pfnFlush(pLogger);
}}}
I guess this is unlikely, but I think it would be good to correctly sanity check this for this corner case."	ColinIanKing
16312	RPM upgraid fails when VBoxSVC --auto-shutdown is running	other	VirtualBox 5.1.12	2016-12-22T04:44:18Z	2016-12-22T04:44:18Z	2016-12-22T04:44:18Z	"When trying to upgrate VirtualBox with yum/rpm, the first attempt fails if VBoxSvc --auto-shutdown is running.  The preinstall script shuts down services, but only waits 1 second for VBoxSVC to terminate, when it takes closer to 10 (which is documented in the error message, but the script doesn't take into account!).  Thus the upgrade fails, but works if you try again after the service terminates.

The solution is to chane the 'sleep 1' on line 103 of /usr/lib/virtualbox/routines.sh to 'sleep 10' (or do a loop checking ever second for 10 seconds, or something like that).

{{{
# yum update
Loaded plugins: aliases, auto-update-debuginfo, changelog, fastestmirror, filter-data, keys, list-data, merge-conf,
              : priorities, ps, remove-with-leaves, rpm-warm-cache, show-leaves, verify
Loading mirror speeds from cached hostfile
 * base: mirrors.centos.webair.com
 * elrepo: mirrors.evowise.com
 * epel: mirror.symnds.com
 * extras: mirror.umd.edu
 * nux-dextop: mirror.li.nux.ro
 * updates: mirror.datto.com
Skipping filters plugin, no data
Resolving Dependencies
Skipping filters plugin, no data
--> Running transaction check
---> Package VirtualBox-5.1.x86_64 0:5.1.10_112026_el7-1 will be updated
---> Package VirtualBox-5.1.x86_64 0:5.1.12_112440_el7-1 will be an update
--> Finished Dependency Resolution

Dependencies Resolved

===================================================================================================================
 Package                     Arch                Version                             Repository               Size
===================================================================================================================
Updating:
 VirtualBox-5.1              x86_64              5.1.12_112440_el7-1                 virtualbox               75 M

Transaction Summary
===================================================================================================================
Upgrade  1 Package

Total download size: 75 M
Is this ok [y/d/N]: y
Downloading packages:
No Presto metadata available for virtualbox
VirtualBox-5.1-5.1.12_112440_el7-1.x86_64.rpm                                               |  75 MB  00:00:05     
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
A copy of VirtualBox is currently running.  Please close it and try again.
Please note that it can take up to ten seconds for VirtualBox (in particular
the VBoxSVC daemon) to finish running.
error: %pre(VirtualBox-5.1-5.1.12_112440_el7-1.x86_64) scriptlet failed, exit status 1
Error in PREIN scriptlet in rpm package VirtualBox-5.1-5.1.12_112440_el7-1.x86_64
  Verifying  : VirtualBox-5.1-5.1.12_112440_el7-1.x86_64                                                       1/2 
VirtualBox-5.1-5.1.10_112026_el7-1.x86_64 was supposed to be removed but is not!
  Verifying  : VirtualBox-5.1-5.1.10_112026_el7-1.x86_64                                                       2/2 

Failed:
  VirtualBox-5.1.x86_64 0:5.1.10_112026_el7-1              VirtualBox-5.1.x86_64 0:5.1.12_112440_el7-1             

Complete!
}}}
"	Joshua Megerman
18199	Roll-over highlighting does not work right/simlarly on my different screens	all	VirtualBox 6.0.0	2018-12-18T23:02:11Z	2019-01-18T00:03:22Z	2019-01-18T00:03:22Z	"I'm on a three monitor setup, one 1920x1080, and two 1900x1200. Gnome on Oracle Linux 7.5.

When the VirtualBox Manager UI is on the 1900x1200 screens, and I ""roll over"" the machines on the left hand side panel, the entries highlight with a blue color.

When the VirtualBox Manager UI is on the 1900x1080 screen, and I roll over the machines on the left hand side panel, the machines highlight with a blue color... but the machine that is highlighted is not the machine my cursor is over."	ronabop
21319	Ring Zero Assertion Error on virtual machine after upgrade to 7.0.x	Windows	VirtualBox-7.0.4	2022-11-29T20:07:25Z	2022-11-30T14:14:53Z	2022-11-30T14:14:53Z	"Not sure about the trigger - sometimes hangs in 30 minutes, sometimes an hour. The machine was created in 6.1.34. The machine will hang in a fresh reboot of devuan (host) with nothing else running on either host or guest (Win7), excepting some autostarted license management servers.

Working on a core dump for you guys now."	nobodyreally
7042	retain window geometry after full screen	Windows	VirtualBox 3.2.4	2010-06-22T09:25:19Z	2010-06-22T09:25:19Z	2010-06-22T09:25:19Z	"The following is a regression since (I think) VBox 3.2.

Scenario:
  * set up a guest VM (tested with Windows XP and 7) with the same desktop resolution as the host
  * disable ""Guest Display Auto-resize""
  * position/resize the Guest WM window to show only parts of its desktop (offering scrollbars to pan the full desktop area)
  * go into Full Screen with Hostkey+F
  * come back from Full Screen with Hostkey+F

VBox will now ignore the previously set window size and instead expand the guest VM window to fill the whole screen. In previous versions it would respect the window size set by the user.

Retaining the window geometry (and scroll position) set by the user is very useful when having several guest VMs running side-by-side on one screen for overview, and easily being able to go into Full Screen when a guest needs attention."	Mike Wilson
15929	"Restored VM stays ""darkened"" if switching workspaces while restoring"	Windows	VirtualBox 5.0.26	2016-09-14T08:24:50Z	2016-11-09T13:03:53Z	2016-11-09T13:03:53Z	"The following applies to Fedora 24. The latest VirtualBox version distributed from packages with it is 5.0.26.

To reproduce:

1) have more workspaces active in Gnome, e.g. A and B
2) start restoring a suspended Windows 10 VM in workspace A; the Windows desktop is showed darkened, to represent that you can't use it yet
3) switch to workspace B before restore is completed
4) wait some time for restoring to complete
5) switch back to workspace A

... and the Windows desktop will still be darkened, despite being active. 

If, instead, you don't switch workspace for the duration of the restore, the darkening is removed at completion.

Note that if - from another workspace - I ""look"" at the VirtualBox window using a video capture device (e.g. obs-studio), the window is correctly not darkened.

The issue could be VirtualBox's or of the way VirtualBox interacts with Gnome's window manager / composite manager (mutter?). I found a similar issue from the past at https://forums.virtualbox.org/viewtopic.php?f=7&t=68896&p=372386#p328269 , with compton, another Linux composite manager.

Thanks."	giacecco
20063	Resources misuse on Ubuntu 20.04LTS host with a Windows 10 guest	Windows	VirtualBox 6.1.16	2020-11-24T14:18:52Z	2020-11-24T14:18:52Z	2020-11-24T14:18:52Z	After the '''update''' from 6.1.14 to 6.1.16 I'm observing a resources misuse on Ubuntu 20.04LTS. This means '''high RAM and CPU usage with no activity''' in the Windows 10 guest. Extension pack and guest additions have also been updated.	ProTerm
17740	resolution lock with VB and GA  5.2.10  ubuntu 18.04 host, windows 10 pro guest, nvidia-340 driver	Windows	VirtualBox 5.2.10	2018-05-07T08:07:12Z	2018-05-07T11:10:17Z	2018-05-07T11:10:17Z	"Tried several times to install/uninstall Guest Additions,
however there are problems with video driver, as resolution gets locked to 800x600, with flickers etc.

GA: 5.2.10, VB: 5.2.10_Ubuntu r121806

Guest: windows 10 pro

changed generic nvidia driver with specific nvidia-340.106 driver

The graphics card is an old

Quadro FX 580
  "	ft
15777	Resolution issues across 2 versions and the test build	Windows	VirtualBox 5.1.2	2016-08-10T19:14:41Z	2016-08-10T19:14:41Z	2016-08-10T19:14:41Z	"On version 5.1.2 of virtualbox and even the testbuild even with guest additions installed and after running vboxmanage controlvm win2008server setvideomodehint 1366 768 60 it will not change the window size beyond this [[Image(https://imgur.com/TuTE05B)]]. If I try seamless mode it just shows a black screen with the vbox controls at the bottom and the same thing happens with the fullscreen mode. The only mode it doesn't do that in is the regular one that's too tiny for me to use or in scaled mode. On version 5.0.24 I can use the VM in regular mode fine but it also has the same issues on seamless mode and fullscreen. 

Specs: slackware 14.2 64bit 
i5-2430M processor
intel integrated graphics (sandybridge/hd 3000)
8gb ram

guest OS: windows 2008 server"	MachinaeWolf
12629	Resolution Changes to 640x480 after remote desktop	Windows	VirtualBox 4.3.6	2014-01-20T13:48:15Z	2015-11-03T10:30:29Z	2015-11-03T10:30:29Z	"I have a Windows 7 guest running on an Ubuntu host.  I can remote desktop to the Windows7 guest without issue.  After closing remote desktop, virtual box resolution is now set to 640x480.  The only way to resolve is to shutdown and restart virtual box guest.

Steps to reproduce
 * Start Windows 7 Guest
 * Login to Guest
 * Move to new workstation and remote desktop to guest
 * logout of remote desktop
 * attempt to login to the console of Windows 7 guest
Using Virtual Box 4.3.6 with Guest Addons.  This issue hass been present on several past versions as well."	shawnl
18664	Reset of USB device causes failure to attach	Windows	VirtualBox 6.0.8	2019-05-21T11:28:08Z	2019-05-21T11:28:08Z	2019-05-21T11:28:08Z	"For some time now we have been able to test our USB3 machine vision cameras in a Windows VM but a recent change to VirtualBox has introduced a device reset during the attach process. 
The cameras we use are designed for continuous running in a factory and so the reset being issued is causing them to go through a full reset to ensure that they can be recovered in a fault case. This means that they are disconnecting from the host causing VirtualBox to lose track and fail to attach them to the guest. 
If I set a USB filter it gets stuck in a loop of constantly resetting the device and failing to attach it.

Is it possible to configure VirtualBox to disable the new device reset feature either globally or for a specific device?"	Dan
12352	Request: Option to store differencing image on same host device as base image	all	VirtualBox 4.2.18	2013-11-12T20:33:09Z	2013-11-12T20:33:09Z	2013-11-12T20:33:09Z	"I have a host with two drives, one SSD and one HD.
I have a guest with two .vdi's. The guest os (/) is on the host SSD and file storage .vdi (/home) is on the larger host HD.
However when snapshots are used, the differencing image is always stored in the default VM location. This makes snapshots unusable with multiple host storage locations.
whatever folder structure you would like is fine, (i.e. subfolder called snapshots) I would just like to see an option to store the differencing images on the same host media.

I have read through the forums, about the closest thing I've found was a request for a custom differencing folder (ramdisk)"	ImEdwardo
18477	Request for VBox to pass through Speculative Store Bypass (SSB) mitigations to guest => duplicate of #17987	Linux	VirtualBox 6.0.4	2019-03-06T08:37:25Z	2021-02-01T15:42:31Z	2021-02-01T15:42:31Z	"Hi,

Using Host VirtualBox 6.0.4 on CentOS 7.6.

Guest also CentOS 7.6

On the Host

$ grep . /sys/devices/system/cpu/vulnerabilities/*

gives

/sys/devices/system/cpu/vulnerabilities/spec_store_bypass:Mitigation: Speculative Store Bypass disabled via prctl and seccomp

but inside the Virtual Machine Guest

$ grep . /sys/devices/system/cpu/vulnerabilities/*

gives

/sys/devices/system/cpu/vulnerabilities/spec_store_bypass:Vulnerable


Kindly check."	Thomas Stephen Lee
20824	Reproducible split lock / freeze	Windows	VirtualBox 6.1.32	2022-02-10T19:22:17Z	2022-12-19T20:44:58Z	2022-12-19T20:44:58Z	"When attempting to install Visual Studio in a Windows 7 x64 or Windows 10 x64 guest with Ubuntu 20.04.1 w/ hwe host, installer freezes during file extraction and VM is unresponsive and cannot be recovered without killing the VM.

The origin of the error is a split lock, for example:

{{{
Feb  9 08:23:09 Laptop2021 kernel: [333455.818444] Split lock detected
Feb  9 08:23:09 Laptop2021 kernel: [333455.818444] : 0000 [#1] SMP NOPTI
Feb  9 08:23:09 Laptop2021 kernel: [333455.818450] CPU: 1 PID: 1510081 Comm: EMT Tainted: P           O      5.13.0-28-generic #31~20.04.1-Ubuntu
Feb  9 08:23:09 Laptop2021 kernel: [333455.818452] Hardware name: Dell Inc. XPS 13 9310 2-in-1/0W6MV0, BIOS 2.7.0 12/11/2021
Feb  9 08:23:09 Laptop2021 kernel: [333455.818453] RIP: 0010:0xffffa4346aa02680
Feb  9 08:23:09 Laptop2021 kernel: [333455.818456] Code: 89 02 c3 cc cc cc cc 53 49 89 ca 49 89 d3 41 8b 1b 41 8b 4b 04 9c 41 8b 02 83 24 24 bf 83 e0 40 48 09 04 24 9d 8b 06 8b 56 04 <f0> 0f c7 0f 89 06 89 56 04 9c 41 5b 41 8b 02 83 e0 bf 41 83 e3 40
Feb  9 08:23:09 Laptop2021 kernel: [333455.818458] RSP: 0018:ffffa43448393928 EFLAGS: 00010206
Feb  9 08:23:09 Laptop2021 kernel: [333455.818460] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
Feb  9 08:23:09 Laptop2021 kernel: [333455.818461] RDX: 0000000000000000 RSI: ffffa43448393948 RDI: ffff93cf3a781e7c
Feb  9 08:23:09 Laptop2021 kernel: [333455.818462] RBP: ffffa43448486000 R08: ffffa43448393838 R09: 0000000000000000
Feb  9 08:23:09 Laptop2021 kernel: [333455.818463] R10: ffffa4344839393c R11: ffffa43448393958 R12: 0000000000000000
Feb  9 08:23:09 Laptop2021 kernel: [333455.818463] R13: ffffa43448393b38 R14: ffffa43448486000 R15: ffffa43448475000
Feb  9 08:23:09 Laptop2021 kernel: [333455.818464] FS:  00007f5e75dfb700(0000) GS:ffff93d27f680000(0000) knlGS:fffff80002a2c000
Feb  9 08:23:09 Laptop2021 kernel: [333455.818466] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb  9 08:23:09 Laptop2021 kernel: [333455.818467] CR2: 000000006e0c096c CR3: 00000003e3316001 CR4: 0000000000772ee0
Feb  9 08:23:09 Laptop2021 kernel: [333455.818468] PKRU: 55555554
Feb  9 08:23:09 Laptop2021 kernel: [333455.818469] Call Trace:
Feb  9 08:23:09 Laptop2021 kernel: [333455.818470]  <TASK>
Feb  9 08:23:09 Laptop2021 kernel: [333455.818472]  ? sched_clock+0x9/0x10
Feb  9 08:23:09 Laptop2021 kernel: [333455.818476]  ? sched_clock_cpu+0x11/0xb0
Feb  9 08:23:09 Laptop2021 kernel: [333455.818478]  ? newidle_balance+0x1e9/0x3f0
Feb  9 08:23:09 Laptop2021 kernel: [333455.818481]  ? schedule_hrtimeout_range_clock+0xa0/0x110
Feb  9 08:23:09 Laptop2021 kernel: [333455.818484]  ? hrtimer_init_sleeper+0x80/0x80
Feb  9 08:23:09 Laptop2021 kernel: [333455.818486]  ? finish_wait+0x5c/0x70
Feb  9 08:23:09 Laptop2021 kernel: [333455.818494]  ? rtR0SemEventMultiLnxWait.isra.0+0x283/0x3c0 [vboxdrv]
Feb  9 08:23:09 Laptop2021 kernel: [333455.818509]  ? wait_woken+0x80/0x80
Feb  9 08:23:09 Laptop2021 kernel: [333455.818512]  ? SUPR0GetCurrentGdtRw+0xe/0x10 [vboxdrv]
Feb  9 08:23:09 Laptop2021 kernel: [333455.818519]  ? VBoxHost_RTThreadCtxHookEnable+0x31/0x50 [vboxdrv]
Feb  9 08:23:09 Laptop2021 kernel: [333455.818531]  ? supdrvIOCtlFast+0x66/0xb0 [vboxdrv]
Feb  9 08:23:09 Laptop2021 kernel: [333455.818539]  ? VBoxDrvLinuxIOCtl_6_1_32+0x56/0x260 [vboxdrv]
Feb  9 08:23:09 Laptop2021 kernel: [333455.818546]  ? __x64_sys_ioctl+0x91/0xc0
Feb  9 08:23:09 Laptop2021 kernel: [333455.818549]  ? do_syscall_64+0x61/0xb0
Feb  9 08:23:09 Laptop2021 kernel: [333455.818552]  ? do_syscall_64+0x6e/0xb0
Feb  9 08:23:09 Laptop2021 kernel: [333455.818553]  ? syscall_exit_to_user_mode+0x27/0x50
Feb  9 08:23:09 Laptop2021 kernel: [333455.818555]  ? do_syscall_64+0x6e/0xb0
Feb  9 08:23:09 Laptop2021 kernel: [333455.818557]  ? do_syscall_64+0x6e/0xb0
Feb  9 08:23:09 Laptop2021 kernel: [333455.818558]  ? asm_sysvec_apic_timer_interrupt+0xa/0x20
Feb  9 08:23:09 Laptop2021 kernel: [333455.818564]  ? entry_SYSCALL_64_after_hwframe+0x44/0xae
Feb  9 08:23:09 Laptop2021 kernel: [333455.818566]  </TASK>
Feb  9 08:23:09 Laptop2021 kernel: [333455.818567] Modules linked in: snd_usb_audio snd_usbmidi_lib r8153_ecm cdc_ether usbnet r8152 mii vboxnetadp(O) vboxnetflt(O) vboxdrv(O) ccm rfcomm cmac algif_hash algif_skcipher af_alg bnep binfmt_misc nls_iso8859_1 snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_hda_codec_hdmi snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_ctl_led snd_hda_codec_realtek snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg mei_hdcp snd_intel_sdw_acpi snd_hda_codec intel_rapl_msr snd_hda_core snd_hwdep snd_pcm snd_seq_midi uvcvideo snd_seq_midi_event videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev snd_rawmidi mc btusb btrtl dell_laptop snd_seq ledtrig_audio dell_smm_hwmon btbcm btintel intel_tcc_cooling snd_seq_device x86_pkg_temp_thermal snd_timer
Feb  9 08:23:09 Laptop2021 kernel: [333455.818615]  intel_powerclamp coretemp bluetooth kvm_intel snd dell_wmi iwlmvm kvm mac80211 intel_cstate ecdh_generic ecc hid_sensor_magn_3d libarc4 input_leds dell_smbios efi_pstore dcdbas iwlwifi serio_raw dell_wmi_sysman dell_wmi_descriptor wmi_bmof hid_sensor_als hid_sensor_incl_3d hid_sensor_rotation hid_sensor_custom_intel_hinge hid_sensor_accel_3d hid_sensor_gyro_3d hid_sensor_trigger soundcore industrialio_triggered_buffer kfifo_buf hid_sensor_iio_common industrialio cfg80211 intel_pmt_telemetry hid_multitouch processor_thermal_device mei_me mei processor_thermal_rfim joydev processor_thermal_mbox processor_thermal_rapl intel_pmt_class intel_rapl_common cros_ec_ishtp cros_ec intel_soc_dts_iosf ucsi_acpi typec_ucsi typec intel_hid int3403_thermal soc_button_array int340x_thermal_zone sparse_keymap acpi_pad mac_hid acpi_tad int3400_thermal acpi_thermal_rel sch_fq_codel sunrpc msr parport_pc ppdev lp parport ip_tables x_tables autofs4 zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO)
Feb  9 08:23:09 Laptop2021 kernel: [333455.818649]  icp(PO) zcommon(PO) znvpair(PO) spl(O) dm_crypt hid_sensor_custom hid_sensor_hub intel_ishtp_loader intel_ishtp_hid wacom usbhid hid_generic i915 crct10dif_pclmul crc32_pclmul i2c_algo_bit ghash_clmulni_intel drm_kms_helper aesni_intel syscopyarea rtsx_pci_sdmmc sysfillrect crypto_simd nvme sysimgblt i2c_i801 fb_sys_fops cryptd intel_lpss_pci intel_lpss i2c_smbus intel_ish_ipc cec psmouse rc_core nvme_core rtsx_pci idma64 i2c_hid_acpi xhci_pci intel_ishtp drm i2c_hid thunderbolt xhci_pci_renesas intel_pmt wmi hid pinctrl_tigerlake video
Feb  9 08:23:09 Laptop2021 kernel: [333455.818672] ---[ end trace e310c2a1fbafbaa6 ]---
Feb  9 08:23:09 Laptop2021 kernel: [333456.044605] RIP: 0010:0xffffa4346aa02680
Feb  9 08:23:09 Laptop2021 kernel: [333456.044612] Code: 89 02 c3 cc cc cc cc 53 49 89 ca 49 89 d3 41 8b 1b 41 8b 4b 04 9c 41 8b 02 83 24 24 bf 83 e0 40 48 09 04 24 9d 8b 06 8b 56 04 <f0> 0f c7 0f 89 06 89 56 04 9c 41 5b 41 8b 02 83 e0 bf 41 83 e3 40
Feb  9 08:23:09 Laptop2021 kernel: [333456.044614] RSP: 0018:ffffa43448393928 EFLAGS: 00010206
Feb  9 08:23:09 Laptop2021 kernel: [333456.044616] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
Feb  9 08:23:09 Laptop2021 kernel: [333456.044617] RDX: 0000000000000000 RSI: ffffa43448393948 RDI: ffff93cf3a781e7c
Feb  9 08:23:09 Laptop2021 kernel: [333456.044618] RBP: ffffa43448486000 R08: ffffa43448393838 R09: 0000000000000000
Feb  9 08:23:09 Laptop2021 kernel: [333456.044619] R10: ffffa4344839393c R11: ffffa43448393958 R12: 0000000000000000
Feb  9 08:23:09 Laptop2021 kernel: [333456.044619] R13: ffffa43448393b38 R14: ffffa43448486000 R15: ffffa43448475000
Feb  9 08:23:09 Laptop2021 kernel: [333456.044620] FS:  00007f5e75dfb700(0000) GS:ffff93d27f680000(0000) knlGS:fffff80002a2c000
Feb  9 08:23:09 Laptop2021 kernel: [333456.044621] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb  9 08:23:09 Laptop2021 kernel: [333456.044622] CR2: 000000006e0c096c CR3: 00000003e3316002 CR4: 0000000000772ee0
Feb  9 08:23:09 Laptop2021 kernel: [333456.044623] PKRU: 55555554
}}}

Other split_lock traces have different detailed call stacks, but the reproducer below causes a split_lock 100% of the time.

Steps to reproduce:

Hardware: XPS 9310, Ubuntu 20.04.1 w/ HWE kernel host, Virtualbox 6.1.32

1. Install Windows 10 x64 20H2 in virtualbox (all default options).

2. Download the visual studio tools installer in guest: https://aka.ms/vs/15/release/vs_buildtools.exe

3. Attempt installation:
vs_buildtools.exe --wait --norestart --nocache modify --installPath ""%ProgramFiles%\Microsoft Visual Studio\2017\BuildTools"" --add Microsoft.VisualStudio.Workload.MSBuildTools --add Microsoft.VisualStudio.Workload.VCTools --lang en-US

This occurs independent of video driver (VMSVGA, VBoxSVGA)."	tmcqueen
19167	Repository metadata broken for Fedora	other	VirtualBox 6.1.0	2019-12-16T15:32:36Z	2020-01-01T02:08:10Z	2020-01-01T02:08:10Z	"Attempting to install VBox 6.1 on Fedora 31 results in this error:


{{{
[MIRROR] VirtualBox-6.1-6.1.0_135406_fedora31-1.x86_64.rpm:
Downloading successful, but checksum doesn't match.
Calculated: 7e6c702d838aaf8e3cdc655a71a855889e785f4241d000843810719b182ef7dd(sha256)
Expected: 8a55bbb38789bbccb64f652611e4c3c67eebde4485097fd07197e1350feca33f(sha256)
}}}
"	thomasfedb
19901	Reopen #6650 closed on 08/14/2016	Linux	VirtualBox 6.1.14	2020-09-18T23:49:19Z	2020-09-18T23:49:19Z	2020-09-18T23:49:19Z	"vbox-img --help documentation allows the `convert` command to output to stdout. This has been requested by forum users a few times in several forums. Mentioned 2010 ticket is just one user case. But this usage fails, as seen in log attached.
There seems to be an unjustified regression in the code, in `vbox-img.cpp`:797. The following line of code was withdrawn at changeset 33235 with commit message ""Storage/vbox-img: implement stdout handling"".

     {{{ AssertFailedReturn(VERR_NOT_SUPPORTED); }}}

However for some reason this line has been reintroduced later on.
I tested a custom build of vbox-img with the attached patch and the requested stdout handling worked well. Attached proposed patch against 6.1.14a code.
Alternatively, if this capability is still immature, revise the `--help` output and reopen #6650


"	fabnicol
12312	Rendering in Civilization IV is broken on Windows 8 guests	Windows	VirtualBox 4.3.2	2013-11-04T17:54:17Z	2015-04-27T19:02:14Z	2015-04-27T19:02:14Z	"Hi,

I've noticed that rendering within game Civilization IV (or its spin-off Colonization) is fully broken, with a black screen instead of anything else.

Steps to reproduce :
DO : start a Civ IV game
EXPECT : the map is properly displayed
ACTUAL : rendering is broken (almost everything black). Playing with details does not change anything.

My hardware
Ubuntu Saucy AMD64
AMD Phenom x4 9850
8 GB RAM
NVidia GeForce 660Ti w/ 2 GB RAM

VM : Windows 8 32 bits"	gojul
16942	removing the deb package should also remove the systemd service	other	VirtualBox 5.1.24	2017-07-25T06:44:32Z	2017-07-25T06:44:32Z	2017-07-25T06:44:32Z	"As said, a lot of people remove virtualbox-4.2 virtualbox-5.0 virtualbox-5.1, and they try to install the Ubuntu version.

The problem is that without a --purge, your virtualbox package doesn't remove the systemd services, leading to install errors
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1705940

DKMS: install completed.
Configurando virtualbox (5.0.40-dfsg-0ubuntu1.16.04.1) ...
insserv: script virtualbox: service vboxdrv already provided!
insserv: exiting now!
update-rc.d: error: insserv rejected the script header
dpkg: error al procesar el paquete virtualbox (--configure):
 el subproceso instalado el script post-installation devolvió el código de salida de error 1
dpkg: problemas de dependencias impiden la configuración de virtualbox-qt:
 virtualbox-qt depende de virtualbox (= 5.0.40-dfsg-0ubuntu1.16.04.1); sin embargo:
 El paquete `virtualbox' no está configurado todavía.
  El paquete `virtualbox-4.2' que provee virtualbox no está instalado.


so, please remove your files when virtualbox is removed :)

thanks
"	LocutusOfBorg
18652	Reiner SCT CyberJack USB no longer works (reset full speed usb device ...)	Windows	VirtualBox 6.0.8	2019-05-16T18:04:22Z	2019-05-31T07:57:06Z	2019-05-31T07:57:06Z	"Since Virtualbox 6.0.6 it appears that the Reiner SCT CyberJack Standard Chipcard reader (USB) can no longer be used from within a Windows VM.

Card reader is detected ok by Linux
[  611.544511] usb 1-7: new full-speed USB device number 5 using xhci_hcd
[  611.879182] usb 1-7: New USB device found, idVendor=0c4b, idProduct=0500, bcdDevice= 0.01
[  611.879185] usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  611.879187] usb 1-7: Product: cyberJack RFID standard
[  611.879188] usb 1-7: Manufacturer: REINER SCT
[  611.879189] usb 1-7: SerialNumber: 5287xxxxxx

After launching a Windows 10 VM (USB device connected automatically to VM) countless messages of type
[  612.661394] usb 1-7: reset full-speed USB device number 5 using xhci_hcd

and the CyberJack driver within the VM cannot access the chipcard reader.

*Additional info*
Symptom: The reader does not seem to accept the card if plugged in"	Jörg Skottke
8764	Regression: VirtualBox and VM configuration broken if VM folder exists	other	VirtualBox 4.0.6	2011-04-22T10:26:54Z	2011-04-22T10:41:21Z	2011-04-22T10:41:21Z	"I just updated VirtualBox to version 4.0.6 through the Ubuntu 10.10 64bit repository you provide. The application is totally broken since then: It started with the configuration window not offering the list of categories at the left. The same happened when I tried to open a VM configuration. I then purged the VirtualBox configuration, which made the config work again - until I changed the VM folder to where I put my VMs. If I then restarted VirtualBox, the old state came back. I then tried to instead create a folder with the name VirtualBox suggested ""(VirtualBox VMs"" or similar), same effect. Some more attempts showed that, if the VM folder exists during VirtualBox start, everything breaks. Which of course makes it rather impossible to do anything. I could not find any log file or console output.
VirtualBox also did not correctly re-add the VMs in the VM folder if I put them into the folder they were in - not sure how I am supposed to start them again.
Yes, I did re-boot my whole system, to no avail.

I attached a screenshot of how the configuration window looks like."	Ralf Jung
17419	Regression: VirtualBox 5.1.30 can not be compiled without kernel build/source directory	Linux	VirtualBox 5.1.30	2018-01-04T20:46:00Z	2018-01-05T17:51:46Z	2018-01-05T17:51:46Z	"In VirtualBox Release 5.1.6 it was possible to compile VBox from Sources without access to the kernel build- and source directory when using --disable-kmods.

When compiling VirtualBox 5.1.30 this gives errors. Not in all environments is the kernel source accessible when compiling a user mode program (or the kernel module build is separated)."	core-it-admin
14568	Regression: protocol error if the host folder name differs from share name	Linux	VirtualBox 5.0.4	2015-09-10T13:15:38Z	2015-09-10T13:44:00Z	2015-09-10T13:44:00Z	"I remember many years ago in VBox 2 or 3 there was an issue that name of the folder on host system has to match the name of the share for it to work properly. In 4 it worked properly though. Now on 5.0.4 I've encountered the same issue again:

on host:
1. mkdir ~/vm-shared
2. mkdir ~/test

in VBox UI:
1. add folder ~/vm-shared with name ""shared""
2. add folder ~/test with name ""test""

on guest (under root):
1. mkdir /mnt/shared && mount -t vboxsf -o uid=1000,gid=100 shared /mnt/shared
2. mkdir /mnt/test && mount -t vboxsf -o uid=1000,gid=100 test /mnt/test

now on guest, try to execute following command:
1. mkdir /mnt/shared/somedir
2. mkdir /mnt/test/somedir

Second command executed successfully, but first command fails with protocol error."	indifferent
17420	Regression: Cannot compile VirtualBox 5.2.4 on Ubuntu 16.04, Qt5 not found	Linux	VirtualBox 5.2.4	2018-01-04T21:02:16Z	2020-10-08T16:13:01Z	2020-10-08T16:13:01Z	Even with the qt5 package installed on Ubuntu 16.04, the VirtualBox 5.2.4 configure script does not find Qt5. This is a regression since VirtualBox 5.1.	core-it-admin
18123	Regression when play mci mp3 since 5.2.20	Windows	VirtualBox 5.2.20	2018-11-11T20:34:29Z	2019-02-08T10:58:30Z	2019-02-08T10:58:30Z	"Hello,

I debian 9.5 Stretch installed in the Host machine.

Since the release of VirtualBox 5.2.20 and 5.2.22,
In windows guest (2000,7) when I want to play a youtube video in the guest machine it's OK ,it's work fine !!.
ON THE OTHER HAND :
when i play an mp3 / wav from the MCI player windows or windows media player THEN result the sound jerks and hash.

In short:
Since version 5.2.20 when I want to play an mp3 from the MCI, it plays only 80% time of the mp3.
And apparently I'm the only one with this problem.
In versions prior to 5.2.20 I have no problem.

How to solve this problem?

I DON'T KNOW if the log can you help it;;


Thank you."	Sizy458
17471	regression 5.2.2 -> 5.2.4, USB stopped work with TomTom Go	Windows	VirtualBox 5.2.4	2018-01-17T23:42:55Z	2018-06-20T23:01:34Z	2018-06-20T23:01:34Z	"Moving from 5.2.2 to 5.2.4 TomTom My Drive software is unable to connect to my TomTom.
TomTom Go software seems to see the TomTom device but it can't connect to it anymore.

Virtualbox was working fine with 5.2.2.

USB is configured as 2.0. Host is Debian running kernel 4.14.7, guest is Windows 7.

Still not working with 5.2.6.



thanks"	IvanSB
13635	Reduce dialog overload on extension pack upgrade	all	VirtualBox 4.3.20	2014-11-22T11:31:01Z	2018-05-13T11:41:00Z	2018-05-13T11:41:00Z	"Hi,

When you've updated VirtualBox to a newer version and you had the extension pack installed before, you'll get presented with the notification that a newer extension pack is available when you start VirtualBox again after the VirtualBox update.

It's nice to get the reminder and the option to upgrade the extension pack, but the amount of subsequent dialogs the user is presented with is just madness. 7 in total just to perform the upgrade.

These are the action the user has to perform at the moment:
1. Press ""Download"" button on the upgrade available dialog
2. Press ""Download"" button on the download dialog
3. Press ""Install"" button on the download complete dialog
4. Press ""Upgrade"" button on a confirmation dialog
5. Press ""I agree"" button on the license dialog
6. Supply password on the system's admin rights needed dialog
7. Press ""OK"" button on the installed confirmation dialog

This makes a handy feature just tedious instead of being helpful and efficient.

I understand that there are different situations in which a user can install the extension pack and that there are different dialogs needed in those situations, but those dialogs should only be displayed when they actually apply.

The first 4 actions can, and IMHO should, be combined into just 1 when we are dealing the the update available notification. There's a new upgrade -> download and install.
Having to agree to the license could even be considered redundant on upgrade. You already agreed on it on the first install. If the license hasn't changed there's no point in displaying it again.

Would it be possible and desired to reduce the extension pack upgrade step to 3 or 4 steps instead of the current 7?
The current situation only makes it tedious and leaves a messy impression."	Forage
17997	Re-ordering VMS is a royal pain	other	VirtualBox 5.2.18	2018-09-19T17:30:55Z	2018-09-19T17:31:49Z	2018-09-19T17:31:49Z	When trying to re-order guest images in the list, it takes several attempts to do so.	iMarkM
16295	RDP-Server very slow then 1 connection unreachable	all	VirtualBox 5.1.10	2016-12-16T14:05:11Z	2016-12-16T14:05:11Z	2016-12-16T14:05:11Z	"Hello,

the RDP-Server have some trouble if the client gets unreachable. All another connections (available and future) are extreme slow and unusable.

The problem comes up then someone change from LAN to WLAN, without cancel conventional the connection before.

To reproduction that issue do the follow:


{{{
1. Enable RDP for a VM
2. Start the VM
3. Connect via RDP-Client to the VM
}}}

Way 1:

{{{
4. Change the IP ( ifconfig eth0 192.168.1.15 netmask 255.255.0.0 )
5. Close the connection and reconnect
}}}

Way 2:

{{{
4. Unplug the networkcable physical.
5. Connect with a another PC
}}}

Now the RDP connection is unusable / heavy slow."	dk_lcom
20131	rcu_sched detected stalls on CPUs/tasks: linux guest and host ?ryzen issue	Linux	VirtualBox 6.1.16	2021-01-17T18:39:22Z	2021-11-07T13:22:29Z	2021-11-07T13:22:29Z	"Linux debian guest on Debian host Virtualbox 6.1.16

Host: Linux  5.6.0-0.bpo.2-amd64 #1 SMP Debian 5.6.14-2~bpo10+1 (2020-06-09) x86_64 GNU/Linux  Debian 10
AMD Ryzen 9 3900X 12-Core 32Gb ram 

guest 4 cores, 4gb ram
dmesg:

[  225.539622] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:

[  225.540724] rcu:     0-...!: (27 ticks this GP) idle=c50/0/0x0 softirq=2529/2                                                                                        530 fqs=0

[  225.541761] rcu:     1-...!: (0 ticks this GP) idle=ac8/0/0x0 softirq=2101/21                                                                                        01 fqs=0

[  225.542767] rcu:     3-...!: (26 ticks this GP) idle=99c/0/0x0 softirq=2173/2                                                                                        174 fqs=0

[  225.543767]  (detected by 2, t=5271 jiffies, g=2529, q=2)

[  225.543770] Sending NMI from CPU 2 to CPUs 0:

[  225.543825] NMI backtrace for cpu 0 skipped: idling at native_safe_halt+0xe/0                                                                                        x10

[  225.544771] Sending NMI from CPU 2 to CPUs 1:

[  225.544797] NMI backtrace for cpu 1 skipped: idling at native_safe_halt+0xe/0                                                                                        x10

[  225.545769] Sending NMI from CPU 2 to CPUs 3:

[  225.545796] NMI backtrace for cpu 3 skipped: idling at native_safe_halt+0xe/0                                                                                        x10

[  225.546769] rcu: rcu_sched kthread starved for 5272 jiffies! g2529 f0x0 RCU_G                                                                                        P_WAIT_FQS(5) ->state=0x402 ->cpu=1

[  225.547792] rcu: RCU grace-period kthread stack dump:

[  225.548812] rcu_sched       I    0    11      2 0x80004000

[  225.548816] Call Trace:

[  225.548836]  ? __schedule+0x2d8/0x760

[  225.548838]  ? __switch_to_asm+0x40/0x70

[  225.548840]  ? __switch_to_asm+0x40/0x70

[  225.548842]  schedule+0x4a/0xb0

[  225.548843]  schedule_timeout+0x15e/0x300

[  225.548850]  ? __next_timer_interrupt+0xd0/0xd0

[  225.548853]  rcu_gp_kthread+0x452/0x8d0

[  225.548864]  kthread+0xf9/0x130

[  225.548869]  ? kfree_call_rcu+0x10/0x10

[  225.548870]  ? kthread_park+0x90/0x90

[  225.548872]  ret_from_fork+0x22/0x40

[  285.421645] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:

[  285.422242] rcu:     0-...!: (0 ticks this GP) idle=da0/0/0x0 softirq=2535/25                                                                                        35 fqs=0

[  285.422780] rcu:     1-...!: (37 ticks this GP) idle=d4c/0/0x0 softirq=2103/2                                                                                        103 fqs=0

[  285.423305] rcu:     3-...!: (46 ticks this GP) idle=b84/0/0x0 softirq=2178/2                                                                                        179 fqs=0

[  285.423815]  (detected by 2, t=5268 jiffies, g=2541, q=866)

[  285.423817] Sending NMI from CPU 2 to CPUs 0:

[  285.423858] NMI backtrace for cpu 0 skipped: idling at native_safe_halt+0xe/0                                                                                        x10

[  285.424818] Sending NMI from CPU 2 to CPUs 1:

[  285.424845] NMI backtrace for cpu 1 skipped: idling at native_safe_halt+0xe/0                                                                                        x10

[  285.425817] Sending NMI from CPU 2 to CPUs 3:

[  285.425847] NMI backtrace for cpu 3 skipped: idling at native_safe_halt+0xe/0                                                                                        x10

[  285.426815] rcu: rcu_sched kthread starved for 5268 jiffies! g2541 f0x0 RCU_G                                                                                        P_WAIT_FQS(5) ->state=0x402 ->cpu=0

[  285.427228] rcu: RCU grace-period kthread stack dump:

[  285.427620] rcu_sched       I    0    11      2 0x80004000

[  285.427623] Call Trace:

[  285.427629]  ? __schedule+0x2d8/0x760

[  285.427630]  ? __switch_to_asm+0x40/0x70

[  285.427631]  ? __switch_to_asm+0x40/0x70

[  285.427633]  schedule+0x4a/0xb0

[  285.427634]  schedule_timeout+0x15e/0x300

[  285.427637]  ? __next_timer_interrupt+0xd0/0xd0

[  285.427640]  rcu_gp_kthread+0x452/0x8d0

[  285.427643]  kthread+0xf9/0x130

[  285.427645]  ? kfree_call_rcu+0x10/0x10

[  285.427647]  ? kthread_park+0x90/0x90

[  285.427648]  ret_from_fork+0x22/0x40

System is unusable.

Guest transferred from Intel i5 core system, were it worked perfectly.
Same error in Debian 9, 10 and bullseye guests.
Tried multiple combination of cores and ram - no effect.

Interestingly Alpine 3.12 guest on same system has no problem. 

Current workaround: install guest additions on guest and error messages go. 

I've attached the virtualbox logs.  host1 - is related to the dmesg output above.
host2 and host3 are logs from the same system, just running longer. 

Many thanks for your help.
"	RT_db
16107	Random Freeze of Ubuntu 16.04 guest under 16.04 Host	Linux	VirtualBox 5.1.6	2016-10-23T12:14:23Z	2016-10-25T19:08:40Z	2016-10-25T19:08:40Z	"I encouter random freezes of a 16.04 guest system under a 16.04 host system.

This seems not to be new in the 5.1 versions as I had this problem in previous versions, too. The same guest system was working fine before the update to Ubuntu 16.04 (The box was 14.04 before). 

Unfortunately I do not find a pattern when the box freezes. Sometimes it happens soon after the start of the box, sometimes the box runs stable for 1-2 days. The guest system just freezes. 



"	Andreas P
11856	Quick shutdown of all vms wanted	all	VirtualBox 4.2.12	2013-06-12T08:26:00Z	2013-06-12T08:36:25Z	2013-06-12T08:36:25Z	"This is not a bug, but an enhancement-question


I'm running Debian 7.0.
When i'm shutting down the system 
(This can manual or automatic or by powerloss and other causes..)
Init sends the SIGTERM signal and 5 sec later the SIGKILL.

In the /etc/rcx.d  the vbox-services are executed for shutdown/reboot at the beginning of the shutdown/reboot.
K02vboxautostart-service
K02vboxballoonctrl-services
K02vboxweb-services
K03vboxdrv
(after this unmouting nfs takes place)

Because of the shutdown order, i cannot move the proces more to the back. I can only try to shutdown the vm's before vboxservices are going down. This means a K01 for my script.

I did make a script to put the vm's in savestate one by one. (because a powerdown will not work for some machines.)
Saving a machine takes a few seconds.
I want to save 5 or more vm's.

By default i can save one vm.
With some tuning i can save 4 vm's before the host go's down.

The problem is, that the other vm's are just stopped. And could lose data, because the proces is killed, without the change to save the state off the machine.


I have a question.

Is it possible to make a command likje this:

vboxmanage controlvm all savestate

And that this command brings all machines down '''at once'''.
Not one after an other but alltogether. So it go's quicker and can be done in 5-10 sec.

Or an other sollution would be, the possibility to run commands on the background. So i can call all vm's one by one and don't have to wait for finishing before i can call the next one.

something like this:

vboxmanage controlvm <vm> savestate &

Thanks





"	ED
18053	Query Installed Guest Extensions Version	other	VirtualBox 5.2.18	2018-10-16T14:35:29Z	2018-10-25T23:52:41Z	2018-10-25T23:52:41Z	"Not a bug, but a question. I tried looking at the forums but was unable to answer it.

Is there a way to determine the version of Extensions installed on a VM without it running? I looked at ""vboxmanage showvminfo"" but it didn't seem to be listed there nor is there any information shown in the VirtualBox Manager GUI. 

Thanks,"	jim.rather
18596	QT Recursive repaint detected -> Segmentation fault (core dumped)	all	VirtualBox 6.0.6	2019-04-24T13:08:56Z	2019-04-24T13:16:01Z	2019-04-24T13:16:01Z	"~$ virtualbox

Qt WARNING: QWidget::repaint: Recursive repaint detected
Qt WARNING: QBackingStore::endPaint() called with active painter on backingstore paint device
Segmentation fault (core dumped)

---

Rescaling VirtualBox Manager window while looking at VBox.log in the VirtualBox Manager, same crash happens when i use the logviewer(ctrl+l).

Fault seems to happend shortly after scaling the window so bottom slide bar is supposed to disappear."	KjerkreitYtre
19637	QT 5.15 breaks VirtualBox (6.1.8)	other	VirtualBox 6.1.8	2020-06-03T15:05:50Z	2020-06-03T15:12:46Z	2020-06-03T15:12:46Z	"Some Qt header files have changed in 5.15 and on my Gentoo box I am no longer able to compile VirtualBox (tested only with 6.1.8, others might break also). The issue is a complaint about QPâinterPath. E.g.:


{{{
kBuild: Compiling UICommon - /tmp/VirtualBox-6.1.8/src/VBox/Frontends/VirtualBox/src/globals/UIImageTools.cpp
/tmp/VirtualBox-6.1.8/src/VBox/Frontends/VirtualBox/src/globals/UIImageTools.cpp: In function ‘QImage betaLabelImage(const QSize&)’:
/tmp/VirtualBox-6.1.8/src/VBox/Frontends/VirtualBox/src/globals/UIImageTools.cpp:225:18: error: aggregate ‘QPainterPath tp’ has incomplete type and cannot be defined
  225 |     QPainterPath tp;
      |                  ^~
/tmp/VirtualBox-6.1.8/src/VBox/Frontends/VirtualBox/src/globals/UIImageTools.cpp:231:5: error: ‘QPainterPathStroker’ was not declared in this scope; did you mean ‘QPainterPath’?
  231 |     QPainterPathStroker pps;
      |     ^~~~~~~~~~~~~~~~~~~
      |     QPainterPath
/tmp/VirtualBox-6.1.8/src/VBox/Frontends/VirtualBox/src/globals/UIImageTools.cpp:232:18: error: variable ‘QPainterPath pp’ has initializer but incomplete type
  232 |     QPainterPath pp = pps.createStroke(tp);
      |                  ^~
/tmp/VirtualBox-6.1.8/src/VBox/Frontends/VirtualBox/src/globals/UIImageTools.cpp:232:23: error: ‘pps’ was not declared in this scope
  232 |     QPainterPath pp = pps.createStroke(tp);
      |                       ^~~
kmk: *** [/tmp/VirtualBox-6.1.8/kBuild/footer-pass2-compiling-targets.kmk:277: /tmp/VirtualBox-6.1.8/out/linux.amd64/release/obj/UICommon/src/globals/UIImageTools.o] Error 1
kmk: *** Waiting for unfinished jobs....

}}}
"	sqrt
20622	Python wrapper of VirtualBox API under Debian Bullseye doesn't work	other	VirtualBox 6.1.26	2021-10-20T14:31:12Z	2021-10-20T14:31:12Z	2021-10-20T14:31:12Z	"
When starting vboxshell.py under Python3.9 on Debian Bullseye the following error eventuates:

{{{
#!sh
test@testpc231:/$ cd /lib/virtualbox
test@testpc231:/lib/virtualbox$ python3.9 vboxshell.py 
Traceback (most recent call last):
  File ""/usr/lib/virtualbox/vboxshell.py"", line 3621, in <module>
    main(sys.argv)
  File ""/usr/lib/virtualbox/vboxshell.py"", line 3589, in main
    oVBoxMgr = VirtualBoxManager(style, params)
  File ""/usr/local/lib/python3.9/dist-packages/vboxapi/__init__.py"", line 989, in __init__
    self.platform = PlatformXPCOM(dPlatformParams)
  File ""/usr/local/lib/python3.9/dist-packages/vboxapi/__init__.py"", line 752, in __init__
    import xpcom.components
  File ""/usr/lib/virtualbox/sdk/bindings/xpcom/python/xpcom/components.py"", line 240, in <module>
    _shutdownObserver = xpcom.server.WrapObject(_ShutdownObserver(), interfaces.nsIObserver)
  File ""/usr/lib/virtualbox/sdk/bindings/xpcom/python/xpcom/server/__init__.py"", line 64, in WrapObject
    return _xpcom.WrapObject(policy( ob, iid ), iid, bWrapClient)
  File ""/usr/lib/virtualbox/sdk/bindings/xpcom/python/xpcom/server/policy.py"", line 161, in __init__
    raise ServerException(nsError.NS_ERROR_NO_INTERFACE)
xpcom.ServerException: 0x80004002 (NS_ERROR_NO_INTERFACE)
}}}

Testing conditions were as follows:

Setting up a fresh Debian Bullseye installation on amd64 from a debian-11.1.0-amd64-DVD-1.iso installer image with package groups ""Debian desktop environment"", ""Xfce"" and ""Standard System Tools"" selected. System local language is ""de_DE.UTF-8"".

Next installing virtualbox-6.1_6.1.26-145957~Debian~bullseye_amd64.deb by Debian package management tools of the distro from repo
""deb [arch=amd64] https://download.virtualbox.org/virtualbox/debian bullseye contrib""

Now standard functionality (configuration of VMs, running VMs, etc) provided by the VirtualBox components and tools (hypervisor, GUI-App, VBoxManage) looks like working fine out of the box.

Unfortunately, this doesn't hold true for the Python wrapper of the API of VirtualBox. Starting vboxshell.py by the python3.9 interpreter of the distro provides the above mentioned error!

"	Georg Fischer
20994	PXE UNDI driver transmit seems to be mapping existing transmit buffer instead of making a copy	other	VirtualBox 6.1.34	2022-06-19T04:07:03Z	2022-06-19T04:07:03Z	2022-06-19T04:07:03Z	"To be fair, haven't dug that far into VirtualBox code (don't really use SVN, and don't have an easy web interface to search the code for what I'm looking for) but, the most recent code I could find on GitHub for VBox seems to suggest it's mapping the supplied transmit buffer and not copying it before return: https://github.com/TedHartDavis/VBoxMirror/blob/3d7f37ab5b248566e1dc17df8ee495628bb007e5/src/VBox/Devices/EFI/FirmwareNew/OptionRomPkg/UndiRuntimeDxe/Decode.c#L1214, https://github.com/TedHartDavis/VBoxMirror/blob/3d7f37ab5b248566e1dc17df8ee495628bb007e5/src/VBox/Devices/EFI/Firmware/OptionRomPkg/UndiRuntimeDxe/E100b.c#L1100

Given that, I'm currently the following behavior running GRUB in VirtualBox and it sending DNS:

1. GRUB (2.06) allocates a single, fixed scratch-space buffer for sending packets via PXE UNDI; this buffer is reused for every packet send. (See https://github.com/rhboot/grub2/blob/ef36b3c93d27bdfc7a68469be33bd8be95630e6a/grub-core/net/drivers/i386/pc/pxe.c#L259)
2. When running in VirtualBox, I can get GRUB to send DNS requests manually with the net_nslookup command.
3. When GRUB is in prefer-ipv4 mode (default), it tries to send one A DNS request followed by an IPv6 AAAA request.
4. Looking in Wireshark, I can see it just sending two AAAA requests instead (seems like the AAAA query contents are somehow clobbering the A query), separated by about 0.2ms.
5. When I set debug=dns in GRUB, the delay of debug-print-to-console seems to introduce enough delay that I see separate A and AAAA requests in Wireshark (now separated by about 1ms).

The best explanation I have for these observations is that VirtualBox's UNDI/PXE implementation is not mixing well with GRUB's extreme transmit buffer reuse, and causing a sufficiently quick sequence of transmits to clobber previous packets' contents.

I'm not that familiar with PXE or UNDI API requirements, but it seems like the driver should not return without at least making a copy of the data buffer, even if it doesn't transmit the packet immediately? In any case, would hope someone can take a look at the spec and determine whether this is actually a bug on VirtualBox's side or GRUB's.

Thanks in advance!"	henryptung
5624	PXE does not work with virtio	other	VirtualBox 3.1.0	2009-12-01T15:48:04Z	2009-12-01T18:53:54Z	2009-12-01T18:53:54Z	"Hello,

If virtio-net is used, PXE does not work. It fails with the error:

Unknown Ethernet controller! Aborting PXE boot...

The workarround is to revert to the old nic (intel/pcnet)"	Luiz Angelo Daros de Luca
17580	PulseAudio-related segmentation fault from PowerShell beeps	Windows	VirtualBox 5.2.8	2018-03-01T22:22:38Z	2018-03-02T09:12:00Z	2018-03-02T09:12:00Z	"I previously reported this issue as https://bugs.debian.org/889791 and was requested to report it here.

On a Debian buster/sid amd64 host, using virtualbox 5.2.8-dfsg-1 packages, with kernel 4.15.7, when running a Windows 7 guest using the PulseAudio host audio driver and ""ICH AC97"" audio controller, running PowerShell and causing repeated beeping (e.g. by pressing `^G` repeatedly and `<Enter>` occasionally) will cause VirtualBox to crash with SIGSEGV.

I was able to reproduce the issue using the Microsoft-provided [https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/ ""IE8 on Win7 (x86)"" VM image] after installing the [http://www.realtek.com.tw/downloads/downloadsCheck.aspx?Langid=1&PNid=23&PFid=23&Level=4&Conn=3&DownTypeID=3&GetDown=false Realtek AC'97 Audio Codecs] but was unable to reproduce it from terminal beeps using a Linux image.  I was also unable to reproduce the issue with the ""Intel HD Audio"" audio controller using 5.2.8-dfsg-1, although it was previously reproducible with 5.2.6-dfsg-3+b1.

I will attach VBox.log and a backtrace momentarily.

Thanks,
Kevin

Note: This sounds similar to https://www.virtualbox.org/ticket/15725 which was closed for lack of follow-up."	kevinoid
19984	PulseAudio not working on Fedora 33	other		2020-10-20T18:53:34Z	2020-10-25T21:57:40Z	2020-10-25T21:57:40Z	"Hi there,
I've been using VirtualBox version 6.1.97 r140489 and r140902 (Q.t 5.6.1) which I compiled myself.
What I noticed is that if I pick PulseAudio on the host, both Windows 10 Enterprise x64 and Windows XP Professional x86 are completely silent and on playback, they fail, with players not showing any kind of progress.
If I choose ALSA, however, audio works, but the guest cannot receive any input from the microphone of the host.
I also tried to make a brand new virtual machine with Win10 and it didn't change, I was able to reproduce the error.
The host is Fedora 33 x64, kernel 5.8.15.
I just wanted to let you know so that you can get it fixed before releasing a new stable version.

By looking at the logs https://pastebin.com/dwYh7C6i it seems that the problem lies here:

00:00:01.525860 PulseAudio: Using v13.99.0

00:00:01.527615 PulseAudio: Retrieving server information ...

but then it gets stuck on ""Retrieving server information""

00:01:39.235641 PulseAudio: Retrieving server information ...

00:01:39.243184 PulseAudio: Retrieving server information ...

00:01:39.246628 PulseAudio: Retrieving server information ...

00:01:39.254586 PulseAudio: Retrieving server information ...

00:01:39.257787 PulseAudio: Retrieving server information ...

00:01:39.269556 PulseAudio: Retrieving server information ...

00:01:39.282748 PulseAudio: Retrieving server information ...

00:01:39.291351 PulseAudio: Retrieving server information ...

00:01:39.300245 PulseAudio: Retrieving server information ...

00:01:39.304005 PulseAudio: Retrieving server information ...

00:01:39.306203 PulseAudio: Retrieving server information ...

00:01:39.308411 PulseAudio: Retrieving server information ...

00:01:39.311230 PulseAudio: Retrieving server information ...

00:01:39.323857 PulseAudio: Retrieving server information ...

00:01:39.337777 PulseAudio: Retrieving server information ...

00:01:39.346414 PulseAudio: Retrieving server information ...

00:01:39.356345 PulseAudio: Retrieving server information ...

00:01:39.360085 PulseAudio: Retrieving server information ...

00:01:39.362385 PulseAudio: Retrieving server information ...

00:01:39.365149 PulseAudio: Retrieving server information ...

00:01:39.368284 PulseAudio: Retrieving server information ...

00:01:39.381721 PulseAudio: Retrieving server information ...

00:01:39.396202 PulseAudio: Retrieving server information ...

00:01:39.408159 PulseAudio: Retrieving server information ...

00:01:39.417439 PulseAudio: Retrieving server information ...

00:01:39.421454 PulseAudio: Retrieving server information ...

00:01:39.424015 PulseAudio: Retrieving server information ...

00:01:39.427194 PulseAudio: Retrieving server information ...

You can see the full logs in the pastebin if you're interested, though.

Cheers,
Frank."	FranceBB
17934	PulseAudio failed to init context	Linux	VirtualBox 5.2.18	2018-08-16T13:59:13Z	2018-09-09T17:50:51Z	2018-09-09T17:50:51Z	"Host: Ubuntu 16.04[[BR]]
Guest: Ubuntu 16.04

updated VBox from 5.2.16 to 5.2.18;[[BR]]
installed extpack 5.2.18;[[BR]]
rebooted host;[[BR]]
start guest, get error as below;[[BR]]
install guest additions 5.2.18 in guest;[[BR]]
shutdown guest;[[BR]]
restart guest VM, get same error as before (log excerpt):


{{{
00:00:00.801653 Audio: Initializing PulseAudio driver
00:00:30.807983 PulseAudio: Failed to initialize context (state 5)
00:00:30.808320 Audio: Initialization of host backend failed with VERR_AUDIO_BACKEND_INIT_FAILED
00:00:30.808478 Audio: Initializing NULL driver
00:00:30.808523 VM: Raising runtime error 'HostAudioNotResponding' (fFlags=0x0)
00:00:30.808538 Console: VM runtime error: fatal=false, errorID=HostAudioNotResponding message=""Host audio backend initialization has failed. Selecting the NULL audio backend with the consequence that no sound is audible""
}}}

As the error msg says there is no guest audio playing through the host.

Host audio itself is ok, i.e. all audio functions on host are intact.

"	sunrider
17971	Protocol error when using PHP rename over shared folders.	Windows	VirtualBox 5.2.18	2018-09-06T18:45:34Z	2018-09-06T18:45:34Z	2018-09-06T18:45:34Z	"I am trying to rename/move a file that is living in a directory and I am giving a new name to the file and a new directory as well. Below is an snippet of such code:

{{{
rename($currentFilePath, $newname);
}}}

For some reason `rename()` is returning an error like the following:

> Protocol error var/www/html/editor/application/models/forms_model.php 455

I am trying now executing the command `mv` directly into the VM and this is the result:

{{{
$ mv /var/www/html/epa_editor/public/epa_forms/archive/Clone_16621_SamplePDFFile_5mb.pdf ""/var/www/html/epa _editor/public/epa_forms/stage/testing (Clone of Form #: 15615).pdf""
    mv: cannot move `/var/www/html/epa_editor/public/epa_forms/archive/Clone_16621_SamplePDFFile_5mb.pdf' to `/var/www/html/epa_editor/public/epa_forms/stage/testing (Clone of Form #: 15615).pdf': Protocol error
}}}

So apparently is a VBox issue with shared folders that has not been fixed. 

Related issues closed as ""fixed"":

 * https://www.virtualbox.org/ticket/1393
 * https://www.virtualbox.org/ticket/8463
 * https://www.virtualbox.org/ticket/1393
 * https://www.virtualbox.org/ticket/1321

The original issue was reported at SO (https://stackoverflow.com/questions/52209856/php-5-3-3-rename-function-fails-with-protocol-error) looking for help but it's not a PHP error but VBox.

  [1]: http://php.net/manual/en/function.rename.php
  [2]: https://stackoverflow.com/questions/19139434/php-move-a-file-into-a-different-folder-on-the-server
  [3]: https://www.virtualbox.org/ticket/1393"	reynierpm
20147	Problems when masquerade is enabled on host	Linux	VirtualBox 6.1.16	2021-01-22T19:27:56Z	2021-01-22T19:27:56Z	2021-01-22T19:27:56Z	"Steps to reproduce issue:

1. Configure host linux with firewalld  + enable masquerade on public zone (or configuration alike with iptables or nftables by hand)
2. Test access to both http and https on guest side
3. Disable masquerade on host and repeat 2

If netfilter masquerading is enabled on host, and guest is in bridge modem, both http and https don't work.

For example:

{{{

curl -I http://www.virtualbox.org
curl: (56) Recv failure: Connection reset by peer
root@techier-glossa:~# curl -I https://www.virtualbox.org
curl: (35) OpenSSL SSL_connect: Connection reset by peer in connection to www.virtualbox.org:443
}}}


If I disable netfilter masquerading, it works.

In bridge mode it should not concern at all if host is doing that.

This the configuration of firewalld:

[root@munster ~]# firewall-cmd --zone=lxc --list-all   

{{{
lxc (active)
  target: ACCEPT
  icmp-block-inversion: no
  interfaces: lxcbr0
  sources: 
  services: 
  ports: 
  protocols: 
  masquerade: no
  forward-ports: 
  source-ports: 
  icmp-blocks: 
  rich rules: 
[root@munster ~]# firewall-cmd --zone=libvirt --list-all
libvirt (active)
  target: ACCEPT
  icmp-block-inversion: no
  interfaces: virbr0
  sources: 
  services: dhcp dhcpv6 dns ssh tftp
  ports: 
  protocols: icmp ipv6-icmp
  masquerade: no
  forward-ports: 
  source-ports: 
  icmp-blocks: 
  rich rules: 
        rule priority=""32767"" reject
[root@munster ~]# firewall-cmd --zone=public --list-all
public (active)
  target: default
  icmp-block-inversion: no
  interfaces: wlp108s0
  sources: 
  services: dhcpv6-client kdeconnect mdns ssh
  ports: 
  protocols: 
  masquerade: yes
  forward-ports: 
  source-ports: 
  icmp-blocks: 
  rich rules: 

}}}



As far I know, In bridge mode it should not concern at all if host is doing that, should it?

Thanks in advance"	sblk
19475	Problems in guest settings with too many CPUs present at the host.	all	VirtualBox 6.1.4	2020-04-10T01:08:41Z	2020-04-10T21:14:10Z	2020-04-10T21:14:10Z	"If there are more than 32 CPU cores present at the host computer, the guest settings CPU-slider-bar shows only red, but the slider is slidable anyway.

After limiting the number of available cores of the host to 32 or less, the guest settings seem to act normal.

As the host (IBM System X3850) has four 10-core-XEON 8870 CPUs, there are 40 cores (80 threads) altogether, which I would like to use entirely."	Orbiter
18222	Problem with VBoxAutostart and possible workaround	all	VirtualBox 6.0.0	2018-12-22T10:39:26Z	2018-12-22T10:39:26Z	2018-12-22T10:39:26Z	"Hello,
in the last days I've discovered a problem which seems to be a bug in the virtualbox autostart service. Here follows the overview now:

How to reproduce?
Create several virtual machines and add them to the autostart of VirtualBox by following e.g. that guide (it doesn't matter which you choose) https://pgaskin.net/linux-tips/configuring-virtualbox-autostart/ . Now set also the ""autostop-type"" of all your autostart VMs to ""savestate"". If you reboot your system now, all VMs will crash and only the first VM will be automatically started, the rest stays off.

What is my system?
It could be reproduced using a fresh installed debian 9 and the virtualbox version 6-RC1 (installed by https://wiki.debian.org/VirtualBox).

What is the reason for that failure?
If you add more than two VMs to the autostart, the script ""vboxautostart-service.sh"" will start in the line
{{{
start_daemon `basename $user | sed -ne ""s/\(.*\).start/\1/p""` $binary $PARAMS > /dev/null 2>&1
}}}
multiple instances of VBoxAutostart - the second one will crash, because an other instace is already running. That causes a return of the exit code of 1 - the systemd envroiment (activated by that file /lib/systemd/system/vboxautostart-service.service) take that as a failure of the service and marks it as crashed too. If you now try to stop the service by hand or reboots the system systemd will (i guess) skip the stop part of the script, because the service is not running / crashed - regardless that a VM is running. That causes the system not to stop and wait for the VMs and let them crash.

How to fix?
Simply remove the ""--background""-flag from the parameter list of the start procedure.
{{{
PARAMS=""--background --start --config $VBOXAUTOSTART_CONFIG""
}}}
->
{{{
PARAMS=""--start --config $VBOXAUTOSTART_CONFIG""
}}}
Now the bootup maybe takes some more time, but all VMs are started correctly and also gets correctly shutdowned impliced by the ""autostop-type"" setting.

Thanks for reading this (short) report,
Simonmicro"	Simonmicro
8405	Problem with the graphical abilities of a windows xp guest running unity3d	Windows	VirtualBox 4.0.4	2011-02-22T20:57:13Z	2015-03-12T10:26:24Z	2015-03-12T10:26:24Z	"The programm unity3d( a game editor) is verry unhappy in a Virtualbox enviroment.
It is exrtreme in a manner, that the program is not able to run more than some minutes and with heavy visual impairements(it is stable in a native windows installation).

You can find the program under:

http://unity3d.com/unity/download/

I think here is the posebility to improve the graphical abilities of virtualbox.


Greetings
"	anonymous
17609	problem with kernel	other	VirtualBox 5.2.8	2018-03-08T18:30:30Z	2018-03-08T18:30:30Z	2018-03-08T18:30:30Z	"I run kali linux as OS , i have installed the vbox version 5.2.8 
and i have an issue with ubuntu virtual machines everything goes well at the beginning then , the  same issue appear and at a certain time the virtual machine does not work anymore and i have this error message :





Code d'erreur : 
NS_ERROR_FAILURE (0x80004005)
Composant : 
SessionMachine
Interface : 
ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}




also i can't run this commande : 


 sudo /etc/init.d/vboxdrv setup 


then i get this message:

bash: /etc/init.d/vboxdrv: Aucun fichier ou dossier de ce type

 


"	amine
17021	Problem showing a bsod (blue screen) in the guest machine	Windows	VirtualBox 5.1.26	2017-08-18T18:10:18Z	2017-08-26T16:14:44Z	2017-08-26T16:14:44Z	"
When i have a bsod (blue screen) in the guest machine Windows 10,
then i don't view the bsod.
I can not know what is written in the BSOD.
I think this problem comes from the driver graphics Virtualbox."	Sizy458
18095	Problem input audio	Windows	VirtualBox 5.2.18	2018-11-01T20:06:13Z	2018-11-04T14:37:06Z	2018-11-04T14:37:06Z	"I tested recording audio since audacity runned in the host machine ,it's work fine !

On Goldwave runned in the guest machine i note :
I find that the record level sound of its saturates at
33% and 
that virtualbox regresses !!."	Sizy458
11462	Problem font with VirtualBox from a terminal in Red Hat 6.2	Linux	VirtualBox 4.2.6	2013-02-06T13:48:27Z	2013-02-22T14:11:53Z	2013-02-22T14:11:53Z	"Hi, 
When we launched !VirtualBox, we had only ""squares"" on the GUI.
{{{
[root# VirtualBox 
Xlib:  extension ""SYNC"" missing on display ""10.102.130.2:32.0"".
}}}
And firstable, we had a failed installation with vboxpci 
{{{
[root@opisidb1 log]# /etc/init.d/vboxdrv setup
Stopping VirtualBox kernel modules                         [  OK  ]
Uninstalling old VirtualBox DKMS kernel modulesWARNING: /lib/modules/2.6.32-220.13.1.el6.x86_64/extra/vboxpci.ko needs unknown symbol kmem_cache_alloc_trace
                                                           [  OK  ]
Trying to register the VirtualBox kernel modules using DKMSWARNING: /lib/modules/2.6.32-220.13.1.el6.x86_64/extra/vboxpci.ko needs unknown symbol kmem_cache_alloc_trace
                                                           [  OK  ]
Starting VirtualBox kernel modules                         [FAILED]
  (modprobe vboxpci failed. Please use 'dmesg' to find out why)

root#dmesg
vboxdrv: Found 8 processor cores.
vboxdrv: fAsync=0 offMin=0x51c offMax=0x28308
vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
vboxdrv: Successfully loaded version 4.2.6 (interface 0x001a0004).
vboxpci: Unknown symbol kmem_cache_alloc_trace
vboxdrv: Found 8 processor cores.
vboxdrv: fAsync=0 offMin=0x62c offMax=0x2a7f8
vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
vboxdrv: Successfully loaded version 4.2.6 (interface 0x001a0004).
vboxpci: Unknown symbol kmem_cache_alloc_trace
warning: `VirtualBox' uses 32-bit capabilities (legacy support in use)
vboxdrv: Found 8 processor cores.
vboxdrv: fAsync=0 offMin=0x664 offMax=0x2a8d0
vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
vboxdrv: Successfully loaded version 4.2.6 (interface 0x001a0004).
vboxpci: Unknown symbol kmem_cache_alloc_trace
vboxdrv: Found 8 processor cores.
vboxdrv: fAsync=0 offMin=0x4fc offMax=0x27658
vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
vboxdrv: Successfully loaded version 4.2.6 (interface 0x001a0004).
vboxpci: Unknown symbol kmem_cache_alloc_trace
}}}"	fornesi
18245	Prevent boot if Shared folder is not available or Require Shared folder in order to boot	Windows	VirtualBox 6.0.0	2018-12-28T18:52:56Z	2019-01-03T16:01:54Z	2019-01-03T16:01:54Z	I searched but could not find an answer for this. Is there a way to prevent a guest system from booting if the attached Shared Folder is unavailable? I realize you get a prompt disclosing this fact, but I would like to prevent the VM from booting.	jim.rather
15652	PowerDown and DisplayRefresh race condition	all	VirtualBox 5.0.20	2016-07-21T05:46:38Z	2016-11-04T10:58:38Z	2016-11-04T10:58:38Z	"Sometimes VBoxHeadless crash happens:
{{{
Program terminated with signal SIGSEGV, Segmentation fault.
#0  __memcpy_sse2_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:33
33      ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S: No such file or directory.

(gdb) thread apply all bt
Thread 28 (Thread 0x7fdb3da64700 (LWP 6747)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007fdb3cfa2472 in VBoxNsprPR_WaitCondVar (cvar=0x6ca700, timeout=4294967295) at ../VirtualBox-5.0.20/src/libs/xpcom18a4/nsprpub/pr/src/pthreads/ptsynch.c:392
#2  0x00007fdb3cfa2702 in VBoxNsprPR_Wait (mon=0x6d4090, timeout=<optimized out>) at ../VirtualBox-5.0.20/src/libs/xpcom18a4/nsprpub/pr/src/pthreads/ptsynch.c:571
#3  0x00007fdb360e3deb in Wait (interval=4294967295, this=0x7fdb3da63de0) at ../VirtualBox-5.0.20/src/libs/xpcom18a4/xpcom/threads/nsAutoLock.h:285
#4  DConnectWorker::Run (this=0x6c9fd0) at ../VirtualBox-5.0.20/src/libs/xpcom18a4/ipc/ipcd/extensions/dconnect/src/ipcDConnectService.cpp:2956
#5  0x00007fdb3cf91607 in nsThread::Main (arg=0x6ca280) at ../VirtualBox-5.0.20/src/libs/xpcom18a4/xpcom/threads/nsThread.cpp:118
#6  0x00007fdb3cfa11a7 in _pt_root (arg=0x6d4330) at ../VirtualBox-5.0.20/src/libs/xpcom18a4/nsprpub/pr/src/pthreads/ptthread.c:224
#7  _pt_iprt_root (Thread=<optimized out>, pvUser=0x6d4330) at ../VirtualBox-5.0.20/src/libs/xpcom18a4/nsprpub/pr/src/pthreads/ptthread.c:272
#8  0x00007fdb3d312274 in rtThreadMain (pThread=0x6d44a0, NativeThread=140579608872704, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#9  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x6d44a0) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#10 0x00007fdb3d676184 in start_thread (arg=0x7fdb3da64700) at pthread_create.c:312
#11 0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 27 (Thread 0x7fdb05355700 (LWP 6771)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238
#1  0x00007fdb3d3942b5 in rtSemEventWait (fAutoResume=true, cMillies=20000, hEventSem=0x7fdb184a0200) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/linux/../posix/semevent-posix.cpp:479
#2  RTSemEventWait (hEventSem=0x7fdb184a0200, cMillies=20000) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/linux/../posix/semevent-posix.cpp:496
#3  0x00007fdb076397ef in drvACPIPoller (pDrvIns=0x7fdb1849f390, pThread=0x7fdb1849f500) at ../VirtualBox-5.0.20/src/VBox/Devices/PC/DrvACPI.cpp:894
#4  0x00007fdb0763a3f1 in drvACPIPoller (pDrvIns=<optimized out>, pThread=<optimized out>) at ../VirtualBox-5.0.20/src/VBox/Devices/PC/DrvACPI.cpp:515
#5  0x00007fdb341c728b in pdmR3ThreadMain (Thread=0x7fdb1849f660, pvUser=0x7fdb1849f500) at ../VirtualBox-5.0.20/src/VBox/VMM/VMMR3/PDMThread.cpp:788
#6  0x00007fdb3d312274 in rtThreadMain (pThread=0x7fdb1849f660, NativeThread=140578661947136, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#7  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x7fdb1849f660) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#8  0x00007fdb3d676184 in start_thread (arg=0x7fdb05355700) at pthread_create.c:312
#9  0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 26 (Thread 0x7fdb3d941700 (LWP 6818)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007fdb3d394390 in rtSemEventWait (fAutoResume=true, cMillies=<optimized out>, hEventSem=0x7fdb28007cd0)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/linux/../posix/semevent-posix.cpp:383
#2  RTSemEventWait (hEventSem=0x7fdb28007cd0, cMillies=<optimized out>) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/linux/../posix/semevent-posix.cpp:496
#3  0x00007fdb35545451 in videoRecThread (Thread=<optimized out>, pvUser=0x7fdb280087f0) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/VideoRec.cpp:397
#4  0x00007fdb3d312274 in rtThreadMain (pThread=0x7fdb28008d30, NativeThread=140579607680768, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#5  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x7fdb28008d30) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#6  0x00007fdb3d676184 in start_thread (arg=0x7fdb3d941700) at pthread_create.c:312
#7  0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 25 (Thread 0x7fdb3d8c0700 (LWP 6752)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238
#1  0x00007fdb3d3942b5 in rtSemEventWait (fAutoResume=true, cMillies=2000, hEventSem=0x7fdb20003600) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/linux/../posix/semevent-posix.cpp:479
#2  RTSemEventWait (hEventSem=0x7fdb20003600, cMillies=2000) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/linux/../posix/semevent-posix.cpp:496
#3  0x00007fdb3548f0fd in waitRemoteUSBThreadEvent (cMillies=2000, this=0x7fdb280070a0) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/ConsoleVRDPServer.cpp:3070
#4  threadRemoteUSB (self=<optimized out>, pvUser=0x7fdb280070a0) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/ConsoleVRDPServer.cpp:3047
#5  0x00007fdb3d312274 in rtThreadMain (pThread=0x7fdb20003670, NativeThread=140579607152384, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#6  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x7fdb20003670) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#7  0x00007fdb3d676184 in start_thread (arg=0x7fdb3d8c0700) at pthread_create.c:312
#8  0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 24 (Thread 0x7fdb054d8700 (LWP 6768)):
#0  0x00007fdb3c7021e7 in ioctl () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fdb3d39c78d in suplibOsIOCtl (pThis=<optimized out>, uFunction=<optimized out>, pvReq=<optimized out>, cbReq=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/HostDrivers/Support/linux/SUPLib-linux.cpp:184
#2  0x00007fdb3d39a031 in SUPR3CallVMMR0Ex (pVMR0=<optimized out>, idCpu=<optimized out>, uOperation=<optimized out>, u64Arg=<optimized out>, pReqHdr=0x7fdb054d7cd0)
    at ../VirtualBox-5.0.20/src/VBox/HostDrivers/Support/SUPLib.cpp:683
#3  0x00007fdb341beba1 in pdmR3DrvHlp_SUPCallVMMR0Ex (pDrvIns=0x7fdb25eb81c0, uOperation=52, pvArg=0x7fdb054d7cd0, cbArg=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/VMM/VMMR3/PDMDriver.cpp:1437
#4  0x00007fdb0763677a in PDMDrvHlpSUPCallVMMR0Ex (cbArg=24, pvArg=0x7fdb054d7cd0, uOperation=52, pDrvIns=0x7fdb25eb81c0) at ../VirtualBox-5.0.20/include/VBox/vmm/pdmdrv.h:1736
#5  drvR3IntNetRecvRun (pThis=pThis@entry=0x7fdb25eb8280) at ../VirtualBox-5.0.20/src/VBox/Devices/Network/DrvIntNet.cpp:856
#6  0x00007fdb07637487 in drvR3IntNetRecvThread (ThreadSelf=<optimized out>, pvUser=0x7fdb25eb8280) at ../VirtualBox-5.0.20/src/VBox/Devices/Network/DrvIntNet.cpp:904
#7  0x00007fdb3d312274 in rtThreadMain (pThread=0x7fdb184445a0, NativeThread=140578663532288, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#8  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x7fdb184445a0) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#9  0x00007fdb3d676184 in start_thread (arg=0x7fdb054d8700) at pthread_create.c:312
#10 0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 23 (Thread 0x7fdb3da85700 (LWP 6746)):
#0  0x00007fdb3c6fdfdd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fdb3cfa4427 in poll (__timeout=-1, __nfds=2, __fds=0x7fdb3da84b90) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46
#2  _pr_poll_with_poll (pds=0x6c8ea8, npds=2, timeout=4294967295) at ../VirtualBox-5.0.20/src/libs/xpcom18a4/nsprpub/pr/src/pthreads/ptio.c:3906
#3  0x00007fdb3cfa6070 in VBoxNsprPR_Poll (pds=<optimized out>, npds=<optimized out>, timeout=<optimized out>)
    at ../VirtualBox-5.0.20/src/libs/xpcom18a4/nsprpub/pr/src/pthreads/ptio.c:4308
#4  0x00007fdb360e67df in ConnThread (arg=0x6c8ea0) at ../VirtualBox-5.0.20/src/libs/xpcom18a4/ipc/ipcd/client/src/ipcConnectionUnix.cpp:336
#5  0x00007fdb3cfa11a7 in _pt_root (arg=0x6c91b0) at ../VirtualBox-5.0.20/src/libs/xpcom18a4/nsprpub/pr/src/pthreads/ptthread.c:224
#6  _pt_iprt_root (Thread=<optimized out>, pvUser=0x6c91b0) at ../VirtualBox-5.0.20/src/libs/xpcom18a4/nsprpub/pr/src/pthreads/ptthread.c:272
#7  0x00007fdb3d312274 in rtThreadMain (pThread=0x6c9320, NativeThread=140579609007872, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#8  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x6c9320) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#9  0x00007fdb3d676184 in start_thread (arg=0x7fdb3da85700) at pthread_create.c:312
#10 0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 22 (Thread 0x7fdb05126700 (LWP 6854)):
#0  0x00007fdb3c7021e7 in ioctl () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fdb3d39c78d in suplibOsIOCtl (pThis=<optimized out>, uFunction=<optimized out>, pvReq=<optimized out>, cbReq=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/HostDrivers/Support/linux/SUPLib-linux.cpp:184
#2  0x00007fdb3d396dba in supSemOp2 (pSession=<optimized out>, u64Arg=<optimized out>, uOp=0, hSem=<optimized out>, uType=0)
    at ../VirtualBox-5.0.20/src/VBox/HostDrivers/Support/SUPLibSem.cpp:68
#3  SUPSemEventWaitNoResume (pSession=<optimized out>, hEvent=<optimized out>, cMillies=<optimized out>) at ../VirtualBox-5.0.20/src/VBox/HostDrivers/Support/SUPLibSem.cpp:138
#4  0x00007fdb342c24ef in pdmR3R0CritSectEnterContended (pCritSect=0x7fdb240473c8, hNativeSelf=140578659657472, pSrcPos=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/VMM/VMMAll/PDMAllCritSect.cpp:172
#5  0x00007fdb075ca22a in vgaPortSetRenderVRAM (pInterface=0x7fdb24044e10, fRender=<optimized out>) at ../VirtualBox-5.0.20/src/VBox/Devices/Graphics/DevVGA.cpp:5315
#6  0x00007fdb35496ed3 in Display::i_handleDisplayResize (this=this@entry=0x7fdb28003a00, uScreenId=uScreenId@entry=0, bpp=bpp@entry=32, pvVRAM=0x7fdb05701000, cbLine=4608, w=1152, h=864, flags=1)
    at ../VirtualBox-5.0.20/src/VBox/Main/src-client/DisplayImpl.cpp:911
#7  0x00007fdb354982b5 in Display::i_notifyPowerDown (this=0x7fdb28003a00) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/DisplayImpl.cpp:1557
#8  0x00007fdb3544f060 in Console::i_powerDown (this=0x7fdb28001180, aProgress=0x7fdb280083a0) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/ConsoleImpl.cpp:7630
#9  0x00007fdb35450358 in Console::i_powerDownThread (Thread=<optimized out>, pvUser=0x7fdb28008210) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/ConsoleImpl.cpp:10074
#10 0x00007fdb3d312274 in rtThreadMain (pThread=0x7fdb29978920, NativeThread=140578659657472, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#11 0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x7fdb29978920) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#12 0x00007fdb3d676184 in start_thread (arg=0x7fdb05126700) at pthread_create.c:312
#13 0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 21 (Thread 0x7fdb3da43700 (LWP 6748)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238
#1  0x00007fdb3d3942b5 in rtSemEventWait (fAutoResume=true, cMillies=30000, hEventSem=0x6d7960) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/linux/../posix/semevent-posix.cpp:479
#2  RTSemEventWait (hEventSem=0x6d7960, cMillies=30000) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/linux/../posix/semevent-posix.cpp:496
#3  0x00007fdb354bdce7 in VirtualBoxClient::SVCWatcherThread (ThreadSelf=<optimized out>, pvUser=0x6d6560) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/VirtualBoxClientImpl.cpp:284
#4  0x00007fdb3d312274 in rtThreadMain (pThread=0x6d79d0, NativeThread=140579608737536, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#5  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x6d79d0) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#6  0x00007fdb3d676184 in start_thread (arg=0x7fdb3da43700) at pthread_create.c:312
#7  0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 20 (Thread 0x7fdb053d6700 (LWP 6770)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238
#1  0x00007fdb3d394a11 in rtSemEventMultiPosixWaitTimed (pThis=0x7fdb1849e030, fFlags=<optimized out>, uTimeout=<optimized out>, pSrcPos=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/linux/../posix/semeventmulti-posix.cpp:562
#2  0x00007fdb07668509 in ohciR3ThreadFrame (pDevIns=<optimized out>, pThread=<optimized out>) at ../VirtualBox-5.0.20/src/VBox/Devices/USB/DevOHCI.cpp:3977
#3  0x00007fdb341c728b in pdmR3ThreadMain (Thread=0x7fdb1849e300, pvUser=0x7fdb1849e1a0) at ../VirtualBox-5.0.20/src/VBox/VMM/VMMR3/PDMThread.cpp:788
#4  0x00007fdb3d312274 in rtThreadMain (pThread=0x7fdb1849e300, NativeThread=140578662475520, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#5  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x7fdb1849e300) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#6  0x00007fdb3d676184 in start_thread (arg=0x7fdb053d6700) at pthread_create.c:312
#7  0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 19 (Thread 0x7fdb3d9c2700 (LWP 6749)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238
#1  0x00007fdb3d3942b5 in rtSemEventWait (fAutoResume=true, cMillies=999, hEventSem=0x7fdb2800e3e0) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/linux/../posix/semevent-posix.cpp:479
#2  RTSemEventWait (hEventSem=0x7fdb2800e3e0, cMillies=999) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/linux/../posix/semevent-posix.cpp:496
#3  0x00007fdb3d360953 in rtTimerLRThread (hThreadSelf=<optimized out>, pvUser=0x7fdb2800e390) at ../VirtualBox-5.0.20/src/VBox/Runtime/generic/timerlr-generic.cpp:341
#4  0x00007fdb3d312274 in rtThreadMain (pThread=0x7fdb2800bfd0, NativeThread=140579608209152, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#5  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x7fdb2800bfd0) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#6  0x00007fdb3d676184 in start_thread (arg=0x7fdb3d9c2700) at pthread_create.c:312
#7  0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 18 (Thread 0x7fdb052d4700 (LWP 6772)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007fdb3d394390 in rtSemEventWait (fAutoResume=true, cMillies=<optimized out>, hEventSem=0x7fdb184a05f0)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/linux/../posix/semevent-posix.cpp:383
#2  RTSemEventWait (hEventSem=0x7fdb184a05f0, cMillies=<optimized out>) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/linux/../posix/semevent-posix.cpp:496
#3  0x00007fdb075b6d8e in usbHidUrbReap (pUsbIns=0x7fdb184a0320, cMillies=4294967295) at ../VirtualBox-5.0.20/src/VBox/Devices/Input/UsbMouse.cpp:1686
#4  0x00007fdb07673aea in vusbUrbDoReapAsyncDev (pDev=0x7fdb184a3530, cMillies=4294967295) at ../VirtualBox-5.0.20/src/VBox/Devices/USB/VUSBUrb.cpp:2067
#5  0x00007fdb0766aeb3 in vusbDevUrbIoThread (hThread=<optimized out>, pvUser=0x7fdb184a3530) at ../VirtualBox-5.0.20/src/VBox/Devices/USB/VUSBDevice.cpp:1155
#6  0x00007fdb3d312274 in rtThreadMain (pThread=0x7fdb184a4400, NativeThread=140578661418752, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#7  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x7fdb184a4400) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#8  0x00007fdb3d676184 in start_thread (arg=0x7fdb052d4700) at pthread_create.c:312
#9  0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 17 (Thread 0x7fdb36aef700 (LWP 6773)):
#0  0x00007fdb3c702c53 in select () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fdb276842fc in ?? () from /usr/lib/x86_64-linux-gnu/libvncserver.so.0
#2  0x00007fdb3d676184 in start_thread (arg=0x7fdb36aef700) at pthread_create.c:312
#3  0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 16 (Thread 0x7fdb05457700 (LWP 6769)):
#0  0x00007fdb3c7021e7 in ioctl () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fdb3d39c78d in suplibOsIOCtl (pThis=<optimized out>, uFunction=<optimized out>, pvReq=<optimized out>, cbReq=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/HostDrivers/Support/linux/SUPLib-linux.cpp:184
#2  0x00007fdb3d396dba in supSemOp2 (pSession=<optimized out>, u64Arg=<optimized out>, uOp=0, hSem=<optimized out>, uType=0)
    at ../VirtualBox-5.0.20/src/VBox/HostDrivers/Support/SUPLibSem.cpp:68
#3  SUPSemEventWaitNoResume (pSession=<optimized out>, hEvent=<optimized out>, cMillies=<optimized out>) at ../VirtualBox-5.0.20/src/VBox/HostDrivers/Support/SUPLibSem.cpp:138
#4  0x00007fdb0763639d in drvR3IntNetXmitThread (pDrvIns=0x7fdb25eb81c0, pThread=0x7fdb184450f0) at ../VirtualBox-5.0.20/src/VBox/Devices/Network/DrvIntNet.cpp:626
#5  0x00007fdb341c728b in pdmR3ThreadMain (Thread=0x7fdb18445250, pvUser=0x7fdb184450f0) at ../VirtualBox-5.0.20/src/VBox/VMM/VMMR3/PDMThread.cpp:788
#6  0x00007fdb3d312274 in rtThreadMain (pThread=0x7fdb18445250, NativeThread=140578663003904, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#7  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x7fdb18445250) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#8  0x00007fdb3d676184 in start_thread (arg=0x7fdb05457700) at pthread_create.c:312
#9  0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 15 (Thread 0x7fdb340fb700 (LWP 6751)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007fdb3d394892 in rtSemEventMultiPosixWaitIndefinite (pThis=0x7fdb20000b10, pSrcPos=<optimized out>, fFlags=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/linux/../posix/semeventmulti-posix.cpp:433
#2  0x00007fdb35539678 in HGCMThread::MsgGet (this=this@entry=0x7fdb20000a30, ppMsg=ppMsg@entry=0x7fdb340fadf0) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCMThread.cpp:543
#3  0x00007fdb35539e6e in hgcmMsgGet (hThread=hThread@entry=2147483649, ppMsg=ppMsg@entry=0x7fdb340fadf0) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCMThread.cpp:799
#4  0x00007fdb3553d31b in hgcmThread (ThreadHandle=2147483649, pvUser=<optimized out>) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCM.cpp:1812
#5  0x00007fdb35538d11 in hgcmWorkerThreadFunc (ThreadSelf=<optimized out>, pvUser=0x7fdb20000a30) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCMThread.cpp:194
#6  0x00007fdb3d312274 in rtThreadMain (pThread=0x7fdb20000c60, NativeThread=140579448010496, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#7  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x7fdb20000c60) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#8  0x00007fdb3d676184 in start_thread (arg=0x7fdb340fb700) at pthread_create.c:312
#9  0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 14 (Thread 0x7fdb0563b700 (LWP 6765)):
#0  0x00007fdb3c7021e7 in ioctl () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fdb3d39c78d in suplibOsIOCtl (pThis=<optimized out>, uFunction=<optimized out>, pvReq=<optimized out>, cbReq=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/HostDrivers/Support/linux/SUPLib-linux.cpp:184
#2  0x00007fdb3d396dba in supSemOp2 (pSession=<optimized out>, u64Arg=<optimized out>, uOp=0, hSem=<optimized out>, uType=0)
    at ../VirtualBox-5.0.20/src/VBox/HostDrivers/Support/SUPLibSem.cpp:68
#3  SUPSemEventWaitNoResume (pSession=<optimized out>, hEvent=<optimized out>, cMillies=<optimized out>) at ../VirtualBox-5.0.20/src/VBox/HostDrivers/Support/SUPLibSem.cpp:138
#4  0x00007fdb076ab218 in ahciAsyncIOLoop (pDevIns=<optimized out>, pThread=0x7fdb183aabd0) at ../VirtualBox-5.0.20/src/VBox/Devices/Storage/DevAHCI.cpp:6881
#5  0x00007fdb341c728b in pdmR3ThreadMain (Thread=0x7fdb183eac50, pvUser=0x7fdb183aabd0) at ../VirtualBox-5.0.20/src/VBox/VMM/VMMR3/PDMThread.cpp:788
#6  0x00007fdb3d312274 in rtThreadMain (pThread=0x7fdb183eac50, NativeThread=140578664986368, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#7  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x7fdb183eac50) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#8  0x00007fdb3d676184 in start_thread (arg=0x7fdb0563b700) at pthread_create.c:312
#9  0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 13 (Thread 0x7fdb24891700 (LWP 6761)):
#0  0x00007fdb3c648e3a in do_sigwaitinfo (info=0x7fdb24890d00, set=0x7fdb24890c80) at ../nptl/sysdeps/unix/sysv/linux/../../../../../sysdeps/unix/sysv/linux/sigwaitinfo.c:54
#1  __GI___sigwaitinfo (set=0x7fdb24890c80, info=0x7fdb24890d00) at ../nptl/sysdeps/unix/sysv/linux/../../../../../sysdeps/unix/sysv/linux/sigwaitinfo.c:81
#2  0x00007fdb3d391d55 in rttimerThread (hThreadSelf=<optimized out>, pvArg=<optimized out>) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/timer-posix.cpp:373
#3  0x00007fdb3d312274 in rtThreadMain (pThread=0x7fdb18354fc0, NativeThread=140579187529472, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#4  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x7fdb18354fc0) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#5  0x00007fdb3d676184 in start_thread (arg=0x7fdb24891700) at pthread_create.c:312
#6  0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 12 (Thread 0x7fdb0718e700 (LWP 6763)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007fdb3d394892 in rtSemEventMultiPosixWaitIndefinite (pThis=0x7fdb1c0042f0, pSrcPos=<optimized out>, fFlags=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/linux/../posix/semeventmulti-posix.cpp:433
#2  0x00007fdb35539678 in HGCMThread::MsgGet (this=this@entry=0x7fdb1c004470, ppMsg=ppMsg@entry=0x7fdb0718ddf8) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCMThread.cpp:543
#3  0x00007fdb35539e6e in hgcmMsgGet (hThread=hThread@entry=2147483689, ppMsg=ppMsg@entry=0x7fdb0718ddf8) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCMThread.cpp:799
#4  0x00007fdb3553adbc in hgcmServiceThread (ThreadHandle=2147483689, pvUser=0x7fdb1c0043a0) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCM.cpp:519
#5  0x00007fdb35538d11 in hgcmWorkerThreadFunc (ThreadSelf=<optimized out>, pvUser=0x7fdb1c004470) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCMThread.cpp:194
#6  0x00007fdb3d312274 in rtThreadMain (pThread=0x7fdb1c004630, NativeThread=140578693637888, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#7  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x7fdb1c004630) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#8  0x00007fdb3d676184 in start_thread (arg=0x7fdb0718e700) at pthread_create.c:312
#9  0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 11 (Thread 0x7fdb05700700 (LWP 6764)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007fdb3d394390 in rtSemEventWait (fAutoResume=true, cMillies=<optimized out>, hEventSem=0x7fdb183a5960)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/linux/../posix/semevent-posix.cpp:383
#2  RTSemEventWait (hEventSem=0x7fdb183a5960, cMillies=<optimized out>) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/linux/../posix/semevent-posix.cpp:496
#3  0x00007fdb343186df in pdmacFileAioMgrNormal (hThreadSelf=<optimized out>, pvUser=0x7fdb183a5890) at ../VirtualBox-5.0.20/src/VBox/VMM/VMMR3/PDMAsyncCompletionFileNormal.cpp:1626
#4  0x00007fdb3d312274 in rtThreadMain (pThread=0x7fdb183a5e00, NativeThread=140578665793280, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#5  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x7fdb183a5e00) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#6  0x00007fdb3d676184 in start_thread (arg=0x7fdb05700700) at pthread_create.c:312
#7  0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 10 (Thread 0x7fdb2629e700 (LWP 6759)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007fdb3d394390 in rtSemEventWait (fAutoResume=true, cMillies=<optimized out>, hEventSem=0x7fdb080013d0)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/linux/../posix/semevent-posix.cpp:383
#2  RTSemEventWait (hEventSem=0x7fdb080013d0, cMillies=<optimized out>) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/linux/../posix/semevent-posix.cpp:496
#3  0x00007fdb3d30fcee in RTReqQueueProcess (hQueue=0x7fdb08001350, cMillies=4294967295) at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/reqqueue.cpp:127
#4  0x00007fdb262a08fe in guestProp::Service::threadNotifyHost (self=<optimized out>, pvUser=0x7fdb080012d0)
    at ../VirtualBox-5.0.20/src/VBox/HostServices/GuestProperties/service.cpp:1531
#5  0x00007fdb3d312274 in rtThreadMain (pThread=0x7fdb08001440, NativeThread=140579214845696, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#6  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x7fdb08001440) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#7  0x00007fdb3d676184 in start_thread (arg=0x7fdb2629e700) at pthread_create.c:312
#8  0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 9 (Thread 0x7fdb3da87780 (LWP 6744)):
#0  0x00007fdb3c702c53 in select () at ../sysdeps/unix/syscall-template.S:81
#1  0x000000000040caab in com::waitForEventsOnXPCOM (pQueue=<optimized out>, cMsTimeout=cMsTimeout@entry=4294967295) at ../VirtualBox-5.0.20/src/VBox/Main/glue/NativeEventQueue.cpp:348
#2  0x000000000040cfcc in com::NativeEventQueue::processEventQueue (this=0x6c3af0, cMsTimeout=cMsTimeout@entry=4294967295)
    at ../VirtualBox-5.0.20/src/VBox/Main/glue/NativeEventQueue.cpp:524
#3  0x0000000000405c68 in TrustedMain (argc=argc@entry=7, argv=<optimized out>, envp=envp@entry=0x7ffd3e0fcf88)
    at ../VirtualBox-5.0.20/src/VBox/Frontends/VBoxHeadless/VBoxHeadless.cpp:1238
#4  0x0000000000403419 in main (argc=7, argv=0x6829f0, envp=0x7ffd3e0fcf88) at ../VirtualBox-5.0.20/src/VBox/Frontends/VBoxHeadless/VBoxHeadless.cpp:1376

Thread 8 (Thread 0x7fdb26a3d700 (LWP 6756)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007fdb3d394892 in rtSemEventMultiPosixWaitIndefinite (pThis=0x7fdb1c000a70, pSrcPos=<optimized out>, fFlags=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/linux/../posix/semeventmulti-posix.cpp:433
#2  0x00007fdb35539678 in HGCMThread::MsgGet (this=this@entry=0x7fdb1c000990, ppMsg=ppMsg@entry=0x7fdb26a3cdf8) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCMThread.cpp:543
#3  0x00007fdb35539e6e in hgcmMsgGet (hThread=hThread@entry=2147483651, ppMsg=ppMsg@entry=0x7fdb26a3cdf8) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCMThread.cpp:799
#4  0x00007fdb3553adbc in hgcmServiceThread (ThreadHandle=2147483651, pvUser=0x7fdb1c0008c0) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCM.cpp:519
#5  0x00007fdb35538d11 in hgcmWorkerThreadFunc (ThreadSelf=<optimized out>, pvUser=0x7fdb1c000990) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCMThread.cpp:194
#6  0x00007fdb3d312274 in rtThreadMain (pThread=0x7fdb1c000bc0, NativeThread=140579222836992, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#7  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x7fdb1c000bc0) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#8  0x00007fdb3d676184 in start_thread (arg=0x7fdb26a3d700) at pthread_create.c:312
#9  0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 7 (Thread 0x7fdb05599700 (LWP 6767)):
#0  0x00007fdb3c7021e7 in ioctl () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fdb3d39c78d in suplibOsIOCtl (pThis=<optimized out>, uFunction=<optimized out>, pvReq=<optimized out>, cbReq=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/HostDrivers/Support/linux/SUPLib-linux.cpp:184
#2  0x00007fdb3d396dba in supSemOp2 (pSession=<optimized out>, u64Arg=<optimized out>, uOp=0, hSem=<optimized out>, uType=0)
    at ../VirtualBox-5.0.20/src/VBox/HostDrivers/Support/SUPLibSem.cpp:68
#3  SUPSemEventWaitNoResume (pSession=<optimized out>, hEvent=<optimized out>, cMillies=<optimized out>) at ../VirtualBox-5.0.20/src/VBox/HostDrivers/Support/SUPLibSem.cpp:138
#4  0x00007fdb075e0678 in ataR3AsyncIOThread (ThreadSelf=<optimized out>, pvUser=0x7fdb25eb1ae8) at ../VirtualBox-5.0.20/src/VBox/Devices/Storage/DevATA.cpp:5483
#5  0x00007fdb3d312274 in rtThreadMain (pThread=0x7fdb1843eec0, NativeThread=140578664322816, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#6  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x7fdb1843eec0) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#7  0x00007fdb3d676184 in start_thread (arg=0x7fdb05599700) at pthread_create.c:312
#8  0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 6 (Thread 0x7fdb055ba700 (LWP 6766)):
#0  0x00007fdb3c7021e7 in ioctl () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fdb3d39c78d in suplibOsIOCtl (pThis=<optimized out>, uFunction=<optimized out>, pvReq=<optimized out>, cbReq=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/HostDrivers/Support/linux/SUPLib-linux.cpp:184
#2  0x00007fdb3d396dba in supSemOp2 (pSession=<optimized out>, u64Arg=<optimized out>, uOp=0, hSem=<optimized out>, uType=0)
    at ../VirtualBox-5.0.20/src/VBox/HostDrivers/Support/SUPLibSem.cpp:68
#3  SUPSemEventWaitNoResume (pSession=<optimized out>, hEvent=<optimized out>, cMillies=<optimized out>) at ../VirtualBox-5.0.20/src/VBox/HostDrivers/Support/SUPLibSem.cpp:138
#4  0x00007fdb075e0678 in ataR3AsyncIOThread (ThreadSelf=<optimized out>, pvUser=0x7fdb25eb1350) at ../VirtualBox-5.0.20/src/VBox/Devices/Storage/DevATA.cpp:5483
#5  0x00007fdb3d312274 in rtThreadMain (pThread=0x7fdb183ee710, NativeThread=140578664457984, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#6  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x7fdb183ee710) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#7  0x00007fdb3d676184 in start_thread (arg=0x7fdb055ba700) at pthread_create.c:312
#8  0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 5 (Thread 0x7fdb24810700 (LWP 6762)):
#0  0x00007fdb3d67db9d in nanosleep () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fdb3d39189d in RTThreadSleep (cMillies=100) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread2-posix.cpp:82
#2  0x00007fdb34318b5a in pdmR3NsTxThread (pVM=<optimized out>, pThread=0x7fdb18363db0) at ../VirtualBox-5.0.20/src/VBox/VMM/VMMR3/PDMNetShaper.cpp:418
#3  0x00007fdb341c73a3 in pdmR3ThreadMain (Thread=0x7fdb18363f10, pvUser=0x7fdb18363db0) at ../VirtualBox-5.0.20/src/VBox/VMM/VMMR3/PDMThread.cpp:792
#4  0x00007fdb3d312274 in rtThreadMain (pThread=0x7fdb18363f10, NativeThread=140579187001088, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#5  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x7fdb18363f10) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#6  0x00007fdb3d676184 in start_thread (arg=0x7fdb24810700) at pthread_create.c:312
#7  0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 4 (Thread 0x7fdb267b7700 (LWP 6757)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007fdb3d394892 in rtSemEventMultiPosixWaitIndefinite (pThis=0x7fdb1c0018e0, pSrcPos=<optimized out>, fFlags=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/linux/../posix/semeventmulti-posix.cpp:433
#2  0x00007fdb35539678 in HGCMThread::MsgGet (this=this@entry=0x7fdb1c001800, ppMsg=ppMsg@entry=0x7fdb267b6df8) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCMThread.cpp:543
#3  0x00007fdb35539e6e in hgcmMsgGet (hThread=hThread@entry=2147483658, ppMsg=ppMsg@entry=0x7fdb267b6df8) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCMThread.cpp:799
#4  0x00007fdb3553adbc in hgcmServiceThread (ThreadHandle=2147483658, pvUser=0x7fdb1c001730) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCM.cpp:519
#5  0x00007fdb35538d11 in hgcmWorkerThreadFunc (ThreadSelf=<optimized out>, pvUser=0x7fdb1c001800) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCMThread.cpp:194
#6  0x00007fdb3d312274 in rtThreadMain (pThread=0x7fdb1c001a30, NativeThread=140579220190976, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#7  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x7fdb1c001a30) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#8  0x00007fdb3d676184 in start_thread (arg=0x7fdb267b7700) at pthread_create.c:312
#9  0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 3 (Thread 0x7fdb2621d700 (LWP 6760)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007fdb3d394892 in rtSemEventMultiPosixWaitIndefinite (pThis=0x7fdb1c003630, pSrcPos=<optimized out>, fFlags=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/linux/../posix/semeventmulti-posix.cpp:433
#2  0x00007fdb35539678 in HGCMThread::MsgGet (this=this@entry=0x7fdb1c003550, ppMsg=ppMsg@entry=0x7fdb2621cdf8) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCMThread.cpp:543
#3  0x00007fdb35539e6e in hgcmMsgGet (hThread=hThread@entry=2147483684, ppMsg=ppMsg@entry=0x7fdb2621cdf8) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCMThread.cpp:799
#4  0x00007fdb3553adbc in hgcmServiceThread (ThreadHandle=2147483684, pvUser=0x7fdb1c003480) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCM.cpp:519
#5  0x00007fdb35538d11 in hgcmWorkerThreadFunc (ThreadSelf=<optimized out>, pvUser=0x7fdb1c003550) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCMThread.cpp:194
#6  0x00007fdb3d312274 in rtThreadMain (pThread=0x7fdb1c003780, NativeThread=140579214317312, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#7  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x7fdb1c003780) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#8  0x00007fdb3d676184 in start_thread (arg=0x7fdb2621d700) at pthread_create.c:312
#9  0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7fdb2652a700 (LWP 6758)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007fdb3d394892 in rtSemEventMultiPosixWaitIndefinite (pThis=0x7fdb1c0025a0, pSrcPos=<optimized out>, fFlags=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/linux/../posix/semeventmulti-posix.cpp:433
#2  0x00007fdb35539678 in HGCMThread::MsgGet (this=this@entry=0x7fdb1c002720, ppMsg=ppMsg@entry=0x7fdb26529df8) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCMThread.cpp:543
#3  0x00007fdb35539e6e in hgcmMsgGet (hThread=hThread@entry=2147483665, ppMsg=ppMsg@entry=0x7fdb26529df8) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCMThread.cpp:799
#4  0x00007fdb3553adbc in hgcmServiceThread (ThreadHandle=2147483665, pvUser=0x7fdb1c002650) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCM.cpp:519
#5  0x00007fdb35538d11 in hgcmWorkerThreadFunc (ThreadSelf=<optimized out>, pvUser=0x7fdb1c002720) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCMThread.cpp:194
#6  0x00007fdb3d312274 in rtThreadMain (pThread=0x7fdb1c0028e0, NativeThread=140579217516288, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#7  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x7fdb1c0028e0) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#8  0x00007fdb3d676184 in start_thread (arg=0x7fdb2652a700) at pthread_create.c:312
#9  0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7fdb27424700 (LWP 6753)):
#0  __memcpy_sse2_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:33
#1  0x00007fdb3549bca6 in memcpy (__len=4608, __src=0x0, __dest=<optimized out>) at /usr/include/x86_64-linux-gnu/bits/string3.h:51
#2  Display::i_handleDisplayUpdate (this=0x7fdb28003a00, uScreenId=0, x=0, y=826, w=<optimized out>, h=38) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/DisplayImpl.cpp:1058
#3  0x00007fdb075cb665 in vga_draw_graphic (pThis=pThis@entry=0x7fdb24034100, full_update=false, fFailOnResize=fFailOnResize@entry=false, reset_dirty=reset_dirty@entry=true, pDrv=0x7fdb183937f8)
    at ../VirtualBox-5.0.20/src/VBox/Devices/Graphics/DevVGA.cpp:2521
#4  0x00007fdb075d32e5 in vga_update_display (pThis=pThis@entry=0x7fdb24034100, fUpdateAll=fUpdateAll@entry=false, fFailOnResize=fFailOnResize@entry=false, reset_dirty=reset_dirty@entry=true, 
    pDrv=<optimized out>, pcur_graphic_mode=pcur_graphic_mode@entry=0x7fdb240347a8) at ../VirtualBox-5.0.20/src/VBox/Devices/Graphics/DevVGA.cpp:2670
#5  0x00007fdb075d36f8 in vgaPortUpdateDisplay (pInterface=0x7fdb24044e10) at ../VirtualBox-5.0.20/src/VBox/Devices/Graphics/DevVGA.cpp:4684
#6  0x00007fdb35498859 in Display::i_displayRefreshCallback (pInterface=0x7fdb183937f8) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/DisplayImpl.cpp:3018
#7  0x00007fdb075cc3b8 in vgaTimerRefresh (pDevIns=<optimized out>, pTimer=0x7fdb25ea9450, pvUser=0x7fdb24034100) at ../VirtualBox-5.0.20/src/VBox/Devices/Graphics/DevVGA.cpp:5335
#8  0x00007fdb34213ef3 in tmR3TimerQueueRun (pVM=pVM@entry=0x7fdb3405a000, pQueue=0x7fdb25e9c920) at ../VirtualBox-5.0.20/src/VBox/VMM/VMMR3/TM.cpp:2171
#9  0x00007fdb342174a9 in TMR3TimerQueuesDo (pVM=0x7fdb3405a000) at ../VirtualBox-5.0.20/src/VBox/VMM/VMMR3/TM.cpp:2087
#10 0x00007fdb34221809 in vmR3HaltGlobal1Halt (pUVCpu=0x7fdb27addfa0, fMask=607, u64Now=<optimized out>) at ../VirtualBox-5.0.20/src/VBox/VMM/VMMR3/VMEmt.cpp:685
#11 0x00007fdb34222982 in VMR3WaitHalted (pVM=0x7fdb3405a000, pVCpu=0x7fdb34075000, fIgnoreInterrupts=<optimized out>) at ../VirtualBox-5.0.20/src/VBox/VMM/VMMR3/VMEmt.cpp:1105
#12 0x00007fdb34192eb2 in EMR3ExecuteVM (pVM=<optimized out>, pVCpu=<optimized out>) at ../VirtualBox-5.0.20/src/VBox/VMM/VMMR3/EM.cpp:2566
#13 0x00007fdb34222d61 in vmR3EmulationThreadWithId (ThreadSelf=0x7fdb20008610, pUVCpu=0x7fdb27addfa0, idCpu=0) at ../VirtualBox-5.0.20/src/VBox/VMM/VMMR3/VMEmt.cpp:235
#14 0x00007fdb3d312274 in rtThreadMain (pThread=0x7fdb20008610, NativeThread=140579233220352, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#15 0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x7fdb20008610) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#16 0x00007fdb3d676184 in start_thread (arg=0x7fdb27424700) at pthread_create.c:312
#17 0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

(gdb) up
#1  0x00007fdb3549bca6 in memcpy (__len=4608, __src=0x0, __dest=<optimized out>) at /usr/include/x86_64-linux-gnu/bits/string3.h:51

(gdb) list
51	  return __builtin___memcpy_chk (__dest, __src, __len, __bos0 (__dest));
46	
47	__fortify_function void *
48	__NTH (memcpy (void *__restrict __dest, const void *__restrict __src,
49		       size_t __len))
50	{
51	  return __builtin___memcpy_chk (__dest, __src, __len, __bos0 (__dest));
52	}
53	
54	__fortify_function void *
55	__NTH (memmove (void *__dest, const void *__src, size_t __len))

(gdb) up
#2  Display::i_handleDisplayUpdate (this=0x7fdb28003a00, uScreenId=0, x=0, y=826, w=<optimized out>, h=38) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/DisplayImpl.cpp:1058
1058	                        memcpy(pu8Dst, pu8Src, w * 4);
1053	                    const uint8_t *pu8Src = pFBInfo->updateImage.pu8Address + pFBInfo->updateImage.cbLine * y + x * 4;
1054	
1055	                    int i;
1056	                    for (i = y; i < y + h; ++i)
1057	                    {
1058	                        memcpy(pu8Dst, pu8Src, w * 4);
1059	                        pu8Dst += w * 4;
1060	                        pu8Src += pFBInfo->updateImage.cbLine;
1061	                    }
1062	

(gdb) print pu8Src
$1 = (const uint8_t *) 0x0
(gdb) print pFBInfo
$1 = (DISPLAYFBINFO *) 0x7fdb28003aa8
(gdb) print pFBInfo->updateImage.pu8Address
$2 = (uint8_t *) 0x0
(gdb) print pFBInfo->updateImage.cbLine
$3 = 0
(gdb) print pu8Dst
$4 = <optimized out>
(gdb) print w
$5 = <optimized out>

}}}


Thread 1 trying to refresh VGA Display and Thread 22 trying to power down virtual machine and resize display.

In i_handleDisplayResize pFBInfo->updateImage probably was nulled:
{{{
int Display::i_handleDisplayResize(unsigned uScreenId, uint32_t bpp, void *pvVRAM,
                                   uint32_t cbLine, uint32_t w, uint32_t h, uint16_t flags)
{
    LogRel((""Display::handleDisplayResize: uScreenId=%d pvVRAM=%p w=%d h=%d bpp=%d cbLine=0x%X flags=0x%X\n"", uScreenId,
            pvVRAM, w, h, bpp, cbLine, flags));

    if (uScreenId >= mcMonitors)
    {
        return VINF_SUCCESS;
    }

    DISPLAYFBINFO *pFBInfo = &maFramebuffers[uScreenId];

    /* Reset the update mode. */
    pFBInfo->updateImage.pSourceBitmap.setNull();
    pFBInfo->updateImage.pu8Address = NULL;
    pFBInfo->updateImage.cbLine = 0;
}}}
"	gim
20355	Possible race condition bug in UIMachineView::focusOutEvent / focusInEvent blocks mouse click on host/guest (Qt GUI)	all	VirtualBox 6.1.22	2021-05-10T09:09:08Z	2021-12-03T17:33:29Z	2021-12-03T17:33:29Z	"For more than two years now (so probably since VB version 6.0 or so) from time to time I am affected by a bug which stops mouse click interactions on the host and guest as well.
I can still move the mouse pointer but clicks are not recognized anymore. The only solution then is to shut down *all* running guest instances. Then the mouse clicks starts working again. There will be no entry in the logs, when the bug occurs.


=== How to reproduce ===


It happend very randomly to me but after a while with a screen record I figured out the following steps to reliable reproduce the bug on XFCE:

1) Click on the taskbar to restore VM window from minimized state[[BR]]
2) Press down the mouse button on the taskbar and keep it pressed[[BR]]
3) Release the mouse button and immediately press it again[[BR]]
4) Now no further clicks are registered until VM is shut down[[BR]]


(I agree that this looks like a very special and rare circumstance - however I think that this bug is a race condition and as I often switch between different windows with the taskbar I'm hit by it very often.)

Here is a screencast of the bug as GIF: https://s3.gifyu.com/images/vbox-bug.gif

=== Possible cause === 

From the steps I assume that the bug is kind of a race condition on the minimize respectively focus out / focus in event of the window. So I tried to build VirtualBox from source and try to trace the bug. And indeed I figured out, that the bug does not occure if I comment out the following 3 lines in the file {{{src/VBox/Frontends/VirtualBox/src/runtime/UIMachineView.cpp}}}

{{{
void UIMachineView::focusOutEvent(QFocusEvent *pEvent)
{
    /* If native event filter exists: */
    if (m_pNativeEventFilter)
    {
        /* Uninstall/destroy existing native event filter: */
            
        //qApp->removeNativeEventFilter(m_pNativeEventFilter);
        //delete m_pNativeEventFilter;
        //m_pNativeEventFilter = 0;
    }

    /* Call to base-class: */
    QAbstractScrollArea::focusOutEvent(pEvent);
}
}}}

I tried to dig deeper but I'm kind of stuck. Because I don't know what this native event filter is used for and why it is destroyed on focus out event."	Cryptkeeper
14189	Port forwarding silently fails when source ports are privileged	Linux	VirtualBox 4.3.28	2015-06-09T21:21:38Z	2015-06-09T23:38:27Z	2015-06-09T23:38:27Z	"I just spent a really unproductive hour or so trying to work out why I was getting ""Connection refused"" from a test LDAP server in a VM.

Then I resorted to trying to forward the port using SSH. The SSH client reminded me that privileged ports cannot be forwarded unless you're root. (Oh yeah, Unix. Privileged ports. I remember now.)

So my suggestion is:

 - The VirtualBox GUI should warn the user about this.

 - There should be an error displayed if port forwarding fails because the port is privileged.

The documentation at https://www.virtualbox.org/manual/ch06.html mentions the limitation, but it states that the VM will refuse to start in such a situation. That doesn't appear to be true -- I tried restarting the VM and didn't get a useful error message."	meta
15545	Popup menu does not appear	Windows	VirtualBox 5.0.22	2016-06-23T12:35:15Z	2016-06-23T16:03:22Z	2016-06-23T16:03:22Z	Popup menu in virtual machine does not appear. I have set various settings but it does not resolve problem	Destructor
15352	Poor/missing documentation of Balloon parameters	other	VirtualBox 5.0.18	2016-04-25T23:17:39Z	2016-04-25T23:17:39Z	2016-04-25T23:17:39Z	"The parameters involved in the balloon control (in VBoxBalloonCtrl) are very poorly described (section 9.22.1).  I had to read the code to understand how they are being used.

BalloonLowerLimitMB - despite the confusing name, this parameter is the minimum free memory that should be maintain in the Guest. It is not a ""balloon lower limit"", it is a Guest free memory lower limit.

VBOXWATCHDOG_BALLOON_SAFETYMARGIN - this parameter is only visible in the daemon start up script. While I assumed this was the memory safety margin in the Guest, it is not. It is the memory safety margin the Host. The balloon daemon will not reduce the balloon in a Guest if that would cause the Host to not have enough memory.


"	prensing
17342	PokerStars freezes up in Virtualbox 5.2+ but not in 5.1.30	Windows	VirtualBox 5.2.0	2017-12-03T16:25:38Z	2017-12-27T06:01:41Z	2017-12-27T06:01:41Z	"Arch Linux 64-bit host, Windows 7 64-bit guest

To encounter the issue:

Use the following:
* virtualbox-5.2.2-2
* virtualbox-ext-oracle-5.2.2-1
* virtualbox-guest-iso-5.2.2-1
* virtualbox-host-dkms-5.2.2-2
Start the Windows 7 guest in Safe Mode, install the Guest Additions, select Direct3d support, agree to install only Basic Direct3d support, reboot the guest, then start PokerStars (the most recent build is 20294) and click the ""Challenges"" button in the menu. This resulted in the window freezing for several minutes (I had to force-kill it).

The program similarly hangs when sitting down at a table, which is the more serious part; the Challenges window just provides a more convenient way to test the issue.

Using all 5.2.0 VirtualBox components instead of 5.2.2 made no difference (PokerStars froze just the same).

It does not seem specific to the PokerStars build, as trying it with an earlier build of PokerStars made no difference.

For comparison, using VirtualBox 5.1.30 instead of 5.2+ and following the same steps as described above did NOT produce the issue (PokerStars works fine without hanging using the following):
* virtualbox 5.1.30-1
* virtualbox-ext-oracle 5.1.30-1
* virtualbox-guest-iso 5.1.30-1
* virtualbox-host-dkms 5.1.30-1"	sleepnought
10222	Please implement readPhysicalMemory or a raw memory dumper	other	VirtualBox 4.1.8	2012-02-07T01:46:11Z	2012-02-22T12:45:28Z	2012-02-22T12:45:28Z	"Hello,

We are studying the use of VBox in a forensic course. However, the access to VM memory is critical.

I found many references at the forum about people trying to get the VM memory contents. However, no one provided a solution. I still can get the memory, treating it as a real machine, but that would taint the VM memory with the memory dumper. The best solution would be to collect the VM memory using the VM solution resources, specially in a paused state. The best solution would be to have a simple read function that could access a Snapshot.

The VBOX SDK guide describes the function readPhysicalMemory and notes that it is not developed in 4.0.0. We are already in 4.1.8 and it is still not imeplemented. I got this error message when running a python script that calls this function:

 0x80004001 (Method ReadPhysicalMemory is not implemented)

Please, could you please provide the implementation of this function in the next vbox release. Alternatively, this could be implemented in a VBoxManage debugvm option, specially if considering snapshots. The needed function is a raw VM memory dump.

Vmware Server/Workstation, for example, stores the memory in a flat vmem file. Libvirt has the virDomainMemoryPeek API function. Just Vbox lacks at this point.

Thanks,"	Luiz Angelo Daros de Luca
16178	Please fix audio debugging instructions	all		2016-11-10T15:15:36Z	2016-11-11T17:04:29Z	2016-11-11T17:04:29Z	"The instructions available here https://www.virtualbox.org/wiki/AudioDebug to provide useful log files for audio issues debugging are misleading, at least for Linux.

They suggest to set an environment variable in a shell with elevated privileges, then kill this shell and check in another, non-privileged, shell that the variable is set. I'm quite sure that running VirtualBox with VBOX_RELEASE_LOG set will never happen this way.

My suggestion would be to ask people to close VirtualBox, then run from the command line


{{{
VBOX_RELEASE_LOG=drv_host_audio.e.l.l2.l3.f+drv_audio.e.l.l2.l3.f+audio_mixer.e.l.l2.l3.f+dev_hda_codec.e.l.l2.l3.f+dev_hda.e.l.l2.l3.f+dev_ac97.e.l.l2.l3.f VirtualBox
}}}


then check in the log that ""Audio: Verbose logging enabled"" is there.

I can't test the provided instructions for Windows."	slv
20123	Please find attachment, VM not started	Linux	VirtualBox 6.1.16	2021-01-11T14:30:15Z	2021-01-11T14:30:15Z	2021-01-11T14:30:15Z		vijay.hambir
14223	Please change the Mandriva name on the rpm page to OpenMandriva	all	VirtualBox 4.3.28	2015-06-25T23:09:52Z	2015-06-26T08:07:08Z	2015-06-26T08:07:08Z	"Hi, I am the president of the OpenMandriva Association, this body was formed from users and developers of Mandriva prior to their final bankcruptcy. It was formed with the purpose of legally passing on the source code of the OpenMandriva distribution into the hands of the OpenSource community. 
The OpenMandriva association creates and distributes it's own OpenMandriva OS created from this sourcecode. We want very much to keep the name of Mandriva alive under the auspices of the OpenMandriva Association and one of the ways we can do this is to ask you whether you would change your current web pages to show OpenMandriva rpm packages rather than Mandriva and to change the name part of the rpm filename from mdv to omdv. We are more than happy to support you with updated rpm spec files for the builds. Since sadly Mandriva is no more and the web pages should be changed anyway to reflect this point in history it is felt that this might be the best time to ask for your help and cooperation.

I was advised on the admin/moderation forum that here would be the best place to make the request

This web page from the founder of Mnadrake/Mandriva may be of interest.
http://www.indidea.org/gael/blog/

Regards,

Colin Close
President 
OpenMandriva Association"	itchka
13452	Please add workdir argument to guestcontrol exec	Linux	VirtualBox 4.3.16	2014-10-01T12:52:36Z	2015-09-21T09:42:31Z	2015-09-21T09:42:31Z	"I'm working on virtual build-test factory, based on VirtualBox. VBoxManage guestcontrol helps immensely, but tasks such as 'make' often need concrete folder to run in. Because of that I have to use construct as following, wrapping everything under bash command:

{{{
VBoxManage guestcontrol ""$ARG_VM_NAME"" exec --wait-exit --wait-stderr \
--image ""/bin/bash"" --username $VM_USER_LOGIN --password $VM_USER_PASSWORD \
-- -c ""cd '/mnt/ramdisk/$BUILD/buildroot' && make images""
}}}

It would be very helpful to have --workdir or similar argument to guestcontrol exec, similarly to process spawning libraries in programming languages and libraries."	indifferent
17202	Please add Ubuntu 17.10 (artful) Support to the PPA	all	VirtualBox 5.2.0	2017-10-22T22:53:00Z	2017-12-04T13:43:20Z	2017-12-04T13:43:20Z	Please add Ubuntu 17.10 (artful) Support to the PPA	Neti_Netwalker
14593	Please add support to more network cards	Windows	VirtualBox 5.0.2	2015-09-15T19:45:13Z	2016-10-11T03:11:55Z	2016-10-11T03:11:55Z	"Hi!

I'm trying to run Siemens WinAC RTX 2010 on Windows XP SP3 Pro English guest. It installs and works fine, but this software needs some specific network cards to be enabled to work with network. The supported network cards by Siemens WinAC RTX 2010:

Intel Gigabit CT (chip set: Intel I82574L)
Intel 2-Port PCIe (chip set: Intel  I82571EB)
Intel Pro/1000 PL (chip set: Intel 82573L)
Intel Pro/1000 GT (chip set: Intel 82541PI)
Intel Gigabit (chip set:  82571EB) 

But none of these network cards are supported by Virtualbox.

So, Can the Virtualbox development team add support to one or two network cards from this list?"	fluisgirardi
11687	Please add support for Guests to control Host Audio Volume (+/-)	all	VirtualBox 4.2.10	2013-04-09T16:19:51Z	2013-04-19T19:37:36Z	2013-04-19T19:37:36Z	"Please add support for Guests to control Audio Volume (+/-). Probably best to add a check box in the Audio Section of the Settings GUI (where it says Enable Audo; Host Audio Driver = ALSA; Audio Controller = Intel HD Audio).

Right now if I watch a video in Guest OS in Full Screen, and I need to increase or lower the volume I have to 
1. Pause the Video
2. Exit full screen mode
3. Go to the Host OS to increase or lower the volume
4. Then go back to the Guest OS and change it to full screen mode.
5. Resume Video and hope it is the correct volume or go back to Step 1."	Quickbooks Office
21452	Please add require for kernel headers in Fedora rpm packages	other	VirtualBox-7.0.6	2023-02-01T03:03:22Z	2023-02-01T03:03:22Z	2023-02-01T03:03:22Z	"A long time annoying missing thing is that Fedora rpms does not by itself fetch the required kernel headers,
and therefore won't work until user figures out whats missing.

YES - I am aware that Fedora have HAD a problem with fetching the wrong version - and that's most likely why you don't do it ....... but this is FIXED now.

Fedora now has a new package in all repos, that should fix this problem - it is called kernel-devel-matched

coming with this description:
This meta package is used to install matching core and devel packages for a given kernel.

Please add ""Requires: kernel-devel-matched"" for new releases, to finally fix this annoyance 
"	Yoda
18138	Please add a fedora 29 repo	other	VirtualBox 5.2.22	2018-11-19T11:09:43Z	2018-12-08T23:40:55Z	2018-12-08T23:40:55Z	"Fedora 29 has been released. Please add a repo:
http://download.virtualbox.org/virtualbox/rpm/fedora/"	jammy
16604	Plasma 5 screen scaling on 4K monitor causes Windows guest to be 1/4 size of window.	Windows	VirtualBox 5.1.16	2017-03-24T03:45:05Z	2021-09-28T15:31:23Z	2021-09-28T15:31:23Z	"This is a very specific bug to KDE / Plasma 5.

I have a laptop with a 4K display. KDE / Plasma 5 are not yet suited to the resolution. To help with icon size I selected System Settings => Display and Monitor => Scaled Display (button) and set the scale to 2.0.

This doubled all my icons nicely, but within the Windows 10 VM, the graphics were scaled to half resolution on both axes, but were not scaled back up to fill the screen. Mouse clicking was difficult because they were based on the full size of the window but the graphics were 1/2 size.

This is a small issue as I just turned of the Plasma feature to fix VirtualBox. And since it limits display resolution, it's probably not a good fix for the small icons.
"	Raydude
20330	Pipewire audio server unusable	Linux	VirtualBox 6.1.20	2021-04-30T02:08:34Z	2021-10-25T09:43:20Z	2021-10-25T09:43:20Z	"GNOME 40 introduces a new sound server, Pipewire, to replace pulseaudio to control sound under Linux.

Fedora 34 makes Pipewire as default, while it has a pulseaudio module to maintain compatibility, VirtualBox can't play sound with Pipewire, and it affects video playback as well.

Under GNOME settings, there is a testing option under sound preferences, no sound is available in the test.

If there is a video in a web page, like YouTube, sometimes sound can play 2-3 seconds but then the video will be muted, and frames are freezed as well, not only sound is unavailable but the video is affcted as well.

I tried to remove Pipewire and install Pulseaudio, everything is ok and back to normal again.

As Pipewire introduces many new features and better integration in future Linux development, it would be important to fix this issue before pulseaudio is completely phased out (it may take 2-3 years though...)."	Promet
6074	Permission denied to access shared folders on Windows when folder contains broken symbolic link	Windows	VirtualBox 3.1.2	2010-01-26T13:39:36Z	2011-05-25T12:52:29Z	2011-05-25T12:52:29Z	"Host: Ubuntu 9.10 AMD64 Guest: Windows XP 32bits

For some reason, Windows prevented me to access a shared folder by telling me I need administraor privileges to access it (while I have them).
I noticed that I have some broken symbolic links on the ext4 filesystem of that folder. After removing them, access to the folder was granted by Windows guest os."	Ankhterus
16385	PCI passthrought works incorrectly with I/O ports	Linux	VirtualBox 5.0.20	2017-01-15T13:18:39Z	2017-01-16T15:45:15Z	2017-01-16T15:45:15Z	"Hello,

I am using virtualBox 5.0.20 OSS with extension pack

# VBoxManage list extpacks
Extension Packs: 1
Pack no. 0:   Oracle VM VirtualBox Extension Pack
Version:      5.0.20
Revision:     106931
Edition:      
Description:  USB 2.0 and USB 3.0 Host Controller, Host Webcam, VirtualBox RDP, PXE ROM, Disk Encryption.
VRDE Module:  VBoxVRDP
Usable:       true 
Why unusable:

Host kernel is 3.16.7
Guest kernel is 4.9.0

On the host machine I have the following PCI device:

04:00.0 0700: 1393:1320 (rev 02) (prog-if 80)
        Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Interrupt: pin A routed to IRQ 19
        Region 1: I/O ports at e080 [size=128]
        Region 2: I/O ports at e100 [size=64]
        Region 3: I/O ports at e140 [size=16]
        Kernel driver in use: pci-stub
        Kernel modules: mxser

When passed into the guest system it looks like the following:

03:00.0 0700: 1393:1320 (rev 02) (prog-if 80)
        Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Interrupt: pin A routed to IRQ 17
        Region 1: I/O ports at e000 [size=128]
        Region 2: I/O ports at e080 [size=64]
        Region 3: I/O ports at e0c0 [size=16]

However, access to I/O ports doesn't work in guest system.

To test I/O ports the following simple code snipped is used: https://gist.github.com/matwey/b42f8b9fb50ab8c603d120c54d04c9be

On the host (when accessed to 0xe100) result is the following:

# ./a.out 
64: FF 00 01 00 00 60 90 00 FF 00 01 00 00 60 90 00 FF 00 01 00 00 60 90 00 FF 00 01 00 00 60 90 00 FF 00 01 00 00 60 90 00 FF 00 01 00 00 60 90 00 FF 00 01 00 00 60 90 00 FF 00 01 00 00 60 90 00

On the guest (when accessed to 0xe080) result is the following:

# ./a.out 
64: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF"	Matwey V. Kornilov
17388	PCI passthrough fails with general protection fault in VBoxPciRawR3.so	all	VirtualBox 5.2.4	2017-12-21T21:37:03Z	2017-12-21T21:37:03Z	2017-12-21T21:37:03Z	"starting a VM with a PCI device attached fails with a segfault in VBoxPciRawR3.so.

{{{
kernel: traps: EMT-0[15909] general protection ip:7f846c2b908f sp:7f84923cccd0 error:0 in VBoxPciRawR3.so[7f846c2b6000+c000]
}}}

This is 100% reproducible.

Linux kernel version 4.14.8-1-ck"	Thermi
18204	PCI passthrough :invalid region	Windows	VirtualBox 6.0.0	2018-12-19T18:33:07Z	2019-01-06T11:42:00Z	2019-01-06T11:42:00Z	"'''Host:''' debian 9  amd64

'''CPU:''' AMD

'''Virtualbox:''' 5.2.x , 6.0.0

'''Guest:''' win7  64-bit

'''PCI passthrough :''' AMD GPU

'''lspci -vv  -s1e:00.0'''

{{{
1e:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Device 687f (rev c1) (prog-if 00 [VGA controller])
        Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device 6b76
        Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Interrupt: pin A routed to IRQ 41
        Region 0: Memory at e0000000 (64-bit, prefetchable) [size=256M]
        Region 2: Memory at f0000000 (64-bit, prefetchable) [size=2M]
        Region 4: I/O ports at f000 [size=256]
        Region 5: Memory at f7800000 (32-bit, non-prefetchable) [size=512K]
        [virtual] Expansion ROM at f7880000 [disabled] [size=128K]
...
}}}

'''Second GPU:''' (not passthrough)
{{{
1b:00.0 VGA compatible controller: NVIDIA Corporation GP108 
}}}

'''dmesg'''
{{{
[10178.205401] vboxpci: detected device: 1002:687f at 1e:00.0, driver <none>
[10178.205458] pci-stub 0000:1e:00.0: claimed by stub
[10178.205486] vboxPciFileWrite: error -19
[10178.205560] vboxpci 0000:1e:00.0: vboxPciOsDevInit
[10178.205665] vboxpci 0000:1e:00.0: region 0: mmio e0000000+268435456
[10178.205668] vboxpci 0000:1e:00.0: region 2: mmio f0000000+2097152
[10178.205671] vboxpci 0000:1e:00.0: region 4: pio f000+256
[10178.205673] vboxpci 0000:1e:00.0: region 5: mmio f7800000+524288
[10178.205676] vboxpci 0000:1e:00.0: region 6: mmio f7880000+131072
[10178.205697] vboxpci 0000:1e:00.0: got irq 94
[10179.615799] vboxpci: created IOMMU domain ffff8a6575448a20
[10179.667123] vboxpci 0000:1e:00.0: PCIRAW_POWER_ON
[10179.667134] vboxpci 0000:1e:00.0: pci_reset_function() failed
[10179.667182] vboxpci 0000:1e:00.0: attached to IOMMU
[10179.673069] vboxpci 0000:1e:00.0: invalid region 5
[10179.673119] vboxpci 0000:1e:00.0: reg=0 start=e0000000 size=268435456
[10179.677495] vboxpci 0000:1e:00.0: invalid region 2
[10185.325467] vboxpci 0000:1e:00.0: reg=0 start=e0000000 size=268435456
[10185.327882] vboxpci 0000:1e:00.0: invalid region 2
[10185.327885] vboxpci 0000:1e:00.0: invalid region 5
[10186.596095] vboxpci: freeing IOMMU domain ffff8a699a958c20
[10187.832128] vboxpci 0000:1e:00.0: reg=0 start=e0000000 size=268435456
[10187.836709] vboxpci 0000:1e:00.0: invalid region 2
[10187.836714] vboxpci 0000:1e:00.0: invalid region 5
[10215.836023] vboxpci 0000:1e:00.0: PCIRAW_POWER_OFF
[10215.836071] vboxpci 0000:1e:00.0: detached from IOMMU
[10215.898276] traps: EMT-0[7904] general protection ip:7f1f36e5e1bf sp:7f1f6cff2db0 error:0
[10215.898284]  in VBoxPciRawR3.so[7f1f36e5b000+c000]
[10216.035409] vboxpci 0000:1e:00.0: freeing irq 94
[10216.035428] vboxpci 0000:1e:00.0: vboxPciOsDevDeinit
[10216.035612] vboxpci: freeing IOMMU domain ffff8a6575448a20
[10219.287799] vboxpci: created IOMMU domain ffff8a6a1c90cc20
}}}

Checking out from yours Subversion server. 

'''I think problem is  in file:''' src/VBox/HostDrivers/VBoxPci/linux/VBoxPci-linux.c

'''Method:''' vboxPciOsDevMapRegion

'''Line:'''813  

'''In commit''':75599
{{{
if (!pPciDev || iRegion < 0 || iRegion > 0)
}}}

'''IMHO corect line is:'''
{{{
if (!pPciDev || iRegion < 0 || iRegion > 6)
}}}



'''svn  diff -r58962:58963''' (line 776 in 58962  vs line 787 in 58963)
"	svj
20498	PATH_SDK_QT5_INC auto-detects to .../QtGui	other	VirtualBox 6.1.26	2021-08-11T14:59:26Z	2021-10-21T14:35:26Z	2021-10-21T14:35:26Z	"When building VirtualBox from source, ./configure sets PATH_SDK_QT5_INC to ""/usr/include/qt5/QtGui"" in ""AutoConfig.kmk"", which causes numerous compile errors. The correct path should be ""/usr/include/qt5""."	guanx
18783	Patch VirtualBox 6.0.10 for Linux kernel 5.3.y	all	VirtualBox 6.0.10	2019-07-23T14:24:38Z	2019-07-25T06:09:10Z	2019-07-25T06:09:10Z	"
Patch VirtualBox 6.0.10 for Linux kernel 5.3.y


{{{
diff -ruN ./virtualbox-6.0.10.orig/r0drv/linux/mp-r0drv-linux.c ./virtualbox-6.0.10/r0drv/linux/mp-r0drv-linux.c
--- ./virtualbox-6.0.10.orig/r0drv/linux/mp-r0drv-linux.c       2019-07-12 11:38:58.000000000 +0300
+++ ./virtualbox-6.0.10/r0drv/linux/mp-r0drv-linux.c    2019-07-22 21:03:06.993331834 +0300
@@ -283,12 +283,7 @@
     if (RTCpuSetCount(&OnlineSet) > 1)
     {
         /* Fire the function on all other CPUs without waiting for completion. */
-# if LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 27)
-        int rc = smp_call_function(rtmpLinuxAllWrapper, &Args, 0 /* wait */);
-# else
-        int rc = smp_call_function(rtmpLinuxAllWrapper, &Args, 0 /* retry */, 0 /* wait */);
-# endif
-        Assert(!rc); NOREF(rc);
+        NOREF(smp_call_function(rtmpLinuxAllWrapper, &Args, 0 /* wait */));
     }
 #endif
 
@@ -326,7 +321,6 @@
 {
 #ifdef CONFIG_SMP
     IPRT_LINUX_SAVE_EFL_AC();
-    int rc;
     RTMPARGS Args;
 
     RTTHREADPREEMPTSTATE PreemptState = RTTHREADPREEMPTSTATE_INITIALIZER;
@@ -337,14 +331,11 @@
     Args.cHits = 0;
 
     RTThreadPreemptDisable(&PreemptState);
-# if LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 27)
-    rc = smp_call_function(rtmpLinuxWrapper, &Args, 1 /* wait */);
-# else /* older kernels */
-    rc = smp_call_function(rtmpLinuxWrapper, &Args, 0 /* retry */, 1 /* wait */);
-# endif /* older kernels */
+
+    NOREF(smp_call_function(rtmpLinuxWrapper, &Args, 1 /* wait */));
+
     RTThreadPreemptRestore(&PreemptState);
 
-    Assert(rc == 0); NOREF(rc);
     IPRT_LINUX_RESTORE_EFL_AC();
 #else
     RT_NOREF(pfnWorker, pvUser1, pvUser2);
diff -ruN ./virtualbox-6.0.10.orig/vboxnetflt/linux/VBoxNetFlt-linux.c ./virtualbox-6.0.10/vboxnetflt/linux/VBoxNetFlt-linux.c
--- ./virtualbox-6.0.10.orig/vboxnetflt/linux/VBoxNetFlt-linux.c        2019-07-22 21:05:55.545025085 +0300
+++ ./virtualbox-6.0.10/vboxnetflt/linux/VBoxNetFlt-linux.c     2019-07-22 21:06:08.743978844 +0300
@@ -2107,6 +2107,8 @@
     struct in_device *in_dev;
     struct inet6_dev *in6_dev;
 
+    const struct in_ifaddr *ifa;
+
     if (ulEventType != NETDEV_REGISTER)
         return NOTIFY_OK;
 
@@ -2123,7 +2125,8 @@
 #endif
     if (in_dev != NULL)
     {
-        for_ifa(in_dev) {
+        rcu_read_lock();
+        in_dev_for_each_ifa_rcu(ifa, in_dev) {
             if (VBOX_IPV4_IS_LOOPBACK(ifa->ifa_address))
                 return NOTIFY_OK;
 
@@ -2137,7 +2140,8 @@
 
             pThis->pSwitchPort->pfnNotifyHostAddress(pThis->pSwitchPort,
                 /* :fAdded */ true, kIntNetAddrType_IPv4, &ifa->ifa_address);
-        } endfor_ifa(in_dev);
+        }
+     rcu_read_unlock();
     }
 
     /*


}}}



Best regards, Andy Lavr.
"	Andy Lavr
20471	pasting from Linux to windows 7 VM  via shared clipboard still crashes VM VB 6.1.24 6.1.24 r145751	Windows	VirtualBox 6.1.24	2021-07-23T17:58:26Z	2021-10-20T17:50:46Z	2021-10-20T17:50:46Z	Copying text in linux host and pasting into a windows 7 VM crashes the VM.The first few pastes work, then they stop working, then the VM crashes without any messages. I've attached the log. This crashing started in a more recent VB version--6.1.20 or .22 and continued with testbuilds including 145697.	matthewls
20383	Pass-Through Microphone Audio Broken Virtualbox Ver: 6.1.22-144080~Ubuntu~eoan	Windows	VirtualBox 6.1.22	2021-06-01T09:05:23Z	2021-06-22T09:02:54Z	2021-06-22T09:02:54Z	"Problem Statement:

Unable to pass microphone audio from Windows guest to Linux host.

Verified with both Windows 7x64 & Windows 10x64 using built in recording application

(NOTE: Though not supported, it appears that this is now happening with my Android OS Guest. Microphone audio pass-through was working prior to latest Virtualbox updates)

pavucontrol used in Linux host to control and verify existence of audio in/out



Virtualbox initial Audio settings:

Enabled Audio

Host Audio Driver = Pulse Audio

Audio Controller = Intel HD Audio

Extended Features: Enabled both Audio Input & Output



Additional steps taken:

Verified user permissions attached to vboxuser. Assumed that the newer Kernel and Inten Chipset combination not yet compatible with Virtualbox. Obtained 6305_Vista_PG537 audio driver and installed in both Windows guests, then changed Audio Controller to ICH AC97. I'm still able to pass through Speaker Audio, but Microphone Audio remains elusive in both Windows versions. In addition, did try the Sound Blaster Audio Controller, but as expected, lost all audio without a matching Windows drivers.
Reloaded new Windows guest to re-verify installation, result log attached

Host System:

OS: Ubuntu 20.04 x86_64

Kernel: 5.11.0-7614-generic

Desktop Environment: KDE

CPU: 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz

RAM: -14936 MB / 23894 MB

Disk: 157G / 912G

Virtualbox Ver: 6.1.22-144080~Ubuntu~eoan

Virtualbox-ext-pack Ver: 6.1.22



Guest System:

OS: Win10_20H2_v2_English_x64.iso, No Service Pack

Virtualbox VBoxGuestAdditions.iso

Base Memory: 8192

Enable I/O APIC

Use Default and Nested paging for Hardware Virtualization: Enabled Nested Paging

Processors: 2

Extended Features: PAE/NX Enabled

Paravirtualization Interface: Default

(VT-xAMD-V,Nested Paging, PAE/NX, Hyper-V Paravirtualization)

Video Memory: 256Mb

Graphics Controller: VBoxSVGA

Acceleration: Enabled 3D Acceleration"	MSterba
19872	Partial or Blank VBox UI in Cinnamon 4.6	all	VirtualBox 6.1.14	2020-09-09T03:47:51Z	2020-09-09T03:50:59Z	2020-09-09T03:50:59Z	"Host: Ubuntu 20.04 (focal) also verified on Linux Mint 20 Ulyana[[BR]]
Kernel: 5.4.0-47-generic[[BR]]
Guest: N/A as it is the main UI[[BR]]
GPU: Nvidia GTX 1060[[BR]]
GPU Driver: nvidia-driver-440-server Xorg[[BR]]
GPU Driver Source: graphics-drivers-ubuntu-ppa-focal[[BR]]
Display Manager: Cinnamon 4.6[[BR]]
Failure is on the host level[[BR]]
[[BR]]
After installing VirtualBox via both apt (virtualbox 6.1.10), downloaded (virtualbox 6.1.14), and through added virtualbox repo (virtualbox 6.1.14) on both Linux Mint 20 and Ubuntu 20.04 running Cinnamon 4.6 (on Ubuntu 20.04 using the UbuntuRemix repo) the UI is either blank or shows up partially.  The cli functionality is all there and working, it is just the UI.  Sometimes I can guess my way around and launch a VM, but for any guest I am using the screen does not refresh.[[BR]]
[[BR]]
Attached are the VBoxBugReport and a screenshot of the partial UI.[[BR]][[BR]]
I would love to take the time to troubleshoot more, but I just don't have it as this is my main system and I need it up and running for work.  I am wiping it and reinstalling Ubuntu 20.04 with Cinnamon 4.4 in which Virtualbox works just fine."	Jared Grange
13137	Parent UUID ... of the medium ... does not match UUID... of its parent medium stored in the media registry ...	Windows	VirtualBox 4.3.10	2014-06-20T17:05:40Z	2015-06-01T07:53:10Z	2015-06-01T07:53:10Z	"I have a virtual hd which reports the following:


{{{
$ VBoxManage showhdinfo b4938314-1204-43f0-8752-767515f71b39
UUID:           b4938314-1204-43f0-8752-767515f71b39
Parent UUID:    9c1d4675-e810-45d6-941d-ba0ced1037ea
State:          inaccessible
Access Error:   Parent UUID {b43a1680-4e28-45a7-80d4-7f43520f54df} of the medium '/u/martin/VirtualBox VMs/Windows XP Professional/Snapshots/{b4938314-1204-43f0-8752-767515f71b39}.vmdk' does not match UUID {9c1d4675-e810-45d6-941d-ba0ced1037ea} of its parent medium stored in the media registry ('/u/martin/.VirtualBox/VirtualBox.xml')
Type:           normal (differencing)
Auto-Reset:     off
Location:       /u/martin/VirtualBox VMs/Windows XP Professional/Snapshots/{b4938314-1204-43f0-8752-767515f71b39}.vmdk
Storage format: VMDK
Format variant: differencing default
Capacity:       0 MBytes
Size on disk:   0 MBytes
In use by VMs:  Windows XP Professional (UUID: ed45ab68-3ae8-4c86-bb30-54b728ade86c) [Snapshot 1 (UUID: 3c90fa44-287d-4e66-8c7c-91d65ad7c340)]
}}}

I suspect something went wrong in the past while deleting a snapshot.

I've attached the VM's logs and .vbox files.
"	mslw
19440	OVF import fails due to incorrect validation of SHA256 digests	all	VirtualBox 6.1.4	2020-03-27T15:38:37Z	2020-03-27T15:38:37Z	2020-03-27T15:38:37Z	"
When importing a virtual machine (VM) from .ovf file that is accompanied by a
.mf file that specifies file integrity hashes using SHA256, the importer (both
fom the GUI or using VBoxManage) check the integrity of the files as part of
the import process.

Specifically, the file I am seeing the issues is the hard drive of the VM,
provided in VMDK format. The importer exits with an error indicating that the
digest of the VMDK file does not match the one in the .mf file, but using tools
such as sha256 sum I see that the hash does match (see output below).

{{{
$ VBoxManage import ~/vms/testvm0146.ovf

(...snip...)

0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...
Progress state: VBOX_E_FILE_ERROR
VBoxManage: error: Appliance import failed
VBoxManage: error: Digest mismatch (VERR_NOT_EQUAL): Attribute 'SHA256' on
'testvm0146-0.vmdk' does not match
('03d3ec55ec53133041967054525ca1fbf8714208f9be242219e85a24f0745de9' vs.
'19ffb23de176d73835fe3528d5b4e5a5aac3c15b5e83fc7732f888c6c2d47f9d')
VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component
ApplianceWrap, interface IAppliance
VBoxManage: error: Context: ""RTEXITCODE handleImportAppliance(HandlerArg*)"" at
line 1118 of file VBoxManageAppliance.cpp
}}}

However, sha256sum gives the following output:

{{{
$ sha256sum ~/vms/testvm0146-0.vmdk
03d3ec55ec53133041967054525ca1fbf8714208f9be242219e85a24f0745de9
/home/me/vms/testvm0146-0.vmdk
}}}

Additionally, sha246deep also provides the same hash:

{{{
$ sha256deep ~/vms/testvm0146-0.vmdk
03d3ec55ec53133041967054525ca1fbf8714208f9be242219e85a24f0745de9
/home/me/vms/testvm0146-0.vmdk
}}}

The contents of the testvm0146.mf file are:

{{{
$ cat ~/vms/testvm0146.mf
SHA256(testvm0146-0.vmdk)=
03d3ec55ec53133041967054525ca1fbf8714208f9be242219e85a24f0745de9
SHA256(testvm0146-1.nvram)=
4615577454b8ea7c464f4aee064936e48db52ddb08f23e9ea74ade5e12fce8ce
SHA256(testvm0146.ovf)=
7cbaf2f6dc9ada576ae99ba0f5ef001432650581ad401d4312f297d2737ced49
}}}

As can be seen, the output of sha256sum and the .mf file match
(`03d3ec55ec53133041967054525ca1fbf8714208f9be242219e85a24f0745de9`), but for
some reason virtualbox determines the SHA256 hash to be
`19ffb23de176d73835fe3528d5b4e5a5aac3c15b5e83fc7732f888c6c2d47f9d`, and thus the
comparison fails.

This has been seen both in Oracle Virtualbox packages (in Ubuntu) as well as Debian-packaged virtualbox (in Debian), which suggests the issue is probably upstream in virtualbox.
"	radnaj
13494	Overloaded message loop makes Guest window unresponsive to inputs when guest additions installed	Windows	VirtualBox 4.3.16	2014-10-11T11:20:45Z	2015-10-17T20:33:36Z	2015-10-17T20:33:36Z	"I'm on Ubuntu 12.04 host using LXDE desktop, and the guest is Windows XP. I haven't tested it with other Windows versions like win7. 

My old GDI+ game completely freezes the guest window after some seconds. The only the to recover is simply killing the virtualbox process. It doesn't happen when guest additions are not installed.

I decided to investigate further and wrote the C program that reproduces the problem. (Simply using the Code::Blocks template with some edits).

The normal behavior is when you see the repeated rederawings clicking on the window should immediately bring up a messagebox with the coordinates. Or pressing key should bring up one with the character pressed. '''This happens on native windows, and in VirtualBox without guest additions'''. 

With guest additions, if you run it for some time and click the window, nothing happens. The drawings keep going and you get response after several seconds. 

It looks like the driver becomes overloaded with stuff, rendering the window unresponsive, till it processed all the events.

It's probably worth noting that the hard disk indicator is red when this hanging happen. Maybe it's writing somehing? I'm not sure whether the VM is thrashing or just because the whole GUI was frozen.

Adding several milliseconds of Sleep() into the message loop relieves the problem a bit. But it makes the game very laggy. 

Hopefully this helps reproducing the problem.

Also a note: at least one OpenGL game the OpenArena works fine on VirtualBox too.


{{{
#if defined(UNICODE) && !defined(_UNICODE)
    #define _UNICODE
#elif defined(_UNICODE) && !defined(UNICODE)
    #define UNICODE
#endif

#include <tchar.h>
#include <stdio.h>
#include <windows.h>

/*  Declare Windows procedure  */
LRESULT CALLBACK WindowProcedure (HWND, UINT, WPARAM, LPARAM);

/*  Make the class name into a global variable  */
TCHAR szClassName[ ] = _T(""CodeBlocksWindowsApp"");

int WINAPI WinMain (HINSTANCE hThisInstance,
                     HINSTANCE hPrevInstance,
                     LPSTR lpszArgument,
                     int nCmdShow)
{
    HWND hwnd;               /* This is the handle for our window */
    MSG messages;            /* Here messages to the application are saved */
    WNDCLASSEX wincl;        /* Data structure for the windowclass */

    /* The Window structure */
    wincl.hInstance = hThisInstance;
    wincl.lpszClassName = szClassName;
    wincl.lpfnWndProc = WindowProcedure;      /* This function is called by windows */
    wincl.style = CS_DBLCLKS;                 /* Catch double-clicks */
    wincl.cbSize = sizeof (WNDCLASSEX);

    /* Use default icon and mouse-pointer */
    wincl.hIcon = LoadIcon (NULL, IDI_APPLICATION);
    wincl.hIconSm = LoadIcon (NULL, IDI_APPLICATION);
    wincl.hCursor = LoadCursor (NULL, IDC_ARROW);
    wincl.lpszMenuName = NULL;                 /* No menu */
    wincl.cbClsExtra = 0;                      /* No extra bytes after the window class */
    wincl.cbWndExtra = 0;                      /* structure or the window instance */
    /* Use Windows's default colour as the background of the window */
    wincl.hbrBackground = (HBRUSH) COLOR_BACKGROUND;

    /* Register the window class, and if it fails quit the program */
    if (!RegisterClassEx (&wincl))
        return 0;

    /* The class is registered, let's create the program*/
    hwnd = CreateWindowEx (
           0,                   /* Extended possibilites for variation */
           szClassName,         /* Classname */
           _T(""Code::Blocks Template Windows App""),       /* Title Text */
           WS_OVERLAPPEDWINDOW, /* default window */
           CW_USEDEFAULT,       /* Windows decides the position */
           CW_USEDEFAULT,       /* where the window ends up on the screen */
           544,                 /* The programs width */
           375,                 /* and height in pixels */
           HWND_DESKTOP,        /* The window is a child-window to desktop */
           NULL,                /* No menu */
           hThisInstance,       /* Program Instance handler */
           NULL                 /* No Window Creation data */
           );

    /* Make the window visible on the screen */
    ShowWindow (hwnd, nCmdShow);

    /* Run the message loop.*/
    for (;;)
    {
        /* Chew window messages. */
        while (PeekMessage(&messages, NULL, 0, 0, PM_REMOVE))
        {
            TranslateMessage(&messages);
            DispatchMessage(&messages);
        }
        /* Step the game world. (omitted)*/

        /* Schedule redraw in next loop. */
        InvalidateRect(hwnd, NULL, TRUE);
    }

    /* The program return-value is 0 - The value that PostQuitMessage() gave */
    return messages.wParam;
}


/*  This function is called by the Windows function DispatchMessage()  */

LRESULT CALLBACK WindowProcedure (HWND hwnd, UINT message, WPARAM wParam, LPARAM lParam)
{
    PAINTSTRUCT ps;

    switch (message)                  /* handle the messages */
    {
        case WM_PAINT:
            BeginPaint(hwnd, &ps);
                /* Simulate expensive painting operation. */
                for (int i = 0; i < 1000; i++)
                {
                    MoveToEx(ps.hdc, rand() % 300, rand() % 300, NULL);
                    LineTo(ps.hdc, rand() % 300, rand() % 300);
                }
            EndPaint(hwnd, &ps);
        break;
        case WM_DESTROY:
            PostQuitMessage (0);       /* send a WM_QUIT to the message queue */
            break;
        case WM_LBUTTONDOWN:
            {
                WORD x = LOWORD(lParam);
                WORD y = HIWORD(lParam);
                TCHAR str[200];
                _sntprintf(str, 200, ""%d: %d"", x, y);
                MessageBox(hwnd, str, """", MB_OK);
            }
            break;
        case WM_CHAR:
            {
                TCHAR str[50];
                _sntprintf(str, 50, ""%c\n"", (char)wParam);
                MessageBox(hwnd, str, """", MB_OK);
            }
            break;
        default:                      /* for messages that we don't deal with */
            return DefWindowProc (hwnd, message, wParam, lParam);
    }

    return 0;
}
}}}"	Calmarius
7982	OVA file made with VirtualBox 4.0 can't be read by VMware ovftool	Linux	VirtualBox 4.0.0	2011-01-03T03:16:29Z	2019-07-01T22:52:08Z	2019-07-01T22:52:08Z	"I created a 32-bit openSUSE 11.3 virtual machine using VirtualBox 4.0.0 on a 64-bit openSUSE 11.3 host. The machine works fine. I then exported it to an OVA file using the Export wizard, which did not report any errors. But when I try to read it into VMware using VMware's ""ovftool"" conversion utility, ""ovftool"" reports an error:


znmeb@AlgoCompSynth:~/VirtualBox> ovftool Project\ Kipling.ova .
Opening OVA source: Project Kipling.ova
Opening VMX target: .
Error: OVF Package is not supported by target:
 - Line 25: Unsupported hardware family 'virtualbox-2.2'.


I've attached the XML 'ovf' file - it is indeed calling this a 'virtualbox-2.2' machine, which the VMware tools apparently do not support. I haven't checked the VMware documents yet to see what they do support, but I can do that if you don't have that filed away somewhere.
"	Ed Borasky
18083	Ordering of groups (inside groups) gets lost upon GUI restart	all	VirtualBox 5.2.20	2018-10-26T04:16:14Z	2018-11-05T07:37:26Z	2018-11-05T07:37:26Z	"This issue did appear with 5.2.18 (AFAIK) and is still in the current one. I have not been able to pinpoint, what exactly is missing and in which file.

This is happening: VBox GUI shows groups + vm's, but in a messed up order. Next i manually sort them, as they should show up, close the app, reopen, and the order is back to the messed up one, which did not happen half a year ago.

I am going to attach 2 screenshots and the main config file."	Bard0
20423	Oracle VirtualBox SharedClipboard Use After Free Vulnerability	Linux	VirtualBox 6.1.22	2021-06-17T03:14:59Z	2021-06-17T03:14:59Z	2021-06-17T03:14:59Z	"=  Oracle VirtualBox SharedClipboard Use After Free Vulnerability =



== Affected Software ==

Oracle VM VirtualBox 6.1.22



== Description of Vulnerability ==

This vulnerability allows guest VM to cause denial of service in the context of the host hypervisor. High privileged code on the target guest system is required to exploit this vulnerability. 



== Technical Details ==

VirtualBox provide a HostService named **""VBoxSharedClipboard""** to perform the operation of shared clipboard between Host and Guest. The guest sends the request through **HGCM (Host-Guest Communication Manager)**. The vulnerability is when guest quickly send `VMMDevReq_HGCMDisconnect` and `VMMDevReq_HGCMCall64` to the same service sequentially. That service will operate the `VMMDevReq_HGCMCall64` after the `VMMDevReq_HGCMDisconnect`. So `pvClient` the internal object used in service has been released when it perform disconnect function. But Later **HGCMCall** will use that freed object to operate guest requested function and cause use after free.

In code [1], it free the pCtx and later will be used in **HGCMCall**

`svcDisconnect` -> 
    `ShClSvcImplDisconnect`

{{{
#!div style=""font-size: 80%""
Code highlighting:
{{{#!C
int ShClSvcImplDisconnect(PSHCLCLIENT pClient)
{
    LogFlowFuncEnter();

    PSHCLCONTEXT pCtx = pClient->State.pCtx;
    AssertPtr(pCtx);

    /* Drop the reference to the client, in case it is still there.  This
     * will cause any outstanding clipboard data requests from X11 to fail
     * immediately. */
    pCtx->fShuttingDown = true;

    int rc = ShClX11ThreadStop(&pCtx->X11);
    /** @todo handle this slightly more reasonably, or be really sure
     *        it won't go wrong. */
    AssertRC(rc);

    ShClX11Destroy(&pCtx->X11);
    RTCritSectDelete(&pCtx->CritSect);

    RTMemFree(pCtx); // code [1]

    LogFlowFuncLeaveRC(rc);
    return rc;
}

}}}
}}}

When the guest send a `VBOX_SHCL_GUEST_FN_REPORT_FORMATS` request and guest's uMode is set to `VBOX_SHCL_MODE_BIDIRECTIONAL` or `VBOX_SHCL_MODE_GUEST_TO_HOST`
which is `not` default setting in code [2], it will perform the following function. In function `XtAppAddTimeOut`, it will get crashed.


{{{
#!div style=""font-size: 80%""
Code highlighting:
{{{#!C
static int shClSvcClientReportFormats(PSHCLCLIENT pClient, uint32_t cParms, VBOXHGCMSVCPARM paParms[])
{
    /*
     * Check if the service mode allows this operation and whether the guest is
     * supposed to be reading from the host.
     */
    uint32_t uMode = ShClSvcGetMode();
    if (   uMode == VBOX_SHCL_MODE_BIDIRECTIONAL //code [2]
        || uMode == VBOX_SHCL_MODE_GUEST_TO_HOST)
    { /* likely */ } 
    else
        return VERR_ACCESS_DENIED;
}}}
}}}

`svcCall` -> 
    `shClSvcClientReportFormats` -> 
        `ShClSvcImplFormatAnnounce` ->
            `ShClX11ReportFormatsToX11` ->
                `clipThreadScheduleCall` ->
                    `XtAppAddTimeOut` ->
                        `clipThreadScheduleCall`

{{{
#!div style=""font-size: 80%""
Code highlighting:
{{{#!C

static int clipThreadScheduleCall(PSHCLX11CTX pCtx,
                                  void (*proc)(void *, void *),
                                  void *client_data)
{
    LogFlowFunc((""proc=%p, client_data=%p\n"", proc, client_data));

#ifndef TESTCASE
    XtAppAddTimeOut(pCtx->pAppContext, 0, (XtTimerCallbackProc)proc,
                    (XtPointer)client_data);
    ssize_t cbWritten = write(pCtx->wakeupPipeWrite, WAKE_UP_STRING, WAKE_UP_STRING_LEN);
    Assert(cbWritten == WAKE_UP_STRING_LEN);

}}}
}}}


== The POC ==

The following are step by step guide for replicating the bug:
1. Upload the file `poc.c` and `internal.h` into the guest
2. Compile the poc by `gcc poc.c -o poc`
3. Run `poc` as root



== Requirements ==

* The Host OS must be Linux
* Attacker must be able to run **high-privileged** code on the guest
* The setting of Shared Clipboard need to be `Guest to Host` or `Bidirectional`"	info_starlabs
20718	Oracle Linux 8.2 Guest Mouse Pointer Integration Ubuntu 20.10 Host	Linux	VirtualBox 6.1.30	2021-12-09T15:28:43Z	2021-12-09T15:28:43Z	2021-12-09T15:28:43Z	The mouse does not work right inside Oracle Linux 8.2 guest in VirtualBox 6.1 latest on Ubuntu 20.10 host. The mouse exits before reaching margin of VM console which makes installer GUI buttons inside Oracle Linux 8.2 installer unclickable.	orabuntu
13578	Option to disable the USB device filters	other	VirtualBox 4.3.18	2014-10-31T12:18:10Z	2015-03-21T21:47:42Z	2015-03-21T21:47:42Z	To activate USB devices on the guest they must be either registered in the USB device filter list or the device must be manually activated in the guest. Probably there could also be an option that disables the USB device filters which would cause that all USB devices would automatically be avtivated on the guest.	Sworddragon
19635	"Option ""Auto-resize Guest Display"" grayed out on Xubuntu/Kubuntu 20.4 Host and Windows 10 Guest"	Windows	VirtualBox 6.1.8	2020-06-02T09:32:16Z	2020-11-01T21:31:34Z	2020-11-01T21:31:34Z	"Option ''""Auto-resize Guest Display""'' is disabled / grayed out. Max. resolution is set to 1920x1200. Guest Add-Ons are installed (most recent ones).

I think problems started when I updated to Kubuntu/Xubuntu 20.04 (not really sure). I was able to reproduce this issue on three (!) machines independently. One with Xubuntu 20.04 and two with Kubuntu 20.04. Different graphics cards as well.

A solution is to set ''""Graphics Controller""'' from ''""VBoxSVGA""'' to ''""VBoxVGA""'' and disable 3D acceleration. Then you have to shut down and restart your VM properly (by OS shutdown functionality).

However, ''VBoxVGA'' is not recommended and 3D Acceleration is not available. Should be considered as a bug!


'''Laptop 1:'''

Lenovo Thinkpad P1 2nd Gen

Kubuntu 20.04

VirtualBox 6.1.8

NVIDIA Quadro T2000

Switchable graphics are disabled => Intel graphics card not used

nvidia-driver-440


'''Laptop 2:'''

Lenovo Thinkpad T430

Xubuntu 20.04

VirtualBox 6.1.8

Switchable Graphics active

NVIDIA NVS 5400M

nvidia-driver-390


'''Laptop 3''':

Lenovo Thinkpad T570

Kubuntu 20.04

VirtualBox 6.1.6_Ubuntu r137129

Intel Corporation HD Graphics 620 (rev 02)

Kernel driver"	openminded
18999	openSUSE install links broken	Linux	VirtualBox 6.0.12	2019-10-10T13:29:11Z	2019-10-10T13:29:11Z	2019-10-10T13:29:11Z	"Following the instructions and links on https://www.virtualbox.org/wiki/Linux_Downloads (OpenSUSE) section and it appears the links do not point to the appropriate files on your servers. 

The following terminal output showing errors below:

peter@localhost:~> sudo rpm --import oracle_vbox.asc

[sudo] password for root:
 
peter@localhost:~> wget -q https://www.virtualbox.org/download/oracle_vbox.asc -O- | rpm --import -
error: -: import read failed(0).

peter@localhost:~> zypper refresh

Root privileges are required to run this command.

peter@localhost:~> sudo zypper refresh

Repository 'openSUSE-Tumbleweed-Non-Oss' is up to date.
                                                    
Repository 'openSUSE-Tumbleweed-Oss' is up to date.
                                                        
Repository 'openSUSE-Tumbleweed-Update' is up to date.
                                                     
Retrieving repository 'VirtualBox for openSUSE 20191004 - x86_64' metadata .........................[error]

Repository 'VirtualBox for openSUSE 20191004 - x86_64' is invalid.

[virtualbox|http://download.virtualbox.org/virtualbox/rpm/opensuse/20191004/x86_64] Valid metadata not found at specified URL

Please check if the URIs defined for this repository are pointing to a valid repository.

Skipping repository 'VirtualBox for openSUSE 20191004 - x86_64' because of the above error.

Some of the repositories have not been refreshed because of an error.

peter@localhost:~> ^C

peter@localhost:~>

Another problem for noobs is the error in instruction missing the ""sudo"" root user authority - easy to correct this one as terminal gives the correct advice. (""instruction to run zypper refresh"")

I cannot find any advice on how the following can be implemented ""Users of openSUSE can add  the openSUSE repo file to /etc/zypp/repos.d/."" How is this done and where? This needs more instruction please.



"	ozfossil
15009	Opening the storage settings causes the font color to be temporary black	Windows	VirtualBox 5.0.12	2016-01-05T12:10:01Z	2016-01-07T19:58:24Z	2016-01-07T19:58:24Z	"If I'm opening directly the storage settings of a virtual machine the color of the pre-selected text (in my case ""Controller: SATA"") is black while it should be white. But selecting the pre-selected text again fixes the issue."	Sworddragon
20690	opengl 3D-rendering malfunction	Windows	VirtualBox 6.1.30	2021-11-25T18:28:33Z	2021-11-25T18:28:33Z	2021-11-25T18:28:33Z	"I use a Windows10Pro guest within virtualbox on a linux host machine (debian bullseye).
The problem arises running a CAD application within the guest and rendering a 3D-Model.
The model appears top down. It is not possible to rotate it to head up. Also, some textures of faces are not displayed (these structures are displayed like wireframe - front faces missing).
When I use a Mesa (Software) renderer client by the application, opengl rendering works correct, but much slower - as expected.
"	woec007
8801	only printable Serial-Number allowed for the USB-filter	Windows	VirtualBox 4.0.6	2011-04-27T19:08:53Z	2017-09-08T12:43:16Z	2017-09-08T12:43:16Z	Hi, when i want to make an permanent filter for an USB-Device, which has none-printable characters, the whole VM will crash at the next startup. The failure which is shown, said that in line X a wrong value has been readed. For a workaround, the serial-number could be deleted and the VM will start. The USB-device was an ST-Link from STMicroelectronics.	BjoernC
7897	Only one IP of multi-homed guest is visible	Windows	VirtualBox 3.2.12	2010-12-23T21:06:05Z	2010-12-24T08:03:51Z	2010-12-24T08:03:51Z	"I have a Windows guest that is multihomed (multiple IPs to single NIC).  The host's NIC is bridged so traffic should be passed for both IPs.  However, from the outside network, I can only ping the first IP address assigned to the guest NIC.  Inside the guest, I can ping the first and second IP addresses assigned to the guest NIC.  This is why I believe this is a bug in the host interface bridging code.

BTW, thanks for making bridged adapter support much simpler in VirtualBox 3.1 on Linux...it was a huge PITA before :-)

The vbox.log is attached."	Ken Yee
15227	On Ubuntu 14.04 host Windows 7 guest crashes when copying a few MB to shared clipboard	Windows	VirtualBox 5.0.16	2016-03-09T17:41:29Z	2016-03-10T10:13:44Z	2016-03-10T10:13:44Z	"I've upgraded to VB 5.0.16 this morning and ever since I copy a larger amount of data (simple US ASCII text, a few megabytes) to the shared clipboard on the guest, the latter one crashes.

I'm using an Ubuntu 14.04 (fully updated) host and a Windows 7 guest (fully updated).
The guest has the new (5.0.16) Guest Additions, which was installed using Windows Safe Mode so I could install basic 3D acceleration as well.

The VB log has nothing regarding the crash (meaning that it simply cuts off).
It ends like this:
00:01:52.297240 RTC: period=0x20 (32) 1024 Hz
00:01:52.311908 RTC: period=0x200 (512) 64 Hz
00:01:56.312957 RTC: period=0x20 (32) 1024 Hz
00:01:56.327648 RTC: period=0x200 (512) 64 Hz
00:02:00.328344 RTC: period=0x20 (32) 1024 Hz

The host's syslog (and kern.log) does have some useful info:
Mar  9 18:20:51 mydesktop kernel: [29070.988917] SHCLIP[27199]: segfault at 7f714c3ab5a8 ip 00007f7286ee6e0c sp 00007f7243ffece8 error 4 in libc-2.19.so[7f7286e64000+1bb000]
Mar  9 18:20:51 mydesktop kernel: [29071.180556] vboxnetflt: 0 out of 32992 packets were not sent (directed to host)

I haven't had any VB crashes for a long time, but since the 5.0.14 -> 5.0.16 upgrade using the clipboard became a russian roulette. :("	muzso
16045	On later RHEL6.8 kernels, hostonly networks stop working after just a few minutes	other	VirtualBox 5.1.6	2016-10-07T15:11:18Z	2016-10-07T17:45:32Z	2016-10-07T17:45:32Z	"Hi everyone,
Thanks for !VirtualBox, it's a great product.

I use !VirtualBox as my hypervisor for virtual OpenStack deployments.
I have been using it since the early 5.0 times to deploy multi-nodes OpenStack deployments. These deployments typically include 4 to 12 nodes as VBox machines, using multiple e1000 interfaces (4 per vbox machine, 3 of them being host-only network interfaces).

Here's some more detail:

- Large RHEL6.x hypervisor (128Gb or 192Gb RAM). These typically are kept up-to-date with the RedHat kernels.
- One large undercloud VBox VM (16Gb, pagefusion off, nestedpaging on, vtxvpid on, largepages on, paravirt KVM). It has 4 NICs:
 - nic0: hostonly to `vboxnet0`
 - nic1: hostonly to `vboxnet1`
 - nic2: hostonly to `vboxnet2`
 - nic3: Bridged to external network (Main Hypervisor interface)

- 8 to 16 overcloud VBox VM's with the same settings as the above but using a slightly different NIC configuration:
 - nic0: hostonly to `vboxnet0`
 - nic1: hostonly to `vboxnet1`
 - nic2: hostonly to `vboxnet1` (to make a BOND with nic1)
 - nic3: hostonly to `vboxnet2` 

On nic1/nic2 (connected to `vboxnet1`), I use a mixture of 802.1Q Tagged VLAN's (this is specific to OpenStack).

As I am testing some OpenStack corner cases, I am deleting/re-creating this setup on a very frequent basis (sometimes 4 times per day).

Description of problem:
On latest RHEL6.8 kernels (2.6.32-642.6.1), the `vboxnet[0-2]` network stop 'working' after just a few minutes when deploying the nodes.
No traffic can be seen by tcpdump'ing the adapters on either the Hypervisor or the nodes.
On the hypervisor (RHEL6.8 host), I attempt to capture network traffic like this:
{{{
# tcpdump -nevi vboxnet1
}}}
or
{{{
# tcpdump -nevi vboxnet2
}}}
On the undercloud node, I attempt to capture traffic like this:
{{{
# tcpdump -nevi eth1 (connected to vboxnet1)
}}}
or
{{{
# tcpdump -nevi eth2 (connected to vboxnet2)
}}}
At the begining of a deployment (PXE'ing the overcloud nodes), things start working properly but stop after just a few minutes.

Things were working properly with:
- VBox 5.0.26 + Kernel 2.6.32-642.3.1.el6.x86_64
- VBox 5.0.26 + Kernel 2.6.32-642.4.2.el6.x86_64
- VBox 5.1.6 + Kernel 2.6.32-642.4.2.el6.x86_64

I am also taking great care in making sure that the vbox kernel modules are freshly compiled on the running kernel by cleaning out the /lib/modules and forcing a rebuild (using DKMS on VBox 5.0 and using `vboxconfig` on VBox 5.1)

Things stop working after just a few minutes with:
- VBox 5.1.6 + Kernel 2.6.32-642.6.1.el6.x86_64 (the latest RHEL6.8 kernel).

I am currently trying to isolate the issue and see if I can provide more data.

Is there a way to put an hostonly network in debug mode?

Thanks,
"	ElCoyote
18100	Old DHCP leases interfere with changed server configuration	Linux	VirtualBox 5.2.20	2018-11-03T19:31:54Z	2018-11-03T19:35:58Z	2018-11-03T19:35:58Z	"Host: openSUSE Leap 15

virtualbox-host-kmp-default-5.2.20_k4.12.14_lp150.12.22-lp150.4.20.1.x86_64
virtualbox-host-source-5.2.20-lp150.4.20.1.noarch
virtualbox-5.2.20-lp150.4.20.1.x86_64
virtualbox-qt-5.2.20-lp150.4.20.1.x86_64

In short, the lease file for a NAT net must be deleted by hand. Otherwise the DHCP server (with a different IP) hands out the old leases (wrong IPs)."	robert spitzenpfeil
16668	Office apps display error in seamless mode	Windows	VirtualBox 5.1.20	2017-04-19T05:51:02Z	2017-08-08T07:50:13Z	2017-08-08T07:50:13Z	Windows with an non standard frame such as the ms office 2013 apps got an transparent aura surrounding them.	mietz
17061	NVMe w/o extension pack has too generic of error message	Linux	VirtualBox 5.1.26	2017-09-07T18:12:07Z	2017-09-07T18:12:07Z	2017-09-07T18:12:07Z	"Steps to reproduce:
- Create new Debian 64 VM using defaults for all choices
- Add NVMe controller
- Run VM and note that error message correctly indicates that extpack required but does not mention NVMe even though it does mention USB and RDP."	LNS
18389	numeric username issue	other	VirtualBox 5.2.26	2019-01-30T11:46:57Z	2019-01-30T14:37:45Z	2019-01-30T14:37:45Z	"when use VBoxManage to run a headless VM, it starts and runs correctly and  'Machine state' changed to 'Running' according to the Log.
but when try to list runninng VMs, its state always remains 'Powered Off'

{{{
VBoxManage list vms --long | grep -e Name: -e State:
}}}

It's suspected to be related to the numeric username. It's not locally created one but from AD using SSSD. And when changed to local user, above works fine, headless VM shows the correct machine state."	t4lwh
15722	Number Input in Guest System on Wayland Host	Windows	VirtualBox 5.1.2	2016-08-02T07:31:52Z	2021-04-24T05:35:14Z	2021-04-24T05:35:14Z	"I run VirtualBox 5.1.2-1 on Arch Linux with Gnome 3.20.2. If Gnome is started with Wayland, I cannot input any numbers in the Guest system.

This does not happen, if I use an X.Org session on the Host system."	Phylu
13991	NUL character with a value of 0 ^@ Shown In Linux Console	Linux	VirtualBox 4.3.24	2015-03-26T07:46:08Z	2015-03-26T11:12:54Z	2015-03-26T11:12:54Z	"Hi,

My Specs;

Slackware 14.1 x86_64 - Host
screen size 1920x1080
Virtualbox 4.3.24 - (compiled from source)


Slackware 14.1 x86_64 - Guest
screen size 1920x965
Virtualbox 4.3.24 - (Guest Additions installed)

I noticed when I restart or shutdown Slackware, in the console, I am seeing the NUL character with a value of 0 that is represented as `^@` appear next to text on the screen.

I thought at first something in the Slackware system was causing this.

I was running the Guest with the default of 'Auto-resize Guest Display', this causes the console to have a small size, and it seems for some reason Virtualbox doesn't like it and creates the Nul Character, because if I change the Guest to 'Scaled Mode' it never appears.

I tested this several times changing back and forth with the 'Auto-resize Guest Dispaly' and 'Scaled Mode', and everytime it was on 'Auto-resize Guest Display' it appeared, and everytime it was on 'Scaled Mode' it did not appear.

I'm attaching a screen shot, called vb_character.jpg, notice the line with the red dot I marked, to the far left the word; `^@Sending`..."	VBoxGrl
15378	Not possible to resume VM after host hibernate & resume => Ubuntu bug	all	VirtualBox 5.0.20	2016-05-02T08:34:21Z	2021-07-10T22:33:05Z	2021-07-10T22:33:05Z	"After hibernating and resuming my Ubuntu 14.04 host with a running VM, the VM is paused. All attempts to resume this VM failed with the error message: ""VM is paused due to host power management"". It tried to resume using the GUI by unchecking the hook at menu item ""Machine/Pause"", and I used the CLI tool with these command lines: ""VBoxManage controlvm $VMNAME resume"" and ""VBoxManage startvm $VMNAME"" and always got the same error message.

Workaround: Close the VM, then start it again. All data in the VM is lost.

{{{
$ VBoxManage --version
5.0.20r106931
}}}

{{{
$ uname -a
Linux $HOSTNAME 3.13.0-85-generic #129-Ubuntu SMP Thu Mar 17 20:50:15 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
}}}

{{{
$ cat /etc/os-release
NAME=""Ubuntu""
VERSION=""14.04.4 LTS, Trusty Tahr""
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME=""Ubuntu 14.04.4 LTS""
VERSION_ID=""14.04""
HOME_URL=""http://www.ubuntu.com/""
SUPPORT_URL=""http://help.ubuntu.com/""
BUG_REPORT_URL=""http://bugs.launchpad.net/ubuntu/""
}}}"	Bohnenzaehler
20822	Not able to import an OVA and converting the virtual disk to VDI	Linux	VirtualBox 6.1.32	2022-02-10T11:31:42Z	2022-02-23T18:01:18Z	2022-02-23T18:01:18Z	"

I'm using the official Ubuntu focal cloud image in ova format downloaded from

https://cloud-images.ubuntu.com/focal/current

I try to import it with the command:
{{{
VBoxManage import focal-server-cloudimg-amd64.ova
  --options importtovdi   --vsys 0 --vmname focal-osm11
           --memory 8192 --cpus 2 --eula accept
           --unit 9 --ignore
}}}
Note: I use the importtovdi to be able to resize the disk

I get the following error
{{{           
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interpreting /home/paag/virt/vbox-cloud/focal-server-cloudimg-amd64.ova...
OK.
Disks:
  vmdisk1	10737418240	0	http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized	ubuntu-focal-20.04-cloudimg.vmdk	565177344	-1	

Virtual system 0:
 0: Suggested OS type: ""Ubuntu_64""
    (change with ""--vsys 0 --ostype <type>""; use ""list ostypes"" to list all possible values)
 1: VM name specified with --vmname: ""focal-osm11""
 2: Suggested VM group ""/""
    (change with ""--vsys 0 --group <group>"")
 3: VM settings file name specified with --settingsfile: ""/home/paag/VirtualBox VMs/focal-osm11/focal-osm11.vbox""
 4: Suggested VM base folder ""/home/paag/VirtualBox VMs""
    (change with ""--vsys 0 --basefolder <path>"")
 5: Product (ignored): Ubuntu 20.04 Server (20220208)
 6: No. of CPUs specified with --cpus: 2
 7: Guest memory specified with --memory: 8192 MB
 8: Network adapter: orig VM Network, config 3, extra type=Bridged
 9: Floppy -- disabled
10: CD-ROM
    (disable with ""--vsys 0 --unit 10 --ignore"")
11: SCSI controller, type LsiLogic
    (change with ""--vsys 0 --unit 11 --scsitype {BusLogic|LsiLogic}"";
    disable with ""--vsys 0 --unit 11 --ignore"")
12: IDE controller, type PIIX4
    (disable with ""--vsys 0 --unit 12 --ignore"")
13: IDE controller, type PIIX4
    (disable with ""--vsys 0 --unit 13 --ignore"")
14: Hard disk image: source image=ubuntu-focal-20.04-cloudimg.vmdk, target path=ubuntu-focal-20.04-cloudimg.vdi, controller=11;channel=0
    (change target path with ""--vsys 0 --unit 14 --disk path"";
    disable with ""--vsys 0 --unit 14 --ignore"")
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...
Progress state: VBOX_E_INVALID_OBJECT_STATE
VBoxManage: error: Appliance import failed
VBoxManage: error: Storage for the medium '/home/paag/VirtualBox VMs/focal-osm11/ubuntu-focal-20.04-cloudimg.vdi' is not created
VBoxManage: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component ApplianceWrap, interface IAppliance
VBoxManage: error: Context: ""RTEXITCODE handleImportAppliance(HandlerArg*)"" at line 1119 of file VBoxManageAppliance.cpp
}}}
"	paaguti-u
15393	Not able to connect to USB Webcam	Windows	VirtualBox 5.0.20	2016-05-05T17:21:44Z	2016-05-09T13:35:08Z	2016-05-09T13:35:08Z	"I am running on a Windows 10 Host. Guest is Ubuntu 14.04 LST.
I Have a Microsoft LifeCam HD-5000 webcam connected to USB 2.0

I tried to add it via settings. VB recognized the HW and I added it.

However when searching for the device with lsusb and dmesg it was nowhere to be found. 

Here is what I expected to find:
http://www.linux-hardware-guide.com/2013-05-18-microsoft-lifecam-hd-5000-hd-webcam
"	Yonatan
20075	No VirtualBox packages for Ubutnu 20.10 'Groovy'	all	VirtualBox 6.1.16	2020-12-01T16:15:55Z	2021-01-08T19:31:37Z	2021-01-08T19:31:37Z	"As of 2020-12-01 there are no VirtualBox DEB packages for
newly released (2020-10-22) Ubuntu version 20.10 'Groovy':

http://download.virtualbox.org/virtualbox/debian/dists/

VirtalBox packages for the previous Ubuntu release 20.04 'Focal'
require dependency package 'python-is-python2' to be installed,
but this breaks many other packages in Ubuntu 20.10, e.g. 'dh-python'.
"	PHD
19296	No USB devices available to Win7/Win10 guests on Linux host [VBox 6.0.16]	Windows	VirtualBox 6.0.16	2020-02-08T15:47:58Z	2020-12-10T17:45:16Z	2020-12-10T17:45:16Z	"Under VirtualBox 6.0.14-133895, right-clicking on the USB icon on the VBox window status displays a menu showing a list of the USB interfaces/devices available on the host. Each entry in the list has a checkbox which can be used to assign the USB device to the Guest OS.

However, after upgrading to Version 6.0.16-135674 of VirtualBox, right-clicking on the USB icon does not show the list of USB interfaces/devices - instead it shows a menu list with the only entry of ""USB Settings..."" and a greyed-out entry stating ""No USB Devices Connected""

Although I discovered this issue when running Windows 7 and Windows 10 guest VMs, the same issue also arose when running an Ubuntu 16.04.6 guest VM too.

I have attached the following files:
- a screenshot of a Win10 guest VM, showing the the USB device statuses when running under VBox 6.0.14-133895
- a screenshot of a Win10 guest VM, showing the the USB device statuses when running under VBox 6.0.16-135674
- a zipped copy of the VM log for the Win10 guest, runing under VBox 6.0.16-135674.

My host system is a Lenovo Thinkpad E590 laptop with Intel Core i5-8265U CPU & 8Gb RAM, running Ubuntu 16.04.6.

I originally raised this as an issue on the forum, at [https://forums.virtualbox.org/viewtopic.php?f=7&t=96663&p=469555#p469555]"	thoikix
19046	"No Ubuntu 19.10 ""eoan"" packages"	all	VirtualBox 6.0.14	2019-10-23T15:53:58Z	2019-10-23T15:53:58Z	2019-10-23T15:53:58Z	"Thank you for my favorite desktop virtualization software!

I'm using the `disco` packages on `eoan`, because there doesn't seem to be a public eoan APT repo."	mightyiam
15919	No sound when VirtualBox is installed	other	VirtualBox 5.0.26	2016-09-12T09:10:47Z	2016-09-12T09:42:50Z	2016-09-12T09:42:50Z	"The original report was filed here:
https://github.com/NixOS/nixpkgs/issues/15005

When VirtualBox is installed in NixOS, the kernel emits a backtrace which then results in the host not having any sound. So far it only seems to be happening on the Skylake architecture. We tried multiple Linux versions with always the same result.

None of us have kernel debugging experience, do you mind pointing us to the right direction?"	zimbatm
18820	No sound on 5.2.32 Linux guest on Linux host	Linux	VirtualBox 5.2.32	2019-08-08T05:31:36Z	2019-12-25T08:55:48Z	2019-12-25T08:55:48Z	"I first reported this issue on July 18 here:
https://forums.virtualbox.org/viewtopic.php?f=7&t=93940

For the following weeks I tried playing with various configurations including .asoundrc and asoundrc.conf, the VB audio settings and tools like alsamixer and not a peep. It was extremely frustrating

Sound worked just fine on a quick boot up in qemu. I was about to give up on VB when someone with the identical problem replied to the above thread reporting that reverting to 5.2.18 corrected it. Doing so corrected the issue for me also.

There are logs attached to the above-mentioned thread.  I was also emailing various logs and command output to someone for assistance so may have something else useful in history.

Here are my system specs:

Host: Devuan Jessie 32 bit

Guests: Devuan ascii and Devuan Beowulf also 32 bit, of course.

I was using these VMs for package testing and had not previously tested audio.

Thanks you and hope that you can find the bug and correct it.

"	nauved
19067	No sound from any guest when using ALSA (PulseAudio works)	all	VirtualBox 6.0.14	2019-11-06T13:54:17Z	2019-11-06T13:54:17Z	2019-11-06T13:54:17Z	"When running VirtualBox 6.0.14 on Ubuntu 19.10, neither Windows 10 guest nor latest Debian are able to emit any sounds if I configure the host to use ALSA. PulseAudio does work.

It would seem the problem is somewhere on the host side where it for some reason fails to interact with the sound system. PulseAudio wasn’t running when I tried using ALSA. The configuration is the default, that is, neither /etc/asoundrc nor ~/.asoundrc are present.

The log does not appear to contain anything of relevance, attaching anyway."	rdaysky
21423	No repo for Fedora 37	all	VirtualBox-7.0.6	2023-01-21T22:40:54Z	2023-02-02T11:15:50Z	2023-02-02T11:15:50Z	"I just updated my Fedora (x86_64) host to release 37.

The DNF upgrade complained of a 404 for the VirtualBox repo.

Sure enough, http://download.virtualbox.org/virtualbox/rpm/fedora/ does not have a '37' child.

Can this be fixed?

Thanks."	Timothe Litt
17303	"No obvious way to exit snapshot ""Properties"" without changes"	all	VirtualBox 5.2.0	2017-11-22T21:57:00Z	2017-11-22T22:06:27Z	2017-11-22T22:06:27Z	"In vboxmanage, Snapshots view, if an existing snapshot is selected and then the ""Properties"" button is pressed, a large editable form appears. It has ""Reset"" and ""Apply"" buttons but they are grayed out if no changes have been made (as they should be).

The problem is, there is no apparent way to make the form go away without making any changes.

I suggest adding a ""Cancel"" button which closes the form without making changes (and discarding changes if entered).  Most users will immediately understand it's function, since many dialogs in Linux and Open Office work that way (for example)."	Jim Avera
19638	no network connection with virtio-net after some time	Linux	VirtualBox 6.0.22	2020-06-03T17:54:10Z	2020-06-03T17:57:42Z	2020-06-03T17:57:42Z	"Hi,

I'm running an Ubuntu 18.04 guest on a ubuntu 18.04 host. The guest uses virtio-net for the network adapter.

After some uptime, you can use the interface anymore. The syslog is flodded with

{{{
net eth0: Unexpected TXQ (0) queue failure: -5
}}}

I have to reboot the VM to get it working again.

If you need any information, please don't hesitate to ask for.

Regards,
meiser"	Peter Meiser
16261	no media in w7 when connecting usb3 disk with uas	Windows	VirtualBox 5.1.10	2016-12-02T19:22:58Z	2016-12-05T08:11:55Z	2016-12-05T08:11:55Z	"I'm using gentoo, kernel 4.4.26, VB version 5.1.10. Also I have an external disk seagate 3tb st3000dm001 in its native external enclosure (with usb3). I get a contradiction.
On the host (gentoo) it is seen as a disk ONLY if the module ""uas"" (USB attached SCSI) is loaded. Otherwise, only as some usb controller.
In the guest (w7pro) it appears as a disk ONLY if the ""uas"" module of the host is disabled. Otherwise, again only as some attached usb device.
I could reproduce it several times in a row. With and w/o a reboot.

Technically I can insert/remove the ""uas"" module depending on a situation. Also, I'm not sure is it a problem of ""uas"" module or VB, but the pattern is clear.

Any suggestions to solve/improve this behaviour?"	alex-kas
18815	No guest DHCP through host WiFi in bridged mode	Linux	VirtualBox 6.0.10	2019-08-06T13:32:14Z	2019-08-25T02:48:36Z	2019-08-25T02:48:36Z	"Hi there!

I'm experiencing problems with the combination host wifi, bridged mode and guest DHCP. I'm hoping not to create a duplicate.

- Host OS: Ubuntu 18.04
- Guest OS: Ubuntu 18.04
- Version 6.0.10 r132072 (Qt5.9.5)

The guest VM is sending DHCP Requests with its MAC address but gets no answer.
When debugging on the hosts wlan0 I see 2 DHCP Requests - 1 from the MAC of the guest VM and 1 with the MAC of wlan0 on behalf of the guest VM - but still no answer. I'm using tcpdump to trace packets.

Debugging of the DHCP server shows incoming request and outgoing answers.

Other physical devices get IP addresses.

A friend of mine with Windows 10 for the host OS sees the same problem.

There are hints on the net to change the adapter type from 'Intel PRO 1000 MT Desktop' to '... Server' - unfortunately without success for me.

On cable ethernet it works fine. The same goes for WiFi using manual IP address configuration on the guest OS.

Cheers!

JK
"	JKu
14414	No DNS server information on DHCP enabled NATNetworks	Linux	VirtualBox 5.0.0	2015-08-07T13:43:58Z	2015-08-17T19:28:16Z	2015-08-17T19:28:16Z	"I've configured a NATNetwork with DHCP enabled:

{{{
NetworkName:    NatNetwork
IP:             10.0.3.1
Network:        10.0.3.0/24
IPv6 Enabled:   No
IPv6 Prefix:    
DHCP Enabled:   Yes
Enabled:        Yes
loopback mappings (ipv4)
        127.0.0.1=2
}}}

It created a DHCP server configuration like this:
{{{
NetworkName:    NatNetwork
IP:             10.0.3.3
NetworkMask:    255.255.255.0
lowerIPAddress: 10.0.3.4
upperIPAddress: 10.0.3.254
Enabled:        Yes
}}}

When the VM is started it requests the IP address to DHCP server. On the DHCP response (DHCP ACK package) there is no DNS information, but there is the Domain Name (DNS suffix).

If I manually configure the DNS in the virtual machine to 10.0.3.1 the name resolution works.
"	jacksonfoz
11508	No detection of screen size change in fullscreen when using xubuntu/xfce4 as host	Windows	VirtualBox 4.2.6	2013-02-20T17:10:36Z	2013-02-20T17:10:36Z	2013-02-20T17:10:36Z	"With Ubuntu (Unity/metacity or compiz), no problem.
With xfce4, I can resize the screen with xrandr or the xfce4 tools, vbox does not detect it. If I go windowed then fullscreen again (host + f), the vbox screen is resized correctly (and I see Display::handleDisplayResize() in logs).
In case it's xfce's fault, is there a way to send the Display::handleDisplayResize() event manually?"	acathla
18406	no 64 bit guest support in VB on  intel 64bit CPU and 64bit Kubuntu 18.4 host	Windows	VirtualBox 6.0.4	2019-02-02T07:31:06Z	2019-02-10T08:40:38Z	2019-02-10T08:40:38Z	"VTX is enabled in bios, Kubuntu 18.04 64bit host OS is running fine, Virtual box 64 bit is installed latest version and matching Evtension Pack. However there is no 64 bit support for the guests, only 32 bit.
This feature was working previously on the same machine on Kubuntu 17.1, but doesn't work any more after fresh install Kubuntu 18.04., Kubuntu 18.10 has same issue.
Hint: problem could be CPU specific"	ElenaLight
14034	NMI kernel panics on HP Proliants running RHEL causing machines to reboot at VBoxHost_RTSemEventMultiWaitEx	Windows	VirtualBox 4.3.26	2015-04-08T10:41:49Z	2017-02-06T10:09:06Z	2017-02-06T10:09:06Z	"Over the past few months we have been experiencing seemingly random reboots of our DL360 G7 and DL360 G6 machines every few days when using VirtualBox 4.3. We don't think we have been suffering from this problem when using VirtualBox 4.2. The vmcore-dmesg.txt file that is written to /var/crash contains stack traces that might seem to implicate VirtualBox as a cause of the crashes

{{{
<4>Pid: 5567, comm: EMT-0 Not tainted 2.6.32-504.12.2.el6.x86_64 #1
<4>Call Trace:
<4> <NMI>  [<ffffffff8152933c>] ? panic+0xa7/0x16f
<4> [<ffffffffa002e4df>] ? hpwdt_pretimeout+0x9f/0xcc [hpwdt]
<4> [<ffffffff815300f5>] ? notifier_call_chain+0x55/0x80
<4> [<ffffffff8153015a>] ? atomic_notifier_call_chain+0x1a/0x20
<4> [<ffffffff810a4eae>] ? notify_die+0x2e/0x30
<4> [<ffffffff8152de17>] ? do_nmi+0x217/0x340
<4> [<ffffffff8152d680>] ? nmi+0x20/0x30
<4> <<EOE>>  [<ffffffffa04bb210>] ? VBoxHost_RTSemEventMultiWaitEx+0x10/0x20 [vboxdrv]
<4> [<ffffffffa04b84da>] ? rtR0MemAllocEx+0x8a/0x250 [vboxdrv]
<4> [<ffffffffa04a98ca>] ? supdrvIOCtlFast+0x8a/0xa0 [vboxdrv]
<4> [<ffffffffa04a93a4>] ? VBoxDrvLinuxIOCtl_4_3_26+0x54/0x210 [vboxdrv]
<4> [<ffffffff811a3782>] ? vfs_ioctl+0x22/0xa0
<4> [<ffffffff811a3924>] ? do_vfs_ioctl+0x84/0x580
<4> [<ffffffff810e5c7b>] ? audit_syscall_entry+0x1cb/0x200
<4> [<ffffffff811a3ea1>] ? sys_ioctl+0x81/0xa0
<4> [<ffffffff810e5a7e>] ? __audit_syscall_exit+0x25e/0x290
<4> [<ffffffff8100b072>] ? system_call_fastpath+0x16/0x1b
}}}
These machines are running recently patched versions of Red Hat Enterprise Linux Server release 6.6 (Santiago). The problem has been seen on about 6 different machines. This is occuring with VirtualBox 4.3.26 but has been happening with many other recent releases in the 4.3 series. We only have 1 guest VM running on each of these RHEL machines and it is running Windows 2008 R2 64 Bit as a guest.

We have not as far as we know configured the HP Watchdog Timer in any special way.
Ticket 13762 seems to bear some similarities to this ticket. I have attached one example of vmcore-dmesg.txt

"	nj
17965	New Kali Linux Kernel 4.17.0 error	Windows	VirtualBox 5.2.18	2018-08-31T07:34:38Z	2018-09-11T14:19:35Z	2018-09-11T14:19:35Z	"I updated virtualbox to the lastest version and then i upgraded my Linux host (Kali) and it has changed from kernel 4.15.0 to kernel 4.17.0... after this upgrade my Linux machine is unable to run graphical environment... i get a black screen for a long time and only some times it give me this message:

''' started update utmp about system runlevel changes '''

and it remains stuck like this. I switched to a new console (alt-ctrl-F1) for try to resolve somehow, but without results.
I updated the same version of Kali Linux (always kernel from 4.15.0 to 4.17.0) to another virtual host (under VMWare) and i didn't have problems, it runs fine."	Maxxx
15642	Never fixed VBox 5.1/5.0.26/24 VGA: fixed an occasional hang when running Windows guests with 3D enabled	Windows	VirtualBox 5.1.0	2016-07-19T10:14:14Z	2016-09-24T06:08:43Z	2016-09-24T06:08:43Z	"When I installed GuestAddition of VBox5.1/5.0.26 also 5.0.24,
they required to check 2D/3D function as automatically.

I always turned off 3D function for disabling at VMM.
Only 2D using I can not get more bigger screen size 1280x720 on GuestOS
Before your announcement of fixed 3D function,I could used 1920x1200 as GuestOS.
I think this is also bug.

But it is more terrible things which turn on 3D function on VMM.
After turn on 3D function when GuestOS(Windows10 64bit) is started up, GuestOS is crashed and HostOS(Debian8 64bit)Gnome on Xorg also is crashed. I attached log file.

It is seemed to have relationship with GPU.
Crashed GPU is NVIDIA Corporation GF108 [GeForce GT 630] on Debian8

But I also tested below GPU.It is no problem at VBox 5.1.
NVIDIA Corporation GF106 [GeForce GTS 450]

Thank you

Yomo



"	Yomo
20950	Network interface names in the GUI are unsorted	all	VirtualBox 6.1.32	2022-05-20T10:14:25Z	2022-05-20T10:14:25Z	2022-05-20T10:14:25Z	The network interface names in the GUI are unsorted. When configuring a bridged adapter to be mapped to one of many test VLAN interfaces on a host machine, it is necessary to go linearly through the whole list to find the right interface. The list should be alphabetically sorted.	Thomas Dreibholz
6519	Network bridge does not work with multiple mac addresses on the guest side	Linux	VirtualBox 3.1.6	2010-04-10T00:41:23Z	2011-02-19T18:34:59Z	2011-02-19T18:34:59Z	"The Bridged network mode seems to be unable to deal with multiple MAC addresses being used to send packets from a guest. This situation occurs when a network bridge is configured inside a guest system.

It looks like the virtualbox network bridge can only keep track of one MAC address for which it accepts incoming packets for the guest; that mac address is most likely set to the source address of the last outgoing packet from the guest. This results in major packetloss for both the guest and systems on the other side of the guest's network bridge.

In most cases, the described behaviour is close to how a normal NIC would behave. However, if the NIC is in Promiscuous mode (which is the case for network bridges), the NIC should present all packets it receives to the guest, without filtering.

It may not be feasible to present all received packets to the guest for performance reasons; however if the guest explicitly enables promiscuous mode it is requesting to receive all such packets, and usually needs this behaviour.

A reasonable alternative to accepting *all* packets would be to enlarge the MAC address buffer, but this would require a far more complex network switch implementation."	Ivo Smits
9004	Neo-layout keyboard in host is not supported, regression from Bug #2595?	Windows	VirtualBox 4.0.8	2011-06-01T09:56:10Z	2011-09-30T21:22:07Z	2011-09-30T21:22:07Z	I am using Virtualbox 4.0.8 on Linux Debian Host (Debian SID) with a NEO2 Keyboard layout (see http://www.neo-layout.org). If I use this keyboard while starting Virtualbox, several keys don’t work: for example [CAPS]+[l] for “-” etc. If I overwrite VBoxKeyboard.so with the version of VBoxKeyboard.so attached to Bug #2595, everything works fine.	Johannes Fichtinger
14724	Need way to move virtual-disk files of running VM	other	VirtualBox 5.0.6	2015-10-20T23:35:20Z	2017-03-17T11:01:58Z	2017-03-17T11:01:58Z	"This is an enhancement request to permit virtual disk files to be moved while they are in use by a (paused) VM.

If an out-of-disk condition occurs, VBox very nicely pauses the VM and pops up a message so you can fix the problem and resume.  However, it continues to hold the virtual disk (including snapshot) files open, so even if they are moved and replaced by symlinks, no disk space can be freed up.  If the VM was running in a dedicated partition, i.e., there is nothing else to move or delete besides VM's files, then there is no possible recovery without loosing VM state; VBox won't close the old files until the VM is shut down, and it and it can't save the VM state if disk is full.

Following are a couple of suggestions, one basic and the other fancy:

Method A (Basic): When a VM is ""paused"", close all the VM's files, at least the virtual disks; re-open them only when the VM is resumed.

   This would let you manually relocate a virtual disk and replace it with a symlink while the VM is paused.  Using the symlink would be necessary because the .vbox file still could not be edited while VBox is running.

Method B (Fancy): Provide a comprehensive command to move a virtual disk, updating VirtualBox.xml or the VM's .vbox file as appropriate.  For example

  VBoxManage modifyvm <vmident> --movemedium <uuid|filename> /destination/folder/
  VBoxManage modifyvm <vmident> --movesnap <snapid|filename> /destination/folder/

This would 
  1. pause all VMs using the specified virtual disk *if not already paused*
(and make them close the underlying files, just as in the simpler method above); 
  2. move the file, 
  3. update and rewrite VirtualBox.xml or the VM's .vbox file with the new path; 
  4. resume VMs paused in step 1 (but not VMs which were already paused)

"	Jim Avera
4189	Need ot be able to chunk large VMDK files when exporting an appliance	Solaris	VirtualBox 2.2.4	2009-06-05T16:44:35Z	2009-06-05T16:44:35Z	2009-06-05T16:44:35Z	"We need an easy way to split up the files that comprise a virtual appliance so that they are easily distributed to our end users on media like DVDs and CDs. My preference would be a check box in the Export Appliance dialog box with an option like ""Split large files into 2 GB chunks."" Import Appliance should be smart enough to recognize that is importing a chunked vmdk and rebuild it as part of the import. (If that is too difficult to do, it would be acceptable if the user had to select an option in the Import Appliance dialog to tell VirtualBox to rejoin the vmdk.)

In the current release of VirtualBox, this exercise is left to the users. Sure, I can take a virtual appliance and split it up using my native OS utilities or an installer product of some sort, and then provide instructions for the end user to rebuild the file but there are some major disadvantages to doing things this way:

- The user requires extra disk space - some space for the split up file, and then some space for the rebuilt file

- It is an acceptance barrier to the end user to have to perform an additional step beyond File / Import Appliance to import an appliance

- Every developer who wants to redistribute virtual appliances on DVDs has to come up with their own methods of chunking, which likely vary depending on the operating system on which the appliance will be deployed.

Therefore, while the omission of any chunking capability might meet the OVF standard, it provides difficulties for those of us who want to send out virtual appliances using any medium other than file downloads.

Please consider this RFE. The lack of a chunking feature is causing some developers to have to do a lot of extra work. Please note that redistribution of VMware virtual machines on DVDs is trivial because that product support 2 GB chunks for their vmdk files.

Thanks and regards,

David"	David Goldsmith
10557	Need an option to save a machine's state somewhere else	all	VirtualBox 4.1.14	2012-05-12T17:08:26Z	2012-05-12T17:08:26Z	2012-05-12T17:08:26Z	"Suppose you incurr into a DISK FULL error while a VM is running (it actually happened to me). The machine is automatically paused, and you are prompted to free some space on disk.
Suppose you cannot free up any space because the vdi and snapshots are alone on a disk partition and they have filled it up.

- You cannot save the machine
- You cannot clone it because when you clone it, you are not asked where to store the files for the new machine
- you cannot export it because it is not turned off

- you have other disks with plenty of space where you could save the current space and copy all the vdi's so as to later resume the machine with enough disk space, but there's no way you can do that because you can't save it anywhere else than in the disk that is full.


So, an option should exist (or at least should be provided as a backup mechanism whenever a disk full error is encountered) to save the current machine state somewhere other than the default location.

"	matteo sisti sette
2439	"Need ""are you sure"" power off option"	Windows	VirtualBox 2.0.2	2008-10-18T22:03:01Z	2009-05-04T01:54:45Z	2009-05-04T01:54:45Z	"Hi All,

   When I click the ""X"" in the upper right of my virtual machine's window, I am given three
options, ""Save State"", ""shutdown"", and ""power off"".  The first two are harmless.  The
""power off"" can cause damage to the guest OS.  And, ""butterfingers"" here is always pressing
the wrong button. This is not a fault of the software by my own ""klutz"" factor.

   Would the developers please consider adding a two step process to the power off function?
Maybe a prompt to the effect of ""Are you sure?"".  This would save my ever loving careless ass.
Consider it a ""Human Engineering"" enhancement.

Many thanks,
-T


"	ToddAndMargo
20337	Natnetwork loose connectivity after a while	Linux	VirtualBox 6.1.22	2021-05-04T08:29:04Z	2021-05-04T08:29:04Z	2021-05-04T08:29:04Z	"Hi,
I have created 5 VMs based on Debian 10, with Natnetwork configured (because i need to let the VMs talk to each others and access the Vpn on the host).

Each one has static IP, no specific tunning or special configuration. just Debian Vms and default natnetwork configured.

All Vms are working without any problems, i can access it with port forwarding. and after a while (one minute, 3 minutes...), the IP connectivity is suddenly cut, the ssh connections are stuck !

I must restart the natnetwork with VBoxManage ... Same result with paravirtualized network interface or Intel Pro desktop.
So, it s impossible to work in theses conditions.

it seems that problem exists for years or i missed something ?

Thanks to do something on that issue.
Francois




"	Francois94130
18068	NAT process infinite loop call `poll` function	Linux	VirtualBox 5.2.20	2018-10-22T07:42:56Z	2018-10-22T07:42:56Z	2018-10-22T07:42:56Z	"Host machine: Fedora 28
Guest machine: Windows 10

My guest system is Windows 10 and using NAT network, and Windows 10 system suddenly unable to access the Internet at some point, but my host machine can access the network normally. I using Wireshark capturing some ARP data flow in Windows 10:

{{{
1   0.000000 PcsCompu_7a:1a:df → RealtekU_12:35:02 ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
    2   0.207297 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
    3   3.718693 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
    4   4.500012 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
    5   5.500048 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
    6   6.719889 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
    7  10.721331 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
    8  11.499537 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
    9  12.500007 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   10  15.499582 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   11  16.721794 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   12  17.500389 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   13  18.500008 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   14  21.499517 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   15  22.725696 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   16  23.499997 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   17  24.499501 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   18  27.499508 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   19  27.982749 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   20  28.500004 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   21  29.500001 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   22  34.985277 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   23  35.500502 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   24  36.500023 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   25  38.248133 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   26  42.249642 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   27  42.999528 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   28  43.999519 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   29  47.235338 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   30  48.000015 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   31  49.000018 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
}}}

IP 10.0.2.2 is NAT's gateway address, as you see, my Windows system send some ARP broadcast packet to find 10.0.2.2's MAC address, but not recive any response packet.

At the same time, in my host machine, the `NAT` process occupies a lot of CPU resources. I using `strace` command tracing `NAT` process:

{{{
poll([{fd=46, events=POLLPRI|POLLRDNORM|POLLRDBAND}, {fd=45, events=POLLIN}, {fd=98, events=POLLIN|POLLPRI}, {fd=76, events=POLLIN|POLLPRI}, {fd=229, events=POLLIN|POLLPRI}, {fd=93, events=POLLIN|POLLPRI}, {fd=91, events=POLLIN}, {fd=89, events=POLLIN}, {fd=81, events=POLLIN}, {fd=96, events=POLLIN}, {fd=102, events=POLLIN}, {fd=97, events=POLLIN}, {fd=88, events=POLLIN}, {fd=70, events=POLLIN}, {fd=68, events=POLLIN}], 15, 500) = 1 ([{fd=91, revents=POLLIN}])
poll([{fd=46, events=POLLPRI|POLLRDNORM|POLLRDBAND}, {fd=45, events=POLLIN}, {fd=98, events=POLLIN|POLLPRI}, {fd=76, events=POLLIN|POLLPRI}, {fd=229, events=POLLIN|POLLPRI}, {fd=93, events=POLLIN|POLLPRI}, {fd=91, events=POLLIN}, {fd=89, events=POLLIN}, {fd=81, events=POLLIN}, {fd=96, events=POLLIN}, {fd=102, events=POLLIN}, {fd=97, events=POLLIN}, {fd=88, events=POLLIN}, {fd=70, events=POLLIN}, {fd=68, events=POLLIN}], 15, 500) = 1 ([{fd=91, revents=POLLIN}])
poll([{fd=46, events=POLLPRI|POLLRDNORM|POLLRDBAND}, {fd=45, events=POLLIN}, {fd=98, events=POLLIN|POLLPRI}, {fd=76, events=POLLIN|POLLPRI}, {fd=229, events=POLLIN|POLLPRI}, {fd=93, events=POLLIN|POLLPRI}, {fd=91, events=POLLIN}, {fd=89, events=POLLIN}, {fd=81, events=POLLIN}, {fd=96, events=POLLIN}, {fd=102, events=POLLIN}, {fd=97, events=POLLIN}, {fd=88, events=POLLIN}, {fd=70, events=POLLIN}, {fd=68, events=POLLIN}], 15, 500) = 1 ([{fd=91, revents=POLLIN}])
poll([{fd=46, events=POLLPRI|POLLRDNORM|POLLRDBAND}, {fd=45, events=POLLIN}, {fd=98, events=POLLIN|POLLPRI}, {fd=76, events=POLLIN|POLLPRI}, {fd=229, events=POLLIN|POLLPRI}, {fd=93, events=POLLIN|POLLPRI}, {fd=91, events=POLLIN}, {fd=89, events=POLLIN}, {fd=81, events=POLLIN}, {fd=96, events=POLLIN}, {fd=102, events=POLLIN}, {fd=97, events=POLLIN}, {fd=88, events=POLLIN}, {fd=70, events=POLLIN}, {fd=68, events=POLLIN}], 15, 500) = 1 ([{fd=91, revents=POLLIN}])
poll([{fd=46, events=POLLPRI|POLLRDNORM|POLLRDBAND}, {fd=45, events=POLLIN}, {fd=98, events=POLLIN|POLLPRI}, {fd=76, events=POLLIN|POLLPRI}, {fd=229, events=POLLIN|POLLPRI}, {fd=93, events=POLLIN|POLLPRI}, {fd=91, events=POLLIN}, {fd=89, events=POLLIN}, {fd=81, events=POLLIN}, {fd=96, events=POLLIN}, {fd=102, events=POLLIN}, {fd=97, events=POLLIN}, {fd=88, events=POLLIN}, {fd=70, events=POLLIN}, {fd=68, events=POLLIN}], 15, 500) = 1 ([{fd=91, revents=POLLIN}])
poll([{fd=46, events=POLLPRI|POLLRDNORM|POLLRDBAND}, {fd=45, events=POLLIN}, {fd=98, events=POLLIN|POLLPRI}, {fd=76, events=POLLIN|POLLPRI}, {fd=229, events=POLLIN|POLLPRI}, {fd=93, events=POLLIN|POLLPRI}, {fd=91, events=POLLIN}, {fd=89, events=POLLIN}, {fd=81, events=POLLIN}, {fd=96, events=POLLIN}, {fd=102, events=POLLIN}, {fd=97, events=POLLIN}, {fd=88, events=POLLIN}, {fd=70, events=POLLIN}, {fd=68, events=POLLIN}], 15, 500) = 1 ([{fd=91, revents=POLLIN}])
poll([{fd=46, events=POLLPRI|POLLRDNORM|POLLRDBAND}, {fd=45, events=POLLIN}, {fd=98, events=POLLIN|POLLPRI}, {fd=76, events=POLLIN|POLLPRI}, {fd=229, events=POLLIN|POLLPRI}, {fd=93, events=POLLIN|POLLPRI}, {fd=91, events=POLLIN}, {fd=89, events=POLLIN}, {fd=81, events=POLLIN}, {fd=96, events=POLLIN}, {fd=102, events=POLLIN}, {fd=97, events=POLLIN}, {fd=88, events=POLLIN}, {fd=70, events=POLLIN}, {fd=68, events=POLLIN}], 15, 500) = 1 ([{fd=91, revents=POLLIN}])
poll([{fd=46, events=POLLPRI|POLLRDNORM|POLLRDBAND}, {fd=45, events=POLLIN}, {fd=98, events=POLLIN|POLLPRI}, {fd=76, events=POLLIN|POLLPRI}, {fd=229, events=POLLIN|POLLPRI}, {fd=93, events=POLLIN|POLLPRI}, {fd=91, events=POLLIN}, {fd=89, events=POLLIN}, {fd=81, events=POLLIN}, {fd=96, events=POLLIN}, {fd=102, events=POLLIN}, {fd=97, events=POLLIN}, {fd=88, events=POLLIN}, {fd=70, events=POLLIN}, {fd=68, events=POLLIN}], 15, 500) = 1 ([{fd=91, revents=POLLIN}])
poll([{fd=46, events=POLLPRI|POLLRDNORM|POLLRDBAND}, {fd=45, events=POLLIN}, {fd=98, events=POLLIN|POLLPRI}, {fd=76, events=POLLIN|POLLPRI}, {fd=229, events=POLLIN|POLLPRI}, {fd=93, events=POLLIN|POLLPRI}, {fd=91, events=POLLIN}, {fd=89, events=POLLIN}, {fd=81, events=POLLIN}, {fd=96, events=POLLIN}, {fd=102, events=POLLIN}, {fd=97, events=POLLIN}, {fd=88, events=POLLIN}, {fd=70, events=POLLIN}, {fd=68, events=POLLIN}], 15, 500) = 1 ([{fd=91, revents=POLLIN}])
.......

}}}

as you see, NAT process infinite loop call `poll` function"	lu4nx
14748	nat network hangs intermittantly	Windows	VirtualBox 5.0.8	2015-10-26T12:17:06Z	2021-05-04T20:17:25Z	2021-05-04T20:17:25Z	"Host: Ubuntu 14.04 64Bit

Virtualbox 5.0.8

Guest: Windows Server 2012, Windows XP - defect present for both guests.

Both guests are headless, used only by RDP.

Sometimes (1-2 times per day) guest network adapter stops to recieve any packets from ""media"", can't ping default gw for this network interface.

The only things that fix issue is nat network restart:

{{{
VBoxManage natnetwork stop --netname nat-int-network-2
VBoxManage natnetwork start --netname nat-int-network-2
}}}

Of course, may be there are another ways... reboot particular guest or perform ""sudo  /etc/init.d/vboxdrv restart"" (requiring all VMs stop)... But the only way I found to fix issue (while not rebooting/stopping guest is restart nat network...
 
I have two nat networks (192.168.1.0/24 and 192.168.2.0/24). They hangs indpendently:

- First one, nat-int-network (192.168.1.0/24), connected to WinXP guest (single network adapter within guest) hangs rarely - 1-2 times per month. 

- Second one, nat-int-network-2 (192.168.2.0/24), connected to Windows Server 2012 Guest (one of two network adapters within guest, second one is openvpn tap0 interface attached to guest as Bridged Adapter) and hangs more often - 1-2 times per day... sometime 1 time per 2-3 days...

Windows Server guest is a loaded by 5-10 simultaneous RDP-sessions, but average load is quite moderate... 

I understand that info provied is not enough.
Please, let me know - what kind of details should I add to?"	dtgeorge
20286	máquina demorando para iniciar	Linux	VirtualBox 6.1.18	2021-04-04T01:18:53Z	2021-04-04T01:58:10Z	2021-04-04T01:58:10Z	"já tentei de varias formas corrigir isso, instalei extensões (Oracle_VM_VirtualBox_Extension_Pack-6.1.18)
 e também pack pra distribuição a qual eu uso (virtualbox-6.1_6.1.18-142142_Debian_buster_amd64 (1).deb)

 E ate agora nada, uso o Linux da ofensive security (https://www.offensive-security.com/kali-linux-vm-vmware-virtualbox-image-download/#1572305786534-030ce714-cc3b)
 imagem pronta.
[[BR]]
 Inicio a maquina e deixo o computador ligado, e ela varou  passou 28 horas sem sair da tela preta com a logo do kali "	anjo gelado
20204	"My VBoxManage-code, runned on the host, can not bring a ""windows guest registry value"" into my guestproperty"	Windows	VirtualBox 6.1.14	2021-02-18T22:12:24Z	2021-02-18T22:12:24Z	2021-02-18T22:12:24Z	"I try to get a registry value of the guest with a command that runs in the host. But this does not work.

To get a better idea of the problem, I have checked parts of my code separately.

First I have tested the command in the windows guest.
Result: It works.

Here is the command:
I go into my Windows 7 guest. I open the cmd-window. I type in the cmd-window the following inclusive <""> .

{{{
""%SystemRoot%\system32\cmd.exe"" -- 'cmd' /c start ""run this"" For /F ""EOL=H Tokens=2,*"" %G In ('""""%SystemRoot%\System32\reg.exe"" Query ""HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.docx\UserChoice"" /V ""ProgId"" 2> NUL""') Do @""D:\NT3x\VBoxControl.exe"" --nologo guestproperty set /myproperties/myproperty ""%H""
}}}

To be sure, that it has worked, I go back to my Linux host and type in a terminal the following:

{{{
VBoxManage guestproperty get ""MyWin7Guest"" /myproperties/myproperty
}}}
 Output:

{{{
Value: Word.Document.12
}}}

After, I now change the guestproperty (so that I can use it later again) with the command:

{{{
VBoxManage guestproperty set ""MyWin7Guest"" /myproperties/myproperty ""deleted""
}}}

Now I create a variable of the code above, (but not of the whole one, please compare them) because I need it later.
I do this in a linux terminal in my Linux host:

{{{
q='For /F ""EOL=H Tokens=2,*"" %G In ('
w=""'""
e='""""%SystemRoot%\System32\reg.exe"" Query ""HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.docx\UserChoice"" /V ""ProgId"" 2> NUL""'
r=""'""
t=') Do @""D:\NT3x\VBoxControl.exe"" --nologo guestproperty set /myproperties/myproperty ""%H""'
p=$q$w$e$r$t
}}}
So I have the code above in $p. I need this later:

{{{
$ echo $p
For /F ""EOL=H Tokens=2,*"" %G In ('""""%SystemRoot%\System32\reg.exe"" Query ""HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.docx\UserChoice"" /V ""ProgId"" 2> NUL""') Do @""D:\NT3x\VBoxControl.exe"" --nologo guestproperty set /myproperties/myproperty ""%H""
}}}



As the code has worked in my guest-system, I can now go one step further. I'll put the following code in front of it:

{{{
VBoxManage guestcontrol ""MyWin7Guest"" start --username XX  --password YY --exe
}}}

So that I have now the following whole code:

{{{
VBoxManage guestcontrol ""MyWin7Guest"" start --username XX  --password YY --exe ""%SystemRoot%\system32\cmd.exe"" -- 'cmd' /c start ""run this"" $p
}}}


I type this code into a terminal in my Linux host. Done.
What is the output? No output. No error. It looks like this if the code had been executed correctly.

To be sure, that it has worked, I type in my Linux terminal the following:

{{{
VBoxManage guestproperty get ""MyWin7Guest"" /myproperties/myproperty
}}}

Here is the result:

{{{
$ VBoxManage guestproperty get ""Win7NeuFurOfficeVersuch"" /myproperties/myproperty
Value: deleted
}}}

So: Why does this not work? Is this a VirtualBox error?




"	wemido
16145	Music is cutt when resizing iTunes	Windows	VirtualBox 5.1.8	2016-11-03T18:22:30Z	2016-11-03T18:22:30Z	2016-11-03T18:22:30Z	"Hello,
when I resize iTunes 12.5.3 (latest version) in a little windows has the virtualbox, I pause the music and I restart it, the music is cut. As if I put play/pause button in loop.
Also, if I try to listen the radio Beats 1, there is a problem with the audio stream. I have the same problem on Windows 7 and Windows 10. (It's not a iTunes problem because it works with VMware."	CLeBeR
19063	Multiple VBoxSVC processes on Linux host	other	VirtualBox 5.2.32	2019-11-05T10:01:27Z	2019-11-05T10:01:27Z	2019-11-05T10:01:27Z	"Hello,

I use VirtualBox on headless Linux server.

From time to time I get second VBoxSVC process running:
{{{
#: ps aufx | grep VBoxSVC
jenkins   6445  0.0  0.0  14856  1040 pts/0    S+   09:19   0:00              \_ grep VBoxSVC
jenkins  19100  2.2  0.0 1077660 84388 ?       Sl   Oct17 604:18 /usr/lib/virtualbox/VBoxSVC --auto-shutdown
jenkins  27511  1.7  0.0 875548 28544 ?        Sl   Nov04  15:58 /usr/lib/virtualbox/VBoxSVC --auto-shutdown
}}}
I have to kill processes every time I get this issue.
All VBoxHeadless processes always start by user jenkins.
/tmp permissions: drwxrwxrwt  root root
{{{
#: ls -la /tmp/
drwx------  2 jenkins jenkins  4096 Nov  4 18:14 .vbox-jenkins-ipc

#: ls -l /tmp/.vbox-jenkins-ipc/
srwx------ 1 jenkins jenkins 0 Nov  4 18:14 ipcd
-rw------- 1 jenkins jenkins 6 Nov  4 18:14 lock
}}}

User jenkins is in vboxusers group.

Version: 5.2.32r132073.

Host: Ubuntu 18.04.3 LTS"	mgubanov
16775	Multiple snapshots cause inconsistent parent UUID in vdi causing VER_FILE_NOT_FOUND error	Windows	VirtualBox 5.1.22	2017-05-21T16:05:59Z	2017-05-21T16:05:59Z	2017-05-21T16:05:59Z	"'''Problem:'''  Snapshotting and deleting of old snapshots in a running VM results in the retention of a reference to a deleted snapshot, inhibiting the resume of saved state.

Setup and process of snapshotting and snapshot removal:

I have a situation where I need to run a long set of analytics in a guest VM.  I constructed a single base VM that installed all the software and base set of data.  I then created 4 linked clones of that base VM.  In each clone, I then configure the specific parameters of an algorithm.  The execution of each set of analysis is approximately 1 month.

To protect myself from unexpected problems that require a complete restart of the analysis, I began to use snapshots twice a day to capture the current state so if the VM crashed for any reason (e.g. power outage or the host becoming frozen), I have a state that I can revert to and resume, losing at most 12 hours of analysis.

After a couple of days, I decided to clean up a few of the older snapshots (using the UI to remove old snapshots in the order of oldest to newest until I had only one snapshot left and the current state for each clone).

I performed the snapshot operation one each of the running clones and I conducted the snapshot removal against the running clones.  In other words, as the VM was running, I began with the oldest snapshot and used the GUI to do the removal (merge and delete).  All worked well.  The VM continued to run and I was able to take another snapshot and then remove the older snapshot.  However, when I decided to do maintenance to the host, the problem emerged.  

I saved the state of each running clone, conducted my host maintenance (basic patching and rebooted the host).  When I went to restart the 4 clones, each reports that there is a missing snapshot.  The snapshot is the immediate parent which is the snapshot just prior to the current snapshot.  Error message below.


{{{
Error:
Could not open the medium '/home/jpb/VirtualBox VMs/OT-Strat-Dev Clone1/Snapshots/{fe2f4eca-c178-4a2d-9092-8c82d6bab0b0}.vdi'.
VD: error VERR_FILE_NOT_FOUND opening image file '/home/jpb/VirtualBox VMs/OT-Strat-Dev Clone1/Snapshots/{fe2f4eca-c178-4a2d-9092-8c82d6bab0b0}.vdi' (VERR_FILE_NOT_FOUND).


Result Code: 
NS_ERROR_FAILURE (0x80004005)
Component: 
MediumWrap
Interface: 
IMedium {4afe423b-43e0-e9d0-82e8-ceb307940dda}

}}}

The missing snapshot that it cannot find I believe to be the most recently removed snapshot from the running VM prior to saving the state.

I've attached 2 views from the Virtual Media Manager.  View 1 shows the child of Clone1 which represents the current state (I believe).  It also shows its parent ""missing"".  View 2 is the same but I highlighted the ""missing"" snapshot.

The third attachment is from the VBox Manager showing the snapshots for Clone1.

Doing a showmediuminfo command against the lowest level snapshot (current state), it shows that the Parent UUID as the missing snapshot (which was deleted via the GUI after it merged it with the base).
{{{
jpb@explorer:~/VirtualBox VMs/OT-Strat-Dev Clone1/Snapshots$ vboxmanage showmediuminfo f1a42411-6f9a-44ae-be07-00ae7de93f89
UUID:           f1a42411-6f9a-44ae-be07-00ae7de93f89
Parent UUID:    fe2f4eca-c178-4a2d-9092-8c82d6bab0b0
State:          created
Type:           normal (differencing)
Auto-Reset:     off
Location:       /home/jpb/VirtualBox VMs/OT-Strat-Dev Clone1/Snapshots/{f1a42411-6f9a-44ae-be07-00ae7de93f89}.vdi
Storage format: VDI
Format variant: differencing default
Capacity:       81920 MBytes
Size on disk:   678 MBytes
Encryption:     disabled
In use by VMs:  OT-Strat-Dev Clone1 (UUID: 640b91f3-4748-480a-8d8e-51c576201b5e)
}}}


However, when I use the dumphdinfo, I get a different value for the uuidParent - which is actually the higher (and correct) UUID of the surviving and recent snapshot.
{{{
jpb@explorer:~/VirtualBox VMs/OT-Strat-Dev Clone1/Snapshots$ vboxmanage internalcommands dumphdinfo {f1a42411-6f9a-44ae-be07-00ae7de93f89}.vdi
--- Dumping VD Disk, Images=1
Dumping VD image ""{f1a42411-6f9a-44ae-be07-00ae7de93f89}.vdi"" (Backend=VDI)
Dumping VDI image ""{f1a42411-6f9a-44ae-be07-00ae7de93f89}.vdi"" mode=r/o uOpenFlags=9 File=0x00563f4bf61680
Header: Version=00010001 Type=4 Flags=0 Size=85899345920
Header: cbBlock=1048576 cbBlockExtra=0 cBlocks=81920 cBlocksAllocated=676
Header: offBlocks=1048576 offData=2097152
Header: Geometry: C/H/S=1024/255/63 cbSector=512
Header: uuidCreation={f1a42411-6f9a-44ae-be07-00ae7de93f89}
Header: uuidModification={eff43f9a-8441-4e7b-9956-17fad78601a5}
Header: uuidParent={3f80396b-40b9-4c17-aa02-8013bf5a3ea6}
Header: uuidParentModification={44e04488-2274-4b00-92ac-1d0c0a02d180}
Image:  fFlags=00020000 offStartBlocks=1048576 offStartData=2097152
Image:  uBlockMask=000FFFFF cbTotalBlockData=1048576 uShiftOffset2Index=20 offStartBlockData=0

}}}

I haven't found the way to change the uuid that shows up in showmediuminfo to match the uuidParent of the dumphdinfo.  I believe this would resolve my problem and allow me to restore the saved state of my clones.

My snapshot directory also interestingly has multiple saved state files which I assume happens as part of the snapshotting of a running VM since the date and time stamp corresponds to the snapshotting events.  So, these do not look to be cleaned up by the snapshot process.
{{{
jpb@explorer:~/VirtualBox VMs/OT-Strat-Dev Clone1/Snapshots$ ls -l
total 11186860
-rw------- 1 jpb jpb  905360735 May 10 16:03 2017-05-10T21-03-44-944351000Z.sav
-rw------- 1 jpb jpb  872413499 May 20 07:54 2017-05-20T12-53-55-899688000Z.sav
-rw------- 1 jpb jpb  970377870 May 20 17:29 2017-05-20T22-28-49-589899000Z.sav
-rw-r--r-- 1 jpb jpb 7647264768 May 20 07:55 {3f80396b-40b9-4c17-aa02-8013bf5a3ea6}.vdi
-rw------- 1 jpb jpb  352321536 May 17 09:55 {7b0b9120-8a8d-46a1-a82b-fec4448e9b9f}.vdi
-rw------- 1 jpb jpb  710934528 May 20 17:28 {f1a42411-6f9a-44ae-be07-00ae7de93f89}.vdi

}}}




My current option is to revert to the snapshot, discarding the current state and reprocess the work from the last 12 hours.  I'll save clone1 as is incase you need more information.






"	jbrown10
17029	Multiple Instances of VBoxXPCOMIPCD, VBoxSVC, VBoxHeadless	Windows	VirtualBox 5.1.26	2017-08-21T10:24:38Z	2017-08-23T12:18:41Z	2017-08-23T12:18:41Z	"Hello!

After upgrading from debian 8/jessie running virtualbox 5.1.24 to debian 9/stretch and virtualbox 5.1.26, multiple processes (at least two) for a single virtual machine may be started (with two seperate VBoxSVC-processes as their parents).

The commands ""vboxmanage showvminfo"" and also ""vboxmanage list runningvms"" sometimes report a wrong - ""powered off"" or ""aborted"" - state for running and fully functional machines.

Several Win10 and Win8 guests are not able to start anymore due to severe filesystem damages.

The relevant part of ""ps aufx"" looks something like this:

{{{
...
vbox      1788  Sl   /usr/lib/virtualbox/vboxwebsrv --background -F /var/log/vboxweb.log -R 10 -S 1048576 -I 86400
vbox      1800  S    /usr/lib/virtualbox/VBoxXPCOMIPCD
vbox      1809  Sl   /usr/lib/virtualbox/VBoxSVC --auto-shutdown
vbox      3834  Sl   \_ /usr/lib/virtualbox/VBoxHeadless --comment VM221 --startvm 5e5c64e7-...
vbox      4093  Sl   \_ /usr/lib/virtualbox/VBoxHeadless --comment VM320 --startvm cfe3de02-...
vbox      4186  Sl   \_ /usr/lib/virtualbox/VBoxHeadless --comment VM050 --startvm 43d2653e-...
vbox      4187  Sl   \_ /usr/lib/virtualbox/VBoxHeadless --comment VM222 --startvm 6206dddc-...
vbox      4441  Sl   \_ /usr/lib/virtualbox/VBoxHeadless --comment VM223 --startvm 056443b9-...
vbox      4936  Sl   \_ /usr/lib/virtualbox/VBoxHeadless --comment VM057 --startvm 0bd9f77d-...
vbox     18145  Sl   \_ /usr/lib/virtualbox/VBoxHeadless --comment VM322 --startvm 0429d803-...
vbox      2083  Sl   \_ /usr/lib/virtualbox/VBoxHeadless --comment VM321 --startvm 5b36d602-...
...
vbox      2169  S    /usr/lib/virtualbox/VBoxXPCOMIPCD
vbox      2174  Sl   /usr/lib/virtualbox/VBoxSVC --auto-shutdown
vbox      2218  Sl   \_ /usr/lib/virtualbox/VBoxHeadless --comment VM322 --startvm 0429d803-...
...
}}}

in this excerpt ""VM322"" is running as PID 18145 and 2218.

The host system is a DELL PowerEdge T620 server powered by two Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz running Debian 4.9.30-2+deb9u3 (2017-08-06) x86_64 GNU/Linux.
Guests are about 36 machines running MS Windows (Win2000 - Win10).

A downgrade to the virtualbox 5.1.24 deb-package installed in debian ""stretch"" did not solve the problem.

Thanks a lot for any advice!"	mh367
20669	Multicast originating from different subnet does not reach Guest only on Ubuntu(Linux?) Host	Linux	VirtualBox 6.1.28	2021-11-15T17:07:49Z	2021-11-17T19:07:55Z	2021-11-17T19:07:55Z	"Hello,

I have run into an issue that I now believe is a bug.

Basically, I am receiving status updates from various devices on the network in my VM. They use multicast on 224.0.0.50.
The devices are on a different subnet from the Host and the Guest (the host and the guest are on the same subnet), but everyone can communicate between each other just fine.
This works on Host Windows 10 but not on Host Ubuntu 18.04. 
Using Virtualbox 6.1.28. 

Also, tried:
- 6.1.26
- 6.1.29 revision 148164 test build
- 6.1.97 development revision 148162

All the above w/ extpack

The guest is using bridged networking.
On Windows it's using Intel PRO/1000 MT Desktop (82540EM). 
On the Ubuntu host I've tried them all with no luck.
On Windows promiscuous mode is set to Deny and greyed out, on the Ubuntu host I tried enabling it to Allow-All, no luck.

Both hosts receive the multicast packet (used wireshark on windows and tcpdump on linux to verify on both the hosts and the guests), but only on the Windows 10 host will it manage to be picked up by the Guest.
I'm attaching a screenshot from a packet capture from inside the Guest with Windows 10 as a host. These two packets are the expected behavior. On Ubuntu Host, only the first one (the direct reply) makes it all the way to the Guest. The multicast packet is lost.

It is worth mentioning that it's the exact same VM copied from Windows to Linux to make this test as good as possible.

Multicast packets originating from the same subnet are well-received.
I also tried mimicking network routes on the Ubuntu host as seen on the Windows host but to no avail.
I tried nuking the routes on the windows host to see if it affected the Windows Guest receiving it but it did not.
"	idmistir
10190	"MS Flight beta report ""no Shader 3 support"" and close"	Windows	VirtualBox 4.1.8	2012-01-25T13:08:40Z	2014-03-17T03:53:44Z	2014-03-17T03:53:44Z	"I tried to install the new MS Flight beta on WinXP in VB4.1.8
I keep 3D acceleration activated with 128 MB dedicated to VideoRAM.
My Host is Linux Ubuntu 11.10, and the card is a NVidia G104M
The installation work, but on Flight start it detect ""no Shader 3 support"" and close."	Valerio Messina
3883	Moving VM window status bar to the top of the window would save space	other	VirtualBox 2.2.2	2009-04-30T00:05:24Z	2014-12-03T15:23:56Z	2014-12-03T15:23:56Z	Is it possible/feasible to move the status bar icons from the bottom right of VM windows to the right side of the menu bar? That would save space, allowing a larger guest desktop size for a given VM window size.	Donuts
19101	Movie Maker with Windows Vista	Windows	VirtualBox 6.0.14	2019-11-22T00:07:10Z	2019-11-23T00:12:49Z	2019-11-23T00:12:49Z	"Hey!

I need to use the old Windows Movie Maker and therefore I set up a Windows Vista machine.

Issue:
Movie Maker starts fine after some tinkering, but the guest OS crashes if anything is done with the timeline.

Things I did:
- Installed Windows Vista
- Installed all available updates (+ Firefox)
- Installed guest additions 6.0.14 multiple times with different settings, inside and outside of Safe Mode
- Added one shared directory

VM settings:
- 2 GB RAM
- 2 CPU cores
- 3D acceleration enabled
- 2D acceleration enabled
- VBoxSVGA
- 256 MB graphics memory


At first, Movie Maker did not start at all because it needs graphics acceleration. Also, it didn't start when I installed the Guest Additions with regular Direct3D support - dxdiag.exe reported that there was no Direct3D acceleration available.
Installing the Guest Additions with the experimental Aero (WDDM) support failed once in safe mode, but succeeded on the second try.
Movie Maker starts fine now, but as soon as an item is added to the media timeline or moved within it, the Guest OS freezes for a few seconds, then reboots.

Anything I can do to help debug this problem?"	jeinzi
18028	Mouse wheel scrolling usually not working, cursor off, hotkeys not sent to vm, after moving to edge of screen	Linux	VirtualBox 5.1.0	2018-10-03T14:20:07Z	2018-10-03T14:20:07Z	2018-10-03T14:20:07Z	"This is not a new issue but I couldn't find a related bug report that's still open.

I believe the following issues may be related.

A) Mouse wheel scrolling usually doesn't work while ""mouse integration"" is not active (input captured). It always works fine at first, right after clicking or hitting Ctrl in the VM window to capture both mouse and keyboard. At some point, it stops working. Hitting Ctrl to release the mouse reveals that the host's mouse cursor is usually about half a screen away from the VM's cursor. After moving the host's cursor back to where the VM's cursor is and then clicking to recapture the input, it works again. But not for long.
This is happening so often that I tend to not use the mouse wheel at all and use the good old scrollbar buttons instead. Unfortunately, some desktop environments (Gnome/GTK) have lost the scrollbar buttons for whatever reason. In that case, the combination of a temporarily broken scroll wheel *and* a broken scrollbar makes it rather difficult to navigate through content (vertically and horizontally).

B) Whenever a VM is started, mouse integration is active by default, which means the VM's cursor is moved together with the host's cursor as long as it's within the VM window without requiring the user to click into the VM window first.
Unfortunately, the cursor is often way off. Sometimes even a third cursor would fit between the host's and the VM's cursor. I'll attach a screenshot.
This is one of the reasons why I usually disable mouse integration after starting a VM. But then, the first issue happens.

C) While mouse integration is active, hotkeys often don't work, i.e., they're not sent to the VM. For example, after starting a VM, you'd hit Alt + Tab while working inside the VM and you get the host's task switcher showing your open Virtualbox windows. What you actually wanted to do is switch windows inside the VM.
You have to first click somewhere inside the VM and then hit Ctrl to temporarily capture the keyboard and send hotkeys to the VM. I say temporarily because at random times, apparently when moving the cursor to the edge of the screen (but strangely not always), it stops working again and the next time Alt + Tab is used, it's sent to the host again.
This is the main reason why I have to disable mouse integration after starting a VM and then only interact with the VM with mouse and keyboard captured and locked inside the VM window.

D) This is just a minor glitch. I don't remember when I first noticed that but it wasn't always like this. The user interface bar at the top of the screen gets stuck, covering that area in the VM. That's particularly annoying if the DE's panel (task bar) is at the top of the screen. This is solved by moving the host's cursor over the user interface panel and back in the VM, then it disappears normally.

E) This is not a glitch, just a note: When mouse integration is disabled but the input controls are *not* captured (e.g., VM on one monitor, host applications on another monitor), most keystrokes are still sent to the guest system (of course no hotkeys) while the VM window is focused. This may be counterintuitive because not having clicked into the VM window means that the user does not want to interact with it. Accidentally moving the host's mouse to the VM window may change the focus and then hitting space may active a button in the guest instead of inserting a whitespace in a host application window.

If it makes a difference, most VM windows are used in full screen mode. There may be a second or third monitor with other VMs or host application windows running.

Again, I am under the impression that the issues described above may be symptoms of one general issue. It appears that the VM window sometimes loses the input controls while the user is working with the VM or they get ""out of sync"" unexpectedly.

This behavior has been seen on different systems, but most recently on Debian, currently running Virtualbox 5.1.38. Some guest systems are running Fedora 28.

"	basic6
18016	Mouse problem with Win10 1809 guest and two displays	Windows	VirtualBox 5.2.18	2018-09-27T14:32:46Z	2018-12-17T11:33:59Z	2018-12-17T11:33:59Z	"Hi,
using the latest Win10 build causes a problem when using two displays: The cursor is not in place 'where the action is' (sorry, don't have better words to describe it). There is kind of an offset that gets larger the more I move the mouse to the right. You point the mouse to a desktop icon, and another icon to the right gets highlighted. Happened after updating the guest to Win10 1809. With one display all is fine.
Host: Laptop with core-i5, two additional 1080p-displays (VGA and HDMI), Mageia Linux 6 (64bit), VBox 5.2.18, kernel 4.14.70
Guest: Windows 10 Version 1809 build 17763.1, 64bit"	Squonk
9271	Mouse pointer Issues in graphics applications	Windows	VirtualBox 4.1.0	2011-07-22T07:42:56Z	2011-07-22T07:42:56Z	2011-07-22T07:42:56Z	"I have tested on three systems running Ubuntu 11.04 with unity.  P4 with Nvidia, Core 2 with Intel graphics and AMD with ATI graphics.  Problem is the same regardless of host 32bit or 64bit OS.  Virtualbox is 4.1.0

Problem is with 32bit Win XP SP3 guest - when 4.1 additions are installed mouse pointer seems ""inaccurate"" resulting in difficulties to manipulate objects in graphics packages.  Downgrading guest additions to 4.0.12 resolves the problem.

Problem is easily repeated with CorelDraw 11.  1 create a square object, 2 convert object to curves, 3 with the ""pick"" tool selected move mouse over each of the four nodes.  Correct behavior is that as mouse is over a node tool should change from pick to node edit however with additions 4.1.0 this is erratic and often never happens at all.  Other less consistent problems are also occurring, for example on complex graphics it is sometimes impossible to select an object.  Again this problem only manifests when additions 4.1.0 are installed on the guest.

I have tried disabling both 2d and 3d acceleration but this did not resolve the problem.  I expect this bug will cause problems in other applications too where manipulation of graphics is needed.
"	Mark
16380	Mouse pointer disappears after VM resume	Linux	VirtualBox 5.1.12	2017-01-12T09:55:03Z	2018-12-11T20:44:10Z	2018-12-11T20:44:10Z	"When I resume my Linux VM, the mouse cursor is never visible when moved into the VM window.

The mouse appears to be working correctly, as I can see icons / menus become ""highlighted"" when I move the mouse around.

And mouse clicks also work as expected.

It's just that the cursor itself is invisible !!

This issue is never present when starting the VM from scratch.[[br]]
It *only* happens when starting from a suspend.

Host : Ubuntu 16.04.1 LTS (64bit)[[br]]
Guest : Ubuntu 16.04.1 LTS (64bit)

Both host and guest are fully up-to-date."	mpfj
19908	Mouse not working in Virtualbox 6.1.14 with Arch Linux as Host	Linux	VirtualBox 6.1.14	2020-09-22T14:38:36Z	2021-03-24T19:25:54Z	2021-03-24T19:25:54Z	"I installed Kali Linux as Guest OS while the Host OS is Arch Linux. Whenever I go to Full-screen mode and return back to normal screen mode, the Mouse/Touchpad click is not working. I can move the cursor, but cannot click/tap or scroll through anything in both Guest OS (Kali) and Host OS (Arch).

Steps to Reproduce:
1. Install Kali Linux as Guest and fully update the Guest OS.
2. Reboot the VM.
3. Switch to full screen mode with Host+F.
4. Again, switch to normal screen mode with Host+F.
5. Now, the mouse/touchpad stops working except moving the cursor in both Host(Arch) and Guest(Kali) OSs

This steps to reproduce fail rarely, but I can assure you it happens randomly each time when you stat up the VM and surf a bit.

When I shutdown my Guest(Kali) VM, then the mouse/touchpad operates normally as before.

My Laptop Specs:
Lenovo L340-15IWL
Intel i5-8265U
8GB DDR4 RAM
Intel UHD Graphics 620"	404_vip_not_found
19923	Mouse Middle-Scroll Click aborts Linux guest	Linux	VirtualBox 6.1.10	2020-09-28T00:50:08Z	2020-09-30T06:32:13Z	2020-09-30T06:32:13Z	"On Linux host 20.04.1, using linux guest 20.04 
At random occurrence when I middle click or scrollwheel click (to open multiple tabs in firefox) the guest machine immediately aborts. Shows (Aborted) within Vbox machine list window

I think this has occured before years ago and needed some upgrade. I am unable to search the bugs or forum as I kept getting error mesages ""Unable to search at this time. Please check back in several minutes""
"	FleddyFlinty
19205	Mouse loses focus when enabling second virtual screen	Windows	VirtualBox 6.1.0	2020-01-07T09:39:43Z	2020-01-15T14:59:28Z	2020-01-15T14:59:28Z	"I have created a Windows 10 1909 guest running Virtualbox 6.1.0 r135406 guest additions with two virtual screens on an Ubuntu 18.04 (4.15.0-74-generic) host running Virtualbox 6.1.0 r135406. The mouse loses focus when you enable the second virtual screen: if you choose 'Extend these displays' from Display settings you cannot click on 'Keep changes'. The mouse pointer seems to get offset, you can click on the Start Menu in the first virtual screen but when you hover over the Start menu items the mouse pointer is offset: the Calculator gets highlighted but the mouse pointer is shown above it. When you 'click on' the Calculator while it is highlighted it launches. You can move the mouse to the second virtual screen but nothing happens when you click anywhere.

Regards,
GW"	gwiesenekker
18644	mouse doesn't work in new version	Windows	VirtualBox 6.0.6	2019-05-15T09:39:45Z	2019-05-21T16:21:46Z	2019-05-21T16:21:46Z	"Hello
When I use a [java] robot to do something repetitive for me, mouse doesn't work when I'm not in virtual machine. sometimes I need to do something like that and I open few virtual machine in same time, but in new version it doesn't work anymore.
also sometimes, when I focus on virtual machine, right click occurs automatically and it bothers me.
both of them don't exist in previous versions. 

Thank you

Version 6.0.6_Debian r129722
I just installed it from repository and it was newest version."	Java
13509	Mouse does not work in full screen mode (HOST+F)	Windows	VirtualBox 4.3.18	2014-10-14T13:18:33Z	2014-10-14T14:06:13Z	2014-10-14T14:06:13Z	"When going to full screen mode (HOST+F) on Linux, using Windows, the mouse is unusable (mouse moves around, but you cannot click on anything... keyboard still works).  When leaving full screen mode (HOST+F) part of the Linux UI is covered by something left over by Virtual Box (force closing Virtual box seems to be the only way to get Linux Desktop usable again).

For more on this, view the forum message:
https://forums.virtualbox.org/viewtopic.php?f=2&t=63740&p=301543#p301543

My System
Host: Ubuntu 14.04 64bit
Guest: Windows 8.1 64bit"	darthjdc
8969	Mouse clicks move mouse pointer, and mouse not properly captured	Windows	VirtualBox 4.0.8	2011-05-26T15:54:35Z	2011-05-27T20:39:30Z	2011-05-27T20:39:30Z	"Running VirtualBox 4.0.8 (32 bit) on Fedora 14 (32 bit) with guest Windows XP SP3 (32 bit, 1024x768). The host has a single display (1280x1024), PS/2 mouse, window manager is fvwm2. Everything was fine about 3 months ago (IIRC that was with VBox 4.0.4).

Started Windows XP today, and as soon as I hit the left mouse button for the first time, the mouse goes nuts. On each click, the mouse pointer is relocated on the screen (makes double-clicks impossible). Mouse movements do not properly end on the edge of the screen but just in the middle of the movement the guest mouse pointer is relocated and mouse control is back under Linux control (a little bit like the Host Key has been pressed during the movement; changing it doesn't help).

Guest additions are not installed (so there's no special mouse integration). It's a standard setup.

I've also moved the old installation out of the way, removed the VirtualBox package, reinstalled it and made a Windows XP (SP2) install from scratch. Same behaviour.

It doesn't look like this is Windows' fault, because it happens with a clean Windows XP SP2 as well as a fully patched and customized Windows XP SP3. Looks like VirtualBox and Linux (Fedora) no longer work well with each other. Fedora is fully patched.

I've also tried a USB mouse (just in case VirtualBox has problems with PS/2), but that didn't change anything. It doesn't look like a hardware fault because everything is recognized and basically works.

Same problem with different screen resolutions within the guest system.

I'm wondering that simple mouse movement can cause the mouse to be no longer captered by the guest system. That should be impossible without the Guest Additions.

I'll append a VBox.log but there are not errors in it.
"	Andreas M. Kirchwitz
20386	Mouse click stops working on host/guest due to window focusOutEvent problem in Qt GUI	Windows	VirtualBox 6.1.22	2021-06-03T13:33:07Z	2022-08-03T03:01:09Z	2022-08-03T03:01:09Z	"https://forums.virtualbox.org/viewtopic.php?f=7&t=102798

Here's a cut & paste of problem description:

Mouse click stops working on host/guest due to window focusOutEvent problem in Qt GUI

Postby Cryptkeeper » 7. May 2021, 17:37
Hi,

for more than two years now (so probably since VB version 6.0 or so) from time to time I am affected by a very anoying bug. Then mouse clicks stops working on the host and the guest as well. I can still move the mouse pointer but clicks are not recognized anymore. The only solution then is to shut down *all* running guest instances. Then the mouse clicks starts working again.

I am sure it is not a drag and drop problem like in https://www.virtualbox.org/ticket/14743

There will be no entry in the logs, when the bug occurs. It happend very randomly to me but after a while with a screen record I figured out the following steps to reliable reproduce the bug:

1) Click on the taskbar to restore VM window from minimized state
2) Press down the mouse button on the taskbar and keep it pressed
3) Release the mouse button and immediatly press it again
4) Now no further clicks are registered until VM is shut down

(I agree that this looks like a very special and rare circumstance - however I think that this bug is a race condition and as I often switch between different windows with the taskbar I'm hit by it very often.)

Here is a screencast of the bug as GIF: https://s3.gifyu.com/images/vbox-bug.gif

When the bug occurs *xprop* on the hosts exits with the error ""xprop: error: Can't grab the mouse"" - on the guest it just hangs as no click is registered. Also the bug only occurs with the Qt front end of VirtualBox - with the SDL front end I couldn't reproduce the error.

From the steps I assume that the bug is kind of a race condition on the minimize respectively focus out / focus in event of the window. So I tried to build VirtualBox from source and try to trace the bug. And indeed I figured out, that the bug does not occure if I comment out the following 3 lines in the file src/VBox/Frontends/VirtualBox/src/runtime/UIMachineView.cpp.

Code: Select all   Expand view
    void UIMachineView::focusOutEvent(QFocusEvent *pEvent)
    {
        /* If native event filter exists: */
        if (m_pNativeEventFilter)
        {
            /* Uninstall/destroy existing native event filter: */
               
            //qApp->removeNativeEventFilter(m_pNativeEventFilter);
            //delete m_pNativeEventFilter;
            //m_pNativeEventFilter = 0;
        }

        /* Call to base-class: */
        QAbstractScrollArea::focusOutEvent(pEvent);
    }



I tried to dig deeper but I'm kind of stuck. Because I don't know what this native event filter is used for and why it is destroyed on focus out event.

Can anyone help me to debug this further?

Thanks a lot!"	Seann
20775	Mouse click doesn't work in window for choice iso	other	VirtualBox 6.1.32	2022-01-19T09:18:22Z	2022-04-22T10:23:49Z	2022-04-22T10:23:49Z	"My OS is Debian 11 with KDE Plasma
When I try to select iso in virtual machine settings, mouse left button click doesn't work. But the keyboard in this dialog works"	blbulyandavbulyan
19594	Mouse behaves badly with two screens Guest Additions 6.1.8	Linux	VirtualBox 6.1.8	2020-05-17T17:28:43Z	2020-06-11T15:04:39Z	2020-06-11T15:04:39Z	"My configuration is 
Host: Debian Stretch
Guests: Debian Buster (two screens), Debian Buster (one screen), Ubuntu Focal Fossa Server
Desktop: Gnome classic on host and guests (including Ubuntu server)

When I upgraded from 6.1.6 to 6.1.8 (including an upgrade of the guest additions) the mouse did not behave correctly on the guests with two screens and the secondary screen stays black even though the window for the second screen opens. When I move the mouse over a widget and click, it sometimes does nothing and sometimes activates a different window. Downgrading to VBox 6.0 and installing the 6.0 guest additions fixed the problem.

I recall having a similar or perhaps exactly the same problem with my two screen guests in an earlier upgrade of VBox (I don't remember the versions involved). I think there was a bug report in that previous case as well."	linux_user_1
20499	mouse and keyboard stop working after a few seconds	Windows	VirtualBox 6.1.24	2021-08-12T08:23:44Z	2021-12-08T17:08:17Z	2021-12-08T17:08:17Z	"Host: Debian 10, 64 bit, custom 5.10.x kernel
Guests: Win 7 Pro 32 bit, Win 10 Pro 64 bit, possibly other versions too
Affected VirtualBox versions: 6.1.24 and 6.1.26

After powering on a windows VM the VM stops reacting to mouse clicks or keyboard input. With Guest Additions installed the mouse pointer still moves. The VirtualBox app window won't refresh. I have to destroy the VM window to resume normal operation. When I start the Windows VM in safe mode mouse and keyboard work fine. Another observation is that the Remote Display is affected too (RDP client connects, changes size to VM's resolution, but black window) and works only when VM is started in safe mode. A downgrade of VirtualBox 6.1.22 resolves all issues."	madires
13568	"mount vboxsf won't accept option ""user"""	Linux	VirtualBox 4.3.18	2014-10-29T12:30:33Z	2014-11-02T20:32:51Z	2014-11-02T20:32:51Z	"Even though the vbox shared folders can be mounted through mount(8) and a usual /etc/fstab entry can be created, some options accepted by mount won't work for vboxsf, e.g. ""user"" and ""group"".

{{{
juanlu@minted ~ $ tail /etc/fstab
# mint shared folder
mint /media/sf_mint vboxsf defaults,user,uid=1000,gid=999 0 0
juanlu@minted ~ $ mount mint
Only root can mount shared folders from the host.
juanlu@minted ~ $ sudo !!
sudo mount mint
unknown mount option `user'
valid options:
  rw         mount read write (default)
  ro         mount read only
  uid       =<arg> default file owner user id
  gid       =<arg> default file owner group id
  ttl       =<arg> time to live for dentry
  iocharset =<arg> i/o charset (default utf8)
  convertcp =<arg> convert share name from given charset to utf8
  dmode     =<arg> mode of all directories
  fmode     =<arg> mode of all regular files
  umask     =<arg> umask of directories and regular files
  dmask     =<arg> umask of directories
  fmask     =<arg> umask of regular files
}}}

This might be just a non-implemented feature in mount.vboxsf.c. If it's not, then probably a clarification is needed in the user manual that not all mount(8) options are allowed for vboxsf, and in that case it would be nice to have a rationale of why is that.
 "	juanlu001
9103	modifyvm --resize doesn't work with snapshots	other	VirtualBox 4.0.8	2011-06-24T10:27:29Z	2017-09-13T14:31:41Z	2017-09-13T14:31:41Z	"I have a 20GB dynamic .vdi which I want to resize to 40GB so I issue:

VBoxManage modifyhd /full/path/to/hd.vdi --resize 40960

and it responds (instantly) with:

0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%

Running VBoxManage showhdinfo on the image tells me:

...
Logical size:         40960 MBytes
Current size on disk: 18464 MBytes
Type:                 normal (base)
Storage format:       VDI
Format variant:       dynamic default
...

and also reports the same logical size for the snapshot files.

The problem is that gparted reports that the drive is still 20G (not the partition; the whole drive).

Windows disk management also sees the drive as 20G.

It looks like while VirtualBox can see the new logical size, it's not reporting it to the guest correctly."	jonsiddle
16005	Missing newline(s) in VBManager VM Description	all	VirtualBox 5.1.6	2016-09-30T10:07:24Z	2016-09-30T10:28:35Z	2016-09-30T10:28:35Z	"Hello!
There is small problem with Debian GNU/Linux 8 amd64 with Oracle VM VirtualBox Manager v5.1.6 from Oracle repository, but probably problem exist for all platforms.

Reproduce steps:
create any virtual machine in VM Manager, Ctrl-S on it, General -> Description, then enter a few lines with newline between them, press OK.

When user clicks on the machine Details -> Descriptions all lines are displayed together, missing new line.

Here is screenshot attached with problem."	maestro
10504	Missing case-insensitivity for certain filenames for Windows 7 guests	Windows	VirtualBox 4.1.12	2012-05-02T13:16:10Z	2012-05-02T13:16:10Z	2012-05-02T13:16:10Z	"Use a Windows 7 64-bit guest on VirtualBox 4.1.2 on Linux 64-bit hosts.
Mount a VirtualBox-Filesystem share.
Open a ""cmd"" box and change the current directory into a directory in this share.
Execute following script:

{{{
mkdir test
mkdir test\Client
mkdir test\Client\a
mkdir test\Client\a\b
dir test\client\a
dir test\Client\a
}}}

What is expected that ""test\client\a"" should be accessible. What is actually observed is that ""test\client\a"" is not accessible. However, ""test\Client\a"" is accessible.

Running apps which access VirtualBox-shares is therefore quite restricted.


"	xbaldauf
21429	MiniToolbar not showing when in fullscreen	all	VirtualBox-7.0.6	2023-01-23T04:23:37Z	2023-01-23T04:23:37Z	2023-01-23T04:23:37Z	When I upgraded from VirtualBox 7.0.4 to 7.0.6, the mini toolbar stopped showing at the top of the screen. It doesn't matter whether I already installed the operating system or just running it, it does not want to show when I start the operating system. The only work around that I know about is to do the host-f to get out of fullscreen and then host-f again to make the mini toolbar show. It does not matter whether it is FreeDOS, A Linux guest OS, or Windows, the mini toolbar will not show when I first start the OS. My host OS is Ubuntu Cinnamon 22.04 LTS. 	soldier4messiah
14411	mini-toolbar is missing when guest VM is set to full screen.	Windows	VirtualBox 5.0.0	2015-08-06T21:05:46Z	2017-06-20T00:54:09Z	2017-06-20T00:54:09Z	"Both the mini-tool bar and bottom bar are unavailable when the guest VM is set to full screen. I have tested on both Ubuntu 15.04 and a Windows 7 64-bit professional guests.

I tried resinstalling the guest additions and rebooting but this did not fix the issue. I have also tried removing the option for 3d acceleration from both guests and rebooting but the same problem persists. Virtualbox extensions are also installed.

Host details:

Linux computer1 4.1.4-1-ARCH #1 SMP PREEMPT Mon Aug 3 21:30:37 UTC 2015 x86_64 GNU/Linux
GNOME Shell 3.16.3
Virtualbox version 5.0.0_OSE r101573

Cycling into and out of fullscreen using Ctrl+F does not restore the mini-toolbar. It is important to note that the mini-tool bar does appear in seemless mode.

Ctrl+home key brings up an alternate mini-toolbar menu which is a workaround until this bug is fixed.

There have been others who reported similar issues with the mini-toolbar ranging back 10 months to 3 years ago but no fix was provided. 

Reference:

https://www.virtualbox.org/ticket/9775
https://www.virtualbox.org/ticket/10599
"	Nelson Pereira
16355	Mini ToolBar on different monitor than virtual machine window	Windows	VirtualBox 5.1.12	2017-01-05T09:19:15Z	2018-06-05T13:27:28Z	2018-06-05T13:27:28Z	"Host: Linux Mint 18.1 Mate, 2 monitors
Guest: Windows 10

Mini ToolBar shows up on different (primary) monitor, whereas virtual machine window starts in its remembered position on secondary monitor. When the machine is minimized and maximized Mini ToolBar moves to correct screen. This is not remembered after virtual machine is stopped and started."	morvael
15811	Mini toolbar hides itself after you click on a menu header	all	VirtualBox 5.1.4	2016-08-17T13:43:40Z	2016-08-17T13:43:40Z	2016-08-17T13:43:40Z	"Lubuntu 16.04 x86-64 host. This issue seems to apply to all guest OSes.

I have configured guest VMs to show the mini toolbar at the top of the screen when in full-screen mode. If you mouse over the hidden toolbar it appears. On clicking a menu header, the menu appears but the toolbar then hides itself after a second or two. I think the toolbar should remain shown until either the user selects a menu item or clicks away from the menu."	Donuts
16965	Mini Toolbar hidden in full screen mode in 5.1.26	Windows	VirtualBox 5.1.26	2017-07-31T20:24:17Z	2017-10-26T12:06:29Z	2017-10-26T12:06:29Z	VB 5.1.26, Linux host, Windows 10 guest.  After upgrading from 5.1.24 to 5.1.26 the mini-toolbar no longer appears when I mouse-over the top of the screen in full-screen mode.  host-home does bring up the menu.	Don Hughes
18817	Mini toolbar display corruption	Windows	VirtualBox 6.0.10	2019-08-07T07:49:07Z	2019-08-07T07:49:07Z	2019-08-07T07:49:07Z	"Using a Dell XPS13 (2018) with a second full HD monitor (1920x1080) the mini toolbar display becomes corrupted (see attached image).
The menu items do not line up with the display although they all work by a trial-and-error method.
"	Smot
14912	Microsoft RD Client on iOS - keyboard not working	Linux	VirtualBox 5.0.10	2015-12-09T01:44:02Z	2015-12-09T01:44:02Z	2015-12-09T01:44:02Z	"I am running 5.0.10 Virtualbox on Intel Atom, with 2GBRAM. Latest Guest Extension Pack. I have a Ubuntu 14.4.3LTS guest, latest kernel, 5.0.10 Guest additions. I have configured the guest to share a desktop via VRDE. The gust runs in console mode. When connecting to the guest with Microsoft's official  RD Client software for IOS (either iPad or iPhone), the only key that appears to work on the keyboard is ENTER. That produces a line as expected. Nothing else seems to work. I noticed on log in ""Numlock Enabled"" shows up. I have seen the same problem with a Virtual OpenWRT instance which does not run any guest extensions so it does not seem isolated to just Ubuntu."	Bruksee
16932	Microsoft Office unusable in version 5.1.24, was working in 5.1.22 fairly well, not perfect though	Windows	VirtualBox 5.1.24	2017-07-21T16:35:05Z	2017-11-08T04:52:07Z	2017-11-08T04:52:07Z	"After installing the latest VBox (5.1.24) the guest becomes unusable when Microsoft Office is running. It becomes completely unresponsive. The clock (showing seconds) no longer advances by 1 second, instead it jumps every few seconds showing that the VM is hung most of the time. The guest window even darkens periodically showing that the host detects it as unresponsive.[[BR]]

For some applications, it's enough to open it without loading anything (Word 2016 or Excel 2016 for example). The older versions (i.e. Word 2013 or Excel 2013) can be opened, but if a document is loaded, or in the case of Excel if any single cell (or a range of cells)  is copied to the clipboard, the guest becomes pretty much locked. It is possible with persistent clicks on the close button to terminate MS Office application and regain guest responsiveness, but this usually takes minutes as the VM pretty much doesn't respond for most of the time.[[BR]]

I have reverted to 5.1.22 and the problem went away proving it's a regression in 5.1.24.
"	Rafcio
20115	Microsoft Office hangs when opening a file in a network share	Windows	VirtualBox 6.1.16	2021-01-03T18:52:18Z	2021-01-07T07:44:09Z	2021-01-07T07:44:09Z	"Microsoft Office hangs when opening a .docx file in a network share.

Deactivating 3d acceleration does not solve the problem.

May be relate to [https://www.virtualbox.org/ticket/15513 this] although I am able to open the file, it hangs when I scroll it down.

VirtualBox Version 6.1.16 r140961 (Qt5.14.2)

'''HOST:'''

{{{
Operating System: Kubuntu 20.10
KDE Plasma Version: 5.19.5
KDE Frameworks Version: 5.74.0
Qt Version: 5.14.2
Kernel Version: 5.8.0-33-generic
OS Type: 64-bit
Processors: 12 × Intel® Core™ i7-8750H CPU @ 2.20GHz
Memory: 15,5 GiB of RAM
Graphics Processor: GeForce GTX 1060/PCIe/SSE2
}}}

'''GUEST:'''

{{{
Edition	Windows 10 Education
Version	20H2
Installed on	‎12/‎6/‎2020
OS build	19042.685
Experience	Windows Feature Experience Pack 120.2212.551.0
}}}
"	JohnJane
6418	Microsoft NetworkLoadBalance unicast mode can't work on VirtualBox3.1.4(Linux version)	Windows	VirtualBox 3.1.4	2010-03-25T03:14:41Z	2010-03-26T02:25:15Z	2010-03-26T02:25:15Z	"I use VB-3.1.4 to test the WIN2003 Network Load Balance, but I find it can't work on unicast mode, while the multi-cast mode can work fine. I tested the WIN2003 with the same configuration for unicast mode on vmware, and it works. I search the bug report for it, but there is no help. Is there some bugs on VB?

BTW: I use virtual box with non-root account.
"	dwei
16191	Microphone not detecting any sound: Windows guest, Linux host	Windows	VirtualBox 5.1.6	2016-11-17T00:22:01Z	2016-12-02T17:45:20Z	2016-12-02T17:45:20Z	"Host: Ubuntu 16.10 64-bit, 4.8.0-27-generic

Host audio controller: PulseAudio

Guest: Windows 7 32-bit

Guest audio controller: ICH 97 (Sound Blaster 16 not detected by guest, with Intel HD Audio guest does not detect any capturing device)

Microphone is correctly enumerated by the guest, but it never detects any sound from the host. On occasions the device shows as ""unavailable"" in the guest.

The logs show that the capture device is being correctly recognized.

Additional information:

* Problem symptoms seem similar to the ones reported #15802, which is marked as closed.
* Problem shows in official VirtualBox package for Ubuntu 16.10, version is 5.1.6_Ubuntu r110634 (using matching extension pack & Guest additions)
* Problem persists in virtualbox-5.1_5.1.8-111374~Ubuntu~yakkety_amd64.deb
* It used to work correctly in the official package for Ubuntu 16.04: virtualbox-5.0.24-dfsg-0ubuntu1.16.04.1
* These users seem to be affected by the same problem: https://forums.virtualbox.org/viewtopic.php?f=7&t=78797
"	trifon
19689	Microphone does not work when going from version VirtualBox 5 to 6	Windows	VirtualBox 6.1.10	2020-06-29T16:38:37Z	2021-06-01T08:29:46Z	2021-06-01T08:29:46Z	"The microphone does not work on any of the guest systems.
I have ubuntu 20.04 host, VirtualBox 6.1.10 r138449 (Qt5.12.8). The microphone works in hosts, but it doesn't work on any of the guests: Windows 10 and ubuntu 20.04.

VirtualBox Audio Configuration: 
Host Controller: Pulseaudio
Controller: Audio Intel HD

When I used version 5 of virtualbox everything worked perfectly."	Abate Bus
15246	Menus not displayed when using multiple monitors	all	VirtualBox 5.0.16	2016-03-16T11:06:10Z	2016-03-16T11:06:10Z	2016-03-16T11:06:10Z	"When multiple monitors are connected to my Linux desktop, menus in VirtualBox are not displayed.

When clicking a menu in the menu bar, or right clicking a VM, no menu appears.

I have tried launching the GUI from the command line, including setting VBOX_GUI_DBG_ENABLED=true and VBOX_GUI_DBG_AUTO_SHOW=true. However, no terminal output is displayed when clicking a menu.

GNOME 3.18.2 on Arch Linux
Intel graphics card with i965 driver, kernel 4.4.0
VirtualBox 5.0.16
"	Rainmaker
18201	Menues detached from top bar in UI	all	VirtualBox 6.0.0	2018-12-18T23:18:44Z	2018-12-18T23:18:44Z	2018-12-18T23:18:44Z	"I'm on a three monitor setup, one 1920x1080, and two 1900x1200. Gnome on Oracle Linux 7.5. 

On the higher resolution screens, the menubar elements attached to guest machines ('File Machine View Input...') are detached from the top bar. 
"	ronabop
18414	Menu bar very small on portrait screen	other	VirtualBox 6.0.4	2019-02-06T06:51:02Z	2019-02-07T00:02:25Z	2019-02-07T00:02:25Z	"When I have a VM on my portrait screen with 6.0.4, it's menu bar is tiny.  This isn't a hidpi screen or anything fancy.  When I drag it back to the other landscape screen, the menu bar looks ""normal"".

I've attached a screenshot"	iwienand
19595	memtest86 8.3 freezes	other	VirtualBox 6.1.8	2020-05-17T19:04:41Z	2022-10-21T13:02:22Z	2022-10-21T13:02:22Z	"https://www.memtest86.com/download.htm

doesn't work in VirtualBox 6.1.8 - it freezes on start on 

Retrieving CPU MSR data...

I've tried playing with various VBox settings - nothing helps."	Artem S. Tashkinov
12279	Memory leak: VBoxService.exe slowly eats up RAM	Windows	VirtualBox 4.3.0	2013-11-01T01:34:35Z	2020-03-05T12:48:08Z	2020-03-05T12:48:08Z	"version 4.3
host: Ubuntu 10.04 x64
guest: windows xp sp3 with VB addition ver 4.3, running in headless

the VBoxService.exe  starts leaking memory once the VM is login through remote desktop (mstsc, not vrdp). If the VM is not running in headless mode, no leaking.

the fixed in https://www.virtualbox.org/ticket/12072 seems not working here
this ticket is  https://www.virtualbox.org/ticket/10970 , however, seems yet to be fixed.



"	maxchen
18693	Memory Leak in VirtualBox 6.0.8	Linux	VirtualBox 6.0.8	2019-06-07T00:05:41Z	2019-06-08T07:34:02Z	2019-06-08T07:34:02Z	"Hello,

It seems like there's a memory leak in VirtualBox 6.0.8.

I'm running with a Linux host (Ubuntu 16.04) and a single Linux guest (Ubuntu 16.04) in headless mode, being accessed by another machine on the network via Virtualbox's RDP server.

What I see is that the ""VBoxHeadless"" process consumes more and more memory as time goes on, at a rate of about 100 MiB every few minutes. This continues indefinitely until the system runs out of memory.

The only thing running on the guest is an instance of Firefox with some web-based FB game.

I've attached the log and vbox file. Please let me know if there's anything else needed.

As of now, the system is up and running, consuming more and more memory.

Thanks,
Jake"	unklejoe
20280	Memory Leak in vboxdrv	Linux	VirtualBox 6.1.18	2021-03-30T17:30:41Z	2021-05-11T12:22:45Z	2021-05-11T12:22:45Z	"I detected a small memory leak in the openSUSE version that I maintain. To see if the problem had been fixed, I installed test build revision 143492. It has the same problem.

The kmemleak report is as follows:


{{{

localhost:cat > /sys/kernel/debug/kmemleak
unreferenced object 0xffff88827c95b380 (size 128):
  comm ""EMT-0"", pid 4550, jiffies 4294918407 (age 94.516s)
  hex dump (first 32 bytes):
    19 01 09 18 01 00 00 80 58 00 00 00 58 00 00 00  ........X...X...
    10 12 61 19 58 00 00 00 08 00 00 00 00 00 00 00  ..a.X...........
  backtrace:
    [<000000008fe681f2>] rtR0MemAllocEx+0xc5/0x130 [vboxdrv]
    [<00000000064e6217>] VBoxHost_RTMemAllocZTag+0x2a/0x70 [vboxdrv]
    [<00000000523d21fa>] rtR0MemObjNew+0x37/0x70 [vboxdrv]
    [<00000000df0eec39>] rtR0MemObjNativeMapKernel+0x57/0x140 [vboxdrv]
    [<000000008419dc13>] VBoxHost_RTR0MemObjMapKernelExTag+0x12d/0x1f0 [vboxdrv]
    [<00000000ec3fe3f7>] SUPR0PageMapKernel+0x1e2/0x270 [vboxdrv]
unreferenced object 0xffff88827c95b600 (size 128):
  comm ""EMT-0"", pid 4550, jiffies 4294918412 (age 94.496s)
  hex dump (first 32 bytes):
    19 01 09 18 01 00 00 80 58 00 00 00 58 00 00 00  ........X...X...
    10 12 61 19 58 00 00 00 08 00 00 00 00 00 00 00  ..a.X...........
  backtrace:
    [<000000008fe681f2>] rtR0MemAllocEx+0xc5/0x130 [vboxdrv]
    [<00000000064e6217>] VBoxHost_RTMemAllocZTag+0x2a/0x70 [vboxdrv]
    [<00000000523d21fa>] rtR0MemObjNew+0x37/0x70 [vboxdrv]
    [<00000000df0eec39>] rtR0MemObjNativeMapKernel+0x57/0x140 [vboxdrv]
    [<000000008419dc13>] VBoxHost_RTR0MemObjMapKernelExTag+0x12d/0x1f0 [vboxdrv]
    [<00000000ec3fe3f7>] SUPR0PageMapKernel+0x1e2/0x270 [vboxdrv]
unreferenced object 0xffff88827c95b680 (size 128):
  comm ""EMT-0"", pid 4550, jiffies 4294918412 (age 94.496s)
  hex dump (first 32 bytes):
    19 01 09 18 01 00 00 80 58 00 00 00 58 00 00 00  ........X...X...
    10 12 61 19 58 00 00 00 08 00 00 00 00 00 00 00  ..a.X...........
  backtrace:
    [<000000008fe681f2>] rtR0MemAllocEx+0xc5/0x130 [vboxdrv]
    [<00000000064e6217>] VBoxHost_RTMemAllocZTag+0x2a/0x70 [vboxdrv]
    [<00000000523d21fa>] rtR0MemObjNew+0x37/0x70 [vboxdrv]
    [<00000000df0eec39>] rtR0MemObjNativeMapKernel+0x57/0x140 [vboxdrv]
    [<000000008419dc13>] VBoxHost_RTR0MemObjMapKernelExTag+0x12d/0x1f0 [vboxdrv]
    [<00000000ec3fe3f7>] SUPR0PageMapKernel+0x1e2/0x270 [vboxdrv]
localhost:~ # 
}}}

To trigger this leak, load the GUI, start and stop a VM, and then close the GUI. Until the final step, the kmemleak scan is clean. Note, this is a real leak. If vboxdrv is unloaded, the backtrace info is lost. The first leaked block is reported as:

{{{
unreferenced object 0xffff88827c95b380 (size 128):
  comm ""EMT-0"", pid 4550, jiffies 4294918407 (age 1095.172s)
  hex dump (first 32 bytes):
    19 01 09 18 01 00 00 80 58 00 00 00 58 00 00 00  ........X...X...
    10 12 61 19 58 00 00 00 08 00 00 00 00 00 00 00  ..a.X...........
  backtrace:
    [<000000008fe681f2>] 0xffffffffa0c9fb05
    [<00000000064e6217>] 0xffffffffa0c9d82a
    [<00000000523d21fa>] 0xffffffffa0c9edd7
    [<00000000df0eec39>] 0xffffffffa0ca1067
    [<000000008419dc13>] 0xffffffffa0c9e55d
    [<00000000ec3fe3f7>] 0xffffffffa0c8c1b2

}}}

"	Larry Finger
11857	"medium type ""dvddrive"" cannot be used via a readonly iscsi target"	all	VirtualBox 4.2.12	2013-06-12T14:11:49Z	2020-01-21T21:23:06Z	2020-01-21T21:23:06Z	"ISO mediums exposed in a {{{dvddrive}}} cannot be used over iSCSI when the target is readonly.

According to [http://www.virtualbox.org/manual/ch05.html#hdimagewrites documentation], CD/DVD images are created read-only, but this doesn't seem to be the case, at least with iSCSI.  I need access to a series of readonly iscsi targets that are exposing ISOs, but this does not seem possible unless I start snapshotting guests after the medium is added, and before it is turned on.


A sample target I am trying to connect to
{{{
ryan@TehDualLinux:~$ sudo tgtadm --lld iscsi --mode target --op show
Target 2: iqn.2001-04.com.TehDualLinux-2260f94a-90f3-4147-9e32-39c773f7095b
    System information:
        Driver: iscsi
        State: ready
    I_T nexus information:
    LUN information:
        LUN: 0
            Type: controller
            SCSI ID: IET     00020000
            SCSI SN: beaf20
            Size: 0 MB, Block size: 1
            Online: Yes
            Removable media: No
            Readonly: No
            Backing store type: null
            Backing store path: None
            Backing store flags: 
        LUN: 1
            Type: disk
            SCSI ID: IET     00020001
            SCSI SN: beaf21
            Size: 1013 MB, Block size: 512
            Online: Yes
            Removable media: No
            Readonly: Yes
            Backing store type: rdwr
            Backing store path: /usr/local/storage/linuxmint-14.1-mate-dvd32bit.iso
            Backing store flags: 
    Account information:
    ACL information:
        ALL

}}}



Adding the above target to VirtualBox
{{{
VBoxManage storageattach ""NewPasswordWindowsReadOnly2"" --storagectl ""MyController"" --port 1 --device 0 --type dvddrive --medium iscsi --server localhost --target ""iqn.2001-04.com.TehDualLinux-2260f94a-90f3-4147-9e32-39c773f7095b"" --lun 1 --tport 3260
}}}



It was added successfully.
{{{
vboxmanage list hdds

...
UUID:        2d4790e0-678b-4fc0-b529-32aebfec6f97
Parent UUID: base
Format:      iSCSI
Location:    localhost|iqn.2001-04.com.TehDualLinux-2260f94a-90f3-4147-9e32-39c773f7095b|1
State:       created
Type:        normal
Usage:       NewPasswordWindowsReadOnly2 (UUID: e86ffe75-2412-4aa6-9b36-3a0c0f3e4780)
...

}}}


After we try and turn the machine on, it fails with:
{{{
Failed to open a session for the virtual machine NewPasswordWindowsReadOnly2.
VD: error VERR_VD_IMAGE_READ_ONLY opening image file 'localhost|iqn.2001-04.com.TehDualLinux-2260f94a-90f3-4147-9e32-39c773f7095b|1' (VERR_VD_IMAGE_READ_ONLY).
Failed to open image 'localhost|iqn.2001-04.com.TehDualLinux-2260f94a-90f3-4147-9e32-39c773f7095b|1' in read-write mode rc=VERR_VD_IMAGE_READ_ONLY (VERR_VD_IMAGE_READ_ONLY).
Failed to attach driver below us! Image is read-only. (VERR_VD_IMAGE_READ_ONLY).
AHCI: Failed to attach drive to Port1 (VERR_VD_IMAGE_READ_ONLY).
}}}

Steps to replicate:

1.  Make an iSCSI target with any iSCSI software and make it readonly
2.  Add the target to your guest via vboxmanage stoargeattach and do not take snapshots
3.  Turn on the guest.

Summary:

- If you remove the readonly flag on the iscsi target everything works perfectly (even through VirutalBox does not need write on this medium)
- If you take a snapshot (thus a differencing medium is created), everything works perfectly
- If you add the DVD as multiattach instead of ""normal"", it creates a differencing medium, and everything works perfectly.
- If you add the medium normally, even though VirtualBox's documentation claims it is readonly, it tries to access the medium as read/write."	rshaw
16661	Maximized windows broken in seamless mode	Windows	VirtualBox 5.1.18	2017-04-18T07:37:21Z	2017-08-08T07:48:32Z	2017-08-08T07:48:32Z	When i maximize a window in seamless mode (host debian stretch, guest win 7), only the area of the former non maximized window is displayed the rest of the now maximized window is transparent.	mietz
17285	Mapping shared folder fails if USB drive is connected after VM is started	Windows	VirtualBox 5.1.30	2017-11-18T05:44:24Z	2017-11-30T06:50:57Z	2017-11-30T06:50:57Z	"This basically is ""reopening"" of ticket #11445 (https://www.virtualbox.org/ticket/11445#comment:1) . The issue is still present in version 5.2.
"	Rafcio
17169	Magix Music Maker (Free) freezes current VM	Windows	VirtualBox 5.1.26	2017-10-15T20:28:54Z	2017-10-15T20:28:54Z	2017-10-15T20:28:54Z	"I have downloaded and installed ""Magix Music Maker Free"" in a Windows 10  VM (with Guest Additions).
The installation went fine, but when I started the program, right before starting the UI (was in Splashscreen) it froze the Virtual Mashine completly. The UI of the VM was responsive but when I e.g. selected ""Close"" the dialog did not appear and I had to kill the process of the VM.

I also tried the same with a Windows 7 VM (also with Guest Additions) and the same happened."	LinusCDE
18289	Machine unable to open	all	VirtualBox 6.0.0	2019-01-08T14:33:55Z	2019-01-08T14:35:46Z	2019-01-08T14:35:46Z	A critical error has occurred while running the virtual machine and the machine execution has been stopped.	sgaur
17398	Machine remains in aborted state with 3D enabled	Linux	VirtualBox 5.2.4	2017-12-24T10:07:30Z	2017-12-24T10:07:30Z	2017-12-24T10:07:30Z	With guest additions 5.2.4 when I save the state of a VM it starts saving the state but remains in an aborted state. This only happens with 3D enabled. Log has been attached.	mcpudding
17100	Machine inaccessible after snapshot deletion	Windows	VirtualBox 5.1.28	2017-09-19T23:35:28Z	2017-09-22T18:33:09Z	2017-09-22T18:33:09Z	Deleting second-to-last snapshot corrupts the VM, leading to machine inaccessible - line 9 - current snapshot missing.  This problem began with release 5.1.26 or before.  It occurs with 5.1.28 and also with 5.2.0_BETA3, which I'm running now.  Everything works fine before the snapshot deletion, including the ability to take a new snapshot.  The only way I know to recover is to restore the entire VM from backup.	kingfisher289
20962	machine guest freeze on emit audio	Windows	VirtualBox 6.0.22	2022-05-30T19:31:09Z	2022-06-10T14:43:03Z	2022-06-10T14:43:03Z	"Hello [[BR]]

Virtualbox 6.0.24[[BR]]


I play audio mp3 MCI windows, then the machine guest random freeze[[BR]]
Thank.[[BR]]
"	Sizy458
20979	machine folder share corrupts data	Linux	VirtualBox 6.1.34	2022-06-11T01:27:45Z	2022-06-11T01:27:45Z	2022-06-11T01:27:45Z	After upgrading to 6.1.32, machine folder shares started showing corruption when being written to. Also happens in 6.1.34. Happens on new install of ubuntu 22.04 as guest on ubuntu 22.04 host.	illk
20312	Machine does not terminate: VBOX_E_INVALID_VM_STATE (0x80BB0002)	Linux	VirtualBox 6.1.20	2021-04-22T05:33:58Z	2021-04-22T05:33:58Z	2021-04-22T05:33:58Z	"Invalid machine state: Stopping.


Fehlercode: 
VBOX_E_INVALID_VM_STATE (0x80BB0002)
Komponente: 
ConsoleWrap
Interface: 
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}


Log attached

Issue first occured today, with VirtualBox 6.1.20"	Thermi
21344	Machine became unstable after multiple save and restore	Windows	VirtualBox 6.1.40	2022-12-16T17:04:54Z	2022-12-16T17:04:54Z	2022-12-16T17:04:54Z	"Hello,[[BR]]

My machine work good but when i make many time action stop by save state and resume [[BR]]
state or after some time then my guest machine has problem :[[BR]]

_Flicking mouse cursor[[BR]]

_Click don't respond when i execute more windows processus[[BR]]


I reboot my guest machine then same problem.[[BR]]

I shutdown my guest machine and restart then no problem.[[BR]]

"	Sizy458
10811	MAC addresses filtered by VBox bridging	Linux	VirtualBox 4.1.18	2012-08-07T02:59:11Z	2019-09-12T16:25:43Z	2019-09-12T16:25:43Z	"I am attempting to run an OpenVPN server in a Ubuntu 12.04 (server) guest machine running on a Ubuntu 12.04 (server) host via VBoxHeadless.  This OpenVPN server needs to run as a layer 2 VPN (tap) which means it will place clients onto the local LAN with their own MAC addresses visible, and these clients need to be capable of two-way communication at layer 2.  I have been using the bridged network adapter for the VM.

When run from within the VM, I can connect clients to this server and ping/log into the server's IP, (guest machine) but I cannot access the Host's IP or anything else on the LAN from the client.  If I set up the OpenVPN server identically on the host, (Which is the same OS and otherwise identical setup) it works fine.  OpenVPN requires setting up a bridge internally on the server for this kind of layer 2 tap VPN, and putting the ethernet interface into promiscuous mode.  I've tried attaching the VM bridged adapter to the physical eth0 interface of the host and also to a bridged adapter on the host that was then bridged to the eth0 interface while eth0 was in promiscuous mode (similar to the setup on the guest)

I have found two other references to this problem, one with a Linux host, the other with Windows.  The Windows one was ticket #8965.  Both references indicate that this bug was a regression between versions 4.0.4 and 4.0.6.  Since I'm using Ubuntu 12.04 and VBox 4.1.18, downgrading to VBox 4.0.4 to confirm this would be painful.

Looking at the changelog of 4.0.6, I suspect that I've found the culprit:
""Host-Only & Bridged & Internal Networking: fix for processing promiscuous mode requests by VMs, defaulting to switch behaviour ""

Not sure what is meant by ""switch behavior"" but a switch is nothing more than a many-port bridge, which will broadcast frames to all ports but the one it came in on if the MAC is not in the MAC table, will learn the source MAC of any frame and put it in the MAC table for the port it came in on, and will unicast learned MACs to the ports on which the MAC table says they reside.  This may be somewhat inconsistent with being able to specify a MAC for the bridged adapter of the guest (which I have also done in this case)  If the switch portion is not flooding unlearned frames out to the guest machine virtual ports and also learning new MAC entries from frames sent by those ports, then the behavior may be efficient, but it will also be incorrect for Guests with their interfaces in promiscuous mode.

This bug is closely related to #8965 and this version with the Linux host type is also referenced here: https://forums.virtualbox.org/viewtopic.php?f=7&t=42335&p=203067&hilit=openvpn#p203067
"	Raltar
17710	LsiLogic SCSI BIOS: int13_harddisk: function 02, error 04 ! or  int13_harddisk_ext: function 42, error 04 !	Windows	VirtualBox 5.1.22	2018-04-24T13:19:49Z	2018-04-24T20:00:33Z	2018-04-24T20:00:33Z	"while starting winxp32/64 win764 guests(linux guests same controller work fine) using LsiLogic SCSI controller(also SAS) with ""Use Host I/O cache"" active, on debian 8 host i get very often these errors while hang

same guests same setup on win764 host work fine

win xp 32/64: VMMDev: Guest Log: BIOS: int13_harddisk: function 02, error 04 !
win764: VMMDev: Guest Log: BIOS: int13_harddisk_ext: function 42, error 04 !

the bug doesnt appear if ""Use Host I/O cache"" is off
also no data corruption on guests

more detail: https://forums.virtualbox.org/viewtopic.php?f=7&t=87646&p=418668#p418668


'''my setup'''
vbox 5.1.22 r115126 (Qt5.3.2)
guest: Hdd controller LsiLogic SCSI
host: 3.16.0-4-amd64 #1 SMP Debian 3.16.51-3 (2017-12-13) x86_64 GNU/Linux Debian 8.10"	justaquiz
17177	Loss of usb device after live snapshot or snapshot restore	Linux	VirtualBox 5.1.30	2017-10-18T09:32:09Z	2017-10-24T15:20:39Z	2017-10-24T15:20:39Z	"{{{
Host OS: Solus 3 (linux)
Guest OS: Solus 3
Solus kernel: 4.13.5-24.current
VirtualBox Build: 5.1.30r118389
Extension pack installed
USB 2.0 selected
}}}

* USB gamepad shared with the guest.
* Cold boot.
* Play a game using gamepad (e.g. supertux 2)
* Take a live snapshot.
* Gamepad no longer working.
* Restore snapshot.
* Gamepad not working.
* Reboot = gamepad working again.

"	romulous75
17564	Lock-up in the file browser on rename	all	VirtualBox 5.2.6	2018-02-25T22:30:29Z	2018-03-03T20:49:55Z	2018-03-03T20:49:55Z	"Reprod as follows:

- Create a new virtual machine
- Add new storage attachment
- Choose 'add hard disk'
- Navigate to a file (pretty much any file or folder will do)
- Right-click 'rename'
- Hit backspace to remove the content of the filename so it is blank.
- Now click 'open'

A dialog is permanently displayed on the screen saying:

The name """" can not be used.

Try using another name, with fewer characters or no punctuation marks.

From this point there is no option but to kill VirtualBox.
"	Biff
8830	Lock screen removes all clipboard data	Windows	VirtualBox 4.0.6	2011-05-03T10:11:42Z	2011-11-13T18:49:37Z	2011-11-13T18:49:37Z	Lock screen removes all clipboard data.	386sky
18746	Live snaphot cloning (VBoxManage clonevm) fails when basefolder is SMB share	all	VirtualBox 6.0.8	2019-07-07T18:49:50Z	2019-07-29T18:17:19Z	2019-07-29T18:17:19Z	"When the `--basefolder` is specified to point to a Samba share, the clonevm process fails for a previously-created live snapshot.

Interesting note: the issue does NOT occur when the snapshot was taken from a VM that was powered off (not live). Live snapshot clones do succeed, however, when the basefolder is on the local ext4 filesystem.

Host is Ubuntu 16.04 amd64 running kernel 4.15.

{{{
$ VBoxManage snapshot ""{7a81c085-7fd5-49c6-a698-c64eda275119}"" take backup.tmp --live
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Snapshot taken. UUID: d53e1bfb-2111-4945-ac1a-d1b10206c5f3

$ VBoxManage clonevm ""{7a81c085-7fd5-49c6-a698-c64eda275119}"" --snapshot backup.tmp --options keepallmacs,keepdisknames --basefolder /vmdata/_backups/tmp --name ""iot-manager.bak""
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...
Progress state: VBOX_E_IPRT_ERROR
VBoxManage: error: Clone VM failed
VBoxManage: error: Code VBOX_E_IPRT_ERROR (0x80BB0005) - Runtime subsystem error (extended info not available)
VBoxManage: error: Context: ""RTEXITCODE handleCloneVM(HandlerArg*)"" at line 609 of file VBoxManageMisc.cpp
}}}

/vmdata/_backups is a Samba mountpoint on a Synology box. Relevant info from `mount`:
{{{
//mynas/NAS/VM stuff/backups on /vmdata/_backups type cifs (rw,relatime,vers=3.0,sec=ntlmssp,cache=strict,username=nasuser,domain=,uid=1000,forceuid,gid=0,noforcegid,addr=mynas,file_mode=0755,dir_mode=0755,soft,nounix,serverino,mapposix,rsize=1048576,wsize=1048576,echo_interval=60,actimeo=1)
}}}
"	Aleksandr Kotlyar
9087	"Linux: Please optimize output of VBoxHeadless in ""top"""	other	VirtualBox 4.0.8	2011-06-17T21:05:07Z	2011-06-17T21:05:07Z	2011-06-17T21:05:07Z	"On a Linux host the ""top"" program is a great tool to see how many resources (memory, CPU usage,...) are used by various Linux processes[[BR]]
But when running multiple headless virtual machines on one physical server it's not possible to see which virtual machine is using how many resources. Instead every virtual machine process is  visible as ""VBoxHeadless"" process (which is of course in principle correct).[[BR]]

My proposal and trivial feature request:[[BR]]
In VBoxHeadless code on Linux, could you please add a call to ""prctl(PR_SET_NAME, _VIRT_MACHINE_NAME_)"", so that the ""top"" program can report the real VM name?[[BR]]

Current example of ""top"" with 3 virtual machines:[[BR]]

{{{
top - 22:52:30 up 14:45,  4 users,  load average: 0.22, 0.09, 0.11
Tasks: 262 total,   1 running, 261 sleeping,   0 stopped,   0 zombie
Cpu(s):  1.0%us, 11.4%sy,  1.0%ni, 86.6%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
Mem:   8194156k total,  8141484k used,    52672k free,    33564k buffers
Swap:  8388604k total,        0k used,  8388604k free,  1826788k cached

PID   USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
10097 root      20   0 3380m 2.1g 2.1g S 14.0 26.9  13:57.83 VBoxHeadless
10181 root      20   0 2790m 1.6g 1.5g S  8.0 20.1   3:53.61 VBoxHeadless
10141 root      20   0 2618m 1.5g 1.5g S  1.3 19.7   2:38.39 VBoxHeadless
}}}

Now, if the VBoxHeadleass process was started as ""VBoxHeadless --comment MY_VMACHINE --startvm 2d576-6b3-48-9f-333333 --vrde config"", with the proposed prctl() call, one of the ""VBoxHeadless"" processes above would instead show up as ""MY_VMACHINE"".[[BR]]



"	Helge Deller
14855	Linux: Link local IPv6 address is the only one returned for host-only interfaces	other	VirtualBox 5.0.10	2015-11-21T22:08:52Z	2018-04-19T07:50:45Z	2018-04-19T07:50:45Z	"When configuring IPv6 on Linux, the interface may have a Link Local Address (fe::) in addition to the address configured through VirtualBox. VirtualBox retrieves the addresses from {{{/proc/net/if_inet6}}}. Here is an example of what these entries look like:
{{{
$ cat /proc/net/if_inet6 
00000000000000000000000000000001 01 80 10 80       lo
fd22dfff102810700000000000000000 06 40 00 80 vboxnet3
fe80000000000000020acdfffe20a291 02 40 20 80     eth0
fe80000000000000080027fffe000003 06 40 20 80 vboxnet3
}}}

Note the order of the addresses. When VirtualBox parses the file, the code assumes there would only be one entry for an interface (and does not terminate early), i.e. (this is NetIf-linux.cpp):
{{{#!c
173             for (;;)
174             {
[...]
182                 if (n == EOF)
183                     break;
184                 if (n != 9 || uLength > 128)
185                 {
[...]
188                     break;
189                 }
190                 if (!strcmp(Req.ifr_name, szName))
191                 {
192                     pInfo->IPv6Address.au32[0] = htonl(IPv6Address.au32[0]);
193                     pInfo->IPv6Address.au32[1] = htonl(IPv6Address.au32[1]);
194                     pInfo->IPv6Address.au32[2] = htonl(IPv6Address.au32[2]);
195                     pInfo->IPv6Address.au32[3] = htonl(IPv6Address.au32[3]);
196                     ASMBitSetRange(&pInfo->IPv6NetMask, 0, uLength);
197                 }
198             }
199             fclose(fp);
200         }
}}}

For the above example, the last, Link-Local entry wins. Since VirtualBox does not handle multiple addresses per interface, it should at least ignore the Link-Local automatically created addresses. Unfortunately, this means that it would be impossible to tell which address to pick if a user configures a different link-local address.

I attached a proposed patch to resolve this."	timuralp
20223	Linux/64bit host XMM register usage in kernel randomly crashes Linux guest	Linux	VirtualBox 6.1.16	2021-02-24T18:57:46Z	2021-02-24T18:57:46Z	2021-02-24T18:57:46Z	"'''Synopsis:''' src/VBox/VMM/Makefile.kmk 'knows' flag VBOX_WITH_KERNEL_USING_XMM, which is added for Windows/64bit builds only.
Problem is that Linux kernel DOES MAKE USE of XMM registers, too. Examples include aes-ni kernel module (AES-NI instructions implicitly use XMM0..15) or RAID, respectively).
VMM at ring 0 only implements XMM wrappers for Windows/64bit and does not have conditionals to abort build if VBOX_WITH_KERNEL_USING_XMM is set in src/VBox/VMM/Makefile.kmk for linux.amd64. This yields a kernel panic because Microsoft ABI is completely different from System V ABI (aka gcc ABI).
The 6.1.18 trunk seems to rely on a complete rewrite of src/VBox/VMM/VMMR0/HMR0A.asm but 6.1.13 / 6.1.16 (6.0 also) still have this problem.

'''Solution is:'''

a) Add VBOX_WITH_KERNEL_USING_XMM to src/VBox/VMM/Makefile.kmk for linux.amd64


b) Provide conditional implementation in src/VBox/VMM/VMMR0/HMR0A.asm for gcc/amd64 expecting function parameters in System V ABI registers rdi, rsi, rdx, rcx, r8, and r9. The two wrappers hmR0VMXStartVMWrapXMM and hmR0SVMRunWrapXMM need this.


c) calling CPUMIsGuestFPUStateActive from yasm assembler to C++ requires suffix ""wrt ..plt""

I have patches for this but optimized only for ""my"" Intel CPU. VBox users either have to switch to 6.1.18 or apply the above mentioned modifications.

'''Recommendation:'''

VBOX maintainers should think about making VBOX_WITH_KERNEL_USING_XMM the default for Linux, too (because of possible AES-NI or RAID usage, respectively)."	vboxcomapijunkie
19408	Linux panic with a 'not-present page' when rebooting resumed VM	all	VirtualBox 6.1.4	2020-03-16T08:52:47Z	2020-08-31T21:03:37Z	2020-08-31T21:03:37Z	After I suspended/resumed Windows 10 guest (Fedora 31 host, kernel 5.5.9), the rebooted it, VM caused kernel oops and virtual box froze (all windows, including manager). Attaching kernel oops report.	Max Fedotov
20129	Linux kernel version 5.10 - we need changes	all	VirtualBox 6.1.16	2021-01-16T15:57:13Z	2021-01-25T07:23:02Z	2021-01-25T07:23:02Z	"Linux kernel 5.10 won't work with the latest virtualbox 6.1.16, under Fedora 32/33.


/tmp/vbox.0/r0drv/linux/memobj-r0drv-linux.c: In function ‘rtR0MemObjLinuxVMap’:
/tmp/vbox.0/r0drv/linux/memobj-r0drv-linux.c:560:34: error: implicit declaration of function ‘alloc_vm_area’ [-Werror=implicit-function-declaration]
  560 |                 pMemLnx->pArea = alloc_vm_area(pMemLnx->Core.cb, papPtes); /* Note! pArea->nr_pages is not set. */
      |                                  ^~~~~~~~~~~~~
/tmp/vbox.0/r0drv/linux/memobj-r0drv-linux.c:560:32: warning: assignment to ‘struct vm_struct *’ from ‘int’ makes pointer from integer without a cast [-Wint-conversion]
  560 |                 pMemLnx->pArea = alloc_vm_area(pMemLnx->Core.cb, papPtes); /* Note! pArea->nr_pages is not set. */
      |                                ^
   ./tools/objtool/objtool orc generate  --module --no-fp --retpoline --uaccess /tmp/vbox.0/SUPDrvTracer.o
/tmp/vbox.0/SUPDrvTracer.o: warning: objtool: .text+0x7: indirect jump found in RETPOLINE build
/tmp/vbox.0/SUPDrvTracer.o: warning: objtool: supdrvTracerProbeFireStub() is missing an ELF size annotation


Thank you.


PS:
It seems like a common occurrence, first a new kernel is released, packaged and distributed to update repos, we update and discover that its not working, then wait 3-4 months for a new virtualbox. Maybe it would be possible to test future kernels earlier? 
"	VirtualBarista
15164	Linux kernel 4.4.0-7.22 (amd64, Ubuntu Xenial) locks up if not using serial output	Linux		2016-02-21T14:35:14Z	2016-12-25T22:06:53Z	2016-12-25T22:06:53Z	"Hello!

I'm experiencing a rather strange bug. It's perfectly possible that it's a guest kernel bug, and in that case sorry for the noise.

Linux host, Linux strange 4.4.0-6-generic #21-Ubuntu SMP Tue Feb 16 20:32:27 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux, 5.0.15r105570 test build

Guest, created by Vagrant, using Ubuntu's linux-image-4.4.0-7-generic_4.4.0-7.22_amd64.deb kernel package.

If I enable a serial port (COM1, raw file output), the guest boots without a problem (but a bit slowly, because it uses a low baud rate by default, I guess). If on the other hand I don't and it doesn't switch to it, the guest kernel basically stops progress after ""no floppy controllers found"" (or work still pending). Eventually initializes the random pool (random: nonblocking pool initialized), and nothing further. I can type, but of course nothing happens, just keys get echoed. Upon sending a SysRq T (tasks?) only the last lines are visible, but it informed me of a pending console_callback.

Any ideas?"	Pas
18810	Linux Host: High CPU usage with idle Windows 10 guest	Windows	VirtualBox 6.0.6	2019-08-04T13:36:07Z	2019-08-05T06:46:47Z	2019-08-05T06:46:47Z	"When Windows 10 is in idle mode, there still high CPU usage in host.
Host is Kubuntu 18.04.

---
{{{
rfried@rfried-mobl1 ~/dev/vim-bitwise master $ top
top - 16:34:02 up 6 days, 55 min,  8 users,  load average: 1.49, 1.84, 1.89
Tasks: 357 total,   1 running, 356 sleeping,   0 stopped,   0 zombie
%Cpu(s):  2.0 us,  7.1 sy,  0.0 ni, 90.5 id,  0.0 wa,  0.0 hi,  0.4 si,  0.0 st
MiB Mem :  32001.6 total,   1579.0 free,  13931.3 used,  16491.3 buff/cache
MiB Swap:   2048.0 total,   2036.5 free,     11.5 used.  17438.4 avail Mem 

  PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND                                                                                                                 
27416 rfried    20   0   11.1g   8.5g   8.3g S 138.1  27.2 681:52.72 VirtualBoxVM  
}}}"	rfried
18017	Linux host, Windows guest: screen resolutions limited and fix messes up the pointer	Windows	VirtualBox 5.2.18	2018-09-27T16:00:13Z	2018-09-28T05:16:57Z	2018-09-28T05:16:57Z	"1) Windows 10 VM exposes only resolutions lower than my native one. I worked around the problem by issuing this command:


{{{
VBoxManage setextradata global GUI/MaxGuestResolution any
}}}

''However'' - and this is problem 2) - once the VM was using my native resolution, setting the scaling within my Windows 10 Guest to 150%, and especially to anything higher, causes pointer strangeness in Word 365. For, once the pointer changes - changes upon mouse-over of an icon in the Word ribbon - it does not, for some time or occasionally permanently, change back.

Virtual Box 5-2
Linux Mint 19 x64 Cinnamon

An existing bug report contains the first of the two problems that I have detailed; however, I am afraid that I cannot manage to re-locate that report."	JN
18634	Linux host, Windows guest: screen corruption; and once the pointer changes it does not change back	Windows	VirtualBox 6.0.6	2019-05-12T02:15:12Z	2019-05-12T02:15:12Z	2019-05-12T02:15:12Z	"To reproduce the screen corruption:

In Windows, set the 'scale and layout' option to 200%.
Do things.
Rebooting seemed to fix the problem but then the corruption returned.

To reproduce the pointer problem:

In Windows, set the 'scale and layout' option to 200%.
Open Word. Move pointer over toolbar and then to text area.

These problems makes the VM unusual at the 200% scale. I do not have the problems when the scaling is set to 175%.

Host: Linux Mint 19.1 Cinnamon x64; kernel 5.1
Guest: Windows 10 Home, build 1809
Machine: Lenovo Thinkpad X1CG2560x1440 6; 16GB RAM; Intel i7-8550U (8) @ 4.000GHz; Intel UHD Graphics 620; resolution 2560x1440 - HiDPI enabled on the host OS.
VirtualBox Version 6.0.6 r130049 (Qt5.9.5)
"	JN
18180	Linux host, Windows and Linux guests: CPU does not exceed 1.99GHz	other	VirtualBox 5.2.22	2018-12-12T22:25:49Z	2018-12-12T22:34:14Z	2018-12-12T22:34:14Z	"Host: ThinkPad X1 Carbon 6th Generation. Intel i7-8550U (quad-core, plus hyperthreading giving eight virtual cores), 1.8GHz boosting to 4.0GHz. OS (natie) Linux Mint 19 x64 Cinnamon. The boost works on the native OS. When running Windows 10 Home in a VM, or Linux Mint 19.1 x64 Beta in a VM, the CPU speed in the guest does not exceed 1.99GHz. This severely limits performance.

Virtual Box 5.2.23 (test build). In each of the two VMs in question, four processors are allocated and the execution cap is set to 100 (one hundred)%."	JN
9092	Linux host Windows XP guest virtual drive gets corrupted when installing service pack	Windows	VirtualBox 4.0.8	2011-06-21T11:51:35Z	2011-06-29T19:00:50Z	2011-06-29T19:00:50Z	"I am using Ubuntu 11.04 as the host and I am trying to install Windows XP as the guest and then using windows update to install all the updates. I have 2 Win XP CDs, one does not include any service pack the other includes service pack 2.  

The installs works fine from both CDs in that their are no errors. Windows update seems to work fine in that there are no errors.  When service pack 2 or 3, depending upon which CD I started with, is applied Windows update says the service pack was successfully installed and requires a reboot.  When the guest starts to boot I get a message that Windows cannot be found.  When I boot the guest with the CD and select repair and run chkdsk on drive c:, chkdsk finds file after file that is corrupt and cannot be fixed. 

I have tried this many times now with the same result. I have tried installing and not installing the 4.0.8 extensions before using the Windows update.  The virtual drive is defined as IDE master. I have even managed to corrupt the virtual drives of Windows XP that were created under VirtualBox version 3."	Mark Myers
19327	Linux host vlan interface cannot be bridged to guest	all	VirtualBox 6.1.4	2020-02-20T16:56:07Z	2020-02-20T16:56:07Z	2020-02-20T16:56:07Z	Linux host vlan interface cannot be bridged to guest.	tulipb
20764	Linux host seamless mode with windows 10 guest often don't display anything	other	VirtualBox 6.1.30	2022-01-08T21:02:10Z	2022-01-08T21:02:10Z	2022-01-08T21:02:10Z	"I installed windows 10 as a guest and run a few apps using seamless-mode but it won't work quite often (no error or anything.. it just doesn't display anything of the vm in seamless when it doesn't work).
I think the issue first appears after restoring from a snapshot (save machine state) instead of rebooting, but a reboot doesn't fix it.
after some time (a few reboots of host and guest it ""randomly"" works again but I can reproduce it very often..).

I already tried all Display / Graphics settings on the vm.

the issue happens on both KDE and XFCE.
I currently use the version from the ubuntu repos:
6.1.26
but I also tried with 6.1.30 and the same issue occurs."	test111
20765	Linux host seamless mode with windows 10 guest Keeps displaying Background the same size the last closed Window was	Windows	VirtualBox 6.1.30	2022-01-08T21:07:12Z	2022-01-19T09:11:22Z	2022-01-19T09:11:22Z	"I installed windows 10 as a guest and run a few apps using seamless-mode
almost every time I close the last Window seamless-mode will leave me with a part of my Screen occupied by a part of my screen displaying the background of the VM and making that part of the Linux-Desktop inaccessible.

I already tried all Display / Graphics settings on the vm.

the issue happens on both KDE and XFCE. I currently use the version from the ubuntu repos: 6.1.26 but I also tried with 6.1.30 and the same issue occurs."	test111
4678	Linux host running on MacBook Hardware: Default release key should be left-winkey	other	VirtualBox 3.0.4	2009-08-05T02:03:49Z	2009-08-05T08:16:12Z	2009-08-05T08:16:12Z	"Here's a simple one:

The default key to release a captured mouse from the VBox window is right-ctrl. Quite rightly it is set to Left-Command when running on an OSX host, because some hardware, such as a MacBook Pro, doesn't have such a button, and you'll be unable to free your mouse without some annoyance.

However the same decision isn't taken when you run on Linux (or, I imagine, Windows,) running on a MacBook. It'd be neat if the installer would figure out that we're on an Apple device and set the release key to something different!"	Chris Smowton
15090	"Linux host running ""perf top"" kills Virtualbox vm's (VERR_PGM_INVALID_CR3_ADDR)"	all	VirtualBox 5.0.14	2016-01-29T12:50:34Z	2017-06-26T07:20:41Z	2017-06-26T07:20:41Z	"If I run Linux tool ""perf top"" on host and Virtualbox VM at the same time, VM crashes. It doesn't matter which is started first.

Host versions tested:
 * Linux 4.3.3-3-ARCH #1 SMP PREEMPT x86_64
 * perf version 4.4.gafd2ff
 * !VirtualBox 5.0.14_OSE !r105127

Guest versions tested:
 * Linux 4.4.0-4-ARCH #1 SMP PREEMPT x86_64
 * Linux 2.6.18-164el5PAE #1 SMP i686
 * Windows10 64-bit modern.ie without guest additions

Host dmesg:
{{{
[  313.192046] capability: warning: `VirtualBox' uses 32-bit capabilities (legacy support in use)
[  371.880286] SUPR0GipMap: fGetGipCpu=0x3
[  372.327223] vboxdrv: ffffffffa08b4020 VMMR0.r0
[  372.522422] vboxdrv: ffffffffa09af020 VBoxDDR0.r0
[  372.529397] vboxdrv: ffffffffa00c6020 VBoxDD2R0.r0
[  372.617800] VBoxNetFlt: attached to 'eth0' / 74:d0:2b:95:1b:92
[  372.624009] device eth0 entered promiscuous mode
[  374.602722] HPET: Using timer above configured range: 2
[  374.603501] HPET: Using timer above configured range: 2
[  374.603507] HPET: Using timer above configured range: 2
[  374.603511] HPET: Using timer above configured range: 2
[  374.603515] HPET: Using timer above configured range: 2
[  374.603519] HPET: Using timer above configured range: 2
[  374.603523] HPET: Using timer above configured range: 2
[  374.603527] HPET: Using timer above configured range: 2
[  374.603531] HPET: Using timer above configured range: 2
[  374.603535] HPET: Using timer above configured range: 2
[  374.603539] HPET: Using timer above configured range: 2
[  374.603543] HPET: Using timer above configured range: 2
[  389.380249] device eth0 left promiscuous mode
[  390.099756] vboxnetflt: 0 out of 4 packets were not sent (directed to host)
}}}
Attaching VBox.log's in a second."	dimaqq
15525	Linux host hangs during compiling	Linux	VirtualBox 5.0.22	2016-06-17T18:15:49Z	2016-10-17T17:48:37Z	2016-10-17T17:48:37Z	I'm compiling LibreOffice on Xubuntu 16.04 guest machine and sometimes (3 freezes - 6 compilings) guest machine freezes. Guest machine is allowed to use 2 cores. I have AMD Phenom II with 4 cores. Host machine - Linux Mint 17.3 (based on ubuntu 14.04)	yanp.bugz
20024	Linux host freezes with bridged adapter and apt	Linux	VirtualBox 6.1.16	2020-11-08T00:50:16Z	2020-11-08T03:28:46Z	2020-11-08T03:28:46Z	"My Linux (Fedora 33) host freezes whenever I enable bridged adapter and the guest transfers (some) data.

Steps to reproduce:
1. Install an Ubuntu 20.04 server guest
2. Go to Guest settings, Network, Attached to, Bridged Adapter
3. Run an apt install command on it. I was following [these instructions](https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-quickstart).
4. The host completely freezes, and I'm forced to reboot.

I've installed some server software (Jitsi Meet) and now it freezes even on guest boot.

Some hardware details:

{{{
*-cpu
          product: AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx
          vendor: Advanced Micro Devices [AMD]
          physical id: 1
          bus info: cpu@0
          size: 1443MHz
          capacity: 2100MHz
          width: 64 bits
          capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp x86-64 constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb hw_pstate sme ssbd sev ibpb vmmcall fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflushopt sha_ni xsaveopt xsavec xgetbv1 xsaves clzero irperf xsaveerptr arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov succor smca cpufreq
}}}



{{{
*-network
                description: Wireless interface
                product: RTL8822CE 802.11ac PCIe Wireless Network Adapter
                vendor: Realtek Semiconductor Co., Ltd.
                physical id: 0
                bus info: pci@0000:02:00.0
                logical name: wlp2s0
                version: 00
                serial: [REMOVED]
                width: 64 bits
                clock: 33MHz
                capabilities: bus_master cap_list ethernet physical wireless
                configuration: broadcast=yes driver=rtw_8822ce driverversion=5.8.18-300.fc33.x86_64 firmware=N/A ip=[REMOVED] latency=0 link=yes multicast=yes wireless=IEEE 802.11
                resources: irq:81 ioport:2000(size=256) memory:c0700000-c070ffff
}}}

I will append a log file in some minutes"	gabrc
17176	Linux Host Freeze	Windows		2017-10-17T22:08:53Z	2017-10-17T22:08:53Z	2017-10-17T22:08:53Z	"I am trying to use 5.2 RC1 with VBoxGuestAdditions_5.2.0-118335.iso. While compiling it gives the error.

Removing existing VirtualBox kernel modules.
Building the main Guest Additions module.
make KBUILD_VERBOSE=1 CONFIG_MODULE_SIG= -C /lib/modules/4.13.5-200.fc26.x86_64/build SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 -j4 modules
make[1]: warning: -jN forced in submake: disabling jobserver mode.
test -e include/generated/autoconf.h -a -e include/config/auto.conf || (                \
echo >&2;                                                       \
echo >&2 ""  ERROR: Kernel configuration is invalid."";           \
echo >&2 ""         include/generated/autoconf.h or include/config/auto.conf are missing."";\
echo >&2 ""         Run 'make oldconfig && make prepare' on kernel src to fix it."";      \
echo >&2 ;                                                      \
/bin/false)
mkdir -p /tmp/vbox.0/.tmp_versions ; rm -f /tmp/vbox.0/.tmp_versions/*
make -f ./scripts/Makefile.build obj=/tmp/vbox.0


Due to this VM freezes 

[  374.469053] [drm:vbox_bo_unpin [vboxvideo]] *ERROR* unpin bad ffff973728313400
[  374.485162] [drm:vbox_bo_unpin [vboxvideo]] *ERROR* unpin bad ffff973728312000
[  374.498844] [drm:vbox_bo_unpin [vboxvideo]] *ERROR* unpin bad ffff973728313400
[  374.751049] [drm:vbox_bo_unpin [vboxvideo]] *ERROR* unpin bad ffff973728312000
[  374.767185] [drm:vbox_bo_unpin [vboxvideo]] *ERROR* unpin bad ffff973728313400
[  374.783423] [drm:vbox_bo_unpin [vboxvideo]] *ERROR* unpin bad ffff973728312000
[  374.799557] [drm:vbox_bo_unpin [vboxvideo]] *ERROR* unpin bad ffff973728313400
[  374.809525] [drm:vbox_bo_unpin [vboxvideo]] *ERROR* unpin bad ffff973728312000
[  374.818953] [drm:vbox_bo_unpin [vboxvideo]] *ERROR* unpin bad ffff973728313400
[  374.834671] [drm:vbox_bo_unpin [vboxvideo]] *ERROR* unpin bad ffff973728312000
[  374.853894] [drm:vbox_bo_unpin [vboxvideo]] *ERROR* unpin bad ffff973728313400
[  374.871137] [drm:vbox_bo_unpin [vboxvideo]] *ERROR* unpin bad ffff973728312000
[  374.903968] [drm:vbox_bo_unpin [vboxvideo]] *ERROR* unpin bad ffff973728313400
[  375.086138] [drm:vbox_bo_unpin [vboxvideo]] *ERROR* unpin bad ffff973728312000
[  375.105844] [drm:vbox_bo_unpin [vboxvideo]] *ERROR* unpin bad ffff973728313400
[  375.130701] [drm:vbox_bo_unpin [vboxvideo]] *ERROR* unpin bad ffff973728312000
[  375.153612] [drm:vbox_bo_unpin [vboxvideo]] *ERROR* unpin bad ffff973728313400
[  380.547353] [drm:vbox_bo_unpin [vboxvideo]] *ERROR* unpin bad ffff973728312000


Linux 4.13.5-200.fc26.x86_64 #1 SMP Thu Oct 5 16:53:13 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

"	Taral
17257	Linux host + Windows 10 + client tools results in minor display corruption	Windows	VirtualBox 5.1.30	2017-11-09T11:30:46Z	2017-11-09T11:50:46Z	2017-11-09T11:50:46Z	"Steps to reproduce:

1. Start with host Ubuntu Linux 16.04 LTS 64 bit (I'm able to reproduce with intel i7-3770K + integrated graphics (i915 driver)).
2. Install Windows 10 as client (https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/ - I'm reproducing with 32 bit Windows 10).
3. Launch Internet Explorer 11
4. Visit https://jsfiddle.net/rwfvo4L7/

Expected results:

Rounded corners for the grey rounded boxes should look normal.

Actual results:

Rounded left side corners have some kind of horizontal comb-like effect. Similar problems may appear on some diagonal lines in SVG graphics etc.

Additional information:

May be related: https://www.virtualbox.org/ticket/14637
"	mtrantalainen
20000	Linux guests lock up with Host I/O cache disabled (NVMe and SATA)	Linux	VirtualBox 6.1.14	2020-10-26T15:57:22Z	2021-02-23T21:37:44Z	2021-02-23T21:37:44Z	"I have been finding that Linux guests seem to lock up when Host I/O cache is disabled when disks are under load (for example when installing system updates). dmesg also shows disk timeouts, and it seems no further disk operations succeed after this point without killing the VM process and restarting.

A log is attached. I'm not sure how to reproduce this reliably, but it seems to happen when I'm installing updates. I have seen this with both Ubuntu and Fedora guests. I will also upload a screenshot shortly with the exact messages, but I seem to have misplaced it for the moment.

I should also note that this is with the VDI nonrotational option turned on and discard=on in the guest Linux OS.

Anything else I can do to help diagnose?"	Hamish McIntyre-Bhatty
20030	linux guests cannot be restored	Linux	VirtualBox 6.1.16	2020-11-09T19:54:36Z	2020-11-29T22:19:16Z	2020-11-29T22:19:16Z	"Unable to restore linux guest (Ubuntu) in linux host (Fedora Rawhide). Error ""Kernel driver not installed"" (even though the package is). Running akmods as recommended results in error (log attached).

System info - uname -r: 5.10.0-0.rc2.20201105git4ef8451b3326.64.fc34.x86_64
Specific VB packages: 6.1.16_RPMFusion r140961

This makes virtualbox completely unusable. Has persisted for ~a few weeks with diligent system updating on Fedora Rawhide."	xris
20365	Linux guest won't boot unless hard disk is set as the priority	Linux	VirtualBox 6.1.22	2021-05-13T19:11:02Z	2021-05-14T10:33:56Z	2021-05-14T10:33:56Z	"After installing the latest CentOS 7.8
The OS refuses to boot unless the boot order for the VM is specifically changed so that the VM boots from the disk first.
If I set the boot order to something else (for example network for IPXE testing),the operating system instead shows an error ""fatal: int18: BOOT FAILURE"".
Most of what I found online talks about installing the disk in GPT vs MBR, but that shouldn't have much bearing since I know I installed the VM as MBR. None the less, I still tried to change the VM to UEFI since that is what the online community instructs.  However, no effect was detected besides the VM booting into the UEFI shell. However, if the boot order for the VM is changed, even though the other boot options are not being used and the option for disk is eventually reached, the boot option for the disk will eventually show the error.

"	Rusty_Almighty
16071	Linux Guest is aborting after some time of inactivity (when afk)	Linux	VirtualBox 5.1.6	2016-10-15T23:34:16Z	2016-10-20T07:39:44Z	2016-10-20T07:39:44Z	"I can start up and work with the guest system (Linux mint xcfe 18 64 bit), but after a while (when I am away from keyboard) the VM aborts.



"	Klausss
19640	Linux Fullscreen Guest display broken	Linux	VirtualBox 6.1.10	2020-06-06T09:37:36Z	2020-11-09T03:22:37Z	2020-11-09T03:22:37Z	"At VirtualBox 6.1.4, the login screen shows fullscreen and once logged in, the desktop is set to fullscreen - in my case 1280 x 1024. 

Since VirtualBox 6.1.6 all my Debian 10 guests that run fullscreen have had
their display go blank once you've logged in. 

The same problem still exists with VirtualBox 6.1.10. The login screen is 
reduced to 800 x 600 and once logged in, the guests screen goes blank.
If you use the View -> Set Fullscreen (or Host+F key), the guests screen
reappears as windowed. Do this again and the guests display is fullscreen
again. However, rebooting the guest results in the same blank screen again. 

Attached are two VBoxLogs, one from 6.1.10 which is taken at the point the guests screen has gone blank and the other when using the GA's from 6.1.4, when everything works as it should.  

The Host is running Debian 10 with the Mate desktop.  
The affected guest(s) are also running Debian 10 with the Mate desktop."	Feline
19688	Linux 5.7.x + VBox 6.1.10 driver install failure	other	VirtualBox 6.1.10	2020-06-29T14:00:55Z	2020-07-05T09:47:27Z	2020-07-05T09:47:27Z	"Trying to install just built modules I've got the error:
{{{
ERROR: modpost: ""VBoxHost_RTErrConvertToErrno"" [/usr/src/virtualbox-ose-6.1.10/vboxnetflt/vboxnetflt.ko] undefined!
ERROR: modpost: ""VBoxHost_RTUuidFromStr"" [/usr/src/virtualbox-ose-6.1.10/vboxnetflt/vboxnetflt.ko] undefined!
ERROR: modpost: ""VBoxHost_RTErrConvertFromErrno"" [/usr/src/virtualbox-ose-6.1.10/vboxnetflt/vboxnetflt.ko] undefined!
ERROR: modpost: ""VBoxHost_RTLogLoggerEx"" [/usr/src/virtualbox-ose-6.1.10/vboxnetflt/vboxnetflt.ko] undefined!
ERROR: modpost: ""VBoxHost_RTNetIPv6PseudoChecksumEx"" [/usr/src/virtualbox-ose-6.1.10/vboxnetflt/vboxnetflt.ko] undefined!
ERROR: modpost: ""VBoxHost_RTSpinlockDestroy"" [/usr/src/virtualbox-ose-6.1.10/vboxnetflt/vboxnetflt.ko] undefined!
ERROR: modpost: ""VBoxHost_RTUuidCompareStr"" [/usr/src/virtualbox-ose-6.1.10/vboxnetflt/vboxnetflt.ko] undefined!
ERROR: modpost: ""VBoxHost_RTSemEventCreate"" [/usr/src/virtualbox-ose-6.1.10/vboxnetflt/vboxnetflt.ko] undefined!
ERROR: modpost: ""VBoxHost_RTSemFastMutexRequest"" [/usr/src/virtualbox-ose-6.1.10/vboxnetflt/vboxnetflt.ko] undefined!
ERROR: modpost: ""VBoxHost_RTLogRelGetDefaultInstanceEx"" [/usr/src/virtualbox-ose-6.1.10/vboxnetflt/vboxnetflt.ko] undefined!
ERROR: modpost: ""VBoxHost_RTSemEventSignal"" [/usr/src/virtualbox-ose-6.1.10/vboxnetflt/vboxnetflt.ko] undefined!
ERROR: modpost: ""VBoxHost_RTMemAllocTag"" [/usr/src/virtualbox-ose-6.1.10/vboxnetflt/vboxnetflt.ko] undefined!
ERROR: modpost: ""VBoxHost_RTSemEventWait"" [/usr/src/virtualbox-ose-6.1.10/vboxnetflt/vboxnetflt.ko] undefined!
ERROR: modpost: ""VBoxHost_RTNetIPv4PseudoChecksum"" [/usr/src/virtualbox-ose-6.1.10/vboxnetflt/vboxnetflt.ko] undefined!
ERROR: modpost: ""VBoxHost_RTNetIPv4FinalizeChecksum"" [/usr/src/virtualbox-ose-6.1.10/vboxnetflt/vboxnetflt.ko] undefined!
ERROR: modpost: ""VBoxHost_RTSemFastMutexRelease"" [/usr/src/virtualbox-ose-6.1.10/vboxnetflt/vboxnetflt.ko] undefined!
ERROR: modpost: ""VBoxHost_RTSpinlockAcquire"" [/usr/src/virtualbox-ose-6.1.10/vboxnetflt/vboxnetflt.ko] undefined!
ERROR: modpost: ""VBoxHost_RTR0Term"" [/usr/src/virtualbox-ose-6.1.10/vboxnetflt/vboxnetflt.ko] undefined!
ERROR: modpost: ""VBoxHost_RTMemFree"" [/usr/src/virtualbox-ose-6.1.10/vboxnetflt/vboxnetflt.ko] undefined!
ERROR: modpost: ""VBoxHost_RTTimeNanoTS"" [/usr/src/virtualbox-ose-6.1.10/vboxnetflt/vboxnetflt.ko] undefined!
ERROR: modpost: ""VBoxHost_RTSemEventDestroy"" [/usr/src/virtualbox-ose-6.1.10/vboxnetflt/vboxnetflt.ko] undefined!
ERROR: modpost: ""VBoxHost_RTThreadPreemptIsEnabled"" [/usr/src/virtualbox-ose-6.1.10/vboxnetflt/vboxnetflt.ko] undefined!
ERROR: modpost: ""VBoxHost_RTSpinlockRelease"" [/usr/src/virtualbox-ose-6.1.10/vboxnetflt/vboxnetflt.ko] undefined!
ERROR: modpost: ""VBoxHost_RTSemFastMutexDestroy"" [/usr/src/virtualbox-ose-6.1.10/vboxnetflt/vboxnetflt.ko] undefined!
ERROR: modpost: ""VBoxHost_RTMemAllocZVarTag"" [/usr/src/virtualbox-ose-6.1.10/vboxnetflt/vboxnetflt.ko] undefined!
ERROR: modpost: ""VBoxHost_RTSemFastMutexCreate"" [/usr/src/virtualbox-ose-6.1.10/vboxnetflt/vboxnetflt.ko] undefined!
ERROR: modpost: ""VBoxHost_RTR0Init"" [/usr/src/virtualbox-ose-6.1.10/vboxnetflt/vboxnetflt.ko] undefined!
ERROR: modpost: ""SUPDrvLinuxIDC"" [/usr/src/virtualbox-ose-6.1.10/vboxnetflt/vboxnetflt.ko] undefined!
ERROR: modpost: ""VBoxHost_RTSpinlockCreate"" [/usr/src/virtualbox-ose-6.1.10/vboxnetflt/vboxnetflt.ko] undefined!
ERROR: modpost: ""VBoxHost_RTNetIPv4HdrChecksum"" [/usr/src/virtualbox-ose-6.1.10/vboxnetflt/vboxnetflt.ko] undefined!
}}}

My kernel is 5.7.6, GCC is 9.3.0.
"	Alex Turbov
10014	Linux (64-bit) host, Windows 7 64-bit guest: can't execute files from shared folders	Windows	VirtualBox 4.1.6	2011-12-10T14:46:58Z	2017-03-24T20:32:11Z	2017-03-24T20:32:11Z	"With a Linux (debian 64-bit) host and a Windows 7 64-bit guest, I've enabled shared folders.  Most access works fine, and the performance is great.  However, I am not able to execute programs (.exe, etc.) or do certain other operations such as opening pdf files by double-clicking on them.  Instead, I have to copy the folders locally in order to operate on them.

I have seen other reports similar to this with Windows host and Linux or Solaris guest that can be resolved by specifying permissions at the time of mounting, but I don't see any options like this for attaching a Windows share.  (My Linux experience is much deeper than my Windows experience.)  I know that when sharing a volume on Windows, you can set things up this way, so perhaps this is intentional.  My shared folder is set as ""full"" access. "	Jay Berkenbilt
13834	linked clone - uuid already exists	Linux	VirtualBox 4.3.22	2015-02-14T09:48:11Z	2015-02-14T09:48:11Z	2015-02-14T09:48:11Z	"goodmorning, I have this problem, and I think that all versions from 4.3 are affected, because the problem doesn't .
I created 1 virtualmachine, started, SO installed, closed, everything fine.
I want a (one or more) clone of this machine, type linked-clone, so I use the procedure to create a linked-clone.
If I remove 1 of the 2 machine (remove only) and than I re-add there is the error about ""uuid already exists"" and I can't re-add the machine.
I think the problem is that each machine load all the structure of snapshots for both the machine, so if I re-add the one removed, it sais that already exists.
I have this problem with host Linux and Windows"	sigfrido.barb
18447	libffi-d78936b1.so.6.0.4: cannot open shared object file: No such file or directory	Linux	VirtualBox 6.0.4	2019-02-22T03:47:38Z	2019-02-22T03:57:05Z	2019-02-22T03:57:05Z	"Hi,

I have linux laptop with with ubuntu 18.04 OS.

          $lsb_release -a No LSB modules are available.
            Distributor ID: Ubuntu Description: Ubuntu 18.04.2 
            LTS Release: 18.04
            Codename: bionic

I have virtualBox 6 installed in it. Below is the VBox details -

Version 6.0.4 r128413 (Qt5.9.5) Copyright © 2019 Oracle Corporation and/or its affiliates. All rights reserved.


When I tried to create virtual OS using virtual Box I get below error - 

 libffi-d78936b1.so.6.0.4: cannot open shared object file: No such file or directory

I have attached the completed error trace



"	rajpsgit
8070	Less reliance on absolute paths in VirtualBox	other	VirtualBox 4.0.0	2011-01-12T09:58:58Z	2011-09-12T15:03:54Z	2011-09-12T15:03:54Z	"VirtualBox should be able to work with relative paths properly. Example: The virtualdisk was created under /home/user/.VirtualBox/VDI/mydisk.vdi
For ease of use I have symlinked /home/user/VirtualBox to /home/user/.VirtualBox, but whenever I try to work with diskimages through the symlink (/home/user/VirtualBox) I am getting errors of already registered diskimages under the hidden .VirtualBox directory.
"	mark_orion
18182	Latest Insider Build Sound Driver Broke	Windows	VirtualBox 5.2.22	2018-12-14T15:31:38Z	2018-12-26T19:16:15Z	2018-12-26T19:16:15Z	"Running build 18298, sound driver not working on Windows 10 guest, Ubuntu 18.10 host. Getting error in Device Manager:
该设备无法启动。 (代码 10)

{操作失败}
请求的操作不成功。

Or Google Translate: The device could not be started. (Code 10)

{operation failed}
The requested operation was unsuccessful.


Using Virtualbox 5.2.22 r126460."	Paul Stejskal
18597	Large icons when i drag from small to big monitor	all	VirtualBox 6.0.6	2019-04-24T17:38:46Z	2019-05-29T09:39:05Z	2019-05-29T09:39:05Z	I have a problem with virtualbox 6.0.X, when I have 2 monitors and one is 17' and monitor 2 is 32' then when I drop virtualbox from small monitor to larger then I have big icons in virtualbox. Others program works good. When I can then I send screen in attachment	liske1
21016	KUbuntu 22.04 jammy host, Virtualbox 6.1.32 Windows guest: copy and paste causes GUI to freeze	Windows	VirtualBox 6.1.34	2022-07-08T06:52:56Z	2022-08-17T07:26:38Z	2022-08-17T07:26:38Z	"I am running a windows guest in Virtual Box on Kubuntu 22.04 jammy with kernel 5.15.0-27-generic. From time to time I experience different kinds of freezes. Sometimes, when I am in the VM I can contiue to work in the VM, but can't select another window from the host. Sometimes, when I am outside of the VM I can continue to work in all windows of the host, but can't switch back to the guest. In all cases so far I was able to switch to the console (Ctrl-Alt-F2) and back to the GUI. The mouse continues to work.

Often the system went back to normal after waiting for a couple of seconds. But some times, even waiting for 10 minutes, does not solve the problem and the poweroff via the CLI from the console helps: ""VBoxManage controlvm poweroff"".

I had this problem also seldomly on KUbuntu 18.04. It was so rare that I did not bother. Now it is happening more often and I already tried to find a solution via Google.

By now I am quite certain that it is caused by copy-and-paste in the Windows VM and keeping things selected. Especially when working with Excel. This forum post seems to describe the same issue: https://forums.virtualbox.org/viewtopic.php?t=99685

I've also asked on askubuntu: https://askubuntu.com/questions/1406257/kubuntu-22-04-jammy-host-virtualbox-6-1-32-windows-guest-gui-freezes-in-both-d
At the time I thought it might be related to using shared folders, but by now I am quite certain that copy and pasting from Windows to Linux causes the problem.
"	cs224
18157	keys repeat (example: moving the cursor) will make shift or control key stick	Windows	VirtualBox 5.2.10	2018-11-29T03:14:51Z	2018-12-05T01:56:28Z	2018-12-05T01:56:28Z	"Hello,

I have a problem with the indiscriminately activation of caps-lock and/or ctrl while typing, moving the cursor or selecting text.

This symptom will happen if I use one key very long (selecting text...) . (Not often and not exact reproducible, but several times a day.)


'''Host is:'''
- Linux Mint 19 Tara / Cinnamon (freshly installed 8 Weeks ago)
- 2 different computers (physical identical and with similar installation) with the same problem!
- 16 GB Ram, i3 CPU
- ASRock H370M ITX ac / BIOS v3
- Onboard/CPU graphics
- Virtual Box 5.2.10


'''Guest is:'''
- Windows 7 (several installations (old converted computer and freshley installed also))
- Guest Additions are also installed
- USB Additions are also installed... but the issue was earlier as this installation

- no test with Linux as guest!


'''Annoying:'''
- text will be selected if virtualbox thinks that shift is pressed
OR
- the cursor jumps by word like the ctrl key is pressed

This can change in ""one session"" of this issue. (selecting ... jumping ... selecting)

 
'''
I'm able to ""solve"" the problem with:'''
continue with selecting text!  cursor right ..... cursor left ..... cursor up and down.... 
watching if text is selected (blue) while the cursor is moving the text.

No typing of Letters is possible, because every character is combinated with the ""virtual ctrl"" or the ""virtual shift"" key. Result: typing ""s"" is combinated with ctrl to: save my document... and so on.

Clicking with the mouse (on a existing document in task bar) will cause to open a very new document. I'm not able to get into an opened document with the mouse via taskbar. Every mouse-click will open an new instance of the program.



'''I can see ""this"" before the issue begins:'''
- If I move the cursor along the line the cursor has a certain speed. Very short time before the issue starts, the speed will reduce a little bit.

- While the issue is active the cursor has his regular speed.

short time before the issue ""ends"" (for an hour or two or 15 minutes) the speed of the cursor is reduced  to zero. Sometimes the issue has a continuation. Sometimes the issue ends and regular work is possible.

This can last up to 5 minutes!

The reboot of the guest is no real solution. Sometimes the issue takes part within 5 minutes.

The time itself is no factor: If I leave the computer for a while, the issue is still alive.
ONLY continuous run over the timer will solve the problem.


'''the keyboard''' 
is working fine in Linux! No ""virtual ctrl"" or ""virtual shift"" key.


'''Any open questions?'''
- what is needed? (log-files, list of installed programs, ...?)


''Any ideas?
''

regards
Linu
"	Galin
7727	Keyboard should be released to host when mouse moves outside of Vbox window	Windows	VirtualBox 3.2.10	2010-11-16T16:05:37Z	2010-11-17T08:50:27Z	2010-11-17T08:50:27Z	"Currently, it takes two user actions to release the keyboard:
  a) move mouse off the vbox window
  b) click the mouse

The mouse click is unnecessary and redundant.  Moving the mouse is a clear indication that the user wants to do something outside of the vbox guest.  Guest additions should release the keyboard to the host at this point.  Curiously, even seamless mode does not help in this respect.

This may sound trivial at first glance, but it makes things clumsy when switching back and forth between guest vbox windows and host windows.  With Vbox, it takes a careful mouse movement to a harmless place, an additional mouse click, before being able to use keyboard CUA.  Also, finding a harmless place for the extra mouse click can be a problem when using a full host taskbar and a maximized vbox guest window.

Instead, it is much easier to just move the mouse to any max position off of the vbox window, and the use keyboard shortcuts to change to a different host desktop.

As a point of reference, a Large Commercial Virtualization package works this way.  It does not require the extra mouse click."	mtnbiker
16734	Keyboard re-captured with no clear reason	Windows	VirtualBox 5.1.22	2017-05-05T16:56:11Z	2017-05-05T16:56:11Z	2017-05-05T16:56:11Z	"I'm on a laptop with classic brightness and volume control hotkeys, and when the keyboard and mouse integration is active in the guest these hotkeys don't work but that's expected, I'd say (keyboard backlight control always works, though).

So I press the host key, right ctrl, to disable integration, and that kinda works, but only for a brief moment. Meaning:

- I press host key, icon goes from green to black.
- I can wait forever and nothing happens (ok)
- I press volume up or down, volume is changed in the host
- After about 1/2 sec the icon goes back to green and integration is active, hotkeys don't work anymore in the host.

Even more strange is the behaviour with brightness control:

- I press host key, icon goes from green to black.
- I press dimming up or down ONCE, host screen is affected
- I can wait whatever time I want
- I press dimming up or down again, host screen is affected again
- After about 1/2 sec the icon goes back to green and integration is active, hotkeys don't work anymore.

Maybe it has something to do with windows focus because these hotkeys trigger on screen notifications, but the integration is reactivated well before the notification is gone, and for brightness it only happens on the second event, so the first notification does nothing.

I know it's more of an annoyance than an issue, but still..."	ctrl
15902	keyboard not working when using certain rdesktop options	Windows	VirtualBox 5.1.4	2016-09-08T06:02:40Z	2016-09-08T06:02:40Z	2016-09-08T06:02:40Z	"First of all, this problem *only* occurs on the login screen of the Windows client.
If I succeed logging into the client, the keyboard works fine.

The scenario:

I just updated the host from Ubuntu 14.04 to 16.04. 
On 14.04 I never saw this problem.
Maybe I should mention, that I upgraded Virtualbox also from 4.3.x to 5.1.4.

I have some headless Windows guests (Win 7, Win 10) - all of them have the same problem.

When I now try to connect from a Linux machine:

rdesktop -a 24 -g 1600x950 -z -N -xl -u klaus -d gbr 192.168.1.30

I see the welcome (login) screen and I'm able to use the mouse, but I cannot type in a password.

I can workaround this using the -p option:

rdesktop -a 24 -g 1600x950 -z -N -xl -u klaus -d gbr -p - 192.168.1.30

but thus is nasty, as you cannot put such stuff into a menu item (putting the password in plain text would help, but us at least as nasty).

Strange to say, that this phenomenon does *not* occur, when I omit all those user related options (-u, -d, -p). When using this commandline:

rdesktop -a 24 -g 1600x950 -z -N -xl 192.168.1.30

everything is fine. I see the login screen and can type in my credentials.
Unfortunately I have to type in all the stuff now (user, domain, password) each time ... that's annoying, but it works .... as long as noone uses one of the -u, -d, -p options.
If anyone tries to connect using one of these options, the keyboard is dead at the login screen for all subsequent connects. 
I need to poweroff/startup the guest machine to get this working again.

This is reproducable with rdesktop 1.7.1 (e.g. on LinuxMint 17.1) as well as with rdesktop 1.8.3 (e.g. on Ubuntu 16.04). Therefore I'd say this is no rdesktop problem but rather a problem of virtualbox.
I unfortunately haven't found possibilities to debug/trace those connections - that would possibly give us some more informations..."	kläuser
16733	Keyboard Layout VirtualBox 5.1 - Ubuntu 16.04 Host - Incorrect keymap	Linux	VirtualBox 5.1.22	2017-05-05T16:00:58Z	2017-05-05T16:00:58Z	2017-05-05T16:00:58Z	"Hi,

When using VirtualBox 5.1 on Ubuntu 16.04 host, the VirtualBox GUI interface does not use the correct keymap.

All other programs on the Host operate without issues.

I tried on 2 hosts and they both display the same problem.

Only solution I found was reinstall VirtualBox 5.036 that is provided by apt-get.

I also installed VirtualBox 5.1 on Centos 7 and the issue does not happen.

I will update this ticket soon when I trie on a Debian 8.7 host..."	leo.rudolph
8819	Keyboard layout 'Programmer Dvorak'	other	VirtualBox 4.0.6	2011-05-01T04:14:04Z	2011-05-03T09:18:31Z	2011-05-03T09:18:31Z	"It's not very easy to submit a bug report for VirtualBox, in my opinion. I have to open a web browser, navigate to virtualbox.org, and then find the bug-tracker. (I would have guessed that there was no bug tracker, except that VBox.log told me explicitly.) Then, I had to create an account. That last step isn't too bad per se, but by the time I've done all of these, I may well have lost or forgotten the source of the bug (e.g. error message) I was going to report in the first place--and, after all, I'm volunteering my bug sighting in the first place!

I suggest some sort of integrated bug tracker. Something that can be initiated directly from the VM manager; something with step-by-step instructions (i.e. ""wizard style"") to guide me through collecting the bug and documenting it properly; that allows me to create an account if need be--without opening a web-browser.

I've seen this done well, and it really helps the bug submitters; The ""Apport"" program for Ubuntu does this for their bug tracker. I bet it would also increase the quality and responsiveness of bug reports."	Jonathan Paugh
17668	Keyboard does not work in Linux Build 5.2.8 r121009	Windows	VirtualBox 5.2.8	2018-04-06T01:26:33Z	2018-04-11T09:49:23Z	2018-04-11T09:49:23Z	I am running build 5.2.8 r121009 on Centos 7. The keyboard stops working in the VM (I am unable to type anything in the VM) but continues to work just fine in the host OS.  The only way I can get the keyboard back is to reboot the guest operating system.  I just ran rum update and all patches are installed.	ErikJ
15729	keyboard differences in VB 5.1	Linux	VirtualBox 5.1.2	2016-08-03T07:01:19Z	2016-08-03T07:36:49Z	2016-08-03T07:36:49Z	"VB 5.1.2 r108956 on 64-bit Ubuntu 16.04, running 64-bit Ubuntu 16.04 guest with the guest additions.

Something has changed in the way keyboard handling works in VB 5.1.  Two problems that I'm guessing may be related:

'''#1)'''
In the past, the extra ""multimedia"" buttons on my USB keyboard (including the ""calculator"" button) have always worked.  They used to be handled by the host, even when the guest had focus.  In VB 5.1, those buttons don't work anymore when the guest has focus.

'''#2)'''
The other more serious keyboard change in VB 5.1 is that ALT+TAB is no longer always caught by the guest.  Instead of going between the apps in the guest, ALT+TAB is handled by the host, even when the guest has focus.  This doesn't happen 100% of the time."	Stéphane Charette
16410	Keyboard capturing sometimes not working	Windows	VirtualBox 5.1.14	2017-01-20T12:19:25Z	2017-01-20T19:04:41Z	2017-01-20T19:04:41Z	Since upgrade to 5.1.12 my keyboard is sometimes not automatically captured when I change between host and guest. I'm running a Windows 7 Professional guest on a Ubuntu 16.04 host with current host extensions installed.	Mellon
19105	Keyboard capture does not work properly under Wayland	all	VirtualBox 6.0.14	2019-11-22T11:09:16Z	2019-11-23T01:23:30Z	2019-11-23T01:23:30Z	"I am using Virtualbox on Fedora under Wayland (Gnome/Mutter). It generally works correctly apart from being able to capture all keyboard presses.

Key combinations that have meaning to the OS (Alt+Tab, Cmd key, Alt+F4 etc.) are handled by the OS and don't make it to the VM. That '''was''' previously a known issue with Wayland, but has since been fixed by providing the appropriate extension. This has been implemented by Gnome and is in use by the Gnome Boxes app to provide correct keyboard behaviour.

See these two issues for some history and context:
https://bugzilla.redhat.com/show_bug.cgi?id=1285770
https://bugs.freedesktop.org/show_bug.cgi?id=97333

Implementing the same functionality for VirtualBox would greatly improve the usability on Wayland."	WillW
20570	"Key ""accent grave"" not received in guest"	Windows	VirtualBox 6.1.26	2021-09-20T11:03:08Z	2021-09-20T12:10:30Z	2021-09-20T12:10:30Z	"When I run a Windows 10 guest on a Fedora 34 host, the ""accent grave"" key is not received at all in the guest. However, if I run the guest headless and connect over RDP using xfreerdp directly from my Fedora 34 host, the ""accent grave"" key works like normal. So something is wrong with the VirtualBox guest window on this platform.

    > vboxmanage --version
    6.1.26_RPMFusionr145957

    > uname -a
    Linux xxxxx.xxxxx.xxx 5.12.14-300.fc34.x86_64 #1 SMP Wed Jun 30 18:30:21 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux"	Byron
10686	Kernel Panic: MONITOR/MWAIT	Linux	VirtualBox 4.1.14	2012-06-20T01:56:16Z	2015-07-25T03:44:42Z	2015-07-25T03:44:42Z	"I'm running Slackware 13.37 x86 host and guest on VirtualBox 4.1.14, this is on a Sony Vaio with a Intel Core i3, and when I try to boot the Slack guest it kernel panics and gives me this message;

kernel panic not syncing: Attempted to kill the idle task!
atkbd serio0: Spurious ACK on isa0060/serio0. Some program may be trying 
to access hardware directly

I'm attaching a screen shot to this bug report you can also see.

I have a desktop running an AMD and the guest will boot and run just fine, it's only on my Vaio with the i3 that it won't boot, so I recompiled the kernel 3.4.3 hoping this would help with no luck.

I've also attached the VB log....

I also noticed that if I try to boot the Slackware 13.37 CD it too won't boot on the Sony and kernel panics and locks up as well.

I read there seems to be an issue here with Slack and i3/i5/i7 cpus?

I hope someone might know a fix for VB OSE 4.1.14 I can apply to get this to bootup?

THANKS

P.S. Since I'm running Slackware and I compiled the OSE version into a slackware package, this is the build script I used;

http://slackbuilds.org/repository/13.37/system/virtualbox/

Until this gets updated, I'm not able to use 4.1.16....

"	DasFox
16804	Kernel panic on Arch Linux guest	Linux	VirtualBox 5.1.22	2017-06-01T09:34:49Z	2017-06-01T09:34:49Z	2017-06-01T09:34:49Z	Arch Linux kernel is producing a kernel panic. A screenshot and the log is provided.	Panos Kavalagios
20441	Kernel module compilation error - VirtualBox 6.1.22 kernel 5.12.13	other	VirtualBox 6.1.22	2021-06-30T12:19:38Z	2021-07-02T08:00:08Z	2021-07-02T08:00:08Z	"I'm using AlmaLinux 8.4 (Centos clone)

kernel module compilation fails:


{{{
$ /sbin/akmodsbuild -l /tmp/akmod512 --kernels 5.12.13-1.el8.elrepo.x86_64 /usr/src/akmods/VirtualBox-kmod.latest                                                                                
* Rebuilding /usr/src/akmods/VirtualBox-kmod.latest for kernel(s) 5.12.13-1.el8.elrepo.x86_64: prep build build build                                                                                             
rpmbuild failed with errorcode 1; last 35 Lines of log:
---
  MODPOST /tmp/akmodsbuild.AO9JWwgz/BUILD/VirtualBox-kmod-6.1.22/_kmod_build_5.12.13-1.el8.elrepo.x86_64/vboxsf/Module.symvers                                                                                    
ERROR: modpost: ""VBoxGuest_RTAssertMsg2Weak"" [/tmp/akmodsbuild.AO9JWwgz/BUILD/VirtualBox-kmod-6.1.22/_kmod_build_5.12.13-1.el8.elrepo.x86_64/vboxsf/vboxsf.ko] undefined!                                         
ERROR: modpost: ""VBoxGuest_RTAssertMsg1Weak"" [/tmp/akmodsbuild.AO9JWwgz/BUILD/VirtualBox-kmod-6.1.22/_kmod_build_5.12.13-1.el8.elrepo.x86_64/vboxsf/vboxsf.ko] undefined!                                         
ERROR: modpost: ""VBoxGuest_RTSemMutexDestroy"" [/tmp/akmodsbuild.AO9JWwgz/BUILD/VirtualBox-kmod-6.1.22/_kmod_build_5.12.13-1.el8.elrepo.x86_64/vboxsf/vboxsf.ko] undefined!                                        
ERROR: modpost: ""VBoxGuest_RTSemMutexCreate"" [/tmp/akmodsbuild.AO9JWwgz/BUILD/VirtualBox-kmod-6.1.22/_kmod_build_5.12.13-1.el8.elrepo.x86_64/vboxsf/vboxsf.ko] undefined!                                         
ERROR: modpost: ""VBoxGuest_RTSemMutexRequest"" [/tmp/akmodsbuild.AO9JWwgz/BUILD/VirtualBox-kmod-6.1.22/_kmod_build_5.12.13-1.el8.elrepo.x86_64/vboxsf/vboxsf.ko] undefined!                                        
ERROR: modpost: ""VBoxGuest_RTMemContAlloc"" [/tmp/akmodsbuild.AO9JWwgz/BUILD/VirtualBox-kmod-6.1.22/_kmod_build_5.12.13-1.el8.elrepo.x86_64/vboxsf/vboxsf.ko] undefined!                                           
ERROR: modpost: ""VBoxGuest_RTLogLoggerEx"" [/tmp/akmodsbuild.AO9JWwgz/BUILD/VirtualBox-kmod-6.1.22/_kmod_build_5.12.13-1.el8.elrepo.x86_64/vboxsf/vboxsf.ko] undefined!                                            
ERROR: modpost: ""VBoxGuest_RTAssertShouldPanic"" [/tmp/akmodsbuild.AO9JWwgz/BUILD/VirtualBox-kmod-6.1.22/_kmod_build_5.12.13-1.el8.elrepo.x86_64/vboxsf/vboxsf.ko] undefined!                                      
ERROR: modpost: ""VBoxGuest_rtR0MemObjLinuxVirtToPage"" [/tmp/akmodsbuild.AO9JWwgz/BUILD/VirtualBox-kmod-6.1.22/_kmod_build_5.12.13-1.el8.elrepo.x86_64/vboxsf/vboxsf.ko] undefined!                                
ERROR: modpost: ""VBoxGuest_RTSemMutexRelease"" [/tmp/akmodsbuild.AO9JWwgz/BUILD/VirtualBox-kmod-6.1.22/_kmod_build_5.12.13-1.el8.elrepo.x86_64/vboxsf/vboxsf.ko] undefined!                                        
ERROR: modpost: ""VBoxGuest_RTMemContFree"" [/tmp/akmodsbuild.AO9JWwgz/BUILD/VirtualBox-kmod-6.1.22/_kmod_build_5.12.13-1.el8.elrepo.x86_64/vboxsf/vboxsf.ko] undefined!                                            
ERROR: modpost: ""VBoxGuest_RTSemFastMutexDestroy"" [/tmp/akmodsbuild.AO9JWwgz/BUILD/VirtualBox-kmod-6.1.22/_kmod_build_5.12.13-1.el8.elrepo.x86_64/vboxsf/vboxsf.ko] undefined!                                    
ERROR: modpost: ""VBoxGuest_RTSemFastMutexCreate"" [/tmp/akmodsbuild.AO9JWwgz/BUILD/VirtualBox-kmod-6.1.22/_kmod_build_5.12.13-1.el8.elrepo.x86_64/vboxsf/vboxsf.ko] undefined!                                     
ERROR: modpost: ""VBoxGuest_RTErrConvertToErrno"" [/tmp/akmodsbuild.AO9JWwgz/BUILD/VirtualBox-kmod-6.1.22/_kmod_build_5.12.13-1.el8.elrepo.x86_64/vboxsf/vboxsf.ko] undefined!                                      
ERROR: modpost: ""VBoxGuest_RTStrCopy"" [/tmp/akmodsbuild.AO9JWwgz/BUILD/VirtualBox-kmod-6.1.22/_kmod_build_5.12.13-1.el8.elrepo.x86_64/vboxsf/vboxsf.ko] undefined!                                                
ERROR: modpost: ""VBoxGuest_RTLogRelGetDefaultInstanceEx"" [/tmp/akmodsbuild.AO9JWwgz/BUILD/VirtualBox-kmod-6.1.22/_kmod_build_5.12.13-1.el8.elrepo.x86_64/vboxsf/vboxsf.ko] undefined!                             
ERROR: modpost: ""VBoxGuest_RTStrNLen"" [/tmp/akmodsbuild.AO9JWwgz/BUILD/VirtualBox-kmod-6.1.22/_kmod_build_5.12.13-1.el8.elrepo.x86_64/vboxsf/vboxsf.ko] undefined!                                                
ERROR: modpost: ""VBoxGuest_RTSemFastMutexRelease"" [/tmp/akmodsbuild.AO9JWwgz/BUILD/VirtualBox-kmod-6.1.22/_kmod_build_5.12.13-1.el8.elrepo.x86_64/vboxsf/vboxsf.ko] undefined!                                    
ERROR: modpost: ""VBoxGuest_RTSemFastMutexRequest"" [/tmp/akmodsbuild.AO9JWwgz/BUILD/VirtualBox-kmod-6.1.22/_kmod_build_5.12.13-1.el8.elrepo.x86_64/vboxsf/vboxsf.ko] undefined!                                    
ERROR: modpost: ""VBoxGuestIDC"" [/tmp/akmodsbuild.AO9JWwgz/BUILD/VirtualBox-kmod-6.1.22/_kmod_build_5.12.13-1.el8.elrepo.x86_64/vboxsf/vboxsf.ko] undefined!                                                       
ERROR: modpost: ""VBoxGuest_RTLogBackdoorPrintf"" [/tmp/akmodsbuild.AO9JWwgz/BUILD/VirtualBox-kmod-6.1.22/_kmod_build_5.12.13-1.el8.elrepo.x86_64/vboxsf/vboxsf.ko] undefined!                                      
make[1]: *** [scripts/Makefile.modpost:145: /tmp/akmodsbuild.AO9JWwgz/BUILD/VirtualBox-kmod-6.1.22/_kmod_build_5.12.13-1.el8.elrepo.x86_64/vboxsf/Module.symvers] Error 1                                         
make[1]: *** Deleting file '/tmp/akmodsbuild.AO9JWwgz/BUILD/VirtualBox-kmod-6.1.22/_kmod_build_5.12.13-1.el8.elrepo.x86_64/vboxsf/Module.symvers'                                                                 
make: *** [Makefile:1763: modules] Error 2
make: Leaving directory '/usr/src/kernels/5.12.13-1.el8.elrepo.x86_64'
error: Bad exit status from /var/tmp/rpm-tmp.VeA55J (%build)


RPM build errors:
    user mockbuild does not exist - using root
    group mock does not exist - using root
    user mockbuild does not exist - using root
    group mock does not exist - using root
    Bad exit status from /var/tmp/rpm-tmp.VeA55J (%build)

}}}

Building against an older kernel (5.4.128-1.el8.elrepo.x86_64) works correctly.

"	asalamon
20551	Kernel driver not installed (rc=-1908)	Windows	VirtualBox 6.1.26	2021-09-16T09:29:17Z	2021-09-16T15:13:23Z	2021-09-16T15:13:23Z	"after upgrade centos to newest version (and update virtualbox 6.1.26) I had this error when starting virtuals: ""
Kernel driver not installed (rc=-1908)

The VirtualBox Linux kernel driver is either not loaded or not set up correctly. Please try setting it up again by executing

'/sbin/vboxconfig'

as root.

If your system has EFI Secure Boot enabled you may also need to sign the kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load them. Please see your Linux system's documentation for more information.

where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT. 
""
after use ""sudo /sbin/vboxconfig"" 
I have this:
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: failed: Look at /var/log/vbox-setup.log to find out what went wrong.

There were problems setting up VirtualBox.  To re-start the set-up process, run
  /sbin/vboxconfig
as root.  If your system is using EFI Secure Boot you may need to sign the
kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load
them. Please see your Linux system's documentation for more information.
(log from file attached)
"	oszymanski
19128	Kernel bug (vboxdr - VBoxNetFlt) - eth device unintentionally enters promiscuous mode	Linux	VirtualBox 6.0.14	2019-12-03T21:42:59Z	2019-12-04T06:44:26Z	2019-12-04T06:44:26Z	"Hello, 

When a natnetwork definied. For a while, after some reboots of VM, when VM just started Linux Kernel shows problems.
It is reproducabe: make a new natnetwork eg. like this:

{{{

$ VBoxManage natnetwork add --netname anyad \
--network ""192.168.15.0/24"" --enable --ipv6 on \
--port-forward-4 ""www:tcp:[]:10080:[192.168.15.10]:80"" \
--port-forward-4 ""ssh:tcp:[]:10022:[192.168.15.10]:22"" \
--port-forward-4 ""ssl:tcp:[]:10443:[192.168.15.10]:443"" \
--port-forward-6 ""www_ipv6:tcp:[]:10080:[192.168.15.10]:80"" \
--port-forward-6 ""ssh_ipv6:tcp:[]:10022:[192.168.15.10]:22"" \
--port-forward-6 ""ssl_ipv6:tcp:[]:10443:[192.168.15.10]:443
}}}
""


{{{
$ VBoxManage dhcpserver modify --ip 192.168.15.3 --netmask 255.255.255.0 \
--netname anyad --lowerip 192.168.15.10 --upperip 192.168.15.100
}}}


Then you select natnetwork definied above for VM. After some rebootings of VM there will be Kernel messages just when you start the affected VM like this:


{{{
[ 6693.723692] vboxdrv: 0000000000000000 VMMR0.r0
[ 6693.850079] vboxdrv: 0000000000000000 VBoxDDR0.r0
[ 6693.896097] VBoxNetFlt: attached to 'enp3s0' / xx:zz:xx:zz:xx:zz
[ 6693.901656] vboxdrv: 0000000000000000 VBoxEhciR0.r0
}}}

No need VM to start the guest OS totally, as soon as VM begun to run the Kernel messages sign.
When VM will be just stopped, Kernel message will be like this:
{{{

[ 6355.406993] device enp3s0 left promiscuous mode
[ 6356.691870] vboxnetflt: 0 out of 9668 packets were not sent (directed to host)

}}}

Temporary workaround:

{{{
$ VBoxManage natnetwork remove --netname anyad
$ VBoxManage dhcpserver remove --netname anyad
}}}

After re-make a new natnetwork with same option like above I wrote.


Affected VB versions: 6.0.14 and 6.1.0_RC1 r135151[[BR]]

Affected Kernel: Linux 5.0.0-36-generic"	petervagyok
20163	kernel 5.10.11 panic at VM start, when CONFIG_DEBUG_SPINLOCK=y in kernel .config	X11	VirtualBox 6.1.18	2021-01-29T20:36:15Z	2021-02-16T18:31:10Z	2021-02-16T18:31:10Z	"this is on app-emulation/virtualbox-6.1.18::gentoo

kernel 5.10.11

No panic when CONFIG_DEBUG_SPINLOCK=n (which means CONFIG_DEBUG_LOCK_ALLOC=n also)  

Also panic when using CONFIG_DEBUG_LOCK_ALLOC=y (which forces CONFIG_DEBUG_SPINLOCK=y)  

Still panic when CONFIG_DEBUG_SPINLOCK=y and CONFIG_DEBUG_LOCK_ALLOC=n  


This has been mentioned in a comment(thanks!) in https://www.virtualbox.org/ticket/20055#comment:16

I'm happy to test any patches, or if you think the issue is on the kernel side...

Here are my notes, I'm not sure how useful all this is but I'm happy to do more things if you tell me what:

Using /usr/src/.config.prev18_DEBUGlocks
      KERNEL: /var/crash/vmlinux-5.10.11-gentoo-x86_64-2021-01-29-01_35_09
    DUMPFILE: /var/crash/crashdump-2021-01-29-01_42_27  [PARTIAL DUMP]

Below, the word ""crash"" references https://github.com/crash-utility/crash

///
dmesg seen by crash's 'log' command:
{{{
...
[   27.789537] zram1: detected capacity change from 0 to 206158430208
[   27.792783] zram2: detected capacity change from 0 to 206158430208
[   27.807234] vboxdrv: loading out-of-tree module taints kernel.
[   27.807944] vboxdrv: Found 12 processor cores
[   27.808318] ------------[ cut here ]------------
[   27.808318] DEBUG_LOCKS_WARN_ON(lockdep_hardirqs_enabled())
[   27.808325] WARNING: CPU: 4 PID: 12692 at kernel/locking/lockdep.c:5281 check_flags.part.0+0x157/0x160
[   27.808325] Modules linked in: vboxdrv(O+) pcspkr
[   27.808328] CPU: 4 PID: 12692 Comm: modprobe Tainted: G     U     O      5.10.11-gentoo-x86_64 #1
[   27.808329] Hardware name: System manufacturer System Product Name/PRIME Z370-A, BIOS 2401 07/12/2019
[   27.808330] RIP: 0010:check_flags.part.0+0x157/0x160
[   27.808331] Code: c0 0f 84 3f 9c 04 01 44 8b 0d 0d cf 7c 02 45 85 c9 0f 85 2f 9c 04 01 48 c7 c6 2f 22 d3 9a 48 c7 c7 cb e5 d1 9a e8 82 52 04 01 <0f> 0b e9 15 9c 04 01 66 90 41 57 41 56 49 89 fe 41 55 41 89 d5 41
[   27.808332] RSP: 0018:ffffb32948e37a10 EFLAGS: 00010082
[   27.808333] RAX: 0000000000000000 RBX: 0000000000000001 RCX: 0000000000000000
[   27.808334] RDX: 0000000000000000 RSI: ffffffff991424fc RDI: ffffffff9b065d40
[   27.808334] RBP: ffffffff9b768300 R08: 0000000000000001 R09: 0000000000000000
[   27.808335] R10: 0000000000000000 R11: fffffffffe02e9f8 R12: 0000000000000001
[   27.808335] R13: 0000000000000000 R14: ffffffff9b76c688 R15: 0000000000000046
[   27.808336] FS:  00007bcdb219fb80(0000) GS:ffff996609800000(0000) knlGS:0000000000000000
[   27.808337] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   27.808338] CR2: 00007bcdb232f445 CR3: 00000002d416e005 CR4: 00000000001706e0
[   27.808338] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[   27.808339] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[   27.808339] Call Trace:
[   27.808342]  ? lock_is_held_type+0x65/0x110
[   27.808344]  ? rcu_read_lock_sched_held+0x3a/0x70
[   27.808345]  ? lock_acquire+0x39a/0x480
[   27.808347]  ? ktime_get_ts64+0x46/0x280
[   27.808355]  ? VBoxHost_RTTimeSystemNanoTS+0x30/0x60 [vboxdrv]
[   27.808360]  ? VBoxHost_RTTimeSystemNanoTS+0x30/0x60 [vboxdrv]
[   27.808365]  ? supdrvLdrGetExportedSymbol+0x3342/0x3640 [vboxdrv]
[   27.808369]  ? supdrvGipCreate+0x820/0xc50 [vboxdrv]
[   27.808370]  ? rcu_read_lock_sched_held+0x3a/0x70
[   27.808371]  ? lockdep_init_map_waits+0x42/0x200
[   27.808375]  ? supdrvInitDevExt+0x14a/0x310 [vboxdrv]
[   27.808380]  ? init_module+0x91/0x1000 [vboxdrv]
[   27.808380]  ? 0xffffffffc0297000
[   27.808382]  ? do_one_initcall+0x7a/0x2d0
[   27.808383]  ? do_init_module+0x57/0x230
[   27.808384]  ? load_module+0x2445/0x26e0
[   27.808386]  ? __do_sys_finit_module+0xc0/0x100
[   27.808387]  ? do_syscall_64+0x33/0x40
[   27.808388]  ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
[   27.808388] irq event stamp: 5085
[   27.808390] hardirqs last  enabled at (5085): [<ffffffff99167cd5>] ktime_get_ts64+0x205/0x280
[   27.808390] hardirqs last disabled at (5084): [<ffffffff99167c9d>] ktime_get_ts64+0x1cd/0x280
[   27.808391] softirqs last  enabled at (5000): [<ffffffff9a400eff>] asm_call_irq_on_stack+0xf/0x20
[   27.808392] softirqs last disabled at (4995): [<ffffffff9a400eff>] asm_call_irq_on_stack+0xf/0x20
[   27.808392] ---[ end trace 3f8fdc7480d9e05c ]---
[   27.808393] possible reason: unannotated irqs-off.
[   27.808393] irq event stamp: 5085
[   27.808394] hardirqs last  enabled at (5085): [<ffffffff99167cd5>] ktime_get_ts64+0x205/0x280
[   27.808395] hardirqs last disabled at (5084): [<ffffffff99167c9d>] ktime_get_ts64+0x1cd/0x280
[   27.808395] softirqs last  enabled at (5000): [<ffffffff9a400eff>] asm_call_irq_on_stack+0xf/0x20
[   27.808396] softirqs last disabled at (4995): [<ffffffff9a400eff>] asm_call_irq_on_stack+0xf/0x20
[   27.823374] zram3: detected capacity change from 0 to 206158430208
[   27.824878] vboxdrv: TSC mode is Invariant, tentative frequency 3714564013 Hz
[   27.830217] xhci_hcd 0000:00:14.0: Cancel URB 00000000493c99df, dev 14, ep 0x81, starting at offset 0xfff92010
[   27.831594] vboxdrv: Successfully loaded version 6.1.18 (interface 0x00300000)
[   27.833271] xhci_hcd 0000:00:14.0: // Ding dong!
...
[   57.854519] elogind-daemon[13194]: New session 2 of user user.
[   62.295045] i2c i2c-1: NAK from device addr 0x50 msg #0
[   62.298587] i2c i2c-0: NAK from device addr 0x50 msg #0
[   62.302129] i2c i2c-2: NAK from device addr 0x50 msg #0
[   62.331645] snd_hda_intel 0000:00:1f.3: power state changed by ACPI to D0
[   62.344256] snd_hda_intel 0000:00:1f.3: PME# disabled
[   71.473189] snd_hda_intel 0000:00:1f.3: saving config space at offset 0x0 (reading 0xa2f08086)
[   71.473206] snd_hda_intel 0000:00:1f.3: saving config space at offset 0x4 (reading 0x100406)
[   71.473215] snd_hda_intel 0000:00:1f.3: saving config space at offset 0x8 (reading 0x4030000)
[   71.473223] snd_hda_intel 0000:00:1f.3: saving config space at offset 0xc (reading 0x2010)
[   71.473230] snd_hda_intel 0000:00:1f.3: saving config space at offset 0x10 (reading 0xfff20004)
[   71.473238] snd_hda_intel 0000:00:1f.3: saving config space at offset 0x14 (reading 0x2f)
[   71.473258] snd_hda_intel 0000:00:1f.3: saving config space at offset 0x18 (reading 0x0)
[   71.473260] snd_hda_intel 0000:00:1f.3: saving config space at offset 0x1c (reading 0x0)
[   71.473263] snd_hda_intel 0000:00:1f.3: saving config space at offset 0x20 (reading 0xfff00004)
[   71.473265] snd_hda_intel 0000:00:1f.3: saving config space at offset 0x24 (reading 0x2f)
[   71.473267] snd_hda_intel 0000:00:1f.3: saving config space at offset 0x28 (reading 0x0)
[   71.473270] snd_hda_intel 0000:00:1f.3: saving config space at offset 0x2c (reading 0x87241043)
[   71.473272] snd_hda_intel 0000:00:1f.3: saving config space at offset 0x30 (reading 0x0)
[   71.473274] snd_hda_intel 0000:00:1f.3: saving config space at offset 0x34 (reading 0x50)
[   71.473277] snd_hda_intel 0000:00:1f.3: saving config space at offset 0x38 (reading 0x0)
[   71.473279] snd_hda_intel 0000:00:1f.3: saving config space at offset 0x3c (reading 0x10b)
[   71.473297] snd_hda_intel 0000:00:1f.3: PME# enabled
[   71.485469] snd_hda_intel 0000:00:1f.3: power state changed by ACPI to D3hot
[   72.024850] SUPR0GipMap: fGetGipCpu=0x1b
[   73.474107] BUGGY: kernel NULL pointer dereference, address: 0000000000000004
[   73.474120] #PF: supervisor read access in kernel mode
[   73.474126] #PF: error_code(0x0000) - not-present page
[   73.474131] PGD 0 P4D 0 
[   73.474143] Oops: 0000 [#1] SMP NOPTI
[   73.474151] CPU: 2 PID: 14833 Comm: EMT-0 Kdump: loaded Tainted: G     U  W  O      5.10.11-gentoo-x86_64 #1
[   73.474157] Hardware name: System manufacturer System Product Name/PRIME Z370-A, BIOS 2401 07/12/2019
[   73.474174] RIP: 0010:do_raw_spin_lock+0x4/0x90
[   73.474181] Code: 48 8d 88 b8 06 00 00 48 c7 c7 58 48 d3 9a e8 79 3a 04 01 e9 5b 3b 06 01 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 53 48 89 fb <8b> 47 04 3d ad 4e ad de 75 46 48 8b 53 10 65 48 8b 04 25 00 6f 01
[   73.474187] RSP: 0018:ffffb3294a0ebd30 EFLAGS: 00010296
[   73.474194] RAX: ffffffff992838a1 RBX: 0000000000000000 RCX: 0000000000000000
[   73.474199] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
[   73.474204] RBP: ffffb3294a0ebdf8 R08: 0000000000000001 R09: 0000000000000000
[   73.474209] R10: ffffffffc026f760 R11: 000000000007b438 R12: ffffffffc0240080
[   73.474213] R13: ffffb3294bea1000 R14: 0000000000000001 R15: ffffb3294a0ebde0
[   73.474220] FS:  0000754d3c1f4640(0000) GS:ffff996609600000(0000) knlGS:0000000000000000
[   73.474225] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   73.474230] CR2: 0000000000000004 CR3: 00000002d7102004 CR4: 00000000001706e0
[   73.474234] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[   73.474239] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[   73.474243] Call Trace:
[   73.474255]  ? __apply_to_page_range+0x2e1/0x6a0
[   73.474286]  ? rtR0TermNative+0xd0/0x220 [vboxdrv]
[   73.474313]  ? rtR0MemObjNativeProtect+0x74/0xa0 [vboxdrv]
[   73.474338]  ? VBoxHost_RTR0MemObjProtect+0x81/0xc0 [vboxdrv]
[   73.474360]  ? supdrvIOCtl+0x3265/0x3800 [vboxdrv]
[   73.474379]  ? SUPR0Printf+0x22f/0x330 [vboxdrv]
[   73.474388]  ? __x64_sys_ioctl+0x7e/0xb0
[   73.474395]  ? do_syscall_64+0x33/0x40
[   73.474402]  ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
[   73.474407] Modules linked in: vboxnetadp(O) vboxnetflt(O) vboxdrv(O) pcspkr
[   73.474425] CR2: 0000000000000004
}}}
(it ended here)

///
Partial output of crash's ""bt -sFlxg"":
{{{
PID: 14833  TASK: ffff9959886acf80  CPU: 2   COMMAND: ""EMT-0""
 #0 [ffffb3294a0eba68] machine_kexec+0x191 at ffffffff9904d3b1
    /usr/src/linux-5.10.11-gentoo/arch/x86/include/asm/mem_encrypt.h: 77
    ffffb3294a0eba70: 0000000000000018 0000ffff99574000 
    ffffb3294a0eba80: ffff995740000000 0000000f0a001000 
    ffffb3294a0eba90: ffff99664a001000 0000000f0a000000 
    ffffb3294a0ebaa0: 0000000000000000 cc4567c5b1908400 
    ffffb3294a0ebab0: ffffb3294a0ebc88 ffffb3294a0ebc88 
    ffffb3294a0ebac0: 0000000000000009 __crash_kexec+225 
 #1 [ffffb3294a0ebac8] __crash_kexec+0xe1 at ffffffff99188a21
    /usr/src/linux-5.10.11-gentoo/kernel/kexec_core.c: 963
    ffffb3294a0ebad0: ffffb3294a0ebde0 0000000000000001 
    ffffb3294a0ebae0: ffffb3294bea1000 rtR0TermNative+208 
    ffffb3294a0ebaf0: ffffb3294a0ebdf8 0000000000000000 
    ffffb3294a0ebb00: 000000000007b438 __this_module+992 
    ffffb3294a0ebb10: 0000000000000000 0000000000000001 
    ffffb3294a0ebb20: __apply_to_page_range+737 0000000000000000 
    ffffb3294a0ebb30: 0000000000000000 0000000000000000 
    ffffb3294a0ebb40: 0000000000000000 ffffffffffffffff 
    ffffb3294a0ebb50: do_raw_spin_lock+4 0000000000000010 
    ffffb3294a0ebb60: 0000000000010296 ffffb3294a0ebd30 
    ffffb3294a0ebb70: 0000000000000018 cc4567c5b1908400 
    ffffb3294a0ebb80: 0000000000000046 crash_kexec+52   
 #2 [ffffb3294a0ebb88] crash_kexec+0x34 at ffffffff99189954
    /usr/src/linux-5.10.11-gentoo/arch/x86/include/asm/atomic.h: 41
    ffffb3294a0ebb90: ffffb3294a0ebc88 oops_end+132     
 #3 [ffffb3294a0ebb98] oops_end+0x84 at ffffffff99022034
    /usr/src/linux-5.10.11-gentoo/arch/x86/kernel/dumpstack.c: 359
    ffffb3294a0ebba0: [task_struct]    ffffb3294a0ebc88 
    ffffb3294a0ebbb0: 0000000000000004 no_context+572   
    ffffb3294a0ebbc0: 0000000000000000 contig_page_data+3600 
    ffffb3294a0ebbd0: 0000000000000004 0000000000000000 
    ffffb3294a0ebbe0: 0000000000000000 0000000000000000 
    ffffb3294a0ebbf0: cc4567c5b1908400 0000000000000000 
    ffffb3294a0ebc00: ffffb3294a0ebc88 0000000000000000 
    ffffb3294a0ebc10: 0000000000000004 0000000000000000 
    ffffb3294a0ebc20: [mm_struct]      exc_page_fault+732 
 #4 [ffffb3294a0ebc28] exc_page_fault+0x2dc at ffffffff9a22a69c
    /usr/src/linux-5.10.11-gentoo/arch/x86/mm/fault.c: 1320
    ffffb3294a0ebc30: 0000000000000000 0000000000000000 
    ffffb3294a0ebc40: 0000000000000000 00042cc000000000 
    ffffb3294a0ebc50: 0000000000000000 0000000000000000 
    ffffb3294a0ebc60: 0000000000000000 0000000000000000 
    ffffb3294a0ebc70: 0000000000000000 0000000000000000 
    ffffb3294a0ebc80: asm_exc_page_fault+27 
 #5 [ffffb3294a0ebc80] asm_exc_page_fault+0x1b at ffffffff9a400acb
    /usr/src/linux-5.10.11-gentoo/arch/x86/include/asm/idtentry.h: 583
    ffffb3294a0ebc88: ffffb3294a0ebde0 0000000000000001 
    ffffb3294a0ebc98: ffffb3294bea1000 rtR0TermNative+208 
 #6 [ffffb3294a0ebca0] rtR0TermNative+0xd0 at ffffffffc0240080 [vboxdrv]
    ffffb3294a0ebca8: ffffb3294a0ebdf8 0000000000000000 
    ffffb3294a0ebcb8: 000000000007b438 __this_module+992 
    ffffb3294a0ebcc8: 0000000000000000 0000000000000001 
    ffffb3294a0ebcd8: __apply_to_page_range+737 
 #7 [ffffb3294a0ebcd8] __apply_to_page_range+0x2e1 at ffffffff992838a1
    /usr/src/linux-5.10.11-gentoo/include/linux/spinlock.h: 354
    ffffb3294a0ebce0: 0000000000000000 0000000000000000 
    ffffb3294a0ebcf0: 0000000000000000 0000000000000000 
    ffffb3294a0ebd00: ffffffffffffffff do_raw_spin_lock+4 
    ffffb3294a0ebd10: 0000000000000010 0000000000010296 
    ffffb3294a0ebd20: ffffb3294a0ebd30 0000000000000018 
    ffffb3294a0ebd30: ffffb3294beed000 __apply_to_page_range+737 
    ffffb3294a0ebd40: ffff9958401012f8 ffffb3294beed000 
    ffffb3294a0ebd50: [mm_struct]      ffff995858f00508 
    ffffb3294a0ebd60: 0000000000000000 ffffb3294beecfff 
    ffffb3294a0ebd70: ffffb3294beed000 ffff995840000528 
    ffffb3294a0ebd80: ffffb3294beed000 ffff995a17102b30 
    ffffb3294a0ebd90: ffffb3294beecfff rtR0TermNative+208 
 #8 [ffffb3294a0ebd98] rtR0TermNative+0xd0 at ffffffffc0240080 [vboxdrv]
    ffffb3294a0ebda0: ffffb3294beecfff [kmalloc-8k]     
    ffffb3294a0ebdb0: ffffb3294a0ebdf8 0000000000000000 
    ffffb3294a0ebdc0: 0000000000000000 ffffb3294c609010 
    ffffb3294a0ebdd0: [kmalloc-192]    rtR0MemObjNativeProtect+116 
 #9 [ffffb3294a0ebdd8] rtR0MemObjNativeProtect+0x74 at ffffffffc0241774 [vboxdrv]
    ffffb3294a0ebde0: [kmalloc-8k]     8000000000000161 
    ffffb3294a0ebdf0: cc4567c5b1908400 ffffb3294a0ebe10 
    ffffb3294a0ebe00: VBoxHost_RTR0MemObjProtect+129 
#10 [ffffb3294a0ebe00] VBoxHost_RTR0MemObjProtect+0x81 at ffffffffc023ecd1 [vboxdrv]
    ffffb3294a0ebe08: __this_module+992 ffffb3294a0ebea8 
    ffffb3294a0ebe18: supdrvIOCtl+12901 
#11 [ffffb3294a0ebe18] supdrvIOCtl+0x3265 at ffffffffc02339a5 [vboxdrv]
    ffffb3294a0ebe20: 0000000000000004 [kmalloc-2k]     
    ffffb3294a0ebe30: __this_module+992 00000004001fc060 
    ffffb3294a0ebe40: 00000000000004ff 0000000000205900 
    ffffb3294a0ebe50: __this_module+992 0000000000000000 
    ffffb3294a0ebe60: 0000000000000000 0000000000000000 
    ffffb3294a0ebe70: ffffb3294a0ebea8 cc4567c5b1908400 
    ffffb3294a0ebe80: 0000000000205978 0000000000005684 
    ffffb3294a0ebe90: 0000754d24911010 [kmalloc-2k]     
    ffffb3294a0ebea0: ffffb3294c609010 ffffb3294a0ebf08 
    ffffb3294a0ebeb0: SUPR0Printf+559  
#12 [ffffb3294a0ebeb0] SUPR0Printf+0x22f at ffffffffc022b67f [vboxdrv]
    RIP: 0000754d82eb9e37  RSP: 0000754d3c1f2b58  RFLAGS: 00000246
    RAX: ffffffffffffffda  RBX: 0000754d24911010  RCX: 0000754d82eb9e37
    RDX: 0000754d24911010  RSI: 0000000000005684  RDI: 000000000000000b
    RBP: 0000754d3c1f2b70   R8: 0000000000000000   R9: 00000000fffffffc
    R10: 0000000000000000  R11: 0000000000000246  R12: 0000754d6ef3afcf
    R13: 0000000000000000  R14: 0000754d3c1f2e20  R15: 0000000000000004
    ORIG_RAX: 0000000000000010  CS: 0033  SS: 002b
}}}
///
{{{
crash> mod
     MODULE       NAME              BASE          SIZE  OBJECT FILE
ffffffffc0225100  pcspkr      ffffffffc0223000   16384  (not loaded)  [CONFIG_KALLSYMS]
ffffffffc026f380  vboxdrv     ffffffffc022b000  438272  (not loaded)  [CONFIG_KALLSYMS]
ffffffffc02b0040  vboxnetflt  ffffffffc02ab000   28672  (not loaded)  [CONFIG_KALLSYMS]
ffffffffc02b9180  vboxnetadp  ffffffffc02b7000   28672  (not loaded)  [CONFIG_KALLSYMS]
}}}
///
{{{
crash> add-symbol-file /usr/lib/debug/lib/modules/5.10.11-gentoo-x86_64/misc/vboxdrv.ko.debug 0xffffffffc022b000
add symbol table from file ""/usr/lib/debug/lib/modules/5.10.11-gentoo-x86_64/misc/vboxdrv.ko.debug"" at
        .text_addr = 0xffffffffc022b000
Reading symbols from /usr/lib/debug/lib/modules/5.10.11-gentoo-x86_64/misc/vboxdrv.ko.debug...done.
}}}
///
{{{
crash> info line *rtR0TermNative+0xd0
Line 540 of ""/usr/src/debug/app-emulation/virtualbox-modules-6.1.18/vboxdrv/r0drv/linux/memobj-r0drv-linux.c"" starts at address 0xffffffffc0240080 <rtR0MemObjLinuxApplyPageRange> and ends at 0xffffffffc0240084 <rtR0MemObjLinuxApplyPageRange+4>.
crash> info line *rtR0MemObjLinuxApplyPageRange+4
Line 542 of ""/usr/src/debug/app-emulation/virtualbox-modules-6.1.18/vboxdrv/r0drv/linux/memobj-r0drv-linux.c"" starts at address 0xffffffffc0240084 <rtR0MemObjLinuxApplyPageRange+4> and ends at 0xffffffffc0240087 <rtR0MemObjLinuxApplyPageRange+7>.
}}}
{{{
  /**                                                                                                                                    
   * Callback called in apply_to_page_range().                                                                                           
   *                                                                                                                                     
   * @returns Linux status code.                                                                                                         
   * @param   pPte                Pointer to the page table entry for the given address.                                                 
   * @param   uAddr               The address to apply the new protection to.                                                            
   * @param   pvUser              The opaque user data.                                                                                  
   */                                                                                                                                    
  static DECLCALLBACK(int) rtR0MemObjLinuxApplyPageRange(pte_t *pPte, unsigned long uAddr, void *pvUser)                                 
  { //this is line 540                                                                                                                   
      PCLNXAPPLYPGRANGE pArgs = (PCLNXAPPLYPGRANGE)pvUser;                                                                               
      PRTR0MEMOBJLNX pMemLnx = pArgs->pMemLnx;  //this is line 542                                                                                         
      size_t idxPg = (uAddr - (unsigned long)pMemLnx->Core.pv) >> PAGE_SHIFT;                                                            
                                                                                                                                         
      set_pte(pPte, mk_pte(pMemLnx->apPages[idxPg], pArgs->fPg));                                                                        
      return 0;                                                                                                                          
  }                                                                                                                                      
  #endif
}}}
///
{{{
crash> info line *rtR0TermNative+208
Line 540 of ""/usr/src/debug/app-emulation/virtualbox-modules-6.1.18/vboxdrv/r0drv/linux/memobj-r0drv-linux.c"" starts at address 0xffffffffc0240080 <rtR0MemObjLinuxApplyPageRange> and ends at 0xffffffffc0240084 <rtR0MemObjLinuxApplyPageRange+4>.
(ok this doesn't seem to be useful?)
}}}
///
{{{
crash> info line *rtR0TermNative
Line 117 of ""/usr/src/debug/app-emulation/virtualbox-modules-6.1.18/vboxdrv/r0drv/linux/initterm-r0drv-linux.c"" starts at address 0xffffffffc023ffb0 <rtR0TermNative> and ends at 0xffffffffc023ffb4 <rtR0TermNative+4>.

  DECLHIDDEN(void) rtR0TermNative(void)                                                                                                  
  { //this is line 117                                                                                                                   
      IPRT_LINUX_SAVE_EFL_AC();                                                                                                          
                                                                                                                                         
      rtR0LnxWorkqueueFlush();                                                                                                           
  #if RTLNX_VER_MIN(2,5,41)                                                                                                              
      destroy_workqueue(g_prtR0LnxWorkQueue);                                                                                            
      g_prtR0LnxWorkQueue = NULL;                                                                                                        
  #endif                                                                                                                                 
                                                                                                                                         
      rtR0MemExecCleanup();                                                                                                              
                                                                                                                                         
      IPRT_LINUX_RESTORE_EFL_AC();                                                                                                       
  }
}}}
///
{{{
crash> info line *__apply_to_page_range+0x2e1
No line number information available for address 0xffffffff992838a1
(don't know how to make this work, tho it does work in the output of 'bt -l')
crash> sym 0xffffffff992838a1
ffffffff992838a1 (t) __apply_to_page_range+737 /usr/src/linux-5.10.11-gentoo/include/linux/spinlock.h: 354
crash> info line *__apply_to_page_range+737
No line number information available for address 0xffffffff992838a1
//ok so 0x2e1 is 737 in decimal
crash> sym 0xffffffff992838a1
ffffffff992838a1 (t) __apply_to_page_range+737 /usr/src/linux-5.10.11-gentoo/include/linux/spinlock.h: 354

 #7 [ffffb3294a0ebcd8] __apply_to_page_range+0x2e1 at ffffffff992838a1
    /usr/src/linux-5.10.11-gentoo/include/linux/spinlock.h: 354

  static __always_inline void spin_lock(spinlock_t *lock)                                                                                
  {                                                                                                                                      
    raw_spin_lock(&lock->rlock); // this is line 354                                                                                     
  }
}}}
///
---------------
Another crash, now with the following .config diff (compared to /usr/src/.config.prev18_nondebug):

{{{
-CONFIG_DEBUG_LOCK_ALLOC=y
-CONFIG_LOCKDEP=y
-# CONFIG_DEBUG_LOCKDEP is not set
+# CONFIG_DEBUG_LOCK_ALLOC is not set
}}}
      KERNEL: /var/crash/vmlinux-5.10.11-gentoo-x86_64-2021-01-29-19_54_43

    DUMPFILE: /var/crash/crashdump-2021-01-29-20_22_50  [PARTIAL DUMP]

'log' partial output:
{{{
...
[   14.857357] vboxdrv: loading out-of-tree module taints kernel.
[   14.857929] vboxdrv: Found 12 processor cores
[   14.873771] vboxdrv: TSC mode is Invariant, tentative frequency 3695998457 Hz
[   14.873771] vboxdrv: Successfully loaded version 6.1.18 (interface 0x00300000)
...
[   56.083785] snd_hda_intel 0000:00:1f.3: power state changed by ACPI to D3hot
[   61.037910] SUPR0GipMap: fGetGipCpu=0x1b
[   62.739845] BUGGY: kernel NULL pointer dereference, address: 0000000000000004
[   62.739856] #PF: supervisor read access in kernel mode
[   62.739862] #PF: error_code(0x0000) - not-present page
[   62.739866] PGD 0 P4D 0 
[   62.739876] Oops: 0000 [#1] SMP NOPTI
[   62.739883] CPU: 9 PID: 14846 Comm: EMT-0 Kdump: loaded Tainted: G     U     O      5.10.11-gentoo-x86_64 #1
[   62.739887] Hardware name: System manufacturer System Product Name/PRIME Z370-A, BIOS 2401 07/12/2019
[   62.739897] RIP: 0010:do_raw_spin_lock+0x4/0x90
[   62.739904] Code: 48 8d 88 90 06 00 00 48 c7 c7 f0 c7 aa 94 e8 f6 be e4 00 e9 33 b4 e6 00 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 53 48 89 fb <8b> 47 04 3d ad 4e ad de 75 46 48 8b 53 10 65 48 8b 04 25 40 6d 01
[   62.739909] RSP: 0018:ffffb532498a7d30 EFLAGS: 00010286
[   62.739915] RAX: ffff997800000588 RBX: 0000000000000000 RCX: 0000000000000000
[   62.739920] RDX: 0000000101207067 RSI: 00000000040481c0 RDI: 0000000000000000
[   62.739923] RBP: ffffb532498a7df8 R08: ffff997901207588 R09: 0000000000000001
[   62.739927] R10: ffffffffc0273560 R11: 0000000000061918 R12: ffffffffc0244000
[   62.739931] R13: ffffb532498b1000 R14: 0000000000000001 R15: ffffb532498a7de0
[   62.739937] FS:  0000751ec8366640(0000) GS:ffff99880a480000(0000) knlGS:0000000000000000
[   62.739941] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   62.739945] CR2: 0000000000000004 CR3: 000000032b99c004 CR4: 00000000001706e0
[   62.739949] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[   62.739954] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[   62.739957] Call Trace:
[   62.739967]  ? __apply_to_page_range+0x2e1/0x6a0
[   62.739999]  ? rtR0TermNative+0xd0/0x220 [vboxdrv]
[   62.740026]  ? rtR0MemObjNativeProtect+0x74/0xa0 [vboxdrv]
[   62.740051]  ? VBoxHost_RTR0MemObjProtect+0x81/0xc0 [vboxdrv]
[   62.740074]  ? supdrvIOCtl+0x3265/0x3800 [vboxdrv]
[   62.740094]  ? SUPR0Printf+0x22f/0x330 [vboxdrv]
[   62.740101]  ? __x64_sys_ioctl+0x7e/0xb0
[   62.740109]  ? do_syscall_64+0x33/0x40
[   62.740117]  ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
[   62.740121] Modules linked in: vboxnetadp(O) vboxnetflt(O) vboxdrv(O) pcspkr
[   62.740136] CR2: 0000000000000004
}}}
{{{
crash> bt -l
PID: 14846  TASK: ffff99792fa78000  CPU: 9   COMMAND: ""EMT-0""
 #0 [ffffb532498a7a68] machine_kexec at ffffffff93042956
    /usr/src/linux-5.10.11-gentoo/arch/x86/include/asm/mem_encrypt.h: 77
 #1 [ffffb532498a7ac8] __crash_kexec at ffffffff9314bee1
    /usr/src/linux-5.10.11-gentoo/kernel/kexec_core.c: 963
 #2 [ffffb532498a7b88] crash_kexec at ffffffff9314cdf4
    /usr/src/linux-5.10.11-gentoo/arch/x86/include/asm/atomic.h: 41
 #3 [ffffb532498a7b98] oops_end at ffffffff9301cd84
    /usr/src/linux-5.10.11-gentoo/arch/x86/kernel/dumpstack.c: 359
 #4 [ffffb532498a7c28] exc_page_fault at ffffffff94002016
    /usr/src/linux-5.10.11-gentoo/arch/x86/mm/fault.c: 1346
 #5 [ffffb532498a7c80] asm_exc_page_fault at ffffffff94200acb
    /usr/src/linux-5.10.11-gentoo/arch/x86/include/asm/idtentry.h: 583
 #6 [ffffb532498a7ca0] rtR0TermNative at ffffffffc0244000 [vboxdrv]
 #7 [ffffb532498a7d08] do_raw_spin_lock at ffffffff9310dc54
    /usr/src/linux-5.10.11-gentoo/kernel/locking/spinlock_debug.c: 112
 #8 [ffffb532498a7d38] __apply_to_page_range at ffffffff931feb71
    /usr/src/linux-5.10.11-gentoo/include/linux/spinlock.h: 354
 #9 [ffffb532498a7dd8] rtR0MemObjNativeProtect at ffffffffc02456f4 [vboxdrv]
#10 [ffffb532498a7e00] VBoxHost_RTR0MemObjProtect at ffffffffc0242c81 [vboxdrv]
#11 [ffffb532498a7e18] supdrvIOCtl at ffffffffc0237955 [vboxdrv]
#12 [ffffb532498a7eb0] SUPR0Printf at ffffffffc022f62f [vboxdrv]
    RIP: 0000751f0b85ae37  RSP: 0000751ec8364b58  RFLAGS: 00000246
    RAX: ffffffffffffffda  RBX: 0000751ead314010  RCX: 0000751f0b85ae37
    RDX: 0000751ead314010  RSI: 0000000000005684  RDI: 000000000000000b
    RBP: 0000751ec8364b70   R8: 0000000000000000   R9: 00000000fffffffc
    R10: 0000000000000000  R11: 0000000000000246  R12: 0000751efc3aefcf
    R13: 0000000000000000  R14: 0000751ec8364e20  R15: 0000000000000004
    ORIG_RAX: 0000000000000010  CS: 0033  SS: 002b
}}}
///

{{{
 /*                                                                                                                                     
   * We are now relying on the NMI watchdog to detect lockup instead of doing                                                            
   * the detection here with an unfair lock which can cause problem of its own.                                                          
   */                                                                                                                                    
  void do_raw_spin_lock(raw_spinlock_t *lock)                                                                                            
  {                                                                                                                                      
    debug_spin_lock_before(lock); // this is line 112                                                                                    
    arch_spin_lock(&lock->raw_lock);                                                                                                     
    mmiowb_spin_lock();                                                                                                                  
    debug_spin_lock_after(lock);                                                                                                         
  }
}}}
///
{{{
PID: 14846  TASK: ffff99792fa78000  CPU: 9   COMMAND: ""EMT-0""
 #0 [ffffb532498a7a68] machine_kexec+0x186 at ffffffff93042956
    /usr/src/linux-5.10.11-gentoo/arch/x86/include/asm/mem_encrypt.h: 77
    ffffb532498a7a70: 00000000498a7d30 0000ffff99780000 
    ffffb532498a7a80: ffff997800000000 000000003d001000 
    ffffb532498a7a90: ffff99783d001000 000000003d000000 
    ffffb532498a7aa0: 0000000000000000 c2c563b4d1c59e00 
    ffffb532498a7ab0: ffffb532498a7c88 ffffb532498a7c88 
    ffffb532498a7ac0: 0000000000000009 __crash_kexec+225 
 #1 [ffffb532498a7ac8] __crash_kexec+0xe1 at ffffffff9314bee1
    /usr/src/linux-5.10.11-gentoo/kernel/kexec_core.c: 963
    ffffb532498a7ad0: ffffb532498a7de0 0000000000000001 
    ffffb532498a7ae0: ffffb532498b1000 rtR0TermNative+208 
    ffffb532498a7af0: ffffb532498a7df8 0000000000000000 
    ffffb532498a7b00: 0000000000061918 __this_module+864 
    ffffb532498a7b10: 0000000000000001 ffff997901207588 
    ffffb532498a7b20: ffff997800000588 0000000000000000 
    ffffb532498a7b30: 0000000101207067 00000000040481c0 
    ffffb532498a7b40: 0000000000000000 ffffffffffffffff 
    ffffb532498a7b50: do_raw_spin_lock+4 0000000000000010 
    ffffb532498a7b60: 0000000000010286 ffffb532498a7d30 
    ffffb532498a7b70: 0000000000000018 c2c563b4d1c59e00 
    ffffb532498a7b80: 0000000000000246 crash_kexec+52   
 #2 [ffffb532498a7b88] crash_kexec+0x34 at ffffffff9314cdf4
    /usr/src/linux-5.10.11-gentoo/arch/x86/include/asm/atomic.h: 41
    ffffb532498a7b90: ffffb532498a7c88 oops_end+132     
 #3 [ffffb532498a7b98] oops_end+0x84 at ffffffff9301cd84
    /usr/src/linux-5.10.11-gentoo/arch/x86/kernel/dumpstack.c: 359
    ffffb532498a7ba0: [task_struct]    ffffb532498a7c88 
    ffffb532498a7bb0: 0000000000000004 no_context+572   
    ffffb532498a7bc0: 0000000000000000 0000000000000000 
    ffffb532498a7bd0: 0000000000000000 0000000000000000 
    ffffb532498a7be0: 0000000000000000 0000000000000000 
    ffffb532498a7bf0: c2c563b4d1c59e00 0000000000000214 
    ffffb532498a7c00: 0000000000000000 ffffb532498a7c88 
    ffffb532498a7c10: 0000000000000004 0000000000000000 
    ffffb532498a7c20: [mm_struct]      exc_page_fault+790 
 #4 [ffffb532498a7c28] exc_page_fault+0x316 at ffffffff94002016
    /usr/src/linux-5.10.11-gentoo/arch/x86/mm/fault.c: 1346
    ffffb532498a7c30: [mm_struct]      0000000000000000 
    ffffb532498a7c40: 0000000000000000 00000000000001d0 
    ffffb532498a7c50: 0000000000000000 0000000000000000 
    ffffb532498a7c60: 0000000000000000 0000000000000000 
    ffffb532498a7c70: 0000000000000000 0000000000000000 
    ffffb532498a7c80: asm_exc_page_fault+27 
 #5 [ffffb532498a7c80] asm_exc_page_fault+0x1b at ffffffff94200acb
    /usr/src/linux-5.10.11-gentoo/arch/x86/include/asm/idtentry.h: 583
    ffffb532498a7c88: ffffb532498a7de0 0000000000000001 
    ffffb532498a7c98: ffffb532498b1000 rtR0TermNative+208 
 #6 [ffffb532498a7ca0] rtR0TermNative+0xd0 at ffffffffc0244000 [vboxdrv]
    ffffb532498a7ca8: ffffb532498a7df8 0000000000000000 
    ffffb532498a7cb8: 0000000000061918 __this_module+864 
    ffffb532498a7cc8: 0000000000000001 ffff997901207588 
    ffffb532498a7cd8: ffff997800000588 0000000000000000 
    ffffb532498a7ce8: 0000000101207067 00000000040481c0 
    ffffb532498a7cf8: 0000000000000000 ffffffffffffffff 
    ffffb532498a7d08: do_raw_spin_lock+4 
 #7 [ffffb532498a7d08] do_raw_spin_lock+0x4 at ffffffff9310dc54
    /usr/src/linux-5.10.11-gentoo/kernel/locking/spinlock_debug.c: 112
    ffffb532498a7d10: 0000000000000010 0000000000010286 
    ffffb532498a7d20: ffffb532498a7d30 0000000000000018 
    ffffb532498a7d30: ffffb532498fd000 __apply_to_page_range+737 
 #8 [ffffb532498a7d38] __apply_to_page_range+0x2e1 at ffffffff931feb71
    /usr/src/linux-5.10.11-gentoo/include/linux/spinlock.h: 354
    ffffb532498a7d40: ffff997900067260 ffffb532498fd000 
    ffffb532498a7d50: [mm_struct]      ffff997901207588 
    ffffb532498a7d60: 0000000000000000 ffffb532498fcfff 
    ffffb532498a7d70: ffffb532498fd000 ffff997900000648 
    ffffb532498a7d80: ffffb532498fd000 ffff997b2b99cb50 
    ffffb532498a7d90: ffffb532498fcfff rtR0TermNative+208 
    ffffb532498a7da0: ffffb532498fcfff [kmalloc-8k]     
    ffffb532498a7db0: ffffb532498a7df8 0000000000000000 
    ffffb532498a7dc0: 0000000000000000 ffffb5324a109010 
    ffffb532498a7dd0: [kmalloc-192]    rtR0MemObjNativeProtect+116 
 #9 [ffffb532498a7dd8] rtR0MemObjNativeProtect+0x74 at ffffffffc02456f4 [vboxdrv]
    ffffb532498a7de0: [kmalloc-8k]     8000000000000161 
    ffffb532498a7df0: c2c563b4d1c59e00 ffffb532498a7e10 
    ffffb532498a7e00: VBoxHost_RTR0MemObjProtect+129 
#10 [ffffb532498a7e00] VBoxHost_RTR0MemObjProtect+0x81 at ffffffffc0242c81 [vboxdrv]
    ffffb532498a7e08: __this_module+864 ffffb532498a7ea8 
    ffffb532498a7e18: supdrvIOCtl+12901 
#11 [ffffb532498a7e18] supdrvIOCtl+0x3265 at ffffffffc0237955 [vboxdrv]
    ffffb532498a7e20: 0000000000000004 [kmalloc-2k]     
    ffffb532498a7e30: __this_module+864 00000004001fc060 
    ffffb532498a7e40: 00000000000004ff 0000000000205900 
    ffffb532498a7e50: __this_module+864 0000000000000000 
    ffffb532498a7e60: 0000000000000000 0000000000000000 
    ffffb532498a7e70: 0000000000205978 c2c563b4d1c59e00 
    ffffb532498a7e80: 0000000000205978 0000000000005684 
    ffffb532498a7e90: 0000751ead314010 [kmalloc-2k]     
    ffffb532498a7ea0: ffffb5324a109010 ffffb532498a7f08 
    ffffb532498a7eb0: SUPR0Printf+559  
#12 [ffffb532498a7eb0] SUPR0Printf+0x22f at ffffffffc022f62f [vboxdrv]
    RIP: 0000751f0b85ae37  RSP: 0000751ec8364b58  RFLAGS: 00000246
    RAX: ffffffffffffffda  RBX: 0000751ead314010  RCX: 0000751f0b85ae37
    RDX: 0000751ead314010  RSI: 0000000000005684  RDI: 000000000000000b
    RBP: 0000751ec8364b70   R8: 0000000000000000   R9: 00000000fffffffc
    R10: 0000000000000000  R11: 0000000000000246  R12: 0000751efc3aefcf
    R13: 0000000000000000  R14: 0000751ec8364e20  R15: 0000000000000004
    ORIG_RAX: 0000000000000010  CS: 0033  SS: 002b
}}}
///
{{{
 #9 [ffffb532498a7dd8] rtR0MemObjNativeProtect+0x74 at ffffffffc02456f4 [vboxdrv]
crash> info line *0xffffffffc02456f4
Line 1919 of ""/usr/src/debug/app-emulation/virtualbox-modules-6.1.18/vboxdrv/r0drv/linux/memobj-r0drv-linux.c"" starts at address 0xffffffffc02456f4 <rtR0MemObjNativeProtect+116> and ends at 0xffffffffc0245720 <rtR0MemObjNativeGetPagePhysAddr>.
  # elif defined(IPRT_USE_APPLY_TO_PAGE_RANGE_FOR_EXEC)                                                                                                    
      PRTR0MEMOBJLNX pMemLnx = (PRTR0MEMOBJLNX)pMem;                                                                                                       
      if (   pMemLnx->fExecutable                                                                                                                          
          && pMemLnx->fMappedToRing0)                                                                                                                      
      {                                                                                                                                                    
          LNXAPPLYPGRANGE Args;                                                                                                                            
          Args.pMemLnx = pMemLnx;                                                                                                                          
          Args.fPg = rtR0MemObjLinuxConvertProt(fProt, true /*fKernel*/);                                                                                  
          int rcLnx = apply_to_page_range(current->active_mm, (unsigned long)pMemLnx->Core.pv + offSub, cbSub,                                             
                                          rtR0MemObjLinuxApplyPageRange, (void *)&Args);                                                                   
          if (rcLnx)  //this is line 1919   !!!!!!!!!!!!!!!!!!!!!!!!!!!  which seems off by one (a normal thing) 
              return VERR_NOT_SUPPORTED;                                                                                                                   
                                                                                                                                                           
          return VINF_SUCCESS;                                                                                                                             
      }                                                                                                                                                    
  # endif                       
}}}
---------
no crash now with the following .config diff (compared to previous):
{{{
-CONFIG_UNINLINE_SPIN_UNLOCK=y
+CONFIG_INLINE_SPIN_UNLOCK_IRQ=y
+CONFIG_INLINE_READ_UNLOCK=y
+CONFIG_INLINE_READ_UNLOCK_IRQ=y
+CONFIG_INLINE_WRITE_UNLOCK=y
+CONFIG_INLINE_WRITE_UNLOCK_IRQ=y
-CONFIG_DEBUG_SPINLOCK=y
+# CONFIG_DEBUG_SPINLOCK is not set
}}}
so to avoid crash, you need(at least):

CONFIG_DEBUG_SPINLOCK=n (which forces CONFIG_DEBUG_LOCK_ALLOC=n)

but doesn't matter if =y on the following:
{{{
CONFIG_DEBUG_RT_MUTEXES=y
CONFIG_DEBUG_MUTEXES=y
CONFIG_DEBUG_LOCKING_API_SELFTESTS=y
}}}
-------
nvmTODO: try with:
{{{
+# CONFIG_DEBUG_SPINLOCK is not set
}}}
but with
{{{
CONFIG_DEBUG_LOCK_ALLOC=y
}}}
Can't, because if CONFIG_DEBUG_LOCK_ALLOC=y then it's forced that CONFIG_DEBUG_SPINLOCK=y !
--------
"	ozugzug
20333	keep restarting vm windows 10 on linux host	Windows	VirtualBox 6.1.22	2021-05-01T12:14:58Z	2021-05-01T12:14:58Z	2021-05-01T12:14:58Z	"I report sudden and continuous reboots with windows 10 virtual machine on linux host.
with cpu core i5 and i7 11th generation my machine like those of many users suddenly reboots. "	fantic10
16696	KDE taskbar is not visible	Linux	VirtualBox 5.1.20	2017-04-25T12:35:28Z	2018-05-08T21:46:35Z	2018-05-08T21:46:35Z	The KDE taskbar is not visible on a Linux guest. It disappears as soon as you click on the bar. Screenshots and log attached.	Panos Kavalagios
17171	KDE scale display causing mouse offset	Windows	VirtualBox 5.1.28	2017-10-16T18:06:53Z	2017-10-16T18:06:53Z	2017-10-16T18:06:53Z	After setting up scale display option in KDE plasma (5.10) mouse cursor doesn't point to right place. Cursor is visible but it points to place with certain offset in guest machine. I'm guessing offset value relates to scale value. The problem seems to occur only with mouse integration turned on.	Kamil
16785	kde plasma 5 activity switching blocked by seamless or fullscreen VM	Windows	VirtualBox 5.1.22	2017-05-24T20:06:00Z	2017-05-24T20:06:00Z	2017-05-24T20:06:00Z	"Seamless and full screen sessions assigned to one activity prevents switching away from that activity. Activity switching works normally if the VM is windowed or minimized, whether or not the VM is assigned to one or all activities. 

Switching is normal in all modes if VM is assigned to all  activities, and virtual window assignment and switching work fine.
Version 5.1.23 r115730 (Qt5.6.1)"	matthewls
15655	KDE Active Screen Edge Actions of host are not disabled when running a guest OS in full screen mode	other	VirtualBox 5.1.0	2016-07-21T15:40:53Z	2016-07-21T15:40:53Z	2016-07-21T15:40:53Z	"When running a virtual machine in full screen mode (Host Key + F) under KDE on a Linux host, the Active Screen Edge Actions as configured in System Settings -> Workspace -> Desktop Behavior -> Screen Edges are still triggered by KDE when moving the mouse pointer into the respective corner. This collides with similiar functions of the guest desktop environment (e.g. when running a KDE guest on a KDE host).  For example when setting the upper left corner to ""Lock Screen"" or ""Present Windows - All Desktops"", moving the mouse courser into the upper left corner inside a guest machine triggers the respective action of the host machine.

When running a virtual machine in full screen mode, host features such as KDE Active Screen Edges should be disabled by VirtualBox.

I tested VirtualBox 5.0.24_RPMFusion r108355 under Fedora 23 with KDE 5.6.5 as well as VirtualBox 5.1.0 r108711 on Kubuntu 16.04 Xenial with KDE 5.5.5. The guest systems I used where Ubuntu 16.04 Xenial and Fedora 24 on the first host, and Ubuntu 16.04 Xenial on the second one, all with Guest Additions installed. 
"	Felix Kuehnl
19687	Kali problem	other	VirtualBox 6.1.10	2020-06-28T22:36:29Z	2020-06-28T22:36:29Z	2020-06-28T22:36:29Z	I have a problem when I start the kali machine, it doesn´t work 	alex1011
16909	kali linux is not installing	Windows	VirtualBox 5.1.22	2017-07-18T08:26:15Z	2017-07-24T09:47:57Z	2017-07-24T09:47:57Z	i choosed the version debian 32bit and then i started the machine and clicked Graphical install after this all i see its a black screen	LazyDanu
21463	Kali Linux	Windows	VirtualBox-7.0.6	2023-02-07T19:34:10Z	2023-02-14T11:16:52Z	2023-02-14T11:16:52Z	"My Kali on the VM is not syncing-Kernel Panic, need help as I'm not able to finish my online school project without this
"	Sonja
20798	JMicron Icy Box IB-G1826MF-C31 usb connect	Windows	VirtualBox 6.1.32	2022-01-30T08:57:57Z	2022-01-30T08:57:57Z	2022-01-30T08:57:57Z	"Hello,


I tried to connect JMicron Icy Box IB-G1826MF-C31 inside with a Crucial P5 Plus 500GB nvme m.2 ssd through USB to the guest system but I get only notification to the device connection but no drive assigned to it. If I add the drive letter manually in the disk manager of the guest system then I can browse the files on it, but only read only. The host system is a Fedora 35, the guest system which I tried was Windows 10 and Windows 7 fully updated. Any other USB devices are working, for ex. Kingston 128GB stick, or webcam, etc. If I connect this USB kit to the host system I can read and write files and folders, its the same when I use it on windows based host system. I need to use it like an usb device because the Rekordbox software (shared folders way not a solution).
Here is some info from the host system:

[924180.551542] usb 4-1: new SuperSpeed USB device number 24 using xhci_hcd
[924180.564117] usb 4-1: New USB device found, idVendor=152d, idProduct=0583, bcdDevice=83.03
[924180.564126] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[924180.564130] usb 4-1: Product: ICY  BOX
[924180.564133] usb 4-1: Manufacturer: JMicron
[924180.564136] usb 4-1: SerialNumber: DD564198838E6
[924180.567996] scsi host5: uas
[924180.568513] scsi 5:0:0:0: Direct-Access     CT500P5P SSD8             8303 PQ: 0 ANSI: 6
[924180.569234] sd 5:0:0:0: Attached scsi generic sg3 type 0
[924182.546281] sd 5:0:0:0: [sdd] 976773168 512-byte logical blocks: (500 GB/466 GiB)
[924182.546285] sd 5:0:0:0: [sdd] 4096-byte physical blocks
[924182.546366] sd 5:0:0:0: [sdd] Write Protect is off
[924182.546367] sd 5:0:0:0: [sdd] Mode Sense: 5f 00 00 08
[924182.546562] sd 5:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[924182.546790] sd 5:0:0:0: [sdd] Optimal transfer size 33553920 bytes not a multiple of physical block size (4096 bytes)
[924182.560170]  sdd: sdd1
[924182.584089] sd 5:0:0:0: [sdd] Attached SCSI disk

"	RGeri77
6049	JACK audio support for Virtualbox (Linux host)	other	VirtualBox 3.1.2	2010-01-21T15:16:26Z	2013-04-01T04:56:32Z	2013-04-01T04:56:32Z	"It is difficult to use audio from one or more Virtualbox VMs and other applications simultaniously. Or to route the audio stream between VMs and applications.
Virtualbox currently supports OSS, ALSA and pulseaudio. While the pulseaudio implementation on many distros (Ubuntu) is buggy and difficult to configure, OSS and ALSA usually do not support multiple applications using the audio device at the same time.
I suggest additional support for JACK (Jack Audio Connection Kit). JACK is a well established soundsystem that many (semi)professional audio users use."	mark_orion
2736	It is impossible to set a user's font table for text output in a graphics mode	other	VirtualBox 2.0.6	2008-12-10T09:33:20Z	2008-12-10T09:33:20Z	2008-12-10T09:33:20Z	"Interruption of VGA BIOS for installation of a user's font table is not fulfilled. The standard system call is used:

Int 10H                                                   [EGA] [MCGA] [VGA]
Function 11H (17) Subfunction 21H (33)
Set Int 43H for user's font

Call with:

  AH            = 11H
  AL            = 21H
  BL            = character rows specifier

                  00H             if user specified (see register DL)
                  01H           = 14 (0EH) rows
                  02H           = 25 (19H) rows
                  03H           = 43 (2BH) rows

  CX            = points (bytes per character)
  DL            = character rows per screen (if BL = 00H)
  ES:BP         = segment:offset of user font table

Returns:

  Nothing

Notes:

  - This function provides font selection in graphics
    (all-points-addressable) display modes.
"	Igor
19933	Issues due to lost USB packets (control and bulk type transfers)	Linux	VirtualBox 6.1.14	2020-10-02T23:46:30Z	2020-10-02T23:48:14Z	2020-10-02T23:48:14Z	"Hi all,

I'm using the latest VirtualBox version under Kubuntu 18.04 LTS. I'm having errors when testing a software I've made in a VM running the same OS, but it makes no difference on other VMs running other Linux distributions. However, my software doesn't have issues when it is running on my native machine, no VMs involved. I even tested this on a different machine, and no issues whatsoever even after a few hours.

The history here is that this software controls a USB switcher, monitoring it continuously, ever 200ms (but that can be changed in the options). The USB switcher itself is based on the CP2130 from Silicon Labs. The software has all the kinks ironed, but it fails on a VirtualBox VM, which should not happen. This also happens, seemingly, irregardless of the version of VBox I have installed. I've recently updated to the latest version from the VirtualBox repository, but saw no differences. In fact, I've seen it fail catastrophically and even causing the device to reset (the software forces a reset if more than 10 errors occur) quite rapidly. More frequently, errors are due to lost control transfers, but can happen with bulk transfers as well.

To sort this out, I've decided to run traces with Wireshark, simultaneoulsy inside and outside the VM, monitoring the same connections essentially. I can conclude that there were some lost packets because I've seen errors reporting inside the VM pertaining to packets that simply were not matched to any packets caught outside the VM, which might mean that the request packet never went outside the VM to the USB host, and due to timeout, it generated a ENOENT response inside the VM, but not outside. I must add that responses that exceed 100ms are ruled out the the application.

I have the images proving the issue, the screenshots highlighting some of the packets and the traces taken inside and outside the VM.

Kind regards, Samuel Lourenço"	bloguetronica
19780	Issue with guest additions on Windows 10 vm	Windows	VirtualBox 6.1.10	2020-07-30T09:45:15Z	2020-07-30T09:45:15Z	2020-07-30T09:45:15Z	I got an issue with full screen (impossible to get) and with the graphics, almost impossible to use like that, transparent window, strange layout, window who doesnt appear, everything is up to date (windows iso, vb, guest additions, extention vb)	toolhelp
17430	Invisible mouse pointer with remote control. (Linux host)	all	VirtualBox 5.2.4	2018-01-07T19:26:25Z	2018-01-09T19:55:37Z	2018-01-09T19:55:37Z	"When I try to remote control a virtual machine with TeamViewer or vnc the Mouse pointer of the ""supporter"" is not shown in the virtual machine.[[BR]]
The ""local"" mouse pointer of the virtual machine remains where it was left. The remote Pointer is invisible.[[BR]]

TeamViewer as well as vnc do work without restrictions, only the remote mouse is invisible in the virtual machine.[[BR]]

The local mouse pointer reflects the state of the remote pointer (hand, arrow, busy, ...) but does not move from the position where it was left by the local user.

I tried Debian stretch (KDE) and Linux Mint (Cinnamon) as host and Windows and Debian as guest.[[BR]]

In the Windows guest I tried no 3d-acceleration, Direct3D and WDDM with no avail.[[BR]]

The host is equipped with a Intel i3-6100 CPU and uses the builtin Intel graphics.
"	Gurkensalat
19946	interrupt transfers stop working	Windows	VirtualBox 6.1.10	2020-10-07T12:04:10Z	2020-10-12T06:01:20Z	2020-10-12T06:01:20Z	"After forwarding a SCM Microsystems, Inc. SCR331 SmartCard Reader USB device to the guest, it can at first be used normally. If it isn't used for a few seconds (no cards are inserted or removed, no interrupt responses are sent), interrupt handling stops working for the device. The reader can still be accessed (for example, if a card is inserted certutil can still read it), but further interrupts don't reach the guest (if no card was inserted, newly inserted cards are not noticed).

Running wireshark on both host and guest shows that on both host and guest an interrupt in request is sent out and after 5 seconds a response from the device is received. After that, the guest has no further traffic, but on the host, a SET FEATURE request is sent and a response received.

I have also seen this problem on an older modified virtualbox verion 5.1.38. I was unable to use wireshark in this configuration, but observed that in qemu-usb in file hcd-xhci.c, in function xhci_process_comands, in a switch on TBRType type, it falls into CR_STOP_ENDPOINT."	Cochimetl
6148	international characters cannot be created on mounted linux guest shared folder	Linux	VirtualBox 3.1.2	2010-02-09T14:16:21Z	2010-02-09T14:16:21Z	2010-02-09T14:16:21Z	"Im using linux ubuntu as guest running on linux host ubuntu. shared folder mount perfectly and I can copy move and delete any files on it, but files with caracters with acentos gives me ""protocol error"" see the command:

suporte@lanhelpdataserver:~$ touch test.txt
suporte@lanhelpdataserver:~$ 

the above creates the file test.txt

suporte@lanhelpdataserver:~$ touch testé.txt
touch: cannot touch `testé.txt': Protocol error
suporte@lanhelpdataserver:~$ 

the above returns the error, the only change is the addition of character ""é"" on filename.

thanks."	Marcus Leandro
16271	Interface scale up hidpi gnome	all	VirtualBox 5.1.10	2016-12-06T20:31:03Z	2016-12-13T07:05:32Z	2016-12-13T07:05:32Z	"After updating to the new version of virtualbox, the whole interface is scaling up. I attach a picture of the the interface itself.

I went and uninstalled the package called virtualbox-qt and installed the previous version of it and everything went back to normal. This might have to do something with bug #15707.

I'm running openSUSE Tumbleweed, gnome, full HD 14"""	flanaras
5148	integration between host/guest panels and menus	Windows	VirtualBox 3.0.8	2009-10-07T11:24:50Z	2009-12-01T20:17:43Z	2009-12-01T20:17:43Z	"It would be nice if the applications and icons normally shown on the Windows taskbar were instead shown on the GNOME panel window list.

It would be nice if all the icons in the Windows systray were in the GNOME panel notification area.

It would be nice if the start menu button were integrated into a subfolder in the GNOME menu or similar.

It would be nice if the launcher icons on the Windows bar were integrated into the GNOME panel too.

All the icons from Windows should be scaled to fit the GNOME desktop.

I'm using Debian GNU/Linux with the GNOME desktop as a host and Windows XP and Windows 7 as guests. It would also be useful to have similar things for other Linux desktops."	Paul Wise
5862	integrate host and guest keyboard window switching (ALT+TAB)	Windows	VirtualBox 3.1.2	2009-12-28T20:15:16Z	2010-02-23T13:53:25Z	2010-02-23T13:53:25Z	"I feel the same as the reporter of Ticket #778, about the VM instantly passing keyboard focus to the guest being very annoying for people such as myself who use the keyboard to switch between windows in the host system.

However, instead of disabling this focus-passing, I propose another interesting feature that will solve this problem: Just like the mouse focus is seamlessly shared between the host and guest (with guest additions), maybe the ALT+TAB window switching inside the guest could be integrated with that of the host. So that you can somehow switch through both host and guest windows without needing other keyboard shortcuts / mouse clicks inbetween."	uetsah
17027	Installing VirtualBox Guest Additions in Windows 7 does nothing	Windows	VirtualBox 5.1.26	2017-08-21T02:43:06Z	2017-09-19T15:14:48Z	2017-09-19T15:14:48Z	"NOTE: I already raised this issue in the forum. No luck, nevertheless. The thread is https://forums.virtualbox.org/viewtopic.php?f=2&t=84071&p=399327#p399327

My host is a 8GB Ubuntu 16.04 running VirtualBox 5.1.26. I have been running a Windows XP guest without problem for the last eight years.

I upgraded my host OS and I don't want to dual boot anymore (Ubuntu/Windows 7), so I copied the relevant harddisks partitions to a VDI image. After messing around a bit with ""fdisk"" and ""grub"", I am successfully booting Windows 7 as a guest. Slow running but Nice!. It is a Windows 7 x86-64 guest.

I proceed to uninstall most HP, Adobe, etc, crap, even the ATI video driver, the WIFI driver, etc. I reboot Windows 7 guest and everything works fine except sound (disabled) and network (drivers uninstalled). I insist that windows works fine, although harddisk performance is not stellar. I disabled Security Esencials and Windows Defender too.

After rebooting one more time, I install ""VirtualBox Guest Additions"" . Install finishes correctly and prompts to reboot. I reboot... and Windows 7 guest is working fine but... with no ""VirtualBox Guest Additions"", Nothing seems to happen. Host integration is not working and VirtualBox says that there are not guest additions running in the guest. I repeat install (it goes fine) and reboot. Same thing.

Checking the guest harddisk, I see ""VirtualBox Guest Additions"" directory with 19 files inside the ""C:/Program files"" directory. Everything seems ok. But the virtual machine is not enabling the Guest Additions.

I wonder if this is a Windows 7 32/64 issue but I lack the knowledge to debug this issue myself.

Please, Help!

Thanks in advance!."	jceajcea
20549	installing virtual box on Linux  5.10.0-kali9-amd64	other	VirtualBox 6.1.26	2021-09-15T15:28:55Z	2021-09-15T21:17:11Z	2021-09-15T21:17:11Z	"Hi , 

i have a problem while installing virtual box latest version on my linux  kernel : 5.10.0-kali9-amd64
make.log

DKMS make.log for virtualbox-6.1.26 for kernel 5.10.0-kali9-amd64 (x86_64)
{{{
Wed 15 Sep 2021 04:19:27 PM +01
make: Entering directory '/usr/src/linux-headers-5.10.0-kali9-amd64'
arch/x86/Makefile:147: CONFIG_X86_X32 enabled but no binutils support
  CC [M]  /var/lib/dkms/virtualbox/6.1.26/build/vboxdrv/linux/SUPDrv-linux.o
  CC [M]  /var/lib/dkms/virtualbox/6.1.26/build/vboxdrv/SUPDrv.o
  CC [M]  /var/lib/dkms/virtualbox/6.1.26/build/vboxdrv/SUPDrvGip.o
  CC [M]  /var/lib/dkms/virtualbox/6.1.26/build/vboxdrv/SUPDrvSem.o
as: error while loading shared libraries: libopcodes-2.35.1-system.so: cannot open shared object file: No such file or directory
make[3]: *** [/usr/src/linux-headers-5.10.0-kali9-common/scripts/Makefile.build:284: /var/lib/dkms/virtualbox/6.1.26/build/vboxdrv/SUPDrvSem.o] Error 1
make[3]: *** Waiting for unfinished jobs....
as: error while loading shared libraries: libopcodes-2.35.1-system.so: cannot open shared object file: No such file or directory
make[3]: *** [/usr/src/linux-headers-5.10.0-kali9-common/scripts/Makefile.build:284: /var/lib/dkms/virtualbox/6.1.26/build/vboxdrv/linux/SUPDrv-linux.o] Error 1
as: error while loading shared libraries: libopcodes-2.35.1-system.so: cannot open shared object file: No such file or directory
make[3]: *** [/usr/src/linux-headers-5.10.0-kali9-common/scripts/Makefile.build:284: /var/lib/dkms/virtualbox/6.1.26/build/vboxdrv/SUPDrvGip.o] Error 1
as: error while loading shared libraries: libopcodes-2.35.1-system.so: cannot open shared object file: No such file or directory
make[3]: *** [/usr/src/linux-headers-5.10.0-kali9-common/scripts/Makefile.build:284: /var/lib/dkms/virtualbox/6.1.26/build/vboxdrv/SUPDrv.o] Error 1
make[2]: *** [/usr/src/linux-headers-5.10.0-kali9-common/scripts/Makefile.build:501: /var/lib/dkms/virtualbox/6.1.26/build/vboxdrv] Error 2
make[1]: *** [/usr/src/linux-headers-5.10.0-kali9-common/Makefile:1845: /var/lib/dkms/virtualbox/6.1.26/build] Error 2
make: *** [/usr/src/linux-headers-5.10.0-kali9-common/Makefile:185: __sub-make] Error 2
make: Leaving directory '/usr/src/linux-headers-5.10.0-kali9-amd64'
}}}"	kof2002
19797	installed virtualbox 6.1.12 on centos 7 but vboxweb-service is not started	Linux	VirtualBox 6.1.10	2020-08-06T11:52:45Z	2020-08-06T11:52:45Z	2020-08-06T11:52:45Z	"installed virtualbox 6.1.12 but vboxweb-service is not started.
i tried to start ------>
systemctl start vboxweb-service

""Job for vboxweb-service.service failed because the control process exited with error code. See ""systemctl status vboxweb-service.service"" and ""journalctl -xe"" for details.""

systemctl status vboxweb-service -l
● vboxweb-service.service
   Loaded: loaded (/usr/lib/virtualbox/vboxweb-service.sh; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2020-08-06 17:19:28 IST; 1min 17s ago
  Process: 5801 ExecStart=/usr/lib/virtualbox/vboxweb-service.sh start (code=exited, status=1/FAILURE)

Aug 06 17:19:28 localhost.localdomain systemd[1]: Starting vboxweb-service.service...
Aug 06 17:19:28 localhost.localdomain vboxweb-service.sh[5801]: vboxweb-service.sh: Starting VirtualBox web service.
Aug 06 17:19:28 localhost.localdomain su[5807]: (to admin) root on none
Aug 06 17:19:28 localhost.localdomain vboxweb-service.sh[5801]: vboxweb-service.sh: failed: VirtualBox web service failed to start.
Aug 06 17:19:28 localhost.localdomain systemd[1]: vboxweb-service.service: control process exited, code=exited status=1
Aug 06 17:19:28 localhost.localdomain systemd[1]: Failed to start vboxweb-service.service.
Aug 06 17:19:28 localhost.localdomain systemd[1]: Unit vboxweb-service.service entered failed state.
Aug 06 17:19:28 localhost.localdomain systemd[1]: vboxweb-service.service failed."	pmssy
17754	Installation without disabling secureboot	other	VirtualBox 5.2.12	2018-05-10T20:51:17Z	2018-05-27T04:19:00Z	2018-05-27T04:19:00Z	There aresome guides about installing virtualbox without disabling secureboot in linux. Please make them an automatic available option.	Mahdi.G
15913	Installation of guest additions in Fedora 24 32 bits guest hangs => Linux 4.7 bug	Linux	VirtualBox 5.0.24	2016-09-09T10:10:20Z	2016-10-06T11:49:28Z	2016-10-06T11:49:28Z	"I am trying to install the guest additions in a fresh installed Fedora 24 32 bits but the VBoxLinuxAdditions.run script hangs.

The !VirtualBox version I am using is 5.0.24, but I have tried to install guest additions 5.1.4, since the former one doesn't compile under kernel 4.7.2 32 bits.

The exact sequence of commands used are:
{{{
# sudo dnf install install gcc cpp kernel-devel kernel-headers kernel-PAE-devel
# sudo wget http://download.virtualbox.org/virtualbox/5.1.4/VBoxGuestAdditions_5.1.4.iso
# sudo mkdir /tmp/vbox
# sudo mount -o loop /home/vagrant/VBoxGuestAdditions_5.1.4.iso /tmp/vbox
# sudo sh /tmp/vbox/VBoxLinuxAdditions.run
}}}

In the last step it hangs after the following messages are shown:
{{{
Verifying archive integrity... All good.
Uncompressing VirtualBox 5.1.4 Guest Additions for Linux...........
VirtualBox Guest Additions installer
Copying additional installer modules ...
Installing additional modules ...
vboxadd.sh: Building Guest Additions kernel modules.
vboxadd.sh: Starting the VirtualBox Guest Additions.
}}}

I have also tried with the latest test build at https://www.virtualbox.org/download/testcase/VBoxGuestAdditions_5.1.5-110588.iso but the result is the same.

Exactly the same procedure for a Fedora 24 64 bits guest is working fine and the guest installation finishes without problems.

A pstree command shows the following relevant process tree:
{{{
  │   │           └─sudo,30032 sh -x /tmp/vbox/VBoxLinuxAdditions.run
  │   │               └─sh,30033 -x /tmp/vbox/VBoxLinuxAdditions.run
  │   │                   └─sh,30090 ./install.sh /tmp/vbox/VBoxLinuxAdditions.run
  │   │                       └─vboxadd,30253 /opt/VBoxGuestAdditions-5.1.5/init/vboxadd setup
  │   │                           └─modprobe,32361 vboxsf
}}}

So it looks like it is loading the kernel module where the installation hangs.
This is the list of packages I have installed which are relevant to the kernel:
{{{
$ rpm -qa | grep kernel 
kernel-headers-4.7.2-201.fc24.i686
kernel-PAE-modules-4.7.2-201.fc24.i686
abrt-addon-kerneloops-2.8.2-1.fc24.i686
kernel-devel-4.7.2-201.fc24.i686
kernel-PAE-core-4.7.2-201.fc24.i686
kernel-PAE-devel-4.7.2-201.fc24.i686
libreport-plugin-kerneloops-2.7.2-1.fc24.i686
}}}

I have tried to have a look to the stack of the modprobe command:
{{{
#sudo cat /proc/32361/stack 
[<f8edddfd>] rtR0SemEventMultiLnxWait.isra.2+0x36d/0x3c0 [vboxguest]
[<f8edde73>] VBoxGuest_RTSemEventMultiWaitEx+0x23/0x30 [vboxguest]
[<f8eec5db>] VBoxGuest_RTSemEventMultiWait+0x5b/0x60 [vboxguest]
[<f8ed4361>] vgdrvHgcmAsyncWaitCallbackWorker+0xe1/0x220 [vboxguest]
[<f8ed44be>] vgdrvHgcmAsyncWaitCallback+0x1e/0x20 [vboxguest]
[<f8ed6ff1>] VbglR0HGCMInternalConnect+0x111/0x130 [vboxguest]
[<f8ed60a5>] VGDrvCommonIoCtl+0xad5/0x1550 [vboxguest]
[<f8ed2245>] VBoxGuestIDCCall+0x45/0x70 [vboxguest]
[<f8625b4d>] vbglDriverIOCtl+0x2d/0x40 [vboxsf]
[<f8626780>] VbglHGCMConnect+0x50/0xb0 [vboxsf]
[<f8626a8e>] VbglR0SfConnect+0x5e/0x90 [vboxsf]
[<f840b075>] init+0x75/0x1000 [vboxsf]
[<c0402182>] do_one_initcall+0x42/0x170
[<c056e0af>] do_init_module+0x50/0x1a8
[<c04f4c1a>] load_module+0x213a/0x27a0
[<c04f54b1>] SyS_finit_module+0xb1/0x100
[<c040388d>] do_fast_syscall_32+0x8d/0x140
[<c0b3f932>] sysenter_past_esp+0x47/0x75
[<ffffffff>] 0xffffffff

}}}

I don't know if that's useful.

I attach the output of running the installation script with sh -x, but I am afraid it doesn't give much extra information.

I also attach VBoxSVC.log just in case it is useful.

Regards
"	cquike
21391	Installation of Additions not finishing on WinXP64 (VB 7.0.4)	Windows	VirtualBox-7.0.4	2023-01-03T10:32:52Z	2023-01-03T10:41:38Z	2023-01-03T10:41:38Z	"I have a WinXP64bit. I installed old guest-additions. Now I migrate to Virtualbox7. I installed the new guest-additions https://download.virtualbox.org/virtualbox/7.0.0/Oracle_VM_VirtualBox_Extension_Pack-7.0.0.vbox-extpack

Then I try to install the guest-additions in the guest-vm. Unfortunately the installation does not finish and remains at coping VBoxControl.exe."	grim
21390	Installation of Additions not finishing on WinXP64 (VB 7.0.4)	Windows	VirtualBox-7.0.4	2023-01-03T10:32:51Z	2023-01-03T10:32:51Z	2023-01-03T10:32:51Z	"I have a WinXP64bit. I installed old guest-additions. Now I migrate to Virtualbox7. I installed the new guest-additions https://download.virtualbox.org/virtualbox/7.0.0/Oracle_VM_VirtualBox_Extension_Pack-7.0.0.vbox-extpack

Then I try to install the guest-additions in the guest-vm. Unfortunately the installation does not finish and remains at coping VBoxControl.exe."	grim
18058	Installation fails > Failed to send WATCHDOG=1 notification message: Connection refused	all	VirtualBox 5.2.20	2018-10-17T18:00:02Z	2018-10-17T18:00:02Z	2018-10-17T18:00:02Z	"Hi,

I'm on openSUSE Tumbleweed.  When I use the '''5.2.20/All distributions''' bits, my desktop has a brain freeze.  I get the errors below.  Using the '''5.2.18/All distributions''' bits does not cause this issue.

When this happens, I cannot properly shutdown my machine.  I have to hit the power button.

I tried it twice.  The second time after a clean boot.

My workaround is to revert to '''5.2.18'''

The strange thing is my laptop is also running Tumbleweed and I had no issue going to 5.2.20.

Let me know what debug information I can provide.  I know this information is a bit .. sparse to act upon.  ;)  

Thx!

{{{
[ 1518.687793] systemd-journald[2372]: Failed to send WATCHDOG=1 notification message: Connection refused
[ 1588.685640] systemd-journald[2372]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
[ 1698.682197] systemd-journald[2372]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
[ 1768.680023] systemd-journald[2372]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
}}}
"	Pablo Sanchez
19387	Install of VirtualBox 6.1.4 crashes Sudoers on Ubuntu 18.4.4	other	VirtualBox 6.1.4	2020-03-09T01:29:27Z	2020-03-09T06:39:53Z	2020-03-09T06:39:53Z	When I install VirtualBox 6.1.4 on Ubuntu 18.04.4 the sudoers complex of files is corrupted somehow and the owner of the system can no longer use the sudo command to run as administrator. One example of this is trying to install VirtualBox extensions after installing VirtualBox which always fails on authentication. This behavior survives a reboot.	jgossage
16258	Install fails v5.1.10 - Linux 64 - Ubuntu	all	VirtualBox 5.1.10	2016-12-02T10:42:58Z	2016-12-05T14:55:33Z	2016-12-05T14:55:33Z	"I downloaded the full installer for VirtuabBox, debian distro Linux 64bit.

The package manager reports an ""unsatisfiable Dependency"" on QT Core:

{{{
Error: Dependency is not satisfiable: libqt5core5a (>=5.6.0-beta)
}}}


I have scanned the debian repositories.  Sure enough there is No Stable package available to support this installer package.

I don't know what using the in-test version might be on my other stable system programs.

{{{
Package libqt5core5a

    wheezy-backports (libs): Qt 5 core module
    5.3.2+dfsg-4+deb8u1~bpo70+1: amd64
    jessie (stable) (libs): Qt 5 core module
    5.3.2+dfsg-4+deb8u1: amd64
    stretch (testing) (libs): Qt 5 core module
    5.7.1~20161021+dfsg-6: amd64
    sid (unstable) (libs): Qt 5 core module
    5.7.1~20161021+dfsg-6: amd64
}}}

I suggest it is infeasible to use this version of virtualbox on a stable system.  It might be OK for a test system or development system.  I had a mismatch of GTK versions one time and it caused all kinds of chaos with the GUI.  I don't recommend the experience."	Will
17975	Input Capture Fails	Windows	VirtualBox 5.2.18	2018-09-09T15:12:52Z	2018-09-09T15:12:52Z	2018-09-09T15:12:52Z	"Hello,

I am running Ubuntu Linux 18.04 LTS with all the latest patches installed.

Linux xxxxxxx 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 16:00:05 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

I installed Virtualbox/Extension Pack/Guest Additions from virtualbox.org; version 5.2.18 r124319 (Qt5 9.5)

I but both Windows XP and Windows 7 as guests.

Whenever I make use of the Virtualbox control bar at the bottom of the screen, and then click back into my VM, the mouse and keyboard input are not captured by the VM. I need to click off onto my second screen and then click back into the VM for the input to be captured.

I purchased a Virtualbox Enterprise license on CDW so that this ticket may receive priority attention since I am a paying customer. Please feel free to call me via the information on my account if you need any confirmation of the CDW purchase.

Thank you in advance."	SloanUser
16111	Incorrect video output after VirtualBox guest screen resizes (w&w/o guest agent)	all	VirtualBox 5.1.8	2016-10-24T18:29:53Z	2016-10-24T19:09:50Z	2016-10-24T19:09:50Z	"I face with various problems with windows size. I'm awesomewm (tiled wm) user.
So, what happens.
After video mode changed, GUI windows is resized.
Then window output immediately moves to the top left corner (maybe because of tiled wm layout). The rest screen may be filled with the previously placed parts of video output of guest.
The second issue - size of video output. After resize there may be options (when guest addons are installed)
1. Video output it just ok 
2. Screen size bigger then actual window, so scrollbars are drawn. It is bigger exactly on the size of that scrollbars.
3. Screen height equals to the screen height of the smallest screen (when there are more than one display). Currently I face with this issue only with ubuntu as a guest.

[[Image(http://s1.alxchk.me/guest-window-output-garbage-after-resize.png)]]

[[Image(guest-agent-window-resized-to-second-screen-height-01.png)]]

[[Image(guest-agent-window-resized-to-second-screen-height-02.png)]]
"	Oleksii
15353	Incorrect quoting in balloon control startup script	other	VirtualBox 5.0.18	2016-04-25T23:26:10Z	2016-04-25T23:26:10Z	2016-04-25T23:26:10Z	"On Linux, in /etc/init.d/vboxballoonctrl-service, the quoting of parameters like VBOXWATCHDOG_BALLOON_INTERVAL when building the command line is incorrect. In version 5.0.18  this is around line 239. The code is like:
    ...  PARAMS=""$PARAMS --balloon-interval \""$VBOXWATCHDOG_BALLOON_INTERVAL\""""

The extra backslashed quote marks get carried through to the command line and then into the running application itself. VBoxBalloonCtrl then ends up trying to interpret:
     ""1024""
(including the quote!!) as a number and fails.

You should either remove the quotes (since nothing should have spaces), or start the daemon with an ""eval""."	prensing
15273	Inconsistent state of attached disks, cannot close medium	other	VirtualBox 5.0.16	2016-03-25T12:05:42Z	2016-04-13T15:33:30Z	2016-04-13T15:33:30Z	" 1. I have running VM 

 2. Then I attach disk, I want to be sure that it is hotpluggable
{{{
VBoxManage storageattach itr  --storagectl SATA --port 2 --type hdd --hotpluggable on --medium /media/usb/1/kjonca/vdi/wsus.vdi
}}}
 got error:
{{{
VBoxManage: error: The machine is not mutable (state is Running)
VBoxManage: error: Details: code VBOX_E_INVALID_VM_STATE (0x80bb0002), component SessionMachine, interface IMachine, callee nsISupports
VBoxManage: error: Context: ""SetHotPluggableForDevice(Bstr(pszCtl).raw(), port, device, TRUE)"" at line 881 of file VBoxManageStorageController.cpp
}}}
 3. I cannot deregister disk:
{{{
VBoxManage storageattach itr  --storagectl SATA --port 2 --medium none ; VBoxManage closemedium /media/usb/1/kjonca/vdi/wsus.vdi
VBoxManage: error: Medium '/media/usb/1/kjonca/vdi/wsus.vdi' is locked for writing by another task
VBoxManage: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MediumWrap, interface IMedium, callee nsISupports
VBoxManage: error: Context: ""Close()"" at line 1554 of file VBoxManageDisk.cpp
}}}
The only way to resolve it is restarting virtualbox."	Kamil Jońca
8637	Inappropriate Runlevel for openSUSE 11.4	other	VirtualBox 4.0.4	2011-03-27T13:01:30Z	2011-03-27T13:01:30Z	2011-03-27T13:01:30Z	"/etc/init.d/vboxdrv and /etc/init.d/vboxweb-service contain runlevel 4 
in the openSUSE 11.4 RPM package, however, runlevel 4 is not used at all 
in openSUSE and thus leads to errors when trying to change any of the 
runlevel scripts.

- No Log-Attachment needed for this -"	Michael Kromer
9212	in seamless mode with Linux KDE host, sliding open a KDE auto-hidden panel causes temporary screen corruption	Windows	VirtualBox 4.0.12	2011-07-16T03:25:20Z	2011-07-16T04:01:54Z	2011-07-16T04:01:54Z	"Host: Ubuntu 10.10 with KDE desktop

Guest: Windows XP Pro SP3

VirtualBox 3.2.8_OSE r64453


Steps to reproduce:

Set the KDE task panel to auto-hide (in Panel Options | Panel Settings | More settings). Open the KDE System Settings app and select Desktop Effects under Workspace Appearance and Behavior. In the All Effects tab, make sure that 'Sliding popups' is checked.

Start a Windows guest in seamless mode. Move the mouse to open the KDE task panel. As it is sliding open, the display will show stale contents from closed and dragged windows on the guest desktop (see attached screenshot).

Workaround: uncheck the KDE 'Sliding popups' option mentioned above.
"	David-Sarah Hopwood
5574	In Seamless mode clicking on window titles bring guest windows to top	Windows	VirtualBox 3.0.12	2009-11-27T11:24:49Z	2009-11-27T11:24:49Z	2009-11-27T11:24:49Z	"I have VirtualBox installed on Ubuntu 9.04(actually Linux Mint 7),using KDE 4.3.2
Guest is Windows XP SP3, themes are disabled.

First i had to move startmenu from bottom of screen to right edge of screen because when no applications are open in gues, it displays windows xp background in Ubuntu.

Clicking on window titles in ubuntu, or even different tabs in opera or firefox in ubuntu, makes open windows (not minimized ones) appear into desktop.
the workaround is to minimize all windows so you can safely do the rest of your work.

"	roozbeh
16177	in linux 64bit plasma 5 virtualbox start only from terminal	all	VirtualBox 5.1.8	2016-11-10T08:45:33Z	2016-11-21T11:22:12Z	2016-11-21T11:22:12Z	As the title say: virtualbox, from release 5.1.6 (and included the build 5.1.9) does not start from menu, but only from terminal.	duns
9791	Improved support for Ubuntu Unity	other	VirtualBox 4.1.4	2011-10-20T10:46:13Z	2011-10-20T10:46:13Z	2011-10-20T10:46:13Z	"It would be nice if I could have individual virtual machines pinned to the unity taskbar.  Adding the icon to the desktop doesn't quite achieve this functionality as if I remove it from the desktop, the Unity bar entry disappears.

Most ideal way would likely be to have each VM create a separate entry in the Unity bar, and allow them to be pinned from the right click menu.

Beyond that, perhaps the VirtualBox team can explore other things they may want to put in those menus.  Probably some neat options!"	omega
16270	Impossible to reconnect VRDP after disconnection	Windows	VirtualBox 5.1.10	2016-12-06T17:10:27Z	2016-12-07T09:08:08Z	2016-12-07T09:08:08Z	"Hi, we are using VRDP on virtualbox 5.1.10 on Debian Wheezy. Virtual Machine is a Windows XP.

5.1.10-112026~Debian~wheezy

VBox ExtPack is install too.

My problem with vrdp occurs when there is a network disconnection or if the PC that connects to VRDP is disconnected suddenly without properly closing the RDP connection.
{{{
00:14:22.877226 VRDP: Connection opened (IPv4): 15
00:14:22.877825 VRDP: Negotiating security method with the client.
00:14:22.891875 VRDP: Methods 0x0000001b
00:14:22.891913 VRDP: Channel: [rdpdr] [1004]. Accepted.
00:14:22.891929 VRDP: Channel: [rdpsnd] [1005]. Accepted.
00:14:22.891942 VRDP: Channel: [drdynvc] [1006]. Accepted.
00:14:22.891974 VRDP: Channel: [cliprdr] [1007]. Accepted.
00:14:22.966644 VRDP: Client seems to be MSFT.
00:14:22.966680 VRDP: Logon: VM-W7-PC (11.46.49.32) build 7601. User: [] Domain: [] Screen: 0
00:14:22.967984 AUTH: User: []. Domain: []. Authentication type: [Null]
00:14:22.968014 AUTH: Access granted.
00:14:22.968756 AUTH: Multiple connections are not enabled. Access denied.
00:14:22.968779 VRDP: Connection closed: 15
00:14:35.670630 VRDP: New connection: 
00:14:35.670763 VRDP: Connection opened (IPv4): 16
00:14:35.671358 VRDP: Negotiating security method with the client.
00:14:35.672871 VRDP: Connection closed: 16
00:14:35.705151 VRDP: New connection: 
00:14:35.705210 VRDP: Connection opened (IPv4): 17
00:14:35.705832 VRDP: Negotiating security method with the client.
00:14:35.723321 VRDP: Methods 0x0000001b
00:14:35.723383 VRDP: Channel: [rdpdr] [1004]. Accepted.
00:14:35.723398 VRDP: Channel: [rdpsnd] [1005]. Accepted.
00:14:35.723412 VRDP: Channel: [drdynvc] [1006]. Accepted.
00:14:35.723425 VRDP: Channel: [cliprdr] [1007]. Accepted.
00:14:35.783553 VRDP: Client seems to be MSFT.
00:14:35.783592 VRDP: Logon: VM-W7-PC (11.46.49.32) build 7601. User: [] Domain: [] Screen: 0
00:14:35.784755 AUTH: User: []. Domain: []. Authentication type: [Null]
00:14:35.784785 AUTH: Access granted.
00:14:35.785588 AUTH: Multiple connections are not enabled. Access denied.
00:14:35.785618 VRDP: Connection closed: 17
00:16:08.662647 VRDP: New connection: 
00:16:08.662747 VRDP: Connection opened (IPv4): 18
00:16:08.663370 VRDP: Negotiating security method with the client.
00:16:08.664983 VRDP: Connection closed: 18
00:16:08.689273 VRDP: New connection: 
00:16:08.689333 VRDP: Connection opened (IPv4): 19
00:16:08.689886 VRDP: Negotiating security method with the client.
00:16:08.719393 VRDP: Methods 0x0000001b
00:16:08.719401 VRDP: Channel: [rdpdr] [1004]. Accepted.
00:16:08.719404 VRDP: Channel: [rdpsnd] [1005]. Accepted.
00:16:08.719407 VRDP: Channel: [drdynvc] [1006]. Accepted.
00:16:08.719410 VRDP: Channel: [cliprdr] [1007]. Accepted.
00:16:08.789932 VRDP: Client seems to be MSFT.
00:16:08.789994 VRDP: Logon: VM-W7-PC (11.46.49.32) build 7601. User: [] Domain: [] Screen: 0
00:16:08.791341 AUTH: User: []. Domain: []. Authentication type: [Null]
00:16:08.791372 AUTH: Access granted.
00:16:08.792399 AUTH: Multiple connections are not enabled. Access denied.
00:16:08.792434 VRDP: Connection closed: 19
00:19:15.028325 VRDP: New connection: 
00:19:15.028558 VRDP: Connection opened (IPv4): 20
00:19:15.029174 VRDP: Negotiating security method with the client.
00:19:15.030794 VRDP: Connection closed: 20
00:19:15.073957 VRDP: New connection: 
00:19:15.074088 VRDP: Connection opened (IPv4): 21
00:19:15.074707 VRDP: Negotiating security method with the client.
00:19:15.091989 VRDP: Methods 0x0000001b
00:19:15.092058 VRDP: Channel: [rdpdr] [1004]. Accepted.
00:19:15.092076 VRDP: Channel: [rdpsnd] [1005]. Accepted.
00:19:15.092091 VRDP: Channel: [drdynvc] [1006]. Accepted.
00:19:15.092107 VRDP: Channel: [cliprdr] [1007]. Accepted.
00:19:15.219874 VRDP: Client seems to be MSFT.
00:19:15.219935 VRDP: Logon: VM-W7-PC (11.46.49.32) build 7601. User: [] Domain: [] Screen: 0
00:19:15.220837 AUTH: User: []. Domain: []. Authentication type: [Null]
00:19:15.221122 AUTH: Access granted.
00:19:15.221791 AUTH: Multiple connections are not enabled. Access denied.
00:19:15.221815 VRDP: Connection closed: 21
}}}

Similars problems are already evoke in many tickets like #4655.

Just disconnect your RJ45 cable, on your server or on the PC who RDP WHEN RDP is connected and you will not can connect you again.
For reconnect you will have to reboot VM or disable/enable VRDP."	Ravinou
4003	Impossible to hide USB devices, specifically the host system disk	Windows	VirtualBox 2.2.2	2009-05-12T18:22:19Z	2009-05-13T09:13:16Z	2009-05-13T09:13:16Z	"
My host system (Ubuntu Jaunty 9.04) boots from an external USB disk that is selectable in the USB selection menu as any other connected usb device.

If I click on it by mistake it happens that the system disk gets disconnected from the host and assigned to the guest, making the system instantly unstable and unusable, and corrupting every filesystem on it.

Since this situation is not really common I don't know if this possibility should be denied in a first place, but I think that at least there should be the possibility to hide or exclude specific USB devices from the selection menu.

Perhaps a feature like filters but whith a blacklist logic..."	Mico
19014	Imported OVA with SATA controller unbootable in BIOS mode	Solaris	VirtualBox 6.0.12	2019-10-14T18:18:20Z	2019-10-14T18:21:06Z	2019-10-14T18:21:06Z	"'''Steps to reproduce:'''

1. Import OVA/OVF template with following entry for disk controller:

{{{
<Item>
<rasd:Description>SATA Controller</rasd:Description>
<rasd:Caption>sataController0</rasd:Caption>
<rasd:InstanceID>4</rasd:InstanceID>
<rasd:ResourceType>20</rasd:ResourceType>
<rasd:ResourceSubType>AHCI</rasd:ResourceSubType>
<rasd:Address>0</rasd:Address>
<rasd:BusNumber>0</rasd:BusNumber>
</Item>
}}}

2. Try to boot...

'''Expected:'''

System booted up.

'''Actually'''

Got weird behavior -- on first boot strange error appears,
on second boot system freezes after passing GRUB.
Sometimes after several reboots system is booted.

'''Workaround'''
Seems it's similar to #6984.

SATA controller is created with port count equal to 30.
If port count is set to 1, system boots up flawlessly.

Also when SATA controlled is removed via VirtualBox UI,
and new is one added to the system, it's port count is 0.

Tested with Fedora 30. Screenshot attached."	Roman Valov
18730	Ignore extra entries in OVF manifest file (.mf)	other	VirtualBox 6.0.8	2019-06-28T14:33:18Z	2019-06-28T14:50:03Z	2019-06-28T14:50:03Z	"When a faulty program adds additional entries in the manifest file [1], VirtualBox crashes sometimes without error, sometimes with the error ""NS_ERROR_CALL_FAILED (0x800706BE)"". I propose that it should instead just ignore these entries.

[1] https://code.vmware.com/forums/3086#613566|5230149"	darkdragon
18705	Icon error	Linux	VirtualBox 6.0.8	2019-06-12T21:32:30Z	2022-05-30T22:25:28Z	2022-05-30T22:25:28Z	i am using ubuntu as host and when i launch some virtual machine, the icon does not appears. It looks like a lost item.	betoherrera82
21440	I/O errors with virtio-scsi	Linux	VirtualBox-7.0.6	2023-01-28T00:22:38Z	2023-02-09T18:44:17Z	2023-02-09T18:44:17Z	"I have just created a new guest, and to improve performance, I have chosen the virtio-scsi for the storage controller.

The host I/O cache is disabled.

Under medium IO load, I started to get I/O errors on the console of the guest within 15 minutes.

I'm attaching the log (which doesn't show any errors as far as I can tell), and a screenshot which shows the guest console.

I am aware that some related bugs were allegedly fixed for 7.0.4, but I'm on 7.0.6, and still see it. 
"	csillag
21439	I/O errors with virtio-scsi	Linux	VirtualBox-7.0.6	2023-01-28T00:22:36Z	2023-01-28T00:22:36Z	2023-01-28T00:22:36Z	"I have just created a new guest, and to improve performance, I have chosen the virtio-scsi for the storage controller.

The host I/O cache is disabled.

Under medium IO load, I started to get I/O errors on the console of the guest within 15 minutes.

I'm attaching the log (which doesn't show any errors as far as I can tell), and a screenshot which shows the guest console.

I am aware that some related bugs were allegedly fixed for 7.0.4, but I'm on 7.0.6, and still see it. 
"	csillag
3236	hostif networking doesn't work when link is down	other	VirtualBox 2.1.2	2009-01-30T17:15:04Z	2010-05-03T17:44:31Z	2010-05-03T17:44:31Z	"I route traffic from eth0 to wlan0, and use hostif eth0 for VirtualBox. If no devices are physically connected to eth0 (and turned on), the kernel reports 'eth0: link down', and virtualbox networking doesn't work. When a devices is on and connected to eth0, the kernel reports 'eth0: link up', and virtualbox networking starts working. If I disconnect the device from eth0 it stops working again.

I could just use wlan0 hostif instead, but then it's difficult to filter the traffic, run my own DHCP server, etc. Also I already forward eth0 to wlan0 for physical devices, and it makes sense to use the same setup for virtualbox."	Bryce Allen
16708	HostAudioNotResponding	Windows		2017-04-28T04:52:00Z	2017-05-09T13:56:54Z	2017-05-09T13:56:54Z	"Some AC'97 audio streams (PCM Input, PCM Microphone) could not be opened. Guest applications generating audio output or depending on audio input may hang. Make sure your host audio device is working properly. Check the logfile for error messages of the audio subsystem.

Using the latest test build, Version 5.1.21 r115071 (Qt5.6.1) on Arch Linux.

Audio works, it's ALSA (no PulseAudio), in both the main operating system and Virtualbox.

So why the error?

I've tried using special kernels as I thought it might be a latency issue. No improvement with linux-ck, linux-pf or linux-rt.

Doesn't matter if you use AC 97 or Intel HD Audio drivers."	shillshocked
18720	Host system freezes as soon as the mouse pointer enters the VM on nVidia	Linux	VirtualBox 6.0.8	2019-06-22T10:07:00Z	2019-06-22T16:19:15Z	2019-06-22T16:19:15Z	"Host system freezes immediately when mouse pointer enters the VM when running on nVidia with proprietary drivers. I tried to disable nVidia and run on Intel HD and the issue is not reproducible.
The rest of the system is perfectly stable when running on nVidia.
These are two logs of Virtualbox with different graphics controllers:

https://pastebin.com/azj2dG3v
https://pastebin.com/uCcQ45jL

After the mouse pointer enters the VM, the host freezes, so I cannot control the system anymore, I can only send sysrq and reboot. If I check kernel messages after the boot, this is what I found at the end of the previous session:

https://pastebin.com/n83NqFhA

I do not know where the issue comes from, so I tried to report the issue also to nVidia here:

https://devtalk.nvidia.com/default/topic/1056067/linux/virtualbox-freezes-my-system-when-on-nvidia-but-not-when-on-intel-hd/

but I thought I could also report to Virtualbox and see if together we can find a fix.

Host system is Kubuntu 19.04. Guest system I tried are KDE Neon and Kubuntu 19.04. I tried with official VirtualBox 6.0.8."	Luca Carlon
15917	Host Panel overlaping guest on full screen on dual monitors	all	VirtualBox 5.0.14	2016-09-11T15:18:55Z	2016-09-11T15:18:55Z	2016-09-11T15:18:55Z	"Virtualbox: 5.0.14 r105127 from source
Host: Slackware 14.1 3.10.103 XFCE + Extension Pack
Guest: Uauntu 14.04 XFCE, Slackware 14.1 XFCE, Debian 8 LXDE, Windows 7 64bit
- Guest additions included on all

Host panel appears forefront and overlapping my guest taskbar on the opposite screen than I'm currently working on. Auto hiding host panel helps but doesn't fix the problem."	nonenene
4134	Host Only Networking: Route Connections	other	VirtualBox 2.2.4	2009-05-30T12:49:28Z	2010-05-31T06:50:17Z	2010-05-31T06:50:17Z	"To make host-only networking more user-friendly add the folwing configuration options to
File -> Global Settings -> Networking -> HostOnly Networking Connection -> Change.

Add a additional tab to the existing ""DHCP Settings"" and ""Adapter"" tabs with the following checkboxes:

[ ] Routing
   [ ] Regular Routing
       (use the current default route to forward connections)
   [ ] NAT
       (hide the the hosts of the host-only-network behind the host-machine)
        e.g.:
        iptables -t nat -A POSTROUTING -o ${IFNAME} -j MASQUERADE
        echo 1 >/proc/sys/net/ipv4/ip_forward

[ ] DNS Forwarding
    Activate a proxy dns listening on the gateway ip of the host-only-network
    which forwards all requests to the currently(!) configured dns-servers in /etc/resolv.conf
    Maybe you can reuse ""dnsmasq"".

Keep in mind that virtualbox is used often on laptops - therefore the networking settings are changeing
i.e. if you are at home (using wlan) or at work (using ethernet).
"	Marc Schoechlin
6514	Host only interfaces and DHCP servers show strange behavior	other	VirtualBox 3.1.6	2010-04-09T09:45:04Z	2010-04-09T10:00:59Z	2010-04-09T10:00:59Z	"I am using the PHP web api to create a few host only interfaces and dhcp servers for them. 

When I set them up properly the guest (Win XP) has no issues getting an IP from the dhcp server. However, any changes to the dhcp server configuration while the machine is running have no effect (I haven't tried using the cableConnected feature of the guest network adapter, but I disable/enable the connection from the guest so that should work). Those changes only appear after I stop and start the virtual machine, so maybe I am missing a neccessary step (note: restarting the guest w/o stopping the vm does not work either). 

An odd thing is that under no circumstances does the state of the dhcp server make any difference. Disabling the server by using the IDHCPServer::stop() function does not seem to stop the server. Or it could be that this is supposed to do something completely different, but I can't really tell since there is almost no information about it in the API docs.

Another issue I have is when trying to enable dynamic configuration on the host only interface. As far as I can understand enabling that will allow a dhcp server to give an address to the interface. But what I get when I call 
{{{
IHostNetworkInterface::enableDynamicIpConfig()
}}}
is this:

{{{
Fatal error: Uncaught SoapFault exception: [SOAP-ENV:Client] VirtualBox error: (0x0) in <...the stack trace..>
}}}
I get the same error when I try to call IHostNetworkInterface::dhcpRediscover(). All this could have something to do with the fact that there is no dhcp server that could handle the address allocation for these interfaces but there is nothing in the docs that explains how to add such s server.

Attempting to do all this using the CLI also got me nowhere because there is no info about the ''VBoxManage hostonlyif'' subcommand.

Am I missing something or is there something wrong here?"	Sm0k1n
17645	Host modules build without dkms patch	Linux	VirtualBox 5.2.6	2018-03-28T14:10:58Z	2018-03-28T14:10:58Z	2018-03-28T14:10:58Z	"Using VirtualBox 5.2.8 I cannot get the host modules to build. The 5.0.x modules build fine. It seems the makefile no longer functions correctly on systems without DKMS. System is LFS, GCC 5.3, QT5.10.1, kernel 4.14.29 

The errors are below. I've created a patch to fix these issues, I'm not sure if this patch is the correct way to fix it though.


{{{
=== Building 'vboxdrv' module ===
make[1]: Entering directory '/mnt/data/packages/virtualbox-host-modules/1/vboxhost-5.2.8_OSE/vboxdrv'
make V= CONFIG_MODULE_SIG= -C /usr/lib/modules/4.14.29/build SUBDIRS=/mnt/data/packages/virtualbox-host-modules/1/vboxhost-5.2.8_OSE/vboxdrv SRCROOT=/mnt/data/pl/packages/virtualbox-host-modules/1/vboxhost-5.2.8_OSE/vboxdrv -j4 modules
make[2]: Entering directory '/mnt/data/packages/virtualbox-host-modules/1/vboxhost-5.2.8_OSE/vboxdrv'
make[2]: warning: -jN forced in submake: disabling jobserver mode.
  CC [M]  /mnt/data/packages/virtualbox-host-modules/1/vboxhost-5.2.8_OSE/vboxdrv/linux/SUPDrv-linux.o
cc1: fatal error: /mnt/data/packages/virtualbox-host-modules/1/vboxhost-5.2.8_OSE/vboxdrv/vboxdrv/include/VBox/SUPDrvMangling.h: No such file or directory
compilation terminated.
  CC [M]  /mnt/data/packages/virtualbox-host-modules/1/vboxhost-5.2.8_OSE/vboxdrv/SUPDrv.o
cc1: fatal error: /mnt/data/packages/virtualbox-host-modules/1/vboxhost-5.2.8_OSE/vboxdrv/vboxdrv/include/VBox/SUPDrvMangling.h: No such file or directory
compilation terminated.
make[3]: *** [scripts/Makefile.build:329: /mnt/data/packages/virtualbox-host-modules/1/vboxhost-5.2.8_OSE/vboxdrv/linux/SUPDrv-linux.o] Error 1
make[3]: *** Waiting for unfinished jobs....
make[3]: *** [scripts/Makefile.build:329: /mnt/data/packages/virtualbox-host-modules/1/vboxhost-5.2.8_OSE/vboxdrv/SUPDrv.o] Error 1
make[2]: *** [Makefile:1519: _module_/mnt/data/packages/virtualbox-host-modules/1/vboxhost-5.2.8_OSE/vboxdrv] Error 2
make[2]: Leaving directory '/usr/lib/modules/4.14.29/build'
make[1]: *** [/mnt/data/packages/virtualbox-host-modules/1/vboxhost-5.2.8_OSE/vboxdrv/Makefile.include.footer:101: vboxdrv] Error 2
make[1]: Leaving directory '/mnt/data/packages/virtualbox-host-modules/1/vboxhost-5.2.8_OSE/vboxdrv'
make: *** [Makefile:49: all] Error 2

}}}
"	Willie
19912	Host gnome topleft hot-corner doesn't work when VM is running and focused.	Windows	VirtualBox 6.1.14	2020-09-23T23:47:19Z	2020-09-23T23:47:19Z	2020-09-23T23:47:19Z	"I use Virtualbox 6.1.14 r140239 on Debian 10.5 with an Nvidia driver and an Nvidia proprietary driver.When I opened a Win10 VM and had it focused,I am unable to use the topleft hot-corner action of Gnome desktop. 
In gnome,when moving cursor to the topleft corner,it works as if you clicked the 'Activities' button on the topleft.While when focusing on a Virtualbox Win10 VM,moving cursor to the topleft corner doesn't cause any reactive.
This bug does not only exist on Debian,but also on Arch.
There is another spotter of this bug:
https://www.reddit.com/r/gnome/comments/dhqxbg/topleft_hotcorner_not_working_when_virtualbox/"	TyamaAROU
20240	Host Freeze Ubuntu 20.04	other	VirtualBox 6.1.16	2021-03-08T09:47:09Z	2021-03-08T09:47:09Z	2021-03-08T09:47:09Z	"Sometimes i got a freeze of the Host (Ubuntu 20.04.1) after several guest are up. (kernel panic)

Host: Linux 5.8.0-44
Guests are all RHEL 7.8"	Chris81
16694	Host fails to resume from suspend when virtualbox installed	other	VirtualBox 5.1.18	2017-04-25T07:35:52Z	2017-04-25T07:38:26Z	2017-04-25T07:38:26Z	"Since I installed virtualbox my laptop fails to suspend to RAM properly.

Looks like it suspends, but when I open the lid it just reboots.

Laptop is a Dell XPS 13 9350 Developer edition
OS: Ubuntu 16.10 / 17.04
Virtual box does not need to be running, just installed


Steps to reproduce:
- close lid and suspend to ram
- open lid and it will just restarts most of the time

From the logs:
Suspending:

Apr 21 16:55:24 XPS13 systemd[1]: Starting TLP suspend/resume...
Apr 21 16:55:24 XPS13 psensor.desktop[15786]: [2017-04-21T15:55:24] [ERR] lmsensor: Cannot get value of subfeature temp1_input: I/O error.
Apr 21 16:55:24 XPS13 systemd[1]: Started TLP suspend/resume.
Apr 21 16:55:24 XPS13 systemd[1]: Reached target Sleep.
Apr 21 16:55:24 XPS13 systemd[1]: Starting Suspend...
Apr 21 16:55:24 XPS13 systemd-sleep[26264]: Failed to connect to non-global ctrl_ifname: (nil)  error: No such file or directory
Apr 21 16:55:24 XPS13 systemd-sleep[26265]: /lib/systemd/system-sleep/wpasupplicant failed with error code 255.
Apr 21 16:55:24 XPS13 systemd-sleep[26264]: Suspending system...
Suspend never finished

And it just reboots:
Apr 21 17:59:10 XPS13 rsyslogd: [origin software=""rsyslogd"" swVersion=""8.16.0"" x-pid=""902"" x-info=""http://www.rsyslog.com""] start

Let me know if more info is needed"	silles
14182	Host detects wrong number of cores (half of them)	Linux	VirtualBox 4.3.28	2015-06-08T07:11:01Z	2017-02-27T21:55:31Z	2017-02-27T21:55:31Z	"I've a system with 4 Opteron 6174, each of them has 12 cores so the system has a total of 48 cores.

But Vbox seems to detect just half of them, this is the relevant line on one of the client log files:

00:00:00.728345 Physical host cores: 24

I attach the full log for completeness"	Alex
10838	Horizontal wheel-scroll becomes alt-vertical-wheel-scroll	Windows	VirtualBox 4.1.18	2012-08-19T12:54:07Z	2012-08-25T06:39:31Z	2012-08-25T06:39:31Z	"I have a Windows 7 guest on Virtualbox 4.1.18 r78361 on 64-bit Ubuntu 12.04 host (Unity 2D/3D), and when in the Windows guest, a horizontal mouse wheel-scroll becomes the alt-vertical-scroll event (with effect similar to page-up/down). This is very annoying as whenever I accidentally touch horizontal scroll wheel the whole page jumps up or down a full page or more. This happens both of my bluetooth mouses (Apple and Logitech). I have the latest guest addition installed on the guest Windows 7 OS. I've tried both PS2 mode and absolute position mode (e.g. tablet mode) HID mouse emulation in virtualbox setup, with same result. I can't find any mention of this problem after an hour of search.

BTW, the same Virtualbox with an Ubuntu guest works fine, e.g. horizontal and vertical mouse wheel-scroll work as they normally should.

What can I do? If it can't be fixed, e.g. horizontal scroll-wheel to scroll horizontally, then I don't mind if there is a way to disable horizontal scroll-wheel events from Virtualbox's .vbox guest-machine configuration..."	powerstrip2
16751	Horizontal scroll for windows guest.	Windows	VirtualBox 5.1.22	2017-05-11T17:38:44Z	2017-05-11T17:55:34Z	2017-05-11T17:55:34Z	Currently there still isn't any support of horizontal scrolling for guest vm.	amosb
5489	high-bandwidth multicast traffic	Linux	VirtualBox 3.0.10	2009-11-17T16:30:27Z	2009-12-04T11:00:18Z	2009-12-04T11:00:18Z	"Hi!

When I generate a lot of multicast traffic (500mbps) from some host on the network to a virtual machine with a virtual e1000 (over the software network bridge), the network on my virtual machine hangs after a couple of seconds. All hosts (virtual and non-virtual) are running Debian Lenny. 
The physical host gives kernel stack traces in its kernel ring buffer that seem to be related. 

The physical host is a four-core Intel Core2 which can handle the multicast traffic in the host os. The virtual host is a four-core as well, with a virtual e1000. 

I will attach the kernel ring buffer log. "	Stefaan
11947	High I/O on SharedFolders hangs system	other	VirtualBox 4.2.16	2013-07-09T15:52:02Z	2016-08-17T15:05:50Z	2016-08-17T15:05:50Z	"Running a deep file scan (IdentityFinder) within a 32bit Windows XP guest on a Shared Folder is causing multiple VMs to independently hang. Guest OS remains somewhat responsive (right click on start bar provides menu) but Explorer or other applications remain unresponsive. 

Task Manager is still running/updating and shows 0% CPU usage.

I've included virtual box log. Machine went unresponsive at 10 minutes. Resized window at 35 minutes to provide timeline. Host OS shows vmware process as utilizing between 13-40% cpu utilization.

Host OS is Fedora 19 with yum packages ""akmod-VirtualBox Virtualbox"" installed.



"	dsiercks
10031	High I/O causing filesystem corruption	Linux	VirtualBox 4.1.4	2011-12-15T18:30:45Z	2021-04-22T15:10:32Z	2021-04-22T15:10:32Z	"Hello,
We are running an Ubuntu 10.04 32bit guest on a RHEL 64 bit host. The guest storage control is SATA AHCI with host I/O caching enabled. 
Host info:
OS Type:	Linux (2.6.18-194.el5)
VirtualBox:	4.1.4 (74291)
Processors:	Intel(R) Xeon(R) CPU 3060 @ 2.40GHz (2)
HWVirtEx, PAE, Long Mode (64-bit)

It seems during times of high I/O, like backups and etc, the guest filesystem resets to read-only. We have this issue with both ext3 and ext4 filesystems. Switching to ext3 seemed to lessen the occurrences though.

Here is a snip of syslog around the time of the corruption..


{{{
Dec 15 08:01:48 vault sm-mta[1437]: rejecting connections on daemon MTA-v4: load average: 12
Dec 15 08:01:48 vault sm-mta[1437]: rejecting connections on daemon MSP-v4: load average: 12
Dec 15 08:02:03 vault sm-mta[1437]: rejecting connections on daemon MTA-v4: load average: 12
Dec 15 08:02:03 vault sm-mta[1437]: rejecting connections on daemon MSP-v4: load average: 12
Dec 15 08:02:18 vault sm-mta[1437]: rejecting connections on daemon MTA-v4: load average: 12
Dec 15 08:02:18 vault sm-mta[1437]: rejecting connections on daemon MSP-v4: load average: 12
Dec 15 08:02:29 vault kernel: [ 2338.011698] ata4.00: exception Emask 0x0 SAct 0xffff SErr 0x0 action 0x6 frozen
Dec 15 08:02:29 vault kernel: [ 2338.011714] ata4.00: failed command: WRITE FPDMA QUEUED
Dec 15 08:02:29 vault kernel: [ 2338.011721] ata4.00: cmd 61/00:00:b7:5c:9d/04:00:09:00:00/40 tag 0 ncq 524288 out
Dec 15 08:02:29 vault kernel: [ 2338.011723]          res 40/00:00:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
Dec 15 08:02:29 vault kernel: [ 2338.011726] ata4.00: status: { DRDY }
Dec 15 08:02:29 vault kernel: [ 2338.011729] ata4.00: failed command: WRITE FPDMA QUEUED
Dec 15 08:02:29 vault kernel: [ 2338.011736] ata4.00: cmd 61/00:08:77:31:9d/04:00:09:00:00/40 tag 1 ncq 524288 out
Dec 15 08:02:29 vault kernel: [ 2338.011737]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 15 08:02:29 vault kernel: [ 2338.011740] ata4.00: status: { DRDY }
Dec 15 08:02:29 vault kernel: [ 2338.011743] ata4.00: failed command: WRITE FPDMA QUEUED
Dec 15 08:02:29 vault kernel: [ 2338.011749] ata4.00: cmd 61/00:10:77:35:9d/04:00:09:00:00/40 tag 2 ncq 524288 out
Dec 15 08:02:29 vault kernel: [ 2338.011751]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
}}}
And then later on in the file....
{{{
Dec 15 08:02:29 vault kernel: [ 2338.011969] ata4: hard resetting link
Dec 15 08:02:29 vault kernel: [ 2338.332268] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Dec 15 08:02:33 vault kernel: [ 2342.108804] ata4.00: configured for UDMA/133
Dec 15 08:02:33 vault kernel: [ 2342.108811] ata4.00: device reported invalid CHS sector 0
Dec 15 08:02:33 vault kernel: [ 2342.108815] ata4.00: device reported invalid CHS sector 0
Dec 15 08:02:33 vault kernel: [ 2342.108818] ata4.00: device reported invalid CHS sector 0
Dec 15 08:02:33 vault kernel: [ 2342.108820] ata4.00: device reported invalid CHS sector 0
Dec 15 08:02:33 vault kernel: [ 2342.108823] ata4.00: device reported invalid CHS sector 0
Dec 15 08:02:33 vault kernel: [ 2342.108826] ata4.00: device reported invalid CHS sector 0
Dec 15 08:02:33 vault kernel: [ 2342.108829] ata4.00: device reported invalid CHS sector 0
Dec 15 08:02:33 vault kernel: [ 2342.108831] ata4.00: device reported invalid CHS sector 0
Dec 15 08:02:33 vault kernel: [ 2342.108834] ata4.00: device reported invalid CHS sector 0
Dec 15 08:02:33 vault kernel: [ 2342.108837] ata4.00: device reported invalid CHS sector 0
Dec 15 08:02:33 vault kernel: [ 2342.108840] ata4.00: device reported invalid CHS sector 0
}}}

At this point the guest needs to be shut down and the drive mounted and fsck, which complains about allot of IO handle stuff."	Indigo42
12851	High cpu-load (up to 100%) on idle	Windows	VirtualBox 4.3.6	2014-03-20T23:24:59Z	2020-09-12T21:09:13Z	2020-09-12T21:09:13Z	"My host is Linux 3.13.6 x86_64 and the guest is Windows XP SP3 32 bit with all current updates installed. The guest additions with experimental 3D support are installed too.

If the Windows XP guest is booted up and reached the idle state (0-1% cpu-load in the task manager) I'm noticing that on my Linux host the cpu-load is constantly at ~15% of one core (AMD Phenom II X6 1045T). If I'm booting up the Windows XP guest into the safe mode and it reached the idle state the cpu-load on my Linux guest goes even up to the maximum (~600%/600%)."	Sworddragon
10611	High CPU usage from interrupts (20% on 8 idle processors)	Windows	VirtualBox 4.1.16	2012-05-28T13:52:26Z	2017-01-10T16:55:06Z	2017-01-10T16:55:06Z	"The idle guest OS has a high CPU usage from interrupts, consuming around 20-25% of the 8 available virtual processors. When load increases so do the interrupts. If I drop the number of processors then the usage from interrupts drops substantially.

Number of processors with corresponding CPU usage from interrupts:
* 2 processors = 5%
* 4 processors = 4%
* 6 processors = 5%
* 8 processors = 20-25%

Host: Debian 6.0.5 [[br]]
Guest: Windows 7 SP1 [[br]]
VirtualBox: 4.1.16 [[br]]

Specs of the physical host: [[br]]
2 x Xeon E5620 @ 2.40GHz, 8 cores in total, 24GB RAM"	Denis Kozlov
16245	HiDPI host (KDE Plasma 5) menu clicks are in wrong place	Windows	VirtualBox 5.1.6	2016-11-29T23:02:40Z	2016-12-04T15:38:03Z	2016-12-04T15:38:03Z	"When using KDE Plasma 5 as a host, menu clicks in the UI are misplaced; clicking a menu item in the VirtualBox UI causes the click to be registered inside the guest OS window.

Clicks also do not register anywhere inside the window sometimes (multiple client clicks required to get the guest OS to realise one single click).

OS: Kubuntu 16.10 (fresh installation)
PC: Dell XPS 13 Late 2016

Video: https://1drv.ms/v/s!Aqb97db1Lae8gvArfCENGu1I8RZsCQ"	davewthompson
16783	"held keypress causes ""flickering"" responses in VM"	Windows	VirtualBox 5.1.22	2017-05-24T18:12:33Z	2017-05-24T19:25:59Z	2017-05-24T19:25:59Z	Through version 5.1.22, press-and-holding a key in a VM produced continuous responses. Now, in Version 5.1.23 r115604 (Qt5.6.1), the response is flickering and functionally broken. Specifically, I press and hold numeric keyboard 5 to temporarily activate the microphone input for Dragon Naturally Speaking dictation. This always worked before to keep the mic on (red mic icon to green); now the mic icon color flickers during and after the key hold, as though the keyboard buffer is overflowing or not being read immediately. This happens in both seamless and window mode guest. Host: Mint KDE 18.1, kernel 4.1.2, AMD FX-9370 8 core CPU, 32GB RAM, microsoft wireless keyboard; Guest: windows 7 64, 5GB VRAM, 4 VCPUs	matthewls
19735	headless start failed with vmsvga display	Linux	VirtualBox 6.1.10	2020-07-19T17:00:05Z	2020-07-19T17:00:05Z	2020-07-19T17:00:05Z	"Host - fedora 31 workstation

Guest - Ubuntu 18.04.4 LTS

VirtualBox 6.1.12

1. I set up VMSVGA (as recommended for linux guests) with 3D driver in VM settings
2. I logon to host with ssh
3. I have started VM by command: VBoxManage startvm ""vmname"" --type headless
4. VM started
5. Shortly VM stoped with status ""interrupted""

6. I set up old VBoxVGA driver without 3D in VM settings
7. I have repeated steps 2-3
8. All is OK!

9. I have repeated step 1
10. I logon to host with ssh BUT with -X option
11. I have repeated step 3
12. All is OK
13. BUT when I have closed session (which started at step 10) then my VM stopped!

I would like to use steps 1-4 but without step 5 :)
At this time I use my VM with old VBoxVGA driver.
May be step 5 - result of some bug with VMSVGA driver..."	tol2000
20873	HDAT2 crashes under SysLinux 6.04 in VirtualBox 6.1.32 r149290 (Qt5.15.2)	other	VirtualBox 6.1.32	2022-03-17T15:59:04Z	2022-10-22T11:20:35Z	2022-10-22T11:20:35Z	"Steps to reproduce:

* Create a HDD with the Syslinux 6.04 bootloader and add HDAT2 (HDAT2IMG_74.IMG from www.hdat2.com) to the menu
* Start it.

Result: VBox crashes.

NB: This crash does not happen when using the floppy image directly mounted as a floppy"	Artem S. Tashkinov
9052	Have Virtual Machines create .desktop icons for Gnome 3	other	VirtualBox 4.0.8	2011-06-09T16:16:17Z	2011-06-09T16:25:49Z	2011-06-09T16:25:49Z	The Create Desktop Icon is rather useless in Gnome 3 since there is no desktop.   It would be nice if we could have it installed in an area that the Overview page search can find.  That way I can hit the Win-Key -> type Linux and it would show all my Linux virtual machines.	Michael Carter
19829	Hard to move VirtualBox guest windows	all	VirtualBox 6.1.10	2020-08-23T21:48:19Z	2020-08-23T21:52:32Z	2020-08-23T21:52:32Z	"On Ubuntu Mate 20.04.1 folal (but not on 18.04.5 bionic) VirtualBox guest windows won't move unless
1) The focus is starts on a different window.
2) Press the Host key (Right Control)

This worked correctly on Ubuntu Mate 18.04.5 but is broken on 20.04.1

Both systems have VirtualBox 6.1.12 r139181"	Howad
19269	Hard Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)	Linux	VirtualBox 6.1.2	2020-01-26T14:09:11Z	2021-02-02T03:03:30Z	2021-02-02T03:03:30Z	"Upgrading a fedora 28 guest to 31, at the reboot I get a guru
meditation fault.

It seems to be reproducible.

Initially, I was running VirtualBox 5.2.20 r125813 linux.amd64 (Oct 15 2018 17:11:04).
The fault is ""VCPU0: Guru Meditation -2301 (VERR_REM_VIRTUAL_CPU_ERROR)""

I removed VirtualBox from the host and installed VirtualBox to 6.1.2 r135662 linux.amd64 (Jan 13 2020 12:43:05) and its extension pack.
I then attempted to boot the guest.

The fault is ""VCPU0: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)""

The host is Fedora 28 - the details are in your logs, attached.

I did not attach the .PNG files because they consist of (only) a black screen.

However, prior to that, I do see the splash screen, ""Welcome to Grub"",
then the crash.  I use a detachable start - but a ""normal"" start has
the same symptom.

This is a ""hard"" failure - every time I try to start this machine.


Both versions of VirtualBox were installed from download.virtualbox.org/virtualbox/rpm/fedora

I do not plan to revert to VirtualBox 5.*...
"	Timothe Litt
19126	Hard freeze on Centos Host system with Guest using Shared Folders	Windows	VirtualBox 6.0.14	2019-12-03T15:38:08Z	2019-12-09T15:33:25Z	2019-12-09T15:33:25Z	"Running Centos 7.7 Host with a Windows 10 Guest using a Shared Folder. I have experienced issues in the past with Shared Folders, but in the past it only seemed to affect the Guest systems. This issue is hard to troubleshoot since the Host system freezes, I can only resolve it by unplugging the power. I have tried using the SysRq keys to no avail. In troubleshooting the issue, I have stopped all other host applications except VirtualBox and disconnected the Shared folder. For a week, I did not experience any freezing of the host the system. If I connect the Shared Folder I will randomly experience a hard freeze in a couple of hours or a couple of days.

The host system has 16GB RAM and 4 cores. I am using 4GB and 2 cores for my Windows 10 1909 guest.

I do not know how to troubleshoot this any further since the Host system hard freezes, I do not get any indications of problems in any of the host logs. It most likely freezes before documenting the problem. I welcome any tests or settings which you want me to implement in order to determine the problem or fixes.
 "	jim.rather
19415	Gust Additions fails to install correctly on Windows 10 when Graphics Controller set to null	Windows	VirtualBox 6.1.4	2020-03-19T07:19:41Z	2020-03-19T07:19:41Z	2020-03-19T07:19:41Z	"If you
 - disable the graphics controller (by setting it to null)
 - install the Guest Additions on Windows 10 Guest
It will
 - look like it finished
   - the untrained eye will not notice
     - gives an error message about missing hardware in the detailed output
After install
 - the tray icon will be there
   - making you think it worked
 - most (if not all) features enabled by guest additions will not work"	Cameron Tacklind
17358	Guru Meditation when starting Windows 10 VM on Linux after 5.2.2 upgrade	Windows	VirtualBox 5.2.0	2017-12-08T12:16:48Z	2017-12-18T17:31:40Z	2017-12-18T17:31:40Z	"After the Upgrade from VirtualBox 5.2.0 to VirtualBox 5.2.2 the vm no longer starts, it fails with a guru meditation. 

Surprisingly only Windows 10 appears to be affected, any Linux, even ReactOS are working as expected.



The requested PNG file only shows a black screen, little helpful so i only attached the logfile. "	Jörg Skottke
18627	Guru meditation when execute perf top on Linux	Windows	VirtualBox 6.0.6	2019-05-08T03:39:04Z	2019-05-08T03:39:04Z	2019-05-08T03:39:04Z	"This is always reproducible. Steps to reproduce:
1. Boot Windows 10 guest. Image from https://developer.microsoft.com/en-us/windows/downloads/virtual-machines
2. Execute 'sudo perf top' on the Linux host shell.
3. VirtualBox shows a Guru Meditation error dialog.

Host: Ubuntu 19.04
Kernel: Linux 5.0
CPU: i7-8700K
RAM: 32GiB"	Eric Zhang
21027	Guru Meditation on installation	all	VirtualBox 6.1.36	2022-07-21T09:50:16Z	2022-07-21T09:50:16Z	2022-07-21T09:50:16Z	"Hi,

i tried version 6.0, 6.1 from repository and the latest testing 152223 Version. With each i get a error, when i try to install Windows 10 or Kubuntu. See both logs.

Can someone give me a hint, where to search?
"	murrcoss
16933	"guru meditation at ""Starting Windows"" in Windows 7 guest"	Windows	VirtualBox 5.1.24	2017-07-21T20:51:48Z	2018-01-25T21:07:18Z	2018-01-25T21:07:18Z	Windows 7 guest failed to start.	jlong
20151	guru meditation appears when running two VMs	Windows	VirtualBox 6.1.16	2021-01-24T12:24:52Z	2021-01-24T12:24:52Z	2021-01-24T12:24:52Z	"when running two vitualbox vms or a vitualbox vm and a vmware vm , the guru meditation will appears once in a while. When running only one vitualbox vm the prompt do not appears.
Version 6.1.14 and 6.1.16 reach the same ""guru meditation"" prompt.

Vmare works well no matter how many vms opened.
"	rnaa
17993	Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT) while debugging in guest Windows	Windows	VirtualBox 5.2.18	2018-09-18T08:28:14Z	2018-09-26T03:43:32Z	2018-09-26T03:43:32Z	Whenever I try to debug application and/or attach debugger to running process, the machine crashes with Guru Meditation. Crashes on msvc 2010 and msvc 2015.	Marcin Wichtowski
16586	Guru Meditation -2701 (VERR_VMM_RING0_ASSERTION) on Ubuntu 16.04.2 LTS	Linux	VirtualBox 5.0.36	2017-03-20T14:20:03Z	2017-03-20T15:23:34Z	2017-03-20T15:23:34Z	"One of our Production-VMs (the gateway) just crashed with this error after 3.5 days of runtime.

We have no idea how to debug this further.
Googling does not really show up anything helpful either.

* Guest + host have vbox-extensions installed
* host did not run out of ram
* Guest worked fine for weeks prior to getting moved to this Guest-Machine.

Host and Guest are Ubuntu 16.04.2 LTS."	Someone
17426	Guru Meditation -1668 (VERR_PGM_INVALID_CR3_ADDR)	Linux	VirtualBox 5.0.40	2018-01-07T02:07:42Z	2018-01-08T12:07:57Z	2018-01-08T12:07:57Z	Running virtualbox on ubuntu 16.04 host with arch linux as guest after first crash with same error i completelly reinstalled arch so now this error appear on fresh installed system.	Den
17903	Guru meditation (VERR_VMX_INVALID_GUEST_STATE) on any host with any guest.	Windows	VirtualBox 5.2.16	2018-07-28T23:47:08Z	2018-07-29T05:15:35Z	2018-07-29T05:15:35Z	"I have tried numerous BIOS settings and software settings however whenever trying to run a guest on my system (Ubuntu 18.04) I receive (VERR_VMX_INVALID_GUEST_STATE) on both Ubuntu 18.04 and Windows 10 1803 hosts. You can see a list of what I have tried here https://forums.virtualbox.org/viewtopic.php?f=6&t=88833&p=426110#p426110

I have tried downgrading to 5.1.x but I receive hardening issues when doing so. 

Attached are the logs. "	Surgikill
19824	Guru Meditation (tripple fault) while using GNS3	Linux	VirtualBox 6.1.10	2020-08-20T17:37:56Z	2021-04-21T11:07:18Z	2021-04-21T11:07:18Z	"Hello,

I'm using gns3 VM, which launches QEMU VMs, inside virtualbox 6.1.12 (this bugtracker is still missing that version). Today, I got a VINF_EM_TRIPLE_FAULT

I'll attach VBox.log"	Luiz Angelo Daros de Luca
17673	Guru Meditation	all	VirtualBox 5.2.8	2018-04-10T13:36:56Z	2018-04-10T13:37:54Z	2018-04-10T13:37:54Z	Both Ubuntu and Win7 Guest VM	maxine
20224	GUI remains white, popup window is empty when call Settings	Windows	VirtualBox 6.1.18	2021-02-24T23:03:29Z	2021-02-24T23:03:29Z	2021-02-24T23:03:29Z	"Hi, 
When I do call Settings for a VM, the popup window remains white, and no  menue items, I cannot change the settings. 
Linux mint 20.1 with cinnamon, kernel 5.8.0-43 generic. 
when I resize the popup window, remains white. 
Seems to me some problem with java: 
openjdk version ""11.0.10"" 2021-01-19
OpenJDK Runtime Environment (build 11.0.10+9-Ubuntu-0ubuntu1.20.04)
OpenJDK 64-Bit Server VM (build 11.0.10+9-Ubuntu-0ubuntu1.20.04, mixed mode, sharing)


Please review my screenshots. 
thx. 

"	szilike
19905	"GUI glitches on Wayland running ""sudo virtualbox"""	other	VirtualBox 6.1.14	2020-09-20T23:09:18Z	2020-09-21T20:12:14Z	2020-09-21T20:12:14Z	"Buttons and virtual machine names highlight is not working normally when hovering with a mouse and virtual machine window is only partially updated. 

The bug appear on recent GNOME on Wayland running ""sudo virtualbox"".
I've reproduced the bug on Ubuntu 20.04 and Fedora 32. There was no such glitches on earlier GNOME versions from Fedora 31 and there is no such glitches on Xorg, only Wayland and recent GNOME.

VirtualBox is required to run from a privileged user to access physical hard drives (as documented in VB manual chapter 9)."	GnomeUser
15980	Guests won't go in Save States on Host shutdown with Ubuntu 16.04	all	VirtualBox 5.1.6	2016-09-23T19:52:18Z	2016-09-23T19:52:18Z	2016-09-23T19:52:18Z	"I've noticed that since Ubuntu 16.04 (probably since systemd was introduced with 15.04), VMs won't automatically go in savestates on shutdown or reboot of the host.
Following instructions in vboxdrv.sh, I created a virtualbox file in /etc/default, containing SHUTDOWN_USERS=""myuser"" and SHUTDOWN=savestate with no luck.
Here's what I've tested:
1. I've done that test with a fresh install 14.04 and it works like a charm.
2. With 16.04, if I run /usr/lib/virtualbox/vboxdrv.sh stop, all VMs will successfully go in savestate.
3. If I run ""systemctl stop vboxdrv.service"", all VMs will successfully go in savestate as well.
I blame systemd. There seem to be some configuration errors concerning the dependencies in vboxdrv.service but I couldn't figure out how to fix them."	uspinosa
21210	GuestInfo reverts to old data after VM shutdown	all	VirtualBox-7.0.2	2022-10-27T22:16:11Z	2022-10-28T14:33:25Z	2022-10-28T14:33:25Z	"I'm trying to get information about my guests without having to start them. Here's an example of my '''Debian 11''' VM:

'''System is off'''

{{{
/VirtualBox/GuestAdd/HostVerLastChecked  = '6.1.38'                       @ 2022-10-02T23:48:31.042Z
/VirtualBox/GuestAdd/Revision            = '154048'                       @ 2022-10-24T19:03:35.218Z
/VirtualBox/GuestAdd/Version             = '6.1.40'                       @ 2022-10-24T19:03:35.217Z
/VirtualBox/GuestAdd/VersionExt          = '6.1.40'                       @ 2022-10-24T19:03:35.217Z
/VirtualBox/GuestInfo/Net/0/MAC          = '0800273D1A5F'                 @ 2022-10-24T19:03:35.220Z
/VirtualBox/GuestInfo/Net/0/Name         = 'enp0s3'                       @ 2022-10-24T19:03:35.220Z
/VirtualBox/GuestInfo/Net/0/Status       = 'Up'                           @ 2022-10-24T19:03:35.220Z
/VirtualBox/GuestInfo/Net/0/V4/Broadcast = '10.0.2.255'                   @ 2022-10-24T19:03:35.220Z
/VirtualBox/GuestInfo/Net/0/V4/IP        = '10.0.2.111'                   @ 2022-10-24T19:03:35.220Z
/VirtualBox/GuestInfo/Net/0/V4/Netmask   = '255.255.255.0'                @ 2022-10-24T19:03:35.220Z
/VirtualBox/GuestInfo/Net/Count          = '1'                            @ 2022-10-24T19:03:50.225Z
/VirtualBox/GuestInfo/OS/Product         = 'Linux'                        @ 2022-10-24T19:03:35.217Z
/VirtualBox/GuestInfo/OS/Release         = '5.10.0-19-amd64'              @ 2022-10-24T19:03:35.217Z
/VirtualBox/GuestInfo/OS/ServicePack     = ''                             @ 2022-10-24T19:03:35.217Z
/VirtualBox/GuestInfo/OS/Version         = '#1 SMP Debian 5.10.149-1 (2022-10-17)' @ 2022-10-24T19:03:35.217Z
/VirtualBox/HostInfo/GUI/LanguageID      = 'en_US'                        @ 2022-10-24T19:03:53.671Z RDONLYGUEST
}}}

'''System is on, logged in'''
{{{
/VirtualBox/GuestAdd/HostVerLastChecked    = '7.0.2'                        @ 2022-10-27T19:39:15.924Z
/VirtualBox/GuestAdd/Revision              = '154219'                       @ 2022-10-27T19:38:57.972Z
/VirtualBox/GuestAdd/Version               = '7.0.2'                        @ 2022-10-27T19:38:57.972Z
/VirtualBox/GuestAdd/VersionExt            = '7.0.2'                        @ 2022-10-27T19:38:57.972Z
/VirtualBox/GuestInfo/Net/0/MAC            = '0800273D1A5F'                 @ 2022-10-27T19:38:57.975Z
/VirtualBox/GuestInfo/Net/0/Name           = 'enp0s3'                       @ 2022-10-27T19:38:57.976Z
/VirtualBox/GuestInfo/Net/0/Status         = 'Up'                           @ 2022-10-27T19:38:57.976Z
/VirtualBox/GuestInfo/Net/0/V4/Broadcast   = '10.0.2.255'                   @ 2022-10-27T19:38:57.975Z
/VirtualBox/GuestInfo/Net/0/V4/IP          = '10.0.2.111'                   @ 2022-10-27T19:38:57.975Z
/VirtualBox/GuestInfo/Net/0/V4/Netmask     = '255.255.255.0'                @ 2022-10-27T19:38:57.975Z
/VirtualBox/GuestInfo/Net/Count            = '1'                            @ 2022-10-27T19:39:18.000Z
/VirtualBox/GuestInfo/OS/LoggedInUsers     = '1'                            @ 2022-10-27T19:39:17.999Z TRANSIENT, TRANSRESET
/VirtualBox/GuestInfo/OS/LoggedInUsersList = 'ajgringo619'                  @ 2022-10-27T19:39:17.999Z TRANSIENT, TRANSRESET
/VirtualBox/GuestInfo/OS/NoLoggedInUsers   = 'false'                        @ 2022-10-27T19:39:17.999Z TRANSIENT, TRANSRESET
/VirtualBox/GuestInfo/OS/Product           = 'Linux'                        @ 2022-10-27T19:38:57.972Z
/VirtualBox/GuestInfo/OS/Release           = '5.10.0-19-amd64'              @ 2022-10-27T19:38:57.972Z
/VirtualBox/GuestInfo/OS/ServicePack       = ''                             @ 2022-10-27T19:38:57.972Z
/VirtualBox/GuestInfo/OS/Version           = '#1 SMP Debian 5.10.149-1 (2022-10-17)' @ 2022-10-27T19:38:57.972Z
/VirtualBox/HostGuest/SysprepArgs          = ''                             @ 2022-10-27T19:38:49.097Z TRANSIENT, RDONLYGUEST
/VirtualBox/HostGuest/SysprepExec          = ''                             @ 2022-10-27T19:38:49.097Z TRANSIENT, RDONLYGUEST
/VirtualBox/HostInfo/GUI/LanguageID        = 'en_US'                        @ 2022-10-27T19:39:10.318Z RDONLYGUEST
/VirtualBox/HostInfo/VBoxRev               = '154219'                       @ 2022-10-27T19:38:49.151Z TRANSIENT, RDONLYGUEST
/VirtualBox/HostInfo/VBoxVer               = '7.0.2'                        @ 2022-10-27T19:38:49.151Z TRANSIENT, RDONLYGUEST
/VirtualBox/HostInfo/VBoxVerExt            = '7.0.2'                        @ 2022-10-27T19:38:49.151Z TRANSIENT, RDONLYGUEST
/VirtualBox/VMInfo/ResetCounter            = '0'                            @ 2022-10-27T19:38:49.097Z TRANSIENT, RDONLYGUEST
/VirtualBox/VMInfo/ResumeCounter           = '0'                            @ 2022-10-27T19:38:49.097Z TRANSIENT, RDONLYGUEST
}}}
As soon as I shut the VM down, the data reverts to the first list (exactly, including timestamps).  This is not consistent; some VMs retain their data, while others don't. All of my systems in question are using the ISO version of Guest Additions."	ajgringo619
19211	Guest won't boot in EFI mode after deleting/adding main disk file	Linux	VirtualBox 6.1.0	2020-01-08T16:50:31Z	2021-03-18T09:26:14Z	2021-03-18T09:26:14Z	"Setup:
2 VDI disks.
EFI mode enabled (the main disk can only boot in EFI mode).
Hard disk as first device in System/Boot order VM settings.
Regular rebuild of disk images: regular re-add of those images in the storage settings.

After update to VBox 6.1.0, we encountered a bug where after removing and re-adding the bootable media (VDI disk) from the VM storage settings, it won't be able to boot anymore.

It tries to boot in PXE mode and drops into an EFI shell after some time.
I can boot by running the bootx64.efi executable from the shell.

When entering the bios/uefi menu (after exiting EFI shell), we can see that the disk is not in the boot options anymore, there are only PXE and EFI shell.

Reverting to 6.0.14 make it works as expected (boot correctly after disk change)."	vclement
19890	Guest Windows Slowly Shrink Vertically to 103 pixels  and Jump Around on Resize	all	VirtualBox 6.1.14	2020-09-15T16:29:16Z	2020-11-16T19:02:58Z	2020-11-16T19:02:58Z	"Hi,

I started a thread on the Community Forums on this on Sept 3rd, and despite some excellent questions from Volunteer fth0 in Germany, I think it's time for a bug report.

The trail on community is at [https://forums.virtualbox.org/viewtopic.php?f=7&t=99659].  It includes a small video of the shrinking guest windows, plus a bunch of Log files.

----
'''SUMMARY'''

I just upgraded to V 6.1.12 r139181 and I'm seeing some very odd behavior in guest windows. A subsequent upgrade to Version 6.1.14 r140239 (Qt5.14.2), including the extpack and Guest Additions, has not changed anything.

'''DETAILS'''

Guest windows jump around randomly at irregular times, and guest windows slowly shrink vertically '''unless maximized''' after a resize. Over a period of 15 - 20 minutes, a guest windows shrinks, vertically only, until it's 103 pixels in height.  It seems to shrink 1 or 2 pixels at a rate that appears dependent on the host machine's loading, but often around every 1 or 2 seconds.  This makes it impossible to do much with the guest OS, because any menu picks get removed by the window redraw before an option can be chosen.

Horizontal size seems to be irrelevant.  Scale factor in Display Setting for all guests is 100%.

If I resize a guest window, it will jump elsewhere randomly - often to another screen or straddling two monitors, and then start shrinking.


This happens on both Windows and Linux guests, with VBoxVGA and VBoxSVGA graphics controllers. It has only started since the update to the 6.1.12 and 6.1.14 versions...all was fine before that.

The host machine is an 8 physical core (16 virtual) AMD Ryzen 7 2700X PowerSpec G162 with an AMD Radeon RX580 GPU, with 48G RAM and 15Tb Storage so it can handle the VBox load.
The machine is running KDE Neon 5.19.4, which is KDE's own distro, based on Plasma 5.19.4 and the 5.14.2 Kernel. I have compositing switched on for full KDE effects.
I have 3 4k Monitors, although I don't think that's relevant.

The Log files contain large numbers of repeats of these lines, with the X size reducing by 1 or 2 pixels each time, until 103 is reached.


{{{
00:04:30.078206 GUI: UIMachineView::sltPerformGuestResize: Sending guest size-hint to screen 0 as 2245x103 if necessary
00:04:30.182443 VMMDev: SetVideoModeHint: Got a video mode hint (2245x103x32)@(0x0),(1;0) at 0
00:04:30.182825 VMMDev: Guest Log: Got multi resize request 1 displays
00:04:30.182851 VMMDev: Guest Log: [0]: 0 0x39 0,0 2245x103 32
00:04:30.194294 GUI: UIMediumEnumerator: Medium-enumeration finished!
00:04:30.205602 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=00007f9698000000 w=2245 h=103 bpp=32 cbLine=0x2314 flags=0x1 origin=0,0
}}}


At fth0's suggestions, I tried setting extradata to various initial window sizes, to see if that affected the shrinking behaviour, but it hasn't made much difference.





"	PHands
15094	Guest windows move to leftmost monitor on X11 when guest resizes its display	all	VirtualBox 5.0.14	2016-01-29T19:50:21Z	2016-01-29T19:50:21Z	2016-01-29T19:50:21Z	I have two Linux host machines running different versions of GNOME (RHEL6 - GNOME 2.28 and Arch - GNOME 3.18), both with multiple (host) monitors.  On both of them, whenever a guest resizes its display (e.g. switching from the bootloader to the guest's GUI, or changing display resolutions from within the guest), the guest window will be moved over to the leftmost monitor if it isn't already there.	Michael Hansen
17337	guest windows distorted in seamless mode works on 5.2.2 (no such problems on 5.1.30)	Windows	VirtualBox 5.2.0	2017-11-30T21:09:33Z	2018-02-15T20:19:34Z	2018-02-15T20:19:34Z	"== STEPS TO REPRODUCE
 1. Using Kubuntu Trusty host, Create XP VM in ≤ 5.1.30. Seamless mode should work fine (see expected results below).
 2. Upgrade to 5.2.2. 
 3. Boot XP guest.
 4. Switch to seamless mode.

== EXPECTED RESULTS
 1. Guest desktop disappears.
 2. Host window decorations disappear.
 3. Space is drawn on the host desktop for the guest windows.
 4. Guest windows act like host windows, responding appropriate to movement, e.g.
 5. Guest windows appear normally.

== ACTUAL RESULTS
All of the above assumptions are correct except for the 5th one. The space is drawn, the windows act normally, there are no other decorations, but every guest window is a visual nightmare. See attached screenshot.

== NOTES
 * Host is Kubuntu Trusty running the 4.2.0-42-generic kernel and is fully up to date and restarted.
 * Tested with versions from the repos at download.virtualbox.org: 5.1.30-118389~Ubuntu~trusty and 5.2.2-119230~Ubuntu~trusty. In both cases, the expansion packs and guest additions were updated accordingly.
 * Guest video memory is maxed out.
 * Turning acceleration off, enabling both 2D/3D or one or the other had no effect.
 * Initially the guest was using multiple monitors. Disabling the virtual screen had no effect. Lowering the number of monitors to one had no effect, either.
 * Full screen, scaled, and normal modes all function appropriately.
 * VM has been running for years with no problems.
 * Logs are attached. You should see the switch to seamless at 0:00:48.457777."	Walter Lapchynski
19783	Guest Windows Desktop load fails if Guest Additions Direct3D installed	Windows	VirtualBox 6.1.10	2020-07-30T20:59:28Z	2020-07-30T20:59:28Z	2020-07-30T20:59:28Z	"Host: Ubuntu 18.04 kernel 4.15.0-112
VBox: 6.1.12
Guests:
(a) Windows Server 2008 64bit
(b) Windows Vista 64bit
(c) Windows Vista 32bit

Problem:
When, during the install of the VBox Guest Additions 6.1.12, the Direct3D support is selected (default=selected), on the subsequent reboot, after the user credentials have been entered and the login succeeds, the desktop fails to load. The VM either performs a reset after a few seconds (a) or hangs indefinitely ((b) and (c)).

The problem is reproducible.

The problem disappears when the Direct3D support is disabled during installation of the VBox Guest Additions.

The problem does NOT show with a Windows Server 2008 32bit version.

The problem is independent of the setting of the 3D Acceleration in the VM Display Settings.


[P.S.: The 'Create New Ticket' webpage does not allow the selection of 'VirtualBox 6.1.12' in the Version dropdown selector. 6.1.12 is not present there. So I chose 6.1.10.]"	sunrider
14267	Guest windows 7 x64  crashes in BSOD after upgrading to VB v5.0 unless nested paging left OFF	Windows	VirtualBox 5.0.0	2015-07-13T11:05:17Z	2015-07-31T11:07:36Z	2015-07-31T11:07:36Z	Recently I upgraded to VB 5.0 on Linux Mint host machine. When I try to start my Windows 7 x64 guest machine it enters BSOD with 0x0000007E exception unless I switch nested paging feature OFF. Under VB 4.3 it was on and ok. Attaching VBox.log for more details.	dvb15
19115	Guest Windows 7 Aero don't working since v.6.0.14 (VboxSVGA, 3D, 2D active)	Windows	VirtualBox 6.0.14	2019-11-28T11:38:32Z	2020-01-15T19:15:25Z	2020-01-15T19:15:25Z	"Hi, after Update to Virtualbox 6.0.14 witch Extensions, my Guest Windows 7 Aero don't working, the Startmenu and Taskbar are blur, I can't see the items. The same in two different W7-guests. Guest-Tolls are installed v.6.0.14 with 3d-experimental driver. If I switch to VBoxVGA, all functioning perfect. My Host is Ubuntu 18.04. With Virtualbox v.6.0.12 were all W7-guests OK.

Please help
Best regards
Peter"	user324
20590	Guest window size decreases on login (Linux)	Linux	VirtualBox 6.1.26	2021-10-01T20:18:32Z	2021-10-04T19:23:20Z	2021-10-04T19:23:20Z	"I had one OpenSuSE 15.2 guest machine unexpectedly go back to a resolution of 1024X768 after rebooting and logging in. I was able to click and drag the window to increase the display size to fix the issue.

Things that didn't work were:
using the display settings within the OS to set a resolution
Using the View menu to set Auto-resize Guest Display and then use the View menu to set the display size for Virtual Screen 1.
In both cases the screen would resize as expected but, after a reboot and logging in again the screen size would jump back to 2014X768. When 3D acceleration was turned off I could see that the screen size was initially at the selected size before jumping back to 1025X763. With 3D acceleration turned on I cannot see the jump.

3D acceleration was initially turned off. Turning it on didn't change the symptoms.
Using VMSVGA "	Patrick Headley
14718	guest window resizes to a very minimal size (vertically)	all	VirtualBox 5.0.6	2015-10-19T13:09:20Z	2018-05-21T17:57:37Z	2018-05-21T17:57:37Z	"This started when I upgraded from 4.3.30 to 5.0.6 using RPMs for openSUSE 13.2 as provided by virtualbox.org.
Every guest resize event leads to the host window to become very small (height is very minimal; width also but not that much). I can provide a screenshot when required.
This happens for every guest system (Windows, Linux etc). For Windows where the default is that the guest resizes to adapt to the host window it's worst because every resize of the host window results in a resize event within the guest which immediately makes the host window small again. I have to disable the the automatic guest resizing to be able to do anything."	Wolfgang Rosenauer
15156	Guest Win10 graphics driver never loads with 3D acceleration enabled on Linux Host	Windows	VirtualBox 5.0.14	2016-02-17T22:33:09Z	2016-10-06T23:42:31Z	2016-10-06T23:42:31Z	"Hi,

Win10 x64 acceleration has never worked for me, since even before 5.x came out. The boot splash screen works correctly, but when the login screen is supposed to appear, instead I see the cursor cycle endlessly between pointer -> busy -> background busy over a black screen; the login screen never appears.
My guest is entirely up to date and has Oracle (i.e. not Ubuntu) additions 5.0.14 installed; other additions functionality seems to work fine (including guest display resizing if acceleration is disabled).
My host is Ubuntu 15.10 x64 running Oracle Virtualbox 5.0.14. I am using Oibaf's git snapshot mesa+drivers ppa in the given log, but I see exactly the same behaviour using the stable graphics stack. (I'm on Intel 4th gen graphics)
VBox log attached - is there any other information I can provide?"	akdor1154
17791	Guest VM becomes unresponsive after 2 or 3 days continuous uptime	Windows	VirtualBox 5.2.12	2018-05-30T20:35:20Z	2018-09-04T18:09:22Z	2018-09-04T18:09:22Z	"Using CentOS 7.5.1804 host and Windows 7 guest with dual monitors full screen, USB mouse.

After the VM has been running continuously for about 2 or 3 days, the VM starts going into an abnormal wait state. The cursor can be moved with the mouse, but it changes from a pointer to a blue circle after clicking on something. At first, the ""wait state"" circle is short-lived, changing back to the normal pointer after less than a second. The problem gets worse over time and the cursor will begin to flash between normal pointer and blue circle a few times and then for longer and longer intervals. The longer I let it go, the more time it spends in the wait state. When the cursor is displayed as a blue circle, any button press on the mouse is ignored as well as key presses on the keyboard, although there was one time that I must have been clicking all over the place trying to get a response and on killing the VM, those clicks seemed to appear in the Linux host.

If I let the problem persist and don't reboot the VM, eventually the VM becomes completely unusable. The cursor stayed as a blue circle for over 30 minutes one time before I gave up and killed it. I have to reboot the VM to clear the problem and when I first started doing that, I would halt the VM and also reboot the Linux machine. More recently, I have only been shutting down the VM and restarting it. Earlier today, I shut down the VM and restarted, but noticed I was still having the problem. I shut the VM down again, exited the VB GUI console and made sure all VB processes were stopped, then started it back up. That cleared the problem.

When the guest system enters a wait state hang, CPU utilization on both host and guest still seem normal; no CPUs are pegged. When the guest seems to have entered a permanent wait state, it is still getting work done. I have had this happen when the Windows task manager was running and showing the CPU usage history. I had it set to slow updates, meaning it should update every 4 seconds but I was getting updates more like around 16 seconds.

I had been using the paravirtualized network driver and wondered if that could be a problem, so changed to the Intel PRO/1000 MT Desktop adapter with no change.

I first started having this problem in later versions of 5.0 on CentOS 6 and I had other problems with 5.1 so didn't run that for any appreciable amount of time. I have captured trace files of a hung VM if that could be useful to anyone.

I see similar reports on the forum about lost mouse clicks, and dual monitors may be one of the conditions required to reproduce.
"	linus100
15833	Guest video driver doesn't work with host's Nvidia card	Windows	VirtualBox 5.1.2	2016-08-20T03:18:29Z	2019-06-07T13:13:00Z	2019-06-07T13:13:00Z	"I have two video cards on my host system: Intel 530 and Nvidia GT 610. On Intel's card everything is okay, but when I'm switching to the Nvidia, guest Windows 10 doesn't load video driver properly and reports following message in device's properties: ""Windows has stopped this device because it has reported problems. (Code 43)"". Window auto resize doesn't work."	ashep
20546	Guest suspended with DiskFull error when using fixed size VDI	Linux	VirtualBox 6.1.26	2021-09-13T21:58:24Z	2021-09-14T06:52:48Z	2021-09-14T06:52:48Z	"VirtualBox guest with fixed size VDI file is suspended when the host runs low on disk space.
Fixed size VDI files should never trigger a disk full condition as they are a fixed preallocated size that will never expand.

VirtualBox build 146314
Host: Fedora Linux 33
Guest Fedora Linux 34
Log File Info:
VD#1: Host disk full
VM: Raising runtime error 'DrvVD_DISKFULL' (fFlags=0x6)
Console: VM runtime error: fatal=false, errorID=DrvVD_DISKFULL message=""Host system reported disk full. VM execution is suspended. You can resume after freeing some space""

VBoxManage showmediuminfo disk ...
Storage format: VDI
Format variant: fixed default
Capacity:       66560 MBytes
Size on disk:   66562 MBytes"	RP15873
21337	Guest start aborted every time when bridged network interface name changes	all	VirtualBox-7.0.4	2022-12-13T20:35:52Z	2022-12-13T20:41:08Z	2022-12-13T20:41:08Z	"Attaching to physical interface via bridge adapter may cause guest to crash at start up. Every time when laptop is connected to docking station the network interface changes under Linux.

The error message displayed with VB 6.1. There one can change the network settings by pressing ""Change Network Settings"" button. With VB 7.0 the VM simply crashed after that button has been pressed."	EmergReanimator
18009	Guest screen size is not same as window size HiDPI @1.5 Linux host	Windows	VirtualBox 5.2.18	2018-09-25T13:56:06Z	2018-09-25T13:56:06Z	2018-09-25T13:56:06Z	"Host openSUSE Tumbleweed 2018-09-23
VirtualBox 5.2.18_SUSE r123745
Qt 5.11.1
HiDPI@1.5

Guest Windows 10
VirtualBox additions installed
2D accelerate
3D accelerate
VirtualBox screen scale 100%
Windows display scale 150%

Guest system display is smaller than the window, leaving black space around. Mouse pointer is wrongly mapped to the whole window instead of guest system display area.

[[Image(https://i.imgur.com/nPo9esr.png)]]"	Guo Yunhe
18562	guest screen flickering by 3d acceleration on	Windows	VirtualBox 6.0.4	2019-04-16T03:18:06Z	2019-10-19T00:31:46Z	2019-10-19T00:31:46Z	"Hello,
My Windows 10 guest screen of apps in Ubuntu-18.04 host shows flickering and/or overlapping.
- Flickering 3~5 times while the tile menu brings up by clicking Start button
- Overlapping top-left area of a window especially graphical apps, e.g. youtube, web browser
I did many googling and reading virtual box forums with similar issues and solutions but no effect for me.
- Turning 3d acceleration off is a solution but drawing is too slow!
- export CR_RENDER_FORCE_PRESENT_MAIN_THREAD=0 in /etc/profile.d/my-cr-test.sh - no effect
- replace /usr/lib/virtualbox/VBoxOGLrenderspu.so with compiled one from source codes - no effect
My hardware and software:
  - AMD Ryzen 5 2600 16GB: Ubuntu 18.04.2 LTS
  - NVIDIA GeForce GTX 1050 2GB: nvidia-driver-418  
Please check it.
  "	siriusjt
16452	Guest OS time is not in sync with host OS time after host is awake from sleep mode	Windows	VirtualBox 5.1.14	2017-02-04T16:42:10Z	2019-07-10T08:51:22Z	2019-07-10T08:51:22Z	"Details:
Host OS - Win 7 64x
Guest OS - Ubuntu Desktop 64x

Steps to replicate:
Start the Guest OS in VM box.
Put the Host OS in sleep mode.
Start the Host OS after some time from sleep mode.
Observe the clock on guest OS in VM, it displays the time when the host was put in to sleep. (I usually put to sleep after leaving work and start next day)
Even after login to Guest OS, the time doesn't sync have to manually sync.

Please see the screen shot for reference.
Couldn't find a reference to this issue in community."	anurag26
16904	guest OS screen and host OS screen	Linux	VirtualBox 5.1.22	2017-07-16T00:28:49Z	2017-07-28T05:51:21Z	2017-07-28T05:51:21Z	"My host OS is https://parabola.nu  with XFCE desktop .
I downloaded virtualbox latest version, SHA256 is right. And I run 'pacman -S gcc make linux-libre-headers' as root , and then virtualbox successfully installed.
Sometimes I use Ctrl + Alt + F1 to switch to terminal and use Alt + F2 to back to graphical user interface. I installed some guest OSes , one of the guest OSes is parabola too . When the guest OS sleeps, my host OS decreases screen brightness too"	vbgaofei
17158	Guest OS Additions crashes Windows XP and Windows 7 Guests	Windows	VirtualBox 5.1.28	2017-10-11T23:39:27Z	2017-10-11T23:39:27Z	2017-10-11T23:39:27Z	"This one is new to me. I was previously running an XP Guest x86 using VB 5.1 under Windows 10 Pro x64. Everything was fine. I had virtualization, nested pages, etc. enabled.

I then installed VB 5.1 under Ubuntu 16.04.LTS, x64 (of course), on ""super spiffy"" (that's ""shiny"") hardware and re-created the XP Guest x86. Things ran OK for a while and then began crashing.

I had been thinking about moving the ""content"" (applications) to a virtual Windows 7 box instead anyway, so I created a new Windows 7 x86 Guest. Again, everything ran fine for a while, and then would all of a sudden crash, or not boot, or freeze.

After having pulled my hair out for a few days, I tried uninstalling the VirtualBox GuestOS Additions. First from the XP Guest, and when that got a lot more stable, I did the same thing for the Windoes 7 Guest.

No more crashes, no more sudden freezing, no more BSOD.
(Or at least not yet, two days and counting.)

Every once in a while though, Ubuntu will report a ""System Problem"" and the VirtualBox Guest Window disappeares. In the Ubuntu crash log it says ""This is not an official version ..."" (I'm assuming they're talking about VirtualBox since the 16.04 dist contains 5.0.x). When that happens, however, I am still connected via RDP to the actual Guest OS, and it continues to run."	joho68
18135	Guest network down with version 5.2 and e1000	Linux	VirtualBox 5.2.20	2018-11-17T15:07:25Z	2018-11-17T15:07:25Z	2018-11-17T15:07:25Z	"After an upgrade from 5.1.38-122592 to 5.2.20-125813 the guest network did not automatically come up. The network worked fine after bringing the interface down/up.
Another copy of the same VM running on different hardware with identical software did not have the problem.

Both VMs were using E1000 network adapters in bridged mode. Switching to either of the PCnet adapters fixed the issue on the ""not working"" system.

[Beware: User speculation] The not working system is slower and it looks like there was a recent change to the E1000 LinkUpDelay from 5000ms to 3000ms. I'm suspecting that the shortened delay may be related to the problem. I could not find a configuration setting for the LinkUpDelay.

Host systems: Debian 9 (stable) 64 bit (fully up to date)

Guest systems: Debian 9 32 bit (fully up to date)

About the VirtualBox version. I first noticed the issue on 5.2.20, but did not have a chance to gather logs until after upgrading to 5.2.22. Both versions have the issue.

Not working hardware:
{{{
  AMD Turion(tm) 64 Mobile Technology ML-34 (800 MHz single core)  
  Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8100/8101L/8139 PCI Fast Ethernet Adapter (rev 10)
	Subsystem: Hewlett-Packard Company RTL-8100/8101L/8139 PCI Fast Ethernet Adapter
	Flags: bus master, medium devsel, latency 128, IRQ 22, NUMA node 0
	I/O ports at a000 [size=256]
	Memory at c020a400 (32-bit, non-prefetchable) [size=256]
	Capabilities: [50] Power Management version 2
	Kernel driver in use: 8139too
	Kernel modules: 8139cp, 8139too
}}}
Working hardware:
{{{
  Intel(R) Core(TM)2 Duo CPU T7100 @ 1.80GHz (dual core, 800 MHz)  
  Ethernet controller: Broadcom Limited NetLink BCM5787M Gigabit Ethernet PCI Express (rev 02)
	Subsystem: Hewlett-Packard Company 6710b
	Physical Slot: 1
	Flags: bus master, fast devsel, latency 0, IRQ 30
	Memory at e4000000 (64-bit, non-prefetchable) [size=64K]
	Expansion ROM at <ignored> [disabled]
	Capabilities: [48] Power Management version 3
	Capabilities: [50] Vital Product Data
	Capabilities: [58] Vendor Specific Information: Len=78 <?>
	Capabilities: [e8] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [d0] Express Endpoint, MSI 00
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [13c] Virtual Channel
	Capabilities: [160] Device Serial Number 00-1c-c4-ff-fe-c9-02-6d
	Capabilities: [16c] Power Budgeting <?>
	Kernel driver in use: tg3
	Kernel modules: tg3
}}}"	FixItDad
16958	Guest display auto-resize dit not work anymore	Windows	VirtualBox 5.1.26	2017-07-29T15:41:06Z	2017-07-29T15:41:06Z	2017-07-29T15:41:06Z	"Guest display auto-resize worked perfectly for years (Windows 10 guest on Kubuntu 14.04 host). Since upgrade to VirtualBox 5.1.26 r117224 (from 5.1.24 r117012), the display resolution is not evaluated properly.

At startup the VM display resolution is wrong in fullscreen mode (1920x1080 instead of 1340x1440 on the host). There is no way to set it manually in Windows display properties settings. The maximum proposed resolution is 1920x1080. The host resolution (1340x1440) is not present in the proposed list.

The following workaround works:

* Disable ""Auto-resize Guest Display""
* Enable it again immediately (without any screen mode change before)

Then the guest window is set to the proper resolution (and this resolution become available in the Windows display settings).

'''Remark:''' there is another bug. Just after the VM startup (in fullscreen mode), this workaround cannot be applied directly. In the mini bar, the ""Auto-resize Guest Display"" option is not clickable (like if it was disabled). Pressing <host>-F  (to exit fullscreen mode) then  pressing <host>-F one time again (to get back in fullscreen mode) fixes it. The ""Auto-resize Guest Display"" option become operable.

The effect of the workaround is very volatile. If, for any reason, the guest display resolution is reevaluated, then the correct resolution is lost. For example, in all the following situations (but not limited to), the correct resolution is lost and the workaround has to be applied again to recover the correct screen resolution:

* The VM state is saved and the restored later
* The VM window is minimized and then restored on the host.
* The guest screen mode is changed (any mode), then restored to fullscreen.
* ...

Apparently, any action that conduct to reevaluate the guest display resolution bring back a wrong one (except if you are lucky and have a 1920x1080 display). The workaround must be applied again to get back to the correct screen resolution.

== Environment ==

=== Host ===

* OS : Ubuntu 14.04.1 (88~14.04.1-Ubuntu SMP Fri Jan 13 14:54:07 UTC 2017 )
* Kernel release: 3.19.0-80-generic
* Platform: x86_64
* Desktop: KDE (kubuntu-desktop)
* KDELibs Version: 4.13.3
* Qt version: 4.8.6
* VirtualBox version: 5.1.26 r117224

=== Guest ===

* OS: Windows 10 Pro
* Version: 1703 15063.483
* Platform: x64
* VirtualBox Guest Additions: 5.1.26




 "	Laurent Simon
17287	Guest crashed when connecting to remote system using Remote Desktop	Windows	VirtualBox 5.2.0	2017-11-18T06:00:24Z	2017-11-18T06:00:24Z	2017-11-18T06:00:24Z	The title says it all. And I wouldn't even bother opening a new ticket if it happened once, but it actually happened twice in a row. There was no guru meditation. The guest window simply disappeared. I restarted the guest and tried to establish connection to remote system, and again the same thing happened. On the third attempt the connection was successful, but there might be something in the log files from those 2 sessions that will allow you to find and fix the bug. 	Rafcio
14495	Guest crash when drag and drop file into it on Linux host	all	VirtualBox 5.0.2	2015-08-25T12:00:59Z	2015-08-27T09:14:29Z	2015-08-27T09:14:29Z	"When I drag a file to a Windows XP guest, the virtual machine crash and state change to ""Aborted"". 
Tried Linux Mint guest, same problem. 
"	FiveYellowMice
16868	Guest background not fully cleared in seamless mode	Windows	VirtualBox 5.1.22	2017-07-03T09:33:11Z	2017-07-03T09:33:11Z	2017-07-03T09:33:11Z	I'm running Windows 7 Pro as guest on a Linux Mint 18.1 host (both 64 bit). Seamless mode seems to work quite well despite relatively slow redrawing of guest windows. But there is a problem with the suppression of the windows background: There is always a square of the windows desktop keeping on the host desktop and I cannot get rid of it.	Mellon
17493	Guest audio pass via vRDP sound weird (jitter?)	Windows	VirtualBox 5.1.32	2018-01-22T17:50:33Z	2018-10-29T11:18:55Z	2018-10-29T11:18:55Z	"HOST is Debian 9.3[[br]]GUEST is Windows XP

What sound like: Jitter? echo in the tunnel?[[br]](It may not be noticed if playback duration is less than a second.)

At first I suspect that remmina client cause it. Later I found Microsoft's RDP client (mstsc.exe) also run into this.

Tried to change sound back-end between PulseAudio and ALSA, No avail."	NoNoNo
18071	Guest audio pass via vRDP no sound at all	all	VirtualBox 5.2.20	2018-10-23T10:37:08Z	2019-05-11T23:40:16Z	2019-05-11T23:40:16Z	"HOST is Debian 9.5[[BR]]GUEST is Windows XP and Debian 8

Situation change after VBox 5.1.x ([https://www.virtualbox.org/ticket/17493 # 17493]). From weird sound to heard no sound with VBox 5.2.20.

Both clients, remmina and Microsoft's mstsc.exe, got the same situation."	NoNoNo
18169	Guest Additions will not install properly in Centos	Linux	VirtualBox 5.2.22	2018-12-04T23:46:36Z	2018-12-14T10:19:53Z	2018-12-14T10:19:53Z	"{{{
/tmp/vbox.0/vbox_ttm.c: In function ‘vbox_bo_unpin’:
/tmp/vbox.0/vbox_ttm.c:486:2: error: too many arguments to function ‘ttm_bo_validate’
  ret = ttm_bo_validate(&bo->bo, &bo->placement, false, false);
  ^
In file included from /tmp/vbox.0/vbox_drv.h:92:0,
                 from /tmp/vbox.0/vbox_ttm.c:31:
include/drm/ttm/ttm_bo_api.h:344:5: note: declared here
 int ttm_bo_validate(struct ttm_buffer_object *bo,
     ^
/tmp/vbox.0/vbox_ttm.c: In function ‘vbox_bo_push_sysram’:
/tmp/vbox.0/vbox_ttm.c:525:2: error: too many arguments to function ‘ttm_bo_validate’
  ret = ttm_bo_validate(&bo->bo, &bo->placement, false, false);
  ^
In file included from /tmp/vbox.0/vbox_drv.h:92:0,
                 from /tmp/vbox.0/vbox_ttm.c:31:
include/drm/ttm/ttm_bo_api.h:344:5: note: declared here
 int ttm_bo_validate(struct ttm_buffer_object *bo,
     ^
make[2]: *** [/tmp/vbox.0/vbox_ttm.o] Error 1
make[1]: *** [_module_/tmp/vbox.0] Error 2
make: *** [vboxvideo] Error 2
}}}"	bc
19664	Guest Additions prevent Lubuntu desktop from starting	Linux	VirtualBox 6.1.10	2020-06-14T18:23:45Z	2020-08-04T10:21:05Z	2020-08-04T10:21:05Z	"The guest is a 32 bit Lubuntu 18.04 Linux machine. The host is a 64 bit Ubuntu 18.04 Linux machine.

The guest works great as long as I do not install Guest Additions. After installing Guest Additions, I get the login / greeter screen, but after logging in, the desktop does not start.

To test this, I created the virtual machine and restarted it many times, logging in successfully. After one of these logins, I took a snapshot and installed Guest Additions. After that and a restart, the desktop did not start.

To confirm that the snapshot was not the problem, I restored the snapshot and did not install Guest Additions. I was able to restart and have the desktop start.

I would be happy to provide additional information but I do not know what would be helpful."	Organic_Marble
18881	Guest additions installation fails with: The network operation failed with the following error:  During network request: Unknown reason.	other	VirtualBox 6.0.10	2019-08-29T20:43:10Z	2019-08-29T21:50:24Z	2019-08-29T21:50:24Z	"When clicked ""Devices -> Insert Guest Additions CD Image..."" it starts downloading the Guest Additions image and when the download is at about cca. 80% it always fails with the following error:

The network operation failed with the following error: 
During network request: Unknown reason.

Which is really not helpful error. I can download the Guest Additions by hand and manually install it. My network is working OK. Also VirtualBox strace didn't reveal anything suspicious.

It seems this problem has been already reported in various downstream bug trackers across distributions.

I am able to reproduce this problem on Fedora 30 host, RPMFusion VirtualBox package:
VirtualBox-6.0.10-1.fc30.x86_64
The guest is Windows 10 Home 32 bit, but it doesn't seems this is important for the reproducer."	yardas
20861	Guest Additions do not build on Centos Stream 8	Linux	VirtualBox 6.1.32	2022-03-07T15:04:04Z	2022-03-22T16:11:33Z	2022-03-22T16:11:33Z	"Updated to the latest kernel on CentosStream 8: 4.18.0-365.el8.x86_64 and the Guest Additions does not compile anymore.
Tried the 6.1.32, then the latest 6.1.33-149980 and the result is the same: the vbox_drv.h tries to include drm/ttm/ttm_memory.h which is not available anymore in this kernel release (apparently the ttm subtree was restrustured)."	piters
15994	Guest additions detect GB as KB and claims about too less free space	Linux	VirtualBox 5.1.6	2016-09-27T22:07:04Z	2016-09-27T22:07:04Z	2016-09-27T22:07:04Z	"On installing the guest additions on Android 4.4 I'm getting these errors:

{{{
Uncompressing VirtualBox 5.1.6 Guest Additions for Linux-kP: No such file or directory
mnt/VBoxLinuxAdditions.run[367]: 7.2G: unexpected '.'

Not enough space left in /data/local/tmp (7.2G KB) to decompress mnt/VBoxLinuxAdditions.run (7912 KB)
Consider setting TMPDIR to a directory with more free space.
}}}"	Sworddragon
17215	Guest additions command line updating fails (Linux host, Windows guest) => Obsolete	Windows	VirtualBox 5.2.0	2017-10-27T09:13:59Z	2022-04-19T14:54:50Z	2022-04-19T14:54:50Z	"I have a Linux host (Ubuntu 16.04, 64 bits) and a Windows guest (Windows 7 professional, 64 bits). I try to update the guest additions using the command line.

So I issue the command (from the Linux host, with the VM guest powered on):
{{{
VBoxManage guestcontrol ""win7""  updateadditions --source /usr/share/virtualbox/VBoxGuestAdditions.iso --verbose
}}}
The command fails and I get the following output:
{{{
Updating Guest Additions ...
Using source: /usr/share/virtualbox/VBoxGuestAdditions.iso
VBoxManage: error: Could not open guest session: VERR_TIMEOUT
VBoxManage: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005), component GuestWrap, interface IGuest, callee nsISupports
VBoxManage: error: Context: ""UpdateGuestAdditions(Bstr(strSource).raw(), ComSafeArrayAsInParam(aArgs), ComSafeArrayAsInParam(aUpdateFlags), pProgress.asOutParam())"" at line 3667 of file VBoxManageGuestCtrl.cpp
}}}
I tried with Virtualbox 5.1.30 and 5.2.0 and I get the same result.

Manually updating the guest additions (withon the guest) works as expected.

And I was also able to start a program within the guest, using commands like:
{{{
VBoxManage guestcontrol ""win7"" --username my_account run --exe ""C:\Windows\System32\notepad.exe""
}}}
So, I think this issue is clearly a bug..."	roland651
14245	Guest Additions are broken when built with new versions of system Mesa	Linux	VirtualBox 4.3.28	2015-07-06T15:43:24Z	2015-08-01T20:20:57Z	2015-08-01T20:20:57Z	"Most Linux distributions use system versions of Mesa instead of the bundled Mesa 7.2. But with new versions of Mesa Guest Additions are broken. For example, glxinfo reports (null) for ""OpenGL renderer string"" and other glGetString() requests.

This patch from Fedora is used for new Mesa support by various distributions:

http://cvs.rpmfusion.org/viewvc/rpms/VirtualBox/devel/VirtualBox-4.3.10-mesa_guest.patch?revision=1.1&root=free&view=markup

Likely it's incomplete.

Perhaps Virtual Box 5.0+ should support Mesa 10+ because Mesa 7.2 is really old."	Pulfer
17756	Guest (windows 10) cannot detect microphone (playback works fine)	Windows	VirtualBox 5.2.12	2018-05-11T08:57:28Z	2018-07-03T07:40:51Z	2018-07-03T07:40:51Z	"Host: Debian stretch

Guest: Windows 10

Audio Controller: Intel HD Audio 

Virtualbox version:5.2.12 r122591

Playback works fine, but windows 10 (guest) cannot detect microphone (there is no microphone in the devices list) (microphone in host works perfectly)"	MeatShooter
7952	gues key mapping problem while host is using XkbOptions	Linux	VirtualBox 4.0.0	2010-12-30T09:23:05Z	2011-01-19T02:02:53Z	2011-01-19T02:02:53Z	"My host is archlinux with xorg 7.6, and i am using XkbOption for some key mapping workaround, like blow:


{{{
 Section ""InputClass""
         Identifier ""evdev keyboard catchall""
         MatchIsKeyboard ""on""
         MatchDevicePath ""/dev/input/event*""
         Driver ""evdev""
     Option ""XkbLayout"" ""us, de""
     Option ""XkbOptions"" ""ctrl:swapcaps, grp:menu_toggle""
 EndSection
}}}


with this configuration, the keys ""CapsLock"" and ""Ctrl"" are swapped, and the key ""Menu"" is mapped to ""ISO_Next_Group"".

This workaround works fine before I updated virtualbox to 4.0.0. after updated i found it does not work for guests (neither for linux or windows guest). I've tried using xev in the guest to catch what happend. When I press down ""CapsLock"", it should be ""Control_L"", but it is ""CapsLock"".

It seems that virtualbox has ignored the XkbOptions and accesses the keyboard as is."	Zer4tul
17473	GRUB countdown problem	Linux	VirtualBox 5.1.26	2018-01-18T02:46:21Z	2018-01-23T10:14:51Z	2018-01-23T10:14:51Z	"The file /etc/default/grub   contains GRUB_TIMEOUT=5 by default . After starting my Guest OS , it will show a sentence ""The highlighted entry will be executed automatically in 5s"" .
VirtualBox has such a problem that makes GRUB (That's Guest OS ,but not host OS) unable to show this sentence when it's countdowning at 5s . After countdowning at 5s , GRUB shows 4s 3s 2s and 1s very normally . This problem doesn't always appear ,but only sometimes appears "	vbgaofei
17603	"Group of device files changes after running VirtuaBox with ""raw partitions image"""	Windows	VirtualBox 5.2.8	2018-03-07T14:24:26Z	2018-03-07T14:24:26Z	2018-03-07T14:24:26Z	"I'm using VirtualBox to run a ""real"" Windows 10 installation, using an image created according to the instructions in section 9.9.1.2 under https://www.virtualbox.org/manual/ch09.html#rawdisk. The actual partition numbers specified were 1,2,3 in my case.

This works fairly well, but there is one slight issue: The group ownership of the /dev files corresponding to the above mentioned partitions changes after I complete the VirtualBox session. The following sequence of shell commands and output should illustrate what happens:

{{{
[toralf@osl-97214 ~]$ ls -tlra /dev/sda[123]
brw-rw---- 1 root disk 8, 1 Mar  7 14:54 /dev/sda1
brw-rw---- 1 root disk 8, 3 Mar  7 14:54 /dev/sda3
brw-rw---- 1 root disk 8, 2 Mar  7 14:54 /dev/sda2
[toralf@osl-97214 ~]$ VirtualBox --startvm Win10partition
[toralf@osl-97214 ~]$ ls -tlra /dev/sda[123]
brw-rw---- 1 root root 8, 1 Mar  7 15:05 /dev/sda1
brw-rw---- 1 root root 8, 3 Mar  7 15:05 /dev/sda3
brw-rw---- 1 root root 8, 2 Mar  7 15:05 /dev/sda2
}}}
Note that the first output represents the way everything looks after a reboot.

This is a bit annoying as it means I can't give a regular users access to the Windows installation via addition to group ""disk"". Or rather, I can, but there can only be one VirtualBox session after each boot, unless someone intervenes. I guess I can add users to ""root"", to, but I'm somehow less comfortable doing that."	toralf
18638	Graphics Issues, Machine Crashing on Linux Host and Windows 10 Guest	Windows	VirtualBox 6.0.6	2019-05-13T20:13:50Z	2019-09-30T12:35:59Z	2019-09-30T12:35:59Z	"So I've been having major trouble getting my Windows 10 Guest to work correctly (From an Ubuntu 18.10 host). I've been having major graphics issues lately, especially when I turn on VBoxSVGA, which I use with 2D and 3D acceleration enabled.

Just now after experiencing some weird issue's I'll go into in a bit and trying to reboot my machine, I got a message box telling me VirtualBox had to abort and to submit a ticket. 

I'm attaching a log file for the ticket, as well as the VM Guest configuration file. As far as I know, everything is up to date and configured correctly.

I'm also attaching the output of lspci (for my host's graphics card) and a partial dump of dmesg as there are some warnings from VB kernel modules.

Some background:
Basically, everything seems to be working intermittently graphics-wise. All the issues seem to be occurring due to crashes inside C:\WINDOWS\system32\VBoxSVGA.dll, including frequent windows in Desktop Window Manager (dwm.exe). 

Additionally, sometimes I am getting the error ""Display driver failed to start; using Microsoft Basic Display Driver instead. Check Windows Update for a newer display driver."". When this happens I have no choice but to restart because the guest's screen becomes totally black with a working cursor and a blurred version of the VB bios screen overlayed in white. There is no way to resolve this without a reboot.

When things get really bad, pretty much all apps refuse to launch (though the ones already launch still work) and they fail silently (this is really ironic and frustrating as this includes debugging apps), though for each attempt I see an error relating to VBoxSVGA.dll in the Windows Error Log. I am attaching several days worth of Windows Error Logs (Application Logs) in XML format in the hopes they contain some information. I'm also attaching an HTML export of the Windows Error Reports that were generated. (Unfortunately I didn't have saving minidumps enabled at the time.)

When this whole ""nothing will start"" phenomenon occurs a program that I'm frequently trying to use -- a 3D modeling program called Autodesk Fusion 360 -- actually freaks out because it will keep trying to restart a Chrome WebView process ad infinitum (obviously the ad infinitum bit isn't on VirtualBox). I've included a stack trace from a minidump of one of these crashes as it's one of the few minidumps I have. (I can't attach the minidump itself as the memory contains proprietary content.) 

If anyone could offer any help, it would be greatly appreciated. I'm happy to assist with debugging this in any way I can.
"	Mike Vastola
18905	Graphics Issues with VBoxSVGA	Windows	VirtualBox 6.0.10	2019-09-04T13:27:12Z	2019-09-04T18:45:33Z	2019-09-04T18:45:33Z	"With the upgrade to VirtualBox 6.0.12 I received a warning that in version 6.1.0 VBoxVGA will no longer be supported and I need to migrate my VM to VBoxSVGA.

I attempted to change my Graphics Controller which placed my VM in an unusable state as it kept crashing the Windows GUI.  I put the guest into SafeMode to install the guest additions which allowed me to boot.

Now when using the guest I am unable to view applications as they render as black boxes.  Examples of applications not working: Google Chrome, Microsoft Outlook, just about anything not part of Windows OS.

I have also tested VMSVGA and this is not working either.  My Display configuration is:
Video Memory: 256 MB
Screens: 2
Graphics Controller: VMSVGA
Acceleration: 2D Video, 3D
Remote Desktop Server: Disabled
Recording: Disabled

Happy to provide anything that helps with diagnostics, but the logs were not showing anything of value to me.
"	Bryan R Festa
17973	Graphical Glitch on Virtualbox Window Maximization	Windows	VirtualBox 5.2.18	2018-09-09T14:49:16Z	2018-09-13T09:26:12Z	2018-09-13T09:26:12Z	"Hello,

I am running Ubuntu Linux 18.04 LTS with all the latest patches installed.

Linux xxxxxxx 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 16:00:05 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

I installed Virtualbox/Extension Pack/Guest Additions from virtualbox.org; version 5.2.18 r124319 (Qt5 9.5)

My machine has two monitors (1 VGA; 1 DVI). 

I run both Windows XP and Windows 7 as guests, with one running on each screen.  

If I minimize either VM via the virtualbox control bar I am correctly shown the Linux desktop. However, when I try to restore/maximize the VM by choosing it from the Linux taskbar, the VM desktop is restored with significant graphical glitches. I am forced to CTRL-F twice to take the VM out of fullscreen mode/restore fullscreen mode to correct it.  This is completely reproducible and happens 100% of the time, independent of guest OS. 

I have attached the following pictures (VM icons deleted to protect privacy):

1. Dual Screen Linux Desktop
2. Both VMs running
3. One VM Minimized
4. VM Restored with graphical glitch

I have also attached the log from the VM that was minimized/maximized from right after picture 4 was taken.

I purchased a Virtualbox Enterprise license on CDW so that this ticket may receive priority attention since I am a paying customer. Please feel free to call me via the information on my account if you need any confirmation of the CDW purchase.

Thank you in advance.
"	SloanUser
21266	good day. The guest additions CD does not work. I think the CD drive is not working.	other	VirtualBox-7.0.2	2022-11-11T23:19:44Z	2023-01-18T15:29:07Z	2023-01-18T15:29:07Z	I tried several things but the cd player does not work, what would be the solution.	yuvlower.hacsshikkennvyu@…
19374	Goldwave freeze guest machine	Windows	VirtualBox 6.1.4	2020-03-03T19:30:57Z	2022-10-22T21:54:42Z	2022-10-22T21:54:42Z	"On virtualbox 6.1.4[[BR]] with virtualbox addtion 6.1.4 in mode vboxsvga[[BR]]

In software goldwave , in long sound , when i remove by keyboard 'suppr' a lot sample ,[[BR]]

then i have random problem which is graphics sound sample redraw very slow (system freeze temporarily !) [[BR]]
I see the graphics which is drawn very slowly ![[BR]]

I join log I don't know if this will help correct this bug!

Please solve this bug ! please ![[BR]]

OS Guest: Windows Seven [[BR]]

Thank.[[BR]]

"	Sizy458
20813	Gnome desktop icons not clickable	Windows	VirtualBox 6.1.32	2022-02-07T11:51:03Z	2022-02-07T11:51:03Z	2022-02-07T11:51:03Z	"There is an issue with gnome desktop icons on CentOS Stream 8 host. After switch any virtualbox guest to seamless mode a linux window ""under guest"" or desktop icons cannot be clicked. Even if guest machine is minimalized. Also virtualbox menu is not clickable. This problem apears on X11 or Wayland GUI mode on host.
The same set up on CentOS 7.x works as intented."	Liwiusz
21474	Global buffer overflow in hdaMmioWrite()	Linux	VirtualBox-7.0.6	2023-02-08T03:23:02Z	2023-02-08T03:23:02Z	2023-02-08T03:23:02Z	"When issuing mmio_writeb(0x2146, 0xc2), cbBefore[1] can be too large for g_afMasks[2], which only has five elements.

{{{
static DECLCALLBACK(VBOXSTRICTRC) hdaMmioWrite(PPDMDEVINS pDevIns, void *pvUser, RTGCPHYS off, void const *pv, unsigned cb) {
    // ...
    idxRegDsc = hdaR3RegLookupWithin(off);
    if (idxRegDsc != -1)
    {
        uint32_t const cbBefore = (uint32_t)off - g_aHdaRegMap[idxRegDsc].off; // [1]
        Assert(cbBefore > 0 && cbBefore < 4);
        off      -= cbBefore;
        idxRegMem = g_aHdaRegMap[idxRegDsc].idxReg;
        u64Value <<= cbBefore * 8;
        u64Value  |= pThis->au32Regs[idxRegMem] & g_afMasks[cbBefore]; // ------> [2]
}}}"	cyruscyliu
15394	GetLogicalProcessorInformationEx() broken under Windows 7	Windows	VirtualBox 4.3.36	2016-05-07T08:39:16Z	2016-05-07T08:39:16Z	2016-05-07T08:39:16Z	"Hi.

So, the main issue I want to report is that GetLogicalProcessorInformationEx() basically returns garbage under Windows 7.  It's a fresh, Vanilla install of Windows 7.  The only software installed is the Windows Platform SDK.  The first record returned looks okay, but they rapidly deteriorate until after two or three you're looking at 0xCDCDCDCDCD, etc.

GetLogicalProcessorInformation(), the earlier version (no ""Ex"" on the end), also has a problem, but it seems mainly to work - the problem is that it only reports data caches.  No instruction or unified caches are reported.  Everything else seemed fine, on my one system.

Separately from VB, but related to getting this bug reported, the Oracle account creation process appears to have a number of issues.

1. The account creation page does not load if DOM storage is turned off.
2. Upon creating the account, a page is shown saying an email has been sent with instructions to activate the account.  In fact, a password reset email has been sent.
3. Upon performing the password reset, a SECOND password reset email is sent.
4. Upon performing the second reset, the account is confirmed.
5. Trying to log in does not work, at least not under Firefox - ""page is not redirectly correctly"".  However, you are in fact logged in, and so I was able to come back to this page and post this bug report.

As an aside, I spent three hours this morning trying to get VB 5.0 installed, to see if the GetLogicalProcessorInformationEx() existed there.  I was able to install 5.0 itself just fine from the VB repos, but the QT interface is not provided.  After a few hours, I concluded that although the QT package is shown via the web by Debian to be present in jessie-backports, it in fact is not present (not indeed are any of the 5.0 packages); aptitude only finds 4.3.36.  I gave up.
"	Secret Private
21351	GetFileInformationByHandleExfor VBoxSharedFolderFS  works incorrectly	other	VirtualBox-7.0.4	2022-12-21T13:12:21Z	2023-01-04T12:13:46Z	2023-01-04T12:13:46Z	"it returns ERROR_FILE_NOT_FOUND, while there are files in a directory

details:


https://github.com/boostorg/filesystem/issues/261#issuecomment-1335574338"	basiliscos
2652	Gentoo hardened (grsecurity) hosts not supported	Linux	VirtualBox 4.2.2	2008-11-25T12:59:06Z	2012-10-22T08:45:10Z	2012-10-22T08:45:10Z	"Hello,


I am running VirtualBox 2.0.6 on a Gentoo Hardened Host (2.6.23-r7).

Running normal linux systems as guest works fine, however when I try to boot a Gentoo Hardened _Guest_ system, VirtualBox reports a Guru Mediation Error and the VM freezes on kernel bootup. I tried with various hardened Guest kernels (2.6.23-r7, 2.6.24-r3 and 2.6.25-r9, all hardened-sources from Gentoo) but the error remains. Grsecurity/PAX presetting in the kernel is set to ""high"". The produced log is attached.


I will try to narrow down the search on why the kernel crashes by disabling some of the hardened options but so far I didn't have much success.

Best regards,


Christian Holler"	Christian Holler
21418	general protection fault in VBoxRT.so on Linux 5.15	Linux	VirtualBox 6.1.40	2023-01-20T00:47:16Z	2023-01-20T00:47:16Z	2023-01-20T00:47:16Z	"On Linux 5.15.0-58-generic as shipped by Ubuntu, I have been getting repeated general protection faults while trying to run a Linux guest:

[104009.209640] VMMR0InitVM: eflags=246 fKernelFeatures=0x0 (SUPKERNELFEATURES_SMAP=0)
[104254.184865] traps: CharIo[1979689] general protection fault ip:7fdabb249cec sp:7fda75ab2c88 error:0 in VBoxRT.so[7fdabb0da000+1ca000]
[112313.218922] VMMR0InitVM: eflags=246 fKernelFeatures=0x0 (SUPKERNELFEATURES_SMAP=0)
[112533.549601] traps: CharIo[2118320] general protection fault ip:7f1e2041bcec sp:7f1deec85c88 error:0 in VBoxRT.so[7f1e202ac000+1ca000]
cfriesen@yow-cfriesen-lx:~/vdm_workspace/iso/wrcp$ 


The VM log file looks like this:

00:00:29.903869 GIM: KVM: VCPU  4: Enabled system-time struct. at 0x0000000501fc6100 - u32TscScale=0xaaab08c1 i8TscShift=-1 uVersion=2 fFlags=0x1 uTsc=0x14b4fd3719 uVirtNanoTS=0x6e702e07f TscKHz=2999974
00:00:29.910783 APIC5: Switched mode to x2APIC
00:00:29.910795 GIM: KVM: VCPU  5: Enabled system-time struct. at 0x0000000501fc6140 - u32TscScale=0xaaab08c1 i8TscShift=-1 uVersion=2 fFlags=0x1 uTsc=0x14b636f299 uVirtNanoTS=0x6e76b748e TscKHz=2999974
00:00:29.916720 APIC6: Switched mode to x2APIC
00:00:29.916669 GIM: KVM: VCPU  6: Enabled system-time struct. at 0x0000000501fc6180 - u32TscScale=0xaaab08c1 i8TscShift=-1 uVersion=2 fFlags=0x1 uTsc=0x14b7460d8d uVirtNanoTS=0x6e7c5d311 TscKHz=2999974
00:00:29.921905 APIC7: Switched mode to x2APIC
00:00:29.921824 GIM: KVM: VCPU  7: Enabled system-time struct. at 0x0000000501fc61c0 - u32TscScale=0xaaab08c1 i8TscShift=-1 uVersion=2 fFlags=0x1 uTsc=0x14b833dc4c uVirtNanoTS=0x6e8151828 TscKHz=2999974
00:00:29.914199 IEM: rdmsr(0x4e) -> #GP(0)
00:00:29.925422 IEM: rdmsr(0x4e) -> #GP(0)
00:00:29.919380 IEM: rdmsr(0x4e) -> #GP(0)
00:00:29.907340 IEM: rdmsr(0x4e) -> #GP(0)
00:00:29.886932 IEM: rdmsr(0x4e) -> #GP(0)
00:00:40.477240 PIIX3 ATA: Ctl#1: RESET, DevSel=0 AIOIf=0 CmdIf0=0xa0 (-1 usec ago) CmdIf1=0x00 (-1 usec ago)
00:00:40.477303 PIIX3 ATA: Ctl#1: finished processing RESET
00:00:40.481279 AHCI#0: Reset the HBA
00:00:40.481292 VD#0: Cancelling all active requests
00:00:40.481295 VD#1: Cancelling all active requests
00:00:40.481297 VD#2: Cancelling all active requests
00:00:40.590027 AHCI#0: Port 0 reset
00:00:40.591645 VD#0: Cancelling all active requests
00:00:40.933168 AHCI#0: Port 1 reset
00:00:40.934890 VD#1: Cancelling all active requests
00:00:41.261123 AHCI#0: Port 2 reset
00:00:41.262793 VD#2: Cancelling all active requests


"	Chris Friesen
17862	Full screen view out of sync	Windows	VirtualBox 5.2.14	2018-07-10T07:09:22Z	2018-07-10T07:09:22Z	2018-07-10T07:09:22Z	"Host is Ubuntu 18.04 with Gnome Shell as the desktop. Guest is Windows 10.
Switch guest to full screen (HOST+f), then minimise using the mini toolbar.
Use the VB manager option to ""Show"" the VM. The top of the display is missing, and all mouse clicks are out of alignmnent by this gap.
The problem does not happen if the VM is re-displayed by using the operating system to select the guest, only when the ""Show"" button is used.
See screenshot.

"	Smot
15710	Full screen tool bar does not work properly on Linux hosts	all	VirtualBox 5.1.2	2016-07-29T09:37:58Z	2016-07-29T09:37:58Z	2016-07-29T09:37:58Z	"In full screen, the bottom tool bar does not appear as quick as it does before 5.1 when mouse approaches bottom of screen, and no hover effects when mouse hovering on the buttons.

When click a button on the tool bar for the first time, it will work as usual. However, after that, these buttons become decorations. The virtual machine is normal, but the only ways to quit it is to either let itself power off, or use shortcut to minimize all windows."	FiveYellowMice
544	Full Screen shown behind kicker	other	VirtualBox 1.4.0	2007-08-08T08:20:25Z	2015-03-20T22:14:14Z	2015-03-20T22:14:14Z	"Host machine: Slackware 12.0, KDE 3.5.7

When I turn full screen on in my machine, it'll turn on ok, but it will be behind my kicker. So in order to see it properly I'll have to use one of kickers hiding buttons.

I'll attach screenshot which I think explains everything."	AbsintheSyringe
16931	Full screen mode unusable on RHEL 6 since VBox 5.0, still not fixed	Windows	VirtualBox 5.1.24	2017-07-21T15:45:25Z	2017-09-06T05:48:25Z	2017-09-06T05:48:25Z	This was reported previously, but the ticket has been closed as too old with no resolution. Since VBox version 5.0 the full screen mode is unusable on Red Hat Enterprise Linux. If switched to full screen mode, the screen is not painted correctly showing either the host desktop (not the guest desktop), or the host desktop is overlaid over the guest desktop. Major issue that seems to be ignored by developers. The hardware is ThinkPad W520.	Rafcio
14045	full screen mode not ok with 2 sceens  under Ubuntu 14.04  64Bit	Linux	VirtualBox 4.3.26	2015-04-11T21:04:09Z	2015-04-13T05:54:53Z	2015-04-13T05:54:53Z	"on full screen mode - the guest appears only half (screen_shot attach to this ticket)

One Screen is Belinea, other one Fujitsu Siemens (different sizes)

On Fujitsu Siemens screen: in full screen mode - onle half display (see screen-shot)

On Belinea (smaler one): display is cut on the right side

"	Yupi
19423	full crash of host machine	Linux	VirtualBox 6.1.4	2020-03-23T02:23:17Z	2020-03-23T02:23:17Z	2020-03-23T02:23:17Z	"This report is going to be very incomplete for now.  I'll update it, if I can get some instruction on what and how to collect some better detail.  I am getting this crash half a dozen times a day when working in the environment

Environment:
Host Fedora 31 workstations 5.5.10-200.fc31.x86_64
dual monitors
16GB memory, 4 cores
Guest Fedora 31 workstations 5.5.10-200.fc31.x86_64
single monitor
6GB memory, 2 cores
Large window, slightly extending past the physical monitor size
scaled mode
Running guest application: qtcreator, debugging an application

The symptoms, just before the hard (black screen) crash of the host:

Attempt some operation in qtcreator, like clicking to create a new breakpoint.  The application freezes, the VM freezes, and all other applications windows except shells freeze.  Freeze might not be quite right.  Clicking on an application window on the host (2nd monitor) that is occluding a shell window activates the shell not the application window.  So the application might already be dead, and just a ghost of the window left on the desktop.  The shell window seems active, but not much time to look around.  In a few seconds, the host goes into full black screen crash, with a blinking text cursor.  Sometimes, in a few more seconds, the host login windows appears without any additional user actions.  Sometimes, ctrl+alt+del will initiate a reboot.

So, is there anything I can enable ahead of time, to get a log that might be useful for tracking this down?  What data can I collect after host reboot to include here?

I have other fc31 guest vms that are not crashing, so there is some interaction with the running applications.  But a misbehaving application should not crash the VM, and definitely should not crash the host machine."	mMerlin
19684	Frequent IO Read overload freezing the OpenSUSE VM	Linux	VirtualBox 6.1.10	2020-06-26T10:02:40Z	2020-06-26T10:02:40Z	2020-06-26T10:02:40Z	"My OpenSUSE VM frequently freezes and the Read IO is constantly maximum. It seemed to always happen when browser the internet, regardless of which browser used. The VM is used for browsing a few websites, connecting to a vpn and ssh tocompany hosts. The CPU also spikes to high load.

I've installed OpenSUSE 15.1 KDE and 15.2 multiple times and have set it up mostly in the same way. This is the setup:

EFI
LUKS > LVM > btrfs
HOST IO cache ON (also tried off)
SSD drive on for storage container
4GB RAM (2GB in use)
4 vCPU
VMDK storage format
guest additions installed

I installed the same setup, except for EFI that is replaces with BIOS (I think I tried that with VB as well), and this issue never happens. Same resources given to VM.

Unfortunately I don't have the logs anymore."	lmmmm
21115	freeze gnome gui ubuntu	other	VirtualBox 6.1.38	2022-10-01T22:01:15Z	2022-10-04T12:55:49Z	2022-10-04T12:55:49Z	"in end of game (red alert 2 yuri revenge win 2k os) the gnome UI freeze (ubuntu 0.22) only mouse is move.
open a new session ctrl F1 or F2 and KILL virtualbox from other user,exit session.
the old session run normal.
the freeze is in 6.1.38_ubuntu 153438 and previsus version. the freeze is not only in end game session this in casual in other usage of VM 

example read bad hard disk from usb


os info:
System:
  Kernel: 5.15.0-48-generic x86_64 bits: 64 compiler: gcc v: 11.2.0
    Desktop: GNOME 42.4 Distro: Ubuntu 22.04.1 LTS (Jammy Jellyfish)
Machine:
  Type: Laptop System: SANTECH product: X170SM v: N/A
    serial: <superuser required>
  Mobo: SANTECH model: X170SM serial: <superuser required> UEFI: INSYDE
    v: 1.07.02TSAS date: 06/10/2020
Battery:
  ID-1: BAT0 charge: 92.2 Wh (100.0%) condition: 92.2/96.5 Wh (95.5%)
    volts: 16.3 min: 14.4 model: Notebook BAT status: Full
CPU:
  Info: 8-core model: Intel Core i7-10700F bits: 64 type: MT MCP
    arch: Comet Lake rev: 5 cache: L1: 512 KiB L2: 2 MiB L3: 16 MiB
  Speed (MHz): avg: 4703 high: 4761 min/max: 800/4800 cores: 1: 4702
    2: 4700 3: 4761 4: 4754 5: 4705 6: 4700 7: 4694 8: 4701 9: 4702 10: 4700
    11: 4693 12: 4704 13: 4656 14: 4683 15: 4700 16: 4698 bogomips: 92796
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: NVIDIA TU104BM [GeForce RTX 2070 SUPER Mobile / Max-Q]
    vendor: CLEVO/KAPOK driver: nvidia v: 510.85.02 bus-ID: 01:00.0
  Device-2: Chicony USB2.0 Camera type: USB driver: uvcvideo bus-ID: 1-8:3
  Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: nvidia
    unloaded: fbdev,modesetting,nouveau,vesa gpu: nvidia
    resolution: 5120x2880~60Hz
  OpenGL: renderer: NVIDIA GeForce RTX 2070 Super/PCIe/SSE2
    v: 4.6.0 NVIDIA 510.85.02 direct render: Yes
Audio:
  Device-1: Intel Comet Lake PCH cAVS vendor: CLEVO/KAPOK
    driver: snd_hda_intel v: kernel bus-ID: 00:1f.3
  Device-2: NVIDIA TU104 HD Audio vendor: CLEVO/KAPOK driver: snd_hda_intel
    v: kernel bus-ID: 01:00.1
  Sound Server-1: ALSA v: k5.15.0-48-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus-ID: 42:00.0
  IF: wlp66s0 state: up mac: <filter>
  Device-2: Realtek Killer E3000 2.5GbE vendor: CLEVO/KAPOK driver: r8169
    v: kernel port: 3000 bus-ID: 43:00.0
  IF: enp67s0 state: down mac: <filter>
  IF-ID-1: vboxnet0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8
    bus-ID: 1-14:6
  Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter>
    bt-v: 3.0 lmp-v: 5.2
Drives:
  Local Storage: total: 2.27 TiB used: 1.78 TiB (78.1%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 500GB
    size: 465.76 GiB temp: 39.9 C
  ID-2: /dev/sda type: USB model: External USB3.0 size: 1.82 TiB
Partition:
  ID-1: / size: 216.18 GiB used: 146.21 GiB (67.6%) fs: ext4
    dev: /dev/nvme0n1p5
  ID-2: /boot/efi size: 96 MiB used: 33.6 MiB (35.0%) fs: vfat
    dev: /dev/nvme0n1p1
Swap:
  ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) file: /swapfile
Sensors:
  System Temperatures: cpu: 43.0 C pch: 48.0 C mobo: N/A gpu: nvidia
    temp: 38 C
  Fan Speeds (RPM): N/A
Info:
  Processes: 376 Uptime: 2h 24m Memory: 15.39 GiB used: 3.36 GiB (21.8%)
  Init: systemd runlevel: 5 Compilers: gcc: 11.2.0 clang: 14.0.0-1ubuntu1
  Packages: 3599 Shell: Bash v: 5.1.16 inxi: 3.3.13




"	gufo rosso
21201	FreeBSD 12.3 and pfSense 2.6.0 networking no longer works with upgrade to VB 7.0.2 => fixed in SVN	BSD	VirtualBox-7.0.2	2022-10-24T17:12:33Z	2023-01-12T15:03:06Z	2023-01-12T15:03:06Z	"Hi,

After a recent upgrade from VirtualBox 6.1.40 to 7.0.2 on Arch Linux, all of my pfSense virtual machines hang at ""Configuring WAN interface"" during the boot process. Reverting VirtualBox back to 6.1.40 fixes it.

The pfSense VM (CE 2.6.0) is configured with EFI enabled and the WAN interface is a NAT virtual network adapter with ""virtio-net"". I've tried changing the adapter to either of the Intel PRO/1000 Server options and it does eventually boot after a 5 minute hang at the same point, but it is unable to get an IP and therefore doesn't work either.

I've also tried to create a brand new pfSense VM using the same settings as our currently running ones and while it installs properly, after the reboot it is stuck on ""Default interfaces not found -- Running interface assignment option."". This also works properly in 6.1.40. I've also tried setting the network interface to bridge mode and no change.

Edit: All other VM work properly, including other FreeBSD 13.1 virtual machines but same behavior with FreeBSD 12.3.

Any suggestions?"	rickga
17940	For Fedora, Virtualbox is being built for unsupported releases (Fedora 26)	other	VirtualBox 5.2.18	2018-08-19T02:54:27Z	2018-08-20T15:39:29Z	2018-08-20T15:39:29Z	"currently, VirtualBox is provided as an rpm for Fedora 26, which has reached End-of-Life status. Those rpm seem to work fine in the two supported releases Fedora 27 and 28.

Maybe it's time to drop support for F26 and build VirtualBox on/for never Fedora releases.
"	F
14757	Flickering in Chrome and odd behaviour of Snipping Tool	Windows	VirtualBox 5.0.8	2015-10-27T12:12:45Z	2016-09-05T01:46:30Z	2016-09-05T01:46:30Z	"Hi,

since version 5.0.8 I have a terrible flickering in Google Chrome. No matter the website, but it makes it impossible to read or use these websites. Same Website in Internet Explorer doesn't flicker.

Snipping Tool: Sometimes when I click on new screenshot the snipping tool window becomes part of the background, sometimes it leaves a white space where the window was and sometimes it works normally. Haven't figured a trigger that reproduces or avoids it. Workaround is is to abort the screenshot and try again.

Setup:
Host: openSUSE Leap 42.1 RC1
Virtualbox from virtualbox.org, not from the openSUSE repos.
Guest: Windows7 Pro 64bit
Dual Screen on host and guest. 128mb Graphics memory for the VM. 3d acceleration enabled for that vbox.
Graphics driver on the host: radeon
[     5.335] (II) LoadModule: ""radeon""

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM]

I tried VBox guest additions both w/ and w/o the 3d support, no change. Only disabling 3d acceleration in VirtualBox helped.

Kind regards
Vonor"	Vonor
3451	files with national characters not shown via \vboxsvr	Windows	VirtualBox 2.1.4	2009-02-27T10:13:55Z	2009-02-27T10:13:55Z	2009-02-27T10:13:55Z	"I am running VB 2.1.4_OSE with GA 2.1.4r42893. Guest is WinXPSP2, host is Debian 5.0 (smbd 3.2.5). When accesing host shares via standard \10.0.2.2\ I get full list of all files on that share (files with national characters have them converted to '_'s). When accessing shares via GA - Shared Folders, only files without national characters are shown.
"	wolcano
3645	files in guest shared folders seems not to reflect changes done in host	Linux	VirtualBox 2.1.4	2009-04-06T20:34:53Z	2009-04-15T08:44:17Z	2009-04-15T08:44:17Z	"I have a guest OS (Ubuntu Hardy Heron) with shares a folder (in read/write) with the host OS (Ubuntu Hardy Heron). I use a web editor to edit the files in this folder in the host OS so the modifications should be seen in the guest OS (the shared folder, mounted in the guest, is the root directory of an apache web server installed just in the guest).
The problem is that, when I modify a file in the host side, these changes seem not reflected correctly in guest side. Via a simple cat or less or vi the modified files seem correct but with apache the modifications aren't reflected (I can test this via ""telnet server 80""). In fact often the modifications are seen as strange characters or other times other strange behaviours happen.
I can solve this either:
- umount and then re-mount the shared folder (but I have to do this after every file change)
or
- simply edit the file via vi (guest side) and, with no modifications, save the file"	Marco 
20253	file system damage on flashUSB	other	VirtualBox 6.1.18	2021-03-13T14:45:33Z	2021-03-13T14:45:33Z	2021-03-13T14:45:33Z	"I'm on Debian, I formatted a flashUSB3 with BTRFS and put on it a VM., that I had previously on an HDD.

At the beginning everything work as expected, few boots was very fast, and guest responsive, I can work well with the guest.

After some days, the guest OS start to freeze, report error, and also Debian kmesg show BTRFS fs csum errors.
I tested the flashUSB with badblocks, no error. I checked the flashUSB with
$ f3probe --destructive, and the flash is the real thing.

So I tried to format the flashUSB with ext3, exported the appliance again from HDD to flashUSB but after some days happened the same.

I changed the flashUSB (was a Philips) with a brand new Kingston, same happen.

I changed the flashUSB with an USB3 HDD, and everything work.
I changed the HDD with an USB3 SDD, and everything work.

Now I'm sure there is bug with flashUSB3 ?
"	Valerio Messina
18675	File corruption on shared folder - Linux host + Windows 7 guest	Windows	VirtualBox 6.0.8	2019-05-24T17:16:26Z	2019-06-05T00:38:48Z	2019-06-05T00:38:48Z	"Setup :
Host : Ubuntu 16.04 x64
Guest : Windows 7 x64
Shared folder (on ext4 partition) between host and guest

I'm using a Windows 7 virtual machine only for Adobe Photoshop CS6 x64.

Before v6.0.8 I installed v6.0.6 only briefly, I had to revert back to 6.0.4 because of the mouse integration bug. So I for the present issue I installed 6.0.8 over 6.0.4.

I encountered a strange behaviour with the shared folder I'm using to exchange files between the host and the guest. 
In Photoshop CS6 x64, after I installed VirtualBox v6.0.8, sometimes Photoshop tells me it couldn't read the TIFF files I had worked on before. And when it could, sometimes the content was scrambled.
I checked my images in other software (under Windows ''and'' Ubuntu) : correct.
I opened the files in the VM with Photoshop CS6 x32 this time : correct.
I checked my TIFF files with an utility called jHove, which checks the TIF file integrity : no errors.
So my image files are without flaws. I can save them in Photoshop but not read them back, at least in the x64 version. Weird.
I also copied the files directly on the guest : this time Photoshop CS6 x64 was happy.

For 2 days I have tested many things. It only occurs in Photoshop CS6 x64, when I'm using the shared folder.

So I decided to revert back to VirtualBox v6.0.4, and dang! Photoshop CS6 x64 was happy again with my files...

So my conclusion is the problem comes from the shared folder functions, but only when reading my files, not when I'm writing.

I'm including my v6.0.4 last log file, I didn't think about saving one when I was under v6.0.8 sorry."	Parazythum
19497	Feture request: minimize the virtualbox machine window when the guest OS powers off its virtual screen	Linux	VirtualBox 6.0.14	2020-04-15T23:32:38Z	2020-04-16T01:53:18Z	2020-04-16T01:53:18Z	"Hello,

my guest ubuntu OS always keeps saying (in the background) that it's unable to lock screen while I have a virtualbox machine in the foreground. Well in a way that is a feature I understand, but also as it hinders security (host OS is not locking when there's no keyboard and no mouse activity and a virtualbox guest is in the foreground) it is an antifeature as well. As a solution which would make this a feature without any drawbacks I suggest you to minimize the guest OS window (or otherwise prevent it preventing the host OS to lock) when the guest OS blanks or powers off its virtual screen. Maybe you can add a configuration option for this as well, but maybe as until today there were no use to powering off/blanking the virtual screen this feature might be OK without any configuration option as well.

Thank you in advance.

Imre"	Imre84
18281	Feedback of /sbin/vboxconfig on failing module load not always helpful	other	VirtualBox 6.0.0	2019-01-04T12:54:29Z	2019-01-04T12:54:29Z	2019-01-04T12:54:29Z	"Failing of `/sbin/vboxconfig` due to failing module load results in the feedback

{{{
$ sudo /sbin/vboxconfig
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why.

There were problems setting up VirtualBox.  To re-start the set-up process, run
  /sbin/vboxconfig
as root.
}}}

However, `dmesg` doesn't reliably show the reason for the failure, in my case it contains no new message in comparison to `dmesg` executed right before running `/sbin/vboxconfig` whereas `sudo modprobe -vvv vbox*` shows the reason for the failure:

{{{
modprobe: INFO: ../libkmod/libkmod.c:364 kmod_set_log_fn() custom logging function 0x560016357ee0 registered
modprobe: DEBUG: ../libkmod/libkmod-index.c:755 index_mm_open() file=/lib/modules/4.18.0-13-generic/modules.dep.bin
modprobe: DEBUG: ../libkmod/libkmod-index.c:755 index_mm_open() file=/lib/modules/4.18.0-13-generic/modules.alias.bin
modprobe: DEBUG: ../libkmod/libkmod-index.c:755 index_mm_open() file=/lib/modules/4.18.0-13-generic/modules.symbols.bin
modprobe: DEBUG: ../libkmod/libkmod-index.c:755 index_mm_open() file=/lib/modules/4.18.0-13-generic/modules.builtin.bin
modprobe: DEBUG: ../libkmod/libkmod-module.c:556 kmod_module_new_from_lookup() input alias=vboxdrv-module-signing, normalized=vboxdrv_module_signing
modprobe: DEBUG: ../libkmod/libkmod-module.c:562 kmod_module_new_from_lookup() lookup modules.dep vboxdrv_module_signing
modprobe: DEBUG: ../libkmod/libkmod.c:574 kmod_search_moddep() use mmaped index 'modules.dep' modname=vboxdrv_module_signing
modprobe: DEBUG: ../libkmod/libkmod-module.c:566 kmod_module_new_from_lookup() lookup modules.symbols vboxdrv_module_signing
modprobe: DEBUG: ../libkmod/libkmod-module.c:570 kmod_module_new_from_lookup() lookup install and remove commands vboxdrv_module_signing
modprobe: DEBUG: ../libkmod/libkmod-module.c:574 kmod_module_new_from_lookup() lookup modules.aliases vboxdrv_module_signing
modprobe: DEBUG: ../libkmod/libkmod.c:434 kmod_lookup_alias_from_alias_bin() use mmaped index 'modules.alias' for name=vboxdrv_module_signing
modprobe: DEBUG: ../libkmod/libkmod-module.c:578 kmod_module_new_from_lookup() lookup modules.builtin vboxdrv_module_signing
modprobe: DEBUG: ../libkmod/libkmod.c:501 lookup_builtin_file() use mmaped index 'modules.builtin' modname=vboxdrv_module_signing
modprobe: DEBUG: ../libkmod/libkmod-module.c:583 kmod_module_new_from_lookup() lookup vboxdrv_module_signing=0, list=(nil)
modprobe: FATAL: Module vboxdrv-module-signing not found in directory /lib/modules/4.18.0-13-generic
}}}

Please note that I'm requesting a fix for the feedback of the script, not the issue shown in the output of `modprobe`.

experienced with 6.0.0 r127566 (Qt5.11.1) on Ubuntu 18.10"	karl-philipp.richter
9430	Fedora15 does not hook into my wireless connection	other	VirtualBox 4.1.0	2011-08-14T16:10:27Z	2011-08-14T18:54:34Z	2011-08-14T18:54:34Z	"You seem to be building functional obsolescence into your software for network connections.  Every time I get an update, my wireless connection quits working! The first time I built Fedora15 it worked OK, however, it kept crashing on the Screen Shot feature.  Then when I updated the wireless through my port quit working, now in 

Also, the 64 bit version does not work on this machine.

I'm a tech trying to work with you here. I have been recommending Virtual Box for some time over the others; however, it's starting to get old quick when I have to keep rebuilding my boxes. 

When I click on Fedora15 repositories, which is generally required to get things working it asks for the nick, then goes no further, see attached.  It worked before in earlier versions.


Windows Servers I have not had any problem with.
"	Kenneth W. Hill
20832	Fedora-35 HOST + Windows 10/11 GUEST: Keyboard entries and Touchpad Taps stop responging, after ~10m	Windows	VirtualBox 6.1.32	2022-02-17T15:54:38Z	2022-10-10T12:08:30Z	2022-10-10T12:08:30Z	"Dear Friends:

I have a bug that I've been facing for approaching 2-years (19-months, actually). No matter what I do, the bug remains. Let me explain.

The bug, which I describe further below, first appeared in '''August''' of '''2020''' on '''Fedora-32 64-bit''', which is the '''HOST''' O/S. Back then, I had hoped that the bug would be confined to a particular '''Fedora Kernel''' and waited for the next one; but as I upgraded Fedora-32 Kernels, the bug persisted.

Then, I eventually upgraded to '''Fedora-33''' (again, the '''HOST'''), and the bug persisted through that Fedora version and through all of its Kernels, as well. The same occurred with '''Fedora-34'''.

For '''Fedora-35''', I decided to reinstall everything from scratch: I reinstalled '''Fedora-35''' ('''HOST''') from scratch; as well as reinstalled '''Windows-10''' ('''GUEST'''). Without customizing much, except to apply the '''Extension Pack''' and '''Guest Additions''', I launched a Windows-10 VM (with everything fresth). The bug immediately surfaced. It always takes about ~5 to 10 minutes to occur, by the way.

Now, all of this was on a '''Lenovo''' '''Y700-17isk''' Laptop.

So, I decided to do the same procedure on an '''ASUS G750 Rogue''' Laptop: I installed '''Fedora-35''' ('''HOST''') from scratch; as well as installed '''Windows-10''' ('''GUEST''') from scratch. Without customizing much, except to apply the '''Extension Pack''' and '''Guest Additions''', I launched a Windows-10 VM (with everything fresh). The bug immediately surfaced. 

No matter what I do, I cannot get rid of this bug. I think that circa '''August 2020''', either '''Fedora''' and/or '''VirtualBox''' changed something that is causing this long-running bug.

'''THE PROBLEM''':

-- I first reported this problem on '''August 2020''' ('''Lenovo Y700-17isk''' laptop) [https://forums.virtualbox.org/viewtopic.php?f=7&t=99328 here]

-- Then, I reported this problam again yesterday, '''February 2022''' ('''ASUS G750 Rogue''') [https://forums.virtualbox.org/viewtopic.php?f=7&t=105295 here]


Here is a paste of yesterdays description for your convenience:


{{{
VirtualBox Version..................: 6.1.32_rpmfusion
HOST O/S............................: Fedora-35
HOST Kernel.........................: 5.14.10-300.fc35.x86_64
GUEST O/S (with latest updates......: Windows-11 (happens with Windows-10, as well)

}}}


What happens is this: VirtualBox is working perfectly (Network, Audio, Shared Drive, Cut & Paste, Keyboard & Mouse Capture, Mapped USB Devices, etc); but then suddenly, after, say, 5 to 10 minutes, the Keyboard stops responding to Keystrokes, and the Touchpad stops responding to Taps. The only thing that responds is moving the mouse-cursor around by swiping around the Touchpad, but that's it. This happens whether or not the GUEST (Windows 10 / 11) is in Fullscreen mode or Window mode. Except for being able to move the mouse-cursor around, Keystrokes and Touchpad Taps stop working inside the GUEST window, or around it on the HOST. The only option I have to to crash the Laptop by holding the power-button down. Actually, I did try to SSH into the HOST from another server, and while it does initiate the SSH connection, it never can never actually log in. So the HOST is still quote/unquote kind of running, but in a hobbled state.

I should also mention that this issue arises even with more basics setups: USB disabled; Audio disabled; Network with LAN or Bridged; etc.

Please help me. I think this is a real bug. It persists no matter what I do. For the better part of two-years, I haven't been able to use VirtualBox.

I can upload or add more information. Just let me know what you need.

Thank you in advance!"	nyceyes
20600	Fedora 35 compatibility / udev rules errors	other	VirtualBox 6.1.26	2021-10-09T22:50:29Z	2022-10-21T12:53:24Z	2022-10-21T12:53:24Z	"There are some error messages which I guess should be fixed:


{{{
vboxdrv: /etc/udev/rules.d/60-vboxdrv.rules:1 Only network interfaces can be renamed, ignoring NAME=""vboxdrv"".
vboxdrvu: /etc/udev/rules.d/60-vboxdrv.rules:2 Only network interfaces can be renamed, ignoring NAME=""vboxdrvu"".
VBoxNetFlt: Successfully started.
VBoxNetAdp: Successfully started.
vboxnetctl: /etc/udev/rules.d/60-vboxdrv.rules:3 Only network interfaces can be renamed, ignoring NAME=""vboxnetctl"".
}}}

I'm using VirtualBox-6.1-6.1.26_145957_fedora33-1.x86_64.rpm"	Artem S. Tashkinov
14731	Fedora 22 Host, Windows 7 Guest: switch to seamless turns windows objects into a dark shadow	Windows	VirtualBox 5.0.6	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
2760	Feature request: direct tun/tap support not available since 2.1.0	other	VirtualBox 2.1.0	2008-12-17T19:17:21Z	2015-05-19T17:36:20Z	2015-05-19T17:36:20Z	"It was very nice that virtualbox supported the direct usage of tun/tap interfaces and NOT used another driver which means one more possible point of failure or incompatibility. That was a major advantage compared to other virtualisation systems (vmware for example). Now there is possibly a ""double bridge"" (on in the ""filter driver"" and one in the working and very stable kernel mainline bridge code) which means double work, possibly worse performance.

Why reinvent the wheel? Please readd direct tap support again!
"	M. Schinkel
3438	Feature Request:  Pass guest hyperlinks to host OS	Windows	VirtualBox 2.1.4	2009-02-25T19:27:22Z	2014-04-30T08:26:37Z	2014-04-30T08:26:37Z	"It would be nice if there was a way through the VirtualBox guest addition drivers to permit hyperlinks clicked in the guest OS to be passed directly to the host OS operating system.  I forsee this being a selectable option, possibly through the ""shared folders"" option.  There should also be a modifiable key to bypass the option (such as cntrl-shift-click, which would leave the link in the guest OS).  URLs should probably be selectable (such as http:// and ftp:// links).  

My specific instance is that I only use my Windows virtual machine for Outlook.  I would prefer that most links I access would open in Firefox in Linux.  Thanks!"	blamerson
7407	feature request - double-click action in main window customizable (i.e. open settings instead of starting vm)	other	VirtualBox 3.1.8	2010-08-31T22:25:07Z	2010-08-31T22:25:07Z	2010-08-31T22:25:07Z	"just a feature request. i would like it if the double-click action in the main gui window were customizable (i.e. i could open wm settings instead of starting vm, useful perhaps if i were tweaking settings alot to fine tune things, or swapping a bit of storage media while the vm's are down)

""shiny"""	shiny
17752	fatal error in recompiler cpu: Trying to execute code with memory type	Windows	VirtualBox 5.1.34	2018-05-10T17:54:18Z	2018-05-10T19:54:32Z	2018-05-10T19:54:32Z	"hello the community.
I have a crash with:
Gest windows 7 - Host linux kubuntu 17-10 - virtualbox 5.1.34
I tested this with XP and it's OK. Only windows 7 crash. Windows 7 boot with boot without error.
Please help me to resolve this problem.
Thank you for your help and excuse me for my poor english...
regards"	GB74
8481	Failure when non-existing uppercase and underscore directory	Windows	VirtualBox 4.0.4	2011-03-03T09:18:43Z	2011-03-03T09:18:43Z	2011-03-03T09:18:43Z	"1. Ubuntu 10.10 Host
2. Windows XP Guest
3. VirtualBox-Guest-Tools 4.0.4
4. Shared Folder called ""Share"" pointing to ~/Share

5. Do this:
{{{
cd ~/Share
rm -rf /tmp/HELLO_WORLD #yes, the directory must not exist
ln -s /tmp/HELLO_WORLD HELLO_WORLD
}}}

6. Try to access \VBOXSVR\Share:

""Auf \VBOXSVR\Share kann nicht zugegriffen werden. Sie haben eventuell keine Berechtigung, diese Netzwerkressource zu verwenden. Wenden Sie sich an den Administrator des Servers, um herauszufinden, ob Sie über Berechtigungen verfügen.

Falscher Parameter."" 

Unfortunately my Windows is german and i didn't find an exact translation in google...
""Unable to access \vboxscr\share. You might have unsufficent privileges to use this ressource. Consult your admin blah blah

Wrong parameter.""


If you try the same with ""hello_world"" or ""HELLO"" or ""HELLO_WORLd"", there will be no error."	garfield
20465	Failure to load signed modules on UEFI secure boot system	all	VirtualBox 6.1.24	2021-07-21T06:39:00Z	2021-07-21T06:39:00Z	2021-07-21T06:39:00Z	"As in title really. VirtualBox scripts build the modules, put them in right place but they (rightfully) cannot be loaded.

So I sign them.

And the story repeats - /usr/lib/virtualbox/vboxdrv.sh scripts doesn't recognize the drivers as valid ones, rebuilds them (trashing the signature I've just made) and the story repeats.

The problem probably is in line 330 in function module_available():

    [ ""$mod_dir"" != ""misc"" ] || return

which likely should be:

    [ ""$mod_dir"" = ""misc"" ] || return
"	Tomek
18492	failure to install completely	Linux	VirtualBox 6.0.4	2019-03-12T23:55:27Z	2019-03-13T00:20:57Z	2019-03-13T00:20:57Z	"This is a new Fedora Core system (fc31/rawhide). 

Installation file is: VirtualBox-6.0.5-129304-Linux_amd64.run

Again, the execution of vboxconfig has failed. I know, it's expected. The problem is one that I seem to have seen A LOT. Eventually it gets fixed but it seems to come back (always(?)). Is the fix NOT being propagated to the development tree? Here's the same old message that I've been seeing:

     22    ./tools/objtool/objtool orc generate  --module --no-fp --retpoline /tmp/vbox.0/SUPR0IdcClient.o
     23 /tmp/vbox.0/linux/VBoxPci-linux.c: In function ‘vboxPciFileWrite’:
     24 /tmp/vbox.0/linux/VBoxPci-linux.c:375:12: error: implicit declaration of function ‘get_ds’; did you mean ‘get_fs’? [-Werror=implicit-function-declaration]
     25   375 |     set_fs(get_ds());
     26       |            ^~~~~~
     27       |            get_fs
     28 /tmp/vbox.0/linux/VBoxPci-linux.c:375:12: error: incompatible type for argument 1 of ‘set_fs’
     29   375 |     set_fs(get_ds());
     30       |            ^~~~~~~~
     31       |            |
     32       |            int

Am I doing something wrong?

Best regards,

Obiewan (George)
"	George R. Goffe
18602	Failure Restoring machine	Windows	VirtualBox 6.0.4	2019-04-26T15:20:30Z	2019-04-26T15:20:30Z	2019-04-26T15:20:30Z	"On a virtual machine when i restore[[BR]]
I have error ""Session avorted""[[BR]]


[[BR]]

AND
[[BR]]
i have a other error in log :
''00:00:01.865624 !!Assertion Failed!!
00:00:01.865624 Expression: !VMCPU_FF_IS_SET(pVCpu, VMCPU_FF_INTERRUPT_PIC)
00:00:01.865625 Location  : /home/vbox/tinderbox/6.0-lnx64-rel/src/VBox/VMM/VMMR3/PDM.cpp(1006) int pdmR3LoadExec(VM*, SSMHANDLE*, uint32_t, uint32_t)
00:00:01.865658 Stack     :
00:00:01.865658 00007fd31c0334e3 VBoxRT.so + 0x1f04e3''
"	Sizy458
19718	Failed to start VirtualBox hub service	other	VirtualBox 6.1.10	2020-07-14T18:54:01Z	2020-07-15T06:54:19Z	2020-07-15T06:54:19Z	"I'm using VirtualBox 6.1.10_Ubuntu r138449 on Linux Mint MATE 19.3.
When starting Linux, I've got this error message : ""Failed to start VirtualBox hub service"".

I've got another message error when I type this command line :
$sudo dpkg-reconfigure virtualbox
See https://github.com/linuxmint/mintsystem/issues/121"	InfoLibre
19276	Failed to load unit 'pgm' (VERR_SSM_INTEGRITY_DECOMPRESSION).	Windows	VirtualBox 5.2.36	2020-01-28T18:38:51Z	2020-02-03T15:37:05Z	2020-02-03T15:37:05Z	"Failed to open a session for the virtual machine Windows 7 Test.

Failed to load unit 'pgm' (VERR_SSM_INTEGRITY_DECOMPRESSION).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

"	DHDurgee
19685	Failed to create a snapshot of the virtual machine: Win Server 2019 guest	Windows	VirtualBox 6.1.10	2020-06-26T21:10:29Z	2020-06-27T16:25:05Z	2020-06-27T16:25:05Z	"I cannot snapshot any Win Server 2019 guest.

I can snapshot a guest before the OS is installed, but after, it refuses to snapshot or export.
Guests are stopped when I attempt. I have created multiple guests to attempt snapshoting, all fail.
Dispite the error message, the NVRAM file is copieed to the destination directory, but vbox fails anyway.
I have checked permissions and selinux.
I have tried temporarily changing the value for the ""Guest OS"" selector, and the ""Graphics Controller""

Version  VirtualBox 6.1.10
Host  CentOS linux kernel 3.10.0-1127.13.1.el7.x86_64


{{{

Failed to create a snapshot of the virtual machine melbourne.

Could not copy NVRAM file '/home/vmadmin/VirtualBox_VMs/melbourne/melbourne.nvram' to '/home/vmadmin/vbox_vms/melbourne/snapshots/2020-06-26T20-32-43-296493000Z.nvram' (VERR_NOT_SUPPORTED).

Result Code: VBOX_E_IPRT_ERROR (0x80BB0005)
Component: SessionMachine
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}
}}}

"	Charlweed
15593	Fail to save machine state	Windows	VirtualBox 5.0.24	2016-07-11T18:48:59Z	2016-07-11T18:48:59Z	2016-07-11T18:48:59Z	"Hi,

Every time I try to save the machine state I get an error. This has happened through several VirtualBox versions.

The error is: 
Result Code: 
NS_ERROR_FAILURE (0x80004005)

My host is Ubuntu 14.04 LTS and my guest is Windows XP sp3

Thanks
"	mau17
16119	Extremely slow text display in safe mode boot with Windows Server 2008 guest	Windows	VirtualBox 5.1.8	2016-10-26T20:33:28Z	2016-10-27T15:16:49Z	2016-10-27T15:16:49Z	"Host: Lubuntu 16.04 x86-64, Core 2 Duo T9500 CPU
Guest: Windows Server 2008 x86

I created a Windows Server 2008 VM, single CPU, VT-x, no I/O APIC.

It boots normally fine. However if I boot in safe mode (press F8 at startup), text rendering is incredibly slow. It's like a 300 baud modem: each line of text appears slowly. Once the screen is full, it takes ages to redraw the whole screen scrolled up by one line.

I noticed this in the changelog for VirtualBox 2.2.0:
""VMM: ﬁxed extremely slow safe mode booting in e.g. Windows 2008 (VT-x/AMD-V only)""

Could there have been some regression causing that problem to reappear?"	Donuts
15981	extension pack does not install on vnc desktop	all	VirtualBox 5.0.6	2016-09-24T02:35:38Z	2016-10-07T15:08:09Z	2016-10-07T15:08:09Z	"hello.
extension pack does not install when running virtualbox on a vnc virtual desktop.

it does install when using the real, hardware based graphical monitor"	mraix
16898	excel 2002 crashes upon close on win7 guest in VB 5.1.22 r115126 (Qt5.6.1) on ubuntu 14.04	Windows	VirtualBox 5.1.22	2017-07-12T23:13:15Z	2017-09-27T04:13:01Z	2017-09-27T04:13:01Z	"host os ubuntu 14.04 LTS 64 bit
virtualbox Version 5.1.22 r115126 (Qt5.6.1)
guest os win 7 pro ver 6.1 build 7601 service pack 1
excel 2002 (10.6871.6870) sp3

On close or exit win7 reports excel crashed.
This crash happens every time.

The VB log file has no indications at all for this event.

Win7 reports:
Problem signature:
  Problem Event Name:	APPCRASH
  Application Name:	EXCEL.EXE
  Application Version:	10.0.6871.0
  Application Timestamp:	4daf71c5
  Fault Module Name:	TFSOfficeAdd-in.dll
  Fault Module Version:	15.112.26313.0
  Fault Module Timestamp:	58c6a842
  Exception Code:	c0000005
  Exception Offset:	0000f27a
  OS Version:	6.1.7601.2.1.0.256.48
  Locale ID:	1033

Additional information about the problem:
  LCID:	1033

"	oldunixguy
3821	Estimate required and available disk space when discarding snapshots	Windows	VirtualBox 2.2.0	2009-04-23T12:21:10Z	2009-04-23T12:21:10Z	2009-04-23T12:21:10Z	"When discarding snapshots in the Virtual Media Manager, it would be good to estimate the required and available disk space before the operation starts and refuse it if there is not enough disk space.

Today I have deleted 40Gig .vdi file in this way. The Manager said that there is not enough disk space and removed the file. This was a key file, as the VirtualBox then has refused to starg Windows.

Happily, I have had a backup copy of that file."	Vladimir
17936	ERROR: could not insert 'vboxdrv': Exec format error	other	VirtualBox 5.1.38	2018-08-17T12:50:05Z	2018-08-17T12:50:05Z	2018-08-17T12:50:05Z	"See below. I tried uninstalling and reinstalling, to no avail.

isdev@Pingu:~$ sudo modprobe vboxdrv
modprobe: ERROR: could not insert 'vboxdrv': Exec format error
-----

Ubuntu
Release 16.04.2 LTS (Xenial Xerus) 64-bit
Kernel Linux 4.4.0-130-generic x86_64
MATE 1.12.1
-----

[338798.369639] vboxdrv: version magic '4.4.0-130-generic SMP mod_unload modversions ' should be '4.4.0-130-generic SMP mod_unload modversions retpoline '
-----

isdev@Pingu:~$ dpkg -s virtualbox
Package: virtualbox
Status: install ok installed
Priority: optional
Section: contrib/misc
Installed-Size: 70410
Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
Architecture: amd64
Version: 5.1.38-dfsg-0ubuntu1.16.04.1
Depends: adduser, iproute2, procps, virtualbox-dkms (>= 5.1.38-dfsg-0ubuntu1.16.04.1) | virtualbox-source (>= 5.1.38-dfsg-0ubuntu1.16.04.1) | virtualbox-modules, init-system-helpers (>= 1.18~), python3 (<< 3.6), python3 (>= 3.5~), python3.5, libc6 (>= 2.15), libcurl3-gnutls (>= 7.16.2), libdevmapper1.02.1 (>= 2:1.02.97), libgcc1 (>= 1:3.0), libgsoap8, libpng12-0 (>= 1.2.13-4), libpython3.5 (>= 3.5.0~b1), libsdl1.2debian (>= 1.2.11), libssl1.0.0 (>= 1.0.0), libstdc++6 (>= 5.2), libvncserver1 (>= 0.9.10), libvpx3 (>= 1.5.0), libx11-6, libxcursor1 (>> 1.1.2), libxext6, libxml2 (>= 2.7.4), libxmu6, libxt6, zlib1g (>= 1:1.1.4)
Recommends: virtualbox-qt (= 5.1.38-dfsg-0ubuntu1.16.04.1), libgl1-mesa-glx | libgl1, libqt5core5a (>= 5.0.2), libqt5opengl5 (>= 5.0.2) | libqt5opengl5-gles (>= 5.0.2), libqt5widgets5 (>= 5.0.2)
Suggests: vde2, virtualbox-guest-additions-iso
Conflicts: virtualbox-2.0, virtualbox-2.1, virtualbox-2.2, virtualbox-3.0, virtualbox-3.1, virtualbox-3.2, virtualbox-4.0, virtualbox-4.1, virtualbox-4.2, virtualbox-4.3, virtualbox-5.0, virtualbox-5.1
Conffiles:
 /etc/default/virtualbox 903beafa3922607d1ac07950d9ae2d50
 /etc/init.d/virtualbox 3aed81b34e30eca2393ca3c9730da675
Description: x86 virtualization solution - base binaries
 VirtualBox is a free x86 virtualization solution allowing a wide range
 of x86 operating systems such as Windows, DOS, BSD or Linux to run on a
 Linux system.
 .
 This package provides the binaries for VirtualBox. Either the virtualbox-dkms
 or the virtualbox-source package is also required in order to compile the
 kernel modules needed for virtualbox. A graphical user interface for
 VirtualBox is provided by the package virtualbox-qt.

"	PeterF
14455	Error writing to a file froma SMB share - shared through VirtualBox	Windows	VirtualBox 5.0.2	2015-08-16T13:00:39Z	2015-08-16T13:00:39Z	2015-08-16T13:00:39Z	"Summary:  This problem is similar to ticket # 14252.  Have upgraded to 5.0.2r102096, however, problem still exists.  Did not have problem with version 4.3.28.  Can create a file, delete the file, but cannot modify the file that is an SMB share, shared via VirtualBox to guest systems.

Issue:  Connect a SMB share to Linux host and share it via VirtualBox to guest VMs.  In Linux Guest VM access shared folder via mount /media/sf_Shared.  Can create file, however, cannot modify file.  Receive the following error:  ""The document cannot be saved, as it was not possible to write to /media/sf_Shared/lin.txt.  Check that you have write access to this file or that enough disk space is available.""  In Linux guest delete file works.  With a Windows 8.1 Guest VM access shared folder via G: drive (\\vboxsvr\Shared).  Can create file, however cannot modify file lin.txt.  Receive error:  ""An unexpected error occurred while writing G:\lin.txt.""  In Windows guest delete file works.  Also,  created file from both Linux and Windows guest systems and then accessed the file from the host.  Confirmed permissions set on the file were correct.  Can modify the file via the host.

Temporary Workaround:  In both Linux and Windows guest systems connect to SMB server directly (\\mestor\Shared).  Can modify files.

Host System:
HP envy15t with 16GB RAM, Intel i7-4700MQ, Sandisk SSD 120GB drive
Xubuntu - 15.04 - Vivid
VirtualBox version 5.0.2 r102096

Linux Guest System:
Kubuntu - 14.10 - utopic
Guest Additions version 5.0.2r102096

Windows Guest System:
Windows 8.1 - 6.3 build 9600
Guest Additions version 5.0.2r102096

Sincerely,

Charles"	GrizzlyWullf
15842	Error with VBoxManage internalcommands createrawvmdk on SAS 4K block size drive.	Linux	VirtualBox 5.1.4	2016-08-21T22:16:56Z	2016-08-21T22:16:56Z	2016-08-21T22:16:56Z	"  - The host (and guests) are under Ubuntu 16.04.1 LTS.
  - My system has 2 X SAMSUNG MZ7KM480 SSD and 6 X SEAGATE  Model: ST1000NX0323. I can create virtual drive on SSD drives without any problem but it does NOT work on SAS drives. The problem is the same with DOS or GPT format.
  - The user is in vboxusers and disk groups.
  - Partitions are readable with the dd command.

ma@X10DRi:~$ VBoxManage internalcommands createrawvmdk -filename /export/VirtualBox/VMs/VM-A1/lvdatah6.vmdk -rawdisk /dev/sdh -partitions 6
VBoxManage: error: Logical partition without magic
VBoxManage: error: Cannot read the partition information from '/dev/sdh'
VBoxManage: error: The raw disk vmdk file was not created
ma@X10DRi:~$ fdisk -l /dev/sdh
Disk /dev/sdh: 931,5 GiB, 1000204886016 bytes, 244190646 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x44def683

Device     Boot    Start       End   Sectors   Size Id Type
/dev/sdh1            256 244190645 244190390 931,5G  5 Extended
/dev/sdh5            512  52429311  52428800   200G 83 Linux
/dev/sdh6       52429568  55051007   2621440    10G 83 Linux

ma@X10DRi:~$ VBoxManage internalcommands createrawvmdk -filename /export/VirtualBox/VMs/VM-A1/lvdataf6.vmdk -rawdisk /dev/sdf -partitions 6
VBoxManage: error: Cannot read the partition information from '/dev/sdf'
VBoxManage: error: The raw disk vmdk file was not created

ma@X10DRi:~$ fdisk -l /dev/sdf
Disk /dev/sdf: 931,5 GiB, 1000204886016 bytes, 244190646 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 3D5F9AA3-AA3D-49E4-88B7-1E9CD35FFDF8

Device        Start      End  Sectors  Size Type
/dev/sdf5       512 52429311 52428800  200G Linux LVM
/dev/sdf6  52429568 55051007  2621440   10G Linux filesystem

#
# The behavior is exactly the same with the root user.
#
 - hdparm works well with our SSD drive seems NOT to be working with our ST1000NX0323 drives
 - smartctl works well on our both type of drives
 "	michelparis
20196	Error while using VirtioSCSI through vboxwebsrv (Invalid controller type 11 (0x80070057))	Linux	VirtualBox 6.1.18	2021-02-16T09:30:51Z	2021-02-16T10:52:37Z	2021-02-16T10:52:37Z	"Since the lsilogic SCSI controller intermittently crashes with kernel panic, we've tried switching to the new Virtio SCSI controller. 

However, while attempting to use the Java SDK to select this controller through vboxwebsrv, we get an error. This seems to be related to using vboxwebsrv, as selecting the virtio-scsi controller in the UI of Virtualbox or vboxmanage works as expected.

Since the virtio scsi controller is new in 6.1, we suspect that vboxwebsrv has not been modified to accept/handle the new controller type, but we can't be sure.

The error we get back is
{{{
VirtualBox error: rc=0x80070057 Invalid controller type 11 (0x80070057)
}}}

The Java code is:

{{{
IAppliance ova = vbox.createAppliance();
waitFor(ova.read(ovaName));
ova.interpret();
waitFor(ova.importMachines(List.of(ImportOptions.ImportToVDI)));
machine = vbox.findMachine(ova.getMachines().get(0));
ISession session = manager.getSessionObject();
machine.lockMachine(session, LockType.Write);
IStorageController storage = session.getMachine().getStorageControllers().get(0);
storage.setControllerType(StorageControllerType.VirtioSCSI);
session.getMachine().saveSettings();
}}}

The error happens on the line
{{{
storage.setControllerType(StorageControllerType.VirtioSCSI);
}}}

The vboxwebsrv log says:
{{{
00:00:37.787184 SQW01    -- entering __vbox__IStorageController_USCOREsetControllerType
00:00:37.787195 SQW01       findRefFromId(): looking up objref 97ccd3f131838cc7-0000000000000009
00:00:37.787200 SQW01       findComPtrFromId(): returning original IStorageController*=0x7FE6E8004570 (IUnknown*=0x7FE6E80046C0)
00:00:37.787203 SQW01       calling COM method COMSETTER(ControllerType)
00:00:37.787418 main     Pumping COM event queue
00:00:37.787613 main     Pumping COM event queue
00:00:37.787965 main     Pumping COM event queue
00:00:37.788172 main     Pumping COM event queue
00:00:37.788311 main     Pumping COM event queue
00:00:37.788450 main     Pumping COM event queue
00:00:37.788535 main     Pumping COM event queue
00:00:37.788619 main     Pumping COM event queue
00:00:37.788701 main     Pumping COM event queue
00:00:37.788762 SQW01       error, raising SOAP exception
00:00:37.788766 SQW01    API method name:            IStorageController::COMSETTER(ControllerType)
00:00:37.788767 SQW01    API return code:            0x80070057 (NS_ERROR_INVALID_ARG)
00:00:37.788776 SQW01    COM error info result code: 0x80070057 (NS_ERROR_INVALID_ARG)
00:00:37.788777 SQW01    COM error info text:        Invalid controller type 11
00:00:37.788840 main     Pumping COM event queue
00:00:37.788896 main     Pumping COM event queue
00:00:37.788899 SQW01       * ManagedObjectRef: MOR created for IVirtualBoxErrorInfo*=0x007fe6e8005070 (IUnknown*=0x007fe6e8007560; COM refcount now 4/2), new ID is 0xa; now 10 objects total
00:00:37.788906 SQW01    -- leaving __vbox__IStorageController_USCOREsetControllerType, rc: 0x80070057 (-2147024809)
}}}

Installed vboxwebsrv:
{{{
VirtualBox web service 6.1.18 r142142 linux.amd64 (Jan  7 2021 17:47:09) release log
}}}
"	haster
19656	Error when starting VBoxSVC on alpine linux (MUSL)	Linux	VirtualBox 6.1.8	2020-06-11T07:20:05Z	2020-06-11T07:20:05Z	2020-06-11T07:20:05Z	"Hello

I have compiled the virtualbox in alpine linux (MUSL), but when I run it, I get a failure of XPCOM

this is the mistake

VBoxSVC: error: Failed to initialize XPCOM! 
(rc=NS_ERROR_FILE_TARGET_DOES_NOT_EXIST)
VBoxSVC: error: Failed to shutdown XPCOM! (rc=Unknown Status 0x80460016)
XPCOM server has shutdown."	Sodomon
18713	Error when going to full screen Windows 10 (Host+F)	Windows	VirtualBox 6.0.8	2019-06-17T09:43:57Z	2019-06-17T09:43:57Z	2019-06-17T09:43:57Z	"When I go from reduced to full screen I loose the precision of the mouse pointer and sometimes no keyboard.

To get the keyboard again I go to the bottom menu use the menu line full screen line twice (Host+F). Sometimes I get the keyboard response again sometimes I have to do it once more.

The shift of the mouse pointer works immediately when using Host+F. The mouse pointer is shifted from about the size of a menu-bar only vertically."	alainsc11
18179	Error unclear when cloning and default vm folder is not available	all	VirtualBox 5.2.22	2018-12-12T09:56:10Z	2018-12-12T09:56:10Z	2018-12-12T09:56:10Z	"Hi, I think there should be a more readable error when you try to clone a vm and the default vm folder is not available (e.g. was an external drive, now unplugged). On 5.2.22 on Linux I only get a generic VBOX_E_IPRT_ERROR.

To reproduce:
- Configure the default vm folder to a new position
- Render the position unavailable (rename, remove, unplug)
- Create a linked clone of a vm
- A snapshot is created on the original vm
- Error VBOX_E_IPRT_ERROR appears

I think it should say that folder xyz is not available, would make troubleshooting faster."	ctrl
14048	Error Starting Virtual Machine (was Previously Working)	Windows	VirtualBox 4.3.26	2015-04-14T08:04:19Z	2015-04-14T08:04:19Z	2015-04-14T08:04:19Z	"Hi,

I initially installed the VirtualBox-4.3.20-96997-Win in January this year. It was working fine for about a month, the period I was using it.

However, today, after a gap of about 2 months when I again wanted to use it, it refused to open and flashed the error message mentioned below. I read somewhere that reinstalling helps in solving this problem and so I did exactly that by first using the same version and when that didn't work I downloaded the recent version (VirtualBox-4.3.26-98988-Win) and installed it. However it too is displaying the same message now.

Can someone help me in solving this problem?

'''System OS''': Windows Vista SP1[[BR]]
'''Firewall/Antivirus''': Yes (Windows/Avira respectively)[[BR]]
'''OS to run in VM''': Ubuntu[[BR]]

[[BR]]

'''Error Message'''


{{{
    Failed to open a session for the virtual machine CS50 Appliance 2014.

    The virtual machine 'CS50 Appliance 2014' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\Viper\VirtualBox VMs\CS50 Appliance 2014\Logs\VBoxStartup.log'.

    Result Code: E_FAIL (0x80004005)
    Component: Machine
    Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}


}}}


Log files attached in zip format.
"	freeman00in
16879	Error sending boot command: VBoxManage error: VBoxManage: error: Could not send all scan codes to the virtual keyboard (VERR_PDM_NO_QUEUE_ITEMS)	Linux	VirtualBox 5.1.22	2017-07-06T10:11:57Z	2017-08-14T10:55:08Z	2017-08-14T10:55:08Z	"While using packer tool to automate creation of VM images I face the following errors:
{{{
==> virtualbox-iso: Typing the boot command...
==> virtualbox-iso: Error sending boot command: VBoxManage error: VBoxManage: error: Could not send all scan codes to the virtual keyboard (VERR_PDM_NO_QUEUE_ITEMS)
==> virtualbox-iso: VBoxManage: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005), component KeyboardWrap, interface IKeyboard, callee nsISupports
==> virtualbox-iso: VBoxManage: error: Context: ""PutScancodes(ComSafeArrayAsInParam(saScancodes), &codesStored)"" at line 345 of file VBoxManageControlVM.cpp
==> virtualbox-iso: Unregistering and deleting virtual machine...
==> virtualbox-iso: Error deleting virtual machine: VBoxManage error: VBoxManage: error: Cannot unregister the machine 'foo' while it is locked
==> virtualbox-iso: VBoxManage: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MachineWrap, interface IMachine, callee nsISupports
==> virtualbox-iso: VBoxManage: error: Context: ""Unregister(CleanupMode_DetachAllReturnHardDisksOnly, ComSafeArrayAsOutParam(aMedia))"" at line 156 of file VBoxManageMisc.cpp
==> virtualbox-iso: Deleting output directory...
Build 'virtualbox-iso' errored: Error sending boot command: VBoxManage error: VBoxManage: error: Could not send all scan codes to the virtual keyboard (VERR_PDM_NO_QUEUE_ITEMS)
VBoxManage: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005), component KeyboardWrap, interface IKeyboard, callee nsISupports
VBoxManage: error: Context: ""PutScancodes(ComSafeArrayAsInParam(saScancodes), &codesStored)"" at line 345 of file VBoxManageControlVM.cpp
}}}
After this happens VM enters ""Guru Meditation"" state.

I searched for more information about the error got and found https://github.com/hashicorp/packer/issues/4309 referring to https://www.virtualbox.org/changeset/64906/vbox that seems to be some attempt to fix this (?).
Anyway, https://www.virtualbox.org/changeset/64906/vbox looks not to be included in VirtualBox-5.1-5.1.22_115126_el7-1.x86_64 RPM I am using in my Centos 7.3 (judging by the lack of VboxManage keyboardputstring/keyboardputfile API added in this changeset).

Steps to reproduce:
{{{
packer build -var vm_name=foo -var no_gui=true centos-vbox.json
Packer version 1.0.0
}}}
Mapping from packer API to VBoxManage calls can be seen in attached packer debug log. ISO image used is just a minimal CentOs 7.3 image. kickstart file should not be relevant for this bug.
The bug is not deterministic, it happens once per ~4 executions."	pstrzelczak
8473	Error opening current controlling terminal for the process	other	VirtualBox 4.0.4	2011-03-02T06:43:45Z	2018-11-22T09:51:57Z	2018-11-22T09:51:57Z	"Trying to install Oracle_VM_VirtualBox_Extension_Pack-4.0.4-70112.vbox-extpack I got an error popup saying

Failed to install the Extension Pack /export/harri/Oracle_VM_VirtualBox_Extension_Pack-4.0.4-70112.vbox-extpack.

The installer failed with exit code 127: Error creating textual authentication agent: Error opening current controlling terminal for the process (`/dev/tty'): No such device or address.

Details

Result Code: 
NS_ERROR_FAILURE (0x80004005)
Component: 
ExtPackManager
Interface: 
IExtPackManager {2451b1ba-ab1c-42fb-b453-c58433bea8c7}


Of course I checked the access permissions to /dev/tty. Its readable and writable for everybody:

% ls -al /dev/tty
crw-rw-rw- 1 root root 5, 0 Mar  2 06:04 /dev/tty


Please note that running Virtualbox as root is not an option.
"	Harri
10092	Error message when using a normal command which should not give this message	Linux	VirtualBox 4.1.8	2011-12-27T12:27:01Z	2015-05-29T16:01:19Z	2015-05-29T16:01:19Z	"After giving the command (as root):
{{{
su - vboxuser -c ""/usr/bin/VBoxManage controlvm ""vmname"" acpipowerbutton""
}}}
the following command is given in a loop each second
{{{
su - vboxuser -c ""/usr/bin/VBoxManage -nologo showvminfo ""vmname"" -machinereadable"" | grep -q 'VMState=""poweroff""'
}}}
until this command returns 0 and the loop is ended.
Apparently at the moment the command returns VMState=""poweroff"" the command VBoxManage also gives the following error message:
{{{
VBoxManage: error: The object is not ready
VBoxManage: error: Details: code E_ACCESSDENIED (0x80070005), component Console, interface IConsole, callee nsISupports
Context: ""COMGETTER(RemoteUSBDevices)(ComSafeArrayAsOutParam(coll))"" at line 1698 of file VBoxManageInfo.cpp
}}}"	Freek de Kruijf
17797	Error in ipl windows xp	other	VirtualBox 5.1.34	2018-06-01T09:46:09Z	2018-06-01T10:06:16Z	2018-06-01T10:06:16Z	starting windows xp from my linux system (ubuntu 16.04) i get an error (see logs attached)	paocos
18928	Error Importing an Appliance (ODI)	Windows	VirtualBox 6.0.12	2019-09-13T19:33:36Z	2019-09-20T05:02:14Z	2019-09-20T05:02:14Z	"Hi

I have Virtual Box installed on my work laptop with a working appliance on it for just Linux.
I am trying to import an appliance for Oracle Data Integrator but I keep getting an error message shown here:

''Failed to import appliance C:\Users\marhamil\Downloads\VBoxApp-ODI12c\ODI 12c Getting Started VM - OTN 122131.ova.
Result Code: E_INVALIDARG (0x80070057)''

Please can someone help?

Thanks,
From Mark"	Mark H
12261	Error Enable 3D Acceleration in Virtualbox.	all	VirtualBox 4.3.0	2013-10-26T14:34:56Z	2015-04-06T23:40:17Z	2015-04-06T23:40:17Z	"When I try to Enable 3D Acceleration enabled in the VMs, I get the following message:

""
This VM was configured to use 3D acceleration. However, the 3D support of the host is not working properly and the VM cannot be started. To fix this problem, either fix the host 3D support (update the host graphics driver?) or disable 3D acceleration in the VM settings (VERR_NOT_AVAILABLE).

Código Resultado: NS_ERROR_FAILURE (0x80004005)
Componente: Console
Interfaz: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}""

My graphics card is ATI / AMD Integrated ATI Raedon 3300 and I have installed the proprietary drivers 13.1 Legacy. My OS is Linux Mint 13 64 bits based on Ubuntu 12.04.1 LTS.

I think I have correctly installed the proprietary drivers and I have also installed Video Hardware Acceleration...

[[Image(http://imageshack.us/a/img812/7149/aqer.png)]]

'''Note :''' In the version 4.2.18 this did not happen, working properly ..

Thanks ..
"	Malus
19850	Error Cloudera Virtual Box	other	VirtualBox 6.1.10	2020-09-03T07:28:37Z	2020-09-10T14:32:21Z	2020-09-10T14:32:21Z	"Me sale error al iniciar el VirtualBox, tengo una AMD y active la virtualizacion

Adjunto el log:
https://drive.google.com/file/d/1RqturBGi68vClXJsaWS3rkjeQao9SJPC/view?usp=sharing

Y la imagen del problema:
https://drive.google.com/file/d/1UqPO0Mo4fyurG37aYymOQpjvV9bYwtM-/view?usp=sharing"	angelocalixto
21419	"Error ""kmk: glslangValidator: Command not found""while building VirtualBox"	other	VirtualBox-7.0.6	2023-01-20T05:46:10Z	2023-01-20T06:20:37Z	2023-01-20T06:20:37Z	"My System Environment:
Ubuntu 22.04.1 LTS

Kernel version:
5.15.0-58-generic #64-Ubuntu SMP

I followed instructions in https://www.virtualbox.org/wiki/Linux%20build%20instructions to build VirtualBox from source code. The all packages I had downloaded and then I began to build with command ""kmk all"", but error occurred: 

{{{
glslangValidator -V --vn ""dxvk_blit_frag_1d"" ""/home/ph/VirtualBox/VirtualBox-7.0.6/src/libs/dxvk-native-1.9.2a/src/dxvk/shaders/dxvk_blit_frag_1d.frag"" -o ""/home/ph/VirtualBox/VirtualBox-7.0.6/out/linux.amd64/release/obj/VBox-DxVkNativeDxVk/shaders/dxvk_blit_frag_1d.h""
kmk: glslangValidator: Command not found
kmk: *** [/home/ph/VirtualBox/VirtualBox-7.0.6/src/libs/dxvk-native-1.9.2a/Makefile.kmk:281: /home/ph/VirtualBox/VirtualBox-7.0.6/out/linux.amd64/release/obj/VBox-DxVkNativeDxVk/shaders/dxvk_blit_frag_1d.h] Error 127
kmk: *** Waiting for unfinished jobs....
kBuild: Generating C++ Server API wrapper files from XIDL - part 2
filesplitter: Out of 66 files: 66 rewritten, 0 unchanged. (/home/ph/VirtualBox/VirtualBox-7.0.6/out/linux.amd64/release/obj/VBoxAPIWrap)
kBuild: Linking VBox-DxVkNativeUtil
kBuild: Generating C++ Server API wrapper header files from XIDL
filesplitter: Out of 133 files: 133 rewritten, 0 unchanged. (/home/ph/VirtualBox/VirtualBox-7.0.6/out/linux.amd64/release/obj/VBoxAPIWrap)
kBuild: Compiling RuntimeGuestR3Shared - /home/ph/VirtualBox/VirtualBox-7.0.6/src/VBox/Runtime/common/fs/isomakercmd.cpp
kBuild: Compiling RuntimeGuestR3 - /home/ph/VirtualBox/VirtualBox-7.0.6/src/VBox/Runtime/common/fs/isomakercmd.cpp
kBuild: Compiling bldRTErrMsgSorter - /home/ph/VirtualBox/VirtualBox-7.0.6/src/VBox/Runtime/common/err/errmsg-sorter.cpp
kBuild: Compiling RuntimeR3 - /home/ph/VirtualBox/VirtualBox-7.0.6/src/VBox/Runtime/common/fs/isomakercmd.cpp
kmk: *** Exiting with status 2

}}}
"	penghao
15321	Enhancing vbox-img from VBoxManage	Windows	VirtualBox 5.0.18	2016-04-19T17:30:33Z	2016-04-19T19:13:56Z	2016-04-19T19:13:56Z	"vbox-img is capable of doing things from VBoxManage and maybe this can be enhanced further to contain all useful things from VBoxManage that affect disk images. For example ""vbox-img compact"" does not show any progress while I remember that ""VBoxManage modifyhd"" has done this which could also be implemented in vbox-img."	Sworddragon
19614	Enabling Page Fusion cause Windows 10 guests to hang random time after booting	Windows	VirtualBox 6.1.8	2020-05-23T00:41:37Z	2020-05-23T00:41:37Z	2020-05-23T00:41:37Z	"I first posted in the [https://forums.virtualbox.org/viewtopic.php?f=2&t=98123&sid=51fc9f959284400beaac6aadba19f088 forums] and didn't get much direction.

Sometime after upgrading to 6.1.x (don't remember the exact version - .2 or .3 or maybe .4 I think) my Windows 10 guests would randomly freeze shortly after booting.  I built a new from DVD/ISO Windows 10 1909 VM and it didn't/wouldn't freeze.  In comparing the output of ""VBoxManage showvminfo"" I noticed that I had different settings for [https://www.virtualbox.org/manual/UserManual.html#guestadd-balloon Memory Balloning] and [https://www.virtualbox.org/manual/UserManual.html#guestadd-pagefusion Page Fusion].

The freezing behavior didn't change with adjustments to the memory balloning settings, but did for page fusion.  If page fusion was enabled on the ""old"" Windows or the ""new"" Windows guest they would freeze.  Disabling page fusion on the guests and they wouldn't freeze.  I could repeat this Page Fusion '''Enabled''' = Freeze, Page Fusion '''Disabled''' = No Freeze.

The guest additions version of the guest matched the host (6.1.8) when I did the final set of testing.

VirtualBox: 6.1.8 with guest additions[[BR]]
Host: Linux Mint 18.3 Cinnamon 64-bit[[BR]]
Kernel: 4.15.0.n[[BR]]
Memory: 48GB (was 16GB when I initially set up memory balloning and page fusion back in 5.2 days)[[BR]]



"	DerekD
19182	Enabling 3D-acceleration hangs boot	Linux	VirtualBox 6.1.0	2019-12-23T12:49:13Z	2019-12-23T12:49:13Z	2019-12-23T12:49:13Z	"VBox 6.1.0 – Version 6.1.0 r135406 (Qt5.9.5)

Host: Ubuntu 18.04; 4.15.0-72-generic #4.15.0.72.81

Guest: Manjaro Linux 18.1.4, 4.19.88-1-MANJARO

Guest: VBoxSVGA, 3D enabled; Guest Additions 6.1.0

Box freezes at boot after boot menu and short appearance of bootup messages. This occurs with bith Chipsets, PIIX3 and ICH9.

Problem disappears when disabling 3D in VM settings.

Possibly a duplicate of Ticket #18914, as under 6.0.10 the problem did not appear and 18914 is for VB 6.0.12."	phaidros
10383	Enable mouse integration to be disabled in the guest config	Windows	VirtualBox 4.1.8	2012-03-26T19:44:41Z	2012-03-26T19:44:41Z	2012-03-26T19:44:41Z	"When using a VirtualBox guest in full-screen mode as root, the mouse integration can cause issues with programs like Synergy <http://synergy-foss.org/>. Because this is for school computer labs and the local user does not own the guest (for security reasons), I would like to be able to permanently disable mouse integration in the guest config.

Host is RHEL 5.6 x86_64. Guest is Windows XP.

BTW, I have the host key disabled for security reasons, which is why this is a pain."	jwedgeco
14985	Enable 3D acceleration cause black screen or flickering -> obsolete	Linux	VirtualBox 5.0.12	2015-12-29T01:31:41Z	2018-01-19T12:51:38Z	2018-01-19T12:51:38Z	"Ubuntu 14.04.3 X64 + mate 1.82 for both host and guest
Enable 3D acceleration for guest VM
enable hardware acceleration for Chrome in both guest and host
for Chrome, flicking in VM, but works fine in host 

the screen of VM will go black randomly, only can I sent ctrl-alt-backspace to restart X. However, after update both kernel to 4.2 (sudo apt-get install linux-generic-lts-wily). no more black screen in VM. But Chrome still flickering screen when launch if  hardware acceleration is enable in its setings. A 4 seconds screen cast is on https://youtu.be/paVfpClhyj8"	maxchen
17712	ed stat  Guest VM with OS/2 does not resume from saved state	other	VirtualBox 5.2.10	2018-04-25T12:44:02Z	2018-04-29T16:50:16Z	2018-04-29T16:50:16Z	"Since versions 5.1.36 and 5.2.10 VM-guest (OS/2 Warp4.5.2) does no longer resume from saved state. Up to and including VBox 5.1.34 all worked without any problems.

When trying to resume following error message pops up:
{{{
Für die virtuelle Maschine OS2 konnte keine neue Sitzung eröffnet werden.
    (translation: ""for the VM OS2 no new session could be opened"")
The VM session was aborted.

Fehlercode:NS_ERROR_FAILURE (0x80004005)
Komponente:SessionMachine
Interface:ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}
}}}
and vbox.log ends '''before''' the usual lines
{{{
00:00:03.338926 Changing the VM state from 'LOADING' to 'SUSPENDED'
00:00:03.338980 Changing the VM state from 'SUSPENDED' to 'RESUMING'
00:00:03.339245 Changing the VM state from 'RESUMING' to 'RUNNING'
00:00:03.339263 Console: Machine state changed to 'Running'
...
}}}

I have prepared a test-VM with OS/2 guest (just fresh installed, no guest-additions yet) called ""Warp5"". Will upload the complete tar.bz2-packed folder (it's only 293 MB) with which you easily can reproduce the bug. The VM is absolutely virgin, no snapshots and shut down. After importing it into '''VBox 5.1.24''', just do the following steps:
1. create a snapshot to preserve the vdi for testing
2. start-up the VM, it will boot automatically to the desktop
3. click on the desktop to catch the mouse pointer
     do whatever you like, or even nothing
4. release mouse pointer (ctrl right)
5. close the VM and select ""save the VM""
   reboot host (this is just to simulate normal usage and makes sure the bug shows up if present)
6. start the VM again - it only takes a few seconds and with VBox 5.1.34 all is fine.

Try the same with VBox 5.1.36 or 5.2.10 and VM will crash for sure without any significant log entries for guest or host.

Remark:
to cleanly shut down the OS/2-VM, just right click on the desktop and from the menu popping up select ""Systemabschluß"".

If additional information is needed, please let me know.
"	Ingo
11978	Dup ping and not network connectivity while bridged on WIFI	all	VirtualBox 4.2.16	2013-07-21T22:49:50Z	2015-12-29T19:30:45Z	2015-12-29T19:30:45Z	"Good day all,
I am running Fedora 19 x64.  Using the same laptop for couple of years now and longer for Virtualbox.  During the last upgrade I started having connectivity issues on some machines.  Further investigation found that only machines that were bridged on the WIFI was affected.  Let me know if you want any configuration files or anything at all.
Thanks, Devon
{{{
[devon@fisc-dcj-rhw ~]$ ping google.com
PING google.com (74.125.229.227) 56(84) bytes of data.
64 bytes from 74.125.229.227: icmp_seq=1 ttl=56 time=15.5 ms
64 bytes from 74.125.229.227: icmp_seq=1 ttl=55 time=15.6 ms (DUP!)
64 bytes from 74.125.229.227: icmp_seq=2 ttl=56 time=18.6 ms
64 bytes from 74.125.229.227: icmp_seq=2 ttl=55 time=18.7 ms (DUP!)
64 bytes from 74.125.229.227: icmp_seq=3 ttl=56 time=17.7 ms
64 bytes from 74.125.229.227: icmp_seq=3 ttl=55 time=17.8 ms (DUP!)
64 bytes from 74.125.229.227: icmp_seq=4 ttl=56 time=83.2 ms
64 bytes from 74.125.229.227: icmp_seq=4 ttl=55 time=83.3 ms (DUP!)
64 bytes from 74.125.229.227: icmp_seq=5 ttl=56 time=103 ms
64 bytes from 74.125.229.227: icmp_seq=5 ttl=55 time=103 ms (DUP!)
}}}"	Devon
8179	Dreamweaver ftp errors because of uppercase directories on mapped drives	Windows	VirtualBox 4.0.2	2011-01-25T02:37:44Z	2015-06-17T17:48:25Z	2015-06-17T17:48:25Z	"My setup:

Virtualbox 4.0.2
Host OS: Ubuntu 10.10
Guest OS: Windows 7
Dreamweaver version: CS5

I keep getting errors when trying to put files onto my server. An example error would be:
------------------------------------------------------------
Started: 1/24/2011 6:23 PM

DOMAIN.COM\index.html - error occurred - An FTP error occurred - cannot put index.html.  Access denied.  The file may not exist, or there could be a permission problem. 

File activity incomplete. 1 file(s) or folder(s) were not completed.

Files with errors: 1
DOMAIN.COM\index.html

Finished: 1/24/2011 6:23 PM
----------------------------------------------------

The error is occurring because the directory DOMAIN.COM does not exist on the server. However, I didn't put it from a local file system with an uppercase directory of DOMAIN.COM. On my system the directory in question is lowercase, domain.com.

This only seems to happen when the local location is on a mapped network drive."	V_RocKs
20784	Dragging a file from mobile phone to guest crashes the machine	Linux	VirtualBox 6.1.26	2022-01-20T17:42:29Z	2022-01-20T17:42:29Z	2022-01-20T17:42:29Z	When I drag a file from phone through MTP accessed in KDE directly into an Ubuntu guest running the same operating system, VirtualBox crashes.	miklcct
17512	Drag-n-Drop error, Linux host, Windows 7 client	Windows	VirtualBox 5.2.6	2018-01-31T07:55:47Z	2022-02-04T10:57:46Z	2022-02-04T10:57:46Z	"When attempting to drag a PDF attachment from Thunderbird on Linux and dropping on a Windows 7 VM desktop, I get the error:

Drag and drop operation from host to guest failed.

Drag and drop error from host (VERR_INVALID_PARAMETER).

Result Code: VBOX_E_IPRT_ERROR (0x80BB0005)
Component: GuestWrap
Interface: IGuest {13a11514-402e-022e-6180-c3944de3f9c8}

I have attached files per the website https://www.virtualbox.org/wiki/DnDDebug."	mfoley
19277	Drag and Drop from Windows 8.1 to Ubuntu 18.04	Windows	VirtualBox 6.1.2	2020-01-29T09:18:55Z	2022-02-04T10:56:17Z	2022-02-04T10:56:17Z	"Hello.
Virtualbox 6.1.2 
The latest extension pack 6.1.2
Host system is Ubuntu 18.04
Guest System is Windows 8.1
Drug and drop files or directories from host system to guest works well.
If I drag and drop a file from guest system to host everything also works fine.
But when I drag and drop directory (directory name 123456) from guest system to host system, it writes error:
Error getting information about the file «/tmp/VirtualBox Dropped Files/2020-01-29T09:12:18.533778000Z/123456»: No such file or directory

I went to the directory /tmp/VirtualBox Dropped Files/2020-01-29T09:12:18.533778000Z/
There I see my files with a false slash:
123456\Hello.txt
123456\Hello2.txt
This is a file names.

But it must be /tmp/VirtualBox Dropped Files/2020-01-29T09:12:18.533778000Z/123456/Hello.txt
and etc.

Please fix a bug.
And in my home directory it create Directory with name /tmp/VirtualBox Dropped Files/2020-01-29T09:12:18.533778000Z/123456

I attach screenshots"	dotmitsu
16146	Double click to single click in VirtualBox GUI	Windows	VirtualBox 5.1.8	2016-11-04T01:22:25Z	2016-12-01T17:28:16Z	2016-12-01T17:28:16Z	"Whether I click on the QT Menu's(File, Machine, View...) or within the VM I have to double-click to produce a single click, I think it might be a QT bug along these lines, http://stackoverflow.com/questions/18444431/mouse-events-blocked-because-of-qgl-view
If I turn off Mouse Integration in the menu the cursor is captured and I can use the VM normally.

"	chrisq
17044	Doing network copy from shared folder does not transfer file correctly: wrong md5sum	other	VirtualBox 5.1.26	2017-08-30T02:50:26Z	2019-08-29T10:40:50Z	2019-08-29T10:40:50Z	"When I copy file from shared folder to remote target with scp, scp exists with success 0, yet the md5sum on the remote target is different from the source.
Coping / scp'ing the same file from non-shared folder within same Vm works correctly: same md5sum on remote target.
Scp transfers different file sizes in the two cases.

E.g. 
md5sum  /media/sf_dloads/dhnc_m4_fw.tar.bz2

403f9fe21ed74762923d3d7c2087d62a  /media/sf_dloads/dhnc_m4_fw.tar.bz2

md5sum dhnc_m4_fw.tar.bz2 

403f9fe21ed74762923d3d7c2087d62a  dhnc_m4_fw.tar.bz2

scp -v /media/sf_dloads/test/dhnc_m4_fw.tar.bz2  root@192.168.1.110:/tmp/

.....
Transferred: sent 455796, received 1796 bytes, in 1.2 seconds
Bytes per second: sent 367895.7, received 1449.6
debug1: Exit status 0

on target:

md5sum  /tmp/dhnc_m4_fw.tar.bz2

ed67bef761dbfb2b35f62510b2c930c5  /tmp/dhnc_m4_fw.tar.bz2

scp -v dhnc_m4_fw.tar.bz2  root@192.168.1.110:/tmp/

.....
Transferred: sent 456788, received 1856 bytes, in 1.6 seconds
Bytes per second: sent 291460.5, received 1184.2
debug1: Exit status 0

on target:

 md5sum  /tmp/dhnc_m4_fw.tar.bz2

403f9fe21ed74762923d3d7c2087d62a  /tmp/dhnc_m4_fw.tar.bz2
"	dry
11922	Document on creating CD/DVD (and installing Guest Additions) do not mention VM must be shut down	Linux	VirtualBox 4.2.14	2013-07-03T12:44:00Z	2013-07-04T19:52:51Z	2013-07-04T19:52:51Z	"I'm running a CentOS 6 VM guest on an XUbuntu 13.04 host using virtualbox 4.2.10_Ubuntu r84101

Under Machine -> Settings -> Storage, the menu item to ""Add a CD/DVD Device"" is disabled for both the IDE and SATA controllers.

Neither https://www.virtualbox.org/manual/ch04.html#idp14782496 
nor https://www.virtualbox.org/manual/ch03.html#settings-storage say anything about shutting down in order to use Device -> Storage -> Add CD/DVD Device.

The latter says ""You can modify these media attachments freely.""

Please add text to these manual pages to make it clear how to add a CD or DVD device.
"	David Biesack
15953	doc/manual/fr_FR/ missing man_VBoxManage-debugvm.xml and man_VBoxManage-extpack.xml	Linux	VirtualBox 5.1.6	2016-09-19T02:26:12Z	2016-09-21T14:57:54Z	2016-09-21T14:57:54Z	"I'm trying build Vbox with VBOX_WITH_DOCS_TRANSLATIONS=1


{{{
kmk: *** No rule to make target `/builddir/build/BUILD/VirtualBox-5.1.6/doc/manual/fr_FR/man_VBoxManage-debugvm.xml', needed by `/builddir/build/BUILD/VirtualBox-5.1.6/obj/obj/manual/fr_FR/user_man_VBoxManage-debugvm.xml'.  Stop.
}}}

in ./doc/manual/Makefile.kmk, user_man_VBoxManage-debugvm.xml should not be add to fr_FR translation .

fyi is not a new bug , search on french contributions seems that doesn't have debugvm

https://www.virtualbox.org/pipermail/vbox-dev/2013-February/011232.html etc "	sergiomb
19592	dnf upgrade of virtual box sequence	Linux	VirtualBox 6.1.8	2020-05-16T21:33:02Z	2020-05-22T12:20:53Z	2020-05-22T12:20:53Z	"The update sequence seems wrong, taking steps to apply 6.1.6 after 6.1.8 

Output to screen:

# dnf upgrade
Last metadata expiration check: 1:17:10 ago on Sat 16 May 2020 03:43:57 PM EDT.
Dependencies resolved.
=========================================================================================================================
 Package                      Architecture         Version                                Repository                Size
=========================================================================================================================
Upgrading:
 VirtualBox-6.1               x86_64               6.1.8_137981_fedora31-1                virtualbox                94 M

Transaction Summary
=========================================================================================================================
Upgrade  1 Package

Total download size: 94 M
Is this ok [y/N]: y
Downloading Packages:
VirtualBox-6.1-6.1.8_137981_fedora31-1.x86_64.rpm                                        3.8 MB/s |  94 MB     00:24    
-------------------------------------------------------------------------------------------------------------------------
Total                                                                                    3.8 MB/s |  94 MB     00:24     
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing        :                                                                                                 1/1 
  Running scriptlet: VirtualBox-6.1-6.1.8_137981_fedora31-1.x86_64                                                   1/2 
  Upgrading        : VirtualBox-6.1-6.1.8_137981_fedora31-1.x86_64                                                   1/2 
  Running scriptlet: VirtualBox-6.1-6.1.8_137981_fedora31-1.x86_64                                                   1/2 

Creating group 'vboxusers'. VM users must be member of that group!


  Running scriptlet: VirtualBox-6.1-6.1.6_137129_fedora31-1.x86_64                                                   2/2 
  Cleanup          : VirtualBox-6.1-6.1.6_137129_fedora31-1.x86_64                                                   2/2 
  Running scriptlet: VirtualBox-6.1-6.1.6_137129_fedora31-1.x86_64                                                   2/2 
  Verifying        : VirtualBox-6.1-6.1.8_137981_fedora31-1.x86_64                                                   1/2 
  Verifying        : VirtualBox-6.1-6.1.6_137129_fedora31-1.x86_64                                                   2/2 

Upgraded:
  VirtualBox-6.1-6.1.8_137981_fedora31-1.x86_64                                                                          

Complete!

"	Wheaties
19956	Disk booting no longer works automatically on EFI system after cdrom is removed	Linux	VirtualBox 6.1.14	2020-10-10T18:31:05Z	2021-03-19T19:45:35Z	2021-03-19T19:45:35Z	"I am able to install devuan 32 bit and 64 bit to respective EFI VMs.  This involves navigating the UI and possibly booting from the EFI shell to coerce vbox to boot the install media.  However, after the install is complete, vbox correctly boots to the grub menu the installation media installed.

A problem arises, however, if I insert any arbitrary CD into the cdrom device.  Any attempt to boot off the CD requires navigating the UI again, and in most cases, requires booting from the EFI shell no matter what combination of options I select (such as deleting all but the Cdrom from the boot options and even changing the boot order).  There does not seem to be any way to get vbox to boot off the hard drive after a cd has been inserted and removed.

This behavior appears to be consistent across 32 and 64 bit EFI VMs.

Steps to reproduce:

* Create new EFI VM
* launch installer CD (most likely from EFI Shell, since vbox won't launch the CD automatically)
* complete the install and reboot from hard drive
* insert any CD into the drive
* attempt reboot
* remove the CD from the drive
* attempt to reboot from hard drive again

Expected Results:

VM will return to booting from the hard drive without needing to do anything; the grub menu will appear as normal.

Actual Results:

If the scenario is reproduced, vbox will not boot off the hard drive by itself.  It will be necessary to launch from navigating and selecting via the UI or by using the EFI shell"	Harry M
18142	"disable option for ""Welcome to VirtualBox!"""	all	VirtualBox 5.2.22	2018-11-21T15:21:32Z	2018-11-30T00:17:10Z	2018-11-30T00:17:10Z	"after I start VirtualBox, before the machines and the details was shown, now I see this ""Welcome to VirtualBox!"" Mickey Mouse design. I would like a preference to disable this or to have the choice what so see, the Mickey Mouse Welcome, the machine details, the machine snaps, etc.."	keinereiner
11290	DirectDraw clipping/refresh bug with XP guest	Windows	VirtualBox 4.2.2	2012-12-14T17:35:17Z	2016-08-17T10:20:58Z	2016-08-17T10:20:58Z	"I'm using VirtualBox 4.2.2. Lubuntu 11.10 x86-64 host, Windows XP Pro SP3 guest.

This issue happens with Guest Additions versions 4.1.14 and 4.2.2. It shows up with the WinUAE Amiga emulator.

When WinUAE is using DirectDraw for its graphics output, dragging the window partly off-screen causes the image to appear near the upper left of the screen. See the attached screenshots. The problem does not happen when WinUAE is set to use Direct3D.

To demonstrate:
- Download an example program, e.g. ftp://ftp.amigascne.org/pub/amiga/Groups/D/DOC/DOC-NoName
- Download the WinUAE installer from http://www.winuae.net/ and run it.
- Run WinUAE. When the setting window opens click Miscellaneous in the treeview. Set Graphics API to DirectDraw.
- Click Floppy drives and then the ""..."" button near the top right of the window. Choose the program you just downloaded.
- Click Start to start the emulation. In a few seconds you should see something in the emulation window.
- Press the middle mouse button to un-capture the mouse and drag the emulation window so it is partly off-screen. Notice that the window contents appear at the top left of the desktop, and the actual emulation window no longer updates.
"	Donuts
17067	Dir Copy Fails to Copy Files to Shared Dir	Windows	VirtualBox 5.1.26	2017-09-08T19:02:26Z	2019-06-04T06:05:46Z	2019-06-04T06:05:46Z	"Running VB Version 5.1.26 r117224 (Qt5.5.1) on Linux Mint 18.2 Cinnamon x64. Guest is Windows 10 Home x64 version 10.0.15063. All with latest updates (including the Creator's Update). 
Several shared folders set up on the Host. Shared Clipboard & Drag and Drop set to Bidirectional. VB.log attached.

Problem: Copying a directory FROM the Windows 10 guest to a Linux Shared Directory results in only the first directory being created. No files or sub-directories are copied. This has only been the case since Windows 10 Creator's Update installed. The last version that did not have this problem was 5.1.22 but that was before the Creator's Update installed.

Steps to reproduce:-
1. In the Windows 10 Guest open two instances of File Explorer.
2. Set one to a directory containing files on the Guest and the other to a Shared Folder on the Host.
3. Drag the Windows directory to the Shared folder.

I'm finding nothing is transferred except the top-most directory but none of it's children.

This forum post refers: https://forums.virtualbox.org/viewtopic.php?f=7&t=83829"	Craig100
21003	Dialogs don't fit in 1366x768 screen	all	VirtualBox 6.1.32	2022-06-22T08:38:02Z	2022-06-22T08:38:02Z	2022-06-22T08:38:02Z	Dialogs don't fit in my laptop's screen and I don't see the buttons.	paaguti-u
15030	DHCP server on natnetwork doesn't return DNS servers	Linux	VirtualBox 5.0.12	2016-01-12T14:24:23Z	2016-01-12T15:16:39Z	2016-01-12T15:16:39Z	"If I start up a guest VM on old school nat networking I see an option 6 come thru with the DHCP response from the virtualbox DHCP server.

If I do the same on a natnetwork'd guest all but one of the same options arrive in the DHCP response, including 15 for a DNS domain name, but option 6 is consistently missing and obviously this means the DNS server is never configured inside the guest.
If I set it manually in the guest to the IP I configured under ""VBoxManage dhcpserver add"" everything works as expected so networking is certainly working.

This is easily observed with a linux guest by installing and running dhcpdump while running ""dhclient -d"""	tommyvn
16283	Detachable run won't let its window close correctly	other	VirtualBox 5.0.18	2016-12-12T21:16:10Z	2016-12-15T16:13:55Z	2016-12-15T16:13:55Z	"VirtualBox 5.0.18 r106667, Ubuntu 14.04.4 (64-bit) guest running on CentOS 7 (64-bit) host. I run the guest in detachable mode, but when I close the window and select ""Continue to run in background"", I get this message:

Failed to set the extra data for key GUI/Fullscreen of machine  to value {}.

The object is not ready.

Result Code: E_ACCESSDENIED (0x80070005)
Component: SessionMachine
Interface: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}

...and the guest aborts."	Daniel U. Thibault
21169	Deprecation of libIDL on Linux	other	VirtualBox 7.0.0	2022-10-19T15:21:19Z	2022-11-01T12:17:07Z	2022-11-01T12:17:07Z	"Hi,

libIDL has been deprecated 8 years ago and some distributions (i.e., Gentoo) are trying to drop it.  VirtualBox still depends on it (it is the only dependency left in the tree).

Please consider finding a non-deprecated replacement.

Thank you!


https://gitlab.gnome.org/Archive/libidl
"	ceamac
17938	Deleting snapshot on-line causes I/O errors in guest	other	VirtualBox 5.2.16	2018-08-18T21:53:28Z	2018-08-19T09:09:22Z	2018-08-19T09:09:22Z	"Host: Fedora 28
Guests: Fedora 28 x2 + (2 older Fedora machines)

Both guests in this event are F28 & had a single snapshot + current state, and were up (but largely idle).

Deleted snapshot of first machine.  (Using VirtualBox GUI).  It took quite a while, as the snapshot was almost 2 yrs old.

While the delete was running, I had an ssh session into the VM.  I got an error ""Read only filesystem"", then ""ps not found"".  ls worked - for a while.

This typically means that the kernel got an unrecoverable Disk I/O error - e.g. a timeout.  But as the logs live on the disk in question, and it went read-only, I can't prove it.

shutdown was also not found.  I waited a while, and commands started getting bus errors.  Seemed clear that the disks were off-line.

So I waited for the disk merge (snapshot delete) to finish, did a vboxmanage reset, and rebooted the VM.

Log file will be attached.  Note that it also shows a lot of display resize events - I see no reason for this.  The VM was started detachable; the GUI is visible, but it seems to blink for no particular reason...

Here is an 'ls' of the VDI involved:
{{{
 ls -lih /home/root/VirtualBox_VMs/Overkiller/*.vdi /home/root/VirtualBox_VMs/Overkiller/*/*.vdi
12323679 -rw-------. 1 root root 1.6G Mar 20  2016 /home/root/VirtualBox_VMs/Overkiller/Fedora23_Overkiller.vdi
12320772 -rw-------. 1 root root  35G Aug 18 16:04 /home/root/VirtualBox_VMs/Overkiller/Fedora_17_Overkill.vdi
13893639 -rw-------. 1 root root  22G Aug 18 15:49 /home/root/VirtualBox_VMs/Overkiller/Snapshots/{e981f25e-0fc7-4ba7-9666-9d00bc48eae3}.vdi
}}}

The I/O errors don't appear to be a one-off event.  I had a second VM which also had a single snapshot that I deleted the same way.  It suffered the same fate.  Log also attached.  Its ls:
{{{
ls -lih /home/root/VirtualBox_VMs/WikiWorld/*.vdi /home/root/VirtualBox_VMs/WikiWorld/*/*.vdi
9306120 -rw-------. 1 root root 30G Aug 18 16:08 /home/root/VirtualBox_VMs/WikiWorld/Snapshots/{1bb6e5e7-1e5a-40c8-8d61-daf4ff6611be}.vdi
9306115 -rw-------. 1 root root 49G Aug 18 16:08 /home/root/VirtualBox_VMs/WikiWorld/atto_wiki.vdi

}}}

Snapshot delete times were on the order of 30 minutes (each).

If deleting a snapshot on-line can cause this much havoc, it should not be allowed...
"	Timothe Litt
17606	DeleteSnap ERROR with aRC=VBOX_E_FILE_ERROR (0x80bb0004)	Windows	VirtualBox 5.2.8	2018-03-08T12:02:31Z	2018-04-14T08:39:55Z	2018-04-14T08:39:55Z	"I am running VBox 5.2.8 under fc26. When I tried to delete the oldest snapshot from my Guest Win10x64 it showed progress 4, 3, 2 minutes,
but the all of a sudden the CPU consumption of all 4 cores went up
and the Delete Snapshot ended with a dialog message 
""Callee RC: NS_ERROR_CALL_FAILED (0x800706BE)"".
In the VBoxSVC.log I found the last message:

00:11:03.872176 DeleteSnap ERROR [COM]: aRC=VBOX_E_FILE_ERROR (0x80bb0004) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Could not merge the medium '/home/ksp/VB/Machines/Win10/Snapshots/{299f0e8c-9fca-4d32-be09-8e3201ee7117}.vdi' to '/home/ksp/VB/Machines/Win10/Win10-disk1.vdi' (VERR_INVALID_PARAMETER)}, preserve=true  aResultDetail=0

The problem is reproduceable
"	snoopy26
21415	"Debian/Ubuntu repositories: remove dependency ""vitualbox-x.y recommends linux-image"""	all	VirtualBox-7.0.6	2023-01-17T23:59:41Z	2023-01-17T23:59:41Z	2023-01-17T23:59:41Z	"vitualbox-x.y packages in Debian/Ubuntu repositories should have their dependency

""vitualbox-x.y recommends linux-image"" removed.

1.

This dependency sometimes makes apt resolve conflicts by installing random ""linux-image-*"" packages (which provide ""linux-image"" virtual package).

This mostly includes Linux kernel images dedicated for cloud:
linux-image-*-azure, linux-image-*-gcp, linux-image-*-oracle, linux-image-*-aws

Automatically installing these makes an annoying mess in host's Linux installation,
and may also result in failed upgrades if /boot partition is too small to fit all these kernel images.

2.

At least 1 package providing ""linux-image"" is obviously most likely installed already in any Linux system, so this dependency is quite useless anyway.
"	PHD
14605	Date and time on Linux guests is not updated after a session restoration	Linux	VirtualBox 5.0.4	2015-09-18T13:52:48Z	2015-09-30T15:51:24Z	2015-09-30T15:51:24Z	"When you save the machine state and then restoring it on Linux Guest operating systems after some time the date continues to display the last one before saving and not the current date and time. The problem is not reproduced on Windows Guest, where the clock is refreshed automatically.

It might be in the way that Linux system works to retrieve the time from the hardware clock during boot process and then it is maintained by the OS, but if there is any work around would be great to cause the guest to refresh the date like issuing ""hwclock --hctosys"" automatically."	Panos Kavalagios
16301	Cut off top and bottom on full screen	Windows	VirtualBox 5.0.22	2016-12-17T09:41:39Z	2016-12-17T09:41:39Z	2016-12-17T09:41:39Z	"Preconditions:
- Host: Linux Mint 17.3 64bit
- Guest: Windows 7 64bit
- Guest additions installed
- Fullscreen mode on (host+f)

Reproduction route:
1. lock guest windows (Win+l)
2. leave fullscreen (Host+f)
3. go back to fullscreen (Host+f)
4. click to unlock guest windows

Expected: Fullscreen covers all area
Actual: Top and bottom of the screen are cut off"	JanuszWirtualizacji
21477	Custom VM icons don't show up in Ubuntu Dock with VirtualBox 7	other	VirtualBox-7.0.6	2023-02-08T22:05:46Z	2023-02-08T22:05:46Z	2023-02-08T22:05:46Z	"In Virtualbox 6, I modified the iconfile for each vm, and that icon would show up in the Ubuntu dock. 

On upgrading to 7, the custom icons are still shown inside the VBox Manager GUI, but I just get the default icon in the OS dock bar.

Desired capability shown here: https://twitter.com/0xdf_/status/1529429480858697728

Host OS is Ubuntu 22.04."	dfors
18915	Critical structure corruption blue screen	Windows	VirtualBox 6.0.12	2019-09-09T06:53:24Z	2019-09-18T07:38:00Z	2019-09-18T07:38:00Z	"Hi,
Virtualbox became unusable for me since a few months where the ""CRITICAL_STRUCTURE_CORRUPTION"" blue screens are happening regularly (multiple times per day). I also get screen refreshes all the time where the screen stays black for about 2-3 seconds where nothing can be done until the normal desktop gets back.

Attached is the most recent logfile from today, older logs can be found in my thread in the forum: https://forums.virtualbox.org/viewtopic.php?f=2&t=93939

I am using the VboxVGA driver and I can't use the VboxSVGA driver because the graphical glitches with this driver make working impossible (see my other thread here: https://forums.virtualbox.org/viewtopic.php?f=2&t=94585)"	0x00
16820	Critical error on Windows 7 guest	Windows	VirtualBox 5.1.22	2017-06-08T11:10:42Z	2017-06-08T11:10:42Z	2017-06-08T11:10:42Z	A critical error has occurred to win7 VM. Information attached.	Panos Kavalagios
14591	Critical Error - Failed to create VirtualBoxClient COM object	other	VirtualBox 5.0.4	2015-09-15T16:49:05Z	2015-09-15T16:49:05Z	2015-09-15T16:49:05Z	"using RHEL 6 with latest version of VirtualBox

here is the tutorial I followed to install: http://tecadmin.net/install-oracle-virtualbox-on-centos-redhat-and-fedora/"	seaner8
19318	Critical Error	other	VirtualBox 6.1.2	2020-02-17T02:06:33Z	2020-02-17T16:36:25Z	2020-02-17T16:36:25Z	I was running OpenPLC on my VirtualBox and it froze. I shut it down and now it will not let me start up. 	Urala
4804	creating directories with umlauts in a shared folder fail with error 0x80070057 on Windows Host	other	VirtualBox 3.0.2	2009-08-18T15:42:26Z	2009-08-18T15:42:26Z	2009-08-18T15:42:26Z	"A) cannot create folders with umlauts in a shared folder within a Windows Server 2008 guest.
(probably windows guest in general...)

If I try to create an ""umlaut folder"" within Gentoo guests, which have access to this folder via NFS , there are no problems and the folder is properly created. Also on the host (Gentoo) the folder-name is correctly written in umlauts. (all systems UTF-8)

B) this linux-host-created umlaut-folder is not listed when I refresh the shared folder view in the windows host....

log says nothing related, just:
00:00:01.461 SharedFolders host service: adding host mapping.
00:00:01.461     Host path /mnt/VIRTUAL/EXCHANGE, map name EXCHANGE, writable 1
00:00:01.461 SharedFolders host service: add mapping result VINF_SUCCESS
00:00:01.461 SharedFolders host service: adding host mapping.

I'm using virtualbox-bin 3.0.2 

HOST:
srv1 ~ # eix virtualbox
[U] app-emulation/virtualbox-bin
     Available versions:  1.6.6!f (~)3.0.4+i!m {additions chm headless sdk vboxwebsrv}
     Installed versions:  3.0.2!s(19:32:09 24.07.2009)(additions chm -headless -sdk -vboxwebsrv)
     Homepage:            http://www.virtualbox.org/
     Description:         Family of powerful x86 virtualization products for enterprise as well as home use

[U] app-emulation/virtualbox-modules
     Available versions:  1.6.6 1.6.6-r1 (~)3.0.4 {kernel_linux}
     Installed versions:  3.0.2(19:30:22 24.07.2009)(kernel_linux)
     Homepage:            http://www.virtualbox.org/
     Description:         Kernel Modules for Virtualbox


GUESTS:

web1 EXCHANGE # eix virtualbox
[I] app-emulation/virtualbox-guest-additions
     Available versions:  1.6.6 (~)1.6.6-r1 (~)2.1.4 (~)2.2.0 (~)2.2.2 (~)2.2.4 (~)3.0.2 {X}
     Installed versions:  3.0.2(03:03:35 23.07.2009)(kernel_linux -X)
     Homepage:            http://www.virtualbox.org/
     Description:         VirtualBox kernel modules and user-space tools for Linux guests

Is this a known problem , since in virtualbox's change-logs I could not find any fixes ?!
Also when searching internet and your bug-reports I could'nt find a similar issue ?!

"	rottex
16627	Create a VM in a non-default directory	all	VirtualBox 5.1.18	2017-03-31T03:35:59Z	2017-05-23T00:11:22Z	2017-05-23T00:11:22Z	"When creating a VM (using the VirtualBox GUI), it should be possible to override the ''default machine folder''.

This would make it easier to put different VMs in different places.  As it is, one's only recourse is to either change the preference setting first, create the VM, then set it back afterward; or to create the VM where it isn't wanted, and then move it using the remove/move/re-add sequence.  Both of these options are annoying.

Suggested UI: add a ""folder"" button next to ''Name'' input field in the dialog (or the first page of same in guided mode), like the one that already appears next to the virtual-disk ''File Location'' input field."	Eric Siegerman
19272	crashes very much when i right click in winscp	Windows	VirtualBox 6.1.2	2020-01-28T11:36:57Z	2020-03-02T16:17:39Z	2020-03-02T16:17:39Z	"Peace, Host mint Mate 19.3, guest win 10 (1909) with high contrast theme
file:///home/zouhairy/VirtualBox%20VMs/Win/Logs/VBox.log
"	majed17
16133	Crashes if GUI used with a screen reader	Linux	VirtualBox 5.1.8	2016-11-01T21:25:38Z	2016-11-01T21:25:38Z	2016-11-01T21:25:38Z	"Hi,

On a Debian testing with upstream repo's package:
1. Install qt-at-spi
2. Enable accessibility in the Desktop.
3. Run VirtualBox.
4. Arrow keys, opening dialogs, crash the graphical interface.
5. Run without Orca running.
6. Arrow keys work. Run again screen reader, it crashes as soon as you press an arrow key.

VBoxManage works, VMs as well, but GUI is unusable.

Best regards"	texou
14077	Crash with RDR_FILE_SYSTEM in Windows 7	Windows	VirtualBox 4.3.26	2015-04-25T14:49:25Z	2015-05-10T07:46:01Z	2015-05-10T07:46:01Z	"I already read:

* https://www.virtualbox.org/ticket/57
* https://www.virtualbox.org/ticket/1683
* https://www.virtualbox.org/ticket/991

and all those tickets were created 7 years ago or even sooner, they are all closed as FIXED, and yet, for 2-3 months I see my guest Windows 7 crashes with RDR_FILE_SYSTEM constantly. The uptime can be around 2-3 days max.

I saw this with 4.3.22, after upgrade to 4.3.26 I still see this crash.

Host: openSUSE 13.2 64-bit, Windows 7 64-bit, using shared folders which are mapped as network drive in guest. Activity in guest: Visual Studio, Free Commander, Notepad++, Cygwin. Crashes occurs during user activity (for example when I am saving a file) or on idle (during night for example)."	thxOracle
14992	Crash Windows 7 / RAW FILE CONVERTER EX powered by SILKYPIX	Windows	VirtualBox 5.0.12	2015-12-30T16:13:06Z	2015-12-30T16:13:06Z	2015-12-30T16:13:06Z	"When I try to start the program RAW FILE CONVERTER EX powered by SILKYPIX (which is Fuji-supplied raw photo conversion software) Virtualbox crashes out on me. This used to work a couple of months/versions ago (maybe a regression in 5.x?)

I tried disabling 3D both in the guest additions install and the Virtualbox config and I got a blue-screen (unfortunately the VBox.png is corrupt and did not capture the bluescreen)"	Andrew Basterfield
20028	Crash when restoring Fedora virtual machine from a Snapshot	Linux	VirtualBox 6.1.14	2020-11-09T16:45:26Z	2020-11-09T16:45:26Z	2020-11-09T16:45:26Z	"Shortly after restoring from snapshot with virtualbox 6.1.14, the Fedora VM locked up, and a few interesting things happened after I ended the process (the only way to close it as it was totally unresponsive):


The HDD with the OS on became detached.
Virtualbox refused to re-attach the HDD without dropping the saved state (shown in screenshot)
Upon re-attaching the HDD after dropping my saved state, the HDD state had not been restored to the state it was in when I took the snapshot (it was as if I hadn't tried to restore the snapshot).

Attached is the Vbox.log file, and a screenshot of the error I was given as mentioned above.

Please let me know if there's anything I can do to help further debug this. I want to note that VirtualBox 6.1.16 seems generally much more stable than 6.1.14, but I thought the information in this report might still be useful."	Hamish McIntyre-Bhatty
20126	Crash when removing  vms from command line	all	VirtualBox 6.1.16	2021-01-13T11:32:19Z	2021-01-13T11:32:19Z	2021-01-13T11:32:19Z	"When removing a VM from the command line, Virtualbox often crashes with a critical error when *other* VMs are running. The dialog says for those running (one for each window): ""A critical error has occurred while running the virtual machine and the machine execution should be stopped. [...] Press OK to power off the machine.""

The command executed is
$ vboxmanage unregistervm ""${childvm}"" --delete
where the variable ""childvm"" is a valid name of a VM.

The given log is:
--- start of log ---
Log created: 2021-01-13T10:42:27.425692000Z
Process ID:  3619370 (0x373a2a)
Parent PID:  12731 (0x31bb)
Executable:  /usr/lib/virtualbox/VBoxSVC
Arg[0]: /usr/lib/virtualbox/VBoxSVC
Arg[1]: --auto-shutdown
AddRef: illegal refcnt=3221225469 state=2
--- end of log ---

During the crash ""Oracle VM VirtualBox Manager"" always says data is unavailable. Sometimes the manager refreshes the data itself, other times you need to restart the manager.

"	Mrpn
17072	crash when reloading vm settings while editing USB filter	Windows	VirtualBox 5.1.26	2017-09-11T09:03:52Z	2017-09-11T09:03:52Z	2017-09-11T09:03:52Z	"VirtualBox crashes when editing a newly added but not-yet-saved USB filter, if the vm's settings got reloaded in the mean time. This is with virtualbox-5.1 (5.1.26-117224~Ubuntu~xenial) on Ubuntu 16.04.

I could reproduce it with these steps:
- start guest (Windows 7 in my case)
- open USB settings for that VM
- add new USB device filter
- edit the new USB device filter
- while edit window is open, resize VM window
- vbox asks whether to reload settings because they changed while being edited
- yes, reload
- newly added filter disappears, but edit window is still open
- keep editing in edit window
- close edit window with ok
- crash, VM aborted:
[  732.398256] VirtualBox[3393]: segfault at 2 ip 00007f160d12e773 sp 00007ffe48efbb58 error 4 in VirtualBox.so[7f160d028000+9b7000]

I didn't test with other hosts/guests, but it may not be specific to my setup."	daniel.klauer
18983	Crash Virtualbox guest bcause of segfalut of libc	Windows	VirtualBox 6.0.12	2019-10-04T23:24:00Z	2019-10-06T18:51:23Z	2019-10-06T18:51:23Z	"Guest Windows10 is crashed suddenly when it is happen segfalut on Debian9 host.

Debian9 syslog is recorded with below messages.
It is seemed that this crash is associated with VBoxDrvLinuxIOCtl control.

{{{
Oct  5 07:45:53 svyomo2 kernel: [172631.378421] EMT-5[6163]: segfault at 7f7cf160ffa0 ip 00007f7d361d80b4 sp 00007f7cf170e918 error 4 in libc-2.24.so[7f7d360af000+195000]
Oct  5 07:45:53 svyomo2 kernel: [172631.378430] Code: 0e 88 0f c3 c5 fa 6f 06 c5 fa 6f 4c 16 f0 c5 fa 7f 07 c5 fa 7f 4c 17 f0 c3 48 8b 4c 16 f8 48 8b 36 48 89 4c 17 f8 48 89 37 c3 <8b> 4c 16 fc 8b 36 89 4c 17 fc 89 37 c3 0f b7 4c 16 fe 0f b7 36 66
Oct  5 07:45:53 svyomo2 kernel: [172631.378561] VBoxDrvLinuxIOCtl: copy_to_user(0x7f7cc00f28e0,,0x18); uCmd=0xc0305698!
Oct  5 07:45:53 svyomo2 kernel: [172631.378636] VBoxDrvLinuxIOCtl: copy_to_user(0x7f7cc10dce10,,0x18); uCmd=0xc0305698!
Oct  5 07:45:56 svyomo2 kernel: [172634.716100] device enxcce1d50dc8db left promiscuous mode
Oct  5 07:45:56 svyomo2 kernel: [172634.740027] vboxnetflt: 0 out of 332085879 packets were not sent (directed to host)
Oct  5 07:46:52 svyomo2 kernel: [172690.335485] vboxdrv: 0000000013086699 VMMR0.r0
Oct  5 07:46:52 svyomo2 kernel: [172690.818663] vboxdrv: 00000000f3fc2f31 VBoxDDR0.r0
Oct  5 07:46:52 svyomo2 kernel: [172691.049999] VBoxNetFlt: attached to 'enxcce1d50dc8db' / cc:e1:d5:0d:c8:db
Oct  5 07:46:53 svyomo2 kernel: [172691.509566] device enxcce1d50dc8db entered promiscuous mode
Oct  5 07:46:53 svyomo2 kernel: [172691.556485] vboxdrv: 0000000094df3d3b VBoxEhciR0.r0
}}}
"	Yomo
20968	Crash virtualbox guest	Windows	VirtualBox 6.1.32	2022-06-06T15:47:17Z	2022-06-06T15:47:17Z	2022-06-06T15:47:17Z	"I have a crash on virtualbox ""AVORTED""[[BR]]
Thank.[[BR]]

 "	Sizy458
20114	Crash on guest VM	Windows	VirtualBox 6.1.14	2021-01-01T13:31:41Z	2021-01-01T13:40:31Z	2021-01-01T13:40:31Z	"I have a crash VM[[BR]]
Please solve bug ![[BR]]
I have installed microsoft net framework 4.0.[[BR]]
Guest : Windows XP[[BR]]


Thank
"	Sizy458
18441	Crash host	Windows	VirtualBox 6.0.4	2019-02-17T19:08:48Z	2019-02-17T19:11:30Z	2019-02-17T19:11:30Z	"I have developpe dopengl windows application[[BR]]

i have sended corrupt data in glDrawArrays without doing it on purpose ,
and i my machine guest and host freeze."	Sizy458
18346	Crash after reboot Windows 10 guest	Windows	VirtualBox 6.0.2	2019-01-22T11:13:04Z	2019-01-22T11:13:04Z	2019-01-22T11:13:04Z	"Hi,

I rebooted a Windows 10 guest because a shared folder was showing up twice (I have reported this issue in the Windows Guest forum) but it crashed. After powering down the guest it boots normally.
Host OS is ubuntu version 18.04.1, Virtualbox version is 6.02, guest OS is a new install of Windows 10 1803 with the 6.02 guest additions. 
I have attached the logs for review.

Regards,
Gijsbert
"	gwiesenekker
15925	Crackling sound with Windows 10 anniversary update	Windows	VirtualBox 5.1.6	2016-09-13T13:29:11Z	2022-03-23T19:55:58Z	2022-03-23T19:55:58Z	"Since latest Windows 10 update (""anniversary update"") on my guest VM, sound is very crackling.

This seems to be pretty common with people having updated their Windows 10 guest: https://forums.virtualbox.org/viewtopic.php?f=7&t=79129

I was using VirtualBox 5.0.26, I've update to VirtualBox 5.1.6 with no change.

I'm using Linux host (Fedora), but in the forum thread, one user was using Windows host."	olem
14057	CPU spikes when concurrently using an XP VM and its complete clone on Debian	Windows	VirtualBox 4.3.26	2015-04-18T11:11:53Z	2015-04-18T11:11:53Z	2015-04-18T11:11:53Z	"Host Linux sandy 3.2.0-4-amd64 #1 SMP Debian 3.2.65-1+deb7u2 x86_64 GNU/Linux
Virtualbox 4.3.26-98988 (happened also with 4.2.28-97679)

I have an XP virtual machine with a test installation of oracle rdbms. To do some speed optimizations on some plsql code and compare results, I cloned it (complete) and changed name, mac and ip.

When one vm is running and idling and I launch the other one, both the machines go to 200% cpu consumption (quad core host). After a (long) while the second machine boot completes, and they both go back to idling.

When I log in on the second vm, the first starts spinning again. After a while the login is completed and both go back to idle.

Whatever I try to do on one of the two, the other one immediately starts using all the available cpu, 50/50 with the first one.

Both the original vm and the clone run perfectly on their own, if the other one is shut down or even paused. If I run another unrelated XP guest with one of the two, the issue does not appear.

I'm using vboxheadless and connecting with Remote Display, but this can be triggered also when not connected to the desktop, e.g. launching a plsql cpu consuming loop via sqldeveloper (not i/o bound operations).

Typical output of top when the issue is occurring

top - 12:59:39 up 7 days, 15:02,  1 user,  load average: 3,34, 5,32, 5,05
Tasks: 192 total,   2 running, 190 sleeping,   0 stopped,   0 zombie
%Cpu(s):  1,5 us, 98,4 sy,  0,0 ni,  0,1 id,  0,0 wa,  0,0 hi,  0,0 si,  0,0 st
KiB Mem:  12280376 total, 12063944 used,   216432 free,    68776 buffers
KiB Swap:  7771064 total,        0 used,  7771064 free,  2834160 cache

  PID USER      PR  NI  VIRT  RES  SHR S  %CPU %MEM    TIME+  COMMAND
14613 vbox      20   0 4003m 3,6g 3,6g S 198,0 30,9  36:11.00 VBoxHeadless                
 9930 vbox      20   0 3981m 3,6g 3,6g S 196,0 30,9  40:37.10 VBoxHeadless

"	ctrl
15775	Could not read from the boot medium. System halted	other	VirtualBox 5.0.10	2016-08-10T05:55:35Z	2016-09-02T07:28:15Z	2016-09-02T07:28:15Z	"In virtualbox version 4.2 and 4.3 when we tried to boot the payloads from network, The DHCP server used to continuosly search for ip whereas in vbox 5.0 it search for ip only once and then timeout occurs and it proceeds to boot from medium. 

Thanks in advance."	bhanu
16329	Corruption when accessing files via Shared Folders	Linux	VirtualBox 5.1.12	2016-12-26T01:20:30Z	2016-12-28T19:36:57Z	2016-12-28T19:36:57Z	"I am seeing intermittent file corruption when checking a borgbackup repository via a Shared Folder

Host is Ubuntu x64 16.04 using Virtualbox 5.1.12
Guest is Ubuntu Mint x64 16.10

Here is the output of 5 sequential runs of the same command to verify the repository, you can see that some detect errors and others don't.  The errors that are detected are different between runs as well.


{{{
jlmcgraw@mate1604:~$ borgbackup check /media/sf_Shared_Folder/borg_vm_backups/
Segment entry checksum mismatch [segment 273, offset 8]
Index object count mismatch. 117954 != 117952
Completed repository check, errors found.

jlmcgraw@mate1604:~$ borgbackup check /media/sf_Shared_Folder/borg_vm_backups/
Enter passphrase for key /media/sf_Shared_Folder/borg_vm_backups: 

jlmcgraw@mate1604:~$ borgbackup check /media/sf_Shared_Folder/borg_vm_backups/
Enter passphrase for key /media/sf_Shared_Folder/borg_vm_backups: 

jlmcgraw@mate1604:~$ borgbackup check /media/sf_Shared_Folder/borg_vm_backups/
Segment entry checksum mismatch [segment 155, offset 2726665]
Index object count mismatch. 117954 != 117951
Completed repository check, errors found.

jlmcgraw@mate1604:~$ borgbackup check /media/sf_Shared_Folder/borg_vm_backups/
Enter passphrase for key /media/sf_Shared_Folder/borg_vm_backup
}}}


I'm unable to recreate the errors when checking the repository from the host machine.

I've also noticed occasional errors in files hosted on the shared folder in other applications as well.  E.g. unzipping a file, errors about duplicity archive errors etc etc so the problem isn't just limited to borg

I will run memory diagnostics again tonight just to be sure, I've run them before and found no errors.

"	jlm
21212	Copying URL from guest to host causes the VM to crash (SharedClipboard)	Windows	VirtualBox-7.0.2	2022-10-28T16:16:20Z	2023-02-05T12:13:10Z	2023-02-05T12:13:10Z	"Host OS: Fedora Linux 36 x64 X11 (Xorg) kernel 5.19.16
Guest OS: Windows XP Professional x86 (with Microsoft Premier Extended Support Updates 'till July 2019)
Bug: Copying URL from guest to host causes the VM to crash

Bug Description:
When Shared Clipboard is enabled, it's possible to copy text from guest to host and vice versa, however when ""particular"" things like URL and other particularly formatted texts are copied (like from Chrome etc) those fail to be converted properly and therefore cannot be pasted to the host. On top of that, this might lead the guest to crash, which of course is bad.

To highlight the relevant portion of the logs, I'd say that this should give a pretty good insight:


{{{
08:37:22.815753 Shared Clipboard: Signalling host about guest clipboard data failed with VERR_NOT_FOUND
08:37:22.816014 Shared Clipboard: Signalling host about guest clipboard data failed with VERR_NOT_FOUND
08:37:22.816241 Shared Clipboard: Signalling host about guest clipboard data failed with VERR_NOT_FOUND
08:37:22.816442 Shared Clipboard: Signalling host about guest clipboard data failed with VERR_NOT_FOUND
08:37:22.816727 Shared Clipboard: Signalling host about guest clipboard data failed with VERR_NOT_FOUND
08:37:22.816894 Shared Clipboard: Signalling host about guest clipboard data failed with VERR_NOT_FOUND
08:37:52.813496 Shared Clipboard: Requesting data in format 0x1 for X11 host failed with VERR_TIMEOUT
08:37:52.813528 Shared Clipboard: Converting VBox formats 'UNICODETEXT' to 'UTF8_STRING' for X11 (idxFmtX11=1, fmtX11=3, atomTarget='UTF8_STRING') failed, rc=VERR_TIMEOUT
08:38:22.814024 Shared Clipboard: Error reading host clipboard data from X11, rc=VERR_TIMEOUT
08:38:22.814071 Shared Clipboard: Reading host clipboard data failed with VERR_TIMEOUT
08:38:22.814101 Shared Clipboard: Requesting data in format 0x1 for X11 host failed with VERR_TIMEOUT
08:38:22.814156 Shared Clipboard: Converting VBox formats 'UNICODETEXT' to 'UTF8_STRING' for X11 (idxFmtX11=1, fmtX11=3, atomTarget='UTF8_STRING') failed, rc=VERR_TIMEOUT
08:38:22.814179 Shared Clipboard: Converting X11 format 'UTF8_STRING' (idxFmtX11=1) to VBox format 0x1 failed, rc=VERR_NO_DATA
}}}

To put this into context, I was trying to copy the following URL from Chrome Canary via an RDP session from a Windows XP VM:

"	FranceBB
14842	Converting OVA-deployed machine to EFI gives Error: No mapping found.	Linux	VirtualBox 5.0.10	2015-11-18T14:10:02Z	2021-03-19T19:54:16Z	2021-03-19T19:54:16Z	"I'm generating OVA template which is intended to be tested for BIOS and UEFI boot capabilities. There is no problem with regular workflow, deploy machine, turn it on and continue with BIOS boot. But once I've turned on ""Enable EFI"" options in deployed machine settings I've got error from UEFI interactive shell - Error: No mapping found. It seems VirtualBox doesn't generate UEFI default boot entries for OVA-deployed instance. Could it be fixed?"	Roman Valov
14290	Content of the hosts video memory is shown	Windows	VirtualBox 5.0.0	2015-07-17T07:38:31Z	2016-02-24T03:39:57Z	2016-02-24T03:39:57Z	"For example if I'm opening an application on the guest system that seems to take advantage of 3D acceleration (in this case ""XPS-Viewer EP"" on Windows XP) I'm seeing content from the memory of the graphics card (for example textures from a game that I have played on the host system before).

Additionally to this issue that I'm seeing content of the graphics card instead of the document this behavior could leak unwanted data to the guest system. Maybe VirtualBox could allocate and zeroing the amount of video memory that is configured for the guest system before it starts to avoid that the guest system can read anything at any time from the host system (the same applies for the system memory if not already done)."	Sworddragon
14368	Connecting Kemper Profiling Amplifier To VM Aborts the VM	Linux	VirtualBox 5.0.0	2015-08-02T03:57:21Z	2015-09-21T15:11:23Z	2015-09-21T15:11:23Z	"Connecting Kemper Profiling Amplifier (KPA) [http://www.kemper-amps.com/] via USB to a virtual machine aborts the VM.

I have tried with both Linux and Windows guests. No problems when connecting KPA to Linux or Windows machine directly.

Nothing is written to VBox.log when KPA is connected to VM. The VM just shuts down and the state in VirtualBox GUI becomes ""Aborted"".

In the attached VBox.log you can see bootup of Kubuntu 14.04 VM. After the VM had booted up, I connected KPA to it (nothing written to VBox.log at this point).

In the lsusb-kpa.txt you can see the output of command lsusb -v -d 133e:0001"	Janne Rönkkö
17747	Confilct between Virtualbox 5.12.10 r122088 and compiz ubuntu 18.04	Windows	VirtualBox 5.2.10	2018-05-09T17:42:01Z	2018-05-24T12:53:34Z	2018-05-24T12:53:34Z	"Hello !
 This ticket for report a bug between Oracle Virtual box 5.12.10 on Ubuntu 18.04 and Compiz tools !
When Ubuntu 18.04 is set on compiz management, the task bar setting in top of the screen in a virtual machine doesn't appear ! When setting in Marco appearance, it's work fine and task bar appear in the right position in the top of the screen ! For information, this trouble doesn't appear in VMware machines with compiz setting !
Here details of the configuration :
Ubuntu 18.04
Virtual Box 5.12.10 r122088
Virtual machine with Windows XP SP3 !"	Papusone
11333	configure script rejects --prefix	other	VirtualBox 4.2.6	2012-12-26T07:05:03Z	2013-02-05T12:01:26Z	2013-02-05T12:01:26Z	"as far as i can see, there is no way to teach vbox' configure script the used prefix.

sabotage linux uses """" (empty, i.e. ""/"") as prefix. there is no /usr."	John.Spencer
21321	Compiling the kernel-modules fails with error: ‘VMX_BF_EPT_PT_0_MASK’ undeclared	all	VirtualBox-7.0.4	2022-11-30T11:30:21Z	2022-12-01T19:08:04Z	2022-12-01T19:08:04Z	"The compilation fails with:

vboxdrv/include/VBox/vmm/hm_vmx.h:532:29: error: ‘VMX_BF_EPT_PT_0_MASK’ undeclared here (not in a function); did you mean ‘VMX_BF_EPT_PT_READ_MASK’?
  532 | RT_BF_ASSERT_COMPILE_CHECKS(VMX_BF_EPT_PT_, UINT64_C(0), UINT64_MAX,

The line in hm_vmx.h which is causing this:

RT_BF_ASSERT_COMPILE_CHECKS(VMX_BF_EPT_PT_, UINT64_C(0), UINT64_MAX,
                            (READ, WRITE, EXECUTE, MEMTYPE, IGNORE_PAT, IGN_7, ACCESSED, DIRTY, EXECUTE_USER, IGN_59_11,
                            SUPER_SHW_STACK, IGN_62_61, SUPPRESS_VE));

The cause is that the C preprocessor is replacing READ with '0' (and WRITE with '1') due to the linux kernel header file: tools/virtio/linux/kernel.h

which has (line 29):
/* generic data direction definitions */
#define READ                    0
#define WRITE                   1

I would say this is an unintended side effect and a small rename of the variables in hm_vmx.h would fix this

Apparently a workaround (https://bugs.gentoo.org/880229) is to set the Linux kernel config option CONFIG_JUMP_LABEL but I did not test this yet"	gentoo-bird
8982	CoDeSys on windows xp work with time delays	Windows	VirtualBox 4.0.8	2011-05-28T16:37:12Z	2011-05-28T16:37:12Z	2011-05-28T16:37:12Z	"I´am using CoDeSys(a SoftSPS)on windows xp.
The guest get delays from 2sec up to 10 sec when I switch between CoDeSys and envince(pdf-viewer) until the switch finished which make working time expensive.
There are also delays between the call of the functions/views within CoDeSys.
Also the whole guest seems to be slowed down when I call services/widgets/programms.

It could not be my host: There is enough RAM and one core is free for maintain the windows guest.

3D support is enabled.

For getting the program(not a one stop shop):
http://www.3s-software.com/index.shtml?de_contact"	maninred2
18446	Code NS_ERROR_FACTORY_NOT_REGISTERED (0x80040154) - Class not registered (extended info not available)	Linux	VirtualBox 6.0.4	2019-02-22T03:34:40Z	2019-02-22T09:28:11Z	2019-02-22T09:28:11Z	"Hi,

I have linux laptop with with ubuntu 18.04 OS.

$lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.2 LTS
Release:	18.04
Codename:	bionic


I have virtualBox 6 installed in it. Below is the VBox details -

          Version 6.0.4 r128413 (Qt5.9.5)
          Copyright © 2019 Oracle Corporation and/or its affiliates. All rights reserved.

I have minidcos installed and tried to create virtual machine https://minidcos.readthedocs.io/en/latest/dcos-vagrant-cli.html# .

When I run the command `minidcos vagrant create ./dcos_generate_config.sh --agents 0` I get below error.

Code NS_ERROR_FACTORY_NOT_REGISTERED (0x80040154) - Class not registered (extended info not available)

I have below permissions for my `/tmp` folder.

ajkumar@rajkumar:Downloads$sudo ls -ld /tmp
[sudo] password for rajkumar: 
drwxrwxrwx 9 root root 4096 Feb 21 21:14 /tmp
rajkumar@rajkumar:Downloads$ls -ld /tmp
drwxrwxrwx 9 root root 4096 Feb 21 21:14 /tmp






"	rajpsgit
13079	clonevm makes immutable hard disks normal in clone	Linux	VirtualBox 4.3.12	2014-05-31T12:22:05Z	2014-05-31T12:22:05Z	2014-05-31T12:22:05Z	"When cloning a VM, '''ALL''' the cloned new VM's hard disks are of type '''normal''' whereas some of the source VM's hard disks are of type '''immutable'''.  Cloning is not preserving hard disk type and is resetting immutable hard disks to normal.

Both host and guest are Ubuntu Trusty Server."	Senthil Nathan
13765	clonevm faster: make use of --reflink	all	VirtualBox 4.3.20	2015-01-16T12:43:06Z	2015-01-16T12:43:06Z	2015-01-16T12:43:06Z	"I'm running vbox machines off a btrfs partition with CoW. When combined with bcache (SSD-backed cache) the fragmentation penalty of fragmented images doesn't hurt much - i.e. I get adequate perfomance of 3-8 VMs on my Lenovo T540p notebook. 

When I clone the vm (separate copy), virtualbox does a full copy of the image - taking considerable time (4 hours for 100GB image) and space. I suggest to utilize the ""cp --reflink=auto"" instead. The copy is made instantly (if possible and falls back to traditional copy) and no additional space is taken until there are changed blocks in the image file.  "	rugubara
9964	cloned(full) openSUSE12.1 is not able to find it´s harddrive	Linux	VirtualBox 4.1.6	2011-11-28T16:49:27Z	2011-11-28T16:56:50Z	2011-11-28T16:56:50Z	"I´ve made two clones of a working openSUSE12.1 64bit vm(on a openSUSE12.1 64 bit host).

Both have problems to start up correctly.

They tell me that they have problems to find their harddrive and give me an option to make a fallback to a other drive as far as I could see.

It´snot important what I choose then, both failed.

I attach a screenshot for the exact error message and the logs."	maninred2
18357	Clone fails because newly created vdi is attached to clone it just made.	Windows	VirtualBox 6.0.2	2019-01-24T11:59:38Z	2019-01-24T11:59:38Z	2019-01-24T11:59:38Z	"Failed to clone the virtual machine Windows 10 MAIN (64 Bit) Fresh SSD.

Medium '/home/mark/VirtualBox VMs/Windows 10 MAIN (64 Bit) Fresh SSD Clone1/Windows 10 MAIN (64 Bit) Fresh SSD Clone1.vdi' '''cannot be closed because it is still attached to 1 virtual machines.'''

Result Code: VBOX_E_OBJECT_IN_USE (0x80BB000C)
Component: MediumWrap
Interface: IMedium {ad47ad09-787b-44ab-b343-a082a3f2dfb1}
----------------------------

Repeatable. Ubuntu 18.04.1 host

"	BFG
19654	Clipboard sharing suddenly stops working in reccent release	all	VirtualBox 6.1.10	2020-06-10T19:17:26Z	2020-06-10T19:17:26Z	2020-06-10T19:17:26Z	"VB 6.1.10 r138449 the host is Ubuntu 18.04.04. Shared clipboard periodically stops working on guests after many hours of working. There is no new lines in the virtual machine log file after the event. If two guests are running it may stop working only for one of them and still works fine on another one. I've observed this on different guests Win10, Linux, WinXP, so this is probably a bug on the host side. Interestingly restart of the guests brings feature back into operational state. 

It seams you are changing the code of the shared clipboard infrastructure due to multiple crash reports #19226 and I would say that the most stable release so far was VB 6.1.8. It didn't crash on copy&paste (not as often as previous releases) and the shared clipboard is again broken in the current VB 6.1.10."	GnomeUser
19653	Clipboard sharing suddenly stops working in reccent release	all	VirtualBox 6.1.10	2020-06-10T19:17:19Z	2020-06-10T19:17:19Z	2020-06-10T19:17:19Z	"VB 6.1.10 r138449 the host is Ubuntu 18.04.04. Shared clipboard periodically stops working on guests after many hours of working. There is no new lines in the virtual machine log file after the event. If two guests are running it may stop working only for one of them and still works fine on another one. I've observed this on different guests Win10, Linux, WinXP, so this is probably a bug on the host side. Interestingly restart of the guests brings feature back into operational state. 

It seams you are changing the code of the shared clipboard infrastructure due to multiple crash reports #19226 and I would say that the most stable release so far was VB 6.1.8. It didn't crash on copy&paste (not as often as previous releases) and the shared clipboard is again broken in the current VB 6.1.10."	GnomeUser
17421	Clipboard sharing stops working after large copying on guest	Windows	VirtualBox 5.2.4	2018-01-05T06:43:59Z	2018-01-05T07:59:44Z	2018-01-05T07:59:44Z	When copying an image which is large (tested larger 2MB), the clipboard sharing stops working completely.	amosb
8141	Clipboard sharing between 3 machines / security issue?	Windows	VirtualBox 4.0.2	2011-01-21T12:26:03Z	2011-03-01T16:04:51Z	2011-03-01T16:04:51Z	"I've recently run into a scenario that is a bit troubling. I have two desktop Ubuntu Lucid machines, let's call them D1 and D2, and two users working on them, U1 on D1 and U2 on D2. U1 has VirtualBox running a Windows VM (V1) with D1 as a host. User U2 has a RDP connection opened to V1. 

The users U1 and U2, however, have different TS sessions on the Windows machine. So U1 sees his Windows desktop in the VirtualBox window on his desktop D1, and U2 sees his Windows desktop in the rdesktop window on his desktop D2. The Windows VM runs two user sessions concurrently.

Every once in a while, when U2 copies something in the clipboard on his desktop session on D2, user U1 is able to paste the same thing on his desktop session on D1.

I believe the reason for this is because there is clipboard sharing between D1 and V1 via VirtualBox, and also between V1 and D2 via RDP. So in fact, the clipboard somehow becomes shared by all 3 machines.

This does not seem to occur when running the VM in headless mode, and both users connecting to it via RDP, which indicates that the problem is more likely in the way VirtualBox manages clipboard sharing rather than rdesktop / RDP.

"	Adrian Roman
20909	Clipboard exchange between Devua host and Windows guest stopped working	Windows	VirtualBox 6.1.32	2022-04-22T23:22:44Z	2022-06-21T14:56:39Z	2022-06-21T14:56:39Z	"For unknown reasons, the exchange of data via '''clipboard''' stopped working some time ago.

The host is (uname -a):  
''Linux Archimedes 5.17.0-1-amd64 #1 SMP PREEMPT Debian 5.17.3-1 (2022-04-18) x86_64 GNU/Linux''

The guest is (MS Windows 10):  
''Windows 10 pro 64bit''

"	Joerg Schiermeier
19445	Clipboard broken	other	VirtualBox 6.1.4	2020-03-29T18:11:09Z	2020-03-30T07:56:51Z	2020-03-30T07:56:51Z	"I have tried several combinations of
  Fedora Linux 26 and 31 (64-bit)
  Virtual Box 5.2.8, 6.1.2, and 6.1.4
  Virtual Box extensions (same versions as VBox)
  VBoxGuestAdditions 5.2.8, 6.1.2, 6.1.4 for ecs (OS/2)
all running on Intel x86/x64 hardware
all running the same ecs virtual machine (except for Guest Additions)

Fedora 26 and VBox 5.2.8 with any of those
versions of GuestAdditions: clipboard works fine

Fedora 31 with either VBox 6.1.2 or 6.1.4
and any of those GuestAdditions: clipboard
fails both within ecs and between ecs and Linux.
"	FuzzyFred
20375	Clipboard and drag&drop doesn't work bidirectionally (VB 6.1.22/Guest additions 6.1.22_Host: Ubuntu 20.04 / Guest: Win 8.1)	Windows	VirtualBox 6.1.22	2021-05-23T16:16:07Z	2021-05-23T16:16:07Z	2021-05-23T16:16:07Z	"Clipboard and drag&drop doesn't work properly bidirectionally

VB 6.1.22
Guest additions installed 6.1.22 (tried to downgrade to 6.1.18 with same results)
Host: Ubuntu 20.04
Guest: Win 8.1

Done tests from file manager on both sides:

Drag&Drop from guest to host (file): OK
Drag&Drop from host to guest (file): nothing happens

Copy&Paste from guest to host (file): OK
Copy&Paste from host to guest (file): nothing happens

Copy&Paste from guest to host (text): OK
Copy&Paste from host to guest (text): OK


Done test with a program (Host: WPS Docs / Guest: Word 2013):

Drag&Drop from guest to host (image): nothing happens
Drag&Drop from host to guest (image): nothing happens

Copy&Paste from guest to host (image): OK
Copy&Paste from host to guest (image): OK

PrintScreen from guest to host: OK
PrintScreen from host to guest: nothing happens

Hope the issue is clear enough to understand.
"	cimarron
16787	Clipboard actions interference [Host:Debian 9 Stretch RC03][Guests: Win7Ultimate, Debian 8.8 Jessie]	all	VirtualBox 5.1.22	2017-05-26T05:50:31Z	2017-05-26T06:21:04Z	2017-05-26T06:21:04Z	"VirtualBox Graphical User Interface
VirtualBox version 5.1.22 r115126 (Qt5.7.1)

Prerequisites:

(P0) HOST: NVIDIA, Wacom drivers, 3 monitors total, Xorg under xfce4, Clipman for clipboard monitoring (Debian 9 Stretch RC03)
(P1) Each guest has installed the corresponding ""Guest Additions"";
(P2) Each guest has bidirectional clipboard sharing enabled;
(P3) Windows 7 Ultimate guest has the ""seamless mode"" enabled (thanks guys, this is awesome)
(P4) After launching Win 7 Ultimate guest, xfce4-screenshooter can no longer catch screenshots and move it to clipboard; the copy-paste operations are still nominal;
(P5) With both Win 7 Ultimate and Debian 8.8 Jessie guests clipboard operations within the HOST (within the guests this phenomena has not been confirmed) are being interfered the following way:

(01) Any and every mouse/Wacom Pen selection renders as copying to clipboard, before even the Ctrl+C is pressed; that means any selection automatically puts the selected text into the Host's clipboard, from within any and every application of the Host (Chrome, Chromium, Opera, Libre Office Calc, Libre Office Writer, Notes, Thunar, Terminal, and whatnot)

(02) After reboot both xfce4-screenshooter and clipboard operations work fine PRIOR to launching the VirtualBox

"	al64128
16128	Client loses TCP/UDP connectivity, VirtualBox on host uses 100% CPU	Linux	VirtualBox 5.1.8	2016-10-30T08:24:52Z	2016-11-24T08:00:57Z	2016-11-24T08:00:57Z	"I have a guest debian server running on ubuntu host (both 64 bits). Networking mode was set to NAT and port forwarding was set for guest ports 22 and 80 to control and use this server.

It worked fine during low-load testing, but when it come to production with some load (1-2 requests per seconds from around the world), following issue was discovered:

- It's happening after some time, usually after 2-3 days but last time it happens after 7 hours only.
- CPU usage of VBoxHeadless process on host jumps and stay at 100%, although there is no any load on the guest.
- Guest system continues to work but it cannot nor accept nor create new TCP connections (existing TCP connections, e.g. early opened ssh session, continues to work).
- Outgoing TCP connection from the guest (e.g. wget) fails with error code ""Network is unreachable"". This error code is a clear sign that ""bad thing happened"".
- DNS resolving on guest fails so it seems that UDP is affected too.
- PINGs from guest are working! So I consider that network, routing, etc is OK, and the bug is in NAT code.

Of course there are no any messages in any logs when it happens.

I think that symptoms are quite similar to Bug #15223, but don't know could they have common reason or not. First discovering this issue in 4.3.old, I've upgraded to 4.3.40 and then to 5.1.8, but the issue is still here.

"	Roman Trunov
20302	Client ID prevails over MAC based mapping with the NAT Network DHCP server	Linux	VirtualBox 6.1.18	2021-04-13T09:35:05Z	2021-04-22T14:00:30Z	2021-04-22T14:00:30Z	"I've got two Ubuntu (though what matters here is Systemd-Network) guest VMs connected to a NAT Service network with the DHCP service enabled.
I have added a static mapping between the guests NIC MAC addresses and their assigned IPs. The NatNetwork-Dhcpd.config file shows what I mean:

    <Config MACAddress=""08:00:27:00:00:01"" name=""59c98231-ac44-4e62-8bfe-1bd937c3fff1/0"" fixedAddress=""192.168.40.101""/>

    <Config MACAddress=""08:00:27:00:00:02"" name=""824e3a1b-2542-454d-bfee-c8aad2ad1c90/0"" fixedAddress=""192.168.40.102""/>

The same information is reflected in `VirtualBox.xml` (the global config file) though when using `VBoxManage` to set up the mapping I did use the first NIC of each guest to set the mapping hence the `/0` after the guest VM UUID:


    <Config MACAddress=""08:00:27:00:00:01"" name=""59c98231-ac44-4e62-8bfe-1bd937c3fff1/0"" fixedAddress=""192.168.40.101""/>

    <Config MACAddress=""08:00:27:00:00:02"" name=""824e3a1b-2542-454d-bfee-c8aad2ad1c90/0"" fixedAddress=""192.168.40.102""/>

Now it comes the twist: DHCP Client ID in machines running Systemd-Network use /etc/machine-id to construct it but both machines have the same contents (due to cloning, you know) in this file hence the Client ID sent to the DHCP is always the same (as seen in NatService-Dhcpd.log)... and the dhcp server in the Nat Service returns the same IP address for both guests.

Is it a bug, a feature or just RFC compliance?
Thanks in advance."	jcb
20214	click close button freez machine	BSD	VirtualBox 6.1.18	2021-02-21T14:57:09Z	2021-03-19T19:54:28Z	2021-03-19T19:54:28Z	"Halo,

the problem is that click on red cross freezing machine. I believe it is mistake because after this click the menu shows up. So when I click it on VPN server machine, to hide it down (not to shout down) I lost the connection.[[Image()]]

So my suggestion is not to freeze machine until the required action is chosen. Please take a look at enclosed picture.
file:///home/swk/Obrazy/Zrzut%20ekranu%20z%202021-02-21%2015-40-25.png
I'm not sure if it enclosed "	PimCo
15137	Clearing read-only file attribute from Windows guest result in world writable permission.	Windows	VirtualBox 5.0.14	2016-02-10T10:11:10Z	2016-02-10T10:11:10Z	2016-02-10T10:11:10Z	"The shared folders of VirtualBox blindly maps read-only attribute of Windows guest to POSIX write permission. This behavior cause dangerous and undesired file permissions are set in the host system.

=== Steps to Reproduce ===
{{{
$ umask
0022
$ ls -l a.txt
-rw-r--r-- 1 user1 user1 0 Feb 10 00:00 a.txt
}}}
 1. Set read-only attribute of the file ""a.txt"", from a Windows guest with the shared folder mounted.
{{{
$ ls -l a.txt
-r--r--r-- 1 user1 user1 0 Feb 10 00:00 a.txt
}}}
 1. Unset read-only attribute of the same file, from the same Windows guest.
{{{
$ ls -l a.txt
-rw-rw-rw- 1 user1 user1 0 Feb 10 00:00 a.txt
}}}

----
VirtualBox respects umask when only creating new files, but it should do the same when mapping read-only attribute (or something similar). Leaving files world writable is simply unacceptable."	JackieKu
17706	Civilzation II (2) crash at opening	Windows	VirtualBox 5.2.10	2018-04-23T06:24:44Z	2018-04-23T09:41:58Z	2018-04-23T09:41:58Z	"When Civilization II (2) is open, the opening of session Win XP 32 fail with the following message: 

The VM session was aborted.

Code d'erreur : NS_ERROR_FAILURE (0x80004005)
Composant : SessionMachine
Interface : ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}

Otherwise, it runs OK, I mean : if I close Civ2 before closing the session, it started OK.

Interface graphique de VirtualBox
Version 5.2.10 r122088 (Qt5.6.1)

Ubuntu 16.04 LTS, 8 Go RAM

Same problem with version 5.2.8

OK with version before 5.2.8

"	jeando
17714	Ciritical Error during Windows Update (possibly VERR_PAGE_TABLE_NOT_PRESENT related)	Windows	VirtualBox 5.2.10	2018-04-27T08:07:06Z	2018-05-22T06:23:03Z	2018-05-22T06:23:03Z	"Host: Ubuntu 16.04.4 LTS (Xenial)
Guest: Windows 7 Professional 32-bit
VirtualBox: Version 5.2.10 r122088 (Qt5.6.1) (Installed from the VirtualBox repository) with Windows Guest Additions v5.0.36

I am getting a 'Critical Error' when booting my Win 7 OS and it occurs when attempting to install a Windows update during boot time. I have narrowed it down to the '2018-04 Security Monthly Quality Rollup for Windows 7 for x86-based Systems (KB4093118)' update (I say narrow but there's 137MB worth of update in that so a fair amount going on).

I raised the issue [https://forums.virtualbox.org/viewtopic.php?f=7&t=87736 in the forum] and it was suggested that the presence of 'VERR_PAGE_TABLE_NOT_PRESENT' in the logfile (attached) *might* be a clue.
"	MJN
15848	Choppy Audio and Slow Flash Video in VirtualBox 5.1	Windows	VirtualBox 5.1.4	2016-08-23T05:12:47Z	2016-09-16T15:52:38Z	2016-09-16T15:52:38Z	"Host: Fedora 24 - 64-bit + Pulseaudio<br>
Guest: Windows 10 - 64-bit <br>
<br>
Audio is choppy with sound artifacts. Am able to reproduce it on a couple of installations now on 2 different laptops. Very difficult to watch a video in VM<br>
<br>
Also, there is another problem which might be unrelated but flash videos on different sites hang while loading inside VM. Sometimes they even become slow.However, they instantly open on browsers outside the VM. In the 5.0 series I used to face flash videos becoming *slow* during playback(like 1 second on the flash video elapsing after 3 seconds in real). I didnt report it because a restart would fix the problem for many hours till it recurred. This problem seems to have been cured in 5.1 though.

"	shek
17638	"Changing ""View -> Virtual Screen -> Use Host Screen Y"" does not respect the VM "" ""Full Screen Mode"" / ""Auto-resize guest"" setting combo"	all	VirtualBox 5.2.8	2018-03-26T10:49:30Z	2018-03-26T10:49:30Z	2018-03-26T10:49:30Z	"On an Ubuntu 16.04 multi-monitor machine that has at least 2 monitors of different resolutions. Start a VM (with guest additions installed) in full screen mode and using ""Auto-resize guest display"" on ""resolution 1"" monitor. Open the VM context menu (Host Key + Home). Select View -> Virtual Screen -> Use Host Screen and select a monitor with ""resolution 2"". The VM retains the previous resolution (resolution 1).

Expected behavior: The VM is automatically resized to the new screen resolution (resolution 2) so that it is full screen in that new resolution.

Known workaround: Use the VM context menu. Deselect ""Auto-resize guest display"". Open the VM context menu. Select ""Auto-resize guest display"".

I highly suspect that this can be reproduced on any guest/host combination and any video card driver, so I won't be attaching the log file unless necessary to debug, as it would take me some time to filter out some of the lines in it. I'm attaching the relevant lines I saw (I've included the lines triggered by me turning a monitor off and on again; the action is unrelated to this bug that I've been able to consistently hit for the past few months)."	Maximilian Machedon
4924	Change mount behaviour in suse guests (vboxadd)	Linux	VirtualBox 3.0.4	2009-09-07T12:45:12Z	2010-03-12T04:06:17Z	2010-03-12T04:06:17Z	"Having vboxsf in the fstab with opensuse is not that good, as suse cannot umount volumes correctly (did not track down this one), however I think the way devices get unmounted is not the best way to do so.

As vboxadd simply unmounts mounted devices defined by fstab, it will never unmount manual mounts (umount -a -t vboxsf), so I suggest to read in /proc/mounts to unmount all *currently* mounted devices, so removing kernel modules wont fail.

Also there is a problem with vboxsf in conjunction with suse: a correctly configured fstab shows mount usage at boot time, as mount.vboxsf does not recognize vboxsf correctly at boot time (at least with suse), so i think its a good idea to use ""auto"" as per default. I changed my configuration to use noauto, and changed mount -a -t vboxsf to a simple mount for loop with all vboxsf definitions.

For all described the attached patch is working."	Michael Kromer
18735	Certain VM (RedHat) crashing module VBoxNetFlt if launch any other VM	Linux	VirtualBox 6.0.8	2019-07-02T10:01:17Z	2019-07-02T10:01:17Z	2019-07-02T10:01:17Z	"I'm using come vms, but I have one merged from VMware with RedHat inside which crashing module VBoxNetFlt if start together with any other VM. If only ""problem"" VM launched - it's OK.
Crash accompanied with VirtualBox-Guru-Mediatation screen and after that there is no way to launch any VM (just not starting) until perform the full-reboot. 
Instead rebooting I've tried to reload modules VBox*, but module VBoxNetFlt cannot be unloaded with ""it's using"" reason (while it's not actually using).
Logs and dmesg included."	e01
20485	CentOS 7, VirtualBox 6.1: compiler_types.h:214:24: error: expected ‘(’ before ‘__inline’	other	VirtualBox 6.1.26	2021-08-02T14:37:07Z	2021-08-10T10:57:17Z	2021-08-10T10:57:17Z	"CentOS 7, kernel 5.4.137-1.el7.elrepo.x86_64, Virtual Box 6.1

I try to start Virtual machine on Virtual Box 6.1.

''/sbin/vboxconfig''


but I get error:

''vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: failed: Look at /var/log/vbox-setup.log to find out what went wrong.

There were problems setting up VirtualBox. To re-start the set-up process, run
/sbin/vboxconfig
as root. If your system is using EFI Secure Boot you may need to sign the
kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load
them. Please see your Linux system's documentation for more information.''

Here error in file var/log/vbox-setup.log

''In file included from <command-line>:0:0:
./arch/x86/include/asm/page_64.h: In function ‘clear_page’:
././include/linux/compiler_types.h:214:24: error: expected ‘(’ before ‘__inline’
 #define asm_inline asm __inline
                        ^
./arch/x86/include/asm/alternative.h:256:2: note: in expansion of macro ‘asm_inline’
  asm_inline volatile (ALTERNATIVE_2(""call %P[old]"", ""call %P[new1]"", feature1,\
  ^
./arch/x86/include/asm/page_64.h:49:2: note: in expansion of macro ‘alternative_call_2’
  alternative_call_2(clear_page_orig,''


P.S.

''
gcc --version

gcc (GCC) 8.3.1 20190311 (Red Hat 8.3.1-3)''
"	a_subscriber
9007	Captured/filtered USB devices are released and reacquired when guest reboots	Windows	VirtualBox 4.0.8	2011-06-01T13:34:26Z	2016-08-23T07:18:59Z	2016-08-23T07:18:59Z	"Hi,

Host: Xubuntu 9.10 x86, VirtualBox 4.0.8 (with PUEL extension pack).
Guest: Windows XP SP3

When the guest is rebooted, VirtualBox seems to free/release any filtered USB devices, then re-capture them. I think all filtered USB devices should remain filtered when the guest reboots.

This problem is most noticeable when using a USB floppy drive. Most(?) Linux distributions treat USB floppy drives as generic removable drives. So when you insert a disk, the kernel attempts to read the last sector and scans for partition tables. In combination with the default block device readahead of 256 blocks, that process can take 30 seconds or so. *Every time you insert a disk*. It's quite annoying. Floppy disks never have a partition table of course so the scan is pointless. Anyway...

To reproduce the problem:
 - Connect a USB floppy drive to your system.
 - Add the floppy drive to the USB Device Filters of a Windows guest VM.
 - Start the Windows VM. Insert a floppy disk. Notice the drive only spins for a short time. Because it is captured, the Linux host OS doesn't attempt to access it.
 - Reboot the guest OS.
 - Notice how when the guest reboots, the kernel creates a /dev/sdX block device and scans for partitions (taking about 30 seconds). Then the block device is removed when VirtualBox re-captures the device.

Other drives are probably affected similarly, so you get an unnecessary block device creation, partition scan and device removal whenever the guest is rebooted. (That takes less time than for USB floppy drives so will be less noticeable.)

"	Donuts
1936	Caps lock not being properly passed through to guest	Windows	VirtualBox 1.6.4	2008-08-10T17:40:03Z	2015-10-08T02:58:23Z	2015-10-08T02:58:23Z	"The caps lock key is not being correctly passed through to the guest,
using VBoxSDL. If I press caps lock and release it it works fine,
but if i hold down caps lock and press another character, such as j, the caps lock is sent
before the j. This is relatively
important for some assistive technologies that use the caps lock key as a 
modifier for screen reading functions."	Tyler Spivey
17051	Caps Lock key being remapped in Linux guest can cause the mapping to malfunction	Linux	VirtualBox 5.1.26	2017-09-04T00:45:46Z	2017-09-13T12:53:46Z	2017-09-13T12:53:46Z	"When Colemak is set as the default keyboard layout and Shift+Shift is mapped to serve as a Caps Lock (e.g. with ""setxkbmap -option shift:both_capslock""), Shift+Shift also starts working as Backspace for a little while."	GeneralFailer
18444	Cannot use microphone. Applications that try to record audio hang	Linux	VirtualBox 6.0.4	2019-02-20T20:30:46Z	2020-05-10T16:39:50Z	2020-05-10T16:39:50Z	"After I upgraded VirtualBox from 5.x to 6.0.4, I can no longer use microphone from within the VirtualBox VM. I run Debian on both the host and the guest system.

Steps to reproduce:
* Create a new VM. Set guest OS to Debian 64-bit, don't change any other settings.
* Boot the VM using a Debian live CD.
* Enable audio input for the VM.
* Inside the VM, try to use a program that tries to record audio, such as SOX (run these commands: apt-get install sox; rec -n).
* Observe that the program hangs. On the host system, the same program works fine."	abacabadabacaba
15006	Cannot update Win 8.1 to Win 10.0 because of display	Windows	VirtualBox 5.0.12	2016-01-05T00:59:05Z	2016-01-07T18:27:59Z	2016-01-07T18:27:59Z	"host: opensuse 43.2, linux 4.1.13-5-default x86_64

guest: windows 8.1

Occasionally I get a popup to update to window 10. I say ""Yes!"" It then spits out this message:

... cannot upgrade ...
The display manufacturer hasn't made you display compatible with Windows 10. Check with your manufacturer for support.

It then suggests I buy a new computer. I have tried this with the setting ""Windows 8.1 (64 bit)"" and ""Windows 10 (64 bit)"".

Is there a way to convince the upgrade evaluator that the display really is a marvel of modern technology?
"	James Moe
16990	Cannot start the Guest in VirtualBox	Windows	VirtualBox 5.1.26	2017-08-08T06:13:46Z	2017-10-21T09:19:21Z	2017-10-21T09:19:21Z	"'''Some of my information:'''[[BR]]
Machine: MSI GE62-489 (CPU: Intel® Core™ i7-6700HQ @ 2.60GHz × 8 )[[BR]]
Host system: Ubuntu 14.04 64-bit(kernel: 4.4.0-89-generic)[[BR]]
VirtualBox version: 5.1.26 r117224[[BR]]
Guest system: Windows 7 64-bit[[BR]]
[[BR]]

When I try to start Guest in VirtualBox, it showed 2 error messages:[[BR]]

'''First message:'''

{{{
Failed to open a session for the virtual machine Windows 7.

The virtual machine 'Windows 7' has terminated unexpectedly during startup with exit code 1 (0x1).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
}}}

Just like the following figure:[[BR]]
[[Image(http://i4.bvimg.com/1949/3876f081487a381e.png)]]

'''Second message:'''

{{{
Kernel driver not installed (rc=-1908)

The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or 
there is a permission problem with /dev/vboxdrv. Please reinstall 
the kernel module by executing

'/sbin/vboxconfig'

as root.

where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED 
(-1908) - The support driver is not installed. On linux, open returned 
ENOENT.
}}}
 
Just like the following figure:[[BR]]

[[Image(http://i4.bvimg.com/1949/5c44b8e679464f9c.png)]]

Then, I do what he told me to do, run the following command in terminal:

{{{
$ sudo /sbin/vboxconfig
}}}

It shows the following message:

{{{
Adding system startup for /etc/init.d/vboxdrv ...
   /etc/rc0.d/K80vboxdrv -> ../init.d/vboxdrv
   /etc/rc1.d/K80vboxdrv -> ../init.d/vboxdrv
   /etc/rc6.d/K80vboxdrv -> ../init.d/vboxdrv
   /etc/rc2.d/S20vboxdrv -> ../init.d/vboxdrv
   /etc/rc3.d/S20vboxdrv -> ../init.d/vboxdrv
   /etc/rc4.d/S20vboxdrv -> ../init.d/vboxdrv
   /etc/rc5.d/S20vboxdrv -> ../init.d/vboxdrv
 Adding system startup for /etc/init.d/vboxballoonctrl-service ...
   /etc/rc0.d/K65vboxballoonctrl-service -> ../init.d/vboxballoonctrl-service
   /etc/rc1.d/K65vboxballoonctrl-service -> ../init.d/vboxballoonctrl-service
   /etc/rc6.d/K65vboxballoonctrl-service -> ../init.d/vboxballoonctrl-service
   /etc/rc2.d/S35vboxballoonctrl-service -> ../init.d/vboxballoonctrl-service
   /etc/rc3.d/S35vboxballoonctrl-service -> ../init.d/vboxballoonctrl-service
   /etc/rc4.d/S35vboxballoonctrl-service -> ../init.d/vboxballoonctrl-service
   /etc/rc5.d/S35vboxballoonctrl-service -> ../init.d/vboxballoonctrl-service
 Adding system startup for /etc/init.d/vboxautostart-service ...
   /etc/rc0.d/K65vboxautostart-service -> ../init.d/vboxautostart-service
   /etc/rc1.d/K65vboxautostart-service -> ../init.d/vboxautostart-service
   /etc/rc6.d/K65vboxautostart-service -> ../init.d/vboxautostart-service
   /etc/rc2.d/S35vboxautostart-service -> ../init.d/vboxautostart-service
   /etc/rc3.d/S35vboxautostart-service -> ../init.d/vboxautostart-service
   /etc/rc4.d/S35vboxautostart-service -> ../init.d/vboxautostart-service
   /etc/rc5.d/S35vboxautostart-service -> ../init.d/vboxautostart-service
 Adding system startup for /etc/init.d/vboxweb-service ...
   /etc/rc0.d/K65vboxweb-service -> ../init.d/vboxweb-service
   /etc/rc1.d/K65vboxweb-service -> ../init.d/vboxweb-service
   /etc/rc6.d/K65vboxweb-service -> ../init.d/vboxweb-service
   /etc/rc2.d/S35vboxweb-service -> ../init.d/vboxweb-service
   /etc/rc3.d/S35vboxweb-service -> ../init.d/vboxweb-service
   /etc/rc4.d/S35vboxweb-service -> ../init.d/vboxweb-service
   /etc/rc5.d/S35vboxweb-service -> ../init.d/vboxweb-service
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why.

There were problems setting up VirtualBox.  To re-start the set-up process, run
  /sbin/vboxconfig
as root.
}}}

You can see this line:

{{{
vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why.
}}}

So I run the following command in terminal:

{{{
$ dmesg
}}}

It shows about 1000 lines. The whole information it shows is in the attach file. There are some errors and warnings from this information:

{{{
[    0.019546] ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20150930/dswload-210)
[    0.027179] ACPI Error: 1 table load failures, 9 successful (20150930/tbxfload-214)
[    0.205608] ACPI Error: [^^^PEG0.PEGP.EASP] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359)
[    0.205611] ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.EC._REG] (Node ffff88027b0ef4b0), AE_NOT_FOUND (20150930/psparse-542)
[    0.205622] ACPI : EC: Fail in evaluating the _REG object of EC device. Broken bios is suspected.
[    0.221593] ACPI Error: [^^^PEG0.PEGP.EASP] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359)
[    0.221596] ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.EC._REG] (Node ffff88027b0ef4b0), AE_NOT_FOUND (20150930/psparse-542)
[    2.603310] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-19.ucode failed with error -2
[    2.603334] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-18.ucode failed with error -2
[    2.603347] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-17.ucode failed with error -2
[    3.273673] EXT4-fs (sda7): re-mounted. Opts: errors=remount-ro
[  126.578953] systemd-hostnamed[5793]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname!
[ 1952.203735] systemd-hostnamed[13694]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname!
}}}

Now I don't know what to do. The Guest system just cannot start.[[BR]]

'''Another information:'''[[BR]]

If I choose kernel 3.19.0-25-generic to come in when I start up my machine, the same VirtualBox can use normally. The Guest system win7 can start normally. But I never succeed to start guest normally with any linux kernel who is newer than 3.19.0-25

So, how to solve this problem? Thank you very much!"	TimeCoder
16952	Cannot start any VM after install extension pack.	all	VirtualBox 5.1.26	2017-07-28T08:14:29Z	2017-07-28T08:44:45Z	2017-07-28T08:44:45Z	"After installation ""Extension Pack"", I cannot start any VM with error:
Loading VD plugins failed (VERR_ACCESS_DENIED).

After removing ""Extension Pack"" works all fine (of course without extension pack funcions).ls "	Polish
15788	Cannot resize guest window, auto-resize and seamless mode are greyed out [GuestAddition is installed]	Windows	VirtualBox 5.1.2	2016-08-13T18:02:26Z	2016-08-13T18:02:26Z	2016-08-13T18:02:26Z	"Host: Fedora 24, Guest: Win8.1
After installing guest OS, and installing GuestAdditions, I am unable to resize guest window.
It's size is fixed, 1024x768. In the View menu intem Seamless mode and Auto resize guest display are both disabled (greyed out).
Earlier everything was fine on my machine, it worked as it expected. But one day it went wrong. I uninstall and reinstall VBox, but the issue is still present. Then I made a clean Fedora 24 install on this machine, but the issue is still present. I've remove my GPU and used my motherboard integrated GPU but the issue is still present. In this machine I am unable to use VBox, because it's screen is too small, and unable to resize."	VChris
18525	Cannot launch Virtual Machine - Argument aWidth is invalid	Linux	VirtualBox 6.0.4	2019-03-27T11:06:59Z	2019-03-27T11:06:59Z	2019-03-27T11:06:59Z	"I can not launch any of my former created or new created VMs.

VirtualBox Guru Medition Error is showing up. Fatal Error (my translation from german text showing up)

Host: Ubuntu 18.04
Guest: any

Ataching log to investigate error.

Thanks for good work!"	Mate
18422	Cannot install Extension Pack 6.0.4	other	VirtualBox 6.0.4	2019-02-07T14:10:43Z	2019-02-07T14:10:43Z	2019-02-07T14:10:43Z	"Failed to load the main module ('/usr/lib/virtualbox/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/linux.amd64/VBoxPuelMain.so'): VERR_FILE_NOT_FOUND - /usr/lib/virtualbox/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/linux.amd64/VBoxPuelMain.so: undefined symbol: _ZNK16RTCRestArrayBase9baseCloneEv.
"	dizcza
7461	Cannot delete old and unused VM snapshot.	Linux	VirtualBox 3.2.8	2010-09-11T20:30:53Z	2016-01-27T20:27:06Z	2016-01-27T20:27:06Z	"Hi all.

I've created a snapshot of my Debian Testing VM (running on Mandriva Linux Cooker) a long time ago, and now I don't want it anymore, but VirtualBox won't let me delete it.

I'm getting:

{{{
Failed to delete the snapshot Before hard-disk resize of the virtual machine Debian No. 1.
Hard disk '/home/shlomif/.VirtualBox/HardDisks/Debian No. 1.vdi' has more than one child hard disk (2).

Details:


Result Code: 
NS_ERROR_FAILURE (0x80004005)
Component: 
Machine
Interface: 
IMachine {6d9212cb-a5c0-48b7-bbc1-3fa2ba2ee6d2}

}}}

The VM is turned off and the snapshot is occupying unnecessary space on my hard disk. Please help me delete it.

Regards,

-- Shlomi Fish"	Shlomi Fish
19727	Cannot connect to OCI Cloud: VERR_CR_KEY_UNSUPPORTED_CIPHER	other	VirtualBox 6.1.10	2020-07-16T07:23:18Z	2020-07-16T07:23:18Z	2020-07-16T07:23:18Z	"VirtualBox running on CentOS Linux release 7.8.2003 (Core)
- Linux 3.10.0-1127.13.1.el7.x86_64

has problem opening the Key from profile because of unsupported cipher
(Works in Windows, exact same profile)

VBoxManage cloud --provider=OCI --profile=oci list instances
Parameter 'compartment' is empty or absent.
Trying to get the compartment from the passed cloud profile 'oci'
Found the compartment 'ocid1.compartment.oc1..xxxxxxxxxxxxxxxxxxxxx':
Reply is in the form 'instance name' = 'instance id'
0%...
Progress state: VBOX_E_IPRT_ERROR
VBoxManage: error: Failed to list instances
VBoxManage: error: Failed to read signing key from ""~/.oci/oci_api_key.pem"": VERR_CR_KEY_UNSUPPORTED_CIPHER
VBoxManage: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005), component CloudClientWrap, interface ICloudClient
VBoxManage: error: Context: ""RTEXITCODE listCloudInstances(HandlerArg*, int, PCLOUDCOMMONOPT)"" at line 229 of file VBoxManageCloud.cpp"	SpongeTort
18754	Cannot capture mouse pointer in video recording of Ubuntu 18.04 LiveCD guest	Linux	VirtualBox 6.0.8	2019-07-15T04:27:15Z	2020-05-09T14:32:41Z	2020-05-09T14:32:41Z	"This is on Ubuntu 18.04 host, VirtualBox 6.0.8 r130520, and Ubuntu 18.04 LiveCD (installer) guest.

Please see this video: https://i.imgur.com/KTiGSCJ.mp4

The video starts with Ubuntu 18.04 as guest in VirtualBox, controlled by rdesktop.

While mouse integration is active in VirtualBox, even if the actual mouse is controlling rdesktop, there is no mouse pointer rendered in the VirtualBox Ubuntu LiveCD guest.

If I turn off mouse integration in VirtualBox, then: when we have the actual host mouse pointer controlling via rdesktop - a mouse pointer appears rendered in the VirtualBox Ubuntu LiveCD guest. So this looks promising.

But if I do a Recording video capture in VirtualBox in this state - there is still no mouse pointer in the video recording, even if the host mouse was controlling via rdesktop, and the VirtualBox Ubuntu LiveCD appeared to be rendering the mouse pointer's ""clone""!

Maybe this is a bug in VirtualBox?

Attached is the .webm recorded by VirtualBox in the test run shown in the video above."	sdaau
14532	Cannot access webcam over getUserMedia()	Windows	VirtualBox 5.0.2	2015-09-01T21:38:50Z	2016-01-15T14:22:35Z	2016-01-15T14:22:35Z	"When booting Windows 10 with the latest Edge within Virtual Box 5.0.2 from Ubuntu 15.04 I cannot access the Webcam within Edge.

Beware, it works fine when the website uses a Flash plugin. There the webcam shows up. But NOT when it's being loaded through the getUserMedia() API. It's a native Javascript function most modern browsers implement.

I have the drivers installed. Let me repeat: it works fine through Flash, but not via JavaScript. Can you please look at it? This is blocking the development of www.videomail.io where I need to test it for the latest Edge.

Many thanks!"	Michael Heuberger
18770	can't use VirtualBox under debian-live-10.0.0-amd64-kde	all	VirtualBox 6.0.10	2019-07-18T10:56:13Z	2019-08-01T17:26:01Z	2019-08-01T17:26:01Z	"hello,
i just made a fresh installation of [https://cdimage.debian.org/debian-cd/current-live/amd64/iso-hybrid/ debian-live-10.0.0-amd64-kde.iso] to my harddisk and i tried to install virtualbox.

i followed the instruction on [https://www.virtualbox.org/wiki/Linux_Downloads Debian-based Linux distributions]


{{{
:~$ echo ""deb https://download.virtualbox.org/virtualbox/debian buster contrib"" | sudo tee -a /etc/apt/sources.list.d/virtualbox.list
:~$ wget -q https://www.virtualbox.org/download/oracle_vbox_2016.asc -O- | sudo apt-key add -

:~$ sudo apt update -y
Hit:1 http://security.debian.org/debian-security buster/updates InRelease
Hit:2 https://download.virtualbox.org/virtualbox/debian buster InRelease                          
Hit:3 http://deb.debian.org/debian buster InRelease                
Hit:4 http://deb.debian.org/debian buster-updates InRelease
Reading package lists... Done
Building dependency tree       
Reading state information... Done
All packages are up to date.


:~$ apt search virtualbox
...
virtualbox-5.2/unknown 5.2.32-132073~Ubuntu~bionic amd64
  Oracle VM VirtualBox

virtualbox-6.0/unknown 6.0.10-132072~Ubuntu~bionic amd64
  Oracle VM VirtualBox
...


:~$ sudo apt install virtualbox-6.0
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following additional packages will be installed:
  libcurl4 libsdl-ttf2.0-0 linux-headers-amd64
Recommended packages:
  linux-image
The following NEW packages will be installed:
  libcurl4 libsdl-ttf2.0-0 linux-headers-amd64 virtualbox-6.0
0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 103 MB of archives.
After this operation, 228 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://deb.debian.org/debian buster/main amd64 libcurl4 amd64 7.64.0-4 [332 kB]
Get:2 http://deb.debian.org/debian buster/main amd64 libsdl-ttf2.0-0 amd64 2.0.11-6 [18,6 kB]
Get:3 http://deb.debian.org/debian buster/main amd64 linux-headers-amd64 amd64 4.19+105 [6.652 B]
Get:4 https://download.virtualbox.org/virtualbox/debian buster/contrib amd64 virtualbox-6.0 amd64 6.0.10-132072~Ubuntu~bionic [102 MB]                                                                                                                                        
Fetched 103 MB in 30s (3.424 kB/s)                                                                                                                                                                                                                                            
...

}}}

i was wondering that during installation the virtualbox packet it was shown ""6.0.10-132072~Ubuntu~bionic"", but i am on an debian environment at that moment

ok, so far so good... virtualbox starts as normal as i expected.[[BR]]

but when i create a new virtual machine and start it, i get an error message.

{{{
Failed to open a session for the virtual machine Test.

The virtual machine 'Test' has terminated unexpectedly during startup with exit code 1 (0x1).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {5047460a-265d-4538-b23e-ddba5fb84976}

}}}

the same error message i get, when i add an existing virtual machine i created and used earlier under Ubuntu19.04.


the current installed version under Debian Buster (KDE) shows:
Version 6.0.10 r132072 (Qt5.11.3)
"	beta_tester
17854	Can't upgrade extension pack as normal user from GUI on Ubuntu 18.04 (due to missing gksu?)	all	VirtualBox 5.2.14	2018-07-03T19:33:43Z	2018-07-03T19:33:43Z	2018-07-03T19:33:43Z	"On Ubuntu 18.04, it is no longer possible to upgrade the extension pack from the VirtualBox manager GUI when running as an unprivileged user.  This used to work under Ubuntu 17.10 and earlier versions (you were prompted for a password to gain root privileges).

After accepting the license, I get the following error message:

{{{

Failed to install the Extension Pack /home/nate/.config/VirtualBox/Oracle_VM_VirtualBox_Extension_Pack-5.2.14.vbox-extpack.

The installer failed with exit code 127: Error creating textual authentication agent: Error opening current controlling terminal for the process (`/dev/tty'): No such device or address.

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: ExtPackManagerWrap
Interface: IExtPackManager {edba9d10-45d8-b440-1712-46ac0c9bc4c5}

}}}

I think the root cause of the error is that Ubuntu 18.04 no longer includes gksu (see [https://bugs.launchpad.net/ubuntu/+source/umit/+bug/1740618 Ubuntu bug 1740618]).  Looking at the source to VBoxExtPackHelperApp, it tries to execute gksu to elevate privileges.  If that doesn't work it tries to run pkexec, which here doesn't work either, I guess because it doesn't have a tty to talk to.  The ""Error creating textual authentication agent"" message is apparently from pkexec.

A workaround is to install the extension pack manually with VBoxManage, or to run the VirtualBox GUI as root under sudo (but this is a bit annoying for me, because root has a different ~/.config/VirtualBox which points to a bunch of stale VMs and produces more warnings).  However, from the symptoms above, it would be hard for a new user to know to try this.

VirtualBox 5.2.14 installed from http://download.virtualbox.org/virtualbox/debian.  The package file is virtualbox-5.2_5.2.14-123301~Ubuntu~bionic_amd64.deb.

(Not sure which component applies to the GUI manager, or if this is ""installer"".  Have marked as component GUI for now but feel free to change.)"	Nate Eldredge
18297	Can't unmount vdi file	Linux	VirtualBox 6.0.0	2019-01-10T22:59:09Z	2019-01-12T21:41:45Z	2019-01-12T21:41:45Z	"I just tried to gparted one of the vdi files and I am getting error unmount it. I have two VM setup both are Ubuntu 18.04 with latest updates

VM1 - is what I am booing into (fresh install)
VM2 - is what is attached as additional IDE or SATA to VM1

VM2 was cloned from VM1

Here is what I did try to do

1. in VM1 attach VM2 vdi file. I did try as IDE and SATA each time
2. Boot to VM1
3. Start gparted
4. Select /dev/sda (VM2)
5. Try to resize ext4 partition (Did checked it is not mounted)
6. Apply changes

It seams that /dev/sdb is VM1 what I booted into.

Resize fails

"	oxoocoffee
12359	Can't switch workspace on Linux host when guest in fullscreen	Windows	VirtualBox 4.3.2	2013-11-13T20:46:09Z	2018-02-01T04:55:49Z	2018-02-01T04:55:49Z	"Whenever the guest (in this case Windows 7) is running fullscreen (in my case with 2 monitors, one of each guest is replicated in fullscreen on my two physical monitors) I cannot hit right-ctrl and change workspace. Often times the guest menu (at the top) gets locked and/or I am completely ""locked into"" the guest without possibility to move out into the host except for shutting down the guest from within the VM.

This worked without a problem in 4.2.x. Also, whenever I run anything else on the host in fullscreen (youtube video, whatever) the guest VM decides for unknown reasons that I have unplugged all monitors and resizes guest-resolution seemingly randomly. Very annoying!"	isecore
18489	Can't run VirtualBox as non root-user.	all	VirtualBox 6.0.4	2019-03-12T12:27:07Z	2019-03-26T19:05:35Z	2019-03-26T19:05:35Z	"As a normal user I get:
> virtualbox
Qt FATAL: FATAL: The application binary appears to be running setuid, this is a security hole.
Abgebrochen

Existing vms can be started by e.g. vboxmanage startvm VMName 
"	ThomKB
13727	can't run a program with Transient Folders with Windows 10 Technical Preview Build 9841	Windows	VirtualBox 4.3.20	2015-01-03T01:03:45Z	2015-01-03T01:03:45Z	2015-01-03T01:03:45Z	"I am using the modern.IE Windows 10 with Internet Explorer 11 VirtualBox download.

I am using VirtualBox 4.3.20 r96996 on Fedora 20 x86_64.

I updated Windows 10 with the available Windows Updates.

I installed the VirtualBox Guest Additions for 4.3.20.

I changed a few of the settings as they come from Microsoft (modern.IE):

1) Chipset -> ICH9
2) Enable I/O APIC
3) IDE -> ICH6
4) switch the HD to the SATA controller
  a) SATA is set to AHCI
  b) enable Use Host I/O Cache

Once the guest is booted, I go to Devices -> Shared Folders Settings...

I add a Transient Folders that maps to my local (ext4) Linux filesystem. A ""Downloads"" directory in my home directory.

I then ""browse"" to \\VBOXSVR\Downloads in Windows Explorer.

I get the file listing.

I doulbe-click on an installer program for a PDF Viewer.

I get an error:
""ShellExecuteEX failed; code 1.
Incorrect function.""

If I copy the file from \\VBOXSVR\Downloads to a local guest directory, it runs fine.

But I have ran this same installer the same way with all of the other modern.IE VirtualBox images, i.e. running the installer from the \\VBOXSVR\Downloads share works on all the other modern.IE images but Windows 10 w/IE 11."	allenatdecisiv
17113	Can't reboot after changing windows 10 display resolution on ubuntu-16.04 and virtualbox-5.1.28	Windows	VirtualBox 5.1.28	2017-09-27T02:21:49Z	2017-10-02T15:40:15Z	2017-10-02T15:40:15Z	"
After changing windows 10 display resolution, I encountered boot fail of windows 10 vm.
I's using virtualbox-5.1.28 and ubuntu-16.04. And I've installed vargrant-2.0.0 but I didn't use it.

I found following error messages from VBox.log but I can't figure out any clues.

1111 00:00:00.337951 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={02326f63-bcb3-4481-96e0-30d1c2ee97f6} aCompo     nent={DisplayWrap} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=0
1112 00:00:00.343556 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={02326f63-bcb3-4481-96e0-30d1c2ee97f6} aCompo     nent={DisplayWrap} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=0

"	edward.lee
12477	Can't operate any more on a locked VM -- a way to force lock removal is needed	Windows	VirtualBox 4.3.4	2013-12-12T09:58:29Z	2016-12-19T13:20:55Z	2016-12-19T13:20:55Z	"Sometimes it happens that a VM stops or hangs for some unknown reason and it becomes impossible to operate on it any more because vbox says it's locked.

For example:
{{{
$ VBoxManage controlvm xyz poweroff
VBoxManage: error: The virtual machine is being powered down
VBoxManage: error: Details: code VBOX_E_INVALID_VM_STATE (0x80bb0002), component Console, interface IConsole, callee nsISupports
VBoxManage: error: Context: ""PowerDown(progress.asOutParam())"" at line 222 of file VBoxManageControlVM.cpp
}}}

and trying to start it gives:
{{{
$ VBoxHeadless -s xyz
Oracle VM VirtualBox Headless Interface 4.3.4
(C) 2008-2013 Oracle Corporation
All rights reserved.

VBoxHeadless: error: The machine 'xyz' is already locked for a session (or being unlocked)
VBoxHeadless: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component Machine, interface IMachine, callee nsISupports
VBoxHeadless: error: Context: ""LockMachine(session, LockType_VM)"" at line 955 of file VBoxHeadless.cpp
}}}

Now I'm stuck: the only way I know to solve this problem is to completely shutdown vbox and/or restart the server, but this forces to shutdown all the other running vms, and thats not really easy on some situation.

I suppose that a way to force the removal of a lock is much needed."	Alex
18025	Can't launch VirtualBox 5.2.18-1 on fedora 28.	other	VirtualBox 5.2.18	2018-10-02T06:29:57Z	2018-10-02T15:18:54Z	2018-10-02T15:18:54Z	"On Fedora 28 I can't launch VirtualBox 5.2.18-1. I am receiving the following error messages:

VirtualBox: Error -610 in supR3HardenedMainInitRuntime!
VirtualBox: dlopen(""/usr/lib64/virtualbox/VBoxRT.so"",) failed: <NULL>

VirtualBox: Tip! It may help to reinstall VirtualBox.

And the tip doesn't help.
"	EPOdata
12635	Can't import to different basedir	other	VirtualBox 4.3.6	2014-01-22T21:03:11Z	2014-01-22T21:03:11Z	2014-01-22T21:03:11Z	"It's nice to have --basedire option for cloning, and the very same option would be quite useful also when importing OVF or other formats.

Otherwise, to move my VM to the correct basedir I first have to import it,  clone --basedir , and finally remove the old copy.

Not very straightforard"	Alex
6323	Can't get IP Forwarding to work with Host-only adapter	Linux	VirtualBox 3.0.6	2010-03-04T07:48:08Z	2011-01-26T12:41:53Z	2011-01-26T12:41:53Z	"Hello, 

I'm developing a software to demonstrate how Man in the middle works using arp cache poisoning. I can't get ip forwarding to work with Host-only adapter! 

I was previously using a bridged network on tun/tap devices that I was creating myself. My network was designed like this : 

[*]1 bridge br0

[*]2 tun/tap interfaces tap0 and tap1


Then I add the tap0 and tap1 to the bridge and configure my 2 VMs to use bridged network on tap0 and tap1.
With this configuration, ip-forwading works perfectly fine!  My bridge br0 can play the role of the attacker and forward ip between my first and second VM.

'''Now I'm trying to use host-only adapter''', so that i could use later in my program the ''VBoxManage hostonly ipconfig'' command line. In the configuration I want to be, my 1st VM wants to talk to my 2nd VM but its arp cache has been corrupted so that packets are sent to the host (host-only interface). My problem is packets aren't forwarded by the host, and they normally should be.

I'm enabling ip forwarding on the host-only adapter  (vboxnet0), as I was doing before with my bridge br0 : 

{{{
echo 1 > /proc/sys/net/ipv4/conf/*/forwarding 
echo 0 > /proc/sys/net/ipv4/conf/*/send_redirects
}}}

Unfortunately, even though each machine in this configuration can communicate with one another, the vboxnet0 interface doesn't forward ip packets. Shouldn't host only interface behave like a normal networking interface?

Thank you, 

Laurent Sebag"	grattemedi
10195	Can't delete snapshot in 4.1.8	Windows	VirtualBox 4.1.8	2012-01-26T17:45:07Z	2016-09-01T23:10:26Z	2016-09-01T23:10:26Z	"I made a snapshot (by mistake...I thought that was how one was supposed to end a session before going home.) and now I can't delete it. I get the following messages:

{{{
Failed to delete the snapshot Snapshot 1 of the virtual machine Win7.

Could not merge the medium '/local/home/skelem/VirtualBox VMs/Win7/Snapshots/{e28386b1-690c-4b83-acf2-f522ce331a65}.vdi' to '/local/home/skelem/VirtualBox VMs/Win7/Win7.vdi' (VERR_INVALID_PARAMETER).


Result Code: 
VBOX_E_FILE_ERROR (0x80BB0004)
Component: 
Medium
Interface: 
IMedium {53f9cc0c-e0fd-40a5-a404-a7a5272082cd}
}}}

4.1.8 r75467"	Chelmite
19951	Can't boot from bootable USB and install window on freshly created Windows VM	Windows	VirtualBox 6.1.14	2020-10-09T17:22:31Z	2020-10-09T17:22:31Z	2020-10-09T17:22:31Z	"1. I wasted an hour of my life downloading and creating an installable USB drive with Windows 10, using Microsoft's official tool.
2. In Virtual Box on a Linux host, I created a VM, chose Windows as the machine type, enabled the USB controller,
3. Then I plugged the physical Windows bootable USB drive into the host's physical USB port, and added that device to the VM
4. I powered on the VM and I was asked to choose whether to boot from a physical optical drive on the host, an ISO image simulating an optical drive, and I don't remember what other options, but there was no option to boot from the USB drive.

I should have that option. Now I have to start over and download a DVD ISO image and use that."	php4fan
5856	Can not write to VBox shared folders until someone logs in	Windows	VirtualBox 3.1.2	2009-12-27T21:36:34Z	2009-12-27T21:36:34Z	2009-12-27T21:36:34Z	"Vbox 3.1.2
Host: CentOS 5.4
Guest: Windows Server 2003 as a Terminal Server
Guest Additions: 3.1.2

Hi All,

Would you please fix this for me?

I have Cobian Backup (http://www.cobian.se/cobianbackup.htm) set to backup certain files on my Guest in the middle of the night to my host's VBox shared drive (\VBOXSVR\Drivers-Windows\pro-backup). Before I do my backups on the Host, I shut the Guest down.  After the backups are complete, I restart the Guest.  So, the Guest gets reboot once a day.

Problem: Cobian can not see the drive, unless someone logs in (any account will do).  This has shown up mightily during the holidays as no one is using the Guest.

Cobian error:
    12/25/2009 10:20:17 PM The destination directory ""\VBOXSVR\Drivers-Windows\pro-backup\pro60 2009-12-25 22;20;10"" doesn't exist. Trying to create it

    ERR 12/25/2009 10:20:17 PM Cannot create the destination directory ""\VBOXSVR\Drivers-Windows\pro-backup\pro60 2009-12-25 22;20;10""

Many thanks,
-T"	ToddAndMargo
20377	Can not select extension file for install in host	other	VirtualBox 6.1.22	2021-05-24T19:37:00Z	2021-07-21T18:51:46Z	2021-07-21T18:51:46Z	"In Fedora 33/34 is not possible to select the extension file in the GUI manager...mouse click does not select anything and it is only possible to close the file window by closing the window from OS/desktop.

Desktop is KDE
Vbox is  6.1.22"	Knud
17898	Can Not Assign More Than 8 Processors to Windows 10 Guest	Windows	VirtualBox 5.2.16	2018-07-28T02:33:08Z	2019-09-02T08:47:10Z	2019-09-02T08:47:10Z	"I just built a new Linux (Gentoo) system based on a SuperMicro mainboard, C9X299-PG300, and an Intel i9-7940X (14-core, 28 thread) CPU. I copied over my Windows 10 VirtualBox guest VM from the old system (Intel i7 8-core) to the new system. The Virtual Box guest boots without issue using the old settings (8-processors). However, if I shut down the VM and change the settings to a higher processor count (I have tried 12 and 14 cores), the VM does not progress very far into its boot: I see a blue background and the windows icon. None of the VirtualBox activity icons at the bottom of the Guest window are active: all dark. That is it. There is one Virtual Box process that continues to run at 100% cpu usage until I kill the VM. In the VirtualBox log the relevant part is:


{{{
00:00:03.569172 VMMDev: Guest Log: BIOS: Boot : bseqnr=1, bootseq=0032
00:00:03.570686 VMMDev: Guest Log: BIOS: Booting from Hard Disk...
00:00:03.872720 Display::handleDisplayResize: uScreenId=0 pvVRAM=00007f2f74000000 w=1024 h=768 bpp=24 cbLine=0xC00 flags=0x0
00:00:03.872802 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=1024x768, Sending to async-handler
00:00:03.872885 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=1024x768
00:00:03.872897 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=1024x768
00:00:03.872908 GUI: UIFrameBufferPrivate::performResize: Size=1024x768, Directly using source bitmap content
00:00:04.610473 GIM: HyperV: Guest OS reported ID 0x1040a0000271b
00:00:04.610490 GIM: HyperV: Open-source=false Vendor=0x1 OS=0x4 (Windows NT or derivative) Major=10 Minor=0 ServicePack=0 Build=10011
00:00:04.610506 GIM: HyperV: Enabled hypercall page at 0x000000000020f000
00:00:04.610778 GIM: HyperV: Unknown/invalid hypercall opcode 0x8001 (32769)
00:00:04.610792 GIM: HyperV: Enabled TSC page at 0x000000000000c000 - u64TscScale=0xd3add100000000 u64TscKHz=0x2f3dc9 (3 096 009) Seq=1
00:00:04.610982 TM: Switching TSC mode from 'VirtTscEmulated' to 'RealTscOffset'
00:00:04.611068 GIM0: HyperV: Enabled APIC-assist page at 0x000000000000d000
00:00:04.614818 APIC0: Attempt to read reserved/unknown MSR (0x80e) -> #GP(0)
00:00:04.614825 IEM: rdmsr(0x80e) -> #GP(0)
00:00:04.614859 GIM: HyperV: Guest indicates a fatal condition! P0=0x1e P1=0xffffffffc0000096 P2=0xfffff80360406fd9 P3=0x0 P4=0x0
00:05:36.462561 GUI: Request to close active machine-window.
}}}

The ""HyperV: Guest indicates a fatal condition!"" does not look good."	Jagdpanther
16289	Camera access not working	Linux	VirtualBox 5.1.10	2016-12-14T11:37:44Z	2016-12-14T16:14:02Z	2016-12-14T16:14:02Z	"Apps such as Viber and Camera apps aren't able to connect with the host camera on my laptop since updating to the new VBox version. 

Running Android version 4.4 lollipop 32-bit on VBox 5.1 on Ubuntu 16.04 (64-bit)

(see screenshots)"	d3m0nking
20130	Calling launchVMProcess via vboxwebsrv causes VERR_ENV_INVALID_VAR_NAME	Linux	VirtualBox 6.1.16	2021-01-16T23:43:41Z	2021-01-21T14:23:58Z	2021-01-21T14:23:58Z	"When Sending the SOAP request:


{{{
<soap-env:Envelope xmlns:soap-env=""http://schemas.xmlsoap.org/soap/envelope/"">
	<soap-env:Body>
		<ns0:IMachine_launchVMProcess xmlns:ns0=""http://www.virtualbox.org/"">
			<_this>692d166c1e430875-0000000000000004</_this>
			<session>692d166c1e430875-0000000000000003</session>
			<name/>
			<environmentChanges/>
		</ns0:IMachine_launchVMProcess>
	</soap-env:Body>
</soap-env:Envelope>
}}}


I get:


{{{
<SOAP-ENV:Envelope xmlns:SOAP-ENV=""http://schemas.xmlsoap.org/soap/envelope/"" xmlns:SOAP-ENC=""http://schemas.xmlsoap.org/soap/encoding/"" xmlns:xsi=""http://www.w3.org/2001/XMLSchema-instance"" xmlns:xsd=""http://www.w3.org/2001/XMLSchema"" xmlns:vbox=""http://www.virtualbox.org/"">
	<SOAP-ENV:Body>
		<SOAP-ENV:Fault>
			<faultcode>SOAP-ENV:Client</faultcode>
			<faultstring>VirtualBox error: rc=0x80bb0005 Could not launch the VM process for the machine 'myvm01' (VERR_ENV_INVALID_VAR_NAME) (0x80bb0005)</faultstring>
			<detail>
				<vbox:RuntimeFault>
					<resultCode>-2135228411</resultCode>
					<returnval>692d166c1e430875-0000000000000005</returnval>
				</vbox:RuntimeFault>
			</detail>
		</SOAP-ENV:Fault>
	</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
}}}


I am able to start the VM without messages via the GUI and with 
""vboxmanage startvm myvm01""

It does not look like any messages are added to the VM's log file, and the only thing added to VBoxSVC.log is


{{{
01:40:03.911204 nspr-3   ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={85632c68-b5bb-4316-a900-5eb28d3413df} aComponent={MachineWrap} aText={Could not launch the VM process for the machine 'myvm01' (VERR_ENV_INVALID_VAR_NAME)}, preserve=false aResultDetail=-752
}}}


All my soap calls to create the VM, query the power state, and power off the VM function.  My code did work as expected on version 5.1.

I also got the error on 6.1.14 and 6.1.12, I was unable to test prior versions due to compile errors when compiling the kernel modules.  I'm running on Ubuntu 20.04 with the ""virtualbox-6.1_6.1.16-140961~Ubuntu~eoan_amd64.deb"" package downloaded from virtualbox's downloads.

My code can be found at:
https://github.com/T3kton/subcontractor_plugins/tree/master/subcontractor_plugins/virtualbox

the power on function is at:
https://github.com/T3kton/subcontractor_plugins/blob/master/subcontractor_plugins/virtualbox/client.py#L182

Thanks"	pnhowe
16056	Button for mini toolbar is present on host taskbar	all	VirtualBox 5.1.6	2016-10-10T16:17:20Z	2016-10-10T16:17:20Z	2016-10-10T16:17:20Z	"Host: Lubuntu 16.04 x86-64

I have a VM in full-screen mode, with mini toolbar auto-hiding at the top of the screen. When I minimise or Alt-Tab out of the VM so the host desktop is visible, there are two buttons on the host taskbar: one represents the running VM:
""vm_name [Running] - Oracle VM VirtualBox""

The second taskbar button seems to be for the mini toolbar:
""VirtualBox""

Would it be possible to have the mini toolbar *not* have its own taskbar button? It seems useless and just wastes space. Clicking it restores the VM, just like clicking the VM's taskbar button."	Donuts
18583	building virtualbox without opengl on server without X11	other	VirtualBox 6.0.6	2019-04-20T05:50:31Z	2020-10-03T08:32:39Z	2020-10-03T08:32:39Z	"since version 6.0.x me cannt build virtualbox on server for headless use.
last version running is 6.0.0_rc1.
glx.h can not be found --- is there new flag or a bug ???

regards"	WMOE
20363	building kernel modules on a multiarch host fails	other	VirtualBox 6.1.22	2021-05-13T15:17:30Z	2021-05-13T15:17:30Z	2021-05-13T15:17:30Z	"In the Makefile-header.gmk of the three actual kernel modules, the BUILD_TARGET_ARCH_DEF variable, that reflect in BUILD_TARGET_ARCH, the actually used one, is set by the shell command 
$(shell dpkg-architecture -qDEB_HOST_GNU_CPU)
But on a multiarch environment is perfectly sane having a 32 bit version of dpkg-architecture, even if running a 64 bit kernel or building for a 64 bit kernel installed but not running at the moment of building.
In such a case, the build fails because BUILD_TARGET_ARCH is set to i686.
Maybe it's a bug in dpkg, but please consider using a different method to find the target kernel architecture.
Regards
Claudio"	Claudio Laurita
20878	Building kernel module fails on CentOS8 and Kernel 5.17	all	VirtualBox 6.1.32	2022-03-23T08:28:45Z	2022-04-06T06:49:22Z	2022-04-06T06:49:22Z	"Had running VB6.1.32 under kernel 5.16. Reboot triggered after installing kernel 5.17. Build kernel driver failed with error.


{{{
Building the main VirtualBox module.
Error building the module:
make V=1 CONFIG_MODULE_SIG= CONFIG_MODULE_SIG_ALL= -C /lib/modules/5.17.0-1.el8.elrepo.x86_64/build M=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 -j16 modules
make[1]: warning: -j16 forced in submake: resetting jobserver mode.
/bin/sh: -c: line 0: syntax error near unexpected token `('
/bin/sh: -c: line 0: `if [ ""gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-10)"" != """"gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-4)"""" ]; then \'
make[1]: *** [Makefile:1717: prepare] Error 1
make: *** [/tmp/vbox.0/Makefile-footer.gmk:117: vboxdrv] Error 2

}}}
"	HRZ d. Universität Bielefeld
11476	build time dependences not documentend in debian control file	all	VirtualBox 4.2.6	2013-02-09T05:09:56Z	2013-02-09T05:11:26Z	2013-02-09T05:11:26Z	"building from a svn copy (4.2.51~svn-1) in a debian wheezy with vanilla 3.6.7 stable kernel.

packages that are needed to build virtualbox but are not indicated at build environment check time, so dpkg-buildpackage does not complain while they are not installed and build ends up failing later:

libdevmapper-dev
makeself 

also, linux-headers-generic is obsoleted and uninstallable in wheezy so I have benn forced to build vbox with 
dpkg-buildpakage -d"	AlejandroAmo
20210	BUG: unable to handle page fault for address: 00007efdf3ddc000	all	VirtualBox 6.1.18	2021-02-20T23:15:31Z	2021-12-07T20:23:15Z	2021-12-07T20:23:15Z	"Virtualbox panic and freeze VM.
Ubuntu 20.04
5.11.0 mainline kernel"	freetestuser
17727	Bug In VirtualBox in 5.2 Latest Version	Windows	VirtualBox 5.2.10	2018-05-02T10:33:08Z	2018-05-02T22:28:33Z	2018-05-02T22:28:33Z	"Hi I am using the latest version of Virtual box. When I am trying to reverting the snapshot and starting it showing me the VM has aborted error. But if I am executing normally. without reverting the snapshot it running the VM. 

I am using CentOS7 has host machine.
and my guest machine is Windows 7
.
Kindly fix this issue.
I am also attaching the log file."	seantree
21062	BUG in updating Nat Network configuration: parameter Network CIDR	Windows	VirtualBox 6.1.36	2022-08-14T19:28:06Z	2022-08-14T19:28:06Z	2022-08-14T19:28:06Z	"Changing the parameter Network CIDR does not affect the correct configuration of the DHCP server active on the NAT network.
The IP address of the DHCP server and the range of addresses served are not updated.

For the walkthrough see my post on Forum

https://forums.virtualbox.org/viewtopic.php?f=7&t=106799 "	sagypt
16236	Bug in the vboxdrv module (rtR0MemAllocEx) on Linux 4.8.8+ (grsecurity)	other	VirtualBox 5.1.10	2016-11-27T16:41:52Z	2016-12-07T03:02:27Z	2016-12-07T03:02:27Z	"Hi, I'm a Gentoo user, I've a custom kernel. Both with 4.8.8 and 4.8.10 I get the following error when I try to start a virtual machine. I'm using VirtualBox 5.1.10.

Here's the VirtualBox error message:

{{{
Failed to open a session for the virtual machine '...'.

The virtual machine '...' has terminated unexpectedly during startup because of signal 11.

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
}}}

From dmesg:

{{{
[  367.948576] ------------[ cut here ]------------
[  367.948664] kernel BUG at ./arch/x86/include/asm/irqflags.h:26!
[  367.948752] invalid opcode: 0000 [#1] SMP
[  367.948794] Modules linked in:  vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O)
[  367.949080] CPU: 4 PID: 4724 Comm: VirtualBox Tainted: G           O    4.8.10 #1
[  367.949156] Hardware name: 
[  367.949225] task: ffff880818dc6400 task.stack: ffff880818ed4000
[  367.949292] RIP: 0010:[<ffffffff820409e5>]  [<ffffffff820409e5>] _raw_spin_lock_irqsave+0x25/0x30
[  367.949382] RSP: 0018:ffff880818ed7a90  EFLAGS: 00050206
[  367.949431] RAX: ffff8808823fba00 RBX: 0000000000040246 RCX: ffff8808823fbb50
[  367.949494] RDX: ffff8808823fba90 RSI: 0000000000000002 RDI: ffff8808823fbde0
[  367.949557] RBP: ffff880818ed7a98 R08: ffffea001f3c6220 R09: 0000000000706231
[  367.949635] R10: 0000000000000000 R11: 0000000000000002 R12: ffff8808823fc400
[  367.949698] R13: ffff880818ed7c38 R14: ffff8808823fba00 R15: 0000000000003360
[  367.949762] FS:  00007f9e1b0bb700(0000) GS:ffff880882100000(0000) knlGS:0000000000000000
[  367.949834] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[  367.949885] CR2: 00005576006e5000 CR3: 00000008059b9000 CR4: 00000000003606f0
[  367.949963] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[  367.950026] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[  367.950088] Stack:
[  367.950110]  0000000000000002 ffff880818ed7b70 ffffffff812475b4 ffffea001fb99380
[  367.950192]  00000001024280ca ffffea002138a780 ffff880818ed7b80 ffffffff8129e1bf
[  367.950286]  fffffffffffffffc 024080c0024280ca 0000001100400190 0000000000000100
[  367.950373] Call Trace:
[  367.950405]  [<ffffffff812475b4>] get_page_from_freelist+0x4d4/0xaa0
[  367.950465]  [<ffffffff8129e1bf>] ? get_partial_node.isra.71+0xdf/0x210
[  367.950541]  [<ffffffff8124807e>] __alloc_pages_nodemask+0x15e/0xe20
[  367.950601]  [<ffffffff812beee4>] ? lookup_fast+0xe4/0x2f0
[  367.950652]  [<ffffffff812473bc>] ? get_page_from_freelist+0x2dc/0xaa0
[  367.950714]  [<ffffffff81293738>] alloc_pages_current+0x98/0x140
[  367.950781]  [<ffffffff81266f79>] kmalloc_order_trace+0x29/0xe0
[  367.950841]  [<ffffffff8129ff23>] __kmalloc+0x1d3/0x220
[  367.950908]  [<ffffffffa002bfc0>] ? rtR0MemAllocEx+0x170/0x240 [vboxdrv]
[  367.950984]  [<ffffffffa002bfc0>] rtR0MemAllocEx+0x170/0x240 [vboxdrv]
[  367.951057]  [<ffffffffa0029d32>] VBoxHost_RTMemAllocTag+0x22/0x50 [vboxdrv]
[  367.951144]  [<ffffffffa0019549>] SUPR0Printf+0x1c9/0x310 [vboxdrv]
[  367.951205]  [<ffffffff812c8c81>] do_vfs_ioctl+0xa1/0x950
[  367.951257]  [<ffffffff812c95a4>] sys_ioctl+0x74/0x80
[  367.951308]  [<ffffffff82040d1f>] entry_SYSCALL_64_fastpath+0x13/0x93
[  367.951375] Code: 84 00 00 00 00 00 55 48 89 e5 53 9c 5b f7 c3 00 00 04 00 75 16 fa 31 c0 ba 01 00 00 00 f0 0f b1 17 85 c0 75 08 48 89 d8 5b 5d c3 <0f> 0b 89 c6 e8 d2 cf 15 ff eb ef 55 48 89 e5 48 83 ec 10 65 48 
[  367.951822] RIP  [<ffffffff820409e5>] _raw_spin_lock_irqsave+0x25/0x30
[  367.951889]  RSP <ffff880818ed7a90>
[  367.976384] ---[ end trace 0f2758158db10a18 ]---

}}}
"	vboxuser123
20322	Bug from Red Hat Bugtracker	other	VirtualBox 6.1.20	2021-04-24T07:40:16Z	2021-04-26T20:37:48Z	2021-04-26T20:37:48Z	"https://bugzilla.redhat.com/show_bug.cgi?id=1952869 

Having some wierd bug with a Fedora VM on an Ubuntu host "	bittin-
18418	Broken display output for guest application entering full screen mode with changed resolution	Windows	VirtualBox 6.0.4	2019-02-06T17:49:34Z	2019-02-06T17:54:29Z	2019-02-06T17:54:29Z	"Steps to reproduce:
1. Install guest OS, install guest addons
2. Have guest OS in maximised window (not full screen)
2. Start application (a game in my case - Heroes of Might and Magic IV, DirectX 9.0c)

Expected result:
Application should be started, due to its lower resolution it should be surrounded by unused area (like when OS boots).

Actual result:
Guest display is broken."	mmikk
5130	"Bridging eth0 needs ""link"" in order to work"	Linux	VirtualBox 3.0.6	2009-10-06T12:30:03Z	2011-01-26T12:41:31Z	2011-01-26T12:41:31Z	"Ran into problem when trying to bridge virtual Ubuntu 9.10 with host Fedora 11 using the distributions VBox-packages. Using NIC eth0 (Thinkpad T61)

In order to get the bridge to work I had to plug in a TP-cable in the host to get ""link"". When cable removed the bridge stop working.

kernel: 2.6.30.8-64-fc11.i586
VBox 3.0.6

I don't have a problem with the issue as there is a easy workaround, but one have to be aware of it."	Niklas Andersson
5747	Bridged Networking on Ethernet and Wireless Bonded interface fails	Windows	VirtualBox 3.1.0	2009-12-14T04:44:54Z	2021-08-11T16:19:10Z	2021-08-11T16:19:10Z	"I am using bonding to enslave eth0 and wlan0 together on a Debian Linux Host.

if the ethernet interface is operating and is the primary (which is what I have as default) the Guest is able to access the network.  if the the wireless interface if the primary the guest cannot access the network.

using NAT works but I need to use a PPTP VPN from the guest but Virtualbox does not support GRE via NAT setup.

My network interfaces looks like this on the host to setup bonding between the wireless and ethernet.


# The loopback network interface[[BR]]
auto lo[[BR]]
iface lo inet loopback[[BR]]
[[BR]]
# Bonding interface[[BR]]
auto bond0[[BR]]
iface bond0 inet dhcp[[BR]]
  bond_mode active-backup[[BR]]
  bond_primary eth0[[BR]]
  bond_miimon 100[[BR]]
  bond_downdelay 200[[BR]]
  bond_updelay 200[[BR]]
  wpa-ssid wifi[[BR]]
  wpa-ap-scan 1[[BR]]
  wpa-psk password[[BR]]
  wpa-scan-ssid 1[[BR]]
  wpa-iface wlan0[[BR]]
  slaves eth0 wlan0[[BR]]"	James Robertson
17405	Bridged Networking Malfunctioning	all	VirtualBox 5.2.4	2017-12-28T01:59:10Z	2018-01-28T17:24:12Z	2018-01-28T17:24:12Z	"'''Host OS:''' Debian 9.3 (Linux)
'''Hypervisor:''' Virtualbox 5.2.4 
'''Guest OS:''' Security Onion (Elastic) Beta 3, Kali 2017.3, and I feel confident in assuming all OS's would have the same issue and I can test others if needed.

'''Situation:''' This week I upgraded my home lab from older versions of the above software, all previously worked on my hardware without issue, but Bridge Mode Networking is now failing to connect to SOME online resource and has dropped packets when it does connect. However NAT Mode Networking allows access to all online resources without issue.

'''Guest Configuration:''' My SecurityOnion Guest VM has a Bridged Adapter connection on Network Adapter 1, giving it internal vm network and external network access / Network Adapter 2 is listening in promiscuous mode on my switch's Mirrored Port.

Upon installing the guest OS (SecOnion) I began having issues pulling updates from the ubuntu.com software repositories. This was odd because on my host machine Speedtest.net was saying I had a 60+mbps connection to my ISP and furthermore my host machine was able to access ubuntu.com and pull down the same repositories without issue, this is what led me to verifying that I can use NAT but not Bridged Mode. NAT does allow me to access all resources (and update the systme), but I need to use Bridge Mode for my lab.

What's REALLY odd is that even with Bridge mode in its limited capacity, it IS able to pull down Google.com, Wikipedia.com, even Reddit.com with little issue (It does seem like it doesn't fully resolve any of the webpages though -spinning tabs and whatnot). But it completely fails to access Ubuntu.com, Fedora.com, Amazon.com... It's just VERY odd behavior... and it only happens in the VM when using Bridged Mode.

This behavior is repeatable (unable to access ubuntu.com and others) and happens every time I've tried to build a VM on this newer software.

Please let me know if there is any additional information I can provide.

-J

"	Id1010terror
13947	bridged networking broken for Windows 8.1 guest	Windows	VirtualBox 4.3.24	2015-03-09T21:20:21Z	2015-03-12T14:13:44Z	2015-03-12T14:13:44Z	The windows 8.1 guest diagnostics don't see a problem with the bridged connection, but web browsers are unable to connect to any URL. If the adapter (Intel Pro 1000 desktop) is set to NAT in the Linux host then the connection is ok (browsers are able to connect). This problem also existed for version 4.3.18. Windows 7 guests do not have this problem.	nbi
21075	Bridged network doesn't work on WiFi interface on Ubuntu jammy with kernel 5.15.0-46	Windows	VirtualBox 6.1.36	2022-08-24T08:30:11Z	2022-08-24T08:30:11Z	2022-08-24T08:30:11Z	"Upon upgrading to jammy and using latest kernel 5.15.0-46 the bridged networking on WiFi interface stopped working - host (Windows 10 ENT 64bit). It works fine if I manually switch to 5.13.0-52 kernel.

The difference I spotted is when I list interfaces is that the WiFi is listed as not WiFi:

{{{
vboxmanage list bridgedifs
Name:            wlp3s0
GUID:            33706c77-3073-4000-8000-340286543f76
DHCP:            Disabled
IPAddress:       192.168.1.9
NetworkMask:     255.255.255.0
IPV6Address:     fe80::2421:bd44:a0a3:b042
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 34:02:86:54:3f:76
MediumType:      Ethernet
Wireless:        No
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-wlp3s0

Name:            enp0s25
GUID:            30706e65-3273-4035-8000-68f7289e3ac5
DHCP:            Disabled
IPAddress:       0.0.0.0
NetworkMask:     0.0.0.0
IPV6Address:     
IPV6NetworkMaskPrefixLength: 0
HardwareAddress: 68:f7:28:9e:3a:c5
MediumType:      Ethernet
Wireless:        No
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-enp0s25
}}}
"	rskolnik
13369	Bottom toolbar is displayed incorrectly	Windows	VirtualBox 4.3.16	2014-09-11T06:24:25Z	2015-02-13T12:39:42Z	2015-02-13T12:39:42Z	"After updating VB to version 4.3.16, bottom toolbar on my guest Windows is displayed incorrectly (see attachement).
Toolbar appear in wrong place (above the Windows toolbar and above my system toolbar). It also exist even when I minimize the VB window.

To trigger the toolbar, I need to place mouse pointer in the edge of the system toolbar what is wrong also.

I'm working on full screen with two monitors. In previous version the toolbar was displayed correctly.

Host system:
Linux mateusz 3.13-1-amd64 #1 SMP Debian 3.13.10-1 (2014-04-15) x86_64 GNU/Linux

Guest system:
Windows 7 Professional x64 with all updates"	mmaj
15258	booting issue	Linux	VirtualBox 5.0.16	2016-03-21T17:53:10Z	2016-03-22T10:29:14Z	2016-03-22T10:29:14Z	"i installed kali as VM 
every time i boot it : i get black screen with Loading , Please wait 

which never goes away "	zee.21
16685	Booting error (VINF_EM_DBG_HYPER_ASSERTION / raw mode)	Windows	VirtualBox 5.0.32	2017-04-22T05:37:09Z	2017-04-24T16:16:30Z	2017-04-24T16:16:30Z	When booting getting a critical error.  This happens at the start up of the virtual session	Brett
15758	Blinking displays on Windows guests with DWM (10, Vista, 7, 8.x)	Windows	VirtualBox 5.1.2	2016-08-07T11:21:23Z	2019-05-15T10:51:49Z	2019-05-15T10:51:49Z	"Hi,

I've remarked that since VirtualBox 5.0 (and further versions) any Windows guest with DWM has a very annoying blinking effect. It's very proeminent on Windows 10, 7 and Vista guest, much less on Windows 8 guests.

This problem appears especially once Firefox has been started in the guest, but also with Windows 10 start menu or if you start CCleaner in Vista with admin privileges. It is also much more likely to occur if you start the VM, then switch to another host window, and then switch back to the VM window.

Under Windows 10 you can also the problem when starting Age of Empires 3 in the guest.

Note that w/ VirtualBox 4.x such blinking problem did not appear.

Guests affected :
Windows 10 x64, Windows 8.1 x32, Windows 7, Windows Vista, all with guest additions 5.1.2 installed.
256 MB of VRAM allocated to each VM.
All updates installed to each VM.

Host :
Debian GNU/Linux Jessie 8 stable with all updates installed, including backports (Kernel 4.6.74). Arch AMD64
NVidia binary driver 367.27 (but actually the issue also appeared with older versions of the driver incl. 352.xx)
Intel Core i7 4790 (not overclocked)
32 GB system RAM
NVidia GeForce GTX 1070 (but the issue also occured when I have a GTX 970)"	gojul
6465	Blackberry synchronization appears broken => Fixed in SVN	Windows	VirtualBox 3.1.4	2010-03-30T19:21:28Z	2017-02-26T04:17:27Z	2017-02-26T04:17:27Z	"Host Debian Lenny 64 bit, client Windows XP SP3.

Blackberry synchronization works fine in VB 3.0.2. Since then, I've tried VB versions 3.0.4, 3.0.6, 3.0.8, 3.1.2 and 3.1.4 and the Blackberry USB support fails in various ways, some quite comical, so I revert back to VB 3.0.2."	George R. Young
19906	Black Screen after trying to log onto to Kali Linux	Linux	VirtualBox 6.1.14	2020-09-21T01:28:21Z	2020-10-09T13:06:33Z	2020-10-09T13:06:33Z	"So recently I have been trying to log back into my Kali Linux virtual machine in virtual box. But so far, after I sign in to with my username and password , it cuts to a black screen. How do I fix this? I have screenshots inside that kali linux that I desperately need... 

Please help.. I tried to use some ways to fix it but I can't.. I desperately need that information before something happens to it."	MrFrank
13792	Bidirectional clipboard not working host->guest under certain circumstances (see text)	Windows	VirtualBox 4.3.20	2015-01-27T14:40:53Z	2015-02-27T11:18:21Z	2015-02-27T11:18:21Z	"Host: Debian jessie, VirtualBox 4.3.20
Guest: Windows 7, with guest additions 4.3.20, bidirectional clipboard activated

When host has text in clipboard, then VM is started and trying to paste the text in VM, it will not work.
If text is copied to clipboard on host *after* VM start, it will work.

Step-by-step instructions:

*** NOT working ***
1. HOST: Copy text 'abc' to clipboard (using mousepad and CTRL-C or right-click menu)
2. HOST: Start VM
3. VM: Start Notepad
4. VM: Press CTRL-V or choose Edit->Paste from menu (which is *not* greyed out, i.e. there should be sth. in clipboard)
4a. VM: *DOES NOT WORK* (nothing pasted)
5. HOST: Paste in mousepad
5a. HOST: *DOES NOT WORK* (nothing pasted)
REMARK: Obviously, the clipboard seems to be cleared when the VM started
6. HOST: Copy text 'abc' to clipboard {again, as in 1.}
7. HOST: Paste in mousepad
7a. HOST: => *WORKS*
8. VM: Paste in Notepad
8a. VM: *DOES NOT WORK* (nothing pasted)
9. VM: Copy text 'xyz' to clipboard
10. VM: Paste in Notepad
10a. VM: => *WORKS*
11. HOST: Paste in mousepad
11a. HOST: => *WORKS*
12. Shutdown Guest OS


*** working ***
1. HOST: Start VM
2. VM: Start Notepad
3. HOST: Copy text 'abc' to clipboard
4. VM: Paste in Notepad
4a. VM: *WORKS*
5. VM: Copy text 'xyz' to clipboard
6. HOST: Paste in mousepad
6a. HOST: *WORKS*
7. Shutdown Guest OS
"	hmickler
19028	Bad 3D display in Virtualbox 6.0.14	all	VirtualBox 6.0.14	2019-10-18T17:24:53Z	2020-03-13T23:21:36Z	2020-03-13T23:21:36Z	"I have a terrible 3D display in some of my VMs on my Ryzen 3 2200G with Host Ubuntu 19.10/Linux 5.3.0-18 using Virtualbox 6.0.14. I did not have those problems with Ubuntu 19.04/Linux 5.0 and Virtualbox 6.0.12.
- Windows 7, half the time the screen is unreadable after booting, the screen is black with say 2"" of horizontal display of a part of the screen.
- Ubuntu 16.04, the top bar and unity dock are completely garbled.
- Ubuntu 19.10, the wall paper is covered by a strange pattern of blocks. 
All other VM are correct, Xubuntu 18.04, Windows XP, Ubuntu Mate 19.04, Xubuntu 19.10, Ubuntu Mate 19.10, Linux Mint, Peppermint and Windows 10.

Currently I had to switch of the 3D acceleration for those 3 VMs."	BertiN45
19587	Awful Linux Guest Performance	Linux	VirtualBox 6.1.6	2020-05-15T10:45:54Z	2020-05-15T11:02:43Z	2020-05-15T11:02:43Z	"I just tested 64bit VBox 6.0.20 and 6.1.6 with a 64bit Linux guest on a 64bit Linux host (updating Guest Additions each time). Started at 6.0.20, performance was fine. Upgraded to 6.1.6, performance was so bad that the VM is unusable. Downgraded back to 6.0.20, performance is normal. So, VBox 6.1 is broken for Linux guests because of the awful performance.

Host: Intel Core i7 (1st gen) 28G RAM
Guest: 2 cores, 4G RAM

Logs for both the broken 6.1.6 guest and the working 6.0.20 guest are attached.

I ran this test because a user on a FB group had perf issues with a 64bit Linux guest. After I suggested that he downgrade to 6.0.20, his perf is back to normal.
"	Tom3.14159
14098	Automated kernel modules recompilation	Windows	VirtualBox 4.3.26	2015-05-07T11:26:13Z	2015-05-07T11:33:06Z	2015-05-07T11:33:06Z	"Whenever the host OS is updated (in my case Ubuntu), VirtualBox is not able to start my VM and brings up a weird error. A popup then appears prompting me to do `sudo /etc/init.d/vboxdrv setup`

If VirtualBox knows that this is needed, why doesn't it just do it itself? Maybe just showing a prompt with a more user-friendly message saying 'VirtualBox needs to recompile its kernel modules, probably due to a recent OS system update. Confirm?' and the user just presses OK and its done automatically?

At the moment this process is really annoying:
1. You have to copy the command to run from the message box.
2. You have to open a terminal window and paste it but NOT press enter, since Virtual Box is still running. If on the other hand you close Virtual Box before pasting the clipboard info is lost.
3. Close VirtualBox
4. Press enter, wait for Kernel module recompilation.
5. Start VirtualBox.

This could immensely be simplified from a user point of view if when the message is shown and the user confirms, VirtualBox automatically closes, recompiles the kernel modules and restarts.



"	jbx
19442	Autoformat pasted MAC address on adapter configuration dialog	Linux	VirtualBox 6.1.4	2020-03-28T08:15:33Z	2021-02-16T00:58:27Z	2021-02-16T00:58:27Z	"For my home lab, I usually use the same MAC addresses for creating my VMs after reinstalling the host (bridged adapters)

To set the VMs up faster, I want to be able to copy-paste that information from my static DHCP config file to the MAC address field. The format in the DHCP config file is like AA:BB:CC:DD:EE:FF but VBox does not accept the "":"" character. When pasting such a string with CTRL+V into the MAC address field, it should accept the string and automatically remove the "":"" characters"	prischnikov
15863	Auto-Resize is broken with tiling window managers	Windows	VirtualBox 5.1.4	2016-08-30T07:19:15Z	2020-11-19T13:26:17Z	2020-11-19T13:26:17Z	"I run Archlinux with i3wm, installed VirtualBox via pacman (virtualbox).  A recent update has caused nasty behavior around window sizing for guests: using the ""auto-resize"" feature is completely broken. The window is now resized to some seemingly arbitrary size, and I cannot override it (it just resizes right back). It also cannot be auto reassigned to a specific workspace.

"	amosb
19183	Auto-resize feature not working	Linux	VirtualBox 6.1.0	2019-12-23T12:53:14Z	2019-12-31T14:35:14Z	2019-12-31T14:35:14Z	"VBox 6.1.0 – Version 6.1.0 r135406 (Qt5.9.5)

Host: Ubuntu 18.04; 4.15.0-72-generic #4.15.0.72.81

Guest: Manjaro Linux 18.1.4, 4.19.88-1-MANJARO

Guest: VBoxSVGA; Guest Additions 6.1.0

Enabling ›auto-resize‹ in guest window (›View‹ – ›Auto-resize Guest Display‹) has no effect. Manual resizing of display works fine."	phaidros
3500	Auto startup and shutdown for VMs	other	VirtualBox 2.1.4	2009-03-05T10:24:05Z	2017-09-19T08:32:39Z	2017-09-19T08:32:39Z	It would be good to have an option to allow (headless ?) VMs to be started automatically on host boot and gracefully shut down when the host shuts down. I know that scripts exist, but configuring this in an easy and uncomplicated way via the GUI would be a great enhancement.	mark_orion
18064	Audio/Video out of sync for Linux guest (since 5.2.20)	Linux	VirtualBox 5.2.20	2018-10-20T14:55:24Z	2019-03-26T03:15:54Z	2019-03-26T03:15:54Z	"Host: Ubuntu 16.04
Guest: Ubuntu 16.04

Playing video (e.g. in FF Browser on YouTube) always has audio out of sync (audio lagging behind).
Problem is reproducible.

The problem is NOT present for Windows 10 guests on same host system.

The problem was NOT present on VBox 5.2.18 and has been introduced with VBox 5.2.20."	sunrider
17514	Audio stops working on Windows 7 guest	Windows	VirtualBox 5.2.6	2018-01-31T17:19:50Z	2018-01-31T18:35:26Z	2018-01-31T18:35:26Z	"Hello,
I am running VirtualBox 5.2.6 on Ubuntu 16.04 with Windows 7 guest. When I launch GoToMtg and connect to a conference using computer audio, it starts sound starts to crackle then stops completely. I am using a headset.

This worked flawlessly in 5.1.<latest>

I have an almost identical system, exact same problem on 5.2.6"	KLN
18600	Audio input gets automatically enabled	Windows	VirtualBox 6.0.6	2019-04-26T08:15:34Z	2019-04-26T17:26:28Z	2019-04-26T17:26:28Z	"I have a Windows 10 Guest for which I would like to disable audio input (not output), I have used the settings and the menu options to disable audio input several times but it always seems to get re-enabled automatically after closing and opening VirtualBox.

Host: Fedora 29 with VirtualBox 6.0.7 r130207 (test build)
Guest: Microsoft Windows 10 Pro (Version 10.0.17134 Build 17134) with latest Guest Additions installed

Happy to provide more information :)"	Damon Harris
18349	Audio getting muted in screen reader installed on Windows 10 guest (Virtualbox 6.0.2)	Windows	VirtualBox 6.0.2	2019-01-22T17:45:46Z	2019-01-22T17:45:46Z	2019-01-22T17:45:46Z	"I've upgraded recently from Virtualbox 5.2.6 to 6.0.2 - Archlinux is the host and Windows 10 the guest system. As I'm totally blind, I use a screen reader to access the computer (NVDA 2018.4.1 installed on the guest). Both virtualbox-ext-oracle and guest additions are up to date.

After upgrading I noticed that the screen reader gets muted for a while and starts speaking again. The problem happens suddenly and frequently. When it gets muted and I switch to the host window and go back to the guest, it starts speaking again and after some seconds (or minutes) the problem repeats.

I've already confirmed that the problem isn't related to the screen reader; its commands continue working even when it is muted and there are no logs showing a NVDA crash. Initially, I thought that the entire audio was being affected by the problem, but when I play a video (from Youtube, for example) in background and continue to use the screen reader, surprisingly the issue doesn't happen (after stopping the video the problem back to arise as before).

Are you aware about some known issue that may be related to the aforementioned problem?"	alan-ghelardi
16105	Audio capture for multiple VMs problem since 5.0 version	other	VirtualBox 5.1.8	2016-10-22T14:31:49Z	2018-02-14T10:18:47Z	2018-02-14T10:18:47Z	"I have 3 virtual machines, all with android x86 image, and using audio input device for capturing audio.
On host machine I run linux and using pulseaudio.
After booting up the VM, it's up with sink name same ""Virtualbox"", when I booting up second VM it also starts with sink name ""Virtualbox""...(I see it in pavucontrol application on Inputs tab).
No possibility to apply separate inputs for different VMs(because all of them has same name of sink in pavucontrol).
Also no possibility to change sink name, because starting from version 5.0 all VMs starts with sink name ""VirtualBox"", in alder versions(4.3.40 for examle) VM create the sink name same as vertual machine name.
No workaround for this problem, only rollback to version 4.*"	antonIO
15853	audio and video out of sync on Ubuntu 16.04.1	Linux	VirtualBox 5.1.4	2016-08-23T18:21:45Z	2017-10-30T10:52:29Z	2017-10-30T10:52:29Z	"Audio and video are out of sync when a youtube video is playing.
Behaviour noticed in a topic of VirtualBox forum: [https://forums.virtualbox.org/viewtopic.php?f=3&t=79360]

My original issue concerned the fact that the Linux guest was unable to reproduce all media contents. In the forum I was suggested to change the Audio Controller, solution that solved the issue.

However @Perryg noticed that audio and video are out of sync and suggested to open this ticket.

My Linux host  is Ubuntu 14.04 LTS, 5,7 GB of total memory
My Linux guest is Ubuntu 16.04.1 LTS, 2 GB of memory and 50 GB of fixed-size file as virtual hard disk.

I attach two log files:

VBox1.log file concerning my original issue posted to the forum
Vbox2.log file recording the reproduction of a youtube video and the reproduction of the same video with videos application."	jrkul
19297	Attempting to set up virus protection	Windows	VirtualBox 5.2.34	2020-02-09T02:37:12Z	2020-02-09T07:56:32Z	2020-02-09T07:56:32Z	After a very long set up process to get windows 7 pro 32 bit running and finally see my usb drive, I encountered a fatal error when attempting to set up bitdefender virus protection within virtualbox running under feren (ubuntu 18.04 variant).  The software tells me to send you these two files for your review.  Hope you can clear up what is going on here as I a now unable to proceed any further with Virtualbox.	Tripleripple
17028	ata2.00 exception Emask 0x0 SAct 0x0 SErr action	Linux	VirtualBox 5.1.22	2017-08-21T06:25:54Z	2017-08-21T09:50:55Z	2017-08-21T09:50:55Z	"Hi

Every alternate day on Guest VM running with RHEL 6.5 64bit cpu usage is high and after reboot it shows this error
 
ata2.00 exception Emask 0x0 SAct 0x0 SErr action  on 0x6 is frozen

attached screen shot for more details[[Image()]]"	prabhakarraksan
19641	Assigning more vCPU (within the physical core limits) causes random freezes on guests	Linux	VirtualBox 6.1.8	2020-06-07T04:04:45Z	2021-05-19T05:19:07Z	2021-05-19T05:19:07Z	"'''Host Info'''
-------------------
Host: Fedora 32 (64 bit)[[BR]]

CPU: Intel® Core™ i9-9880H CPU @ 2.30GHz × 8 Cores[[BR]]

GPU: Intel UHD-630[[BR]]

HyperThreading: Disabled[[BR]]

Physical Cores: 8[[BR]]

VirtualBox Version: 6.1.8[[BR]]

Display Protocol: X11[[BR]]



'''Guest Info'''
------------------------------
Guest: Debian 10 (Kernel 4.19.0-9-amd64) (Also reproducible in Kubuntu 20.04)[[BR]]

Display Adapter: VMSVGA[[BR]]

3D Acceleration: Enabled[[BR]]

VBox Guest Additions: Installed[[BR]]


----

When I assign 4 cores to the guest, on random starts the guest's animation and scrolling lags. When I checked the Session Information it showed Guest Load about ~0-1% and VMM Load about ~25%. The next restart of the guest doesn't have this behavior. Guest is smooth and doesn't cause pauses.[[BR]]


I tried changing few settings to find the root cause of the issue and surprisingly reducing the CPU count to 1 or 2 fixes the issue. The issue was not reproducible at all.
"	LienCaspari
21500	aRC=VBOX_E_FILE_ERROR (0x80bb0004)	Linux	VirtualBox-7.0.6	2023-02-12T20:13:33Z	2023-02-12T20:21:59Z	2023-02-12T20:21:59Z	"
If the annotations/describing textfield of the machine => <attached pic> grows up to more than 8192 bytes/signs/text and when this machine once is exported as *.ova it will not be possible to import again and use it in Virtalbox


=> ERROR-Notation while refusing to load *.ova  :

ApplRead ERROR [COM]: aRC=VBOX_E_FILE_ERROR (0x80bb0004) aIID={86a98347-7619-41aa-aece-b21ac5c1a7e6} aComponent={ApplianceWrap} aText={Element 'Annotation' exceeds limit of 8192 bytes VERR_BUFFER_OVERFLOW (Buffer too small to save result.)}, preserve=false aResultDetail=0



It will be helpful to reserve enough place for text annotations
in my case I store all notices of buildups for new machines as helpful stepbystep reminders



"	pabel
21499	aRC=VBOX_E_FILE_ERROR (0x80bb0004)	Linux	VirtualBox-7.0.6	2023-02-12T20:12:20Z	2023-02-12T20:12:20Z	2023-02-12T20:12:20Z	"
If the annotations/describing textfield of the machine => <attached pic> grows up to more than 8192 bytes/signs/text and when this machine once is exported as *.ova it will not be possible to import again and use it in Virtalbox


=> ERROR-Notation while refusing to load *.ova  :

ApplRead ERROR [COM]: aRC=VBOX_E_FILE_ERROR (0x80bb0004) aIID={86a98347-7619-41aa-aece-b21ac5c1a7e6} aComponent={ApplianceWrap} aText={Element 'Annotation' exceeds limit of 8192 bytes VERR_BUFFER_OVERFLOW (Buffer too small to save result.)}, preserve=false aResultDetail=0



It will be helpful to reserve enough place for text annotations
in my case I store all notices of buildups for new machines as helpful stepbystep reminders



"	pabel
19331	Any guest crashes with Linux 5.5 as host and VBox > 6.0.0	all	VirtualBox 6.1.4	2020-02-21T12:48:33Z	2020-02-21T15:13:24Z	2020-02-21T15:13:24Z	"Ever since going from VBox 5.x to 6.x, guests are practically unusable because they crash or have other severe problems (corruption of data passed from host to guest, e.g. network data, file data, ...).
Log is attached of one of the cases with a Windows 10 Guest."	Thermi
20021	AMD Ryzen 9 3900XT - Slackware Current64 - kernel 5.9.3-burdi64 - VM's fail to start	Linux	VirtualBox 6.1.16	2020-11-05T16:24:25Z	2020-11-05T16:24:25Z	2020-11-05T16:24:25Z	"Some weeks ago my multi-boot Intel i7-6700 system died on me. From backups I was able to clone things on the AMD Ryzen 9 3900XT replacement. Since then when VB is started under Slackware Current64 all VM's fail to start, whereas when VB is started under Xubuntu 20.04.1 these VM's start as expected.

The failure occurs very early in the start sequence: the big ""starting arrow"" remains shown and the system freezes all over. Sometimes I can start another user session via <Alt+Fx>. Very often a hard restart is required.
The Slackware instance initially ran my own kernel 5.8.14-burdi64, the Xubuntu one kernel 5.4.0-48-generic. During the testing these kernels were upped. At the moment they are 5.9.3-burdi64 and 5.4.0-52-generic respectively. The symptoms however stayed the same.[[BR]]
I started out with VB 6.1.14-140239. Nowadays I test with VB 6.1.16-140961, a preliminary test with VB 6.1.17-141128 shows no discernable effects.[[BR]]
It should be noted that both the Slackware and Xubuntu instances via symlinks refer to the same VM's.

The Slackware ""error"" VBox.log ends with:[[BR]]

{{{
GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated:[[BR]]
 Screen 0 work area is actually resized to: 0x0 x 1920x1173
}}}

while the Xubuntu ""ok"" one contains:

{{{
GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated:[[BR]]
 Screen 0 work area is actually resized to: 0x25 x 1920x1150
}}}


The i7-6700 had embedded video, so used the i915 driver. My Ryzen has a discrete video card -- an ASUS Radeon RX 550 PH-RX550-2G-EVO one:
-- lspci: [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] (rev c7).
supported by the amdgpu driver.

To isolate the problem I did the following tests:[[BR]]
-- I cloned the Slackware instance to an i5 laptop with embedded video: the VM's there started and ran without problems;[[BR]]
-- Back on the AMD box I replaced my 5.9.3-burdi64 kernel with Slackware's stock 5.4.74 one: the VM's started and ran without problems;[[BR]]
-- I upped the Xubuntu kernel to the 5.9.2-050902-generic one from the kernel PPA: the VM's started and ran without problems;[[BR]]
-- I replaced the Xubuntu VB 6.1.16-140961 .deb implementation with the .run one: the VM's started and ran without problems;[[BR]]
-- Back on my Slackware instance I replaced the 5.4.74 kernel with the Xubuntu 5.9.2-050902-generic one: the VM's started and ran without problems.

As said when the problem occurs one often cannot do much more than hard resetting the system. By formally repeating these tests and collecting as much info as possible I found that for the ""error"" case the syslog reports an oops ""unable to handle page fault for address"", the call trace of which starts within vboxdrv.

The Slackware the VBox.logs and the /var/log/messages file as collected are:[[BR]]
-- VBox-59S.log: the ""error"" with my 5.9.3-burdi64 kernel;[[BR]]
-- VBox-54S.log: the ""ok"" with Slackware's stock 5.4.74 kernel;[[BR]]
-- VBox-59U.log: the ""ok"" with the Xubuntu 5.9.2-050902-generic kernel;[[BR]]
-- messages: searching for ""========="" will give you the ""error"" and ""ok"" sections.

It is likely that something in the configuration of my 5.9.3-burdi64 kernel triggers the problem. But which setting is the culprit? My config is 187.4 kB and the Xubuntu one is 248.8 kB. So comparing the two is an almost hopeless endevour ...

Any hints would be appreciated.[[BR]]
:D
"	burdi01
18347	Always NS_ERROR_FAILURE after latest Fedora 29 update	all	VirtualBox 6.0.2	2019-01-22T14:27:25Z	2019-01-24T08:01:39Z	2019-01-24T08:01:39Z	"After Fedora 29 latest update, it's not possible to start any VM in virtualbox.

Kernel version is '''4.19.15-300.fc29.x86_64'''

The message '''The virtual machine '<name>' has terminated unexpectedly during startup with exit code 1 (0x1).''' is always returned with :


{{{
Error code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {5047460a-265d-4538-b23e-ddba5fb84976}
}}}


I've remove VirtualBox and reinstalled it with same problem.

I've remove 6.0.2 and installed 6.0.0 with same problem.

There's no error when ""/sbin/vboxconfig"" is launched.

There's no error when ""/sbin/rcvboxdrvd setup"" command is launched.

And no log is generated in the vms... I have no idea to solve the problem.

Same behaviour for all my VMs (as root or not): Windows, Kali, RedHat."	chla
4939	alt-tab back out of guest doesn't work	Linux	VirtualBox 3.0.6	2009-09-10T13:33:47Z	2010-04-04T02:11:47Z	2010-04-04T02:11:47Z	"Host: Centos 5.3, GNOME 2.16.0
Guest: Ubuntu 9.04, GNOME 2.26.1, guest additions installed

If I alt-tab into a guest window (seamless or not), then alt-tab only works within the guest, letting me switch between windows there but not back out.

I'd like to be able to set a different switch-between-windows hotkey in my guest, say alt-` or alt-esc, so I can alt-tab into it, switch between windows using the guest's hotkey, and then alt-tab back out to my host desktop.

But this doesn't work because alt-tab is still just passed through to the guest, which then just treats it as a tab.

It would be really, really useful to be able to define some hotkeys which are *not* passed through like this... Please! :-)"	Andrew Clegg
13778	Alt+Tab breaks keyboard input	Windows	VirtualBox 4.3.20	2015-01-22T20:57:46Z	2015-01-22T20:57:46Z	2015-01-22T20:57:46Z	"My computer is a Lenovo thinkpad x230. 
Host OS is Fedora 20. 
Guest OS is 64bit Windows 7 Enterprise SP1. 

I can reproduce this bug in 4.3.20_96996_fedora18-1 from the virtualbox yum repo, and the test build 97569. 

Attached is the latest log from the last time I reproduced the bug, these are also the events I describe in this report. 

1. Start guest VM.
2. Open notepad or any input field to test keyboard
3. Type some words. 
4. Press right Ctrl to release keyboard from guest
5. Press alt+tab to switch host OS program, do not release alt
6. Switch back to guest VM with alt+shift+tab
7. Type some words in notepad

Expected result:
Letters from a-z and numbers from 0-9 typed out on screen. 

Result:
The menus activate randomly in notepad, no words are typed. In other programs like Putty I see strange characters being input, sometimes spaces, sometimes returns, never the expected character. In the Windows desktop random functions might be activated, or nothing will happen at all depending on what keys I press from a-z and 0-9 on the keyboard. 

Workaround:
Press left ctrl+alt once and typing is restored. "	stemid
15131	Alt+MouseScroll is broken	Windows	VirtualBox 5.0.14	2016-02-09T19:58:57Z	2016-02-09T19:58:57Z	2016-02-09T19:58:57Z	"From some time [Alt] + Mouse ScrollUp/ScrollDown doesn't work.
I've tested it in Photoshop, Indesign, Corel Ventura in the Windows Guest.
A Scroll itself is working also [Alt] itself is working too.
But the combination/shortcut is broken.
Seems like pressing [Alt] makes a Scrolling non-working.
"	sarbash
4635	Allow remapping of parallel port addresses	other	VirtualBox 3.0.2	2009-07-27T21:36:38Z	2009-07-27T21:36:38Z	2009-07-27T21:36:38Z	"This suggestion is for when VirtualBox properly/offically supports guest access to host parallel port(s).

Some systems cannot have parallel ports which live at the normal/legacy LPT1/2/3 I/O address ranges. It is possible to add hardware parallel ports to such systems, but the port base address is not the normal legacy value. For example, a laptop with no built-in parallel port can be used with a PCI Express-based ExpressCard parallel card. (The PCI Express parallel port cannot live at the legacy LPT1 address range.)

Most well-written software works with such parallel ports, but much older software is hard-coded to only work with the legacy address ranges.

To be able to use such software, VirtualBox needs to remap accesses to the legacy parallel I/O range to that used by the host's parallel port. So in addition to a direct pass-through, an option to set the I/O address range used for the guest's parallel port would be really useful, and should allow use of software which does not work when run in the host OS.
"	Donuts
18413	All VM guests stuck (black screen) and can't be killed - after a USB filter is set	Windows	VirtualBox 6.0.4	2019-02-05T17:00:11Z	2019-02-05T17:00:11Z	2019-02-05T17:00:11Z	"HOST: Linux Mint 19.1/Cinnamon + VirtualBox 5.2.24 first, then 6.0.4
GUESTS: Windows 10 Home, Windows 7 Prof, both worked fine until

I SET a new USB FILTER for Win10 (I am in the vboxusers group)
and then I started Win10 : just a black screen appeared, nothing else.
I could nor stop it, neither kill it from a terminal. Then I even had my Linux host to force to stop with the power button, too.

TESTS
1. After a new Linux host start I started Vbox again (now without any modification) and then Win7 guest. Same result as above.

2. I deleted completely VirtualBox 5.2.24 with all its files, even the VM-s from my laptop, (they were exported not long ago to an external drive). Then I installed VirtualBox 6.0.4 and its Extension Pack, and imported my 2 Windows VMs. They both worked fine again. I installed the apropriate GuestAdditions in both. Still ok. I could work with them well. 
Then I added myself to the vboxusers, rebooted Linux and started VirtualBox again. I set a new USB filter for Win10 and started it. Black screen again which could not be killed, and Linux could not be stopped. 

3. After a new start I tested my Win7 guest as well, neither works it any more. Black screen, stuck, Lx can't be stopped.

I think some Vbox configuration goes bad... I use Vbox since many years, and I do not rememeber similar problem. In a formerly Vbox version I could set USB filters, however I do not remeber the version number unfortunately. Anyhow, I appreciate Vbox very much, it is an excellent work. 

"	JBM
16501	All VM fails when changing dual monitor setup	all	VirtualBox 5.1.14	2017-02-21T13:07:31Z	2017-04-04T16:27:10Z	2017-04-04T16:27:10Z	"Hello, here is what I get when I change the setup several times :
{{{
virtualbox --debug
Gtk-Message: Failed to load module ""canberra-gtk-module""
Qt WARNING: QObject::connect: No such signal QApplication::screenRemoved(QScreen *)
Qt WARNING: QObject::connect: No such signal QScreen::availableGeometryChanged(const QRect &)
Qt WARNING: QObject::connect: No such signal QScreen::availableGeometryChanged(const QRect &)
Qt WARNING: QPainter::begin: Paint device returned engine == 0, type: 2
Qt WARNING: QPainter::end: Painter not active, aborted
Segmentation fault
}}}
All virtualbox VM crashes. 

I'm running debian 8.7 with 4.9 linux kernel. 
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Venus XTX [Radeon HD 8890M / R9 M275X/M375X] (rev 83)
I'm using the radeon opensource driver. The dual monitor is working perfectly except for this issue."	gyust
17802	After upgrade to Fedora 28 mouse not working in VM	Windows	VirtualBox 5.2.12	2018-06-05T10:22:25Z	2018-06-13T20:48:28Z	2018-06-13T20:48:28Z	"Hello all.

After i performed the upgrade to Fedora 28 in my notebook Dell Inspiron 15 Series 5000 (I15-5557-A40), at the Microsoft Windows 10 VM the mouse not working ( i can see the mouse, but the right/left click not working any more). To resolve this, i need to pause the VM and start it again, and by this the mouse click working fine after this process.

I also tried to reinstall the VirtualBox (versions 5.2.12, 5.2.11, 5.2.10), but not worked also.

Please help me in this to resolve"	Cautella
19239	After updating from VB 6.1.0 to 6.1.2. start of guests fails with NS_ERROR_FAILURE (0x80004005)created	Windows	VirtualBox 6.1.2	2020-01-17T13:03:20Z	2020-01-17T13:03:20Z	2020-01-17T13:03:20Z	"Hi,
my host ist Debian bullseye (5.4.0-2-amd64), the guests are Windows 10 (actual version). When I start a guest, I get the error NS_ERROR_FAILURE (0x80004005). The VBOX.Log is attached. Going back to 6.1.0 everything works fine - I have attached the corresponding VBOX.Log.1.

The VBOX.log.1 from version 6.1.0 continues after

""00:00:01.161562 PGM: pgmR3PoolInit: cMaxPages=0x500 cMaxUsers=0xa00 cMaxPhysExts=0xa00 fCacheEnable=true"" 

with 
 
00:00:01.815025 TM: GIP - u32Mode=3 (Invariant) u32UpdateHz=62 u32UpdateIntervalNS=16000000 enmUseTscDelta=2 (Practically Zero) fGetGipCpu=0x1b cCpus=4
00:00:01.815087 TM: GIP - u64CpuHz=2 659 999 145 (0x9e8c5da9)  SUPGetCpuHzFromGip => 2 659 999 145
00:00:01.815102 TM: GIP - CPU: iCpuSet=0x0 idCpu=0x0 idApic=0x0 iGipCpu=0x0 i64TSCDelta=0 enmState=3 u64CpuHz=2659999145(*) cErrors=0
00:00:01.815110 TM: GIP - CPU: iCpuSet=0x1 idCpu=0x1 idApic=0x1 iGipCpu=0x1 i64TSCDelta=0 enmState=3 u64CpuHz=2659999145(*) cErrors=0
00:00:01.815116 TM: GIP - CPU: iCpuSet=0x2 idCpu=0x2 idApic=0x4 iGipCpu=0x2 i64TSCDelta=0 enmState=3 u64CpuHz=2659999145(*) cErrors=0
00:00:01.815124 TM: GIP - CPU: iCpuSet=0x3 idCpu=0x3 idApic=0x5 iGipCpu=0x3 i64TSCDelta=0 enmState=3 u64CpuHz=2659999145(*) cErrors=0
"	Dr. Michael Hälsig
17576	After update vbox guest machines force window decorations even when disabled by window manager	all	VirtualBox 5.2.8	2018-02-28T21:54:25Z	2018-08-26T07:21:32Z	2018-08-26T07:21:32Z	"After VirtualBox was updated last night to 5.2.8 on Debian Testing, guest machines now have window decorations and borders forced even though my window manager (JWM) is set to remove them.

Before last night's VirtualBox update, my window manager rules worked properly.  It appears that something was changed in VirtualBox to cause this."	Will B
17636	After minimising full screen VM, on restoring only quarter of screen shown	all	VirtualBox 5.2.8	2018-03-24T12:39:30Z	2020-09-07T14:16:14Z	2020-09-07T14:16:14Z	"On a Kubuntu host, when running a VM full screen, if I minimise the VM and then restore it, the VM stays in full screen mode but only about a quarter of it is shown.

In the attached screen shot you can see a Xubuntu guest part showing top left on a Kubuntu host.

The problem occurs both with Windows and Linux guest.

The problem has only occurred since the host upgraded to Kubuntu 17.10.

If I alternately minimise/maximise/minimise/maximise/.... on the maximise it alternately fails/works.

Bug originally reported on Launchpad  #1731495

"	ximera
20625	After hardware upgrade OS/2 does not boot	other	VirtualBox 6.1.26	2021-10-22T05:44:13Z	2022-01-25T14:25:45Z	2022-01-25T14:25:45Z	"opensuse tumbleweed 20211012
linux v5.14.9-1-default x86_64
VBox v6.1.26_SUSE r145957

After an hardware upgrade the OS/2 guest has stopped booting. The boot proceeds normally to a point, then simply stops.

Old CPU: AMD Athlon II 4x
New CPU: AMD Ryzen 5 5600x

Mainboard
Old: asus m5a88-m
New: asus tuf gaming b550+
"	James Moe
19954	"after DISabling timesync in VB linux guest's GuestAdditions, boot errors: ""timesync Error: vgsvcTimeSyncWorker: VbglR3GetHostTime failed; rc2=VERR_NOT_SUPPORTED"" ?"	Linux	VirtualBox 6.1.14	2020-10-10T03:37:13Z	2020-10-10T03:37:13Z	2020-10-10T03:37:13Z	"I run
{{{
rpm -qa | grep -i virtualbox
	VirtualBox-6.1-6.1.14_140239_fedora32-1.x86_64

uname -rm
	5.8.13-200.fc32.x86_64 x86_64
}}}

for both host & guests.

I've been having lots of time-sync issues in guests -- large drifts, time jumping forward & backwards, etc.

That's despite running chrony time sync clients in each guest.

After some digging, found this

	https://docs.oracle.com/en/virtualization/virtualbox/6.1/admin/fine-tune-timers.html#disabletimesync

and disabled timesync in clients' GuestAdditions, with
{{{
VBoxManage setextradata ""<vm name>"" ""VBoxInternal/Devices/VMMDev/0/Config/GetHostTimeDisabled"" 1
}}}

Now, on guest reboot, I'm seeing these errors in guest dmesg log,
{{{
dmesg | egrep -i ""timesync|virtualbox""
	[    0.000000] DMI: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
	[    2.123518] usb 2-1: Manufacturer: VirtualBox
	[    2.134288] input: VirtualBox USB Tablet as /devices/pci0000:00/0000:00:06.0/usb2/2-1/2-1:1.0/0003:80EE:0021.0001/input/input5
	[    2.134476] hid-generic 0003:80EE:0021.0001: input,hidraw0: USB HID v1.10 Mouse [VirtualBox USB Tablet] on usb-0000:00:06.0-1/input0
	[   27.809171] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
	[   27.809255] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
	[   57.418443] 02:19:39.352350 timesync Error: vgsvcTimeSyncWorker: VbglR3GetHostTime failed; rc2=VERR_NOT_SUPPORTED
	[   66.602300] 02:19:49.375515 timesync Error: vgsvcTimeSyncWorker: VbglR3GetHostTime failed; rc2=VERR_NOT_SUPPORTED
	[   75.767563] 02:19:59.378440 timesync Error: vgsvcTimeSyncWorker: VbglR3GetHostTime failed; rc2=VERR_NOT_SUPPORTED
	[   84.932750] 02:20:09.381252 timesync Error: vgsvcTimeSyncWorker: VbglR3GetHostTime failed; rc2=VERR_NOT_SUPPORTED
	[   94.098285] 02:20:19.384482 timesync Error: vgsvcTimeSyncWorker: VbglR3GetHostTime failed; rc2=VERR_NOT_SUPPORTED
	[  103.264664] 02:20:29.388593 timesync Error: vgsvcTimeSyncWorker: VbglR3GetHostTime failed; rc2=VERR_NOT_SUPPORTED
	[  112.496162] 02:20:39.463769 timesync Error: vgsvcTimeSyncWorker: VbglR3GetHostTime failed; rc2=VERR_NOT_SUPPORTED
	[  121.658906] 02:20:49.463953 timesync Error: vgsvcTimeSyncWorker: VbglR3GetHostTime failed; rc2=VERR_NOT_SUPPORTED
	[  130.822255] 02:20:59.464766 timesync Error: vgsvcTimeSyncWorker: VbglR3GetHostTime failed; rc2=VERR_NOT_SUPPORTED
	[  139.985037] 02:21:09.464959 timesync Error: vgsvcTimeSyncWorker: VbglR3GetHostTime failed; rc2=VERR_NOT_SUPPORTED
}}}

Clearly 'errors', not warnings ...

Either a bug, or add'l config is needed to fix/silence that^ ..."	pgnd
19394	After anydesk disconnects, mouse use is corrupted	Windows	VirtualBox 6.1.4	2020-03-11T17:24:23Z	2020-03-11T17:24:23Z	2020-03-11T17:24:23Z	On Ubuntu20 using vbox 6.21.4.r136177, running a win10 box, when an AnyDesk user is controlling the box, while they are using it and after they disconnect, the local user of the win10box can't properly use the mouse or enter informaiton via keyboard.  Unable to highlight test or enter information.  Should be able to highlight and enter information.	phelix
10157	Adding vCPUs degrades network performance.	other	VirtualBox 4.1.8	2012-01-11T12:28:32Z	2015-10-12T11:19:25Z	2015-10-12T11:19:25Z	"Observed on both Ubuntu 11.04 (2.6 kernel) and Mac OS X 10.6 hosts, both with quad core Intel i7 CPUs. Below is pasted from my forum post: https://forums.virtualbox.org/viewtopic.php?f=7&t=47136. 

I decided to run some network throughput benchmarks (mainly interested in max packets per second), and have noticed a large discrepancy when assigning one CPU to a VM vs 2 or more CPUs. My setup (all 64-bit):
Host: Ubuntu 11.04 2.6.38-13-generic #53-Ubuntu SMP, 3 GHz Intel i7 950 (4 phys cores + HT), 12GB RAM, Ethernet: Intel 82574L Gigabit
Guest: Ubuntu 11.10 3.0.0-12-server kernel, 1GB Ram assigned
VirtualBox version: 4.1.8 

Following are the results of the basic testing I performed using netserver/netperf against a bridged network interface (bridged to above Intel device). The following commands were run on the Guest against its local interface (not the loopback):
netserver -4 (starts an ipv4 tcp/udp server). 
netperf -H <IP_address_of_eth0> -t TCP_CRR (runs a TCP connect/request/response transaction benchmark) 

Single-CPU VM
~17-18k transactions per second

2-CPU VM
~5k TPS

2-CPU VM with eth0 interrupts and netserver/netperf all pinned to the same core
~7k TPS
Confirmed v. low scheduling interrupts during benchmark (watching /proc/interrupts)

2-CPU VM with 2nd core disabled via hotplugging
Disabled the second cpu with: echo '0' > /sys/devices/system/cpu/cpu1/online and confirmed via /proc/interrupts and other system tools.
~8.5k TPS

Also worth noting that on the host system, the same test yields around 26k TPS. netfilter/conntrack is disabled on both host and guest. 

So even with the second cpu disabled I'm seeing around a 50% performance degradation vs the single-cpu VM. The results with more than 2 CPUs were very similar to the 2-CPU scenario. 

I would like to understand why this is the case (I'm certainly no virtualization expert); are additional extensions/emulations loaded when starting a multicore guest?

Update
I repeated the same test on an OS X 10.6 host on similar architecture (quad core intel i7) and the results were the same, also on VBox 4.1.8. 

I decided to extend the test to something CPU bound and ran a Linpack benchmark (single thread), but the results are unaffected by number of vCPUs (which is good). And so I also ran a a disk read benchmark using hdparm, and this was also unaffected, so this seems to be confined to network performance for now."	james little
16622	Adding an SSD on 2-HD system can confuse drive assignments	Linux	VirtualBox 5.1.18	2017-03-29T18:55:10Z	2017-03-31T15:00:41Z	2017-03-31T15:00:41Z	"Starting with a 2 HD Dell M6800, VB sees the drives as HD1 = sda & HD2 = sdb.

Adding a Samsung EVO 250GB SSD drive caused Linux to assign drives as:
 HD1 = sda, SSD = sdb & HD2 = sdc

My local Mageia Linux install repository resides on HD2p7. This physical source disk was originally defined in DIST[-pt].vmdk as sdb.  After the SSD was installed, VB could not see the installation files because HD2(sdb) was now at sdc.  

Simply editing DIST.vmdk to change the only occurrence of sdb to sdc resolved the problem.

Could this have been overcome by using UUID instead of sdX?
"	Pierre Fortin
13416	Add option to allow VM to swap	Linux	VirtualBox 4.3.16	2014-09-18T09:08:41Z	2014-09-18T09:08:41Z	2014-09-18T09:08:41Z	"Test setup is the following:

 * Host machine: Linux, 16GB RAM, 16GB swap.
 * Guest 1: Linux, 5GB RAM, 2GB swap, 4.5GB ramdisk
 * Guest 2: Linux, 5GB RAM, 2GB swap, 4.5GB ramdisk
 * Guest 3: Linux, 5GB RAM, 2GB swap, 4.5GB ramdisk
 * Guest 4: Linux, 5GB RAM, 2GB swap, 4.5GB ramdisk

Steps to reproduce:
1. Start all 4 VMs.
2. Start growing ramdisk.

When host free RAM is close to zero - VirtualBox will abort one of the VMs. Swap usage on host is still very low.

Please add the option to allow VM to swap, so all of those 4 VMs will be able to work together, even if slower (swap based on SSD disk makes it not so bad)."	indifferent
9054	Add Host CPU/System info to About or other dialog.	Linux	VirtualBox 4.0.4	2011-06-09T21:00:26Z	2012-09-12T09:38:47Z	2012-09-12T09:38:47Z	"Hello, thanks for an awesome project.  I use it for a pre-made LAMP development environment:  http://drupal.org/project/quickstart.

My users are asking me whether they should install the i386 or amd64 version.  

Could you please add a ""System info"" dialog to the Virtualbox host UI?

Basically, CPU info, host OS info, AMD-V/VT-X extensions enabled, etc.  For a  big bonus, ""This system can/can't run a 64-bit guest.""  Other things could be added (3d support, USB, etc) but for now just the 32/64 bit info would be great.

This might seem trivial, but would greatly simplify supporting my users, saving them alot of trouble choosing which guest to download, and helping me help them.

Thanks again for a great project,

Mike
"	MIchael Cole
20106	AC97 possible regression in rev 76862	other	VirtualBox 6.1.16	2020-12-29T10:56:52Z	2021-01-25T12:25:45Z	2021-01-25T12:25:45Z	"I'm investigating why ac97 driver (https://github.com/deadw00d/AROS/tree/alt-abiv0/workbench/devs/AHI/Drivers/ac97) that we created stopped working with VBox. The driver continues working with real hardware and QEMU. After debugging and analysing VBox code I think a regression was introduced in rev 76862 by deleting the ichac97R3StreamFetchBDLE(pThis, pStream); call when setting up LVI register.

What happens now is that CIV register is advanced, but the PICB register is not refreshed (refresh is done ichac97R3StreamFetchBDLE(pThis, pStream)). What then happens is when ichac97R3StreamTransfer() is called, the cbLeft is zero so the whole logic of this function is skipped. The ""hardware"" hangs in mode where DMA is saying its active, Bus Master is enabled but nothing is tranfered. The only way to kick the ""hardware"" again is to set the CR register where the code again advanced the CIV but then calls ichac97R3StreamFetchBDLE() to update PICB. This way however a previous buffer is lost.

There are two places I see possible to change:
- restore the call to ichac97R3StreamFetchBDLE when setting LVI and advancing CIV
- allow ichac97R3StreamTransfer to operate with *initial* empty PICB just like the code in the look (when it sees empty PICB it continues to next buffer)"	deadwood
20288	absurd delay to start virtualization	Linux	VirtualBox 6.1.18	2021-04-04T13:41:19Z	2021-04-04T13:41:19Z	2021-04-04T13:41:19Z	"I tried in many ways to correct this, I installed medications (Oracle_VM_VirtualBox_Extension_Pack-6.1.18)

and also a distribution pack that I use (virtualbox-6.1_6.1.18-142142_Debian_buster_amd64 (1) .deb)

And so far nothing, I use the Linux of the offensive security (https://www.offensive-security.com/kali-linux-vm-vmware-virtualbox-image-download/#1572305786534-030ce714-cc3b) image ready.


I start the machine and leave the computer on, and it went 28 hours without leaving the black screen with the kali logo
"	anjo gelado
19077	A serious error occurred while running a virtual computer with virtualbox	Windows	VirtualBox 6.0.10	2019-11-11T01:08:08Z	2019-11-11T01:08:08Z	2019-11-11T01:08:08Z	Last friday， I use the virtualbox to run an ubuntu virtual machine to build a cross-compilation chain.And then I close the virtual machine.Today when I open it, I get a serious error, and I can't open it success.I have attach the log for this problem	Liyongchun
17651	A critical error has occurred while running the virtual machine and the machine execution has been stopped	Linux	VirtualBox 5.2.6	2018-03-30T11:53:53Z	2018-04-19T20:14:39Z	2018-04-19T20:14:39Z	"While starting new virtual box and choosing to install Ubuntu 32bit OS I received Guru Meditation box stating that ""A critical error has occurred while running the virtual machine and the machine execution has been stopped"".

Log attached."	H88
17631	A critical error	Windows	VirtualBox 5.2.8	2018-03-21T15:20:42Z	2018-03-21T15:20:42Z	2018-03-21T15:20:42Z	"VirtualBox stops with the message ""A critical error has occurred while running the virtual machine and the machine execution has been stopped."" It is random but usually within 10 minutes after the booting. The host is Arch linux and the guest is Windows 10. I attached the log."	asitstands
19367	a crash on resume machine	Windows	VirtualBox 6.1.4	2020-03-01T18:33:44Z	2020-03-21T14:19:51Z	2020-03-21T14:19:51Z	"When i resume machine , i have crash on load 'vga'.[[BR]]
I had executed a opengl application.[[BR]]
Thank.[[BR]]

"	Sizy458
19372	a crash on resume machine	Windows	VirtualBox 6.1.4	2020-03-02T20:36:39Z	2020-03-02T20:39:12Z	2020-03-02T20:39:12Z	"Video mode VBOXSvga dualscreen.[[BR]]
On resume machine i have error loading 'VGA' [[BR]]

link on complete log :[[BR]]

[http://s000.tinyupload.com/index.php?file_id=35541543786314765463]

I join log part.[[BR]]

Information i'am not used opengl application.[[BR]]


thank"	Sizy458
14923	`guestcontrol run` memory leak in host	Windows	VirtualBox 5.0.10	2015-12-12T00:43:40Z	2018-08-28T09:12:25Z	2018-08-28T09:12:25Z	"#14850 is the only other open memory leak I can find.  That looks like a guest side leak associated with disk IO, but this is a host side leak associated with `vboxmanage <name> guestcontrol run`

I'm running an Ubuntu host, and a Windows 7 (all updates installed) guest.  The guest is given 1 CPU and 2GB of RAM, but I can get it to consume >8GB of RAM (enough to have the Linux OOM system kill it).  I verified that the guest stabilizes at using ~650MB of RAM in this case, so the leak is definitely on the host side.  To trigger the leak, I first start my VM:

{{{
ian$ vboxheadless -startvm win-7-pro-loaded-base
}}}

Then I run: 
{{{
ian$ vboxmanage guestcontrol win-7-pro-loaded-base run --username administrator ""C:\\Windows\\System32\\ping.exe"" -- ""-t"" ""localhost"" 2>&1
}}}

You can accelerate the leak by running many of the `vboxmanage` commands in parallel.  With 6 running, the `vboxheadless` process went from using 3GB to 5GB (RES in `htop`) RAM in 12 minutes.

Attached are the VBox.log from one occassion of running this, along with an image of `vboxheadless` memory use over time with 6 `vboxmanage` commands running, and an image of the stabilized guest memory.

I also attached a zip of running:
{{{
sudo strace -i -ff -p <vboxheadless first thread PID> -o strace_output/strace
}}}

for a few minutes while the 6 `vboxmanage` commands were running.

Let me know if there's more information I can supply, or if you'd like me to try anything.  I started along the path of building and running virtualbox from source so I could poke around, but I'm having a few issues.

Thanks in advance for all of your help!"	iano
18042	[X11] Virtual machine window WM_NAME name and class being set too late	all	VirtualBox 5.2.18	2018-10-11T04:29:43Z	2018-10-11T04:39:56Z	2018-10-11T04:39:56Z	"Under X11 VirtualBox sets the virtual machine window's WM_NAME name and class too late, interfering with window manager rules.  ""Too late"" meaning that the virtual machine window has been displayed and handled by the window manager, *then* the WM_NAME name and class is set.

The virtual machine window class was being set correctly with VirtualBox 5.2.6, however all versions thereafter have not worked correctly.

After looking at the code in `src/VBox/Frontends/VirtualBox/src/runtime/UIMachineWindow.cpp void UIMachineWindow::prepare()` it appears the X11 window class-setting code was moved in 5.2.8 from the beginning of the `prepare()` function to the end. This appears to be the root cause of this issue."	Will B
21268	[virtualbox 7.0.2] doesn't work with a Windows 11 guest on an Arch Linux host	Windows	VirtualBox-7.0.2	2022-11-13T13:18:33Z	2022-11-13T13:18:33Z	2022-11-13T13:18:33Z	"Hi,

while downgraded guest additions solved a freeze issue with a Windows 11 guest, USB is broken.

There are no issues with a Windows 7 or a Windows 10 guest.
{{{
$ uname -r; pacman -Q virtualbox
4.19.255-rt113-0.1000
virtualbox 7.0.2-2
}}}
Windows 7

guest never updated to guest additions version 7.0.2r154219
now at version 6.1.40r154048
USB 2.0 enabled does work with my iPads connected by USB

Windows 10

guest updated to guest additions version 7.0.2r154219
now at version 7.0.2r154219
USB 2.0 enabled does work with my iPads connected by USB

Windows 11

guest updated to guest additions version 7.0.2r154219 does cause freezes 
downgraded to guest additions version 6.1.40r154048
now at version 6.1.40r154048 no freezes anymore, but
USB 2.0 as well as USB 1.1 enabled do n o t work with my iPads

For more details, see

https://bugs.archlinux.org/task/76531

https://forums.virtualbox.org/viewtopic.php?f=7&t=107757

https://bbs.archlinux.org/viewtopic.php?id=281196

https://lists.archlinux.org/archives/list/arch-general@lists.archlinux.org/thread/GSDRGWQEULBUM254XGBZLX7NCFWF5FCE/#GSDRGWQEULBUM254XGBZLX7NCFWF5FCE

Regards,

Ralf"	Ralf
20252	[SVN version] compile error under python 3.9: _Py_NewReference was not declared in this scopt	other		2021-03-13T05:36:35Z	2021-08-05T08:38:43Z	2021-08-05T08:38:43Z	"Hi,

I come across a compilation problem for virtualbox svn with __Py_NewReference under Arch Linux and python 3.9.


{{{
/build/virtualbox-svn/src/VirtualBox/src/libs/xpcom18a4/python/src/PyIID.cpp: In constructor ‘Py_nsIID::Py_nsIID(const nsIID&)’:
/build/virtualbox-svn/src/VirtualBox/src/libs/xpcom18a4/python/src/PyIID.cpp:268:2: error: ‘_Py_NewReference’ was not declared in this scope; did you mean ‘_PyWeakReference’?
  268 |  _Py_NewReference(this);
      |  ^~~~~~~~~~~~~~~~
      |  _PyWeakReference
}}}


{{{
/build/virtualbox-svn/src/VirtualBox/src/libs/xpcom18a4/python/src/PyISupports.cpp: In constructor ‘Py_nsISupports::Py_nsISupports(nsISupports*, const nsIID&, PyXPCOM_TypeObject*)’:
/build/virtualbox-svn/src/VirtualBox/src/libs/xpcom18a4/python/src/PyISupports.cpp:148:2: error: ‘_Py_NewReference’ was not declared in this scope; did you mean ‘_PyWeakReference’?
  148 |  _Py_NewReference(this);
      |  ^~~~~~~~~~~~~~~~
      |  _PyWeakReference
}}}


{{{
@g++ -c -O2 -g -pipe -ansi -Wall -Wno-unused -Wno-non-virtual-dtor -Wno-invalid-offsetof -Wno-sign-compare -Wno-unused -Wno-ctor-dtor-privacy -fvisibility-inlines-hidden -fvisibility=hidden -DVBOX_HAVE_VISIBILITY_HIDDEN -DRT_USE_VISIBILITY_DEFAULT -fdiagnostics-show-option -Wno-delete-non-virtual-dtor  -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fno-omit-frame-pointer -fPIC -Wno-write-strings -pthread -m64 -I/build/virtualbox-svn/src/VirtualBox/src/libs/xpcom18a4/python/src -I/usr/include/python3.9 -I/build/virtualbox-svn/src/VirtualBox/src/libs/xpcom18a4/xpcom/build -I/build/virtualbox-svn/src/VirtualBox/src/libs/xpcom18a4/xpcom/ds -I/build/virtualbox-svn/src/VirtualBox/src/libs/xpcom18a4/xpcom/io -I/build/virtualbox-svn/src/VirtualBox/src/libs/xpcom18a4/xpcom/base -I/build/virtualbox-svn/src/VirtualBox/src/libs/xpcom18a4/xpcom/components -I/build/virtualbox-svn/src/VirtualBox/src/libs/xpcom18a4/xpcom/threads -I/build/virtualbox-svn/src/VirtualBox/src/libs/xpcom18a4/xpcom/proxy/src -I/build/virtualbox-svn/src/VirtualBox/src/libs/xpcom18a4/xpcom/reflect/xptcall/src -I/build/virtualbox-svn/src/VirtualBox/src/libs/xpcom18a4/ipc/ipcd/client/src -I/build/virtualbox-svn/src/VirtualBox/src/libs/xpcom18a4/ipc/ipcd/shared/src -I/build/virtualbox-svn/src/VirtualBox/src/libs/xpcom18a4/ipc/ipcd/extensions/lock/src -I/build/virtualbox-svn/src/VirtualBox/src/libs/xpcom18a4/ipc/ipcd/extensions/transmngr/src -I/build/virtualbox-svn/src/VirtualBox/src/libs/xpcom18a4/ipc/ipcd/extensions/dconnect/src -I/build/virtualbox-svn/src/VirtualBox/src/libs/xpcom18a4/ipc/ipcd/extensions/transmngr/common -I/build/virtualbox-svn/src/VirtualBox/out/linux.amd64/release/bin/sdk/bindings/xpcom/include -I/build/virtualbox-svn/src/VirtualBox/out/linux.amd64/release/bin/sdk/bindings/xpcom/include/nsprpub -I/build/virtualbox-svn/src/VirtualBox/out/linux.amd64/release/bin/sdk/bindings/xpcom/include/string -I/build/virtualbox-svn/src/VirtualBox/out/linux.amd64/release/bin/sdk/bindings/xpcom/include/xpcom -I/build/virtualbox-svn/src/VirtualBox/out/linux.amd64/release/bin/sdk/bindings/xpcom/include/ipcd -I/build/virtualbox-svn/src/VirtualBox/src/libs/xpcom18a4/python -I/build/virtualbox-svn/src/VirtualBox/out/linux.amd64/release/obj/VBoxPython3/dtrace -I/build/virtualbox-svn/src/VirtualBox/include -I/build/virtualbox-svn/src/VirtualBox/out/linux.amd64/release -DVBOX -DVBOX_OSE -DVBOX_WITH_64_BITS_GUESTS -DRT_OS_LINUX -D_FILE_OFFSET_BITS=64 -DRT_ARCH_AMD64 -D__AMD64__ -DVBOX_WITH_DEBUGGER -DVBOX_WITH_HARDENING -DRTPATH_APP_PRIVATE=\""/usr/share/virtualbox\"" -DRTPATH_APP_PRIVATE_ARCH=\""/usr/lib/virtualbox\"" -DRTPATH_SHARED_LIBS=\""/usr/lib/virtualbox\"" -DRTPATH_APP_DOCS=\""/usr/share/doc/virtualbox\"" -DMOZILLA_CLIENT=1 -DNDEBUG=1 -D_IMPL_NS_COM -DXPCOM_DLL_BASE=\""VBoxXPCOM\"" -DMOZ_DLL_SUFFIX=\"".so\"" -DIN_RING3 -DVBOX_USE_IPRT_IN_XPCOM -DVBOX_WITH_XPCOM_NAMESPACE_CLEANUP -DMOZ_PRESERVE_PIC -D_IMPL_NS_COM -D_IMPL_NS_BASE -DEXPORT_XPTI_API -DEXPORT_XPT_API -DVBOX_PYXPCOM -DVBOX_WITH_XPCOM -DPy_LIMITED_API=0x03030000 -DOSTYPE=\""Linux2.6\"" -DOSARCH=\""Linux\"" -DXP_UNIX=1 -D_GNU_SOURCE -DHAVE_VISIBILITY_ATTRIBUTE=1 -DHAVE_VA_LIST_AS_ARRAY -DHAVE_VA_COPY -DVA_COPY\(a\,b\)=__builtin_va_copy\(a\,b\) -Wp,-MD,/build/virtualbox-svn/src/VirtualBox/out/linux.amd64/release/obj/VBoxPython3/src/TypeObject.o.dep -Wp,-MT,/build/virtualbox-svn/src/VirtualBox/out/linux.amd64/release/obj/VBoxPython3/src/TypeObject.o -Wp,-MP -o /build/virtualbox-svn/src/VirtualBox/out/linux.amd64/release/obj/VBoxPython3/src/TypeObject.o  /build/virtualbox-svn/src/VirtualBox/src/libs/xpcom18a4/python/src/TypeObject.cpp
kBuild: Compiling VBoxPython3 - /build/virtualbox-svn/src/VirtualBox/src/libs/xpcom18a4/python/src/TypeObject.cpp
/build/virtualbox-svn/src/VirtualBox/src/libs/xpcom18a4/python/src/TypeObject.cpp: In constructor ‘PyXPCOM_TypeObject::PyXPCOM_TypeObject(const char*, PyXPCOM_TypeObject*, int, PyMethodDef*, PyXPCOM_I_CTOR)’:
/build/virtualbox-svn/src/VirtualBox/src/libs/xpcom18a4/python/src/TypeObject.cpp:437:2: error: ‘_Py_NewReference’ was not declared in this scope; did you mean ‘_PyWeakReference’?
  437 |  _Py_NewReference(this);
      |  ^~~~~~~~~~~~~~~~
      |  _PyWeakReference
kmk: *** [/build/virtualbox-svn/src/VirtualBox/kBuild/footer-pass2-compiling-targets.kmk:277: /build/virtualbox-svn/src/VirtualBox/out/linux.amd64/release/obj/VBoxPython3/src/TypeObject.o] Error 1
}}}

I note that there are discussions about removing _Py_NewReference from public API ([https://bugs.python.org/issue40989]). Maybe it is relevant?

Attached is the full log.

"	winstonwu91
21221	[regression][7.0.2?] Windows XP guest has suddenly stopped working and causes VBox Internal Error	Windows	VirtualBox-7.0.2	2022-10-30T16:34:06Z	2022-10-31T15:15:10Z	2022-10-31T15:15:10Z	"All of a sudden my Windows XP guest which I've used for almost a decade without any modifications (I always revert to a snapshot I created back then) has stopped working.

It did work with VirtualBox 7.0.
It probably even worked with VirtualBox 7.0.2 with Linux kernel 5.19.16.
I cannot be sure. I will attach a log file.

I can even send this guest in its entirety to VirtualBox developers if necessary. There's nothing private/personal about it."	Artem S. Tashkinov
15802	[Regression] No microphone, Windows Guest, Linux Host.	Windows	VirtualBox 5.1.2	2016-08-16T20:21:02Z	2018-10-14T12:00:32Z	2018-10-14T12:00:32Z	"Linux Host

Ubuntu 16.04

Kernel 4.7.0-040700-generic

Guest: Windows 8.1 (also appears to affect any other guest)

Audio Controller: Intel HD Audio

Microphone is enumerated by the guest, but it is always silent. On occasions fiddling with microphone driver enumeration (i.e. toggling ""Show unplugged recording devices"" several times, going to its properties, etc) can even crash VirtualBox (rare, happened to me only twice).

PulseAudio shows VirtualBox has requested and received microphone and speaker.
I've also tried the ALSA driver, same result. Couldn't try OSS driver (immediately aborts VM, didn't look much into it; I assumed either I had a missing dependency or the OSS device couldn't be grabbed)

I tried AC97 audio controller but Windows 8.1 won't install drivers for it.

Useful info:
* Problem shows in official virtualbox-5.1_5.1.2-108956-Ubuntu-xenial_amd64 (using matching extension pack & Guest additions)
* Problem persists in test build VirtualBox-5.1.3-110032-Linux_amd64.run (using matching extension pack & Guest additions)
* It works correctly in virtualbox-5.1_5.1.0-108711-Ubuntu-xenial_amd64.deb

More info:

These users seem to be affected by the same problem:
https://forums.virtualbox.org/viewtopic.php?f=7&t=78797"	dark_sylinc
19608	[Patch] Fixed BIOS int 13h, ah=48h	all	VirtualBox 6.1.8	2020-05-21T13:31:13Z	2020-05-21T13:31:13Z	2020-05-21T13:31:13Z	"Patch for VirtualBox 6.1.8. Fixes an impossible condition in «edd_fill_dpt» function, which implements the function 48h of the BIOS interrupt 13h.

{{{
diff -ruN ./VirtualBox-6.1.8{.orig,}/src/VBox/Devices/PC/BIOS/disk.c
--- ./VirtualBox-6.1.8.orig/src/VBox/Devices/PC/BIOS/disk.c	2020-05-14 20:39:11.000000000 +0200
+++ ./VirtualBox-6.1.8/src/VBox/Devices/PC/BIOS/disk.c	2020-05-21 14:53:18.672394097 +0200
@@ -140,6 +140,7 @@
 int edd_fill_dpt(dpt_t __far *dpt, bio_dsk_t __far *bios_dsk, uint8_t device)
 {
     uint16_t    ebda_seg = read_word(0x0040,0x000E);
+    uint16_t    new_dpt_size;
 
     /* Check if buffer is large enough. */
     if (dpt->size < 0x1a)
@@ -149,7 +150,7 @@
     if (dpt->size >= 0x1a) {
         uint64_t    lba;
 
-        dpt->size      = 0x1a;
+        new_dpt_size   = 0x1a;
         dpt->blksize   = bios_dsk->devices[device].blksize;
 
         if (bios_dsk->devices[device].device == DSK_DEVICE_CDROM) {
@@ -175,7 +176,7 @@
         uint8_t     channel, irq, mode, checksum, i, xlation;
         uint16_t    iobase1, iobase2, options;
 
-        dpt->size = 0x1e;
+        new_dpt_size      = 0x1e;
         dpt->dpte_segment = ebda_seg;
         dpt->dpte_offset  = (uint16_t)&EbdaData->bdisk.dpte;
 
@@ -227,7 +228,7 @@
         iface   = bios_dsk->channels[channel].iface;
         iobase1 = bios_dsk->channels[channel].iobase1;
 
-        dpt->size       = 0x42;
+        new_dpt_size    = 0x42;
         dpt->key        = 0xbedd;
         dpt->dpi_length = 0x24;
         dpt->reserved1  = 0;
@@ -269,6 +270,8 @@
         checksum = -checksum;
         dpt->checksum = checksum;
     }
+
+    dpt->size = new_dpt_size;
     return 0;
 }
 
}}}
"	jlxip
15765	[Linux] [KDE5] Windows Guest scales incorrectly on High DPI host with Guest Additions	Windows	VirtualBox 5.1.2	2016-08-08T17:32:10Z	2018-06-25T15:42:01Z	2018-06-25T15:42:01Z	"Hello,

I have a Dell XPS 15 9530 with a high DPI (3200x1800) screen. I'm running Arch Linux with KDE Plasma 5, which has support for high resolution displays.

With the migration of VirtualBox to QT 5, the GUI scales very well and is a pleasure to use on my high DPI screen. Except for one problem: when I install the VirtualBox Guest Additions on a Windows 8.1 or 10 host, the VM only fills up a quarter of the screen; the rest is black. The strange thing is that this only happens when the Guest Additions are installed on the Windows Guest. Without them, it runs fine.

Input is also registered wrong: I have to move in the ""black area"" in order to be able to click on something on the Windows desktop. 

Another strange thing is that when pausing the VM, VirtualBox scales the VM perfectly fine, but when resuming, it's gone.

I attached screenshots to make things a little bit more clear, together with the VBox.log file from a Windows 8.1 guest."	JonasDeMoor
21501	[GuruMeditation] VirtualBox inside VirtualBox.	Windows	VirtualBox-7.0.6	2023-02-12T23:47:37Z	2023-02-12T23:47:37Z	2023-02-12T23:47:37Z	"Host: Windows 10 
VM that I am working on: Arch-Linux
VM that I am trying to start inside the Arch-Linux VM: Alpine-Linux

I thought it was a problem about the Arch-VM, or dedicated resources, but no, I also tried to start the Alpine-VM inside a Xubuntu-VM and a Debian-VM, but still get Guru Meditation.
"	Nobody
19806	[Guest OS windows 7] VirtualboxVM process memory increases while launch app in guest OS	Windows	VirtualBox 6.1.10	2020-08-11T05:32:15Z	2020-08-11T06:39:55Z	2020-08-11T06:39:55Z	"Host OS : ubuntu 20.04
VirtualBox: 6.1.12.r139181
Guest OS: windows 7 ultimate x64 7601
test app: mBlock

VM config: Memory 2G.

How to reproduce:
1. Use top to monitor memory usage.
2. Open VirtualBox, boot windows 7 guest os to desktop.
3. Install and launch app named mblock.exe.
4. While mblock launch completely. then close it.
5. Repeat launch mblock.exe and close scene several times.
6. Check memory status. ==> We find it increse to 3.3G, But i only allocate 2G."	ramboliu
20121	[Extension_Pack] Linux downloads the .gz extension file instead of .vbox-extpack	all	VirtualBox 6.1.16	2021-01-09T19:13:00Z	2021-01-09T19:13:00Z	2021-01-09T19:13:00Z	"Oracle_VM_VirtualBox_Extension_Pack-6.1.16.gz

After manually modifying the file name extension, it was possible to install the package.

Link: https://download.virtualbox.org/virtualbox/6.1.16/Oracle_VM_VirtualBox_Extension_Pack-6.1.16.vbox-extpack



OS:
cat /etc/os-release
NAME=""Ubuntu""
VERSION=""20.04.1 LTS (Focal Fossa)""
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME=""Ubuntu 20.04.1 LTS""
VERSION_ID=""20.04""
HOME_URL=""https://www.ubuntu.com/""
SUPPORT_URL=""https://help.ubuntu.com/""
BUG_REPORT_URL=""https://bugs.launchpad.net/ubuntu/""
PRIVACY_POLICY_URL=""https://www.ubuntu.com/legal/terms-and-policies/privacy-policy""
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal
"	rh.silicon@…
21309	[drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:34:plane-0] flip_done timed out	Linux	VirtualBox-7.0.4	2022-11-24T10:14:40Z	2023-01-16T13:56:25Z	2023-01-16T13:56:25Z	"Hi,

Seeing this below error after upgrade to VBOX 7.0.4

[Thu Nov 24 06:55:56 2022] CPU: 0 PID: 9189 Comm: kworker/0:1 Kdump: loaded Tainted: G           OE     5.4.17-2136.313.6.el8uek.x86_64 #2
[Thu Nov 24 06:55:56 2022] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
[Thu Nov 24 06:55:56 2022] Workqueue: events vmw_fb_dirty_flush [vmwgfx]

Attaching the file with dmesg from VM.

Host: Fedora 
Host Kernel: 6.0.8-300.fc37.x86_64
VM : Oracle Linux Server release 8.7
VM Kernel: 5.4.17-2136.313.6.el8uek.x86_64

Please let me know if you need any further information.
Thanks,
Srini."	Srini8987
20745	[98915.402109] VirtualBox[21633]: segfault at 289 ip 00007ff0a5e639f8 sp 00007ffd7c5ac148 error 4 in libQt5Gui.so.5.12.8[7ff0a5e0e000+41d000]	all	VirtualBox 6.1.30	2021-12-23T21:01:11Z	2021-12-23T21:44:29Z	2021-12-23T21:44:29Z	"VirtualBox crashed, with the following dmesg:

[98915.402109] VirtualBox[21633]: segfault at 289 ip 00007ff0a5e639f8 sp 00007ffd7c5ac148 error 4 in libQt5Gui.so.5.12.8[7ff0a5e0e000+41d000]

All VMs were forcible shutdown by the crash.

Core files attached.
"	keanepgh
20744	[98915.402109] VirtualBox[21633]: segfault at 289 ip 00007ff0a5e639f8 sp 00007ffd7c5ac148 error 4 in libQt5Gui.so.5.12.8[7ff0a5e0e000+41d000]	all	VirtualBox 6.1.30	2021-12-23T21:01:06Z	2021-12-23T21:01:06Z	2021-12-23T21:01:06Z	"VirtualBox crashed, with the following dmesg:

[98915.402109] VirtualBox[21633]: segfault at 289 ip 00007ff0a5e639f8 sp 00007ffd7c5ac148 error 4 in libQt5Gui.so.5.12.8[7ff0a5e0e000+41d000]

All VMs were forcible shutdown by the crash.

Core files attached.
"	keanepgh
19325	6.1.4_136177_fedora31-1 : Checksum mismatch	other	VirtualBox 6.1.2	2020-02-20T10:22:35Z	2020-02-20T11:37:48Z	2020-02-20T11:37:48Z	"When updating Virtualbox by Fedora dnf tool, following message appears:

{{{
# LANG=C  dnf update
Fedora 31 - x86_64 - VirtualBox                                                                     1.2 kB/s | 181  B     00:00    
Dependencies resolved.
====================================================================================================================================
 Package                         Architecture            Version                                  Repository                   Size
====================================================================================================================================
Upgrading:
 VirtualBox-6.1                  x86_64                  6.1.4_136177_fedora31-1                  virtualbox                  100 M

Transaction Summary
====================================================================================================================================
Upgrade  1 Package

Total download size: 100 M
Is this ok [y/N]: y
Downloading Packages:
[MIRROR] VirtualBox-6.1-6.1.4_136177_fedora31-1.x86_64.rpm: Downloading successful, but checksum doesn't match. Calculated: 21ee97ad781368ae5655a2d87f3e172139ecd022e640b47419075633e5dfd9fd(sha256)  Expected: 64d3c8e3462d6b229664f80845486ae8c576bc38a7a3eb633b01a93a906de55a(sha256) 
[MIRROR] VirtualBox-6.1-6.1.4_136177_fedora31-1.x86_64.rpm: Downloading successful, but checksum doesn't match. Calculated: 21ee97ad781368ae5655a2d87f3e172139ecd022e640b47419075633e5dfd9fd(sha256)  Expected: 64d3c8e3462d6b229664f80845486ae8c576bc38a7a3eb633b01a93a906de55a(sha256) 
[MIRROR] VirtualBox-6.1-6.1.4_136177_fedora31-1.x86_64.rpm: Downloading successful, but checksum doesn't match. Calculated: 21ee97ad781368ae5655a2d87f3e172139ecd022e640b47419075633e5dfd9fd(sha256)  Expected: 64d3c8e3462d6b229664f80845486ae8c576bc38a7a3eb633b01a93a906de55a(sha256) 
[MIRROR] VirtualBox-6.1-6.1.4_136177_fedora31-1.x86_64.rpm: Downloading successful, but checksum doesn't match. Calculated: 21ee97ad781368ae5655a2d87f3e172139ecd022e640b47419075633e5dfd9fd(sha256)  Expected: 64d3c8e3462d6b229664f80845486ae8c576bc38a7a3eb633b01a93a906de55a(sha256) 
[FAILED] VirtualBox-6.1-6.1.4_136177_fedora31-1.x86_64.rpm: No more mirrors to try - All mirrors were already tried without success

The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: Error downloading packages:
  Cannot download VirtualBox-6.1-6.1.4_136177_fedora31-1.x86_64.rpm: All mirrors were tried
}}}

Obviously packages are broken or checksum was calculated wrong.

Due to security reasons this update was rejected by package manager."	bitkocher
20858	6.1.32 Ubuntu package lacks the VirtualBox.chm manual file	Linux	VirtualBox 6.1.32	2022-03-06T07:12:07Z	2022-03-06T07:12:07Z	2022-03-06T07:12:07Z	"Help > Contents will reveal an error dialog saying ""Unable to load the chm file /usr/share/doc/virtualbox-6.1/VirtualBox.chm""

```
$ tree /usr/share/doc/virtualbox-6.1/
virtualbox-6.1/
├── changelog.Debian.gz
├── LICENSE
└── UserManual.pdf

0 directories, 3 files
```

I've extracted the package https://download.virtualbox.org/virtualbox/6.1.32/virtualbox-6.1_6.1.32-149290~Ubuntu~eoan_amd64.deb and can also verify that the file is indeed missing."	林博仁(Buo-Ren, Lin)
20632	6.1.28 Does Not Work at All on Kubuntu 20.04.3 LTS	all	VirtualBox 6.1.28	2021-10-24T17:10:08Z	2021-10-31T09:23:19Z	2021-10-31T09:23:19Z	"As reported by several people on your [https://forums.virtualbox.org/viewtopic.php?f=7&t=104196 forums]...

Host: Kubuntu 20.04.03
Guests: (2) Kubuntu 20.04.03 and (1) Windows 10
VB: Version 6.1.28 r147628 (Qt5.12.8)
Package: https://download.virtualbox.org/virtualbox/6.1.28/virtualbox-6.1_6.1.28-147628~Ubuntu~eoan_amd64.deb

All is well on 6.1.26. Upgrading to 6.1.28 causes all guests to fail on startup, with the following error message.

{{{
Failed to open a session for the virtual machine | machine name |
}}}

Under ""Details"", the error contains:

{{{
The virtual machine |machine name| has terminated unexpectedly during startup with exit code 1 (0x1).

Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
MachineWrap
Interface:
IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}
}}}

I further attempted to export the guests from 6.1.26, and import them into 6.1.28, but that made no difference.

Downgrading back to 6.1.26 restores correct functionality, so luckily, that's easy. This operation also proves that there's nothing amiss with the machines themselves.

Even worse, newly-created VMs exhibit the same error, so to put it bluntly, 6.1.28 does not work at all on this system.

"	Hillman
18314	6.0.2 RPM was built for fedora26, while 6.0.0 RPM was built for fedora29. Regression?	other	VirtualBox 6.0.2	2019-01-16T06:50:53Z	2019-01-16T07:02:14Z	2019-01-16T07:02:14Z	"Summary says it all. 6.0.0 installed fine on Fedora 29, because the RPM had a requires for libvpx.so.5()(64bit) from libvpx-1.7.0.

6.0.2 doesn't upgrade on Fedora 29, because it has a requires for libvpx.so.4 from libvpx-1.6.* which is no longer present on 29."	Valdis Kletnieks
19092	6.0.14 Extensio Pack installation error on Linux Mint Debian Edition 3	other	VirtualBox 6.0.14	2019-11-16T22:39:26Z	2019-11-17T01:57:01Z	2019-11-17T01:57:01Z	Система LMDE 3,Ошибка установки VirtualBox 6.0.14 Oracle VM VirtualBox Extension Pack.	gri
18811	6.0.10 snaphot fails on NFS share with savestate	all	VirtualBox 6.0.10	2019-08-04T15:36:05Z	2019-08-14T03:50:42Z	2019-08-14T03:50:42Z	"This all works with 5.2.X. A fresh install of 6.0.10 yields the following bug:

With a VM located on an NFS share, if that VM is put into ""savestate"", and we try to clone that VM, the clone fails with the following error:
{{{
Progress state: VBOX_E_IPRT_ERROR
VBoxManage: error: Clone VM failed
VBoxManage: error: Code VBOX_E_IPRT_ERROR (0x80BB0005) - Runtime subsystem error (extended info not available)
VBoxManage: error: Context: ""RTEXITCODE handleCloneVM(HandlerArg*)"" at line 609 of file VBoxManageMisc.cpp
}}}

If the VM was shutdown using poweroff or acpipowerbutton, the clone works as expected.
[[BR]]
Note: If the VM is located on a local ext4 filesystem, cloning of a savestate VM works as expected. The issue only happens if the VM is on an NFS share AND the vm was put into ""savestate"".

Some traces below:
VMinfo:
{{{
[vbox@scvm001 ]$ vm showvminfo dtest
Name:                        dtest
Groups:                      /
Guest OS:                    Ubuntu (64-bit)
UUID:                        7ff40ac1-6ebb-4d3f-9726-148f9f700e41
Config file:                 /home/vbox/vms/dtest/dtest.vbox
Snapshot folder:             /home/vbox/vms/dtest/Snapshots
Log folder:                  /home/vbox/vms/dtest/Logs
Hardware UUID:               7ff40ac1-6ebb-4d3f-9726-148f9f700e41
Memory size                  2048MB
Page Fusion:                 disabled
VRAM size:                   16MB
CPU exec cap:                100%
HPET:                        disabled
CPUProfile:                  host
Chipset:                     piix3
Firmware:                    BIOS
Number of CPUs:              2
PAE:                         disabled
Long Mode:                   enabled
Triple Fault Reset:          disabled
APIC:                        enabled
X2APIC:                      enabled
Nested VT-x/AMD-V:           disabled
CPUID Portability Level:     0
CPUID overrides:             None
Boot menu mode:              message and menu
Boot Device 1:               DVD
Boot Device 2:               HardDisk
Boot Device 3:               Not Assigned
Boot Device 4:               Not Assigned
ACPI:                        enabled
IOAPIC:                      enabled
BIOS APIC mode:              APIC
Time offset:                 0ms
RTC:                         UTC
Hardw. virt.ext:             enabled
Nested Paging:               enabled
Large Pages:                 disabled
VT-x VPID:                   enabled
VT-x unr. exec.:             enabled
Paravirt. Provider:          Default
Effective Paravirt. Prov.:   KVM
State:                       powered off (since 2019-07-25T18:24:07.000000000)
Monitor count:               1
3D Acceleration:             disabled
2D Video Acceleration:       disabled
Teleporter Enabled:          disabled
Teleporter Port:             0
Teleporter Address:          
Teleporter Password:         
Tracing Enabled:             disabled
Allow Tracing to Access VM:  disabled
Tracing Configuration:       
Autostart Enabled:           disabled
Autostart Delay:             0
Default Frontend:            
Storage Controller Name (0):            SATA
Storage Controller Type (0):            IntelAhci
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0):  30
Storage Controller Port Count (0):      1
Storage Controller Bootable (0):        on
Storage Controller Name (1):            IDE
Storage Controller Type (1):            PIIX4
Storage Controller Instance Number (1): 0
Storage Controller Max Port Count (1):  2
Storage Controller Port Count (1):      2
Storage Controller Bootable (1):        on
SATA (0, 0): /home/vbox/vms/dtest/dtest.vmdk (UUID: 2ec6b9b3-1ea9-44e8-b2b2-d752ef938034)
IDE (1, 0): Empty
NIC 1:                       MAC: 080027BDA9CB, Attachment: Bridged Interface 'enp65s0', Cable connected: on, Trace: off (file: none), Type: 82545EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none
NIC 2:                       disabled
NIC 3:                       disabled
NIC 4:                       disabled
NIC 5:                       disabled
NIC 6:                       disabled
NIC 7:                       disabled
NIC 8:                       disabled
Pointing Device:             PS/2 Mouse
Keyboard Device:             PS/2 Keyboard
UART 1:                      disabled
UART 2:                      disabled
UART 3:                      disabled
UART 4:                      disabled
LPT 1:                       disabled
LPT 2:                       disabled
Audio:                       disabled
Audio playback:              disabled
Audio capture:               disabled
Clipboard Mode:              disabled
Drag and drop Mode:          disabled
VRDE:                        enabled (Address 0.0.0.0, Ports 3400, MultiConn: off, ReuseSingleConn: off, Authentication type: null)
Video redirection:           disabled
VRDE property               : TCP/Ports  = ""3400""
VRDE property               : TCP/Address = <not set>
VRDE property               : VideoChannel/Enabled = <not set>
VRDE property               : VideoChannel/Quality = <not set>
VRDE property               : VideoChannel/DownscaleProtection = <not set>
VRDE property               : Client/DisableDisplay = <not set>
VRDE property               : Client/DisableInput = <not set>
VRDE property               : Client/DisableAudio = <not set>
VRDE property               : Client/DisableUSB = <not set>
VRDE property               : Client/DisableClipboard = <not set>
VRDE property               : Client/DisableUpstreamAudio = <not set>
VRDE property               : Client/DisableRDPDR = <not set>
VRDE property               : H3DRedirect/Enabled = <not set>
VRDE property               : Security/Method = <not set>
VRDE property               : Security/ServerCertificate = <not set>
VRDE property               : Security/ServerPrivateKey = <not set>
VRDE property               : Security/CACertificate = <not set>
VRDE property               : Audio/RateCorrectionMode = <not set>
VRDE property               : Audio/LogPath = <not set>
OHCI USB:                    disabled
EHCI USB:                    disabled
xHCI USB:                    disabled

USB Device Filters:

<none>

Bandwidth groups:  <none>

Shared folders:<none>

Capturing:                   not active
Capture audio:               not active
Capture screens:             0
Capture file:                /home/vbox/vms/dtest/dtest.webm
Capture dimensions:          1024x768
Capture rate:                512kbps
Capture FPS:                 25kbps
Capture options:             

Description:
dtest
Guest:

Configured memory balloon size: 0MB
}}}

Show where the disk is located
{{{
[vbox@scvm001 ]$ vm showvminfo dtest | grep SATA
Storage Controller Name (0):            SATA
SATA (0, 0): /home/vbox/vms/dtest/dtest.vmdk (UUID: 2ec6b9b3-1ea9-44e8-b2b2-d752ef938034)
}}}

Show the disk mount point
{{{
[vbox@scvm001 ]$ df -k /home/vbox/vms/dtest/dtest.vmdk
Filesystem      1K-blocks       Used  Available Use% Mounted on
scqn001:/vbox  3787705600 1550129152 2237035776  41% /mnt/scqn001
}}}

Show the mount type and mount options. This is an NFS mount.
{{{
[vbox@scvm001 ]$ grep /mnt/scqn001 /etc/mtab
scqn001:/vbox /mnt/scqn001 nfs4 rw,relatime,vers=4.2,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.10.31,local_lock=none,addr=192.168.10.29 0 0
}}}

Start the VM
{{{
[vbox@scvm001 ]$ vm startvm --type headless dtest
Waiting for VM ""dtest"" to power on...
VM ""dtest"" has been successfully started.
}}}

Show clone working if VM is set to ""poweroff""
{{{
[vbox@scvm001 ]$ vboxmanage controlvm dtest poweroff
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
[vbox@scvm001 ]$ vboxmanage clonevm dtest --mode all --basefolder /mnt/lv001-r0/backup/vms --name dtest-20190803-114608-vboxbu
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Machine has been successfully cloned as ""dtest-20190803-114608-vboxbu""
[vbox@scvm001 ]$ vboxmanage startvm dtest --type headless
Waiting for VM ""dtest"" to power on...
VM ""dtest"" has been successfully started.
}}}

Show clone working if VM is set to ""acpipowerbutton""
{{{
[vbox@scvm001 ]$ vboxmanage controlvm dtest acpipowerbutton
[vbox@scvm001 ]$ vboxmanage clonevm dtest --mode all --basefolder /mnt/lv001-r0/backup/vms --name dtest-20190803-114015-vboxbu
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Machine has been successfully cloned as ""dtest-20190803-114015-vboxbu""
[vbox@scvm001 ]$ vboxmanage startvm dtest --type headless
Waiting for VM ""dtest"" to power on...
VM ""dtest"" has been successfully started.
}}}

Show clone failing is VM is set to ""savestate""
{{{
[vbox@scvm001 ]$ vboxmanage controlvm dtest savestate
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
[vbox@scvm001 ]$ vboxmanage clonevm dtest --mode all --basefolder /mnt/lv001-r0/backup/vms --name dtest-20190803-114359-vboxbu
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...
Progress state: VBOX_E_IPRT_ERROR
VBoxManage: error: Clone VM failed
VBoxManage: error: Code VBOX_E_IPRT_ERROR (0x80BB0005) - Runtime subsystem error (extended info not available)
VBoxManage: error: Context: ""RTEXITCODE handleCloneVM(HandlerArg*)"" at line 609 of file VBoxManageMisc.cpp
[vbox@scvm001 ]$ vboxmanage startvm dtest --type headless
Waiting for VM ""dtest"" to power on...
VM ""dtest"" has been successfully started.
}}}

Removing 6.0.10 and installing 5.2.X, everything works as expected.


"	guideloom
18215	6.0.0 Windows guest addition installation aborted	Windows	VirtualBox 6.0.0	2018-12-20T17:21:13Z	2019-09-18T14:03:34Z	2019-09-18T14:03:34Z	"VirtualBox 6.0.0 r127566

Guest: MS Windows 10 EDU build 1803, 64-bit

Host: Linux Mint 19.1 MATE, 64-bit

When trying to install guest additions, the installation in MS Windows 10 will be aborted with error (log files attached). Tried also uninstall old guest additions in first place and then new one but did not help."	Edmund Laugasson
17607	5.2.8 Has Issues Passing Though USB Devices Consistently	Linux	VirtualBox 5.2.8	2018-03-08T14:27:46Z	2018-03-08T14:27:46Z	2018-03-08T14:27:46Z	I use USB passthrough often, and after updating to the newest version, the passthrough was working maybe 1 of 10 tries. Currently, I am trying to passthrough USB to Serial cables. Downgrading to 5.2.6 has solved these issues. 	SheepyBloke
17950	5.2.18 still not in fedora 28 repository	other	VirtualBox 5.2.18	2018-08-22T18:25:20Z	2018-08-22T19:16:08Z	2018-08-22T19:16:08Z	"First reported, and details in https://forums.virtualbox.org/viewtopic.php?f=7&t=89122

Short form: the rpm is present for Fedora 26, but not Fedora 28.

Fedora 26: http://download.virtualbox.org/virtualbox/rpm/fedora/26/x86_64

Fedora 28: http://download.virtualbox.org/virtualbox/rpm/fedora/28/x86_64

Note that dnf selects the URI based on the release it's run on.

Apparently I'm not the only one who is experiencing this.

Thanks.
"	Timothe Litt
17964	5.2.18 still not availale for RHEL / CentOS 7 -> fixed	other	VirtualBox 5.2.18	2018-08-31T06:42:40Z	2018-09-12T12:12:23Z	2018-09-12T12:12:23Z	"Hello!

VB 5.2.18 is still not available for the above mentioned platform. Yesterday I tried to update and any update from 5.2.16 -> 5.2.18 was found, so finally I tried a workaround and installed a downloaded RPM manually (from http://download.virtualbox.org/virtualbox/rpm/rhel/7/x86_64/VirtualBox-5.2-5.2.18_124319_el7-1.x86_64.rpm, so it is really existiing and at it right place).

But that's what I still get from yum:
{{{
# yum --disablerepo ""*"" --enablerepo ""virtualbox"" list available
Loaded plugins: aliases, changelog, fastestmirror, langpacks, verify
Loading mirror speeds from cached hostfile
Available Packages
VirtualBox-4.3.x86_64 4.3.40_110317_el7-1  virtualbox
VirtualBox-5.0.x86_64 5.0.40_115130_el7-1  virtualbox
VirtualBox-5.1.x86_64 5.1.38_122592_el7-1  virtualbox
}}}
Just as a try to get back to the ""standard install"" from REPO:
{{{
# yum reinstall VirtualBox-5.2
Loaded plugins: aliases, changelog, fastestmirror, langpacks, verify
Loading mirror speeds from cached hostfile
 * base: mirror.cuegee.de
 * epel: ftp-stud.hs-esslingen.de
 * extras: mirror.cuegee.de
 * updates: mirror.cuegee.de
Installed package VirtualBox-5.2-5.2.18_124319_el7-1.x86_64 not available.
Error: Nothing to do
}}}
Maybe this is a duplicate of another ticket, but I found any for RHEL/CentOS 7.

With regards."	HRZ d. Universität Bielefeld
15804	5.1x Windows Guest Video Playback 2x speed - No Sound	Windows	VirtualBox 5.1.4	2016-08-17T08:13:37Z	2016-10-12T03:02:56Z	2016-10-12T03:02:56Z	"Problem: 
With 5.1x if I play back a video in Windows 7 guest then it does not have sound and the video plays back at about 2x speed. This is true in several media players. Also, true in Firefox 47, 48 and Google Chrome 52. So this issue is systemic. Tried disabling 2D and 3D with the same issue. Went through several installs, cold power downs, reboots and many experiments.

Solution:
Uninstall / Purge VirtualBox 5.1x and install 5.0x (5.0.24) and video playback and sound work properly.

Host: Ubuntu 16.04 with all updates
Guest: Windows 7 sp1 with all updates
Graphics Card: Nvidia GeForce GTX 980 4GB
Graphics Driver: 3.57 to 3.67
VirtualBox: 5.1, 5.12 5.14
Motherboard: ASUS Rampage V Extreme
CPU: I7-5820K
Memory: 64GB"	JavaDev11
16110	5.1.x series - Fullscreen and mouse pointer offset in Gnome 3.20+	Windows	VirtualBox 5.1.8	2016-10-24T17:34:07Z	2020-02-07T12:14:09Z	2020-02-07T12:14:09Z	"Windows 10 guest, Arch Linux host with Gnome 3.20 and 3.22. Been observing this regression since the initial 5.1.x releases and still present in 5.1.8 with 5.1.8 guest additions.

STR:

1) Load guest Win10 in fullscreen mode. 
2) Navigate away to another non-Virtualbox window. 
3) Navigate back to Virtualbox window.

Expected result: Fullscreen display is maintained

Actual result: Entire fullscreen display is shifted down by X pixels equal to the size of the Gnome bar at top of screen. This offset equally applies to the mouse pointer. Notice in attached screenshot that the top bar area from the native display manager is showing the Gnome desktop background. Also notice the position of the pointer relative to the hovered state of the taskbar icon."	tekstryder
15936	5.1.6 segfault in VBoxDD.so on USB unplug	Windows	VirtualBox 5.1.6	2016-09-15T15:51:39Z	2016-09-22T17:40:27Z	2016-09-22T17:40:27Z	"Hi,
the VM window just disappears.
It does not happen every time. As matter of fact I was working several days now with many USB unplug events. This time I captured logs.

{{{
04:11:12.098613 VUSB: Detached '00007fe874d5be50[proxy 0c2e:096a]' from port 1
04:11:12.098710 AssertLogRel /home/vbox/vbox-5.1.6/src/VBox/VMM/VMMR3/TM.cpp(1727) int TMR3TimerDestroy(PTMTIMER): <NULL>
}}}

and syslog

{{{
Sep 15 17:14:41 don kernel: [27511.485796] USBDevIo--1[19180]: segfault at e8 ip 00007fe89133910a sp 00007fe85557ae90 error 4
Sep 15 17:14:41 don kernel: [27511.485802] EhciFramer[14246]: segfault at f0 ip 00007fe891335ca0 sp 00007fe85600eb50 error 4 in VBoxDD.so[7fe89127a000+28e000]
Sep 15 17:14:41 don kernel: [27511.485808]  in VBoxDD.so[7fe89127a000+28e000]
}}}

 I can also share the Ubuntu crash report with the devs; but do not want to see it in the public. I this also 9MB.

And I can provide the USB device if that makes a difference (I live close to Endersbach).

Here is the link to the forum post:
[https://forums.virtualbox.org/viewtopic.php?f=7&t=79708&p=372643#p372643]
(there is also wrote about another crash, but I think the two are unrelated).

"	ucrasher2
17109	5.1.28 - after upgrading guest additions, teamviewer 12 becomes unstable in Win 7 64-bit guest	Windows	VirtualBox 5.1.28	2017-09-22T16:36:19Z	2017-09-22T16:36:19Z	2017-09-22T16:36:19Z	"upgraded virtualbox 5.1.26 on xubuntu 16.04.3 to version 5.1.28, and upgraded guest additions simultaneously on Win7 64-bit Guest. Noticed that Teamviewer 12 started crashing (""TeamViewer 12 has stopped working"") intermittently, but most often when manipulating TV controls and reliably when ending the TV session.  Bringing Windows patches up-to-date and updating Teamviewer had no effect.

I have another VM with Teamviewer as an ""emergency spare"" (both machines were cloned from a common ancestor).  I did not update the guest additions (remained at 5.1.26), and the same (non-updated) version of TeamViewer worked as normal.  Immediately after updating the Guest Additions to 5.1.28, and re-connecting with the same remote Teamviewer host, Teamviewer began crashing as on the other VM."	BISISysadmin
16546	5.1.16 seamless mini toolbar broken	Windows	VirtualBox 5.1.16	2017-03-09T17:43:59Z	2017-04-20T13:02:00Z	2017-04-20T13:02:00Z	"Toolbar problems. Toolbar settings fails--on screen, not dismissable, but works otherwise .Minitoolbar does not work in seamless mode (mouseclicks do nothing to menu items). Both toolbar & mini work fine in 5.1.15 r113680 and below.

Reproduce:
1. windowed :start vm, click view menubar, menubar settings. try to dismiss settings bar, no dice.
2. seamless: click menubar item, no response.

"	matthewls
14498	4k resolution on Linux + GNOME/gtk host extremely buggy	all	VirtualBox 5.0.2	2015-08-25T18:13:11Z	2015-08-25T18:17:18Z	2015-08-25T18:17:18Z	UI components are extremely buggy wih overlaps and placement on a host with Ubuntu GNOME 3.16+ 4k resolution display.	sgnn7
19196	4K External Monitor greatly distorts GUI	all	VirtualBox 6.1.0	2020-01-03T18:33:44Z	2020-01-03T18:33:44Z	2020-01-03T18:33:44Z	"I use a 4K TV as an external monitor via HDMI on Ubuntu 18.04. 

When I open VirtualBox, the default window size is huge and doesn't fit on my laptop screen, but the text is a normal size. When I move the window to the external monitor, the font and icon sizes become huge.

In either case, it's extremely difficult and frustrating to use in this condition, so I usually have to unplug the external monitor in order to use VirtualBox. 


*I've been using VirtualBox almost daily for years now; it's the only reason I was able to make the jump to Linux as my daily driver. Thank You."	awsoonn
17634	3Dconnection Space Navigator doesn't work	Windows	VirtualBox 5.2.6	2018-03-22T14:58:09Z	2018-04-19T17:49:21Z	2018-04-19T17:49:21Z	"3Dconnection fails to initialize player. I have the impression, that 3Dacceleration does not work properly.
I attach screen shots and dxdiag info file."	steamer
16845	3D stopped working in Ubuntu 16.04 with NVIDIA  nouveau 1.0.0	all	VirtualBox 5.1.22	2017-06-19T02:44:08Z	2017-06-19T02:44:08Z	2017-06-19T02:44:08Z	"After updating the OS (possibly including vbox), all my VMs now won't start any longer.
   Ubuntu 16.04, kernel 4.4.0-79-generic

   Virtualbox Version 5.1.22 r115126 (Qt5.5.1)

   NVIDIA graphics card; I think using nouveu driver (please see Xorg.0.log, attached)

If I disable 3D in each VM (and discard saved state!) then they start OK.

Don't know if this was caused by a change in VirtualBox or the OS or driver...

Here is the error pop-up I get when trying to start a previously-working VM: 

""This VM was configured to use 3D acceleration. However, the 3D support of the host is not working properly and the VM cannot be started. To fix this problem, either fix the host 3D support (update the host graphics driver?) or disable 3D acceleration in the VM settings (VERR_NOT_AVAILABLE).

Result Code: 
NS_ERROR_FAILURE (0x80004005)
Component: 
ConsoleWrap
Interface: 
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}""



"	Jim Avera
20605	3D opengl with vulcan nvidia	other	VirtualBox 6.1.26	2021-10-13T18:27:19Z	2021-10-13T18:27:19Z	2021-10-13T18:27:19Z	"Hello[[BR]]

[[BR]]
[[BR]]

Would it be possible to implement in future version VirtualBox the functions[[BR]]

3d acceleration NVIDIA vulkan technology?[[BR]] Opengl 3.0 or more....[[BR]]


like do software vmware player and vmware workstation .[[BR]]

Thank.[[BR]]
"	Sizy458
14119	3d graphics window closes the program menu.	Windows	VirtualBox 4.3.28	2015-05-15T12:01:08Z	2015-05-15T16:08:20Z	2015-05-15T16:08:20Z	The three-dimensional programs running in windowed mode menu under the window are 3D graphics. Attached a screenshot. This is evident when the mode switches on 3D acceleration in VirtualBoх.	3DRaven
19742	3D acceleration on Windows 10 guests apparently doesn't play nicely with some applications	Windows	VirtualBox 6.1.8	2020-07-20T22:12:50Z	2021-01-31T18:32:34Z	2021-01-31T18:32:34Z	"Host: Ubuntu 18.04.04 LTS on Dell Precision T7610, Quadro K600
Guest: Windows 10 Pro Version 1909 Build 18363.959

Windows 10 guest machine is started with VBoxSVGA, 3D acceleration enabled. Start Rstudio Windows v1.2.5001. Main window contents appear inverted; see attached screenshot. 

Start Windows 10 guest with 3D acceleration disabled; application appears normal. Seems worth reporting even though I'm not 100% sure this isn't an Rstudio problem. 

"	ekoski1
21487	3D acceleration causes Linux guest freezes	Linux	VirtualBox-7.0.6	2023-02-09T12:20:27Z	2023-02-12T01:04:54Z	2023-02-12T01:04:54Z	"Hi,

//Checking the forums, there seems to be several people reporting instances of their '''Windows 11 Guests''' freezing.  I have a situation with '''Linux Guests'''.  Below are some details in case you need a test case.//

I'm experiencing frequent freezes when 3D acceleration is enabled on Linux Guests.  There is no issue with a '''Windows 10 Guest'''.

The current work-around is to disable 3D acceleration.

I captured a core dump of the frozen Guest using '''vboxmanage debugvm dumpvmcore'''.  If there is any value, I can upload it to my G Drive.  It is 460 MB.

== Environment ==

=== Guest

I have tried to create a minimal test case using openSUSE MicroOS (immutable O/S).

Below are some of the highlight settings of the Guest.  However I suspect '''VBox.log''' may only be needed.

* Download latest MicroOS - https://get.opensuse.org/microos/#download
* Set up a new Guest VM:
  * Base memory:  3072 MB (4096 crashes)
  * Processor:  1
  * Storage:  
    * controller > Use Host I/O Cache
    * 30 GB vdi > Solid-state Drive (assuming you're using an SSD)
      * Current allocation is 8.02 GB
  * Display:
    * Video Memory:  128 MB
    * Graphics controller:
      * VMSVGA
      * Enable 3D Acceleration
* Using the MicroOS ISO, create a new Guest
  * Selected local TZ rather than UTC.
  * Select KDE desktop
* On first boot, the Guest will set up bootstrap apps.
* Use '''discover''' to install the '''Brave browser'''.  '''Discover''' is KDE's flatpak manager.  By default, it lives in the systray.  Its icon is a blue shopping bag.  :)
* I did some minor KDE tweaking (e.g. focus-follows-mouse, etc.)  If required, I could upload a tar-ball of the test user's $HOME.

=== Test Case

Using the test case below, the Guest may take upwards of a few hours to freeze.  Sometimes it freezes in a few minutes.

I run it in a '''Virtual Desktop''' and periodically check.

* Run two instances of '''Brave'''
* In each, go to web pages that auto-refresh periodically.  For example:
  * https://edition.cnn.com
  * https://www.theweathernetwork.com/fr/weather/ile-de-france/paris

=== Host

* openSUSE Tumbleweed - rolling distro
* Regularly kept up to date.
* As of this writing, kernel 6.1.8-1
* Using '''Prime offloading'''
  * iGPU - Intel UHD Graphics
  * dGPU - Nvidia GeForce RTX 2060 Max-Q  
"	Pablo Sanchez
16988	32 bit Windows 8 Guest on Ubuntu 17.04 spontaneously restarting with PIIX3 ATA error	Windows	VirtualBox 5.1.22	2017-08-07T01:54:20Z	2017-08-07T07:01:52Z	2017-08-07T07:01:52Z	"I could find one similar report to the one I'm filing, but it's from 9 years ago here: https://www.virtualbox.org/ticket/2600 so I decided to file a new report.

I have a Windows 8 guest running on Ubuntu 17.04. When I trying to manipulate data in Excel (copying and pasting), the machine freezes then spontaneously restarts. I think this is the relevant error code from the log file:
{{{
00:12:32.753320 PIIX3 ATA: Ctl#1: RESET, DevSel=0 AIOIf=0 CmdIf0=0xa0 (-1 usec ago) CmdIf1=0x00 (-1 usec ago)
00:12:32.753435 PIIX3 ATA: Ctl#1: finished processing RESET
00:12:32.755451 PIIX3 ATA: LUN#2: performing device RESET
}}}"	theronmuller
19262	2D graphics performance issue when increasing the number of cores	Windows	VirtualBox 6.1.2	2020-01-24T12:13:58Z	2020-01-24T12:13:58Z	2020-01-24T12:13:58Z	"Hi,

to increase the performances of Adobe Lightroom in a Windows 7 VM, I tried recently to increase the number of cores in my Windows 7 VM and I noticed a serious drop in 2D graphics performances.

I first believed it was due to some regression in recent versions of VirtualBox, so I did some benchmarks (using PassMark 9) in the VM with VirtualBox 5.2.x and 6.1.x, and I got the same performance drop for 2D graphics, whatever the VirtualBox version, when I increased the number of cores in the VM. So, it's not a regression.

I have a very powerful machine, with 16 physical cores and 128 GB RAM, so I was able to plot the PassMark 2D score vs the number of cores (2, 4, 8 or 16) in the VM. Then I exported my VM to VMware Player, and I did the same benchmark. The attached image 'figure_2D.png' shows the results (higher score is better). As you can see, the 2D graphics score for VirtualBox linearly decreases as the number of cores increases. The 2D score is divided by ~4 between 2 cores and 16.

However, this is not the same for VMware, where one can see a small decrease of 15% between 2 cores and 16.

I also plotted the CPU score of PassMark vs the number of cores in the VM (image 'figure_CPU.png', higher score is better). For this benchmark, VirtualBox and VMware perform the same until 8 cores, but VMware gives a much better result for 16 cores.

I tried many parameter tweaks in VirtualBox but I was not able to improve the situation. I also tried with another PC that has less cores, and I saw the same performance drop...

Note that the performance drop I see in PassMark scores (in a Windows 7 VM) reflects what I see as a user in the windows 7 VM. This is not an artefact of using PassMark in a VM. For example, with 16 cores in a VirtualBox VM, moving a window is painfully slow. The CPU load is very high even when I do nothing, the fans are at maximum speeds, etc. Those problems do not arise in VMware player: the CPOU load is low, and the VM is very snappy, whatever the number of cores.

To me, there should be no interaction between increasing the number of cores and the 2D graphics performance. It's clearly a bug or perhaps a side effect of the way multicore processing is done in VirtualBox...


My hardware: HP Z820 Workstation with two Intel Xeon CPU E5-2687W 0 @ 3.10GHz, 16 cores, 32 threads and 128 GB RAM, graphic card id an Nvidia Quadro K2000

Host system: Ubuntu Linux 18.04, 64 bits

Guest system: Windows 7 Professional SP1, 64 bits, 4GB RAM in the VM, guest additions installed, 256 MB video RAM


"	roland651
18372	00:08:27.570846 !!Assertion Failed!! 00:08:27.570847 Expression: RT_SUCCESS_NP(rc) 00:08:27.570847 Location  : F:\tinderbox\win-rel\src\VBox\VMM\VMMAll\PGMAllPool.cpp(2645) int __cdecl pgmPoolMonitorInsert(struct PGMPOOL *,struct PGMPOOLPAGE *) 00:08:27.570850 PGMHandlerPhysicalRegisterEx 00000000dea18000 failed with -1701 00:08:28.581275 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'	Windows	VirtualBox 6.0.2	2019-01-28T05:17:16Z	2019-01-29T10:31:48Z	2019-01-29T10:31:48Z	"I've installed this morning my first Virtual machine, based on the last version of Debian, my laptop running a version of Window 8

I've installed on my VM Apache and MySQL, cus I need a web development environment.

And when I'm running my VM I got an issue, it stops to run, and close it, I don't know why, I do nothing extraordinary, just running Apache and MySQL and try to download a file from my Gmail. I don't understand what happened..."	Hota
17378	/sbin/vboxconfig fails during upgrade of Vbox to 5.2.2	Linux	VirtualBox 5.2.2	2017-12-18T19:52:19Z	2017-12-18T19:52:19Z	2017-12-18T19:52:19Z	"Current system is Fedora 28 x86_64 (Rawhide).

Install of VirtualBox released version fails during config. The developer version fails as well... with the same error message (see inclosed install log)."	George R. Goffe
17232	/sbin/vboxconfig fails during upgrade of Vbox	Linux	VirtualBox 5.2.0	2017-11-01T05:31:50Z	2017-11-01T16:20:41Z	2017-11-01T16:20:41Z	"I have upgraded kernels on this Fedora 28 (rawhide) system and tried the latest Vbox release (!VirtualBox-5.2-5.2.0_RC1_118201_fedora26-1.x86_64.rpm) as well as the latest developer version (!VirtualBox-5.2.1-118869-Linux_amd64.run) with the same apparent result.

Can someone tell me what I'm doing wrong here please?

George..."	George R. Goffe
19847	/opt/VirtualBox/vboxwebsrv: no process found	all	VirtualBox 6.1.10	2020-08-31T14:09:46Z	2020-08-31T14:09:46Z	2020-08-31T14:09:46Z	"VirtualBox-6.1.13-140124-Linux_amd64.run

running Leap 15.1 with kernel 5.5.0-1.g3f183bf-default

VirtualBox has been installed successfully.

giga-151:/home/hmi/import # service vboxweb-service status
* vboxweb-service.service
   Loaded: loaded (/opt/VirtualBox/vboxweb-service.sh; enabled; vendor preset: disabled)
   Active: active (exited) since Mon 2020-08-31 15:19:05 CEST; 3min 30s ago
  Process: 7724 ExecStart=/opt/VirtualBox/vboxweb-service.sh start (code=exited, status=0/SUCCESS)
    Tasks: 0
   CGroup: /system.slice/vboxweb-service.service

Aug 31 15:19:05 giga-151 vboxweb-service.sh[7724]: vboxweb-service.sh: Starting VirtualBox web service.
Aug 31 15:19:05 giga-151 su[7730]: (to vbox) root on none
Aug 31 15:19:04 giga-151 systemd[1]: Starting vboxweb-service.service...
Aug 31 15:19:05 giga-151 vboxweb-service.sh[7781]: VirtualBox web service started.
Aug 31 15:19:05 giga-151 systemd[1]: Started vboxweb-service.service.

giga-151:/home/hmi/import # service vboxweb-service stop

giga-151:/home/hmi/import # service vboxweb-service status
* vboxweb-service.service
   Loaded: loaded (/opt/VirtualBox/vboxweb-service.sh; enabled; vendor preset: disabled)
   Active: inactive (dead) since Mon 2020-08-31 15:23:11 CEST; 5s ago
  Process: 7897 ExecStop=/opt/VirtualBox/vboxweb-service.sh stop (code=exited, status=0/SUCCESS)
  Process: 7724 ExecStart=/opt/VirtualBox/vboxweb-service.sh start (code=exited, status=0/SUCCESS)

Aug 31 15:19:05 giga-151 vboxweb-service.sh[7724]: vboxweb-service.sh: Starting VirtualBox web service.
Aug 31 15:19:05 giga-151 su[7730]: (to vbox) root on none
Aug 31 15:19:04 giga-151 systemd[1]: Starting vboxweb-service.service...
Aug 31 15:19:05 giga-151 vboxweb-service.sh[7781]: VirtualBox web service started.
Aug 31 15:19:05 giga-151 systemd[1]: Started vboxweb-service.service.
Aug 31 15:23:10 giga-151 systemd[1]: Stopping vboxweb-service.service...
Aug 31 15:23:10 giga-151 vboxweb-service.sh[7897]: vboxweb-service.sh: Stopping VirtualBox web service.
Aug 31 15:23:10 giga-151 vboxweb-service.sh[7897]: 
'''/opt/VirtualBox/vboxwebsrv: no process found'''
Aug 31 15:23:11 giga-151 vboxweb-service.sh[7906]: VirtualBox web service stopped."	hgf_m
11029	/etc/init.d/vboxautostart-service stop has no effect	other	VirtualBox 4.2.0	2012-10-05T10:03:26Z	2012-10-16T08:39:40Z	2012-10-16T08:39:40Z	"On my Debian server (squeeze) I upgraded to VirtualBox 4.2. I was especially interested in 4.2 because of its new ""autostart"" feature. I was finally able to setup that feature (well, you could say there is some room for improvement in the official documentation) and all machines that are supposed to start automatically are started in the expected order when running script `/etc/init.d/vboxautostart-service` with the `start` option.

However, running `/etc/init.d/vboxautostart-service stop` has no effect at all. Indeed, in that script, almost the complete functionality of function stop() is commented out and replaced by a single call to `exit 0`.

What is the reason for disabling the `stop` command? Was this by accident or intentionally?"	Martin Burger
16813	/dev/tty: No such device or address	all	VirtualBox 5.1.22	2017-06-05T03:20:03Z	2017-06-11T18:32:49Z	2017-06-11T18:32:49Z	"I've got an error message thrown by VBox->Preferences->Extensions, whenever trying to upgrade the VBox Extension Package:

'''""The installer failed with exit code 127: Error creating textual authentication agent: Error opening current controlling terminal for the process (`/dev/tty'): No such device or address.""'''

This seems little bit weird since `/dev/tty` is part of the system:

{{{
ls /dev/tty
/dev/tty
}}}

I need some help regarding this issue."	kaisbe
12812	*.start and *.stop scripts are not created by VBoxManage modifyvm myvm --autostart-enabled on	Linux	VirtualBox 4.3.8	2014-03-12T06:54:47Z	2014-03-12T06:54:47Z	2014-03-12T06:54:47Z	"I have followed the steps in this tutorial: [http://www.vionblog.com/virtualbox-4-3-autostart-debian-wheezy/]

The problem is no *.start or *.stop files are created in /etc/vbox/ (and no errors are shown) after running the command:

{{{
$ VBoxManage modifyvm myvm --autostart-enabled on
}}}

In case it helps, trying to disable auto start for the same VM does give an error:

{{{
$ VBoxManage modifyvm myvm --autostart-enabled off
VBoxManage: error: Removing machine 'myvm' to the autostart database failed with VERR_FILE_NOT_FOUND
VBoxManage: error: Details: code NS_ERROR_UNEXPECTED (0x8000ffff), component SessionMachine, interface IMachine, callee nsISupports
VBoxManage: error: Context: ""COMSETTER(AutostartEnabled)(ValueUnion.f)"" at line 2616 of file VBoxManageModifyVM.cpp
}}}

Host os: Ubuntu Server 12.04-4 (amd64)

VirtualBox: 4.3.8

This issue was reported on the forum a few weeks ago, but there has been no reply:
[https://forums.virtualbox.org/viewtopic.php?f=7&t=60425&p=282223#p282223]

Thanks!


For reference, here's user/group involved:

{{{
$ whoami 
dan
$ groups
dan adm cdrom sudo dip plugdev lpadmin sambashare vboxusers
}}}
 

The contents of /etc/vbox

{{{
$ ls -al /etc/vbox/
total 12
drwxrwxr-t   2 root vboxusers 4096 Mar 12 00:55 .
drwxr-xr-x 101 root root      4096 Mar 12 02:11 ..
-rw-r--r--   1 root root       239 Mar 12 00:55 autostart.conf
}}}

content of autostart.conf:

{{{
# Default policy is to deny starting a VM, the other option is ""allow"".
default_policy = deny

# user dan is allowed to start virtual machines but starting them
# will be delayed for 10 seconds
dan = {
 allow = true
 startup_delay = 10
}
}}}

uname:

{{{
$ uname -a
Linux ubu-host64 3.11.0-18-generic #32~precise1-Ubuntu SMP Thu Feb 20 17:52:10 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
}}}"	Dan Rollo
19526	'vboxmanage list runningvms' FAILs to list running VMs	Linux	VirtualBox 6.1.6	2020-04-23T19:52:03Z	2020-04-25T10:58:06Z	2020-04-25T10:58:06Z	"noting this similar symptom, from a still open issue

	""vboxmanage list runningvms does not list anything""
	https://www.virtualbox.org/ticket/6808#propertyform
		Opened 10 years ago[[BR]]
		Last modified 4 years ago

has that been fixed/addressed elsewhere?

here, running latest VB release
{{{
	VBoxManage --version
		6.1.6r137129
}}}

on host,
{{{
	lsb_release -rd
		Description:    openSUSE Leap 15.1
		Release:        15.1
}}}

checking available vms, correctly returns
{{{
	> VBoxManage list vms
		""Debian_Stable"" {...}
		""Win10_Pro"" {...}
		""openSUSE_Leap"" {...}
	>
}}}

if i launch a guest, e.g.
{{{
	""openSUSE_Leap""
}}}

is, atm, up & running ... and accessible,
{{{
	ps ax | grep vir
		24799 ?        Sl     0:16 /usr/lib/virtualbox/VirtualBox
		24816 ?        S      0:08 /usr/lib/virtualbox/VBoxXPCOMIPCD
		24822 ?        Sl     0:19 /usr/lib/virtualbox/VBoxSVC --auto-shutdown
		40167 ?        Sl     0:27 /usr/lib/virtualbox/VirtualBoxVM --comment openSUSE_Leap --startvm ... --no-startvm-errormsgbox
		40176 ?        S      0:00 /usr/lib/virtualbox/VBoxXPCOMIPCD
		40182 ?        Sl     0:00 /usr/lib/virtualbox/VBoxSVC --auto-shutdown
}}}

but checking RUNNING vms, still (again?) returns blank
{{{
	> VBoxManage list runningvms
	> 
}}}"	pgnd
18420	'Solid State Disk' setting after snapshot not detected by Linux 4.15.0 guest	Linux	VirtualBox 5.2.26	2019-02-06T22:29:59Z	2020-02-28T14:58:57Z	2020-02-28T14:58:57Z	"Same symptom as with https://www.virtualbox.org/ticket/12025 :
""Solid State Disk"" is checked in VBoxManage but the guest does not recognize that, and `cat /sys/block/sda/queue/rotational` in the guest gives ""0""

Host: Ubuntu 18.04;   Guest: Ubuntu 18.04 (kernel 4.15.0)

NOTE: ""Solid State Disk"" was checked only after taking a snapshot. There is only one snapshot.

Possibly relevant: VBox.log (attached) mentions both the snapshot and original vdi, and ""NonRotatingMedium"" is set for the snapshot.  Here's an extract:

[/Devices/ahci/0/LUN#0/Config/] (level 5)
   Mountable           <integer> = 0
   NonRotationalMedium <integer> = 1
   Path                <string>  = "".../Snapshots/{d5ad9312-a011-4939-b281-a71f223ae696}.vdi"" (cb=93)
   
 [/Devices/ahci/0/LUN#0/Config/Parent/] (level 6)
   Path   <string>  = "".../disk1.vdi"" (cb=64)


"	Jim Avera
9527	'Shared Folders' returning incorrect file order to Win API	Windows	VirtualBox 4.1.2	2011-08-30T07:18:57Z	2013-02-20T20:06:36Z	2013-02-20T20:06:36Z	"I am using some proprietary software on Windows XP guest under Linux host. This software (Magpie from MEA in Australia) extracts certain data from certain binary files output from a datalogger and collates it in a database. When run in WinXP under VirtualBox with the data stored in a VirtualBox 'shared folder' mounted as a Windows network drive it loses data.  When the data is stored within the VirtualBox 'disk' it works fine and it also works fine when the data is on a real Windows network share.

I have spoken to the developer of the software and it turns out that it is using the Windows API calls 'FindFirstFile' and 'FindNextFile'. The virtualbox ""pseudo-network redirector"" driver in WinXP is not returning files in the same order as either windows or a windows network share (which it is pretending to be) does. This leads to the data problems within the software. See attached screenshot for file dialog box with incorrectly ordered files. When the data are stored on the windows virtual disk or on a windows share the files are in date order.

Interestingly, when run under WINE the file order in this dialog is exactly the same as when run using Virtualbox and a 'shared folder'. I conclude from this that when the above API calls are run against a virtualbox 'shared folder' it is presenting the files as they are presented to it by my linux host, not in the order that windows would present them.

Unfortunately, I am not a developer and have no idea how linux chooses to present it's files or anything further about these API calls..."	solanum
11031	'Bridged Networking' on host vlan interfaces does not work	other	VirtualBox 4.2.0	2012-10-05T22:17:44Z	2018-07-09T14:30:18Z	2018-07-09T14:30:18Z	"I have searched the forums, and looked on the internet... and this seems to be a regression in the 4.2.0 release.  Downgrading back to 4.1.22 on the same kernel resolves the issue.

I am on gentoo 64-bit, running gentoo-sources-3.6.0.  Same results on 3.5.4

I have a vm-host with several 1q vlan interfaces on it.  I then bind my VM's to a particular interface using the 'Bridge Adapter'.  The VM's are vlan-agnostic.

The symptom I have on VB 4.2.0 is that none of my VM's have network access.  As soon as I switch to NAT on the VM's everything works fine.  Downgrading to 4.1.22 on the same kernel restores network access for the 'Bridge Adapter'.

{{{
daffy TAZ6 # cat /proc/net/vlan/config
VLAN Dev name    | VLAN ID
Name-Type: VLAN_NAME_TYPE_RAW_PLUS_VID_NO_PAD
eth0.10        | 10  | eth0
eth0.11        | 11  | eth0
eth0.12        | 12  | eth0
eth0.13        | 13  | eth0
eth0.14        | 14  | eth0
eth0.20        | 20  | eth0
eth0.25        | 25  | eth0
}}}

My VM-HOST network layout:
{{{
[ROUTER]====1Q-TRUNK===[VM HOST]
                              eth0.10--bridged--VM1, VM2, VM3....
                              eth0.11--bridged--VM6, VM7, VM8
                              eth0.12--bridged--VM4
                              eth0.13
                              eth0.14--bridged--VM5
                              eth0.20
                              eth0.25
}}}

The ROUTER and VM-HOST have the VM's MAC address in their arp tables.  The VM itself only has the VM-HOST's MAC address - but not the ROUTER's.  The VM can communicate with the VM-HOST but not anything else on the same L2 vlan.  All other devices on the same L2 vlan have VM's MAC address (after a ping, say) but the VM never has any of the other hosts in it's arp table.  Seems like packets destined to the VM never make it past the VM-HOST.  I don't see any odd kernel events.

This is the forum post I started prior to this bug - https://forums.virtualbox.org/viewtopic.php?f=7&t=51886

I can attach all the details here if need be."	nocternal
21300	'Assertion Failed' in PGMHandlerPhysicalDeregister	Windows	VirtualBox-7.0.4	2022-11-23T13:04:12Z	2022-11-28T19:06:50Z	2022-11-28T19:06:50Z	"3d mode in VirtualBox-7.0.4 works a little worse than in wine.
I tried to figure out what was wrong and installed Virtualbox with the debug flag. 
The first start of the virtual machine ended with 'Assertion Failed'. 
The problem only appears in 3d mode. 

Host: Gentoo linux

Guest: Windows 10

Backtrace:
{{{

!!Assertion Failed!!
Expression: <none>
Location  : /var/tmp/portage/app-emulation/virtualbox-7.0.4/work/VirtualBox-7.0.4/src/VBox/VMM/VMMAll/PGMAllHandler.cpp(570) int PGMHandlerPhysicalDeregister(PVMCC, RTGCPHYS)
Stack     :
00007f0be44cf7d0 VBoxRT.so!RTAssertMsg2V+0x3f7 (rva:0x28e7d0)

Didn't find range starting at 0000000136b26000

Thread 46 ""VMSVGA FIFO"" received signal SIGTRAP, Trace/breakpoint trap.
[Switching to Thread 0x7f0b504ff6c0 (LWP 613)]
0x00007f0b8bb68403 in PGMHandlerPhysicalDeregister (pVM=0x7f0b6bbde000, GCPhys=5212626944) at /var/tmp/portage/app-emulation/virtualbox-7.0.4/work/VirtualBox-7.0.4/src/VBox/VMM/VMMAll/PGMAllHandler.cpp:570
570	        AssertMsgFailed((""Didn't find range starting at %RGp\n"", GCPhys));
(gdb) bt
#0  0x00007f0b8bb68403 in PGMHandlerPhysicalDeregister(PVMCC, RTGCPHYS) (pVM=0x7f0b6bbde000, GCPhys=5212626944) at /var/tmp/portage/app-emulation/virtualbox-7.0.4/work/VirtualBox-7.0.4/src/VBox/VMM/VMMAll/PGMAllHandler.cpp:570
#1  0x00007f0b8b839f3a in pdmR3DevHlp_PGMHandlerPhysicalDeregister(PPDMDEVINS, RTGCPHYS) (pDevIns=0x7f0b6b9b4000, GCPhys=5212626944)
    at /var/tmp/portage/app-emulation/virtualbox-7.0.4/work/VirtualBox-7.0.4/src/VBox/VMM/VMMR3/PDMDevHlp.cpp:918
#2  0x00007f0b50ae8179 in PDMDevHlpPGMHandlerPhysicalDeregister(PPDMDEVINS, RTGCPHYS) (pDevIns=0x7f0b6b9b4000, GCPhys=5212626944)
    at /var/tmp/portage/app-emulation/virtualbox-7.0.4/work/VirtualBox-7.0.4/include/VBox/vmm/pdmdev.h:9514
#3  0x00007f0b50aea1d9 in vmsvgaR3GboDestroy(PVMSVGAR3STATE, PVMSVGAGBO) (pSvgaR3State=0x7f0b6447f100, pGbo=0x7f0b644801f0)
    at /var/tmp/portage/app-emulation/virtualbox-7.0.4/work/VirtualBox-7.0.4/src/VBox/Devices/Graphics/DevVGA-SVGA-cmd.cpp:629
#4  0x00007f0b50aeafb8 in vmsvgaR3OTableSetOrGrow(PVMSVGAR3STATE, SVGAOTableType, PPN64, uint32_t, uint32, SVGAMobFormat, bool)
    (pSvgaR3State=0x7f0b6447f100, type=SVGA_OTABLE_SURFACE, baseAddress=1482153, sizeInBytes=16384, validSizeInBytes=8192, ptDepth=SVGA3D_MOBFMT_PTDEPTH64_1, fGrow=true)
    at /var/tmp/portage/app-emulation/virtualbox-7.0.4/work/VirtualBox-7.0.4/src/VBox/Devices/Graphics/DevVGA-SVGA-cmd.cpp:833
#5  0x00007f0b50af18b2 in vmsvga3dCmdGrowOTable(PVGASTATECC, SVGA3dCmdGrowOTable const*, uint32_t) (pThisCC=0x7f0b6b9b4180, pCmd=0x7f0b65773c68, cbCmd=24)
    at /var/tmp/portage/app-emulation/virtualbox-7.0.4/work/VirtualBox-7.0.4/src/VBox/Devices/Graphics/DevVGA-SVGA-cmd.cpp:3653
#6  0x00007f0b50afb2b7 in vmsvgaR3Process3dCmd(VGAState*, VGASTATER3*, unsigned int, SVGAFifo3dCmdId, unsigned int, void const*)
    (pThis=0x7f0b6b9b4840, pThisCC=0x7f0b6b9b4180, idDXContext=4294967295, enmCmdId=SVGA_3D_CMD_GROW_OTABLE, cbCmd=24, pvCmd=0x7f0b65773c68)
    at /var/tmp/portage/app-emulation/virtualbox-7.0.4/work/VirtualBox-7.0.4/src/VBox/Devices/Graphics/DevVGA-SVGA-cmd.cpp:5897
#7  0x00007f0b50ad8f11 in vmsvgaR3CmdBufProcessCommands(PPDMDEVINS, PVGASTATE, PVGASTATECC, uint32_t, void const*, uint32_t, uint32_t*, uint32_t*)
    (pDevIns=0x7f0b6b9b4000, pThis=0x7f0b6b9b4840, pThisCC=0x7f0b6b9b4180, idDXContext=4294967295, pvCommands=0x7f0b65773a70, cbCommands=528, poffNextCmd=0x7f0b504feb18, pu32IrqStatus=0x7f0b504feb1c)
    at /var/tmp/portage/app-emulation/virtualbox-7.0.4/work/VirtualBox-7.0.4/src/VBox/Devices/Graphics/DevVGA-SVGA.cpp:3805
#8  0x00007f0b50ad9423 in vmsvgaR3CmdBufProcessBuffers(PPDMDEVINS, PVGASTATE, PVGASTATECC, PPDMTHREAD) (pDevIns=0x7f0b6b9b4000, pThis=0x7f0b6b9b4840, pThisCC=0x7f0b6b9b4180, pThread=0x7f0b644b0ee0)
    at /var/tmp/portage/app-emulation/virtualbox-7.0.4/work/VirtualBox-7.0.4/src/VBox/Devices/Graphics/DevVGA-SVGA.cpp:3909
#9  0x00007f0b50adc420 in vmsvgaR3FifoLoop(PPDMDEVINS, PPDMTHREAD) (pDevIns=0x7f0b6b9b4000, pThread=0x7f0b644b0ee0)
    at /var/tmp/portage/app-emulation/virtualbox-7.0.4/work/VirtualBox-7.0.4/src/VBox/Devices/Graphics/DevVGA-SVGA.cpp:4759
#10 0x00007f0b8b8844fd in pdmR3ThreadMain(RTTHREAD, void*) (Thread=0x7f0b644b1100, pvUser=0x7f0b644b0ee0) at /var/tmp/portage/app-emulation/virtualbox-7.0.4/work/VirtualBox-7.0.4/src/VBox/VMM/VMMR3/PDMThread.cpp:790
#11 0x00007f0be4509d6e in rtThreadMain(PRTTHREADINT, RTNATIVETHREAD, char const*) (pThread=0x7f0b644b1100, NativeThread=139686568785600, pszThreadName=0x7f0b644b19e0 ""VMSVGA FIFO"")
    at /var/tmp/portage/app-emulation/virtualbox-7.0.4/work/VirtualBox-7.0.4/src/VBox/Runtime/common/misc/thread.cpp:759
#12 0x00007f0be4693b84 in rtThreadNativeMain(void*) (pvArgs=0x7f0b644b1100) at /var/tmp/portage/app-emulation/virtualbox-7.0.4/work/VirtualBox-7.0.4/src/VBox/Runtime/r3/posix/thread-posix.cpp:430
#13 0x00007f0be48e2d6a in start_thread () at /lib64/libc.so.6
#14 0x00007f0be49620ac in clone3 () at /lib64/libc.so.6
(gdb) c
Continuing.

!!Assertion Failed!!
Expression: RT_SUCCESS_NP(rc)
Location  : /var/tmp/portage/app-emulation/virtualbox-7.0.4/work/VirtualBox-7.0.4/src/VBox/Devices/Graphics/DevVGA-SVGA-cmd.cpp(630) void vmsvgaR3GboDestroy(PVMSVGAR3STATE, PVMSVGAGBO)
Stack     :
00007f0be44cf7d0 VBoxRT.so!RTAssertMsg2V+0x3f7 (rva:0x28e7d0)

VERR_PGM_HANDLER_NOT_FOUND (-1607) - Specified access handler was not found.
Qt WARNING: QCursor: Cannot create bitmap cursor; invalid bitmap(s)
Qt WARNING: QCursor: Cannot create bitmap cursor; invalid bitmap(s)

Thread 46 ""VMSVGA FIFO"" received signal SIGTRAP, Trace/breakpoint trap.
0x00007f0b50aea251 in vmsvgaR3GboDestroy (pSvgaR3State=0x7f0b6447f100, pGbo=0x7f0b644801f0) at /var/tmp/portage/app-emulation/virtualbox-7.0.4/work/VirtualBox-7.0.4/src/VBox/Devices/Graphics/DevVGA-SVGA-cmd.cpp:630
630	                AssertRC(rc);
(gdb) c
Continuing.

!!Assertion Failed!!
Expression: <none>
Location  : /var/tmp/portage/app-emulation/virtualbox-7.0.4/work/VirtualBox-7.0.4/src/VBox/VMM/VMMAll/PGMAllHandler.cpp(570) int PGMHandlerPhysicalDeregister(PVMCC, RTGCPHYS)
Stack     :
00007f0be44cf7d0 VBoxRT.so!RTAssertMsg2V+0x3f7 (rva:0x28e7d0)

Didn't find range starting at 0000000132627000

Thread 46 ""VMSVGA FIFO"" received signal SIGTRAP, Trace/breakpoint trap.
0x00007f0b8bb68403 in PGMHandlerPhysicalDeregister (pVM=0x7f0b6bbde000, GCPhys=5140279296) at /var/tmp/portage/app-emulation/virtualbox-7.0.4/work/VirtualBox-7.0.4/src/VBox/VMM/VMMAll/PGMAllHandler.cpp:570
570	        AssertMsgFailed((""Didn't find range starting at %RGp\n"", GCPhys));
(gdb) c
Continuing.
Qt WARNING: QCursor: Cannot create bitmap cursor; invalid bitmap(s)

!!Assertion Failed!!
Expression: RT_SUCCESS_NP(rc)
Location  : /var/tmp/portage/app-emulation/virtualbox-7.0.4/work/VirtualBox-7.0.4/src/VBox/Devices/Graphics/DevVGA-SVGA-cmd.cpp(630) void vmsvgaR3GboDestroy(PVMSVGAR3STATE, PVMSVGAGBO)
Stack     :
00007f0be44cf7d0 VBoxRT.so!RTAssertMsg2V+0x3f7 (rva:0x28e7d0)

VERR_PGM_HANDLER_NOT_FOUND (-1607) - Specified access handler was not found.
Qt WARNING: QCursor: Cannot create bitmap cursor; invalid bitmap(s)

Thread 46 ""VMSVGA FIFO"" received signal SIGTRAP, Trace/breakpoint trap.
0x00007f0b50aea251 in vmsvgaR3GboDestroy (pSvgaR3State=0x7f0b6447f100, pGbo=0x7f0b644801f0) at /var/tmp/portage/app-emulation/virtualbox-7.0.4/work/VirtualBox-7.0.4/src/VBox/Devices/Graphics/DevVGA-SVGA-cmd.cpp:630
630	                AssertRC(rc);
(gdb) c

}}}


I found and fixed two bugs: 
{{{
--- a/src/VBox/Devices/Graphics/DevVGA-SVGA-cmd.cpp	2022-11-17 22:12:54.000000000 +0300
+++ b/src/VBox/Devices/Graphics/DevVGA-SVGA-cmd.cpp	2022-11-23 13:42:19.327889043 +0300
@@ -463,6 +463,8 @@
 
     uint32_t const cPPNsPerPage = X86_PAGE_SIZE / (fGCPhys64 ? sizeof(PPN64) : sizeof(PPN));
 
+    RT_ZERO(*pGbo);
+
     pGbo->cbTotal = sizeInBytes;
     pGbo->cTotalPages = (sizeInBytes + X86_PAGE_SIZE - 1) >> X86_PAGE_SHIFT;
 
@@ -631,7 +633,7 @@
             }
         }
         RTMemFree(pGbo->paDescriptors);
-        RT_ZERO(pGbo);
+        RT_ZERO(*pGbo);
     }
 }
 
}}}

At least now the debug version starts without exceptions."	pv32768
18018	'About' box text is unreadable	other	VirtualBox 5.2.18	2018-09-27T16:02:47Z	2023-02-10T01:08:30Z	2023-02-10T01:08:30Z	"virtual Box 5-2
Linux Mint 19 x64 Cinnamon"	JN
20929	"""vboxmanage showvminfo"" creates warning when editing guest settings"	Windows	VirtualBox 6.1.30	2022-05-05T23:58:31Z	2022-05-10T15:38:13Z	2022-05-10T15:38:13Z	"I have a bash script running in the background that checks every few seconds if a VM is running on my second workspace of Mint20. When i am in Virtualbox Manager and want to edit a setting of a VM that is NOT running, i get a warning that the VM is running and not all settings are stored or changed.. every time that script is called. The exact warning is in Dutch, but from the forum is got this in English:

'''""The virtual machine you are changing has been started. Only certain settings can be changed while a machine is running. All other changes will be lost if you close this window now""'''

The line in the bash script is:
'''""vboxmanage showvminfo ""W7_64"" | grep -c ""running (since"" ""'''

So calling ""vboxmanage showvminfo"" creates a warning that the VM is running when you try to edit guest settings.

To create this situation, open vbox manager, click on usb settings an leave that open, then go to the terminal and start ""vbmanage showvminfo"". The warning pops up that the VM is running.

"	RemonK17
17045	"""vboxmanage list hostinfo"" fails if CPUs have gaps in their processor IDs."	other	VirtualBox 5.1.26	2017-08-30T15:21:53Z	2017-08-30T17:03:33Z	2017-08-30T17:03:33Z	"I have a server containing two Intel(R) Xeon(R) CPU X5675[1] @ 3.07GHz with 6 physical cores each and hyperthreading enabled, which results in 24 processors in total. Running ""vboxmanage list hostinfo"" results in the following shortened output:

{{{
VBoxManage: error: Code NS_ERROR_FAILURE (0x80004005) - Operation failed (extended info not available)
VBoxManage: error: Context: ""GetProcessorDescription(i, processorDescription.asOutParam())"" at line 241 of file VBoxManageList.cpp
VBoxManage: error: Code NS_ERROR_FAILURE (0x80004005) - Operation failed (extended info not available)
VBoxManage: error: Context: ""GetProcessorDescription(i, processorDescription.asOutParam())"" at line 241 of file VBoxManageList.cpp
VBoxManage: error: Code NS_ERROR_FAILURE (0x80004005) - Operation failed (extended info not available)
VBoxManage: error: Context: ""GetProcessorDescription(i, processorDescription.asOutParam())"" at line 241 of file VBoxManageList.cpp
VBoxManage: error: Code NS_ERROR_FAILURE (0x80004005) - Operation failed (extended info not available)
VBoxManage: error: Context: ""GetProcessorDescription(i, processorDescription.asOutParam())"" at line 241 of file VBoxManageList.cpp
Host Information:

Host time: 2017-08-29T09:42:55.061000000Z
Processor online count: 24
Processor count: 24
Processor online core count: 12
Processor core count: 12
Processor supports HW virtualization: yes
Processor supports PAE: yes
Processor supports long mode: yes
Processor supports nested paging: yes
Processor#0 speed: 3066 MHz
Processor#0 description: Intel(R) Xeon(R) CPU           X5675  @ 3.07GHz
Processor#1 speed: 3066 MHz
[...]
Processor#11 speed: 3066 MHz
Processor#11 description: Intel(R) Xeon(R) CPU           X5675  @ 3.07GHz
Processor#12 speed: unknown
Processor#12 description: 
Processor#13 speed: unknown
Processor#13 description: 
Processor#14 speed: unknown
Processor#14 description: 
Processor#15 speed: unknown
Processor#15 description: 
Processor#16 speed: 3066 MHz
Processor#16 description: Intel(R) Xeon(R) CPU           X5675  @ 3.07GHz
[...]
Processor#23 speed: 3066 MHz
Processor#23 description: Intel(R) Xeon(R) CPU           X5675  @ 3.07GHz
Memory size: 145055 MByte
Memory available: 143530 MByte
Operating system: Linux
Operating system version: 4.10.0-33-generic
}}}

As you can see, while the overall number of processors is known, the command fails to retrieve the description of some of those. The reason is pretty simple: The implementation uses a loop to iterate all processor IDs and fails, because my IDs have gaps. Look at the following output of lscpu:

{{{
NUMA node0 CPU(s):     0,2,4,6,8,10,16,18,20,22,24,26
NUMA node1 CPU(s):     1,3,5,7,9,11,17,19,21,23,25,27
}}}

The following is the implementation of VBoxManageList.cpp:

{{{
static HRESULT listHostInfo(const ComPtr<IVirtualBox> pVirtualBox)
{
	[...]
	Bstr processorDescription;
	for (ULONG i = 0; i < processorCount; i++)
	{
		CHECK_ERROR(Host, GetProcessorSpeed(i, &processorSpeed));
		if (processorSpeed)
			RTPrintf(""Processor#%u speed: %lu MHz\n"", i, processorSpeed);
		else
			RTPrintf(""Processor#%u speed: unknown\n"", i);
		CHECK_ERROR(Host, GetProcessorDescription(i, processorDescription.asOutParam()));
		RTPrintf(""Processor#%u description: %ls\n"", i, processorDescription.raw());
	}
	[...]
}
}}}

12, 13, 14 and 15 are not used currently and I'm pretty sure that I don't have any influence on those IDs. Have double-checked the BIOS and from what I've researched on the topic on how those IDs are assigned, I have the feeling that this is really some attribute of the CPUs itself and only used by the Linux kernel, not assigned. So gaps in those IDs should be a valid use case:

> The x2APIC id space is not continuously mapped to logical processors however; there can be gaps in the mapping, meaning that some intermediate x2APIC ids don't necessarily correspond to any logical processor.

https://en.wikipedia.org/wiki/CPUID#EAX.3D4_and_EAX.3DBh:_Intel_thread.2Fcore_and_cache_topology

{{{
c->cpu_core_id = apic->phys_pkg_id(c->initial_apicid, index_msb) &
 				       ((1 << core_bits) - 1);
}}}


http://elixir.free-electrons.com/linux/v4.0.9/source/arch/x86/kernel/cpu/common.c#L546

http://elixir.free-electrons.com/linux/v4.0.9/source/arch/x86/include/asm/processor.h#L114

With 8-core CPUs in mind, the gap of 2 per CPU might even make sense, because it's one additional core with hyperthreading, while the other core might simply be added at the end of the IDs.

So it seems using a loop might be a bit too naive and needs to be reworked to really use the available CPU IDs. I didn't came across any other errors like this one for now and hosting some VMs it looks like all CPUs are used by VirtualBox properly.

[1]: https://ark.intel.com/de/products/52577/Intel-Xeon-Processor-X5675-12M-Cache-3_06-GHz-6_40-GTs-Intel-QPI"	Thorsten Schöning
17319	"""VBoxManage guestcontroll run"" stdin/out redirection not working"	Windows	VirtualBox 5.1.30	2017-11-28T08:49:49Z	2017-11-28T15:18:10Z	2017-11-28T15:18:10Z	"I'm trying to run a python script inside a Windows 7-64bit virtual machine, redirecting stdin and stdout from/to Ubuntu 17.10 host.

GuestAdditions and python have been installed on the VM. I placed the python script on a shared directory.

The following commands never exits and does not echo anything until I pressed CTRL+C :

{{{
echo -1 | VBoxManage --nologo guestcontrol ""w764 Clone"" run --username Hector --password hectorH --exe ""C:\Python27\python.exe"" --wait-stdout -- E:\test.py
}}}

Here is the script ""test.py"":


{{{
print(""Hello"")
while True:
    s = raw_input()
    a = int(s)
    print(a)
    if a < 0:
        break
}}}

I first tried to run it inside a windows terminal on the VM, and this works:

{{{
c:\> c:\python27\python.exe E:\test.py
Hello
-1
-1
}}}

To make sure the login parameters are ok, I run iexplore with success:
{{{
VBoxManage --nologo guestcontrol ""w764 Clone"" run username Hector --password hectorH --exe ""C:\Program Files\Internet Explorer\iexplore.exe""
}}}
"	shangouet
20155	"""VBoxManage convertfromraw --format=vdi"" silently fails?"	Linux	VirtualBox 6.1.18	2021-01-26T09:35:15Z	2023-01-18T19:33:51Z	2023-01-18T19:33:51Z	"I have a raw image that perfectly runs with qemu-kvm, obtained with a Ubuntu Server headless install.

I'm trying to convert this raw image to VDI using VBoxManage, but it appears to fail while not providing any error message.

More precisely, here is what happens:

1) I run this command :


{{{
$ VBoxManage convertfromraw --format vdi output/mini-ubuntu-base.img output/mini-ubuntu-base.vdi
}}}


2) It prints what follows and appears to be running (and my CPU load does tell it is running):


{{{
Converting from raw image file=""output/mini-ubuntu-base.img"" to file=""output/mini-ubuntu-base.vdi""...
Creating dynamic image with size 21474836480 bytes (20480MB)...
}}}


3) *While* it is running, using a second terminal, I can see that a VDI file is being created :


{{{
$ ls -lah output | grep vdi
-rw-------. 1 ebo ebo 6,5G 26 janv. 10:28 mini-ubuntu-base.vdi
}}}


4) But then, when the 'VBoxManage' command returns… the VDI file has disappeared!


{{{
$ ls -lah output | grep vdi
<nothing>
}}}

Which means something went wrong somewhere I suppose, but I tend to believe that some output should tell so?


Additional note: I have other raw images obtained through a similar process that I manage to convert into VDI using VBoxManage without problem using my current environment."	ebo
15184	"""reopening"" 14286"	Windows	VirtualBox 5.0.14	2016-02-28T05:08:25Z	2016-02-29T08:09:37Z	2016-02-29T08:09:37Z	"Attempted to re-open 14286:  Allowed update, but could not change to open/reopened.

Here is my update to the closed/obsolete ticket:

I'm having this same problem. Just started after applying a kernel patch requiring a reboot. So, I tried to find updates/patches and ended up pulling down the latest RPM for SUSE 13.2 64bit.

Here is what I get when I attempt to fire up my W7 Home Premium under VBox (was a working image prior to the kernel patch).

Failed to open a session for the virtual machine W7 Home Premium.

The VM session was aborted.

Result Code: NS_ERROR_FAILURE (0x80004005) Component: SessionMachine Interface: ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}

VBox 5.0.14 r105127 is what is shown with About VirtualBox

Let me know what more you want for diagnosing this.
"	Wylbur
16172	"""One or more disk image files are not currently accessible (...)"" error, but the file is there and the VM starts"	Windows	VirtualBox 5.1.8	2016-11-09T13:17:57Z	2020-04-07T04:52:25Z	2020-04-07T04:52:25Z	"Hi All,
I've upgraded to version 5.1.8 r111374 using the Fedora 24 packages. I only have one Windows 10 VM that I've been using without issues for many months.

Since upgrading, every time I start VirtualBox (not the VM) I get the error saying: ""One or more disk image files are not currently accessible. As a result, you will not be able to operate virtual machines that use these files until they become accessible later. Press Check to open the Virtual Media Manager window and see which files are inaccessible, or press Ignore to ignore this message."".

The file is the VM's sole vdi file, but it is not missing, and if I click on Ignore the VM starts without any issues. Stopping and restarting the VM does not show the error again. Shutting down VirtualBox and restarting it shows the error again.

It is just an annoyance for now but perhaps it can develop in something worse.
"	giacecco
16327	"""Auto Capture keyboard"" option doesn't work"	all	VirtualBox 5.1.12	2016-12-25T12:43:41Z	2019-09-20T04:03:06Z	2019-09-20T04:03:06Z	"Virtualbox captures keyboard even when told to not do so.

Steps to reproduce:

1. Open a VM (e.g. create an empty one).
2. Go to Preferences → Input, and make sure the ""Auto Capture Keyboard"" is disabled.
3. Run the VM.
4. Focus the VM window (e.g. click on it)
5. Try global hotkeys of the host, like switching workspaces, windows, a player — nothing works.

It seem to be a regression to the old [https://www.virtualbox.org/ticket/8596 #8596], but I'm not naming it so because I don't know when it stopped working.

Tested on Archlinux, i3 WM."	Hi-Angel
