﻿ticket	summary	version	created	modified	_changetime	_description	_reporter
15248	"""BUG: unable to handle kernel paging request"""	VirtualBox 5.0.16	2016-03-17T07:00:19Z	2016-03-17T07:02:28Z	2016-03-17T07:02:28Z	"VirtualBox 5.1.6. Host is OSX 10.11.3, guest is recent Arch Linux amd64 (4.4.5 kernel). Guest has VM Guest Additions installed.

The kernel periodically BUGs under heavy load (mostly compiling a large C++ project using `make -j 4`; VM is configured to use 4 CPUs).

Attaching dmesg output, as well as VBOX.log"	neilc
18337	"""Create a Shortcut on Desktop"" overwrites existing shortcut with no warning"	VirtualBox 5.2.0	2019-01-19T20:42:43Z	2019-01-21T22:25:35Z	2019-01-21T22:25:35Z	"The issue was brought to my attention on IRC by ""instantp10neer"" and later in a discussion in the forums: https://forums.virtualbox.org/viewtopic.php?f=6&t=91366 by ""corhsin"" (same user).

If you have a shortcut to the Desktop named exactly as your shortcut-want-to-create, the ""Create a Shortcut on Desktop"" action overwrites the existing shortcut without asking for confirmation.

'''__Steps to reproduce__'''
* Create a shortcut on the desktop named ""Anything"" that points to a text document (for example).
* Create a new VM in !VirtualBox named ""Anything"".
* Right-click on the VM, ""Create a Shortcut on Desktop"".
* The existing shortcut is overwritten without any confirmation.

'''__Solution__'''
* Have a confirmation dialog:
> ''The shortcut/alias ""Anything"" already exists on the Desktop. Do you want to overwrite it? Y/N''\\
\\
BTW, this occurs since 5.2.0 (didn't go further back, but I don't doubt that it's there for ever), and it happens on Win/Linux hosts. On OSX hosts, the same operation results in a NoOp..."	Socratis
14545	"""Failed to create host network interface"" on Windows 10"		2015-09-05T17:15:35Z	2018-09-12T08:34:35Z	2018-09-12T08:34:35Z	"I'm trying to get Xamarin Android Emulator working on Windows 10.  It's failing because VirtualBox does not have a host network adapter set up.  It worked fine on Windows 8.

When I attempt to create a host network adapter in Virtual Box, I get this error:

""Failed to create the host network interface
Result Code: 
E_FAIL (0x80004005)""

I've tried doing a uninstalling/reinstalling, and doing a repair install.  I don't know if this is related to #14040, but I'm using the latest beta, which supposedly fixed that issue..

Version: 5.0.3-102322-Win"	BlueRaja
14969	"""Insert Guest Additions CD image..."" should not have trailing ""..."""	VirtualBox 5.0.12	2015-12-23T01:29:18Z	2015-12-23T01:29:18Z	2015-12-23T01:29:18Z	"I'm running VirtualBox-5.0.13-104829-Win on Windows 7 Pro SP1 x64.

In the virtual machine window's menu (when the VM is not running full screen), or the mini-toolbar (when VM is full screen), the Devices menu includes an item ""Insert Guest Additions CD image..."". The trailing ""..."" is probably incorrect. So far as I can tell there is no subsequent dialog - the virtual CD is inserted without further response from the user.

(The guest machine itself may then present a prompt if, for example, Windows AutoPlay is enabled, but that's not the host's concern.)
"	m6477
19943	"""Invalid Settings Detected"" System : Acceleration page"	VirtualBox 6.1.14	2020-10-06T10:43:35Z	2020-10-06T10:43:35Z	2020-10-06T10:43:35Z	"I tried to use ""old"" machine (created in previous versions of virtualbox) with the actual Virtualbox 6.1.14. But I got a problem described by other people

https://www.reddit.com/r/virtualbox/comments/efffap/i_have_a_problem_invalid_settings_detected/

https://www.reddit.com/r/virtualbox/comments/eig7f4/invalid_settings_detected/


It looks like there was a checkbox ""Enable VT-x|AMD-V"" in Settings>System>Acceleration in 6.0.x linked to the ""Invalid Settings Detected"" alert.

And it looks like in 6.1.x the checkbox was removed but the requirement to unset it was left somehow. 
"	jekka
16172	"""One or more disk image files are not currently accessible (...)"" error, but the file is there and the VM starts"	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
19195	"""Scaled Mode"" makes mouse unusable (lag / slow)"	VirtualBox 6.1.0	2020-01-03T17:39:10Z	2020-01-03T17:39:10Z	2020-01-03T17:39:10Z	"I am trying to install Windows 98 as a guest in MacOS 10.15.2. The screen is HighDPI, so by default I can't see a thing because the 640x480 virtual screen is way to small (ca. 7 x 5.5 cm).
Full screen mode doesn't change anything, the 7x5.5cm window is just in the center of a large black screen.

""Scaled Mode"" does make the window bigger, so this is ok. However, as soon as the screen is scaled up, the mouse becomes unusable. It lags extremely, and overshoots when stopped.

Obviously, there is no guest support even after Windows 98 is installed. "	T1nue
18388	"""The instruction at 0x000000006BC88A90 referenced memory at 0x0000000000000008. The memory could not be read."" when trying to open Devices > Optical Drives"	VirtualBox 5.2.26	2019-01-30T10:53:05Z	2020-04-05T11:30:06Z	2020-04-05T11:30:06Z	"Im using
Host: Windows 10 Pro 64 bit v1803
VB: VirtualBox 5.2.26r128414
Guest: Ubuntu 18.04

Getting the error consistently."	custard130
20155	"""VBoxManage convertfromraw --format=vdi"" silently fails?"	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
19097	"""VirtualBox manager has stopped working"" when removing laptop from docking station"	VirtualBox 6.0.14	2019-11-20T06:38:46Z	2019-11-20T06:49:34Z	2019-11-20T06:49:34Z	"When unddocking/docking my laptop (Fujitsu, Lifebook E Series) from the docking station the VirtualBox manager crashes with a dialog message: ""VirtualBox Manager has stopped working.

I'm running: Windows 10 x64 as host and have one virtual machine running at that time: ""Ubuntu 18.04.3 LTS"". This machine remains working, but the VM Manager is crasing. I followed the instructions to create a coredump which is attached.

My VM also crashes sometimes on dock/undock but here I need to gather more information and will file another ticket.

Expected behavior: Manger should not crash on dock/undock"	martg
18018	'About' box text is unreadable	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
18390	'memory could not be read' crash in Linux guest / Windows host 6.02 and 6.04	VirtualBox 6.0.4	2019-01-30T17:32:41Z	2019-08-21T13:09:11Z	2019-08-21T13:09:11Z	"I am running a Linux guest (Mint Virtualbox image downloaded from www.osboxes.org) in a Windows 10 host.

I started running this guest under VirtualBox 6.0.2 and experienced this crash. A couple of days later I noticed 6.0.4 was available and tried updating to that to see whether it had been fixed, but the crash is still occurring and has happened 3x today, so it is fairly regular.

The guest isn't running too much - it's being used as a dev box with Docker (postgres / pgAdmin) and VS Code. There doesn't seem to be a particular pattern in what I'm doing before a crash. The VM doesn't have many modifications to base settings - 2 CPU, bidir clipboard and 2 networks (NAT and Host Only).

The error message is:
'The instruction at 0x00007FFC612061E3 referenced memory at 0x00000000000010. The memory could not be read'

I have attached the output from VBoxBugReport"	MattA
21080	'NS_ERROR_FAILURE' and '/sbin/rcvboxdrv' and similar commands produce a 'not found' error	VirtualBox 6.1.36	2022-08-26T18:25:43Z	2022-08-26T18:25:43Z	2022-08-26T18:25:43Z	"I had a 6.1 version of Virtual Box installed on Mint 20.3 Cinnamon (which is based upon Ubuntu 20.04). I did an in-place upgrade to Mint 21.0 (based on Ubuntu 22.04). The upgrade removed VirtualBox. I reinstalled VirtualBox, from Mint's repositories. Then I obtained the relevant expansion pack and installed that. 

Then I ran VirtualBox and tried to launch my existing VM, I received a 'NS_ERROR_FAILURE' message (the details of which, incidentally, where invisible until I highlighted them by selecting the relevant text). As part of the recovery procedure (on which I have notes, from previous problems with VirtualBox) I tried `sudo /sbin/rcvboxdrv setup`. Result: 'bash: /usr/lib/virtualbox/vboxdrv.sh: No such file or directory'. After some websearching, I discovered the command `/usr/lib/virtualbox/vboxdrv.sh setup`. Result: again, not found."	NotAlwaysGruntled
9527	'Shared Folders' returning incorrect file order to Win API	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
18420	'Solid State Disk' setting after snapshot not detected by Linux 4.15.0 guest	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
17289	'Take Screenshot' doesn't remember last directory location	VirtualBox 5.2.0	2017-11-18T06:43:18Z	2017-11-18T06:43:18Z	2017-11-18T06:43:18Z	"I just used 'Take Screenshot' to take a bunch of screenshots and for each screenshot I wanted to save I had to switch to the directory that I had used to take the previous screenshot. In other words I wanted all the screenshots in one folder that was not my VM folder.

My suggestion is that you change VirtualBox to remember the previous location. My host is Windows and in that OS it's commonplace to use the last selected location.

Version 5.2.0 r118431 (Qt5.6.2), Windows 7 host.
"	quiettime
18846	'VBoxManage showvminfo' while VM Settings is open causes VirtualBox to think the VM is running	VirtualBox 6.0.10	2019-08-16T17:29:15Z	2019-08-17T08:06:06Z	2019-08-17T08:06:06Z	"'''Steps to recreate'''
* Create a new VM, or use an existing one.
* Open the VM Settings for the VM.
* On a Terminal run the command ""`VBoxManage showvminfo <VM>`"".
* !VirtualBox warning complains that the VM is running:\\
 > ''The virtual machine that 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.''"	Socratis
14215	(Windows 7) Guru Meditation -226 (VERR_INTERNAL_ERROR_2)	VirtualBox 4.3.28	2015-06-21T10:01:44Z	2015-07-06T00:56:59Z	2015-07-06T00:56:59Z	I was trying to install Visual Studio Community 2015 RC on Win7 x64 guest and during component selection got Guru Meditation. No Guru Meditation on the second try.	tico-tico
17857	- Buscador	VirtualBox 5.2.14	2018-07-05T15:43:32Z	2018-07-09T09:00:19Z	2018-07-09T09:00:19Z	"Hello!

We have 3 MacBook Pro's, all running High Sierra (10.13.5), all with the same error after opening a Buscador ISO 2-3 times. The first time it works fine, it seems to run into the boot error sometime later.

I saw an error in a few of the logs: vmmdev guest log bios cd rom boot failure code 0004

Not sure if this is a generic error, or something more telling. Any help would be appreciated, thanks!

"	Kujo
10598	--timesync-set-on-restore syncs time up to 10 seconds after snapshot restore	VirtualBox 4.0.16	2012-05-24T13:44:54Z	2012-05-25T13:35:49Z	2012-05-25T13:35:49Z	"I have a Linux guest(additions 4.0.16) and a Windows host(vbox 4.0.16). The guest service is started via:
{{{
/usr/sbin/vboxguest-service -f -vvvvv --disable-vminfo --disable-cpuhotplug --disable-vmstats --disable-automount --disable-memballoon --timesync-set-threshold 1000 --timesync-set-on-restore 1
}}}

If I restore a snapshot of this machine, even one that is 7 days old, the time is not synced on restore.
~10 seconds (timesync-interval?) after resuming the VM, the vboxguest-service outputs ""The VM session ID changed, forcing resync."" and time is actually synced.

This causes trouble when working with certificates that are generated after taking the snapshot, so for some use cases this is really annoying."	insecure
18732	.iso file not listed when attempting to add it to a VM	VirtualBox 6.0.8	2019-06-30T06:36:54Z	2019-07-06T10:29:21Z	2019-07-06T10:29:21Z	"Howdy,

I just upgraded VB to this level: VirtualBox-6.0.97-131601-Linux_amd64.run but VB still doesn't list the .iso image clonezilla-live-20160210-wily-amd64.iso.

Am I missing something here?

Thanks,

George...

Here's what the file command says about this image:

file clonezilla-live-20160210-wily-amd64.iso
clonezilla-live-20160210-wily-amd64.iso: DOS/MBR boot sector; partition 2 : ID=0xef, start-CHS (0x3ff,254,63), end-CHS (0x3ff,254,63), startsector 427660, 14988 sectors"	George R. Goffe
11029	/etc/init.d/vboxautostart-service stop has no effect	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
17232	/sbin/vboxconfig fails during upgrade of Vbox	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
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'	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
20314	0x00007FF874BF9B2C address	VirtualBox 6.1.18	2021-04-22T12:49:41Z	2021-04-22T12:49:41Z	2021-04-22T12:49:41Z	"After closing the VM, the screen1.png popup. Nothing else. 
screen1.png : 
""0x00007FF874BF9B2C address refer to 0x00007FF874BF9B2C address direction. This can't be written. 
Press Ok... Ok"""	Aec_A
17157	100% CPU usage (windows 10 VM) running on WIndows 10 VM	VirtualBox 5.1.28	2017-10-11T14:44:00Z	2017-10-11T16:55:55Z	2017-10-11T16:55:55Z	"I've recently moved 2 virtual PCs from a windows 10 PC to another windows 10 Pc. They have the same hardware spec. When I run the VM's on the new PC they just run at 100% CPU usage (after login). This did not occur on the other PC. 
I created a new Windows 10 VM and this seems to work with the CPU usage issue.
I have checked various settings on the W10 VM and on the Oracle Virtual Machine settings. They are not 'useable' on the new machine. I did upgrade from VM 5.1.22 to 5.1.28. I need to use the VM's on the new PC - but the CPU issue is stopping any productive use."	RhUkDev
15359	20% clock drift in the guest	VirtualBox 5.0.18	2016-04-27T09:12:25Z	2016-04-29T08:34:13Z	2016-04-29T08:34:13Z	"The clock of my guest runs at 80% of the speed of the host clock: Invoking date and 60s later invoking it again, only 48s have passed in the guest.

Host: Windows 7 Professional 64bit
Guest: Linux Mint 17.1 64bit

"	meixner
16687	2D Acceleration breaks Scaled mode (Windows 7 host, Windows XP guest).	VirtualBox 5.1.20	2017-04-22T14:06:43Z	2017-04-22T14:11:06Z	2017-04-22T14:11:06Z	"Trying to run Starcraft 1.16, the graphics appear corrupted, with lines running all over the place.

With 2D acceleration disabled, starcraft renders scaled to window size just fine."	Danial
19262	2D graphics performance issue when increasing the number of cores	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
14423	2nd screen window - Fail to open	VirtualBox 4.3.30	2015-08-10T13:17:56Z	2015-08-14T14:09:13Z	2015-08-14T14:09:13Z	"I have seen an old ticket on this, which is marked as fixed. I am using 4.3.30 and I have the same or similar issue. I guest the root cause is different.

I also posted on the forum but no reply after 2 weeks.

So, my issue is that the 2nd window, representing the 2nd screen/display configured in my VM does not open up when I start my VM.

I am using Ubuntu 14.04 as the host and a Win 7 Guest. All 64 bits. I actually have 2 identical setups (except one is a desktop while the other is a laptop). On the desktop, I have no issue but on the laptop, after using the setup for a while, I can not get the 2nd display to open up. Initially, it was Ok.

VirtualBox is 4.3.30

In the guest (Win), I can see that the 2nd display is shown but settings are grayed out; this looks like the driver is loaded for the 2nd display but somehow VirtualBox tells Windows that the 2nd monitor is off, which is consistent with the fact that there is not a 2nd window opened."	Claude
19159	3 Crashes of VirtualBoxVM running Ubuntu 18.04 guest on macOS 10.14.6 host	VirtualBox 6.1.0	2019-12-14T16:51:13Z	2019-12-14T16:51:13Z	2019-12-14T16:51:13Z	"I am running VirtualBox Version 6.1.0 r135406 (Qt5.6.3) on a macOS Mojave 10.14.6 host. Guest OS is Ubuntu 18.04.3 (that's what I installed) but ""uname -a"" says:

Linux Ubuntu-1804-VirtualBox 5.0.0-36-generic #39~18.04.1-Ubuntu SMP Tue Nov 12 11:09:50 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

I think this is the case because I have the 6.1 guest additions installed."	Lars Sonchocky-Helldorf
16692	3D acceleration causes Excel to fail to open with a file	VirtualBox 5.1.20	2017-04-25T03:41:59Z	2017-04-25T03:41:59Z	2017-04-25T03:41:59Z	"Double clicking a xlsx file gives the error

{{{
There was a problem sending the command to the program
}}}

under this setting
{{{
VirtualBox
Enable 3D Acceleration
Enable 2D Video Acceleration

Excel
Enable hardware graphic acceleration
}}}

The following settings work fine
{{{
VirtualBox
Enable 3D Acceleration
Enable 2D Video Acceleration

Excel
Disable hardware graphic acceleration
}}}

{{{
VirtualBox
Disable 3D Acceleration
Enable 2D Video Acceleration

Excel
Enable hardware graphic acceleration
}}}

Excel 2016[[BR]]
Guest Windows 10[[BR]]
Host OS X 10.12.4 (16E195)"	Keith Yip
14786	3D acceleration issues persisting on Intel HD video Card	VirtualBox 5.0.8	2015-11-04T17:05:36Z	2015-11-04T17:05:36Z	2015-11-04T17:05:36Z	"Hello

I was very excited about the latest virtual box release (5.08) after I read the change log mentioning bug fixes to 3D acceleration. Unfortunately, I am still having issues.

The problem seems to be with my pixel shader version. I am unable to use some applications due to not having pixel shader version 3.o

Here is a screenshot of a system scan from http://cyri.systemrequirementslab.com/

https://imgur.com/eHQh9c2

Here is my about page from my mac:
https://imgur.com/NM8CSE7

As you can see, the virtual box drivers are still not supporting pixel shader 3.0 which I need to run some of my programs. 

Any help would be appreciated!

"	new61
20528	3d acceleration with VMSVGA sometimes leads to a crash or a hang of VirtualBox	VirtualBox 6.1.26	2021-08-30T20:40:34Z	2021-08-30T20:40:34Z	2021-08-30T20:40:34Z	"When using a Linux VM (debian 9/10) and Windows host with VMSVGA video adapter and 3d acceleration, the VM sometimes might crash or hang. The crash/hang happens in a few minutes after we start a video conferencing app in the browser (with a webcam enabled). With 3d acceleration disabled there is no crash.

When the crash occurs, the error message is ""The instruction at .... referenced memory at 0x0000000000000010...""

The steps to reproduce:

1. Start a VM
2. Forward the webcam to the VM (via VBox UI, Devices->Webcams)
3. Open Google Chrome or Chromium browser. We tried various versions, e.g. Chrome 78.0.3904.108, 64-bit and Chromium 90.0.4430.212, 64-bit. The checkbox ""Use hardware acceleration when available"" needs to be enabled in the browser settings (it is enabled by default).
4. Navigate to zoom.us and login (a free account is enough).
5. Host a meeting with a webcam enabled. The meeting needs to be started in the browser, not in the native linux app. There is no need for others to join the meeting.
6. If it doesn't hang or crash immediately - give it a few minutes to run. And if it doesn't crash now - close the browser (sometimes the crash only happens when closing the browser).

Attached are 2 logs: one with a crash with Chromium 90 and another one with a hang with Chromium 83. The hang has happened when the ""accept cookies"" window from zoom.us was loading: it turned out to be completely corrupted and the VM hang occurred. The error in the log is VMSVGA related but is different to what I see in case of a crash. In the attached logs Hyper-V is enabled. But this doesn't make a difference and we can reproduce this issues with Hyper-V disabled as well.

This problem was first reported in https://www.virtualbox.org/ticket/19154. 
I did more tests today trying to reproduce the problem using Nvidia GPU, but couldn't. Today I also couldn't reproduce the problem using Intel GPU and exactly the same setup as I was using previously. So the problem is not 100% reproducible, unfortunately (until today I could reproduce it all the time - ~20-30 times or so). If I see the problem again, I will do tests with NVidia and will update the ticket."	Mikhail Kovalev
19208	3d acecleration breaks VMSVGA	VirtualBox 6.0.14	2020-01-08T11:15:09Z	2020-01-16T10:33:20Z	2020-01-16T10:33:20Z	The Vivaldi browser gets broken when 3d acceleration is enabled with the graphics controller set to VMSVGA. Several users now experienced the issue while trying to run Vivaldi on Linux (ubuntu 18 in my case).	VincentX
19207	3d acecleration breaks VMSVGA	VirtualBox 6.0.14	2020-01-08T11:15:00Z	2020-01-08T11:19:43Z	2020-01-08T11:19:43Z	The Vivaldi browser gets broken when 3d acceleration is enabled with the graphics controller set to VMSVGA. Several users now experienced the issue while trying to run Vivaldi on Linux (ubuntu 18 in my case).	VincentX
16845	3D stopped working in Ubuntu 16.04 with NVIDIA  nouveau 1.0.0	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
14597	5.0.4 - Guru Meditation - VERR_REM_VIRTUAL_CPU_ERROR	VirtualBox 5.0.4	2015-09-16T06:44:47Z	2015-11-25T16:09:23Z	2015-11-25T16:09:23Z	"I've been using VirtualBox for a while 4.3.18 - 4.3.30 where i have a VM with a live snapshot.
after upgrading to 5.0.4 i've got a problem on my 4.3.30 created VM: ""Guru Meditation - VERR_REM_VIRTUAL_CPU_ERROR""
reverting back 4.3.30 runs the VM fine but not with 5.0.4

Host: Windows 7 x64
guest: Linux based OS

see also: 
[https://forums.virtualbox.org/viewtopic.php?f=6&t=70070]
"	talr
15618	5.1 and Windows XP machine crashes (raw mode, VERR_REM_VIRTUAL_CPU_ERROR Guru)	VirtualBox 5.1.0	2016-07-14T18:40:56Z	2016-09-23T22:00:33Z	2016-09-23T22:00:33Z	Just upgraded to 5.1 from 5.0.24 - and Windows XP machine crashes every time you try to load. The saved session crashed. The fresh boot crashed. I can do a Windows Safe boot (and loaded the new utilities there), but a regular boot still crashes.	Trolleyfan
16474	5.1 installation fails on Sierra due to kext load issue	VirtualBox 5.1.14	2017-02-09T15:56:45Z	2017-11-09T14:59:33Z	2017-11-09T14:59:33Z	"Tested on Mac OS X 10.12.3, fairly recently installed with virtualbox 5.1.14.

{{{
Feb  9 16:46:22 oiketes installd[429]: PackageKit: prevent user idle system sleep
Feb  9 16:46:22 oiketes installd[429]: PackageKit: suspending backupd
Feb  9 16:46:22 oiketes installd[429]: PackageKit: Executing script ""./preflight"" in /private/tmp/PKInstallSandbox.BOhp2m/Scripts/org.virtualbox.pkg.virtualbox.DqpVZp
Feb  9 16:46:22 oiketes installd[429]: PackageKit: Using trashcan path /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/PKInstallSandboxTrash/B4A71E15-7725-4A78-A613-652406DB7FB1.sandboxTrash for sandbox /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/C/PKInstallSandboxManager/B4A71E15-7725-4A78-A613-652406DB7FB1.activeSandbox
Feb  9 16:46:22 oiketes install_monitor[96974]: Temporarily excluding: /Applications, /Library, /System, /bin, /private, /sbin, /usr
Feb  9 16:46:22 oiketes installd[429]: PackageKit: Shoving /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/C/PKInstallSandboxManager/B4A71E15-7725-4A78-A613-652406DB7FB1.activeSandbox/Root (3 items) to /
Feb  9 16:46:22 oiketes installd[429]: PackageKit: Executing script ""./postflight"" in /private/tmp/PKInstallSandbox.BOhp2m/Scripts/org.virtualbox.pkg.vboxkexts.2lA03l
Feb  9 16:46:22 oiketes installd[429]: ./postflight: /Library/LaunchDaemons/org.virtualbox.startup.plist
Feb  9 16:46:22 oiketes installd[429]: ./postflight: /Library/Application Support/VirtualBox/VBoxDrv.kext failed to load - (libkern/kext) kext (kmod) start/stop routine failed; check the system/kernel logs for errors or try kextutil(8).
Feb  9 16:46:22 oiketes install_monitor[96974]: Re-included: /Applications, /Library, /System, /bin, /private, /sbin, /usr
Feb  9 16:46:23 oiketes installd[429]: PackageKit: releasing backupd
Feb  9 16:46:23 oiketes installd[429]: PackageKit: allow user idle system sleep
Feb  9 16:46:23 oiketes installd[429]: PackageKit: Install Failed: Error Domain=PKInstallErrorDomain Code=112 ""An error occurred while running scripts from the package “VirtualBox.pkg”."" UserInfo={NSFilePath=./postflight, NSURL=file://localhost/Volumes/VirtualBox/VirtualBox.pkg#VBoxKEXTs.pkg, PKInstallPackageIdentifier=org.virtualbox.pkg.vboxkexts, NSLocalizedDescription=An error occurred while running scripts from the package “VirtualBox.pkg”.} {
	    NSFilePath = ""./postflight"";
	    NSLocalizedDescription = ""An error occurred while running scripts from the package \U201cVirtualBox.pkg\U201d."";
	    NSURL = ""file://localhost/Volumes/VirtualBox/VirtualBox.pkg#VBoxKEXTs.pkg"";
	    PKInstallPackageIdentifier = ""org.virtualbox.pkg.vboxkexts"";
	}
}}}

In dmesg I see:

{{{
VBoxDrv: vmx_resume=ffffff801a817fb0 vmx_suspend=ffffff801a817f60 vmx_use_count=ffffff801ae8e7c0 (0) cr4=0x1627e0
VBoxDrv: cdevsw_add failed (-1)
}}}

I'm not sure how to debug this problem further at the moment
"	Mike446
16841	5.1.18 working on Mavericks, but not with 5.1.20	VirtualBox 5.1.22	2017-06-18T09:12:32Z	2017-08-17T15:06:53Z	2017-08-17T15:06:53Z	"5.1.20 on Mavericks crash when starting without showing gui, 
but 5.1.18 works fine"	steven_c
17042	5.1.26, Mac OS X, VM aborts when external monitor/keyboard/mouse is unplugged	VirtualBox 5.1.26	2017-08-28T19:21:43Z	2017-08-29T15:35:42Z	2017-08-29T15:35:42Z	"Hello, 

Setup: VirtualBox 5.1.26 on Mac OS X 10.11.6 (El Capitan), guest os is Linux Ubuntu 14.0.4 LTE. Dual monitor. Keyboard, mouse and external monitor are routed from the lightning connector on the mac through an El Gato Thunderbolt2 Dock box. Specifically, the setup looks like:

MAC (lightning connector) -> El Gato Dock (USB + video cables) -> Dell U3415W monitor (USB ports)-> Keyboard, Mouse 

I updated today to 5.1.26 from '24. On the previous version I used to be able to unplug the lightning connector to the dock box from the Mac,  and the VM window would just move to the builtin display and keep going, receiving input from the builtin keyboard and trackpad.

However, on the new version the VM aborts instantly and repeatably as soon as I unplug the connector. 
  "	khomeino
17148	5.1.28 r117968 (Qt5.6.2) VBoxTray.exe bug	VirtualBox 5.1.28	2017-10-09T08:26:01Z	2017-11-20T06:21:15Z	2017-11-20T06:21:15Z	"Drag a file into VBox system(Win7),and then drag out without drop,the cpu will up to 90% .

ps: VBox installed in MAC OS X 10.11.6

"	fermi1981
16072	5.1.6 messed them up, shortkeys, session information window	VirtualBox 5.1.6	2016-10-16T21:46:12Z	2016-10-16T22:51:43Z	2016-10-16T22:51:43Z	"Myself is not familiarized with VB's internal architecture, so hard to select proper ""component"".

5.1.6 is the first 5.1 version used with this config.
Host OS X 10.9.5
Guests Ubuntu 64Bits Desktop 16.04 LTS
In prior of this - I guess - 5.0.26 was in use without any probs.
Build 110634 was downloaded and installed few hours ago and still in use this minute.
V.M.s run in full-screen mode.

(A)
Host key combination without effect, short-keys practically not working,
e.g. full-screen shortkey, pause V.M. short key, pop-up menu while in full-screen shortkey
Occasionally host's shortkey for making screenshots on host which doesn't have
anything in common with VB nor with its virtual machines is not working.

(B)
While in full-screen mode opening the Session Information window/dialog works quite differently
as it was before upgrade to 5.1. This dialog gets maximized to full-screen, some other 
white-background window/dialog seems to be opening in its background, closing Session Information dialog leaves some strange screen (grey background) with no function - strange host's workspaces."	Nikc
17235	5.2 causes blue screen of death on windows 10	VirtualBox 5.2.0	2017-11-04T03:22:51Z	2017-12-11T20:00:20Z	2017-12-11T20:00:20Z	"I upgraded from 5.1.30 to 5.2 to use my ubuntu 17.04 and 17.10 machines. I had multiple BSOD per hour until I reverted to 5.1.30. No BSOD since then.

I have a Surface Pro 4 with the latest Windows 10 updates.

Sorry, I could not capture the error code or QR on the blue screen before the PC rebooted."	silvermangb
17228	5.2.0 breaks NVMe support on Win10 1703 or later [regression]	VirtualBox 5.2.0	2017-10-31T12:02:02Z	2021-07-05T21:23:28Z	2021-07-05T21:23:28Z	"NVMe drive stopped working in a Win10 1703 VM after upgrading VB from 5.1.18 to 5.2.0.

In Device Manager, stornvme.sys is shown with yellow exclamation and (the German version of) this error message:
''This device cannot start. (Code 10) An invalid parameter was passed to a service or function.''

With an older 1607 snapshot of same VM, NVMe worked again.
After copying stornvme.sys from 1607 to 1703, NVMe worked again.
Same with a fresh install of 1709 (upgrade install crashed VB 5.2.0): NVMe failed and worked again after downgrading the driver.

Test results after downgrading VB to latest 5.1:

||= stornvme.sys       =||= 5.1.18/30 =||= 5.2.0 =||
|| 10.0.14393.0 (1607)  || OK          || OK      ||
|| 10.0.15063.0 (1703)  || OK          || Error   ||
|| 10.0.16299.15 (1709) || OK          || Error   ||

Possibly related or duplicate: #16078.
"	chrfranke
17952	5.2.18 - Windows 10 Pro Host 64-bit only supports 32-bit OS.	VirtualBox 5.2.18	2018-08-23T02:53:36Z	2018-08-23T05:20:54Z	2018-08-23T05:20:54Z	In Setting-General for Linux virtual machine, Type: Linux Version: only displays 32-bit OS.  Need 64-bit OS as in past.	BigAlKC
17950	5.2.18 still not in fedora 28 repository	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
18811	6.0.10 snaphot fails on NFS share with savestate	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
19236	6.0.16 Update delivers 6.0.15 and then breaks the Extension installs	VirtualBox 6.0.16	2020-01-16T12:40:51Z	2020-01-22T13:25:08Z	2020-01-22T13:25:08Z	"Was prompted to download 6.0.16 which I did and installed...
After install tried to install the extensions.. extension installer reported requires 6.0.16 but installed is 16.0.15...

After various attempts to remove or downgrade resorted to deleting the Mac VirtualBox app from Applications and downloading and reinstalling 6.0.14 and then the 6.0.14 extensions...

"	Serenak
19919	6.1.14 BSOD when VM starts	VirtualBox 6.1.14	2020-09-26T04:15:58Z	2020-10-19T11:01:04Z	2020-10-19T11:01:04Z	"Just installed 6.1.14, updating my prior installation. As soon as I started my VM (Ubuntu), my Windows 10 (latest update) BSODed. Rebooted, tried again, and BSOD again. I don't have winbdg installed, but I recall it was System Service Exception C???Ctrl 1.0.0.?

Perhaps ""The driver detected an internal driver error on \Device\VBoxNetLwf."" will help.

- System 

  - Provider 

   [ Name]  Microsoft-Windows-Kernel-Power 
   [ Guid]  xxx 
 
   EventID 41 
 
   Version 6 
 
   Level 1 
 
   Task 63 
 
   Opcode 0 
 
   Keywords 0x8000400000000002 
 
  - TimeCreated 

   [ SystemTime]  2020-09-26T03:14:19.511381700Z 
 
   EventRecordID 75446 
 
   Correlation 
 
  - Execution 

   [ ProcessID]  4 
   [ ThreadID]  8 
 
   Channel System 
 
   Computer xxx 
 
  - Security 

   [ UserID]  xxx 
 

- EventData 

  BugcheckCode 59 
  BugcheckParameter1 0xc0000005 
  BugcheckParameter2 0xfffff804633c9277 
  BugcheckParameter3 0xffffb8091c78db10 
  BugcheckParameter4 0x0 
  SleepInProgress 0 
  PowerButtonTimestamp 0 
  BootAppStatus 0 
  Checkpoint 0 
  ConnectedStandbyInProgress false 
  SystemSleepTransitionsToOn 0 
  CsEntryScenarioInstanceId 0 
  BugcheckInfoFromEFI false 
  CheckpointStatus 0 
"	jc3ferrari
19280	6.1.2 Installation failed, could not run required dll	VirtualBox 6.1.2	2020-01-30T16:23:51Z	2020-02-10T19:12:59Z	2020-02-10T19:12:59Z	"I'm attempting to install VBox 6.1.2 on a Windows 10 v1909 host OS and getting an error regarding dll failure which I've attached a screenshot of. Virtualization is enabled on BIOS, Hyper-V is fully enabled in Win10 settings, and there hasn't been a previous installation on this machine for me to try to finish wiping out first. I have tried older versions of VBox (6.0 and 5.2) and run into the same failure, and I couldn't find anything on the forum or general internet that pointed me in the right direction.

Any help is appreciated."	Fluxer
20315	6.1.20 Fails to start guest : memory can't be written	VirtualBox 6.1.20	2021-04-22T14:32:55Z	2021-04-23T21:36:15Z	2021-04-23T21:36:15Z	As of 6.1.18 it succeeded.	MikhailRokhin
20381	6.1.22 hangs perhaps due to vmsvga/video	VirtualBox 6.1.22	2021-05-27T07:24:51Z	2021-07-12T16:38:43Z	2021-07-12T16:38:43Z	"I had to downgrade to 6.1.20, which was stable for me.

I suspect it has something to do with video/vmsvga

Machine: HP Envy Pavilion 17t-j186nr 
Host is windows-10 updated to 19043.985 21H1
Guest is Fedora-Workstation-34 kernel 5.12.6-300, guest additions 6.1.22 is installed

With 6.1.22, If machine is started as hidden, machine can be ssh-ed to and is stable for very long time.

With 6.1.22, If machine is made to be shown, then after GDM login, after starting a terminal app, wezterm, firefox, virtualbox freezes, becomes non-responsive and remains stuck. 

It is possible to get mouse cursor, which in stcuk state is invisible, to the bottom, to hover over and bring up the VM-menu, minimize it and then get to the windows host. Other menu commands like reset do not work.

Outside, in the host windows, taskmgr can be used to kill and Virtualbox processes, helps close all virtualbox windows, and start over. 

reinstall of 6.1.22 did not help
"	gkamathh
20568	6.1.26 Memory can't be written	VirtualBox 6.1.26	2021-09-19T14:57:36Z	2021-09-19T15:00:52Z	2021-09-19T15:00:52Z	Can't repeat it. It was sudden during pausing VM.	MikhailRokhin
20629	6.1.28 kernel trace on 5.15.0-0-rc3	VirtualBox 6.1.28	2021-10-24T09:15:58Z	2021-10-25T02:34:00Z	2021-10-25T02:34:00Z	"
On fedora-35 with self-built kernel-5.15.0-0-rc3 from rawhide.
5.15.0-0.rc3.20211001git4de593fb965f.30.fc35.x86_64

I downloaded and installed latest rpmfusion koji build for Virtualbox 6.1.28 . https://koji.rpmfusion.org/koji/packageinfo?packageID=260
I did akmod build of kmod.
During boot I get the following dmesg kernel trace. 
After logging in, using virtualbox-manager, can't start vbox VMs, also gives another kernel trace
Its possible that even though Virtualbox says in its release notes for 6.1.28 includes 5.15, it might not as kernel-5.15 is still in rc and will be released in december. Still, it would be good to see this work as early as possible.

Info included below
- rpms installed on fedora-35
- dmesg_op_on_boot.txt  Kernel trace on vboxdrv load on boot
- dmesg_op_on_start.txt Kernel trace on attempting to start a vbox vm
- vbox_manager_log.txt  Log from VirtualBox Manager failed vm start

{{{
[root@sirius gana]# rpm -qa | grep -Ei ""kernel-5.15|VirtualBox"" |sort
akmod-VirtualBox-6.1.28-1.fc35.x86_64
kernel-5.15.0-0.rc3.20211001git4de593fb965f.30.fc35.x86_64
kmod-VirtualBox-5.13.19-200.fc34.x86_64-6.1.28-1.fc35.x86_64
kmod-VirtualBox-5.14.9-300.fc35.x86_64-6.1.28-1.fc35.x86_64
kmod-VirtualBox-5.15.0-0.rc3.20211001git4de593fb965f.30.fc35.x86_64-6.1.28-1.fc35.x86_64
kmod-VirtualBox-6.1.28-1.fc35.x86_64
VirtualBox-6.1.28-1.fc35.x86_64
virtualbox-guest-additions-6.1.26-1.fc35.x86_64
VirtualBox-kmodsrc-6.1.28-1.fc35.noarch
VirtualBox-server-6.1.28-1.fc35.x86_64
}}}

dmesg_op_on_boot.txt
{{{
	== dmesg op on boot
[   19.750473] vboxdrv: loading out-of-tree module taints kernel.
[   19.761501] vboxdrv: Found 8 processor cores
[   19.789709] vboxdrv: TSC mode is Invariant, tentative frequency 2394436401 Hz
[   19.789717] vboxdrv: Successfully loaded version 6.1.28_rpmfusion r147628 (interface 0x00320000)
[   19.796985] ------------[ cut here ]------------
[   19.796991] WARNING: CPU: 7 PID: 1182 at kernel/smp.c:876 smp_call_function_many_cond+0x1c7/0x3c0
[   19.797004] Modules linked in: vboxdrv(O) ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle iptable_raw iptable_security ip_set nf_tables nfnetlink ip6table_filter ip6_tables iptable_filter qrtr ns bnep sunrpc vfat fat ntfs3 intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp at24 iTCO_wdt intel_pmc_bxt mei_hdcp iTCO_vendor_support kvm_intel kvm irqbypass rapl intel_cstate intel_uncore snd_ctl_led snd_hda_codec_idt snd_hda_codec_generic ledtrig_audio pcspkr snd_hda_codec_hdmi iwlmvm snd_hda_intel uvcvideo mac80211 snd_intel_dspcfg videobuf2_vmalloc btusb snd_intel_sdw_acpi hp_wmi sparse_keymap btrtl libarc4 joydev videobuf2_memops snd_hda_codec btbcm platform_profile btintel videobuf2_v4l2 videobuf2_common bluetooth snd_seq videodev iwlwifi wmi_bmof snd_seq_device snd_hda_core i2c_i801 mc snd_hwdep ecdh_generic i2c_smbus snd_pcm cfg80211 snd_timer lpc_ich mei_me snd rfkill
[   19.797214]  mei soundcore hp_accel wireless_hotkey lis3lv02d zram ip_tables rtsx_pci_sdmmc mmc_core nouveau crct10dif_pclmul i915 crc32_pclmul drm_ttm_helper crc32c_intel ghash_clmulni_intel mxm_wmi i2c_algo_bit ttm drm_kms_helper serio_raw cec r8169 drm rtsx_pci wmi video hid_multitouch ipmi_devintf ipmi_msghandler fuse
[   19.797290] CPU: 7 PID: 1182 Comm: iprt-VBoxTscThr Tainted: G           O     --------- ---  5.15.0-0.rc3.20211001git4de593fb965f.30.fc35.x86_64 #1
[   19.797295] Hardware name: Hewlett-Packard HP ENVY TS 17 Notebook PC/1966, BIOS F.70 10/20/2017
[   19.797299] RIP: 0010:smp_call_function_many_cond+0x1c7/0x3c0
[   19.797306] Code: ff ff 0f 0b e9 c8 fe ff ff 65 8b 05 63 bb e5 50 a9 ff ff ff 7f 0f 85 8e fe ff ff 65 8b 05 dd c7 e5 50 85 c0 0f 84 7f fe ff ff <0f> 0b 44 3b 35 74 e1 0b 02 0f 82 7d fe ff ff 0f 0b e9 76 fe ff ff
[   19.797310] RSP: 0018:ffffbe3dc23f7d28 EFLAGS: 00010202
[   19.797315] RAX: 0000000000000001 RBX: ffffffffc151ba50 RCX: 0000000000000001
[   19.797319] RDX: ffffbe3dc23f7db0 RSI: 0000000000000001 RDI: ffff99b3c84d7410
[   19.797323] RBP: ffffbe3dc23f7e08 R08: 0000000000000000 R09: ffff99b3c84d7410
[   19.797326] R10: ffffffffaf78170b R11: 0000000000000000 R12: 0000000000000000
[   19.797330] R13: ffffbe3dc23f7db0 R14: 0000000000000007 R15: 0000000000000000
[   19.797333] FS:  0000000000000000(0000) GS:ffff99b70f200000(0000) knlGS:0000000000000000
[   19.797337] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   19.797341] CR2: 0000561641f38cf8 CR3: 0000000109056002 CR4: 00000000001706e0
[   19.797346] Call Trace:
[   19.797352]  ? rtmpLinuxWrapper+0x30/0x30 [vboxdrv]
[   19.797395]  ? supdrvTscMeasureDeltaCallbackUnwrapped.isra.0+0xa70/0xa70 [vboxdrv]
[   19.797425]  VBoxHost_RTMpOnPair+0x147/0x230 [vboxdrv]
[   19.797456]  ? supdrvTscMeasureDeltaCallbackUnwrapped.isra.0+0xa70/0xa70 [vboxdrv]
[   19.797494]  supdrvTscMeasureDeltaOne+0x3b6/0x450 [vboxdrv]
[   19.797519]  ? destroy_timer_on_stack+0x20/0x20
[   19.797536]  supdrvTscDeltaThread+0x3ad/0x5e0 [vboxdrv]
[   19.797567]  ? VBoxHost_RTThreadSleepNoLog+0x40/0x40 [vboxdrv]
[   19.797601]  rtThreadMain+0x3e/0x90 [vboxdrv]
[   19.797631]  rtThreadNativeMain+0x1b/0x20 [vboxdrv]
[   19.797660]  kthread+0x149/0x170
[   19.797666]  ? set_kthread_struct+0x40/0x40
[   19.797686]  ret_from_fork+0x22/0x30
[   19.797716] irq event stamp: 965
[   19.797719] hardirqs last  enabled at (971): [<ffffffffaf172980>] __up_console_sem+0x60/0x70
[   19.797726] hardirqs last disabled at (976): [<ffffffffaf172965>] __up_console_sem+0x45/0x70
[   19.797731] softirqs last  enabled at (0): [<ffffffffaf0e22a2>] copy_process+0x7e2/0x1fe0
[   19.797739] softirqs last disabled at (0): [<0000000000000000>] 0x0
[   19.797744] ---[ end trace 9a75e80b54325f72 ]---
[   19.852286] VBoxNetFlt: Successfully started.
[   19.878033] VBoxNetAdp: Successfully started.
[   21.425883] powercap intel-rapl:0: package locked by BIOS, monitoring only
[   24.086465] systemd-udevd (662) used greatest stack depth: 11200 bytes left
[   25.432027] intel_powerclamp: Start idle injection to reduce power

[   25.432945] ======================================================
[   25.433792] WARNING: possible circular locking dependency detected
[   25.434639] 5.15.0-0.rc3.20211001git4de593fb965f.30.fc35.x86_64 #1 Tainted: G        W  O     --------- ---
[   25.435521] ------------------------------------------------------
[   25.436403] thermald/1071 is trying to acquire lock:
[   25.437274] ffffffffb0e6cd40 (cpu_hotplug_lock){++++}-{0:0}, at: powerclamp_set_cur_state.cold+0x17/0xb5 [intel_powerclamp]
[   25.438199]
               but task is already holding lock:
[   25.440013] ffff99b43d21ee38 (&cdev->lock){+.+.}-{3:3}, at: cur_state_store+0x48/0xb0
[   25.440943]
               which lock already depends on the new lock.

[   25.443691]
               the existing dependency chain (in reverse order) is:
[   25.445519]
               -> #3 (&cdev->lock){+.+.}-{3:3}:
[   25.447340]        __mutex_lock+0x92/0x8c0
[   25.448257]        thermal_zone_bind_cooling_device+0x307/0x450
[   25.449185]        acpi_thermal_cooling_device_cb+0xc7/0x1e0
[   25.450118]        thermal_zone_device_register+0x644/0x6c0
[   25.451056]        acpi_thermal_add+0x2ee/0x4c0
[   25.451996]        acpi_device_probe+0x47/0x160
[   25.452932]        really_probe+0x1f5/0x3f0
[   25.453867]        __driver_probe_device+0xfe/0x180
[   25.454798]        driver_probe_device+0x1e/0x90
[   25.455724]        __driver_attach+0xc4/0x1d0
[   25.456631]        bus_for_each_dev+0x67/0x90
[   25.457555]        bus_add_driver+0x12e/0x1f0
[   25.458465]        driver_register+0x8f/0xe0
[   25.459347]        acpi_thermal_init+0x5e/0x82
[   25.460228]        do_one_initcall+0x67/0x320
[   25.461106]        kernel_init_freeable+0x27d/0x2c9
[   25.461985]        kernel_init+0x16/0x120
[   25.462850]        ret_from_fork+0x22/0x30
[   25.463719]
               -> #2 (&tz->lock){+.+.}-{3:3}:
[   25.465446]        __mutex_lock+0x92/0x8c0
[   25.466300]        thermal_zone_device_update+0x28/0x4c0
[   25.467138]        thermal_zone_device_register+0x67b/0x6c0
[   25.467979]        pkg_thermal_cpu_online+0x204/0x2d0 [x86_pkg_temp_thermal]
[   25.468830]        cpuhp_invoke_callback+0x141/0x390
[   25.469709]        cpuhp_thread_fun+0xd6/0x1e0
[   25.470576]        smpboot_thread_fn+0xf2/0x1d0
[   25.471447]        kthread+0x149/0x170
[   25.472307]        ret_from_fork+0x22/0x30
[   25.473167]
               -> #1 (cpuhp_state-up){+.+.}-{0:0}:
[   25.474870]        cpuhp_thread_fun+0x90/0x1e0
[   25.475726]        smpboot_thread_fn+0xf2/0x1d0
[   25.476624]        kthread+0x149/0x170
[   25.477514]        ret_from_fork+0x22/0x30
[   25.478403]
               -> #0 (cpu_hotplug_lock){++++}-{0:0}:
[   25.480153]        __lock_acquire+0x11fe/0x1e00
[   25.481041]        lock_acquire+0xc4/0x2e0
[   25.481922]        cpus_read_lock+0x3e/0xb0
[   25.482803]        powerclamp_set_cur_state.cold+0x17/0xb5 [intel_powerclamp]
[   25.483708]        cur_state_store+0x5f/0xb0
[   25.484602]        kernfs_fop_write_iter+0x134/0x1d0
[   25.485491]        new_sync_write+0x10e/0x190
[   25.486380]        vfs_write+0x27a/0x390
[   25.487266]        ksys_write+0x58/0xd0
[   25.488143]        do_syscall_64+0x3b/0x90
[   25.489021]        entry_SYSCALL_64_after_hwframe+0x44/0xae
[   25.489892]
               other info that might help us debug this:

[   25.492401] Chain exists of:
                 cpu_hotplug_lock --> &tz->lock --> &cdev->lock

[   25.494817]  Possible unsafe locking scenario:

[   25.496369]        CPU0                    CPU1
[   25.497112]        ----                    ----
[   25.497846]   lock(&cdev->lock);
[   25.498566]                                lock(&tz->lock);
[   25.499286]                                lock(&cdev->lock);
[   25.499999]   lock(cpu_hotplug_lock);
[   25.500703]
                *** DEADLOCK ***

[   25.502787] 5 locks held by thermald/1071:
[   25.503481]  #0: ffff99b427b50100 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x4d/0x60
[   25.504203]  #1: ffff99b3c5619498 (sb_writers#4){.+.+}-{0:0}, at: ksys_write+0x58/0xd0
[   25.504931]  #2: ffff99b406555290 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x100/0x1d0
[   25.505668]  #3: ffff99b4278ea8f8 (kn->active#184){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x108/0x1d0
[   25.506417]  #4: ffff99b43d21ee38 (&cdev->lock){+.+.}-{3:3}, at: cur_state_store+0x48/0xb0
[   25.507169]
               stack backtrace:
[   25.508654] CPU: 7 PID: 1071 Comm: thermald Tainted: G        W  O     --------- ---  5.15.0-0.rc3.20211001git4de593fb965f.30.fc35.x86_64 #1
[   25.509451] Hardware name: Hewlett-Packard HP ENVY TS 17 Notebook PC/1966, BIOS F.70 10/20/2017
[   25.510278] Call Trace:
[   25.511112]  dump_stack_lvl+0x57/0x72
[   25.511952]  check_noncircular+0xdf/0x100
[   25.512792]  __lock_acquire+0x11fe/0x1e00
[   25.513634]  lock_acquire+0xc4/0x2e0
[   25.514470]  ? powerclamp_set_cur_state.cold+0x17/0xb5 [intel_powerclamp]
[   25.515325]  ? lock_is_held_type+0xa7/0x120
[   25.516181]  cpus_read_lock+0x3e/0xb0
[   25.517038]  ? powerclamp_set_cur_state.cold+0x17/0xb5 [intel_powerclamp]
[   25.517915]  powerclamp_set_cur_state.cold+0x17/0xb5 [intel_powerclamp]
[   25.518801]  cur_state_store+0x5f/0xb0
[   25.519686]  kernfs_fop_write_iter+0x134/0x1d0
[   25.520574]  new_sync_write+0x10e/0x190
[   25.521458]  vfs_write+0x27a/0x390
[   25.522347]  ksys_write+0x58/0xd0
[   25.523232]  do_syscall_64+0x3b/0x90
[   25.524100]  entry_SYSCALL_64_after_hwframe+0x44/0xae
[   25.524980] RIP: 0033:0x7f2b815e58ef
[   25.525851] Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 29 88 f8 ff 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 31 44 89 c7 48 89 44 24 08 e8 6c 88 f8 ff 48
[   25.526822] RSP: 002b:00007f2b737ba5b0 EFLAGS: 00000293 ORIG_RAX: 0000000000000001
[   25.527810] RAX: ffffffffffffffda RBX: 00005557fd10ce90 RCX: 00007f2b815e58ef
[   25.528806] RDX: 0000000000000001 RSI: 00007f2b737ba650 RDI: 0000000000000009
[   25.529808] RBP: 0000000000000009 R08: 0000000000000000 R09: 00007f2b6c0015f0
[   25.530813] R10: 0000000000000000 R11: 0000000000000293 R12: 00007f2b737ba640
[   25.531811] R13: 00005557fd10cea0 R14: 00007f2b737ba680 R15: 00007f2b737ba640
[   26.391799] NOHZ tick-stop error: Non-RCU local softirq work is pending, handler #80!!!
[   26.392874] NOHZ tick-stop error: Non-RCU local softirq work is pending, handler #80!!!
[   26.393910] NOHZ tick-stop error: Non-RCU local softirq work is pending, handler #80!!!
[   26.394936] NOHZ tick-stop error: Non-RCU local softirq work is pending, handler #80!!!
[   26.395935] NOHZ tick-stop error: Non-RCU local softirq work is pending, handler #80!!!
[   26.396930] NOHZ tick-stop error: Non-RCU local softirq work is pending, handler #80!!!
}}}

dmesg_op_on_vmstart.txt 
{{{
== Kernel trace on attempting to start a vbox vm

[ 2614.761830] SUPR0GipMap: fGetGipCpu=0x1b
[ 2615.808846] BUG: kernel NULL pointer dereference, address: 0000000000000000
[ 2615.808854] #PF: supervisor read access in kernel mode
[ 2615.808856] #PF: error_code(0x0000) - not-present page
[ 2615.808858] PGD 80000003ad370067 P4D 80000003ad370067 PUD 378fa6067 PMD 0
[ 2615.808865] Oops: 0000 [#1] SMP PTI
[ 2615.808868] CPU: 1 PID: 4868 Comm: EMT Tainted: G        W  O     --------- ---  5.15.0-0.rc3.20211001git4de593fb965f.30.fc35.x86_64 #1
[ 2615.808870] Hardware name: Hewlett-Packard HP ENVY TS 17 Notebook PC/1966, BIOS F.70 10/20/2017
[ 2615.808872] RIP: 0010:do_raw_spin_trylock+0x5/0x40
[ 2615.808878] Code: c6 94 57 5f b0 48 89 ef e8 c8 fe ff ff eb a9 89 c6 48 89 ef e8 cc f4 ff ff 66 90 eb a9 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 <8b> 07 85 c0 75 28 ba 01 00 00 00 f0 0f b1 17 75 1d 65 8b 05 eb b6
[ 2615.808880] RSP: 0018:ffffbe3dc3de3d00 EFLAGS: 00010282
[ 2615.808882] RAX: 0000000000000001 RBX: ffffbe3dc3de3de8 RCX: 0000000000000000
[ 2615.808883] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
[ 2615.808885] RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000
[ 2615.808886] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000018
[ 2615.808887] R13: 0000000000000001 R14: ffffbe3dc7b41000 R15: ffff99b3c01f41e8
[ 2615.808889] FS:  00007fd68ac4e640(0000) GS:ffff99b70e600000(0000) knlGS:0000000000000000
[ 2615.808891] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 2615.808893] CR2: 0000000000000000 CR3: 0000000378f24005 CR4: 00000000001706e0
[ 2615.808894] Call Trace:
[ 2615.808896]  _raw_spin_lock+0x39/0x80
[ 2615.808900]  ? __apply_to_page_range+0x6c9/0x870
[ 2615.808905]  __apply_to_page_range+0x6c9/0x870
[ 2615.808909]  ? rtR0MemObjLinuxConvertProt+0xd0/0xd0 [vboxdrv]
[ 2615.808935]  rtR0MemObjNativeProtect+0x65/0x90 [vboxdrv]
[ 2615.808951]  VBoxHost_RTR0MemObjProtect+0x86/0xc0 [vboxdrv]
[ 2615.808964]  supdrvIOCtl+0x3192/0x36f0 [vboxdrv]
[ 2615.808977]  VBoxDrvLinuxIOCtl_6_1_28+0x11e/0x220 [vboxdrv]
[ 2615.808988]  __x64_sys_ioctl+0x82/0xb0
[ 2615.808993]  do_syscall_64+0x3b/0x90
[ 2615.808996]  entry_SYSCALL_64_after_hwframe+0x44/0xae
[ 2615.808999] RIP: 0033:0x7fd6d23b537b
[ 2615.809002] Code: ff ff ff 85 c0 79 9b 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 7d 2a 0f 00 f7 d8 64 89 01 48
[ 2615.809003] RSP: 002b:00007fd68ac4cbd8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
[ 2615.809005] RAX: ffffffffffffffda RBX: 00007fd68a768010 RCX: 00007fd6d23b537b
[ 2615.809007] RDX: 00007fd68a768010 RSI: 0000000000005684 RDI: 0000000000000007
[ 2615.809008] RBP: 00007fd68ac4cbe0 R08: 0000000000000000 R09: 0000000000000000
[ 2615.809009] R10: 00007fd6d22029a0 R11: 0000000000000246 R12: 00007fd6ab7424df
[ 2615.809011] R13: 00007fd68ac4d040 R14: 00007fd68ac4cd40 R15: 0000000000000000
[ 2615.809014] Modules linked in: uinput rfcomm snd_seq_dummy snd_hrtimer xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_nat_tftp nf_conntrack_tftp bridge stp llc nft_objref nf_conntrack_netbios_ns nf_conntrack_broadcast nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct vboxnetadp(O) vboxnetflt(O) nft_chain_nat vboxdrv(O) ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle iptable_raw iptable_security ip_set nf_tables nfnetlink ip6table_filter ip6_tables iptable_filter qrtr ns bnep sunrpc vfat fat ntfs3 intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp at24 iTCO_wdt intel_pmc_bxt mei_hdcp iTCO_vendor_support kvm_intel kvm irqbypass rapl intel_cstate intel_uncore snd_ctl_led snd_hda_codec_idt snd_hda_codec_generic ledtrig_audio pcspkr snd_hda_codec_hdmi iwlmvm snd_hda_intel uvcvideo mac80211 snd_intel_dspcfg
[ 2615.809060]  videobuf2_vmalloc btusb snd_intel_sdw_acpi hp_wmi sparse_keymap btrtl libarc4 joydev videobuf2_memops snd_hda_codec btbcm platform_profile btintel videobuf2_v4l2 videobuf2_common bluetooth snd_seq videodev iwlwifi wmi_bmof snd_seq_device snd_hda_core i2c_i801 mc snd_hwdep ecdh_generic i2c_smbus snd_pcm cfg80211 snd_timer lpc_ich mei_me snd rfkill mei soundcore hp_accel wireless_hotkey lis3lv02d zram ip_tables rtsx_pci_sdmmc mmc_core nouveau crct10dif_pclmul i915 crc32_pclmul drm_ttm_helper crc32c_intel ghash_clmulni_intel mxm_wmi i2c_algo_bit ttm drm_kms_helper serio_raw cec r8169 drm rtsx_pci wmi video hid_multitouch ipmi_devintf ipmi_msghandler fuse
[ 2615.809099] CR2: 0000000000000000
[ 2615.809101] ---[ end trace 9a75e80b54325f73 ]---
[ 2615.809102] RIP: 0010:do_raw_spin_trylock+0x5/0x40
[ 2615.809106] Code: c6 94 57 5f b0 48 89 ef e8 c8 fe ff ff eb a9 89 c6 48 89 ef e8 cc f4 ff ff 66 90 eb a9 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 <8b> 07 85 c0 75 28 ba 01 00 00 00 f0 0f b1 17 75 1d 65 8b 05 eb b6
[ 2615.809108] RSP: 0018:ffffbe3dc3de3d00 EFLAGS: 00010282
[ 2615.809110] RAX: 0000000000000001 RBX: ffffbe3dc3de3de8 RCX: 0000000000000000
[ 2615.809111] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
[ 2615.809113] RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000
[ 2615.809114] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000018
[ 2615.809115] R13: 0000000000000001 R14: ffffbe3dc7b41000 R15: ffff99b3c01f41e8
[ 2615.809116] FS:  00007fd68ac4e640(0000) GS:ffff99b70e600000(0000) knlGS:0000000000000000
[ 2615.809118] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 2615.809119] CR2: 0000000000000000 CR3: 0000000378f24005 CR4: 00000000001706e0
[ 2615.809121] note: EMT[4868] exited with preempt_count 1
[ 2615.809123] BUG: sleeping function called from invalid context at include/linux/percpu-rwsem.h:49
[ 2615.809124] in_atomic(): 0, irqs_disabled(): 1, non_block: 0, pid: 4868, name: EMT
[ 2615.809126] INFO: lockdep is turned off.
[ 2615.809127] irq event stamp: 0
[ 2615.809128] hardirqs last  enabled at (0): [<0000000000000000>] 0x0
[ 2615.809130] hardirqs last disabled at (0): [<ffffffffaf0e22a2>] copy_process+0x7e2/0x1fe0
[ 2615.809134] softirqs last  enabled at (0): [<ffffffffaf0e22a2>] copy_process+0x7e2/0x1fe0
[ 2615.809137] softirqs last disabled at (0): [<0000000000000000>] 0x0
[ 2615.809138] CPU: 1 PID: 4868 Comm: EMT Tainted: G      D W  O     --------- ---  5.15.0-0.rc3.20211001git4de593fb965f.30.fc35.x86_64 #1
[ 2615.809140] Hardware name: Hewlett-Packard HP ENVY TS 17 Notebook PC/1966, BIOS F.70 10/20/2017
[ 2615.809142] Call Trace:
[ 2615.809143]  dump_stack_lvl+0x57/0x72
[ 2615.809147]  ___might_sleep.cold+0xb6/0xc6
[ 2615.809151]  exit_signals+0x1c/0x2d0
[ 2615.809155]  do_exit+0xba/0xc00
[ 2615.809157]  ? __x64_sys_ioctl+0x82/0xb0
[ 2615.809161]  rewind_stack_do_exit+0x17/0x20
[ 2615.809166] RIP: 0033:0x7fd6d23b537b
[ 2615.809167] Code: ff ff ff 85 c0 79 9b 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 7d 2a 0f 00 f7 d8 64 89 01 48
[ 2615.809169] RSP: 002b:00007fd68ac4cbd8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
[ 2615.809171] RAX: ffffffffffffffda RBX: 00007fd68a768010 RCX: 00007fd6d23b537b
[ 2615.809172] RDX: 00007fd68a768010 RSI: 0000000000005684 RDI: 0000000000000007
[ 2615.809173] RBP: 00007fd68ac4cbe0 R08: 0000000000000000 R09: 0000000000000000
[ 2615.809175] R10: 00007fd6d22029a0 R11: 0000000000000246 R12: 00007fd6ab7424df
[ 2615.809176] R13: 00007fd68ac4d040 R14: 00007fd68ac4cd40 R15: 0000000000000000
}}}

vboxmanager log
{{{

The VM session was aborted.


Result Code: 
NS_ERROR_FAILURE (0x80004005)
Component: 
SessionMachine
Interface: 
ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}


00:00:00.999384 VirtualBox VM 6.1.28_rpmfusion r147628 linux.amd64 (Oct 20 2021 00:00:00) release log
00:00:00.999386 Log opened 2021-10-22T15:51:22.418377000Z
00:00:00.999387 Build Type: release
00:00:00.999390 OS Product: Linux
00:00:00.999391 OS Release: 5.15.0-0.rc3.20211001git4de593fb965f.30.fc35.x86_64
00:00:00.999393 OS Version: #1 SMP Fri Oct 15 15:21:42 IST 2021
00:00:00.999429 DMI Product Name: HP ENVY TS 17 Notebook PC
00:00:00.999446 DMI Product Version: 097E110000405E00000620100
00:00:00.999455 Firmware type: UEFI
00:00:01.000420 Secure Boot: Enabled
00:00:01.000494 Host RAM: 15886MB (15.5GB) total, 12664MB (12.3GB) available
00:00:01.000499 Executable: /usr/lib64/virtualbox/VirtualBoxVM
00:00:01.000500 Process ID: 4901
00:00:01.000500 Package type: LINUX_64BITS_GENERIC (OSE)
00:00:01.010401 Installed Extension Packs:
00:00:01.010428   None installed!
00:00:01.011816 Console: Machine state changed to 'Starting'
00:00:01.012181 Qt version: 5.15.2
00:00:01.012201 X11 Window Manager code: 2
00:00:01.023547 SUP: seg #0: R   0x00000000 LB 0x0004d000
00:00:01.023579 SUP: seg #1: R X 0x0004d000 LB 0x0011a000
00:00:01.023591 SUP: seg #2: R   0x00167000 LB 0x00060000
00:00:01.023601 SUP: seg #3: RW  0x001c7000 LB 0x000350a0
00:00:01.023959 GUI: UIMediumEnumerator: Medium-enumeration finished!
00:00:01.027343 X Server details: vendor: The X.Org Foundation, release: 12101002, protocol version: 11.0, display string: :0
00:00:01.027373 Using known keycode mapping for keycode to scan code conversion
00:00:01.030671 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated: Screen 0 work area is actually resized to: 0x32 x 1920x1048
00:04:45.134014 VirtualBoxClient: detected unresponsive VBoxSVC (rc=NS_ERROR_CALL_FAILED)
00:05:05.310617 GUI: Request to power VM off due to VBoxSVC is unavailable.
00:05:05.310651 GUI: Passing request to power VM off from machine-logic to UI session.
00:05:05.310664 GUI: Powering VM down on UI session power off request...
00:05:05.310683 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Invalid machine state: Starting (must be Running, Paused or Stuck)}, preserve=false aResultDetail=0
}}}"	gkamathh
20858	6.1.32 Ubuntu package lacks the VirtualBox.chm manual file	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)
21038	6.1.36 regression. Recording VMs audio not working	VirtualBox 6.1.36	2022-07-27T00:17:11Z	2022-07-27T00:17:11Z	2022-07-27T00:17:11Z	"In setting select Display->Recording, audio only and highest quality.
The .webm file is created during run (opening the file is logged correctly).
Once the VM is powered down, the file is erased. Tested on windows and debian host (debian guest).
The webm file length never exceeds a few hundred bytes.
Install .34 again, and all was well again."	KurtMielke
19524	6.1.6 performance dreadful on VMSVGA and LinuxMint 18.2 VM on Windows 10 host	VirtualBox 6.1.6	2020-04-23T02:38:46Z	2020-05-28T20:13:00Z	2020-05-28T20:13:00Z	"I require VBoxSVGA with LinuxMint 18.2 running on a Windows 10 host.  Selection of VMSVGA causes a slow down of the entire VM, including disk access.  That's so weird.

"	Trent
17732	64bit guest on 32bit host	VirtualBox 5.2.10	2018-05-05T00:36:11Z	2018-05-18T08:43:06Z	2018-05-18T08:43:06Z	"After downloading the newest 64bit version of Windows 10 (April update), i faced with a serious problem, when i tried to create a fresh install on a new virtual disk (12GB dynamic VDI). Most likely, the cause of the issue, that my host (it has a C2D P8400 CPU) is running the 32bit version of Windows 7. Altought, it'd be not a problem at all, as long, as VT-x is turned on, in both the BIOS and the VM and the CPU has 64bit support. Nonetheless, installing this OS is currently impossible, because guest is always going to hang, shortly after starting (captured wbem file is attached).
Anyways, i'm pretty sure, VT-x is enabled system-wide, because when i disable it in BIOS, i get the expected error message:

{{{
Failed to open a session for the virtual machine VM_00002.

VT-x is disabled in the BIOS for all CPU modes (VERR_VMX_MSR_ALL_VMX_DISABLED).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
}}}

Also i'm sure, the bug is hiding somewhere in Virtualbox's Windows 10 support, since right after this, i successfully managed to install a 64bit Windows 7 system on exactly the same guest and host (screenshot is attached of this).
"	T800
13571	64bit guest on 64bit Windows 8.1 running bootcamp on a macbook air	VirtualBox 4.3.18	2014-10-29T21:04:08Z	2014-11-03T14:43:00Z	2014-11-03T14:43:00Z	"I have just installed Virtual Box 4.3.18r96516, on a Macbook Air running Windows 8.1 in bootcamp. Right after the installation completed, I installed Windows Server 2012R2 64bit on a new virtual machine - this worked perfectly and I also installed an SQL server 2012 afterwards. Now a few hours later after sleeping the computer I get this error: ""VT-x/AMD-V hardware acceleration is not available on your system. Your 64-bit guest will fail to detect a 64-bit CPU and will not be able to boot."". I tried rebooting into OS X and back again, but that didn't work either (same error).
In task manager->performance it says Virtualization Enabled, and from a bit of research I can gather that virtualization should be enabled as default on all macs."	Skovby
21056	[CRITICAL] Network driver causing system crashes on windows 11	VirtualBox 6.1.36	2022-08-08T20:53:39Z	2022-08-08T20:53:39Z	2022-08-08T20:53:39Z	"I'd seen this bug reported in other places, but no currently open tickets mention hard, system-wide crashes. One of them mentions being disconnected from the wifi for a brief time, but this is way worse than just that.

I hadn't even used VirtualBox at all since my computer started up, but any time I try to load more intensive websites on my host operating system (completely independent from VB I might add), it has about a 1 in 10 chance of crashing my entire OS. Straight to black screen, computer shuts off and reboots.

I only use virtualbox once in a while, so imagine my surprise when I started investigating why my computer keeps crashing only to find that this event was found before every crash. Initially I thought that was a bug in this version of the software and updated to 6.1.36, but nothing changed on that front. 

I love open source projects, but honestly if this isn't fixed soon I may have to switch to a proprietary VM software, simply because I can't leave this installed on my computer if it's going to cause crashes every other day. It didn't used to happen before I updated to the most recent version of windows, but the fact remains that this driver is still the cause of those crashes.

The problem always correlates with an event ""The driver detected an internal driver error on \Device\VBoxNetLwf."" The event has ID 12 and is listed under the keyword ""classic""."	pizzamonkey
19483	[CRITICAL] Windows XP VM Won’t Start	VirtualBox 6.1.4	2020-04-13T04:49:42Z	2020-04-13T04:49:42Z	2020-04-13T04:49:42Z	"I was not able to attach a log file for this; the log is empty. Let me describe the issue.
When I make a new VM with Windows XP on it, with sufficient RAM, CPU, Disk, and the correct ISO, it says invalid settings detected. I hover over it and it leads me to System/Acceleration and it tells me to uncheck Hardware Virtualisation. Fair enough, I toggle it off. The invalid settings error persists at the same place. Here are my specs:

Windows 7 Home Premium SP 1 Build 7601
Lenovo Ideapad 2010 (x64 based)
Intel Core i5 CPU, M480 @ 2.67 GHz, 2667 MHz, 2 Cores
BIOS Version LENOVO 29CN35WW(V2.12), 8/12/2010
SMBIOS Version 2.6
8 GB RAM

I am also on the latest stable version, 6.1.4r136177 (Qt5.6.2)


"	Asquenn
21309	[drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:34:plane-0] flip_done timed out	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
12560	[Feature request] Anonymous virtual machines.	VirtualBox 4.3.6	2014-01-01T18:34:35Z	2014-01-01T18:34:35Z	2014-01-01T18:34:35Z	"Hi. I have a feature request. Sometimes, we need to create from scratch, start and stop some virtual machines from a linux bash script. I have this through the VBoxManage command: register a new virtual machine, configure the disk adapter, attach the disk to it, and so on. Because this machines run in headless mode, the name are created by the bash script with a pseudorandom name.

In qemu, is much more simpler to start a virtual machine. Simply call the qemu executable with all the params need. But, in VirtualBox, we need to register the virtual machine, modify it to configure, start, stop, deregister it. And if I have duplicated one disk (with the same UUID) for two virtual machines, the second refuse to configures by the duplicated UUID. If the virtual machine crash, we need to test if they are registered before to restart it.

It is possible add a new mode like qemu without a virtual machine registration?. With this mode, a new executable can be created (for example vboxanonymous or something) which accept all params in the same command line (disks, ram memory, network cards, sound card, etc).

Thanks.

"	marianito1234
9339	[feature request] Enable remote management with GUI	VirtualBox 4.1.0	2011-07-29T11:22:05Z	2011-09-02T10:06:24Z	2011-09-02T10:06:24Z	It would be really nice if the VirtualBox GUI was able to connect to a remote host to manage the VB installation there. This is especially usefull for headless setups. Yes, you could use VBoxManage, but a GUI is always easier. Workarounds such as phpvirtualbox exist, but I think it would be nice to have this functionality implemented in the standard GUI.	Rainmaker
20903	[feature request][Windows] embedding a manifest into the exe/dll	VirtualBox 6.1.32	2022-04-16T01:47:00Z	2022-07-05T20:13:43Z	2022-07-05T20:13:43Z	"Windows Host:  
none of the binaries (exe/dll) include any manifest.

I've done some testing, with a generic manifest I've suited for all of the files,  
with 'compatibility' for running the app outside of Windows 10 vista virtualization, 'DPI awareness' and the text rendering was amazingly crispy, and 'segmented heap' which seems to improve the program stack handling. I even through in 'long-path awareness' just because I've could.

normally I would patched the embedded (resource-24),  
but it seems that Windows Defender don't like me to do that on signed programs, 

so I've just placed a copy of a '.manifest' for each of the files in c:\Program Files\Oracle\VirtualBox (for example 'VirtualBox.exe.manifest') using 
https://github.com/eladkarako/manifest/blob/master/example_manifests/generic.manifest  

and it seems to do the job. 

I did had to apply this registry patch to make it work,  

{{{
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide]
""PreferExternalManifest""=dword:00000001
}}}

still, runs fine.


I'm still testing the overall performances,  
but I can say the GUI is super clear and sharp,  
I'm using a 150% DPI on my screen, which always seems to show things a bit blurry. and that fixed it completely, the controls seems to keep their place correctly (sometimes DPI awareness makes controls leak their position).

using the new Windows 10 segmented heap seems to help with memory allocation somewhat, but I'm still stress testing.

as for long-path awareness,  
I do have a registry patch to opt-in the feature as explained in:  

https://docs.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=cmd#enable-long-paths-in-windows-10-version-1607-and-later

but I don't have any machines on an especially long paths.

however, I know it might help with machines placed on quirky remote locations as well. 


I strongly suggest applying this nice and easy (no actual code modification is required) fix, the results are amazing (at least as for memory consumption with the segmented heap and GUI crispiness).
"	Elad Karako
32	"[feature-reques] Ability to suppress all stupid messages in ""File->Global Settings"""	VirtualBox 1.3.4	2007-02-12T13:33:53Z	2014-03-05T21:14:54Z	2014-03-05T21:14:54Z	"Software: Windows XP Pro SP2 Eng, no extra patches, VirtualBox 1.3.4 Full.

When first installing VirtualBox, it produces a lot of stupid messages which I can't easily get rid of.

Such as: when you ""lock"" in your keyboard and mouse or go fullscreen mode.

This might be good for total-noob, so leave it on by default, but for an experienced guy such as me, it is best to have an option to suppress all of this globally, for all VMs.

The best place IMHO to put this option is in: ""File->Global Settings""

-Alexey Eremenko
"	Technologov
1929	[feature-request] Allow Custom, per-VM BIOS	VirtualBox 1.6.4	2008-08-08T17:45:08Z	2010-05-04T03:35:32Z	2010-05-04T03:35:32Z	"
Hi All,

Since VBox BIOS is based on Qemu (and Bochs) BIOS, I believe there is no need to hide (encapsulate) VBox BIOS into other files.

I think it would be best to have transparent access to separate BIOS file, and allow different BIOSes for each VM for advanced users.

This feature request is actually 2:

1. BIOS should be 1 separate file (for transparency)

2. Per-VM BIOS file must be configurable (like Qemu)

-Technologov, 8.8.08 !"	Technologov
8401	[feature-request] Direct Linux Boot	VirtualBox 4.0.4	2011-02-22T15:27:58Z	2013-04-07T20:50:43Z	2013-04-07T20:50:43Z	"Direct Linux Boot means that the user can specify guest kernel and initrd and boot Linux guest directly, either from CD/DVD, or from HDD, bypassing guest's bootloader.

This is useful for unattended installs, such as where you can command paths for Fedora/Red Hat anaconda to automatically install guest OS.

This is also useful for kernel developers, who want to quick test a kernel.

Note that Qemu (and KVM and Xen) have this feature.

I have opened a related:
 Feature Request: (Automatic) Unattended Guest OS Install (aka Easy Install), Wish #5810

-Technologov, 22.02.2011."	Technologov
7836	[feature-request] Floppy: Create Virtual FAT images from host's filesystem	VirtualBox 3.2.12	2010-12-13T04:01:51Z	2010-12-13T04:01:51Z	2010-12-13T04:01:51Z	"Qemu has very interesting option of creating floppy images from host's filesystem directory tree (if the tree has less than 1.44 MB of data).

http://wiki.qemu.org/download/qemu-doc.html#disk_005fimages_005ffat_005fimages

Qemu command:

qemu linux.img -fda fat:floppy:/my_directory

This feature is a prerequisite for a bigger Feature Request: (Automatic) Unattended Guest OS Install (aka Easy Install), Wish #5810

-Technologov, 13.12.2010."	Technologov
5547	[feature-request] Log all loaded drivers currently running on host	VirtualBox 3.0.12	2009-11-24T16:33:03Z	2009-11-24T16:33:03Z	2009-11-24T16:33:03Z	"On Linux host: ""lsmod | sort"" and equivalent for other host platforms.

This will resolve a lot of trivial issues, such as user running VBox together with coLinux, KVM, or other conflicting driver...

For this to work, there needs to be a ""general"" log file, that is created when the frontend (VBox GUI or CLI) starts up, and not associated with any VM. It must be done *before* VM is actually started, as in some cases conflicting driver may crash the host, leaving us without a clue.

Alternatively the log for VM can be created when VM is actually started, but before ""vboxdrv"" starts running it.

Like this:

1. user clicks to run VM

2. log is created with essential info logged and saved to disk

3. Only now ""vboxdrv"" must actually start executing. In case of host crash/panic/BSOD, we still would have the log file. (after user reboots)

-Technologov, 24.11.2009."	Technologov
715	[feature-request] Make virtual monitor (screen/display) customizable	VirtualBox 1.5.0	2007-09-24T16:37:14Z	2009-11-26T11:12:40Z	2009-11-26T11:12:40Z	"Please make virtual monitor (screen/display) customizable resolution.

This way, if I have an auto-sensing Linux LiveCD running as guest, I still will be able to force-setup guest resolution.

Currently LiveCDs take full screen on Host, which prevents me from running them in windowed mode.

Not only the problem above, but also the LinuxAdditions suffer from this problem.

-Technologov"	Technologov
990	[feature-request] parallel port	VirtualBox 1.5.2	2007-12-19T13:28:34Z	2013-01-17T15:43:55Z	2013-01-17T15:43:55Z	"Hi,
I need to use parallel port in my virtual machine, but virtualbox doesn`t support it.
It`s that possible in the future?

Thanks,
Karol Sikora"	Karol Sikora
9979	[feature-request] Please allow clones from running VMs	VirtualBox 4.1.6	2011-12-01T15:55:38Z	2011-12-01T15:55:38Z	2011-12-01T15:55:38Z	"Hi,

Host: Win 7 x64 + VBox 4.1.6

For me, it is important to be able to clone from existing snapshot of running VM.

Since we speak about 'snapshots' -- there is no technical reason to forbid it.

{{{
- WinXP (clean)
|-- (SP3, offline snapshot) 
|---- current (running)
}}}

In this case I have a running Win XP VM, but would like to use it's SP3 snapshot to create a new linked clone.

-Technologov, 1.12.2011."	Technologov
7111	[feature-request] Please allow to loop mount VBox HDD images on host	VirtualBox 3.2.6	2010-07-02T14:29:11Z	2012-09-23T00:02:53Z	2012-09-23T00:02:53Z	"Hi,

Please allow to loop mount VBox HDD images on host (VDI+VHD+VMDK). One such third party tool exists for Linux hosts (mounts VDI via FUSE), but it would be nice to have it integrated into VBox and available on all hosts.

Recently a Windows-host related solution became known:

A proposed solution to the loop-mount problem by Fernando Cassia:

Maybe it´s a matter of getting in touch with these guys?

http://www.ltr-data.se/opencode.html#ImDisk

""You can use and redistribute the utilities and source code as you like, but remember to link back to this site or my e-mail adress and always attach any following text file when you redistribute the utilities""

""ImDisk? is a virtual disk driver for Windows NT/2000/XP/2003/Vista/2008. It can create virtual hard disk, floppy or CD/DVD drives using image files or system memory. The install package installs a console-mode control program called imdisk.exe and a Control Panel applet.""

Source code

Source code for all of ImDisk?, including a server-part for *nix like systems, is available as a 7-zip compressed file here (94 KB). The Windows parts of the source code can be built in the Windows 2000 build environemt in the latest WDK and the *nix parts can be built with gcc. If you want to call functions for creating/removing/querying virtual disks from your own program you can #include the file inc\imdisk.h in your C/C++ source files and link the cpl\i386\imdisk.lib library. If you would like information about how to write compatible server-end software you can take a look at the I/O packet structures in inc\imdproxy.h.

License

I have received some e-mails with questions wether or not it is okay to include this driver in a commercial product. The answer is yes, just like all other tools I publish here. However, note that a few lines of code are under the GNU GPL license, this is basically the parts related to floppy emulation. Some of the driver code is also ported to Windows NT from the FreeBSD 'md' driver. 

=======================

I think, that a small modification to ImDisk tool will allow to loop-mount VDI images on Windows hosts.

-Technologov, 2.7.2010."	Technologov
893	[feature-request] Revolutionary CLI for mass-management of Virtual Linux Servers	VirtualBox 1.5.2	2007-11-14T20:26:36Z	2010-05-21T15:56:45Z	2010-05-21T15:56:45Z	"OpenVZ (containerization) includes very interesting concepts of mass-management of servers via CLI.

I would like similar concepts to be included into VirtualBox. 

Imagine You can do: (explained & translated to VirtualBox commands set).

(from host)

Executing guest commands right from the host:

# VBoxManage exec [REDHAT-VM] service sshd status

-or-

# VBoxManage exec 101 service sshd status

sshd is stopped

Another example of sending command from host to guest:

# VBoxManage exec [REDHAT-VM] rpm -ivh [mypackage.rpm]

-or-

# VBoxManage exec 101 rpm -ivh [mypackage.rpm]

installing RPM package...

_

This command will give you immediate TTY line login, just like SSH, even if guest has  no networking and no video card:

# VBoxManage enter vm [REDHAT-VM]

-or-

# VBoxManage enter vm 101

doing ""exit"" will exit to host.

OpenVZ, in addition to names such as [REDHAT-VM], has sequential numbers, like 100, 101, ...

Unlike VirtualBox random UUIDs, this concept theoretically gives ability for doing 
interesting things, such as mass-management via groups of sequentially numbered VMs:

# VBoxManage exec 101-104 rpm -ivh [mypackage.rpm]

[101] installing RPM package...

[102] installing RPM package...

[103] package already exists.

[104] installing RPM package...

and

# VBoxManage exec 101-104 service sshd status

[101] sshd is stopped

[102] sshd (pid 16036) is running...

[103] sshd is stopped

[104] sshd is stopped

This is just a concept. Even OpenVZ doesn't implement it fully. Not to mention that OpenVZ is unable to run on Windows hosts.

OpenVZ listing features are more powerful than VirtualBox, due to it's containerization nature. It looks like: 

# VBoxManage list 

VPSID NPROC STATUS IP_ADDR HOSTNAME

101 8 running 10.101.66.1 vps101.my.org

102 7 running 10.101.66.159 vps102.my.org

103 - stopped 10.101.66.103 vps103.my.org

Isn't that powerful ? - to be able to see hostname, IP address, whatever... right from Host.

Implementing this in VirtualBox will require writing new Linux guest addition module, that enables to access directly to 
Linux guest TTY, without going through any standard channels (display or network).
Also, to implement this, VirtualBox will need sequintial VM numbers, in addition to currently existing VM names and UUIDs.

For additional information about this powerful concept of CLI mass-management read here:
http://openvz.org/documentation/guides/

P.S: I know that some people think that VirtualBox is more Desktop-oriented, and while I agree, I believe that this feature requires relatively small developer's effort, and can seriously improve VirtualBox's positions in the server space.
(especially when VirtualBox will support 64-bit guests)

While original idea is not my, I have an idea of how-to extend this concept further !

This will also improve headless capabilities of VirtualBox.

What do you think of it? :)

-Technologov. 14.11.2007."	Technologov
17436	[FIXED IN SVN] VM 5.2.4 error message when starting Fedora 27 VM after kernel packages update Guru Meditation	VirtualBox 5.2.4	2018-01-08T20:46:23Z	2018-01-10T23:04:19Z	2018-01-10T23:04:19Z	"I updated to 5.2.4. After updating all my linux VMs to the 5.2.4 Guest Additions they all did good restarts. I ran my Fedora 27 VM and did a regular update via DNF in a terminal. The only update was new kernel packages. Upon restart the VM generates a consistent error message and I do the recommended power off of the VM. It said to upload the log file and the .png file. The .png file is just a black rectangle. The error message is as follows:

A critical error has occurred while running the virtual machine and the machine execution has been 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 and the image file VBox.png, which you can find in the C:\Users\[username]\VirtualBox VMs\Fedora 27 x64\Logs directory, as well as a description of what you were doing when this error happened. Note that you can also access the above files by selecting Show Log from the Machine menu of the main VirtualBox window.
Press OK if you want to power off the machine or press Ignore if you want to leave it as is for debugging. Please note that debugging requires special (text recommending a power off follows)

I have already posted to the forums, uploaded the VBox.log, and did a web search. In the forums the following was pointed out:

00:00:17.401353 !!   VCPU0: Guru Meditation -1668 (VERR_PGM_INVALID_CR3_ADDR)

I am attaching a .ZIP file of the VBox.log.



"	GregB3
19806	[Guest OS windows 7] VirtualboxVM process memory increases while launch app in guest OS	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
21501	[GuruMeditation] VirtualBox inside VirtualBox.	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
15765	[Linux] [KDE5] Windows Guest scales incorrectly on High DPI host with Guest Additions	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
13868	[On Mac OS X] The installer encountered an error that caused the installation to fail... please contact software manufacturer for assistance	VirtualBox 4.3.22	2015-02-20T02:51:38Z	2015-02-20T08:24:47Z	2015-02-20T08:24:47Z	"Hello ! 
I tried installing VM VirtualBox on my Mac, and I get this error.
I got the same error when installing another software earlier today... no sure if its mac related or software related so to say...
I have attached the installation log.
The part that seems to fail is ""An error occurred while running scripts from the package “VirtualBox.pkg""

Thanks for any help you can provide !"	Tempestyze
7214	[PATCH] Add BeOS and Haiku to the (Other) guest OS list	VirtualBox 3.2.6	2010-07-21T17:00:51Z	2012-09-20T12:15:29Z	2012-09-20T12:15:29Z	"This patch adds BeOS and Haiku to the Other guest OS list, and selects the correct NIC.
Both require the use of the Intel PRO/1000 MT Desktop NIC due to missing driver for the default one.

VBOXOSTYPE_Haiku is defined as a subtype for VBOXOSTYPE_BeOS though technically it is a reimplementation, so maybe 0xD0000 would fit better.
A 64bit port of Haiku has been started but is not ready yet.
2GB is suggested for the disk, which should be enough for default installs. 256MB of RAM is enough for simple use.

Also added simple png files for the GUI, someone can probably do better.

This patch is under MIT license."	François REVOL
19608	[Patch] Fixed BIOS int 13h, ah=48h	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
13725	[patch] make VNC listen on same port for IPv6 and IPv4	VirtualBox 4.3.20	2015-01-02T11:25:52Z	2015-01-02T11:25:52Z	2015-01-02T11:25:52Z	"Currently, VirtualBox always assigns port 5900 when listening for VNC connections via IPv6, as opposed to IPv4, where the port to use can be set using the property TCP/Ports.

The attached patch changes this behavior so that TCP/Ports also applies when listening via IPv6, thereby using the same port number for both IPv4 and IPv6.

It should be applied in /usr/ports and will create a file emulators/virtualbox-ose/files/patch-src-VBox-ExtPacks-VNC-VBoxVNC.cpp.

See also https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193778

-- Martin"	wonko1953
15264	[Request] Add PCI segmentation support on I/O MMU Virtualization	VirtualBox 5.0.16	2016-03-22T13:51:08Z	2016-03-22T13:51:08Z	2016-03-22T13:51:08Z	"Current PCI passthrough support up to Bus/Device/Function only.

For example:
'VBoxManage modifyvm ""VM name"" --pciattach bus:device.function'

Request to add PCI segmentation support on I/O MMU Virtualization, such as:
'VBoxManage modifyvm ""VM name"" --pciattach segment,bus:device.function'"	alexander3133
2957	[Suggestion] ISZ Compressed ISO Support	VirtualBox 2.1.0	2009-01-04T04:52:36Z	2009-05-16T22:01:38Z	2009-05-16T22:01:38Z	"ISO files can be quite large especially with many application install discs. As such to improve the storage footprint of these compressed ISO's can be of use however VirtualBox does not support this format.

The specification is available on the following address.
http://www.ezbsystems.com/isz/iszspec.txt

It is open to use and is currently supported by a number of 3rd party tools and has so far been quite useful.

Here are some example compression levels.[[BR]]

Windows Server 2003 R2 ISO:120mb ISZ:88mb Saving:26%[[BR]]

Visio 2007 ISO:279mb ISZ:238mb Saving:15%[[BR]]

Office 2007 Enterprise ISO:641mb ISZ:502mb Saving:19%[[BR]]

As you can see there are reasonable savings to be had and even if we go based on say about 10% that's still quite substantial when you are talking a few hundred gig of OS or Software install ISO's.
"	Ross Fawcett
20252	[SVN version] compile error under python 3.9: _Py_NewReference was not declared in this scopt		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
18733	[usb_camera] Can't not support 2 camera(rgb+depth) in one module on usb 3.0	VirtualBox 6.0.8	2019-07-01T09:46:33Z	2019-07-05T12:06:57Z	2019-07-05T12:06:57Z	"There is a module that can record video. It has 2 components, rgb and depth camera.

usb 2.0 does not have enough bandwidth. Hence, it adopts usb 3.0 to support 2 camera output.

When I select ""Device"" -> ""Webcams"" or ""USB"", I can see /dev/video0 and video1, but only one component is passed to virtual box. (I only can attach one from windows to ubuntu, not two)."	fugitive666
18734	[usb_camera] Can't not support 2 camera(rgb+depth) in one module on usb 3.0	VirtualBox 6.0.8	2019-07-01T09:46:42Z	2019-07-01T09:46:42Z	2019-07-01T09:46:42Z	"There is a module that can record video. It has 2 components, rgb and depth camera.

usb 2.0 does not have enough bandwidth. Hence, it adopts usb 3.0 to support 2 camera output.

When I select ""Device"" -> ""Webcams"" or ""USB"", I can see /dev/video0 and video1, but only one component is passed to virtual box. (I only can attach one from windows to ubuntu, not two)."	fugitive666
21268	[virtualbox 7.0.2] doesn't work with a Windows 11 guest on an Arch Linux host	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
19599	[VM Crash] Cannot access memory at 0x00000...	VirtualBox 6.1.8	2020-05-18T16:02:11Z	2020-05-18T17:05:29Z	2020-05-18T17:05:29Z	"My Ubuntu VM will randomly decide to access an inaccessible memory address causing a panic and crash.

I haven't been able to nail this down to a specific event, it seems to happen randomly. If I can identify a reproducible event I'll update the report."	Chris Doherty
20474	[vmwgfx]] *ERROR* Failed to open channel	VirtualBox 6.1.24	2021-07-24T10:35:44Z	2022-03-06T08:22:30Z	2022-03-06T08:22:30Z	"I am running VirtualBox 6.1.24 on Win10 x64, Hyper-V is paravirtualization interface. Ubuntu 20.04 is guest OS.VM is configured to use VMSVGA with 3D enabled.

During boot up, dmesg log has many following records:

[  107.916494] 10:21:10.493550 main     VBoxService 6.1.24 r145751 (verbosity: 0) linux.amd64 (Jul 15 2021 18:33:29) release log
               10:21:10.493575 main     Log opened 2021-07-24T10:21:10.493522000Z
[  107.916494] 10:21:10.493713 main     OS Product: Linux
[  107.916494] 10:21:10.493841 main     OS Release: 5.8.0-63-generic
[  107.916494] 10:21:10.493933 main     OS Version: #71~20.04.1-Ubuntu SMP Thu Jul 15 17:46:08 UTC 2021
[  107.916494] 10:21:10.494012 main     Executable: /opt/VBoxGuestAdditions-6.1.24/sbin/VBoxService
               10:21:10.494034 main     Process ID: 1337
               10:21:10.494057 main     Package type: LINUX_64BITS_GENERIC
[  107.920318] 10:21:10.501490 main     6.1.24 r145751 started. Verbose level = 0
[  107.927561] 10:21:10.508214 main     vbglR3GuestCtrlDetectPeekGetCancelSupport: Supported (#1)
[  121.152249] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  121.152249] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  121.193173] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  121.193173] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  133.960208] rfkill: input handler disabled
[  134.204342] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  134.204342] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  137.828211] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  137.828211] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  174.892246] rfkill: input handler enabled
[  177.579907] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  177.579907] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  178.140558] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  178.140558] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  178.292236] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  178.292236] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  183.200987] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  183.200987] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  184.596248] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  184.596248] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  186.692221] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  186.692221] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.


Detailed logs are attached."	tysonite
17631	A critical error	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
19563	A critical error has been occurred while running virtual machine and the machine execution has stopped	VirtualBox 6.1.6	2020-05-06T01:53:56Z	2020-05-06T01:53:56Z	2020-05-06T01:53:56Z	"I have the following error:
""A critical error has occurred while running the virtual machine and the machine execution has been stopped"".

After running Kali Linux 2020.1 a couple of minutes after installation, I restarted the machine and then this error keeps popping up.

Please see the attachment please and also the log.

VBox.log.2[https://gofile.io/?c=rbENBU]

[[Image(https://i.ibb.co/88z8QL4/kali.png)]]


"	Ehsanul
19566	A critical error has occurred while running a virtual Machine	VirtualBox 6.1.4	2020-05-06T12:01:07Z	2020-05-06T12:01:07Z	2020-05-06T12:01:07Z		Kathir
21495	A critical error has occurred while running the virtual machine	VirtualBox-7.0.6	2023-02-12T18:46:52Z	2023-02-12T18:46:52Z	2023-02-12T18:46:52Z	"Hi All,

Please help, I am using the Virtual box(7.0.6) with Windows 10 64 bit(host) and Ubuntu(22.04) 64 bit (client), when i try to run Docker Desktop in virtual box with Nested VT-x/AMD-V enable having an error with

(""A critical error has occurred while running the virtual machine and the machine execution has been stopped."")

When I dont launch docker desktop I dont see this error

Here I am attaching the log record and its files.
"	gopik45
21434	A critical error has occurred while running the virtual machine	VirtualBox-7.0.6	2023-01-26T13:21:06Z	2023-01-26T13:21:06Z	2023-01-26T13:21:06Z	"hi,

i am using the beta version of virtualbox as i am running on an Apple Mac with an Apple M1 pro processor.

i downloaded the virtual machine from https://developer.microsoft.com/en-us/windows/downloads/virtual-machines/

when i run it i see ""https://developer.microsoft.com/en-us/windows/downloads/virtual-machines/""

any thoughts?

thanks

"	tristian2
17651	A critical error has occurred while running the virtual machine and the machine execution has been stopped	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
19437	A critical error has occurred while running the virtual machine and the machine execution has been stopped.	VirtualBox 6.1.4	2020-03-27T13:11:03Z	2020-03-27T13:11:03Z	2020-03-27T13:11:03Z	"I am using windows10 64bit on UEFI pc desktop this error occured to me trying to use kali linux on virtual box i will attach my vbox.log and vbox.png 
i enabled virtualization , and installed the ext pack same version as the program and still can't make up what's is even the problem! , 
i can't figure any thing from the vbox.log so , any suggestions? "	DEV
19077	A serious error occurred while running a virtual computer with virtualbox	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
8393	A way to define key-combinations which always are passed to the Host OS	VirtualBox 4.0.4	2011-02-21T18:37:36Z	2011-02-21T18:37:36Z	2011-02-21T18:37:36Z	"I commonly run certain utilities in my host OS which are useful whether I'm in the guest OS or not. I would like to be able to set up ""pass through shortcuts"" which always get passed to the Host.

For example the NextAction task list manager always activates with Windows+Z but I run it on my host machine. I would like to be able to set up virtual box so the guest machine does not capture Windows+Z."	George Mauer
21054	Ability for the guest to write on a online-for-the-host partition	VirtualBox 6.1.36	2022-08-07T18:00:10Z	2022-08-08T07:55:31Z	2022-08-08T07:55:31Z	"because as I saw it's read-only .

On my PC's hard disk with Windows 10 Home :

Host : Windows 10 Home

Guests :

firmware-testing-amd64-netinst.iso ( a Debian installer ) : installing  Debian physically on my PC's hard disk dual-boot with Windows 10 Home , everything works except GRUB isn't installed on the original ESP ( EFI system partition ) with EFI\Microsoft\Boot etc .

debian-live-11.4.0-amd64-xfce+nonfree.iso ( a Debian live ) : cannot write e.g. a file on a PC's hard disk partition ( original ESP , C: , D: , Debian partition ( me on ext2 ) ) .

See https://forums.virtualbox.org/viewtopic.php?f=6&t=106689 .

Is it a regression related to https://www.virtualbox.org/ticket/14425 ?"	ecccc3
14840	About dialog needs to be revamped.	VirtualBox 5.0.10	2015-11-17T03:01:49Z	2015-11-17T10:38:26Z	2015-11-17T10:38:26Z	"I have provided a screenshot of the about dialog that I am concerned about.

The about dialog box looks too ""complex"" to the eyes.

My suggestions:
Remove the unnecessarily big, blue 5 and the period.
Make the VirtualBox logo and the gray ""VirtualBox"" text smaller.
Emphasize the actual information (version and copyright info), because that is what most people are looking for in the about dialog box.

This is a major usability issue. I hope this issue gets fixed in the next VirtualBox update."	Bug Tracker
21282	ACPI ERST support	VirtualBox-7.0.4	2022-11-18T17:01:28Z	2022-11-18T17:01:28Z	2022-11-18T17:01:28Z	"ACPI ERST supported by almost all modern motherboards/bioses. It allows to write kernel logs, including kernel panic dumps to special storage. Especially useful for catching and writing panic messages, when system is not able to write to generic partitions. Windows also supports writing  to ERST during BSODs.

This is nice and simple way to store kernel panic logs.

Hope VirtualBox will support ERST soon.

According to article from Oracle blog

https://blogs.oracle.com/linux/post/pstore-linux-kernel-persistent-storage-file-system

''Oracle has been working to improve the usability of the Linux kernel pstore feature.''

QEMU already has this feature:

https://www.qemu.org/docs/master/specs/acpi_erst.html"	AndrewByte
13222	Add a config and an icon for Mageia	VirtualBox 4.3.14	2014-07-20T21:37:22Z	2014-07-20T21:37:22Z	2014-07-20T21:37:22Z	Mageia Linux should be supported by Virtualbox since Mageia actively supports Virtualbox.	TinSmith
16183	Add a warning if user running VirtualBox isn't in group vboxusers on Linux hosts	VirtualBox 5.1.8	2016-11-12T10:53:53Z	2016-11-12T10:53:53Z	2016-11-12T10:53:53Z	If the user running `virtualbox` on Linux (hosts) she doesn't see any USB devices and needs to consult a search engine or the manual in order to figure out that it's necessary to be in the group `vboxusers`. A warning should be given in form of a dialog or a status label in order to improve intuitive usage of the software.	krichter
19707	Add ability to sort and group virtual computers with tags	VirtualBox 6.1.10	2020-07-08T17:34:05Z	2020-07-08T17:34:05Z	2020-07-08T17:34:05Z	"I think it would be useful to be able to tag virtuals with some sort of metadata that lived within the .vbox file. These could be keywords or a predefined set of icons (which would really just be another integer value of 1-255, or whatever). Then being able to filter the list of virtuals based on the metadata would be useful for managing large lists of virtuals.

In my case, I have a bunch of virtuals that I want to archive and I'd like to be able to tag them, regardless of the grouping, so I can work through them one-by-one or give that task to someone else. It would potentially allow grouping by more than the one level that's offered now. Other examples might be to group virtuals by OS, company, department, maintenance schedule, virtuals with problems, by network, etc."	SDS
19377	Add additional diagnostic information for the VERR_SUP_VP_THREAD_NOT_ALONE error	VirtualBox 6.1.4	2020-03-04T14:49:22Z	2020-03-04T14:49:22Z	2020-03-04T14:49:22Z	"Would it be possible to add additional information to the hardening log when this happens, to make it easier for users to identify the application that is causing the conflict?

For example, when VirtualBox detects an extra thread running that shouldn't be there, can you print a stacktrace to the hardening log that includes the DLL names for the code that is currently executing in that other thread?"	rwreed
8020	Add appropriate comments for strings that are used in other strings (in translation *.ts files)	VirtualBox 4.0.0	2011-01-06T16:34:20Z	2011-01-06T16:34:20Z	2011-01-06T16:34:20Z	"Some messages are confusing for translation, because it has no explanation or even wrong explanation. Without this, translator must force to check his translation practically.
For example:

in VBoxGlobal section are source texts, that has no explanation: ""hard disk"", ""CD/DVD-ROM disk"", ""floppy disk"". All these strings are incorporated in ""All %1 images (%2)"". For example, in Lithuanian, ""floppy disk"" is ""diskelis"", but in sentence ""All floppy disk images"" it must be translated as ""...diskelių"".

in VBoxProblemReporter section are source texts ""hard disk"", ""CD/DVD"", ""CD/DVD image"", ""floppy"", ""floppy image"" has comment ""failed to mount ..."", but these messages are used in dialog ""Are you sure you want to release the..."". So this situation should be mentioned in the comment. Yes, there is no difference such languages as English, French, but it is important for such languages as Lithuanian. For example, ""hard disk"" in Lithuanian is ""standusis diskas"", but in sentence ""failed to mount hard disk"" it will ""...standžiojo disko"", in sentence ""Are you sure you want to release the hard disk"" it will ""...standųjį diską"". 

So please strive to precisely describe context of strings, that incorporates in other messages, or use full sentence (it would be better for translators).

Regards,
translator to Lithuanian"	Mindaugas Baranauskas
19519	Add CloneVDI features to VirtualBox itself	VirtualBox 6.1.6	2020-04-20T17:09:58Z	2020-04-20T17:09:58Z	2020-04-20T17:09:58Z	"I think the features CloneVDI developer introduced in the program (https://forums.virtualbox.org/viewtopic.php?t=22422) are features which deserve to be added to the main Virtualbox program. It would be a great update to the disk management in Virtualbox.

Thanks in advance."	gio91ber
19745	Add emulation for x86, ARM guests	VirtualBox 6.1.10	2020-07-21T19:46:51Z	2020-07-21T19:46:51Z	2020-07-21T19:46:51Z	With macOS and Windows beginning to shift to ARM, it will prove helpful for VirtualBox to gain support to run emulated ARM and x86 guests.	mcandre
15727	Add HiDPI Support for macOS guests	VirtualBox 5.1.2	2016-08-02T20:49:40Z	2016-08-02T20:49:40Z	2016-08-02T20:49:40Z	When running VirtualBox on a MacBook Pro Retina, the Chrome of VirtualBox (Window Frames and the Icons at the Bottom of the Window) are rendered in HiDPI just fine, but the macOS Guest doesn't run in HiDPI mode.	Lars Sonchocky-Helldorf
6358	Add official support for running as a service	VirtualBox 3.1.4	2010-03-11T11:28:42Z	2012-02-27T16:31:41Z	2012-02-27T16:31:41Z	"Hi
In my opinion the only reason that a lot of users (including me) cant really get virtualbox to work as they want is because of lack of running VB as a service( the very same thing that Virtual Server for microsoft has ). we really need to be able to run VMs before logging in and shutting them down automatically when the system is shutting down. of course they are some tricks around already but they are all really messy and have a lot of issues. i think adding this ability could make a lot of users happy and make the virtual box the best virtualization software ever."	Hamy
13416	Add option to allow VM to swap	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
8808	Add option to stop machine on error warning	VirtualBox 4.0.6	2011-04-29T12:21:20Z	2011-04-29T12:21:20Z	2011-04-29T12:21:20Z	"Sometimes hardware issues cause VB to show a warning when opening a VM. This warning could give the user the option not to start the VM. This would be useful for allowing the error to be corrected before indeed running the VM.
I sometimes get errors due to an issue in a serial peripheral I have (which doesn't seem to have a fix). When I open the VM, I get a warning - then I have to wait for the guest OS to load, then shut it down. Instead, I'd like to tell VB not to open the VM, correct the error condition, and then open the VM correctly."	Emerson Prado
12362	Add possibility to update snapshots	VirtualBox 4.3.2	2013-11-14T09:51:50Z	2013-11-14T09:51:50Z	2013-11-14T09:51:50Z	"Sometimes I want to start a VM with a specific snapshot, do some work and then create a snapshot with the current state that replaces the old one.

At the moment, I would have to create the new snapshot and afterwards manually delete the old one.

It would be more convenient, if I could simply update the old snapshot so it contained the current state.


Lars
"	larsen0815
12590	Add Run from last snapshot workflow option	VirtualBox 4.3.6	2014-01-09T00:14:53Z	2014-01-09T00:14:53Z	2014-01-09T00:14:53Z	"I use VirtualBox to test a lot of software. One action I perform repeatedly is to close a VM session, revert to the last snapshot, then start the VM again. There should be a way to perform this task quickly and automatically.

Instead, I have to close the VM session, right-click the last snapshot, click restore, possibly dismiss a dialog about saving the current state (which I almost never care about, or I would have snapshotted it manually already), then clicking start to bring the VM back up.

There should be an option to do this either on the close dialog itself or as a break-out option. If it could have a hotkey combination - even a complex one, then even better.

Note: If I take a snapshot during a session, then that is the snapshot that should be used, not the one that originally started the machine."	Diggie_OC
15898	Add Shared Folder - pasting folder path causes VBox Manager to crash - until navigated to.	VirtualBox 5.1.4	2016-09-07T10:29:17Z	2016-09-15T14:13:50Z	2016-09-15T14:13:50Z	"{{{
VirtualBox Manager version 5.1.4.
Windows 10.
}}}

(Up to this time I have never tried to add a Shared Folder. Ie no 
VM has one, and I've never attempted to configure one.)

{{{
Select a VM.
Select Settings.
Select Shared Folders.
Select '+' to add a new shared folder.
Paste a folder path into the Folder Path entry box.
select OK.
VirtualBox Manager crashes.
}}}

This crash was completely repeatable until I approached the task in 
a different way.

{{{
Select a VM.
Select Settings.
Select Shared Folders.
Select '+' to add a new shared folder.
Select the drop-down arrow in the Folder Path entry box.
Navigate to the folder I want to add.
Select it.
Select 'Select Folder'.
All works fine.
}}}

After doing the task once this way it now works entirely 
satisfactorily doing it the first way, ie by pasting in a 
folder name.

So, not as serious a fault as I first thought but smells to 
me like something not initialized if one hits some code first 
by pasting the folder name rather than by navigating to it.

[[br]]
I have reported this on the forum and been advised that it is 
a Qt5 library issue and that I should report it here.

I have no unusual storage devices, it's a conventional Windows
desktop computer.  There is no Bluetooth.
[[br]]
The crash occurred for all the VMs that I tried.  Most are
Windows guests, one is Linux.
[[br]]
Once it works it continues to work.

"	Richard Kerry
19803	Add support for SATA attached read-only (RO/RDONLY) vmdk disks		2020-08-09T11:13:26Z	2020-08-09T12:03:10Z	2020-08-09T12:03:10Z	"Currently you cannot attach a full raw real harddisk with the RDONLY (read-only) flag set as the VM execution runs into an error:


'''The I/O cache encountered an error while updating data in medium ""ahci-0-1"" (rc=VERR_INVALID_HANDLE). 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

[Copy] [OK]
}}}

Pressing OK doesn't allow to continue the execution.

Please fix.

Here's an example VMDK image:

{{{
# Disk DescriptorFile
version=1
CID=abcdedfg
parentCID=ffffffff
createType=""fullDevice""

# Extent description
RDONLY 800000000 FLAT ""/dev/sda"" 0

# The disk Data Base
#DDB

ddb.virtualHWVersion = ""4""
ddb.adapterType=""ide""
ddb.geometry.cylinders=""16383""
ddb.geometry.heads=""16""
ddb.geometry.sectors=""63""
ddb.uuid.image=""xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx""
ddb.uuid.parent=""00000000-0000-0000-0000-000000000000""
ddb.uuid.modification=""xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx""
ddb.uuid.parentmodification=""00000000-0000-0000-0000-000000000000""
ddb.geometry.biosCylinders=""1024""
ddb.geometry.biosHeads=""255""
ddb.geometry.biosSectors=""63""
}}}"	Artem S. Tashkinov
18756	Adding permanent shared folder through VBoxManage	VirtualBox 6.0.8	2019-07-15T11:01:23Z	2019-07-15T15:18:49Z	2019-07-15T15:18:49Z	It is not possible to add a permanent shared folder while the VM is running with VBoxManage whereas it is possible from the GUI.	Luc123
19534	Adding USB devices has useless serial number	VirtualBox 6.1.6	2020-04-26T12:47:28Z	2020-04-26T12:47:28Z	2020-04-26T12:47:28Z	"Running on Windows 10
I have a number of USB serial devices and trying to identify which one to add is problematic.

VirtualBox is showing ""Serial No."" but I can't find that number anywhere in device manager or the registry on my machine.
What I can find is at the top of the details is ""Device Instance Path"" which looks unique and is easily found to identify the specific USB device needed.


"	Mad Dog Black
9076	After canceling Cmd-Q confirmation dialog keyboard settings are screwed up	VirtualBox 4.0.8	2011-06-15T05:52:54Z	2011-06-15T05:52:54Z	2011-06-15T05:52:54Z	"I'm using a debian squeeze 64bit guest on my MacOSX 10.6.7 host.

Sometimes, I incidentially hit 'Cmd-Q' and a confirmation dialog pops up, which ask me whether I want to power off the VM, save it to disk or quit the operation an return to the VM. I then choose the third option and continue my work.

Howerver, the keyboard setting are screwed up after canceling this confirmation dialog. If I type 'Ctrl-X', my emacs tells me 'Key C-S-x undefined', for example. Another example is, that typing 'Shift-Left' produces the upper-case letter 'C'.

It would be very nice, if this issue could be fixed,

  TIA, Wolfgang"	Wolfgang Glas
19954	"after DISabling timesync in VB linux guest's GuestAdditions, boot errors: ""timesync Error: vgsvcTimeSyncWorker: VbglR3GetHostTime failed; rc2=VERR_NOT_SUPPORTED"" ?"	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
17900	after install old Ubuntu 8.04 and then reboot, the virtualbox will show error	VirtualBox 5.2.16	2018-07-28T13:42:43Z	2018-07-28T13:42:43Z	2018-07-28T13:42:43Z	"1.after install old Ubuntu 8.04 and then reboot
2.the virtualbox will show error,as attached in the picture, the log is also attached."	nsynet
20135	After installing Centos OS the VM is failing to reboot	VirtualBox 6.1.16	2021-01-18T21:52:15Z	2021-01-18T21:52:15Z	2021-01-18T21:52:15Z	"The Host PC is Windows 10, after installing a Centos minimal image using vagrant the image fails to boot. There are obvious errors that in the log file.
I have installed an ubuntu vm and that works fine.

"	harryv
17636	After minimising full screen VM, on restoring only quarter of screen shown	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
16284	after osx Sierra upgrade - docked VM now requires two clicks	VirtualBox 5.1.10	2016-12-12T21:33:00Z	2016-12-12T21:33:00Z	2016-12-12T21:33:00Z	After upgrading to osx sierra, I noticed that a running, minimized VM in the dock, now requires two clicks (on the docked VM icon) to restore said window (formerly it only required one). The first click restores focus to VB menubar, the second restores the VM window. 	littlerunningdeer
13523	After snapshot VM won't start.	VirtualBox 4.3.16	2014-10-17T14:29:27Z	2014-10-17T15:53:31Z	2014-10-17T15:53:31Z	"I made a snapshot of the virtual machine it would not start anymore the result I get is:
No error info:

Result Code: 
E_FAIL (0x80004005)
Component: 
ProgressProxy
Interface: 
IProgress {c20238e4-3221-4d3f-8891-81ce92d9f913}
"	ditproz
17444	After start virtualbox my bluetooth dongle doesn't  work.	VirtualBox 5.1.30	2018-01-10T09:12:07Z	2018-01-10T10:19:12Z	2018-01-10T10:19:12Z	"In my worktime I want to use an usb bluetooth adapter (Asus USB-BT400) for my bluetooth headset but it's doesn't work. Previously, I thought the problem was with the driver or my motherboard, but later I realized the problem occurs when I launch the virtualbox.
I just need to start the basic program without launching any guest.

The device status is as follows: This device cannot start. (Code 10)
If I close the virtualbox and I replug the adapter, The error will be terminated.

I tried different drivers, usb hubs, and computers but nothing changed.
The host type all of my computer I tried: Windows 10 Enterprise N 64bit"	JosephK
14133	After update, the windows taskbar icon is wrong	VirtualBox 4.3.28	2015-05-18T17:50:17Z	2015-05-18T17:50:17Z	2015-05-18T17:50:17Z	"after running an update, the virtual box icon in the windows task bar goes becomes a default ""white page with folder corner"" icon.  the correct icon does not reappear until reboot."	goat walker
19239	After updating from VB 6.1.0 to 6.1.2. start of guests fails with NS_ERROR_FAILURE (0x80004005)created	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
17522	After updating software and kernel of Xubuntu 17.10.1 - critical error on restart	VirtualBox 5.2.6	2018-02-02T20:44:39Z	2018-04-09T05:43:59Z	2018-04-09T05:43:59Z	"After a good install of Xubuntu, ran software updates, during restart got a critical error:

Installed latest 5.2.7 test build and got same error:

""A critical error has occurred while running the virtual machine and the machine execution has been 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 and the image file VBox.png, which you can find in the /Users/dwhea/VirtualBox VMs/Ubuntu/Logs directory, as well as a description of what you were doing when this error happened. Note that you can also access the above files by selecting Show Log from the Machine menu of the main VirtualBox window. Press OK if you want to power off the machine or press Ignore if you want to leave it as is for debugging. Please note that debugging requires special knowledge and tools, so it is recommended to press OK now."""	wadesnj
16371	After Updating to Windows 10 Enterprise Insider Build 15002 VirtualBox 5.1.12 Won't Launch	VirtualBox 5.1.12	2017-01-10T17:13:23Z	2017-01-12T16:15:58Z	2017-01-12T16:15:58Z	"After Updating to Windows 10 Enterprise Insider Build 15002 VirtualBox 5.1.12 Won't Launch, below is the error I am receiving. I uninstalled and reinstalled Virtual Box, as well as tried starting in Win 8 Compatibility mode. Let me know if you need any other info.
{{{
Log Name:      Application
Source:        Application Error
Date:          1/10/2017 11:07:04 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      CAT-670ZH72.catapultsystems.com
Description:
Faulting application name: VirtualBox.exe, version: 5.1.12.12440, time stamp: 0x58594e7b
Faulting module name: VirtualBox.exe, version: 5.1.12.12440, time stamp: 0x58594e7b
Exception code: 0xc0000005
Fault offset: 0x0000000000013a1d
Faulting process id: 0x2470
Faulting application start time: 0x01d26b63f72f8901
Faulting application path: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
Faulting module path: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
Report Id: e55f15cb-c698-496e-8288-7f3763f5933a
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
<Event xmlns=""http://schemas.microsoft.com/win/2004/08/events/event"">
  <System>
    <Provider Name=""Application Error"" />
    <EventID Qualifiers=""0"">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime=""2017-01-10T17:07:04.074275800Z"" />
    <EventRecordID>496</EventRecordID>
    <Channel>Application</Channel>
    <Computer>CAT-670ZH72.catapultsystems.com</Computer>
    <Security />
  </System>
  <EventData>
    <Data>VirtualBox.exe</Data>
    <Data>5.1.12.12440</Data>
    <Data>58594e7b</Data>
    <Data>VirtualBox.exe</Data>
    <Data>5.1.12.12440</Data>
    <Data>58594e7b</Data>
    <Data>c0000005</Data>
    <Data>0000000000013a1d</Data>
    <Data>2470</Data>
    <Data>01d26b63f72f8901</Data>
    <Data>C:\Program Files\Oracle\VirtualBox\VirtualBox.exe</Data>
    <Data>C:\Program Files\Oracle\VirtualBox\VirtualBox.exe</Data>
    <Data>e55f15cb-c698-496e-8288-7f3763f5933a</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>
}}}"	Bobbyw87
20921	After upgrade guest to Ubuntu 22.04 LTS screen and mouse doesn't work	VirtualBox 6.1.32	2022-04-29T17:53:51Z	2022-04-30T19:42:55Z	2022-04-30T19:42:55Z	"After upgrade guest to Ubuntu 22.04 LTS screen and mouse doesn't work

See please video: https://drive.google.com/file/d/1C0IOJlqY-n71PDoVgYfVfrsuHKaUMnvD/view?usp=sharing"	Ilia Poliakov
18118	After upgrade XP game hangs	VirtualBox 5.2.20	2018-11-09T16:43:26Z	2018-11-09T17:48:29Z	2018-11-09T17:48:29Z	After upgrading to 5.5.20 a game I play in XP hangs up	TG3500
20737	after using save the machine state vm virtual box is not asking for login for next time	VirtualBox 6.1.30	2021-12-19T07:09:26Z	2021-12-19T07:09:26Z	2021-12-19T07:09:26Z	"hello,
i am using Virtual Box 6.1.30 and i am running kali linux in vm my main os or host machine is windows 11 
bug is that when i am selecting 'save the machine state'  before terminating the instance and after closing that machine when i start that machine again it's not asking for login credentials user and password
it's allowing to directly use that machine without login credentials the logged in user is the same before saving the machine state.
 
"	AFTAB SAMA
20428	Alias	VirtualBox 6.1.22	2021-06-24T15:28:36Z	2021-06-24T16:07:46Z	2021-06-24T16:07:46Z	I just updated my mac to 10.15.7 and now I can't create a desktop alias for my vm box like i could before the update. If i go thru the steps to create an alias, it puts an icon on the desktop but it is invalid. If I go directly to where the vm files are stored and I click on the box name, it asks what application i'd like to use to open the file. I am using vm 6.1.22. How can I get my alias back on my desktop???	Peter Decesare
15430	Alias on Desktop corrupt after running	VirtualBox 5.0.20	2016-05-18T19:48:18Z	2016-05-18T19:48:18Z	2016-05-18T19:48:18Z	"If I ""Create Alias on Desktop"" (from the Machine Menu), a shortcut (Alias) is properly created on my desktop.  However, if I use that shortcut to start the machine (when virtual box is not already running) the shortcut may get corrupted by VirtualBox.  By that, I mean that instead of pointing to the .vbox file, it will end up pointing to the .vbox-prev file and thus can't start the VM.  Somehow the application is changing the ""original"" to the preview file.

This happens nearly ever time, but not every time and I am not sure what exactly triggers it.  I generally start the machine from a saved state, with virtual box not already running.

Virtualbox install is standard default installation.  This has existed for at least the last three or four versions."	chrijm
17697	all new VirtualBox session hang when Skype for Business start a conference/meeting call	VirtualBox 5.2.10	2018-04-19T10:04:14Z	2018-05-28T07:23:16Z	2018-05-28T07:23:16Z	all new VirtualBox (after interface changed) session hang when Skype for Business start a conference/meeting call.	blaine
20243	All Virtual Machine freeze when loading into OS	VirtualBox 6.1.18	2021-03-10T23:46:08Z	2021-03-26T01:35:18Z	2021-03-26T01:35:18Z	"All Virtual Machine freeze when loading into OS. I have tried disabling hyper-v, making sure no antivirus is stopping it, and played with all the configuration and the issues persists.

The logs of one of my vms are attached, please let me know what I can get to you so this can be resolved.
"	Cliftonz
18977	"All VM's on VirtualBox  goes to ""Guru Meditation state "" when KVM(virt-manager) VM's are 'power on'"	VirtualBox 6.0.12	2019-10-03T02:19:44Z	2019-10-03T08:12:21Z	2019-10-03T08:12:21Z	"Hello Team
    I am running a host pc ----> Linux GS-4184 4.15.0-64-generic #73-Ubuntu SMP Thu Sep 12 13:16:13 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

    I have created three VM's on Virtualbox names as Client1,Client2,Client3 each 4GB RAM and less than 10GB Memory all are Ubuntu VM's which were running properly before installing KVM. I poweroff the VM's from Virtualbox and installed KVM(virt-manager) and created 3  VM's Database,Server,MyServer all were ubuntu VM's 3GB RAM and less than 10GB memory.But as soon as i power on the VM's on KVM my virtualbox VM's goes to ""guru meditation state"" whenn i click on ignore the get automatically poweroff.At a time am able to run only either Virtualbox VM's or KVM' VM's but i want to run it simultaneously(Because i want to create a VM as a server in KVM which should be in running state so that client VM's on KVM should request it for service ) But i dnt know it is possible or not to run this kvm and VB simultaneously if not then why? If it is possible to use KVM and Virtualbox simultaneously then please give me the solution to resolve this issue. 
"	aeronwin
16015	All VMs crash on macOS 10.12 with NS_ERROR_FAILURE (0x80004005)	VirtualBox 5.1.6	2016-10-02T21:35:54Z	2016-10-03T19:50:54Z	2016-10-03T19:50:54Z	"Hello,
Whenever I launch any of my VMs on macOS 10.12, the VM crashes immediately with NS_ERROR_FAILURE (0x80004005). The whole error given by VirtualBox:

Failed to open a session for the virtual machine OS X Install Test.

The virtual machine 'OS X Install Test' 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}

No VBox.log file is made, but a Crash Reporter log is given, which I have attached. It mentioned ""Illegal Instruction: 4"" and ""BUG IN CLIENT OF LIBDISPATCH: _dispatch_main_queue_callback_4CF called from the wrong thread"".

Jack"	JackMacWindows
3814	All VMs running on X partition should pause (stop running) when there's only certain amount of space left on the X partition	VirtualBox 2.2.0	2009-04-22T18:41:25Z	2009-04-22T18:41:25Z	2009-04-22T18:41:25Z	"All VMs running on X partition should pause (stop running) when there's only certain amount of space left on the X partition.

When they pause, a dialog should open informing the user about it, and maybe it's also interesting to offer her the possibility of discarding snapshots (in order to save space), as long as this ticket is already fixed: http://www.virtualbox.org/ticket/3813

The ""certain amount of space left"" could be, for instance, 10,000 KB."	Andres G. Aragoneses
16743	"Allow ""Restore current snapshot"" from right-click Close in Manager"	VirtualBox 5.1.22	2017-05-08T12:13:19Z	2017-10-29T09:27:32Z	2017-10-29T09:27:32Z	"When a VM window is closed, there are 3 options (save, shut down, power off), and the last option ""Power off the machine"" has a checkbox for ""Restore current snapshot [...]"".

It would seem appropriate to give the same checkbox choice when closing from Oracle VM VirtualBox Manager, and also to use the same option names instead of, e.g., ""Send the shutdown signal"" vs. ""ACPI Shutdown""."	RafSchietekat
18894	Allow deleting running VMs	VirtualBox 6.0.10	2019-09-02T17:32:28Z	2019-09-02T22:30:03Z	2019-09-02T22:30:03Z	"As a user who frequently spins up and tears down many VMs, the current GUI restriction on deleting only non-running VMs is annoying.

Please enable the Remove option when VMs are running, so that users can efficiently delete VMs. It's one thing to show a confirmation prompt on deletion, another to hide the option altogether :/"	mcandre
19320	Allow exporting & importing of VMs with NVMe storage devices	VirtualBox 6.1.2	2020-02-18T03:53:39Z	2020-02-19T03:13:25Z	2020-02-19T03:13:25Z	"VirtualBox errors when exporting a VM with an NVMe controller:

{{{
VBoxManage error: VBoxManage: error: Cannot handle medium attachment: storageBus is 7, channel is 0, device is 0
VBoxManage: error: Details: code VBOX_E_NOT_SUPPORTED (0x80bb0009), component MachineWrap, interface IMachine, callee nsISupports
VBoxManage: error: Context: ""ExportTo(pAppliance, Bstr(pszAbsFilePath).raw(), pVSD.asOutParam())"" at line 1534 of file VBoxManageAppliance.cpp
}}}


There is no support for StorageBus_PCIe in src/VBox/Main/src-server/ApplianceImplExport.cpp nor ApplianceImplImport.cpp"	davecardwell
4635	Allow remapping of parallel port addresses	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
1751	Allow SMBIOS information to be copied from host	VirtualBox 1.6.2	2008-06-20T17:39:36Z	2010-05-24T20:49:04Z	2010-05-24T20:49:04Z	"Please see this thread: <http://forums.virtualbox.org/viewtopic.php?t=3224>, in particular the original message from user disz and the one at Mon Feb 25, 2008 11:53 pm.

In short the request is to add functionality to copy the SMBIOS information from the host to be reflected in the guest machine.

Use case: One prefers for instance Linux as the main operating system. The machine was however originally delivered with Windows, including some software that is desirable to run. Dual-booting is considered cumbersome. This problem could be solved by running the software in a virtualized, seamless Windows guest, but this requires that the OEM version has access to the correct SMBIOS information in order to not fail activation."	Roland Kaufmann
4229	Allow specification of the configuration directory (VBOX_USER_HOME) from the command line.	VirtualBox 2.2.4	2009-06-13T17:22:26Z	2009-06-14T14:42:20Z	2009-06-14T14:42:20Z	"Allow users to specify the configuration file location on the command line (or via the VirtualBox GUI) for all VirtualBox frontends - VirtualBox, VBoxManage, VBoxHeadless, etc.

For instance on a Windows(R) Host:

{{{
VBoxManage configLocation C:\temp\myVirtualMachine list vms
}}}

or

{{{
VBoxHeadless configLocation C:\temp\myVirtualMachine -startvm myVM
}}}


This configuration location would override the environment variable VBOX_USER_HOME (i.e., the configuration location would specify the location of a VirtualBox.xml file and its associated Machines directory).

There are a number of benefits to this approach:
   * Configuration of a virtual machine to run as a Windows service becomes trivial (XP, Vista, 7)
   * Allows users to share virtual machine configurations across multiple users accounts.
      * This is especially important in some academic environments where disk space is limited.
   * Virtual machine configurations could now be distributed easily. 
      * Deployment of virtual machines as a means of High Throughput Computing is simplified.
   * Poses no security risk since file permissions are managed via the host operating system.

"	David Herzfeld
16322	Allow specifying a VHD diff file location when cloning	VirtualBox 5.1.12	2016-12-23T17:21:29Z	2017-03-16T13:19:38Z	2017-03-16T13:19:38Z	When cloning, I expected to be able to specify the destination folder when using the diff method, just like you can when creating a new machine and creating a new disk.	Will Power
10272	Allow storing virtual machine settings in a directory thus multiple virtual box installation could share	VirtualBox 4.0.16	2012-02-21T13:33:20Z	2012-02-21T13:33:20Z	2012-02-21T13:33:20Z	"Currently the settings of each virtual machine are stored in an xml file. I suggest to allow storing settings of a machine in a single directory.

For my case, I have double systems on my machine: a Windows and a Linux. I have Virtual Box installed on both systems, but the settings in the virtualbox of one systems changes, the other won't. So I believe this is a valuable suggestion."	Hong Xu
13303	"Allow to rename or add a comment to the ""Current State"" ""snapshot"""	VirtualBox 4.3.14	2014-08-20T09:25:51Z	2014-09-10T14:03:07Z	2014-09-10T14:03:07Z	"Atm, it is possible to add a name and description for a snapshot. This is not yet possible for the ""Current State"".

I often work with a VM, install software for testing purposes and then forget about it when other things need attention. Two weeks later I will be wondering what the purpose or last state is.

It would be very helpful if I could add a description and/or name, so instead of ""Current State"" the title would be ""Current State (testing Gitlab)"".

I could easily change the title or update it. With snapshots, I would have to create multiple to achieve this.
"	larsen0815
5557	Allow user to specify network card option ROM image, and ship default PXE images for boot.kernel.org	VirtualBox 3.0.12	2009-11-25T03:57:57Z	2009-11-25T07:25:22Z	2009-11-25T07:25:22Z	"Take a look at http://boot.kernel.org/

You can download a tiny floppy or USB/CD image from there, which uses gPXE to boot a selection of Linux operating systems and diagnostic tools over the internet.

Also look at http://rom.etherboot.org/share/pravin/rom-o-matic-BKO.net/

You can build a boot option ROM there. If you were to ship suitable network card boot ROM images with VirtualBox, it would allow new users to immediately test out various OSes by booting over the internet. No need to make hard disk image files or download anything first. New installs could have an initial default VM present so the user could get started straight away.

More generally, make it possible to specify option ROM images for a VM in VirtualBox settings. That is not necessarily specific to network cards; you could have an option ROM for anything, e.g. a nice logo screen prior to booting or whatever.

Alternatively, you could supply .pxe files for each type of emulated network card which would allow users to use VirtualBox's PXE boot facility with NAT networking to bootstrap from boot.kernel.org. Attached is a .pxe file for AMD pcnet32 with the appropriate gpxe script embedded."	Donuts
18899	Allow VM window to close while VM settings window is open	VirtualBox 6.0.10	2019-09-03T01:44:51Z	2019-09-03T09:32:55Z	2019-09-03T09:32:55Z	Please change the parent of the VM virtual display window, so that it can be closed when the VM's settings window is open.	mcandre
17327	alt tab within vm passes alt tab to windows 10	VirtualBox 5.1.30	2017-11-29T08:12:01Z	2017-11-29T08:12:01Z	2017-11-29T08:12:01Z	"If I press my host key combination to switch to seamless mode, but click cancel, alt-tab no longer works within my linux vm, it is instead sent to Windows 10, and the task switcher in Windows 10 comes up.  The only way of making it work again is to switch to seamless mode and back to the normal mode.  Once that's done, the alt-tab is then working within the linux vm.

"	Trent
15131	Alt+MouseScroll is broken	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
3473	alt+printscreen and windows-logo+E  used to work but now do not	VirtualBox 2.1.2	2009-03-02T14:27:17Z	2011-03-21T16:26:07Z	2011-03-21T16:26:07Z	"Hi,

on a solaris host (snv_103 X86) with windows XP guests

   ( in all cases below guest additions were installed )

In 2.0.6 I was able to pop up windows explorer with the standard keyboard shortcut of windows-logo key + 'E'

I was also able to take a ""snapshot"" of the active microsoft window with alt+printscreen (for pasting into Word or an Image Tool or whatever)

In 2.1.2 I no longer can.

At first I thought maybe it was me .... but I uninstalled 2.1.2 and re-installed 2.0.6 and the functionality returned.

I recently installed 2.1.4 and the alt-prtscreen seems to work (it seems slower but I'll take it)  BUT the windows-logo key + 'E' to pop up windows explorer still does not work.

If I can be of help to a developer I'm happy to try things out.
"	cj
13778	Alt+Tab breaks keyboard input	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
14093	AltGr issue on Windows 8.1 and Windows 7 with Czech keyboard layout	VirtualBox 4.3.26	2015-05-04T10:52:51Z	2015-05-15T13:18:34Z	2015-05-15T13:18:34Z	"This is weird issue, as I am not able to reproduce it alltime, but I know, after several hours of running guest it results in this weird issue.

Host: MS Windows 8.1 (64 bit) or Windows 7 (64 bit).
Guest: Debian Wheezy (64 bit) or Debian Jessie (64 bit).
Guests addons installed from Debian's contrib repository.

AltGr-a (~) is not working, when host keyboard layout is Czech, but works if keyboard layout is English USA. All other AltGr combinations (I use) work fine.

I have already investigated it using {{{xev}}}, I can see keystroke {{{ISO_Level3_Shift}}}, but no {{{a}}} keystroke, but for example AltGr-q (\) I can see both keystrokes.

Auto capture is disabled. When auto capture is enabled it works as expected, but it is not handy for me.

I see similar fixed issue #13216.

Offtopic: Is it possible to create Extension Pack, that will not capture several key combinations, so for example ctrl-alt-(anything) will not be captured even if auto capture feature is enabled?"	xdml
19881	AltGr not working most of the time	VirtualBox 6.1.14	2020-09-10T16:11:59Z	2020-09-11T07:33:32Z	2020-09-11T07:33:32Z	"Setup is a Linux (nixos 20.03) VM on a Windows 10 laptop, usually with 2 screens attached. The VM gets 3 virtual screens.
Both host and guest use a german (qwertz) keyboard layout.

Most of the time, the AltGr key and with it many symbols are not working on the guest. According to xev pressing the key does not trigger anything at all.

Often, but not always, changing from one virtual display to another will make the AltGr key work for a few times before falling back to not doing anything at all.

Sometimes, when changing to another screen and beginning to type, the first letter will be greek and I don't even know how to type those deliberately (it's not AltGr+something).

There have been days where it worked the whole time but those are rare.

Turning automatic keyboard capturing off as some related incidents suggested as solution does not help.

Suspending (save execution state) and restarting does also not help reliably.


To me it seems as if somehow the modifier gets stuck or a wrong keycode is sent or it gets out of sync between host and guest or between the virtual screens?
I can't really find any 100% reliable way to trigger or fix this behaviour.


I'll gladly provide any additional info or perform tests that could help this issue."	Nervengift
13916	Altium on VirtualBox	VirtualBox 4.3.24	2015-03-03T23:56:44Z	2015-03-04T19:07:02Z	2015-03-04T19:07:02Z	"this question is different from tickets #10954 and #10190

When I try to use Altium 13.3 on windows 7 vm (ubuntu 14.04 host), I am not able to see the traces when I run interactive routing. Like those previous tickets I did find that Altium said that I was not supporting DirectX9, though I found the two drivers appropriately one being microsoft and the other oracle based. 

When I run dxdiag, I see that I am running DirectX 11 which should be backwards compatible with DirectX9.

any help would be appreciated"	Farris
18111	Always in Snapshot-View - 5.2.20	VirtualBox 5.2.20	2018-11-06T08:01:53Z	2018-11-06T17:31:43Z	2018-11-06T17:31:43Z	"My english isn't so good to translate my problem:
https://forums.virtualbox.org/viewtopic.php?f=5&t=90176"	VM-F4n
18347	Always NS_ERROR_FAILURE after latest Fedora 29 update	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
20021	AMD Ryzen 9 3900XT - Slackware Current64 - kernel 5.9.3-burdi64 - VM's fail to start	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
20548	AMD vs Intel CPU big performance difference	VirtualBox 6.1.26	2021-09-14T07:03:50Z	2021-10-20T11:43:14Z	2021-10-20T11:43:14Z	"I use single VM on both Intel and AMD hardware. When I moved it from Intel to AMD I noticed the performance is much better. Next I tried to switch to Hyper-V on both machines, converted the VDI file and use it. 

On Intel Core i5 2540M and Intel Core i5-8265U the performance difference was about 50 percent while on AMD Ryzen 5 3600 both VirtualBox and Hyper-V performs almost identical (5 percent difference is as expected). The AMD PC machine has super fast Samsung 980 Pro SSD while the Intel laptop just an ordinary WD SSD. Still the difference is huge.

The guest OS I use for software development. It is Windows 10, Visual Studio, MS SQL Server and so on. I run unit tests of a complex project and recorded how long it takes, see the tests.png attachment. 

There is a long thread [https://forums.virtualbox.org/viewtopic.php?f=2&t=103488] about it with more detailed information.

"	Petr Vones
17665	An error, log attached	VirtualBox 5.2.6	2018-04-04T14:07:04Z	2018-04-04T14:07:04Z	2018-04-04T14:07:04Z	I debugged guest Windows 10 with WinDbg, and then I got an error which closed the VM and VirtualBox, probably a crash or an internal error. Log attached.	mailnew4ster
19916	Android x_86 ISO have bugs and don't supprt persian hardware keyboards	VirtualBox 6.1.14	2020-09-25T13:47:14Z	2020-09-25T13:47:14Z	2020-09-25T13:47:14Z	"Hi Innotek team,
This is the only way I can reach oy guys. The Android ISO project has some bugs related to language settings. In Android ISO the hardware and software keyboard for persian does not write Persian characters althought the Arabic keyboard does. Instead for writing text with Persian characters it still uses English characters. Please fix this bug in future releases. 
If this email is not relevant please tell me how to notify the related guys about this issue. 
Thanks"	pakanangel
18395	animations and mouse movement flicker [OS/2 guest]	VirtualBox 6.0.4	2019-01-30T21:54:38Z	2019-01-30T21:54:38Z	2019-01-30T21:54:38Z	"On OS/2 guests animations on the desktop flicker. E.g. the mouse pointer is flickering while you move it. Same as the full window drag.

This occurs with and without guest additions, in windows as well as in fullscreen mode.

For testcase I installed Linux Mint on the same maschine and same vbox environement. There the mouse moves very smooth without flickering."	Frank.os2.org
19331	Any guest crashes with Linux 5.5 as host and VBox > 6.0.0	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
16063	"Any immediate ""VBoxManage modifyvm"" commands after detaching a dvd drive fail with 'The machine 'vm_name' is already locked for a session'"	VirtualBox 5.1.6	2016-10-12T12:36:51Z	2017-02-09T11:24:47Z	2017-02-09T11:24:47Z	"=== Issue occurred on: ===
- The tests below were carried out on VirtualBox v5.1.6.
- The issue was also confirmed to be present in v5.1.2 and v5.1.0.
- The issue was not present in v5.0.26.


=== Issue description: ===
* After a VM is powered down, and a SATA dvd drive is detached from it via: ""VBoxManage.exe storageattach"" any immediately following ""VBoxManage.exe modifyvm"" commands fail with a ""The machine 'vm_name' is already locked for a session"" error.
* However, if we insert a delay (sleep) between the calls to ""VBoxManage.exe storageattach"" and ""VBoxManage.exe modifyvm"" then no errors occurr.
* This issue is related to the following forum thread: https://forums.virtualbox.org/viewtopic.php?f=7&t=78830 and the following Packer issue: https://github.com/mitchellh/packer/issues/3744
 
=== Steps to reproduce: ===
* Execute the test1.sh script to reproduce the issue:

==== Script name: test1.sh ====
{{{
#!sh
#!/usr/bin/env bash

echo ""INFO: Creating VM: test1""
./VBoxManage.exe createvm --name ""test1"" --ostype ""RedHat_64"" --register

echo ""INFO: Adding a SATA controller to VM: test1""
./VBoxManage.exe storagectl ""test1"" --name ""SATA Controller"" --add ""sata"" --portcount 1

# test.iso = CentOS-6.7-x86_64-minimal.iso
echo ""INFO: Attaching a DVD drive with a CentOS 6.x ISO to VM: test1""
./VBoxManage.exe storageattach ""test1"" --storagectl ""SATA Controller"" --port 1 --device 0 --type ""dvddrive"" --medium ""./test.iso""

echo ""INFO: Starting VM: test1""
./VBoxManage.exe startvm ""test1"" --type ""gui""

echo ""INFO: Waiting 10 seconds""
sleep 10s

echo ""INFO: Powering off VM: test1""
./VBoxManage.exe controlvm ""test1"" ""poweroff""

echo ""INFO: Detaching the DVD drive from VM: test1""
./VBoxManage.exe storageattach ""test1"" --storagectl ""SATA Controller"" --port 1 --device 0 --medium ""none""

# The following command will fail with the following error:
#  VBoxManage.exe: error: The machine 'test1' is already locked for a session (or being unlocked)
#  VBoxManage.exe: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MachineWrap, interface IMachine, callee IUnknown
#  VBoxManage.exe: error: Context: ""LockMachine(a->session, LockType_Write)"" at line 507 of file VBoxManageModifyVM.cpp
echo ""INFO: Adjusting memory size of VM: test1""
./VBoxManage.exe modifyvm ""test1"" --memory ""2048""
}}}


* Execute the test2.sh script to see that the issue doesn't occurr if a delay is introduced between the last two VBoxManage calls:

==== Script name: test2.sh ====
{{{
#!sh
#!/usr/bin/env bash

echo ""INFO: Creating VM: test2""
./VBoxManage.exe createvm --name ""test2"" --ostype ""RedHat_64"" --register

echo ""INFO: Adding a SATA controller to VM: test2""
./VBoxManage.exe storagectl ""test2"" --name ""SATA Controller"" --add ""sata"" --portcount 1

# test.iso = CentOS-6.7-x86_64-minimal.iso
echo ""INFO: Attaching a DVD drive with a CentOS 6.x ISO to VM: test2""
./VBoxManage.exe storageattach ""test2"" --storagectl ""SATA Controller"" --port 1 --device 0 --type ""dvddrive"" --medium ""./test.iso""

echo ""INFO: Starting VM: test2""
./VBoxManage.exe startvm ""test2"" --type ""gui""

echo ""INFO: Waiting 10 seconds""
sleep 10s

echo ""INFO: Powering off VM: test2""
./VBoxManage.exe controlvm ""test2"" ""poweroff""

echo ""INFO: Detaching the DVD drive from VM: test2""
./VBoxManage.exe storageattach ""test2"" --storagectl ""SATA Controller"" --port 1 --device 0 --medium ""none""

echo ""INFO: Waiting another 10 seconds""
sleep 10s

# The following command will work fine:
echo ""INFO: Adjusting memory size of VM: test2""
./VBoxManage.exe modifyvm ""test2"" --memory ""2048""
}}}

 
=== Actual results: ===

* Output of test1.sh script's execution:

{{{
 $  ./test1.sh
INFO: Creating VM: test1
Virtual machine 'test1' is created and registered.
UUID: 6bf55cf5-a752-49ca-9730-67e791e2fa96
Settings file: 'C:\apps\VirtualBox\Machines\test1\test1.vbox'
INFO: Adding a SATA controller to VM: test1
INFO: Attaching a DVD drive with a CentOS 6.x ISO to VM: test1
INFO: Starting VM: test1
Waiting for VM ""test1"" to power on...
VM ""test1"" has been successfully started.
INFO: Waiting 10 seconds
INFO: Powering off VM: test1
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
INFO: Detaching the DVD drive from VM: test1
INFO: Adjusting memory size of VM: test1
VBoxManage.exe: error: The machine 'test1' is already locked for a session (or being unlocked)
VBoxManage.exe: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MachineWrap, interface IMachine, callee IUnknown
VBoxManage.exe: error: Context: ""LockMachine(a->session, LockType_Write)"" at line 507 of file VBoxManageModifyVM.cpp
}}}


* Output of test2.sh script's execution:

{{{
 $  ./test2.sh
INFO: Creating VM: test2
Virtual machine 'test2' is created and registered.
UUID: 46de8c6c-96ca-4bc3-aee4-76646d092f7a
Settings file: 'C:\apps\VirtualBox\Machines\test2\test2.vbox'
INFO: Adding a SATA controller to VM: test2
INFO: Attaching a DVD drive with a CentOS 6.x ISO to VM: test2
INFO: Starting VM: test2
Waiting for VM ""test2"" to power on...
VM ""test2"" has been successfully started.
INFO: Waiting 10 seconds
INFO: Powering off VM: test2
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
INFO: Detaching the DVD drive from VM: test2
INFO: Waiting another 10 seconds
INFO: Adjusting memory size of VM: test2
}}}

 
=== Expected results: ===
The call to the ""VBoxManage.exe modifyvm"" command should not error if it is called immediately after a call to ""VBoxManage.exe storageattach"".
"	Jinesh Choksi
19976	Any types of VM cannot be started by hardenedwinrespawn	VirtualBox 6.1.14	2020-10-16T19:22:11Z	2020-10-19T21:39:58Z	2020-10-19T21:39:58Z	I was trying to create vms on my machine, I also enabled virtualization through bios, installed hyper-v (Just in case) on windows 10 home and also I did modified the owner of every hardrive to be my user, it seems it has problem with permission but i used administrator mode and gave all the acording permissions.	Valkiria
16363	App using OpenGL asserts in Visual Studio	VirtualBox 5.1.12	2017-01-06T23:00:15Z	2017-02-02T19:19:08Z	2017-02-02T19:19:08Z	"I have an app written in C++ that runs in Visual Studio 2013. This works fine in a Windows 7 VM but when I upgraded to Windows 10 I find it asserts when attempting to use OpenGL. The app works on Windows 10 without a VM. I've tried turning 3D and 2D acceleration off but it makes no difference.

This happens on hosts using MacOS and Linux.
"	tom.isaacson
17565	appcrash virtualbox.dll	VirtualBox 5.2.6	2018-02-26T02:31:28Z	2018-02-28T16:20:18Z	2018-02-28T16:20:18Z	"It is not possible to create a virtual machine, when creating, error occurs.

O.S: windows7 32bit ver:6.1.7601.2.1.0.256.1

  Nombre del evento de problema:	APPCRASH
  Nombre de la aplicación:	VirtualBox.exe
  Versión de la aplicación:	5.2.6.20293
  Marca de tiempo de la aplicación:	5a5cc3df
  Nombre del módulo con errores:	VirtualBox.dll
  Versión del módulo con errores:	5.2.6.20293
  Marca de tiempo del módulo con errores:	5a5cc3f2
  Código de excepción:	c0000005
  Desplazamiento de excepción:	001edcd7
  Versión del sistema operativo:	6.1.7601.2.1.0.256.1
  Id. de configuración regional:	11274
  Información adicional 1:	0a9e
  Información adicional 2:	0a9e372d3b4ad19135b953a78882e789
  Información adicional 3:	0a9e
  Información adicional 4:	0a9e372d3b4ad19135b953a78882e789
"	ndarz
16594	Apple trackpad bluettooth doen't work anymore	VirtualBox 5.1.18	2017-03-22T08:20:12Z	2017-03-22T08:54:13Z	2017-03-22T08:54:13Z	"I have virtual box   Version 5.1.18 r114002 (Qt5.6.2)
Apple OSx 10.12.3 on a macbookpro

My trackpad was working with the previous virtual box... I have downloaded and installed that latest, and the reproductible behavior is now the following :

when lauching VB : everyhthin OK
When starting my virtual machine  ( windows 10), the bluetooth icon in the menu bar is immediately shown broken... And the bluetooth trackpad doesn't work anymore then for the whole macbookpro
The trackpad of the mac itself keeps working
Bluetooth comes back OK in the menu bar  when the Virtual machine is stopped... And the bluetooth trackpad also then !
Then , it is definitely linked to VB...

Thanks to solve it 

jean Christophe"	flyonearth
17880	AppleKeyStore: operation failed (pid: 31 sel: 7 ret: 'e00002c2 ...	VirtualBox 5.2.16	2018-07-21T05:36:25Z	2018-07-28T20:00:19Z	2018-07-28T20:00:19Z	AppleKeyStore: operation failed (pid: 31 sel: 7 ret: 'e00002c2 ...	Moo
15292	"Application Error ""The memory could not be read"""	VirtualBox 5.0.16	2016-04-06T08:42:29Z	2016-09-18T23:05:43Z	2016-09-18T23:05:43Z	"I recently upgraded to 5.0.16 and started to see a crash after some time of actively using a virtual machine. 

I am attaching the log files I found. If there is a way to enable additional log files to be created please let me know. I also enabled the minidumps in Windows but this crash did not seem to generate any sort of dump."	Plazgoth
15252	Application Error - Sudden crash	VirtualBox 5.0.16	2016-03-17T18:28:50Z	2016-03-17T18:28:50Z	2016-03-17T18:28:50Z	"I was using my Ubuntu VM when suddendly VirtualBox crashed with the following Error Message:
- The instruction at 0xdb43b800 referenced memory at 0x00000000. The memory could not be read.

If I try to debug the program, I get the following additional information:
- An unhandled win32 exception occurred in VirtualBox.exe [8948].

Please find attached the logs, although I don't think you will see the crash reason there.

One minute before it crashed, I have detached the SD-Card-Reader. I had a console window open in the Ubuntu guest and the application crashed exactly in the moment where I entered ""exit"" followed by the Enter-Key."	tacarrie
18433	Application Error - The instruction xxx referenced memory at xxx. The memory could not be read.	VirtualBox 6.0.4	2019-02-12T23:38:53Z	2019-02-12T23:38:53Z	2019-02-12T23:38:53Z	"Intermittently, a running Windows guest VM will crash and display the following error. The console window will then close on its own and return you to the VM manager.
Once it occurred during install of Windows 10 1809 and once after install and installing programs. I have rebooted the host in between the two occurrences.
Afterwards the VM is left in an Aborted state.
This has only appearing since installing VirtualBox 6.x, it has not occured before on v5.x.
The host is running Windows 10 1809 x64."	rjcuk
14387	Application Error when Plugging/Unplugging HDMI for second display	VirtualBox 5.0.0	2015-08-04T13:10:09Z	2015-08-04T13:10:09Z	2015-08-04T13:10:09Z	"When unplugging/plugging in HDMI cable for second display on my laptop, I receive dialog ""VirtualBox.exe - Application Error"", ""The instruction at 0x80165d4a referenced memory at 0x00000018.  The memory could not be read.""

I am running a Windows 8.1 host, with Ubuntu 14.04 as the guest."	cmo
17134	Arch Linux - kernel 4.13 video problems	VirtualBox 5.1.28	2017-10-04T01:41:27Z	2017-10-04T01:41:27Z	2017-10-04T01:41:27Z	"As you know, starting from 4.13 kernel graphics driver for VirtualBox started to being shipped in the kernel, and now it fails to configure resolution/etc properly, when starts it. See attached image 

Host Linux - Fedora 26 with latest updates
Guest Linux - Arch Linux with latest updates 

Exact version of VirtualBox is 5.1.28.r117968
"	akochkov
13055	archive/save metric data	VirtualBox 4.3.12	2014-05-22T11:09:25Z	2014-05-22T11:09:25Z	2014-05-22T11:09:25Z	"Requesting the ability to '''store / archive''' metrics.

Besides setting up a metric, for purposes of long-term data analysis, I will have to rely on a 3rd party tool (such as pnp4nagios) to keep track of resource requirement changes for VM over time.

It would be beneficial to have an local data collection / data archive of the collected metrics that can be directly queried.


"	Senthil Nathan
16440	As a guest, must hold keyboard key a second or more	VirtualBox 5.1.14	2017-02-01T20:49:13Z	2017-02-24T20:12:44Z	2017-02-24T20:12:44Z	"Previously used Control Panel to uninstall VBox 5.0.4 (was installed through MyDesktop)

Uninstalled VBox 5.1.14 which I'm having keyboard issues with (must hold keys for them to be recognized)

Re-downloaded VirtualBox-5.1.14-112924-Win.exe

Installed VBox 5.1.14, used all defaults

Used Start to bring up Oracle VM VirtualBox

Within VBox Manager, clicked on Start (Oracle Linux Server 6.6), replied with password to ""jhoelsch4.dev"" login.  Information had apparently been retained from a previous install of VBox.  So, looks like there are bits of configuration detail, probably retained in the registry.

Three windows are generated:
- Development [Running] - Oracle VM VirtualBox : 1
- Development [Running] - Oracle VM VirtualBox : 2  (contains icons Computer, jhoelsch's Home, Trash, sf_AutoImage, VBOXADDITIONS_5  1.13_112924)
- Development [Running] - Oracle VM VirtualBox : 3 (identical to window 1 above)
When password was entered in window 1, the same keystrokes were echoed in window 3.

Right-click on jhoelsch's Terminal -> Open In Terminal.  This is where keys must be held extra long to be recognized

Notes: 
sf_AutoImage is residual from a shared folder from a prior VBox install.
"	John Hoelscher
15039	Assertion failed, Please contact the product vendor!	VirtualBox 5.0.10	2016-01-17T09:15:08Z	2016-01-18T09:20:19Z	2016-01-18T09:20:19Z	"I got the message below.

Additional info: It occurred after I was trying to delete some snapshots and got various error messages like access denied and invalid object state. I do not know if these errors were related. This time also my harddisk was getting full and eventually the machine refused even to show up in the VirtualBox window.

Just for additinal note, the snapshot delete functionality currently quite often fails, even when disk has enough room. The failures look random - same snapshot always fails, but which ones will fail and which ones will not for same virtual machine, is not predictable.

{{{
Assertion failed: [m->state == MediumState_LockedRead] at 'F:\tinderbox\win-5.0\src\VBox\Main\src-server\MediumImpl.cpp' (4411) in long __cdecl Medium::i_createDiffStorage(class ComObjPtr<class Medium> &,enum __MIDL___MIDL_itf_VirtualBox_0000_0000_0074,class MediumLockList *,class ComObjPtr<class Progress> *,bool).
Please contact the product vendor!.


Result Code: 
E_FAIL (0x80004005)
Component: 
MediumWrap
Interface: 
IMedium {4afe423b-43e0-e9d0-82e8-ceb307940dda}
}}}"	levitation
19576	AssertLogRel F:\tinderbox\win-rel\src\VBox\Runtime\win\RTErrConvertFromWin32.cpp(448) int __cdecl RTErrConvertFromWin32(unsigned int): <NULL>  Unhandled error 1453	VirtualBox 6.1.4	2020-05-11T00:36:11Z	2020-05-11T00:36:11Z	2020-05-11T00:36:11Z	"VirtualBox 6.1.4 under host windows10, running linux guest crashed due to an assertion failure.
Unhandled error 1453.

VirtualBox was running while I was tinkering with the programs on the Windows 10 site when suddenly the PC froze [I think Windows 10 was executing binary dump of the virtualbox image for debugging.] then about a minute or so later, I got an error dialog about memory reference error or something, but I failed to capture the screen, but rely on the log file(s) instead."	ci-zephyurus
15746	At times when virtualizing a windows OS explorer not updating view	VirtualBox 5.1.2	2016-08-04T14:17:36Z	2016-08-10T09:31:05Z	2016-08-10T09:31:05Z	"There are times when I go into explorer and do basic file operations:
1. Creating a folder
2. Renaming a folder
3. Copying files

Afterwards it requires a manual refresh or navigation back to the same file location for the changes to visible.

This has happened only twice now, the same image reloaded is not demonstrating the same problems."	FalconRecall
15853	audio and video out of sync on Ubuntu 16.04.1	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
18240	audio clips are truncated at the end	VirtualBox 5.2.20	2018-12-27T18:28:14Z	2019-02-08T11:01:38Z	2019-02-08T11:01:38Z	"VirtualBox [v5.2.20 and 5.2.22] stops playing audio clips before they finish.

I had this issue somewhere back around ???[v5.1.26/27]???, but is was corrected shortly there after.

The issue has now resurfaced since v5.2.18.

I was keeping up with updates, but was not using the audio applications.

I downgraded to v5.2.18 and plan on staying {safe} with v5.2.18 just because I know the audio is still working correctly.

Just FYI, Tracey

If anyone cares, maybe the archived versions (5.2.20 and 5.2.22) should be fixed as well."	Tracey
17514	Audio stops working on Windows 7 guest	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
19927	"Audio: garbled and hanging audio is caused by a ""bug"" in VirtualBox 5.x and up"	VirtualBox 6.1.14	2020-09-29T03:58:05Z	2020-10-04T01:29:11Z	2020-10-04T01:29:11Z	"Tested in Reactos

source :  https://github.com/reactos/reactos/pull/3141

https://github.com/reactos/reactos/files/5210800/ac97-crash-reactos-msvc.log

"	Blackcrack
10175	auto mount shared folders immediately and not just after reboot	VirtualBox 4.1.8	2012-01-16T21:27:12Z	2012-01-16T21:27:12Z	2012-01-16T21:27:12Z	"When creating a shared folder and setting auto mount it will be mounted after reboot.
It will be helpful if the folder will be mounted immediately without requiring a reboot as well.

Tested on ubuntu 11.10 guest under win7 host.

Thanks"	pablop
15997	Auto-resize Guest Display greyed out	VirtualBox 5.1.6	2016-09-28T11:25:31Z	2016-09-28T11:25:31Z	2016-09-28T11:25:31Z	"I have installed VirtualBox 5.1.6 on a Windows 10 Pro Host. The Guest System is Windows 7 Ultimate. GuestAdditions installed.

Mouse integration and Drag and Drop works fine but Auto-resize Guest Display is greyed out.

Tentatively I have installed the Guest Additions Testbuild.


Stefan"	StefanPreuss
15310	Auto-resize Guest Display not working	VirtualBox 5.0.16	2016-04-14T19:26:21Z	2016-04-14T19:26:21Z	2016-04-14T19:26:21Z	"Host: Mac OS 10.10.5 Macbook Pro retina 15 inch with an external auria EQ276W 27"" monitor
Guest: Debian Jessie
Guest using two displays

I have auto-resize guest display enabled

In full screen mode with the primary screen on the Auria and the secondary screen on the macbook it works fine with both.
If you unplug the DP while in full screen mode it still work fine.
However if you exit full screen mode with the two screens on the macbook (external monitor still unplugged), the window for the primary display has a scroll bar on the right and bottom (ei it doesn't resize).
Also if you go back into full screen mode the primary screen no longer fits on the macbook.

Let me know if you need any additional information.

"	ranamala
14098	Automated kernel modules recompilation	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
20868	Automated login not working on Arch Linux guest of a Windows host	VirtualBox 6.1.32	2022-03-14T16:14:42Z	2022-03-14T16:14:42Z	2022-03-14T16:14:42Z	"I followed instructions in https://www.virtualbox.org/manual/ch09.html#autologon
to be able to login automatically on my Arch Linux host under a Windows 10 host, providing credentials as explained for Windows guests (not described for Linux guests), which shows in syslog on the Linux guest as ...
{{{
pam_vbox_setcred called, iFlags=0x4
pam_vbox_setcred: argv[0] = debug
}}}
but pam_vbox is unable to subsequently retrieve the credentials leaving the following error in syslog:
{{{
pam_vbox: 6.1.32r149290, running on amd64
pam_vbox_init: runtime initialized
pam_vbox_init: guest lib initialized
pam_vbox_init: rhost=<none>, tty=:0, prompt=<none>
her	dbus-daemon[2156]: Successfully activated service 'org.a11y.atspi.Registry'
her	SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
pam_vbox_read_prop: read key ""/VirtualBox/GuestAdd/PAM/CredsWait""=""1""
pam_vbox_read_prop: read key ""/VirtualBox/GuestAdd/PAM/CredsWait"" with rc=VINF_SUCCESS
pam_vbox_read_prop: read key ""/VirtualBox/GuestAdd/PAM/CredsWaitTimeout"" with rc=VERR_NOT_FOUND
pam_vbox_read_prop: read key ""/VirtualBox/GuestAdd/PAM/CredsMsgWaiting"" with rc=VERR_NOT_FOUND
Showing message ""Waiting for credentials ..."" (type 4)
pam_vbox_check_creds: could not query for credentials! rc=VERR_PERMISSION_DENIED. Aborting
pam_vbox_authenticate: overall result rc=VERR_PERMISSION_DENIED
}}}
"	MAnantharaman
10852	Automatic integer-factor scaling under full-screen mode	VirtualBox 4.1.20	2012-08-22T12:05:53Z	2015-05-16T12:18:02Z	2015-05-16T12:18:02Z	"Replying to [ticket:5596 DrD]:
> When running games such as starcraft (and very likely any game set to a lower resolution then the screen's potential), virtualbox fails to scale the image up to fullscreen in full screen mode. Game (or application at hand) remains in a smaller window (at it's running resolution) without scaling up to full screen as it should in these situations. The remaining space is occupied by black borders surrounding said application.

It is to be remembered, though, that the best scaling method is ''integer-factor'' scaling -- in other words, through the mapping of individual pixels to larger (2x2, 3x3, 4x4, and so forth) blocks of like-value pixels.

Such an automatic ""zoom-in magnifying,"" if it may be put that way, while under full-screen mode would continue to feature black bordering, although a much-larger area of the screen would be put to good use.

It has to be noted, though, that this is already achievable through reducing host resolution, for example from 1920x1080 to 960x540, although it could be argued such a method is not ''that'' suited for long-term purposes.

Underlying mechanisms (although mileages may vary) of the implementation would be for a check, triggered by definite conditions, to be performed in order to determine whether native width and height in pixels is great enough for integer-factor scaling to take place, then for the largest suitable scaling to be performed.

Such an implementation would be adapted both to text-mode cases (for example, full-screen Windows-XP command consoles, and various DOS guests), and to classic-video-game cases (StarCraft is to be restated) -- such code would indeed operate great for lots of past games, in which output resolution is of 640x480, and for which double-scaling would be a viable solution, that is, in relation to current-generation modern monitors.
"	twipley
16232	Automatic Screen Resizing doesn't work anymore	VirtualBox 5.1.10	2016-11-25T19:39:06Z	2016-11-25T20:04:11Z	2016-11-25T20:04:11Z	"Mac Os host and Windows 8.1 Guest.

"	FlavioMattosRj
21097	Automatic update of VBox and Failed to open a session for the virtual machine Ubuntu => fixed in SVNsvn	VirtualBox 6.1.38	2022-09-05T12:04:39Z	2022-11-29T03:04:01Z	2022-11-29T03:04:01Z	"Few weeks ago, when I had updated VirtualBox, I had faced an error with opening a session for the virtual machine (guest OS is Ubuntu).
Found a suggestion that VBox version 6.1.32 is good and I had downgraded the VBox and everything works fine, I can start a session for the VM.
I had turned off the automatic update of VirtualBox, but few times since then, VirtualBox was updated automatically to the newest version.

For some, unknown to me reason, I can't use the newest VBox version, but my VBox keep upgrading even when automatic update is turned off.
What is the solution? Should I downgrade my VBox every day?"	AZidai
19670	"Automatic VM name-based configuration assumes ""32"" means ""32-bit"""	VirtualBox 6.1.10	2020-06-17T13:45:31Z	2020-06-23T11:42:20Z	2020-06-23T11:42:20Z	"Fedora 32 is not 32-bit Fedora

I attempted to set up a VM today for version 32 of Fedora x64. When I tried to create a VM named ""Fedora 32"" the creation tool assumed I meant 32-bit Fedora. This lead to several minutes of confusion as I tried to figure out why booting up the Fedora Workstation 32 x64 ISO kept telling me it couldn't run on a 32-bit processor.

I eventually figured out what had happened, and tried to manually change the VM's CPU from 32-bit to x64. However, the ISO still kept insisting that I had a 32-bit processor. Eventually, I had to destroy the VM and create one from scratch.

Not completely sure this is actually a bug, but the algorithm could be fine-tuned to work better, or perhaps provide more noticeable feedback when it changes the ""bit-ness"" of the VM."	imrazor
11885	Automatically detect SSD status of a virtual disk	VirtualBox 4.2.12	2013-06-21T10:56:50Z	2013-06-21T10:56:50Z	2013-06-21T10:56:50Z	"It would be nice if VirtualBox could automatically detect if the SSD option should be enabled for a virtual disk based on the state of the physical disk on which it is stored, as reported by the host OS.

Obviously this can't always be done, if the host disk is actually part of some elaborate volume management scheme, etc., but it would be nice to have it work for simple cases. :)"	Sam Morris
16525	Automatically switching to Seamless mode on start does not use full screen area	VirtualBox 5.1.14	2017-03-02T13:15:31Z	2017-03-02T13:15:31Z	2017-03-02T13:15:31Z	If my Arch Linux x64 guest (on Win10 x64 host) is closed with seamless mode running, when I restart the guest there's a popup saying to switch back to seamless mode. If I click okay, seamless mode starts but there's a gap at the top from the vbox guest OS menu. I have to ctrl+L and ctrl+L again to get it to recognize the actual display size.	R
18683	Automount of Shared folder stopped working in 6.0.8	VirtualBox 6.0.8	2019-05-30T15:13:56Z	2019-05-31T07:52:40Z	2019-05-31T07:52:40Z	SuSE Linux host, Microsoft Windows 10 guest.  After update of VB to 6.0.8 I can no longer access my Shared Folder residing on the host. Was working previously. If I try to mount it manually in Windows, I can access the server, but there are no shares listed.  I can access Samba shares on other machines.	Don Hughes
950	Autostart a vm on startup	VirtualBox 1.5.2	2007-12-06T23:32:43Z	2013-01-09T12:02:50Z	2013-01-09T12:02:50Z	"Hi there,

it would be a nice option, if you could add the possibility to start a vbox automaticly after startup.

"	tobias
17885	AVAST Internet Security reports threats when I start any machine under VB	VirtualBox 5.2.16	2018-07-23T08:45:28Z	2018-07-23T13:07:15Z	2018-07-23T13:07:15Z	"Hi! I've been using VBox since Jan 2014. Since last year I keep getting Threats Blocked messages by my AVAST Internet Security. Threats messages read:
""We’ve safely blocked connection on Sportgoods.co.in because infected with URL:Mal.
 We’ve safely blocked connection on Spmpart.com because infected with URL:Mal.
We’ve safely blocked connection on Tektasarim.com because infected with URL:Mal.
""
This threat is quite annoying. And always shows that Virtual Box is trying to contact the above 3 sites!?!
I'm running Virtual box under Windows-10, fully updated. The guest system runs Windows XP. "	VBFan2018
17068	AVG installation locks up Virtual Box version 5.1.26	VirtualBox 5.1.26	2017-09-09T09:16:05Z	2017-09-18T21:22:24Z	2017-09-18T21:22:24Z	"AVG installation locks up Virtual Box version 5.1.26

Please reply with suggestions to fix problem.

Thanks, Danny."	Bubba
19587	Awful Linux Guest Performance	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
20122	Ayuda para mac	VirtualBox 6.1.16	2021-01-10T16:20:08Z	2021-01-10T16:22:16Z	2021-01-10T16:22:16Z	"Hola no se Ingles solo Español.  Tengo Mac mini e instale big sur porque tenia una falla que cada tanto se reseteaba sola la mac con el sistema operativo anterior de mac.  ahora no me funciona virtualbox, lo re instale y nada.  veo que es muy compleja las soluciones y no quiero perder la informacion que tengo guardada en la particion windows, un arbol genealogico de 165000 personas. Tks

The virtual machine 'Sergio' has terminated unexpectedly during startup with exit code 1 (0x1).


Código resultado: 
NS_ERROR_FAILURE (0x80004005)
Componente: 
MachineWrap
Interfaz: 
IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}


Kernel driver not installed (rc=-1908)

Make sure the kernel module has been loaded successfully.

where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT. "	Perinola
14399	Background VMs are halted when Host is shuting down	VirtualBox 5.0.0	2015-08-05T20:30:19Z	2015-08-05T20:30:19Z	2015-08-05T20:30:19Z	"I see the great feature in VirtualBox 5!!! Its posibility to run virtual machines in background. Its very cool and must have feature.
But!! When i shutdown my windows host machine it halts all background virtual machines. It is not funny. Why halt it? It is better to susspend it by default. Isn't it?

So great tool. Great new features. But fix this ""little bug"" please."	artkor
19028	Bad 3D display in Virtualbox 6.0.14	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
19032	bad display of IE	VirtualBox 6.0.14	2019-10-20T02:00:40Z	2019-10-21T06:22:20Z	2019-10-21T06:22:20Z	"IE windows cannot be display well, especially, the on the top of the IE window. Like url box or tool bar, always in a black block can't see anything.
IE:
google chrome
ms iexplorer"	taurus
19353	Bad installiation on Windows XP 32 bits.	VirtualBox 5.2.38	2020-02-27T08:03:11Z	2020-02-27T08:04:22Z	2020-02-27T08:04:22Z	Hello. I had the installed version of Virtualbox 5.2.36 r135684. I tried installing update 5.2.38. It did not install, the program did not reach the end of the installation process. I don’t know if there were driver updates. Just in case, I inform you that there were no dialog boxes offering to install drivers. I saw only the green line of the installation indicator for a long time (more than an hour) and the button to stop the installation.	hellodearfriends
11105	Better support for clustered environments	VirtualBox 4.2.2	2012-10-22T12:49:50Z	2012-10-22T12:56:50Z	2012-10-22T12:56:50Z	"We would like to see better support for clustered environments.

We run a cluster environment using VirtualBox and glusterFS. All VM's and their virtual disks are stored on mirrored glusterFS volumes via storage nodes (dedicated storage servers). We have several compute nodes (Linux x64 host servers) running the the guest VM's. All compute nodes share the same VirtualBox.xml (stored on a mirrored glusterFS volume) so that any guest VM can be serviced by any compute node. We use phpVirtualBox to manage our VM cluster.

This cluster configuration presents several problems:

1) Updates to guest VMs (i.e. to VirtualBox.xml via vboxmanage) on any server in the cluster is never propogated to the other servers in the cluster unless a complete restart occurrs;

2) Compute node B (or C, D, E, etc) does not know that Compute Node A is currently servicing (running) guest VM '1234'.

Proposed Enhancments:

1) A new file called '{compute node}.state.xml' (or any other name).

This file is created in the guest VM's home VirtualBox folder and updated to reflect the current state of the guest VM. The '{compute name}' is used in the filename to designate which compute node (host server) the state file is for. This file is updated accordingly by the compute node to provide read-only information via vboxmanage and web services.

VirtualBox.xml is modified to better separate configuration information versus 'current running state' information so that the 'current running state' information is by compute node. This will allow for 'teleporation' within a cluster. You cannot use teleportation in a cluster sharing the same VirtualBox.xml.

2) Updates to VirtualBox.xml are propogated to other compute nodes sharing the same VirtualBox.xml.

Perhaps add a new vboxmanag command called ""refresh config"". This command will cause VirtualBox to re-scan the VirtualBox.xml and update it's memory configuration.
This command should also be available in web services.
"	Van Stokes Jr
21002	Better synchronisation between VboxManage CLI and GUI	VirtualBox 6.1.32	2022-06-22T08:31:35Z	2022-06-22T08:31:35Z	2022-06-22T08:31:35Z	"I'd like to use the GUI and CLI simultaneously. However,
VMs created with the CLI sometimes appear as inaccessible in the GUI. And after using the GUI, some VMs appear as inaccessible in

vboxmanage list vms

A better synchronisation would certainly be helpful. "	paaguti-u
9706	Big minimizing machine in Full Screen dual monitor mode	VirtualBox 4.1.4	2011-10-06T19:28:34Z	2011-10-06T19:28:34Z	2011-10-06T19:28:34Z	"I'm running Windows 7 Professional 64 bit as the host and Ubuntu 11.04 as the guest.

The dual monitor mode works much better in this release than in the previous release (the previous release frequently locked-up or froze when running Ubuntu 11.04).   However, there is still one more kink to work out.

When in full screen mode running dual monitors, if I click the minimize button on the VM tab with the VirtualBox controls for the machine, it only minimizes the primary monitor window and leaves the secondary monitor window maximized.  This should be fixed since the auto-resize feature in dual monitor mode in running an Ubuntu guest OS is still a little fragile.  Both windows should minimize when clicking the minimize button from the VirtualBox menu bar."	josiah
16346	BIOS date in orgs.asm is always 06/23/99	VirtualBox 5.1.12	2017-01-02T01:54:52Z	2017-01-02T01:54:52Z	2017-01-02T01:54:52Z	"https://www.virtualbox.org/svn/vbox/trunk/src/VBox/Devices/PC/BIOS/orgs.asm

Notice BIOS_BUILD_DATE is always 06/23/99. I think Win2000 and Win98 often uses this to determine the BIOS date. For example the BIOS date for enabling ACPI in Win2000 is 01/01/99 and in Win98SE is 12/01/99."	Yuhong Bao
2935	BIOS support for booting from usb devices	VirtualBox 3.1.6	2009-01-01T18:33:25Z	2019-01-02T05:25:17Z	2019-01-02T05:25:17Z	"Currently Boot Order has CD/DVD-ROM, Floppy, HDD, Network as options.

It would be nice if boot from USB is also available as an option.

Thanks."	Dhamodharan.P
21490	Bitnami OVA Aborts on M2 Mac Mini Using Virtualbox Developer preview for macOS / Arm64 (M1/M2) hosts	VirtualBox-7.0.6	2023-02-10T16:12:54Z	2023-02-13T20:50:05Z	2023-02-13T20:50:05Z	"Using an M1 Mac Mini 2020, I found the new VirtualBox-7.0.6_BETA4-155176-macOSArm64 download at VirtualBox.org. This is the Developer preview for macOS / Arm64 (M1/M2) hosts.

VirtualBox installs fine and opens as usual.

I imported the Bitnami VM OVA for ResourceSpace bitnami-resourcespace-10.0.0-31-r29-linux-vm-debian-11-x86_64-nami.ova

No apparent problem with importing.

When I click Start, the VM starts the Linux boot, gives a little bit of progress: GRUB Booting Debian GNU/LInux and then the boot sequence aborts and VirtualBox displays Aborted for the status of the VM.

Any ideas what might be happening? Do Bitnami VMs work with the Developer version of VirtualBox for M1 and M2 Mac Minis?

The same problem occurs on an M2 Mac Mini Pro new out of the Box (2023).
"	Kyosho at ZMM
9306	Black screen after finishing an application run in full screen in DOS prompt	VirtualBox 4.1.0	2011-07-25T20:58:26Z	2011-07-25T20:58:26Z	2011-07-25T20:58:26Z	"Hello,

I have an issue with Windows XP (32bits) running as a guest in a Mac osx Lion host. 

When I run an application in the DOS prompt and it goes into a full screen mode, I have no way to restore the window view and manage the desktop; when doing that with ALT+ENTRER of by typing ""exit"" I got an entire black screen and I have to force the close of the virtual machine.

I am experiencing this issue after upgrading to the latest version of Mac OSX (Lion). This issue was not experienced with Snow Leopard.

I attach the last log associated with the issue described.

Thank you."	edu
19535	Black screen after logon	VirtualBox 6.1.6	2020-04-26T13:17:53Z	2022-05-05T23:43:18Z	2022-05-05T23:43:18Z	"I'm trying to work on Oracle DB Developer VM, but it simply goes into black screen after the logon. I have checked all the requirements for this VM and verified if some settings are well, but I couldn't find anything wrong.
I have attached the log file and a screen.

Any advice or suggestion would be very helpful.

Thanks and have a nice day!"	george2123
19996	Black Screen of Death	VirtualBox 6.1.16	2020-10-24T18:59:43Z	2020-10-24T18:59:43Z	2020-10-24T18:59:43Z	"I'm trying to get virtualbox running on a windows 10 pro (2004) machine and create a linuxmint vm.  When I start the VM I get the linux screen that says ""start linux"" and then after 10 seconds the screen goes black.  I have disabled hyper-v, i have unchecked 3d acceleration.  I was able to get VMWARE to work but not having any luck with virtualbox.  I've attached the log file"	rsail
15154	Black screen when connecting to a Windows 2012 server from Windows 10 on VirtualBox	VirtualBox 5.0.14	2016-02-17T19:36:38Z	2016-02-22T10:14:55Z	2016-02-22T10:14:55Z	After upgrading my Windows 10 guest to version 10.0.10586 I get a black screen when connecting to a Windows 2012 server with Remote Desktop. I can connect to older versions of Windows Server without problems. I doesn't matter if I disable bitmap caching on the connection or not.	jespers
18486	Black screen when trying to use Kali Linux	VirtualBox 6.0.4	2019-03-10T16:01:31Z	2019-03-14T09:30:58Z	2019-03-14T09:30:58Z	A Black Screen appears after I click the install button in Kali Linux first menu. I  cannot use it as a live system neither.	Rafael1548
16948	Blank Screen (crash?) on update V5.1.22 -> V5.1.24	VirtualBox 5.1.24	2017-07-26T17:45:25Z	2017-08-03T15:47:01Z	2017-08-03T15:47:01Z	"A few minutes after I updated to V5.1.24 my computer screen suddenly went black.   Ctrl-Alt-Delete did not bring up the Windows 10 blue options screen.  I couldn't get it to respond in any way.  Maybe crashed but without seeing anything I couldn't verify that.  Had to power off.   Tried again and same thing happened within about 10 min.  Had to roll back to V5.1.22.

In the change log I noticed ""GUI: prevent stopped screen updates or black screen on reboot in a multi-screen setup under certain conditions""

FYI: I do have two video cards in this computer.  One on the mother board (not used) and a NVIDIA NVS 315

"	isgdre
18517	"blocage VM WIN7/32bits quand utilisation ""partage"""	VirtualBox 6.0.4	2019-03-23T07:34:32Z	2019-03-23T07:34:32Z	2019-03-23T07:34:32Z	"J'utilise, historiquement, une machine virtuelle WINDOW7 en 32bits.
Depuis le passage en version 6.0.4, l'utilisation des ""Dossiers partagés"", bloque WIN7 définitivement.
J'ai du revenir en version 5.2.26 !!!


I use, historically, a WINDOW7 virtual machine in 32 bits.
Since version 6.0.4, the use of ""Shared Folders"" is blocking WIN7 permanently.
I had to return to version 5.2.26!"	glinux13122
17578	Blue screen after upgrading to 5.2.6 version	VirtualBox 5.2.6	2018-03-01T01:54:57Z	2018-03-01T01:54:57Z	2018-03-01T01:54:57Z	"5.1.30 version of the work is normal, upgrade to 5.2.6 version of the virtual machine and the host has a blue screen phenomenon.
The following is the host debugging information.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {61948, 2332810, 1, 2332810}

Probably caused by : memory_corruption ( nt!MiDereferenceIoPages+ccea8 )

Followup:     MachineOwner
---------

nt!KeBugCheckEx:
fffff802`1ad85430 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffe68b`5f1bf1b0=000000000000001a"	Minghao
9769	Blue screen during install of Windows XP with slipstreamed SATA driver	VirtualBox 4.1.4	2011-10-16T23:37:35Z	2013-01-03T09:02:02Z	2013-01-03T09:02:02Z	"I don't think this was ever fixed, yet the old ticket is closed: 2282
[https://www.virtualbox.org/ticket/2282]

Attempt to install Windows XP Pro SP3 slip-streamed with Intel Storage Matrix version 7.0.0.1020 to 10.6.0.1002, results in blue screen of death at ""device installation stage"" of XP installation. 

That is, XP uses driver to detect corresponding hard disk and copies installation files, but during device installation stage of XP, the user is confronted with BSOD.  If the user attempts to resume installation after a cold boot, installation is successful.  That error should never occur in the first place and seemingly was never fixed; tested virtualbox 4.1.4 and virtualbox 4.0.12, both fail.

Note, to reproduce this error, Vista must be selected as OS within virtualbox so that the default controller is Sata and not IDE.  You must be thinking, ""you selected vista of course it failed.""  I selected Vista to get the sata controller.  I believe this should be fixed.  What's more believable that every version of Intel Storage Matrix AHCI driver is plagued by BSOD therefore that Intel doesn't know how to write drivers or that VirtualBox is at fault?  "	ericore
21354	"Blue Screen when I run any virtual machine in ""Normal Start"""	VirtualBox-7.0.4	2022-12-28T08:52:10Z	2022-12-29T10:05:47Z	2022-12-29T10:05:47Z	"I run Virtual Box(7.0.4r154605) on Winddows 8.1
When I run any my virtual machine in mode ""Normal Start"" a got Blue Screen(BSoD). But when i run in ""Headless Start"" or ""Detachable Start"" it's ok
"	SergeyNZ
17153	Blue screen when starting Windows 7	VirtualBox 5.1.28	2017-10-10T11:57:32Z	2017-10-10T17:02:52Z	2017-10-10T17:02:52Z	"Blue screen when starting Windows 7. After 4 or 5 restarts ok. 
When shutting down a report of a serious error appears. Contact support."	stback
18787	Blue screen when try to launch WinSCP-5.15.3.	VirtualBox 6.0.10	2019-07-24T17:08:00Z	2019-08-17T04:52:53Z	2019-08-17T04:52:53Z	"Guest machine Windows 7 - Win 6.1 (Build 7601 SP 1)

Host machine Windows 10 Ver 1809 (OS Build 17763.615)

Virtual Box - VirtualBox Graphical User Interface, Version 6.0.10 r132072 (Qt5.6.2)

Guest machine fall with Blue screen when try to launch WinSCP-5.15.3. (WinSCP.exe)

Downloaded from here 
https://winscp.net/download/WinSCP-5.15.3-Portable.zip"	dimabol
15123	Bluescreen when starting Beckhoff TwinCAT PLC with activated VT-x	VirtualBox 5.0.14	2016-02-07T20:58:29Z	2016-06-18T13:39:06Z	2016-06-18T13:39:06Z	"With the VBox Version 5.0.10 and 5.0.14 the Windows 7 crashes with a bluescreen when the Beckhoff TwinCAT PLC 3.1 is started.
This happens on a 32 Bit Windows as Long as the VT-x Support is activated and allways on a 64 Bit Windows, because the VT-x Support coulkdn't be swithed off.
With VBox 5.0.4 the System doesn't Crash."	OTonn
16303	Bluetooth disconnect when starting W10 64bit on OS X host	VirtualBox 5.1.10	2016-12-17T22:06:03Z	2016-12-21T18:52:37Z	2016-12-21T18:52:37Z	"
Re: Bluetooth disconnect when starting W10 64bit on OS X host
Postby rcatyvr » 17. Dec 2016, 23:45

Problem hunted down and solved for now:

Latest VirtualBox on El Capitan Mac, latest Window 10 from upgrade on 64 bit VM. 

Starting the VM caused my host Mac's Bluetooth services to stop and refuse to connect to my keyboard and trackpad and from operating inside/outside of, or after closing the VBox application. It is a BIG problem as the only way to close the VM  and restart my host's Bluetooth was to power off then reboot the computer which is an annoying waste of time and can break the HFS+ file system.

Fortunately, I found a wireless Logitech keyboard & mouse handy so I plugged the dongle into my USB hub and was able to continue to troubleshoot without having to crash the system repeatedly just to close the VM

Solution/Work around:

You will need to have at least a wireless or hard wired USB mouse plugged in. Especially if you are using a Mac, be sure that before the Windows VM actually starts to boot that you prevent it from going full screen and you lose the ability to click on the Apple control icon at the top left of the host's screen to do a controlled reboot. If you don't you will probably have to power the unit off the hard way. Note: a similar keyboard setup would help, but is not essential as both in the VM and the host, a functioning mouse can get you through to solution. 

1. Confirmed that I had replicable problem--repeatedly from cold start to full power-off crash.
2. Used an archived Win 10 VDI dated September 22, 2016 to confirm the problem originates in fact in Windows, not VBox--no problems seen
3. Went back to the most up-to-date Windows 10 VDI: Services control, I stopped & disabled: a) Bluetooth Handsfree Service, b) Bluetooth Support Service.
4. REBOOTed the Windows VM
5. Tested and had no further interference with the host's Bluetooth hardware.

Problem solved. I would call this a solution, though it is technically a work around, because disabling Windows' bluetooth should be moot. The host shouldn't be able to pass those services to the VM and therefore there is no need for them to even be there/on. However, that as by default they try to start up (and revert to a manual-start service) at boot time, and as it seems that just querying for the hardware is enough to crash the host's own hardware, those services should be disabled.

I don't know how it does it, but have I found out experimentally that in a VBox VM, Windows 10's bluetooth services/hardware layer have been recently changed and are now somehow attempting to control/attach to the host's Bluetooth stack during the client's boot up--causing them to crash and the host loose its hardware bluetooth service. Not supposed to happen, but it does. 

A long term solution would be for Oracle to figure how the Win10 VM is trying to access the hosts' hardware and crash it, and prevent it from doing so."	rcatyvr
20172	boot issues	VirtualBox 6.1.18	2021-02-07T09:04:30Z	2021-02-07T09:04:30Z	2021-02-07T09:04:30Z	unable to start the device. i tried the newest version of Virtual box, then i was instructed by tech support ofgenymotion to try an older version. i tried two older versions and it still doesnt work. i went through all the stepps offered by genymotion and couldnt run the device	sam10
19238	Boot time for linux guest is about 50% slower on 6.1.2  compared to 5.2.34	VirtualBox 6.1.2	2020-01-16T19:53:21Z	2020-01-20T18:33:01Z	2020-01-20T18:33:01Z	"Host : Windows 10 1903 (10.0.18362.535)

I have been using linux mint 19.2 installed on Virtualbox 5.2.34 for a while.
I just recently upgraded virtualbox to the latest version 6.1.2.

The boot time on 5.2.34 is in average : 1.26  (1 minute and 26 seconds )
The boot time on 6.1.2  is in average : 2.13  (2 minutes and 13 seconds )"	DanMc01
16685	Booting error (VINF_EM_DBG_HYPER_ASSERTION / raw mode)	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
15212	BoxManage showvminfo --machinereadable vcpfile property value is not properly escaped	VirtualBox 5.0.14	2016-03-06T20:42:23Z	2016-03-06T20:42:23Z	2016-03-06T20:42:23Z	"I was trying to see how properly `VBoxManage` escaped the output of `BoxManage showvminfo --machinereadable` and I found out that it does not properly escape the `vcpfile` property value:

{{{
vcpfile=""/home/rgl/VirtualBox VMs/Windows ""/Windows "".webm""
}}}

As a comparison, these are properly escaped:

{{{
name=""Windows \""""
CfgFile=""/home/rgl/VirtualBox VMs/Windows \""/Windows \"".vbox""
SnapFldr=""/home/rgl/VirtualBox VMs/Windows \""/Snapshots""
LogFldr=""/home/rgl/VirtualBox VMs/Windows \""/Logs""
}}}"	ruigodlopes
14241	Brackets in group name of VirtualBox Manager causes erratic behavior.	VirtualBox 4.3.12	2015-07-04T19:44:06Z	2015-07-04T19:44:06Z	2015-07-04T19:44:06Z	"This is to report that including brackets ""("" and "")"" in group names causes erratic behavior; 

When creating groups named ""Base Machines (Stage 0)"" or ""Base Machines (Stage 1)"" cause the groups to show up collapsed and moved to the bottom when the VirtualBox Manager is (re)started (Windows).

Taking out the brackets immediately solved the problem. The VirtualBox Manager seems to have a problem with brackets in group names. Possibly other characters cause similary issues.

I am currently stuck at v4.3.12 due to issue (#13841), but I've seen this behavior up to v4.3.28 (inclusive)."	Hans Vledder
20239	Breakpoint When Starting 6.1.18	VirtualBox 6.1.18	2021-03-07T14:36:12Z	2021-03-07T14:36:12Z	2021-03-07T14:36:12Z	"I was asked to submit this bug report by scottgus1 as a result of my updated version of VirtualBox reaching a ""breakpoint"" when attempting to start it. I had no problems running version 6.1.16.

My original post is at:
https://forums.virtualbox.org/viewtopic.php?f=6&t=101947&p=495568#p495568

"	SarcasticWit
19443	Bridge Adapter Name List displays not existed NIC on Windows	VirtualBox 6.1.4	2020-03-29T10:03:56Z	2020-03-29T10:11:04Z	2020-03-29T10:11:04Z	Some removed NICs are still displayed in the Name List if VMs set to Bridged Adapter mode.	ohnoithappens
21284	Bridge Adapter not Connecting in Virtualbox 7.x	VirtualBox-7.0.4	2022-11-19T05:58:50Z	2022-12-15T19:17:29Z	2022-12-15T19:17:29Z	"I am using a Windows 10 machine. When I change the network setting to the bridge adapter, I am unable to connect. I have attached the log for a clearer understanding of this problem.
 "	gic
14999	Bridge NIC, ssh from VM will freeze for some cmds	VirtualBox 5.0.12	2016-01-01T02:31:46Z	2016-01-01T02:31:46Z	2016-01-01T02:31:46Z	"Happy New Year! [[BR]]

Both host and guest: Ubuntu 14.04.3 + mate 1.8.2 , kernel 4.2 [[BR]]
* for NIC1, bridged mode, connect to box in the same sub-network (/24) with host, cmd ""ps, w"" works, but longer cmd ""top, ps aux"" will freeze the connection.[[BR]]
* in NAT mode, works fine, to outside box and host [[BR]]
Although the ssh from VM have problems when ssh to outside box, no such issues when ssh to host VM.

For outside box, I also try Ubuntu 12.04/14.04, VM NIC bridge mode always freeze for long cmds.

[[BR]]
Video: https://youtu.be/Ng22YngHUA8"	maxchen
20237	BridgedInterface needs trailing blank	VirtualBox 6.1.18	2021-03-06T18:41:27Z	2021-12-22T03:54:56Z	2021-12-22T03:54:56Z	"My network interface card is a ""NVIDIA nForce 10/100/1000 Mbps Ethernet"", host is Windows 10 20H2 build 19042.844. 
When selecting the NIC as bridged interface in the network settings, it is stored to the .vbox file as ""NVIDIA nForce 10/100/1000 Mbps Ethernet"", however when starting the related guest I get an error message that the virtual machine cannot be started as the network interface is not existing.
I can resolve this by adding a trailing blank to the BridgedInterface in the .vbox file as:
<BridgedInterface name=""NVIDIA nForce 10/100/1000 Mbps Ethernet ""/>
before starting VirtualBox.
But whenever I change some settings of the guest, the trailing blank is removed, so I must do this again and again. "	Phantom2398
18418	Broken display output for guest application entering full screen mode with changed resolution	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
13622	BSOD (SYSTEM_SERVICE_EXCEPTION 0x0000003b) on host machine immediately after powering on guest machine	VirtualBox 4.3.18	2014-11-18T22:29:28Z	2015-06-25T13:51:57Z	2015-06-25T13:51:57Z	"Hello.

I get BSOD (SYSTEM_SERVICE_EXCEPTION 0x0000003b) immediately on host machine after powering on guest machine. 

I have searched the forums and did not find anything corresponding to my problem.

Host: Windows 7 SP1 x64
Guest: Windows 2012"	Anton Lisnenko
18748	bsod after installing alcohol 52% and rebooting in windows xp sp3 guest	VirtualBox 5.2.30	2019-07-08T19:55:53Z	2020-03-03T13:03:57Z	2020-03-03T13:03:57Z	"bsod after installing alcohol 52% and rebooting in windows xp sp3 guest
This problem seems to be in Virtualbox 6 also"	nikitastepanov
17121	BSOD after launching VM	VirtualBox 5.1.28	2017-09-29T07:38:51Z	2017-10-02T08:11:17Z	2017-10-02T08:11:17Z	"Hello,

Recently I've upgraded VirtualBox from 5.0.20 to 5.1.28 version. Unfortunatelly it caused that after launching VM appears blue screen; it is possible to launch VM in safe mode, but normal mode crashes. I' ve tried to back to my prior version, but it didn't help; reinstall VirtualBox and change VM settings in many different ways also didn't help. Host is Windows 7 64-bit; guest is Windows XP 32-bit. Interestingly I' ve set this host image on other guest, Windows 10 32-bit on VirtualBox 5.1.10 and it run, but on Ubuntu 32-bit and 64-bit not. Please give me a hint what I have to do to solve this issue."	Skywanter
16179	BSOD after Update	VirtualBox 5.1.8	2016-11-11T10:57:12Z	2016-11-11T10:57:12Z	2016-11-11T10:57:12Z	"Hi,
I update VirtualBox at version VirtualBox-5.1.8-111374-Win (I dont remember the previous version), after this when i run my virtual machine windows crash in BSOD.
I tried to uninstal and reinstal but nothing is changed.
I tried also to install VirtualBox-5.1.6-110634-Win but when I run the virtual machine windows crash with BSOD.
I tried also to create a new empty virtual machine, but also this go in BSOD. Before the update VirtualBox has worked great for long time.
My PC is Windows 7 ultimate 64Bit with processor I5 8GB Ram.
Also now if I try to install the last version, the installation is aborted with an error.
"	RobertoB
20100	BSOD caused by VirtualBox and USBNetworkGate	VirtualBox 6.1.16	2020-12-24T19:17:27Z	2020-12-24T19:17:27Z	2020-12-24T19:17:27Z	"Hi,

I'd like to report a bug relating to the VirtualBox and USB Network Gate software by Eltima/Electronic Team.

The below set of circumstances cause a BSOD in Windows 10. Tested on Win10 Pro 1909, 2004 and 20H2 updates on Intel and AMD CPUs and Lenovo and MSI hardware (available at the time of testing). Guest type did not seem to matter, they were not running or on some devices not even setup.

USBNetGate is installed
VirtualBox is installed AND running (extension pack and no extension pack does not make a difference, different USB controller settings VMs do not make a difference)
USB device is physically being plugged in - at this point machine will crash with blue screen.

Unplugging a device does not cause a crash.
Unplugging or plugging in a device while VirtualBox is not running does not cause a crash
Unplugging or plugging a device while VirtualBox is running and USBNetGate is not installed does not cause a crash.

It is unclear which software is the cause, it only happens with both active at the same time."	JP-BC-Can
16877	BSoD CLOCK_WATCHDOG_TIMEOUT	VirtualBox 5.1.22	2017-07-05T17:30:24Z	2017-07-05T17:30:24Z	2017-07-05T17:30:24Z	"Machine Log: https://pastebin.com/raw/zYqqUp1T
Host OS: Windows 10
There is a dmp file from the bluescreen wich shows VBoxDrv.sys
I'm using Homestead (laravel) with vagrant. Maybe that helps.
Hopefully this is not a duplicate

This bsod just happens randomly when doing something in host system
DMP file can be loaded here: http://www49.zippyshare.com/v/1pxcsU2X/file.html
as to big for the attachmnent page."	keving
14112	BSoD in VBoxNetAdp6.sys with STOP 0x9F		2015-05-13T14:51:58Z	2015-06-30T18:47:27Z	2015-06-30T18:47:27Z	"Version: VirtualBox 5.0 Beta 2 (previously same error in VBoxNetAdp.sys in 4.3.26, 4.2.?).  I'm trying out the beta to try to get past this annoying error.  The last few times I've followed steps similar to

http://dottech.org/101997/how-to-uninstall-virtualbox-drivers-on-windows/

to remove all traces of any drivers/any registry settings I could find to remove any prior copy of VirtualBox

This issue is most similar to: https://www.virtualbox.org/ticket/11730

Win7x64 Host, Bridged Networking turned on, the VirtualBox program isn't running when the crash occurs.

Network Adapters:

* Intel(R)82567V-2 Gigabit Network Connection on latest driver:   10.0.6.0 ( confirmed via windows and HP websites )
* VirtualBox Host-Only Ethernet Adapter

Minidump for v5.0 Beta2:

{{{
Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\051315-86174-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`0ec26c32?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`0023a662?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9a500?

************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       symsrv*symsrv.dll*c:\extracts\ms debuggger\symbols*http://msdl.microsoft.com/downloads/symbols
Symbol search path is: symsrv*symsrv.dll*c:\extracts\ms debuggger\symbols*http://msdl.microsoft.com/downloads/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18839.amd64fre.win7sp1_gdr.150427-0707
Machine Name:
Kernel base = 0xfffff800`02c1b000 PsLoadedModuleList = 0xfffff800`02e62730
Debug session time: Wed May 13 06:57:38.999 2015 (UTC - 7:00)
System Uptime: 0 days 21:49:09.234
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8009aa44d0, fffff80000b9a518, fffffa8014ff7010}

Unable to load image \SystemRoot\system32\DRIVERS\VBoxNetAdp6.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for VBoxNetAdp6.sys
*** ERROR: Module load completed but symbols could not be loaded for VBoxNetAdp6.sys
Probably caused by : ntkrnlmp

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8009aa44d0, Physical Device Object of the stack
Arg3: fffff80000b9a518, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: fffffa8014ff7010, The blocked IRP

Debugging Details:
------------------


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  ntkrnlmp

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: ntkrnlmp

FAULTING_MODULE: fffff8800413e000 VBoxNetAdp6

IRP_ADDRESS: fffffa8014ff7010

DEVICE_OBJECT: fffffa800c4cd050

DRIVER_OBJECT: fffffa800c1f1ce0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

DPC_STACK_BASE:  FFFFF80000BA0FB0

STACK_TEXT:  
fffff800`00b9a4c8 fffff800`02cfe510 : 00000000`0000009f 00000000`00000003 fffffa80`09aa44d0 fffff800`00b9a518 : nt!KeBugCheckEx
fffff800`00b9a4d0 fffff800`02c9b72c : fffff800`00b9a600 fffff800`00b9a600 00000000`00000000 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x324a0
fffff800`00b9a570 fffff800`02c9b5c6 : fffffa80`0d4d5748 fffffa80`0d4d5748 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9a5e0 fffff800`02c9b4ae : 000000b6`e2fdfdf7 fffff800`00b9ac58 00000000`004cd4a7 fffff800`02e12768 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9ac30 fffff800`02c9b297 : 00000031`e222c6c4 00000031`004cd4a7 00000031`e222c6c3 00000000`000000a7 : nt!KiTimerExpiration+0x1be
fffff800`00b9acd0 fffff800`02c875ca : fffff800`02e0ee80 fffff800`02e1ccc0 00000000`00000000 fffff880`013b24c0 : nt!KiRetireDpcList+0x277
fffff800`00b9ad80 00000000`00000000 : fffff800`00b9b000 fffff800`00b95000 fffff800`00b9ad40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

IMAGE_VERSION:  

FAILURE_BUCKET_ID:  X64_0x9F_3_POWER_DOWN_IMAGE_ntkrnlmp

BUCKET_ID:  X64_0x9F_3_POWER_DOWN_IMAGE_ntkrnlmp

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x9f_3_power_down_image_ntkrnlmp

FAILURE_ID_HASH:  {11a584ac-cfbe-b229-0d33-15c5fd69f706}

Followup: MachineOwner
---------

0: kd> lmvm VBoxNetAdp6
start             end                 module name
fffff880`0413e000 fffff880`04161000   VBoxNetAdp6 T (no symbols)           
    Loaded symbol image file: VBoxNetAdp6.sys
    Image path: \SystemRoot\system32\DRIVERS\VBoxNetAdp6.sys
    Image name: VBoxNetAdp6.sys
    Timestamp:        Tue Apr 14 11:38:41 2015 (552D5EB1)
    CheckSum:         0001F0DE
    ImageSize:        00023000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
0: kd> !irp fffffa8014ff7010 1
Irp is active with 3 stacks 2 is current (= 0xfffffa8014ff7128)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
Flags = 00000000
ThreadListEntry.Flink = fffffa8014ff7030
ThreadListEntry.Blink = fffffa8014ff7030
IoStatus.Status = c00000bb
IoStatus.Information = 00000000
RequestorMode = 00000000
Cancel = 00
CancelIrql = 0
ApcEnvironment = 00
UserIosb = 00000000
UserEvent = 00000000
Overlay.AsynchronousParameters.UserApcRoutine = 00000000
Overlay.AsynchronousParameters.UserApcContext = 00000000
Overlay.AllocationSize = 00000000 - 00000000
CancelRoutine = 00000000   
UserBuffer = 00000000
&Tail.Overlay.DeviceQueueEntry = fffffa8014ff7088
Tail.Overlay.Thread = 00000000
Tail.Overlay.AuxiliaryBuffer = 00000000
Tail.Overlay.ListEntry.Flink = fffffa80139c8eb8
Tail.Overlay.ListEntry.Blink = fffff80002e44bc0
Tail.Overlay.CurrentStackLocation = fffffa8014ff7128
Tail.Overlay.OriginalFileObject = 00000000
Tail.Apc = 00000000
Tail.CompletionKey = 00000000
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
>[ 16, 3]   0 e1 fffffa800c4cd050 00000000 fffff80002ee1210-fffffa800ec22a30 Success Error Cancel pending
	       \Driver\VBoxNetAdp	nt!PopSystemIrpCompletion
			Args: 00015400 00000000 00000005 00000003
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa800ec22a30    

			Args: 00000000 00000000 00000000 00000000
0: kd> !devobj fffffa800c4cd050 f
fffff80002e45070: Unable to get value of ObpRootDirectoryObject
Device object (fffffa800c4cd050) is for:
 InfoMask field not found for _OBJECT_HEADER at fffffa800c4cd020
 \Driver\VBoxNetAdp DriverObject fffffa800c1f1ce0
Current Irp 00000000 RefCount 0 Type 00000017 Flags 00002050
DevExt fffffa800c4cd1a0 DevObjExt fffffa800c4ce8e0 
ExtensionFlags (0x00000800)  DOE_DEFAULT_SD_PRESENT
Characteristics (0x00000100)  FILE_DEVICE_SECURE_OPEN
AttachedTo (Lower) fffffa8009aa44d0 \Driver\PnpManager
Device queue is not busy.
0: kd> !drvobj fffffa800c1f1ce0 f
fffff80002e45070: Unable to get value of ObpRootDirectoryObject
fffff80002e45070: Unable to get value of ObpRootDirectoryObject
Driver object (fffffa800c1f1ce0) is for:
 \Driver\VBoxNetAdp
Driver Extension List: (id , addr)

Device Object list:
fffffa800c4cd050  

DriverEntry:   fffff8800413f860	VBoxNetAdp6
DriverStartIo: 00000000	
DriverUnload:  fffff880016aecd0	ndis!ndisMUnloadEx
AddDevice:     00000000	

Dispatch routines:
[00] IRP_MJ_CREATE                      fffff88001608920	ndis!ndisCreateIrpHandler
[01] IRP_MJ_CREATE_NAMED_PIPE           fffff8800169e490	ndis!ndisDummyIrpHandler
[02] IRP_MJ_CLOSE                       fffff88001608160	ndis!ndisCloseIrpHandler
[03] IRP_MJ_READ                        fffff8800169e490	ndis!ndisDummyIrpHandler
[04] IRP_MJ_WRITE                       fffff8800169e490	ndis!ndisDummyIrpHandler
[05] IRP_MJ_QUERY_INFORMATION           fffff8800169e490	ndis!ndisDummyIrpHandler
[06] IRP_MJ_SET_INFORMATION             fffff8800169e490	ndis!ndisDummyIrpHandler
[07] IRP_MJ_QUERY_EA                    fffff8800169e490	ndis!ndisDummyIrpHandler
[08] IRP_MJ_SET_EA                      fffff8800169e490	ndis!ndisDummyIrpHandler
[09] IRP_MJ_FLUSH_BUFFERS               fffff8800169e490	ndis!ndisDummyIrpHandler
[0a] IRP_MJ_QUERY_VOLUME_INFORMATION    fffff8800169e490	ndis!ndisDummyIrpHandler
[0b] IRP_MJ_SET_VOLUME_INFORMATION      fffff8800169e490	ndis!ndisDummyIrpHandler
[0c] IRP_MJ_DIRECTORY_CONTROL           fffff8800169e490	ndis!ndisDummyIrpHandler
[0d] IRP_MJ_FILE_SYSTEM_CONTROL         fffff8800169e490	ndis!ndisDummyIrpHandler
[0e] IRP_MJ_DEVICE_CONTROL              fffff8800169e020	ndis!ndisDeviceControlIrpHandler
[0f] IRP_MJ_INTERNAL_DEVICE_CONTROL     fffff8800169e490	ndis!ndisDummyIrpHandler
[10] IRP_MJ_SHUTDOWN                    fffff8800169e490	ndis!ndisDummyIrpHandler
[11] IRP_MJ_LOCK_CONTROL                fffff8800169e490	ndis!ndisDummyIrpHandler
[12] IRP_MJ_CLEANUP                     fffff8800169e490	ndis!ndisDummyIrpHandler
[13] IRP_MJ_CREATE_MAILSLOT             fffff8800169e490	ndis!ndisDummyIrpHandler
[14] IRP_MJ_QUERY_SECURITY              fffff8800169e490	ndis!ndisDummyIrpHandler
[15] IRP_MJ_SET_SECURITY                fffff8800169e490	ndis!ndisDummyIrpHandler
[16] IRP_MJ_POWER                       fffff88001652c60	ndis!ndisPowerDispatch
[17] IRP_MJ_SYSTEM_CONTROL              fffff88001672ee0	ndis!ndisWMIDispatch
[18] IRP_MJ_DEVICE_CHANGE               fffff8800169e490	ndis!ndisDummyIrpHandler
[19] IRP_MJ_QUERY_QUOTA                 fffff8800169e490	ndis!ndisDummyIrpHandler
[1a] IRP_MJ_SET_QUOTA                   fffff8800169e490	ndis!ndisDummyIrpHandler
[1b] IRP_MJ_PNP                         fffff880016bc560	ndis!ndisPnPDispatch
}}}

Here's a 4.3.26 example:

{{{
Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\040715-17799-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`0023dc32?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`02dcfc32?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`042d4500?

************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       symsrv*symsrv.dll*c:\extracts\ms debuggger\symbols*http://msdl.microsoft.com/downloads/symbols
Symbol search path is: symsrv*symsrv.dll*c:\extracts\ms debuggger\symbols*http://msdl.microsoft.com/downloads/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18741.amd64fre.win7sp1_gdr.150202-1526
Machine Name:
Kernel base = 0xfffff800`02c08000 PsLoadedModuleList = 0xfffff800`02e4c890
Debug session time: Mon Apr  6 20:24:15.313 2015 (UTC - 7:00)
System Uptime: 12 days 4:51:38.831
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
.....................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8009aa6060, fffff800042d4518, fffffa800d2fdd60}

Unable to load image \SystemRoot\system32\DRIVERS\VBoxNetAdp.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for VBoxNetAdp.sys
*** ERROR: Module load completed but symbols could not be loaded for VBoxNetAdp.sys
Probably caused by : ntkrnlmp

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8009aa6060, Physical Device Object of the stack
Arg3: fffff800042d4518, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: fffffa800d2fdd60, The blocked IRP

Debugging Details:
------------------


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  ntkrnlmp

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: ntkrnlmp

FAULTING_MODULE: fffff88005279000 VBoxNetAdp

IRP_ADDRESS: fffffa800d2fdd60

DEVICE_OBJECT: fffffa800c321050

DRIVER_OBJECT: fffffa800aa7ae70

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

DPC_STACK_BASE:  FFFFF800042DAFB0

STACK_TEXT:  
fffff800`042d44c8 fffff800`02cedb92 : 00000000`0000009f 00000000`00000003 fffffa80`09aa6060 fffff800`042d4518 : nt!KeBugCheckEx
fffff800`042d44d0 fffff800`02c88cfc : fffff800`042d4600 fffff800`042d4600 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33af0
fffff800`042d4570 fffff800`02c88b96 : fffff800`02e2f140 00000000`04073b69 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`042d45e0 fffff800`02c88a7e : 00000996`bb12dbac fffff800`042d4c58 00000000`04073b69 fffff800`02dfcfa8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`042d4c30 fffff800`02c88867 : 0000029d`89aab1c1 0000029d`04073b69 0000029d`89aab16a 00000000`00000069 : nt!KiTimerExpiration+0x1be
fffff800`042d4cd0 fffff800`02c74bca : fffff800`02df9e80 fffff800`02e07cc0 00000000`00000000 fffff880`012234c0 : nt!KiRetireDpcList+0x277
fffff800`042d4d80 00000000`00000000 : fffff800`042d5000 fffff800`042cf000 fffff800`042d4d40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

IMAGE_VERSION:  

FAILURE_BUCKET_ID:  X64_0x9F_3_POWER_DOWN_IMAGE_ntkrnlmp

BUCKET_ID:  X64_0x9F_3_POWER_DOWN_IMAGE_ntkrnlmp

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x9f_3_power_down_image_ntkrnlmp

FAILURE_ID_HASH:  {11a584ac-cfbe-b229-0d33-15c5fd69f706}

Followup: MachineOwner
---------

0: kd> lmvm VBoxNetAdp
start             end                 module name
fffff880`05279000 fffff880`052a1000   VBoxNetAdp T (no symbols)           
    Loaded symbol image file: VBoxNetAdp.sys
    Image path: \SystemRoot\system32\DRIVERS\VBoxNetAdp.sys
    Image name: VBoxNetAdp.sys
    Timestamp:        Mon Mar 16 09:35:44 2015 (55070660)
    CheckSum:         00030F13
    ImageSize:        00028000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
0: kd> !irp fffffa800d2fdd60 1
Irp is active with 3 stacks 2 is current (= 0xfffffa800d2fde78)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
Flags = 00000000
ThreadListEntry.Flink = fffffa800d2fdd80
ThreadListEntry.Blink = fffffa800d2fdd80
IoStatus.Status = c00000bb
IoStatus.Information = 00000000
RequestorMode = 00000000
Cancel = 00
CancelIrql = 0
ApcEnvironment = 00
UserIosb = 00000000
UserEvent = 00000000
Overlay.AsynchronousParameters.UserApcRoutine = 00000000
Overlay.AsynchronousParameters.UserApcContext = 00000000
Overlay.AllocationSize = 00000000 - 00000000
CancelRoutine = 00000000   
UserBuffer = 00000000
&Tail.Overlay.DeviceQueueEntry = fffffa800d2fddd8
Tail.Overlay.Thread = 00000000
Tail.Overlay.AuxiliaryBuffer = 00000000
Tail.Overlay.ListEntry.Flink = fffffa800de5fd68
Tail.Overlay.ListEntry.Blink = fffff80002e2ed20
Tail.Overlay.CurrentStackLocation = fffffa800d2fde78
Tail.Overlay.OriginalFileObject = 00000000
Tail.Apc = 00000000
Tail.CompletionKey = 00000000
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
>[ 16, 3]   0 e1 fffffa800c321050 00000000 fffff80002ecb210-fffffa800d27ba50 Success Error Cancel pending
	       \Driver\VBoxNetAdp	nt!PopSystemIrpCompletion
			Args: 00015400 00000000 00000005 00000003
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa800d27ba50    

			Args: 00000000 00000000 00000000 00000000
0: kd> !devobj fffffa800c321050 f
fffff80002e2f1d0: Unable to get value of ObpRootDirectoryObject
Device object (fffffa800c321050) is for:
 InfoMask field not found for _OBJECT_HEADER at fffffa800c321020
 \Driver\VBoxNetAdp DriverObject fffffa800aa7ae70
Current Irp 00000000 RefCount 0 Type 00000017 Flags 00002050
DevExt fffffa800c3211a0 DevObjExt fffffa800c3228e0 
ExtensionFlags (0x00000800)  DOE_DEFAULT_SD_PRESENT
Characteristics (0x00000100)  FILE_DEVICE_SECURE_OPEN
AttachedTo (Lower) fffffa8009aa6060 \Driver\PnpManager
Device queue is not busy.
0: kd> !drvobj fffffa800aa7ae70 f
fffff80002e2f1d0: Unable to get value of ObpRootDirectoryObject
fffff80002e2f1d0: Unable to get value of ObpRootDirectoryObject
Driver object (fffffa800aa7ae70) is for:
 \Driver\VBoxNetAdp
Driver Extension List: (id , addr)

Device Object list:
fffffa800c81f4d0: Could not read device object


DriverEntry:   fffff8800527e0e0	VBoxNetAdp
DriverStartIo: 00000000	
DriverUnload:  fffff880017c04a0	ndis!ndisMUnload
AddDevice:     00000000	

Dispatch routines:
[00] IRP_MJ_CREATE                      fffff88001716920	ndis!ndisCreateIrpHandler
[01] IRP_MJ_CREATE_NAMED_PIPE           fffff880017ac490	ndis!ndisDummyIrpHandler
[02] IRP_MJ_CLOSE                       fffff88001716160	ndis!ndisCloseIrpHandler
[03] IRP_MJ_READ                        fffff880017ac490	ndis!ndisDummyIrpHandler
[04] IRP_MJ_WRITE                       fffff880017ac490	ndis!ndisDummyIrpHandler
[05] IRP_MJ_QUERY_INFORMATION           fffff880017ac490	ndis!ndisDummyIrpHandler
[06] IRP_MJ_SET_INFORMATION             fffff880017ac490	ndis!ndisDummyIrpHandler
[07] IRP_MJ_QUERY_EA                    fffff880017ac490	ndis!ndisDummyIrpHandler
[08] IRP_MJ_SET_EA                      fffff880017ac490	ndis!ndisDummyIrpHandler
[09] IRP_MJ_FLUSH_BUFFERS               fffff880017ac490	ndis!ndisDummyIrpHandler
[0a] IRP_MJ_QUERY_VOLUME_INFORMATION    fffff880017ac490	ndis!ndisDummyIrpHandler
[0b] IRP_MJ_SET_VOLUME_INFORMATION      fffff880017ac490	ndis!ndisDummyIrpHandler
[0c] IRP_MJ_DIRECTORY_CONTROL           fffff880017ac490	ndis!ndisDummyIrpHandler
[0d] IRP_MJ_FILE_SYSTEM_CONTROL         fffff880017ac490	ndis!ndisDummyIrpHandler
[0e] IRP_MJ_DEVICE_CONTROL              fffff880017ac020	ndis!ndisDeviceControlIrpHandler
[0f] IRP_MJ_INTERNAL_DEVICE_CONTROL     fffff880017ac490	ndis!ndisDummyIrpHandler
[10] IRP_MJ_SHUTDOWN                    fffff880017ac490	ndis!ndisDummyIrpHandler
[11] IRP_MJ_LOCK_CONTROL                fffff880017ac490	ndis!ndisDummyIrpHandler
[12] IRP_MJ_CLEANUP                     fffff880017ac490	ndis!ndisDummyIrpHandler
[13] IRP_MJ_CREATE_MAILSLOT             fffff880017ac490	ndis!ndisDummyIrpHandler
[14] IRP_MJ_QUERY_SECURITY              fffff880017ac490	ndis!ndisDummyIrpHandler
[15] IRP_MJ_SET_SECURITY                fffff880017ac490	ndis!ndisDummyIrpHandler
[16] IRP_MJ_POWER                       fffff88001760c60	ndis!ndisPowerDispatch
[17] IRP_MJ_SYSTEM_CONTROL              fffff88001780ee0	ndis!ndisWMIDispatch
[18] IRP_MJ_DEVICE_CHANGE               fffff880017ac490	ndis!ndisDummyIrpHandler
[19] IRP_MJ_QUERY_QUOTA                 fffff880017ac490	ndis!ndisDummyIrpHandler
[1a] IRP_MJ_SET_QUOTA                   fffff880017ac490	ndis!ndisDummyIrpHandler
[1b] IRP_MJ_PNP                         fffff880017ca560	ndis!ndisPnPDispatch
}}}

I've experienced 8 similar crashes since March 3/25 using different versions of VirtualBox.  It would seem that if you need to reproduce this error somewhat reliably, my machine can do it."	ohm
18854	BSOD on Windows 10 host with console CentOS 7 Linux guest in network driver	VirtualBox 6.0.10	2019-08-19T16:22:46Z	2019-08-19T16:22:46Z	2019-08-19T16:22:46Z	"I am using VirtualBox on Windows 10 x64 host.
BSOD of Windows host occured when I using CentOS 7 x64 Linux without GUI (just console mode) installation and trying to install ISPmanager Business https://www.ispsystem.com/software/ispmanager/download to avaluate it:
wget ""http://cdn.ispsystem.com/install.sh""
sh install.sh
, activating the demo version of ISPmanager Business and trying to update packages of it.
The probability of BSOD is approx. 80% in update packages state.
BSOD is in Windows network card driver in ndis!ndisMSendCompleteNetBufferListsInternal+0x121
ndis!ndisCallSendCompleteHandler+0x33
ndis!NdisMSendNetBufferListsComplete+0x1df
e1d65x64+0x133b4
(see Windbg outputs)
Guest network is in bridge mode.
In addition, RusRoute firewall free version http://rusroute.com/ is installed on host system, independed in disabled or enabled state of it (Standard Windows firewall is disalbed in both cases).
Can you tell me what software is the reason os BSOD? Is this the bug in VistualBox or in other third party software, like RusRoute firewall?
The Windows 7, XP guests with the same environment is working fine.
WinDbg of minidump1, minidump2 are attached.

{{{

************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*C:\MySymbols*https://msdl.microsoft.com/download/symbols
Deferred                                       cache*c:\MySymbols
Deferred                                       srv*https://msdl.microsoft.com/download/symbols

Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\minidump\080219-10984-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*C:\MySymbols*https://msdl.microsoft.com/download/symbols
Deferred                                       cache*c:\MySymbols
Deferred                                       srv*https://msdl.microsoft.com/download/symbols
Symbol search path is: srv*C:\MySymbols*https://msdl.microsoft.com/download/symbols;cache*c:\MySymbols;srv*https://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 10 Kernel Version 18362 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff804`18200000 PsLoadedModuleList = 0xfffff804`186432f0
Debug session time: Fri Aug  2 20:15:42.372 2019 (UTC + 3:00)
System Uptime: 0 days 0:49:12.083
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
....................
For analysis of this file, run !analyze -v
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
An attempt was made to execute non-executable memory.  The guilty driver
is on the stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: ffff9d8db279f1a0, Virtual address for the attempted execute.
Arg2: 8a000008092008e3, PTE contents.
Arg3: fffff8041db504a0, (reserved)
Arg4: 0000000000000003, (reserved)

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for e1d65x64.sys

KEY_VALUES_STRING: 1

    Key  : Dump.Attributes.InsufficientDumpfileSize
    Value: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10.0.18362.239 (WinBuild.160101.0800)

DUMP_FILE_ATTRIBUTES: 0xc
  Insufficient Dumpfile Size
  Kernel Generated Triage Dump

DUMP_TYPE:  2

BUGCHECK_P1: ffff9d8db279f1a0

BUGCHECK_P2: 8a000008092008e3

BUGCHECK_P3: fffff8041db504a0

BUGCHECK_P4: 3

CPU_COUNT: 8

CPU_MHZ: 1068

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: 9

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0xFC

PROCESS_NAME:  VirtualBoxVM.e

CURRENT_IRQL:  2

ANALYSIS_SESSION_HOST:  7700K

ANALYSIS_SESSION_TIME:  08-19-2019 19:05:14.0379

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

DPC_STACK_BASE:  FFFFF8041DB50FB0

TRAP_FRAME:  fffff8041db504a0 -- (.trap 0xfffff8041db504a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff9d8db279f1a0 rbx=0000000000000000 rcx=ffff9d8db2ad9950
rdx=ffff9d8db9a923d0 rsi=0000000000000000 rdi=0000000000000000
rip=ffff9d8db279f1a0 rsp=fffff8041db50638 rbp=fffff8041db506b9
 r8=0000000000000001  r9=0000000000000000 r10=fffff80424425b90
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
ffff9d8d`b279f1a0 1101            adc     dword ptr [rcx],eax ds:ffff9d8d`b2ad9950=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff804184554bc to fffff804183bc900

STACK_TEXT:  
fffff804`1db50278 fffff804`184554bc : 00000000`000000fc ffff9d8d`b279f1a0 8a000008`092008e3 fffff804`1db504a0 : nt!KeBugCheckEx
fffff804`1db50280 fffff804`1844fbc1 : 00000000`00000003 00000000`00000001 00000000`00000000 fffff804`1db503c0 : nt!MiCheckSystemNxFault+0x125330
fffff804`1db502c0 fffff804`1827ac2a : 00000000`00000003 00000000`00000011 fffff804`1db50400 00000000`00000000 : nt!MiRaisedIrqlFault+0x12a6e1
fffff804`1db50300 fffff804`183ca920 : ffff9d8d`b279f1a0 ffff9d8d`bb66a950 00000000`00000001 00000000`00000001 : nt!MmAccessFault+0x48a
fffff804`1db504a0 ffff9d8d`b279f1a0 : fffff804`1d18aa51 ffff9d8d`b2ae7a20 ffff9d8d`b281a120 fffff804`244f10b0 : nt!KiPageFault+0x360
fffff804`1db50638 fffff804`1d18aa51 : ffff9d8d`b2ae7a20 ffff9d8d`b281a120 fffff804`244f10b0 ffff9d8d`b9a923d0 : 0xffff9d8d`b279f1a0
fffff804`1db50640 fffff804`1d18eba3 : 00000000`00000002 00000000`00000000 fffff804`00000001 fffff804`244c2101 : ndis!ndisMSendCompleteNetBufferListsInternal+0x121
fffff804`1db50720 fffff804`1d18bcdf : 00001e00`00001e01 ffff9d8d`b26073c1 ffff9d8d`b2adbb60 ffff9d8d`b9a923d0 : ndis!ndisCallSendCompleteHandler+0x33
fffff804`1db50760 fffff804`271033b4 : 00000000`00000002 00000001`00000000 00000001`00000000 fffff804`27100d00 : ndis!NdisMSendNetBufferListsComplete+0x1df
fffff804`1db50850 00000000`00000002 : 00000001`00000000 00000001`00000000 fffff804`27100d00 ffff9d8d`b2be0c60 : e1d65x64+0x133b4
fffff804`1db50858 00000001`00000000 : 00000001`00000000 fffff804`27100d00 ffff9d8d`b2be0c60 ffff9d8d`b29c9d50 : 0x2
fffff804`1db50860 00000001`00000000 : fffff804`27100d00 ffff9d8d`b2be0c60 ffff9d8d`b29c9d50 ffff9d8d`b281f000 : 0x00000001`00000000
fffff804`1db50868 fffff804`27100d00 : ffff9d8d`b2be0c60 ffff9d8d`b29c9d50 ffff9d8d`b281f000 ffff9d8d`b281fe40 : 0x00000001`00000000
fffff804`1db50870 ffff9d8d`b2be0c60 : ffff9d8d`b29c9d50 ffff9d8d`b281f000 ffff9d8d`b281fe40 00000001`b283ad01 : e1d65x64+0x10d00
fffff804`1db50878 ffff9d8d`b29c9d50 : ffff9d8d`b281f000 ffff9d8d`b281fe40 00000001`b283ad01 00000000`00000001 : 0xffff9d8d`b2be0c60
fffff804`1db50880 ffff9d8d`b281f000 : ffff9d8d`b281fe40 00000001`b283ad01 00000000`00000001 ffff9d8d`000001ad : 0xffff9d8d`b29c9d50
fffff804`1db50888 ffff9d8d`b281fe40 : 00000001`b283ad01 00000000`00000001 ffff9d8d`000001ad 00000000`00000000 : 0xffff9d8d`b281f000
fffff804`1db50890 00000001`b283ad01 : 00000000`00000001 ffff9d8d`000001ad 00000000`00000000 ffff9d8d`af928350 : 0xffff9d8d`b281fe40
fffff804`1db50898 00000000`00000001 : ffff9d8d`000001ad 00000000`00000000 ffff9d8d`af928350 00000000`00000000 : 0x00000001`b283ad01
fffff804`1db508a0 ffff9d8d`000001ad : 00000000`00000000 ffff9d8d`af928350 00000000`00000000 00000000`00000000 : 0x1
fffff804`1db508a8 00000000`00000000 : ffff9d8d`af928350 00000000`00000000 00000000`00000000 ffff9d00`00000000 : 0xffff9d8d`000001ad


THREAD_SHA1_HASH_MOD_FUNC:  c0ffbf375cd55e1aa93daf3c03427b8881b1e850

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  5058410cce10b80427a1f7de155fad955a47b3fb

THREAD_SHA1_HASH_MOD:  f2616a5e3854c666781435d2d0ed7d6384206ea6

FOLLOWUP_IP: 
e1d65x64+133b4
fffff804`271033b4 ??              ???

SYMBOL_STACK_INDEX:  9

SYMBOL_NAME:  e1d65x64+133b4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: e1d65x64

IMAGE_NAME:  e1d65x64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  57f4c1b3

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  133b4

FAILURE_BUCKET_ID:  0xFC_e1d65x64!unknown_function

BUCKET_ID:  0xFC_e1d65x64!unknown_function

PRIMARY_PROBLEM_CLASS:  0xFC_e1d65x64!unknown_function

TARGET_TIME:  2019-08-02T17:15:42.000Z

OSBUILD:  18362

OSSERVICEPACK:  239

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  1972-02-02 11:33:06

BUILDDATESTAMP_STR:  160101.0800

BUILDLAB_STR:  WinBuild

BUILDOSVER_STR:  10.0.18362.239

ANALYSIS_SESSION_ELAPSED_TIME:  b5e

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0xfc_e1d65x64!unknown_function

FAILURE_ID_HASH:  {7259990a-ebc1-3d2e-33f5-0c4abf098887}

Followup:     MachineOwner
---------


}}}



{{{

Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\minidump\080219-11296-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*C:\MySymbols*https://msdl.microsoft.com/download/symbols
Symbol search path is: srv*C:\MySymbols*https://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 10 Kernel Version 18362 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff803`62c00000 PsLoadedModuleList = 0xfffff803`630432f0
Debug session time: Fri Aug  2 20:37:09.365 2019 (UTC + 3:00)
System Uptime: 0 days 0:11:15.077
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
................
For analysis of this file, run !analyze -v
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
An attempt was made to execute non-executable memory.  The guilty driver
is on the stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: ffff800803df71a0, Virtual address for the attempted execute.
Arg2: 8a00000809c008e3, PTE contents.
Arg3: ffff908edb1c8340, (reserved)
Arg4: 0000000000000003, (reserved)

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for e1d65x64.sys
*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

DUMP_TYPE:  2

BUGCHECK_P1: ffff800803df71a0

BUGCHECK_P2: 8a00000809c008e3

BUGCHECK_P3: ffff908edb1c8340

BUGCHECK_P4: 3

CPU_COUNT: 8

CPU_MHZ: 1068

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: 9

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0xFC

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_SESSION_HOST:  7700K

ANALYSIS_SESSION_TIME:  08-19-2019 19:08:23.0965

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

TRAP_FRAME:  ffff908edb1c8340 -- (.trap 0xffff908edb1c8340)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff800803df71a0 rbx=0000000000000000 rcx=ffff8008042dab50
rdx=ffff80080ae10600 rsi=0000000000000000 rdi=0000000000000000
rip=ffff800803df71a0 rsp=ffff908edb1c84d8 rbp=ffff908edb1c8559
 r8=0000000000000001  r9=0000000000000000 r10=fffff8036e9c5b90
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
ffff8008`03df71a0 1101            adc     dword ptr [rcx],eax ds:ffff8008`042dab50=03da7ef0
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80362e554bc to fffff80362dbc900

STACK_TEXT:  
ffff908e`db1c8118 fffff803`62e554bc : 00000000`000000fc ffff8008`03df71a0 8a000008`09c008e3 ffff908e`db1c8340 : nt!KeBugCheckEx
ffff908e`db1c8120 fffff803`62e4fbc1 : 00000000`00000003 00000000`00000001 00000000`00000000 ffff908e`db1c8260 : nt!MiCheckSystemNxFault+0x125330
ffff908e`db1c8160 fffff803`62c7ac2a : 00000000`00000006 00000000`00000011 ffff908e`db1c82a0 00000000`00000000 : nt!MiRaisedIrqlFault+0x12a6e1
ffff908e`db1c81a0 fffff803`62dca920 : 00000000`00000000 fffff803`b2503711 00000000`00000002 00000000`00000036 : nt!MmAccessFault+0x48a
ffff908e`db1c8340 ffff8008`03df71a0 : fffff803`6778aa51 ffff8008`0451aa20 ffff8008`03e223f0 fffff803`6ea910b0 : nt!KiPageFault+0x360
ffff908e`db1c84d8 fffff803`6778aa51 : ffff8008`0451aa20 ffff8008`03e223f0 fffff803`6ea910b0 ffff8008`0ae10600 : 0xffff8008`03df71a0
ffff908e`db1c84e0 fffff803`6778eba3 : 00000000`00000002 00000000`00000000 fffff803`00000001 fffff803`6ea62101 : ndis!ndisMSendCompleteNetBufferListsInternal+0x121
ffff908e`db1c85c0 fffff803`6778bcdf : fffff803`60367101 ffff8008`03afb9a1 ffff8008`043198c0 ffff8008`0ae10600 : ndis!ndisCallSendCompleteHandler+0x33
ffff908e`db1c8600 fffff803`70ed33b4 : 00000000`00000002 00000001`00000000 00000001`00000000 fffff803`70ed0d00 : ndis!NdisMSendNetBufferListsComplete+0x1df
ffff908e`db1c86f0 00000000`00000002 : 00000001`00000000 00000001`00000000 fffff803`70ed0d00 00000000`00000000 : e1d65x64+0x133b4
ffff908e`db1c86f8 00000001`00000000 : 00000001`00000000 fffff803`70ed0d00 00000000`00000000 00000000`00000000 : 0x2
ffff908e`db1c8700 00000001`00000000 : fffff803`70ed0d00 00000000`00000000 00000000`00000000 ffff8008`03e23000 : 0x00000001`00000000
ffff908e`db1c8708 fffff803`70ed0d00 : 00000000`00000000 00000000`00000000 ffff8008`03e23000 ffff8008`03e23e40 : 0x00000001`00000000
ffff908e`db1c8710 00000000`00000000 : 00000000`00000000 ffff8008`03e23000 ffff8008`03e23e40 00000001`03e3ed01 : e1d65x64+0x10d00


THREAD_SHA1_HASH_MOD_FUNC:  c0ffbf375cd55e1aa93daf3c03427b8881b1e850

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  5058410cce10b80427a1f7de155fad955a47b3fb

THREAD_SHA1_HASH_MOD:  f2616a5e3854c666781435d2d0ed7d6384206ea6

FOLLOWUP_IP: 
e1d65x64+133b4
fffff803`70ed33b4 448b7dcb        mov     r15d,dword ptr [rbp-35h]

FAULT_INSTR_CODE:  cb7d8b44

SYMBOL_STACK_INDEX:  9

SYMBOL_NAME:  e1d65x64+133b4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: e1d65x64

IMAGE_NAME:  e1d65x64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  57f4c1b3

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  133b4

FAILURE_BUCKET_ID:  0xFC_e1d65x64!unknown_function

BUCKET_ID:  0xFC_e1d65x64!unknown_function

PRIMARY_PROBLEM_CLASS:  0xFC_e1d65x64!unknown_function

TARGET_TIME:  2019-08-02T17:37:09.000Z

OSBUILD:  18362

OSSERVICEPACK:  239

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  1972-02-02 11:33:06

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  10b20

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0xfc_e1d65x64!unknown_function

FAILURE_ID_HASH:  {7259990a-ebc1-3d2e-33f5-0c4abf098887}

Followup:     MachineOwner
---------


}}}
"	MaaSoftware
18457	BSOD on Windows 7 host	VirtualBox 6.0.4	2019-02-27T02:38:18Z	2019-02-27T02:38:18Z	2019-02-27T02:38:18Z	VirtualBox recently started to cause a crash of my host Win7 when I start any VM. log file and minidump are attached.	rgazizov
14322	BSOD on Windows 7 upon hibernating while VirtualBox is open	VirtualBox 4.3.30	2015-07-24T14:06:23Z	2015-09-02T21:52:59Z	2015-09-02T21:52:59Z	"I have a recurring problem where I get a blue screen of death when I hibernate my computer while I have VirtualBox open. I'm running Windows 7 64-bit with a xubuntu on Ubuntu 14.04 (trusty) guest. I'm also using version 4.3.30 of virtualbox and version 4.3.24 of the guest additions. My BSOD provided the following information: the error was a DRIVER_IRQL_NOT_LESS_OR_EQUAL, and was attributed to VBoxNetFlt.sys. I ran WinDbg on the MEMORY.DMP (full dump, not minidump) and got the following info:

{{{
    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Windows\MEMORY.DMP]
    Kernel Summary Dump File: Only kernel address space is available
    
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.18741.amd64fre.win7sp1_gdr.150202-1526
    Machine Name:
    Kernel base = 0xfffff800`0300f000 PsLoadedModuleList = 0xfffff800`03253890
    Debug session time: Fri Apr 10 15:50:18.376 2015 (UTC - 4:00)
    System Uptime: 3 days 14:35:58.020
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...........................................
    Loading User Symbols
    
    Loading unloaded module list
    ................................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {112337, 2, 0, fffff80003076615}
    
    *** ERROR: Module load completed but symbols could not be loaded for avgidsdrivera.sys
    Probably caused by : avgidsdrivera.sys ( avgidsdrivera+10634 )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 0000000000112337, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, bitfield :
    	bit 0 : value 0 = read operation, 1 = write operation
    	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff80003076615, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS:  0000000000112337 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!KiInsertQueueApc+69
    fffff800`03076615 488b4108        mov     rax,qword ptr [rcx+8]
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  System
    
    TRAP_FRAME:  fffff8800bffb710 -- (.trap 0xfffff8800bffb710)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff80003341a58 rbx=0000000000000000 rcx=000000000011232f
    rdx=fffffa800a6373e0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80003076615 rsp=fffff8800bffb8a0 rbp=fffff880009e8180
     r8=0000000000000001  r9=000000000011231f r10=fffff880009e8c01
    r11=fffffa800fd26b00 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe nc
    nt!KiInsertQueueApc+0x69:
    fffff800`03076615 488b4108        mov     rax,qword ptr [rcx+8] ds:00000000`00112337=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80003083469 to fffff80003083ec0
    
    STACK_TEXT:  
    fffff880`0bffb5c8 fffff800`03083469 : 00000000`0000000a 00000000`00112337 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`0bffb5d0 fffff800`030820e0 : fffff880`0bffb738 fffff800`03083153 ffffffff`8000297c fffffa80`105c1060 : nt!KiBugCheckDispatch+0x69
    fffff880`0bffb710 fffff800`03076615 : fffff880`00000001 fffffa80`00000000 00000000`00000000 00000000`00000001 : nt!KiPageFault+0x260
    fffff880`0bffb8a0 fffff800`030656b0 : fffffa80`105c1060 00000000`00000000 00000000`00000078 fffffa80`0a6373d0 : nt!KiInsertQueueApc+0x69
    fffff880`0bffb8d0 fffff880`04c10634 : 00000000`00000000 00000000`778e7ac0 00000000`00000078 00000000`000007ff : nt!KeInsertQueueApc+0x80
    fffff880`0bffb930 fffff880`04c107b4 : 00000000`0000ed04 fffff880`04c3cf50 ffffffff`8000397c fffffa80`1769b6c0 : avgidsdrivera+0x10634
    fffff880`0bffba10 fffff880`04c10866 : ffffffff`8000397c fffffa80`1769b6c0 fffffa80`168f6520 00000000`000007ff : avgidsdrivera+0x107b4
    fffff880`0bffbac0 fffff880`04c2925c : 00000000`00000001 fffff880`0bffbba8 fffffa80`0fd26b50 fffff880`0bffbba8 : avgidsdrivera+0x10866
    fffff880`0bffbb10 fffff800`0337cb43 : 00000000`00000001 00000000`00000001 00000000`00000000 fffffa80`0fd26b50 : avgidsdrivera+0x2925c
    fffff880`0bffbb40 fffff800`0308da95 : fffff800`03338b00 fffff800`0322b201 fffffa80`0fd26b00 fffffa80`00000000 : nt!IopProcessWorkItem+0x23
    fffff880`0bffbb70 fffff800`03322b8a : fffffa80`105029d0 fffffa80`0fd26b50 00000000`00000080 fffffa80`0698eb30 : nt!ExpWorkerThread+0x111
    fffff880`0bffbc00 fffff800`030758e6 : fffff880`03365180 fffffa80`0fd26b50 fffffa80`06d40290 00000000`07fa1011 : nt!PspSystemThreadStartup+0x5a
    fffff880`0bffbc40 00000000`00000000 : fffff880`0bffc000 fffff880`0bff6000 fffff880`0bffb8a0 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    avgidsdrivera+10634
    fffff880`04c10634 84c0            test    al,al
    
    SYMBOL_STACK_INDEX:  5
    
    SYMBOL_NAME:  avgidsdrivera+10634
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: avgidsdrivera
    
    IMAGE_NAME:  avgidsdrivera.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  55128c2a
    
    FAILURE_BUCKET_ID:  X64_0xA_avgidsdrivera+10634
    
    BUCKET_ID:  X64_0xA_avgidsdrivera+10634
    
    Followup: MachineOwner
    ---------
}}}

Please provide any assistance you can on determining the cause of and solution to this problem."	Anomaly13
16392	BSOD SYSTEM_SERVICE_EXCEPTION on Windows 10	VirtualBox 5.1.12	2017-01-16T13:31:29Z	2017-01-16T13:48:12Z	2017-01-16T13:48:12Z	"I use a VM from MongoDB University course M310.
When I run the VM I get BSOD."	enabokov
20145	BSOD when a VM is shut down	VirtualBox 6.1.16	2021-01-21T07:14:05Z	2021-01-22T04:38:45Z	2021-01-22T04:38:45Z	"This issue is not new, but finally I'm fed up. I thought that you get crash reports from Microsoft, but perhaps this is not the case. It's been perhaps a year that this been happening and no solution still.
At least 4 out of 5 times when a particular Windows 7 VM is shut down (not when it's restarted only), it causes the BSOD (memory corruption) on the Windows 10 host. It's more likely to happen when the VM has been running at least several hours, but this is not a requirement. The below info is from the debugger, but I don't know how to debug that, only providing this as a proof it's !VirtualBox (VBoxDrv.sys) that causes the crash.

{{{
BugCheck 1A, {1236, ffff8a871b92b000, ffff8a871b92b308, 242513}

* ERROR: Symbol file could not be found.  Defaulted to export symbols for VBoxDrv.sys - 
* ERROR: Symbol file could not be found.  Defaulted to export symbols for VMMR0.r0 - 
Probably caused by : memory_corruption


BUGCHECK_STR:  0x1a_1236

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  VirtualBoxVM.e

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80782747406 to fffff807827f5780

STACK_TEXT:  
fffff98f`33cdf518 fffff807`82747406 : 00000000`0000001a 00000000`00001236 ffff8a87`1b92b000 ffff8a87`1b92b308 : nt!KeBugCheckEx
fffff98f`33cdf520 fffff807`8271fc5b : ffff8a87`1b92b000 ffff87f2`00000000 ffffed80`06c6f390 ffff8a87`00000001 : nt!MiFreePagesFromMdl+0x4c2
fffff98f`33cdf5b0 fffff807`881be341 : ffff8a87`19ae7010 ffff8a87`1b530aa0 ffff8a87`1b931010 01000000`00100000 : nt!MmFreePagesFromMdl+0xb
fffff98f`33cdf5e0 fffff807`8818347b : ffff8a87`1b92d010 ffff8a87`1b530aa0 ffff8a87`1b931010 00000000`0d846602 : VBoxDrv!g_abRTZero4K+0x12bf1
fffff98f`33cdf610 fffff807`7ebd5f15 : ffff8a87`19ae7010 ffff8a87`19ae7010 ffff8a87`19ae7010 fffff807`8270f2b9 : VBoxDrv!RTR0MemObjFree+0xfb
fffff98f`33cdf640 fffff807`7ebd6a8f : ffff8a87`1b931010 ffff8a87`19ae7260 ffff8a87`16625000 fffff807`8818227c : VMMR0!GMMR0Term+0x645
fffff98f`33cdf6c0 fffff807`7ebd856a : 00000000`00002000 ffff8a87`19ae7018 ffff8a87`19e02010 ffff8a87`16625000 : VMMR0!GMMR0CleanupVM+0x25f
fffff98f`33cdf720 fffff807`7ebd8794 : ffff8a87`19e02030 ffff8a87`16625000 ffff8a87`19e02010 ffff8a87`19e02030 : VMMR0!GVMMR0DestroyVM+0x39a
fffff98f`33cdf750 fffff807`88161cc1 : ffff8a87`1100c8d0 00000000`00000055 ffff8a87`19e02030 ffff8a87`09e02000 : VMMR0!GVMMR0DestroyVM+0x5c4
fffff98f`33cdf7a0 fffff807`7ebd8465 : ffff8a87`16625000 00000000`00000003 00000000`00042000 fffff807`826501c1 : VBoxDrv!SUPR0ObjRelease+0x171
fffff98f`33cdf7d0 fffff807`7ebfe2a1 : 00000000`00000000 00000000`00000000 ffff8a87`171e07c0 00000000`00000000 : VMMR0!GVMMR0DestroyVM+0x295
fffff98f`33cdf840 fffff807`7ebff4ff : 00000000`00000021 00000000`00000000 00000000`00000000 fffff807`8266119e : VMMR0!ModuleInit+0x6e1
fffff98f`33cdf8a0 fffff807`88167bfb : ffff8a87`1d9e7010 ffff8a87`0f8331a0 00000000`00000000 ffff8a87`171e07c0 : VMMR0!VMMR0EntryEx+0x9f
fffff98f`33cdf910 fffff807`881760d4 : 00000000`00000030 fffff98f`33cdfcc0 00000000`00000030 ffff8a87`00000000 : VBoxDrv!SUPR0PageFree+0x296b
fffff98f`33cdf980 fffff807`829fcb82 : 00000000`0022821c fffff807`88175df0 00000000`09a3f848 ffff8a87`00000030 : VBoxDrv!SUPR0IoCtlPerform+0x25a4
fffff98f`33cdfa20 fffff807`829fc7e6 : ffff8a87`189897c0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x382
fffff98f`33cdfb60 fffff807`828071b5 : ffff8a87`178f9080 fffff98f`33cdfcc0 00000000`09a3e4f8 fffff98f`33cdfbe8 : nt!NtDeviceIoControlFile+0x56
fffff98f`33cdfbd0 00007ffa`ad14c094 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000000`09a3f7a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7ffa`ad14c094
}}}

I can provide more info (just ask), perhaps even upload the memory dump for analysis, but I don't have the skills to analyze the crash dump myself.
"	Rafcio
18752	BSOD When Running VM in Windows 7	VirtualBox 6.0.8	2019-07-11T22:44:34Z	2019-07-11T22:57:54Z	2019-07-11T22:57:54Z	Upgraded from 5.2.26 to 5.2.30 and installed as admin. VBox will start fine but when I start a VM within a few seconds I get BSOD. Ran fdisk /F, looks fine. Uninstalled 5.2.30 and reinstalled 6.0.8, as admin, same issue. Uninstalled and reinstalled 5.2.26, same issue. See attache dump files. OS is Windows7 service pack 1	subrag
19079	BSOD после обновления с 5.1.22 до версии 6.0.14	VirtualBox 6.0.14	2019-11-11T12:31:07Z	2019-11-14T08:27:10Z	2019-11-14T08:27:10Z	После обновления VirtualBox с версии 5.1.22 до версии 6.0.14 на Windows 7_x64 не получается запустить ни одну из ранее установленных виртуальных машин, т.к. постоянно выскакивает BSOD. VM установлена не на системном диске.	Назаров Андрей Валерьевич
16236	Bug in the vboxdrv module (rtR0MemAllocEx) on Linux 4.8.8+ (grsecurity)	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
17359	Bug in VirtualBox 5.2.2	VirtualBox 5.2.0	2017-12-08T12:49:54Z	2017-12-08T12:49:54Z	2017-12-08T12:49:54Z	"Hello, I recently installed VirtualBox 5.2.2 on my Windows 7 laptop, but when I click on ""New"" button, VirtualBox crash.

Any help about this? ;)

PS : For the post idk about the type, component etc..."	Soren805
17727	Bug In VirtualBox in 5.2 Latest Version	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
19096	bug keyboard	VirtualBox 6.0.14	2019-11-19T20:01:48Z	2019-11-22T09:56:09Z	2019-11-22T09:56:09Z	"hello i am new, i have a problem whit virtualbox version 6.0.14, when i create the machine the keyboard key is ok, but when i restart the machine, the specificy key (point) don't function why?
Thank you soo much "	seapsi
19828	Bug virtualización por hardware	VirtualBox 6.1.10	2020-08-21T22:41:54Z	2020-08-21T22:41:54Z	2020-08-21T22:41:54Z	en maquinas donde la virtualización no es compatible, aunque no este activada no te deja guardar la configuración	MaurOwO
20210	BUG: unable to handle page fault for address: 00007efdf3ddc000	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
16104	Build 5.1.8: Cannon view or hear YouTube videos in various guests (or flash based vid)	VirtualBox 5.1.8	2016-10-22T12:25:54Z	2016-10-28T14:48:15Z	2016-10-28T14:48:15Z	"Host: Win 7 64 pro sp1: Guests: 1) ubuntu 16.04 64, 2) win 10 latest fast ring build 64. 

In either guest with all same working settings as 5.1.6 and before, I can use any available browser (chrome, firefox, or native) , bring up YouTube, choose any video, and it ""might"" show the first frame and hang there, or it might now show a frame. This is true for video & audio.

It will not play a video regardless of any other attempts on my part. I don't see anything about it showing up in logs so for now will hold off on including one. 

It just seems like a regression from the last build.

Notes: Ubuntu won't give me a screenshot that contains anything but the screen background regardless of how I select or take it.

I'm going to attempt to put my ""post-screenshot"" log here at the end:


{{{
00:00:24.411887 VMMDev: Guest Log: VBoxService 5.1.8 r111374 (verbosity: 0) linux.amd64 (Oct 18 2016 15:52:41) release log
00:00:24.411907 VMMDev: Guest Log: 00:00:00.000100 main     Log opened 2016-10-22T12:10:54.019610000Z
00:00:24.411970 VMMDev: Guest Log: 00:00:00.000182 main     OS Product: Linux
00:00:24.412011 VMMDev: Guest Log: 00:00:00.000217 main     OS Release: 4.4.0-45-generic
00:00:24.412049 VMMDev: Guest Log: 00:00:00.000248 main     OS Version: #66-Ubuntu SMP Wed Oct 19 14:12:37 UTC 2016
00:00:24.412088 VMMDev: Guest Log: 00:00:00.000278 main     Executable: /opt/VBoxGuestAdditions-5.1.8/sbin/VBoxService
00:00:24.412122 VMMDev: Guest Log: 00:00:00.000279 main     Process ID: 1053
00:00:24.412126 VMMDev: Guest Log: 00:00:00.000280 main     Package type: LINUX_64BITS_GENERIC
00:00:24.413273 VMMDev: Guest Log: 00:00:00.001226 main     5.1.8 r111374 started. Verbose level = 0
00:00:24.419240 GUI: UISession::sltAdditionsChange: GA state change event came, notifying listeners.
00:00:24.419266 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=0, Machine-state=5
00:00:24.425031 GUI: UISession::sltAdditionsChange: GA state really changed, notifying listeners.
00:00:24.425057 GUI: UIMachineViewNormal::adjustGuestScreenSize: Adjust guest-screen size if necessary.
00:00:24.425063 GUI: UISession::sltAdditionsChange: GA state change event came, notifying listeners.
00:00:24.425067 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=0, Machine-state=5
00:00:24.433624 VMMDev: Guest Log: 00:00:00.020413 automount vbsvcAutoMountWorker: Shared folder 'XPDrive' was mounted to '/media/sf_XPDrive'
00:00:24.663061 GUI: UISession::sltAdditionsChange: GA state really changed, notifying listeners.
00:00:24.663105 GUI: UIMachineViewNormal::adjustGuestScreenSize: Adjust guest-screen size if necessary.
00:00:24.663112 GUI: UISession::sltAdditionsChange: GA state change event came, notifying listeners.
00:00:24.663116 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=0, Machine-state=5
00:00:24.678804 VBVA: InfoScreen: [0] @0,0 1592x1029, line 0x18e0, BPP 32, flags 0x1
00:00:24.678851 Display::handleDisplayResize: uScreenId=0 pvVRAM=0000000010b00000 w=1592 h=1029 bpp=32 cbLine=0x18E0 flags=0x1
00:00:24.678896 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=1592x1029, Sending to async-handler
00:00:24.678959 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=1592x1029
00:00:24.678974 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=1592x1029
00:00:24.678992 GUI: UIFrameBufferPrivate::performResize: Size=1592x1029, Directly using source bitmap content
00:00:24.680061 Display::handleDisplayResize: uScreenId=0 pvVRAM=0000000010b00000 w=1592 h=1029 bpp=32 cbLine=0x18E0 flags=0x1
00:00:24.680061 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=1592x1029, Sending to async-handler
00:00:24.680754 GUI: UIMachineView::storeGuestSizeHint: Storing guest-screen size-hint for screen 0 as 1592x1029
00:00:24.699300 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=1592x1029
00:00:24.699323 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=1592x1029
00:00:24.699339 GUI: UIFrameBufferPrivate::performResize: Size=1592x1029, Directly using source bitmap content
00:00:24.699403 GUI: UIMachineView::storeGuestSizeHint: Storing guest-screen size-hint for screen 0 as 1592x1029
00:00:26.240260 DSound: Guest source 'Line In' is using host recording device with GUID '{59A1A85D-D99C-484E-82D1-6761B9C037BE}'
00:00:26.334726 DSound: Guest source 'Line In' is using host recording device with GUID '{59A1A85D-D99C-484E-82D1-6761B9C037BE}'
00:00:31.649947 DSound: Guest source 'Line In' is using host recording device with GUID '{59A1A85D-D99C-484E-82D1-6761B9C037BE}'
00:00:31.659948 DSound: Guest source 'Line In' is using host recording device with GUID '{59A1A85D-D99C-484E-82D1-6761B9C037BE}'
00:00:34.756490 VMMDev: Guest Additions capability report: (0x0 -> 0x1) seamless: yes, hostWindowMapping: no, graphics: no
00:00:34.756891 GUI: UISession::sltAdditionsChange: GA state really changed, notifying listeners.
00:00:34.756935 GUI: UIMachineViewNormal::adjustGuestScreenSize: Adjust guest-screen size if necessary.
00:00:34.756945 GUI: UISession::sltAdditionsChange: GA state change event came, notifying listeners.
00:00:34.756951 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=0, Machine-state=5
00:00:36.216479 OpenGL Info: Render SPU: GL_VENDOR:   NVIDIA Corporation
00:00:36.216499 OpenGL Info: Render SPU: GL_RENDERER: GeForce GTX 650 Ti BOOST/PCIe/SSE2
00:00:36.216506 OpenGL Info: Render SPU: GL_VERSION:  4.5.0 NVIDIA 375.57
00:00:36.216515 OpenGL Info: Render SPU: GL_EXTENSIONS: GL_AMD_multi_draw_indirect GL_AMD_seamless_cubemap_per_texture GL_ARB_arrays_of_arrays GL_ARB_base_instance GL_ARB_bindless_texture GL_ARB_blend_func_extended GL_ARB_buffer_storage GL_ARB_clear_buffer_object GL_ARB_clear_texture GL_ARB_clip_control GL_ARB_color_buffer_float GL_ARB_compatibility GL_ARB_compressed_texture_pixel_storage GL_ARB_conservative_depth GL_ARB_compute_shader GL_ARB_compute_variable_group_size GL_ARB_conditional_render_inverted GL_ARB_copy_buffer GL_ARB_copy_image GL_ARB_cull_distance GL_ARB_debug_output GL_ARB_depth_buffer_float GL_ARB_depth_clamp GL_ARB_depth_texture GL_ARB_derivative_control GL_ARB_direct_state_access GL_ARB_draw_buffers GL_ARB_draw_buffers_blend GL_ARB_draw_indirect GL_ARB_draw_elements_base_vertex GL_ARB_draw_instanced GL_ARB_enhanced_layouts GL_ARB_ES2_compatibility GL_ARB_ES3_compatibility GL_ARB_ES3_1_compatibility GL_ARB_ES3_2_compatibility GL_ARB_explicit_attrib_location GL_ARB_explicit_uniform_location GL_ARB_fragment_coord_conventions GL_ARB_fragment_layer_viewport GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_framebuffer_no_attachments GL_ARB_framebuffer_object GL_ARB_framebuffer_sRGB GL_ARB_geometry_shader4 GL_ARB_get_program_binary GL_ARB_get_texture_sub_image GL_ARB_gl_spirv GL_ARB_gpu_shader5 GL_ARB_gpu_shader_fp64 GL_ARB_gpu_shader_int64 GL_ARB_half_float_pixel GL_ARB_half_float_vertex GL_ARB_imaging GL_ARB_indirect_parameters GL_ARB_instanced_arrays GL_ARB_internalformat_query GL_ARB_internalformat_query2 GL_ARB_invalidate_subdata GL_ARB_map_buffer_alignment GL_ARB_map_buffer_range GL_ARB_multi_bind GL_ARB_multi_draw_indirect GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_occlusion_query2 GL_ARB_parallel_shader_compile GL_ARB_pipeline_statistics_query GL_ARB_pixel_buffer_object GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_program_interface_query GL_ARB_provoking_vertex GL_ARB_query_buffer_object GL_ARB_robust_buffer_access_behavior GL_ARB_robustness GL_ARB_sample_shading GL_ARB_sampler_objects GL_ARB_seamless_cube_map GL_ARB_seamless_cubemap_per_texture GL_ARB_separate_shader_objects GL_ARB_shader_atomic_counter_ops GL_ARB_shader_atomic_counters GL_ARB_shader_ballot GL_ARB_shader_bit_encoding GL_ARB_shader_clock GL_ARB_shader_draw_parameters GL_ARB_shader_group_vote GL_ARB_shader_image_load_store GL_ARB_shader_image_size GL_ARB_shader_objects GL_ARB_shader_precision GL_ARB_shader_storage_buffer_object GL_ARB_shader_subroutine GL_ARB_shader_texture_image_samples GL_ARB_shader_texture_lod GL_ARB_shading_language_100 GL_ARB_shading_language_420pack GL_ARB_shading_language_include GL_ARB_shading_language_packing GL_ARB_shadow GL_ARB_sparse_buffer GL_ARB_sparse_texture GL_ARB_stencil_texturing GL_ARB_sync GL_ARB_tessellation_shader GL_ARB_texture_barrier GL_ARB_texture_border_clamp GL_ARB_texture_buffer_object GL_ARB_texture_buffer_object_rgb32 GL_ARB_texture_buffer_range GL_ARB_texture_compression GL_ARB_texture_compression_bptc GL_ARB_texture_compression_rgtc GL_ARB_texture_cube_map GL_ARB_texture_cube_map_array GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_float GL_ARB_texture_gather GL_ARB_texture_mirror_clamp_to_edge GL_ARB_texture_mirrored_repeat GL_ARB_texture_multisample GL_ARB_texture_non_power_of_two GL_ARB_texture_query_levels GL_ARB_texture_query_lod GL_ARB_texture_rectangle GL_ARB_texture_rg GL_ARB_texture_rgb10_a2ui GL_ARB_texture_stencil8 GL_ARB_texture_storage GL_ARB_texture_storage_multisample GL_ARB_texture_swizzle GL_ARB_texture_view GL_ARB_timer_query GL_ARB_transform_feedback2 GL_ARB_transform_feedback3 GL_ARB_transform_feedback_instanced GL_ARB_transform_feedback_overflow_query GL_ARB_transpose_matrix GL_ARB_uniform_buffer_object GL_ARB_vertex_array_bgra GL_ARB_vertex_array_object GL_ARB_vertex_attrib_64bit GL_ARB_vertex_attrib_binding GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_vertex_type_10f_11f_11f_rev GL_ARB_vertex_type_2_10_10_10_rev GL_ARB_viewport_array GL_ARB_window_pos GL_ATI_draw_buffers GL_ATI_texture_float GL_ATI_texture_mirror_once GL_S3_s3tc GL_EXT_texture_env_add GL_EXT_abgr GL_EXT_bgra GL_EXT_bindable_uniform GL_EXT_blend_color GL_EXT_blend_equation_separate GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_compiled_vertex_array GL_EXT_Cg_shader GL_EXT_depth_bounds_test GL_EXT_direct_state_access GL_EXT_draw_buffers2 GL_EXT_draw_instanced GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXTX_framebuffer_mixed_formats GL_EXT_framebuffer_multisample_blit_scaled GL_EXT_framebuffer_object GL_EXT_framebuffer_sRGB GL_EXT_geometry_shader4 GL_EXT_gpu_program_parameters GL_EXT_gpu_shader4 GL_EXT_multi_draw_arrays GL_EXT_packed_depth_stencil GL_EXT_packed_float GL_EXT_packed_pixels GL_EXT_pixel_buffer_object GL_EXT_point_parameters GL_EXT_polygon_offset_clamp GL_EXT_provoking_vertex GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_shader_objects GL_EXT_separate_specular_color GL_EXT_shader_image_load_store GL_EXT_shader_integer_mix GL_EXT_shadow_funcs GL_EXT_stencil_two_side GL_EXT_stencil_wrap GL_EXT_texture3D GL_EXT_texture_array GL_EXT_texture_buffer_object GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_latc GL_EXT_texture_compression_rgtc GL_EXT_texture_compression_s3tc GL_EXT_texture_cube_map GL_EXT_texture_edge_clamp GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_EXT_texture_filter_anisotropic GL_EXT_texture_integer GL_EXT_texture_lod GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_object GL_EXT_texture_shared_exponent GL_EXT_texture_sRGB GL_EXT_texture_sRGB_decode GL_EXT_texture_storage GL_EXT_texture_swizzle GL_EXT_timer_query GL_EXT_transform_feedback2 GL_EXT_vertex_array GL_EXT_vertex_array_bgra GL_EXT_vertex_attrib_64bit GL_EXT_window_rectangles GL_EXT_import_sync_object GL_IBM_rasterpos_clip GL_IBM_texture_mirrored_repeat GL_KHR_context_flush_control GL_KHR_debug GL_KHR_no_error GL_KHR_robust_buffer_access_behavior GL_KHR_robustness GL_KTX_buffer_region GL_NV_alpha_to_coverage_dither_control GL_NV_bindless_multi_draw_indirect GL_NV_bindless_multi_draw_indirect_count GL_NV_bindless_texture GL_NV_blend_equation_advanced GL_NV_blend_square GL_NV_command_list GL_NV_compute_program5 GL_NV_conditional_render GL_NV_copy_depth_to_color GL_NV_copy_image GL_NV_depth_buffer_float GL_NV_depth_clamp GL_NV_draw_texture GL_NV_draw_vulkan_image GL_NV_ES1_1_compatibility GL_NV_ES3_1_compatibility GL_NV_explicit_multisample GL_NV_fence GL_NV_float_buffer GL_NV_fog_distance GL_NV_fragment_program GL_NV_fragment_program_option GL_NV_fragment_program2 GL_NV_framebuffer_multisample_coverage GL_NV_geometry_shader4 GL_NV_gpu_program4 GL_NV_internalformat_sample_query GL_NV_gpu_program4_1 GL_NV_gpu_program5 GL_NV_gpu_program5_mem_extended GL_NV_gpu_program_fp64 GL_NV_gpu_shader5 GL_NV_half_float GL_NV_light_max_exponent GL_NV_multisample_coverage GL_NV_multisample_filter_hint GL_NV_occlusion_query GL_NV_packed_depth_stencil GL_NV_parameter_buffer_object GL_NV_parameter_buffer_object2 GL_NV_path_rendering GL_NV_pixel_data_range GL_NV_point_sprite GL_NV_primitive_restart GL_NV_register_combiners GL_NV_register_combiners2 GL_NV_shader_atomic_counters GL_NV_shader_atomic_float GL_NV_shader_buffer_load GL_NV_shader_storage_buffer_object GL_NV_texgen_reflection GL_NV_texture_barrier GL_NV_texture_compression_vtc GL_NV_texture_env_combine4 GL_NV_texture_multisample GL_NV_texture_rectangle GL_NV_texture_shader GL_NV_texture_shader2 GL_NV_texture_shader3 GL_NV_transform_feedback GL_NV_transform_feedback2 GL_NV_uniform_buffer_unified_memory GL_NV_vertex_array_range GL_NV_vertex_array_range2 GL_NV_vertex_attrib_integer_64bit GL_NV_vertex_buffer_unified_memory GL_NV_vertex_program GL_NV_vertex_program1_1 GL_NV_vertex_program2 GL_NV_vertex_program2_option GL_NV_vertex_program3 GL_NVX_conditional_render GL_NVX_gpu_memory_info GL_NVX_multigpu_info GL_NVX_nvenc_interop GL_NV_shader_thread_group GL_NV_shader_thread_shuffle GL_KHR_blend_equation_advanced GL_SGIS_generate_mipmap GL_SGIS_texture_lod GL_SGIX_depth_texture GL_SGIX_shadow GL_SUN_slice_accum GL_WIN_swap_hint WGL_EXT_swap_control 
00:00:36.262052 OpenGL Info: Render SPU: GL_VENDOR:   NVIDIA Corporation
00:00:36.262087 OpenGL Info: Render SPU: GL_RENDERER: GeForce GTX 650 Ti BOOST/PCIe/SSE2
00:00:36.262097 OpenGL Info: Render SPU: GL_VERSION:  4.5.0 NVIDIA 375.57
00:00:36.262106 OpenGL Info: Render SPU: GL_EXTENSIONS: GL_AMD_multi_draw_indirect GL_AMD_seamless_cubemap_per_texture GL_ARB_arrays_of_arrays GL_ARB_base_instance GL_ARB_bindless_texture GL_ARB_blend_func_extended GL_ARB_buffer_storage GL_ARB_clear_buffer_object GL_ARB_clear_texture GL_ARB_clip_control GL_ARB_color_buffer_float GL_ARB_compatibility GL_ARB_compressed_texture_pixel_storage GL_ARB_conservative_depth GL_ARB_compute_shader GL_ARB_compute_variable_group_size GL_ARB_conditional_render_inverted GL_ARB_copy_buffer GL_ARB_copy_image GL_ARB_cull_distance GL_ARB_debug_output GL_ARB_depth_buffer_float GL_ARB_depth_clamp GL_ARB_depth_texture GL_ARB_derivative_control GL_ARB_direct_state_access GL_ARB_draw_buffers GL_ARB_draw_buffers_blend GL_ARB_draw_indirect GL_ARB_draw_elements_base_vertex GL_ARB_draw_instanced GL_ARB_enhanced_layouts GL_ARB_ES2_compatibility GL_ARB_ES3_compatibility GL_ARB_ES3_1_compatibility GL_ARB_ES3_2_compatibility GL_ARB_explicit_attrib_location GL_ARB_explicit_uniform_location GL_ARB_fragment_coord_conventions GL_ARB_fragment_layer_viewport GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_framebuffer_no_attachments GL_ARB_framebuffer_object GL_ARB_framebuffer_sRGB GL_ARB_geometry_shader4 GL_ARB_get_program_binary GL_ARB_get_texture_sub_image GL_ARB_gl_spirv GL_ARB_gpu_shader5 GL_ARB_gpu_shader_fp64 GL_ARB_gpu_shader_int64 GL_ARB_half_float_pixel GL_ARB_half_float_vertex GL_ARB_imaging GL_ARB_indirect_parameters GL_ARB_instanced_arrays GL_ARB_internalformat_query GL_ARB_internalformat_query2 GL_ARB_invalidate_subdata GL_ARB_map_buffer_alignment GL_ARB_map_buffer_range GL_ARB_multi_bind GL_ARB_multi_draw_indirect GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_occlusion_query2 GL_ARB_parallel_shader_compile GL_ARB_pipeline_statistics_query GL_ARB_pixel_buffer_object GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_program_interface_query GL_ARB_provoking_vertex GL_ARB_query_buffer_object GL_ARB_robust_buffer_access_behavior GL_ARB_robustness GL_ARB_sample_shading GL_ARB_sampler_objects GL_ARB_seamless_cube_map GL_ARB_seamless_cubemap_per_texture GL_ARB_separate_shader_objects GL_ARB_shader_atomic_counter_ops GL_ARB_shader_atomic_counters GL_ARB_shader_ballot GL_ARB_shader_bit_encoding GL_ARB_shader_clock GL_ARB_shader_draw_parameters GL_ARB_shader_group_vote GL_ARB_shader_image_load_store GL_ARB_shader_image_size GL_ARB_shader_objects GL_ARB_shader_precision GL_ARB_shader_storage_buffer_object GL_ARB_shader_subroutine GL_ARB_shader_texture_image_samples GL_ARB_shader_texture_lod GL_ARB_shading_language_100 GL_ARB_shading_language_420pack GL_ARB_shading_language_include GL_ARB_shading_language_packing GL_ARB_shadow GL_ARB_sparse_buffer GL_ARB_sparse_texture GL_ARB_stencil_texturing GL_ARB_sync GL_ARB_tessellation_shader GL_ARB_texture_barrier GL_ARB_texture_border_clamp GL_ARB_texture_buffer_object GL_ARB_texture_buffer_object_rgb32 GL_ARB_texture_buffer_range GL_ARB_texture_compression GL_ARB_texture_compression_bptc GL_ARB_texture_compression_rgtc GL_ARB_texture_cube_map GL_ARB_texture_cube_map_array GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_float GL_ARB_texture_gather GL_ARB_texture_mirror_clamp_to_edge GL_ARB_texture_mirrored_repeat GL_ARB_texture_multisample GL_ARB_texture_non_power_of_two GL_ARB_texture_query_levels GL_ARB_texture_query_lod GL_ARB_texture_rectangle GL_ARB_texture_rg GL_ARB_texture_rgb10_a2ui GL_ARB_texture_stencil8 GL_ARB_texture_storage GL_ARB_texture_storage_multisample GL_ARB_texture_swizzle GL_ARB_texture_view GL_ARB_timer_query GL_ARB_transform_feedback2 GL_ARB_transform_feedback3 GL_ARB_transform_feedback_instanced GL_ARB_transform_feedback_overflow_query GL_ARB_transpose_matrix GL_ARB_uniform_buffer_object GL_ARB_vertex_array_bgra GL_ARB_vertex_array_object GL_ARB_vertex_attrib_64bit GL_ARB_vertex_attrib_binding GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_vertex_type_10f_11f_11f_rev GL_ARB_vertex_type_2_10_10_10_rev GL_ARB_viewport_array GL_ARB_window_pos GL_ATI_draw_buffers GL_ATI_texture_float GL_ATI_texture_mirror_once GL_S3_s3tc GL_EXT_texture_env_add GL_EXT_abgr GL_EXT_bgra GL_EXT_bindable_uniform GL_EXT_blend_color GL_EXT_blend_equation_separate GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_compiled_vertex_array GL_EXT_Cg_shader GL_EXT_depth_bounds_test GL_EXT_direct_state_access GL_EXT_draw_buffers2 GL_EXT_draw_instanced GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXTX_framebuffer_mixed_formats GL_EXT_framebuffer_multisample_blit_scaled GL_EXT_framebuffer_object GL_EXT_framebuffer_sRGB GL_EXT_geometry_shader4 GL_EXT_gpu_program_parameters GL_EXT_gpu_shader4 GL_EXT_multi_draw_arrays GL_EXT_packed_depth_stencil GL_EXT_packed_float GL_EXT_packed_pixels GL_EXT_pixel_buffer_object GL_EXT_point_parameters GL_EXT_polygon_offset_clamp GL_EXT_provoking_vertex GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_shader_objects GL_EXT_separate_specular_color GL_EXT_shader_image_load_store GL_EXT_shader_integer_mix GL_EXT_shadow_funcs GL_EXT_stencil_two_side GL_EXT_stencil_wrap GL_EXT_texture3D GL_EXT_texture_array GL_EXT_texture_buffer_object GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_latc GL_EXT_texture_compression_rgtc GL_EXT_texture_compression_s3tc GL_EXT_texture_cube_map GL_EXT_texture_edge_clamp GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_EXT_texture_filter_anisotropic GL_EXT_texture_integer GL_EXT_texture_lod GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_object GL_EXT_texture_shared_exponent GL_EXT_texture_sRGB GL_EXT_texture_sRGB_decode GL_EXT_texture_storage GL_EXT_texture_swizzle GL_EXT_timer_query GL_EXT_transform_feedback2 GL_EXT_vertex_array GL_EXT_vertex_array_bgra GL_EXT_vertex_attrib_64bit GL_EXT_window_rectangles GL_EXT_import_sync_object GL_IBM_rasterpos_clip GL_IBM_texture_mirrored_repeat GL_KHR_context_flush_control GL_KHR_debug GL_KHR_no_error GL_KHR_robust_buffer_access_behavior GL_KHR_robustness GL_KTX_buffer_region GL_NV_alpha_to_coverage_dither_control GL_NV_bindless_multi_draw_indirect GL_NV_bindless_multi_draw_indirect_count GL_NV_bindless_texture GL_NV_blend_equation_advanced GL_NV_blend_square GL_NV_command_list GL_NV_compute_program5 GL_NV_conditional_render GL_NV_copy_depth_to_color GL_NV_copy_image GL_NV_depth_buffer_float GL_NV_depth_clamp GL_NV_draw_texture GL_NV_draw_vulkan_image GL_NV_ES1_1_compatibility GL_NV_ES3_1_compatibility GL_NV_explicit_multisample GL_NV_fence GL_NV_float_buffer GL_NV_fog_distance GL_NV_fragment_program GL_NV_fragment_program_option GL_NV_fragment_program2 GL_NV_framebuffer_multisample_coverage GL_NV_geometry_shader4 GL_NV_gpu_program4 GL_NV_internalformat_sample_query GL_NV_gpu_program4_1 GL_NV_gpu_program5 GL_NV_gpu_program5_mem_extended GL_NV_gpu_program_fp64 GL_NV_gpu_shader5 GL_NV_half_float GL_NV_light_max_exponent GL_NV_multisample_coverage GL_NV_multisample_filter_hint GL_NV_occlusion_query GL_NV_packed_depth_stencil GL_NV_parameter_buffer_object GL_NV_parameter_buffer_object2 GL_NV_path_rendering GL_NV_pixel_data_range GL_NV_point_sprite GL_NV_primitive_restart GL_NV_register_combiners GL_NV_register_combiners2 GL_NV_shader_atomic_counters GL_NV_shader_atomic_float GL_NV_shader_buffer_load GL_NV_shader_storage_buffer_object GL_NV_texgen_reflection GL_NV_texture_barrier GL_NV_texture_compression_vtc GL_NV_texture_env_combine4 GL_NV_texture_multisample GL_NV_texture_rectangle GL_NV_texture_shader GL_NV_texture_shader2 GL_NV_texture_shader3 GL_NV_transform_feedback GL_NV_transform_feedback2 GL_NV_uniform_buffer_unified_memory GL_NV_vertex_array_range GL_NV_vertex_array_range2 GL_NV_vertex_attrib_integer_64bit GL_NV_vertex_buffer_unified_memory GL_NV_vertex_program GL_NV_vertex_program1_1 GL_NV_vertex_program2 GL_NV_vertex_program2_option GL_NV_vertex_program3 GL_NVX_conditional_render GL_NVX_gpu_memory_info GL_NVX_multigpu_info GL_NVX_nvenc_interop GL_NV_shader_thread_group GL_NV_shader_thread_shuffle GL_KHR_blend_equation_advanced GL_SGIS_generate_mipmap GL_SGIS_texture_lod GL_SGIX_depth_texture GL_SGIX_shadow GL_SUN_slice_accum GL_WIN_swap_hint WGL_EXT_swap_control 
00:00:41.700223 DSound: Guest source 'Line In' is using host recording device with GUID '{59A1A85D-D99C-484E-82D1-6761B9C037BE}'
00:00:41.710224 DSound: Guest source 'Line In' is using host recording device with GUID '{59A1A85D-D99C-484E-82D1-6761B9C037BE}'
}}}

"	Papolytic
16488	Build errors on MacOS Sierra	VirtualBox 5.1.14	2017-02-16T04:04:40Z	2017-02-16T04:04:40Z	2017-02-16T04:04:40Z	"https://www.virtualbox.org/browser/vbox/trunk/configure#L2327 checks `uname -r` but for me this reports 16.4.0

Not sure if there will be other errors in the toolchain, I'm going to attempt to apply trivial / obvious changes and see what happens."	rss
18583	building virtualbox without opengl on server without X11	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
16148	CAINE 8 VGA does not work fine	VirtualBox 5.1.8	2016-11-04T10:51:39Z	2016-11-04T10:51:39Z	2016-11-04T10:51:39Z	VirtualBox today (3/Nov/2016) doesn't work fine with CAINE 8.0 (VGA and connection issues)	fgomeza
16690	calculate required temp storage and check available storage before merging snapshots	VirtualBox 5.1.20	2017-04-24T07:12:04Z	2017-04-24T07:12:04Z	2017-04-24T07:12:04Z	"Hi there,

snapshots are a grate tool for tracking down changes and secure rolling them back. But they can become very memory consuming. If you run out off disk memory while your vm is running that isn't a big problem. The vm is getting paused and you can free up some memory and resume it afterwards without problems. But if want to free up some disk space you would probably just like to get rid of some old snapshots. But while doing that the merge process will take up first much more temp memory while doing that. The problem is if you run out of memory then you'll get a much bigger problem because it will brake your whole configuration and you have to manually do changes in the xml styled .vbox file to fix them up again. 

So could you please calculate the maximum temp space which could be needed to merge snapshots and asking the user if they really want to do it before starting if there isn't enough space left.

And if you run out of space while merging/deleting snapshots please do something that wouldn't crash the whole process with an unusable vm afterwards but maybe pause the process until the user freed up enough space and/or rollback to the last stable state on auto.

It would be also nice to have a feature to delete more then one snapshot at once (while efferently doing that, so dont waste resources while merging with another snapshot that is going to be deleted anyways)


Thanks in advance

"	treaki
16289	Camera access not working	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
16742	can connect to virtual usb3 port. can not connect to virtual usb2 port.	VirtualBox 5.1.22	2017-05-08T12:08:28Z	2017-05-08T12:08:28Z	2017-05-08T12:08:28Z	"Virtualbox-5.1.23-115260-OSX also, 5.1.18 and 5.1.22

when the usb controller is set to usb3, connected a thumb drive works fine. when set to usb2, it cant connect. the error is in the last line of the included log file.

this ticket seems relevant, https://www.virtualbox.org/ticket/15050"	pixelfairy
15649	Can no longer switch screens using mini toolbar	VirtualBox 5.1.0	2016-07-20T14:19:07Z	2022-08-22T13:55:20Z	2022-08-22T13:55:20Z	"I just upgraded to v5.1 and can no longer switch screens using the mini-toolbar command '''View | Virtual Screen 1 | Use Host Screen X'''. I am running the VM in full screen mode. When I choose ""Use Host Screen 2"" nothing happens. No errors.

I can switch out of full screen mode, I can drag the VM to my second monitor and reenter full screen mode. But moving the VM to another monitor via. the mini toolbar menu no longer works for me.

Windows 8.1 host with multiple monitors

Windows 7 VM, with a single monitor

"	s23ayers
17898	Can Not Assign More Than 8 Processors to Windows 10 Guest	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
14825	Can not delete iscsi harddisk	VirtualBox 5.0.10	2015-11-14T10:32:14Z	2015-11-20T08:56:17Z	2015-11-20T08:56:17Z	"I have some trouble with deleting an iscsi disk in virtualbox. Also it is not possible to add the same iscsi disk to another virtual server. It does not matter if the first is powerd of or not. I get an error
because a hard disk '192.168.1.8|iqn.2015-11.priv.thuis:target00' with UUID {fe6776f8-25fa-4b1c-b96e-e16afd633817} already exists

What i did:
{{{
VBoxManage storageattach iscsi-client --storagectl SATA --medium iscsi --port 1 --type hdd --server 192.168.1.8 --target iqn.2015-11.priv.thuis:target00
}}}
Because i did forget to add the username password
I did delete the disk using the GUI.

I try to re-enter it with:
{{{
VBoxManage storageattach iscsi-client --storagectl SATA --medium iscsi --port 1 --type hdd --server 192.168.1.8 --target iqn.2015-11.priv.thuis:target00 --username user --password pass
}}}
I get:
{{{
Cannot register the hard disk '192.168.1.8|iqn.2015-11.priv.thuis:target00' {84b04650-7ac5-4b08-852b-0e4713e88f94} because a hard disk '192.168.1.8|iqn.2015-11.priv.thuis:target00' with UUID {fe6776f8-25fa-4b1c-b96e-e16afd633817} already exists
VBoxManage.exe: error: Details: code E_INVALIDARG (0x80070057), component VirtualBoxWrap, interface IVirtualBox, callee IUnknown
VBoxManage.exe: error: Context: ""CreateMedium(Bstr(""iSCSI"").raw(), bstrISCSIMedium.raw(), AccessMode_ReadWrite, DeviceType_HardDisk, pMedium2Mount.asOutParam())"" at line 608 of file VBoxManageStorageController.cpp

C:\Program Files\Oracle\VirtualBox>vboxmanage list hdds
UUID:           7d29ac59-43b0-4595-a7dc-e5b87033ff8c
Parent UUID:    base
State:          created
Type:           normal (base)
Location:       D:\VMs\Windows 7-32\Windows 7.vdi
Storage format: VDI
Capacity:       25600 MBytes
Encryption:     disabled

UUID:           274c38c6-e931-4a8f-acdf-89436214c23c
Parent UUID:    base
State:          created
Type:           normal (base)
Location:       D:\VMs\CoovaChilli-Deb1386\Debian i386-disk1.vmdk
Storage format: VMDK
Capacity:       8192 MBytes
Encryption:     disabled

UUID:           24e8290b-c1d3-4cea-ab97-05e76c26b0a3
Parent UUID:    base
State:          created
Type:           normal (base)
Location:       D:\VMs\ubuntu i386\ubuntu i386.vdi
Storage format: VDI
Capacity:       8192 MBytes
Encryption:     disabled

UUID:           b72048bf-1990-4325-b7b5-1cfee0606d38
Parent UUID:    base
State:          created
Type:           normal (base)
Location:       D:\VMs\Windows 7-64\Windows 7-64.vdi
Storage format: VDI
Capacity:       25600 MBytes
Encryption:     disabled

UUID:           f379e8af-2580-4a26-b0cc-97fa8f303883
Parent UUID:    base
State:          created
Type:           normal (base)
Location:       D:\VMs\Ubuntu-server-14.04-64\Ubuntu-server-14.04-64.vdi
Storage format: VDI
Capacity:       8192 MBytes
Encryption:     disabled

UUID:           b0e885be-4407-44bc-89e5-589301fc311d
Parent UUID:    base
State:          created
Type:           normal (base)
Location:       D:\VMs\Debian 8 64\Debian 8 64.vdi
Storage format: VDI
Capacity:       8192 MBytes
Encryption:     disabled

UUID:           268f19c2-529a-411f-9334-9066a3074ad6
Parent UUID:    base
State:          created
Type:           normal (base)
Location:       D:\VMs\Debian 8 32\Debian 8 32.vdi
Storage format: VDI
Capacity:       8192 MBytes
Encryption:     disabled

UUID:           30cb79f9-1367-4ed6-802d-54682076a9d7
Parent UUID:    base
State:          created
Type:           normal (base)
Location:       D:\VMs\Zoneminder-1.25.0-Ubuntu-12.04.1-LTS\Zoneminder-1.25.0-Ubuntu-12.04.vmdk
Storage format: VMDK
Capacity:       20480 MBytes
Encryption:     disabled

UUID:           38a669e0-d520-4579-873d-14dd5a208d8e
Parent UUID:    base
State:          created
Type:           normal (base)
Location:       D:\VMs\Samba-1\Debian 8 64-disk2.vmdk
Storage format: VMDK
Capacity:       8192 MBytes
Encryption:     disabled

UUID:           336b4971-4929-446f-9f8b-777d031b5299
Parent UUID:    base
State:          created
Type:           normal (base)
Location:       D:\VMs\Samba-2\Debian 8 64-disk2.vmdk
Storage format: VMDK
Capacity:       8192 MBytes
Encryption:     disabled

UUID:           c2b87337-d0d9-4812-9c9d-0412fc0cb206
Parent UUID:    base
State:          created
Type:           normal (base)
Location:       D:\VMs\iscsi-client\Debian 8 64-disk2.vmdk
Storage format: VMDK
Capacity:       8192 MBytes
Encryption:     disabled

UUID:           9215613d-762e-486f-a314-280751d1a933
Parent UUID:    base
State:          created
Type:           normal (base)
Location:       D:\VMs\iscsi-target\Debian 8 64-disk2.vmdk
Storage format: VMDK
Capacity:       8192 MBytes
Encryption:     disabled

UUID:           747eb50d-4b9a-47ff-bc95-0da5154f2ccc
Parent UUID:    base
State:          created
Type:           normal (base)
Location:       D:\VMs\iscsi-target\iSCSITarget1.vdi
Storage format: VDI
Capacity:       8192 MBytes
Encryption:     disabled

UUID:           80501db1-5695-4330-9929-71992395d127
Parent UUID:    base
State:          created
Type:           normal (base)
Location:       D:\VMs\FreeNAS\FreeNAS.vdi
Storage format: VDI
Capacity:       8192 MBytes
Encryption:     disabled

UUID:           cd38abf5-7ca1-47fd-bc3d-6de6685cf692
Parent UUID:    base
State:          created
Type:           normal (base)
Location:       D:\VMs\Werk\Debian 8 64-disk2.vmdk
Storage format: VMDK
Capacity:       8192 MBytes
Encryption:     disabled


C:\Program Files\Oracle\VirtualBox>
}}}
The disk is not in the list !!!
? Why can i not add it then ?


When i try to delete it with:
{{{
C:\Program Files\Oracle\VirtualBox>vboxmanage closemedium disk {fe6776f8-25fa-4b1c-b96e-e16afd633817}
VBoxManage.exe: error: The given path '{fe6776f8-25fa-4b1c-b96e-e16afd633817}' is not fully qualified
VBoxManage.exe: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component MediumWrap, interface IMedium, callee IUnknown
VBoxManage.exe: error: Context: ""OpenMedium(Bstr(pszFilenameOrUuid).raw(), enmDevType, enmAccessMode, fForceNewUuidOnOpen, pMedium.asOutParam())"" at line 178 of file VBoxManageDisk.cpp
}}}
I have looked at the internet and forums for answers on this issue.
I did not find a good solution

Is this a bug.


Or have i have to do it in some special way

I also want to use iscsi for two hosts, with one disk. If one fails i can start the other one automatically. (2 hosts one up, one down with one storage)


Thanks.

Erik
"	ED
19810	"Can not run any VM's ""Error relaunching VirtualBox VM process: 5"""	VirtualBox 6.0.14	2020-08-13T01:14:11Z	2020-08-13T01:14:11Z	2020-08-13T01:14:11Z	"I get the Error ""Error relaunching VirtualBox VM process:5"" when trying to launch any VM. I have added to ticket number 17849 as this describes a similar problem. However it seems to reference a different file. The file that my logs indicate seems to be a microsoft file which I wouldn't be able to remove. The last time I used the VM's everything was fine. I tried to update to the latest version and this problem started. I've uninstalled and reinstalled the previous version but I still have the issue. The line that shows the error reads as follows:

{{{
a28.27b0: supR3HardenedWinVerifyCacheProcessImportTodos: 'rpcrt4.dll' -> '\Device\HarddiskVolume4\Windows\System32\rpcrt4.dll' [rcNtRedir=0xc0150008]
a28.27b0: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\rpcrt4.dll [lacks WinVerifyTrust]
a28.27b0: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\System32\ntdll.dll (Input=ntdll.dll, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
a28.27b0: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffd78a60000 'C:\WINDOWS\System32\ntdll.dll'
a28.27b0: Error -104 in supR3HardenedWinReSpawn! (enmWhat=5)
a28.27b0: Error relaunching VirtualBox VM process: 5
Command line: '60eaff78-4bdd-042d-2e72-669728efd737-suplib-3rdchild --comment ""Server 2003"" --startvm 192061b8-05a6-407d-ad04-f630af1563c5 --no-startvm-errormsgbox ""--sup-hardening-log=D:\VirtualBox VMs\Server 2003\Logs\VBoxHardening.log""'
a28.27b0: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'opengl32.dll'.
}}}

There also seems to be a lot of lines appended with ""lacks WinVerifyTrust"" and I dont know if this is also an issue


"	Figgis
17760	"can not start the vm and get the error ""VCPU0: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)"""	VirtualBox 5.2.12	2018-05-12T22:19:42Z	2018-05-14T14:15:32Z	2018-05-14T14:15:32Z	"Hi,

I created a centos 7.4 virtual machine. After creating, it works ok under virtual box. However it randomly can not start and the log complains below error: 
VCPU0: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)

Attached please find the log file and the screenshot image. 

Thanks,
Shifeng"	shzhang
19826	Can only attach USB Scanner 1st Time Virtual Machine started	VirtualBox 6.1.10	2020-08-21T15:37:58Z	2020-08-22T17:35:18Z	2020-08-22T17:35:18Z	"Environment:  Fedora 31, kernel 5.7.11, virtualbox 6.1.12_139181, Epson V500 USB scanner.
Not sure when problem started as both kernel and virtualbox have had updates over last several months and hadn't used that specific VM for over a month when problem first noticed.  It is possible the Virtual Machine additions on the Win 10 VM may have been upgraded also during the last 2 months.

After a Fedora reboot, a new user login, and starting a Win10 virtual machine under VirtualBox,   Devices -> USB always shows the scanner (and several other USB devices).  Scanner can be checked and attached to VM and  successfully used.   Once the VM is shutdown, the next time it is started under the same Fedora user login session, none of the USB devices show up as either attached or available, and the scanner can't be added to the VM. 
  
If you logoff the current Linux user and login again, the USB devices can again be seen for the VirtualBox VM (via Devices -> USB) when the VB VM is started, and the scanner can be attached and used successfully.   It's as if something in VB related to the USB interfaces is not getting properly handled when a VM is terminated, preventing VB from seeing USB devices after that point.  But whatever pending USB status that is causing problems seems to be associated with the current Linux user session and gets cleaned up when that session is terminated and restarted.

When the VB USB devices can't be seen, it is still possible for a Windows 10 Virtual Machine running under Fedora Boxes to attach and successfully use the same USB scanner using the same scanner application, and that Boxes VM can be stopped and restarted without causing USB problems.  That would suggest this is not a hardware issue with USB interface or the scanner."	jce_vb
18310	Can't change display settings in an Oracle Linux 6.5 guest	VirtualBox 6.0.0	2019-01-14T07:42:32Z	2019-01-14T08:37:37Z	2019-01-14T08:37:37Z	I recently updated to v 6.0.0 r 127566 on Windows 10. All other guests (Debian Linux distros & earlier Windows versions) work fine, except Oracle Linux 6.5. Display becomes garbled when trying to change the resolution after installing the Guest Addition.	whosnick
15229	Can't clone with name of deleted VM / clone	VirtualBox 5.0.16	2016-03-09T20:35:09Z	2016-03-09T20:35:09Z	2016-03-09T20:35:09Z	"There's something in the Virtualbox internal resources / information that persists when one deletes
the VM files manually (using OS operations), at least on MacOS.
This might have been a mistake, so there should be a way to recover via restoring
the files / directories and re-initializing the VM from recovered files,
but it might have been purposeful / the result of a bug
or failure that you *don't* want to restore (or don't care to) the missing VM.
So, there should be some way to recover by eliminating any knowledge of that VM name,
so that you can re-use it for another clone.
"	SteveCat
15004	Can't compile Virtual Box on Mac OS X El Capitan	VirtualBox 5.0.12	2016-01-03T17:26:44Z	2018-10-02T08:40:00Z	2018-10-02T08:40:00Z	"Hello there,

  I made the Virtual Box source code checkout (svn ....), then I followed the instructions to build Virtual Box on Mac OS X (as from here: https://www.virtualbox.org/wiki/Mac%20OS%20X%20build%20instructions ), but the configure has instructions for older versions only, so it can't ""detect"" the new version, so I modified the configure and ""hardcoded"" the ""detection"" of 10.15, the path to Xcode and the MacOSX10.11.sdk path, and added the path to the openssl lib with --with-openssl-dir=..., then the configure script executed ok, but when I executed kmk command, there was no kmk executable, so I made a checkout of the source code as instructed here http://trac.netlabs.org/kbuild/wiki/Download, but I had trouble compiling it, so I downloaded the source code of  Virtual Box (VirtualBox-5.0.2.tar.bz2), extracted, modified the configure file, executed it, then issued kmk, and it failed saying that I had not a compatible Xcode, then I edited the Config.kmk, ""hardcoded"" the Xcode version (7.2), executed it again, then it started building, but failed because it was not able to figure out the compilers (wanted the gcc ones version 4.2).
Please, someone there update a Mac machine to OS X El Capitan and Xcode to 7.2 version and update the kbuild files to deal with Xcode 7.2.
Also, Xcode now has multiples platforms sdks, so the path to the Mac OS X Sdk is now a bit longer."	Enclle
17816	Can't connect to on Linux guest from Windows via host-only network	VirtualBox 5.2.12	2018-06-12T11:20:47Z	2018-06-12T17:32:08Z	2018-06-12T17:32:08Z	"I have an Ubuntu VM that runs a MySQL server among other things. I connect to it from different host systems - macOS, Windows.

For some unknown reason the host system can no longer connect to the server (mysql says ""connection refused""). I'm connecting through a host-only network via 192.168.56.101. I can ping this IP address without problems.

I have no idea why it stopped working. I did not change any configuration. Deleting and re-creating the host-only network doesn't solve the issue. 

I'm not a networking expert, I have no knowledge of debugging this sort of issues. I was hoping that you could fix this bug."	szx
4290	Can't create hard links on a shared folder (= can't use zsh if home directory is shared folder)	VirtualBox 2.2.4	2009-06-23T19:10:27Z	2020-04-28T09:59:37Z	2020-04-28T09:59:37Z	"It seems the shared folders do not allow hard links to be created (link() system call). The result is always EPERM, Operation not permitted. A simple ""touch foo; ln foo bar"" on a shared folder will demonstrate the problem. This is with VirtualBox 2.2.4 on Mac OS X 10.4.11 host, Linux 64-bit client (tried both Ubuntu 8.04 LTS Server x86-64 and Scientific Linux 4.8 x86-64 (a RHEL4 variant)).

The way I actually noticed was that the zsh delivered with scientific linux (zsh 4.2.0) tries to create a history lock file with link() and fails - and goes into an infinite loop. There's no such problem with the ubuntu version though (zsh 4.3.4). This makes it rather more difficult to use zsh as a login shell :-) I'll see if I can coax it to not use that way of locking.

However, hard linking support would be nice."	lat
3163	Can't create snapshots when ~/Library/VirtualBox is a symlink	VirtualBox 2.1.2	2009-01-25T19:44:11Z	2009-11-11T20:28:51Z	2009-11-11T20:28:51Z	"Hi,

I have had the following setup on my machine to be able to switch between different versions of VirtualBox easily:


{{{
local-admins-macbook-pro:Library lars$ pwd
/Users/lars/Library
local-admins-macbook-pro:Library lars$ ls -al
total 40
.
.
.
lrwxr-xr-x    1 lars  staff    17 25 Jan 01:32 VirtualBox -> VirtualBox 2.0.6/
drwxr-xr-x   14 lars  staff   476 25 Jan 02:49 VirtualBox 2.0.6
drwxr-xr-x   13 lars  staff   442 18 Dez 11:56 VirtualBox 2.1.0
drwxr-xr-x   13 lars  staff   442 24 Jan 23:28 VirtualBox 2.1.2
.
.
.
local-admins-macbook-pro:Library lars$ 

}}}

Everything is working in that kind of setup so far but I noticed that I am no longer able to save snapshots, when trying I get the following error message:

Failed to create a snapshot of the virtual machine Windows XP Professional.
Result Code: Unknown Status 0xBFFFCBD4

However, after reverting to a setup without a symlink (e.g. removing the symlink and renaming the directory ""VirtualBox 2.0.6"" to just ""VirtualBox"" everything works again"	Lars Sonchocky-Helldorf
21098	Can't create VDI file from external hard drive	VirtualBox 6.1.38	2022-09-06T18:59:56Z	2022-09-06T18:59:56Z	2022-09-06T18:59:56Z	"System: Ubuntu Studio 22.04.1 LTS (Jammy Jellyfish)

Trying to create a VDI file from an old hard drive.  The hard drive sits in a USB cradle and shows up as an external drive at /dev/sba.
When the process starts, VBoxManage creates the VDI file in the folder, but after a long time of processing, the VDI file is deleted at the end.

Any ideas are appreciated."	Artotrogus
10195	Can't delete snapshot in 4.1.8	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
16984	Can't enter encryption password  OSX 10.12.5	VirtualBox 5.1.26	2017-08-06T11:53:17Z	2017-08-30T11:21:23Z	2017-08-30T11:21:23Z	"Hello,

Every machine that using a saved state + virtual encryption, can't be unlocked.  Either no password prompt shows up or the password prompt that appears does not allow any typing in it (can't be clicked).

Only solution for now is to discard the saved state and start up normally.

Another remark:  When pausing a VM, no password has to be entered to unlock/decrypt, ideally behaviour should be the same then we starting/starting from saved state.


"	Neekoh
15794	Can't install ReactOS	VirtualBox 5.1.2	2016-08-15T08:33:05Z	2016-08-15T08:33:05Z	2016-08-15T08:33:05Z	I try to install ReactOS 0.4.1 at VirtualBox 5.1.2 on Windows Thin PC SP1 without success. When I start machineI got error immediately.	luk3Z
16223	Can't install VirtualBox on Windows 10	VirtualBox 5.1.10	2016-11-24T09:17:03Z	2016-11-24T09:17:03Z	2016-11-24T09:17:03Z	"I have problem installing VirtualBox-5.1.11-112066-Win.exe Test Build, also VirtualBox-5.1.10-112026-Win.exe

Installer Log is attached"	jovanMeshkov
10759	Can't kill Virtualbox.exe process	VirtualBox 4.1.18	2012-07-13T20:31:09Z	2016-02-23T02:41:25Z	2016-02-23T02:41:25Z	"Windows 7 64 bit Host.
Ubuntu 11.10. OS will lock when running certain programs and the virtualbox.exe process will keep running at 25% cpu. Can't kill it in the command line or in task Manager. Only option is to reboot the host Windows 7. "	speedkills20
18025	Can't launch VirtualBox 5.2.18-1 on fedora 28.	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
19798	Can't load my document	VirtualBox 6.1.10	2020-08-06T17:41:37Z	2020-08-06T17:41:37Z	2020-08-06T17:41:37Z	This is my first time using the software and I can't seem to get my document to open.	TeamBsi
15931	can't load windows 7 on virtualbox after moving virtual machine	VirtualBox 5.1.6	2016-09-14T12:50:37Z	2016-09-14T12:50:37Z	2016-09-14T12:50:37Z	"hello, 
i had vbox installed on win7 and i had a win7 vm workining well.
then i moved the vm to another host (win10) by moving all the folder. 
i added the vm, when i start the vm i see the win7 loading screen, then the vm crash and start again in loop.
i triend even with vbox 5.1.6 and vbox 5.1.7, same result

could you help me please?
thanks"	niconico999
17828	Can't move media due to out of memory errors	VirtualBox 5.2.12	2018-06-18T19:05:10Z	2020-04-17T05:35:22Z	2020-04-17T05:35:22Z	"I'm attempting to move media using the Virtual Media Manager, and getting VERR_NO_MEMORY messages, even when I have a good few gigabytes of RAM free, and no VMs running.

Seems to happen to some (not all) snapshots, so now I have them sprinkled across two different drives.

Full messages:

Could not move medium 'D:/IE11 - Win7/{f4e5739c-1ee9-4b9b-8872-a68e8816f364}.vmdk' (VERR_NO_MEMORY).

Result Code: 
VBOX_E_FILE_ERROR (0x80BB0004)

Component: 
MediumWrap

Interface: 
IMedium {4afe423b-43e0-e9d0-82e8-ceb307940dda}

"	morungos
19330	Can't push Next button when VirtualBox Manager Import Virtual Appliance in  large zoom display setting	VirtualBox 6.1.4	2020-02-21T06:42:01Z	2020-02-21T06:42:01Z	2020-02-21T06:42:01Z	"I am using surface pro 7 with display 300% scale setting.
When Virtualbox Manager -> ""Import Virtual Appliance"", I can't push ""Next"" button because ""Import Virtual Appliance"" window is very large and some buttons appear out of display(attached virualbox6.1.4-scale300%.PNG).

This problem occurs with version 6.1.X, not occurs with version 6.0.X(attached virtual6.0.16-scale300%.PNG).

Of course, I don't always want to use 300%. I wanted to show that this problem occurs even on a famous PC(surface pro 7).
I usually use Fujitsu LIFEBOOK UH75/C3. In this Laptop PC, this problem occurs in its default scale(150%) and not occurs in 125% or less.

Fujits LIFEBOOK UH75/C3: 13.3in(1920 x 1080)
Surface Pro 7 12.3in(2736 x 1824)
Windows 10(1903)
"	TT
17113	Can't reboot after changing windows 10 display resolution on ubuntu-16.04 and virtualbox-5.1.28	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
18479	Can't restart saved state on Windows 10. Exception breakpoint 0x80000003	VirtualBox 6.0.4	2019-03-07T09:50:31Z	2019-03-08T06:02:22Z	2019-03-08T06:02:22Z	"Hi,

I'm running Virtualbox on a Windows 10 64b Pro 1803, and operating with a ""IE 10 - Win 7"" VM (downloaded on Virtualbox site a long time ago), NAT connection and Guest Add-ons installed.
The VM runs perfectly well, but if I stop it via Saving State and try to re-open it I systematically have a crash error. The session is then marked as Aborted and If I start it again it works (I have to start Windows via the ""BIOS"" ""Start windows normally"" menu option, though).
Is there any way I can solve this ?

I've seen in the tickets some which refer to that same breakpoint but they don't seem to apply to my case.

I attached :
- VBox.log
- VBoxHardening.log
- Screenshots of the various error messages I get

Thanks in advance."	jeanmiraptor
18004	Can't restore state of Windows XP guest machine when playing games	VirtualBox 5.2.18	2018-09-23T08:33:53Z	2018-09-23T08:33:53Z	2018-09-23T08:33:53Z	"Hello.

I have a '''Windows XP SP3 guest machine'''. It's running fine and I can pause it, close (with saving state option) and restore it when I'm in desktop.

When I play games and I want to do the same, '''I'm getting error (unknown software exception) in application in localization'''. 

'''So what I'm doing is:'''
1. Start the game.
2. Pause machine once games has loaded.
3. Close machine by saving its state.
4. Open machine with its saved state.

I tried two games: Superbike 2001 and International Rally Championship. Both produce similar error."	Mtik
21235	Can't run VBox	VirtualBox-7.0.2	2022-11-02T17:51:33Z	2022-11-02T17:51:33Z	2022-11-02T17:51:33Z	"I'm first use of vbox . I'm just download vbox and vdi image and run it. And it cause this error
I don't know what type of error it is."	takriz
21335	can't see guest OS mapped network drives in File Manager - regression	VirtualBox-7.0.4	2022-12-12T15:40:17Z	2022-12-12T15:40:17Z	2022-12-12T15:40:17Z	"VB 7.0.4, W10 guest OS.
In the bridged network guest, map a drive to a server on your network - e.g., y:\\myserver\myshare.  (server credentials are different than guest OS credentials)
Start File Mgr, login - observe the Y drive is not shown.  This worked in 6.0."	Justinh
16305	Can't start session for virtual machine	VirtualBox 5.1.10	2016-12-19T06:53:30Z	2017-01-03T09:08:43Z	2017-01-03T09:08:43Z	"I've got an error: 

'''Can't start session for virtual machine'''. 

The virtual machine 'MS DOS' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'E:\VirtualBox VMs\Machines\MS DOS\Logs\VBoxHardening.log'.

Erro code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}



Host - win 7, 64bit. Guest - any vmachine (tried msdos, win xp, win 7, ubuntu and got the same error).

BUT if I start the machine in the background session and then click show (or start background session with interface) - everything works!

Tested on 5.1.10, 5.1.8, 5.1.0 and test build (5.1.11). Seems like an issue with all 5.1.x versions.

Note that 5.0.x works fine on my host."	coldshine
20427	can't start the virtual machine	VirtualBox 6.1.22	2021-06-21T16:18:33Z	2021-06-21T16:40:00Z	2021-06-21T16:40:00Z	"when i start virtual machine i have got this error

{{{
Failed to open a session for the virtual machine Mac.

Could not launch the VM process for the machine 'Mac' (VERR_INVALID_UTF16_ENCODING).

Result Code: VBOX_E_IPRT_ERROR (0x80BB0005)
Component: MachineWrap
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}

}}}

how can i fix it?

"	gihan
13625	Can't start virtualBox	VirtualBox 4.2.18	2014-11-19T16:41:16Z	2014-11-20T16:25:38Z	2014-11-20T16:25:38Z	"Échec de l'ouverture de session pour la machine virtuelle Linux Mint 17.

Failed to load VMMR0.r0 (VERR_LDR_MISMATCH_NATIVE).

Code d'erreur : E_FAIL (0x80004005)
Composant : Console
Interface : IConsole {db7ab4ca-2a3f-4183-9243-c1208da92392}

"	EricG
16000	Can't start VM	VirtualBox 5.1.6	2016-09-28T15:43:23Z	2016-09-28T15:47:54Z	2016-09-28T15:47:54Z	Can't start VM due to hardening complaints of Sophos AV	ak11
17499	Can't start vmachine, MachineWrap E_FAIL (0x80004005)	VirtualBox 5.1.22	2018-01-25T13:27:28Z	2018-01-26T10:28:13Z	2018-01-26T10:28:13Z	"Hello there.

I don't know why, but i can't even start v-box machine. It gives me this error:


{{{
The virtual machine 'TESTING' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\Admin\VirtualBox VMs\TESTING\Logs\VBoxHardening.log'.

Návratový kód: E_FAIL (0x80004005)
Komponenta: MachineWrap
Rozhraní: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
}}}

Log output:

{{{
41c.1af0: Log file opened: 5.1.22r115126 g_hStartupLog=000000000000006c g_uNtVerCombined=0xa03fab00
41c.1af0: \SystemRoot\System32\ntdll.dll:
41c.1af0:     CreationTime:    2018-01-05T15:56:46.395451500Z
41c.1af0:     LastWriteTime:   2018-01-01T12:48:26.082566200Z
41c.1af0:     ChangeTime:      2018-01-06T08:02:19.865353700Z
41c.1af0:     FileAttributes:  0x20
41c.1af0:     Size:            0x1dd100
41c.1af0:     NT Headers:      0xe0
41c.1af0:     Timestamp:       0x6dead514
41c.1af0:     Machine:         0x8664 - amd64
41c.1af0:     Timestamp:       0x6dead514
41c.1af0:     Image Version:   10.0
41c.1af0:     SizeOfImage:     0x1e0000 (1966080)
41c.1af0:     Resource Dir:    0x174000 LB 0x6a1d8
41c.1af0:     [Version info resource found at 0xd8! (ID/Name: 0x1; SubID/SubName: 0x409)]
41c.1af0:     [Raw version resource data: 0x1740f0 LB 0x380, codepage 0x0 (reserved 0x0)]
41c.1af0:     ProductName:     Microsoft® Windows® Operating System
41c.1af0:     ProductVersion:  10.0.16299.192
41c.1af0:     FileVersion:     10.0.16299.192 (WinBuild.160101.0800)
41c.1af0:     FileDescription: NT Layer DLL
41c.1af0: \SystemRoot\System32\kernel32.dll:
41c.1af0:     CreationTime:    2017-09-29T13:42:04.954227600Z
41c.1af0:     LastWriteTime:   2017-09-29T13:42:04.954227600Z
41c.1af0:     ChangeTime:      2018-01-01T19:07:46.735385400Z
41c.1af0:     FileAttributes:  0x20
41c.1af0:     Size:            0xab868
41c.1af0:     NT Headers:      0xe8
41c.1af0:     Timestamp:       0xc2cf900
41c.1af0:     Machine:         0x8664 - amd64
41c.1af0:     Timestamp:       0xc2cf900
41c.1af0:     Image Version:   10.0
41c.1af0:     SizeOfImage:     0xae000 (712704)
41c.1af0:     Resource Dir:    0xac000 LB 0x520
41c.1af0:     [Version info resource found at 0x90! (ID/Name: 0x1; SubID/SubName: 0x409)]
41c.1af0:     [Raw version resource data: 0xac0b0 LB 0x3a4, codepage 0x0 (reserved 0x0)]
41c.1af0:     ProductName:     Microsoft® Windows® Operating System
41c.1af0:     ProductVersion:  10.0.16299.15
41c.1af0:     FileVersion:     10.0.16299.15 (WinBuild.160101.0800)
41c.1af0:     FileDescription: Windows NT BASE API Client DLL
41c.1af0: \SystemRoot\System32\KernelBase.dll:
41c.1af0:     CreationTime:    2017-09-29T13:41:43.124345500Z
41c.1af0:     LastWriteTime:   2017-09-29T13:41:43.124345500Z
41c.1af0:     ChangeTime:      2018-01-01T19:07:46.829134900Z
41c.1af0:     FileAttributes:  0x20
41c.1af0:     Size:            0x266000
41c.1af0:     NT Headers:      0xf0
41c.1af0:     Timestamp:       0x4736733c
41c.1af0:     Machine:         0x8664 - amd64
41c.1af0:     Timestamp:       0x4736733c
41c.1af0:     Image Version:   10.0
41c.1af0:     SizeOfImage:     0x266000 (2514944)
41c.1af0:     Resource Dir:    0x245000 LB 0x548
41c.1af0:     [Version info resource found at 0x90! (ID/Name: 0x1; SubID/SubName: 0x409)]
41c.1af0:     [Raw version resource data: 0x2450b0 LB 0x3bc, codepage 0x0 (reserved 0x0)]
41c.1af0:     ProductName:     Microsoft® Windows® Operating System
41c.1af0:     ProductVersion:  10.0.16299.15
41c.1af0:     FileVersion:     10.0.16299.15 (WinBuild.160101.0800)
41c.1af0:     FileDescription: Windows NT BASE API Client DLL
41c.1af0: \SystemRoot\System32\apisetschema.dll:
41c.1af0:     CreationTime:    2017-09-29T13:42:07.095026600Z
41c.1af0:     LastWriteTime:   2017-09-29T13:42:07.095026600Z
41c.1af0:     ChangeTime:      2018-01-08T20:50:10.598880700Z
41c.1af0:     FileAttributes:  0x20
41c.1af0:     Size:            0x1b398
41c.1af0:     NT Headers:      0xc8
41c.1af0:     Timestamp:       0xf30abf31
41c.1af0:     Machine:         0x8664 - amd64
41c.1af0:     Timestamp:       0xf30abf31
41c.1af0:     Image Version:   10.0
41c.1af0:     SizeOfImage:     0x1c000 (114688)
41c.1af0:     Resource Dir:    0x1b000 LB 0x408
41c.1af0:     [Version info resource found at 0x48! (ID/Name: 0x1; SubID/SubName: 0x409)]
41c.1af0:     [Raw version resource data: 0x1b060 LB 0x3a8, codepage 0x0 (reserved 0x0)]
41c.1af0:     ProductName:     Microsoft® Windows® Operating System
41c.1af0:     ProductVersion:  10.0.16299.15
41c.1af0:     FileVersion:     10.0.16299.15 (WinBuild.160101.0800)
41c.1af0:     FileDescription: ApiSet Schema DLL
41c.1af0: supR3HardenedWinFindAdversaries: 0x0
41c.1af0: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64'
41c.1af0: Calling main()
41c.1af0: SUPR3HardenedMain: pszProgName=VirtualBox fFlags=0x2
41c.1af0: supR3HardenedWinInitAppBin(0x2): '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64'
41c.1af0: SUPR3HardenedMain: Respawn #1
41c.1af0: System32:  \Device\HarddiskVolume1\Windows\System32
41c.1af0: WinSxS:    \Device\HarddiskVolume1\Windows\WinSxS
41c.1af0: KnownDllPath: C:\WINDOWS\System32
41c.1af0: '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe' has no imports
41c.1af0: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe)
41c.1af0: supR3HardNtEnableThreadCreation:
41c.1af0: supR3HardNtDisableThreadCreation: pvLdrInitThunk=00007ff9560791d0 pvNtTerminateThread=00007ff9560a08c0
41c.1af0: supR3HardenedWinDoReSpawn(1): New child 2d54.35dc [kernel32].
41c.1af0: supR3HardNtChildGatherData: PebBaseAddress=000000000116e000 cbPeb=0x388
41c.1af0: supR3HardNtPuChFindNtdll: uNtDllParentAddr=00007ff956000000 uNtDllChildAddr=00007ff956000000
41c.1af0: supR3HardenedWinSetupChildInit: uLdrInitThunk=00007ff9560791d0
41c.1af0: supR3HardenedWinSetupChildInit: Start child.
41c.1af0: supR3HardNtChildWaitFor: Found expected request 0 (PurifyChildAndCloseHandles) after 0 ms.
41c.1af0: supR3HardNtChildPurify: Startup delay kludge #1/0: 263 ms, 16 sleeps
41c.1af0: supHardNtVpScanVirtualMemory: enmKind=CHILD_PURIFICATION
41c.1af0:  *0000000000000000-0000000000e5ffff 0x0001/0x0000 0x0000000
41c.1af0:  *0000000000e60000-0000000000e7ffff 0x0004/0x0004 0x0020000
41c.1af0:  *0000000000e80000-0000000000e98fff 0x0002/0x0002 0x0040000
41c.1af0:   0000000000e99000-0000000000e9ffff 0x0001/0x0000 0x0000000
41c.1af0:  *0000000000ea0000-0000000000f9afff 0x0000/0x0004 0x0020000
41c.1af0:   0000000000f9b000-0000000000f9dfff 0x0104/0x0004 0x0020000
41c.1af0:   0000000000f9e000-0000000000f9ffff 0x0004/0x0004 0x0020000
41c.1af0:  *0000000000fa0000-0000000000fa3fff 0x0002/0x0002 0x0040000
41c.1af0:   0000000000fa4000-0000000000faffff 0x0001/0x0000 0x0000000
41c.1af0:  *0000000000fb0000-0000000000fb0fff 0x0004/0x0004 0x0020000
41c.1af0:   0000000000fb1000-0000000000ffffff 0x0001/0x0000 0x0000000
41c.1af0:  *0000000001000000-000000000116dfff 0x0000/0x0004 0x0020000
41c.1af0:   000000000116e000-0000000001170fff 0x0004/0x0004 0x0020000
41c.1af0:   0000000001171000-00000000011fffff 0x0000/0x0004 0x0020000
41c.1af0:   0000000001200000-000000007ffdffff 0x0001/0x0000 0x0000000
41c.1af0:  *000000007ffe0000-000000007ffe0fff 0x0002/0x0002 0x0020000
41c.1af0:  *000000007ffe1000-000000007ffeffff 0x0000/0x0002 0x0020000
41c.1af0:   000000007fff0000-00007ff7ed97ffff 0x0001/0x0000 0x0000000
41c.1af0:  *00007ff7ed980000-00007ff7ed9a2fff 0x0002/0x0002 0x0040000
41c.1af0:   00007ff7ed9a3000-00007ff7edf0ffff 0x0001/0x0000 0x0000000
41c.1af0:  *00007ff7edf10000-00007ff7edf10fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
41c.1af0:   00007ff7edf11000-00007ff7edf80fff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
41c.1af0:   00007ff7edf81000-00007ff7edf81fff 0x0080/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
41c.1af0:   00007ff7edf82000-00007ff7edfc6fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
41c.1af0:   00007ff7edfc7000-00007ff7edfc7fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
41c.1af0:   00007ff7edfc8000-00007ff7edfc8fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
41c.1af0:   00007ff7edfc9000-00007ff7edfcdfff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
41c.1af0:   00007ff7edfce000-00007ff7edfcefff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
41c.1af0:   00007ff7edfcf000-00007ff7edfcffff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
41c.1af0:   00007ff7edfd0000-00007ff7edfd3fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
41c.1af0:   00007ff7edfd4000-00007ff7ee01bfff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
41c.1af0:   00007ff7ee01c000-00007ff955ffffff 0x0001/0x0000 0x0000000
41c.1af0:  *00007ff956000000-00007ff956000fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
41c.1af0:   00007ff956001000-00007ff956112fff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
41c.1af0:   00007ff956113000-00007ff956158fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
41c.1af0:   00007ff956159000-00007ff956160fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
41c.1af0:   00007ff956161000-00007ff95616efff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
41c.1af0:   00007ff95616f000-00007ff95616ffff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
41c.1af0:   00007ff956170000-00007ff956172fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
41c.1af0:   00007ff956173000-00007ff9561dffff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
41c.1af0:   00007ff9561e0000-00007ffffffdffff 0x0001/0x0000 0x0000000
41c.1af0:  *00007ffffffe0000-00007ffffffeffff 0x0001/0x0002 0x0020000
41c.1af0: VirtualBox.exe: timestamp 0x5903619d (rc=VINF_SUCCESS)
41c.1af0: '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe' has no imports
41c.1af0: '\Device\HarddiskVolume1\Windows\System32\ntdll.dll' has no imports
41c.1af0: supR3HardNtChildPurify: Done after 417 ms and 0 fixes (loop #0).
2d54.35dc: Log file opened: 5.1.22r115126 g_hStartupLog=0000000000000004 g_uNtVerCombined=0xa03fab00
2d54.35dc: supR3HardenedVmProcessInit: uNtDllAddr=00007ff956000000 g_uNtVerCombined=0xa03fab00
41c.1af0: supR3HardNtEnableThreadCreation:
2d54.35dc: ntdll.dll: timestamp 0x6dead514 (rc=VINF_SUCCESS)
2d54.35dc: New simple heap: #1 0000000001300000 LB 0x400000 (for 1966080 allocation)
2d54.35dc: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64'
2d54.35dc: System32:  \Device\HarddiskVolume1\Windows\System32
2d54.35dc: WinSxS:    \Device\HarddiskVolume1\Windows\WinSxS
2d54.35dc: KnownDllPath: C:\WINDOWS\System32
2d54.35dc: supR3HardenedVmProcessInit: Opening vboxdrv stub...
2d54.35dc: supR3HardenedVmProcessInit: Restoring LdrInitializeThunk...
2d54.35dc: supR3HardenedVmProcessInit: Returning to LdrInitializeThunk...
2d54.35dc: Registered Dll notification callback with NTDLL.
2d54.35dc: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\kernel32.dll)
2d54.35dc: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\kernel32.dll
2d54.35dc: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\System32\KERNEL32.DLL (Input=KERNEL32.DLL, rcNtResolve=0xc0150008) *pfFlags=0xffffffff pwszSearchPath=0000000000004001:<flags> [calling]
2d54.35dc: supR3HardenedDllNotificationCallback: load   00007ff952740000 LB 0x00266000 C:\WINDOWS\System32\KERNELBASE.dll [fFlags=0x0]
2d54.35dc: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\KernelBase.dll)
2d54.35dc: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\KernelBase.dll
2d54.35dc: supR3HardenedDllNotificationCallback: load   00007ff9556d0000 LB 0x000ae000 C:\WINDOWS\System32\KERNEL32.DLL [fFlags=0x0]
2d54.35dc: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\kernel32.dll [lacks WinVerifyTrust]
2d54.35dc: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff9556d0000 'C:\WINDOWS\System32\KERNEL32.DLL'
2d54.35dc: supR3HardenedDllNotificationCallback: load   00007ff7edf10000 LB 0x0010c000 C:\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe [fFlags=0x0]
2d54.35dc: '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe' has no imports
2d54.35dc: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe)
2d54.35dc: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
2d54.35dc: supR3HardNtDisableThreadCreation: pvLdrInitThunk=00007ff9560791d0 pvNtTerminateThread=00007ff9560a08c0
41c.1af0: supR3HardNtChildWaitFor: Found expected request 1 (CloseEvents) after 452 ms.
2d54.35dc: \SystemRoot\System32\ntdll.dll:
2d54.35dc:     CreationTime:    2018-01-05T15:56:46.395451500Z
2d54.35dc:     LastWriteTime:   2018-01-01T12:48:26.082566200Z
2d54.35dc:     ChangeTime:      2018-01-06T08:02:19.865353700Z
2d54.35dc:     FileAttributes:  0x20
2d54.35dc:     Size:            0x1dd100
2d54.35dc:     NT Headers:      0xe0
2d54.35dc:     Timestamp:       0x6dead514
2d54.35dc:     Machine:         0x8664 - amd64
2d54.35dc:     Timestamp:       0x6dead514
2d54.35dc:     Image Version:   10.0
2d54.35dc:     SizeOfImage:     0x1e0000 (1966080)
2d54.35dc:     Resource Dir:    0x174000 LB 0x6a1d8
2d54.35dc:     [Version info resource found at 0xd8! (ID/Name: 0x1; SubID/SubName: 0x409)]
2d54.35dc:     [Raw version resource data: 0x1740f0 LB 0x380, codepage 0x0 (reserved 0x0)]
2d54.35dc:     ProductName:     Microsoft® Windows® Operating System
2d54.35dc:     ProductVersion:  10.0.16299.192
2d54.35dc:     FileVersion:     10.0.16299.192 (WinBuild.160101.0800)
2d54.35dc:     FileDescription: NT Layer DLL
2d54.35dc: \SystemRoot\System32\kernel32.dll:
2d54.35dc:     CreationTime:    2017-09-29T13:42:04.954227600Z
2d54.35dc:     LastWriteTime:   2017-09-29T13:42:04.954227600Z
2d54.35dc:     ChangeTime:      2018-01-01T19:07:46.735385400Z
2d54.35dc:     FileAttributes:  0x20
2d54.35dc:     Size:            0xab868
2d54.35dc:     NT Headers:      0xe8
2d54.35dc:     Timestamp:       0xc2cf900
2d54.35dc:     Machine:         0x8664 - amd64
2d54.35dc:     Timestamp:       0xc2cf900
2d54.35dc:     Image Version:   10.0
2d54.35dc:     SizeOfImage:     0xae000 (712704)
2d54.35dc:     Resource Dir:    0xac000 LB 0x520
2d54.35dc:     [Version info resource found at 0x90! (ID/Name: 0x1; SubID/SubName: 0x409)]
2d54.35dc:     [Raw version resource data: 0xac0b0 LB 0x3a4, codepage 0x0 (reserved 0x0)]
2d54.35dc:     ProductName:     Microsoft® Windows® Operating System
2d54.35dc:     ProductVersion:  10.0.16299.15
2d54.35dc:     FileVersion:     10.0.16299.15 (WinBuild.160101.0800)
2d54.35dc:     FileDescription: Windows NT BASE API Client DLL
2d54.35dc: \SystemRoot\System32\KernelBase.dll:
2d54.35dc:     CreationTime:    2017-09-29T13:41:43.124345500Z
2d54.35dc:     LastWriteTime:   2017-09-29T13:41:43.124345500Z
2d54.35dc:     ChangeTime:      2018-01-01T19:07:46.829134900Z
2d54.35dc:     FileAttributes:  0x20
2d54.35dc:     Size:            0x266000
2d54.35dc:     NT Headers:      0xf0
2d54.35dc:     Timestamp:       0x4736733c
2d54.35dc:     Machine:         0x8664 - amd64
2d54.35dc:     Timestamp:       0x4736733c
2d54.35dc:     Image Version:   10.0
2d54.35dc:     SizeOfImage:     0x266000 (2514944)
2d54.35dc:     Resource Dir:    0x245000 LB 0x548
2d54.35dc:     [Version info resource found at 0x90! (ID/Name: 0x1; SubID/SubName: 0x409)]
2d54.35dc:     [Raw version resource data: 0x2450b0 LB 0x3bc, codepage 0x0 (reserved 0x0)]
2d54.35dc:     ProductName:     Microsoft® Windows® Operating System
2d54.35dc:     ProductVersion:  10.0.16299.15
2d54.35dc:     FileVersion:     10.0.16299.15 (WinBuild.160101.0800)
2d54.35dc:     FileDescription: Windows NT BASE API Client DLL
2d54.35dc: \SystemRoot\System32\apisetschema.dll:
2d54.35dc:     CreationTime:    2017-09-29T13:42:07.095026600Z
2d54.35dc:     LastWriteTime:   2017-09-29T13:42:07.095026600Z
2d54.35dc:     ChangeTime:      2018-01-08T20:50:10.598880700Z
2d54.35dc:     FileAttributes:  0x20
2d54.35dc:     Size:            0x1b398
2d54.35dc:     NT Headers:      0xc8
2d54.35dc:     Timestamp:       0xf30abf31
2d54.35dc:     Machine:         0x8664 - amd64
2d54.35dc:     Timestamp:       0xf30abf31
2d54.35dc:     Image Version:   10.0
2d54.35dc:     SizeOfImage:     0x1c000 (114688)
2d54.35dc:     Resource Dir:    0x1b000 LB 0x408
2d54.35dc:     [Version info resource found at 0x48! (ID/Name: 0x1; SubID/SubName: 0x409)]
2d54.35dc:     [Raw version resource data: 0x1b060 LB 0x3a8, codepage 0x0 (reserved 0x0)]
2d54.35dc:     ProductName:     Microsoft® Windows® Operating System
2d54.35dc:     ProductVersion:  10.0.16299.15
2d54.35dc:     FileVersion:     10.0.16299.15 (WinBuild.160101.0800)
2d54.35dc:     FileDescription: ApiSet Schema DLL
2d54.35dc: supR3HardenedWinFindAdversaries: 0x0
2d54.35dc: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64'
2d54.35dc: Calling main()
2d54.35dc: SUPR3HardenedMain: pszProgName=VirtualBox fFlags=0x2
2d54.35dc: supR3HardenedWinInitAppBin(0x2): '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64'
2d54.35dc: '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe' has no imports
2d54.35dc: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe)
2d54.35dc: SUPR3HardenedMain: Respawn #2
2d54.35dc: supR3HardNtEnableThreadCreation:
2d54.35dc: '\Device\HarddiskVolume1\Windows\System32\ntdll.dll' has no imports
2d54.35dc: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\ntdll.dll)
2d54.35dc: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\ntdll.dll
2d54.35dc: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\System32\ntdll.dll (Input=ntdll.dll, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
2d54.35dc: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff956000000 'C:\WINDOWS\System32\ntdll.dll'
2d54.35dc: supR3HardNtDisableThreadCreation: pvLdrInitThunk=00007ff9560791d0 pvNtTerminateThread=00007ff9560a08c0
2d54.35dc: supR3HardenedWinDoReSpawn(2): New child 2fb0.1318 [kernel32].
2d54.35dc: supR3HardenedWinReSpawn: NtSetInformationThread/ThreadHideFromDebugger failed: 0xc0000022 (harmless)
2d54.35dc: supR3HardNtChildGatherData: PebBaseAddress=00000000010b9000 cbPeb=0x388
2d54.35dc: supR3HardNtPuChFindNtdll: uNtDllParentAddr=00007ff956000000 uNtDllChildAddr=00007ff956000000
2d54.35dc: supR3HardenedWinSetupChildInit: uLdrInitThunk=00007ff9560791d0
2d54.35dc: supR3HardenedWinSetupChildInit: Start child.
2d54.35dc: supR3HardNtChildWaitFor: Found expected request 0 (PurifyChildAndCloseHandles) after 1 ms.
2d54.35dc: supR3HardNtChildPurify: Startup delay kludge #1/0: 257 ms, 15 sleeps
2d54.35dc: supHardNtVpScanVirtualMemory: enmKind=CHILD_PURIFICATION
2d54.35dc:  *0000000000000000-0000000000e8ffff 0x0001/0x0000 0x0000000
2d54.35dc:  *0000000000e90000-0000000000eaffff 0x0004/0x0004 0x0020000
2d54.35dc:  *0000000000eb0000-0000000000ec8fff 0x0002/0x0002 0x0040000
2d54.35dc:   0000000000ec9000-0000000000ecffff 0x0001/0x0000 0x0000000
2d54.35dc:  *0000000000ed0000-0000000000fcafff 0x0000/0x0004 0x0020000
2d54.35dc:   0000000000fcb000-0000000000fcdfff 0x0104/0x0004 0x0020000
2d54.35dc:   0000000000fce000-0000000000fcffff 0x0004/0x0004 0x0020000
2d54.35dc:  *0000000000fd0000-0000000000fd3fff 0x0002/0x0002 0x0040000
2d54.35dc:   0000000000fd4000-0000000000fdffff 0x0001/0x0000 0x0000000
2d54.35dc:  *0000000000fe0000-0000000000fe0fff 0x0004/0x0004 0x0020000
2d54.35dc:   0000000000fe1000-0000000000ffffff 0x0001/0x0000 0x0000000
2d54.35dc:  *0000000001000000-00000000010b8fff 0x0000/0x0004 0x0020000
2d54.35dc:   00000000010b9000-00000000010bbfff 0x0004/0x0004 0x0020000
2d54.35dc:   00000000010bc000-00000000011fffff 0x0000/0x0004 0x0020000
2d54.35dc:   0000000001200000-000000007ffdffff 0x0001/0x0000 0x0000000
2d54.35dc:  *000000007ffe0000-000000007ffe0fff 0x0002/0x0002 0x0020000
2d54.35dc:  *000000007ffe1000-000000007ffeffff 0x0000/0x0002 0x0020000
2d54.35dc:   000000007fff0000-00007ff7edc0ffff 0x0001/0x0000 0x0000000
2d54.35dc:  *00007ff7edc10000-00007ff7edc32fff 0x0002/0x0002 0x0040000
2d54.35dc:   00007ff7edc33000-00007ff7edf0ffff 0x0001/0x0000 0x0000000
2d54.35dc:  *00007ff7edf10000-00007ff7edf10fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
2d54.35dc:   00007ff7edf11000-00007ff7edf80fff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
2d54.35dc:   00007ff7edf81000-00007ff7edf81fff 0x0080/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
2d54.35dc:   00007ff7edf82000-00007ff7edfc6fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
2d54.35dc:   00007ff7edfc7000-00007ff7edfc7fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
2d54.35dc:   00007ff7edfc8000-00007ff7edfc8fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
2d54.35dc:   00007ff7edfc9000-00007ff7edfcdfff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
2d54.35dc:   00007ff7edfce000-00007ff7edfcefff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
2d54.35dc:   00007ff7edfcf000-00007ff7edfcffff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
2d54.35dc:   00007ff7edfd0000-00007ff7edfd3fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
2d54.35dc:   00007ff7edfd4000-00007ff7ee01bfff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
2d54.35dc:   00007ff7ee01c000-00007ff955ffffff 0x0001/0x0000 0x0000000
2d54.35dc:  *00007ff956000000-00007ff956000fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
2d54.35dc:   00007ff956001000-00007ff956112fff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
2d54.35dc:   00007ff956113000-00007ff956158fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
2d54.35dc:   00007ff956159000-00007ff956160fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
2d54.35dc:   00007ff956161000-00007ff95616efff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
2d54.35dc:   00007ff95616f000-00007ff95616ffff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
2d54.35dc:   00007ff956170000-00007ff956172fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
2d54.35dc:   00007ff956173000-00007ff9561dffff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
2d54.35dc:   00007ff9561e0000-00007ffffffdffff 0x0001/0x0000 0x0000000
2d54.35dc:  *00007ffffffe0000-00007ffffffeffff 0x0001/0x0002 0x0020000
2d54.35dc: VirtualBox.exe: timestamp 0x5903619d (rc=VINF_SUCCESS)
2d54.35dc: '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe' has no imports
2d54.35dc: '\Device\HarddiskVolume1\Windows\System32\ntdll.dll' has no imports
2d54.35dc: supR3HardNtChildPurify: Done after 463 ms and 0 fixes (loop #0).
2fb0.1318: Log file opened: 5.1.22r115126 g_hStartupLog=0000000000000004 g_uNtVerCombined=0xa03fab00
2fb0.1318: supR3HardenedVmProcessInit: uNtDllAddr=00007ff956000000 g_uNtVerCombined=0xa03fab00
2fb0.1318: ntdll.dll: timestamp 0x6dead514 (rc=VINF_SUCCESS)
2fb0.1318: New simple heap: #1 0000000001300000 LB 0x400000 (for 1966080 allocation)
2d54.35dc: supR3HardenedEarlyCompact: Removed heap 1 (0x00000001300000 LB 0x400000)
2d54.35dc: supR3HardNtEnableThreadCreation:
2fb0.1318: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64'
2fb0.1318: System32:  \Device\HarddiskVolume1\Windows\System32
2fb0.1318: WinSxS:    \Device\HarddiskVolume1\Windows\WinSxS
2fb0.1318: KnownDllPath: C:\WINDOWS\System32
2fb0.1318: supR3HardenedVmProcessInit: Opening vboxdrv...
2fb0.1318: supR3HardenedVmProcessInit: Restoring LdrInitializeThunk...
2fb0.1318: supR3HardenedVmProcessInit: Returning to LdrInitializeThunk...
2fb0.1318: Registered Dll notification callback with NTDLL.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\kernel32.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\kernel32.dll
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\System32\KERNEL32.DLL (Input=KERNEL32.DLL, rcNtResolve=0xc0150008) *pfFlags=0xffffffff pwszSearchPath=0000000000004001:<flags> [calling]
2fb0.1318: supR3HardenedDllNotificationCallback: load   00007ff952740000 LB 0x00266000 C:\WINDOWS\System32\KERNELBASE.dll [fFlags=0x0]
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\KernelBase.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\KernelBase.dll
2fb0.1318: supR3HardenedDllNotificationCallback: load   00007ff9556d0000 LB 0x000ae000 C:\WINDOWS\System32\KERNEL32.DLL [fFlags=0x0]
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\kernel32.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff9556d0000 'C:\WINDOWS\System32\KERNEL32.DLL'
2fb0.1318: supR3HardenedDllNotificationCallback: load   00007ff7edf10000 LB 0x0010c000 C:\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe [fFlags=0x0]
2fb0.1318: '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe' has no imports
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
2fb0.1318: supR3HardNtDisableThreadCreation: pvLdrInitThunk=00007ff9560791d0 pvNtTerminateThread=00007ff9560a08c0
2d54.35dc: supR3HardNtChildWaitFor: Found expected request 1 (CloseEvents) after 452 ms.
2fb0.1318: \SystemRoot\System32\ntdll.dll:
2fb0.1318:     CreationTime:    2018-01-05T15:56:46.395451500Z
2fb0.1318:     LastWriteTime:   2018-01-01T12:48:26.082566200Z
2fb0.1318:     ChangeTime:      2018-01-06T08:02:19.865353700Z
2fb0.1318:     FileAttributes:  0x20
2fb0.1318:     Size:            0x1dd100
2fb0.1318:     NT Headers:      0xe0
2fb0.1318:     Timestamp:       0x6dead514
2fb0.1318:     Machine:         0x8664 - amd64
2fb0.1318:     Timestamp:       0x6dead514
2fb0.1318:     Image Version:   10.0
2fb0.1318:     SizeOfImage:     0x1e0000 (1966080)
2fb0.1318:     Resource Dir:    0x174000 LB 0x6a1d8
2fb0.1318:     [Version info resource found at 0xd8! (ID/Name: 0x1; SubID/SubName: 0x409)]
2fb0.1318:     [Raw version resource data: 0x1740f0 LB 0x380, codepage 0x0 (reserved 0x0)]
2fb0.1318:     ProductName:     Microsoft® Windows® Operating System
2fb0.1318:     ProductVersion:  10.0.16299.192
2fb0.1318:     FileVersion:     10.0.16299.192 (WinBuild.160101.0800)
2fb0.1318:     FileDescription: NT Layer DLL
2fb0.1318: \SystemRoot\System32\kernel32.dll:
2fb0.1318:     CreationTime:    2017-09-29T13:42:04.954227600Z
2fb0.1318:     LastWriteTime:   2017-09-29T13:42:04.954227600Z
2fb0.1318:     ChangeTime:      2018-01-01T19:07:46.735385400Z
2fb0.1318:     FileAttributes:  0x20
2fb0.1318:     Size:            0xab868
2fb0.1318:     NT Headers:      0xe8
2fb0.1318:     Timestamp:       0xc2cf900
2fb0.1318:     Machine:         0x8664 - amd64
2fb0.1318:     Timestamp:       0xc2cf900
2fb0.1318:     Image Version:   10.0
2fb0.1318:     SizeOfImage:     0xae000 (712704)
2fb0.1318:     Resource Dir:    0xac000 LB 0x520
2fb0.1318:     [Version info resource found at 0x90! (ID/Name: 0x1; SubID/SubName: 0x409)]
2fb0.1318:     [Raw version resource data: 0xac0b0 LB 0x3a4, codepage 0x0 (reserved 0x0)]
2fb0.1318:     ProductName:     Microsoft® Windows® Operating System
2fb0.1318:     ProductVersion:  10.0.16299.15
2fb0.1318:     FileVersion:     10.0.16299.15 (WinBuild.160101.0800)
2fb0.1318:     FileDescription: Windows NT BASE API Client DLL
2fb0.1318: \SystemRoot\System32\KernelBase.dll:
2fb0.1318:     CreationTime:    2017-09-29T13:41:43.124345500Z
2fb0.1318:     LastWriteTime:   2017-09-29T13:41:43.124345500Z
2fb0.1318:     ChangeTime:      2018-01-01T19:07:46.829134900Z
2fb0.1318:     FileAttributes:  0x20
2fb0.1318:     Size:            0x266000
2fb0.1318:     NT Headers:      0xf0
2fb0.1318:     Timestamp:       0x4736733c
2fb0.1318:     Machine:         0x8664 - amd64
2fb0.1318:     Timestamp:       0x4736733c
2fb0.1318:     Image Version:   10.0
2fb0.1318:     SizeOfImage:     0x266000 (2514944)
2fb0.1318:     Resource Dir:    0x245000 LB 0x548
2fb0.1318:     [Version info resource found at 0x90! (ID/Name: 0x1; SubID/SubName: 0x409)]
2fb0.1318:     [Raw version resource data: 0x2450b0 LB 0x3bc, codepage 0x0 (reserved 0x0)]
2fb0.1318:     ProductName:     Microsoft® Windows® Operating System
2fb0.1318:     ProductVersion:  10.0.16299.15
2fb0.1318:     FileVersion:     10.0.16299.15 (WinBuild.160101.0800)
2fb0.1318:     FileDescription: Windows NT BASE API Client DLL
2fb0.1318: \SystemRoot\System32\apisetschema.dll:
2fb0.1318:     CreationTime:    2017-09-29T13:42:07.095026600Z
2fb0.1318:     LastWriteTime:   2017-09-29T13:42:07.095026600Z
2fb0.1318:     ChangeTime:      2018-01-08T20:50:10.598880700Z
2fb0.1318:     FileAttributes:  0x20
2fb0.1318:     Size:            0x1b398
2fb0.1318:     NT Headers:      0xc8
2fb0.1318:     Timestamp:       0xf30abf31
2fb0.1318:     Machine:         0x8664 - amd64
2fb0.1318:     Timestamp:       0xf30abf31
2fb0.1318:     Image Version:   10.0
2fb0.1318:     SizeOfImage:     0x1c000 (114688)
2fb0.1318:     Resource Dir:    0x1b000 LB 0x408
2fb0.1318:     [Version info resource found at 0x48! (ID/Name: 0x1; SubID/SubName: 0x409)]
2fb0.1318:     [Raw version resource data: 0x1b060 LB 0x3a8, codepage 0x0 (reserved 0x0)]
2fb0.1318:     ProductName:     Microsoft® Windows® Operating System
2fb0.1318:     ProductVersion:  10.0.16299.15
2fb0.1318:     FileVersion:     10.0.16299.15 (WinBuild.160101.0800)
2fb0.1318:     FileDescription: ApiSet Schema DLL
2fb0.1318: supR3HardenedWinFindAdversaries: 0x0
2fb0.1318: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64'
2fb0.1318: Calling main()
2fb0.1318: SUPR3HardenedMain: pszProgName=VirtualBox fFlags=0x2
2fb0.1318: supR3HardenedWinInitAppBin(0x2): '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64'
2fb0.1318: '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe' has no imports
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe)
2fb0.1318: SUPR3HardenedMain: Final process, opening VBoxDrv...
2fb0.1318: supR3HardenedEarlyCompact: Removed heap 1 (0x00000001300000 LB 0x400000)
2fb0.1318: supR3HardNtEnableThreadCreation:
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VBoxSupLib.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VBoxSupLib.dll
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=C:\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VBoxSupLib.DLL (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
2fb0.1318: supR3HardenedScreenImage/NtCreateSection: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VBoxSupLib.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedDllNotificationCallback: load   00007ff94e950000 LB 0x00005000 C:\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VBoxSupLib.DLL [fFlags=0x0]
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VBoxSupLib.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VBoxSupLib.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=C:\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VBoxSupLib.DLL (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff94e950000 'C:\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VBoxSupLib.DLL'
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VBoxSupLib.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=C:\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VBoxSupLib.DLL (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff94e950000 'C:\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VBoxSupLib.DLL'
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff94e950000 'C:\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VBoxSupLib.DLL'
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'msvcrt.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #1 'msasn1.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #6 'crypt32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #27 'rpcrt4.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\wintrust.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\wintrust.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'rpcrt4.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'rpcrt4.dll' -> '\Device\HarddiskVolume1\Windows\System32\rpcrt4.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\rpcrt4.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\rpcrt4.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'crypt32.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'crypt32.dll' -> '\Device\HarddiskVolume1\Windows\System32\crypt32.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #33 'msasn1.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\crypt32.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\crypt32.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'msasn1.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'msasn1.dll' -> '\Device\HarddiskVolume1\Windows\System32\msasn1.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\msasn1.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\msasn1.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'msvcrt.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'msvcrt.dll' -> '\Device\HarddiskVolume1\Windows\System32\msvcrt.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\msvcrt.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\msvcrt.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'msasn1.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'msasn1.dll' -> '\Device\HarddiskVolume1\Windows\System32\msasn1.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\msasn1.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\system32\Wintrust.dll (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
2fb0.1318: supR3HardenedDllNotificationCallback: load   00007ff9557b0000 LB 0x0009d000 C:\WINDOWS\System32\msvcrt.dll [fFlags=0x0]
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\msvcrt.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedDllNotificationCallback: load   00007ff951c10000 LB 0x00012000 C:\WINDOWS\System32\MSASN1.dll [fFlags=0x0]
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\msasn1.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedDllNotificationCallback: load   00007ff951ed0000 LB 0x000f6000 C:\WINDOWS\System32\ucrtbase.dll [fFlags=0x0]
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\ucrtbase.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\ucrtbase.dll
2fb0.1318: supR3HardenedDllNotificationCallback: load   00007ff9529b0000 LB 0x001ce000 C:\WINDOWS\System32\CRYPT32.dll [fFlags=0x0]
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\crypt32.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedDllNotificationCallback: load   00007ff952eb0000 LB 0x0011f000 C:\WINDOWS\System32\RPCRT4.dll [fFlags=0x0]
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\rpcrt4.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedDllNotificationCallback: load   00007ff954e70000 LB 0x0005b000 C:\WINDOWS\System32\sechost.dll [fFlags=0x0]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #2 'rpcrt4.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\sechost.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\sechost.dll
2fb0.1318: supR3HardenedDllNotificationCallback: load   00007ff953340000 LB 0x000a1000 C:\WINDOWS\System32\advapi32.dll [fFlags=0x0]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'msvcrt.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #6 'sechost.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #27 'rpcrt4.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\advapi32.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\advapi32.dll
2fb0.1318: supR3HardenedDllNotificationCallback: load   00007ff952c20000 LB 0x00058000 C:\WINDOWS\System32\Wintrust.dll [fFlags=0x0]
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\wintrust.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=api-ms-win-core-synch-l1-2-0 (rcNtResolve=0x0) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff952740000 'api-ms-win-core-synch-l1-2-0'
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=api-ms-win-core-fibers-l1-1-1 (rcNtResolve=0x0) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff952740000 'api-ms-win-core-fibers-l1-1-1'
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=api-ms-win-core-fibers-l1-1-1 (rcNtResolve=0x0) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff952740000 'api-ms-win-core-fibers-l1-1-1'
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=api-ms-win-core-synch-l1-2-0 (rcNtResolve=0x0) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff952740000 'api-ms-win-core-synch-l1-2-0'
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=api-ms-win-core-localization-l1-2-1 (rcNtResolve=0x0) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff952740000 'api-ms-win-core-localization-l1-2-1'
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff952c20000 'C:\WINDOWS\system32\Wintrust.dll'
2fb0.1318: supHardenedWinVerifyImageByHandle: -> -626 (\Device\HarddiskVolume1\Windows\System32\bcrypt.dll)
2fb0.1318: Error (rc=0):
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: rc=Unknown Status -626 (0xfffffd8e) fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume1\Windows\System32\bcrypt.dll: Grown load config (244 to 256 bytes) includes non-zero bytes: 00 00 00 00 60 a9 01 80 01 00 00 00
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\bcrypt.dll
2fb0.1318: Error (rc=0):
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\WINDOWS\system32\bcrypt.dll' (C:\WINDOWS\system32\bcrypt.dll): rcNt=0xc0000190
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0xc0000190 'C:\WINDOWS\system32\bcrypt.dll'
2fb0.1318: Warning! Failed to load bcrypt.dll
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\wintrust.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'rpcrt4.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'rpcrt4.dll' -> '\Device\HarddiskVolume1\Windows\System32\rpcrt4.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\rpcrt4.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'sechost.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'sechost.dll' -> '\Device\HarddiskVolume1\Windows\System32\sechost.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\sechost.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'msvcrt.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'msvcrt.dll' -> '\Device\HarddiskVolume1\Windows\System32\msvcrt.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\msvcrt.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'rpcrt4.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'rpcrt4.dll' -> '\Device\HarddiskVolume1\Windows\System32\rpcrt4.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\rpcrt4.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=C:\Windows\System32\WINTRUST.DLL (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff952c20000 'C:\Windows\System32\WINTRUST.DLL'
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\wintrust.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=C:\Windows\System32\WINTRUST.DLL (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff952c20000 'C:\Windows\System32\WINTRUST.DLL'
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\wintrust.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=C:\Windows\System32\WINTRUST.DLL (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff952c20000 'C:\Windows\System32\WINTRUST.DLL'
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\wintrust.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=C:\Windows\System32\WINTRUST.DLL (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff952c20000 'C:\Windows\System32\WINTRUST.DLL'
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\wintrust.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=C:\Windows\System32\WINTRUST.DLL (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff952c20000 'C:\Windows\System32\WINTRUST.DLL'
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\wintrust.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=C:\Windows\System32\WINTRUST.DLL (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff952c20000 'C:\Windows\System32\WINTRUST.DLL'
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\wintrust.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=C:\Windows\System32\WINTRUST.DLL (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff952c20000 'C:\Windows\System32\WINTRUST.DLL'
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\cryptsp.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\cryptsp.dll
2fb0.1318: supR3HardenedDllNotificationCallback: load   00007ff9515d0000 LB 0x00017000 C:\WINDOWS\SYSTEM32\CRYPTSP.dll [fFlags=0x0]
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\cryptsp.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #18 'bcrypt.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\rsaenh.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\rsaenh.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'bcrypt.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'bcrypt.dll' -> '\Device\HarddiskVolume1\Windows\System32\bcrypt.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedScreenImage/Imports: cache hit (Unknown Status -626 (0xfffffd8e)) on \Device\HarddiskVolume1\Windows\System32\bcrypt.dll [lacks WinVerifyTrust]
2fb0.1318: Error (rc=0):
2fb0.1318: supR3HardenedScreenImage/Imports: cached rc=Unknown Status -626 (0xfffffd8e) fImage=1 fProtect=0x0 fAccess=0x0 cHits=1 \Device\HarddiskVolume1\Windows\System32\bcrypt.dll
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\system32\rsaenh.dll (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
2fb0.1318: supR3HardenedScreenImage/NtCreateSection: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\rsaenh.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedScreenImage/NtCreateSection: cache hit (Unknown Status -626 (0xfffffd8e)) on \Device\HarddiskVolume1\Windows\System32\bcrypt.dll [lacks WinVerifyTrust]
2fb0.1318: Error (rc=0):
2fb0.1318: supR3HardenedScreenImage/NtCreateSection: cached rc=Unknown Status -626 (0xfffffd8e) fImage=1 fProtect=0x10 fAccess=0xf cHits=2 \Device\HarddiskVolume1\Windows\System32\bcrypt.dll
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0xc0000190 'C:\WINDOWS\system32\rsaenh.dll'
2fb0.1318: supR3HardNtViCallWinVerifyTrust: WinVerifyTrust failed with 0x8 (<NULL>) on '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe'
2fb0.1318: Error -22919 in VirtualBox! (enmWhat=1)
2fb0.1318: WinVerifyTrust failed on stub executable: WinVerifyTrust failed with hrc=Unknown Status 0x8 on '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe'
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'opengl32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #1 'vboxrt.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #2 'msvcp100.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #3 'msvcr100.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #4 'qt5corevbox.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #5 'qt5guivbox.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #6 'qt5widgetsvbox.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #7 'qt5printsupportvbox.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #8 'qt5openglvbox.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #10 'user32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #11 'advapi32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #12 'shell32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #13 'ole32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #14 'oleaut32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #15 'winmm.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'winmm.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'winmm.dll' -> '\Device\HarddiskVolume1\Windows\System32\winmm.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #1 'winmmbase.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #4 'msvcrt.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\winmm.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\winmm.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'oleaut32.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'oleaut32.dll' -> '\Device\HarddiskVolume1\Windows\System32\oleaut32.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'msvcp_win.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #5 'combase.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #23 'rpcrt4.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\oleaut32.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\oleaut32.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'ole32.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'ole32.dll' -> '\Device\HarddiskVolume1\Windows\System32\ole32.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #22 'rpcrt4.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #46 'gdi32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #47 'user32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #48 'combase.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\ole32.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\ole32.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'shell32.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'shell32.dll' -> '\Device\HarddiskVolume1\Windows\System32\shell32.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'msvcrt.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #73 'user32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #75 'gdi32.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\shell32.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\shell32.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'advapi32.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'advapi32.dll' -> '\Device\HarddiskVolume1\Windows\System32\advapi32.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\advapi32.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'user32.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'user32.dll' -> '\Device\HarddiskVolume1\Windows\System32\user32.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'win32u.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #34 'gdi32.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\user32.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\user32.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'qt5openglvbox.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'qt5openglvbox.dll' -> '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\qt5openglvbox.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'qt5widgetsvbox.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #1 'qt5guivbox.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #2 'qt5corevbox.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #3 'msvcr100.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\Qt5OpenGLVBox.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\Qt5OpenGLVBox.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'qt5printsupportvbox.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'qt5printsupportvbox.dll' -> '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\qt5printsupportvbox.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'gdi32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #1 'user32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #2 'qt5widgetsvbox.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #3 'qt5guivbox.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #4 'qt5corevbox.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #5 'winspool.drv'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #6 'comdlg32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #7 'msvcr100.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\Qt5PrintSupportVBox.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\Qt5PrintSupportVBox.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'qt5widgetsvbox.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'qt5widgetsvbox.dll' -> '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\qt5widgetsvbox.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'gdi32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #1 'user32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #2 'qt5guivbox.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #3 'qt5corevbox.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #4 'shell32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #5 'msvcp100.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #6 'msvcr100.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\Qt5WidgetsVBox.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\Qt5WidgetsVBox.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'qt5guivbox.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'qt5guivbox.dll' -> '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\qt5guivbox.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'ole32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #1 'opengl32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #2 'gdi32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #3 'user32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #4 'qt5corevbox.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #5 'msvcp100.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #6 'msvcr100.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\Qt5GuiVBox.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\Qt5GuiVBox.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'qt5corevbox.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'qt5corevbox.dll' -> '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\qt5corevbox.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #1 'user32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #2 'shell32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #3 'ole32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #4 'advapi32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #5 'ws2_32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #6 'mpr.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #7 'msvcp100.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #8 'msvcr100.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\Qt5CoreVBox.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\Qt5CoreVBox.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'msvcr100.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'msvcr100.dll' -> '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\msvcr100.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\msvcr100.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\msvcr100.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'msvcp100.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'msvcp100.dll' -> '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\msvcp100.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'msvcr100.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\msvcp100.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\msvcp100.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'vboxrt.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'vboxrt.dll' -> '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\vboxrt.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'msvcr100.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #1 'msvcp100.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #3 'ws2_32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #4 'rpcrt4.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VBoxRT.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VBoxRT.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'opengl32.dll'...
2f"	Toby (:
12359	Can't switch workspace on Linux host when guest in fullscreen	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
18297	Can't unmount vdi file	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
17043	Can't update because of SSL certificate format error	VirtualBox 5.1.26	2017-08-29T16:26:01Z	2017-08-29T16:26:01Z	2017-08-29T16:26:01Z	"VirtualBox 5.1.26 AND 5.1.27 R117677 (Qt5.6.2)

The network operation failed with the following error:
During network request: Wrong SSL certificate format.

My OS: Windows 10 Enterprise
version 10.0.15063

"	arrobles
14592	Can't use unscaled HiDPI with Linux guest if display scaling enabled in OS X Yosemite host	VirtualBox 5.0.4	2015-09-15T19:20:48Z	2015-09-15T19:20:48Z	2015-09-15T19:20:48Z	"Host is a MacBook Pro running OS X Yosemite 10.10.5, connected to a 3840x2160 display. Guest is Debian 8 with KDE 4.14.2, guest additions installed. I am attempting to run the guest OS in full-screen mode.

Display scaling is enabled in the host, with the scaled resolution set to 2560x1440. If ""Use Unscaled HiDPI Output"" is UNchecked, the guest correctly sees 2560x1440 as a resolution choice, and defaults to it.

If ""Use Unscaled HiDPI Output is checked, then the display does not work properly. The highest resolution reported to the guest appears to be 2560x1600 (not 3840x2160 as it should be), and for some reason the resolution selected by default is 1024x2880 (which isn't even a valid resolution). This results in the entire display being compressed into a narrow vertical strip up the middle of the screen, with everything squeezed to illegibly small size. Manually selecting 2560x1600 in the guest results in a similarly unreadable rectangle in the center of the screen.

Disabling display scaling on the host results in correct guest behavior, allowing guest to access full 3840x2160 native resolution. Unfortunately, this results in UI elements on host OS X desktop being unusably small. So it seems it is impossible to have both a usable host desktop, AND give the guest OS access to the full native display resolution.

To summarize, the functionality of the Use Unscaled HiDPI Output checkbox appears to be broken in 5.0.4, at least for the hardware/software configuration described above."	MikeUatCS
18366	Can't use vboxapi on Mac using Python bindings with anything other than the system version of Python	VirtualBox 6.0.2	2019-01-26T22:34:51Z	2019-01-26T22:34:51Z	2019-01-26T22:34:51Z	"Version 6.0.2 r128162 (Qt5.6.3)

When I installed VirtualBox it seems to have setup Python bindings to the system Python version on Mojave of 2.7.10.

I have installed the sdk for python 2.7.15 and 3.7 with:
cd /Applications/VirtualBox.app/Contents/MacOS/sdk/installer
sudo VBOX_INSTALL_PATH=/Applications/VirtualBox.app/Contents/MacOS /usr/local/bin/python2 vboxapisetup.py install
sudo VBOX_INSTALL_PATH=/Applications/VirtualBox.app/Contents/MacOS python3 vboxapisetup.py install

The installation appears to complete correctly for both python2.7.15 and python3.7.0.  However my test program only works for the built-in python 2.7.10 (/usr/bin/python).

My test Python program is:

from vboxapi import VirtualBoxManager
mgr = VirtualBoxManager(None, None)

On built-in Mojave Python version, execution is without error (/usr/bin/python test.py)

On brew-installed Python 2 (/usr/local/bin/python2 test.py), I get:
Segmentation fault: 11

On python 3.7.0 (python3 test.py) get:
m=VBoxPython3_7m x=No module named 'VBoxPython3_7m'
m=VBoxPython3m x=No module named 'VBoxPython3m'
m=VBoxPython x=No module named 'VBoxPython'
Traceback (most recent call last):
  File ""test.py"", line 2, in <module>
    mgr = VirtualBoxManager(None, None)
  File ""/usr/local/lib/python3.7/site-packages/vboxapi/__init__.py"", line 989, in __init__
    self.platform = PlatformXPCOM(dPlatformParams)
  File ""/usr/local/lib/python3.7/site-packages/vboxapi/__init__.py"", line 750, in __init__
    import xpcom.vboxxpcom
  File ""/Applications/VirtualBox.app/Contents/MacOS/sdk/bindings/xpcom/python/xpcom/vboxxpcom.py"", line 78, in <module>
    raise Exception('Cannot find VBoxPython module (tried: %s)' % (', '.join(_asVBoxPythons),))
Exception: Cannot find VBoxPython module (tried: VBoxPython3_7m, VBoxPython3m, VBoxPython)


"	keeely
18770	can't use VirtualBox under debian-live-10.0.0-amd64-kde	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
9744	Cancelling out of VM creation deletes entire mount point / junction	VirtualBox 4.1.4	2011-10-13T02:23:54Z	2011-10-13T11:05:56Z	2011-10-13T11:05:56Z	"On a Windows 7 64bit host, I have VirtualBox installed on Drive C:.
My VM ""library"" is a partition mounted via D:\Virtual.
If I start to create a new VM and cancel at any point beyond the ""VM Name and OS Type"" dialog, the mount point ""D:\Virtual"" will be destroyed.
The data on the partition remains intact and the mount point can be recreated."	Mike
14378	Cannot access VirtualBox menus in full-screen mode	VirtualBox 5.0.0	2015-08-03T10:16:54Z	2015-09-10T18:47:16Z	2015-09-10T18:47:16Z	"On an Ubuntu 14.04 system running GNOME 3.10, the VirtualBox menus are no longer accessible in VirtualBox 5.0, installed from the PPA (5.0.0-101573~Ubuntu~trusty). Putting the mouse at the bottom of the screen, the menu does not appear. I have tried explicitly lowering the full-screen window of the Windows 7 guest, but to no avail.

Downgrading to virtualbox-4.3-10161~Ubuntu~trusty fixes the problem, suggesting it was introduced in VirtualBox 5.0."	Reuben Thomas
16033	Cannot attach hard drive to VM on 32-bit Windows 7	VirtualBox 5.1.6	2016-10-05T13:07:09Z	2016-10-06T10:41:49Z	2016-10-06T10:41:49Z	"In VirtualBox 5.1 it is not possible to attach a hard drive to a newly created VM on 32-bit Windows systems (tested with Win7x86).

Steps to reproduce the problem:

- Create a new virtual machine **without** a hard drive.
- Try to attach a hard drive to the SATA-Controller. Attaching the hard drive doesn't succeed because VirtualBox crashes."	ckossmann
18656	Cannot boot from .vmdk if 'Use Host I/O Cache' is disabled	VirtualBox 6.0.8	2019-05-17T19:58:15Z	2019-05-28T14:25:40Z	2019-05-28T14:25:40Z	"Attempting to boot VM from a raw disk fails when 'Use Host I/O Cache' is disabled. When the option is enabled the VMboots normally.

The disk is formatted as GUID with an EFI partition, a macOS HFS+ partition and 2 Linux ext4 partitions (root and swap).
"	granada29
19953	Cannot boot Windows 10 guest on OS X El Capitan host.	VirtualBox 6.1.14	2020-10-10T00:02:56Z	2020-11-09T16:43:34Z	2020-11-09T16:43:34Z	"Hi, 

Downloaded and installed Virtualbox on a vanilla Mac Pro running El Capitan.
Virtualbox alerted that the guest got into guru meditation and I was asked to submit logs.

Thanks,
Roy"	theflyingmooseman
18754	Cannot capture mouse pointer in video recording of Ubuntu 18.04 LiveCD guest	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
16459	Cannot change Virtual Screen from Host screen 1 to 2 in Fullscreen mode	VirtualBox 5.1.14	2017-02-07T08:29:04Z	2017-09-28T04:06:13Z	2017-09-28T04:06:13Z	"Host: Windows 10 Pro x64 with 2 monitors

Guest: Windows 7 Pro x64

When in Full-screen mode, I used to be able to change from monitor 1 to monitor 2 and vice versa by going to View > Virtual Screen 1 > Use Host Screen 1/Use Host Screen 2. 

I believe since v5.1.12, I have to complete the previous step, exit reenter the Full-screen mode to switch the guest display to the other monitor."	Anh Le
17959	Cannot copy text data from Win10 guest onto Mac OS host	VirtualBox 5.2.18	2018-08-28T16:31:03Z	2018-08-31T12:43:27Z	2018-08-31T12:43:27Z	"Host: MacOS High Sierra (10.13.5)[[br]]
Guest: Windows 10 64-bit; Guest Additions installed; bi-di copy&paste enabled[[br]]
VirtualBox Version: 5.2.18 !r124319 (Qt5.6.3) - latest as of Aug 28, 2018; latest Extenions installed[[br]]

Issue:

Copying any rich-text data from within the Windows 10 guest is not paste-able into the Mac OS host.  This is somewhat new behavior that was introduced with a clipboard crash fix in the release after version 5.1.32.  

Before the crash fix was made, pasting copied rich-text from the guest onto the host pasted the plain text extracted from the clipboard.  While not as ""perfect"" of a feature solution as being able to paste the full rich-text, plain text pasting would be welcomed back with open arms.  An ongoing discussion is here:

https://forums.virtualbox.org/viewtopic.php?f=8&t=86056&sid=ef11b0345dfa4278164ef407b4f4a626

While most of the commenters experiencing this bug are seeing the issue with Microsoft Office products, I also see it with Chrome and Firefox.  To reproduce, do the following:

1) within Win10 guest, browse to Google from within Chrome or Firefox, do a search for ""virtualbox""
2) highlight and copy the first found result, which is ""Oracle VM Virtualbox"".  I copied the entire result listing: title, URL, description.
3) hit CTRL+C or right-click/copy
4) mouse-out to Mac OS host and paste into any app such as TextEdit: no data is pasted.

The very inconvenient workaround that most people do is to paste the data into Notepad within the Win10 guest, copy that data, then paste into the host.  A nicer solution that still requires an extra click is to install the PureText app within Win10, which when used, strips the rich text and makes the plain text paste-able into the Mac OS host.

We would like to have the ability to paste any text data (as at the minimum plain text) into the host, which was working in VirtualBox up until and including 5.1.32.
"	TonyRockyTiger
19934	Cannot create 64-bit VM with VirtualBox	VirtualBox 6.1.14	2020-10-03T22:04:20Z	2020-10-03T22:04:20Z	2020-10-03T22:04:20Z	I just got a brand-new computer, running Windows 10 Education. I try to create an Ubuntu 64-bit VM on VirtualBox 6.1.14, but only 32-bit options are available. I checked the BIOS to make sure SVM was enabled, and it already was. I made sure that Hyper-V was disabled, so there weren't two virtualization options available at the same time, but it already was. I've checked Google and Stack Exchange but I couldn't find anything else. Any help would be appreciated.	rochat
17895	Cannot create a disk image via GUI	VirtualBox 5.2.8	2018-07-27T08:30:26Z	2018-07-27T08:30:26Z	2018-07-27T08:30:26Z	"When I create a new HD, and give in the size, like ""9,1GB"", the error appears:

{{{
Could not create the medium storage unit '****'.

VD: The given disk size 9771050598 is not aligned on a sector boundary (512 bytes) (VERR_VD_INVALID_SIZE).

Код ошибки: VBOX_E_FILE_ERROR (0x80BB0004)
Компонент: MediumWrap
Интерфейс: IMedium {4afe423b-43e0-e9d0-82e8-ceb307940dda}
}}}
"	Urmas
12120	Cannot create snapshot with ampersand in the title	VirtualBox 4.2.18	2013-09-17T07:44:21Z	2013-09-25T07:24:08Z	2013-09-25T07:24:08Z	When attempting to create a snapshot with the title ”Nuts&bolts”, VBOX fails with an error message. most probably the filename/filepath derived from the snapshot title is not escaped properly	tudorilisoi
16362	Cannot create solid state drives when VM is running	VirtualBox 5.0.30	2017-01-06T15:38:34Z	2017-01-06T15:38:34Z	2017-01-06T15:38:34Z	"I want to simulate the replacement of a solid state drive while the system is running.

I have a VM (guest OS: ubuntu 14:04), with a SATA controller of 4 hotpluggable disks. The solid-state drive is on port 3.

I first create a new medium to represent the replacement disk:
$ vboxmanage createmedium disk --filename disks/ssd6.vmdk --size 8192 --format VMDK
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Medium created. UUID: 9532c0bc-f14b-4f0c-a4df-b366024ed58d

Then I remove the solid state drive from the VM:
$vboxmanage storageattach  ""standalone_default_1473423571692_13381"" --storagectl SATAController --port=3 --medium=none

Then I want to replace it with a new virtual Solid-State Drive:
$ vboxmanage storageattach  ""standalone_default_1473423571692_13381"" --storagectl SATAController --port=3 --medium=disks/ssd6.vmdk --type hdd --nonrotational on

I get the following  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: ""NonRotationalDevice(Bstr(pszCtl).raw(), port, device, TRUE)"" at line 837 of file VBoxManageStorageController.cpp


If I omit the option --nonrotational on, the command succeeds, but it's added as a regular (hotpluggable) hard disk. 






"	jkv
19808	Cannot get my VM to run with	VirtualBox 6.1.10	2020-08-12T21:00:05Z	2020-08-19T17:49:30Z	2020-08-19T17:49:30Z	"I'm using a Windows 10 Home PC, w/Intel COREi7 CPU
I'm running VirtualBox 6.1

I needed to Enable Nested VT-x/AMD-V under processor. So I ran VBoxManage modifyvm ""virl.1.6.67.default"" --nested-hw-virt on.

Now when I start my VM I get...

Failed to open a session for the virtual machine virl.1.6.67.default.

Cannot enable nested VT-x/AMD-V without nested-paging and unresricted guest execution!

 (VERR_CPUM_INVALID_HWVIRT_CONFIG).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

I edited my my .vbox file to inclued to NestedHWVirt enabled=""true""/> statemen

<CPU count=""2"">
        <PAE enabled=""false""/>
        <NestedHWVirt enabled=""true""/>

I still get the following when I start my VM...

Failed to open a session for the virtual machine virl.1.6.67.default.

Cannot enable nested VT-x/AMD-V without nested-paging and unresricted guest execution!

 (VERR_CPUM_INVALID_HWVIRT_CONFIG).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
"	Mike K
13611	Cannot get rid of 2nd monitor window	VirtualBox 4.3.18	2014-11-12T17:44:05Z	2014-11-14T13:31:57Z	2014-11-14T13:31:57Z	"Never set VB to use 2 monitors for a VM, but somehow after a Windows update occurred in the VM, guessing this was the point at which it first appeared. I have 2 VB displays coming up for a VM.  I have tried to set VB to use only 1 display, however, the Win OS still comes up on the 2nd display thus never allowing me to sign in to the OS.  I have also tried changing the monitor under windows settings to show the desktop on the primary display 1, vs the second but the OS will not allow me to make the change. I did not initiated the change on the OS or through VB and cannot get ride of it.  Also, VB shows the primary display as being corrupted in the preview window.

Please see attached screen shots.  Need to get the VM back and Win OS to using only 1 display.

Thank you
Art"	ArtZ
7972	Cannot install extension pack -- VERR_ACCESS_DENIED	VirtualBox 4.0.0	2011-01-02T01:03:11Z	2018-01-26T21:25:44Z	2018-01-26T21:25:44Z	"''Note: I have not attached a session log file as attempting to install an extension pack, predictably, does not appear to generate anything in the session log for a VM.  I have attempted the installation both without and with VMs running.''

I installed !VirtualBox 4.0.0 onto Windows 7 Professional and attempted to install the extension pack: '''Oracle_VM_VirtualBox_Extension_Pack-4.0.0-69151.vbox-extpack'''
The attempt failed with:
  The installer failed with exit code 1: VBoxExtPackHelperApp.exe: error: Failed to rename the temporary directory to the final one: VERR_ACCESS_DENIED('G:\PROGRA~3\Oracle\VIRTUA~1/ExtensionPacks/Oracle_VM_VirtualBox_Extension_pack-_-inst-4100' -> 'G:\PROGRA~3\Oracle\VIRTUA~1/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack')

''a screencap of the error dialog is attached.'' (''NOTE: My boot drive (C:) is a small solid-state drive so I have the user account directories on my G: drive and install most software there as well.'')

As the error suggests ""access denied"" and the host is Windows 7, I immediately suspected UAC, however, I am not so sure of that now.  I searched the forums for anyone else experiencing the error -- I did find someone else and their error appeared to be identical to mine but, in their case, they have VBox loaded on a Windows XP host, so UAC seems an unlikely contributor.

I did verify that it seems to be actually creating the temporary directory (I did this by opening the !ExtensionPacks subdirectory in Windows Explorer and visually watching it as I attempted the installation -- a new folder appeared briefly then disappeared again followed immediately by the appearance of the error dialog).

I have verified that the MD5 checksum for the extension pack matches the one published on your website.  I can also open that file using 7-zip and it appears reasonable in format and content (as best as I can tell).

I tried installing the extension pack in as many ways as I could imagine: doubleclicking on the file itself; adding it using the preferences dialog in !VirtualBox Manager; running !VirtualBox manager both as an administrator and as a non-elevated administrative user; installing from an elevated command prompt using VBoxManage.exe; etc.  In each case the results were exactly the same.  I even tried rebooting my machine and then running the scenarios again.

Since it was suggesting an access problem, and knowing that Windows 7 has some restrictions on making modifications to the ""Program Files"" directory and subdirectories ( I am not sure exactly what those restrictions are but I know that in some cases things wind up in a virtual directory instead of the intended target) I tried a long shot and deleted the !ExtensionPacks directory then replaced it with a symbolic link to a directory I created in G:\Users\Public which had full access by the special user ""!EveryOne"" so there should not have been any access problems so far as I know -- the results were exactly the same as before so I reversed my changes.

I have checked the Windows Logs in the event viewer -- there are no application errors, system errors, nor security audit failures, corresponding to the failed installation.

I am pretty well tapped out of other ideas of things to try as workarounds.  If there is any other information you need please let me know.  Thanks in advance for any assistance you can provide in resolving this.



"	Leslie Noland
18422	Cannot install Extension Pack 6.0.4	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
19701	Cannot list raw disk partition table when sector size != 512 bytes	VirtualBox 6.1.10	2020-07-04T07:03:36Z	2020-07-04T07:04:52Z	2020-07-04T07:04:52Z	"VBoxManage returns an empty partition table when the disk has a sector size of 4096 bytes. I think this may be the root cause of the problems reported in tickets

https://www.virtualbox.org/ticket/16705

https://www.virtualbox.org/ticket/16498

{{{
VBoxManage internalcommands listpartitions -rawdisk /dev/disk8
Number  Type   StartCHS       EndCHS      Size (MiB)  Start (Sect)
}}}
fdisk (on linux) return the following information about the drive.
{{{
Disk model: Expansion Desk  
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 268431360 bytes
Disklabel type: gpt
Disk identifier: C3BE927E-B799-4B59-A37F-8927D38FA8BF

Device         Start       End   Sectors   Size Type
/dev/sdf1          6     76805     76800   300M EFI System
/dev/sdf2      76806  61110489  61033684 232.8G Apple APFS
/dev/sdf3   61143258 482519263 421376006   1.6T Linux filesystem
/dev/sdf4  482552032 488345871   5793840  22.1G Linux swap
}}}

Using a disk with a sector size of 512 bytes is successful.
{{{
VBoxManage internalcommands listpartitions -rawdisk /dev/disk8
Number  Type   StartCHS       EndCHS      Size (MiB)  Start (Sect)
1       0x00  0   /0  /0   0   /0  /0            200           40
2       0x00  0   /0  /0   0   /0  /0         238546       409640
3       0x00  0   /0  /0   0   /0  /0        1648981    488953032
4       0x00  0   /0  /0   0   /0  /0          20001   3866066944
}}}
fdisk for this drive shows
{{{
Disk model: 006-2DM164      
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 4096 bytes / 33553920 bytes
Disklabel type: gpt
Disk identifier: 0F3513DC-A778-4280-BB61-5399F44E1135

Device          Start        End    Sectors  Size Type
/dev/sdf1          40     409639     409600  200M EFI System
/dev/sdf2      409640  488953031  488543392  233G Apple APFS
/dev/sdf3   488953032 3866066943 3377113912  1.6T Linux filesystem
/dev/sdf4  3866066944 3907028991   40962048 19.5G Linux swap
}}}"	granada29
15242	cannot open VirtualBox imported any machine (Windows or Linux)	VirtualBox 5.0.16	2016-03-13T21:13:22Z	2016-03-14T19:16:32Z	2016-03-14T19:16:32Z	"I want to use VirtualBox on my NetBook ""Aspire One D270"", but I cannot. I tried VirtualBox 5.0.16 either VirtualBox 5.0.0 and also both portable and fix installted. I do not know the reason, hardware? Antivir? Firewall?

Fehlercode:
E_FAIL (0x80004005)
Komponente:
MachineWrap
Interface:
IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}
"	Sven_web
19129	Cannot reconize password in Kali Linux 2019.4 VM	VirtualBox 6.0.14	2019-12-04T01:14:30Z	2019-12-04T05:35:54Z	2019-12-04T05:35:54Z	password not reconized by kali Linux software	tommy smith
16434	Cannot resize VM Win7 on Win 10 Host	VirtualBox 5.1.14	2017-01-30T08:59:18Z	2017-02-02T22:14:54Z	2017-02-02T22:14:54Z	"Hello
Please give me any advice regarding my problem:
I cannot resize VM Win7 on Win 10 Host.
Plese see attached images.
Thank you
Best regards"	movis
21262	Cannot run multiple guest VMs of the same type if their *.vbox files are all in the same directory	VirtualBox-7.0.2	2022-11-10T23:24:47Z	2022-11-10T23:24:47Z	2022-11-10T23:24:47Z	"It seems that Virtualbox is using some kind of folder-level locking construct that makes it impossible to run multiple guest VMs if those guest VMs' corresponding *.vbox files are all in the same folder.  Attempting to launch a second VM stored in the same folder when another is running will lock up the window before the BIOS image appears and the VM will crash with this error:


{{{
The VM session was aborted.
Result Code:
E_FAIL (0X80004005)
Component:
SessionMachine
Interface:
ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}
}}}


I like organizing all of my guest OSes by their main OS-type.  So, for example, Windows NT, 2000, 2003, and 2019 will all live in the same ""WINDOWS"" folder under a given directory hierarchy.  Ditto for Solaris 10, Solaris 11.4, OmniOS, and OpenIndiana under a ""SOLARIS"" directory.  I do not like using individual subfolders under this hierarchy and I want all of the *.vbox files to be together.

I don't really know why I like it this way, but I do, and I have found it difficult to organize things in a different manner that makes both myself and Virtualbox happy.  It feels like the folder-level locking is a kludge (I mean, why not file-level locking?), or at least, the crash is not being handled terribly well (a helpful error message being returned would be a marked improvement vs just outright crashing).

FWIW, how I got to this condition is every time I create a new guest VM, I set the bare minimum config, then shut VBox down and  any services to make sure all of the XML files are flushed out.  Then I manually move *.vbox and *.vdi files around to where I want them, then edit the XML's to point things to the new locations.  Other than the occasional hiccup from a still-running VBox process holding a lock, this setup has worked well for the past several years.  The inability to run multiple OSes of the same type is not a major blocker, but I had been perplexed for a while why it wasn't possible until I finally did some debugging.

Can someone maybe take a look at whether folder-level locking is still appropriate, or at least put some code in to detect this scenario and return an error message to the user?"	Kumba
9733	Cannot set defaultMachineFolder globally	VirtualBox 4.0.4	2011-10-10T18:32:49Z	2011-10-10T18:32:49Z	2011-10-10T18:32:49Z	"I am at a site in which users have networked home directories.

Because of this, virtual machine disks cannot go into $HOME; instead, we place them in a user-specific directory on the local disk.

Before 4.0, we would set VBOX_USER_HOME to this directory in a system shell profile. When users started up VirtualBox for the first time, their configuration would be set accordingly, and new VMs would be created on the local disk as desired.

After 4.0, VBOX_USER_HOME only specifies the location of the user configuration files. VMs go into ""$HOME/VirtualBox VMs"", and while the user can change that, there's nothing that an admin can set for the default value to be something else.

A new environment variable, e.g. VBOX_VM_HOME, would be perfect. A new configuration directive of some sort might also work, provided that the location can be something different for each user, rather than a static value."	Daniel Richard G.
2251	cannot specify disk geometry	VirtualBox 2.0.2	2008-09-16T10:42:47Z	2013-04-15T18:19:34Z	2013-04-15T18:19:34Z	"I do not see any option for setting disk geometry of disk images.

Since some OSes calculate the disk geometry based on disk size or read it from the data stored on the disk rather than querying the bios they can get to a disk geometry different from the one VirtualBox calculates.

This does, of course, cause the OSes to fail unless the geometry is configurable in bios to match what the OS thinks."	Michal Suchanek
16952	Cannot start any VM after install extension pack.	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
19802	Cannot start any VM guest: Make sure the kernel module has been loaded successfully. VERR_SUP_VP_MEMORY_VS_FILE_MISMATCH -Error -5600 in supR3HardenedWinReSpawn! (enmWhat=3)	VirtualBox 6.1.10	2020-08-09T10:52:08Z	2020-08-09T11:15:46Z	2020-08-09T11:15:46Z	"Hello,

I got an issue after upgrading from 6.0.22r 137980 to 6.1.12r 139181.
[[Image()]]

{{{When starting a VM-guest, I receive an error message
NtCreateFile(\Device\VBoxDrvStub) failed: unknown Status -5600 (0xffffea20) (rcNt=0xe986ea20)
CBoxDrvStub error: ntdll.dll: 11 difference between 0x9fe12 and 0x9fe1c in #1 (.text), first: 8b != b8(rc=-5600)

Make sure the kernel module has been loaded successfully.

where supR3HardenedWinReSpawn what: 3
VERR_SUP_VP_MEMORY_VS_FILE_MISMATCH (-5600) - Process Verification
Failure: The memory content does not match the image file.}}}
[[Image()]]

I may run into this, because I didn't instantly restarted the Windows 10 (2004) host after Installation? Also the installer complained the first try, that something (i don't remember, what) was in use by virtualBox. I then restarted the installer and everything went just fine on the second try. But I didn't saw the message box that instructed to reboot, and the installer offered to start virtualbox instead immediately! The virualbox management Window got focus and covered the prompt ""You must reboot your computer!"".

The VirtualBox Window popped up a message box that prompted for updating the VirtualBox 6.1.12 Oracle VM VirtualBox Extension Pack! 

So I just installed it and THEN I rebooted (maybe this is the culprit? If so, the installer shouldn't allow to start VirtualBox instantly, if in the fierst place it should restart the host to install virtual box first completely before updating the extension pack! Not to mention the focus issue of the covered prompt to reboot to fully perform the installation and complete the process ...

I found an outdated bug report (5 years ago) somewhat related:

VirtualBox 4.3.26
https://www.virtualbox.org/query?status=%21closed&version=VirtualBox+4.3.26
(closed defect: fixed)
Opened 5 years ago Last modified 4 years ago
VirtualBox fails to launch any virtual machine: NtCreateFile failed
https://www.virtualbox.org/ticket/14052

Now the errors:


{{{
The virtual machine 'Debian pv10' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'L:\Data\VirtualBox VMs\Debian pv10\Logs\VBoxHardening.log'.

Fehlercode: E_FAIL (0x80004005)
Komponente: MachineWrap
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}
}}}



{{{
35e8.550c: supR3HardNtChildPurify: Done after 517 ms and 0 fixes (loop #0).
384c.548c: Log file opened: 6.1.12r139181 g_hStartupLog=0000000000000004 g_uNtVerCombined=0xa047bb00
384c.548c: supR3HardenedVmProcessInit: uNtDllAddr=00007ffc7dac0000 g_uNtVerCombined=0xa047bb00 (stack ~00000000010ffa48)
384c.548c: ntdll.dll: timestamp 0xb29ecf52 (rc=VINF_SUCCESS)
384c.548c: New simple heap: #1 0000000001200000 LB 0x400000 (for 2031616 allocation)
384c.548c: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume17\Program Files\Oracle\VirtualBox'
384c.548c: System32:  \Device\HarddiskVolume17\Windows\System32
384c.548c: WinSxS:    \Device\HarddiskVolume17\Windows\WinSxS
384c.548c: KnownDllPath: C:\Windows\System32
384c.548c: supR3HardenedVmProcessInit: Opening vboxdrv stub...
35e8.550c: supR3HardNtEnableThreadCreationEx:
384c.548c: supR3HardenedWinReadErrorInfoDevice: 'ntdll.dll: 11 differences between 0x9fe12 and 0x9fe1c in #1 (.text), first: 8b != b8'
384c.548c: Error -5600 in supR3HardenedWinReSpawn! (enmWhat=3)
384c.548c: NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status -5600 (0xffffea20) (rcNt=0xe986ea20)
VBoxDrvStub error: ntdll.dll: 11 differences between 0x9fe12 and 0x9fe1c in #1 (.text), first: 8b != b8
35e8.550c: supR3HardenedWinCheckChild: enmRequest=2 rc=-5600 enmWhat=3 supR3HardenedWinReSpawn: NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status -5600 (0xffffea20) (rcNt=0xe986ea20)
VBoxDrvStub error: ntdll.dll: 11 differences between 0x9fe12 and 0x9fe1c in #1 (.text), first: 8b != b8
384c.548c: KiUserExceptionDispatcher: 0xc0000005 (0000000000000001, 0000000000000024) @ 00007ffc7dac72a6 (flags=0x0)
  rax=0000000000000000 rbx=00007ffc7dc252c0 rcx=00007ffc7dc252c0 rdx=00000000fffffffa
  rsi=0000000000000000 rdi=00007ffc7dc24f00 r8 =0000000000000000 r9 =00007ffc7dc25200
  r10=0000000000000000 r11=00000000010f92e0 r12=0000000000000000 r13=0000000000f34000
  r14=0000000000000001 r15=0000000000000000  P1=0000000000000000  P2=0000000000000000
  rip=00007ffc7dac72a6 rsp=00000000010f9140 rbp=00000000ffffea00    ctxflags=0010005f
  cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b    eflags=00010213   mxcrx=00001f80
   P3=0000000000000000  P4=0000000000000000  P5=00000000010f9368  P6=00007ff7fa73a900
  dr0=0000000000000000 dr1=0000000000000000 dr2=0000000000000000 dr3=0000000000000000
  dr6=0000000000000000 dr7=0000000000000000 vcr=00007ff7fa6d47f0 dcr=00000000010f9300
  lbt=0000000000000000 lbf=0000000000000000 lxt=0000000000000000 lxf=0000000000000000
35e8.550c: Error -5600 in supR3HardenedWinReSpawn! (enmWhat=3)
35e8.550c: NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status -5600 (0xffffea20) (rcNt=0xe986ea20)
VBoxDrvStub error: ntdll.dll: 11 differences between 0x9fe12 and 0x9fe1c in #1 (.text), first: 8b != b8
}}}

I'll attach the complete VBox Hardening.log

Thanks in Advance

floogy  

"	floogy
18299	cannot start guest from snapshot	VirtualBox 6.0.0	2019-01-10T23:52:51Z	2019-02-10T00:10:05Z	2019-02-10T00:10:05Z	"Restored current state from snapshot. Snapshot fails to start:

Failed to open a session for the virtual machine IE11 - Win7.

The VM session was aborted.

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: SessionMachine
Interface: ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}

Can then restart from this point but enters error recovery in Windows. If I then pause and save another snapshot, I cannot start from that snapshot either.
"	keefw
16990	Cannot start the Guest in VirtualBox	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
15486	Cannot start VirtualBox.exe or VBoxSDL.exe because of ntdll.dll error.	VirtualBox 5.0.20	2016-06-07T03:44:18Z	2016-06-07T07:36:43Z	2016-06-07T07:36:43Z	"Basically what title says.
Here is the windows log for this:
{{{
  Problem signature:
  Problem Event Name:	APPCRASH
  Application Name:	VirtualBox.exe
  Application Version:	5.0.21.7750
  Application Timestamp:	57515822
  Fault Module Name:	ntdll.dll
  Fault Module Version:	6.1.7601.23418
  Fault Module Timestamp:	5708a857
  Exception Code:	c0000005
  Exception Offset:	0000000000038600
  OS Version:	6.1.7601.2.1.0.256.48
  Locale ID:	1033
  Additional Information 1:	246f
  Additional Information 2:	246f18be415dcbf9dfc6a8b7680358ac
  Additional Information 3:	246f
  Additional Information 4:	246f18be415dcbf9dfc6a8b7680358ac
}}}
The problem is I can't event get the .log file from virtualbox as it crashes too early. I was able to run virtualbox.exe in safe mode, but I'm not sure how it will help me. I've tried ""diagnostic startup"" in msconfig, and virtualbox.exe also crushes. Versions I've tried: 
* VirtualBox-5.0.21-107750-Win
* VirtualBox-5.0.20-106931-Win
* VirtualBox-4.3.38-106717-Win"	DanceDance
16259	Cannot start VMs due to VERR_SUP_VP_REPLACE_VIRTUAL_MEMORY_FAILED	VirtualBox 5.1.10	2016-12-02T17:35:00Z	2017-04-10T07:02:31Z	2017-04-10T07:02:31Z	"On some windows hosts VirtualBox will not start VMs with DigitalGuardian installed. An error message box with ""VERR_SUP_VP_REPLACE_VIRTUAL_MEMORY_FAILED ... supR3HardNtChildPurify what:5"" appears. This has been reproduced on both a Windows 7 and 2K8R2 systems but not all Win7 and 2K8R2 machines. This is system configuration depended. I have a windows 7 machine where I uninstalled DG but left our driver in place and it still failed. I then copied an MS driver, vms3cat.sys, into dgmaster.sys rebooted and it still failed. I believe there is a logic error in the code that replaces suspect virtual memory.

I have a 2K8R2 VM that reproduces the issue.
"	Stevel
15006	Cannot update Win 8.1 to Win 10.0 because of display	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
19754	Cannot use VM due to Guru Meditation Error	VirtualBox 6.1.10	2020-07-23T09:16:33Z	2020-07-24T07:48:08Z	2020-07-24T07:48:08Z	"when starting a VM it asks me to choose from four options: ubuntu, advances options for ubuntu and two memtests. In the logs the error shows as "" VCPU0: Guru Meditation -1149 (VERR_EM_INTERNAL_ERROR)"".
updated the version from 6.1.10 to 6.1.12 but the problem remains 

after creating new VMs also has the same error

"	virgo
21421	Canonical has updated Ubuntu Linux kernel; DEB package from Oracle no longer works	VirtualBox-7.0.6	2023-01-21T14:39:07Z	2023-01-26T11:11:48Z	2023-01-26T11:11:48Z	"Canonical has updated Ubuntu 22.04 LTS to version 22.04.2. The Linux kernel in this Hardware Enablement Stack has been updated from version 5.15 to 5.19.

With the new kernel version 5.19, virtualization no longer works with the DEB package of Virtualbox 7.0.6 offered by Oracle for Ubuntu 22.04.
See https://www.virtualbox.org/wiki/Linux_Downloads

When starting a virtual machine, the following error appears:
Kernel driver not installed (rc=-1908)

See also: https://forums.virtualbox.org/viewtopic.php?f=7&t=108359"	Atalanttore
20757	CANT START ENGINE	VirtualBox 6.1.30	2022-01-02T18:43:10Z	2022-01-02T18:44:28Z	2022-01-02T18:44:28Z	I cannot start it or attach linux installation to apps. i researched everything, but i've found nothing...plz help me	BABBA BOI
19520	Can’t boot Windows VM on macOS 10.15.3	VirtualBox 6.1.6	2020-04-21T09:11:48Z	2020-04-21T09:11:48Z	2020-04-21T09:11:48Z	"Hello,

Recently upgraded my Hackintosh from Mojave to Catalina, and now I can’t boot a Windows VM (Linux ones may have problems too but I haven’t tested extensively). Parallels Desktop works fine

When booting the latest live CD downloaded from Microsoft’s website, I first get this error (on a brand new VM):
“File: \windows\System32\drivers\nvraid.sys
Error code: 0xc0000098”
Then I press enter and get this one:
“File: \windows\System32\drivers\iaStorV.sys
Error code: 0xc0000221”

It seems that a few weeks ago when I tried (VirtualBox 6.1.4), it did the same thing with same error codes but with different file names. I attach the screenshots and log file.

Thanks!"	GilDev
21324	Carbon Black EDR: VirtualBox VMs Fail to Start After Windows Sensor Upgrades to 7.3.0	VirtualBox-7.0.4	2022-12-05T14:00:00Z	2022-12-05T14:00:00Z	2022-12-05T14:00:00Z	"https://community.carbonblack.com/t5/Knowledge-Base/EDR-VirtualBox-VMs-Fail-to-Start-After-Windows-Sensor-Upgrades/ta-p/113625

Environment
EDR Windows Sensor:  7.3.0
Virtual Box: 6.1.34

Symptoms
VirtualBox VMs do not start if the Windows host is running EDR win-7.3.0.

Cause
VirtualBox hardening script may have issues with the updated, secure signed certificate on the CB win-7.3.0 cbedramsi.dll file.

Resolution
Until VirtualBox hardening script permits the new signed certificate, the Windows host should stay on EDR win-7.2.2.
VMs within VMware Workstation or Microsoft HyperV start properly when the Windows host is running EDR win-7.3.0.

Additional Notes
CB win-7.3.0 uses a new more secure certificate; SHA2 384bit Sectigo CA with integrity checks.
If a case is opened with Virtual Box, VMware Carbon Black Support and Engineers could provide additional information.  
 
"	neglas
20772	Catastrophic data loss with Ubuntu 21.04 guest	VirtualBox 6.1.30	2022-01-16T00:30:27Z	2022-01-22T17:04:20Z	2022-01-22T17:04:20Z	"See also #20763

Following this:

```Jan 15 21:35:14 ubuntu CRON[1188952]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 15 21:37:35 ubuntu kernel: [1355482.810724] ata3.00: exception Emask 0x0 SAct 0x8000000 SErr 0x0 action 0x6 frozen
Jan 15 21:37:35 ubuntu kernel: [1355482.810769] ata3.00: failed command: WRITE FPDMA QUEUED
Jan 15 21:37:35 ubuntu kernel: [1355482.810786] ata3.00: cmd 61/10:d8:90:a0:53/00:00:00:00:00/40 tag 27 ncq dma 8192 out
Jan 15 21:37:35 ubuntu kernel: [1355482.810786]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Jan 15 21:37:35 ubuntu kernel: [1355482.810824] ata3.00: status: { DRDY }
Jan 15 21:37:35 ubuntu kernel: [1355482.810839] ata3: hard resetting link
Jan 15 21:37:37 ubuntu kernel: [1355485.044289] ata3: SATA link down (SStatus 1 SControl 300)
Jan 15 21:37:42 ubuntu kernel: [1355490.294132] ata3: hard resetting link
Jan 15 21:37:45 ubuntu kernel: [1355492.509352] ata3: SATA link down (SStatus 1 SControl 300)
Jan 15 21:38:07 ubuntu kernel: [1355497.707142] ata3: hard resetting link
```

the filesystem in dmesg reports:
```
[1359528.850122] systemd-journald[284]: Failed to write entry (22 items, 739 bytes), ignoring: Read-only file system
[1359528.851568] systemd-journald[284]: Failed to write entry (22 items, 750 bytes), ignoring: Read-only file system
[1359528.852924] systemd-journald[284]: Failed to write entry (22 items, 739 bytes), ignoring: Read-only file system
[1359528.854644] systemd-journald[284]: Failed to write entry (22 items, 750 bytes), ignoring: Read-only file system
[1359528.856205] systemd-journald[284]: Failed to write entry (22 items, 739 bytes), ignoring: Read-only file system
[1359528.857528] systemd-journald[284]: Failed to write entry (22 items, 750 bytes), ignoring: Read-only file system
[1359528.858951] systemd-journald[284]: Failed to write entry (22 items, 739 bytes), ignoring: Read-only file system
[1359528.860305] systemd-journald[284]: Failed to write entry (22 items, 750 bytes), ignoring: Read-only file system
[1359528.862256] systemd-journald[284]: Failed to write entry (22 items, 739 bytes), ignoring: Read-only file system
```

and the filesystem is unbootable, fsck requires run by hand, and probably some files are corrupt.


Linux ubuntu 5.11.0-41-generic #45-Ubuntu SMP Fri Nov 5 11:37:01 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
12:34
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 21.04
Release:	21.04
Codename:	hirsute"	AA
20395	Centos 7 i386 causes serious malfunctions when booted with ncpus>1	VirtualBox 6.1.22	2021-06-11T10:34:08Z	2021-06-11T10:34:08Z	2021-06-11T10:34:08Z	"I had occasion to try testing something on CentOS 7 i386. So I fetched CentOS-7-i386-NetInstall-2009.iso, and tried booting it on my Win10 host running VB 6.1.22, and strange behavior ensued. So I tried a premade 7 2009 image, which did the same, and a premade 7 2003 image, which did either the same thing or aborted.

First, it flooded with BUG: Bad page state in process swapper. Then, after a bit, the strangest behavior ensued - it started pegging multiple cores on the host, attempting to do anything with the VM window or other VB windows became infeasible (I needed to use Task Manager to kill the VM ultimately, the times it didn't abort and crash on its own) and my Caps Lock light started oscillating furiously, which continues even if it ultimately gets into the graphical login screen.

Running with n=1 cores, it seems to work fine.

Since Debian buster i386 works fine on this host, it's not impossible for it to be a flaw in what CentOS 7 is doing, but if it works on real hardware, then not working in a VM still seems like a flaw in the VM?"	rincebrain
17244	CentOS 7 Kernel-ml hangs	VirtualBox 5.2.0	2017-11-05T13:45:10Z	2017-11-05T13:45:10Z	2017-11-05T13:45:10Z	"Documented here: https://bugs.centos.org/view.php?id=11065

Kernel hangs on CPU making the guest graphics mainly unuseable unless you run all Linux in CLI

I'm using the Virtualbox guest additions as advised on the main site, aware that the latest won't compile properly.

Also doesn't like bridging with an RTL8188EE adapter properly, this could be because of the native drivers."	koolholio
18603	CentOS 7.6 guest in MacOS host receives spurious input when switching between desktop screens	VirtualBox 6.0.6	2019-04-26T20:34:19Z	2019-05-17T19:01:07Z	2019-05-17T19:01:07Z	"Host: MacOS 10.13.6 High Sierra
Guest: CentOS 7.6, running KDE

When using the MacOS ""Spaces"" virtual desktop feature, you can use Ctrl-Left arrow/Ctrl-Right arrow to move between desktops. If you make CentOS full screen, then move between virtual desktops, when you switch to the full screen VM, when you first click in the VM it receives some kind of input that causes windows (particularly maximized windows) to come out of maximized state and move locations. Sometimes, a desktop right-click contextual menu to be activated.

After this happens, CentOS gets in a state where it interprets clicks in the wrong location. For example, clicking on a foreground window results in a window behind receiving the click. Clicking on a title bar lets you drag a window, but double clicking on it does not maximize it as expected. However, if you click on the maximize button, the window maximizes.

Another symptom which seems to be related is when the VM is in full screen, moving the mouse pointer down to the bottom to cause the MacOS dock to show itself causes a similar situation to switching desktops."	Glen Kawano
20783	CentOS 9 Stream PXE boot failure	VirtualBox 6.1.30	2022-01-20T16:50:54Z	2022-01-20T16:53:41Z	2022-01-20T16:53:41Z	"Description of problem:
When installing el9 on a VirtualBox guest with an new vmdk files as the storage, the boot will fail with the error:

dracut: FATAL: iscsiroot requested but kernel/initrd does not support iscsi

A bug was submitted to Red Hat however the response is this is a VirtualBox issue.  For more details, please see/contribute to:
https://bugzilla.redhat.com/show_bug.cgi?id=2041094


How reproducible:
This consistently reproducible with implementing a work around. 

Steps to Reproduce:
1. VirtualBox 6.1.30 (Windows host)
2. Create a new Linux VM.
3. Create a new VMDK file as the disk device.
4. Boot the guest using PXE.

Actual results:
Kernel and initrd loads however the boot fails/stops with:

dracut: FATAL: iscsiroot requested but kernel/initrd does not support iscsi

Expected results:
Boot succeeds and ANACONDA start the installation.

Additional info:

If I install CentOS 8 on the guest/vmdk file and then reinstall with EL9, the installation succeeds.

I am attaching 2 console logs.  One is the initial attempt that fails.  The second contains the El8 then EL9 work-around for comparison.

"	MatthewDva
18354	Centos guest crashes when accessed form list of VMs in VBox	VirtualBox 6.0.2	2019-01-23T17:04:20Z	2019-01-23T17:04:20Z	2019-01-23T17:04:20Z	"I have a Centos guest running in VBox 6.0.2 running on a Win 7 PC.
When switching from another app to the guest VM by clicking on the VM in the list of VMs, the guest crashes and goes into ""aborted"" state"	Vinker
20313	CentOS7 poweroff BUG, Couldn't be written	VirtualBox 6.1.18	2021-04-22T07:17:06Z	2021-04-28T02:15:43Z	2021-04-28T02:15:43Z	"* Windows:  Win10 family Chinese version 20H2 19042.928 Mem 16GB
* CentOS: CentOS Linux release 7.9.2009 (Core) 
* Kernel: 3.10.0-1160.el7.x86_64
* Configuration
  * CPU：1cores
  * Mem: 1GB
  * Network Cards: 1 NAT
* Reproduce:

  Actually, every centos7 VM has the same problem, and it seems to have nothing to do with the virtual machine configuration. This problem occurs regardless of poweroff, shutdown, init 0 or ACPI shutdown commands. In addition, win10 1909 also has this problem.
  I wanna know is that a BUG, thank you!

* Error Message


{{{
VirtualBoxVM.exe - Application Error: 
The instruction at 0x00007FFED15D9B2C referenced memory at 0x00007FFED15D9B2C. The memory could not be written. 
Click on OK to terminate the program.
}}}
"	Justin-Young
18735	Certain VM (RedHat) crashing module VBoxNetFlt if launch any other VM	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
14805	Certificate error	VirtualBox 5.0.10	2015-11-11T12:15:07Z	2015-11-18T10:00:05Z	2015-11-18T10:00:05Z	"A fresh install on OSX 10.11.1 (15B42)

{{{
==> Library/VirtualBox/VBoxSVC.log <==
VirtualBox XPCOM Server 5.0.10 r104061 darwin.amd64 (Nov 10 2015 18:29:44) release log
00:00:00.000380 main     Log opened 2015-11-11T12:02:42.712965000Z
00:00:00.000383 main     Build Type: release
00:00:00.000392 main     OS Product: Darwin
00:00:00.000397 main     OS Release: 15.0.0
00:00:00.000401 main     OS Version: Darwin Kernel Version 15.0.0: Sat Sep 19 15:53:46 PDT 2015; root:xnu-3247.10.11~1/RELEASE_X86_64
00:00:00.000488 main     DMI Product Name: MacBookPro11,3
00:00:00.000528 main     DMI Product Version: 1.0
00:00:00.000538 main     Host RAM: 16384MB total, 5797MB available
00:00:00.000541 main     Executable: /Applications/VirtualBox.app/Contents/MacOS/VBoxSVC
00:00:00.000542 main     Process ID: 49823
00:00:00.000542 main     Package type: DARWIN_64BITS_GENERIC
00:00:00.105073 nspr-2   Home directory: '/Users/***/Library/VirtualBox'
00:00:00.105316 nspr-2   Loading settings file ""/Users/***/Library/VirtualBox/VirtualBox.xml"" with version ""1.12-macosx""
00:00:00.140966 nspr-2   HostDnsMonitor: old information
00:00:00.141006 nspr-2     no server entries
00:00:00.141014 nspr-2     no search string entries
00:00:00.141017 nspr-2     no domain set
00:00:00.141020 nspr-2   HostDnsMonitor: new information
00:00:00.141023 nspr-2     server 1: 192.168.254.1
00:00:00.141027 nspr-2     no search string entries
00:00:00.141030 nspr-2     domain: home
00:00:00.141040 nspr-2   HostDnsMonitorProxy::notify
00:00:00.141920 nspr-2   VD: VDInit finished

==> Library/VirtualBox/selectorwindow.log <==
VirtualBox GUI VM Selector Window 5.0.10 r104061 darwin.amd64 (Nov 10 2015 18:29:44) release log
00:00:00.919071 Log opened 2015-11-11T12:02:42.884731000Z
00:00:00.919072 Build Type: release
00:00:00.919086 OS Product: Darwin
00:00:00.919093 OS Release: 15.0.0
00:00:00.919101 OS Version: Darwin Kernel Version 15.0.0: Sat Sep 19 15:53:46 PDT 2015; root:xnu-3247.10.11~1/RELEASE_X86_64
00:00:00.919203 DMI Product Name: MacBookPro11,3
00:00:00.919261 DMI Product Version: 1.0
00:00:00.919269 Host RAM: 16384MB total, 5835MB available
00:00:00.919271 Executable: /Applications/VirtualBox.app/Contents/MacOS/VirtualBox
00:00:00.919271 Process ID: 49819
00:00:00.919272 Package type: DARWIN_64BITS_GENERIC
00:00:00.920639 GUI: UIMediumEnumerator: Medium-enumeration started...
00:00:00.977346 GUI: UISelectorWindow: Geometry loaded to: Origin=1055x628, Size=770x527
00:00:01.015731 SUP: Failed to open ""/dev/vboxdrv"", errno=13, rc=VERR_VM_DRIVER_NOT_ACCESSIBLE
00:00:01.455440 refreshCertificates/#1: Cert: SignatureAlgorithm (1.2.840.113549.1.1.11) does not match TbsCertificate.Signature (1.2.840.113549.1.1.11).  Cert: SignatureAlgorithm (1.2.840.113549.1.1.5) does not match TbsCertificate.Signature (1.2.840.113549.1.1.5).  Duplicate extension RTCRX509TBSCERTIFICATE_F_PRESENT_EXT_KEY_USAGE  InMem.Cert.TbsCertificate.T3.Extensions.paItems[#].ExtnValue.NameConstraints.T0.PermittedSubtrees.paItems[#]: Unexpected sequence type/flags: 0x2/0x80 (expected 0x10/0x20)
00:00:01.458365 refreshCertificates/#3: Found 1/275 SSL certs we/you trust (previously 0/0).
}}}

ls -l /dev/vbox*
{{{
crw-------  1 root  wheel   33,   0 Nov 11 11:57 /dev/vboxdrv
crw-rw-rw-  1 root  wheel   33,   1 Nov 11 11:57 /dev/vboxdrvu
crw-------  1 root  wheel   37,   0 Nov 11 11:57 /dev/vboxnetctl
}}}

kextstat | grep virtualbox
{{{
Index Refs Address            Size       Wired      Name (Version) UUID <Linked Against>
  488    3 0xffffff7f834fb000 0x60000    0x60000    org.virtualbox.kext.VBoxDrv (5.0.10) 23DD0853-7210-3AF2-85FA-1C7FF8F7D1BF <7 5 4 3 1>
  490    0 0xffffff7f83353000 0x8000     0x8000     org.virtualbox.kext.VBoxUSB (5.0.10) C5D33477-F93D-36AD-8748-1EB1105FB93A <489 488 39 7 5 4 3 1>
  492    0 0xffffff7f8335d000 0x5000     0x5000     org.virtualbox.kext.VBoxNetFlt (5.0.10) E5ABC825-5396-34A7-9B63-3A38E9142EEC <488 7 5 4 3 1>
  493    0 0xffffff7f83362000 0x6000     0x6000     org.virtualbox.kext.VBoxNetAdp (5.0.10) BEFC91DC-800F-3F16-8388-50584243FB30 <488 5 4 1>
}}}"	nusnewob
17988	Change Group Fails - Forward-slash in VM name (host: Windows 64-bit)	VirtualBox 5.2.18	2018-09-13T18:22:24Z	2018-09-13T18:22:24Z	2018-09-13T18:22:24Z	"When attempting to change the group of my OS/2 VM, via drag-n-drop, it '''fails to rename the settings file'''.

Here is the error message (it's rather small, so I'm just dumping it):


{{{
Failed to save the settings of the virtual machine OS/2 Warp 4 to C:\Users\veganaize\VirtualBox VMs\GNU_Linux\OS_2 Warp 4\OS_2 Warp 4.vbox.

Could not rename the settings file 'C:\Users\veganaize\VirtualBox VMs\GNU_Linux\OS_2 Warp 4\OS_2 Warp 4.vbox' to 'C:\Users\veganaize\VirtualBox VMs\GNU_Linux\OS_2 Warp 4\OS/2 Warp 4.vbox' (VERR_PATH_NOT_FOUND).

Result Code: E_FAIL (0x80004005)
Component: SessionMachine
Interface: IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}

}}}

'''''As you can see, near the end of the second line, it is attempting to replace the (previous) underscore with a forward-slash in the file's name.'''''"	veganaiZe
17793	Change in VM settings not taken into account with snapshots	VirtualBox 5.2.12	2018-05-31T03:46:27Z	2018-06-08T14:58:51Z	2018-06-08T14:58:51Z	"On a UEFI Windows 10 x64 virtual machine with multiple snapshot, change in the configuration are not taken into account when booting, even if the virtual machine file show that these change are saved.

For example, I tried to change the boot order to ''Network'' on that virtual machine, but it still tries to boot to ''DVD'' and then ''Hard Drive'' (if I press F12 and go to '''Boot Manager''', ''Network'' is not even there and the order doesn't correspond to the one saved.

Virtual Box version 5.2.12 r122591 running on Windows 10 Pro x64 v1709"	Michael Tremblay
19137	Change log rotation scheme from VBox.log[.<number>] to VBox[.<number>].log	VirtualBox 6.0.14	2019-12-08T07:35:04Z	2019-12-08T16:11:18Z	2019-12-08T16:11:18Z	"== Current situation ==

Not sure why it first got implemented as is, but when there's a log rotation, the rotation algorithm calls for the ""`.<number>`"" to be appended to the ""`VBox.log`"" name, resulting in ""`VBox.log.1`"", ""`VBox.log.2`"", ""`VBox.log.3`"", or more, depending on your rotation settings:
{{{
VBoxManage setproperty loghistorycount
}}}

That naming scheme is not very helpful when trying to open/display the logs, because they have a ""`.<number>`"" extension, which could be ''anything'', with the most common use that the file is a part of a multi-part archive (ZIP and RAR come to mind).


== Proposed solution ==

* Change the naming scheme/logic/altorithm from ""`VBox.log.`'''`<number>`'''"" to ""`VBox.`'''`<number>`'''`.log`"".

That way there are always ""`VBox[.<number>]`'''`.log`'''"" files, which can be associated and opened with your favorite application.

'''NOTE''' \\
The same logic applies to the PNG screen-capture files in case of a Guru Meditation, should be addressed there as well."	Socratis
13928	Change of behavior of Host Only Network	VirtualBox 4.3.24	2015-03-06T10:52:19Z	2015-03-06T10:52:19Z	2015-03-06T10:52:19Z	From version 4.3.22 you have added a value for *NdisDeviceType register entry. A value for that entry as NDIS_DEVICE_TYPE_ENDPOINT implies that Windows ignores the endpoint device when it identifies networks. I was using a virtual linux firewall connected to the bridged interface to create a network with different OS including the access to internet from the host. After this change in 4.3.22 Windows does not detect the virtual network and there is no connection from most windows applications.	luisds
8686	Change process directory to / before forking	VirtualBox 4.0.4	2011-04-06T17:14:27Z	2011-05-12T17:42:08Z	2011-05-12T17:42:08Z	"Unfortunately, the startup directory of VBox* services is kept while these daemons run even when nothing else is using that directory/filesystem during execution. This prevents the underlying filesystem from being umounted when needed.

I created a patch to change it to / on Unix-like systems, similar to what GNU daemon(3) function does.
"	blade
7083	character encoding munged in CLI on Windows	VirtualBox 3.2.6	2010-06-27T13:41:42Z	2010-06-27T18:11:58Z	2010-06-27T18:11:58Z	"I must admit that I don't know if VirtualBox is to blame or Windows 7. I have an otherwise US English installation of Windows, but if I set the language in VirtualBox to French, for example, and create a virtual machine, it will name certain things in French. For example, the storage controller is called ""Contrôleur IDE"". However, when I use the VBoxManage showvminfo command it shows as ""Contr¶leur IDE"" (the o with a circumflex gets replaced by a paragraph mark). I have not tried to use the storageattach command yet with this improperly named/displayed controller name, but I suspect I would run into trouble. And, other than me guessing what the name is supposed to be because I know the language well enough, there does not seem to be a way to verify what the name is. If I named it something else more obscure using this apparently incompatible character encoding, I'd have no way to display what it is actually stored as. 

Also, descriptions or snapshot names are displayed wrong. The é (e with acute accent) is replaced by a ú (u with acute accent). This happens in both cmd.exe and powershell interfaces.

I wish everyone would just use UTF, but apparently someone here is not and doesn't realize that the other guy is not. I suspect Windows is to blame, but I'm not sure. In the graphical user interface, comments and names continue to appear correctly as I typed them or as they were automatically created if I switch from French to English. However, certain things like the name of the storage controller are not displayed in the GUI.

-Example-

.\VBoxManage showvminfo browse

Storage Controller Name (0):            Contr¶leur IDE

.\VBoxManage showvminfo WS2003R2-sctltest1

Storage Controller Name (0):            IDE Controller"	$roman
17703	Check for Updates menu option	VirtualBox 5.2.10	2018-04-22T03:57:01Z	2018-04-22T10:31:54Z	2018-04-22T10:31:54Z	"I'm getting this since 5.2.8 and I just updated to 5.2.10 but this persists.


{{{
The network operation failed with the following error: 
During network request: Wrong SSL certificate format.
}}}

Yes, I know I can download the updates from the website, but now I don't get notified of an update from within the application."	Daniel Bair
13341	Chipset and problems	VirtualBox 4.3.14	2014-09-03T12:51:28Z	2014-11-24T12:30:55Z	2014-11-24T12:30:55Z	"Host  - Windows 2003 Std (32 bit)
Guest - Oracle Linux 6.5 (64 bit)

VirtualBox-4.3.14-95030-Win and VirtualBox-4.3.15-95713

If Chipset set to '''PIIX3''':[[br]]

The network is working properly.

# cat /proc/cpuinfo 
> processor	: 0[[br]]
> vendor_id	: GenuineIntel[[br]]
> cpu family	: 6[[br]]
> model		: 23[[br]]
> model name	: Intel(R) Xeon(R) CPU L5420  @ 2.50GHz[[br]]
> stepping	: 6[[br]]
> microcode	: 0x60b[[br]]
>> cpu MHz	: 0.000[[br]]
> cache size	: 6144 KB[[br]]
> physical id	: 0[[br]]
> siblings	: 4[[br]]
> core id		: 0[[br]]
> cpu cores	: 4[[br]]
> apicid		: 0[[br]]
> initial apicid	: 0[[br]]
> fpu		: yes[[br]]
> fpu_exception	: yes[[br]]
> cpuid level	: 5[[br]]
> wp		: yes[[br]]
> flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx lm constant_tsc rep_good nopl pni ssse3 lahf_lm[[br]]
> bogomips	: 4571.13[[br]]
> clflush size	: 64[[br]]
> cache_alignment	: 64[[br]]
> address sizes	: 38 bits physical, 48 bits virtual[[br]]
> power management:[[br]]

[[br]]
[[br]]
If Chipset set to '''ICH9''':[[br]]

# cat /proc/cpuinfo[[br]]
...[[br]]
cpu MHz  : '''2394.048'''[[br]]
...[[br]]

Network interface not work (on guest network interface is up, but there is no network traffic)[[br]]
eth0 - RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)"	PepeN
18061	Choosing 64-bit Windows 7 machine, once I launch it the OS is 32-bit	VirtualBox 5.2.20	2018-10-18T13:38:09Z	2018-10-26T00:16:08Z	2018-10-26T00:16:08Z	I am trying to download this 64-bit software on the my VM. However, I am getting the 216 error. Before launching my Windows 7 VM I make sure I change it to a 64-bit machine, but once launched I check the properties of the computer and it says 32-bit. I created a new vmdk and new vdi and still runing into the same issue.	MikeJack
15848	Choppy Audio and Slow Flash Video in VirtualBox 5.1	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
21393	chrash of VM during shutdown	VirtualBox 6.1.38	2023-01-03T19:26:43Z	2023-01-03T19:26:43Z	2023-01-03T19:26:43Z	I have frequent crashes during the shutdown of the virtual machine.	tiria
17714	Ciritical Error during Windows Update (possibly VERR_PAGE_TABLE_NOT_PRESENT related)	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
17706	Civilzation II (2) crash at opening	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
20214	click close button freez machine	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
19445	Clipboard broken	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
20909	Clipboard exchange between Devua host and Windows guest stopped working	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
18357	Clone fails because newly created vdi is attached to clone it just made.	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
15403	"Clone Function Errors Out when using ""/"" Character"	VirtualBox 5.0.20	2016-05-10T19:30:18Z	2018-03-16T14:36:16Z	2018-03-16T14:36:16Z	"I am trying to create a cloned VM using the following name in the Clone Disk wizard:

Windows 7 / Visual Studio 15 Preview

This worked in prior builds of VirtualBox.  It doesn't seem to like the ""/"" in the cloned disk's name, and it errors out and won't create it.

When I change the cloned name in the wizard to ""Windows 7 - Visual Studio 15 Preview"" (i.e. replacing the ""/"" with a ""-""), then it works.

Again, I had no problem using this in my clone name in prior builds.  I am using the latest build (i.e. 5.0.20.106931)

Please advise."	Master VB Guru
16328	Clone with Everything, Linked Clone errors	VirtualBox 5.1.12	2016-12-25T20:23:28Z	2018-06-13T23:41:35Z	2018-06-13T23:41:35Z	"* Select a VM (""Test"") and choose ""Clone"". The VM did not have snapshots, but it doesn't really matter.
* Switch to ""Expert Mode"", if not already selected.
* The defaults are: Full Clone (for CloneType), Current machine state (for Snapshots).
* Select in that order: Everything (for Snapshots), Linked Clone (for CloneType). Press ""Clone"":
{{{
Failed to clone the virtual machine Test.

Linked clone can only be created for a single machine state.

Result Code: NS_ERROR_INVALID_ARG (0x80070057)
Component: SnapshotMachine
Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
}}}
* We return to the Clone dialog. If you Cancel out, you see the results:
 * No ""Test Clone"" VM has been created.
 * A snapshot for the ""Test"" VM has been created: ""Linked Base for Test and Test Clone""."	Socratis
17670	clonevm --groups does not create new group	VirtualBox 5.2.8	2018-04-06T10:55:31Z	2018-04-20T19:29:27Z	2018-04-20T19:29:27Z	`VBoxManage clonevm VM1 --groups /NewGroup --register` successfully clones and registers `VM1` (placing it in a subdirectory `NewGroup`), but does not create the group `/NewGroup`. (`VBoxManage list groups` does not show the new group.)	BrianNixon
18763	CMPXCHG16B	VirtualBox 6.0.10	2019-07-17T03:48:17Z	2019-07-18T11:29:54Z	2019-07-18T11:29:54Z	"Just upgraded from v5.32 to v6 here, but get this error on about half of the VM's I am trying to upgrade.  I didnt see where a user can change this, please help!
Occurs when I try to launch the VM's.
Thank you.

Duplicate config values '/CPUM/CMPXCHG16B' and '/CPUM/IsaExts/CMPXCHG16B' - please remove the former! (VERR_DUPLICATE).


Result Code: 
E_FAIL (0x80004005)
Component: 
ConsoleWrap
Interface: 
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
"	LindaCarter
18446	Code NS_ERROR_FACTORY_NOT_REGISTERED (0x80040154) - Class not registered (extended info not available)	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
8982	CoDeSys on windows xp work with time delays	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
4208	Command-Q not passed to client OS	VirtualBox 2.2.4	2009-06-08T16:32:52Z	2017-09-30T06:44:01Z	2017-09-30T06:44:01Z	"
Certain key combinations are not being passed through to the client OS. 

Usecase: Command-Q (in X11 as Meta-Q) to quit an application in the client OS results in the  ""Close virtual machine"" dialog (and leads to a 'stuck' command key modifier after dismissal, until meta is pressed again).

Also see Command-H for another example of this problem

http://www.virtualbox.org/changeset/1320 describes a fix, but from what I can tell has either not been applied, or does not work.

Partially related to Ticket #1668, but currently the exhibited behaviour is inconsistent with the behaviour of other keyboard combinations (i.e. pass everything to the client) - 1668 describes how passing through these key combos, if _optional_, may still be useful to some."	Gil Pinheiro
14824	Command-W does not close VirtualBox.	VirtualBox 5.0.10	2015-11-14T00:24:55Z	2015-11-17T10:40:00Z	2015-11-17T10:40:00Z	On the main VirtualBox window (the GUI window that gives a list of virtual machines and its information), the Command-W keyboard shortcut does not close VirtualBox. Annoying as I use the Command-W keyboard shortcut to close windows.	Bug Tracker
7763	configure needs to check for glib2	VirtualBox 3.2.10	2010-11-25T21:30:38Z	2010-11-25T21:34:25Z	2010-11-25T21:34:25Z	"{{{
timeless-mbp:vbox-svn timeless$ ./configure --disable-java --disable-python --disable-opengl --disable-docs --disable-hardening --with-openssl-dir=/opt/local/var/macports/software/openssl/1.0.0a_0/opt/local/
...
Successfully generated '/Users/timeless/devel/virtualbox.org/vbox-svn/AutoConfig.kmk' and '/Users/timeless/devel/virtualbox.org/vbox-svn/env.sh'.
Source '/Users/timeless/devel/virtualbox.org/vbox-svn/env.sh' once before you start to build VBox:

  source /Users/timeless/devel/virtualbox.org/vbox-svn/env.sh
  kmk


  +++ WARNING +++ WARNING +++ WARNING +++ WARNING +++ WARNING +++ WARNING +++
  Hardening is disabled. Please do NOT build packages for distribution with
  disabled hardening!
  +++ WARNING +++ WARNING +++ WARNING +++ WARNING +++ WARNING +++ WARNING +++

Enjoy!
timeless-mbp:vbox-svn timeless$   source /Users/timeless/devel/virtualbox.org/vbox-svn/env.sh
timeless-mbp:vbox-svn timeless$   kmk
Package glib-2.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `glib-2.0.pc'
to the PKG_CONFIG_PATH environment variable
No package 'glib-2.0' found
}}}

I wish configure had complained."	timeless
16369	Configuring VirtualBox OSE to build with OpenSSL 1.1.0 on Windows	VirtualBox 5.1.12	2017-01-10T11:03:57Z	2017-01-11T09:21:04Z	2017-01-11T09:21:04Z	"Currently it is not possible to configure VBox OSE to compile with OpenSSL 1.1.0 libraries on Windows.
The configure.vbs script fails:


{{{
Checking for openssl...
error: Can't locate openssl. Please consult the configure.log and the build requirements.
}}}

The problem is that with OpenSSL 1.1.0 the libraries are now called libcrypto.lib and libssl.lib. However configure.vbs is still looking for libeay32.lib and ssleay32.lib."	IndyJones
20329	Connect bluetooth headset causes freeze	VirtualBox 6.1.18	2021-04-29T18:06:10Z	2021-04-29T18:06:10Z	2021-04-29T18:06:10Z	"Frequently, when I turn on or turn off my bluetooth headset, the Guest OS will freeze. It will no longer respond to any mouse clicks of keyboard presses.

Generally I am in full screen mode. I was recently in windowed mode when this happened and attempting to open the File menu was also unresponsive. Windows then marked the window as Not Responding.


Virtualbox Version 6.1.18 r142142 (Qt5.6.2)
Host: Windows 10 (10.0.18363 Build 18363)
Guest: Ubuntu 20.04


[This thread](https://forums.virtualbox.org/viewtopic.php?f=6&t=94233) contains other users reporting the same issue with slight different pairings of Virtualbox running on Windows10 host with a Linux Guest OS."	plannigan
17786	Consider using Digital Mars C compiler	VirtualBox 5.2.12	2018-05-23T17:30:02Z	2018-07-24T11:11:07Z	2018-07-24T11:11:07Z	Consider using Digital Mars C compiler for things like the BIOS. It should have full support for x86 segmentation etc. It is now fully open source: https://github.com/DigitalMars/Compiler	Yuhong Bao
18463	console boot hangs/highcpu without vbox serial & console=ttyS0 in grub	VirtualBox 6.0.4	2019-02-28T23:57:27Z	2019-03-01T11:15:46Z	2019-03-01T11:15:46Z	"When using a cloud-init image like https://cloud-images.ubuntu.com/bionic/current/bionic-server-cloudimg-amd64.ova
, that uses grub console=ttyS0, boot hangs and high cpu occurs.

You can fix via workaround on cloud init image by removing console=ttyS0 from GRUB_CMD_LINUX_DEFAULT
```
sudo sed -i 's/ console=ttyS0//g' /etc/default/grub.d/50-cloudimg-settings.cfg
sudo update-grub
```

but then `virsh console my-kvm-qemu-vmnane` on Linux doesn't return console information

Workaround is to add a serial port to vm via ""raw with /dev/null""

It works fine in VMWare and other vms just not Virtualbox. This seems like it would be a Virtualbox issue thought there is a bug here https://bugs.launchpad.net/cloud-images/+bug/1573095"	busk
19822	Constant and varied problems installing ubuntu VM from Windows host	VirtualBox 6.1.10	2020-08-19T18:48:57Z	2020-08-19T18:48:57Z	2020-08-19T18:48:57Z	"I've been using VirtualBox for over a decade with few if any problems, but growing instability with Ubuntu from Win10 has at this point made it unusable.  The problem started off with me not being able to update things from ubuntu itself, and progressed from there.  At this point, I have completely uninstalled VirtualBox, deleted my user/.VirtualBox/ directory, then reinstalled VirtualBox.  When I try to install Ubuntu 20.0.4.1 (ubuntu-20.04.1-desktop-amd64.iso) something always goes wrong:  it will freeze partway through the installation (at different points every time).  I finally got it to go through the entire installation process, and now the system itself is unstable:  I get multiple popup windows saying that it 'encountered a problem' and asking if I want to report it.  One time, it hung trying to run 'Terminal'.  Rebooting let me run Terminal, but then froze doing 'apt-get update'.

Things I have tried:
  * Changing the amount of RAM available.  More seemed to help (several hundred times more than the 'recommended' amount), but not consistently.
  * Changing the network from NAT to Bridged (cf https://askubuntu.com/questions/149170/all-my-ubuntu-vms-have-apt-get-update-problems)

I'm happy to provide more information; not sure what "	lpsmith
16711	Convert TRIM commands to hole-punching over raw flat disk image.	VirtualBox 5.1.22	2017-04-29T15:34:49Z	2017-04-29T15:39:24Z	2017-04-29T15:39:24Z	"We can create a raw disk via:
VBoxManage internalcommands createrawvmdk -filename rawtest.vmdk -rawdisk /path/to/rawdisk.img

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.

My request is for the RAW disk image backend, when receiving a TRIM command from the guest, then hole-punching the RAW disk image file. This will save disk space of the host system.
"	jack lee
15960	Copying of HTML from windows host to Firefox on a Linux guest doesn't work	VirtualBox 5.1.6	2016-09-20T16:57:31Z	2016-09-26T07:18:07Z	2016-09-26T07:18:07Z	"I don't know if it is a problem of Firefox or of VirtualBox itself. Copy-pasting HTML works perfectly fine to e.g. Chrome and LibreOffice Writer. But for some reason it doesn't work if pasting is done to Firefox. Though if you copy HTML directly from the linux guest (e.g. from Chrome, Firefox or LibreOffice) and paste to Firefox on the same guest - it works fine. I've also tried to examine the content of X11 clipboard in the guest and ""text/html"" target seems to be perfectly fine (when obtained with some tools like xclip). I've also tried to write the exact content of ""text/html"" provided by VirtualBox in the guest to the X11 clipboard (with ""xclip -t text/html -selection clipboard"") - and if I do that, then pasting works fine as well. It would be really great, if you could confirm that the problem is in the way how Firefox reads the content and not in the way how VirtualBox is providing this content to Firefox - then I would create a bug ticket on the Firefox bug tracker instead. 

Thnx in advance if you decide to investigate this issue."	mskov
20945	Corner dragging second dual monitor screen causes monitor close without warning	VirtualBox 6.1.32	2022-05-17T00:46:57Z	2022-05-17T00:46:57Z	2022-05-17T00:46:57Z	"Using the cursor and left clicking the double arrow to expand/contract monitor 2 will cause the monitor to suddenly close with no warning.

You have to go back to the View menu and click on ""Enable"" Virtual Screen 2 to reopen it.

Using Minimize/Maximize buttons on Virtual Screen work as normal.  The sudden close only happens when dragging the corner to resize it.

System: Unbuntu 20.4
Virtual Box: Oracle VM Virtual Box 6.1
    In VBox Settings assigned Video settings 40MB


It's a minor issue, just thought engineering might want to know it exists, should be duplicable."	Tony C
15045	corrections in OSE build	VirtualBox 5.0.14	2016-01-20T07:54:54Z	2016-01-30T18:30:29Z	2016-01-30T18:30:29Z	"1. Incorrect check of renamed variable (v4->v5): bug5man_ose.patch
2. Absent implib's: ose_st_ssl_web.patch
3. Incorrect check of non-standard latex place: pdf_ose.patch"	yjh
16442	Could not install Oracle_VM_VirtualBox_Extension_Pack-5.1.14-112924	VirtualBox 5.1.14	2017-02-02T16:58:46Z	2017-03-09T15:28:40Z	2017-03-09T15:28:40Z	"Hello,

on a Windows 10 machine, trying to open Oracle_VM_VirtualBox_Extension_Pack-5.1.14-112924 results in 

This application failed to start because it could not find or load the qt platform plugin ""windows"" in """".
Reinstalling the application may fix this problem.

VBox 5.1.14 - latest version is installed and running properly.
Tried repairing VBox but no change in the problem.

What can I do ? 

Thanks
E. Gimissis
MSc ICSD
MCP"	elrod68
15775	Could not read from the boot medium. System halted	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
11277	CPU Hotplug prevents change in vCPU number	VirtualBox 4.2.4	2012-12-09T23:12:26Z	2016-08-16T10:04:45Z	2016-08-16T10:04:45Z	"After setting up a VM with more than one vCPU and CPU hotplug off, then activating the CPU hotplug feature, it is not possible to reduce the amount of vCPU as long as hotplug is enabled.[[BR]]

Steps to reproduce :[[BR]]
1. Create a VM with 2 or more CPUs
2. Enable CPU hotplug via vboxmanage
3. Start the VM then stop the VM
4. Reduce the amount of CPUs using vboxmanage modifyvm VM --cpus x
5. This will fail with the following code :
{{{
NS_ERROR_INVALID_ARG (0x80070057) There is still a CPU attached to socket x.Detach the CPU before removing the socket.
}}}
The only way to make this work is to disable the hotplug feature before setting the amount of vCPU.

IMO this error shouldn't popup as the VM is a PowerOff state and therefore hotunplugging a CPU doesn't make sense..."	Max D
7816	"CPU Idle load hi with ""divider=10"""	VirtualBox 3.2.12	2010-12-10T02:57:43Z	2010-12-10T02:57:43Z	2010-12-10T02:57:43Z	"Idle load with CentOs 5.5 client on OSX 10.6.5 host is ~ 75%. I added ""divider=10"" to grub.conf post additions, and have rebooted the client and the application; still idle load is high.

"	Dale Douglas
19539	CPU overcranks on Macbook Air i5 early 2020 after sleep (either guest OS or host)	VirtualBox 6.1.6	2020-04-28T18:18:55Z	2020-05-01T17:05:04Z	2020-05-01T17:05:04Z	Debian and Ubuntu guests operate normally until after waking from sleep -- either suspending the guest while leaving the OS awake, or sleeping the host OS with the guest either awake or asleep. After waking from any of those states, the CPU maxes out to the thermal limit and stays there until the guest is halted, after which CPU behavior reverts to normal and temperatures stabilize at normal levels (40-55 C depending on other operations). This happens even when all other applications are off. Since it includes both guest and host, this may be two separate problems. Occasionally it does not happen with guest suspend, but it is 100% with the host os sleep. This does not happen on my 2018 Mac Mini, so as far as I know it's specific to the new Macbook Air.	dmnorth
19540	CPU overcranks on Macbook Air i5 early 2020 after sleep (either guest OS or host)	VirtualBox 6.1.6	2020-04-28T18:19:02Z	2020-04-29T02:07:12Z	2020-04-29T02:07:12Z	Debian and Ubuntu guests operate normally until after waking from sleep -- either suspending the guest while leaving the OS awake, or sleeping the host OS with the guest either awake or asleep. After waking from any of those states, the CPU maxes out to the thermal limit and stays there until the guest is halted, after which CPU behavior reverts to normal and temperatures stabilize at normal levels (40-55 C depending on other operations). This happens even when all other applications are off. Since it includes both guest and host, this may be two separate problems. Occasionally it does not happen with guest suspend, but it is 100% with the host os sleep. This does not happen on my 2018 Mac Mini, so as far as I know it's specific to the new Macbook Air.	dmnorth
14057	CPU spikes when concurrently using an XP VM and its complete clone on Debian	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
15925	Crackling sound with Windows 10 anniversary update	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
19588	Crash - referenced memory at 0x0000000000000000	VirtualBox 6.1.6	2020-05-15T16:29:56Z	2022-02-14T21:08:06Z	2022-02-14T21:08:06Z	"Host: Windows 10, 1803

Guest: Linux Mint, 18.3 Cinnamon 64-bit, 3.6.7

Guest Browser: Pale Moon, 28.9.3 (64-bit)

Web Site: 'https://coronavirus.jhu.edu/map.html'

Crash: ""VirtualBoxVM.exe - Application Error""

""The instruction at 0x00007FFA7B9075AD referenced memory at 0x0000000000000000. The memory could not be read.""

Status: Hard, reproducible.

Attached: C:\VMs\Mint18\Mint18-2020-05-15-12-12-36.log
"	Mark Filipak
18750	Crash / BSOD of Windows 10 host when running any VM	VirtualBox 6.0.8	2019-07-09T10:57:14Z	2019-07-10T09:07:37Z	2019-07-10T09:07:37Z	"I used to be able to run my dozen of VM on this Windows 10 Pro PC.
But probably after an update, I'm now not able to run any of my VM.

As soon as I start a VM, the VM seems to start then I get the BSOD.

I looked at this issue in the whole bugtracking database but even after disabling completely Hyper-V I still have the problem.

Uninstalled hyper-v from the control panel + through power shell 
{{{
Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V
}}}
 command

"	egavaldo
17485	Crash 0xc0000005 after host suspend (Linux guest, Windows 7 host)	VirtualBox 5.2.6	2018-01-19T15:58:16Z	2019-09-12T12:38:50Z	2019-09-12T12:38:50Z	"Crash occurred twice for me.
{{{
03:20:07.990450 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 0000000000001140!!!
03:20:07.990470 
03:20:07.990471 ExceptionCode=0xc0000005 ExceptionFlags=0x00000000 ExceptionAddress=000007fefb15be75
03:20:07.990477 ExceptionInformation[0]=0000000000000000
03:20:07.990482 ExceptionInformation[1]=0000000000000070
}}}
!VirtualBox show error message, then virtual machine become turned off."	ukolovda
18346	Crash after reboot Windows 10 guest	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
19375	Crash bsod on guest machine	VirtualBox 6.1.4	2020-03-03T19:41:38Z	2020-03-03T19:41:38Z	2020-03-03T19:41:38Z	"Mode graphics : vboxvga with dual screen[[BR]]
with latest virtualbox addition[[BR]]
Virtualbox version 6.1.4[[BR]]
guest machine : Windows 7 [[BR]]
When i logged on my guest machine , i have a bsod[[BR]]

Thank.[[BR]]
"	Sizy458
13675	Crash due to windowed screen spanning monitors	VirtualBox 4.3.20	2014-12-07T09:48:09Z	2014-12-07T09:48:09Z	2014-12-07T09:48:09Z	"4.3.2 I can stretch the display across multiple monitors with no issues. The display shrinks back to the main display when the system hibernates but can just be resized on wake-up.
All releases after this do not function this way, resulting in BSOD crash.
4.3.20 I can't even stretch the window beyond the main display.

There is a memory.dmp of 350mb created before I rolled back but it may not be complete as I usually just close the VM down and start over.
LMK if a full dump is of any use and I'll reinstall an interim release and replicate the crash."	akaAlso
16484	Crash during guest OS startup	VirtualBox 5.1.14	2017-02-12T18:21:02Z	2017-02-12T18:21:02Z	2017-02-12T18:21:02Z	"VM crashes during guest OS startup: blue screen on Windows 7, kernel panic on Ubuntu
The crashed appeared suddenly: I do not see any changes in guest and host OS.

Guest OS: Windows 7 54 bit, Ubuntu 64 bit
Host OS: Windows 10 64 bit, version 10.0.14393
VitualBox version: 5.1.14, 5.1.15
"	airatsa
21289	crash during shutdown	VirtualBox 6.1.38	2022-11-20T00:08:27Z	2022-11-20T00:08:27Z	2022-11-20T00:08:27Z	the system crashes when I shutdown it	tiria
18441	Crash host	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
17300	crash of all virtual machines	VirtualBox 5.2.0	2017-11-22T16:30:08Z	2018-01-18T14:35:20Z	2018-01-18T14:35:20Z	"Running several VM's.  When all VM's crash with same error simultaneously.  Log of one vm's crash is attached.  This has happened twice over the last week or two. 

Cannot say what steps are needed to reproduce as it seems random when this occurs."	ArtZ
19679	Crash of VirtualBoxVM 6.1.10 Ubuntu 18.04 guest on macOS 10.15.5 host after installing 6.1.10 guest additions	VirtualBox 6.1.10	2020-06-25T09:31:23Z	2020-07-18T01:38:24Z	2020-07-18T01:38:24Z	"Hi,

I've got a crash of VirtualBoxVM 6.1.10 Ubuntu 18.04 guest on macOS 10.15.5 host after installing 6.1.10 guest additions. This crash occurs every time I try to boot up this VM right after entering the Login credentials into the guest. See attached log files"	Lars Sonchocky-Helldorf
19206	Crash of VirtualBoxVM running ReactOS 0.4.12 guest on macOS 10.14.6 host	VirtualBox 6.1.0	2020-01-07T20:55:19Z	2020-01-07T20:55:19Z	2020-01-07T20:55:19Z	I am running VirtualBox Version 6.1.0 r135406 (Qt5.6.3) on a macOS Mojave 10.14.6 host. Guest OS is ReactOS 0.4.12. I got a crash while booting ReactOS	Lars Sonchocky-Helldorf
16722	Crash on changing optical drive assignment	VirtualBox 5.1.22	2017-05-03T09:40:19Z	2017-05-03T11:22:00Z	2017-05-03T11:22:00Z	"Hi,
right from clean install of 5.1.22, when I prepared initial config of Debian64 VM, I went to properties, wanted to delete IDE controller (optical disk) and use opt drive under existing SATA there, it crashed - and always crashes."	peterg91
17912	Crash on Dell docking station disconnect	VirtualBox 5.2.12	2018-08-03T12:44:02Z	2019-03-11T10:30:45Z	2019-03-11T10:30:45Z	"Hello,

I'm using VirtualBox 5.2.12 r122591 (Qt5.6.2) on Windows 7 x64 Dell Latitude E7440. This laptop is usually connected with the docking station to which I have connected 2 monitors. One of those monitors is also a USB hub to which I have attached USB Wifi. I use this Wifi in my Virtual Machine.

My VM is also a Windows 7 x64 system.

Now... sometimes (not everytime but several times per week) when I disconnect laptop from docking station - VirtualBox crashes (only the window with virtual machine, the main window with list of machines is still open).
This isn't a new issue - with previous versions I had the same problem.


{{{
03:44:32.016942 VUSB: Detached '000000000eebcd30[proxy 7392:7811]' from port 1 on RootHub#0
03:44:32.026037 
03:44:32.026039 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 000000000000264c!!!
03:44:32.026081 
03:44:32.026082 ExceptionCode=0xc0000005 ExceptionFlags=0x00000000 ExceptionAddress=000007fed194d510
}}}
"	dariuszszyc
21032	Crash on start up	VirtualBox 6.1.36	2022-07-24T19:24:34Z	2022-08-20T13:35:32Z	2022-08-20T13:35:32Z	"I recently updated to 6.1.36 and previously working machines now crash. I have redownloaded the usb3 extensions before positing this bug.

To reproduce :-
Take a working machine of any guest type.
Change usb to usb 3
Create a usb disk controler
(still boots)
Attach a disk image to the usb controller
(does not boot : ... references memory at 0x00000000)"	sceedy
19580	Crash on switch from guest(Win10) to host(Catalina) window	VirtualBox 6.0.20	2020-05-13T21:49:58Z	2020-07-22T09:43:50Z	2020-07-22T09:43:50Z	"VBox crashes periodically after mouse click outside guest window.
"	Yauheni
19978	Crash reboot VM UEFI Windows Server	VirtualBox 6.1.14	2020-10-18T13:01:23Z	2020-10-19T10:54:03Z	2020-10-19T10:54:03Z	A VM configured for Windows Server 2019 UEFI with VM VirtualBox Extension Pack 6.1.14, hangs on reboot (random). Windows 10 2004 host. This problem has occurred since the first version 6.0.	tiagocoelho2
18983	Crash Virtualbox guest bcause of segfalut of libc	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
14044	Crash Virtualbox on Windows 8.1	VirtualBox 4.3.26	2015-04-11T17:42:10Z	2015-04-21T18:43:49Z	2015-04-21T18:43:49Z	"Hello. 

Virtualbox Crash when i use file explore (in import application, import vdi...). 

Virtualbox end to tun. I use virtualbox 4.3..26.

Regards"	bernalau
20096	Crash when powering off guest OS	VirtualBox 6.1.16	2020-12-19T01:59:57Z	2020-12-19T01:59:57Z	2020-12-19T01:59:57Z	"Host: Windows 10 build 17763 amd64
Guest: Ubuntu 18
1. Start guest OS
2. Sleep/resume host computer (not sure if this is necessary but seems related)
3. From within the guest OS, select the power off setting.
Message box appears: The instruction at 0x0000&FF9E4808561 referenced memory at 0x0000000000000021. The memory could not be written.

This crash is intermittent and happens prior to the screen resizing to the linux text-based shutdown screen (i.e. guest is still running X)"	jkriegshauser
17072	crash when reloading vm settings while editing USB filter	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
20028	Crash when restoring Fedora virtual machine from a Snapshot	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
20002	Crash when restoring machine state and launching or selecting program from favorites	VirtualBox 6.1.16	2020-10-27T14:38:16Z	2020-10-27T14:38:16Z	2020-10-27T14:38:16Z	"Windows 10 host and Ubuntu Desktop guest.

Whenever I save machine state with something running, I get a crash when I restore (the crash comes when I select a favorite, whether it was running or not). I have seen this in various scenarios (basically any other than shutting down with nothing running at all). I have attached logs for the following scenario.

1. Launch Ubuntu VM.
2. Start LibreOffice Writer (really can be anything, Visual Studio Code will do the same thing).
3. Click the 'X' in the far upper right to close VB. Select 'Save the machine state'.
4. In VB with the Ubuntu machine selected, click 'Start'.
5. The machine is restored, with the LibreOffice Writer document open.
6. Click on Chrome in the Favorites panel, trying to launch it (again, I'm not sure it matters what program you try to launch here).
7. The crash window immediately comes up (the one with the OK and IGNORE buttons telling me I have to shut down and where the logs are, etc.)

This behavior is consistent. It basically makes the program unusable because I have to shut down the machine whenever I close VB.
"	mark6139
15424	Crash when suspending Win10 (14342) guest	VirtualBox 5.0.20	2016-05-17T04:51:43Z	2016-08-22T04:44:01Z	2016-08-22T04:44:01Z	"... on a Win8.1 host. Both 64bit.

Screenshot of the Error http://i.imgur.com/OVeyzzg.png"	Stanzilla
19982	Crash when using vscode on linux guest	VirtualBox 6.1.14	2020-10-20T17:19:14Z	2020-10-20T17:19:14Z	2020-10-20T17:19:14Z	"Hello,

VB crashes when I use vscode on a linux ( Ubuntu ) guest. It crashes when I right click to display a menu.
I join the crash  logs and a copy of the error message ( ""memory state cannot be written"" ). Is this enough to start to debug or do you need more information ? 

Thanks !

Crash logs : 

151:19:24.402862 AIOMgr: Async flushes not supported
152:49:24.051989 
152:49:24.051991 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 0000000000004184!!!
152:49:24.053107 
152:49:24.053108 ExceptionCode=0xc0000005 ExceptionFlags=0x00000000 ExceptionAddress=00007ffc189728c2
152:49:24.053118 ExceptionInformation[0]=0000000000000001
152:49:24.053124 ExceptionInformation[1]=0000000000000000
152:49:24.053128 
152:49:24.053129 cs:rip=0033:00007ffc189728c2
152:49:24.053149 ss:rsp=002b:00000000cacbf560 rbp=00000000cacbf610
152:49:24.053154 rax=00000000cdeb87c0 rcx=0000000000000000 rdx=0000000082751090 rbx=0000000082751070
152:49:24.053159 rsi=0000000219a24c00 rdi=0000000219a24c00 rsp=00000000cacbf560 rbp=00000000cacbf610
152:49:24.053165 r8 =0000000000000000 r9 =0000000082751450 r10=0000000000000000 r11=00000000cacbf6a0
152:49:24.053170 r12=000000026a000770 r13=0000000000000000 r14=000000026a000080 r15=00000000cd680f40
152:49:24.053175 ds=002b es=002b fs=0053 gs=002b eflags=00010206
152:49:24.053180 p1home=0000000000000000 p2home=0000000000000000 pe3home=0000000082751070
152:49:24.053185 p4home=0000000000000000 p5home=0000000000000000 pe6home=0000000000000000
152:49:24.053189    LastBranchToRip=0000000000000000    LastBranchFromRip=0000000000000000
152:49:24.053194 LastExceptionToRip=0000000000000000 LastExceptionFromRip=0000000000000000
152:49:24.053202 
152:49:24.053203 Stack 00000000cacbe440, dumping 0x1bc0 bytes (low=00000000cabc0000, high=00000000cacc0000)
152:49:24.054088 00000000cacbe440/0000: 40 e4 cb ca 00 00 00 00-73 74 61 63 6b 6d 61 72 @.......stackmar
152:49:24.054818 00000000cacbe450/0010: 6b 65 72 00 00 00 00 00-00 10 02 00 00 00 00 00 ker.............
152:49:24.054825 00000000cacbe460/0020: 00 00 00 00 00 00 00 00-80 d7 75 54 fc 7f 00 00 ..........uT....
152:49:24.054831 00000000cacbe470/0030: 01 00 00 00 00 00 00 00-ff ff ff ff ff ff ff ff ................
152:49:24.054839 00000000cacbe480/0040: 40 e6 cb ca 00 00 00 00-00 00 00 00 00 00 00 00 @...............
152:49:24.054845 00000000cacbe490/0050: d0 59 c2 fa fb 7f 00 00-50 f8 cb ca 00 00 00 00 .Y......P.......
152:49:24.054848 00000000cacbe4a0/0060: 00 00 00 00 00 00 00 00-aa 08 5f 54 fc 7f 00 00 .........._T....
152:49:24.054849 00000000cacbe4b0/0070: 40 e6 cb ca 00 00 00 00-c2 28 97 18 fc 7f 00 00 @........(......
152:49:24.054851 00000000cacbe4c0/0080: 00 00 cc ca 00 00 00 00-00 00 bc ca 00 00 00 00 ................
152:49:24.054852 00000000cacbe4d0/0090: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.054854 00000000cacbe4e0/00a0: 06 00 00 00 04 00 00 00-00 00 00 00 01 00 00 00 ................
152:49:24.054855 00000000cacbe4f0/00b0: 08 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.054857 00000000cacbe500/00c0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.054858 00000000cacbe510/00d0: 40 e6 cb ca 00 00 00 00-00 00 00 00 00 00 00 00 @...............
152:49:24.054860 00000000cacbe520/00e0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.054862 **************** ****  <ditto x 6>
152:49:24.054862 00000000cacbe590/0150: 25 f0 25 10 04 1a 00 00-00 00 00 00 00 00 00 00 %.%.............
152:49:24.054864 00000000cacbe5a0/0160: 00 00 b4 56 fc 7f 00 00-40 ec cb ca 00 00 00 00 ...V....@.......
152:49:24.054866 00000000cacbe5b0/0170: 50 f8 cb ca 00 00 00 00-b0 f2 cb ca 00 00 00 00 P...............
152:49:24.054868 00000000cacbe5c0/0180: 00 00 00 00 00 00 00 00-b2 4a be 56 fc 7f 00 00 .........J.V....
152:49:24.054869 00000000cacbe5d0/0190: 00 00 00 00 00 00 00 00-20 44 c8 56 fc 7f 00 00 ........ D.V....
152:49:24.054871 00000000cacbe5e0/01a0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.054872 00000000cacbe5f0/01b0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.054882 00000000cacbe600/01c0: 51 ce 06 00 00 00 00 00-56 c6 bc 56 fc 7f 00 00 Q.......V..V....
152:49:24.054883 00000000cacbe610/01d0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.054885 00000000cacbe620/01e0: 08 ec cb ca 00 00 00 00-90 ec cb ca 00 00 00 00 ................
152:49:24.054886 00000000cacbe630/01f0: a4 0e c0 18 fc 7f 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.054902 00000000cacbe640/0200: b0 f2 cb ca 00 00 00 00-c0 ed cb ca 00 00 00 00 ................
152:49:24.054903 00000000cacbe650/0210: 00 00 00 00 00 00 00 00-f0 e6 cb ca 00 00 00 00 ................
152:49:24.054905 00000000cacbe660/0220: c0 ed cb ca 00 00 00 00-c0 c5 bc 56 fc 7f 00 00 ...........V....
152:49:24.054906 00000000cacbe670/0230: 00 00 00 00 00 00 00 00-cf 11 be 56 fc 7f 00 00 ...........V....
152:49:24.054908 00000000cacbe680/0240: 00 00 00 00 00 00 00 00-f0 eb cb ca 00 00 00 00 ................
152:49:24.054909 00000000cacbe690/0250: b0 f2 cb ca 00 00 00 00-b0 f2 cb ca 00 00 00 00 ................
152:49:24.054924 00000000cacbe6a0/0260: 40 ec cb ca 00 00 00 00-09 a2 ba 56 fc 7f 00 00 @..........V....
152:49:24.054926 00000000cacbe6b0/0270: 01 00 00 00 00 00 00 00-00 00 b4 56 fc 7f 00 00 ...........V....
152:49:24.054928 00000000cacbe6c0/0280: 00 00 00 00 00 00 00 00-f0 e9 ca 56 fc 7f 00 00 ...........V....
152:49:24.054929 00000000cacbe6d0/0290: f0 e6 cb ca 00 00 00 00-10 ec cb ca 00 00 00 00 ................
152:49:24.054931 00000000cacbe6e0/02a0: 00 ec cb ca 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.054932 00000000cacbe6f0/02b0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055264 **************** ****  <ditto x 2>
152:49:24.055266 00000000cacbe720/02e0: 0f 00 10 00 a0 1f 00 00-33 00 00 00 00 00 00 00 ........3.......
152:49:24.055268 00000000cacbe730/02f0: 00 00 2b 00 06 02 01 00-00 00 00 00 00 00 00 00 ..+.............
152:49:24.055270 00000000cacbe740/0300: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055272 **************** ****  <ditto x 3>
152:49:24.055273 00000000cacbe780/0340: 00 00 00 00 00 00 00 00-d0 f8 cb ca 00 00 00 00 ................
152:49:24.055275 00000000cacbe790/0350: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055276 **************** ****  <ditto x 5>
152:49:24.055277 00000000cacbe7f0/03b0: 7f 02 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055279 00000000cacbe800/03c0: 00 00 00 00 00 00 00 00-a0 1f 00 00 ff ff 00 00 ................
152:49:24.055280 00000000cacbe810/03d0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055282 **************** ****  <ditto x 23>
152:49:24.055283 00000000cacbe990/0550: c0 ed cb ca 00 00 00 00-00 4c a2 19 02 00 00 00 .........L......
152:49:24.055284 00000000cacbe9a0/0560: ff ff ff ff ff ff ff ff-00 00 00 00 00 00 00 00 ................
152:49:24.055286 00000000cacbe9b0/0570: 80 ea cb ca 00 00 00 00-2b 2e f3 15 f7 7f 00 00 ........+.......
152:49:24.055288 00000000cacbe9c0/0580: 40 94 fa 15 f7 7f 00 00-c0 eb cb ca 00 00 00 00 @...............
152:49:24.055290 00000000cacbe9d0/0590: c0 87 eb cd 00 00 00 00-70 10 75 82 00 00 00 00 ........p.u.....
152:49:24.055291 00000000cacbe9e0/05a0: 00 00 00 00 00 00 00 00-90 10 75 82 00 00 00 00 ..........u.....
152:49:24.055293 00000000cacbe9f0/05b0: 00 4c a2 19 02 00 00 00-00 4c a2 19 02 00 00 00 .L.......L......
152:49:24.055295 00000000cacbea00/05c0: 00 00 00 00 00 00 00 00-50 14 75 82 00 00 00 00 ........P.u.....
152:49:24.055296 00000000cacbea10/05d0: 00 00 00 00 00 00 00 00-a0 f6 cb ca 00 00 00 00 ................
152:49:24.055298 00000000cacbea20/05e0: 70 07 00 6a 02 00 00 00-00 00 00 00 00 00 00 00 p..j............
152:49:24.055300 00000000cacbea30/05f0: 80 00 00 6a 02 00 00 00-40 0f 68 cd 00 00 00 00 ...j....@.h.....
152:49:24.055301 00000000cacbea40/0600: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055303 00000000cacbea50/0610: c2 28 97 18 fc 7f 00 00-60 f5 cb ca 00 00 00 00 .(......`.......
152:49:24.055305 00000000cacbea60/0620: 10 f6 cb ca 00 00 00 00-5f 00 10 00 00 00 00 00 ........_.......
152:49:24.055306 00000000cacbea70/0630: 33 00 00 00 00 00 00 00-2b 00 00 00 00 00 00 00 3.......+.......
152:49:24.055308 00000000cacbea80/0640: 2b 00 00 00 37 66 66 63-2b 00 00 00 32 38 63 32 +...7ffc+...28c2
152:49:24.055310 00000000cacbea90/0650: 53 00 00 00 00 00 00 00-2b 00 00 00 fc 7f 00 00 S.......+.......
152:49:24.055311 00000000cacbeaa0/0660: 06 02 01 00 00 00 00 00-a0 1f 00 00 02 00 00 00 ................
152:49:24.055313 00000000cacbeab0/0670: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055314 **************** ****  <ditto x 7>
152:49:24.055315 00000000cacbeb30/06f0: 00 4c a2 19 02 00 00 00-d6 2f f3 15 f7 7f 00 00 .L......./......
152:49:24.055317 00000000cacbeb40/0700: 02 00 00 00 00 00 00 00-00 70 cf 00 00 00 00 00 .........p......
152:49:24.055318 00000000cacbeb50/0710: 20 97 fa 15 f7 7f 00 00-05 00 00 c0 00 00 00 00  ...............
152:49:24.055320 00000000cacbeb60/0720: 01 00 00 00 00 00 00 00-40 0f 68 cd 00 00 00 00 ........@.h.....
152:49:24.055322 00000000cacbeb70/0730: 80 00 00 6a 02 00 00 00-f2 ec b5 56 fc 7f 00 00 ...j.......V....
152:49:24.055323 00000000cacbeb80/0740: 70 07 00 6a 02 00 00 00-00 4c a2 19 02 00 00 00 p..j.....L......
152:49:24.055325 00000000cacbeb90/0750: b0 f2 cb ca 00 00 00 00-0b 00 10 00 00 00 00 00 ................
152:49:24.055327 00000000cacbeba0/0760: 10 00 00 00 00 00 00 00-dc a0 ba 56 fc 7f 00 00 ...........V....
152:49:24.055329 00000000cacbebb0/0770: 00 00 00 00 00 00 00 00-b0 f2 cb ca 00 00 00 00 ................
152:49:24.055330 00000000cacbebc0/0780: 30 fb ff ff e8 04 00 00-30 fb ff ff d0 04 00 00 0.......0.......
152:49:24.055335 00000000cacbebd0/0790: 19 00 00 00 00 00 00 00-72 3a 20 30 78 63 30 30 ........r: 0xc00
152:49:24.055336 00000000cacbebe0/07a0: 30 30 30 30 35 20 28 30-30 30 30 30 30 30 30 30 00005 (000000000
152:49:24.055338 00000000cacbebf0/07b0: 00 30 30 30 30 30 31 2c-90 ec cb ca 00 00 00 00 .000001,........
152:49:24.055339 00000000cacbec00/07c0: 50 f8 cb ca 00 00 00 00-00 00 b4 56 fc 7f 00 00 P..........V....
152:49:24.055341 00000000cacbec10/07d0: 20 44 c8 56 fc 7f 00 00-00 00 00 00 00 00 00 00  D.V............
152:49:24.055343 00000000cacbec20/07e0: 00 00 cc ca 00 00 00 00-00 d0 cb ca 00 00 00 00 ................
152:49:24.055344 00000000cacbec30/07f0: c0 ed cb ca 00 00 00 00-80 51 9d 18 fc 7f 00 00 .........Q......
152:49:24.055346 00000000cacbec40/0800: 51 ce ba 56 fc 7f 00 00-00 00 b4 56 fc 7f 00 00 Q..V.......V....
152:49:24.055348 00000000cacbec50/0810: f0 e9 ca 56 fc 7f 00 00-50 f8 cb ca 00 00 00 00 ...V....P.......
152:49:24.055349 00000000cacbec60/0820: 00 00 00 00 00 00 00 00-f0 e6 cb ca 00 00 00 00 ................
152:49:24.055351 00000000cacbec70/0830: c0 c5 bc 56 fc 7f 00 00-20 44 c8 56 fc 7f 00 00 ...V.... D.V....
152:49:24.055352 00000000cacbec80/0840: 90 ec cb ca 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055354 00000000cacbec90/0850: 0a 00 00 00 00 00 00 00-80 38 8f 18 fc 7f 00 00 .........8......
152:49:24.055355 00000000cacbeca0/0860: 78 ce ba 56 fc 7f 00 00-00 00 8e 18 fc 7f 00 00 x..V............
152:49:24.055357 00000000cacbecb0/0870: 80 4b a3 18 fc 7f 00 00-00 00 8e 18 fc 7f 00 00 .K..............
152:49:24.055358 00000000cacbecc0/0880: b0 48 a3 18 fc 7f 00 00-00 00 8e 18 fc 7f 00 00 .H..............
152:49:24.055360 00000000cacbecd0/0890: a4 0f a3 18 fc 7f 00 00-00 00 8e 18 fc 7f 00 00 ................
152:49:24.055362 00000000cacbece0/08a0: 78 fc a2 18 fc 7f 00 00-00 00 8e 18 fc 7f 00 00 x...............
152:49:24.055363 00000000cacbecf0/08b0: b4 1d a3 18 fc 7f 00 00-00 00 8e 18 fc 7f 00 00 ................
152:49:24.055365 00000000cacbed00/08c0: b8 1c a3 18 fc 7f 00 00-00 00 a4 18 fc 7f 00 00 ................
152:49:24.055366 00000000cacbed10/08d0: d4 0e c0 18 fc 7f 00 00-00 00 a4 18 fc 7f 00 00 ................
152:49:24.055368 00000000cacbed20/08e0: a4 0e c0 18 fc 7f 00 00-00 00 31 56 fc 7f 00 00 ..........1V....
152:49:24.055369 00000000cacbed30/08f0: d8 ac 3b 56 fc 7f 00 00-00 00 b4 56 fc 7f 00 00 ..;V.......V....
152:49:24.055371 00000000cacbed40/0900: f0 e9 ca 56 fc 7f 00 00-08 c0 f3 15 f7 7f 00 00 ...V............
152:49:24.055373 00000000cacbed50/0910: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055374 00000000cacbed60/0920: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055376 00000000cacbed70/0930: e0 41 c3 4b 97 74 00 00-a0 f6 cb ca 00 00 00 00 .A.K.t..........
152:49:24.055377 00000000cacbed80/0940: 40 0f 68 cd 00 00 00 00-80 00 00 6a 02 00 00 00 @.h........j....
152:49:24.055379 00000000cacbed90/0950: 00 00 00 00 00 00 00 00-70 07 00 6a 02 00 00 00 ........p..j....
152:49:24.055380 00000000cacbeda0/0960: 00 4c a2 19 02 00 00 00-00 4c a2 19 02 00 00 00 .L.......L......
152:49:24.055382 00000000cacbedb0/0970: 10 f6 cb ca 00 00 00 00-3e fe bd 56 fc 7f 00 00 ........>..V....
152:49:24.055384 00000000cacbedc0/0980: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055385 00000000cacbedd0/0990: 70 10 75 82 00 00 00 00-00 00 00 00 00 00 00 00 p.u.............
152:49:24.055387 00000000cacbede0/09a0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055388 00000000cacbedf0/09b0: 5f 00 10 00 a0 1f 00 00-33 00 2b 00 2b 00 53 00 _.......3.+.+.S.
152:49:24.055390 00000000cacbee00/09c0: 2b 00 2b 00 06 02 01 00-00 00 00 00 00 00 00 00 +.+.............
152:49:24.055391 00000000cacbee10/09d0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055393 00000000cacbee20/09e0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055396 00000000cacbee30/09f0: 00 00 00 00 00 00 00 00-c0 87 eb cd 00 00 00 00 ................
152:49:24.055398 00000000cacbee40/0a00: 00 00 00 00 00 00 00 00-90 10 75 82 00 00 00 00 ..........u.....
152:49:24.055399 00000000cacbee50/0a10: 70 10 75 82 00 00 00 00-60 f5 cb ca 00 00 00 00 p.u.....`.......
152:49:24.055401 00000000cacbee60/0a20: 10 f6 cb ca 00 00 00 00-00 4c a2 19 02 00 00 00 .........L......
152:49:24.055403 00000000cacbee70/0a30: 00 4c a2 19 02 00 00 00-00 00 00 00 00 00 00 00 .L..............
152:49:24.055404 00000000cacbee80/0a40: 50 14 75 82 00 00 00 00-00 00 00 00 00 00 00 00 P.u.............
152:49:24.055406 00000000cacbee90/0a50: a0 f6 cb ca 00 00 00 00-70 07 00 6a 02 00 00 00 ........p..j....
152:49:24.055407 00000000cacbeea0/0a60: 00 00 00 00 00 00 00 00-80 00 00 6a 02 00 00 00 ...........j....
152:49:24.055409 00000000cacbeeb0/0a70: 40 0f 68 cd 00 00 00 00-c2 28 97 18 fc 7f 00 00 @.h......(......
152:49:24.055410 00000000cacbeec0/0a80: 7f 02 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055412 00000000cacbeed0/0a90: 00 00 00 00 00 00 00 00-a0 1f 00 00 ff ff 00 00 ................
152:49:24.055413 00000000cacbeee0/0aa0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055415 **************** ****  <ditto x 58>
152:49:24.055416 00000000cacbf290/0e50: 30 fb ff ff a0 07 00 00-30 fb ff ff d0 04 00 00 0.......0.......
152:49:24.055417 00000000cacbf2a0/0e60: f0 00 00 00 e0 01 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055419 00000000cacbf2b0/0e70: 05 00 00 c0 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055421 00000000cacbf2c0/0e80: c2 28 97 18 fc 7f 00 00-02 00 00 00 00 00 00 00 .(..............
152:49:24.055422 00000000cacbf2d0/0e90: 01 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055438 00000000cacbf2e0/0ea0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055440 **************** ****  <ditto x 5>
152:49:24.055440 00000000cacbf340/0f00: 00 00 00 00 00 00 00 00-c6 2b 97 18 fc 7f 00 00 .........+......
152:49:24.055442 00000000cacbf350/0f10: c2 28 97 18 fc 7f 00 00-00 00 00 00 00 00 00 00 .(..............
152:49:24.055443 00000000cacbf360/0f20: 00 00 00 00 00 00 00 00-60 f5 cb ca 00 00 00 00 ........`.......
152:49:24.055445 00000000cacbf370/0f30: f8 37 00 6a 02 00 00 00-87 c9 9a 18 fc 7f 00 00 .7.j............
152:49:24.055446 00000000cacbf380/0f40: 00 00 00 00 00 00 00 00-1c 00 00 00 00 00 00 80 ................
152:49:24.055448 00000000cacbf390/0f50: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055449 **************** ****  <ditto x 2>
152:49:24.055450 00000000cacbf3c0/0f80: 00 82 2f 7c 00 00 00 00-00 00 00 00 02 00 00 00 ../|............
152:49:24.055451 00000000cacbf3d0/0f90: 00 01 00 00 00 00 00 00-c0 81 2f 7c 00 00 00 00 ........../|....
152:49:24.055453 00000000cacbf3e0/0fa0: 17 03 00 00 00 00 00 00-1e 00 00 00 e0 01 00 00 ................
152:49:24.055455 00000000cacbf3f0/0fb0: 17 03 00 00 00 00 00 00-00 00 00 00 17 03 00 00 ................
152:49:24.055456 00000000cacbf400/0fc0: 17 03 00 00 00 00 00 00-00 02 00 00 00 00 00 00 ................
152:49:24.055458 00000000cacbf410/0fd0: 80 79 72 64 02 00 00 00-80 00 00 6a 02 00 00 00 .yrd.......j....
152:49:24.055459 00000000cacbf420/0fe0: 00 00 00 00 01 00 00 00-00 00 00 00 00 02 00 00 ................
152:49:24.055461 00000000cacbf430/0ff0: 00 00 00 00 00 00 00 00-b0 50 3e 44 02 00 00 00 .........P>D....
152:49:24.055462 00000000cacbf440/1000: 50 b2 49 6a 02 00 00 00-a9 57 92 18 fc 7f 00 00 P.Ij.....W......
152:49:24.055464 00000000cacbf450/1010: 10 f6 cb ca 00 00 00 00-b0 f5 cb ca 00 00 00 00 ................
152:49:24.055465 00000000cacbf460/1020: 00 00 00 00 00 00 00 00-1e 00 00 00 17 03 00 00 ................
152:49:24.055467 00000000cacbf470/1030: 00 00 f0 41 00 c0 45 44-00 00 80 3f 00 00 80 3f ...A..ED...?...?
152:49:24.055469 00000000cacbf480/1040: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055473 00000000cacbf490/1050: 28 31 00 6a 02 00 00 00-00 00 80 3f 00 00 80 3f (1.j.......?...?
152:49:24.055488 00000000cacbf4a0/1060: 00 00 00 00 00 c0 45 44-00 00 00 00 00 00 00 00 ......ED........
152:49:24.055490 00000000cacbf4b0/1070: 00 00 00 00 00 00 00 00-00 00 80 3f 00 00 80 3f ...........?...?
152:49:24.055491 00000000cacbf4c0/1080: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055493 00000000cacbf4d0/1090: 32 ac a9 1f bb e0 00 00-00 00 00 00 00 00 00 00 2...............
152:49:24.055497 00000000cacbf4e0/10a0: d2 ab a9 1f bb e0 00 00-01 00 00 00 00 00 00 00 ................
152:49:24.055500 00000000cacbf4f0/10b0: 00 00 00 6a 02 00 00 00-00 00 00 00 00 00 00 00 ...j............
152:49:24.055504 00000000cacbf500/10c0: 01 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055509 00000000cacbf510/10d0: 04 00 00 00 00 00 00 00-80 00 00 6a 02 00 00 00 ...........j....
152:49:24.055512 00000000cacbf520/10e0: 30 f6 cb ca 00 00 00 00-00 da 9a 18 fc 7f 00 00 0...............
152:49:24.055519 00000000cacbf530/10f0: 80 00 00 6a 02 00 00 00-28 f7 cb ca 00 00 00 00 ...j....(.......
152:49:24.055523 00000000cacbf540/1100: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055526 00000000cacbf550/1110: 00 00 00 00 00 00 00 00-40 f8 95 18 fc 7f 00 00 ........@.......
152:49:24.055529 00000000cacbf560/1120: 00 00 00 00 00 00 00 00-68 95 d0 cb 00 00 00 00 ........h.......
152:49:24.055533 00000000cacbf570/1130: 01 00 00 00 01 00 00 00-00 4c a2 19 02 00 00 00 .........L......
152:49:24.055536 00000000cacbf580/1140: 80 00 00 6a 02 00 00 00-df 06 97 18 fc 7f 00 00 ...j............
152:49:24.055540 00000000cacbf590/1150: 00 00 00 00 02 00 00 00-01 00 00 00 00 00 00 00 ................
152:49:24.055543 00000000cacbf5a0/1160: 80 4b 6c 64 02 00 00 00-b0 50 3e 44 02 00 00 00 .Kld.....P>D....
152:49:24.055546 00000000cacbf5b0/1170: b0 50 3e 44 02 00 00 00-00 00 00 00 00 00 00 00 .P>D............
152:49:24.055549 00000000cacbf5c0/1180: 00 00 00 00 00 00 00 00-00 f6 cb ca 00 00 00 00 ................
152:49:24.055553 00000000cacbf5d0/1190: 80 4b 6c 64 02 00 00 00-00 00 00 00 00 00 00 00 .Kld............
152:49:24.055556 00000000cacbf5e0/11a0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055560 00000000cacbf5f0/11b0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055563 00000000cacbf600/11c0: 00 00 00 00 00 00 00 00-1e 00 00 00 17 03 00 00 ................
152:49:24.055564 00000000cacbf610/11d0: 00 00 00 00 00 00 00 00-00 00 8e 18 fc 7f 00 00 ................
152:49:24.055566 00000000cacbf620/11e0: 70 07 00 6a 02 00 00 00-03 00 00 00 00 00 00 00 p..j............
152:49:24.055568 00000000cacbf630/11f0: 00 00 00 00 00 00 00 00-b0 4b ef 7b 00 00 00 00 .........K.{....
152:49:24.055569 00000000cacbf640/1200: b8 0b 00 00 00 00 00 00-ed 1b 91 18 fc 7f 00 00 ................
152:49:24.055571 00000000cacbf650/1210: b0 4b ef 7b 00 00 00 00-00 00 00 00 00 00 00 00 .K.{............
152:49:24.055573 00000000cacbf660/1220: 04 00 00 7a 00 00 00 01-01 00 00 00 00 00 00 00 ...z............
152:49:24.055574 00000000cacbf670/1230: 00 00 00 00 00 00 00 00-04 00 00 7a 98 04 00 01 ...........z....
152:49:24.055576 00000000cacbf680/1240: 60 00 00 00 00 00 00 00-5c 99 dc cb 00 00 00 00 `.......\.......
152:49:24.055577 00000000cacbf690/1250: 00 00 8e 18 fc 7f 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055579 00000000cacbf6a0/1260: 80 00 00 6a 02 00 00 00-79 3a 8f 18 fc 7f 00 00 ...j....y:......
152:49:24.055580 00000000cacbf6b0/1270: b0 4b ef 7b 00 00 00 00-04 00 00 00 00 00 00 00 .K.{............
152:49:24.055582 00000000cacbf6c0/1280: d8 65 91 26 02 00 00 00-38 cf 8a 19 02 00 00 00 .e.&....8.......
152:49:24.055583 00000000cacbf6d0/1290: a0 f7 cb ca 00 00 00 00-7c 91 92 18 fc 7f 00 00 ........|.......
152:49:24.055585 00000000cacbf6e0/12a0: 04 00 00 00 00 00 00 00-04 00 00 00 00 00 00 00 ................
152:49:24.055586 00000000cacbf6f0/12b0: 80 00 00 6a 02 00 00 00-17 53 90 18 fc 7f 00 00 ...j.....S......
152:49:24.055591 00000000cacbf700/12c0: 88 14 00 6a 02 00 00 00-6f 7e 92 18 fc 7f 00 00 ...j....o~......
152:49:24.055593 00000000cacbf710/12d0: 80 00 00 6a 02 00 00 00-80 00 00 6a 02 00 00 00 ...j.......j....
152:49:24.055594 00000000cacbf720/12e0: 98 14 00 6a 02 00 00 00-00 00 00 00 00 00 00 00 ...j............
152:49:24.055596 00000000cacbf730/12f0: f0 43 3e 44 02 00 00 00-88 14 00 6a 02 00 00 00 .C>D.......j....
152:49:24.055598 00000000cacbf740/1300: 01 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055599 00000000cacbf750/1310: 5c 99 dc cb 00 00 00 00-d0 95 dc cb 00 00 00 00 \...............
152:49:24.055601 00000000cacbf760/1320: 01 00 00 00 00 00 00 00-60 90 d0 cb 00 00 00 00 ........`.......
152:49:24.055602 00000000cacbf770/1330: 8c 03 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055604 00000000cacbf780/1340: 00 00 00 00 00 00 00 00-c6 53 b7 18 fc 7f 00 00 .........S......
152:49:24.055605 00000000cacbf790/1350: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055607 00000000cacbf7a0/1360: 00 00 00 00 00 00 00 00-01 00 00 00 00 00 00 00 ................
152:49:24.055608 00000000cacbf7b0/1370: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055610 **************** ****  <ditto x 2>
152:49:24.055610 00000000cacbf7e0/13a0: 01 00 00 00 00 00 00 00-a3 4f b7 18 fc 7f 00 00 .........O......
152:49:24.055612 00000000cacbf7f0/13b0: 60 90 d0 cb 00 00 00 00-00 00 00 00 00 00 00 00 `...............
152:49:24.055614 00000000cacbf800/13c0: 00 00 a4 18 fc 7f 00 00-1c 19 00 00 00 00 00 00 ................
152:49:24.055615 00000000cacbf810/13d0: 00 00 00 00 00 00 00 00-d4 7b 32 56 fc 7f 00 00 .........{2V....
152:49:24.055617 00000000cacbf820/13e0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055618 00000000cacbf830/13f0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055620 00000000cacbf840/1400: 00 00 00 00 00 00 00 00-51 ce ba 56 fc 7f 00 00 ........Q..V....
152:49:24.055621 00000000cacbf850/1410: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055623 **************** ****  <ditto x 2>
152:49:24.055623 00000000cacbf880/1440: 00 00 00 00 1e 91 8b 62-00 00 00 00 00 00 00 00 .......b........
152:49:24.055625 00000000cacbf890/1450: 00 00 00 00 00 00 00 00-c0 06 5f 54 fc 7f 00 00 .........._T....
152:49:24.055626 00000000cacbf8a0/1460: 40 e6 cb ca 00 00 00 00-f0 ff 01 00 78 5f 52 db @...........x_R.
152:49:24.055628 00000000cacbf8b0/1470: de 97 d4 36 fc 7f 00 00-40 e6 cb ca 00 00 00 00 ...6....@.......
152:49:24.055629 00000000cacbf8c0/1480: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055632 **************** ****  <ditto x 114>
152:49:24.055632 00000000cacbfff0/1bb0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055881 Thread ID:   0000000000004184
152:49:24.055891 Thread name: <NULL>
152:49:24.055896 Thread IPRT: 0000000000000000
152:49:24.055901 
152:49:24.055901 Loaded Modules:
152:49:24.055901 Address range                    [*] Timestamp Path
152:49:24.055907 00007ff715f30000..00007ff716045fff   5f51ed66  C:\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
152:49:24.055914 00007ffc56b40000..00007ffc56d2ffff   b5beef21  C:\WINDOWS\SYSTEM32\ntdll.dll
152:49:24.055920 00007ffc56310000..00007ffc563c1fff   53a32b86  C:\WINDOWS\System32\KERNEL32.DLL
152:49:24.055926 00007ffc544f0000..00007ffc54794fff   1b835a75  C:\WINDOWS\System32\KERNELBASE.dll
152:49:24.055932 00007ffc2f520000..00007ffc2f524fff   5f51ecdc  C:\Program Files\Oracle\VirtualBox\VBoxSupLib.DLL
152:49:24.055937 00007ffc54410000..00007ffc5446bfff   ad0f5fb3  C:\WINDOWS\System32\Wintrust.dll
152:49:24.055943 00007ffc56560000..00007ffc565fdfff   f5bdefd7  C:\WINDOWS\System32\msvcrt.dll
152:49:24.055949 00007ffc53a90000..00007ffc53aa1fff   e4c2641f  C:\WINDOWS\System32\MSASN1.dll
152:49:24.055954 00007ffc548d0000..00007ffc54a18fff   0e128cc8  C:\WINDOWS\System32\CRYPT32.dll
152:49:24.055960 00007ffc547d0000..00007ffc548c9fff   32a6df9a  C:\WINDOWS\System32\ucrtbase.dll
152:49:24.055966 00007ffc55970000..00007ffc55a8ffff   ee94cb53  C:\WINDOWS\System32\RPCRT4.dll
152:49:24.055971 00007ffc547a0000..00007ffc547c5fff   b59ada57  C:\WINDOWS\System32\bcrypt.dll
152:49:24.055984 00007ffc54470000..00007ffc544effff   bf9ade76  C:\WINDOWS\System32\bcryptprimitives.dll
152:49:24.055990 00007ffc543f0000..00007ffc54406fff   a51023f1  C:\WINDOWS\System32\CRYPTSP.dll
152:49:24.055996 00007ffc526e0000..00007ffc52712fff   fa3c3542  C:\WINDOWS\system32\rsaenh.dll
152:49:24.056001 00007ffc52d40000..00007ffc52d4bfff   fef011a6  C:\WINDOWS\SYSTEM32\CRYPTBASE.dll
152:49:24.056007 00007ffc56540000..00007ffc5655cfff   13bffc39  C:\WINDOWS\System32\imagehlp.dll
152:49:24.056013 00007ffc54ce0000..00007ffc54d76fff   f222d51c  C:\WINDOWS\System32\sechost.dll
152:49:24.056018 00007ffc51900000..00007ffc51921fff   0ab6ed3a  C:\WINDOWS\SYSTEM32\gpapi.dll
152:49:24.056024 00007ffc53a60000..00007ffc53a82fff   ca538c5d  C:\WINDOWS\System32\profapi.dll
152:49:24.056030 00007ffc52240000..00007ffc5226efff   b35f039c  C:\WINDOWS\System32\cryptnet.dll
152:49:24.056049 00007ffc54d80000..00007ffc54e22fff   502aaa11  C:\WINDOWS\System32\advapi32.dll
152:49:24.056055 00007ffbfaab0000..00007ffbfb08ffff   5f51ed67  C:\Program Files\Oracle\VirtualBox\VBoxRT.dll
152:49:24.056061 00007ffc55880000..00007ffc558eefff   50866107  C:\WINDOWS\System32\WS2_32.dll
152:49:24.056066 00000000502b0000..0000000050381fff   4d5f034a  C:\Program Files\Oracle\VirtualBox\MSVCR100.dll
152:49:24.056072 0000000050210000..00000000502a7fff   4d5f035c  C:\Program Files\Oracle\VirtualBox\MSVCP100.dll
152:49:24.056077 00007ffbf6a50000..00007ffbf6c17fff   5f51ed81  C:\Program Files\Oracle\VirtualBox\VirtualBoxVM.dll
152:49:24.056083 00007ffc550b0000..00007ffc55244fff   57629574  C:\WINDOWS\System32\USER32.dll
152:49:24.056088 00007ffc54bc0000..00007ffc54be0fff   5343f4fb  C:\WINDOWS\System32\win32u.dll
152:49:24.056093 00007ffc563d0000..00007ffc563f5fff   90b22122  C:\WINDOWS\System32\GDI32.dll
152:49:24.056098 00007ffc53ad0000..00007ffc53c65fff   7ea30dec  C:\WINDOWS\System32\gdi32full.dll
152:49:24.056104 00007ffc54a20000..00007ffc54abdfff   2085286c  C:\WINDOWS\System32\msvcp_win.dll
152:49:24.056109 00007ffc56600000..00007ffc56756fff   3340c819  C:\WINDOWS\System32\ole32.dll
152:49:24.056114 00007ffc567c0000..00007ffc56af4fff   8349657a  C:\WINDOWS\System32\combase.dll
152:49:24.056119 00007ffc557b0000..00007ffc55874fff   6ac977e7  C:\WINDOWS\System32\OLEAUT32.dll
152:49:24.056126 00007ffc25480000..00007ffc255d5fff   c7cf39ed  C:\WINDOWS\SYSTEM32\OPENGL32.dll
152:49:24.056132 00007ffbf8790000..00007ffbfaaa6fff   5f51ed79  C:\Program Files\Oracle\VirtualBox\UICommon.dll
152:49:24.056137 0000000077a90000..0000000077ff4fff   58e2613b  C:\Program Files\Oracle\VirtualBox\Qt5CoreVBox.dll
152:49:24.056142 00007ffc55a90000..00007ffc56176fff   37e737cc  C:\WINDOWS\System32\SHELL32.dll
152:49:24.056148 00007ffc54ac0000..00007ffc54b09fff   afaaabaa  C:\WINDOWS\System32\cfgmgr32.dll
152:49:24.056153 00007ffc54bf0000..00007ffc54c98fff   bd8b0e7d  C:\WINDOWS\System32\shcore.dll
152:49:24.056158 00007ffc53c70000..00007ffc543effff   a8db3b62  C:\WINDOWS\System32\windows.storage.dll
152:49:24.056163 00007ffc53a10000..00007ffc53a59fff   fdc4588a  C:\WINDOWS\System32\powrprof.dll
152:49:24.056169 00007ffc53a00000..00007ffc53a0ffff   a2ccd413  C:\WINDOWS\System32\UMPDC.dll
152:49:24.056174 00007ffc562b0000..00007ffc56301fff   f8807ba1  C:\WINDOWS\System32\shlwapi.dll
152:49:24.056179 00007ffc53ab0000..00007ffc53ac0fff   05bef372  C:\WINDOWS\System32\kernel.appcore.dll
152:49:24.056184 00007ffbf8190000..00007ffbf8786fff   58e261e1  C:\Program Files\Oracle\VirtualBox\Qt5GuiVBox.dll
152:49:24.056190 0000000077520000..0000000077a80fff   58e2628d  C:\Program Files\Oracle\VirtualBox\Qt5WidgetsVBox.dll
152:49:24.056195 00000000501b0000..0000000050203fff   58e262df  C:\Program Files\Oracle\VirtualBox\Qt5OpenGLVBox.dll
152:49:24.056200 00007ffc4d690000..00007ffc4d6b3fff   d238be3c  C:\WINDOWS\SYSTEM32\WINMM.dll
152:49:24.056205 00007ffc25450000..00007ffc2547bfff   f93070ee  C:\WINDOWS\SYSTEM32\GLU32.dll
152:49:24.056211 00007ffc2ba80000..00007ffc2ba9afff   57b24d2b  C:\WINDOWS\SYSTEM32\MPR.dll
152:49:24.056216 00007ffc4d660000..00007ffc4d68cfff   d6bb9be2  C:\WINDOWS\SYSTEM32\WINMMBASE.dll
152:49:24.056221 00007ffc51950000..00007ffc5196ffff   bc0e8e8e  C:\WINDOWS\SYSTEM32\dxcore.dll
152:49:24.056227 00007ffc54cb0000..00007ffc54cddfff   4be57136  C:\WINDOWS\System32\IMM32.DLL
152:49:24.056232 00007ffbf8060000..00007ffbf818dfff   58e2632b  C:\Program Files\Oracle\VirtualBox\platforms\qwindows.dll
152:49:24.056237 00007ffc509e0000..00007ffc50a78fff   6eb90ac0  C:\WINDOWS\system32\uxtheme.dll
152:49:24.056242 00007ffc538e0000..00007ffc53904fff   dbb466d6  C:\WINDOWS\system32\userenv.dll
152:49:24.056248 00007ffc56200000..00007ffc562a1fff   9506208f  C:\WINDOWS\System32\clbcatq.dll
152:49:24.056253 00007ffbf7bb0000..00007ffbf7f6ffff   5f51ed74  C:\Program Files\Oracle\VirtualBox\VBoxC.dll
152:49:24.056258 00007ffbf7f70000..00007ffbf805efff   5f51ed6c  C:\Program Files\Oracle\VirtualBox\VBoxProxyStub.dll
152:49:24.056264 00007ffc56400000..00007ffc56534fff   8776e62f  C:\WINDOWS\System32\MSCTF.dll
152:49:24.056269 00007ffc26a40000..00007ffc26a79fff   5c8c75fa  C:\WINDOWS\system32\dataexchange.dll
152:49:24.056274 00007ffc4ca70000..00007ffc4cccafff   7e72d1cb  C:\WINDOWS\system32\d3d11.dll
152:49:24.056280 00007ffc4ccd0000..00007ffc4ceacfff   2ba0a53f  C:\WINDOWS\system32\dcomp.dll
152:49:24.056285 00007ffc51a10000..00007ffc51afafff   4029f10d  C:\WINDOWS\system32\dxgi.dll
152:49:24.056290 00007ffc50ad0000..00007ffc50d31fff   eeb9f7a6  C:\WINDOWS\system32\twinapi.appcore.dll
152:49:24.056296 00007ffc50f10000..00007ffc50f38fff   5be0eb17  C:\WINDOWS\system32\RMCLIENT.dll
152:49:24.056301 00007ffc41fd0000..00007ffc4206dfff   66a372e8  C:\WINDOWS\System32\TextInputFramework.dll
152:49:24.056306 00007ffc4a6f0000..00007ffc4aa19fff   d02b205d  C:\WINDOWS\System32\CoreUIComponents.dll
152:49:24.056312 00007ffc4ceb0000..00007ffc4cf83fff   99046ad7  C:\WINDOWS\System32\CoreMessaging.dll
152:49:24.056317 00007ffc53450000..00007ffc53480fff   d95e6299  C:\WINDOWS\SYSTEM32\ntmarta.dll
152:49:24.056322 00007ffc4b1d0000..00007ffc4b322fff   571c81a7  C:\WINDOWS\SYSTEM32\wintypes.dll
152:49:24.056327 00007ffc40a70000..00007ffc40d15fff   156c7509  C:\WINDOWS\System32\iertutil.dll
152:49:24.056333 00007ffc3e0f0000..00007ffc3e100fff   6e82a406  C:\WINDOWS\system32\wbem\wbemprox.dll
152:49:24.056339 00007ffc3eb30000..00007ffc3ebb3fff   6af5c06d  C:\WINDOWS\SYSTEM32\wbemcomn.dll
152:49:24.056345 00007ffc3d770000..00007ffc3d783fff   f9651a38  C:\WINDOWS\system32\wbem\wbemsvc.dll
152:49:24.056350 00007ffc3d890000..00007ffc3d990fff   65ead981  C:\WINDOWS\system32\wbem\fastprox.dll
152:49:24.056356 00007ffc33850000..00007ffc33864fff   b26a0aaf  C:\WINDOWS\System32\amsi.dll
152:49:24.056361 00007ffc31bd0000..00007ffc31c48fff   c930d9ac  C:\ProgramData\Microsoft\Windows Defender\platform\4.18.2009.7-0\MpOav.dll
152:49:24.056367 00007ffc47f20000..00007ffc47f29fff   927b71e6  C:\WINDOWS\system32\version.dll
152:49:24.056372 00007ffbf66d0000..00007ffbf6a4dfff   5f51ed6c  C:\Program Files\Oracle\VirtualBox\VBoxVMM.DLL
152:49:24.056378 00007ffc534b0000..00007ffc534bffff   5f51ed74  C:\Program Files\Oracle\VirtualBox\VBoxSharedClipboard.DLL
152:49:24.056383 00007ffc534a0000..00007ffc534acfff   5f51ed74  C:\Program Files\Oracle\VirtualBox\VBoxDragAndDropSvc.DLL
152:49:24.056389 00007ffbf5ce0000..00007ffbf66c5fff   5f51ef9a  C:\Program Files\Oracle\VirtualBox\VBoxDD.DLL
152:49:24.056394 00007ffc55340000..00007ffc557affff   a7d94c0a  C:\WINDOWS\System32\SETUPAPI.dll
152:49:24.056400 00007ffbf7b40000..00007ffbf7ba6fff   5f51ed6c  C:\Program Files\Oracle\VirtualBox\VBoxDDU.dll
152:49:24.056405 00007ffbf5480000..00007ffbf5cdbfff   5f51ef98  C:\Program Files\Oracle\VirtualBox\VBoxDD2.dll
152:49:24.056411 00007ffc52880000..00007ffc528b9fff   50afe730  C:\WINDOWS\SYSTEM32\IPHLPAPI.DLL
152:49:24.056416 00007ffc2f500000..00007ffc2f513fff   5f51ed74  C:\Program Files\Oracle\VirtualBox\VBoxSharedFolders.DLL
152:49:24.056421 00007ffc53490000..00007ffc5349bfff   5f51ed74  C:\Program Files\Oracle\VirtualBox\VBoxGuestControlSvc.DLL
152:49:24.056427 00007ffc14a70000..00007ffc14a7cfff   5f51ed74  C:\Program Files\Oracle\VirtualBox\VBoxGuestPropSvc.DLL
152:49:24.056433 00007ffc4b100000..00007ffc4b10afff   3f83c149  C:\WINDOWS\SYSTEM32\WINNSI.DLL
152:49:24.056438 00007ffc55960000..00007ffc55967fff   76a581c8  C:\WINDOWS\System32\NSI.dll
152:49:24.056443 00007ffc4ab20000..00007ffc4ab35fff   1c3a0614  C:\WINDOWS\SYSTEM32\dhcpcsvc6.DLL
152:49:24.056448 00007ffc4ab00000..00007ffc4ab1bfff   3c1facb4  C:\WINDOWS\SYSTEM32\dhcpcsvc.DLL
152:49:24.056454 00007ffc528c0000..00007ffc5298afff   6d09021f  C:\WINDOWS\SYSTEM32\DNSAPI.dll
152:49:24.056459 00007ffc426e0000..00007ffc42751fff   1626851d  C:\WINDOWS\System32\MMDevApi.dll
152:49:24.056464 00007ffc537f0000..00007ffc53819fff   73cca382  C:\WINDOWS\System32\DEVOBJ.dll
152:49:24.056470 00007ffc1fa50000..00007ffc1fae8fff   0f4dfe70  C:\WINDOWS\System32\dsound.dll
152:49:24.056509 00007ffc3ff90000..00007ffc400ecfff   7e935799  C:\WINDOWS\System32\AUDIOSES.DLL
152:49:24.056523 00007ffc18d80000..00007ffc18dc3fff   2c6931f6  C:\WINDOWS\System32\wdmaud.drv
152:49:24.056536 00007ffc2f8c0000..00007ffc2f8c8fff   9b72df6f  C:\WINDOWS\SYSTEM32\ksuser.dll
152:49:24.056546 00007ffc4ad50000..00007ffc4ad59fff   f97bfee2  C:\WINDOWS\SYSTEM32\AVRT.dll
152:49:24.056555 00007ffc2e910000..00007ffc2e91cfff   4d3c7e92  C:\WINDOWS\System32\msacm32.drv
152:49:24.056564 00007ffc2ded0000..00007ffc2deebfff   6a4add8d  C:\WINDOWS\SYSTEM32\MSACM32.dll
152:49:24.056574 00007ffc2e730000..00007ffc2e739fff   5a70c191  C:\WINDOWS\System32\midimap.dll
152:49:24.056583 00007ffc18a40000..00007ffc18c06fff   c808fce5  C:\WINDOWS\system32\d3d9.dll
152:49:24.056592 00007ffc50e30000..00007ffc50e5cfff   7cd7bb0f  C:\WINDOWS\SYSTEM32\dwmapi.dll
152:49:24.056602 00007ffc188e0000..00007ffc18a3cfff*  5eb1b78e  C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdumdim64.dll
152:49:24.056615 00007ffc14fd0000..00007ffc188d8fff   5eb1b648  C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igd9dxva64.dll
152:49:24.056630 00007ffc451c0000..00007ffc45363fff   5eb1b356  C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdgmm64.dll
152:49:24.056643 00007ffc51e70000..00007ffc51e95fff   5eb1b301  C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdinfo64.dll
152:49:24.056659 00007ffc42bb0000..00007ffc451b3fff   5eb1b815  C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igc64.dll
152:49:24.056677 00007ffc4bba0000..00007ffc4bc8ffff   e593a459  C:\Windows\System32\PROPSYS.dll
152:49:24.056688 00007ffc52b70000..00007ffc52bd6fff   65b356bc  C:\WINDOWS\system32\mswsock.dll
152:49:24.056702 00007ffc50d40000..00007ffc50d53fff   c19b74f1  C:\WINDOWS\SYSTEM32\resourcepolicyclient.dll
152:49:24.056713 
152:49:24.056713 Potential code addresses on the stack:
152:49:24.056719 Xcpt PC         : 00007ffc189728c2 - 0x000928c2 bytes into C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdumdim64.dll
152:49:24.056740 00000000cacbf588: 00007ffc189706df - 0x000906df bytes into C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdumdim64.dll
152:49:24.056759 00000000cacbf618: 00007ffc188e0000 - 0x00000000 bytes into C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdumdim64.dll
152:49:24.056770 00000000cacbf648: 00007ffc18911bed - 0x00031bed bytes into C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdumdim64.dll
152:49:24.056777 00000000cacbf690: 00007ffc188e0000 - 0x00000000 bytes into C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdumdim64.dll
152:49:24.056784 00000000cacbf6a8: 00007ffc188f3a79 - 0x00013a79 bytes into C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdumdim64.dll
152:49:24.056791 00000000cacbf6d8: 00007ffc1892917c - 0x0004917c bytes into C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdumdim64.dll
152:49:24.056798 00000000cacbf6f8: 00007ffc18905317 - 0x00025317 bytes into C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdumdim64.dll
152:49:24.056804 00000000cacbf708: 00007ffc18927e6f - 0x00047e6f bytes into C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdumdim64.dll
152:49:24.056813 00000000cacbf788: 00007ffc18b753c6 - 0x001353c6 bytes into C:\WINDOWS\system32\d3d9.dll
152:49:24.056820 00000000cacbf7e8: 00007ffc18b74fa3 - 0x00134fa3 bytes into C:\WINDOWS\system32\d3d9.dll
152:49:24.056829 00000000cacbf800: 00007ffc18a40000 - 0x00000000 bytes into C:\WINDOWS\system32\d3d9.dll
152:49:24.056836 00000000cacbf818: 00007ffc56327bd4 - 0x00017bd4 bytes into C:\WINDOWS\System32\KERNEL32.DLL
152:49:24.056841 00000000cacbf848: 00007ffc56bace51 - 0x0006ce51 bytes into C:\WINDOWS\SYSTEM32\ntdll.dll
152:49:24.056860 00000000cacbf898: 00007ffc545f06c0 - 0x001006c0 bytes into C:\WINDOWS\System32\KERNELBASE.dll"	paulcad
20162	Crash when VM reboots due to null memory reference	VirtualBox 6.1.18	2021-01-29T19:03:17Z	2021-03-20T07:19:24Z	2021-03-20T07:19:24Z	"Hello there,

I've noticed lately that when VirtualBox reboots, either via VirtualBox (HOST+R or similar) or instructed by the guest, this fails entirely and crashes with a null memory reference.

* It impacts any guest VM.
* It doesn't impact ACPI shutdown or hard power off, these seem to close gracefully.
* It doesn't particularly matter what stage the guest is at, it'll occur seconds after powering on, or hours after running.
* This impacts running a VM normally and headlessly.

Specifically the error message is ""The instruction at 0x00007ffab544f3bc referenced memory at 0x0000000000000000. The memory could not be read.""

At this point I can power off the virtual machine and start it up again normally, but I worry if any pending storage writes will have been lost causing corruption. (I did very recently lose a guest due to storage corruption, unsure if this caused it.)

Unfortunately attaching a debugger never seems to succeed, so I'll attach some memory dumps of ""VirtualBoxVM.exe"" and ""VBoxHeadless.exe"" when the fatal error message was present.

I did attempt removing and reinstalling VirtualBox, including a whole reboot between, the only change was the memory address of the instruction. I can replicate this incredibly reliably though if further memory dumps are helpful."	Adam Reece
16215	Crash while installing Avast	VirtualBox 5.1.10	2016-11-23T05:37:36Z	2016-11-23T05:37:36Z	2016-11-23T05:37:36Z	"Host OS = XP Prof 32 bit V 2002 SP3 on 800GB partition. 1GB (of 2) ram
Guest OS = Windows 7 Prof 32 bit SP1 30 GB on 50GB partition (7 GB free).  1GB (of 2) ram
Guest originally restored from Macrium image.
When installing Avast anti-virus (free version) I get a ""guru meditation"" before it completes.
Tried with normal and immutable guests, and with a similar Vista guest
Gets to about 99% (going by the progress bar)
"	jchrisj
17288	Crash while installing DirectX 9.0c on Windows 98	VirtualBox 4.3.36	2017-11-18T06:06:38Z	2017-11-18T11:24:32Z	2017-11-18T11:24:32Z	"While following forum instructions https://forums.virtualbox.org/viewtopic.php?f=2&t=59559

The critical error guru box showed up and suggested I submit this ticket.

My virtualbox version is actual 4.3.40 r110317. On that note, this new ticket form has the version list all out of order, could that be sorted?

The host system is Windows 7 64-bit"	Brrwrist
14992	Crash Windows 7 / RAW FILE CONVERTER EX powered by SILKYPIX	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
19087	"Crash with ExceptionCode=0xc0000005 on ""VMSVGA FIFO"""	VirtualBox 6.0.14	2019-11-15T10:08:14Z	2019-11-16T02:59:14Z	2019-11-16T02:59:14Z	"Host is windows 10/
2 VMs launched. Virtualbox freezes ""1 VirtualBox GUI is frozen.png"". Correctly completing work in the 1st guest Windows XP. Error ""2 VirtualBoxCrush.png"" pops up and the 2nd guest Windows 10 disappears.
There is also a failure of the keyboard and mouse on the fault of the windows  10 host computer when connected to it via the RDP.

It started this week after updating the virtual box to 6.0.14 r133895 (Qt5.6.2), but the Windows 10 host was also updated."	Дмитро
14077	Crash with RDR_FILE_SYSTEM in Windows 7	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
16919	Crash, possibly when pressing several keys very fast or simultaneously		2017-07-19T20:00:06Z	2017-07-19T20:00:06Z	2017-07-19T20:00:06Z	"After installing version 5.1.24 and worked for a while in an XP guest, it crashed. It did that a 2nd time and that's when i got the attached log. Both times i was typing, so i got the impression (without being sure) that it crashed because i was typing too fast or because i pressed many keys simultaneously.

After a fresh start, i tried to reproduce the crash by typing fast and pressing many keys at the same time but without any success.

The same host/guest combination has worked without such issues from version 5.1.0 up to 5.1.22.

Host: WIn7 SP1, Guest: WinXP SP3.

P.S. After installing 5.1.24, i noticed a certain slugginess (even after installing guest additions) when maximizing/restoring/resizing the guest window. Again, was not happening in 5.1.22."	Wand
19388	crashes during win updates	VirtualBox 6.1.4	2020-03-09T14:09:13Z	2020-03-09T14:09:13Z	2020-03-09T14:09:13Z	VB crashed during 1909 install as well as 1909 update	andyknas
19676	Crashes Program after pressing Ctrl+R(Restart) and using the bottom panel	VirtualBox 6.1.10	2020-06-20T12:35:32Z	2020-06-20T12:35:32Z	2020-06-20T12:35:32Z	"Crashes Program after pressing Ctrl+R(Restart) and using the bottom panel
Video: https://youtu.be/MdocMGLR2_M
Restarting W/O crashes on Windows 95.
Bliss OS (Linux Android) Restarting Crashes.
Bottom Panel crashes on all systems and many Virtual Box versions (6.X.X) (MS-DOS,Linux,OS/2 e.t.c)"	Danik2343
19272	crashes very much when i right click in winscp	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
17151	Crashes with critical error when trying to start Window 7 32-bit in Windows 7 64-bit	VirtualBox 5.1.28	2017-10-10T01:06:54Z	2017-10-10T09:13:01Z	2017-10-10T09:13:01Z	"""A critical error has occurred while running the virtual machine and the machine execution has been stopped"" 

Yesterday it ran correctly until now. I tried to start the system and when the Windows logo disappears the message appears."	Francisco Gonzalez
19125	Crashes with vmsvga	VirtualBox 6.0.14	2019-12-02T19:51:45Z	2019-12-09T06:51:32Z	2019-12-09T06:51:32Z	"Vm crashes if more than 128 megabytes of vram is issued to vmsvga graphical controller.
for example 129
I booted from https://archives.fedoraproject.org/pub/archive/fedora/linux/releases/25/Workstation/i386/iso/Fedora-Workstation-netinst-i386-25-1.3.iso"	kotenok2000
15968	Crashing VirtualBox	VirtualBox 5.1.6	2016-09-22T12:06:37Z	2016-09-22T12:06:37Z	2016-09-22T12:06:37Z	"When I'm trying to open any Virtual machine I'm having error:
""The virtual machine 'Helper' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'D:\Games\VirtualBox\Helper\Logs\VBoxHardening.log'.


Код ошибки: 
E_FAIL (0x80004005)
Компонент: 
MachineWrap
Интерфейс: 
IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}""

Log attached."	DenJed
11006	Creating a cloned or linked virtual machine does not allow to select destination folder	VirtualBox 4.2.0	2012-10-01T09:26:51Z	2012-10-01T09:26:51Z	2012-10-01T09:26:51Z	I just add the cloned or linked virtual machine to the same folder as the source virtual machine.	Tsso
14130	Creating a VB on Windows 7-32bit for Windows 8-32bit	VirtualBox 4.3.28	2015-05-17T18:39:55Z	2015-05-18T06:33:45Z	2015-05-18T06:33:45Z	"Tried to run a VB Windows 8.1 (32 bit) on my Windows 7.  

Encountered the following errors:

1.  Failed to create the VirtualBox COM object.
    The application will now terminate.
    Callee RC: E_INVALIDARG (0x80070057)

2.  Failed to open a session for the virtual machine Windows 8.
    The virtual machine 'Windows 8' has terminated unexpectedly during 
    startup with exit code 1 (0x1).  More details may be available in   
    'C:\Users\c3p0i\VirtualBox VMs\Windows 8\Logs\VBoxStartup.log'.

    Result Code: E_FAIL (0x80004005)
    Component: Machine
    Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

I have attached the *.log with this ticket.

Thanks and Regards."	c3p0i
19983	critical eror occured while runing vm and vm stopped	VirtualBox 6.1.16	2020-10-20T17:22:00Z	2020-10-20T17:22:00Z	2020-10-20T17:22:00Z		sebibala
20863	Critical error	VirtualBox 6.1.32	2022-03-09T23:44:02Z	2022-03-09T23:44:02Z	2022-03-09T23:44:02Z	"A critical error has occurred while running the virtual machine and the machine has been stopped.

"	fabio sordi
19744	Critical Error	VirtualBox 6.1.10	2020-07-21T19:42:00Z	2020-07-21T19:42:00Z	2020-07-21T19:42:00Z	Critical error ocurs while compiling with GCC. All my woes seems to have started after upgrading windows 10 (the host) to version 2004 and virtualbox to 6.1.12 r139181 (Qt5.6.2). I often also get program referenced illeegal memory at 0x000000 warra warra warra.	Tiaan
19318	Critical Error	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
17944	Critical Error	VirtualBox 5.2.18	2018-08-21T16:56:12Z	2018-08-22T16:29:33Z	2018-08-22T16:29:33Z	When attempting to do a graphical install of Linux Kali, i receive this error while attempting to do a graphical install. 	Bomban111
17454	Critical error	VirtualBox 5.1.30	2018-01-14T22:36:45Z	2018-01-15T19:04:02Z	2018-01-15T19:04:02Z	"On startup of Ubuntu 16.04 virtual machine:

""A critical error has occurred while running the virtual machine and the machine execution has been 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 and the image file VBox.png, which you can find in the /Users/dwhea/VirtualBox VMs/Ubuntu/Logs directory, as well as a description of what you were doing when this error happened. Note that you can also access the above files by selecting Show Log from the Machine menu of the main VirtualBox window.
Press OK if you want to power off the machine or press Ignore if you want to leave it as is for debugging. Please note that debugging requires special knowledge and tools, so it is recommended to press OK now.""

"	dwhea
14591	Critical Error - Failed to create VirtualBoxClient COM object	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
14878	critical error - GuruMed - HP Solution Center (printer software) always causes in 4.3.34 and 5.0.10	VirtualBox 4.3.34	2015-11-30T11:17:45Z	2016-03-13T13:25:02Z	2016-03-13T13:25:02Z	"Hello,
Thanks for the work you put into OVB, I think it is great!

I have run into a problem with the latest releases that I would like your help with. I have been running OVB for about a year or so and have not had a problem with this software until recently. HP Solution Center is an app that is installed with the HP all-in-one printer driver/software and I use it to launch the scanner component. 

It works fine with OVB releases 4.3.30 and 4.3.32, but it causes an issue in 4.3.34 and 5.0.10. I have not tested earlier releases of 5.0.x. 

I have 64-bit Win 7 guest running on Ubuntu 14.04 LTS.
I have a Photosmart C7280 connected via USB 2 EHCI controller. I have also reproduced the issue when setting up the printer as a network device (bridged Intel PRO/1000 MT Desktop (82540EM)), rather than a USB device.

To download the software, go to http://support.hp.com/us-en/drivers/ and enter the model of ""photosmart c7280"", change the selected OS to MS Win 7 (if not already selected), and download PS_AIO_02_Net_Full_Win_WW_130_140.exe (released 2009-10-20). 

I believe during installation you can skip the printer setup. However, I'm not sure if the issue is reproducible without a printer/scanner being set up. I can do more research and update this ticket. 

Once the installation has completed (and after rebooting), the next and final step is to launch HP Solution Center. 

I set the priority to major without knowing the cause or the full effect of this issue. My guess is that it could be affecting other printer software, and possibly more. 

Thanks for your help.
Chuck"	ceastus
20281	Critical error CentOS 7	VirtualBox 5.2.16	2021-04-02T10:18:23Z	2021-04-02T10:18:23Z	2021-04-02T10:18:23Z	Once a week, a virtual machine running centos 7 crashes with a critical error. Windows server 2008 r2 host - freezes. It is not possible to shutdown virtualbox. Only rebooting the host helps.	Ruby_Ridge
17496	critical error guru meditation	VirtualBox 5.2.6	2018-01-23T06:52:37Z	2018-01-23T09:35:36Z	2018-01-23T09:35:36Z	"sir,
   there is an issue in my virtual box in which my xp virtual window going to
 guru meditation & not work my virtual box window.
"	lalla
19246	Critical error immediately on startup	VirtualBox 6.1.2	2020-01-21T11:01:12Z	2020-01-21T11:01:12Z	2020-01-21T11:01:12Z	"Start button fails within seconds. Failed on R 6.0 so I tried installing 6.1 with same result. As far as I'm aware nothing changed on my system between the last day it worked and the day it failed. 
Please help."	aj_m
20795	Critical error occurred while running VM after Fedora 29 -> 31 upgrade	VirtualBox 6.1.32	2022-01-29T06:28:30Z	2022-02-01T22:46:14Z	2022-02-01T22:46:14Z	"
Had an older version of Fedora 29 running on VirtualBox 6.1.32.  Used the upgrade instructions from this page to upgrade from Fedora 29 to 31, https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/.  The plan was to upgrade from 29 -> 31 -> 33 -> 35.

Fedora 29 was running with no problems on VirtualBox 6.1.32.  After using the upgrade instructions with no apparent errors and the upgrade verification was successful the VM tried to restart with the new installation of Fedora 31.  At that point I got the ""A critical error occurred while running the Virtual Machine.""  The log file and  .png file are attached.  There were no changes to the VirtualBox configuration, the Fedora upgrade process is automatic and after it completes it relaunches the new version.

Note that I tried upgrading to the 6.1.33 build and got the exact same problem, the attached logs are from the 6.1.32 and 6.1.33.
"	dbhinz
17596	Critical Error occurs when trying to build Ubuntu 16.04.4	VirtualBox 5.2.8	2018-03-06T15:22:55Z	2018-04-17T13:08:10Z	2018-04-17T13:08:10Z	"VirtualBox allows me to create a new VM, but just a couple seconds after I point to the ISO for the start-up disk selection, I get a somewhat generic error screen.  It's titled ""VirtualBox - Guru Meditation "".  It says ""A critical error has occurred while running the virtual machine and the machine execution has been stopped.""

I've used many other versions of Ubuntu and Linux on this Win10 host running VirtualBox version 5.2.8 r121009.  I've downloaded this Ubuntu-16.04.4-desktop-i386.iso from several different sources now and they all yield the same result when trying to build a VM."	runnerb0y
19435	Critical error on boot of KISS linux - enters Guru meditation	VirtualBox 6.1.4	2020-03-27T10:36:47Z	2020-03-27T12:06:17Z	2020-03-27T12:06:17Z	I've installed KISS linux to a VDI using an Arch Linux iso. Whenever i attempt to boot from the VDI it immediately enters Guru meditation - before even entering GRUB. I've attached VBox.log.	eranee
16820	Critical error on Windows 7 guest	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
19328	Critical error pop up when starting machine	VirtualBox 6.1.2	2020-02-20T22:31:08Z	2020-02-20T22:31:08Z	2020-02-20T22:31:08Z	When I try to load virtual machine after rebooting I get a pop up stating critical error and suggesting I post here with the logs. If it is relevant, Ubuntu had just performed updates.	tdsTPPS
20891	Critical Error starting VM Machine	VirtualBox 6.1.32	2022-04-01T15:36:41Z	2022-04-04T11:54:50Z	2022-04-04T11:54:50Z	"After some minutes of run, the VM go in a critical error.
Sometimes during the boot of VM I have a critical error and the VM stops.

The VM Machine has Windows 10 OS.
The host machine is Windows 7

Some days ago there was no trouble running this VM. Now I have this trouble.
I have tried to update VirtualBox (now is 6.1.32 r 149290 (Qt5.6.2)) but I have the same error.

In attach: VBox.log,  VBox.png, ""screen-shot of error"""	Bebuccio
20974	Critical Error while installing windows 10 in virtualbox	VirtualBox 6.1.34	2022-06-08T17:00:27Z	2022-06-08T17:00:27Z	2022-06-08T17:00:27Z	Critical Error while installing windows 10 in virtualbox. At the beginning of the install of windows 10 a popup window alerted me that an error occurred. It did not specify the error but gave an option to ignore or power down.	Tony_Z
20587	Critical error while running virtual machine	VirtualBox 6.1.26	2021-10-01T12:19:57Z	2021-10-01T12:19:57Z	2021-10-01T12:19:57Z	"Error message is appearing on trying to start virtual machine: Critical error has occurred while running the virtual machine and the machine execution has been stopped.
"	SUNNY25
17251	Critical Error whilst starting game	VirtualBox 5.2.0	2017-11-07T06:04:55Z	2017-11-07T06:04:55Z	2017-11-07T06:04:55Z	I was trying to start Melbourne Cup Challenge/Frankie Dettori Racing when the Critical Error message came up. I am running Windows 10 and this game last ran on Windows XP. I have Windows XP 32-bit installed on Virtual Box.	James Bluntus
21114	Critical error. The memory could not be read.	VirtualBox 6.1.38	2022-09-29T13:24:38Z	2022-09-29T13:24:38Z	2022-09-29T13:24:38Z	Unfortunately, I don't have a log file or a reproduction step for the error.	Eugene
19292	Critical Error: Guru Meditation	VirtualBox 6.1.2	2020-02-05T23:37:45Z	2020-02-05T23:37:45Z	2020-02-05T23:37:45Z	"I set up an Ubuntu 18.04 guest on my Macbook Pro 2019 earlier today, and everything was going ok and I was able to use it. I set up port forwarding with VBoxManage modifyvm ""vmname"" --natpf1 ""ssh,tcp,127.0.0.1,3022,10.0.2.15,22"" and was able to ssh into my vm. I was also able to use VBoxHeadless successfully. I then opened the VirtualBox GUI, right clicked on my virtual machine name and opened settings, and changed the name of the guest slightly (there was an uppercase by mistake). I then checked to see if my port forwarding rule had been updated and it had. Upon trying to use VBoxHeadless to start the vm it produced a lot of errors in the command line, so I stopped it and tried to open it with the VirtualBox GUI. This was when I receive the Critical Error message and was directed here. I have attached the log file and png from the log folder as requested in the pop up box."	josh6
18915	Critical structure corruption blue screen	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
20185	Crush VM and GUI	VirtualBox 6.1.18	2021-02-13T16:15:51Z	2021-02-13T16:15:51Z	2021-02-13T16:15:51Z	The program swore many windows about the error on each of the 2 running VMs.	Дмитро
21231	Current State displayed as (changed) just after taking snapshots	VirtualBox-7.0.2	2022-11-01T14:29:42Z	2022-11-05T11:29:47Z	2022-11-05T11:29:47Z	"Running Virtualbox Version 7.0.0 r153978 (Qt5.15.2) on Windows 11.
I powered off 2 virtual machines (one Linux guest and another FreeBSD guest). I wait a couple of minutes after they have been powered off to take a snapshot of current state, but for some reason says ""Current State (changed)"" like if I powered on the virtual machine after that, which did not happen.

I had noticed this to happen to me occasionally with FreeBSD guest, but now is happening to me also with Linux guest.

If I take a second consecutive snapshot without powering on the vm, then it's fixed and now says ""Current State"" without (changed).

Could not test if the issue is reproducible with the Linux or macOS versions of Virtualbox, anybody had the same issue?

Forum thread: https://forums.virtualbox.org/viewtopic.php?f=6&t=107653"	DeGarden
18919	Cursor doesn't capture	VirtualBox 6.0.12	2019-09-09T22:07:48Z	2019-09-12T13:14:40Z	2019-09-12T13:14:40Z	Hello, I have a problem. The cursor doesn't capture on my Windows 98 guest. I hope there's a solution. It happens, surprise, on the !VirtualBox last version and Windows 98 SE.	SamiVirtualBox
18382	Cursor scaling - cursor becomes very small or sometimes almost invisible	VirtualBox 6.0.4	2019-01-29T07:16:02Z	2019-01-29T07:16:02Z	2019-01-29T07:16:02Z	"This bug is not new to version 6 as I've seen it in 5.2 also. The mouse pointer (hardware cursor) depending on the application can become very small or even almost disappear. The cursor becomes much smaller in the RDP session started from the guest. Also it is smaller and with weird shapes in MS Office applications like Excel or Word. In Word or any other text editor (like Notepad++) where the cursor should be an I-beam it pretty much disappears. What is left of it when the mouse pointer is over an editor window are literally 2 pixels. Almost impossible to see.
This bug has been on and off over the last few months. I suspect although have no proof that Microsoft patches to the host or guest OS cause this change of behavior. Right now the bug is fully ""visible"" (pun intended)."	Rafcio
16884	custom vbox icons revert second time vm is run	VirtualBox 5.1.22	2017-07-07T14:45:14Z	2017-07-07T17:55:59Z	2017-07-07T17:55:59Z	"Related to https://www.virtualbox.org/ticket/15052

I would like to give my VMs custom icons, to distinguish between them in the Dock (tray) and in the app switcher (which for all but the selected app shows only the icon)

In macOS you can give a file or app a custom icon via the Finder by opening the `Get Info` window, selecting the icon, and pasting a new one on top of it.

If I give one of my _.vbox_ VM files a custom icon via `Get Info > paste the new icon`, VirtualBox reverts it to the default light blue cube after on the second open. That is, I apply a custom icon, open the VM, shut down the VM, and open the VM, and while it's opening for the second time the icon reverts.

"	olets
15855	Custom VESA mode does not work for 4bit resolution	VirtualBox 5.1.2	2016-08-24T23:38:00Z	2016-08-24T23:38:00Z	2016-08-24T23:38:00Z	"I'm trying to add custom VESA mode 1400x1050x4.

I'm using command VBoxManage setextradata ""WinXp"" ""CustomVideoMode1"" ""1400x1050x4""

and the line

	<ExtraDataItem name=""CustomVideoMode1"" value=""1400x1050x4""/>

is created in WinXp.vbox correctly.

When I try to start the virtual machine VB gives me the VERR_VGA_INVALID_CUSTOM_MODE error.

Note, that 1400x1050x8, 16, 24 and 32  work very fine, but I'm interested in 4bit colors.

A small modification in 'VBox/Devices/Graphics/DevVGA.cpp' will probably solve this problem.

Please refer to the attached 'Custom VESA mode 4bit resolution.png' for a possible solution."	ErikB
12050	Customizable keybindings needed		2013-08-26T19:06:07Z	1970-01-01T00:00:00Z	1970-01-01T00:00:00Z	"Since Win8.x now has a dependency on the Win-Key, and there are keyboards that do not have the ""Windows Keys"", there needs to be a utility for creating custom keybindings for VirtualBox VMs.   I'm considering custom keybindings rather than hard-coding some combination for the WinKey, since that allows the flexibility for a user to re-map keys which the Host OS may want to use for different purpose."	jelabarre59
19169	"CVE-2019-11135 causes Win10 Guests with Q2'19 Intel CPUs to get stuck with ""IEM: wrmsr(0x122,0x0`00000003) -> #GP(0)"""	VirtualBox 6.0.8	2019-12-17T19:13:19Z	2020-07-09T13:03:59Z	2020-07-09T13:03:59Z	"When applying the [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11135 CVE-2019-11135] microcode update via Microsoft's [https://support.microsoft.com/en-us/help/4524570/windows-10-update-kb4524570 2019-11 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB4524570)], a Win10 (64-bit) guest will not boot completely, but will rather get stuck with:
{{{
00:00:07.800331 IEM: wrmsr(0x122,0x0`00000003) -> #GP(0)
}}}
Intel CPUs that have been affected so far are all Q2'19:
* [https://ark.intel.com/content/www/us/en/ark/products/193563/intel-core-i7-8665u-processor-8m-cache-up-to-4-80-ghz.html Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz]
* [https://ark.intel.com/content/www/us/en/ark/products/192987/intel-core-i9-9880h-processor-16m-cache-up-to-4-80-ghz.html Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz]
* [https://ark.intel.com/content/www/us/en/ark/products/192993/intel-xeon-e-2286m-processor-16m-cache-2-40-ghz.html Intel(R) Xeon(R) E-2286M  CPU @ 2.40GHz]

This affects all !VirtualBox > 6.0.8, hence the 6.0.10 version assigned.

Related discussion in the forums: https://forums.virtualbox.org/viewtopic.php?f=2&t=95783"	Socratis
14605	Date and time on Linux guests is not updated after a session restoration	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
14917	Debian guest is aborted when plugging in or unplugging thunderbolt on mac host	VirtualBox 5.0.10	2015-12-10T16:20:29Z	2015-12-10T16:20:29Z	2015-12-10T16:20:29Z	"Guest:
Debian Jessie
3.16.0-4-amd64
monitor count 2
video memory 50
ram 9000 MB
cpu 4

Host:
MacBook Pro (Retina 15-inch, Late 2013)
Processor: 2.3 GHz Intel Core i7
Memory: 16 GB
Graphics NVIDIA GeForce GT 750M 2048 MB

Unfortunately this issue is intermittent, but sometimes when I plug in or unplug the thunderbolt to an external monitor the guest goes right to aborted.

I would like to attach logs to this ticket, but I see how to.



"	ranamala
20492	Debian installer hangs: BUG: unable to handle kernel NULL pointer dereference at 00000004	VirtualBox 6.1.26	2021-08-06T22:14:39Z	2021-08-06T22:14:39Z	2021-08-06T22:14:39Z	"I'm trying to install Debian 10 i386 on a Windows 10 (64-bit) host but the installer hangs during ""Select and install software"", specifically ""Configuring man-db (i386)"". Do not modify the default software selection (Debian desktop, print server and standard system utilities). It happens every time, both in the graphical and the non-graphical installer. I'm running an AMD Ryzen 7 3800X and AMD-V appears to be enabled.

This is logged by the kernel once the system hangs:
{{{
[  401.003262] BUG: unable to handle kernel NULL pointer dereference at 00000004
[  401.003775] *pde = 00000000 
[  401.003978] Oops: 0002 [#1] SMP
[  401.004197] CPU: 0 PID: 21003 Comm: mandb Not tainted 4.19.0-17-686 #1 Debian 4.19.194-1
[  401.004767] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
[  401.005336] EIP: _raw_spin_lock+0x14/0x30
[  401.005618] Code: 89 d8 5b 5d c3 90 89 c8 e8 c9 7e a2 ff eb f1 8d b4 26 00 00 00 00 0f 1f 44 00 00 55 89 c1 89 e5 53 31 d2 bb 01 00 00 00 89 d0 <3e> 0f b1 19 85 c0 75 04 5b 5d c3 90 89 c2 89 c8 e8 27 6a a2 ff 90
[  401.007152] EAX: 00000000 EBX: 00000001 ECX: 00000004 EDX: 00000000
[  401.007694] ESI: 00000000 EDI: 00000020 EBP: ee4efef8 ESP: ee4efef4
[  401.008228] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS: 00010046
[  401.008863] CR0: 80050033 CR2: 00000004 CR3: 362bf000 CR4: 000406d0
[  401.009382] Call Trace:
[  401.009597]  speculation_ctrl_update+0x1aa/0x220
[  401.009976]  speculation_ctrl_update_current+0x18/0x20
[  401.010399]  task_update_spec_tif+0x25/0x30
[  401.010745]  ssb_prctl_set.part.1+0x1d/0x30
[  401.011091]  arch_seccomp_spec_mitigate+0x45/0x50
[  401.011488]  do_seccomp+0x5b0/0x5f0
[  401.011776]  sys_seccomp+0x16/0x20
[  401.012059]  do_fast_syscall_32+0x81/0x1a0
[  401.012400]  entry_SYSENTER_32+0x68/0xbb
[  401.012848] EIP: 0xb7efdd31
[  401.013188] Code: f6 ff ff 55 89 e5 8b 55 08 8b 80 5c cd ff ff 85 d2 74 02 89 02 5d c3 8b 04 24 c3 8b 1c 24 c3 90 90 51 52 55 89 e5 0f 34 cd 80 <5d> 5a 59 c3 90 90 90 90 8d 76 00 58 b8 77 00 00 00 cd 80 90 8d 76
[  401.015419] EAX: ffffffda EBX: 00000001 ECX: 00000000 EDX: 0162db20
[  401.016174] ESI: 015b5352 EDI: b7eded4d EBP: b7c7dde9 ESP: bfdab85c
[  401.016929] DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 007b EFLAGS: 00000246
[  401.017753] Modules linked in: fuse battery dm_mod md_mod xfs jfs btrfs xor zstd_decompress zstd_compress xxhash raid6_pq libcrc32c vfat fat ext4 crc16 mbcache jbd2 crc32c_generic fscrypto ecb e1000 nls_utf8 isofs usb_storage hid_generic usbhid hid sr_mod cdrom sd_mod ata_generic ohci_pci ehci_pci ohci_hcd ehci_hcd ata_piix snd_intel8x0 snd_ac97_codec ahci libahci ac97_bus evdev libata psmouse snd_pcm snd_timer usbcore usb_common snd soundcore scsi_mod
[  401.022503] CR2: 0000000000000004
[  401.022903] ---[ end trace 8693d9353e91b6c4 ]---
[  401.023448] EIP: _raw_spin_lock+0x14/0x30
[  401.023933] Code: 89 d8 5b 5d c3 90 89 c8 e8 c9 7e a2 ff eb f1 8d b4 26 00 00 00 00 0f 1f 44 00 00 55 89 c1 89 e5 53 31 d2 bb 01 00 00 00 89 d0 <3e> 0f b1 19 85 c0 75 04 5b 5d c3 90 89 c2 89 c8 e8 27 6a a2 ff 90
[  401.026189] EAX: 00000000 EBX: 00000001 ECX: 00000004 EDX: 00000000
[  401.026947] ESI: 00000000 EDI: 00000020 EBP: ee4efef8 ESP: dca193bc
[  401.027704] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS: 00010046
[  401.028492] CR0: 80050033 CR2: 00000004 CR3: 362bf000 CR4: 000406d0
}}}

I've attached the full kernel log, as well as the VirtualBox log on the host."	joelpuig
20955	Debian Jessie not booting on VBox 6.0.24		2022-05-23T11:15:00Z	2022-05-23T16:45:03Z	2022-05-23T16:45:03Z	"Hello,

Recently downloaded VirtualBox under Windows, and I'm struggling to run Debian 8.11.1 ('''Jessie''') as my ''guest'' OS.

At the moment, I've tried to boot it from a ''DVD'' iso (after successful installation), but as soon as it's meant to login the screen prompts a message like ""Something went wrong, and the system can't recover""...

I've read this might be due to VBox graphical settings, and that a VBoxSVGA controller was suggested in place of VMSVGA.

Almost nothing changed by enabling or disabling 3D acceleration...

Please, can you help?

Mine was the first installer from here: [https://cdimage.debian.org/cdimage/archive/8.11.1/amd64/iso-dvd/]

Thanks"	Antonin
20445	debian packages use version number in package name	VirtualBox 6.1.22	2021-07-02T18:03:18Z	2021-07-02T18:03:18Z	2021-07-02T18:03:18Z	"The Debian package system aptitude is based on the assumption that the name of a package does not include any part of the version number, except in special cases, as for certain libraries, in which the major field of the version expresses the API, and is needed to determine compatibility with dependent packages.

The reason for such an assumptions largely is to facilitate automatic upgrades, in which the package manager may detect that a new version supersedes an older by virtue of the names matching but the version fields (in the metadata not the package name) being different.

Thus, the package name virtualbox-6.1 should be changed to simply virtualbox (or virtualbox-oracle to avoid collisions with packages created by distribution creators), such that users would automatically acquire version 6.2, or 7.0, when it becomes available.

"	brainchild
18410	debian-stretch-netinst does not work with 'VBoxManage unattended install' because of incorrect install menu defaults	VirtualBox 6.0.4	2019-02-05T08:50:00Z	2019-09-17T19:52:27Z	2019-09-17T19:52:27Z	"[attached script: reproduce-bug.sh] # 88 lines[[BR]]
[attached patch: fix.patch] # 4 lines[[BR]]

The install menu defaults for the stock debian-stretch-netinst ISO is setup to be ""Graphical Install"" rather than just ""Install"".

The files in the ISO that control this are[[BR]]
/isolinux/menu.cfg[[BR]]
/isolinux/gtk.cfg[[BR]]
/isolinux/txt.cfg[[BR]]

VBoxManage already generates a replacement for one of the above files, but flattens its name to ${aux_base_path}isolinux-txt.cfg, so this file is patched after it was generated, but before it was used.[[BR]]
Specifically, this patch was applied after running 'VBoxManage unattended install ...' but before running 'VBoxManage startvm <vm>'.

This works only because the /isolinux/txt.cfg follows /isolinux/gtk.cfg (in /isolinux/menu.cfg) and thus can override its use of 'default label' and 'menu default'. But this order could change in the future so the ideal solution is below.

The ideal solution is[[BR]]
  - Remove 'default installgui' and 'menu default' (within 'label installgui') from /isolinux/gtk.cfg[[BR]]
  - Add 'default install' and 'menu default' (within 'label install') from /isolinux/txt.cfg[[BR]]

Currently, since there is no 'ui' directives used, the 'default installgui' and 'default install' are being ignored.[[BR]]
---[[BR]]
https://www.syslinux.org/wiki/index.php?title=Config

https://www.syslinux.org/wiki/index.php?title=Menu

The function that modifies /isolinux/txt.cfg is:[[BR]]
  src/VBox/Main/src-server/UnattendedInstaller.cpp:[[BR]]
  HRESULT UnattendedDebianInstaller::editDebianTxtCfg(GeneralTextScript *pEditor)[[BR]]

# to see the bug, do this[[BR]]
./reproduce-bug.sh[[BR]]

It will use the graphical installer, and thus mandates a manual install.[[BR]]

# to see my fix, do this[[BR]]
fix=1 ./reproduce-bug.sh[[BR]]
"	Robert Nielsen
16817	Debugging high CPU usage macOS	VirtualBox 5.1.22	2017-06-06T15:00:56Z	2017-06-06T20:13:09Z	2017-06-06T20:13:09Z	I'm using docksal to run a virtual box on macOS 10.12.4. When I view the activity monitor VBoxheadless is consumming 120-140% CPU. I've tried toggling a few things in the settings, but I'm out of my depth in terms of actually debugging the issue.	Claytron
20374	Default Start Mode Preference	VirtualBox 6.1.22	2021-05-20T16:57:35Z	2021-05-20T16:57:35Z	2021-05-20T16:57:35Z	"When I start the virtual machine in VirtualBox Manager, I want the virtual machine to start with my preferred startup mode (normal|headless|detached).

I want to set the default startup mode (normal|headless|detached) as a preference.

Thank you.

"	Lynda
14253	Default VM Start Method	VirtualBox 5.0.0	2015-07-09T13:58:25Z	2022-07-28T11:56:56Z	2022-07-28T11:56:56Z	Would like to see the ability to set detachable mode as the default start method when pressing the big green start button in the GUI.	jeremywj
18876	Default window size is inscrutably small on macOS	VirtualBox 6.0.10	2019-08-28T15:50:47Z	2019-08-28T17:08:35Z	2019-08-28T17:08:35Z	Ever since the v6 update to VirtualBox, the default window size has been ludicrously small, about 2 inches tall. Please fix the default window dimensions for modern Retina displays and test more on macOS before publishing releases.	mcandre
16217	Defaultly started VM  goes to shutdown if send it to background	VirtualBox 5.1.10	2016-11-23T09:48:14Z	2016-11-23T09:48:14Z	2016-11-23T09:48:14Z	"1) Start VM as always.

2) Choose ""Send to background"" in window context menu from Dock.

3) Window dissapeas, in VirtualBox.app discover that VM goes to shutdown."	776166
2906	Defining a keyboard filter	VirtualBox 2.1.0	2008-12-27T11:41:24Z	2009-01-03T20:42:01Z	2009-01-03T20:42:01Z	"Good morning,

Have you ever used a Windows guest on a Linux machine and tried to switch to the next desktop with a key combination like Ctrl+Alt+Right? Instead the keys are captured by the Windows guest which... does nothing with them.

In the same way one could want to let the host process some special keys like the media keys (Play, Next Track, Volume, ...) or the hotkeys we defined because we don't have a media keyboard, let the OS process Exposé / Flip 3D, etc.

That's why implementing a keyboard filter letting the user choose which keys are transfered to the guest and which are kept to the host could greatly improve the usability of virtual machines.

The filter would be defined per-machine because it depends on the guest OS and machines are not portable across OSes anyway, so no consistency problem is to be feared.

Additionaly, one could define if a shortcut is valid in full screen or only in windowed / seamless, else it may be necessary to add an ""Exclusive mode"" like VMWare in which filters are disabled. Thinking further, it may optionaly be useful allowing to redefine keys: for example Ctrl+Alt+Tab does Alt+Tab in the host, Win+F9 does F9 (Exposé).

Thank you for reading me,[[BR]]
Florian"	Brunni
15377	Delayed handling of mouse button	VirtualBox 5.0.20	2016-05-02T01:43:13Z	2016-07-12T06:50:14Z	2016-07-12T06:50:14Z	"When running Protel 99SE (an electronic schematic/PCB capture suite) in Virtualbox 5.0.20, clicking on a component to select it with the left mouse button is not recognised for between 500 and 1000 ms.  If the mouse is moved within this time the mouse button click is recognised and the component is selected at that point.  Otherwise selection only occurs after the time delay.

Protel 99SE is being run in a 32-bit mswindows guest, hosted on 64-bit Linux.  Win2k and winxp guests exhibit identical behaviour.  The problem occurs regardless of whether guest additions are installed.

A ""click"" in this context is a mouse button down/up event sequence - not a press and hold.

The problem did not occur in VirtualBox 4.1.x.  Testing shows it to be present in all versions of VirtualBox from 4.2.x on, and is independent of whether a 32-bit or 64-bit host OS is in use.

This regression seems to have been introduced at the same time as the problem described in ticket #15376, so it may be another manifestation of a change introduced in that version (perhaps in the way keyboard/mouse events are handled).
"	Jwoithe
21331	Delete of a VM does not delete unattended files, so can't recreate VM	VirtualBox-7.0.4	2022-12-09T23:40:43Z	2022-12-09T23:40:43Z	2022-12-09T23:40:43Z	If you create a VM using unattended installation, then you RMB on the VM in the hypervisor -> Remove -> Delete All, the unattended files remain.  then if you try to create a new VM using the same VM name, you get an error because of the left over files.	Justinh
18580	Deleting a snapshot doesn't show estimated time and operation progress bar always starts from 99%.	VirtualBox 6.0.6	2019-04-19T09:50:35Z	2019-04-21T13:19:53Z	2019-04-21T13:19:53Z	"Deleting a snapshot doesn't show estimated time and operation progress bar always starts from 99%.
Host: Windows 10 1809 (64-bit).

Quote from VirtualBox 6.0.6 Release Notes:
''""This is a maintenance release. The following items were fixed and/or added:
[...]
User interface: fixed operation progress when deleting snapshots""
''"	MisVin
18335	Deleting a snapshot shows an incorrect estimated time (14714 days 5 hours)	VirtualBox 6.0.2	2019-01-19T12:42:53Z	2019-02-13T07:13:41Z	2019-02-13T07:13:41Z	"After upgrading VirtualBox to version 6.0.0, when deleting a snapshot, the same time is always displayed (14714 days 5 hours), even if the snapshot deletion only takes a few minutes.
The problem also exists in version 6.0.2.
See also:
https://forums.virtualbox.org/viewtopic.php?f=8&t=90855
https://forums.virtualbox.org/viewtopic.php?f=15&t=90741
"	MisVin
21345	Deleting running VM snapshot leaves the .sav file on disk	VirtualBox-7.0.4	2022-12-18T16:39:15Z	2022-12-18T16:39:15Z	2022-12-18T16:39:15Z	"The snapshot file for running VM (.sav) remains on the disk after deleting the snapshot. Issue appeared with 7.0.4 and was not there in 6.1.xx.

I have multiple running VM snapshots so it takes time and effort to identify the unused .sav files and delete them manually.

Issue is replicated easily as mentioned on the [https://forums.virtualbox.org/viewtopic.php?f=6&t=108066 forum's thread]."	AmirPK
14679	Deleting Snapshot Error: VBOX_E_FILE_ERROR (0x80BB0004) - File not accessible or erroneous file contents	VirtualBox 5.0.4	2015-10-07T09:45:36Z	2015-10-07T09:55:32Z	2015-10-07T09:55:32Z	"Build used ""5.0.4.102546"" on Gentoo Linux 64 bit (binary package, so i did not need to compile anything), Modules Version ""5.0.4"".
Guest: ""Windows 10 Pro 64Bit""

When deleting a snapshot it seems it comes to some sort of race condition inside virtualbox. Afterwards the VM can't be used anymore, without setting it back to a snapshot before the deleted one.
It's randomly reproducible.
There are no errors known on the storage (harddisk, raid, and filesystem are clean and checked without errors).
This issue can reproduced on running VM's (deleting a live snapshot) or on pwoered off VMs.

Running the command from above results in a deleted snapshot file.
Reverting to an older snapshot in the dependency tree works fine and the VM is runnable. Reverting to a newer snapshot is not possible (as the depending parent snapshot of course is missing).
The vbox file was not updated by the command.


{{{#!default
VBoxManage snapshot ""Gaming01"" delete aa95f360-73a3-4b9a-958b-d21845d2f08a
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...
Progress state: VBOX_E_FILE_ERROR
VBoxManage: error: Snapshot operation failed
VBoxManage: error: Code VBOX_E_FILE_ERROR (0x80BB0004) - File not accessible or erroneous file contents (extended info not available)
VBoxManage: error: Context: ""RTEXITCODE handleSnapshot(HandlerArg*)"" at line 527 of file VBoxManageSnapshot.cpp
}}}
"	NightDragon
21169	Deprecation of libIDL on Linux	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
17278	Desplome de la Maquina virtual gana 10 al usar que Explorer	VirtualBox 5.2.0	2017-11-16T10:40:21Z	2017-11-16T10:40:21Z	2017-11-16T10:40:21Z	"Iniciar Internet explorer, y en ocasiones sin hacer nada se produce un error 
critico, abrir una nueva pestaña, cerrar I E., no es posible hacer nada con
 I. E.

Produce un error y muchas veces cierra la maquina virtual.

solo es necesario abrir I.E. y cerrarlo.

host 1709 ( c de so 16299.64 )
guest 1709  ( c de so 17035.1000 )

con guest windows 8.1 ocurre muy parecido, pero no cierra la maquina virtual
"	Josep Maria Mercé Currià
20951	Después de desconectar segundo monitor, la máquina virtual sigue intentando mostrarse allí	VirtualBox 6.1.32	2022-05-20T16:44:03Z	2022-05-20T16:44:03Z	2022-05-20T16:44:03Z	"Ayer trabajé con un monitor adicional a mi computadora.  Abrí una máquina virtual y la desplegué en el monitor externo.
Hoy ya no tengo ese monitor.  Abrí VirtualBox, abro la misma máquina virtual de ayer, pero no se despliega en la pantalla del computador, el problema es que se está desplegando en el monitor externo que ya no tengo conectado.
Bajé todas las ventanas (Win+D) para intentar ver la máquina virtual, pero no hay forma."	renezito
14258	Detachable broken when 3d acceleration is enabled	VirtualBox 5.0.0	2015-07-11T02:25:18Z	2015-10-07T09:27:17Z	2015-10-07T09:27:17Z	If you enable 3d acceleration for a VM it will not boot in detachable mode.	jeremywj
14442	Detachable GUI - Seamless mode not implemented	VirtualBox 5.0.2	2015-08-14T16:28:52Z	2015-08-14T16:28:52Z	2015-08-14T16:28:52Z	"This is a placeholder for implementing the Seamless mode with the detachable GUI mode. Goal would be equivalent behaviour compared to 4.3.30.[[BR]]
[[BR]]
Currently nothing will be displayed when switching to Seamless mode after starting the VM headless and attaching the GUI to it."	Max D
18889	Detect elementaryOS as Ubuntu 64-Bit	VirtualBox 6.0.10	2019-09-01T13:19:53Z	2019-09-01T14:34:58Z	2019-09-01T14:34:58Z	"I recently switched from Ubuntu to ElementaryOS (which is based on Ubuntu)

When I create a new VM with the wizard GUI, I want, that when I type ""elementary"" in the VM name text field, the OS should be detected as Ubuntu 64 Bit by default."	prischnikov
16683	DHCP Reservations	VirtualBox 5.1.20	2017-04-21T17:49:12Z	2018-12-13T10:40:14Z	2018-12-13T10:40:14Z	"Being able to define a DHCP IP reservation based on MAC address for Internal and NAT Networks. This is extremely useful having a reliable IP of r guest before the OS is installed. Think automated builds.

Running an external DHCP server is not always easy or even possible. Try to to install a DHCPd server on a Windows or Mac desktop.... "	hydrian
21417	Different IGuestSession::processCreate behavior in v7 from v6	VirtualBox-7.0.6	2023-01-18T10:56:03Z	2023-01-18T10:56:03Z	2023-01-18T10:56:03Z	In version 6 if call IGuestSession::processCreate with ProcessCreateFlag_Profile flag, new process created and its UI showed at virtual machine desktop. In version 7 if do the same call, the new process will be created as background process(no UI is displayed). Is it defect or an expected behavior? If expected behavior, please tell me how to create process with UI in version 7.	ReseT
7954	Different VBox question text deleting snapshots w/o merging	VirtualBox 4.0.0	2010-12-30T14:26:39Z	2010-12-31T17:26:03Z	2010-12-31T17:26:03Z	"Hello,

I would like to request an enhancement to the question pop-up text first shown when deleting snapshots using the VirtualBox Manager (GUI)?

This is the first portion of the text currently being shown:

""Deleting the snapshot will cause the state information saved in it to be lost, and disk data spread over several image files that VirtualBox has created together with the snapshot will be merged into one file.  This can be a lengthy process, and the information in the snapshot cannot be recovered.""

My request is to continue to show the above text when a merge will take place, and to show a different text when the snapshot data will be thrown away without any merge.  Perhaps truncating the current text to, ""Deleting the snapshot will cause the state information saved in it to be lost."" would be sufficient?  Or other wording that does not mention a merge will take place.

Thank you for your time and consideration.

Kind regards,
--appyface
"	appyface
18712	Digest mismatch (VERR_NOT_EQUAL)	VirtualBox 6.0.8	2019-06-16T20:35:37Z	2019-06-21T22:22:43Z	2019-06-21T22:22:43Z	Digest mismatch (VERR_NOT_EQUAL): Attribute 'SHA1' on 'C0916.ovf' does not match ('13f56535cf5261df839f3b97f2d4539ae856bb9b' vs. '9759331507231488c32eb31c35db32673af3b698').	RahulBilove
17067	Dir Copy Fails to Copy Files to Shared Dir	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
20739	Direct 3D Not Available On Virtualbox Windows 7 Guest	VirtualBox 6.1.30	2021-12-21T01:04:18Z	2021-12-21T01:04:18Z	2021-12-21T01:04:18Z	"My system prosesor is ryzen 5700G and use iGPU.

3D Acceleration is checked
Display RAM has set to 256MB
Guest Extension has installed with Direct3D Support (Experimental) checked

And the result still Direct 3D Not Available on DXDIAG Windows 7"	Fedro243
17133	Direct3D 7 Failure at step40 - NVIDIA GTX460	VirtualBox 5.1.28	2017-10-03T17:02:39Z	2017-10-09T10:24:36Z	2017-10-09T10:24:36Z	"I cannot get direct3d to run in my Windows XP Professional 32-bit guest.
Ran the Virtualbox addon program to enable direct3d.
DxDiag tests report failure on Direct3D 7 at step 40 (Creating flipping primary surface with one back buffer)
The screen flashes several times and then fails 3D emulation.
The other DxDiag tests seem ok. (one exception d3d 8 and d3d 9 list as old version.
Installed DirectX-2010 end-user runtime to update files.  Same status listed.
Have gone two days of troubleshooting to get to this point.
Please could you look into any issues with Nvidia GTX460 and this issue for VirtualBox Build 5.1.28."	Praetorian
12487	Disable ICH9 Chipset for NetWare Guests	VirtualBox 4.3.4	2013-12-15T07:20:21Z	2013-12-15T07:20:21Z	2013-12-15T07:20:21Z	"After a fair bit of experimentation, confusion, and trial/error, I have determined that using the ICH9 chipset on a variety of NetWare guests just leads to many issues, one of which is extremely subtle.

For example, if running a NetWare 4.2 SP9 guest (PIIX3 chipset), IPX-only, NDS 6.21, and you try to install an NW5.1SP8/NW6.0SP5 guest into the existing tree, also IPX-only, but using the ICH9 chipset, then the second guest cannot see the first over IPX.  I even ran a packet capture and the two were definitely talking to each other during the initial setup, but once you try to install the second guest into the first's tree, they stop and IPX just breaks down.  Setting the second guest back to PIIX3 chipset solves this problem.

So I think the best thing to do is to just disable the chipset field in the guest properties if the chosen guest type is ""Other/NetWare"" so people who try this in the future don't go through the same punishment."	kumba
3813	Discarding a Snapshot should not decrease space left on the device before increasing it	VirtualBox 2.1.2	2009-04-22T18:38:29Z	2009-07-31T14:21:25Z	2009-07-31T14:21:25Z	This is very related to the ticket http://www.virtualbox.org/ticket/3811 . That one is to avoid making the VM unusable. This one is to allow the user save disk space by discarding Snapshots instead of finding something else to remove on the partition (because what usually happens is that the user runs out of space *because* of not noticing how much space VirtualBox Snapshots take).	Andres G. Aragoneses
18063	Disk encryption causes guest to crash	VirtualBox 5.2.20	2018-10-20T14:24:02Z	2018-10-26T00:18:19Z	2018-10-26T00:18:19Z	"Enabling disk encryption under General tab in VB causes VM to not start afterwards. Windows error ""A recent hardware or software change might be the cause"". VM goes into a typical Windows repair process that doesn't work. Issue is happening with Windows 7 and XP both. VB version 5.2.20 with updated Extension Pack 5.2.20 as well."	mfuszner
20321	disk vmdk corrupted	VirtualBox 5.2.32	2021-04-23T17:36:32Z	2021-04-23T17:36:32Z	2021-04-23T17:36:32Z	"I want to describe my happening:
I have 2 laptops
One with Virtual box 5.2.32 r132073 (Qt5.6.2) version
One with Virtual box 6.1 version

I have first enlarged my vmdk by using VBoxmanage.exe from 10 GB to 100Gb and I have used with my Ubuntu Linux VM for developing. All right.
Then I have moved this vmdk on an external disk (1 Tera) in order to have much more space on my physical disk c:


Any days ago I have thought of create another Vm on second laptop with Virtual Box 6.1 version and use the same virtual disk after lighting my first VM on first laptop off.

So I have corrupted my virtual disk vmdk. In fact now when I use my first laptop and launch my VM I obtain this list of message:

....
...
...
...
...

...

fatal error token exceeds yylmax

  "	masdelmon
17962	Display after resize goes black	VirtualBox 5.2.18	2018-08-30T13:05:18Z	2019-10-10T01:54:06Z	2019-10-10T01:54:06Z	"Hi,

after resizing display it goes black and VM has to be restarted. VB is running on Win10 enterprise 64bit, guest system is Ubuntu."	Zool0
21195	Display issue with Windows 8	VirtualBox-7.0.2	2022-10-23T09:32:08Z	2022-10-23T09:32:08Z	2022-10-23T09:32:08Z	"Windows 8 may not render UI properly in VirtualBox 7.0.2 r154219.
Guest OS: Windows 8
Host OS: Windows 10 Pro 21H2
Virtual Graphics Card: VBOXSVGA(192MB VRAM)
Host Graphics Card: Intel HD Graphics 4000 and AMD Radeon HD8570M with dinamic-switching.
[[Image()]]"	Shimakaze
16250	Display resolution capped at 1024x768	VirtualBox 5.1.10	2016-11-30T22:58:53Z	2016-12-01T17:28:20Z	2016-12-01T17:28:20Z	Just installed 5.1.10 r112026 Qt5.6.2 and tried to get Lubuntu running on a Win 7/64 workstation with dual 1920x1080 displays. Tried setting everything in sight including preferences but the Lubuntu VM still shows a capped display size. Similar to bugs: 15997  15788  15310	stkvbox
19081	Display shrinks to 1024x768	VirtualBox 6.0.14	2019-11-13T13:01:31Z	2019-11-16T08:39:50Z	2019-11-16T08:39:50Z	"I've been using VirtualBox for several years but recently my Windows 10 guest upgraded from release 1803 to 1903. Since then I've had problems.

Initially I would have random lockups. Suddenly the guest would be unresponsive and after a while it would crash and VirtualBox would report that the guest had aborted. Googling led me to sites that suggested the lockups were usually related to the graphics driver.

I was using VBoxVGA (as I'd originally started on v5.1 of VirtualBox). After lots of reading about the VirtualBox video drivers I discovered I should have been using VBoxSVGA when I upgraded to v6.0 of VirtualBox (currently on v6.0.14).

Since the switch I've not had any lockups but at random times instead my desktop shrinks. I'm using a 4K monitor in Full Screen mode (3840x2160) and when the shrink occurs the Windows 10 desktop has shrunk to 1024x768 and is centred on the screen with a massive black border all around. The guest hasn't crashed and Host+F twice restores the screen to the full size but all my open applications have been squashed too, so I have to resize them.

I asked this question on the forums and it was suggested I log the problem here with logs.

When I originally reported the issue in the forums I was at home using my Windows 7 desktop but it's just occurred while I'm away running the VM on my laptop (Win 10 Home host).

Host: Windows 10 Home (Build 1903)
Guest: Windows 10 Pro (Build 1903)"	Iain Waddell
15498	display size 4096 or more is impossible; guest size is screen size modulo 4096	VirtualBox 5.0.20	2016-06-10T09:30:21Z	2016-09-08T07:06:31Z	2016-09-08T07:06:31Z	"In ''Auto-resize Guest Display'' mode or also in Fullscreen mode on a very large screen (4096 pixels or more). I see the following wrong behaviour:

The guest's screen size is only ''actual screen size modulo 4096'' rounded down to the next smaller multiple of 8.
If the size is 4096, then 4096 % 4096 = 0, then the default 1024 width is applied. (or 768 for the height)

I tried setting different sizes with `VBoxManage controlvm <VMName> setvideomodehint` command.

I attached the VBox.log file. during that session I had executed the following commands:

{{{
VBoxManage controlvm Kubuntu setvideomodehint 4096 2160 32
VBoxManage controlvm Kubuntu setvideomodehint 4095 2160 32
VBoxManage controlvm Kubuntu setvideomodehint 4087 2160 32
VBoxManage controlvm Kubuntu setvideomodehint 8192 2160 32
VBoxManage controlvm Kubuntu setvideomodehint 8191 2160 32
VBoxManage controlvm Kubuntu setvideomodehint 8193 2160 32
VBoxManage controlvm Kubuntu setvideomodehint 9192 2160 32
VBoxManage controlvm Kubuntu setvideomodehint 1000 4095 32
VBoxManage controlvm Kubuntu setvideomodehint 1000 4096 32
VBoxManage controlvm Kubuntu setvideomodehint 0 0 32
VBoxManage controlvm Kubuntu setvideomodehint 4088 2160 32
}}}


In the log file one can see, that the resulting guest display size is wrong whenever  w > 4095 or h > 4095

{{{
00:00:15.395987 VMMDev: SetVideoModeHint: Got a video mode hint (4096x2160x32)@(0x0),(1;0) at 0
00:00:15.439417 Display::handleDisplayResize: uScreenId=0 pvVRAM=00000001266af000 w=1024 h=2160 bpp=32 cbLine=0x1000 flags=0x1

00:02:15.240295 VMMDev: SetVideoModeHint: Got a video mode hint (4095x2160x32)@(0x0),(1;0) at 0
00:02:17.409141 Display::handleDisplayResize: uScreenId=0 pvVRAM=00000001266af000 w=4088 h=2160 bpp=32 cbLine=0x3FE0 flags=0x1

00:02:56.419179 VMMDev: SetVideoModeHint: Got a video mode hint (4087x2160x32)@(0x0),(1;0) at 0
00:02:58.579637 VBVA: InfoScreen: [0] @0,0 4080x2160, line 0x3fc0, BPP 32, flags 0x1

00:03:19.311747 VMMDev: SetVideoModeHint: Got a video mode hint (8192x2160x32)@(0x0),(1;0) at 0
00:03:20.454025 Display::handleDisplayResize: uScreenId=0 pvVRAM=00000001266af000 w=1024 h=2160 bpp=32 cbLine=0x1000 flags=0x1

00:03:25.949484 VMMDev: SetVideoModeHint: Got a video mode hint (8191x2160x32)@(0x0),(1;0) at 0
00:03:28.074011 Display::handleDisplayResize: uScreenId=0 pvVRAM=00000001266af000 w=4088 h=2160 bpp=32 cbLine=0x3FE0 flags=0x1

00:03:43.210929 VMMDev: SetVideoModeHint: Got a video mode hint (8193x2160x32)@(0x0),(1;0) at 0
00:03:44.349569 Display::handleDisplayResize: uScreenId=0 pvVRAM=00000001266af000 w=2560 h=1600 bpp=32 cbLine=0x2800 flags=0x1

00:04:06.325388 VMMDev: SetVideoModeHint: Got a video mode hint (9192x2160x32)@(0x0),(1;0) at 0
00:04:08.445923 VBVA: InfoScreen: [0] @0,0 1000x2160, line 0xfa0, BPP 32, flags 0x1

00:04:43.460792 VMMDev: SetVideoModeHint: Got a video mode hint (1000x4095x32)@(0x0),(1;0) at 0
00:04:45.586547 Display::handleDisplayResize: uScreenId=0 pvVRAM=00000001266af000 w=1000 h=4095 bpp=32 cbLine=0xFA0 flags=0x1

00:04:49.388757 VMMDev: SetVideoModeHint: Got a video mode hint (1000x4096x32)@(0x0),(1;0) at 0
00:04:51.501883 Display::handleDisplayResize: uScreenId=0 pvVRAM=00000001266af000 w=1000 h=768 bpp=32 cbLine=0xFA0 flags=0x1

00:05:34.159715 VMMDev: SetVideoModeHint: Got a video mode hint (4088x2160x32)@(0x0),(1;0) at 0
00:05:35.290404 VBVA: InfoScreen: [0] @0,0 4088x2160, line 0x3fe0, BPP 32, flags 0x1

}}}


it looks like the size is only an 8 bit integer.  The lowest 4 bits are always 0 and bits 13 and up are lost.

I tried this with several Linux distributions (Ubuntu, Kubuntu, Mint, Fedora). The behaviour is always the same.

"	schnidrig
15750	Distorted display on / after pausing / taking / restoring snapshot	VirtualBox 5.1.2	2016-08-05T08:44:07Z	2016-08-05T21:40:09Z	2016-08-05T21:40:09Z	"Host: VirtualBox 5.1.2 on Mac OS X 10.11.3

Guest: Windows 7 32-bit

When pausing a VM, taking a snapshot or restoring a snapshot the display is distorted. The only way to clear the display is to click the affected areas and / or resize a window to be full screen.

This problem did not occur with VirtualBox 5.1.0. This only seems to affect my Windows 7 32-bit VM, a Windows 10 64-bit VM is unaffected."	Nathan Pardoe
19868	Divide by zero crashes VM		2020-09-07T12:23:59Z	2020-09-07T15:22:41Z	2020-09-07T15:22:41Z	"I have multiple, reproducible crashes on macOS host with Windows 10 guest.

Will attach 4 example crash reports.

Note that I run 6.1.12, not 6.1.14, and the update checker thinks this is the latest release.

--- 1 ---

Crashed Thread:        23  TaskSet0

Exception Type:        EXC_ARITHMETIC (SIGFPE)
Exception Codes:       EXC_I386_DIV (divide by zero)
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Floating point exception: 8
Termination Reason:    Namespace SIGNAL, Code 0x8
Terminating Process:   exc handler [63034]

--- 2 ---

Crashed Thread:        25  TaskSet0

Exception Type:        EXC_ARITHMETIC (SIGFPE)
Exception Codes:       EXC_I386_DIV (divide by zero)
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Floating point exception: 8
Termination Reason:    Namespace SIGNAL, Code 0x8
Terminating Process:   exc handler [5393]

--- 3 ---

Crashed Thread:        23  TaskSet0

Exception Type:        EXC_ARITHMETIC (SIGFPE)
Exception Codes:       EXC_I386_DIV (divide by zero)
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Floating point exception: 8
Termination Reason:    Namespace SIGNAL, Code 0x8
Terminating Process:   exc handler [23291]

--- 4 ---

Crashed Thread:        26  TaskSet0

Exception Type:        EXC_ARITHMETIC (SIGFPE)
Exception Codes:       EXC_I386_DIV (divide by zero)
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Floating point exception: 8
Termination Reason:    Namespace SIGNAL, Code 0x8
Terminating Process:   exc handler [66175]
"	jonashaag
19781	DMI Handle is not unique	VirtualBox 6.1.8	2020-07-30T13:42:09Z	2020-07-30T13:42:09Z	2020-07-30T13:42:09Z	"I have been having issues with the DMI on VirtualBox.

When I run dmidecode on Ubuntu 18.04, there are 2 entries for Handle 0x0008.
When python's py-dmidecode runs, it loops through the DMI and the contents of the second entry for Handle 0x0008 replace the previous entry, causing it's output to be invalid.

I think the Handle entries should be unique.

I have attached a copy of my dmi output with the above issue (0x0008 listed twice)."	MattRobinson
18430	DnD does work from Host to Guest but not the reverse	VirtualBox 6.0.4	2019-02-11T22:27:26Z	2019-02-11T22:27:26Z	2019-02-11T22:27:26Z	"Hi, I'm kind of new with VirtualBox and I recently install VirtualBox 6.0.4 version with Win 7 OS as my guest machine, with my Win 7 pro host machine. As I did some searches before, I of course did follow all of the usual common recommandations about:(i) ""Setting>General>Advanced>Bidirectional"" stuff, as well as (ii) I did install the ""Guest Additions"" with the Devices recommanded procedure. Now, I can copy/paste text (ex. https sites adresses) both ways. I can also drag n drop pdf, zip files/docs (like the one attached hereto) from host to guest machine. Now, the only thing missing, is drag n drop from guest to host!! I attached the log files of both host and guest, as per recommandations of your collegue in previous ""Investigating drag and drop (DnD) problems"" (https://www.virtualbox.org/wiki/DnDDebug). Thanks for any kind of help from anybody."	TrueGeek
17717	DNS resolver does not work	VirtualBox 5.2.10	2018-04-28T20:27:43Z	2018-04-30T14:56:28Z	2018-04-30T14:56:28Z	"Adapter in NAT mode, network ""192.168.100/24"".

Guest network adapter is called enp0s3, `ip addr` shows the interface is up with ""inet 192.168.100.15/25"".

`ip route` shows ""default via 192.168.100.2 dev enp0s3"".


Now, on the host-side the default DNS is 192.168.1.1.
The guest can ping this IP, but according to the [https://www.virtualbox.org/manual/ch09.html#changenat manual/ch09.html#changenat] the name server should be available at 192.168.100.3.

In the guest: `drill virtualbox.org @192.168.100.3` fails with ""Error: error sending query: Could not send or receive, because of network error"".
`drill virtualbox.org @192.168.1.1` (""directly"" through the DNS in the host's network) works.

I can however ping 192.168.100.3. I can also ping .2 and .4 successfully."	xnoreq
8144	Dock does not show up anymore after switching between applications	VirtualBox 4.0.2	2011-01-21T16:51:00Z	2011-01-21T16:51:00Z	2011-01-21T16:51:00Z	"Steps to reproduce:
 * Enable the option ""show dock and menu bar in full screen mode automatically""
 * Switch VM to full screen mode
 * When I move the mouse to the top border, the menu bar shows up. When I move mouse to the left border, the dock shows up. (I have my dock configured to the left side of the screen.) This is the expected behavior.
 * I click on the icon of some other application in the dock. The windows of this application show up.
 * I click on the icon of the VM in the dock or (makes no difference) click in the VM desktop in the background. The windows of the other application and the dock disappear.
 * When I move the mouse now to the left border, nothing happens. The dock does not show up anymore. However the menu bar on the top border still shows up if I move the mouse there.
 
Hiding the VM and the reentering the VM does not change anything, the dock still does not work anymore. What helps is switching off and then on again the full screen mode. Then the dock works again, until the next time."	cmr
7779	Dock issue causing log pollution when using Spaces	VirtualBox 3.2.10	2010-11-30T09:54:01Z	2014-12-12T08:49:00Z	2014-12-12T08:49:00Z	"An issue exists in VirtualBox's handling of the Mac GUI that causes a huge numbers of kCGErrorIllegalArgument errors to be logged by the Mac OS X Dock each time one changes Spaces. This happens regardless of whether I set the VM Dock icon to reflect the VM screen or not, whether I'm in seamless/auto-resize/fullscreen mode or not.

Here's what I copied from system.log after going back and forth twice (4 Space jumps):
Nov 30 10:39:14 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:14 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:14 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:14 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:14 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:14 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:14 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:14 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:14 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:14 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:14 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:14 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:14 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:14 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:14 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:14 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:14 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:14 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:14 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:14 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:14 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:14 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:14 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:14 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:14 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:14 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:14 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:14 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:14 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:14 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:14 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:14 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:14 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:14 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:14 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:14 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:14 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:14 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:14 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:14 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:14 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:14 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:14 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:14 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:14 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:14 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:14 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:14 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:18 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:18 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:18 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:18 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:18 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:18 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:18 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:18 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:18 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:18 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:18 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:18 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:18 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:18 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:18 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:18 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:18 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:18 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:18 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:18 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:18 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:18 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:18 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:18 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:18 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:18 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:18 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:18 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:18 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:18 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:18 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:18 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:18 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:18 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:18 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:18 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:18 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:18 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:18 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:18 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:18 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:18 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:19 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:19 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:19 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:19 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:19 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:19 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:19 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:19 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:19 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:19 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:19 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:19 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:19 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:19 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:19 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:19 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:19 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:19 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:19 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:19 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:19 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:19 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:19 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:19 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:19 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:19 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:19 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:19 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:19 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:19 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:26 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:26 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:26 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:26 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:26 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:26 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:26 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:26 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:26 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:26 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:26 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:26 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:26 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:26 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:26 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:26 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:26 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:26 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:26 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:26 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:26 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:26 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:26 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:26 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:26 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:26 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:26 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:26 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:26 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:26 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:27 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:27 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:27 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:27 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:27 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:27 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:27 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:27 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:27 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:27 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:27 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:27 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:27 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:27 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:27 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:27 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:27 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:27 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:27 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:27 portia Dock[217]: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
Nov 30 10:39:27 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:27 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 1: [nan 0.000 0.000 nan]
Nov 30 10:39:27 portia com.apple.Dock.agent[217]: Tue Nov 30 10:39:27 portia.local Dock[217] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]"	RJVB
16638	Don't import appliances if there's not enough space on disk	VirtualBox 5.1.18	2017-04-05T18:50:26Z	2017-04-06T10:26:05Z	2017-04-06T10:26:05Z	"When importing appliances, it is common that the appliance file is smaller than the actual guest disk size.
Given that, if you are importing an appliance and you don't know the guest disk size, you'll get an error after the host disk is full.
Some import operations may take up to a hour, or more, so if you get the error after the import cannot continue, this is a little frustating to see the time you could save.

E.g.: I have a 20GB appliance the allocates more than 100GB. I was trying to import it on a disk with 80GB free. After 40min importing, I got the allocation error.

So, my suggestion is to show the final size for allocated space in the import dialog, or maybe even check the drive that the user is placing the VM disk and give a message like 'You don't have enough space to import that machine here', or something like that."	tgarcia
15168	DOS batch file crashes on run attempt (Command Prompt Only) w98	VirtualBox 5.0.14	2016-02-22T22:17:09Z	2016-02-22T22:17:09Z	2016-02-22T22:17:09Z	"I can successfully boot to Windows 98 or DOS but cannot get a DOS application to run; which is the goal of virtualizing this system.

1) Start Windows 98 VPC
2) Boots to Microsoft Windows 98 Startup Menu
3) (Select) 5. Command prompt only (Enter)
4) C:\>

SO FAR, ALL IS WELL...
5) Type Start (start.bat) and Enter
c:\>start (enter)
6) Crash!

"	Big B Creations
17890	Double Clicking or Open of .vbox File or Alias Error	VirtualBox 5.2.16	2018-07-24T18:23:08Z	2018-07-29T07:50:16Z	2018-07-29T07:50:16Z	"Double Clicking or Open of .vbox File or Alias produces the error:
""Failed to open virtual machine located in /Users/mike/VirtualBox VMs/Windows 10/Windows 10.vbox.

Trying to open a VM config '/Users/mike/VirtualBox VMs/Windows 10/Windows 10.vbox' which has the same UUID as an existing virtual machine.

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}
Callee: IVirtualBox {9570b9d5-f1a1-448a-10c5-e12f5285adad}""

Have changed the UUID withe command line "" /Applications/VirtualBox.app/Contents/MacOS/VBoxManage internalcommands sethduuid '/Users/mike/VirtualBox VMs/Widows 10/Windows 10.vdi'"" but get the same error.
"	McTTRS
17778	Double cursor on Mac OS host with unscaled HiDPI / W10 Guest with 200% scale	VirtualBox 5.2.12	2018-05-20T22:07:20Z	2019-02-26T11:24:24Z	2019-02-26T11:24:24Z	"Mac OS host (MacBook retina) with unscaled HiDPI enabled, 3d acceleration disabled (otherwise bug #17369 resurfaces). W10 Guest with 200% DPI scale (to compensate for the smaller fonts etc - is there a different way in W10 to do this?). VB Version 5.2.12 r122591 (Qt5.6.3), matching guest additions version installed. Result - double two cursors, host and guest, with guest cursor ""chasing"" host cursor. "	plexus
14155	Double-click-hold doesn't work	VirtualBox 4.3.28	2015-05-27T09:23:52Z	2016-05-06T18:33:33Z	2016-05-06T18:33:33Z	"I had VBox 4.3.24 and updated to 4.3.28. Since then, holding the mouse button on a double-click doesn't work on my Windows guests. This method of text selection is available on several applications (like Notepad++ and most IDEs) to extend the selection on a word-by-word basis.

This doesn't seem to be a Guest Additions problem since I tried another VM with an older version of Guest Additions and I had the same problem.
"	Constantine Dokolas
14711	Doubleclicking text and dragging no longer works.	VirtualBox 4.3.30	2015-10-17T13:08:54Z	2016-03-10T17:06:31Z	2016-03-10T17:06:31Z	"In a Win XP guest, I can no longer do whole-word text selection by doubleclicking and dragging. This normally lets you select chunks of text in whole words, and is standard across the windows GUI.

I have just upgraded from 4.3.20 to 4.3.30 r101610.

Following the installation of 4.3.30, this no longer works. Doubleclicking text selects a whole word, but you cannot extend it by dragging. The drag does nothing. I don't know whether this is a problem in VBoxSvc, or VBoxAdditions, or was caused by a change in how mouse input is handled in the host code. 

Unfortunately this is a real productivity killer for me.

If anyone can reproduce this bug, or can't reproduce it, I would be very grateful if you could add your findings to this ticket. Thank you.

"	dan.pope@…
18096	Download froze	VirtualBox 5.2.20	2018-11-01T21:28:54Z	2018-11-03T21:10:41Z	2018-11-03T21:10:41Z	Im having trouble, Ive gone through most of the steps for downloading kali Linux on virtul box, Ive used kali before, just not virtualbox. I go thorugh lots of the steps, set the hostname, domainname, all of that, the timezone, stuff like that. But, then I it goes to 'Install the system'. And then the screen freezes. Under the download progress bar it says 'Installed libeatmydata1 (amd64)' And the whole screen just freezes	2skywalkers
19098	DR-DOS/Caldera-OpenDOS-7.01 floppy images not recognized	VirtualBox 6.0.14	2019-11-20T12:58:57Z	2019-11-20T12:58:57Z	2019-11-20T12:58:57Z	"Trying to install DR-DOS 7/Caldera OpenDOS 7 fails because we cannot 
recognize the floppy images:

if you grab them from:

[https://winworldpc.com/product/dr-dos/7x][[BR]]

We fail with the following error during the attempt to
boot from the floppy initally:

{{{
Failed to open the disk image file /home/sw/Caldera-OpenDOS-7.01/Full-1440/DISK01.IMG.
 
GUI-error:
 
Could not get the storage format of the medium '/home/sw/Caldera-OpenDOS-7.01/Full-1440/DISK01.IMG' (VERR_NOT_SUPPORTED).
 
Result Code: VBOX_E_IPRT_ERROR (0x80BB0005)
Component: MediumWrap
Interface: IMedium {ad47ad09-787b-44ab-b343-a082a3f2dfb1}
Callee: IVirtualBox {d0a0163f-e254-4e5b-a1f2-011cf991c38d}
Callee RC: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)
 
Logfile: VBoxSVC.log
 
09:00:56.107381 nspr-9   ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={ad47ad09-787b-44ab-b343-a082a3f2dfb1} aComponent={MediumWrap} aText={Could not get the storage format of the medium '/home/sw/Caldera-OpenDOS-7.01/Full-1440/DISK01.IMG' (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=-37
}}}

We get the following information for the floppy images:
{{{
$ pwd
/home/sw/Caldera-OpenDOS-7.01/Full-1440
VBox/6.0 fbatschu@lserver Full-1440 $ file *
DISK01.IMG: DOS/MBR boot sector, code offset 0x56+2, OEM-ID ""OPENDOS7"", root entries 224, sectors 2880 (volumes <=32 MB), sectors/FAT 9, sectors/track 18, serial number 0x18e44553, label: ""DISK_01    "", FAT (12 bit), followed by FAT
DISK02.IMG: DOS/MBR boot sector, code offset 0x56+2, OEM-ID ""OPENDOS7"", root entries 224, sectors 2880 (volumes <=32 MB), sectors/FAT 9, sectors/track 18, serial number 0x18e50c23, unlabeled, FAT (12 bit), followed by FAT
DISK03.IMG: DOS/MBR boot sector, code offset 0x56+2, OEM-ID ""OPENDOS7"", root entries 224, sectors 2880 (volumes <=32 MB), sectors/FAT 9, sectors/track 18, serial number 0x18e50e5d, unlabeled, FAT (12 bit), followed by FAT
DISK04.IMG: DOS/MBR boot sector, code offset 0x56+2, OEM-ID ""OPENDOS7"", root entries 224, sectors 2880 (volumes <=32 MB), sectors/FAT 9, sectors/track 18, serial number 0x18e51139, unlabeled, FAT (12 bit), followed by FAT
DISK05.IMG: DOS/MBR boot sector, code offset 0x56+2, OEM-ID ""OPENDOS7"", root entries 224, sectors 2880 (volumes <=32 MB), sectors/FAT 9, sectors/track 18, serial number 0x18e51457, unlabeled, FAT (12 bit), followed by FAT
}}}

interestingly, grabbing the floppy images for PC-DOS 2000
and do an instalation with them, works fine, those images
from:

[https://winworldpc.com/product/pc-dos/2000][[BR]]

those working images look like this:
{{{
/home/sw/isos/IBM-PC-DOS-2000$ file disk*
disk01.img: DOS/MBR boot sector, code offset 0x3c+2, OEM-ID ""IBM  7.0"", root entries 224, sectors 2880 (volumes <=32 MB), sectors/FAT 9, sectors/track 18, serial number 0x226f11d4, label: ""DISK      1"", FAT (12 bit), followed by FAT
disk02.img: DOS/MBR boot sector, code offset 0x3c+2, OEM-ID ""IBM  7.0"", root entries 224, sectors 2880 (volumes <=32 MB), sectors/FAT 9, sectors/track 18, serial number 0x1e3d10db, label: ""DISK      2"", FAT (12 bit), followed by FAT
disk03.img: DOS/MBR boot sector, code offset 0x3c+2, OEM-ID ""IBM  7.0"", root entries 224, sectors 2880 (volumes <=32 MB), sectors/FAT 9, sectors/track 18, serial number 0xb5910dd, label: ""DISK      3"", FAT (12 bit), followed by FAT
disk04.img: DOS/MBR boot sector, code offset 0x3c+2, OEM-ID ""IBM  7.0"", root entries 224, sectors 2880 (volumes <=32 MB), sectors/FAT 9, sectors/track 18, serial number 0x395a10de, label: ""DISK      4"", FAT (12 bit), followed by FAT
disk05.img: DOS/MBR boot sector, code offset 0x3c+2, OEM-ID ""IBM  7.0"", root entries 224, sectors 2880 (volumes <=32 MB), sectors/FAT 9, sectors/track 18, serial number 0x332010e0, label: ""DISK      5"", FAT (12 bit), followed by FAT
disk06.img: DOS/MBR boot sector, code offset 0x3c+2, OEM-ID ""IBM  7.0"", root entries 224, sectors 2880 (volumes <=32 MB), sectors/FAT 9, sectors/track 18, serial number 0x314f10e2, label: ""DISK      6"", FAT (12 bit), followed by FAT

}}}"	Frank Batschulat (Oracle)
14492	drag and drop fails on win 10 host 64bit	VirtualBox 5.0.2	2015-08-25T04:39:12Z	2015-10-09T14:47:55Z	2015-10-09T14:47:55Z	"win 10 64bit host
win xp pro sp3 guest
vb 5.0.2 latest stable release
guest add installed

drag and drop not working...
tried bi directional
also host to guest and guest to host
not working in any case

what have i to set..??

thxs in advance!

cheers!!"	giusi
16943	Drag and Drop Feature not working	VirtualBox 5.1.24	2017-07-25T07:14:16Z	2018-08-28T12:19:32Z	2018-08-28T12:19:32Z	"Drag and Drop setting is already Bidirectional.. but this feature is not functioning properly.

Restart will solve it temporarily then again the issue will come.

Similar ticket has been already issued but for older version ""5.1.22"". 
I'm using latest version ""5.1.24"" and tested on Win 2016 & win10. "	alman7005
10007	Drag and Drop ISO on to CD/DVD Icon	VirtualBox 4.1.6	2011-12-07T18:46:51Z	2011-12-07T18:46:51Z	2011-12-07T18:46:51Z	You should be able to drag/drop an .ISO file on to the icon in the statusbar.  I couldn't do that with the release as of today Dec 7, 2011 Using Win7 x64.	dfatvb
15468	drag and drop not bidirectional	VirtualBox 5.0.20	2016-05-31T16:24:29Z	2016-05-31T16:24:29Z	2016-05-31T16:24:29Z	"Hi, I have a Windows 10 Host, with a Ubuntu 15.10 guest, Virtual Box and Guest addition latest version. When I drag and drop files from guest to host no problem, when I do it from host to guest my files go only in /tmp/VirtualBox dropped files and not where I dropped them.
I attached log files, hope it helps.
Thanks"	rok
15413	Drag and drop only working to host not the other way	VirtualBox 5.0.20	2016-05-13T18:39:12Z	2016-05-13T18:46:37Z	2016-05-13T18:46:37Z	"My windows 10 guest does not accept files vie drag and drop only the host does which is also a windows 10 machine.
hope somebody can help me Thx.
log files are attached"	DerProGamer2000
8179	Dreamweaver ftp errors because of uppercase directories on mapped drives	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
16844	DRIVER_POWER_STATE_FAILURE VirtualBox 5.1.22	VirtualBox 5.1.22	2017-06-19T01:54:53Z	2021-05-01T14:19:17Z	2021-05-01T14:19:17Z	"I started receiving a lot of BSODS on my PC after windows clean install. All of them were related to DRIVER_POWER_STATE_FAILURE while PC going to sleep.

I realised then it's connected to VB because it happened only after I used VB. I checked it, started PC, started VB, finished VB, tries to restart PC ==> bsod. I googled for VB + DRIVER_POWER_STATE_FAILURE BSOD and found out that it's quite a common issue.

I attach my dump files. I thinks it can be connected either with asus usb drivers or rapid mode by samsung (but I have another PC with samsung and VB and there are no issued there).

My host is windows 10 pro x64, my guests are windows 7 x86\64, windows 10 pro x86\64.

I would appreciate any help."	toouur
20779	drm:vmw_host_printf [vmwgfx]] *ERROR* in version 6.1.30 & 6.1.32	VirtualBox 6.1.32	2022-01-20T05:44:09Z	2022-01-20T08:26:05Z	2022-01-20T08:26:05Z	"CentOS 9 Stream VM provisioned with *.vdi|*.vhd|*.vmdk disk and dynamically allocated capacity of 100GB configurations gives the 'drm:vmw_host_printf [vmwgfx]] *ERROR* Failed to send host log message' after OS post installation boot. 

Included are screenshots of the error, device configurations and the host Windows OS configurations occurring on two workstations. A provisioned VM with a *.vdi|*.vhd|*.vmdk disk capacity of 45.6GB dynamically allocated encountered no issues with the post-install boot with the same CentOS 9 Stream OS.

Supporting images are attached. Please let me know if additional technical information about the issue is needed."	BrownFoxx
17550	drop when creating snapshot	VirtualBox 5.2.6	2018-02-18T21:28:33Z	2018-02-27T23:20:27Z	2018-02-27T23:20:27Z	"This bug has already f**** !!!

System: ubuntu 16.04 (latest)
Virtualbox: 5.2.6 (off repository)
Guest System: Windows 8.1 latest
Guest Additions: 5.2.6

Kernel info: Linux FirstEmpty 4.13.0-32-generic #35~16.04.1-Ubuntu SMP Thu Jan 25 10:13:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux


At an uptime of more than 40 minutes and the creation of a snapshot (instead of shutting down) - the virtual machine drops!

01:49:28.306340 GIM: HyperV: Resetting MMIO2 regions and MSRs
01:49:28.307849 Changing the VM state from 'DESTROYING' to 'TERMINATED'
01:49:28.310970 Console: Machine state changed to 'Saved'
01:49:59.308109 AssertLogRel /home/vbox/vbox-5.2.6/src/VBox/VMM/VMMR3/VM.cpp(2592) void vmR3DestroyUVM(PUVM, uint32_t): RT_SUCCESS_NP(rc2)
01:50:08.149769 iCpu=0 rc=VERR_TIMEOUT

00:43:37.423573 GIM: HyperV: Resetting MMIO2 regions and MSRs
00:43:37.426432 Changing the VM state from 'DESTROYING' to 'TERMINATED'
00:43:37.433702 Console: Machine state changed to 'Saved'
00:44:08.426807 AssertLogRel /home/vbox/vbox-5.2.6/src/VBox/VMM/VMMR3/VM.cpp(2592) void vmR3DestroyUVM(PUVM, uint32_t): RT_SUCCESS_NP(rc2)
00:44:33.446952 iCpu=0 rc=VERR_TIMEOUT
00:44:33.998557 GUI: Passing request to close Runtime UI from machine-logic to UI session."	Ilja
6271	During Clonezilla Live CD Process, Text Only display shifts down so bottom lines appear off screen	VirtualBox 3.1.4	2010-02-22T21:41:34Z	2011-03-25T01:04:52Z	2011-03-25T01:04:52Z	During the text only live CD process (using Clonezilla Alternative, Ubuntu-based), Virtualbox incorrectly slowly shifts the display 'down' so that the top rows are repeated and the bottom rows are not visible.	khamer
20672	During the execution of the docker pull command the VM dies	VirtualBox 6.1.28	2021-11-17T15:23:26Z	2021-11-18T19:23:27Z	2021-11-18T19:23:27Z	"I have a VM installed with the operating system Ubuntu 20.04 LTS .
Running the command docker pull from the docker registry of AWS the virtual machine dies "	GriGiu
17077	DVD in OVF does not appear in imported VM	VirtualBox 5.1.26	2017-09-12T19:22:23Z	2017-09-12T19:22:23Z	2017-09-12T19:22:23Z	"Linux Virtual Box Version 5.1.26 r117224 (Qt5.5.1)

A DVD that is specified in the OVF file and shows on the ""import"" screen is not present after the OVF file is imported."	gerardw
18647	E_FAIL (0x80004005)	VirtualBox 6.0.8	2019-05-15T18:28:56Z	2019-05-15T18:28:56Z	2019-05-15T18:28:56Z	"https://youtu.be/W1SR-SZixI8

Графический интерфейс VirtualBox
Версия 6.0.8 r130520 (Qt5.6.2)
Copyright © 2019 Oracle Corporation and/or its affiliates. All rights reserved.


My email: alex@finogenov.ru"	Alexander
15236	E_FAIL (0x80004005)  MachineWrap IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}	VirtualBox 5.0.16	2016-03-11T13:49:55Z	2016-03-11T13:49:55Z	2016-03-11T13:49:55Z	"I get this error when starting any virtual box:
E_FAIL (0x80004005)  MachineWrap IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}

i run on windows 8.1 but dunno why it happens. 

greets"	Drake
20516	E_FAIL (0x80004005) after host PC hibernation	VirtualBox 6.1.26	2021-08-20T18:10:26Z	2021-08-23T18:40:35Z	2021-08-23T18:40:35Z	"After I woke up the host PC from hibernation, when I try to start a virtual machine I get the following error:

{{{
Failed to open a session for the virtual machine Windows_10_Pro_LV_2018_SP1.
The VM session was aborted.
Result Code: E_FAIL (0x80004005)
Component: SessionMachine
Interface: ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}
}}}

The error occurs before the VirtualBox logo appears in the launch screen of the virtual machine.[[BR]]
The error does not happen if the host PC is shutdown and restarted.[[BR]]
The error has occurred after updating virtualbox to 6.1.26.

VirtualBox Graphical User Interface[[BR]]
Version 6.1.26 r145957 (Qt5.6.2)[[BR]]
Host OS: Windows 7 Pro 64bit[[BR]]
Guest OS: Windows 10 Pro 64bit or Windows 7 Pro 64bit

As highlighted in the forum post [https://forums.virtualbox.org/viewtopic.php?f=6&t=103708], the problem is solved by completely disabling the audio of the virtual machine.

The issue is repeatable, by re-enabling the audio the error appears the same.

The VBox.log file is attached for checking.
"	Asper
20540	E_FAIL (0x80004005) after Launch	VirtualBox 6.1.26	2021-09-08T07:35:16Z	2021-09-16T09:34:36Z	2021-09-16T09:34:36Z	"current status:

Version 6.1.26 r145957 (Qt5.6.2)

Host OS: Windows 10 64bit

Guest OS: Red Hat(64-bit)

The error occur just when i launch the guestOS before the logo appear.

The VM session was aborted.
Result Code: E_FAIL (0x80004005)

Component: SessionMachine

Interface: ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}

i have found out a similar case on Ticket #20516 which have proved to be solved out.but it didn't work in my case. 

log file is attached below 

"	kirSin
20539	E_FAIL (0x80004005) after Launch	VirtualBox 6.1.26	2021-09-08T07:35:16Z	2021-09-08T07:35:16Z	2021-09-08T07:35:16Z	"current status:

Version 6.1.26 r145957 (Qt5.6.2)

Host OS: Windows 10 64bit

Guest OS: Red Hat(64-bit)

The error occur just when i launch the guestOS before the logo appear.

The VM session was aborted.
Result Code: E_FAIL (0x80004005)

Component: SessionMachine

Interface: ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}

i have found out a similar case on Ticket #20516 which have proved to be solved out.but it didn't work in my case. 

log file is attached below 

"	kirSin
14803	E_FAIL (0x80004005) Critical Error on Windows 10 (Build 1240)	VirtualBox 5.0.10	2015-11-11T10:36:24Z	2015-11-11T10:36:24Z	2015-11-11T10:36:24Z	"I can't run VM session with Comodo Internet Security installed on my PC. (CIS 8.2.0.4703). 


{{{
The virtual machine 'name' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005). More details may be available in 'C:\Users\User\VirtualBox VMs\name\Logs\VBoxHardening.log'.


Result Code: 
E_FAIL (0x80004005)
Component: 
MachineWrap
Interface: 
IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}

}}}
"	netak
17510	E_FAIL (0x80004005) err	VirtualBox 5.2.6	2018-01-30T05:51:52Z	2018-01-30T08:21:31Z	2018-01-30T08:21:31Z	"가상 머신 windowspe의 세션을 열 수 없습니다.

The virtual machine 'windowspe' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005).  More details may be available in 'E:\windowspe\Logs\VBoxHardening.log'.

결과 코드: E_FAIL (0x80004005)
구성 요소: MachineWrap
인터페이스: IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}

"	wooqwer
14566	E_FAIL (0x80004005) MediumWrap.cpp[2245]	VirtualBox 5.0.4	2015-09-10T08:02:14Z	2015-09-11T07:59:48Z	2015-09-11T07:59:48Z	"Ever since the upgrade to VirtualBox 5 I'm unable to add/modify storage controllers or optical drivers.
Either VirtualBox crashes or quits silently. Error is still present even with 5.0.4.2546."	wpa1160
17145	E_FAIL (0x80004005) SessionMachine	VirtualBox 5.1.28	2017-10-08T13:49:21Z	2017-10-08T13:53:54Z	2017-10-08T13:53:54Z	"Не удалось открыть сессию для виртуальной машины BOT.

The VM session was aborted.

Код ошибки: E_FAIL (0x80004005)
Компонент: SessionMachine
Интерфейс: ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}

"	free0n
19705	E_FAIL (0x80004005)-IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}	VirtualBox 6.1.10	2020-07-07T14:20:55Z	2020-07-07T14:23:19Z	2020-07-07T14:23:19Z	"Dear all,

Host : Windows 7 Enterprise 64bit,
Laptop Toshiba Satellite L645
Virtual box Version 6.1.10 r138449 (Qt5.6.2)
Avast AV already uninstall
Firewall already setup to allow this virtualbox
VT-X already disable (when the VT-X was enabled,that still error found on virtualbox)


when I was going running  the Windows 7 or Linux , error


Result Code: 
E_FAIL (0x80004005)
Component: 
MachineWrap
Interface: 
IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}.



I was forgot what is old version of Virtual box that installed before.
and with old version, virtual box is normal and not found error


Please fix it and help me....Thanks

"	n3wkid2019
18416	Each time VirtualBox starts VM from the saved state it hangs up with error E_FAIL (0x80004005)	VirtualBox 6.0.4	2019-02-06T13:26:41Z	2019-02-11T08:05:44Z	2019-02-11T08:05:44Z	"This problem occurs each time I start virtual machine from the saved state.

This problem occurs on VirtualBoX versions 6.03, 6.04 and 6.05 r128628

This problem occurs on any kind of virtual machines (Windows XP, Windows 7, Ubuntu etc)
"	gastor
20807	echec de l'ouverture de session pour la machine virtuelle XP	VirtualBox 6.1.32	2022-02-03T12:54:58Z	2022-02-03T19:58:46Z	2022-02-03T19:58:46Z	"bonjour,
je rencontre un pb à l'ouverture de session suite à la mise à jour de Virtual box 6.1.32

comment corriger cela, svp merci?

""Échec de l'ouverture de session pour la machine virtuelle XP.

Not in a hypervisor partition (HVP=0) (VERR_NEM_NOT_AVAILABLE).

VT-x is disabled in the BIOS for all CPU modes (VERR_VMX_MSR_ALL_VMX_DISABLED).

Code d'erreur : E_FAIL (0x80004005)
Composant : ConsoleWrap
Interface : IConsole {872da645-4a9b-1727-bee2-5585105b9eed}""

"	mas421
17712	ed stat  Guest VM with OS/2 does not resume from saved state	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
21470	Emulated TPM does not include Endorsement Key (EK) certificate	VirtualBox-7.0.6	2023-02-07T21:37:06Z	2023-02-07T21:37:06Z	2023-02-07T21:37:06Z	"The command ""sudo tpm2_nvread 0x1c00002 > ekcert.der"", installed with the tpm2-tools package on Linux, does not return an endorsement key (EK) certificate. On VMware Fusion's emulator, a self-signed dynamic certificate/key pair is dynamically created in the emulated TPM and the above command works fine."	NedRyerson
10383	Enable mouse integration to be disabled in the guest config	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
7018	Enable user to import custom icons with the file menu and/or automatically from a specified directory.	VirtualBox 3.2.4	2010-06-17T07:01:26Z	2016-01-20T14:52:30Z	2016-01-20T14:52:30Z	"'''Disclaimer: This ticket is about a customization feature only! '''

== General Statement ==

I want the user '''to be able to import custom virtual machine OS icons with a file menu''' and store its file location in a configuration file (or possibly the registry for Windows, if ''VirtualBox'' uses this for configuration), and/or '''I want ''!VirtualBox'' to automatically import icons from a specified directory''' that the user decides with a Preference setting, or by default, which would be ~/.!VirtualBox/icons/ (Linux) and ""%USERPROFILE%\My Documents\.!VirtualBox\icons\"" (Windows NT). If the default directory does not exist, and the preference defines that it must import from this directory, ''!VirtualBox'' should create this empty directory if given the proper file permissions, otherwise display it as a warning, not an error. Finally, if the file is imported from another location besides the directory for the custom icons, the selected file should be copied to that directory.

Once an icon has been imported, the user should be able to select it from a [http://en.wikipedia.org/wiki/Drop-down_list drop-down list] in `Settings > General`, and a text label should say the exact string before the list:
{{{
  Icon:
}}}

The other option to import icons from a directory (and all subdirectories for that matter) should be in `Settings > Advanced` and display:
{{{
  [C] Import icons automatically
  [ <Directory of icon list>  ▼ ]
}}}

 * [C] is a [http://en.wikipedia.org/wiki/Check_box check box]. When checked, icons are imported from the directory tree. Otherwise, no importing is done automatically.
 * The second line is an ASCII representation of a drop-down list (see above).
 * <Directory of icon list> shows a full path with the text cut off at a specific width (the width does not need to match the one represented in the above ASCII figure. Fit the width in the [http://en.wikipedia.org/wiki/Paned_window paned window] below the `Advanced` tab.)
----


First, I understand that the predefined icons serve a purpose. They are integrated because they have predefined settings for each new virtual machine that the user creates ^[citation needed]^. In this case, it only makes implementation more difficult if developers decide to completely remove the predefined ones that may contain suggested settings, which include memory, CPU, and peripheral settings ^[citation needed]^. But this is NOT any part of the issue. Instead, it is the '''''inability''''' to use other icons for a simple purpose such as customization and appearance.

Should users wish to replace the icon image with a more desirable, preferable or distinctive alternative, grant each user of !VirtualBox this ability.

The other small problem is choice between giving the user ability to import custom icons from a file menu or automatically from a directory. Importing from a directory seems easier for the developer and might be more preferable for users. A quick import from a file browser may actually be a effort worth doing, since the images will be copied to the defined icon folder anyway. 

To concur, the importance level of this issue I will weigh and should be weighed on user reviews, concern and critique, appropriately as to never exceed minor.

- Ticket reported by: Mr. R

,,Note: 
I respect all the work developers have contributed in the creation of VirtualBox. Feel free to remove any suggestions and ""shoulds"" from this ticket.,,"	Mr. R
21409	enabling capture with usbattach command always fails	VirtualBox-7.0.4	2023-01-13T21:17:22Z	2023-01-13T21:17:22Z	2023-01-13T21:17:22Z	"I was able to reproduce with both virtualbox 6.1.40-154048~Debian~bullseye and 7.0.4-154605~Debian~bullseye.

Host is mostly Debian bullseye with a Gnome from bookworm.
Guest is Windows 7 Ultimate with latest updates installed.

{{{
$ VBoxManage controlvm ""Win7 Ultimate Hermes"" usbattach 7d1e5806-5813-4320-b11f-809e116092c5 --capturefile ""usb_astrometa_20230103-1""
$ ls usb*
ls: impossible d'accéder à 'usb*': Aucun fichier ou dossier de ce type
$ VBoxManage controlvm ""Win7 Ultimate Hermes"" usbdetach 7d1e5806-5813-4320-b11f-809e116092c5 --capturefile ""usb_astrometa_20230103-1""
VBoxManage: error: USB device with UUID {7d1e5806-5813-4320-b11f-809e116092c5} is not attached to this machine
VBoxManage: error: Details: code NS_ERROR_INVALID_ARG (0x80070057), component ConsoleWrap, interface IConsole, callee nsISupports
VBoxManage: error: Context: ""DetachUSBDevice(usbId.raw(), dev.asOutParam())"" at line 1451 of file VBoxManageControlVM.cpp

$ VBoxManage controlvm ""Win7 Ultimate Hermes"" usbattach 7d1e5806-5813-4320-b11f-809e116092c5 --capturefile ""usb_astrometa_20230103-1""
VBoxManage: error: Code NS_ERROR_FAILURE (0x80004005) - Operation failed (extended info not available)
VBoxManage: error: Context: ""AttachUSBDevice(usbId.raw(), captureFilename.raw())"" at line 1447 of file VBoxManageControlVM.cpp

}}}


VBox.log extract:
{{{
00:07:37.598240 PDMUsb: Failed to attach USB device 'USBProxy' instance 1 to hub 00007fccb84e93b0: VERR_NOT_FOUND
00:07:37.765443 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={6ac83d89-6ee7-4e33-8ae6-b257b2e81be8} aComponent={ConsoleWrap} aText={Failed to create a proxy device for the USB device. (Error: VERR_NOT_FOUND)}, preserve=false aResultDetail=-78
00:07:56.597244 ERROR [COM]: aRC=NS_ERROR_INVALID_ARG (0x80070057) aIID={6ac83d89-6ee7-4e33-8ae6-b257b2e81be8} aComponent={ConsoleWrap} aText={USB device with UUID {7d1e5806-5813-4320-b11f-809e116092c5} is not attached to this machine}, preserve=false aResultDetail=0
00:08:05.070747 PDMUsb: Failed to attach USB device 'USBProxy' instance 2 to hub 00007fccb84e93b0: VERR_NOT_FOUND
00:08:05.223122 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={6ac83d89-6ee7-4e33-8ae6-b257b2e81be8} aComponent={ConsoleWrap} aText={Failed to create a proxy device for the USB device. (Error: VERR_NOT_FOUND)}, preserve=false aResultDetail=-78
}}}


This issue seems to have already been asked in the forum in November 2020 https://forums.virtualbox.org/viewtopic.php?f=7&t=100495

My ""VBoxManage list usbhost"":
{{{
Host USB Devices:

UUID:               d6e93f88-6381-4089-96f7-8abba8cd6718
VendorId:           0x17ef (17EF)
ProductId:          0x608d (608D)
Revision:           1.0 (0100)
Port:               1
USB version/speed:  2/Low
Manufacturer:       PixArt
Product:            Lenovo USB Optical Mouse
Address:            sysfs:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-8/1-8.2//device:/dev/vboxusb/001/007
Current State:      Busy

UUID:               025e451f-eb3f-4e61-a323-5e317182f509
VendorId:           0x17ef (17EF)
ProductId:          0x608c (608C)
Revision:           1.20 (0120)
Port:               0
USB version/speed:  2/Low
Manufacturer:       LiteOn
Product:            Lenovo Calliope USB Keyboard
Address:            sysfs:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-8/1-8.1//device:/dev/vboxusb/001/005
Current State:      Busy

UUID:               1fbaede8-53a9-4d9f-af86-a4708f66cc9b
VendorId:           0x174c (174C)
ProductId:          0x55aa (55AA)
Revision:           1.0 (0100)
Port:               3
USB version/speed:  3/Super
Manufacturer:       Ugreen
Product:            Ugreen Storage Device
SerialNumber:       021912063F24
Address:            sysfs:/sys/devices/pci0000:00/0000:00:14.0/usb2/2-4//device:/dev/vboxusb/002/012
Current State:      Busy

UUID:               d3504e3c-c92f-40fa-9107-b63aee699a85
VendorId:           0x174c (174C)
ProductId:          0x55aa (55AA)
Revision:           1.0 (0100)
Port:               2
USB version/speed:  3/Super
Manufacturer:       Ugreen
Product:            Ugreen Storage Device
SerialNumber:       022001030BFA
Address:            sysfs:/sys/devices/pci0000:00/0000:00:14.0/usb2/2-3//device:/dev/vboxusb/002/011
Current State:      Busy

UUID:               e04d293c-2d4a-4e0d-b32a-f297a68f75e4
VendorId:           0x10c4 (10C4)
ProductId:          0xea60 (EA60)
Revision:           1.0 (0100)
Port:               1
USB version/speed:  2/Full
Manufacturer:       Silicon Labs
Product:            CP2104 USB to UART Bridge Controller
SerialNumber:       00DB1A1E
Address:            sysfs:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5.2//device:/dev/vboxusb/001/013
Current State:      Busy

UUID:               699af1c0-be96-4f48-a254-a50b36888be9
VendorId:           0x0a12 (0A12)
ProductId:          0x0001 (0001)
Revision:           49.100 (49100)
Port:               0
USB version/speed:  2/Full
Manufacturer:       Cambridge Silicon Radio, Ltd
Product:            Bluetooth Dongle (HCI mode)
Address:            sysfs:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5.1//device:/dev/vboxusb/001/004
Current State:      Busy

UUID:               7d1e5806-5813-4320-b11f-809e116092c5
VendorId:           0x0781 (0781)
ProductId:          0x5581 (5581)
Revision:           1.0 (0100)
Port:               5
USB version/speed:  3/Super
Manufacturer:       SanDisk
Product:            Ultra
SerialNumber:       4C530001030927114111
Address:            sysfs:/sys/devices/pci0000:00/0000:00:14.0/usb2/2-6//device:/dev/vboxusb/002/013
Current State:      Available

}}}
"	Alban Browaeys
18893	Enhancement: CLI flag to sleep host for N seconds	VirtualBox 6.0.10	2019-09-02T16:20:25Z	2020-01-17T01:01:43Z	2020-01-17T01:01:43Z	"Some legacy operating systems such as OS/2 Warp require floppy diskettes to be inserted before being bootable, with corresponding delays for the data to load. Unfortunately, automation frameworks like Packer do not currently provide a way for the host to sleep during these data loads.

Fortunately, Packer does provide a ""vboxmanage"" section in its configuration, where subcommands like ""modifyvm"", ""storagectl"", etc. can be triggered. Could VBoxManage get a command line option to sleep for N seconds, so that automated VM builds can successfully boot these legacy operating system guests?

E.g., `VBoxManage sleep <seconds>` would suffice."	mcandre
15321	Enhancing vbox-img from VBoxManage	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
7345	Entering Fullscreen with Guest - Disrupts Synergy	VirtualBox 3.2.8	2010-08-18T09:40:41Z	2018-03-08T15:25:19Z	2018-03-08T15:25:19Z	"The cursor is lost, and also communication is disrupted between my Host and other PC's via Synergy when a GUEST is run in FullScreen Mode.

While running Synergy on a Host (Ubuntu 10.04 - 64Bit) everything works fine.  I can access guest systems, and move between my Host system and other systems via Synergy.  But when I enter FullScreen Mode, communication between the Host and other PC's is interrupted.  I have control of the guest system until the cursor hits the edge of the screen.  Then I lose the cursor and have to exit FullScreen Mode to regain control of any system.  

I'm running VBox 3.2.8. My host is Ubuntu 10.04 (64 Bit) with an Ubuntu 10.04 (32 Bit) and a WinXP Guest. I have an Ubuntu 10.04 sys to my left and a WinXP sys to my right. When I go Full Screen with a Guest System, it's like Synergy can no longer talk to the other remote systems. When my cursor hits the system edge, it disappears and will not return UNTIL I EXIT Full Screen mode on the Guest System. I need to be full screen in my Ubuntu Guest system 90% of the time, with Synergy still able to work on the Host.

Other users are reporting the same issue HERE -->  http://forums.virtualbox.org/viewtopic.php?f=7&t=33040

Thank you for your assistance!"	jdm
11296	entropy quality	VirtualBox 4.2.4	2012-12-16T17:16:55Z	2012-12-17T09:17:54Z	2012-12-17T09:17:54Z	"Many cryptographic operations depend on good entropy. Bad entropy results in weak keys and poor security.

There is no information about entropy quality available on virtualbox.org.

What sources of entropy are available to virtual machines? How good are those sources? Does the virtual CPU have an accurate TSC or does it provide entropy? Does the --synthcpu option change anything?

Does Virtual Box implement any measures to provide good entropy to virtual machines?

None of these questions is answered on virtualbox.org."	Tsso
21058	Erro ao inicializar maquina virtual	VirtualBox 6.1.36	2022-08-10T13:55:48Z	2022-08-10T13:55:48Z	2022-08-10T13:55:48Z	"Bom dia,

O seguinte erro aparece ao inicializar a maquina virtual.
Falha ao abrir uma sessão para a máquina virtual:
The virtual machine 'VIRT' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005)

Já fiz vários testes para sanar o erro, mas sem sucesso, incluindo:
Desinstalar e instalar novamente, atualizar para a ultima versão, desativar Hyper-V do Windows e entre outros básicos. O mais estranho que o erro começou ""do nada"". Podem me ajudar?
"	Gugu Aquino
20069	Error	VirtualBox 6.1.16	2020-11-26T12:27:18Z	2020-11-26T12:27:18Z	2020-11-26T12:27:18Z	"Hey, 
I have got problem with virtual box. It whount start or install system. Only system i can install is windows xp but its very, very slow. I have got Windows 10 Pro 2004."	Daniel_Mandinec
21419	"Error ""kmk: glslangValidator: Command not found""while building VirtualBox"	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
17865	Error (rc=-5640): More than one thread in process - Windows 10	VirtualBox 5.2.14	2018-07-12T18:24:26Z	2018-07-12T21:39:44Z	2018-07-12T21:39:44Z	"I've been using VirtualBox since last december, without problems. There are logs of normal use until last month, June.

After that, it started to give me the same error message for every VM I try to open:

Error (rc=-5640):
More than one thread in process
Error -5640 in supR3HardenedWinReSpawn! (enmWhat=1)


No big updates on my notebook since last month, maybe a Windows Update (my main suspect).

I'm attaching one of the logs of error, e another, old, from June, when Virtual Box was still working well.
"	MarcelloRothery
18003	Error -104 in supR3HardenedWinReSpawn	VirtualBox 5.2.18	2018-09-22T21:46:28Z	2018-09-22T21:57:30Z	2018-09-22T21:57:30Z	"VirtualBox fails when launching any VM. 
Tried reinstalls and also reverting to older 4.x versions and other suggestions. Always fails with the same error.

OS: windows 10
VB: 5.2.18 (also other 4.x versions)

"	vbfxuser
17856	Error -5640 in supR3HardenedWinReSpawn! (enmWhat=1) (Hardening Issue while starting an image)	VirtualBox 5.2.6	2018-07-04T12:43:41Z	2018-07-04T18:34:01Z	2018-07-04T18:34:01Z	"I am running Oracle Virtual Box 5.2.6 r120293 (Qt5.6.2) and I am trying to launch CentOS 7 gust image and see the error ""Error (rc=-5640)""

I am on Windows 10 [1709] 64-bit OS and x64-bit Processor.

I have tried most of the options that are mentioned in the link:

https://forums.virtualbox.org/viewtopic.php?f=25&t=82106

Can anyone help us if this is a bug or something that is coming from my environment.

I have attached the VBoXHardening.log"	SarmaK
13598	Error al iniciar máquina	VirtualBox 4.3.18	2014-11-07T02:49:12Z	2014-11-10T14:16:25Z	2014-11-10T14:16:25Z	"Fallo al abrir una sesión para la máquina virtual PC_WindowsXPSP3.

The virtual machine 'PC_WindowsXPSP3' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'N:\EquiposVM\PC_WindowsXPSP3\Logs\VBoxStartup.log'.

Código Resultado: E_FAIL (0x80004005)
Componente: Machine
Interfaz: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}"	seterymco
17559	Error al mostrar informacion	VirtualBox 5.2.6	2018-02-22T17:23:40Z	2018-02-28T06:42:10Z	2018-02-28T06:42:10Z	al mostrar la informacion si el puntero esta en el anfitrion o en la MV sale codigo html	FalconXCI
19850	Error Cloudera Virtual Box	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
13710	Error code 5 with install windows 7	VirtualBox 4.3.20	2014-12-23T07:54:44Z	2014-12-23T07:54:44Z	2014-12-23T07:54:44Z	"Hi,

When I want install Windows 7 on VM, I have ""code error 5"".

This probleme come from the BIOS (old BIOS make this with Windows 7 CD bootable).
It's possible to update BIOS of VM in Virtual Box? 
Or propose a choice

Best regards"	Olivier69
17265	Error fetching directory count. (TIFFRewriteDirectory)	VirtualBox 5.1.30	2017-11-11T11:09:15Z	2017-11-11T11:09:15Z	2017-11-11T11:09:15Z	"Guest machine vagrant/xenial64. Latest box update is installed. Host machine is macOS Sierra 10.12.6.

GraphicsMagick 1.3.25 2016-09-05 Q16 http://www.GraphicsMagick.org/
Copyright (C) 2002-2016 GraphicsMagick Group.
Additional copyrights and licenses apply to this software.
See http://www.GraphicsMagick.org/www/Copyright.html for details.

Feature Support:
  Native Thread Safe       yes
  Large Files (> 32 bit)   yes
  Large Memory (> 32 bit)  yes
  BZIP                     yes
  DPS                      no
  FlashPix                 no
  FreeType                 yes
  Ghostscript (Library)    no
  JBIG                     yes
  JPEG-2000                no
  JPEG                     yes
  Little CMS               yes
  Loadable Modules         no
  OpenMP                   yes (201307)
  PNG                      yes
  TIFF                     yes
  TRIO                     no
  UMEM                     no
  WebP                     yes
  WMF                      yes
  X11                      yes
  XML                      yes
  ZLIB                     yes

Host type: x86_64-pc-linux-gnu

-----

apt-cache show libtiff5
Package: libtiff5
Architecture: amd64
Version: 4.0.6-1ubuntu0.2

----

The is appear when I run the following command which writes tiff file to a shared folder. Example command:
 gm convert -type Bilevel -density 300 -colorspace Gray -colors 2 /app/uploads/2nd_phase_10_1510393003.pdf -compress group4 /app/uploads/2nd_phase_10_1510393003.tiff
The folder /app is shared folder.
When I change the command and writing to folder than shared one, then everything is  OK"	varp
20398	Error Guru Meditation	VirtualBox 6.1.22	2021-06-14T09:48:51Z	2021-06-14T09:48:51Z	2021-06-14T09:48:51Z	Al intentar cargar el sistema operativo de una nueva máquina virtual me ha dado el mensaje Guru Meditation y no puedo instalarla	Alfonsodearagon
18928	Error Importing an Appliance (ODI)	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
17797	Error in ipl windows xp	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
16147	Error in supR3HardenedWinReSpawn (System32\ntdll.dll rc=-626)	VirtualBox 5.1.8	2016-11-04T10:49:21Z	2016-11-04T12:47:38Z	2016-11-04T12:47:38Z	"VirtualBox on my machine is failing to start any virtual machine.  I'm sure the log can explain what's going on better than I can, so I've attached the log.

Thanks for any help you can provide,
skippythegoat"	skippythegoat
14435	ERROR In SupR3HardenedWinResSpawn	VirtualBox 5.0.0	2015-08-13T13:52:28Z	2015-11-21T22:09:45Z	2015-11-21T22:09:45Z	"OS Win7 x32 Ultimate.
Bitdefender Antivirus Free Edition 1.0.21.1099.
VirtualBox - 5.0.0-101573 (similar errors appeared with version 4.3.14)
When I run the guest appears this window:
""ERROR In SupR3HardenedWinResSpawn""
After removal of the antivirus VBox starts as expected."	digitadropper@…
14978	Error In supR3HardNtChildWaitFor	VirtualBox 5.0.12	2015-12-26T14:09:49Z	2017-12-22T06:27:04Z	2017-12-22T06:27:04Z	"Hello,
I get this error on startup since 5.0.8 (also on .10 and .12).
Key Host Info:
- Lenovo x250 16GB RAM, 512 SSD
- Host win7 (latest patches some win10 upgrade stuff suppressed)
- guests: debian (but probably irrelevant)
- avira antivir antivirus
- comodo firewall

When I start vbox, after a while I get the following error:
---------------------------
VirtualBox - Error In supR3HardNtChildWaitFor
Timed out after 60001 ms waiting for child request #1 (CloseEvents).
(rc=258)
where: supR3HardNtChildWaitFor
what:  5
Unknown Status 258 (0x102) (258) - Unknown Status 258 (0x102)
---------------------------

If I do not close it and wait a while (another minute or so) I get it again, and then the guest opens just fine. See this bug description:
https://forums.virtualbox.org/viewtopic.php?t=64111&f=6#p301426 (way back from Oct 2014 and 4.3.18)
...it is essentially this. If I close any of the dialogs, then the guest does not open. Attached are the logs (from 5.0.10, I can recreate with .12 if desired) and a screenshot of the errors. The logs appear normal.

Thanks
Nils
"	Nils
14905	Error In supR3HardNtChildWaitFor	VirtualBox 5.0.10	2015-12-06T21:10:26Z	2016-02-01T09:27:14Z	2016-02-01T09:27:14Z	"Since last week I've been encountering problem with starting Linux virtual machine. It's now starting about 2 minutes and before start it throws an error (in attachment: error-screenshot.jpg).
I've disabled my Avira antivirus real-time protection but it doesn't help, I hadn't installed any additional software before bug started to appear (only Avira Antivirus had made it's update)."	DSProgrammer
20059	error in window vista	VirtualBox 6.1.16	2020-11-23T01:29:24Z	2020-11-23T01:29:24Z	2020-11-23T01:29:24Z	error in window vista	lev115
17652	Error message	VirtualBox 4.3.26	2018-03-30T16:37:24Z	2018-04-19T20:24:34Z	2018-04-19T20:24:34Z	"Trying to run a program called WISEPC 2015 which is supposed to run on VirtualBox, and I get an error message. I have attached the log file and image.

""A critical error has occurred while running the VM and the machine execution has been stopped""

""Unable to allocate and unlock memory. The VM has been paused. Please close applications to free up memory or close the VM."	Carman
15827	Error message when starting VMs: Error In supR3HardenedWinReSpawn	VirtualBox 5.1.4	2016-08-19T13:34:14Z	2021-07-06T13:05:47Z	2021-07-06T13:05:47Z	"Almost everyday when I start my machine and run Vbox and try to start a vm, a msgbox appears with the following error:


{{{
VirtualBox - Error In supR3HardenedWinReSpawn
(rc=-5640)
Please try reinstalling VirtualBox.
where supR3HardenedWinReSpawn what: 1
VERR_SUP_VP_THREAD_NOT_ALONE (-5640) - Process Verification Failure: The process has more than one thread.
}}}

When I click ""ok"", another msgbox appears:

{{{
Failed to open a session for the virtual machine Ubuntu 16.04.

The virtual machine 'Ubuntu 16.04' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\jbassi\VirtualBox VMs\Ubuntu 16.04\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
}}}

This has been happening for month, with current version, last version, tests versions, etc.
The reason I haven't reported this bug until now is because if I try again a few times (two or three) the VM starts up correctly. So I cannot reproduce everytime. In order to reproduce I need to restart the machine. The first time I try after a reboot almost always fails.

Version: Version 5.1.4 r110228 (Qt5.5.1)
Host: Windows 8.1 Enterprise
CPU: Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz
"	asdfafds
14823	Error messages on a Windows 7 shutdown when VirtualBox is still open	VirtualBox 5.0.10	2015-11-13T19:53:35Z	2019-11-12T21:48:28Z	2019-11-12T21:48:28Z	"I always get a series of 6 error messages that popup when I try to shutdown my computer when virtualbox is still open.  I don't have to have any VMs open.

To reproduce:
1. Start computer.
2. open virtualbox.
3. shutdown computer.
I get the attached error messages each time.  I have to click OK on each one.

Let me know what you need.  Maybe it's something to do with my specific computer but I figure it out from the error messages."	Wes Manning
20331	Error NS_ERROR_FAILURE (0x80004005)	VirtualBox 6.1.20	2021-04-30T10:45:50Z	2021-04-30T10:45:50Z	2021-04-30T10:45:50Z	"Everytime I tried to open an ISO file error happened. 

OSX Big Sur 11.3 (20E232)

Nothing in log file. Just an error I attached here. "	r0mkan
15955	"Error occurred when the file from the virtual drag and drop to the host, prompt ""Drag and drop error from guest Drag (VERR_FILE_NOT_FOUND)"""	VirtualBox 5.1.6	2016-09-19T06:13:28Z	2016-09-20T11:56:43Z	2016-09-20T11:56:43Z	"Error occurred when the file from the virtual drag and drop to the host, prompt ""Drag  and drop error from guest Drag (VERR_FILE_NOT_FOUND)  VBOX_E_IPRT_ERROR (0x80BB0005)"".
My operating system: win10_1607."	zhaoyao
15941	Error occurs trying to add a machine to be fixed.	VirtualBox 5.1.6	2016-09-16T09:35:39Z	2016-09-21T23:58:04Z	2016-09-21T23:58:04Z	"An old machine with an old reference to a DVD image cannot be added as the manager incorrectly tries to ""run"" it before actually adding it in, the machine cannot be fixed if its not already in the manager."	Paul17041993
19995	Error occurs when attempting to delete a virtualbox nic if it is disabled in the operating system	VirtualBox 6.1.16	2020-10-23T20:54:34Z	2020-10-23T20:54:34Z	2020-10-23T20:54:34Z	"Not particularly a huge issue, but I have found that, when one attempts to delete a virtualbox virtual network adapter from within virtualbox and the virtual nic has been disabled in the actual operating system, you get this error:

[[Image(https://i.imgur.com/KZwaezQ.png)]]

However, as you may have guessed, if I re-enable the virtual network adapter in the operating system and try to delete the nic in virtualbox, it works."	coolbeans
20066	Error on starting 6.1 with windows  on Mac with Big Sur w	VirtualBox 6.1.16	2020-11-25T13:01:58Z	2020-11-25T13:01:58Z	2020-11-25T13:01:58Z	"Report created by virtualbox app
Failed to open a session for the virtual machine windowsxp.
The virtual machine 'windowsxp' has terminated unexpectedly during startup with exit code 1 (0x1).
 Result Code: Component: Interface:
NS_ERROR_FAILURE (0x80004005)
MachineWrap
IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}
Report created by the Mac running BIG SUR 11.0.1
Process: VirtualBoxVM [8761]
Path: /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/ MacOS/VirtualBoxVM
Identifier: Version:
Code Type: Parent Process: Responsible: User ID:
org.virtualbox.app.VirtualBoxVM 6.1.16 (6.1.16)
X86-64 (Native) ??? [1]
VirtualBox [8746] 501
Date/Time:
OS Version:
Report Version: Anonymous UUID:
2020-11-25 13:42:08.204 +0100 macOS 11.0.1 (20B29)
12
Time Awake Since Boot: 11000 seconds System Integrity Protection: enabled
Crashed Thread:
Exception Type: Exception Codes: Exception Note:
0 Dispatch queue: com.apple.main-thread
EXC_CRASH (SIGABRT) 0x0000000000000000, 0x0000000000000000
EXC_CORPSE_NOTIFY
1C733168-1404-0509-755D-EA122E4D740A
Application Specific Information: crashed on child side of fork pre-exec
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff20315462 __pthread_kill + 10
1 libsystem_pthread.dylib 0x00007fff20343610 pthread_kill + 263
2 libsystem_c.dylib 0x00007fff20296720 abort + 120
3 org.qt-project.QtCoreVBox
4 org.qt-project.QtCoreVBox
const + 224
5 VirtualBoxVM.dylib
0x000000010d529619 0x10d513000 + 91673 0x000000010d52b020 QMessageLogger::fatal(char const*, ...)
0x000000010d37bb3b TrustedError + 1691
6 org.virtualbox.app.VirtualBoxVM
7 org.virtualbox.app.VirtualBoxVM
8 org.virtualbox.app.VirtualBoxVM
9 org.virtualbox.app.VirtualBoxVM
10 libdyld.dylib 0x00007fff2035e631 start + 1
Thread 3:
0 libsystem_pthread.dylib
Thread 5:: Dispatch queue: NSCGSDisableUpdates
0 libsystem_kernel.dylib
1 libdispatch.dylib
2 libdispatch.dylib
3 com.apple.SkyLight
CGSUpdateManager::enable_updates_common() + 1146
4 com.apple.SkyLight 130
5 libdispatch.dylib
6 libdispatch.dylib
7 libdispatch.dylib
8 libdispatch.dylib
9 libdispatch.dylib
0x00007fff24bf7501 SLSReenableUpdateTokenWithSeed +
0x00007fff201975dd _dispatch_call_block_and_release + 12 0x00007fff201987c7 _dispatch_client_callout + 8 0x00007fff2019e5fe _dispatch_lane_serial_drain + 606 0x00007fff2019f0cb _dispatch_lane_invoke + 375 0x00007fff201a8c5d _dispatch_workloop_worker_thread + 819
0x000000010d331d70 0x10d32f000 + 11632 0x000000010d331f1d 0x10d32f000 + 12061 0x000000010d3323a6 0x10d32f000 + 13222 0x000000010d3324bd 0x10d32f000 + 13501
Thread 1:: Dispatch queue: com.apple.SkyLight.UpdateManager.SerialSema
0 libsystem_kernel.dylib 0x00007fff2030eeba semaphore_wait_trap + 10
1 com.apple.SkyLight 0x00007fff24bf6ce1 invocation function for block in
(anonymous namespace)::InterprocessSerialSemaphore::asyncWait(void (int) block_pointer) + 35
2 libdispatch.dylib
3 libdispatch.dylib
4 libdispatch.dylib
5 libdispatch.dylib
6 libdispatch.dylib
7 libsystem_pthread.dylib
8 libsystem_pthread.dylib
Thread 2:
0 libsystem_pthread.dylib
0 libsystem_kernel.dylib
1 libsystem_kernel.dylib
2 com.apple.CoreFoundation
3 com.apple.CoreFoundation
4 com.apple.CoreFoundation
5 com.apple.AppKit
6 libsystem_pthread.dylib
7 libsystem_pthread.dylib
0x00007fff201975dd _dispatch_call_block_and_release + 12 0x00007fff201987c7 _dispatch_client_callout + 8 0x00007fff2019e5fe _dispatch_lane_serial_drain + 606 0x00007fff2019f0cb _dispatch_lane_invoke + 375 0x00007fff201a8c5d _dispatch_workloop_worker_thread + 819
0x00007fff20340499 _pthread_wqthread + 314 0x00007fff2033f467 start_wqthread + 15
0x00007fff2033f458 start_wqthread + 0
0x00007fff2033f458 start_wqthread + 0 Thread 4:: com.apple.NSEventThread
0x00007fff2030ee7e mach_msg_trap + 10 0x00007fff2030f1f0 mach_msg + 60
0x00007fff2043bbe7 __CFRunLoopServiceMachPort + 316 0x00007fff2043a2ba __CFRunLoopRun + 1315 0x00007fff204396be CFRunLoopRunSpecific + 563 0x00007fff22dd936d _NSEventThread + 124 0x00007fff20343950 _pthread_start + 224 0x00007fff2033f47b thread_start + 15
0x00007fff2030eed2 semaphore_timedwait_trap + 10 0x00007fff20198cda _dispatch_sema4_timedwait + 76 0x00007fff20199106 _dispatch_semaphore_wait_slow + 58
0x00007fff24bf6ad0

10 libsystem_pthread.dylib 11 libsystem_pthread.dylib
Thread 6:
0 libsystem_pthread.dylib
0x00007fff20340499 _pthread_wqthread + 314 0x00007fff2033f467 start_wqthread + 15
0x00007fff2033f458 start_wqthread + 0
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x000000011a6c3e00 rcx: 0x00007ffee28c9948 rdx:
0x0000000000000000
rdi: 0x0000000000000303 rsi: 0x0000000000000006 rbp: 0x00007ffee28c9970 rsp:
0x00007ffee28c9948
r8: 0x00000000000130a8 r9: 0x00007fff88abce68 r10: 0x000000011a6c3e00 r11:
0x0000000000000246
r12: 0x0000000000000303 r13: 0x0000000000000003 r14: 0x0000000000000006 r15:
0x0000000000000016
rip: 0x00007fff20315462 rfl: 0x0000000000000246 cr2: 0x000000010d5abcb0
Logical CPU: 0
Error Code:
Trap Number: 133
0x02000148
Thread 0 instruction stream not available. Thread 0 last branch register state not available.
Binary Images:
0x10d32f000 - 0x10d350fff +org.virtualbox.app.VirtualBoxVM (6.1.16 - 6.1.16)
<E16212EC-8D76-3B0C-814C-7BFCC94C0A11> /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/ VirtualBoxVM
0x10d372000 - 0x10d495fff +VirtualBoxVM.dylib (0) <6B4E090D-66B3-3FC7-B32F- 836043159D92> /Applications/VirtualBox.app/Contents/MacOS/VirtualBoxVM.dylib
0x10d4fe000 - 0x10d507fff +org.qt-project.QtMacExtrasVBox (5.6 - 5.6.3) <AC6F0DC8- BF41-3A20-B803-656B301B8CDF> /Applications/VirtualBox.app/Contents/Frameworks/QtMacExtrasVBox.framework/Versions/5/ QtMacExtrasVBox
0x10d513000 - 0x10da3afff +org.qt-project.QtCoreVBox (5.6 - 5.6.3) <3A7A08E0-9422- 393E-BD97-FD15E751434C> /Applications/VirtualBox.app/Contents/Frameworks/QtCoreVBox.framework/Versions/5/ QtCoreVBox
0x10dafe000 - 0x10dfd9fff +org.qt-project.QtGuiVBox (5.6 - 5.6.3) <80F8D761-23D7- 381D-B8D5-1C0C130F7876> /Applications/VirtualBox.app/Contents/Frameworks/QtGuiVBox.framework/Versions/5/ QtGuiVBox
0x10e0da000 - 0x10e5e3fff +org.qt-project.QtWidgetsVBox (5.6 - 5.6.3) <9B8AA540- 6691-39F4-B3A2-74B3D4B990D9> /Applications/VirtualBox.app/Contents/Frameworks/QtWidgetsVBox.framework/Versions/5/ QtWidgetsVBox
0x10e755000 - 0x10e789fff +org.qt-project.QtPrintSupportVBox (5.6 - 5.6.3) <4C8D48EF-FC21-3BE7-895F-584399F0B308>

/Applications/VirtualBox.app/Contents/Frameworks/QtPrintSupportVBox.framework/Versions/5/ QtPrintSupportVBox
0x10e7b0000 - 0x10e7effff +org.qt-project.QtOpenGLVBox (5.6 - 5.6.3) <F75D0235- BFE7-3966-A3C4-CFEA758B9A71> /Applications/VirtualBox.app/Contents/Frameworks/QtOpenGLVBox.framework/Versions/5/ QtOpenGLVBox
0x10e815000 - 0x10e86afff +VBoxDDU.dylib (0) <C1A74C25-F355-3CCF-8977- B32A96C74B6E> /Applications/VirtualBox.app/Contents/MacOS/VBoxDDU.dylib
0x10e87a000 - 0x110922fff +UICommon.dylib (0) <E2B541E7-B929-3FBD-A0F2- E252A939AF93> /Applications/VirtualBox.app/Contents/MacOS/UICommon.dylib
0x110b24000 - 0x111084fff +VBoxRT.dylib (0) <140513F2-DF4C-35FC-8557- 25E51BF36ABC> /Applications/VirtualBox.app/Contents/MacOS/VBoxRT.dylib
0x1111a6000 - 0x1114abfff +VBoxVMM.dylib (0) <51AAF6AB-AED0-3DD3-87E0- 3C883C15F13B> /Applications/VirtualBox.app/Contents/MacOS/VBoxVMM.dylib
0x11152c000 - 0x1115ddfff +VBoxXPCOM.dylib (0) <D6B028AC-EC98-3C70-88BF- F5A0F9EC8B9B> /Applications/VirtualBox.app/Contents/MacOS/VBoxXPCOM.dylib
0x111797000 - 0x1117a6fff libobjc-trampolines.dylib (818.2) <27F9380F-20DE-3228- B34B-499FC8637F39> /usr/lib/libobjc-trampolines.dylib
0x1154e1000 - 0x115620fff +libqcocoa.dylib (0) <FA226E50-20A3-3C6D-B04E- 9262D65300BC> /Applications/VirtualBox.app/Contents/plugins/platforms/libqcocoa.dylib
0x11a5ec000 - 0x11a687fff dyld (832.7.1) <2705F0D8-C104-3DE9-BEB5- B1EF6E28656D> /usr/lib/dyld
0x7fff2007c000 - 0x7fff2007dfff libsystem_blocks.dylib (78) <83E2F888-F4C1-3181-B21B- 136A0D7293DD> /usr/lib/system/libsystem_blocks.dylib
0x7fff2007e000 - 0x7fff200b3fff libxpc.dylib (2038.40.38) <DC50F7DD-1C4B-3BD2-A54D- C5D7D97A3718> /usr/lib/system/libxpc.dylib
0x7fff200b4000 - 0x7fff200cbfff libsystem_trace.dylib (1277.50.1) <94196441-5456-342D- 84D1-C60A9249D273> /usr/lib/system/libsystem_trace.dylib
0x7fff200cc000 - 0x7fff20167fff libcorecrypto.dylib (1000.40.21) <2FA5C1BD-F41C-3FCF- B1FA-7BED6E19ABEE> /usr/lib/system/libcorecrypto.dylib
0x7fff20168000 - 0x7fff20194fff libsystem_malloc.dylib (317.40.8) <3688DBCE-2FFD- 3F98-B12B-69ABE231908D> /usr/lib/system/libsystem_malloc.dylib
0x7fff20195000 - 0x7fff201d9fff libdispatch.dylib (1271.40.12) <C55547DC-A05B-34A1- BD41-D54948D8F57F> /usr/lib/system/libdispatch.dylib
0x7fff201da000 - 0x7fff20212fff libobjc.A.dylib (818.2) <DD09F187-80F1-308F-9395- 912F27E9A390> /usr/lib/libobjc.A.dylib
0x7fff20213000 - 0x7fff20215fff libsystem_featureflags.dylib (28.40.2) <3E1E8F98-E791- 301D-909F-4CA205C94D1A> /usr/lib/system/libsystem_featureflags.dylib
0x7fff20216000 - 0x7fff2029efff libsystem_c.dylib (1439.40.11) <8D791F3A-4848-302F- 88CD-46D91DE73127> /usr/lib/system/libsystem_c.dylib
0x7fff2029f000 - 0x7fff202f4fff libc++.1.dylib (904.4) <E7F465AC-C8FF-31DB-8EC4- 7EBBA7468EB5> /usr/lib/libc++.1.dylib
0x7fff202f5000 - 0x7fff2030dfff libc++abi.dylib (904.4) <253848B5-ED35-3202-8593- 5DCC763A8192> /usr/lib/libc++abi.dylib
0x7fff2030e000 - 0x7fff2033cfff libsystem_kernel.dylib (7195.50.7) <41068F5C-74E3-3C98- 9256-6A18364FB5BA> /usr/lib/system/libsystem_kernel.dylib
0x7fff2033d000 - 0x7fff20348fff libsystem_pthread.dylib (454.40.3) <78072EC6-2257-361A- AAF5-4A3C1832B5EB> /usr/lib/system/libsystem_pthread.dylib
0x7fff20349000 - 0x7fff20383fff libdyld.dylib (832.7.1) <0C66AB9F-E22C-3286-B76B- DA4008698CD2> /usr/lib/system/libdyld.dylib
0x7fff20384000 - 0x7fff2038dfff libsystem_platform.dylib (254.40.4) <6C05D209-129A- 373A-A90D-CC27AB18C091> /usr/lib/system/libsystem_platform.dylib

0x7fff2038e000 - 0x7fff203b9fff libsystem_info.dylib (542.40.3) <90DDEF9D-9DBA-3599- A9DD-A7F730AE945F> /usr/lib/system/libsystem_info.dylib
0x7fff203ba000 - 0x7fff20855fff com.apple.CoreFoundation (6.9 - 1770.106) <7EBD4941- 5978-33EF-98FB-724BB81E92C8> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x7fff20856000 - 0x7fff20a84fff com.apple.LaunchServices (1122.5.1 - 1122.5.1) <E26F607E-C523-3753-95FC-7A75130632FE> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/ LaunchServices.framework/Versions/A/LaunchServices
0x7fff20a85000 - 0x7fff20b58fff com.apple.gpusw.MetalTools (1.0 - 1) <0CC81516-4858- 3463-A2D8-8FCA414B63FD> /System/Library/PrivateFrameworks/MetalTools.framework/Versions/A/MetalTools
0x7fff20b59000 - 0x7fff20dbcfff libBLAS.dylib (1336.40.1) <903B0DDC-4B74-3305-B81D- 8E66D6AFAD04> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/ vecLib.framework/Versions/A/libBLAS.dylib
0x7fff20dbd000 - 0x7fff20e0afff com.apple.Lexicon-framework (1.0 - 86.1) <A6282972- 785B-3AC4-84A5-6780315011F1> /System/Library/PrivateFrameworks/Lexicon.framework/Versions/A/Lexicon
0x7fff20e0b000 - 0x7fff20e79fff libSparse.dylib (106) <D2BC7FE6-7801-3C3B-B8AC- A1F152F92D12> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/ vecLib.framework/Versions/A/libSparse.dylib
0x7fff20e7a000 - 0x7fff20ef6fff com.apple.SystemConfiguration (1.20 - 1.20) <660AA1E5- A70A-3FC1-9462-570FBBC76125> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration
0x7fff20ef7000 - 0x7fff20f2cfff libCRFSuite.dylib (50) <6873F563-F0FB-32C5-A47A- D97A4931FEA8> /usr/lib/libCRFSuite.dylib
0x7fff20f2d000 - 0x7fff21163fff libmecabra.dylib (929) <CF4538C2-3F4A-360C-B6D9- DEBBA67CD5F0> /usr/lib/libmecabra.dylib
0x7fff21164000 - 0x7fff214c7fff com.apple.Foundation (6.9 - 1770.106) <87138770-ED31- 393C-B462-4DAF1A0A52D7> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x7fff214c8000 - 0x7fff215b4fff com.apple.LanguageModeling (1.0 - 247) <83FC0636- F2C6-33F1-A873-E3D5A07A9BA4> /System/Library/PrivateFrameworks/LanguageModeling.framework/Versions/A/ LanguageModeling
0x7fff215b5000 - 0x7fff216ebfff com.apple.CoreDisplay (229.1 - 229.1) <AA59D0CD-E87F- 3C7A-AD83-6EC5D4E67DD5> /System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay
0x7fff216ec000 - 0x7fff21961fff com.apple.audio.AudioToolboxCore (1.0 - 1180.19.2) <B7A2D61A-1494-31D8-B8BD-E4D99F512F2A> /System/Library/PrivateFrameworks/AudioToolboxCore.framework/Versions/A/AudioToolboxCore
0x7fff21962000 - 0x7fff21b4bfff com.apple.CoreText (677.1.0.7 - 677.1.0.7) <ACB75DE7- 96D0-379E-8E94-B7DF51A694B9> /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText
0x7fff21b4c000 - 0x7fff221effff com.apple.audio.CoreAudio (5.0 - 5.0) <6A945D2C-386F- 375C-8343-845012AAA414> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
0x7fff221f0000 - 0x7fff2253ffff com.apple.security (7.0 - 59754.41.1) <93F55E6B-0EB7- 3E06-A742-CEBE33A01DCE> /System/Library/Frameworks/Security.framework/Versions/A/Security
0x7fff22540000 - 0x7fff227a1fff libicucore.A.dylib (66108) <D5A29DA5-5693-38EA-B09B- 5D7160B26339> /usr/lib/libicucore.A.dylib

0x7fff227a2000 - 0x7fff227abfff libsystem_darwin.dylib (1439.40.11) <3BD9046F-FAED- 3FD9-8191-49A4618555A3> /usr/lib/system/libsystem_darwin.dylib
0x7fff227ac000 - 0x7fff22a93fff com.apple.CoreServices.CarbonCore (1307 - 1307) <F20CD75D-F81D-36F3-90AE-7C2F26E01DA4> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/ CarbonCore.framework/Versions/A/CarbonCore
0x7fff22a94000 - 0x7fff22ad2fff com.apple.CoreServicesInternal (476 - 476) <E861339B- F001-3BBC-96C7-916E41B0F238> /System/Library/PrivateFrameworks/CoreServicesInternal.framework/Versions/A/ CoreServicesInternal
0x7fff22ad3000 - 0x7fff22b0dfff com.apple.CSStore (1122.5.1 - 1122.5.1) <74069AC7- 3AA9-3953-A036-425105377BFF> /System/Library/PrivateFrameworks/CoreServicesStore.framework/Versions/A/CoreServicesStore
0x7fff22b0e000 - 0x7fff22bbbfff com.apple.framework.IOKit (2.0.2 - 1845.50.1) <18A1F263-4AE2-3F9B-A38F-50BEB00B43D1> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x7fff22bbc000 - 0x7fff22bc7fff libsystem_notify.dylib (279.40.4) <73D358B2-6C2D-33DF- 975C-BE9EE5F45A0F> /usr/lib/system/libsystem_notify.dylib
0x7fff22bc8000 - 0x7fff22c13fff libsandbox.1.dylib (1441.40.38) <C3EE1BD6-3A84-3997- A6F1-B8CA56747A87> /usr/lib/libsandbox.1.dylib
0x7fff22c14000 - 0x7fff23970fff com.apple.AppKit (6.9 - 2022.10.104) <FA93F8CC-AB69- 3E81-AC53-3FA08704738C> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x7fff23971000 - 0x7fff23bc4fff com.apple.UIFoundation (1.0 - 725) <7F8DC3AA-296B- 37DE-AF30-40F2653452C1> /System/Library/PrivateFrameworks/UIFoundation.framework/Versions/A/UIFoundation
0x7fff23bc5000 - 0x7fff23bd7fff com.apple.UniformTypeIdentifiers (631.8 - 631.8) <071D25FB-2014-3066-9B85-6FE5CCC0B6AC> /System/Library/Frameworks/UniformTypeIdentifiers.framework/Versions/A/ UniformTypeIdentifiers
0x7fff23bd8000 - 0x7fff23d62fff com.apple.desktopservices (1.16 - 1346.1.2) <A32717C6- 9203-365E-8999-2E0E846B59F5> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/ DesktopServicesPriv
0x7fff2402f000 - 0x7fff24672fff libnetwork.dylib (2288.40.53) <CEC9E75A-51F6-3675- 9EA5-007C3DB82A7B> /usr/lib/libnetwork.dylib
0x7fff24673000 - 0x7fff24b10fff com.apple.CFNetwork (1207.2 - 1207.2) <B3968D35- EAF0-3661-8F93-3255128411B6> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
0x7fff24b11000 - 0x7fff24b1ffff libsystem_networkextension.dylib (1295.40.29) <84A5011E- 1511-30C7-86D8-514CFA59EF42> /usr/lib/system/libsystem_networkextension.dylib
0x7fff24b20000 - 0x7fff24b20fff libenergytrace.dylib (22) <3646415C-FA89-30B2-84C4- 3FDB868DF6F6> /usr/lib/libenergytrace.dylib
0x7fff24b21000 - 0x7fff24b7cfff libMobileGestalt.dylib (978.40.29) <BC657BA3-6A59- 35EF-8E90-26D431477F74> /usr/lib/libMobileGestalt.dylib
0x7fff24b7d000 - 0x7fff24b93fff libsystem_asl.dylib (385) <EB8BA94D-1B45-322E-9D26- 272872423807> /usr/lib/system/libsystem_asl.dylib
0x7fff24b94000 - 0x7fff24babfff com.apple.TCC (1.0 - 1) <A3F5F853-54FC-3E67-9F8B- 3605B1063D6F> /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC
0x7fff24bac000 - 0x7fff24f0afff com.apple.SkyLight (1.600.0 - 564) <8C9746D1-E3E5- 346F-AA56-6EFCDC13DBA4> /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight

0x7fff24f0b000 - 0x7fff2559efff com.apple.CoreGraphics (2.0 - 1463) <C5688C95-BE5D- 3278-B1CD-F0A02DF8BDEC> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics
0x7fff2559f000 - 0x7fff25695fff com.apple.ColorSync (4.13.0 - 3472) <37533610-6D35- 304E-8D76-945DA4E524AB> /System/Library/Frameworks/ColorSync.framework/Versions/A/ColorSync
0x7fff25696000 - 0x7fff256f1fff com.apple.HIServices (1.22 - 712) <8B336535-DBFD- 3B34-8099-FF2DEE52BE7F> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ HIServices.framework/Versions/A/HIServices
0x7fff25a9d000 - 0x7fff25ebafff com.apple.CoreData (120 - 1044.1) <57B11511-9A86-3373- 8A84-C1AEBC304131> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
0x7fff25ebb000 - 0x7fff25ed1fff com.apple.ProtocolBuffer (1 - 285.20.8.8.1) <7B0CA279- FD76-32D3-9A8B-ABA6AA799C30> /System/Library/PrivateFrameworks/ProtocolBuffer.framework/Versions/A/ProtocolBuffer
0x7fff25ed2000 - 0x7fff26091fff libsqlite3.dylib (321.1) <821CC6A3-785F-3EE7-ADFA- 9231367F8E09> /usr/lib/libsqlite3.dylib
0x7fff26092000 - 0x7fff2610efff com.apple.Accounts (113 - 113) <71C2E841-B020-3116- B883-418F84E2343B> /System/Library/Frameworks/Accounts.framework/Versions/A/Accounts 0x7fff2610f000 - 0x7fff26127fff com.apple.commonutilities (8.0 - 900) <8290C811-7A21-
3492-B1BC-67FDF0E1BC3A> /System/Library/PrivateFrameworks/CommonUtilities.framework/Versions/A/CommonUtilities
0x7fff26128000 - 0x7fff261a9fff com.apple.BaseBoard (526 - 526) <E401B7D4-F695-3F7C- 87E2-D553189CA550> /System/Library/PrivateFrameworks/BaseBoard.framework/Versions/A/BaseBoard
0x7fff261aa000 - 0x7fff261f5fff com.apple.RunningBoardServices (1.0 - 505.40.18) <26B2DD3C-EF2D-3FD6-9653-D4F857930917> /System/Library/PrivateFrameworks/RunningBoardServices.framework/Versions/A/ RunningBoardServices
0x7fff261f6000 - 0x7fff2626bfff com.apple.AE (918 - 918) <9A914CB1-A413-352B-95BA- D639D66DC591> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/ Versions/A/AE
0x7fff2626c000 - 0x7fff26272fff libdns_services.dylib (1310.40.42) <5D270035-0D34-3E64- 9BA3-8F302E2D767C> /usr/lib/libdns_services.dylib
0x7fff26273000 - 0x7fff2627afff libsystem_symptoms.dylib (1431.40.36) <81345ED1-342F- 347F-B979-39846E607C8C> /usr/lib/system/libsystem_symptoms.dylib
0x7fff2627b000 - 0x7fff263fffff com.apple.Network (1.0 - 1) <91834A81-98F8-36D6-B6DA- D024ED6ECFC7> /System/Library/Frameworks/Network.framework/Versions/A/Network
0x7fff26400000 - 0x7fff26424fff com.apple.analyticsd (1.0 - 1) <C34AD81D-9BD0-3295- BBC5-39D762835717> /System/Library/PrivateFrameworks/CoreAnalytics.framework/Versions/ A/CoreAnalytics
0x7fff26425000 - 0x7fff26427fff libDiagnosticMessagesClient.dylib (112) <BA70052F-9547- 368E-A643-ACF46CA53A3F> /usr/lib/libDiagnosticMessagesClient.dylib
0x7fff26428000 - 0x7fff26474fff com.apple.spotlight.metadata.utilities (1.0 - 2149.9) <732E84A3-6D75-3C92-8C0A-028547EDDF4D> /System/Library/PrivateFrameworks/MetadataUtilities.framework/Versions/A/MetadataUtilities
0x7fff26475000 - 0x7fff2650ffff com.apple.Metadata (10.7.0 - 2149.9) <19EA1487-2CDE- 36C6-8EC1-537E33FB8874> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/ Metadata.framework/Versions/A/Metadata

0x7fff26510000 - 0x7fff26516fff com.apple.DiskArbitration (2.7 - 2.7) <2E613BB2-B956- 3668-9B33-1464DBC83611> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
0x7fff26517000 - 0x7fff26bbdfff com.apple.vImage (8.1 - 543) <9CFD36A4-7508-31EB- 8B78-E5572F5C5426> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/ Versions/A/vImage
0x7fff26bbe000 - 0x7fff26e80fff com.apple.QuartzCore (1.11 - 924.8.3) <5AB4670A-3630- 3C4B-B3D5-6A55A09063FC> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
0x7fff26e81000 - 0x7fff26ec2fff libFontRegistry.dylib (309) <A9D64BDE-020F-35E6-8EE7- E5FCF748AEDB> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib
0x7fff26ec3000 - 0x7fff27004fff com.apple.coreui (2.1 - 688.1) <41699554-ABC8-3431- A4E1-026EAD281148> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI
0x7fff27005000 - 0x7fff270f0fff com.apple.ViewBridge (550 - 550) <54AE4058-B1B7-3260- BF7F-27EB494505EC> /System/Library/PrivateFrameworks/ViewBridge.framework/Versions/A/ ViewBridge
0x7fff270f1000 - 0x7fff270fcfff com.apple.PerformanceAnalysis (1.275 - 275) <07995E93- BF12-3B63-B33C-9D8941CF43B3> /System/Library/PrivateFrameworks/PerformanceAnalysis.framework/Versions/A/ PerformanceAnalysis
0x7fff270fd000 - 0x7fff2710cfff com.apple.OpenDirectory (11.0 - 230.40.1) <F1AC2921- D026-3048-909D-B623F6AAFC94> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory
0x7fff2710d000 - 0x7fff2712cfff com.apple.CFOpenDirectory (11.0 - 230.40.1) <030D197F- 1B82-3E26-AD80-C7621EF6656C> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/ CFOpenDirectory.framework/Versions/A/CFOpenDirectory
0x7fff2712d000 - 0x7fff27135fff com.apple.CoreServices.FSEvents (1290.40.2 - 1290.40.2) <EE985F8A-608D-3A9E-8DDE-C8F635DC69CC> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/ FSEvents.framework/Versions/A/FSEvents
0x7fff27136000 - 0x7fff2715afff com.apple.coreservices.SharedFileList (143 - 143) <CCD817BF-99F0-34A3-A619-8F47A1F83CC8> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/ SharedFileList.framework/Versions/A/SharedFileList
0x7fff2715b000 - 0x7fff2715dfff libapp_launch_measurement.dylib (14.1) <7698D7E2- ECE9-3551-AD03-381DF65EE388> /usr/lib/libapp_launch_measurement.dylib
0x7fff2715e000 - 0x7fff271a6fff com.apple.CoreAutoLayout (1.0 - 21.10.1) <14614F40- 5A4F-31C0-90DC-B1FB3D8ECE66> /System/Library/PrivateFrameworks/CoreAutoLayout.framework/Versions/A/CoreAutoLayout
0x7fff271a7000 - 0x7fff27289fff libxml2.2.dylib (34.8) <667639AF-E0DB-3BFD-B641- 5D0BFBCBF6A3> /usr/lib/libxml2.2.dylib
0x7fff2728a000 - 0x7fff272d6fff com.apple.CoreVideo (1.8 - 408.4) <652F979C-432A-304C- 964C-6AE3231398F3> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
0x7fff272d7000 - 0x7fff272d9fff com.apple.loginsupport (1.0 - 1) <F748E027-FC2A-3492- BBBB-3ED232B2BD1A> /System/Library/PrivateFrameworks/login.framework/Versions/A/Frameworks/ loginsupport.framework/Versions/A/loginsupport

0x7fff27303000 - 0x7fff27320fff com.apple.UserManagement (1.0 - 1) <3677EF4B-F11A- 3485-9DB5-D6251E690B77> /System/Library/PrivateFrameworks/UserManagement.framework/Versions/A/UserManagement
0x7fff282ba000 - 0x7fff282cafff libsystem_containermanager.dylib (318.41.1) <BF178091- 2151-3462-AB4F-A2E111650BA2> /usr/lib/system/libsystem_containermanager.dylib
0x7fff282cb000 - 0x7fff282dcfff com.apple.IOSurface (289.3 - 289.3) <457DD2AD-E48D- 3BD3-9549-9CD9CA6B4F51> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface
0x7fff282dd000 - 0x7fff282e9fff com.apple.IOAccelerator (439.35.4 - 439.35.4) <1FC8B98E-D5A3-3C7B-919B-D187D7A6F76B> /System/Library/PrivateFrameworks/IOAccelerator.framework/Versions/A/IOAccelerator
0x7fff282ea000 - 0x7fff2840ffff com.apple.Metal (244.32.6 - 244.32.6) <6BB79960-68EA- 3CB9-89D9-E8A11B8C9491> /System/Library/Frameworks/Metal.framework/Versions/A/Metal
0x7fff28410000 - 0x7fff2842cfff com.apple.audio.caulk (1.0 - 70) <DCBC8033-421D-39D1- 938A-BDDFF9998179> /System/Library/PrivateFrameworks/caulk.framework/Versions/A/caulk
0x7fff2842d000 - 0x7fff28517fff com.apple.CoreMedia (1.0 - 2757.5) <B547DA4C-81F0- 3793-BCDC-4F454674CBC0> /System/Library/Frameworks/CoreMedia.framework/Versions/A/CoreMedia
0x7fff28518000 - 0x7fff28674fff libFontParser.dylib (305.1.0.5) <A233E765-948B-3954- 99C2-A9122040E41B> /System/Library/PrivateFrameworks/FontServices.framework/libFontParser.dylib
0x7fff28675000 - 0x7fff28974fff com.apple.HIToolbox (2.1.1 - 1060.0.1) <97A715C9-6C47- 388D-8801-A44FB84E5C4D> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/ Versions/A/HIToolbox
0x7fff28975000 - 0x7fff28988fff com.apple.framework.DFRFoundation (1.0 - 264) <C38F9EBB-14D6-354F-8C25-0FB09B110384> /System/Library/PrivateFrameworks/DFRFoundation.framework/Versions/A/DFRFoundation
0x7fff28989000 - 0x7fff2898cfff com.apple.dt.XCTTargetBootstrap (1.0 - 17500) <71F236E8-7169-3A4B-A1CA-94D7F967971D> /System/Library/PrivateFrameworks/XCTTargetBootstrap.framework/Versions/A/ XCTTargetBootstrap
0x7fff2898d000 - 0x7fff289b6fff com.apple.CoreSVG (1.0 - 149) <B105E089-D8AE-3BEF- BE0B-409009959692> /System/Library/PrivateFrameworks/CoreSVG.framework/Versions/A/CoreSVG
0x7fff289b7000 - 0x7fff28bf0fff com.apple.ImageIO (3.3.0 - 2130.1.2) <E6C736F9-05FF- 313E-9707-EBE4EB81BF03> /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO
0x7fff28bf1000 - 0x7fff28f6cfff com.apple.CoreImage (15.0.0 - 1110.11) <AA028F01-5695- 36EA-85EE-EB39CF889102> /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage
0x7fff28f6d000 - 0x7fff28fc8fff com.apple.MetalPerformanceShaders.MPSCore (1.0 - 1) <A929F704-8938-3F9F-8B35-9ABDA03F4D37> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/ MPSCore.framework/Versions/A/MPSCore
0x7fff28fc9000 - 0x7fff28fccfff libsystem_configuration.dylib (1109.40.9) <EA408233- 7EA5-33B5-B099-E9609DD3A0FF> /usr/lib/system/libsystem_configuration.dylib
0x7fff28fcd000 - 0x7fff28fd1fff libsystem_sandbox.dylib (1441.40.38) <349F71A1-4C7C- 3AE0-8A1B-B95CCBB2327F> /usr/lib/system/libsystem_sandbox.dylib
0x7fff28fd2000 - 0x7fff28fd3fff com.apple.AggregateDictionary (1.0 - 1) <59A5FE13-BE12- 3393-BC0F-40007817F8D7>

/System/Library/PrivateFrameworks/AggregateDictionary.framework/Versions/A/ AggregateDictionary
0x7fff28fd4000 - 0x7fff28fd7fff com.apple.AppleSystemInfo (3.1.5 - 3.1.5) <4CE6C43E- 92B6-3933-BEE1-079336A0D6A1> /System/Library/PrivateFrameworks/AppleSystemInfo.framework/Versions/A/AppleSystemInfo
0x7fff28fd8000 - 0x7fff28fd9fff liblangid.dylib (136) <EB65D90D-45E3-326D-9F1E- 3E9E068E64C5> /usr/lib/liblangid.dylib
0x7fff28fda000 - 0x7fff2907afff com.apple.CoreNLP (1.0 - 245) <AC95402C-105B-3830- 8A5B-DA9BCE1AB68B> /System/Library/PrivateFrameworks/CoreNLP.framework/Versions/A/CoreNLP
0x7fff2907b000 - 0x7fff29081fff com.apple.LinguisticData (1.0 - 399) <5C2C56E5-6298- 32D3-B374-362D7C7F4A85> /System/Library/PrivateFrameworks/LinguisticData.framework/Versions/A/LinguisticData
0x7fff29082000 - 0x7fff2973efff libBNNS.dylib (288.40.19) <C5CF6455-A81A-3B09-94F2- C8F7307E5A58> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/ vecLib.framework/Versions/A/libBNNS.dylib
0x7fff2973f000 - 0x7fff29912fff libvDSP.dylib (760.40.6) <CA559095-DE79-3932-B718- 7EFE7770CDF4> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/ vecLib.framework/Versions/A/libvDSP.dylib
0x7fff29913000 - 0x7fff29925fff com.apple.CoreEmoji (1.0 - 128) <7F9AAA77-3D73-3164- 8961-F0BFE55D7AE8> /System/Library/PrivateFrameworks/CoreEmoji.framework/Versions/A/CoreEmoji
0x7fff29926000 - 0x7fff29930fff com.apple.IOMobileFramebuffer (343.0.0 - 343.0.0) <94F7D4E1-88DF-3445-90EF-A0EBC9AF7961> /System/Library/PrivateFrameworks/IOMobileFramebuffer.framework/Versions/A/ IOMobileFramebuffer
0x7fff29931000 - 0x7fff29a03fff com.apple.framework.CoreWLAN (16.0 - 1657) <F8A977ED-F434-33CD-8039-5679152B7971> /System/Library/Frameworks/CoreWLAN.framework/Versions/A/CoreWLAN
0x7fff29a04000 - 0x7fff29c03fff com.apple.CoreUtils (6.4 - 640.15) <D53B6F40-B920- 3A30-A216-440FD2B7AF24> /System/Library/PrivateFrameworks/CoreUtils.framework/Versions/A/CoreUtils
0x7fff29c04000 - 0x7fff29c26fff com.apple.MobileKeyBag (2.0 - 1.0) <841C6DAF-1AF1- 304E-9EBD-49FC945B235A> /System/Library/PrivateFrameworks/MobileKeyBag.framework/Versions/A/MobileKeyBag
0x7fff29c27000 - 0x7fff29c37fff com.apple.AssertionServices (1.0 - 505.40.18) <12D5EA20- 2B9C-3C83-A132-70F77B172775> /System/Library/PrivateFrameworks/AssertionServices.framework/Versions/A/AssertionServices
0x7fff29c38000 - 0x7fff29cc4fff com.apple.securityfoundation (6.0 - 55240.40.4) <AC9A369B-6E9B-3267-B56E-2746853615A0> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation
0x7fff29cc5000 - 0x7fff29ccefff com.apple.coreservices.BackgroundTaskManagement (1.0 - 104) <A59DD866-92E0-3B0E-AE10-36E86878132C> /System/Library/PrivateFrameworks/BackgroundTaskManagement.framework/Versions/A/ BackgroundTaskManagement
0x7fff29ccf000 - 0x7fff29cd3fff com.apple.xpc.ServiceManagement (1.0 - 1) <D522DFA0- C2D9-31EC-BC6F-8B034DACA54D> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement
0x7fff29cd4000 - 0x7fff29cd6fff libquarantine.dylib (119.40.2) <3DD7F9EE-9B9A-3896- A8CC-4D5BE49385AE> /usr/lib/system/libquarantine.dylib
0x7fff29cd7000 - 0x7fff29ce2fff libCheckFix.dylib (31) <E66C5541-5A04-3295-BE25- CC251EC627AE> /usr/lib/libCheckFix.dylib

0x7fff29ce3000 - 0x7fff29cfafff libcoretls.dylib (169) <32CA60AD-6EEF-335D-8FB0- A2695D455939> /usr/lib/libcoretls.dylib
0x7fff29cfb000 - 0x7fff29d0bfff libbsm.0.dylib (68.40.1) <7530532D-8655-34D7-8C1A- 273E196A0DE4> /usr/lib/libbsm.0.dylib
0x7fff29d0c000 - 0x7fff29d55fff libmecab.dylib (929) <533290ED-7500-37B4-9212- D9BA773228F8> /usr/lib/libmecab.dylib
0x7fff29d56000 - 0x7fff29d5bfff libgermantok.dylib (24) <14D82EB1-0212-3E80-90F5- 842233FFA740> /usr/lib/libgermantok.dylib
0x7fff29d5c000 - 0x7fff29d71fff libLinearAlgebra.dylib (1336.40.1) <CF200364-E4AF- 36A8-AB57-1ADFB6BF28B5> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/ Versions/A/libLinearAlgebra.dylib
0x7fff29d72000 - 0x7fff29f99fff com.apple.MetalPerformanceShaders.MPSNeuralNetwork (1.0 - 1) <C08BA44C-9764-363E-A35C-B21AEEFA424B> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/ MPSNeuralNetwork.framework/Versions/A/MPSNeuralNetwork
0x7fff29f9a000 - 0x7fff29fe9fff com.apple.MetalPerformanceShaders.MPSRayIntersector (1.0 - 1) <E7D2B0C7-FAE3-398A-B949-70A0F6CDAD75> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/ MPSRayIntersector.framework/Versions/A/MPSRayIntersector
0x7fff29fea000 - 0x7fff2a130fff com.apple.MLCompute (1.0 - 1) <0621E469-4210-3C45- AC4E-023B25E0D1CE> /System/Library/Frameworks/MLCompute.framework/Versions/A/MLCompute
0x7fff2a131000 - 0x7fff2a167fff com.apple.MetalPerformanceShaders.MPSMatrix (1.0 - 1) <328CA407-7A75-3FE6-9AC1-0D6CE0FF2B0A> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/ MPSMatrix.framework/Versions/A/MPSMatrix
0x7fff2a168000 - 0x7fff2a1a5fff com.apple.MetalPerformanceShaders.MPSNDArray (1.0 - 1) <0CE771E3-E262-3BFC-BF02-888D7EBB0FE3> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/ MPSNDArray.framework/Versions/A/MPSNDArray
0x7fff2a1a6000 - 0x7fff2a236fff com.apple.MetalPerformanceShaders.MPSImage (1.0 - 1) <4130FBE4-C36C-3E1D-BB0B-63D1A64B28E2> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/ MPSImage.framework/Versions/A/MPSImage
0x7fff2a237000 - 0x7fff2a246fff com.apple.AppleFSCompression (125 - 1.0) <5BE26EB2- 6012-33E5-AF38-D8C5F4DF64CA> /System/Library/PrivateFrameworks/AppleFSCompression.framework/Versions/A/ AppleFSCompression
0x7fff2a247000 - 0x7fff2a254fff libbz2.1.0.dylib (44) <F171593B-230C-390E-8EF7- D0659D2F6B54> /usr/lib/libbz2.1.0.dylib
0x7fff2a255000 - 0x7fff2a259fff libsystem_coreservices.dylib (127) <670DDFEB-8100- 3C51-BC96-76BD46A21DF6> /usr/lib/system/libsystem_coreservices.dylib
0x7fff2a25a000 - 0x7fff2a287fff com.apple.CoreServices.OSServices (1122.5.1 - 1122.5.1) <4F03F324-1072-38B8-8BC5-837601C2DBA9> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/ OSServices.framework/Versions/A/OSServices
0x7fff2a288000 - 0x7fff2a3b9fff com.apple.AuthKit (1.0 - 1) <50C7FC9C-283A-3BB0- 8D30-BC39975A2318> /System/Library/PrivateFrameworks/AuthKit.framework/Versions/A/AuthKit
0x7fff2a45d000 - 0x7fff2a46ffff libz.1.dylib (76) <0AF4F195-1F20-3F59-B09F- 31E7249890D5> /usr/lib/libz.1.dylib

0x7fff2a470000 - 0x7fff2a4b7fff libsystem_m.dylib (3186.40.2) <0276200D-C6F2-3E79- AFDC-E4D7F60A7837> /usr/lib/system/libsystem_m.dylib
0x7fff2a4b8000 - 0x7fff2a4b8fff libcharset.1.dylib (59) <56962263-B7B8-3B84-9C2F- F493D9D2630A> /usr/lib/libcharset.1.dylib
0x7fff2a4b9000 - 0x7fff2a4befff libmacho.dylib (973.4) <F2E3F7A6-B15A-30ED-A6AD- 4EFEC37CF3E7> /usr/lib/system/libmacho.dylib
0x7fff2a4bf000 - 0x7fff2a4dafff libkxld.dylib (7195.50.7) <6FFE0801-7BDA-34EE-89E9- EAEC21A7394C> /usr/lib/system/libkxld.dylib
0x7fff2a4db000 - 0x7fff2a4e6fff libcommonCrypto.dylib (60178.40.2) <66E10FDF-896D- 35F4-B9A8-8EE9400AC23A> /usr/lib/system/libcommonCrypto.dylib
0x7fff2a4e7000 - 0x7fff2a4f1fff libunwind.dylib (200.10) <BD13DE19-15F8-3982-ACCB- CD8C036D5D2B> /usr/lib/system/libunwind.dylib
0x7fff2a4f2000 - 0x7fff2a4f9fff liboah.dylib (203.1.3) <5EC28751-3BE8-3BB7-9DBE- 305225CBD41B> /usr/lib/liboah.dylib
0x7fff2a4fa000 - 0x7fff2a504fff libcopyfile.dylib (173.40.2) <17A9CD2E-0527-3FF7-9CFA- 57B30133DFB5> /usr/lib/system/libcopyfile.dylib
0x7fff2a505000 - 0x7fff2a50cfff libcompiler_rt.dylib (102.2) <FE958653-7FEC-3ADD- 9AC0-A386E47208CF> /usr/lib/system/libcompiler_rt.dylib
0x7fff2a50d000 - 0x7fff2a50ffff libsystem_collections.dylib (1439.40.11) <31C10DA5-F9B8- 36E4-B859-8F6B845FF65D> /usr/lib/system/libsystem_collections.dylib
0x7fff2a510000 - 0x7fff2a512fff libsystem_secinit.dylib (87.40.10) <BB2A70F5-BECC- 34BD-90FE-14D31C5FD80D> /usr/lib/system/libsystem_secinit.dylib
0x7fff2a513000 - 0x7fff2a515fff libremovefile.dylib (49.40.3) <24CE2291-AEB3-30C9- 94E8-535AA6E9C6F2> /usr/lib/system/libremovefile.dylib
0x7fff2a516000 - 0x7fff2a516fff libkeymgr.dylib (31) <B47F66C0-27F4-3B77-BAA0- 85E895A7421D> /usr/lib/system/libkeymgr.dylib
0x7fff2a517000 - 0x7fff2a51efff libsystem_dnssd.dylib (1310.40.42) <F54EC6FB-DEC3- 3DA8-A749-4892F50D1F08> /usr/lib/system/libsystem_dnssd.dylib
0x7fff2a51f000 - 0x7fff2a524fff libcache.dylib (83) <C83C4423-D12A-32A0-875D- 81450DF40F42> /usr/lib/system/libcache.dylib
0x7fff2a525000 - 0x7fff2a526fff libSystem.B.dylib (1292.50.1) <14E3BB7B-B95F-3700- 8D12-B9B2012C0AF8> /usr/lib/libSystem.B.dylib
0x7fff2a527000 - 0x7fff2a52afff libfakelink.dylib (3) <6E8ABD0B-6BC7-3E2C-B36B- 2A7DA4ED0804> /usr/lib/libfakelink.dylib
0x7fff2a52b000 - 0x7fff2a52bfff com.apple.SoftLinking (1.0 - 1) <23011830-946E-312B- A4BA-1725568F5E76> /System/Library/PrivateFrameworks/SoftLinking.framework/Versions/A/ SoftLinking
0x7fff2a52c000 - 0x7fff2a563fff libpcap.A.dylib (98.40.1) <F2D9427C-C7D7-35F9-8A65- AE2C76D73E4B> /usr/lib/libpcap.A.dylib
0x7fff2a564000 - 0x7fff2a654fff libiconv.2.dylib (59) <BFC929D5-6E2C-3A49-9760- 870BC89FC558> /usr/lib/libiconv.2.dylib
0x7fff2a655000 - 0x7fff2a666fff libcmph.dylib (8) <ABEA25CF-8895-31DA-B884- F4012007E7E9> /usr/lib/libcmph.dylib
0x7fff2a667000 - 0x7fff2a6d8fff libarchive.2.dylib (83.40.4) <54E0F2AE-C7F5-34A6-8B09- 82FED0643886> /usr/lib/libarchive.2.dylib
0x7fff2a6d9000 - 0x7fff2a740fff com.apple.SearchKit (1.4.1 - 1.4.1) <E51D4AB5-0576- 3392-B45F-E9CA02D22ED5> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/ SearchKit.framework/Versions/A/SearchKit
0x7fff2a741000 - 0x7fff2a742fff libThaiTokenizer.dylib (3) <41BFE684-D7B8-3DBB-A3F6- E25DB819E86A> /usr/lib/libThaiTokenizer.dylib

0x7fff2a743000 - 0x7fff2a76afff com.apple.applesauce (1.0 - 16.26) <0AFF7A71-EE52- 36E6-82B5-459459D99D68> /System/Library/PrivateFrameworks/AppleSauce.framework/Versions/A/AppleSauce
0x7fff2a76b000 - 0x7fff2a782fff libapple_nghttp2.dylib (1.41) <94E600F0-740B-308D-9475- 8720FFB1923E> /usr/lib/libapple_nghttp2.dylib
0x7fff2a783000 - 0x7fff2a795fff libSparseBLAS.dylib (1336.40.1) <7A917514-DD2C-3A97- A29B-F41BDCA18852> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/ Versions/A/libSparseBLAS.dylib
0x7fff2a796000 - 0x7fff2a797fff com.apple.MetalPerformanceShaders.MetalPerformanceShaders (1.0 - 1) <CC090B4C-48B8- 3DE1-84FA-807642C38DF9> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/ MetalPerformanceShaders
0x7fff2a798000 - 0x7fff2a79cfff libpam.2.dylib (28.40.1) <4C7D4B94-5CBA-3480-9BA0- D52B5C675D2A> /usr/lib/libpam.2.dylib
0x7fff2a79d000 - 0x7fff2a7b5fff libcompression.dylib (96.40.6) <C84DBB3A-EDEB-3871- BB2F-AB682A0653F8> /usr/lib/libcompression.dylib
0x7fff2a7b6000 - 0x7fff2a7bbfff libQuadrature.dylib (7) <C13CA095-EE2D-3C50-98E5- A3570323776F> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/ vecLib.framework/Versions/A/libQuadrature.dylib
0x7fff2a7bc000 - 0x7fff2ab58fff libLAPACK.dylib (1336.40.1) <5A406319-C3A7-3D73- 93C2-9968ACC81241> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/ Versions/A/libLAPACK.dylib
0x7fff2ab59000 - 0x7fff2aba7fff com.apple.DictionaryServices (1.2 - 341) <CBFBB0CC- 093A-39AC-99E3-C032029AC7C3> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/ DictionaryServices.framework/Versions/A/DictionaryServices
0x7fff2aba8000 - 0x7fff2abc0fff liblzma.5.dylib (16) <7AEA0ACB-B03C-323B-AD4F- C5BD0584D780> /usr/lib/liblzma.5.dylib
0x7fff2abc1000 - 0x7fff2abc2fff libcoretls_cfhelpers.dylib (169) <86671710-F263-3ED2- 8B7D-0052264682CF> /usr/lib/libcoretls_cfhelpers.dylib
0x7fff2abc3000 - 0x7fff2acbdfff com.apple.APFS (1677.50.1 - 1677.50.1) <CBABD7ED- 84C7-3F72-80EB-5F8AED435566> /System/Library/PrivateFrameworks/APFS.framework/Versions/A/APFS
0x7fff2acbe000 - 0x7fff2accbfff libxar.1.dylib (452) <8999C952-D05A-3BFA-A673- 1EB0B27EBB73> /usr/lib/libxar.1.dylib
0x7fff2accc000 - 0x7fff2accffff libutil.dylib (58.40.2) <ECE0C079-2434-3B7E-89EE- B2E538E7BBAD> /usr/lib/libutil.dylib
0x7fff2acd0000 - 0x7fff2acf8fff libxslt.1.dylib (17.2) <7C79FCBB-B6B4-33A4-BD4B- 34D674C2866F> /usr/lib/libxslt.1.dylib
0x7fff2acf9000 - 0x7fff2ad03fff libChineseTokenizer.dylib (37) <F2ECD480-D020-3141- A3B0-D32C8EDA159F> /usr/lib/libChineseTokenizer.dylib
0x7fff2ad04000 - 0x7fff2adc2fff libvMisc.dylib (760.40.6) <3CA6964F-742A-33C1-90BB- C8B2D1BF0A4D> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/ vecLib.framework/Versions/A/libvMisc.dylib
0x7fff2adc3000 - 0x7fff2ae5bfff libate.dylib (3.0.4) <7D10CB14-3612-31A3-82F2- 232602CA4E86> /usr/lib/libate.dylib
0x7fff2ae5c000 - 0x7fff2ae63fff libIOReport.dylib (64) <AD8D1B4C-F575-316A-9B59- D24C7C15775E> /usr/lib/libIOReport.dylib

0x7fff2ae64000 - 0x7fff2ae92fff com.apple.CrashReporterSupport (10.13 - 15045.1) <2BF44063-CC0D-3CF0-807A-F70E0487E079> /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/ CrashReporterSupport
0x7fff2af7e000 - 0x7fff2af85fff libMatch.1.dylib (38) <93E36D5B-9452-3D8E-BC00- DF3E29E9573F> /usr/lib/libMatch.1.dylib
0x7fff2af86000 - 0x7fff2b011fff libCoreStorage.dylib (554) <7918C52C-BD4A-3661-9735- E7C6B907D48E> /usr/lib/libCoreStorage.dylib
0x7fff2b012000 - 0x7fff2b065fff com.apple.AppleVAFramework (6.1.3 - 6.1.3) <5F9D3C05- FBF9-345D-B49F-95ED20451F0E> /System/Library/PrivateFrameworks/AppleVA.framework/Versions/A/AppleVA
0x7fff2b066000 - 0x7fff2b07ffff libexpat.1.dylib (26) <AE175A8E-4D38-3080-A0A8- 201ACBE332DE> /usr/lib/libexpat.1.dylib
0x7fff2b080000 - 0x7fff2b089fff libheimdal-asn1.dylib (597.40.10) <1316D27D-F0EA- 34C6-A347-BEE21CB6AFA6> /usr/lib/libheimdal-asn1.dylib
0x7fff2b08a000 - 0x7fff2b09efff com.apple.IconFoundation (479.2 - 479.2) <80665902- A372-3C2A-A5EB-25CEDDA30A66> /System/Library/PrivateFrameworks/IconFoundation.framework/Versions/A/IconFoundation
0x7fff2b09f000 - 0x7fff2b10cfff com.apple.IconServices (479.2 - 479.2) <3E085586-2251- 350B-84CE-4CFE7873F9A0> /System/Library/PrivateFrameworks/IconServices.framework/Versions/A/IconServices
0x7fff2b10d000 - 0x7fff2b1aafff com.apple.MediaExperience (1.0 - 1) <86D052FE-4200- 311A-B53D-3C6EF5240A69> /System/Library/PrivateFrameworks/MediaExperience.framework/Versions/A/MediaExperience
0x7fff2b1ab000 - 0x7fff2b1d4fff com.apple.persistentconnection (1.0 - 1.0) <EA6A7841- EC57-39FC-9F2A-11752F6A972C> /System/Library/PrivateFrameworks/PersistentConnection.framework/Versions/A/ PersistentConnection
0x7fff2b1d5000 - 0x7fff2b1e3fff com.apple.GraphVisualizer (1.0 - 100.1) <B9A37FA5- AB1B-3645-9F36-50C48732692D> /System/Library/PrivateFrameworks/GraphVisualizer.framework/Versions/A/GraphVisualizer
0x7fff2b1e4000 - 0x7fff2b5fffff com.apple.vision.FaceCore (4.3.2 - 4.3.2) <54C42FE9-18BE- 3284-A0F5-24F8BD8EE6AE> /System/Library/PrivateFrameworks/FaceCore.framework/Versions/A/FaceCore
0x7fff2b600000 - 0x7fff2b64afff com.apple.OTSVG (1.0 - 677.1.0.7) <918A1463-4534- 3D72-A06E-0531915C4F37> /System/Library/PrivateFrameworks/OTSVG.framework/Versions/A/OTSVG
0x7fff2b64b000 - 0x7fff2b651fff com.apple.xpc.AppServerSupport (1.0 - 2038.40.38) <A437306B-6D63-308B-AC69-468F1A70C8A6> /System/Library/PrivateFrameworks/AppServerSupport.framework/Versions/A/AppServerSupport
0x7fff2b652000 - 0x7fff2b663fff libhvf.dylib (1.0 - $[CURRENT_PROJECT_VERSION]) <D4873860-7D4B-3ACC-8940-2B0956DFB41B> /System/Library/PrivateFrameworks/FontServices.framework/libhvf.dylib
0x7fff2b664000 - 0x7fff2b666fff libspindump.dylib (295) <5B9254B7-7BAB-308E-9182- ECA60A0BA09A> /usr/lib/libspindump.dylib
0x7fff2b667000 - 0x7fff2b727fff com.apple.Heimdal (4.0 - 2.0) <9382C6FC-4234-3D13- A598-0A13C04D9528> /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal
0x7fff2b728000 - 0x7fff2b742fff com.apple.login (3.0 - 3.0) <9C424BA4-9280-30CE-858E- F18587C7E721> /System/Library/PrivateFrameworks/login.framework/Versions/A/login
0x7fff2b8c5000 - 0x7fff2b92ffff com.apple.bom (14.0 - 233) <F2B16396-0757-3E1B-8A67- 5979B9317EF3> /System/Library/PrivateFrameworks/Bom.framework/Versions/A/Bom

0x7fff2b930000 - 0x7fff2b979fff com.apple.AppleJPEG (1.0 - 1) <37C198D5-DF3F-3ED5- 8DD3-5B1FBF7B3059> /System/Library/PrivateFrameworks/AppleJPEG.framework/Versions/A/AppleJPEG
0x7fff2b97a000 - 0x7fff2ba58fff libJP2.dylib (2130.1.2) <F4C74378-8FD9-3A9D-9E14- 86F7213D468A> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/ libJP2.dylib
0x7fff2ba59000 - 0x7fff2ba5cfff com.apple.WatchdogClient.framework (1.0 - 98.40.5) <30521EFA-509E-335C-9D32-5FD6CA769A5A> /System/Library/PrivateFrameworks/WatchdogClient.framework/Versions/A/WatchdogClient
0x7fff2ba5d000 - 0x7fff2ba90fff com.apple.MultitouchSupport.framework (4400.28 - 4400.28) <7A065BB2-13BA-3DB4-93BB-FD4B034EE493> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport
0x7fff2ba91000 - 0x7fff2bbe3fff com.apple.VideoToolbox (1.0 - 2757.5) <286CE415-4B19- 3F7E-A8E4-0CE8C85C7EBF> /System/Library/Frameworks/VideoToolbox.framework/Versions/A/VideoToolbox
0x7fff2bbe4000 - 0x7fff2bc16fff libAudioToolboxUtility.dylib (1180.19.2) <EE687E3D- BA7B-306F-95FC-35A97B7E373B> /usr/lib/libAudioToolboxUtility.dylib
0x7fff2bc17000 - 0x7fff2bc3dfff libPng.dylib (2130.1.2) <C1D8DC7E-D118-3984-80B1- 61D7FA89DC7C> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/ libPng.dylib
0x7fff2bc3e000 - 0x7fff2bc9bfff libTIFF.dylib (2130.1.2) <47BC22DE-0058-3402-90EB- 8EC81BEBC244> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/ libTIFF.dylib
0x7fff2bc9c000 - 0x7fff2bcb8fff com.apple.IOPresentment (50.10 - 37) <A84FB6B2-8ED1- 31DC-AC7C-726E7915F541> /System/Library/PrivateFrameworks/IOPresentment.framework/Versions/A/IOPresentment
0x7fff2bcb9000 - 0x7fff2bcbffff com.apple.GPUWrangler (6.1.27 - 6.1.27) <89405160-B919- 372E-B63A-BA35C9D62EFF> /System/Library/PrivateFrameworks/GPUWrangler.framework/Versions/A/GPUWrangler
0x7fff2bcc0000 - 0x7fff2bcc3fff libRadiance.dylib (2130.1.2) <6A2BF16D-8AF3-32AD- B42F-DA8029A8462E> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/ libRadiance.dylib
0x7fff2bcc4000 - 0x7fff2bcc9fff com.apple.DSExternalDisplay (3.1 - 380) <9BF3CCC3- DB7C-30B3-879B-9650918C73FF> /System/Library/PrivateFrameworks/DSExternalDisplay.framework/Versions/A/DSExternalDisplay
0x7fff2bcca000 - 0x7fff2bceefff libJPEG.dylib (2130.1.2) <E7902D69-99C3-3D7C-9244- 86EA0D1A9617> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/ libJPEG.dylib
0x7fff2bcef000 - 0x7fff2bd1efff com.apple.ATSUI (1.0 - 1) <39A55921-5BA9-3BA0-9C71- FD598BE2E80C> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ Frameworks/ATSUI.framework/Versions/A/ATSUI
0x7fff2bd1f000 - 0x7fff2bd23fff libGIF.dylib (2130.1.2) <BEE81025-0B18-37BD-BB5F- 6E8FD2262336> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/ libGIF.dylib
0x7fff2bd24000 - 0x7fff2bd2dfff com.apple.CMCaptureCore (1.0 - 79.12.3) <43F3557A- D353-36B5-B5D6-3D352478EC2F> /System/Library/PrivateFrameworks/CMCaptureCore.framework/Versions/A/CMCaptureCore
0x7fff2bd2e000 - 0x7fff2bd75fff com.apple.print.framework.PrintCore (16 - 531) <0EB74D87-B560-380C-8B88-EDAED20D0D99> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ PrintCore.framework/Versions/A/PrintCore

0x7fff2bd76000 - 0x7fff2be42fff com.apple.TextureIO (3.10.9 - 3.10.9) <44F02506-287C- 3733-9ED2-01B36F97ABBF> /System/Library/PrivateFrameworks/TextureIO.framework/Versions/A/TextureIO
0x7fff2be43000 - 0x7fff2be4bfff com.apple.InternationalSupport (1.0 - 60) <D92C8AC5- 6D8C-33C9-B011-DE275FA5BB88> /System/Library/PrivateFrameworks/InternationalSupport.framework/Versions/A/ InternationalSupport
0x7fff2be4c000 - 0x7fff2bec7fff com.apple.datadetectorscore (8.0 - 674) <43D2CEDD-8A10- 3A9F-BFE1-CFBBC35149C1> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDetectorsCore
0x7fff2bec8000 - 0x7fff2bf26fff com.apple.UserActivity (434 - 434) <9FDA9333-95A0- 3301-B75C-B6ABD7F94E09> /System/Library/PrivateFrameworks/UserActivity.framework/Versions/A/UserActivity
0x7fff2cb6f000 - 0x7fff2cba0fff libSessionUtility.dylib (76.7) <CA11B08D-BE35-3763- A358-E76B6341B089> /System/Library/PrivateFrameworks/AudioSession.framework/libSessionUtility.dylib
0x7fff2cba1000 - 0x7fff2ccd0fff com.apple.audio.toolbox.AudioToolbox (1.14 - 1.14) <6D66F9E9-C3ED-3015-AB27-BA6D2689A002> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
0x7fff2ccd1000 - 0x7fff2cd38fff com.apple.audio.AudioSession (1.0 - 76.7) <19D0DDAE- D4D2-363A-A6EE-D450E254427D> /System/Library/PrivateFrameworks/AudioSession.framework/Versions/A/AudioSession
0x7fff2cd39000 - 0x7fff2cd4bfff libAudioStatistics.dylib (25) <2310E5CF-38EC-338C- 9C8D-FB79EC9B5C98> /usr/lib/libAudioStatistics.dylib
0x7fff2cd4c000 - 0x7fff2cd5bfff com.apple.speech.synthesis.framework (9.0.48.1 - 9.0.48.1) <92283C03-C35F-3F97-8F81-383FB38CB66B> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ SpeechSynthesis.framework/Versions/A/SpeechSynthesis
0x7fff2cd5c000 - 0x7fff2cdc7fff com.apple.ApplicationServices.ATS (377 - 516) <25751B9A-D1FD-3D90-8EB1-67D3DE9F6163> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/ATS
0x7fff2cdc8000 - 0x7fff2cde0fff libresolv.9.dylib (68) <6C18FE1C-EB05-3E02-925D- DE09157C55F9> /usr/lib/libresolv.9.dylib
0x7fff2cf13000 - 0x7fff2cff2fff libSMC.dylib (20) <2E125E1A-D5D6-3054-8384- E1A7A23DD0FE> /usr/lib/libSMC.dylib
0x7fff2cff3000 - 0x7fff2d052fff libcups.2.dylib (494) <F27A4527-C76D-34FE-B268- 1C57A127C542> /usr/lib/libcups.2.dylib
0x7fff2d053000 - 0x7fff2d062fff com.apple.LangAnalysis (1.7.0 - 254) <B4F48E46-CEF9- 3674-903C-609CA77E78B5> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ LangAnalysis.framework/Versions/A/LangAnalysis
0x7fff2d063000 - 0x7fff2d06dfff com.apple.NetAuth (6.2 - 6.2) <54EC7F7F-0DBB-38E4- 9BBA-0DB0404E2C9D> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth
0x7fff2d06e000 - 0x7fff2d075fff com.apple.ColorSyncLegacy (4.13.0 - 1) <A34CD7EB- 977C-3FF7-A422-9EC40D79A2BD> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ColorSyncLegacy.framework/Versions/A/ColorSyncLegacy
0x7fff2d076000 - 0x7fff2d081fff com.apple.QD (4.0 - 416) <39777BBB-6781-36B5-AF36- E3452D222E09> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ Frameworks/QD.framework/Versions/A/QD

0x7fff2d082000 - 0x7fff2d6f0fff com.apple.audio.AudioResourceArbitration (1.0 - 1) <513ADF72-F3C7-3381-A926-FD1F6683EB09> /System/Library/PrivateFrameworks/AudioResourceArbitration.framework/Versions/A/ AudioResourceArbitration
0x7fff2d6f1000 - 0x7fff2d6fdfff com.apple.perfdata (1.0 - 67.40.1) <9C94952B-AA5F-3541- A326-649EFEAFE8B1> /System/Library/PrivateFrameworks/perfdata.framework/Versions/A/perfdata
0x7fff2d6fe000 - 0x7fff2d70cfff libperfcheck.dylib (41) <32799FC7-F2BF-3440-8853- 378EE0E0445A> /usr/lib/libperfcheck.dylib
0x7fff2d70d000 - 0x7fff2d71cfff com.apple.Kerberos (3.0 - 1) <2529747E-275C-35E6- AB6E-1D14DA5835D2> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos
0x7fff2d71d000 - 0x7fff2d76cfff com.apple.GSS (4.0 - 2.0) <DC8F40C2-966E-3F86-8A21- 47B426965E85> /System/Library/Frameworks/GSS.framework/Versions/A/GSS
0x7fff2d76d000 - 0x7fff2d77dfff com.apple.CommonAuth (4.0 - 2.0) <815F69EE-F251- 3125-A094-C95B25804469> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth
0x7fff2d7d0000 - 0x7fff2d7f2fff com.apple.security.KeychainCircle.KeychainCircle (1.0 - 1) <AD781B2F-DEB0-3E13-9420-C0B6449EDE7A> /System/Library/PrivateFrameworks/KeychainCircle.framework/Versions/A/KeychainCircle
0x7fff2d7f3000 - 0x7fff2d7fbfff com.apple.CorePhoneNumbers (1.0 - 1) <8922ABCB-0302- 382B-A0DD-984668BFA8E3> /System/Library/PrivateFrameworks/CorePhoneNumbers.framework/Versions/A/ CorePhoneNumbers
0x7fff2d950000 - 0x7fff2d950fff liblaunch.dylib (2038.40.38) <D71781B5-4034-3349-BBE5- 4B796CD3629A> /usr/lib/system/liblaunch.dylib
0x7fff2e142000 - 0x7fff2e288fff com.apple.Sharing (1570.6 - 1570.6) <B76CAA48-84E4- 309A-AE4D-FBB5E2D17CAD> /System/Library/PrivateFrameworks/Sharing.framework/Versions/A/Sharing
0x7fff2e289000 - 0x7fff2e3a9fff com.apple.Bluetooth (8.0.1 - 8.0.1f5) <7136F7B5-F009- 3139-BD52-D51815F7D9A4> /System/Library/Frameworks/IOBluetooth.framework/Versions/A/IOBluetooth
0x7fff2e3aa000 - 0x7fff2e3befff com.apple.AppContainer (4.0 - 509.40.16) <705EFE05- 0522-33E1-9139-F9D5B59AEFB7> /System/Library/PrivateFrameworks/AppContainer.framework/Versions/A/AppContainer
0x7fff2e3bf000 - 0x7fff2e3c2fff com.apple.SecCodeWrapper (4.0 - 509.40.16) <74BF3804- 694F-3AE3-95A8-31B1DF5D9468> /System/Library/PrivateFrameworks/SecCodeWrapper.framework/Versions/A/SecCodeWrapper
0x7fff2e3c3000 - 0x7fff2e41cfff com.apple.ProtectedCloudStorage (1.0 - 1) <F5C02479- 9D92-3CB6-8C21-9AA229D411D4> /System/Library/PrivateFrameworks/ProtectedCloudStorage.framework/Versions/A/ ProtectedCloudStorage
0x7fff2fb67000 - 0x7fff2fb92fff com.apple.RemoteViewServices (2.0 - 163) <09228BBD- D1F6-388C-AD09-9AD113C44271> /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/ RemoteViewServices
0x7fff2fb93000 - 0x7fff2fba2fff com.apple.SpeechRecognitionCore (6.1.12 - 6.1.12) <275341D7-157B-3B5A-A81D-382CEF408262> /System/Library/PrivateFrameworks/SpeechRecognitionCore.framework/Versions/A/ SpeechRecognitionCore
0x7fff2fba3000 - 0x7fff2fbaafff com.apple.speech.recognition.framework (6.0.3 - 6.0.3) <66CCAAEC-B04B-326F-BB83-6A9E668111BC>

/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ SpeechRecognition.framework/Versions/A/SpeechRecognition
0x7fff2fdee000 - 0x7fff2fdeefff libsystem_product_info_filter.dylib (8.40.1) <FF59B842- 1290-3C4A-9015-AC972563406E> /usr/lib/system/libsystem_product_info_filter.dylib 0x7fff2fec9000 - 0x7fff2fec9fff com.apple.Accelerate.vecLib (3.11 - vecLib 3.11)
<BBCF1D0C-F727-3B9B-801E-FCEA6C9C1103> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/ Versions/A/vecLib
0x7fff2fef0000 - 0x7fff2fef0fff com.apple.CoreServices (1122.5.1 - 1122.5.1) <070D2800- D014-34E3-AAA9-CB7199EFC728> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x7fff301be000 - 0x7fff301befff com.apple.Accelerate (1.11 - Accelerate 1.11) <5D5F6FDF- 38E5-363A-A73C-3C21A2D11574> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
0x7fff30a22000 - 0x7fff30ab7fff com.apple.CoreBluetooth (1.0 - 1) <0F11E92C-6CFC-3912- BB82-B4CE7BA16FC7> /System/Library/Frameworks/CoreBluetooth.framework/Versions/A/CoreBluetooth
0x7fff30ab8000 - 0x7fff30ac1fff com.apple.SymptomDiagnosticReporter (1.0 - 79.40.12) <3FF67454-E235-33D7-AB87-02496A234188> /System/Library/PrivateFrameworks/SymptomDiagnosticReporter.framework/Versions/A/ SymptomDiagnosticReporter
0x7fff30ad6000 - 0x7fff30ae2fff com.apple.AppleIDAuthSupport (1.0 - 1) <7103A610-7E5A- 34F7-BE69-5E25B334E66A> /System/Library/PrivateFrameworks/AppleIDAuthSupport.framework/Versions/A/ AppleIDAuthSupport
0x7fff30ae3000 - 0x7fff30b8bfff com.apple.DiscRecording (9.0.3 - 9030.4.5) <12CEDA8E- D339-3022-BFD9-135458523B3E> /System/Library/Frameworks/DiscRecording.framework/Versions/A/DiscRecording
0x7fff30b8c000 - 0x7fff30bbffff com.apple.MediaKit (16 - 927.40.2) <E5571EB2-2864- 372E-BE83-DDE90F1A05CC> /System/Library/PrivateFrameworks/MediaKit.framework/Versions/A/MediaKit
0x7fff30bc0000 - 0x7fff30cabfff com.apple.DiskManagement (14.0 - 1733.40.24) <7B3D0853-7B34-331A-902C-D2ED8004FD39> /System/Library/PrivateFrameworks/DiskManagement.framework/Versions/A/DiskManagement
0x7fff31099000 - 0x7fff311b9fff com.apple.FileProvider (325 - 325) <B02BE1B5-92B4- 371F-AEBA-087BB58272D4> /System/Library/Frameworks/FileProvider.framework/Versions/A/FileProvider
0x7fff311ba000 - 0x7fff311ddfff com.apple.GenerationalStorage (2.0 - 322) <3400BD70- 40AE-3FC5-BC7F-B6AB44B6134D> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/ GenerationalStorage
0x7fff31b36000 - 0x7fff31b72fff com.apple.DebugSymbols (195.1 - 195.1) <93BEC865- 279E-3A6E-A24B-487C51FF6459> /System/Library/PrivateFrameworks/DebugSymbols.framework/Versions/A/DebugSymbols
0x7fff31b73000 - 0x7fff31c30fff com.apple.CoreSymbolication (12.2 - 64541.4) <D9F608E4- 437D-3A1C-83E7-7BD6CF830589> /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSymbolication
0x7fff32ab1000 - 0x7fff32b14fff com.apple.framework.Apple80211 (17.0 - 1728) <E5DB3BA3-DA6B-33B2-A111-852B5041DE4E> /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Apple80211

0x7fff32b15000 - 0x7fff32c67fff com.apple.CoreWiFi (3.0 - 341) <4B9C6F89-74B7-35F0- AC61-7ECD993B8139> /System/Library/PrivateFrameworks/CoreWiFi.framework/Versions/A/CoreWiFi
0x7fff32ed4000 - 0x7fff32ee3fff com.apple.xpc.RemoteServiceDiscovery (1.0 - 2038.40.38) <7F2CB942-65FF-3A6B-AA1E-717BB18DEE80> /System/Library/PrivateFrameworks/RemoteServiceDiscovery.framework/Versions/A/ RemoteServiceDiscovery
0x7fff32ee4000 - 0x7fff32efbfff com.apple.xpc.RemoteXPC (1.0 - 2038.40.38) <118A75E2- 58FB-3E30-B0F0-064E42BD3A9B> /System/Library/PrivateFrameworks/RemoteXPC.framework/Versions/A/RemoteXPC
0x7fff32f43000 - 0x7fff32f46fff com.apple.help (1.3.8 - 71) <FFC118DA-4302-3A44-B166- 8810A045B492> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ Help.framework/Versions/A/Help
0x7fff32f47000 - 0x7fff32f4efff com.apple.EFILogin (2.0 - 2) <4EE8F2C6-F75A-3545-93C7- 9EC7DB7E4337> /System/Library/PrivateFrameworks/EFILogin.framework/Versions/A/EFILogin
0x7fff32f4f000 - 0x7fff32f5afff libcsfde.dylib (554) <DB193672-8501-3F7B-BEB4- 4F59C8887512> /usr/lib/libcsfde.dylib
0x7fff33184000 - 0x7fff33184fff com.apple.ApplicationServices (48 - 50) <BF6B5DC5- 22AF-3926-8D21-7F4CFDB03644> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices
0x7fff33484000 - 0x7fff33484fff libHeimdalProxy.dylib (79) <D67CF959-658D-3E1C-9900- 5DC0A507D02A> /System/Library/Frameworks/Kerberos.framework/Versions/A/Libraries/ libHeimdalProxy.dylib
0x7fff33537000 - 0x7fff33537fff com.apple.audio.units.AudioUnit (1.14 - 1.14) <106AE4DA-6F73-393B-889D-5D048ECDDDE1> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
0x7fff344ef000 - 0x7fff3453ffff com.apple.ChunkingLibrary (334 - 334) <996DC3E2-CC2E- 376D-9A31-2D5093C078C5> /System/Library/PrivateFrameworks/ChunkingLibrary.framework/Versions/A/ChunkingLibrary
0x7fff34f35000 - 0x7fff34f38fff com.apple.Cocoa (6.11 - 23) <D673DE75-8885-39F1-9847- 81D602E69229> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
0x7fff3634f000 - 0x7fff3636afff com.apple.openscripting (1.7 - 190) <EA384453-7A25- 36CD-B6D5-FE58AB36334B> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ OpenScripting.framework/Versions/A/OpenScripting
0x7fff3636b000 - 0x7fff3636efff com.apple.securityhi (9.0 - 55008) <E11B58BC-4B25-3991- B243-C2A5C797DE60> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/ Versions/A/SecurityHI
0x7fff3636f000 - 0x7fff36372fff com.apple.ink.framework (10.15 - 227) <1C0F3697-754A- 307E-83B4-2D133D80E7B3> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/ Versions/A/Ink
0x7fff36373000 - 0x7fff36376fff com.apple.CommonPanels (1.2.6 - 101) <50B28EBC-6852- 3843-8BB6-93800D8EE7D6> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ CommonPanels.framework/Versions/A/CommonPanels
0x7fff36377000 - 0x7fff3637efff com.apple.ImageCapture (1707 - 1707) <F8BA52A6-2076- 3439-9F02-8EFABDFADC87> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ ImageCapture.framework/Versions/A/ImageCapture

0x7fff391d9000 - 0x7fff391dcfff com.apple.OSAServicesClient (1.0 - 1) <7193D631-42B0- 3F65-AD4D-161DF0DC2633> /System/Library/PrivateFrameworks/OSAServicesClient.framework/Versions/A/ OSAServicesClient
0x7fff3c709000 - 0x7fff3c70cfff com.apple.print.framework.Print (15 - 271) <47A826E5- 8E5F-3B20-9131-58D9F94C58B6> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/ Versions/A/Print
0x7fff3c70d000 - 0x7fff3c710fff com.apple.Carbon (160 - 164) <DE2A89F4-03DF-3E98- 8C90-48C095DA3FDC> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
0x7fff3c98b000 - 0x7fff3c9aafff com.apple.private.SystemPolicy (1.0 - 1) <10BDB417- 5EFA-348A-9DB7-154F4BC4136D> /System/Library/PrivateFrameworks/SystemPolicy.framework/Versions/A/SystemPolicy
0x7fff3d2cf000 - 0x7fff3d2dafff com.apple.MallocStackLogging (1.0 - 1) <F9CA682E- FCC0-371F-90EA-B5CE51ABF8AC> /System/Library/PrivateFrameworks/MallocStackLogging.framework/Versions/A/ MallocStackLogging
0x7fff3d2f0000 - 0x7fff3d302fff libmis.dylib (274.40.12) <CF45C71D-4237-369F-9FE1- 91C0B9C77C06> /usr/lib/libmis.dylib
0x7fff40a6c000 - 0x7fff40a75fff com.apple.IOAccelMemoryInfo (1.0 - 1) <3D55F378-81F0- 3117-BD6A-5DFCED8C2134> /System/Library/PrivateFrameworks/IOAccelMemoryInfo.framework/Versions/A/ IOAccelMemoryInfo
0x7fff40ea4000 - 0x7fff40ec2fff libCGInterfaces.dylib (543) <B19C6E0A-C7B5-3CCC- A77F-9751CC30523E> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/ Versions/A/Libraries/libCGInterfaces.dylib
0x7fff4778b000 - 0x7fff477d9fff com.apple.osanalytics.OSAnalytics (1.0 - 1) <5B713D10- 3346-3AAD-A977-7095220E3C03> /System/Library/PrivateFrameworks/OSAnalytics.framework/Versions/A/OSAnalytics
0x7fff5125b000 - 0x7fff512ecfff com.apple.Symbolication (12.2 - 64541.5.1) <640AAE2D- 353D-3009-A7A2-55AE3F965398> /System/Library/PrivateFrameworks/Symbolication.framework/Versions/A/Symbolication
0x7fff68f5e000 - 0x7fff68f62fff libmetal_timestamp.dylib (31001.152) <A294D124-55AA- 3C01-B873-225B5717923D> /System/Library/PrivateFrameworks/GPUCompiler.framework/Versions/31001/Libraries/ libmetal_timestamp.dylib
0x7fff6b3cc000 - 0x7fff6b3d2fff libCoreFSCache.dylib (177.22) <F2BD275B-0979-3426- BC9D-60C22E4FDE1C> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreFSCache.dylib
0x7fff6b3d3000 - 0x7fff6b3d7fff libCoreVMClient.dylib (177.22) <57E480B5-F430-3150- A5D9-D255A2F761E5> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib
0x7fff6b3d8000 - 0x7fff6b3e7fff com.apple.opengl (18.0.50 - 18.0.50) <245D7013-B161- 397D-9989-500B639ECDF3> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
0x7fff6b3e8000 - 0x7fff6b3eafff libCVMSPluginSupport.dylib (18.0.50) <58937D53-04AE- 36EA-AF04-A2C6EBD8D8EE> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dy lib

0x7fff6b3eb000 - 0x7fff6b3f3fff libGFXShared.dylib (18.0.50) <8BCF166B-60FA-3321- 83BB-24A3527B60A3> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib
0x7fff6b3f4000 - 0x7fff6b427fff libGLImage.dylib (18.0.50) <BD69E573-1813-3078-BF27- C9183B515647> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib
0x7fff6b428000 - 0x7fff6b464fff libGLU.dylib (18.0.50) <21591978-F81A-3C62-9281- CD0ACDF8EEAC> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
0x7fff6b5fa000 - 0x7fff6b604fff libGL.dylib (18.0.50) <D2379B83-F70E-375A-AD7A- B612D767ABE6> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
0x7fff6ca3b000 - 0x7fff6ca93fff com.apple.opencl (4.5 - 4.5) <4387AA57-D726-3378-8376- E5D6813E219F> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL
0x7fff6d5dd000 - 0x7fff6d795fff com.apple.AMDMTLBronzeDriver (4.0.47 - 4.0.0) <CF956E47-6014-3922-B149-169F25B54E44> /System/Library/Extensions/AMDMTLBronzeDriver.bundle/Contents/MacOS/ AMDMTLBronzeDriver
0x7fff6dd13000 - 0x7fff6dd1afff com.apple.agl (3.3.4 - AGL-3.3.3) <9A62C140-2B9B-341C- A4F2-B90BB88DE758> /System/Library/Frameworks/AGL.framework/Versions/A/AGL
0x7fff783a5000 - 0x7fff783acfff libRosetta.dylib (203.1.3) <5EC28751-3BE8-3BB7-9DBE- 305225CBD41B> /usr/lib/libRosetta.dylib
External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 0 thread_create: 0 thread_set_state: 0
Calls made by this process: task_for_pid: 0 thread_create: 0 thread_set_state: 0
Calls made by all processes on this machine: task_for_pid: 9855
thread_create: 0
thread_set_state: 0
VM Region Summary:
ReadOnly portion of Libraries: Total=742.1M resident=0K(0%) swapped_out_or_unallocated=742.1M(100%)
Writable regions: Total=131.4M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=131.4M(100%)
======= ======= 128K 1
REGION TYPE =========== Accelerate framework Activity Tracing
256K 5760K
72K 5948K
12K
1
6
4
11
CG backing stores CG image CoreAnimation CoreGraphics
2
VIRTUAL REGION
SIZE COUNT (non-coalesced)

CoreUI image data
Dispatch continuations
Foundation 16K Kernel Alloc Once 8K MALLOC 76.1M MALLOC guard page 32K STACK GUARD 56.0M Stack 11.0M 7 VM_ALLOCATE 816K __CTF 759 1 __DATA 14.1M __DATA_CONST 11.7M __DATA_DIRTY 540K __FONT_DATA 4K __LINKEDIT 490.4M __OBJC_RO 61.0M __OBJC_RW 2468K
11 1
59
__TEXT __UNICODE mapped file shared memory =========== TOTAL
251.7M 588K
1480K 32.0M
96.5M 40K
1
1
8 7
25
170 98
1 19 1
2 321
1 34
322
4 ======= =======
1.1G 1119
Model: iMac18,3, BootROM 429.50.1.0.0, 4 processors, Quad-Core Intel Core i5, 3,5 GHz, 16 GB, SMC 2.41f2
Graphics: kHW_AMDRadeonPro575Item, Radeon Pro 575, spdisplays_pcie_device, 4 GB Memory Module: BANK 0/DIMM0, 4 GB, DDR4 SO-DIMM, 2400 MHz, 0x802C, 0x344154463531323634485A2D3247334232202020
Memory Module: BANK 0/DIMM1, 4 GB, DDR4 SO-DIMM, 2400 MHz, 0x198, 0x393930353731312D3031352E4130304720202020
Memory Module: BANK 1/DIMM0, 4 GB, DDR4 SO-DIMM, 2400 MHz, 0x802C, 0x344154463531323634485A2D3247334232202020
Memory Module: BANK 1/DIMM1, 4 GB, DDR4 SO-DIMM, 2400 MHz, 0x198, 0x393930353731312D3031352E4130304720202020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x16F), Broadcom BCM43xx 1.0 (7.77.111.1 AirPortDriverBrcmNIC-1669)
Bluetooth: Version 8.0.1f5, 3 services, 27 devices, 1 incoming serial ports
Network Service: Ethernet, Ethernet, en0
Serial ATA Device: APPLE HDD ST1000DM003, 1 TB
USB Device: USB 3.0 Bus
USB Device: Backup+ Hub
USB Device: Expansion Desk
USB Device: Backup+ Hub BK
USB Device: USB3.1 Hub
USB Device: USB2.0 Hub
USB Device: USB Keyboard
USB Device: Bluetooth USB Host Controller
USB Device: FaceTime HD Camera (Built-in)
USB Device: USB Optical Mouse
USB Device: USB2.1 Hub
USB Device: MT1956

USB Device: Backup+ Hub
USB Device: USB-SATA Bridge
USB Device: USB3.0 Hub
Thunderbolt Bus: iMac, Apple Inc., 41.4"	Jammy
17734	Error on starting the new machine	VirtualBox 5.2.10	2018-05-05T01:22:57Z	2018-05-05T22:49:17Z	2018-05-05T22:49:17Z	I installed virtualbox and set all the settings and installed the extension pack. Then created my first vb with vhd and 32 bit linux os.	greybeard74
18860	Error opening	VirtualBox 5.2.6	2019-08-21T16:57:34Z	2019-08-21T18:35:56Z	2019-08-21T18:35:56Z	"Runtime error opening 'C:\Users\Luis Angel\VirtualBox VMs\mariaxp\mariaxp.vbox' for reading: -102 (File not found.).
F:\tinderbox\win-5.2\src\VBox\Main\src-server\MachineImpl.cpp[739] (long __cdecl Machine::i_registeredInit(void)).
Result Code: 
E_FAIL (0x80004005)
Componente: 
MachineWrap
Interfaz: 
IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}
"	Dilema
19699	Error opening virtual box after upgrade to 6.1	VirtualBox 6.1.10	2020-07-03T14:48:01Z	2020-07-03T14:48:01Z	2020-07-03T14:48:01Z	"Hello,

After upgrade to 6.1 i can no longer open my virtual box image that was working perfectly before this version. How can i make my Virtual box working again with the new version ? 

I will add the logfilesthat were created. 

Thanks"	Johan1974
20459	Error ReLauching VirtualBox VM Process 5	VirtualBox 6.1.22	2021-07-14T06:54:21Z	2021-07-14T06:54:21Z	2021-07-14T06:54:21Z	"Every time I try to launch my windows iso, the message (Error ReLauching VirtualBox VM Process 5)

Error code : 
E_FAIL (0x80004005)
Component : 
MachineWrap
Interface: 
IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}"	William Monette
20195	error relaunching Virtual Box VM Process	VirtualBox 6.1.18	2021-02-16T07:33:09Z	2021-02-16T07:33:09Z	2021-02-16T07:33:09Z	"The virtual machine 'Windows 10' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\HP\VirtualBox VMs\Windows 10\Logs\VBoxHardening.log'.

Return Code (RC): 
E_FAIL (0x80004005)
Component: 
MachineWrap
Interface: 
IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}
"	walec73
14269	Error relaunching VirtualBox VM process: 5	VirtualBox 5.1.8	2015-07-13T18:47:55Z	2020-10-05T21:05:38Z	2020-10-05T21:05:38Z	Unable to run guest VM using latest OVM 5.0 release. See attached screenshot for details.	sombra
14048	Error Starting Virtual Machine (was Previously Working)	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
14037	Error starting virtual machine after upgrading to 4.3.26 The virtual machine 'Vista' has terminated unexpectedly during startup with exit code 1 (0x1).  E_FAIL (0x80004005)	VirtualBox 4.3.26	2015-04-09T07:23:28Z	2015-04-09T07:23:28Z	2015-04-09T07:23:28Z	"Hello, since I upgraded to 4.3.26 (but I tried even using 4.3.27), when I start a VM I got the following error:

Apertura di una sessione per la Macchina Virtuale Vista non riuscita.

The virtual machine 'Vista' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\Daniela\VirtualBox VMs\Vista\Logs\VBoxStartup.log'.

Codice 'uscita: E_FAIL (0x80004005)
Componente: Machine
Interfaccia: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

This is the host machine:
Microsoft Windows 7 Professional 
6.1.7601 Service Pack 1 build 7601
SAMSUNG ELECTRONICS CO., LTD.
X86-based PC
x64 Family 6 Model 58 Stepping 9 GenuineIntel ~2400 Mhz

Please, see the attached file for startup log

Best regards"	shinnai
14460	Error starting VM - E_FAIL 0x80004005 SessionMachine	VirtualBox 5.0.2	2015-08-17T17:23:05Z	2015-08-17T17:30:54Z	2015-08-17T17:30:54Z	"I am getting virtualbox error ""Failed to open a session for the virtual
machine xxxxx.""  The VM session was aborted. See screenshot attachment
for complete error. 

This happens when I start any virtual machine just after launching the
virtualbox manager.  I try the start a second and sometimes third time
and the machine will launch and function normally.  When it shuts down,
I also get an error but everything is being saved inside the machine.

I am running Windows 10 Pro (64-bit) on an HP desktop (I7 processor
with 32gb of memory).  This only started after upgrading to version 5
of virtualbox.  I have tried the original 5.0 version, the 5.01 test
version and am now on 5.02 r102096.  The guest machine doesn't seem
to matter - they all receive the error.  Guests include Windows 10
Enterprise, Windows 2008 R2 server, Windows 7, and Windows 2003 R2
server.

Attached is the screenshot of the error and a clean log (cleared before
starting virtualbox and getting error)."	_Dale_
11860	error starting VM in batch when the path to VM have Unicode characters	VirtualBox 4.2.12	2013-06-13T04:57:57Z	2013-06-13T07:02:18Z	2013-06-13T07:02:18Z	"When I start <<VirtualBox.exe --startvm ""path_to_VM"">> it works only if path_to_VM doesn't have some Unicode characters (specific to a language, like the u with 2 dots above from Munchen).
It shows an error message saying that the VM was not found and it displays the path with those Unicode characters doubled into some strange ones.
If I start <<VBoxManage.exe  --startvm ""path_to_VM""/UUID>> or <<VirtualBox.exe --startvm UUID>> it works with any combination.
But I prefer using <<VirtualBox.exe --startvm ""path_to_VM"">> so could you please fix it...?
Thank you.

Regards, Cosmin"	Cosmin
17836	ERROR TO OPEN VB	VirtualBox 5.2.12	2018-06-22T17:30:20Z	2018-06-22T20:51:18Z	2018-06-22T20:51:18Z	"I AM RECEIVING THIS MESSAGE, EVERY TIME i TRY TO RUN VB:

""Error in supR3HardNtChildWaitFor
Timed out after 2001 md waiting for child request #0 (PurifyChildAndCloseHandles).
Plea try reinstallin VirtualBox.
where: supR3HardNtChildWaitFor what: 5 Unknown Status 258 (0x102) (258) - Unknown Status 258 (0x102)""

So I tried to reinstal but it's the same error.

What's happening???"	alaz
15690	Error trying to run	VirtualBox 5.1.2	2016-07-26T08:12:23Z	2016-08-11T13:27:37Z	2016-08-11T13:27:37Z	It runs if Vista compatibility mode is checked, but still gives error running the machine.	ptnull
18179	Error unclear when cloning and default vm folder is not available	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
18109	Error when drag-and-drop zero length files from guest to host	VirtualBox 5.2.20	2018-11-05T21:50:45Z	2018-11-06T06:41:33Z	2018-11-06T06:41:33Z	"Version: 5.2.20, 5.2.18
Host: Windows 7 SP1
Guest: Windows 7 SP1 RU/EN, Windows XP SP3 RU
Guest additions: installed according to VirtualBox version

Error occurs when dragging zero length file from guest to host:
{{{
Drag and drop operation from guest to host failed.
Current drop operation still in progress.
Result Code: E_FAIL (0x80004005)
Component: GuestDnDSourceWrap
Interface: IGuestDnDSource {dedfb5d9-4c1b-edf7-fdf3-c1be6827dc28}
Callee: IDnDSource {d23a9ca3-42da-c94b-8aec-21968e08355d}
}}}

Same error occurs when dragging folder with zero-length file from guest to host.

After that error any other drag-and-drop operation even with non-enpty files fails with error:
{{{
Drag and drop operation from guest to host failed.
Another drop operation already is in progress.
Result Code: E_INVALIDARG (0x80070057)
Component: GuestDnDSourceWrap
Interface: IGuestDnDSource {dedfb5d9-4c1b-edf7-fdf3-c1be6827dc28}
Callee: IDnDSource {d23a9ca3-42da-c94b-8aec-21968e08355d}
}}}

Steps to reproduce:
1) Install guest Windows 7 or Windows XP (any language in to the VB) 
2) Install VB Additions
3) Turn on drag-and-drop from guest to host (or bidirectional)
4) Drag and drop any non-zero-length file to check that it works
5) Create any new empty file (for ex. new notepad document)
6) Drag it from guest to host
7) Get error

It is possible to ""reset"" the satuation by trying to drag any file from host to guest. May be not immediately, may be couple of times.
I did not find exact scenario. 
Sometimes attempts to drag files from host to guest after error leads to guest interface partially hang. In that case shutdown procedure asks to forcibly close VBoxTrayDnDWnd.

Additional: errors appear in host log files, not in guest.
"	yumashka
20736	Error when i want use a ubuntu machine	VirtualBox 6.1.30	2021-12-18T20:28:51Z	2021-12-18T20:28:51Z	2021-12-18T20:28:51Z	"Hello, 

I'm on ubuntustudio and I use virtualbox 6.1.30. When I want to virtualize a ubuntu machine, i have an error message (file)
If i try to executing '/sbin/vboxconfig, i have an error , i have the passworf window which open indefinitely. "	moijeux
19284	Error when opening vscode file menu	VirtualBox 6.1.2	2020-02-03T08:14:44Z	2020-02-03T08:46:38Z	2020-02-03T08:46:38Z	"
The instruction 0x00000000 referenced memory at 0x00000000. The memory could not be written. Click OK to terminate the program"""	china_liu
19656	Error when starting VBoxSVC on alpine linux (MUSL)	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
17699	Error when starting VM after a snashot restore	VirtualBox 5.2.10	2018-04-19T12:43:17Z	2018-04-26T08:24:17Z	2018-04-26T08:24:17Z	"After upgrading to 5.2.10 r122088, i've been able to start my VMs seamlessy as usual, until I tried to restore some snapshots. The restored VMs don't start, I get instead this error message:
{{{
Failed to open a session for the virtual machine NAMEOFVM.

The VM session was aborted.

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: SessionMachine
Interface: ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}
}}}

On the second attempt to run it, the VMs to start fine.
Until I revert snapshot again, then I seen the error on every first attempt to start it."	efayol
14737	Error When starting Windows 1.01 (VINF_EM_TRIPLE_FAULT)	VirtualBox 5.0.8	2015-10-24T08:35:46Z	2015-10-28T14:29:34Z	2015-10-28T14:29:34Z	"When i try to start the VM it goes to the boot screen and MS-DOS EXCUTIVE and then crashes(Works fine on VBOX4)
"	po
20164	Error while trying to use VM for SAS University Studio	VirtualBox 6.0.22	2021-01-30T04:31:00Z	2021-01-30T04:31:00Z	2021-01-30T04:31:00Z	"This is the description of the error

Fallo al abrir una sesión para la máquina virtual SAS University Edition.

The virtual machine 'SAS University Edition' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\Eduardo Sandoval\VirtualBox VMs\SAS University Edition\Logs\VBoxHardening.log'.

Código resultado: E_FAIL (0x80004005)
Componente: MachineWrap
Interfaz: IMachine {5047460a-265d-4538-b23e-ddba5fb84976}
"	EDUARDO SANDOVAL HERNANDEZ
14336	Error with copyfrom	VirtualBox 5.0.0	2015-07-28T14:13:54Z	2017-11-04T18:24:19Z	2017-11-04T18:24:19Z	"I just recently, upgraded to the latest version of virtual box version 5.0.0 r101573 and I cannot get the copyfrom command to work.

Here is the command I'm trying to run and the resultant error I get:
{{{
C:\Program Files\Oracle\VirtualBox>VBoxManage.exe guestcontrol
    ""Windows Server 2008 x64"" copyfrom
    --target-directory ""C:\BuildLogs\Install Log - Win 7.txt""
    ""C:\ProgramData\MyApp\Installer.txt""
    --username ""TestUser"" --password ""111111"" --recursive --verbose

VBoxManage.exe: error: File copy failed
VBoxManage.exe: error: Unable to write ""C:\ProgramData\MyApp\Installer.txt"" to ""C:\BuildLogs/Install Log - Win 7.txt
"": Access denied
VBoxManage.exe: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005), component G
uestSessionWrap, interface IGuestSession
VBoxManage.exe: error: Context: ""int __cdecl gctlCopyFileToDest(struct COPYCONTE
XT *,const char *,const char *,enum gctlCopyFlags)"" at line 2162 of file VBoxMan
ageGuestCtrl.cpp
VBoxManage.exe: error: Unable to write ""C:\ProgramData\MyApp\Installer.txt"" to ""C:\BuildLogs/Install Log - Win 7.txt
"": Access denied.
VBoxManage.exe: error: Error processing ""C:\ProgramData\MyApp\Installer.txt"", rc=VERR_GENERAL_FAILURE
}}}"	littlebuck144
19085	Error with Windows 10 Enterprise 1903 build 18362.476 and VirtualBox v6.0.14 error	VirtualBox 6.0.14	2019-11-14T04:21:10Z	2019-11-15T05:24:01Z	2019-11-15T05:24:01Z	"my MS Windows is in Portuguese-BR!
my user Windows: ""PCuserWin"" -> is a administrator, per default!
Then, all my software are installed in this profile!
My user Administrator, stay disabled, per default!

I use VirtualBox since v5. My pc is:
- CPU Intel i7 4770K
- RAM 8GB Corsair Vengeance
- VGA Gigabyte nVidia GTX650 Ti Boost 2GB
- SSD 120GB Corsair to Operating System MSWindows
- HDD 1TB free to my virtual machines (normally 2 or 3 for test, and later I delete it)

My antivirus Kaspersky Internet Security v2020, never got in the way of installing VirtualBox or virtual machines!

I do not see any changes on my computer so this new error appears!
-------------------

Sometimes i had this problem when try install ""Package"" as normal user (no Admin) as always:
- all my downloads stay (always) in Drive ""D"" (include VirtualBox + Package)
- my Drive ""C"" only MSWindows, Kaspersky, RAD Studio 10.3.2, and other utilities -> normally, only apps to work! No games!

to avoid this error, I try install it using run VirtualBox app ""As Administrator"", or, I copy the file ""Oracle_VM_VirtualBox_Extension_Pack-6.0.14.vbox-extpack"" to into my folder VirtualBox on Disk""C"". then, works! 


----------- Screen error #1: Fail on install Extension Package  -----------
Falha ao instalar o Pacote de Extensões D:/Downloads/__Utils/VirtualBox/Oracle_VM_VirtualBox_Extension_Pack-6.0.14.vbox-extpack.

The installer failed with exit code 1: VBoxExtPackHelperApp.exe: error: Failed to rename the temporary directory to the final one: VERR_ACCESS_DENIED ('C:\MeusProgs\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack-_-inst-1644' -&gt; 'C:\MeusProgs\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack')


rcExit=1.

Código de Resultado: E_FAIL (0x80004005)
Componente: ExtPackManagerWrap
Interface: IExtPackManager {70401eef-c8e9-466b-9660-45cb3e9979e4}
---------------------------------


Now, using same MSWindows 1903 build 18362.476, i had another error when trying create new VM to test new ISO MSWindows 1909 (downloaded from Microsoft directly):

---------- Screen error #2: Fail to the open a session to ... ----------
Falha ao abrir uma sessão para a máquina virtual Windows101909. <-- my VM

 (VERR_NEM_MISSING_KERNEL_API).

VT-x is not available (VERR_VMX_NO_VMX).

Código de Resultado: E_FAIL (0x80004005)
Componente: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
--------------------------------------------------------------

But my ""VIRTUALIZATION"" always is activated on BIOS and MSWindows, since always!  I never had this error before.

I always create my VM with 2GB and 1 (or 2 cpu virtual), and 80GB disk.
I never use 2 VM in same time.
Later test the new system, I delete my VM. Then, i have many disk space!

"	Emailx45
14455	Error writing to a file froma SMB share - shared through VirtualBox	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
17936	ERROR: could not insert 'vboxdrv': Exec format error	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
6930	Error: Failed to open a session for the virtual machine - session was closed before any attempt to power it on	VirtualBox 3.2.4	2010-06-08T02:01:11Z	2018-02-15T16:44:13Z	2018-02-15T16:44:13Z	"I upgraded VirtualBox to version 3.2.2-62321 on a Windows 7 Ultimate 64-bit host.
Everything was working fine with the previous version 3.1.8.

Since the upgrade to Virtualbox to version 3.2.2-62321, when I start any of my virtual machines I get the following error:

{{{
Failed to open a session for the virtual machine MyMachineName.

The VM session was closed before any attempt to power it on.

Details:

Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: ISession {12f4dcdb-12b2-4ec1-b7cd-ddd9f6c5bf4d}
}}}

At the time of the upgrade, 11 guests were in a saved state and not powered off, 1 guest was powered off.

Attempting to start any of the guests gives the error and in no case does a log get created.

I have since installed VirtualBox 3.2.4, but that made no difference.

I posted the issue on the Forums: [http://forums.virtualbox.org/viewtopic.php?f=6&t=31778&start=0]

Regards,
Leigh"	Leigh Wardle
21454	Error: vmnet_start_interface returned 1001	VirtualBox-7.0.6	2023-02-02T07:25:26Z	2023-02-02T07:49:33Z	2023-02-02T07:49:33Z	"Unable to use host only network with 192.0.2.0/24 network

00:00:01.271232 VMNet: Host network with mask 255.255.255.0 (192.0.2.1 to 192.0.2.200)
00:00:01.271907 VMSetError: /Users/vbox/tinderbox/mac-rel/src/VBox/Devices/Network/DrvVMNet.m(650) int drvVMNetConstruct(PPDMDRVINS, PCFGMNODE, uint32_t); rc=VERR_INVALID_PARAMETER
00:00:01.271911 VMSetError: Error: vmnet_start_interface returned 1001
00:00:01.272118 VMSetError: /Users/vbox/tinderbox/mac-rel/src/VBox/Devices/Network/DevE1000.cpp(8287) int e1kR3Construct(PPDMDEVINS, int, PCFGMNODE); rc=VERR_INVALID_PARAMETER
00:00:01.272121 VMSetError: Failed to attach the network LUN
00:00:01.272141 PDM: Failed to construct 'e1000'/1! VERR_INVALID_PARAMETER (-2) - Invalid parameter.

% cat /etc/vbox/networks.conf
* 192.0.2.0/24
* 0.0.0.0/0 ::/0"	urbanchef
15193	Errors when I start a virtual machine (Virtual Box Version 5.0.14 r105127, Windows 8 - 64 bit)	VirtualBox 5.0.14	2016-03-02T10:40:25Z	2020-07-02T11:48:06Z	2020-07-02T11:48:06Z	"I installed Virtual Box Version 5.0.14 r105127 on Windows 8 - 64 bit

An error dialog appears when I start a virtual machine.
The error message is:


{{{
Failed to open a session for the virtual machine MacOSXYO.

The virtual machine 'MacOSXYO' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\haipv87\VirtualBox VMs\New group\MacOSXYO\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}
}}}


The error log is with content:

{{{
f18.940: supR3HardNtViCallWinVerifyTrustCatFile: WinVerifyTrust => 0x0; cat='C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Microsoft-Windows-SKU-Foundation-Package-avcore~31bf3856ad364e35~amd64~~6.2.9200.16384.cat'; file='\Device\HarddiskVolume2\Windows\System32\winmmbase.dll'
f18.940: supR3HardNtViCallWinVerifyTrustCatFile -> 0 (org 22900)
f18.940: supR3HardenedWinVerifyCacheProcessWvtTodos: 0 (was 22900) fWinVerifyTrust=1 for '\Device\HarddiskVolume2\Windows\System32\winmmbase.dll'
f18.940: Fatal error:
f18.940: supR3HardenedMainGetTrustedMain: LoadLibrary ""C:\Program Files\Oracle\VirtualBox/VirtualBox.dll"" failed, rc=1790
618.c3c: supR3HardNtChildWaitFor[2]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 984 ms, the end);
fb0.f10: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 1350 ms, the end);
}}}


I found some people has the similar problem, but all suggestion not work with my case.

Best Reguard.
"	haiphungvan
21182	"EventID 15, ""The device driver for the Trusted Platform Module (TPM) encountered a non-recoverable error in the TPM hardware, which prevents TPM services (such as data encryption) from being used. For further help, please contact the computer manufacturer"""	VirtualBox-7.0.2	2022-10-21T12:30:43Z	2022-11-30T05:22:35Z	2022-11-30T05:22:35Z	"Each Windows 11 22H2 boot generates six of these TPM errors.

Please fix."	Artem S. Tashkinov
20750	Examples to control VM via COM do not work	VirtualBox 6.1.30	2021-12-26T15:17:09Z	2021-12-26T15:17:09Z	2021-12-26T15:17:09Z	"Hi!

I have a VM named Win8.1, running on a Win10 host, which can be controlled manually via the VM manager.

Now, I'd like to control it via COM, but even the examples shipped with the SDK do not work.


== Python  ==

The file SDKRef.pdf lists the following Python code in section 2.3.1.
I just changed the name of the VM  to Win8.1 and added two print commands:


{{{
import win32com.client
vbox = win32com.client.Dispatch(""VirtualBox.VirtualBox"")
session = win32com.client.Dispatch(""VirtualBox.Session"")
mach = vbox.findMachine(""Win8.1"")
print(""Machine.State: "", mach.State) 
print(""Machine SnapshotFolder: "", mach.SnapshotFolder)
progress = mach.launchVMProcess(session, ""gui"", """")
progress.waitForCompletion(-1)
}}}

The output is:
{{{
Machine.State:  1
Machine SnapshotFolder:  C:\VMs\Win8.1\Snapshots
Traceback (most recent call last):
  File ""C:\Users\webers\Desktop\vbox.py\vbox.py"", line 8, in <module>
    progress = mach.launchVMProcess(session, ""gui"", """")
  File ""<COMObject <unknown>>"", line 2, in launchVMProcess
pywintypes.com_error: (-2147352571, 'Typenkonflikt.', None, 3)
}}}

The output of the two print commands is correct, so COM in general works, but launching the VM fails with error ""Typenkonflikt"" (this is german, so it's not a Python error, but comes from my german VM installation or the german Win10 host)

 
== VBS ==

In sdk\bindings\mscom\vbs\sample, there is this listing, where I only inserted my VM name:

{{{
' $Id: vboxinfo.vbs 135976 2020-02-04 10:35:17Z bird $
'' @file
' ???
'

'
' Copyright (C) 2009-2020 Oracle Corporation
'
' This file is part of VirtualBox Open Source Edition (OSE), as
' available from http://www.virtualbox.org. This file is free software;
' you can redistribute it and/or modify it under the terms of the GNU
' General Public License (GPL) as published by the Free Software
' Foundation, in version 2 as it comes in the ""COPYING"" file of the
' VirtualBox OSE distribution. VirtualBox OSE is distributed in the
' hope that it will be useful, but WITHOUT ANY WARRANTY of any kind.
'

Sub Print(str)
   Wscript.Echo str
End Sub

Sub StartVm(vb, mach)
  Dim session, progress

  Set session = CreateObject(""VirtualBox.Session"")
  Set progress = vb.openRemoteSession(session, mach.id, ""gui"", """")
  progress.waitForCompletion(-1)
  session.close()
End Sub


Sub StopVm(vb, mach)
  Dim session, progress

  Set session = CreateObject(""VirtualBox.Session"")
  vb.openExistingSession session, mach.id
  session.console.powerDown().waitForCompletion(-1)
  session.close()
End Sub


Sub Main
   Dim vb, mach

   set vb = CreateObject(""VirtualBox.VirtualBox"")
   Print ""VirtualBox version "" & vb.version

   ' Safe arrays not fully functional from Visual Basic Script, as we
   ' return real safe arrays, not ones wrapped to VARIANT and VBS engine
   ' gets confused. Until then, explicitly find VM by name.
   ' May wish to use hack like one described in
   ' http://www.tech-archive.net/Archive/Excel/microsoft.public.excel.programming/2006-05/msg02796.html to handle safearrays
   ' if desperate

   Set mach = vb.findMachine(""Win8.1"")
   Print ""Machine: "" & mach.name  & "" ID: "" & mach.id

   StartVm vb, mach
End Sub

Main

}}}

Again, the print commands work correctly. But then, line 26 (Set progress = vb.openRemoteSession(session, mach.id, ""gui"", """") throws an error:

{{{
Line: 26
Column: 3
Error: The object does not support the proberty or method: 'vb.openRemoteSession'
Code: 800A01B6
Source: Run time error in Microsoft VBScript 
}}}
I've also replaced ""openRemoteSesstion"" by ""launchVMProcess"", with the only result that this is replaced in the error message, too.


----

So, is there any functional example on how to control a VM via COM?"	sweber
16898	excel 2002 crashes upon close on win7 guest in VB 5.1.22 r115126 (Qt5.6.1) on ubuntu 14.04	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
14589	Excel 2013 Freezes in VirtualBox	VirtualBox 5.0.4	2015-09-15T14:51:23Z	2016-01-20T16:24:35Z	2016-01-20T16:24:35Z	"Host system: Mac OS X 10.10.4 on a MacBook8,1 (we've also noticed that it happens on some other models as well)

Whenever working in Excel 2013, attempting to select cells or input formulas into those cells, whether one or multiple, causes Excel to respond extremely slowly. You can replicate this by selecting a single cell, then dragging your mouse in any direction to select multiple cells. You'll notice the delay significantly. We do not notice this issue in Excel 2010.

Lastly, as a University, we deploy VBox 4.3.30 to all our students which where we are having the issue. We've also been testing on VBox 5.0.4 and noticed the same issue."	mrkmiller88
14930	Excel 2016 can't open file in Windows 10	VirtualBox 5.0.10	2015-12-14T12:51:22Z	2015-12-14T13:15:05Z	2015-12-14T13:15:05Z	"Hi,

I've an issue when I'm trying to open a file in Excel 2016 from the Explorer under Windows 10 guest. The error says that ""There was a problem sending the command to the program""

Reading different solutions on windows forums I found that if I disable the hardware acceleration graphics in excel, then the file opens normally.

Also it doesn't matter the location of the file. The error happens either if the file is on a local disk(desktop) or shared folder or network mapped folder.

There are some roundabouts where the file opens fine with hardware accelerated graphics enabled:
- If Excel is already open and open a file from the explorer.
- If I open the file form Excel.

The only scenery is opening a file from explorer while the Excel is closed and HW acc graphics is enabled.

setup:
- Guest: Windows 10 pro x64 using hyper-v and graphics acceleration enabled.
- Host: Windows 7 Enterprise x64 @ Intel i5 4300M
- Virtualbox: 5.0.10 r104061 also tested in 5.0.11 r104675."	David Eduardo Cortelezzi
13931	Excessive processor use	VirtualBox 4.3.24	2015-03-06T13:17:07Z	2015-03-10T09:47:37Z	2015-03-10T09:47:37Z	"Since 4.3.22 or so I noticed that after a while VBox is starting to use a lot of processor power. Everything is OK when it starts but after few hours its 90-100% of one thread and some minor-medium use on other threads (35%-40% of total processor time, i7 4770K, 4 cores 8 threads).

Host is Windows 8.1
Guest is 64bit Ubuntu 14.04

It was initially installed under 4.3.20 and there was no problem. It only appeared recently."	randomwhitetrash
15640	Existing CPU is not supported?	VirtualBox 5.0.26	2016-07-18T22:23:48Z	2016-07-19T18:35:12Z	2016-07-19T18:35:12Z	"I tried to update one of my guess Win 7 to Win 10 and it failed saying it was an unsupported cpu (xeon e5405).

Thing is, Win10 upgrade thinks the CPU is fine on the host computer witch is the same CPU (see screen shoots supplied in zip file with logs)"	isgdre
13754	Export Appliance Dialog does not export selected machine if machine state is changed	VirtualBox 4.3.14	2015-01-12T11:55:49Z	2015-01-12T11:55:49Z	2015-01-12T11:55:49Z	"This is a behaviour report that might be used to correct the usabillity. 
I ran into the following scenario:

1. I started (accidently) my centos host
2. I open the dialog export appliance
3. I see that i cant export a running machine (its ok). The running machine is disabled in the select box. So far so good. '''I left this export selection dialog open! '''
4. I shutdown the running host
5. The formerly running machine is now selectable. So i select it.
6. I press export. The default export filename is right. Then the strange thing happend. The Appliance export starts to export the machine next to the one i want

Long story made short:
Start a host from a list with at least 2 hosts.
Open the export dialog
Stop the host and select it at the exporter dialog
Export the host. It will export the wrong host


I have 4 host machines (3 x centos, 1 x windows)
"	jami
21184	export appliance doesn't remember the destination path	VirtualBox-7.0.2	2022-10-21T13:41:10Z	2022-10-21T13:41:10Z	2022-10-21T13:41:10Z	"I export an appliance and it suggests c:\Users\myname\Documents\machineName.ova and this is expected behavior  I choose another path and export the machine properly.  I export a second machine and it goes back to the first path listed not the last path used.

It seems that most apps that will remember the last path used especially if it was the last one used if the app has not been closed.  Perhaps it should remember between runs but certainly if the app has not been closed.  This is on a win 10 host."	pguin
21194	Export creates a defective .ova file (missing disk image) : cannot import itself back.	VirtualBox 6.1.36	2022-10-22T19:25:08Z	2022-10-22T19:25:08Z	2022-10-22T19:25:08Z	"I am using VBox 6.1.36 under Windows 10 Pro.

When I exported my VM from VirtualBox so that it will be imported to VMWare player, etc., VMware Player, and VMWare workstation pro  does not read the disks correctly (I think). 
The number of disks recognized by VMWare player was about half the numbers of attached disks used in VirtualBox. So the import basically failed.

So I tried to read the exported description back to VirtualBox to see what happens.

To my surprise, VirtualBox reported the following error, which collaborates my observation of missing disks in VMWare Player, etc.

--- Begin Quote: The following the error I saw. It is under Japanese Windows 10 Pro.

{{{


仮想アプライアンス""J:\NEW-VMWARE-DIR\debian64bit-Rev02-transition.ova""のインポートに失敗しました。

The above says, VBox failed to import the *.ova description.


&lt;vbox:Machine&gt; element in OVF contains a medium attachment for the disk image 10bf7d63-35a5-4f22-87fd-b11a1634da12 but the OVF describes no such image.

終了コード : E_FAIL (0x80004005)
コンポーネント: ApplianceWrap
インターフェース: IAppliance {86a98347-7619-41aa-aece-b21ac5c1a7e6}
}}}


---- end quote

The original VM seems to work just fine as far as I use it to develop patches for Thunderbird mail client and other tasks.
"	ci-zephyurus
20335	export VM disk image format: vdi instead of vmdk (ova or different VM container format)	VirtualBox 6.1.22	2021-05-03T07:25:34Z	2022-08-19T16:50:16Z	2022-08-19T16:50:16Z	"One of the best VirtualBox features is the export feature which currently uses the ova format. Unfortunately the ova format (effectively) requires the vmdk disk format.

However, VirtualBox's default disk format is vdi.

(And also most stable, best supported, most VirtualBox's developer preferred disk format?)

VirtualBox doesn't support resizing vmdk.

feature request: please support export of VMs in vdi format. Using/extending the ova standard or inventing VirtualBox's own format.

https://forums.virtualbox.org/viewtopic.php?f=1&t=58460"	adrelanos
7681	extended keyboard layout support under the builtin vnc server (OSE)	VirtualBox 3.2.10	2010-11-03T17:24:59Z	2010-11-05T15:37:48Z	2010-11-05T15:37:48Z	"I've just installed virtualbox-ose 3.2.10 under Gentoo Linux, compiled with VBOX_WITH_VNC option enabled (built in VNC server support).

Running a virtual machine with:
 VBoxHeadless -startvm ... --vnc --vncport ...


Connecting to it via UltraVNC from Windows...
Everything seems to work fine - except some extra keys, like: numeric keys on the right side of the keyboard and local characters (Right Alt + some other letter). 
When running the same VM straight from VirtualBox on the same host (under X/Linux, no VNC) - the keyboard works just fine. 

So, whose fault is this? :)
I've noticed a comment ""Numpad keys - these have to be implemented yet..."" in FramebufferVNC.cpp file, so this might explain numeric pad not working. But what about Right Alt? 

I've also seen the patch, which I believe was the precursor for this vnc-support in OSE VirtualBox (http://old.nabble.com/-PATCH--VirtualBox-headless-VNC-support-by-LibVNCServer-(20100421)-td28324779.html) That patch adds another option: ""--vnckeymap"" to VBoxHeadless, which is missing in the official build. Maybe that's the reason, why it's not working? "	Przemo Jankowski
12084	extension pack	VirtualBox 4.2.18	2013-09-08T17:34:05Z	2013-09-08T17:53:03Z	2013-09-08T17:53:03Z	"Would be nice to see what extension pack is installed for a vM in the ""General"" box of the virtualbox manager field, besides the name and OS.  Have many vm's and some need updating and some dont, always a pain to have to startup the vm to see what the currently installed extension pack version is.

thanks,
art"	ArtZ
16269	Extension pack won't load - Windows 10	VirtualBox 5.1.10	2016-12-06T14:10:02Z	2016-12-07T13:13:54Z	2016-12-07T13:13:54Z	"Failed to install the Extension Pack C:/Downloads/Oracle_VM_VirtualBox_Extension_Pack-5.1.10-112026.vbox-extpack.
{{{
The installer failed with exit code 1: VBoxExtPackHelperApp.exe: error: Failed to rename the temporary directory to the final one: VERR_ACCESS_DENIED ('C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack-_-inst-2592' -&gt; 'C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack')

rcExit=1.

Result Code: E_FAIL (0x80004005)
Component: ExtPackManagerWrap
Interface: IExtPackManager {edba9d10-45d8-b440-1712-46ac0c9bc4c5}
}}}
BTW: I am the Admin on this machine. I have tried running vbox as admisitrator, changing permissions for the folders etc..nothing seems to work.

Help! This is effecting my ability to get the networks going within the VM as well.

"	nsaint
18651	Extention Pack install failed	VirtualBox 6.0.8	2019-05-16T15:33:52Z	2019-06-05T21:38:44Z	2019-06-05T21:38:44Z	"Het is niet gelukt het Extention Pack C:/Users/MAARTE~1.KES/AppData/Local/Temp/Oracle_VM_VirtualBox_Extension_Pack-6.0.8.vbox-extpack te installeren.

The installer failed with exit code 1: VBoxExtPackHelperApp.exe: error: Failed to rename the temporary directory to the final one: VERR_ACCESS_DENIED ('C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack-_-inst-15100' -&gt; 'C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack')


rcExit=1.

Resultaatcode:E_FAIL (0x80004005)
Component:ExtPackManagerWrap
Interface:IExtPackManager {70401eef-c8e9-466b-9660-45cb3e9979e4}

"	MJvK
21264	extremely bad performance- guest:windowsXP host:Mac ventura 13.0.1 (intel)	VirtualBox-7.0.2	2022-11-11T10:45:25Z	2022-11-11T10:45:25Z	2022-11-11T10:45:25Z	"Host upgraded from Mac(intel chip) Monterey to MacOS 13 Ventura, and virtualBox upgraded from 6.1 to 7.02. WindowsXP worked fine on 6.1, but now on 7.02 
a major speed down has occurred(both 32bit and 64). Every action is in slow motion now(even typing).

"	cryingmachine
16119	Extremely slow text display in safe mode boot with Windows Server 2008 guest	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
18150	Extremely sluggish mouse movement on macOS	VirtualBox 5.2.22	2018-11-25T01:57:01Z	2018-11-30T00:56:15Z	2018-11-30T00:56:15Z	"Dear fellow developers!

I've been a long-time user of VirtualBox and I've come to appreciate it for it's stable set of features and the fact that it is cross-platform and thus available anywhere. However, with the latest couple of versions, I've run into some real issues. The visual performance is severely degraded. Also, every time I shut down a virtual machine, VirtualBox crashes. I've done a screen recording: https://youtu.be/ndXNDt9kXAY on an example VM running AndroidX86, but I've also observed this on other Linux VMs.

I first noticed this a few months ago when I got a new machine (MacBook Pro 13"" 2017). I initially assumed it was just a bug from a rushed release, but after a couple new releases nothing has changed and unfortunately, VirtualBox is not really usable like this for me.

Could you please look into it? I'm happy to run any kind of diagnostics or try stuff out.

Greetings,
xfbs"	xfbs
15471	F16C, FMA and BMI extensions are not supported.	VirtualBox 5.0.20	2016-06-01T13:33:01Z	2022-11-10T01:12:57Z	2022-11-10T01:12:57Z	"Programs compiled with the Intel Compiler (C or Fortran) for >= Haswell do not run inside a VirtualBox VM (with AVX2 enabled), and immediately exit with the following error message:

{{{Please verify that both the operating system and the processor support Intel(R) F16C, FMA and BMI instructions.}}}

Of course, you can tell the Intel Compiler to generate fallback code, but then AVX2 instructions aren't used either, and the (scientific) program runs much slower.

The AVX2 support in VirtualBox would be even more useful if it was possible to run AVX2 optimized code produced by the Intel Compiler suite."	KlausErz
17547	Facing NS_ERROR_FAILURE on starting all virtual machines	VirtualBox 5.2.6	2018-02-18T07:16:57Z	2018-02-27T22:22:54Z	2018-02-27T22:22:54Z	"Failed to open a session for the virtual machine Ubuntu.

The virtual machine 'Ubuntu' has terminated unexpectedly during startup with exit code 1 (0x1).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}



Host OS: 10.13.1 MacOS High Sierra

I couldn't find any related log file anywhere. Please help. This is blocking me. Tried reinstall multiple times

Also. tried all the solutions suggested on this thread https://www.virtualbox.org/ticket/16015

Nothing worked.

"	Rakesh Sharma
17899	Fail creating machine via SOAP vboxwebsrv	VirtualBox 5.2.16	2018-07-28T12:01:21Z	2018-07-28T18:03:18Z	2018-07-28T18:03:18Z	Trying to use phpvirtualbox it seems that anything I do when trying to create the disk for a machine, it says the files are already there ( altough they're not ). Further debugging got me to vboxwebsrv which might be the trouble maker.	d3xt3r01
15593	Fail to save machine state	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
19874	Failed to create a host network interface	VirtualBox 6.1.14	2020-09-09T17:04:50Z	2020-09-09T17:12:10Z	2020-09-09T17:12:10Z	"

Dear Staff,

Trying to create another host network adapter, but now for some reason I cant.

Please kindly provide some advice on how can I fix this following issue:

Failed to create a host network interface.

Querying NetCfgInstanceId failed (0x00000002).

Result Code: E_FAIL (0x80004005)

Component: HostNetworkInterfaceWrap
Interface: IHostNetworkInterface {455f8c45-44a0-a470-ba20-27890b96dba9}

Please feel free to contact me at johnnydba777@gmail.com tel.9729007979

Sincerely appreciate you.

Looking forward to hearing back from you soon.

Thank you so much;)








"	jr777
19685	Failed to create a snapshot of the virtual machine: Win Server 2019 guest	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
20874	Failed to create cloud machine	VirtualBox 6.1.32	2022-03-17T22:38:26Z	2022-03-17T22:38:26Z	2022-03-17T22:38:26Z	"Failed to create cloud machine.

launchVM: CloudOCISubnet not set.

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: CloudClientWrap
Interface: ICloudClient {435b66a2-0c60-11ea-a0ea-07eb0d1c4ead}

"	LuckyStar
14296	Failed to create COM object - 0x80040154	VirtualBox 5.0.0	2015-07-18T23:42:50Z	2017-11-28T22:25:24Z	2017-11-28T22:25:24Z	"When I try to run a Virtual Machine I get this error:


{{{
Failed to create the VirtualBoxClient COM object.
The application will now terminate.
Details:
Callee RC: 
REGDB_E_CLASSNOTREG (0x80040154)
}}}

After the error the Virtual Machine will not start.
The current virtual machine is a newly created Windows 8.1, but nothing has been installed yet because it won't launch.
Host is Windows 7 x64 and I am running VirtualBox 5.0.0

I've tried repairing my .net with dotNETfx. I have also tried re-registering the VBoxSvc.
I did a full reinstall and deleted the virtual box folders in C:\Users\UserName\

This error was occurring in the most recent stable 4.x version.

I have a forum thread open here:
https://forums.virtualbox.org/viewtopic.php?f=6&t=68992

I will keep trying to fix it on my own, but any help is appreciated.
"	Circa
15382	Failed to create the host-only adapter	VirtualBox 5.0.20	2016-05-03T12:10:34Z	2016-05-03T12:10:34Z	2016-05-03T12:10:34Z	"I installed VirtualBox-5.0.21-106969-Win.exe and have the following error on my Windows 7 (SP1, 64-bit OS):

C:\Program Files\Oracle\VirtualBox>VBoxManage hostonlyif create
0%...
Progress state: E_FAIL
VBoxManage.exe: error: Failed to create the host-only adapter
VBoxManage.exe: error: Could not operate the communication channel (VERR_BROKEN_
PIPE)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component VirtualBoxWr
ap, interface IVirtualBox
VBoxManage.exe: error: Context: ""enum RTEXITCODE __cdecl handleCreate(struct Han
dlerArg *)"" at line 71 of file VBoxManageHostonly.cpp
"	DimonJaguar
14352	Failed to create the VirtualBox COM object. The application will now terminate. Callee RC: E_INVALIDARG (0x80070057)	VirtualBox 4.3.30	2015-07-30T21:43:49Z	2015-07-30T21:43:49Z	2015-07-30T21:43:49Z	After an upgrde from 4.3.12 to 4.3.30, I get the 'Failed to create the VirtualBox COM object. The application will now terminate. Callee RC: E_INVALIDARG (0x80070057)' error. this error has prevented me from upgrading from 4.3.12 to any later version.	dinsdale
18823	Failed to create the VirtualBox object!	VirtualBox 6.0.10	2019-08-09T15:59:24Z	2019-08-30T12:23:03Z	2019-08-30T12:23:03Z	"Version 6.0.10 r132072 (Qt5.6.3)

I created a test bed on VirtualBox of HA cluster. And I simulate hardware failures in loop. And with very rare probability (I got it on 424 iteration) I get VirtualBox error.


{{{
+ VBoxManage snapshot tuchanka0a restore install
VBoxManage: error: Failed to create the VirtualBox object!
VBoxManage: error: Code NS_ERROR_FACTORY_NOT_REGISTERED (0x80040154) - Class not registered (extended info not available)
VBoxManage: error: Most likely, the VirtualBox COM server is not running or failed to start.

}}}
"	Olleg
12456	Failed to Delete Snapshot	VirtualBox 4.3.4	2013-12-08T23:08:48Z	2020-06-22T17:33:33Z	2020-06-22T17:33:33Z	"Have not been able to delete this snapshots for months. Was really hoping 4.3.4 would fix this.

Failed to delete the snapshot before rvm of the virtual machine new-pferd.
Hard disk 'C:\Users\vern\VirtualBox VMs\new-pferd\new-pferd.vdi' has more than one child hard disk (2).
Result Code: 	E_FAIL (0x80004005)
Component: 	SessionMachine
Interface: 	IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}
"	Eukaryote
6314	Failed to load unit 'HGCM' (VERR_INVALID_PARAMETER) on restoring from saved state	VirtualBox 3.1.4	2010-03-02T16:46:05Z	2019-04-15T08:45:31Z	2019-04-15T08:45:31Z	"On restoring machines from a saved state, I regularly get the error:

Failed to load unit 'HGCM' (VERR_INVALID_PARAMETER)

This occurs after the progress bar for the restore has reached 100%. It does not happen every time I try and restore a machine, but once it does happen, it will happen every time I try and restore that particular machine until I discard the saved state. Therefore, I suspect the problem is occurring while saving the state.

Both host and guest are Windows 7 64-bit. I have yet to experience this on other guest operating systems, but I have not used saved state on other guests as much as the Windows 7 ones, so that may be pure chance.


"	Ravenous Bugblatter Beast
18514	Failed to load unit 'HGCM' (VERR_TOO_MUCH_DATA).	VirtualBox 6.0.4	2019-03-22T06:40:12Z	2019-03-24T03:45:44Z	2019-03-24T03:45:44Z	"Failed to open a session for the virtual machine Ubuntu.

Failed to load unit 'HGCM' (VERR_TOO_MUCH_DATA).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

"	SChernolyas
8970	Failed to load unit 'pgm' (VERR_SSM_INTEGRITY_DECOMPRESSION)	VirtualBox 4.0.8	2011-05-26T16:21:51Z	2020-04-20T18:13:29Z	2020-04-20T18:13:29Z	"Failed to load unit 'pgm' (VERR_SSM_INTEGRITY_DECOMPRESSION)

occurs in v4.08

have a virtual world that is frozen in time with virtualbox guest additions service disabled in vw.  when a restore is done, this error now appears.  used to be able to freeze time on vb machine a few versions back without problems and save its state then restore etc.  unable to do this now without getting an error on the restore state.  very problematic. seems like there's some new check that flags the vw when the date is out of sync possibly and its keeping the vw from being restored.

thank you,
art"	art
19276	Failed to load unit 'pgm' (VERR_SSM_INTEGRITY_DECOMPRESSION).	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
14176	Failed to open a session for the virtual machine	VirtualBox 4.3.28	2015-06-05T02:46:43Z	2020-03-26T16:58:20Z	2020-03-26T16:58:20Z	"*********************************************************
Failed to open a session for the virtual machine Arch.

The virtual machine 'Arch' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'H:\FTP\VirtualBox VMs\Arch\Logs\VBoxStartup.log'.

Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}
********************************************************************
I have tried 4.3.26, 4.3.28 and latest beta 5.0 RC1.
I don't have KB3004394 installed.
To be sure, I have installed KB3024777 as well
I can't start any VM at all.
"	sinancetinkaya
15752	Failed to open a session for the virtual machine	VirtualBox 5.1.2	2016-08-05T15:42:22Z	2019-01-19T21:31:44Z	2019-01-19T21:31:44Z	"Fresh install of Windows 10.
Fresh install of VB 5.1.2
Created a default Ubuntu x64 VM using Ubuntu 16.04 .iso
When I try to start the VM I get the following error:

''Failed to open a session for the virtual machine Xerus.

The virtual machine 'Xerus' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005).  More details may be available in 'C:\Users\brad\VirtualBox VMs\Xerus\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
''

I have created a default Win7 VM and get the same result when trying to start it.
"	slattdog
17753	Failed to open a session for the virtual machine	VirtualBox 5.2.12	2018-05-10T18:11:32Z	2018-05-10T21:29:43Z	2018-05-10T21:29:43Z	"Failed to open a session for the virtual machine ubuntu.
or
Failed to open a session for the virtual machine mint.
or
Failed to open a session for the virtual machine windows10.


Raw-mode is unavailable courtesy of Hyper-V. (VERR_SUPDRV_NO_RAW_MODE_HYPER_V_ROOT).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}"	Seeh
11938	Failed to open a session for the virtual machine (3D-related)	VirtualBox 4.2.16	2013-07-06T17:10:39Z	2016-05-08T21:05:00Z	2016-05-08T21:05:00Z	"I did a search and did not see anyone post this for V4.2.16.  I am getting the following error for *every* attempt to restore a session saved by the ""Save the machine state"" action.  This is for three different Windows virtual machines, and has been happening since at least V4.2.14.  There were no problems in V4.1.18 and I didn't do an update between 4.1.18 and 4.2.14.  There never is any error information.

===8<---

Failed to open a session for the virtual machine Windows Temp.

No error info.

Result Code: NS_ERROR_CALL_FAILED (0x800706BE)
Component: ProgressProxy
Interface: IProgress {c20238e4-3221-4d3f-8891-81ce92d9f913}

===8<---

I did see a post where someone first tried killing orphaned processes before trying a restore, and that did not work for me today.
"	gkholman
19136	Failed to open a session for the virtual machine (hardening error)	VirtualBox 6.0.14	2019-12-06T19:41:41Z	2019-12-08T15:48:53Z	2019-12-08T15:48:53Z	"Hello,

Failed to open a session for the virtual machine Linux 16LTS.

The virtual machine 'Linux 16LTS' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\ADELIO\VirtualBox VMs\Linux 16LTS\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {5047460a-265d-4538-b23e-ddba5fb84976}


Failed to open a session for the virtual machine WIN10.

The virtual machine 'WIN10' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\ADELIO\VirtualBox VMs\WIN10\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {5047460a-265d-4538-b23e-ddba5fb84976}




Best Regards,

Adélio Miranda
"	Adelio Miranda
20969	Failed to open a session for the virtual machine Kali-Linux-2022.2-virtualbox-amd64.  The virtual machine 'Kali-Linux-2022.2-virtualbox-amd64' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\Computer\VirtualBox VMs\Kali-Linux-2022.2-virtualbox-amd64\Logs\VBoxHardening.log'.  Result Code: E_FAIL (0x80004005) Component: MachineWrap Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}	VirtualBox 6.1.34	2022-06-07T18:16:09Z	2022-06-07T18:21:22Z	2022-06-07T18:21:22Z	"Failed to open a session for the virtual machine Kali-Linux-2022.2-virtualbox-amd64.

The virtual machine 'Kali-Linux-2022.2-virtualbox-amd64' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\Computer\VirtualBox VMs\Kali-Linux-2022.2-virtualbox-amd64\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}

'''VBoxHardening.log:'''
{{{
1c58.1e4c: Log file opened: 6.1.34r150636 g_hStartupLog=0000000000000084 g_uNtVerCombined=0xa04a6300
1c58.1e4c: \SystemRoot\System32\ntdll.dll:
1c58.1e4c:     CreationTime:    2022-05-13T09:37:24.962297600Z
1c58.1e4c:     LastWriteTime:   2022-05-13T09:37:25.011955800Z
1c58.1e4c:     ChangeTime:      2022-05-13T21:27:08.242392000Z
1c58.1e4c:     FileAttributes:  0x20
1c58.1e4c:     Size:            0x1eeb38
1c58.1e4c:     NT Headers:      0xe8
1c58.1e4c:     Timestamp:       0x7b5414ec
1c58.1e4c:     Machine:         0x8664 - amd64
1c58.1e4c:     Timestamp:       0x7b5414ec
1c58.1e4c:     Image Version:   10.0
1c58.1e4c:     SizeOfImage:     0x1f5000 (2052096)
1c58.1e4c:     Resource Dir:    0x184000 LB 0x6fff8
1c58.1e4c:     [Version info resource found at 0xd8! (ID/Name: 0x1; SubID/SubName: 0x409)]
1c58.1e4c:     [Raw version resource data: 0x1840f0 LB 0x380, codepage 0x0 (reserved 0x0)]
1c58.1e4c:     ProductName:     Microsoft® Windows® Operating System
1c58.1e4c:     ProductVersion:  10.0.19041.1682
1c58.1e4c:     FileVersion:     10.0.19041.1682 (WinBuild.160101.0800)
1c58.1e4c:     FileDescription: NT Layer DLL
1c58.1e4c: \SystemRoot\System32\kernel32.dll:
1c58.1e4c:     CreationTime:    2022-05-13T09:37:16.157371700Z
1c58.1e4c:     LastWriteTime:   2022-05-13T09:37:16.176080300Z
1c58.1e4c:     ChangeTime:      2022-05-13T21:27:08.008042100Z
1c58.1e4c:     FileAttributes:  0x20
1c58.1e4c:     Size:            0xbb058
1c58.1e4c:     NT Headers:      0xe8
1c58.1e4c:     Timestamp:       0x4e5c27cf
1c58.1e4c:     Machine:         0x8664 - amd64
1c58.1e4c:     Timestamp:       0x4e5c27cf
1c58.1e4c:     Image Version:   10.0
1c58.1e4c:     SizeOfImage:     0xbd000 (774144)
1c58.1e4c:     Resource Dir:    0xbb000 LB 0x520
1c58.1e4c:     [Version info resource found at 0x90! (ID/Name: 0x1; SubID/SubName: 0x409)]
1c58.1e4c:     [Raw version resource data: 0xbb0b0 LB 0x3a4, codepage 0x0 (reserved 0x0)]
1c58.1e4c:     ProductName:     Microsoft® Windows® Operating System
1c58.1e4c:     ProductVersion:  10.0.19041.1706
1c58.1e4c:     FileVersion:     10.0.19041.1706 (WinBuild.160101.0800)
1c58.1e4c:     FileDescription: Windows NT BASE API Client DLL
1c58.1e4c: \SystemRoot\System32\KernelBase.dll:
1c58.1e4c:     CreationTime:    2022-05-13T09:37:25.904947200Z
1c58.1e4c:     LastWriteTime:   2022-05-13T09:37:25.981546200Z
1c58.1e4c:     ChangeTime:      2022-05-13T21:27:08.226771300Z
1c58.1e4c:     FileAttributes:  0x20
1c58.1e4c:     Size:            0x2cf640
1c58.1e4c:     NT Headers:      0xf0
1c58.1e4c:     Timestamp:       0x458acb5b
1c58.1e4c:     Machine:         0x8664 - amd64
1c58.1e4c:     Timestamp:       0x458acb5b
1c58.1e4c:     Image Version:   10.0
1c58.1e4c:     SizeOfImage:     0x2cd000 (2936832)
1c58.1e4c:     Resource Dir:    0x2a4000 LB 0x548
1c58.1e4c:     [Version info resource found at 0x90! (ID/Name: 0x1; SubID/SubName: 0x409)]
1c58.1e4c:     [Raw version resource data: 0x2a40b0 LB 0x3bc, codepage 0x0 (reserved 0x0)]
1c58.1e4c:     ProductName:     Microsoft® Windows® Operating System
1c58.1e4c:     ProductVersion:  10.0.19041.1706
1c58.1e4c:     FileVersion:     10.0.19041.1706 (WinBuild.160101.0800)
1c58.1e4c:     FileDescription: Windows NT BASE API Client DLL
1c58.1e4c: \SystemRoot\System32\apisetschema.dll:
1c58.1e4c:     CreationTime:    2019-12-07T09:08:13.518339400Z
1c58.1e4c:     LastWriteTime:   2019-12-07T09:08:13.518339400Z
1c58.1e4c:     ChangeTime:      2022-05-13T09:38:12.902031600Z
1c58.1e4c:     FileAttributes:  0x20
1c58.1e4c:     Size:            0x1f538
1c58.1e4c:     NT Headers:      0xd0
1c58.1e4c:     Timestamp:       0x31288ce0
1c58.1e4c:     Machine:         0x8664 - amd64
1c58.1e4c:     Timestamp:       0x31288ce0
1c58.1e4c:     Image Version:   10.0
1c58.1e4c:     SizeOfImage:     0x20000 (131072)
1c58.1e4c:     Resource Dir:    0x1f000 LB 0x408
1c58.1e4c:     [Version info resource found at 0x48! (ID/Name: 0x1; SubID/SubName: 0x409)]
1c58.1e4c:     [Raw version resource data: 0x1f060 LB 0x3a8, codepage 0x0 (reserved 0x0)]
1c58.1e4c:     ProductName:     Microsoft® Windows® Operating System
1c58.1e4c:     ProductVersion:  10.0.19041.1
1c58.1e4c:     FileVersion:     10.0.19041.1 (WinBuild.160101.0800)
1c58.1e4c:     FileDescription: ApiSet Schema DLL
1c58.1e4c: NtOpenDirectoryObject failed on \Driver: 0xc0000022
1c58.1e4c: supR3HardenedWinFindAdversaries: 0x800
1c58.1e4c: \SystemRoot\System32\drivers\cfrmd.sys:
1c58.1e4c:     CreationTime:    2014-06-26T05:33:42.000000000Z
1c58.1e4c:     LastWriteTime:   2014-06-26T05:33:42.000000000Z
1c58.1e4c:     ChangeTime:      2020-10-11T11:10:28.369648400Z
1c58.1e4c:     FileAttributes:  0x20
1c58.1e4c:     Size:            0x9d20
1c58.1e4c:     NT Headers:      0xe8
1c58.1e4c:     Timestamp:       0x5004f2a1
1c58.1e4c:     Machine:         0x8664 - amd64
1c58.1e4c:     Timestamp:       0x5004f2a1
1c58.1e4c:     Image Version:   6.1
1c58.1e4c:     SizeOfImage:     0xe000 (57344)
1c58.1e4c:     Resource Dir:    0xc000 LB 0x3e0
1c58.1e4c:     [Version info resource found at 0x48! (ID/Name: 0x1; SubID/SubName: 0x409)]
1c58.1e4c:     [Raw version resource data: 0xc060 LB 0x380, codepage 0x0 (reserved 0x0)]
1c58.1e4c:     ProductName:     Windows (R) Win 7 DDK driver
1c58.1e4c:     ProductVersion:  6.1.7600.16385
1c58.1e4c:     FileVersion:     6.1.7600.16385 built by: WinDDK
1c58.1e4c:     FileDescription: Safe Deletion Driver
1c58.1e4c: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox'
1c58.1e4c: Calling main()
1c58.1e4c: SUPR3HardenedMain: pszProgName=VirtualBoxVM fFlags=0x2
1c58.1e4c: supR3HardenedWinInitAppBin(0x2): '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox'
1c58.1e4c: SUPR3HardenedMain: Respawn #1
1c58.1e4c: System32:  \Device\HarddiskVolume4\Windows\System32
1c58.1e4c: WinSxS:    \Device\HarddiskVolume4\Windows\WinSxS
1c58.1e4c: KnownDllPath: C:\WINDOWS\System32
1c58.1e4c: supR3HardenedWinInit: Performing a limited self purification...
1c58.1e4c: supHardNtVpScanVirtualMemory: enmKind=SELF_PURIFICATION
1c58.1e4c:  *0000000000000000-000000000042ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *0000000000430000-000000000043ffff 0x0004/0x0004 0x0040000
1c58.1e4c:   0000000000440000-000000000044ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *0000000000450000-000000000046cfff 0x0002/0x0002 0x0040000
1c58.1e4c:   000000000046d000-000000000046ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *0000000000470000-0000000000520fff 0x0000/0x0004 0x0020000
1c58.1e4c:   0000000000521000-0000000000523fff 0x0104/0x0004 0x0020000
1c58.1e4c:   0000000000524000-000000000056ffff 0x0004/0x0004 0x0020000
1c58.1e4c:  *0000000000570000-0000000000573fff 0x0002/0x0002 0x0040000
1c58.1e4c:   0000000000574000-000000000057ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *0000000000580000-0000000000581fff 0x0004/0x0004 0x0020000
1c58.1e4c:   0000000000582000-000000000058ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *0000000000590000-0000000000591fff 0x0004/0x0004 0x0020000
1c58.1e4c:   0000000000592000-00000000005a9fff 0x0000/0x0004 0x0020000
1c58.1e4c:   00000000005aa000-00000000005fffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *0000000000600000-00000000006affff 0x0000/0x0004 0x0020000
1c58.1e4c:   00000000006b0000-00000000006b2fff 0x0004/0x0004 0x0020000
1c58.1e4c:   00000000006b3000-00000000007fffff 0x0000/0x0004 0x0020000
1c58.1e4c:  *0000000000800000-00000000008c8fff 0x0002/0x0002 0x0040000
1c58.1e4c:   00000000008c9000-00000000008dffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00000000008e0000-00000000008e5fff 0x0004/0x0004 0x0020000
1c58.1e4c:   00000000008e6000-00000000009dffff 0x0000/0x0004 0x0020000
1c58.1e4c:  *00000000009e0000-0000000000a06fff 0x0004/0x0004 0x0020000
1c58.1e4c:   0000000000a07000-0000000000adffff 0x0000/0x0004 0x0020000
1c58.1e4c:   0000000000ae0000-0000000000b0ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *0000000000b10000-0000000000b1efff 0x0004/0x0004 0x0020000
1c58.1e4c:   0000000000b1f000-0000000000b1ffff 0x0000/0x0004 0x0020000
1c58.1e4c:  *0000000000b20000-0000000000b2afff 0x0000/0x0004 0x0020000
1c58.1e4c:   0000000000b2b000-0000000000d20fff 0x0004/0x0004 0x0020000
1c58.1e4c:   0000000000d21000-0000000000d21fff 0x0000/0x0004 0x0020000
1c58.1e4c:   0000000000d22000-000000007ffdffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *000000007ffe0000-000000007ffe0fff 0x0002/0x0002 0x0020000
1c58.1e4c:   000000007ffe1000-000000007ffe2fff 0x0001/0x0000 0x0000000
1c58.1e4c:  *000000007ffe3000-000000007ffe3fff 0x0002/0x0002 0x0020000
1c58.1e4c:   000000007ffe4000-00007ff4407dffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00007ff4407e0000-00007ff4407e4fff 0x0002/0x0002 0x0040000
1c58.1e4c:   00007ff4407e5000-00007ff4408dffff 0x0000/0x0002 0x0040000
1c58.1e4c:  *00007ff4408e0000-00007ff5408fffff 0x0000/0x0004 0x0020000
1c58.1e4c:  *00007ff540900000-00007ff5428fffff 0x0000/0x0004 0x0020000
1c58.1e4c:   00007ff542900000-00007ff542900fff 0x0004/0x0004 0x0020000
1c58.1e4c:   00007ff542901000-00007ff54290ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00007ff542910000-00007ff542910fff 0x0002/0x0002 0x0040000
1c58.1e4c:   00007ff542911000-00007ff54291ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00007ff542920000-00007ff542942fff 0x0002/0x0002 0x0040000
1c58.1e4c:   00007ff542943000-00007ff7afb4ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00007ff7afb50000-00007ff7afb50fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afb51000-00007ff7afbc7fff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afbc8000-00007ff7afbc8fff 0x0080/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afbc9000-00007ff7afc11fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc12000-00007ff7afc14fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc15000-00007ff7afc17fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc18000-00007ff7afc1afff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc1b000-00007ff7afc1bfff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc1c000-00007ff7afc1dfff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc1e000-00007ff7afc1efff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc1f000-00007ff7afc67fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc68000-00007ffbe210ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00007ffbe2110000-00007ffbe2110fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\KernelBase.dll
1c58.1e4c:   00007ffbe2111000-00007ffbe2225fff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\KernelBase.dll
1c58.1e4c:   00007ffbe2226000-00007ffbe239efff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\KernelBase.dll
1c58.1e4c:   00007ffbe239f000-00007ffbe23a2fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\KernelBase.dll
1c58.1e4c:   00007ffbe23a3000-00007ffbe23a3fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\KernelBase.dll
1c58.1e4c:   00007ffbe23a4000-00007ffbe23dcfff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\KernelBase.dll
1c58.1e4c:   00007ffbe23dd000-00007ffbe3f1ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00007ffbe3f20000-00007ffbe3f20fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\kernel32.dll
1c58.1e4c:   00007ffbe3f21000-00007ffbe3f9efff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\kernel32.dll
1c58.1e4c:   00007ffbe3f9f000-00007ffbe3fd1fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\kernel32.dll
1c58.1e4c:   00007ffbe3fd2000-00007ffbe3fd2fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\kernel32.dll
1c58.1e4c:   00007ffbe3fd3000-00007ffbe3fd3fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\kernel32.dll
1c58.1e4c:   00007ffbe3fd4000-00007ffbe3fdcfff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\kernel32.dll
1c58.1e4c:   00007ffbe3fdd000-00007ffbe452ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00007ffbe4530000-00007ffbe4530fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe4531000-00007ffbe464bfff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe464c000-00007ffbe4693fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe4694000-00007ffbe4694fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe4695000-00007ffbe4696fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe4697000-00007ffbe469ffff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe46a0000-00007ffbe4724fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe4725000-00007ffffffeffff 0x0001/0x0000 0x0000000
1c58.1e4c: kernel32.dll: timestamp 0x4e5c27cf (rc=VINF_SUCCESS)
1c58.1e4c: kernelbase.dll: timestamp 0x458acb5b (rc=VINF_SUCCESS)
1c58.1e4c: VirtualBoxVM.exe: timestamp 0x623a5dfe (rc=VINF_SUCCESS)
1c58.1e4c: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe: Signature #1/2: info status: 24202
1c58.1e4c: '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe' has no imports
1c58.1e4c: '\Device\HarddiskVolume4\Windows\System32\ntdll.dll' has no imports
1c58.1e4c: supR3HardenedWinInit: SUPHARDNTVPKIND_SELF_PURIFICATION_LIMITED -> VINF_SUCCESS, cFixes=0
1c58.1e4c: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe: Signature #1/2: info status: 24202
1c58.1e4c: '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe' has no imports
1c58.1e4c: supHardenedWinVerifyImageByHandle: -> 24202 (\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe)
1c58.1e4c: supR3HardNtEnableThreadCreationEx:
1c58.1e4c: supR3HardNtDisableThreadCreation: pvLdrInitThunk=00007ffbe45a4b00 pvNtTerminateThread=00007ffbe45cd790
1c58.1e4c: supR3HardenedWinDoReSpawn(1): New child 284c.3ce4 [kernel32].
1c58.1e4c: supR3HardNtChildGatherData: PebBaseAddress=0000000000a24000 cbPeb=0x388
1c58.1e4c: supR3HardNtPuChFindNtdll: uNtDllParentAddr=00007ffbe4530000 uNtDllChildAddr=00007ffbe4530000
1c58.1e4c: supR3HardenedWinSetupChildInit: uLdrInitThunk=00007ffbe45a4b00
1c58.1e4c: supR3HardenedWinSetupChildInit: Initial context:
  rax=0000000000000000 rbx=0000000000000000 rcx=00007ff7afb57900 rdx=0000000000a24000
  rsi=0000000000000000 rdi=0000000000000000 r8 =0000000000000000 r9 =0000000000000000
  r10=0000000000000000 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
  r14=0000000000000000 r15=0000000000000000  P1=0000000000000000  P2=0000000000000000
  rip=00007ffbe4582630 rsp=00000000009bfe78 rbp=0000000000000000    ctxflags=0010001b
  cs=0033 ss=002b ds=0000 es=0000 fs=0000 gs=0000    eflags=00000200   mxcrx=00001f80
   P3=0000000000000000  P4=0000000000000000  P5=0000000000000000  P6=0000000000000000
  dr0=0000000000000000 dr1=0000000000000000 dr2=0000000000000000 dr3=0000000000000000
  dr6=0000000000000000 dr7=0000000000000000 vcr=0000000000000000 dcr=0000000000000000
  lbt=0000000000000000 lbf=0000000000000000 lxt=0000000000000000 lxf=0000000000000000
1c58.1e4c: supR3HardenedWinSetupChildInit: Start child.
1c58.1e4c: supR3HardNtChildWaitFor: Found expected request 0 (PurifyChildAndCloseHandles) after 0 ms.
1c58.1e4c: supR3HardNtChildPurify: Startup delay kludge #1/0: 523 ms, 34 sleeps
1c58.1e4c: supHardNtVpScanVirtualMemory: enmKind=CHILD_PURIFICATION
1c58.1e4c:  *0000000000000000-000000000087ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *0000000000880000-000000000089ffff 0x0004/0x0004 0x0020000
1c58.1e4c:  *00000000008a0000-00000000008bcfff 0x0002/0x0002 0x0040000
1c58.1e4c:   00000000008bd000-00000000008bffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00000000008c0000-00000000009bafff 0x0000/0x0004 0x0020000
1c58.1e4c:   00000000009bb000-00000000009bdfff 0x0104/0x0004 0x0020000
1c58.1e4c:   00000000009be000-00000000009bffff 0x0004/0x0004 0x0020000
1c58.1e4c:  *00000000009c0000-00000000009c3fff 0x0002/0x0002 0x0040000
1c58.1e4c:   00000000009c4000-00000000009cffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00000000009d0000-00000000009d1fff 0x0004/0x0004 0x0020000
1c58.1e4c:   00000000009d2000-00000000009fffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *0000000000a00000-0000000000a23fff 0x0000/0x0004 0x0020000
1c58.1e4c:   0000000000a24000-0000000000a26fff 0x0004/0x0004 0x0020000
1c58.1e4c:   0000000000a27000-0000000000bfffff 0x0000/0x0004 0x0020000
1c58.1e4c:   0000000000c00000-000000007ffdffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *000000007ffe0000-000000007ffe0fff 0x0002/0x0002 0x0020000
1c58.1e4c:   000000007ffe1000-000000007ffe2fff 0x0001/0x0000 0x0000000
1c58.1e4c:  *000000007ffe3000-000000007ffe3fff 0x0002/0x0002 0x0020000
1c58.1e4c:   000000007ffe4000-00007ff5ee77ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00007ff5ee780000-00007ff5ee780fff 0x0002/0x0002 0x0040000
1c58.1e4c:   00007ff5ee781000-00007ff5ee78ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00007ff5ee790000-00007ff5ee7b2fff 0x0002/0x0002 0x0040000
1c58.1e4c:   00007ff5ee7b3000-00007ff7afb4ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00007ff7afb50000-00007ff7afb50fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afb51000-00007ff7afbc7fff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afbc8000-00007ff7afbc8fff 0x0080/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afbc9000-00007ff7afc11fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc12000-00007ff7afc12fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc13000-00007ff7afc13fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc14000-00007ff7afc18fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc19000-00007ff7afc19fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc1a000-00007ff7afc1afff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc1b000-00007ff7afc1efff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc1f000-00007ff7afc67fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc68000-00007ffbe452ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00007ffbe4530000-00007ffbe4530fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe4531000-00007ffbe464bfff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe464c000-00007ffbe4693fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe4694000-00007ffbe469ffff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe46a0000-00007ffbe46aefff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe46af000-00007ffbe46affff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe46b0000-00007ffbe46b2fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe46b3000-00007ffbe4724fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe4725000-00007ffffffeffff 0x0001/0x0000 0x0000000
1c58.1e4c: supR3HardNtChildPurify: Done after 526 ms and 0 fixes (loop #0).
284c.3ce4: Log file opened: 6.1.34r150636 g_hStartupLog=0000000000000004 g_uNtVerCombined=0xa04a6300
284c.3ce4: supR3HardenedVmProcessInit: uNtDllAddr=00007ffbe4530000 g_uNtVerCombined=0xa04a6300 (stack ~00000000009bf908)
284c.3ce4: ntdll.dll: timestamp 0x7b5414ec (rc=VINF_SUCCESS)
284c.3ce4: New simple heap: #1 0000000000d00000 LB 0x400000 (for 2052096 allocation)
1c58.1e4c: supR3HardNtEnableThreadCreationEx:
284c.3ce4: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox'
284c.3ce4: System32:  \Device\HarddiskVolume4\Windows\System32
284c.3ce4: WinSxS:    \Device\HarddiskVolume4\Windows\WinSxS
284c.3ce4: KnownDllPath: C:\WINDOWS\System32
284c.3ce4: supR3HardenedVmProcessInit: Opening vboxdrv stub...
284c.3ce4: supR3HardenedVmProcessInit: Restoring LdrInitializeThunk...
284c.3ce4: supR3HardenedVmProcessInit: Returning to LdrInitializeThunk...
284c.3ce4: Registered Dll notification callback with NTDLL.
284c.3ce4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\kernel32.dll)
284c.3ce4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\kernel32.dll
284c.3ce4: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\System32\KERNEL32.DLL (Input=KERNEL32.DLL, rcNtResolve=0xc0150008) *pfFlags=0xffffffff pwszSearchPath=0000000000004001:<flags> [calling]
284c.3ce4: supR3HardenedDllNotificationCallback: load   00007ffbe2110000 LB 0x002cd000 C:\WINDOWS\System32\KERNELBASE.dll [fFlags=0x0]
284c.3ce4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\KernelBase.dll)
284c.3ce4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\KernelBase.dll
284c.3ce4: supR3HardenedDllNotificationCallback: load   00007ffbe3f20000 LB 0x000bd000 C:\WINDOWS\System32\KERNEL32.DLL [fFlags=0x0]
284c.3ce4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\kernel32.dll [lacks WinVerifyTrust]
284c.3ce4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe3f20000 'C:\WINDOWS\System32\KERNEL32.DLL'
284c.3ce4: supR3HardenedDllNotificationCallback: load   00007ff7afb50000 LB 0x00118000 C:\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe [fFlags=0x0]
284c.3ce4: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe: Signature #1/2: info status: 24202
284c.3ce4: '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe' has no imports
284c.3ce4: supHardenedWinVerifyImageByHandle: -> 24202 (\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe)
284c.3ce4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4: supR3HardNtDisableThreadCreation: pvLdrInitThunk=00007ffbe45a4b00 pvNtTerminateThread=00007ffbe45cd790
1c58.1e4c: supR3HardNtChildWaitFor: Found expected request 1 (CloseEvents) after 107 ms.
284c.3ce4: \SystemRoot\System32\ntdll.dll:
284c.3ce4:     CreationTime:    2022-05-13T09:37:24.962297600Z
284c.3ce4:     LastWriteTime:   2022-05-13T09:37:25.011955800Z
284c.3ce4:     ChangeTime:      2022-05-13T21:27:08.242392000Z
284c.3ce4:     FileAttributes:  0x20
284c.3ce4:     Size:            0x1eeb38
284c.3ce4:     NT Headers:      0xe8
284c.3ce4:     Timestamp:       0x7b5414ec
284c.3ce4:     Machine:         0x8664 - amd64
284c.3ce4:     Timestamp:       0x7b5414ec
284c.3ce4:     Image Version:   10.0
284c.3ce4:     SizeOfImage:     0x1f5000 (2052096)
284c.3ce4:     Resource Dir:    0x184000 LB 0x6fff8
284c.3ce4:     [Version info resource found at 0xd8! (ID/Name: 0x1; SubID/SubName: 0x409)]
284c.3ce4:     [Raw version resource data: 0x1840f0 LB 0x380, codepage 0x0 (reserved 0x0)]
284c.3ce4:     ProductName:     Microsoft® Windows® Operating System
284c.3ce4:     ProductVersion:  10.0.19041.1682
284c.3ce4:     FileVersion:     10.0.19041.1682 (WinBuild.160101.0800)
284c.3ce4:     FileDescription: NT Layer DLL
284c.3ce4: \SystemRoot\System32\kernel32.dll:
284c.3ce4:     CreationTime:    2022-05-13T09:37:16.157371700Z
284c.3ce4:     LastWriteTime:   2022-05-13T09:37:16.176080300Z
284c.3ce4:     ChangeTime:      2022-05-13T21:27:08.008042100Z
284c.3ce4:     FileAttributes:  0x20
284c.3ce4:     Size:            0xbb058
284c.3ce4:     NT Headers:      0xe8
284c.3ce4:     Timestamp:       0x4e5c27cf
284c.3ce4:     Machine:         0x8664 - amd64
284c.3ce4:     Timestamp:       0x4e5c27cf
284c.3ce4:     Image Version:   10.0
284c.3ce4:     SizeOfImage:     0xbd000 (774144)
284c.3ce4:     Resource Dir:    0xbb000 LB 0x520
284c.3ce4:     [Version info resource found at 0x90! (ID/Name: 0x1; SubID/SubName: 0x409)]
284c.3ce4:     [Raw version resource data: 0xbb0b0 LB 0x3a4, codepage 0x0 (reserved 0x0)]
284c.3ce4:     ProductName:     Microsoft® Windows® Operating System
284c.3ce4:     ProductVersion:  10.0.19041.1706
284c.3ce4:     FileVersion:     10.0.19041.1706 (WinBuild.160101.0800)
284c.3ce4:     FileDescription: Windows NT BASE API Client DLL
284c.3ce4: \SystemRoot\System32\KernelBase.dll:
284c.3ce4:     CreationTime:    2022-05-13T09:37:25.904947200Z
284c.3ce4:     LastWriteTime:   2022-05-13T09:37:25.981546200Z
284c.3ce4:     ChangeTime:      2022-05-13T21:27:08.226771300Z
284c.3ce4:     FileAttributes:  0x20
284c.3ce4:     Size:            0x2cf640
284c.3ce4:     NT Headers:      0xf0
284c.3ce4:     Timestamp:       0x458acb5b
284c.3ce4:     Machine:         0x8664 - amd64
284c.3ce4:     Timestamp:       0x458acb5b
284c.3ce4:     Image Version:   10.0
284c.3ce4:     SizeOfImage:     0x2cd000 (2936832)
284c.3ce4:     Resource Dir:    0x2a4000 LB 0x548
284c.3ce4:     [Version info resource found at 0x90! (ID/Name: 0x1; SubID/SubName: 0x409)]
284c.3ce4:     [Raw version resource data: 0x2a40b0 LB 0x3bc, codepage 0x0 (reserved 0x0)]
284c.3ce4:     ProductName:     Microsoft® Windows® Operating System
284c.3ce4:     ProductVersion:  10.0.19041.1706
284c.3ce4:     FileVersion:     10.0.19041.1706 (WinBuild.160101.0800)
284c.3ce4:     FileDescription: Windows NT BASE API Client DLL
284c.3ce4: \SystemRoot\System32\apisetschema.dll:
284c.3ce4:     CreationTime:    2019-12-07T09:08:13.518339400Z
284c.3ce4:     LastWriteTime:   2019-12-07T09:08:13.518339400Z
284c.3ce4:     ChangeTime:      2022-05-13T09:38:12.902031600Z
284c.3ce4:     FileAttributes:  0x20
284c.3ce4:     Size:            0x1f538
284c.3ce4:     NT Headers:      0xd0
284c.3ce4:     Timestamp:       0x31288ce0
284c.3ce4:     Machine:         0x8664 - amd64
284c.3ce4:     Timestamp:       0x31288ce0
284c.3ce4:     Image Version:   10.0
284c.3ce4:     SizeOfImage:     0x20000 (131072)
284c.3ce4:     Resource Dir:    0x1f000 LB 0x408
284c.3ce4:     [Version info resource found at 0x48! (ID/Name: 0x1; SubID/SubName: 0x409)]
284c.3ce4:     [Raw version resource data: 0x1f060 LB 0x3a8, codepage 0x0 (reserved 0x0)]
284c.3ce4:     ProductName:     Microsoft® Windows® Operating System
284c.3ce4:     ProductVersion:  10.0.19041.1
284c.3ce4:     FileVersion:     10.0.19041.1 (WinBuild.160101.0800)
284c.3ce4:     FileDescription: ApiSet Schema DLL
284c.3ce4: NtOpenDirectoryObject failed on \Driver: 0xc0000022
284c.3ce4: supR3HardenedWinFindAdversaries: 0x800
284c.3ce4: \SystemRoot\System32\drivers\cfrmd.sys:
284c.3ce4:     CreationTime:    2014-06-26T05:33:42.000000000Z
284c.3ce4:     LastWriteTime:   2014-06-26T05:33:42.000000000Z
284c.3ce4:     ChangeTime:      2020-10-11T11:10:28.369648400Z
284c.3ce4:     FileAttributes:  0x20
284c.3ce4:     Size:            0x9d20
284c.3ce4:     NT Headers:      0xe8
284c.3ce4:     Timestamp:       0x5004f2a1
284c.3ce4:     Machine:         0x8664 - amd64
284c.3ce4:     Timestamp:       0x5004f2a1
284c.3ce4:     Image Version:   6.1
284c.3ce4:     SizeOfImage:     0xe000 (57344)
284c.3ce4:     Resource Dir:    0xc000 LB 0x3e0
284c.3ce4:     [Version info resource found at 0x48! (ID/Name: 0x1; SubID/SubName: 0x409)]
284c.3ce4:     [Raw version resource data: 0xc060 LB 0x380, codepage 0x0 (reserved 0x0)]
284c.3ce4:     ProductName:     Windows (R) Win 7 DDK driver
284c.3ce4:     ProductVersion:  6.1.7600.16385
284c.3ce4:     FileVersion:     6.1.7600.16385 built by: WinDDK
284c.3ce4:     FileDescription: Safe Deletion Driver
284c.3ce4: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox'
284c.3ce4: Calling main()
284c.3ce4: SUPR3HardenedMain: pszProgName=VirtualBoxVM fFlags=0x2
284c.3ce4: supR3HardenedWinInitAppBin(0x2): '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox'
284c.3ce4: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe: Signature #1/2: info status: 24202
284c.3ce4: '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe' has no imports
284c.3ce4: supHardenedWinVerifyImageByHandle: -> 24202 (\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe)
284c.3ce4: SUPR3HardenedMain: Respawn #2
284c.3ce4: supR3HardNtEnableThreadCreationEx:
284c.3ce4: supR3HardenedDllNotificationCallback: load   00007ffbe3970000 LB 0x00125000 C:\WINDOWS\System32\RPCRT4.dll [fFlags=0x0]
284c.3ce4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\rpcrt4.dll)
284c.3ce4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\rpcrt4.dll
284c.3ce4: supR3HardenedDllNotificationCallback: load   00007ffbe2c30000 LB 0x0009c000 C:\WINDOWS\System32\sechost.dll [fFlags=0x0]
284c.3ce4: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #11 'rpcrt4.dll'.
284c.3ce4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\sechost.dll)
284c.3ce4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\sechost.dll
284c.3ce4: '\Device\HarddiskVolume4\Windows\System32\ntdll.dll' has no imports
284c.3ce4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\ntdll.dll)
284c.3ce4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\ntdll.dll
284c.3ce4: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'rpcrt4.dll'...
284c.3ce4: supR3HardenedWinVerifyCacheProcessImportTodos: 'rpcrt4.dll' -> '\Device\HarddiskVolume4\Windows\System32\rpcrt4.dll' [rcNtRedir=0xc0150008]
284c.3ce4: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\rpcrt4.dll [lacks WinVerifyTrust]
284c.3ce4: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\System32\ntdll.dll (Input=ntdll.dll, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
284c.3ce4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe4530000 'C:\WINDOWS\System32\ntdll.dll'
284c.3ce4: supR3HardNtDisableThreadCreation: pvLdrInitThunk=00007ffbe45a4b00 pvNtTerminateThread=00007ffbe45cd790
284c.3ce4: supR3HardenedWinDoReSpawn(2): New child 255c.41c4 [kernel32].
284c.3ce4: supR3HardenedWinReSpawn: NtSetInformationThread/ThreadHideFromDebugger failed: 0xc0000022 (harmless)
284c.3ce4: supR3HardNtChildGatherData: PebBaseAddress=0000000000ccf000 cbPeb=0x388
284c.3ce4: supR3HardNtPuChFindNtdll: uNtDllParentAddr=00007ffbe4530000 uNtDllChildAddr=00007ffbe4530000
284c.3ce4: supR3HardenedWinSetupChildInit: uLdrInitThunk=00007ffbe45a4b00
284c.3ce4: supR3HardenedWinSetupChildInit: Initial context:
  rax=0000000000000000 rbx=0000000000000000 rcx=00007ff7afb57900 rdx=0000000000ccf000
  rsi=0000000000000000 rdi=0000000000000000 r8 =0000000000000000 r9 =0000000000000000
  r10=0000000000000000 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
  r14=0000000000000000 r15=0000000000000000  P1=0000000000000000  P2=0000000000000000
  rip=00007ffbe4582630 rsp=0000000000b9fad8 rbp=0000000000000000    ctxflags=0010001b
  cs=0033 ss=002b ds=0000 es=0000 fs=0000 gs=0000    eflags=00000200   mxcrx=00001f80
   P3=0000000000000000  P4=0000000000000000  P5=0000000000000000  P6=0000000000000000
  dr0=0000000000000000 dr1=0000000000000000 dr2=0000000000000000 dr3=0000000000000000
  dr6=0000000000000000 dr7=0000000000000000 vcr=0000000000000000 dcr=0000000000000000
  lbt=0000000000000000 lbf=0000000000000000 lxt=0000000000000000 lxf=0000000000000000
284c.3ce4: kernel32.dll: timestamp 0x4e5c27cf (rc=VINF_SUCCESS)
284c.3ce4: supR3HardenedWinSetupChildInit: Start child.
284c.3ce4: supR3HardNtChildWaitFor: Found expected request 0 (PurifyChildAndCloseHandles) after 0 ms.
284c.3ce4: supR3HardNtChildPurify: Startup delay kludge #1/0: 524 ms, 34 sleeps
284c.3ce4: supHardNtVpScanVirtualMemory: enmKind=CHILD_PURIFICATION
284c.3ce4:  *0000000000000000-0000000000a5ffff 0x0001/0x0000 0x0000000
284c.3ce4:  *0000000000a60000-0000000000a7ffff 0x0004/0x0004 0x0020000
284c.3ce4:  *0000000000a80000-0000000000a9cfff 0x0002/0x0002 0x0040000
284c.3ce4:   0000000000a9d000-0000000000a9ffff 0x0001/0x0000 0x0000000
284c.3ce4:  *0000000000aa0000-0000000000b9afff 0x0000/0x0004 0x0020000
284c.3ce4:   0000000000b9b000-0000000000b9dfff 0x0104/0x0004 0x0020000
284c.3ce4:   0000000000b9e000-0000000000b9ffff 0x0004/0x0004 0x0020000
284c.3ce4:  *0000000000ba0000-0000000000ba3fff 0x0002/0x0002 0x0040000
284c.3ce4:   0000000000ba4000-0000000000baffff 0x0001/0x0000 0x0000000
284c.3ce4:  *0000000000bb0000-0000000000bb1fff 0x0004/0x0004 0x0020000
284c.3ce4:   0000000000bb2000-0000000000bfffff 0x0001/0x0000 0x0000000
284c.3ce4:  *0000000000c00000-0000000000ccefff 0x0000/0x0004 0x0020000
284c.3ce4:   0000000000ccf000-0000000000cd1fff 0x0004/0x0004 0x0020000
284c.3ce4:   0000000000cd2000-0000000000dfffff 0x0000/0x0004 0x0020000
284c.3ce4:   0000000000e00000-000000007ffdffff 0x0001/0x0000 0x0000000
284c.3ce4:  *000000007ffe0000-000000007ffe0fff 0x0002/0x0002 0x0020000
284c.3ce4:   000000007ffe1000-000000007ffe2fff 0x0001/0x0000 0x0000000
284c.3ce4:  *000000007ffe3000-000000007ffe3fff 0x0002/0x0002 0x0020000
284c.3ce4:   000000007ffe4000-00007ff55706ffff 0x0001/0x0000 0x0000000
284c.3ce4:  *00007ff557070000-00007ff557070fff 0x0002/0x0002 0x0040000
284c.3ce4:   00007ff557071000-00007ff55707ffff 0x0001/0x0000 0x0000000
284c.3ce4:  *00007ff557080000-00007ff5570a2fff 0x0002/0x0002 0x0040000
284c.3ce4:   00007ff5570a3000-00007ff7afb4ffff 0x0001/0x0000 0x0000000
284c.3ce4:  *00007ff7afb50000-00007ff7afb50fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4:   00007ff7afb51000-00007ff7afbc7fff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4:   00007ff7afbc8000-00007ff7afbc8fff 0x0080/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4:   00007ff7afbc9000-00007ff7afc11fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4:   00007ff7afc12000-00007ff7afc12fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4:   00007ff7afc13000-00007ff7afc13fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4:   00007ff7afc14000-00007ff7afc18fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4:   00007ff7afc19000-00007ff7afc19fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4:   00007ff7afc1a000-00007ff7afc1afff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4:   00007ff7afc1b000-00007ff7afc1efff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4:   00007ff7afc1f000-00007ff7afc67fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4:   00007ff7afc68000-00007ffbe452ffff 0x0001/0x0000 0x0000000
284c.3ce4:  *00007ffbe4530000-00007ffbe4530fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
284c.3ce4:   00007ffbe4531000-00007ffbe464bfff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
284c.3ce4:   00007ffbe464c000-00007ffbe4693fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
284c.3ce4:   00007ffbe4694000-00007ffbe469ffff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
284c.3ce4:   00007ffbe46a0000-00007ffbe46aefff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
284c.3ce4:   00007ffbe46af000-00007ffbe46affff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
284c.3ce4:   00007ffbe46b0000-00007ffbe46b2fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
284c.3ce4:   00007ffbe46b3000-00007ffbe4724fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
284c.3ce4:   00007ffbe4725000-00007ffffffeffff 0x0001/0x0000 0x0000000
284c.3ce4: VirtualBoxVM.exe: timestamp 0x623a5dfe (rc=VINF_SUCCESS)
284c.3ce4: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe: Signature #1/2: info status: 24202
284c.3ce4: '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe' has no imports
284c.3ce4: '\Device\HarddiskVolume4\Windows\System32\ntdll.dll' has no imports
284c.3ce4: supR3HardNtChildPurify: Done after 566 ms and 0 fixes (loop #0).
284c.3ce4: supR3HardenedEarlyCompact: Removed heap 1 (0x00000000d00000 LB 0x400000)
255c.41c4: Log file opened: 6.1.34r150636 g_hStartupLog=0000000000000004 g_uNtVerCombined=0xa04a6300
255c.41c4: supR3HardenedVmProcessInit: uNtDllAddr=00007ffbe4530000 g_uNtVerCombined=0xa04a6300 (stack ~0000000000b9f568)
284c.3ce4: supR3HardNtEnableThreadCreationEx:
255c.41c4: ntdll.dll: timestamp 0x7b5414ec (rc=VINF_SUCCESS)
255c.41c4: New simple heap: #1 0000000000f00000 LB 0x400000 (for 2052096 allocation)
255c.41c4: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox'
255c.41c4: System32:  \Device\HarddiskVolume4\Windows\System32
255c.41c4: WinSxS:    \Device\HarddiskVolume4\Windows\WinSxS
255c.41c4: KnownDllPath: C:\WINDOWS\System32
255c.41c4: supR3HardenedVmProcessInit: Opening vboxdrv...
255c.41c4: supR3HardenedVmProcessInit: Restoring LdrInitializeThunk...
255c.41c4: supR3HardenedVmProcessInit: Returning to LdrInitializeThunk...
255c.41c4: Registered Dll notification callback with NTDLL.
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\kernel32.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\kernel32.dll
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\System32\KERNEL32.DLL (Input=KERNEL32.DLL, rcNtResolve=0xc0150008) *pfFlags=0xffffffff pwszSearchPath=0000000000004001:<flags> [calling]
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe2110000 LB 0x002cd000 C:\WINDOWS\System32\KERNELBASE.dll [fFlags=0x0]
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\KernelBase.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\KernelBase.dll
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe3f20000 LB 0x000bd000 C:\WINDOWS\System32\KERNEL32.DLL [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\kernel32.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe3f20000 'C:\WINDOWS\System32\KERNEL32.DLL'
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ff7afb50000 LB 0x00118000 C:\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe [fFlags=0x0]
255c.41c4: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe: Signature #1/2: info status: 24202
255c.41c4: '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe' has no imports
255c.41c4: supHardenedWinVerifyImageByHandle: -> 24202 (\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
255c.41c4: supR3HardNtDisableThreadCreation: pvLdrInitThunk=00007ffbe45a4b00 pvNtTerminateThread=00007ffbe45cd790
284c.3ce4: supR3HardNtChildWaitFor: Found expected request 1 (CloseEvents) after 125 ms.
255c.41c4: \SystemRoot\System32\ntdll.dll:
255c.41c4:     CreationTime:    2022-05-13T09:37:24.962297600Z
255c.41c4:     LastWriteTime:   2022-05-13T09:37:25.011955800Z
255c.41c4:     ChangeTime:      2022-05-13T21:27:08.242392000Z
255c.41c4:     FileAttributes:  0x20
255c.41c4:     Size:            0x1eeb38
255c.41c4:     NT Headers:      0xe8
255c.41c4:     Timestamp:       0x7b5414ec
255c.41c4:     Machine:         0x8664 - amd64
255c.41c4:     Timestamp:       0x7b5414ec
255c.41c4:     Image Version:   10.0
255c.41c4:     SizeOfImage:     0x1f5000 (2052096)
255c.41c4:     Resource Dir:    0x184000 LB 0x6fff8
255c.41c4:     [Version info resource found at 0xd8! (ID/Name: 0x1; SubID/SubName: 0x409)]
255c.41c4:     [Raw version resource data: 0x1840f0 LB 0x380, codepage 0x0 (reserved 0x0)]
255c.41c4:     ProductName:     Microsoft® Windows® Operating System
255c.41c4:     ProductVersion:  10.0.19041.1682
255c.41c4:     FileVersion:     10.0.19041.1682 (WinBuild.160101.0800)
255c.41c4:     FileDescription: NT Layer DLL
255c.41c4: \SystemRoot\System32\kernel32.dll:
255c.41c4:     CreationTime:    2022-05-13T09:37:16.157371700Z
255c.41c4:     LastWriteTime:   2022-05-13T09:37:16.176080300Z
255c.41c4:     ChangeTime:      2022-05-13T21:27:08.008042100Z
255c.41c4:     FileAttributes:  0x20
255c.41c4:     Size:            0xbb058
255c.41c4:     NT Headers:      0xe8
255c.41c4:     Timestamp:       0x4e5c27cf
255c.41c4:     Machine:         0x8664 - amd64
255c.41c4:     Timestamp:       0x4e5c27cf
255c.41c4:     Image Version:   10.0
255c.41c4:     SizeOfImage:     0xbd000 (774144)
255c.41c4:     Resource Dir:    0xbb000 LB 0x520
255c.41c4:     [Version info resource found at 0x90! (ID/Name: 0x1; SubID/SubName: 0x409)]
255c.41c4:     [Raw version resource data: 0xbb0b0 LB 0x3a4, codepage 0x0 (reserved 0x0)]
255c.41c4:     ProductName:     Microsoft® Windows® Operating System
255c.41c4:     ProductVersion:  10.0.19041.1706
255c.41c4:     FileVersion:     10.0.19041.1706 (WinBuild.160101.0800)
255c.41c4:     FileDescription: Windows NT BASE API Client DLL
255c.41c4: \SystemRoot\System32\KernelBase.dll:
255c.41c4:     CreationTime:    2022-05-13T09:37:25.904947200Z
255c.41c4:     LastWriteTime:   2022-05-13T09:37:25.981546200Z
255c.41c4:     ChangeTime:      2022-05-13T21:27:08.226771300Z
255c.41c4:     FileAttributes:  0x20
255c.41c4:     Size:            0x2cf640
255c.41c4:     NT Headers:      0xf0
255c.41c4:     Timestamp:       0x458acb5b
255c.41c4:     Machine:         0x8664 - amd64
255c.41c4:     Timestamp:       0x458acb5b
255c.41c4:     Image Version:   10.0
255c.41c4:     SizeOfImage:     0x2cd000 (2936832)
255c.41c4:     Resource Dir:    0x2a4000 LB 0x548
255c.41c4:     [Version info resource found at 0x90! (ID/Name: 0x1; SubID/SubName: 0x409)]
255c.41c4:     [Raw version resource data: 0x2a40b0 LB 0x3bc, codepage 0x0 (reserved 0x0)]
255c.41c4:     ProductName:     Microsoft® Windows® Operating System
255c.41c4:     ProductVersion:  10.0.19041.1706
255c.41c4:     FileVersion:     10.0.19041.1706 (WinBuild.160101.0800)
255c.41c4:     FileDescription: Windows NT BASE API Client DLL
255c.41c4: \SystemRoot\System32\apisetschema.dll:
255c.41c4:     CreationTime:    2019-12-07T09:08:13.518339400Z
255c.41c4:     LastWriteTime:   2019-12-07T09:08:13.518339400Z
255c.41c4:     ChangeTime:      2022-05-13T09:38:12.902031600Z
255c.41c4:     FileAttributes:  0x20
255c.41c4:     Size:            0x1f538
255c.41c4:     NT Headers:      0xd0
255c.41c4:     Timestamp:       0x31288ce0
255c.41c4:     Machine:         0x8664 - amd64
255c.41c4:     Timestamp:       0x31288ce0
255c.41c4:     Image Version:   10.0
255c.41c4:     SizeOfImage:     0x20000 (131072)
255c.41c4:     Resource Dir:    0x1f000 LB 0x408
255c.41c4:     [Version info resource found at 0x48! (ID/Name: 0x1; SubID/SubName: 0x409)]
255c.41c4:     [Raw version resource data: 0x1f060 LB 0x3a8, codepage 0x0 (reserved 0x0)]
255c.41c4:     ProductName:     Microsoft® Windows® Operating System
255c.41c4:     ProductVersion:  10.0.19041.1
255c.41c4:     FileVersion:     10.0.19041.1 (WinBuild.160101.0800)
255c.41c4:     FileDescription: ApiSet Schema DLL
255c.41c4: NtOpenDirectoryObject failed on \Driver: 0xc0000022
255c.41c4: supR3HardenedWinFindAdversaries: 0x800
255c.41c4: \SystemRoot\System32\drivers\cfrmd.sys:
255c.41c4:     CreationTime:    2014-06-26T05:33:42.000000000Z
255c.41c4:     LastWriteTime:   2014-06-26T05:33:42.000000000Z
255c.41c4:     ChangeTime:      2020-10-11T11:10:28.369648400Z
255c.41c4:     FileAttributes:  0x20
255c.41c4:     Size:            0x9d20
255c.41c4:     NT Headers:      0xe8
255c.41c4:     Timestamp:       0x5004f2a1
255c.41c4:     Machine:         0x8664 - amd64
255c.41c4:     Timestamp:       0x5004f2a1
255c.41c4:     Image Version:   6.1
255c.41c4:     SizeOfImage:     0xe000 (57344)
255c.41c4:     Resource Dir:    0xc000 LB 0x3e0
255c.41c4:     [Version info resource found at 0x48! (ID/Name: 0x1; SubID/SubName: 0x409)]
255c.41c4:     [Raw version resource data: 0xc060 LB 0x380, codepage 0x0 (reserved 0x0)]
255c.41c4:     ProductName:     Windows (R) Win 7 DDK driver
255c.41c4:     ProductVersion:  6.1.7600.16385
255c.41c4:     FileVersion:     6.1.7600.16385 built by: WinDDK
255c.41c4:     FileDescription: Safe Deletion Driver
255c.41c4: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox'
255c.41c4: Calling main()
255c.41c4: SUPR3HardenedMain: pszProgName=VirtualBoxVM fFlags=0x2
255c.41c4: supR3HardenedWinInitAppBin(0x2): '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox'
255c.41c4: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe: Signature #1/2: info status: 24202
255c.41c4: '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe' has no imports
255c.41c4: supHardenedWinVerifyImageByHandle: -> 24202 (\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe)
255c.41c4: SUPR3HardenedMain: Final process, opening VBoxDrv...
255c.41c4: supR3HardenedEarlyCompact: Removed heap 1 (0x00000000f00000 LB 0x400000)
255c.41c4: supR3HardNtEnableThreadCreationEx:
255c.41c4: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VBoxSupLib.dll: Signature #1/2: info status: 24202
255c.41c4: supHardenedWinVerifyImageByHandle: -> 24202 (\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VBoxSupLib.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VBoxSupLib.dll
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\Program Files\Oracle\VirtualBox\VBoxSupLib.DLL (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
255c.41c4: supR3HardenedScreenImage/NtCreateSection: cache hit (Unknown Status 24202 (0x5e8a)) on \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VBoxSupLib.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbdcfb0000 LB 0x00005000 C:\Program Files\Oracle\VirtualBox\VBoxSupLib.DLL [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 24202 (0x5e8a)) on \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VBoxSupLib.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 24202 (0x5e8a)) on \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VBoxSupLib.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\Program Files\Oracle\VirtualBox\VBoxSupLib.DLL (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbdcfb0000 'C:\Program Files\Oracle\VirtualBox\VBoxSupLib.DLL'
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 24202 (0x5e8a)) on \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VBoxSupLib.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\Program Files\Oracle\VirtualBox\VBoxSupLib.DLL (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbdcfb0000 'C:\Program Files\Oracle\VirtualBox\VBoxSupLib.DLL'
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbdcfb0000 'C:\Program Files\Oracle\VirtualBox\VBoxSupLib.DLL'
255c.41c4: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'msvcrt.dll'.
255c.41c4: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #29 'rpcrt4.dll'.
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\wintrust.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\wintrust.dll
255c.41c4: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'rpcrt4.dll'...
255c.41c4: supR3HardenedWinVerifyCacheProcessImportTodos: 'rpcrt4.dll' -> '\Device\HarddiskVolume4\Windows\System32\rpcrt4.dll' [rcNtRedir=0xc0150008]
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\rpcrt4.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\rpcrt4.dll
255c.41c4: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'msvcrt.dll'...
255c.41c4: supR3HardenedWinVerifyCacheProcessImportTodos: 'msvcrt.dll' -> '\Device\HarddiskVolume4\Windows\System32\msvcrt.dll' [rcNtRedir=0xc0150008]
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\msvcrt.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\msvcrt.dll
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\system32\Wintrust.dll (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe26a0000 LB 0x0009e000 C:\WINDOWS\System32\msvcrt.dll [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\msvcrt.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe3970000 LB 0x00125000 C:\WINDOWS\System32\RPCRT4.dll [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\rpcrt4.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe2510000 LB 0x00068000 C:\WINDOWS\System32\Wintrust.dll [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\wintrust.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe1c70000 LB 0x00100000 C:\WINDOWS\System32\ucrtbase.dll [fFlags=0x0]
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\ucrtbase.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\ucrtbase.dll
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe1d70000 LB 0x00156000 C:\WINDOWS\System32\CRYPT32.dll [fFlags=0x0]
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\crypt32.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\crypt32.dll
255c.41c4: supR3HardenedIsApiSetDll: ApiSetQueryApiSetPresence(api-ms-win-core-synch-l1-2-0) -> 0x0, fPresent=1
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=api-ms-win-core-synch-l1-2-0 (rcNtResolve=0x0) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe2110000 'api-ms-win-core-synch-l1-2-0'
255c.41c4: supR3HardenedIsApiSetDll: ApiSetQueryApiSetPresence(api-ms-win-core-fibers-l1-1-1) -> 0x0, fPresent=1
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=api-ms-win-core-fibers-l1-1-1 (rcNtResolve=0x0) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe2110000 'api-ms-win-core-fibers-l1-1-1'
255c.41c4: supR3HardenedIsApiSetDll: ApiSetQueryApiSetPresence(api-ms-win-core-fibers-l1-1-1) -> 0x0, fPresent=1
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=api-ms-win-core-fibers-l1-1-1 (rcNtResolve=0x0) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe2110000 'api-ms-win-core-fibers-l1-1-1'
255c.41c4: supR3HardenedIsApiSetDll: ApiSetQueryApiSetPresence(api-ms-win-core-synch-l1-2-0) -> 0x0, fPresent=1
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=api-ms-win-core-synch-l1-2-0 (rcNtResolve=0x0) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe2110000 'api-ms-win-core-synch-l1-2-0'
255c.41c4: supR3HardenedIsApiSetDll: ApiSetQueryApiSetPresence(api-ms-win-core-localization-l1-2-1) -> 0x0, fPresent=1
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=api-ms-win-core-localization-l1-2-1 (rcNtResolve=0x0) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe2110000 'api-ms-win-core-localization-l1-2-1'
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\msasn1.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\msasn1.dll
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe1830000 LB 0x00012000 C:\WINDOWS\SYSTEM32\MSASN1.dll [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\msasn1.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe2510000 'C:\WINDOWS\system32\Wintrust.dll'
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\bcrypt.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\bcrypt.dll
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\system32\bcrypt.dll (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe1c40000 LB 0x00027000 C:\WINDOWS\System32\bcrypt.dll [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\bcrypt.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe1c40000 'C:\WINDOWS\system32\bcrypt.dll'
255c.41c4: bcrypt.dll loaded at 00007ffbe1c40000, BCryptOpenAlgorithmProvider at 00007ffbe1c451e0, preloading providers:
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\bcryptprimitives.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\bcryptprimitives.dll
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\system32\bcryptprimitives.dll (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe23e0000 LB 0x00082000 C:\WINDOWS\System32\bcryptprimitives.dll [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\bcryptprimitives.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe23e0000 'C:\WINDOWS\system32\bcryptprimitives.dll'
255c.41c4:     BCryptOpenAlgorithmProvider(,'MD2',0,0) -> 0x0 (hAlgo=00000000014417e0)
255c.41c4:     BCryptOpenAlgorithmProvider(,'MD4',0,0) -> 0x0 (hAlgo=0000000001441e60)
255c.41c4:     BCryptOpenAlgorithmProvider(,'MD5',0,0) -> 0x0 (hAlgo=0000000001442180)
255c.41c4:     BCryptOpenAlgorithmProvider(,'SHA1',0,0) -> 0x0 (hAlgo=00000000014434b0)
255c.41c4:     BCryptOpenAlgorithmProvider(,'SHA256',0,0) -> 0x0 (hAlgo=00000000014437d0)
255c.41c4:     BCryptOpenAlgorithmProvider(,'SHA512',0,0) -> 0x0 (hAlgo=0000000001443af0)
255c.41c4:     BCryptOpenAlgorithmProvider(,'RSA',0,0) -> 0x0 (hAlgo=0000000001443e10)
255c.41c4:     BCryptOpenAlgorithmProvider(,'DSA',0,0) -> 0x0 (hAlgo=0000000001444130)
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\cryptsp.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\cryptsp.dll
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe15f0000 LB 0x00018000 C:\WINDOWS\SYSTEM32\CRYPTSP.dll [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\cryptsp.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #18 'bcrypt.dll'.
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\rsaenh.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\rsaenh.dll
255c.41c4: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'bcrypt.dll'...
255c.41c4: supR3HardenedWinVerifyCacheProcessImportTodos: 'bcrypt.dll' -> '\Device\HarddiskVolume4\Windows\System32\bcrypt.dll' [rcNtRedir=0xc0150008]
255c.41c4: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\bcrypt.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\system32\rsaenh.dll (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
255c.41c4: supR3HardenedScreenImage/NtCreateSection: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\rsaenh.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe0cb0000 LB 0x00034000 C:\WINDOWS\system32\rsaenh.dll [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\rsaenh.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe0cb0000 'C:\WINDOWS\system32\rsaenh.dll'
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\cryptbase.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\cryptbase.dll
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe1610000 LB 0x0000c000 C:\WINDOWS\SYSTEM32\CRYPTBASE.dll [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\cryptbase.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\kernel32.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\System32\kernel32.dll (Input=kernel32.dll, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe3f20000 'C:\WINDOWS\System32\kernel32.dll'
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\wintrust.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\System32\WINTRUST.DLL (Input=WINTRUST.DLL, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe2510000 'C:\WINDOWS\System32\WINTRUST.DLL'
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\crypt32.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\System32\CRYPT32.dll (rcNtResolve=0xc0150008) *pfFlags=0x2 pwszSearchPath=0000000000000001:<flags> [calling]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe1d70000 'C:\WINDOWS\System32\CRYPT32.dll'
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe4280000 LB 0x0001d000 C:\WINDOWS\System32\imagehlp.dll [fFlags=0x0]
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\imagehlp.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\imagehlp.dll
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\rsaenh.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\system32\rsaenh.dll (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe0cb0000 'C:\WINDOWS\system32\rsaenh.dll'
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe2c30000 LB 0x0009c000 C:\WINDOWS\System32\sechost.dll [fFlags=0x0]
255c.41c4: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #11 'rpcrt4.dll'.
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\sechost.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\sechost.dll
255c.41c4: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'msvcrt.dll'.
255c.41c4: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #10 'rpcrt4.dll'.
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\gpapi.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\gpapi.dll
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe0510000 LB 0x00023000 C:\WINDOWS\SYSTEM32\gpapi.dll [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\gpapi.dll [lacks WinVerifyTrust]
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\profapi.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\profapi.dll
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe1b80000 LB 0x0001f000 C:\WINDOWS\SYSTEM32\profapi.dll [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\profapi.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'msvcrt.dll'.
255c.41c4: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #8 'crypt32.dll'.
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\cryptnet.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\cryptnet.dll
255c.41c4: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'crypt32.dll'...
255c.41c4: supR3HardenedWinVerifyCacheProcessImportTodos: 'crypt32.dll' -> '\Device\HarddiskVolume4\Windows\System32\crypt32.dll' [rcNtRedir=0xc0150008]
255c.41c4: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\crypt32.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'msvcrt.dll'...
255c.41c4: supR3HardenedWin"	Murdoch
18629	Failed to open a session for the virtual machine vm1.	VirtualBox 6.0.6	2019-05-08T17:58:12Z	2020-04-06T15:13:19Z	2020-04-06T15:13:19Z	"win 10 - pro version 1903 - fast ring updates

Failed to open a session for the virtual machine vm1.

Call to WHvSetupPartition failed: ERROR_SUCCESS (Last=0xc000000d/87) (VERR_NEM_VM_CREATE_FAILED).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

"	rolevsky
20257	Failed to open a session for the virtual machine Windows 10	VirtualBox 6.1.18	2021-03-17T00:57:45Z	2021-03-17T00:57:45Z	2021-03-17T00:57:45Z	"
Result Code: NS_ERROR_FAILURE (0x80004005)
Component:  MachineWrap
Interface:  IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}
"	AllisaJ
20256	Failed to open a session for the virtual machine Windows 10	VirtualBox 6.1.18	2021-03-17T00:57:42Z	2021-03-17T00:57:42Z	2021-03-17T00:57:42Z	"
Result Code: NS_ERROR_FAILURE (0x80004005)
Component:  MachineWrap
Interface:  IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}
"	AllisaJ
14561	Failed to open a session for the VM (0x80004005  Component:  MachineWrap)	VirtualBox 5.0.4	2015-09-09T11:14:15Z	2015-09-09T11:29:06Z	2015-09-09T11:29:06Z	I have a problem. Not start a new VM	SergeyO
17393	failed to open a session Machinewrap E_FAIL 0x80004005	VirtualBox 5.1.16	2017-12-23T11:43:15Z	2017-12-25T10:18:49Z	2017-12-25T10:18:49Z	"'''GUEST is UBUNTU,  Host is windos10.
'''   I JUST GOT UPDATED(small update) MY WINDOWS 10(earlier also windos10) HOST. before update of windos10, virtualbox working finely. After update, virtualbox not opening and shows error. failed to open a session Machinewrap E_FAIL 0x80004005. please try to help me in fixing.[[Image()]]"	SUPARI
19693	Failed to open a session the virtual machine in Win 7 Enterprise SP 1 64 Bit	VirtualBox 6.1.10	2020-07-02T04:10:29Z	2020-07-13T14:52:43Z	2020-07-13T14:52:43Z	"Dear all,

My windows:

Win 7 Enterprise 64 bit, SP1
Ram 8Gb
Virtualbox Latest ( 6.1.10 r138449 Qt5.6.2 )

when running to install Linux Mint, error show is below :

Result Code: 
E_FAIL (0x80004005)
Component: 
MachineWrap
Interface: 
IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}


please fix this is.

note: All my virtual already installed, error same.. could not run and failed session.


Thanks
"	n3wkid2019
18483	Failed to open session	VirtualBox 6.0.4	2019-03-09T19:56:15Z	2019-03-09T21:02:07Z	2019-03-09T21:02:07Z	"Hi!

I saved state of my virtual machine.
Sometimes I get error:
Result Code: E_FAIL (0x80004005)
Component: SessionMachine
Interface: ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}
"	SChernolyas
16522	Failed to open sessions after update to vm 5.1.14 on windows 7 sp1	VirtualBox 5.1.14	2017-03-01T07:12:01Z	2017-03-01T07:12:01Z	2017-03-01T07:12:01Z	"when i start vm it shows failed to open session for the virtual machine.
clicked details 
The virtual machine 'ORACLE LINUX 6.5' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'E:\VMware\ORACLE LINUX 6.5\Logs\VBoxHardening.log'.
Result Code: 
E_FAIL (0x80004005)
Component: 
MachineWrap
Interface: 
IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}

i have searched for solutions but could not solve it. i am new at vm.
"	Shahad Al Alam
20619	Failed to Restore VM	VirtualBox 6.1.26	2021-10-19T20:03:53Z	2021-10-19T20:06:26Z	2021-10-19T20:06:26Z	I am restoring the Virtual Machine and it stops completely.	desteves
20550	Failed to save machine state	VirtualBox 6.1.26	2021-09-15T16:14:23Z	2021-09-15T17:09:11Z	2021-09-15T17:09:11Z	"I got an error saving state of running VM. This was working previously, I recently updated VirtualBox, now using Version 6.1.26 r145957 (Qt5.6.2).

{{{
""H:\Program Files\Oracle\VirtualBox\VBoxManage.exe"" controlvm ""{XXXXXX}"" savestate
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...
Progress state: E_ACCESSDENIED
VBoxManage.exe: error: Failed to save machine state
VBoxManage.exe: error: Assertion failed: [SUCCEEDED(rc)] at 'F:\tinderbox\win-6.1\src\VBox\Main\src-server\MachineImpl.cpp' (10359) in long __cdecl Machine::i_saveStorageControllers(struct settings::Storage &).
VBoxManage.exe: error: COM RC=E_ACCESSDENIED (0x80070005).
VBoxManage.exe: error: Please contact the product vendor!
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component SessionMachine, interface IMachine
VBoxManage.exe: error: Context: ""enum RTEXITCODE __cdecl handleControlVM(struct HandlerArg *)"" at line 664 of file VBoxManageControlVM.cpp
}}}


"	Loenix
13942	Failed to start the virtual machine when seemingly unreachable	VirtualBox 4.3.24	2015-03-09T06:39:51Z	2015-03-23T11:28:17Z	2015-03-23T11:28:17Z	"I as a system connected to the virtual media used images located on a network drive.
In the case where the network drive is not available, the virtual system can not start.
  It would be better to just give a message about the unavailability of the resource, not to block the program."	and_kors
18984	failure to install tools	VirtualBox 6.0.12	2019-10-05T05:55:54Z	2019-10-05T16:00:05Z	2019-10-05T16:00:05Z	windows 10 host and guest. see screenshot.	DeGarden
17646	Failure to launch windows 10	VirtualBox 5.2.8	2018-03-29T01:44:05Z	2018-04-19T18:46:29Z	2018-04-19T18:46:29Z	"I'm not entirely sure what's going on. Every time I go to launch VirtualBox, VirtualBox Interface and VirtualBox Manager just sit in my tasks. No gui comes up. Nothing is changing. The processes are not using anything except for ram (which also doesn't change). It's not crashing. It's just nothing. I've tried installing the newest version. I tried the test version, Compatibility, administrator. All my drivers are up to date. I am honestly stumped. If anyone wants to give me some advice on how to fix this that would be great. If it helps at all I can run the free VMware just fine.

I don't have a log file because one is not created in this situation as it never crashes and continues to be benign

I am running 
latest version of windows 10 pro
AMD Ryzen 5 1600X
NVIDIA GeForce GTX 1070
"	Deszip
16321	Failure when trying to do a second clone from one machine	VirtualBox 5.1.12	2016-12-23T17:18:55Z	2016-12-23T17:18:55Z	2016-12-23T17:18:55Z	"I need to make a total of 5 clones from a VHD, all with their own diff drive. See [http://koussilicious.blogspot.ca/2016/12/70-462-training-kit-setup-preparation.html]; these instructions are for Hyper-V but I thought it would work in VirtualBox.

I was able to successfully clone once. But when I did the second, I got this message:

Failed to create a snapshot of the virtual machine 2012R2Parent.

Parent UUID {00000000-0000-0000-0000-000000000000} of the medium 'C:\Users\Will\VirtualBox VMs\2012R2Parent\Snapshots\{a0565d45-af1f-44d6-809a-904e04b32f85}.vhd' does not match UUID {98edf193-685e-4931-8a08-66942b857091} of its parent medium stored in the media registry ('C:\Users\Will\.VirtualBox\VirtualBox.xml').

Result Code: E_FAIL (0x80004005)
Component: MediumWrap
Interface: IMedium {4afe423b-43e0-e9d0-82e8-ceb307940dda}

So in thinking it was that you could not have multiple clones, I tried a clone of a clone. The UI allowed this, but when clicking Create, I got a similar message. When trying to do this a second time to get the error details, the clone on a clone was disabled.

One thing to note is that, as soon as the above happened, the parent VHD was hopelessly corrupted, requiring the VM to be deleted and the VHD to also be deleted."	Will Power
20353	Fallo al abrir una sesión para la máquina virtual Windows XP.	VirtualBox 5.1.26	2021-05-10T01:00:27Z	2021-05-10T01:00:27Z	2021-05-10T01:00:27Z	"Fallo al abrir una sesión para la máquina virtual Windows XP.

The virtual machine 'Windows XP' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\Alejandro Salcido\Downloads\virtualbox\Windows XP\Logs\VBoxHardening.log'.

Código Resultado: E_FAIL (0x80004005)
Componente: MachineWrap
Interfaz: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}

"	VASG
16651	fatal error in recompiler cpu (raw mode)	VirtualBox 5.1.18	2017-04-14T08:34:11Z	2018-04-09T05:48:09Z	2018-04-09T05:48:09Z	"VirtualBox VM 5.1.18 r114002 win.amd64 (Mar 15 2017 16:16:14) 

When I try to reboot a VM that avails worked fine I got this error.
When I use a cone of the same VM all works fine.  "	Giorgio SIlvio
17752	fatal error in recompiler cpu: Trying to execute code with memory type	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
8893	FATAL: Int13_diskette_function: read error	VirtualBox 4.0.6	2011-05-15T00:24:22Z	2011-08-12T09:18:42Z	2011-08-12T09:18:42Z	"Win7Pro w/8GB mobo is Gigabyte 870A-UD3, CPU is AMD Phenom II X6 1075T.  Guests are MS-DOS 6.2 and MS-DOS 6.22.  Multiple error situations.  Both guests crash with error message:  FATAL: Int13_diskette_function: read error.  Same happens with USB Floppy drive.

I've replaced the internal Diskette drive but get the same results.  I can't operate these guests without diskette support.

Please help."	Bill Peavy
18666	feature request	VirtualBox 6.0.8	2019-05-21T15:52:31Z	2019-05-21T15:52:31Z	2019-05-21T15:52:31Z	add built in boot to netboot.xyz (https://netboot.xyz/downloads/)	foilguitar
12403	Feature Request - Mount VDI as Windows Drive	VirtualBox 4.3.2	2013-11-28T10:40:53Z	2013-11-28T10:40:53Z	2013-11-28T10:40:53Z	It would be of great use if VB can provide a way to mount VDI directly in Windows as disk drives and let me defrag it without need to boot into guest OS.	Edward Yang
11211	Feature request: add auto update functionality	VirtualBox 4.2.4	2012-11-19T15:10:13Z	2020-07-22T18:02:36Z	2020-07-22T18:02:36Z	Downloading an new version every time you need to update isn't very user-friendly. Please add an auto-update function (on Mac – don't know about Windows), this would save a lot of people a little bit of time, which in the end is a lot of time ;-).	dink
18845	Feature Request: Automatically enable virtualization	VirtualBox 6.0.10	2019-08-16T15:28:36Z	2019-08-16T15:28:36Z	2019-08-16T15:28:36Z	"Some of us users either do not have the necessary virtualization components for Virtualbox running on our computers, or do not know how to enable them.
Why not have Virtualbox check during install and attempt to enable VT-X or AMD-v as needed from the GUI?

Some manufacturers take advantage of a software way to enable hardware virtualization anyway:
https://stackoverflow.com/questions/31581854/enabling-intel-virtualization-vt-x-without-option-in-bios
https://software.intel.com/en-us/android/articles/intel-hardware-accelerated-execution-manager"	JEB
17222	"Feature request: create full/complete snapshots instead of ""differential"""		2017-10-28T13:48:31Z	2017-10-28T13:48:31Z	2017-10-28T13:48:31Z	"I usually need to create many snapshots at different points in time. This makes a mess, because every snapshot is a child of the one before, and deleting any of them take HOURS.

I'd die for the ability to create '''full/complete snapshots''' without any hierarchy tree above!

Disussion here: https://forums.virtualbox.org/viewtopic.php?f=1&t=85226"	gianluigi.zanettini
721	Feature request: ieee1394 (Firewire) UHCI/OHCI pass-through support	VirtualBox 1.5.0	2007-09-28T02:46:19Z	2010-10-15T18:08:17Z	2010-10-15T18:08:17Z	"ieee1394 (Firewire) OHCI/UHCI support for Windows guests on Linux hosts would be a great boon to musicians and videographers everywhere. Perhaps a VirtualBox Guest Addition adding a virtual firewire chipset driver?

Many pro audio companies such as Alesis, Mackie, M-Audio etc. have great audio interfaces which sadly have no Linux drivers...

Firewire is the *last* thing keeping me (and others) from running fully virtual Windows installations on Linux. It seems no other solutions (VMWare, etc.) have given Firewire a priority. VirtualBox could really pull ahead of the pack here by being the first!
"	Russ Magee
3887	Feature request: make VirtualBox compatible with Virtual PC guest additions, since that supports MS-DOS, Windows 3.1/95/98	VirtualBox 2.2.2	2009-04-30T00:32:20Z	2009-04-30T00:32:20Z	2009-04-30T00:32:20Z	"It would be a great idea if guest additions could be provided for MS-DOS, Windows 3.1, 95 and 98. If the VirtualBox developers need to obtain the Windows 3.1 or 95 DDKs, let me know.

Of course, developing guest additions for those older OSes would take a lot of development time. As an alternative, would it be possible to implement compatibility with guest additions used by Microsoft Virtual PC (2004/2007)? Then MS-DOS and Windows 3.1/95/98 could have guest additions support without much extra work; The user would just need to install the additions from Virtual PC. Also, image files created with Virtual PC would then be completely usable with VirtualBox without needing to uninstall/install additions.
"	Donuts
7837	Feature Request: Option to hide Additions mismatch warning	VirtualBox 3.2.12	2010-12-13T04:10:44Z	2011-01-17T17:02:43Z	2011-01-17T17:02:43Z	"Currently, if the ""guest properties"" feature is used, VirtualBox will check a guest to see what version of the Guest Additions are installed. If the version of the additions that are currently loaded in the guest do not exactly match the version of VirtualBox that you are running, a warning dialog is presented in the guest indicating that you may want to update the Additions.

This is a bit irritating, as there are several legitimate reasons to run mis-matched versions. For example, if you compile your own OSE version, Guest Additions will only be generated for the platform you compiled on. So if you don't have access to a build environment for the other platforms, the only choice is to use the official Additions ISO. Up until 4.0, there was a distinction made between the OSE version and the PUEL, so even if you were running the same version of the Additions, you would get a warning if one was OSE and the other PUEL. I assume that won't be an issue anymore with the move to the open core, but the same can easily be said for testing SVN versions, or making customized versions, etc.

Also, there a a few GNU/Linux distros that ship with Guest Additions pre-installed, and since most of the time the core functionality still works, there is no compelling need to upgrade. And there are still other distros that ship older versions of VirtualBox in their repositories, and you may be sharing Virtual Machines with multiple distros across a LAN -- since each distro may have a different version of VirtualBox installed, the error will pop up on some distros but not others.

In any event, I've currently worked around this issue by disabling the guest properties feature at compile time, but that disables an entire feature set that is otherwise useful.

I admit this is a bit of a specialized request, but it would be great to be able to be able to either disable this warning message alone at compile time, or be able to suppress it somewhere within the VirtualBox settings."	Twisted Lincoln, Inc.
6917	Feature request: Prevent guest resolution auto adjust	VirtualBox 3.2.2	2010-06-07T08:16:38Z	2010-06-07T08:16:38Z	2010-06-07T08:16:38Z	"Hello,
I'm using VBox Windows XP.
Coming out of full screen mode, the guest window is automatically adjusted to the guest's resolution.
Can this behavior be disabled?

For clarity, here is a detailed example:
I have a screen resolution of 1680x1050.
I set the resolution inside the guest to 1680x1050 (so that I can enjoy my full screen real estate when in full screen mode).
I resize the guest window to 100x100 pixels.
I go to full screen mode.
I come out of full screen mode.
=> The guest window doesn't retrieve its size of 100x100! Rather, VBox is trying to stretch it all over the screen to set its size to 1680x1050.
So, I have to resize it back to 100x100, manually.

Yes, if I enable Host+G, it will go back to 100x100 automatically when I come out of full screen mode, but it will also *change the guest resolution* (an even worse problem, because when I go into full screen mode again, all windows sizes and desktop icon positions in the guest are messed up)!

I hope this is clear. I need the guest resolution to never be touched AND the guest window to retrieve its previous size automatically when coming out of full screen mode (with scroll bars, if needed).

Also, a button to go to full screen mode would be nice, instead of having to navigate menus.

Regards."	ExpertNoob
9389	Feature Request: Shutdown host if guest is shut down	VirtualBox 4.1.0	2011-08-06T03:39:02Z	2011-08-16T10:21:34Z	2011-08-16T10:21:34Z	"i want to suggest a new feature that automatically shutdown the host computer when the guest shutdown or turned off, and maybe scheduled shutdown or turn off for guest OS
"	Handi Tang
8849	Feature Request: Snapshot Immutable Images and Enhanced Branching	VirtualBox 4.0.6	2011-05-04T22:23:10Z	2011-05-05T06:39:38Z	2011-05-05T06:39:38Z	"Snapshots:
Snapshots in VMware 7 have a number of advantages: 
They have automatic snapshots every few days + ability to create new VM from snapshots (aka differencing-immutable images).

Another enhancement of the snapshot system would be; having the ability to branch out from many saved states and from the current one. An example of what I am talking about:
 [[Image(http://s.techairlines.com/wp-content/uploads/2009/09/VMware-Snapshots.png)]]

It would be very useful. Thanks for considering."	DNS
14644	Feature request: Support self-adapting framebuffer console on GNU/Linux guest	VirtualBox 5.0.4	2015-09-29T11:40:05Z	2015-09-29T15:12:33Z	2015-09-29T15:12:33Z	"Currently on GNU/Linux guest vesafb will be used in the TTY console, AFAIK it is possible to manually set custom screen resolutions for VM to use but it will be better if there's a framebuffer driver that can self-adapt the size of the TTY console to the size of VM window(just as on X Window System)

Please consider it if it's possible, thanks in advance!

"	林博仁(Buo-Ren Lin)
17313	Feature: Keyboard scancode translation	VirtualBox 5.1.30	2017-11-26T06:16:09Z	2017-11-26T06:16:09Z	2017-11-26T06:16:09Z	"Most modern keyboards use IBM scancodes, and so VirtualBox users are likely to get fairly consistent behavior when sending these scancodes to just about every VM, via VBoxManage controlvm <vm> keyboardputscancode <hexpair>... However, macOS guest VM's use a different scancode set, one for Apple keyboards. This does not present a problem for most graphical VirtualBox users, however it does break some things for command line driven systems such as packer.io. In particular, systems like packer that are built on top of VirtualBox and want to send key codes to macOS VM's are faced with the nuisance of performing scancode translation. I propose that VirtualBox offer a VM configuration option like:

VBoxManage modifyvm <VM> --fromscancodes ibm --toscancodes apple

or similar flag syntax, that declares that VirtualBox should automatically remap scancodes sent via VBoxManage controlvm <VM> keyboardputscancode <hexpair>..., relieving packer and other tools from having to worry about such low level details (packer could then simply use IBM scancodes all the time).

I've also filed a ticket with packer to select more appropriate scancode sets for different kinds of VM's:

https://github.com/hashicorp/packer/issues/5635

As a mac user, I really don't care which of these is implemented, I just want to be able to use macOS guest VM's without having to hack around keyboard incompatibility issues!"	mcandre
15572	Fedora 24 Kernel 4.3.6-300 Breaks VB 5.0.24 on Mac OS X 11.5	VirtualBox 5.0.24	2016-07-05T17:53:41Z	2016-08-16T21:25:27Z	2016-08-16T21:25:27Z	"If I try to save a Fedora 24 session ( kernel 4.3.6-300) on my Macbook Pro. The status
starts off as 'Saving' but changes to 'Aborted' 

The 'Aborted' session, of course, cannot be restarted. However if the Fedora Session is
shutdown then the  image can be rebooted.

In addition, when the Fedora image reboots, a black screen appears and it is necessary to
click on the screen to see the desktop.

Reverting back to kernel 4.5.7-200 fixes the problem.
"	jerrysVB
19215	Fedora 31 Workstation - Hang and Crash	VirtualBox 6.1.0	2020-01-09T21:43:16Z	2020-01-20T13:46:23Z	2020-01-20T13:46:23Z	The  laptop lid was closed but the PC was still running and when I opened up the lid and tried to access the Fedora 31 Workstation VM, the UI didnt response to keyboard/mouse.   I tried to select from the menu ACPI Shutdown and there was no reponse and finally tried Input->Keyboard->Insert CTRL+ALT+DEL.  The VM started shutting down and crashed either coming back up.	Aquis7
19922	Fedora 32 Workstation official ISO fails to install stating integrity problems	VirtualBox 6.1.14	2020-09-27T19:29:36Z	2020-09-27T19:29:36Z	2020-09-27T19:29:36Z	"I download https://torrent.fedoraproject.org/torrents/Fedora-Workstation-Live-x86_64-32.torrent from https://torrent.fedoraproject.org/ . While torrent guarantees file isn't corrupt, I also check the file per vendor instructions.

 sha256sum -c Fedora-Workstation-32-1.6-x86_64-CHECKSUM
Fedora-Workstation-Live-x86_64-32-1.6.iso: OK

When I try to install this specific image, its media check stops at exactly 4.8% and suggests not to use this image. If you ignore (e.g. disable check), it doesn't succeed booting anyway.

Today, I installed VMWare Workstation Player 16 and amazingly, very same ISO passed every test and installed fine. I think I may have triggered a Virtualbox (or windows?) bug."	Ilgaz
20832	Fedora-35 HOST + Windows 10/11 GUEST: Keyboard entries and Touchpad Taps stop responging, after ~10m	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
9430	Fedora15 does not hook into my wireless connection	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
18281	Feedback of /sbin/vboxconfig on failing module load not always helpful	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
15657	File drag from linux host to windows vm when filename has colon causes error	VirtualBox 5.1.0	2016-07-21T15:52:23Z	2016-07-21T15:52:23Z	2016-07-21T15:52:23Z	"Steps to reproduce
1. Take screenshot in Linux Mint Xfce 17.1
2. Save to file, default name includes colon
3. Drag to windows

Expected results
File drags successfully

Actual results
Drag and drop error due to invalid name

Windows uses colon's for alternate data streams so they can't be used in file names."	cosmotic
20253	file system damage on flashUSB	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
13925	file timestamp not preserved on tar-extracted files in shared folders on linux guest windows host	VirtualBox 4.3.24	2015-03-05T17:36:29Z	2015-03-05T17:36:29Z	2015-03-05T17:36:29Z	"There is a strange behavior, that files extracted from TAR package within shared folders on Linux guest/Windows host, does not preserve file timestamp stored in a tarball. The files' timestamp get converted to the extraction time.

I've searched through Virtualbox issues, and saw another ticket regarding timestamp in shared folders, #6473, but that was solved years ago, and does not apply to this particular issue.

Issue is easily reproducable:
- configuration: Windows 7 Host, Linux (Debian, no GUI) Guest
- using tar command from a Linux Guest shell, create a TAR of an older ""test file"", so the timestamp would be evident,
- delete the ""test file""
- extract the ""test file"" from a tar archive
- the timestamp will be wrong, as tar preserves timestamp by default
- to confirm we can do the same procedure within another Linux Guest folder, other than the shared folder, and the timestamp will be preserved.

Here's code sample, presuming we have a file.pdf test file, within /var/www/shared folder, which is a shared folder, both Linux guest and Windows 7 host can see:

{{{
cd /var/www/shared
ls -la
> -rwxrwxrwx 1 root root 11654 Jan 23 08:16 file.pdf
tar -c -f test.tar file.pdf
rm file.pdf
tar -x -f test.tar
ls -la
> -rwxrwxrwx 1 root root 11654 Mar 5 17:30 file.pdf
> -rwxrwxrwx 1 root root 11654 Mar 5 17:30 test.tar
}}}

I would kindly ask anyone to answer if there is a solution to this problem, or is there anything we can do to preserve original timestamps at tar extraction process within shared folders, so we don't need to extract files in a separate folders and move the files back, as we need those timestamps.

We have both, current Virtualbox and current Guest Additions installed."	sargac
18941	First keypress are repeated multiple times	VirtualBox 6.0.12	2019-09-18T06:56:45Z	2019-09-18T06:56:45Z	2019-09-18T06:56:45Z	"Working with MS Project. When creating a new task and then trying to type in the either the successor or predesessor then the first keypress is repeated multiple times (not less than 5 times, but have been seen up to 15 times). So having a task with id 400 and it's predecessor is 399, then typing 399 results in 333333333333399. It's the first keypress no matter what key, this includes the ""Enter-key"" - this has not happened before in earlier versions. 
I can't use this version."	Jan P DK
3128	Fix PCI ID vendor	VirtualBox 2.1.2	2009-01-23T16:46:24Z	2009-11-16T08:10:28Z	2009-11-16T08:10:28Z	The pciid of the graphics card is still branded to Innotek GmbH while i.e. the BIOS bootup screen is not in the latest 2.1.2 release. This is a bit misleading - is this really intended?	Daniel Kulesz
17940	For Fedora, Virtualbox is being built for unsupported releases (Fedora 26)	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
21115	freeze gnome gui ubuntu	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
21318	Freeze on Oracle Linux 9.1 w. UEK Kernel	VirtualBox-7.0.4	2022-11-28T14:07:56Z	2023-02-01T10:53:39Z	2023-02-01T10:53:39Z	"'''Issue:'''
VirtualBox 7.0.4 freezes immediatly when started on Oracle Linux 9.1 with the default UEK kernel running. It freezes so hard that not even a single line is written to the kernel log, so i have not even an idea what is causing this. This does not occur when the system is booted with the RedHat-Compatible Kernel (RHCK).

'''How to reproduce:'''

1. Install Oracle Linux 9.1 and apply all updates
2. Install VirtualBox 7.04 official RPM build 
3. Create any VM and start it

The system i have used to reproduced the behavior is a AMD Epyc with AMD-V enabled if that makes any difference."	Egon Rath
17590	Freezing every time a BSOD appears on Windows 10 guest	VirtualBox 5.2.8	2018-03-05T20:28:58Z	2018-04-22T17:25:16Z	2018-04-22T17:25:16Z	I am running the latest VirtualBox and every time a bsod appears Windows 10 it will also freeze	Neptune BSC LLC
21498	"French translation missing for ""System"""	VirtualBox-7.0.6	2023-02-12T19:55:21Z	2023-02-12T19:55:21Z	2023-02-12T19:55:21Z	"French translation missing for ""System""
should be ""Système"""	Kyle_Katarn
13432	Frequent BSOD's on Windows guests since 4.3.x	VirtualBox 4.3.16	2014-09-24T22:46:10Z	2014-11-25T22:46:21Z	2014-11-25T22:46:21Z	"I've been running everything from 4.3.10 to 4.3.15 and I'm getting constant bluescreens in Windows 7 guests. They are fresh instals as well as older guests. The timing seems to be random, but always within a few minutes. When I can catch the BSOD information, it's regarding ""REFERENCE_BY_POINTER"". The bugcheck is 0x00000018.

At first I thought it was a memory issue, but it occurs even when there is very little memory load on the host.  Host is XP SP3, Intel Core2Duo, 2.93Ghz, 3GB Ram.  I ran a full memory diagnostic which found no problems.

I've done some experimenting, and I can recreate this issue even with barely any memory load on the host. I rolled back to one of the earlier versions that I knew had worked, 4.2.6, and I cannot recreate a single crash, even with an intentionally heavy memory load on the host. I tried several other 4.2.x builds and stopped at 4.2.16. (Newer builds lead to the well-known security issues that also affect the latest 4.3.x branch).  On all of these 4.2.x builds, I just can't get a crash to happen, no matter how hard I try.

Because this didn't happen at all until I upgrade to 4.3.x, I tend to think there's a regression of some kind in 4.3.x.  If anyone is so kind as to take a look at this, I am more than happy to provide additional logs, testing, or information.  

Thanks for reading!"	mjdbb1
19294	Frequent crashing with The Instruction at 0x... referenced memory at 0x... The memory could not be read	VirtualBox 6.1.2	2020-02-06T15:51:02Z	2020-02-07T17:27:51Z	2020-02-07T17:27:51Z	"I have read many similar posts and tried the recommended fixes, but I am still having the issue. 

Host: Windows 10 pro, 16Gb ram, updated the video drivers
Guest: Ubuntu, 8Gb, 256Mb video mem

Seems to happen most frequently when I am running VSCode and click on any menu or context menu.

Attaching logs"	tdsTPPS
18957	Frequent freezes in display output since 6.0	VirtualBox 6.0.12	2019-09-23T12:04:52Z	2020-02-18T14:44:02Z	2020-02-18T14:44:02Z	"Since I updated from 5.2.x to 6.0.x I have problems with my Windows 10 guest. The problems manifest as freezes/pauses/hangs in the UI. The whole display output freezes and a bit later suddenly jumps to the desired output. This is especially visible in continuus animations, but annoying everywhere, especially while typing text.

This happens at least with:
* VBoxVGA without 3D acceleration
* VBoxSVGA without 3D acceleration
* VBoxSVGA with 3D acceleration

I didn't test VMSVGA. 2D-video acceleration settings don't seem to have an effect on the problem.

When I downgrade to 5.2.x (last I tried was 5.2.22) the problem is gone.

With 6.0.2 and 6.0.4 it was very easy to reproduce the problem, nearly every start of the guest showed it. With later versions (6.0.10 and especially 6.0.12) it got better (harder to reproduce). Now the problem only shows up every ~10 starts of the guest.

To get or ""fix"" the problem it is not enough to do a restart of the guest. A full shutdown and cold start is requried.
Additionally the problem can also start when you resume the guest from a saved state. But it seems like a resume can not ""fix"" it.

More information and multiple log files from older VirtualBox versions can be found in the forums: https://forums.virtualbox.org/viewtopic.php?f=2&t=91836

Configuration details:

* VirtualBox 6.0.12 (I could also reproduce it with 6.0.2, 6.0.4 and 6.0.10)
* No extension pack installed
* Guest Additions 6.0.12
* Host OS: Windows 10 x64 1809 (I could also reproduce it with 1803)
* GPU: Intel HD Graphics 530 with driver 26.20.100.6912 (I could also reproduce it with 25.20.100.6519)
* 2 monitors with 1920x1080 resolution (I could also reproduce it with just 1 monitor)
* All monitors (both host and VM) at 100% scaling
* Guest OS: Windows 10 x64 1809 (I could also reproduce it with 1709)
* Guest is running in full screen mode
* Guest settings:
  * 3 of 4 CPU cores (I could also reproduce it with just 2 cores assigned)
  * 10 of 16 GB RAM
  * VRAM at maximum (128/256 MB)
  * All other settings are at their default for a Windows 10 x64 VM"	cremor
19684	Frequent IO Read overload freezing the OpenSUSE VM	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
15174	Fresh install of windows 10 stops responding (repeatable).	VirtualBox 5.0.14	2016-02-23T19:48:20Z	2019-02-25T17:36:04Z	2019-02-25T17:36:04Z	"Windows 10 guest stops responding after leaving it run in the background.  It may have something to do with how windows 10 sleeps or hibernates.   Maybe something to do with the power settings and how it lets hard disks spin down or other such things.   The screen looks fine (not black).  The mouse doesn't move.  It doesn't respond to Ctrl-Alt-Delete.   It doesn't respond to “Send the shutdown signal”.   Sending the “Power off the machine” does close the box and restarting it doesn't give me the options for safe more like windows 7 did.  

Running on Windows 7 Ultimate Host."	isgdre
19911	Fresh VM always crashing due to RAM issue	VirtualBox 6.1.14	2020-09-23T08:31:44Z	2020-09-23T08:31:44Z	2020-09-23T08:31:44Z	"Hey,

recently I built a new computer with 16 GB of DDR4 ram, a Ryzen 7 3700X and a Nvidia RTX 2060 Super. On my old one I never experienced any problems with Virtualbox but now any new VM I create crashes right after I reboot it after installation (Every driver I can think of is up-to-date). 

Of course I will supply more information if you need any. Maybe the log files can already help a lot with this problem.

Thanks in advance

PT400C"	PT400C
16347	Full screen mode broken on MacOS hosts with Guest additions 5.1.4 and later	VirtualBox 5.1.12	2017-01-02T11:11:17Z	2018-05-25T19:57:59Z	2018-05-25T19:57:59Z	"I am running VBOX on MacOS. I am tracking both MacOS versions (currently on macOS Sierra (10.12.2), and VirtualBox versions (currently on 5.1.12). I use all my VMs (Linux) in full screen mode

Last september I had upgraded VBOX to 5.1.4. I then upgraded the guest editions to 5.1.4 as well As a result, full screen mode stopped working: the VMs no longer occupied the whole screen, but only part of it. Luckily I was able to go back to the previous guest additions (5.0.20) and got full screen back to working as usual.

Today I upgraded VBOX to 5.1.12 and tried again upgrading the guest additions to 5.1.12. Same effect: full screen broken the same way (full screen no longer occupies the entire screen). Again, downgraded guest additions to 5.0.20.

What seems to happen is that the guest additions somehow no longer automatically match the resolution of the VM screen to the resolution of the host display (1280x800).

I also see differences in the View menu. 
With guest additions 5.0.20, the View menu is like this:
- Full Screen Mode (Host+F) is checked
- Auto Resize Guest Display is checked.
- Scaled Mode (Host+L) is unchecked

With guest additions 5.1.4 and later:
- Full Screen Mode (Host+F) is checked
- Auto Resize Guest Display is checked but greyed out
- Scaled Mode (Host+L) is unchecked but greyed out


"	agodfrin
16931	Full screen mode unusable on RHEL 6 since VBox 5.0, still not fixed	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
17862	Full screen view out of sync	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
18164	FUll screen with VBox 5.2.22 on windows 7	VirtualBox 5.2.22	2018-12-02T16:15:47Z	2018-12-02T17:50:11Z	2018-12-02T17:50:11Z	"Hi,
I have been using fedora as guest system on windows 7 hosted VBox since years. Yesterday I upgraded from 5.2.18 to 5.2.22 and installed also the vbox additions for it under fedora 29 (linux 4.19).
As a result of this upgrade, suddenly full screen does not work, only normal window mode as well as the adaptive mode (Host-C) are working. Switching to full screen results in the screen freezing - reacting neither to mouse nor to keyboard."	TomKov
17955	fullscreen and gpu passtrough	VirtualBox 5.2.18	2018-08-25T22:49:27Z	2018-08-26T15:11:35Z	2018-08-26T15:11:35Z	windows User account control (run app like admin) does not work in fullscreen. Also I want gpu passtrough. I installed windows vista. Other OS was not tested. Internet is slow like turtle and it sometimes show latency error. I installed extensions and guest additions by iso. My device is asus g750jh with windows 10 insider preview 17744.	puppygamer1994
19287	gcc10 problems	VirtualBox 6.1.2	2020-02-05T08:27:40Z	2020-02-09T02:11:43Z	2020-02-09T02:11:43Z	"We've got reports of probelsm compiling the vbox code base with the newest GCC version 10. See below:

[https://www.virtualbox.org/pipermail/vbox-dev/2020-February/015411.html][[BR]]

{{{
From: ""Sérgio Basto"" <>
To: vbox-dev@virtualbox.org
Cc:
Subject: [vbox-dev] problem with new GCC 10
Date: Wed, 05 Feb 2020 02:06:27 +0100

Hi,
Now seems to me, GCC10 forbids multiple definitions , I got at least  3  
packages with this
problem (of multiple definitions [1])  but in Virtual Box we have thousand  
of lines this these [2]

Best regards,

[1]
https://github.com/telmich/gpm/pull/37

[2]
ld:  
/builddir/build/BUILD/VirtualBox-6.1.2/obj/obj/iPxeBaseBin/src/arch/i386/core/relocate.o:(.bss+0x0):  
multiple definition of `__licence_public_domain';  
/builddir/build/BUILD/VirtualBox-6.1.2/obj/obj/iPxeBaseBin/src/arch/i386/core/basemem_packet.o:(.bss+0x0):  
first defined here
ld:  
/builddir/build/BUILD/VirtualBox-6.1.2/obj/obj/iPxeBaseBin/src/arch/i386/core/relocate.o:(.bss+0x1):  
multiple definition of `__licence_gpl2_only';  
/builddir/build/BUILD/VirtualBox-6.1.2/obj/obj/iPxeBaseBin/src/arch/i386/core/basemem_packet.o:(.bss+0x1):  
first defined here
ld:  
/builddir/build/BUILD/VirtualBox-6.1.2/obj/obj/iPxeBaseBin/src/arch/i386/core/relocate.o:(.bss+0x2):  
multiple definition of `__licence_gpl2_or_later';  
/builddir/build/BUILD/VirtualBox-6.1.2/obj/obj/iPxeBaseBin/src/arch/i386/core/basemem_packet.o:(.bss+0x2):  
first defined here
ld:  
/builddir/build/BUILD/VirtualBox-6.1.2/obj/obj/iPxeBaseBin/src/arch/i386/core/timer2.o:(.bss+0x0):  
multiple definition of `__licence_public_domain';  
/builddir/build/BUILD/VirtualBox-6.1.2/obj/obj/iPxeBaseBin/src/arch/i386/core/basemem_packet.o:(.bss+0x0):  
first defined here
ld:  
/builddir/build/BUILD/VirtualBox-6.1.2/obj/obj/iPxeBaseBin/src/arch/i386/core/timer2.o:(.bss+0x1):  
multiple definition of `__licence_gpl2_only';  
/builddir/build/BUILD/VirtualBox-6.1.2/obj/obj/iPxeBaseBin/src/arch/i386/core/basemem_packet.o:(.bss+0x1):  
first defined here
ld:  
/builddir/build/BUILD/VirtualBox-6.1.2/obj/obj/iPxeBaseBin/src/arch/i386/core/timer2.o:(.bss+0x2):  
multiple definition of `__licence_gpl2_or_later';  
/builddir/build/BUILD/VirtualBox-6.1.2/obj/obj/iPxeBaseBin/src/arch/i386/core/basemem_packet.o:(.bss+0x2):  
first defined here
ld:  
/builddir/build/BUILD/VirtualBox-6.1.2/obj/obj/iPxeBaseBin/src/arch/i386/firmware/pcbios/basemem.o:(.bss+0x0):  
multiple definition of `__licence_public_domain';  
/builddir/build/BUILD/VirtualBox-6.1.2/obj/obj/iPxeBaseBin/src/arch/i386/core/basemem_packet.o:(.bss+0x0):  
first defined here
ld:  
/builddir/build/BUILD/VirtualBox-6.1.2/obj/obj/iPxeBaseBin/src/arch/i386/firmware/pcbios/basemem.o:(.bss+0x1):  
multiple definition of `__licence_gpl2_only';  
/builddir/build/BUILD/VirtualBox-6.1.2/obj/obj/iPxeBaseBin/src/arch/i386/core/basemem_packet.o:(.bss+0x1):  
first defined here
ld:  
/builddir/build/BUILD/VirtualBox-6.1.2/obj/obj/iPxeBaseBin/src/arch/i386/firmware/pcbios/basemem.o:(.bss+0x2):  
multiple definition of `__licence_gpl2_or_later';  
/builddir/build/BUILD/VirtualBox-6.1.2/obj/obj/iPxeBaseBin/src/arch/i386/core/basemem_packet.o:(.bss+0x2):  
first defined here
ld:  
/builddir/build/BUILD/VirtualBox-6.1.2/obj/obj/iPxeBaseBin/src/arch/i386/firmwarel2_or_later';  
/builddir/build/BUILD/VirtualBox-6.1.2/obj/obj/iPxeBaseBin/src/arch/i386/core/basemem_packet.o:(.bss+0x2):  
first defined here
}}}

refer to:

[https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85678][[BR]]
[https://gcc.gnu.org/gcc-10/porting_to.html#common][[BR]]

THe complains are about:

trunk/src/VBox/Devices/PC/ipxe/src/include/compiler.h

{{{
653 #define FILE_LICENCE_PUBLIC_DOMAIN \
654         PROVIDE_SYMBOL ( __licence_public_domain )

662 #define FILE_LICENCE_GPL2_OR_LATER \
663         PROVIDE_SYMBOL ( __licence_gpl2_or_later )

671 #define FILE_LICENCE_GPL2_ONLY \
672         PROVIDE_SYMBOL ( __licence_gpl2_only )

683 #define FILE_LICENCE_GPL_ANY \
684         PROVIDE_SYMBOL ( __licence_gpl_any )

[...]
 60 /** Provide a symbol within this object file */
 61 #ifdef ASSEMBLY
 62 #define PROVIDE_SYMBOL( _sym )                          \
 63         .globl  _sym ;                                  \
 64         .comm   _sym, 0
 65 #else /* ASSEMBLY */
 66 #define PROVIDE_SYMBOL( _sym )                          \
 67         char _sym[0]
 68 #endif /* ASSEMBLY */
}}}"	Frank Batschulat (Oracle)
21413	gdb crashes	VirtualBox-7.0.4	2023-01-17T14:26:49Z	2023-01-19T16:47:58Z	2023-01-19T16:47:58Z	"centos 8/9 x64_86 under virtualbox 7.0.4, mac os Ventura 13.1, intel based macbook pro (2,4 GHz 8-Core Intel Core i9)

if i try to start any application under gdb:

Program received signal SIGSEGV, Segmentation fault.
0x0000aaaa9aa62009 in ?? ()
(gdb) bt
#0 0x0000aaaa9aa62009 in ?? ()
#1 0x00007ffff7feae68 in dl_main (phdr=<optimized out>, phnum=<optimized out>, user_entry=<optimized out>, auxv=<optimized out>) at rtld.c:1883
#2 0x00007ffff7fe7183 in _dl_sysdep_start (start_argptr=start_argptr@entry=0x7fffffffe120, dl_main=dl_main@entry=0x7ffff7fe9000 <dl_main>) at ../sysdeps/unix/sysv/linux/dl-sysdep.c:140
#3 0x00007ffff7fe8ad8 in _dl_start_final (arg=0x7fffffffe120) at rtld.c:502
#4 _dl_start (arg=0x7fffffffe120) at rtld.c:587
#5 0x00007ffff7fe7ba8 in _start () from /lib64/ld-linux-x86-64.so.2
#6 0x0000000000000003 in ?? ()
#7 0x00007fffffffe3dd in ?? ()
#8 0x00007fffffffe3ef in ?? ()
#9 0x00007fffffffe46d in ?? ()
#10 0x0000000000000000 in ?? ()

GDB used to work fine on the previous VirtualBox (6.X), lldb works fine under 7.0.4

link to additional info https://forums.virtualbox.org/viewtopic.php?f=8&t=108016
"	Shaeto
15394	GetLogicalProcessorInformationEx() broken under Windows 7	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
21105	Getting a Guru Meditation - Critical error during CentOS user settings configuration	VirtualBox 6.1.38	2022-09-10T20:33:56Z	2022-09-10T23:49:24Z	2022-09-10T23:49:24Z		ktapodac
14068	Getting an error code when I try to start virtual machines.	VirtualBox 4.3.26	2015-04-21T22:50:28Z	2015-04-22T06:16:05Z	2015-04-22T06:16:05Z	"Failed to load VMMR0.r0 (VERR_SUPLIB_WORLD_WRITABLE)

Result Code: 
NS_ERROR_FAILURE (0x80004005)
Component: 
Console
Interface: 
IConsole {db7ab4ca-2a3f-4183-9243-c1208da92392}

Is there anything that can be done or anything additional I need to install for this? I'm using Linux Mint."	Heidi Hecht
19175	Getting blank screen while running virtual box session in windows 10 pro	VirtualBox 6.1.0	2019-12-20T04:08:42Z	2019-12-20T04:08:42Z	2019-12-20T04:08:42Z	"My VM session is getting stuck at blank screen during startup in windows 10. I can able to run it windows 7 with out any issues but not in windows 10.  

Can someone help me on this.

"	amars404
19447	Getting error when trying to install the virtualbox extension pack	VirtualBox 6.0.18	2020-03-30T05:33:30Z	2020-03-30T05:33:30Z	2020-03-30T05:33:30Z	"I just tried upgrading virtualbox to the latest version that I guess you all just released.  First odd thing I noticed was that virtualbox did not prompt me to automatically download the correct version of the extension pack from the web site.  So, I manually downloaded it and tried to install it, only to get the attached error.  The text of the error is below:

Failed to install the Extension Pack C:/Users/whiggs/Downloads/Oracle_VM_VirtualBox_Extension_Pack-6.1.4 (1).vbox-extpack.

Failed to load the main module ('C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\win.amd64\VBoxPuelMain.DLL'): VERR_SYMBOL_NOT_FOUND - GetLastError=127.

Result Code: E_FAIL (0x80004005)
Component: ExtPackManagerWrap
Interface: IExtPackManager {70401eef-c8e9-466b-9660-45cb3e9979e4}

"	coolbeans
17001	Getting memory Access Violations 5.1.26	VirtualBox 5.1.26	2017-08-11T13:23:44Z	2017-08-15T18:04:07Z	2017-08-15T18:04:07Z	"Randomly getting Memory Access Violations.  Often at some point during startup, but not always.

I looked in the VBox.log file, but nothing jumped out at me.

Are there other ways to debug this?

The VBox.log is attached."	jhellmers
21060	Getting memory reference error after upgraded to Virtualbox 6.1	VirtualBox 6.1.36	2022-08-12T14:01:52Z	2022-08-22T21:48:09Z	2022-08-22T21:48:09Z	I am getting the memory reference error after upgrading to Virtualbox 6.1. Can you please help solving the issue?	Natarajan Arumugam
19981	GNOME issue, Suspected but unsure	VirtualBox 6.1.14	2020-10-20T15:08:11Z	2020-10-20T15:08:11Z	2020-10-20T15:08:11Z	the vm will start but not get past the command line.	eryktyler26
9234	GNU/kFreeBSD support: gnukfreebsd checks in the build system	VirtualBox 4.0.12	2011-07-18T20:38:14Z	2011-11-26T11:26:00Z	2011-11-26T11:26:00Z	"This patch adds GNU/kFreeBSD detection to the build system. It makes the appropiate checks match it with its ""gnukfreebsd"" string identifier.

This patch is copyright 2011 Robert Millan and I hereby license it under the MIT license (http://www.virtualbox.org/wiki/MIT%20license).
"	Robert Millan
6692	go to fullscreen mode when maximizing the guess window	VirtualBox 3.1.8	2010-05-14T10:56:09Z	2010-05-30T11:38:48Z	2010-05-30T11:38:48Z	when maximizing the window of the guess go directly to fullscreen mode (or at least have this configurable)	anonymous
16526	Google Chrome Stable Crashes Linux Guest	VirtualBox 5.1.14	2017-03-02T16:29:09Z	2017-03-02T16:40:47Z	2017-03-02T16:40:47Z	"I am not sure about the complete steps, but I can reproduce this each, and every time.  I launch Google Chrome (Version 56.0.2924.87 (64-bit)) under Ubuntu GNOME 16.04.2 Guest.  I visit a Cisco Acano URL to join a meeting (such as https://join.<some domain>.com/invited.sf?secret=QtsgKqo7mTqO2O4pOM0ouB&id=77223344).  When I join the meeting, VirtualBox crashes with an error message, such as:

    The instruction at 0xdc7aa4f2 referenced memory at 0x00000028.  The memory could not be read.  Click on OK to terminate the program.

Host:  Windows 7 Professional SP-1
       16GB RAM
       AMD Radeon R7 M360/Intel HD Graphics 520
       Dual Core i7
       Three monitors (laptop + two external)
Guest: Ubuntu GNOME 16.04.2
       8GB RAM
       128MB VRAM
       2 CPU
       2 Monitors
"	JayBofMA
17973	Graphical Glitch on Virtualbox Window Maximization	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
18564	Graphics performance is absolutely dismal, to the point of unusability	VirtualBox 6.0.6	2019-04-16T22:41:16Z	2022-07-27T15:13:06Z	2022-07-27T15:13:06Z	"I use Fedora 29 with the Cinnamon desktop (runs in X, requires 3D acceleration).  I have been having pretty dismal graphics performance, to the point where I have to stop typing and let the application catch up with me so that I can spot stuck keys and dropped keystrokes.  It appears numerous X events get dropped in some fashion; often, my shift key gets stuck, as if the key_release event was missed, but that's not the only key that'll get stuck.  I have the same issue with mouse clicks, too, which makes it a bit difficult to cut and paste text or select options in menus.  For the record, this is a freshly created VM utilizing the VMSVGA driver, scaled by 175%, with 3D acceleration activated; resolution is 1920x1200.  When I upgraded from a 6.0.5 pre-release and updated the guest tools, Cinnamon started complaining about using software rendering, although I can see the vmwgfx and vboxvideo drivers loaded.  If I run glxinfo, I see ""OpenGL renderer string: llvmpipe (LLVM 7.0, 256 bits)"" in the output.  I've also started to node, with the 6.0.6 release, that the Menu is getting randomly activated, as if I hit the Windows key.

(Host is osX.)"	Kevin L Mitchell
18895	Gray out, don't rearrange, disabled buttons	VirtualBox 6.0.10	2019-09-02T18:24:42Z	2019-09-02T22:31:32Z	2019-09-02T22:31:32Z	"When the user selects a VM in the VirtualBox GUI, and then selects Tools, and then selects the VM again, the control buttons rearrange in a way that is jarring and makes it all too easy to click on the wrong button.

Don't keep changing the button layout on focus. Instead, gray out any disabled buttons."	mcandre
17603	"Group of device files changes after running VirtuaBox with ""raw partitions image"""	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
17473	GRUB countdown problem	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
7952	gues key mapping problem while host is using XkbOptions	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
19316	Guest additions cannot be installed in Windows Vista	VirtualBox 6.1.2	2020-02-16T11:14:31Z	2022-10-21T13:54:06Z	2022-10-21T13:54:06Z	"VirtualBox 6.1.2 guest additions cannot be installed in a fully updated Windows Vista SP2 x86.

ERROR 800b0010: no signature was present in the subject.

See the attached screenshot."	Artem S. Tashkinov
15994	Guest additions detect GB as KB and claims about too less free space	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
17080	guest additions do not build with 4.14 kernel -> fixed in builds after 1. November 2017, 5.2 and later	VirtualBox 5.1.26	2017-09-14T19:13:55Z	2017-10-31T16:46:43Z	2017-10-31T16:46:43Z	"Got an error message while attempting to install guest additions in a Fedora Rawhide guest for the 4.14.0-0.rc0.git5.1.fc28.x86_64 kernel.
{{{
vboxadd.sh: failed: Look at /var/log/vboxadd-install.log to find out what went wrong.
}}}"	Andre Robatino
18953	guest additions fail to install	VirtualBox 6.0.12	2019-09-22T10:04:43Z	2020-03-31T11:59:06Z	2020-03-31T11:59:06Z	"fails to install see log

https://pastebin.com/sw74ba1C"	DeGarden
18881	Guest additions installation fails with: The network operation failed with the following error:  During network request: Unknown reason.	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
19253	Guest Additions not installing on Win 10 Pro 1903	VirtualBox 6.1.2	2020-01-22T08:07:08Z	2020-01-22T08:07:08Z	2020-01-22T08:07:08Z	"Installing Extension package opens, but never finishes.
I'm trying to update VBox extensions for VBox 6.1.2 r135662 (QT 5.6.2)"	Dizz
11980	guest additions should write system time to RTC after adjusting it	VirtualBox 4.2.16	2013-07-22T13:13:14Z	2016-03-11T12:45:48Z	2016-03-11T12:45:48Z	"When booting a Linux distribution using systemd, the system time is not automatically written to the RTC during shutdown. For further information & rationale, see <http://lists.freedesktop.org/archives/systemd-devel/2011-May/002526.html>.

As a result, booting my system under VirtualBox results in the following:

{{{
Jul 22 03:46:06 wintermute kernel: rtc_cmos rtc_cmos: setting system clock to 2013-07-22 02:46:03 UTC (1374461163)
...
Jul 22 03:46:07 wintermute systemd-fsck[443]: /dev/sdb1: Superblock last write time is in the future.
Jul 22 03:46:07 wintermute systemd-fsck[443]: (by less than a day, probably due to the hardware clock being incorrectly set).  FIXED.
Jul 22 03:46:07 wintermute systemd-fsck[443]: /dev/sdb1: clean, 340335/39321600 files, 138917904/157286139 blocks
...
Jul 22 03:46:08 wintermute systemd[1]: Started LSB: VirtualBox Linux Additions.
Jul 22 13:57:43 wintermute systemd[1]: Time has been changed
}}}

After boot, we can observe the RTC is still wrong:

{{{
$ date
Mon 22 Jul 14:10:15 BST 2013

# hwclock -r
Mon 22 Jul 2013 03:58:44 BST  -0.070616 seconds
}}}

After the guest editions have set the system clock from the host clock, they should set the hardware clock to match. That is, perform the equivalent of `hwclock --systohc`."	Sam Morris
20150	Guest additions VNC screen resize detection code fails	VirtualBox 6.1.18	2021-01-23T18:38:36Z	2021-01-23T18:38:36Z	2021-01-23T18:38:36Z	"When accessing a client using VNC the code fails to detect a screen resize, meaning that clients can not be run 'headless', as the host has to be used to manually detect the resized screen.

This fault was introduced in 6.1.8, forcing me to continue to use 6.1.6 with the new versions of the other software, i.e. Virtualbox & Extension Pack.

p.s. A Debian client actually reports the error to the user."	Sysop
14657	guest audio choppy, video lags and windows screen flickers	VirtualBox 5.0.6	2015-10-02T21:10:36Z	2015-10-06T03:52:48Z	2015-10-06T03:52:48Z	"Host: Win7 64bit, intel i7-930 processor, VirtualBox-5.0.6-103037-Win
Guest: Win8.1 64Bit with VirtualBox_Extension_Pack-5.0.6-103037

Would also like to refer to:

issue #14633, that describes also the audio problem, but may have a different cause.

issue #4088, latency fixes (Windows hosts only; bug ), fixed in the release



To reproduce this: enable 2d/3d video acceleration for the guest, using an usb mouse

Steps to reproduce:[[BR]]

-start the guest[[BR]]-logon, during logon process the screen flickers[[BR]]
-lauch IE, again sometimes the screen flickers during startup of IE[[BR]]
-goto to youtube and start a music video.[[BR]]


-if you don't use the mouse, the sound and video are almost perfect

-hover the mouse above the playing video area[[BR]]
-rapidly move the mouse from left to right/up/down within the video rectangle
a) the sound will become ""choppy"",
b) the video seems also to lag a little


In the previous version (5.0.4) audio was constantly choppy (even without moving the mouse),
as if you put the volume control to high, like to much voltage on a speaker.[[BR]]

In the previous version (5.0.4) the video was constantly lagging, showing blocks, seems to stop some milleseconds 

After installing 5.0.6, the sound and video performs better but it's not solved.

If I disable 2d/3d video acceleration, audio is back to normal, no video lags and no screen flikkering. (don't see a benefit for enabling video acceleration)

Enabling video acceleration and using the usb mouse together seems to cause the problem.

May be both have an issue.

Attached logs and the description might lead to a solution?
"	L.
20120	Guest container crashes	VirtualBox 6.1.16	2021-01-09T15:00:36Z	2021-01-09T15:00:36Z	2021-01-09T15:00:36Z	"The guest container has a hard crash on Windows Server 2016.

More details/logs can be found at:
https://forums.virtualbox.org/viewtopic.php?f=4&t=101209"	User2358
19451	Guest crash after some hours working	VirtualBox 6.1.4	2020-03-31T08:28:07Z	2020-05-26T08:19:05Z	2020-05-26T08:19:05Z	On 6.x versions of VBox crashes are stable :-(	Дмитро
17287	Guest crashed when connecting to remote system using Remote Desktop	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
19914	guest display reacts very slowly	VirtualBox 6.1.14	2020-09-24T21:01:35Z	2020-09-24T21:01:35Z	2020-09-24T21:01:35Z	Hello I want to run Debian Buster as guest on Mac OS X as host. Installation worked, but the guest display reacts very slowly and randers it unusable. When doing a SSH to the guest, I see that CPU usage is almost zero. Why is the display part broken?	kouros
12989	guest display size indicator	VirtualBox 4.3.10	2014-04-25T15:54:41Z	2014-04-25T15:54:41Z	2014-04-25T15:54:41Z	"I would like to have an idea of what the guest '''display''' size is as I'm dynamically adjusting the guest '''window''' size.  The size indicator could be anywhere on the guest window, because it would only show up when the guest window is being resized.

Also, it would be nice to have the ability to make the guest display size snap to the video capture frame size.  This could be a box that can be checked/unchecked.

Thank you!"	stoli
17892	Guest freeze when virtualizing 9 or more CPU	VirtualBox 5.2.16	2018-07-25T02:13:37Z	2018-07-25T02:13:37Z	2018-07-25T02:13:37Z	Attempt to virtualize 9 or more CPUs results guest freeze. Different guest OS'es affected.	Dian
16396	Guest Freeze: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [firefox:3744]	VirtualBox 5.1.12	2017-01-17T08:42:54Z	2018-06-22T15:31:03Z	2018-06-22T15:31:03Z	"I searched a lot for a similar problem and could not find one.
The problem occurs with both 5.1.12 or 5.0.30 and also earlier versions for a few months now.
I tried ubuntu 16.04 64bit VM and also Debian machine 32 bit with jessie and now stretch.
I recompiled the kernel, 4.8.15 same thing.
I am using docker to run the firefox so that is an important information.
The freeze occurs after a while using the firefox. I don't have an idea why it happens or in what situation. Sometimes it can run for a long time, sometimes not. It is sporadic."	Tzahi
20390	Guest hung after host resumes from sleep	VirtualBox 6.1.22	2021-06-07T23:17:24Z	2021-09-08T00:32:39Z	2021-09-08T00:32:39Z	"VirtualBox 6.1.22 r144080
Host:  Windows 10 (2004 - 19041.1023)
Guest: Ubuntu 21.10

When I suspend and resume the host, the guest is no longer responsive, requires a forced power off and complete restart of the guest.  Similar to 20270, but the trick of pausing and resuming doesn't work.

Used to work fine, I suspect it started with a host OS update.  Happened under 6.1.17 too.

Logs attached."	gkcgareth
16552	Guest is super sloooow	VirtualBox 5.1.16	2017-03-11T08:51:29Z	2017-03-11T19:44:52Z	2017-03-11T19:44:52Z	"Don't know why Win XP and 7 (64bit) are both super slow!

macOS Sierra 10.12.2"	Mungo
7874	Guest keyboard starts sending multiple characters for a single keypress after Windows host hibernation	VirtualBox 3.2.12	2010-12-22T15:37:04Z	2015-11-03T14:46:21Z	2015-11-03T14:46:21Z	"After bringing the host up from hibernation, the guest system's keyboard begins to respond erroneously. For example a key press for a single key gets repeated 10 times randomly, preventing the user from typing anything in the guest. A guest restart is needed to get back to normal.

One way to replicate (not 100% of occurrences though) is to hibernate the host system and bring it back up.

(Windows7 64-bit host & CentOS 5.2 guest with latest Guest Additions installed)"	Miro
19876	guest language change changes host	VirtualBox 6.1.14	2020-09-10T00:24:37Z	2020-09-10T00:24:37Z	2020-09-10T00:24:37Z	i am learning german, and though useing a computer in german would help, but when i setup a windows 10 guest on a windows 10 host, and install a new language, it also installs on the host, and changed my time, and language, on top of adding it to the host. when i delete the forein language from the host, it dissapears on the guest as well	devsch
18126	Guest linux fails to receive key input after X11 screen appears on resume from saved state.	VirtualBox 5.2.22	2018-11-13T04:46:02Z	2018-11-13T18:21:23Z	2018-11-13T18:21:23Z	"Hi,

I experienced an apparent hung of guest linux inside virtualbox 
5.2.20 r125813 
running under Windows 10.
After a saved state is resumed, the X11 screen is displayed and
there are teminal windows shown on it.
But when I try to type something to  a consle window nothing gets echoed back. Come to think of it, USB mouse does not respond at all.
I have to kill it (power down the guest OS).

Gesut linux version is Debian GNU/Linux kernel version: 
uname -a
Linux ip030 4.16.0-2-amd64 #1 SMP Debian 4.16.16-2 (2018-06-22) x86_64 GNU/Linux

I have this apparent hung problem three times since I move the image from a XEON-based PC to AMD Ryzen 1700 PC about 10 days ago.

Is it possible that AMD Ryzen and guest linux may have some timing-related issue (like say, timer or counter not handled properly using hardware counter?)

I am asking because I also have a very starnage network adaptor hung (e1000 network card driver got hung). I have not seen this bug often during 5 or 6 years of using the image on a XEON-based PC.

While looking at dmesg output, I noticed that kernel says TSC is unstable or whatever: I am not sure what the message under XEON PC was.

{{{

 dmesg | grep -5 -i bogo 
[    0.004000] hpet clockevent registered
[    0.004000] APIC: Switch to symmetric I/O mode setup
[    0.004000] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[    0.004005] tsc: Detected 2994.376 MHz processor
[    0.004007] tsc: Marking TSC unstable due to TSCs unsynchronized
[    0.004008] Calibrating delay loop (skipped) preset value.. 5988.75 BogoMIPS (lpj=11977504)
[    0.004010] pid_max: default: 32768 minimum: 301
[    0.004046] Security Framework initialized
[    0.004047] Yama: disabled by default; enable with sysctl kernel.yama.*
[    0.004060] AppArmor: AppArmor initialized
[    0.016000] Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes)
--
[    0.024084]  #6
[    0.004000] kvm-clock: cpu 6, msr 3:23fea181, secondary cpu clock
[    0.004000] mce: CPU supports 0 MCE banks
[    0.024443] smp: Brought up 1 node, 7 CPUs
[    0.024443] smpboot: Max logical packages: 1
[    0.024443] smpboot: Total of 7 processors activated (41921.26 BogoMIPS)
[    0.025189] devtmpfs: initialized
[    0.025189] x86/mm: Memory block size: 128MB
[    0.025209] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.025209] futex hash table entries: 2048 (order: 5, 131072 bytes)
[    0.025209] pinctrl core: initialized pinctrl subsystem

}}}



Anyway,  I am attaching Vbox.log when the guest does not receive any input and I had to kill (power down the image). Maybe there might be a clue in there.




"	ci-zephyurus
19399	Guest Locks Up Then Crashes	VirtualBox 6.1.4	2020-03-14T00:04:08Z	2020-03-14T00:04:08Z	2020-03-14T00:04:08Z	"Fresh install of windows 10 x64. All updates installed.

Using Virtualbox 6.1.4 on macos 10.15.3

Installed java 8u241, oracle version.

After opening java control panel, VM locks up. After a bit it crashes. OS reports it as EXC_BAD_ACCESS"	rj45
16608	Guest LPT error stops VM to start since VM versions 5.1.4 ... 5.1.18	VirtualBox 5.1.18	2017-03-25T13:34:44Z	2017-03-25T13:34:44Z	2017-03-25T13:34:44Z	Host Win7Pro 64bit, guest Win XP Pro, on-motherboard LPT. Worked fine until v5.1.2. Starting from v5.1.4 ... v5.1.18 all versions crash during starting guest. LPT initialization error. If downgrading to v5.1.2 (with corresponding extensions)- works fine again.	Lager-Ju
16793	Guest machine freeze when network is active	VirtualBox 5.1.22	2017-05-27T16:37:58Z	2017-05-29T19:26:12Z	2017-05-29T19:26:12Z	"I have a version of VirtualBox 4.3.38 installed on my Debian, runs, and I keep this version !
Why ?
I installed a version 5.3.1 on a Windows Seven machine, version strongly discouraged!
I will join the logs because the guest machine freeze!
Especially when I add the network card from menu Configuration-> NAT network or bridge,
then systematically blocks the FREEZE guest machine!
I keep version 4.3.38.
I join the log!
I have AVG and spyHunter installed on the Windows machine.
I TRY DISABLED SERVICE SPYHUNTER AND AVG THEN FREEZE ALWAYS

J'ai une version de VirtualBox 4.3.38 installé sur ma Debian , fonctionne , et je garde cette version
pourquoi ?
J'ai installé sur une machine Windows Seven la version 5.3.1 , version vivement déconseiller !
Je vous joint les logs car la machine guest freeze !
Surtout quand je rajoute la carte réseau depuis menu Configuration->Reseau NAT ou pont à pount, 
ca freeze  systématiquement , la machine guest FREEZE !
Je garde la version 4.3.38.
Je joint les log !
Product not tested."	Sizy458
18356	Guest machines randomly freezing on Windows	VirtualBox 6.0.2	2019-01-23T20:17:13Z	2021-03-04T18:04:52Z	2021-03-04T18:04:52Z	"Guest machines are just freezing after an random number of minutes. Initially the missing guest heartbeat is just returning an error and resetting the machine. I changed the HeartbeatInterval in order to get the actual cause of this and the message before freezing is:

00:47:36.160501 AHCI#0: Port 0 reset
00:47:36.161610 VD#0: Cancelling all active requests
00:47:36.165047 AHCI#0: Port 0 reset
00:47:36.166097 VD#0: Cancelling all active requests
00:47:36.171464 AHCI#0: Port 0 reset
00:47:36.172509 VD#0: Cancelling all active requests
00:47:36.178255 AHCI#0: Port 0 reset

Same behavior on some version 5, on version 6.0.2 (latest at the time of bug recording) and 6.0.3 r128259. Logs captured from version 6.0.3."	serbanforyou
13108	Guest mouse cursor range limited without guest additions installed	VirtualBox 4.3.12	2014-06-08T21:50:38Z	2018-12-11T13:28:24Z	2018-12-11T13:28:24Z	"When using a guest OS without VirtualBox Guest Additions installed, the guest mouse cursor can only be moved within a part of the guest desktop.  Before the guest mouse cursor reaches the edge of the desktop, the cursor suddenly jumps outside the guest window and appears on the host OS desktop.

The problem happens in version 4.3.12 and 4.2.24 as well as previous versions.  The specific host OS is Windows 7 Professional SP1 and the guest OS is Windows XP SP3 (without guest additions).   The same problem happens for other guest operating systems without guest additions installed.

The display resolution on the host OS is higher than that of the guest OS.  The host OS resolution is 1680 x 1050.  The guest OS resolution is 1024 x 768.

It appears that the mouse becomes un-captured when the (invisible) host cursor position moves outside the guest window.  The cursor in the guest moves slower than in the host, so the guest cursor has not reached the edge of the guest desktop.  Either the mouse should remain captured, or the mouse position in the host should be converted to the correct guest position based on the different screen resolutions.

The problem also happens in full screen mode.  The guest display uses only a portion of the host screen, and the guest mouse cursor stops moving when the (invisible) host cursor moves outside the guest portion of the screen.  The host mouse cursor reappears before the guest cursor has moved to the edge of the guest desktop.

This problem makes VirtualBox very difficult to use with boot CDs or operating systems not supported by guest additions.  In some very old versions of VirtualBox (3.x) this problem did not occur.  I frequently use VirtualBox to test boot CDs that I have created for backup, partitioning and encryption software."	ErikW
16904	guest OS screen and host OS screen	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
20588	Guest OS startup crashes the VM	VirtualBox 6.1.26	2021-10-01T17:44:38Z	2021-10-01T17:44:38Z	2021-10-01T17:44:38Z	"When I trying to start VM with RHEL7 it no longer can startup.
It crashing into ""Guru mediation"".
"	xor2003
16452	Guest OS time is not in sync with host OS time after host is awake from sleep mode	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
20134	Guest OS will not boot	VirtualBox 6.1.16	2021-01-18T18:45:00Z	2021-01-18T18:45:00Z	2021-01-18T18:45:00Z	"Whenever I try to boot ''any'' guest OS, it will freeze and enter guru meditation. This happens on MBR and UEFI based guest OS.
"	Pupilliam
13605	Guest OS Window Disappears after Sleep in MacOS X Yosemite	VirtualBox 4.3.18	2014-11-11T15:23:17Z	2014-11-24T17:57:19Z	2014-11-24T17:57:19Z	"The guest OS Window Disappears on Sleep in MacOS X Yosemite.  The sleeping behavior of the new Yosemite release may be causing this problem.

Steps to reproduce:

1) Open a Windows 7 guest OS.
2) Put the window on a second monitor.
3) Close the Macbook lid to cause the MacOS to sleep.
4) Open the Macbook lid.
5) For a moment you will see no windows from any application, then most of them will pop back up.
6) VirtualBox Guest OS Window never reappears.
7) Clicking ""Show"" button in VirtualBox Manager does nothing.

Workaround: Use Remote Desktop to shutdown the OS and restart.

Please note that the length of time in sleep should be a long time.  Merely closing and opening the MacBook lid for a few seconds will probably not trigger this behavior.

Guest OS is Windows 7 with all patches applied to the date of this writing.

Thank you.


"	Kriston
13059	Guest Processor Affinity	VirtualBox 4.3.12	2014-05-22T23:34:22Z	2014-05-22T23:34:22Z	2014-05-22T23:34:22Z	"Requesting a feature that specifies a guest should run with processor affinity. This can be even better if there is a way to specify if specific processes inside the guest need to run with processor affinity.

I have some single threaded long running process that perform well in the native machine as they are not thrown around different CPUs unlike the processes in the guest machine."	Senthil Nathan
18163	Guest property LoggedInUsers does not work with 'wait' in VBoxManage	VirtualBox 5.2.22	2018-12-02T13:54:57Z	2018-12-02T17:47:06Z	2018-12-02T17:47:06Z	"To wait for a machine to be ready for logins I used

    vboxmanage guestproperty wait <machine> /VirtualBox/GuestProperty/OS/LoggedInUsers

At some point (before 5.2.22) that stopped working. You can still 'get' that property, and it is listed with 'enumerate' for a running <machine>."	thoni56
18859	"Guest randomly crashes with ""The memory could not be read"""	VirtualBox 6.0.10	2019-08-21T13:07:19Z	2019-08-21T19:15:03Z	2019-08-21T19:15:03Z	"I am running a Windows 10 1903 host and a Ubuntu 19.04 guest. The Ubuntu guest crashes fairly often with the attached dialog (see attached PNG file), warning of ""The memory could not be read.""

Both host and guest are using the latest patches. The guest has the current VMWare Extensions installed. The guest has 3D acceleration enabled.

Almost all of this guest OS's usage is for using Chromium browser to browse everyday sites, like Gmail, Facebook, CNN, etc. I feel it's fairly vanilla other than installing a few commodity apps like Chromium, GIMP, and Visual Studio Code.

The crash can happen when I am using nothing other than Chromium. In fact, just today, the crash happened less than 15 minutes after starting the VM. I attached log files from that crash.

Sometimes right-click context menus in Chromium go black. That is, you right-click on something, and the context menu that pops up is just a black rectangle. You can still click on things in that menu, but . I ''loosely'' correlate this to ""the VM is going to crash sooner than later"", but I am not sure there is a correlation. This morning, I did not notice the black context menus, although I do not think I invoked one."	Aren Cambre
21180	Guest resolution without VirtualBox drivers cannot be changed from default 1024x768	VirtualBox-7.0.2	2022-10-21T12:27:14Z	2022-10-23T13:02:30Z	2022-10-23T13:02:30Z	"For a Windows 11 guest, video/monitor/display resolution without VirtualBox guest drivers cannot be changed from default 1024x768.

This used to work for non-EFI earlier Windows releases.

My guest is Windows 11 22H2."	Artem S. Tashkinov
18562	guest screen flickering by 3d acceleration on	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
18520	Guest seems to be unresponsive	VirtualBox 6.0.4	2019-03-25T10:16:37Z	2019-03-26T19:16:09Z	2019-03-26T19:16:09Z	My system freezes after running for a few moments. I start and application and it freezes. The log details that the Guest is unresponsive. This is a regular occurrence for me. I've checked previous tickets and comments on the forum and made changes accordingly but I'm still having the problem. If someone could point out what the issue may be I could fix it myself and should it occur again on another machine I would know how to resolve the problem. Any help would be greatly appreciated. I don't want to have to delete the machine again.	GavEB
21337	Guest start aborted every time when bridged network interface name changes	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
16291	Guest SuSe 13.2 freezes on Host Windows 7 when more than 1 processor (core2 quad) is assigned	VirtualBox 5.1.10	2016-12-15T09:51:04Z	2017-01-06T10:27:29Z	2017-01-06T10:27:29Z	"This issue is similar to that in [https://www.virtualbox.org/ticket/7619 ticket 7619]. However, the issue occurs with a recent VirtualBox version.

When more than 1 processor is assigned to the Guest (Open SuSe 13.2, XFCE Desktop) it freezes after some time and does not react anymore (commonly after below 1 hour). VirtualBox itself still runs. Pausing the VM or Saving it to the Disk (and resuming) works fine but the Guest is still frozen. The Host is Windows 7 SP1.

When I assign 1 processor it works fine (I worked for 2 month with this 1-processor-setup and experienced some performance problems recently, which is way I came back testing a >1 processor setup. But this is not the topic of this ticket).

3D acceleration is not enabled. The issue seems to be correlating with the usage of Mozilla Firefox and/or Thunderbird - but not exclusively. The freezes occured also without Firefox running (but less ofter). 

The host computer has a Core2 Quad Q9400 Processor. It does not support hyper-threading. I could assign up 8 cores in the settings dialog. I mention this because I found some discussion on whether cores or virtual processes are assigned. Idependent whether the processor supports hyper-threading or not, there should be only 4 cores available.

Currently, I am using VirtualBox v5.1.10 but the issue occured also in v5.1.6 and v5.1.8.

Since the number of Core2 processors is declining this issue probably has a quite low priority."	neumannd
18041	guest suse leap 15.0 could not be started after kernel update openSUSE-2018-1140	VirtualBox 5.2.18	2018-10-10T09:09:19Z	2018-10-17T08:11:08Z	2018-10-17T08:11:08Z	"With VirtualBox 5.2.18r on a Windows 10 host my Open Suse Leap Linux updated
the kernel with openSUSE-2018-1140 and from then on the suse guest couldn't be
started again.
Attached you'll find a hardcopy of the Startup sequence Messages.

An native Installation of Suse, including the kernel 4.12.14.lp150.12.19, 
works w/o any issues."	guenni
17791	Guest VM becomes unresponsive after 2 or 3 days continuous uptime	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
14063	"Guest VM hangs if ""Exit full screen"" is clicked while saving state"	VirtualBox 4.3.26	2015-04-21T10:54:31Z	2015-04-21T12:17:21Z	2015-04-21T12:17:21Z	"Steps to reproduce:  

* Have a running Windows guest (I couldn't reproduce it with Linux)  
* Press Close -> choose to save state  
* While saving state mini-window is up, press ""Exit full screen""

Result is that guest VM is stuck in ""Saving"" state indefinitely and with unresponsive GUI, the only way I could abort it is kill -9, after which it goes to ""Aborted"" state. I can alt-tab out of VM to my host WM (openbox on ArchLinux)."	Alex110101
18840	Guest VM with Windows 10 64 bit Pro 1903 is resetting with no reason	VirtualBox 6.0.10	2019-08-16T01:00:00Z	2019-08-17T08:29:31Z	2019-08-17T08:29:31Z		fduenas
18493	Guest W7-32Bit hanging with 6.4.0	VirtualBox 6.0.4	2019-03-14T10:16:54Z	2019-03-15T14:45:17Z	2019-03-15T14:45:17Z	"After upgrading to 6.0.4, my long used Windows 7 32Bit guest hangs after a few minutes or sometimes hours. It seems to work allright at first.

No specific action has been identified which leads to it hanging. It happend while browsing the internet, using the file-explorer and even during logout or shutdown.

The VM has to be killed - no other ways to shut it down. It happend 4 times now, definitively too often for my understanding - and it never happened with 5.2.

I have already upgraded the Guest-Additions, to no avail.

Other guests (e.g. W10 64Bit) work fine on the same host - even more stable in terms of audio I dare say.

I do use dual-screen, which is a very useful feature - one reason for having upgraded from the very stable former versions.
"	ufotech
19030	guest window position not restored	VirtualBox 6.0.14	2019-10-19T09:58:55Z	2020-10-25T12:01:33Z	2020-10-25T12:01:33Z	"The guest window positions (guest with more than one monitor) are not restored.
In 5.0.40 it works well. In 5.1.Y it started not to work.

See also here: https://forums.virtualbox.org/viewtopic.php?f=6&t=95117"	artelogic
16332	Guest Windows 10 displays black desktop on second screen	VirtualBox 5.1.12	2016-12-28T07:27:35Z	2016-12-28T07:27:35Z	2016-12-28T07:27:35Z	"My Virtualbox is installed in laptop, OS is windows 10, I also install a guest windows 10 to do some other tasks. I have a second screen connected to laptop and the guest windows 10 is displayed on second screen. 

If I don't shutdown/save the guest windows 10 then unplug in the second screen and then plugin second screen again:

1. The guest windows 10 will display a black desktop after I run mstsc on guest windows(even I closed mstsc). If I press Windows key on keyboard, Start menu and taskbar can be displayed on guest, but the desktop is still black. After the Start Menu and taskbar is hidden, all desktop is black again. To show the desktop, I write a bat file to restart explorer.exe, press Windows key + R to run the bat file, then the desktop can be displayed.

2. The virtualbox min bar will be displayed on first screen of laptop

My VirtualBox version is 5.1.12r112440(Qt5.6.2)
Host and Guest are latest Windows 10
Extention is installed on host, guest additional is install on guest and 3D support is open"	Peak Zhang
15143	Guest Windows 8.1 64 bits freeze every 2-15 minutes for several seconds/minutes	VirtualBox 5.0.14	2016-02-11T12:07:10Z	2016-03-04T13:15:27Z	2016-03-04T13:15:27Z	"Hi VirtualBox team,

I use Virtual Box 5.0.4 on host Windows 8.1 64 bits and my guest (Windows 8.1 64) freezes every 5 to 30 minutes for several seconds or minutes.
Windows performances are OK according to Windows Task Manager.
Host works perfectly with high availability.

While the guest is frozen, all mouse/keybord inputs are buffered.
When guest become available, all these buffered user actions are executed very quickly.

So this VM is not really useable right now.

I attach my VMlogs to this ticket.
Any help would be really appreciated! :)
Thanks for your support.

Regards,
François M"	François M
18560	Guest Windows hangs on startup with guest additions installed	VirtualBox 6.0.4	2019-04-15T08:17:20Z	2019-04-15T08:26:48Z	2019-04-15T08:26:48Z	"Host: Windows 10 1803 prof
Guest: Windows 7 x86 prof

Today I found that my old VM hangs on startup: black screen with ""Starting Windows"" message.
It doesn't connect to debugger (the debugging was turned on in the guest etc; in previous version of VirtualBox it worked).
I reinstalled Windows fresh in the guest.
It worked normally for a while.
I installed Guest Additions, rebooted and it hung.
Log file contains nothing interesting. The last message is:
00:05:11.555304 GUI: UIFrameBufferPrivate::performResize: Size=1024x768, Directly using source bitmap content
"	iakovk
20893	Guest Windows XP 32 bit does not start anymore after network crash	VirtualBox 6.1.32	2022-04-06T13:22:07Z	2022-04-06T13:29:35Z	2022-04-06T13:29:35Z	"Host: Windows 10 64 bit (12 Gb installed RAM, 8 CPU's)
Guest: Windows XP 32 bit (1 Gb allowed RAM, 1 CPU allowed)
Network: Windows Server 2008 R2

Yesterday there was a problem in the server (hung), while that happened I had an old program running locally within the VM. In spite of that, I still closed everything apparently in a normal way.
Today I cannot launch the host, when I try I get the message in the image [[Image()]]
My system is in Spanish but it informs that there was a critical error during the execution of the VM and has been stopped; it supplies the option to continue (Ignore button), I tried it to no avail.
All I get when I try to launch the host is a black screen and, sometimes, the message in the attached image, other times it just stays there and I have to shut it down using the X button.
By the way, I've been using VM for years and this is the very first time that I have a problem I cannot solve easily, in fact I don't remember ever having problems before. Thanks in advance."	Mamá Cora
21210	GuestInfo reverts to old data after VM shutdown	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
15980	Guests won't go in Save States on Host shutdown with Ubuntu 16.04	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
13958	GUI does not indicate corrupt/missing save file in an obvious way	VirtualBox 4.3.24	2015-03-16T14:15:52Z	2015-03-16T14:20:14Z	2015-03-16T14:20:14Z	"I have a windows 8.1 x64 host running 4.3.24 which cannot start a Windows 7 Enterprise x64 guest with saved state after rebooting the host OS. Something appears to have removed or corrupted the save-state file, but the GUI does not indicate this in an obvious way (it does appear in the log, however).

More desirable behavior would be a ""Save file is missing or corrupt. Restart VM?"" dialog. Instead, I get this, which is also symptomatic of a large number of other (more complex) failures:

{{{
Failed to open a session for the virtual machine CDW Win7.
The VM session was closed before any attempt to power it on.
Result Code: E_FAIL (0x80004005)
Component: SessionMachine
Interface: ISession {12f4dcdb-12b2-4ec1-b7cd-ddd9f6c5bf4d}
}}}

The Log:

{{{
VirtualBox VM 4.3.24 r98716 win.amd64 (Mar  2 2015 14:18:45) release log
00:00:03.174146 Log opened 2015-03-16T13:53:05.920532400Z
00:00:03.174149 Build Type: release
00:00:03.174155 OS Product: Windows 8.1
00:00:03.174157 OS Release: 6.3.9600
00:00:03.174158 OS Service Pack: 
00:00:03.258341 DMI Product Name: 20246
00:00:03.262022 DMI Product Version: Lenovo IdeaPad Yoga 11S
00:00:03.262030 Host RAM: 8071MB total, 5351MB available
00:00:03.262033 Executable: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
00:00:03.262034 Process ID: 4556
00:00:03.262035 Package type: WINDOWS_64BITS_GENERIC
00:00:03.262679 ERROR [COM]: aRC=VBOX_E_FILE_ERROR (0x80bb0004) aIID={8ab7c520-2442-4b66-8d74-4ff1e195d2b6} aComponent={Console} aText={VM cannot start because the saved state file 'C:\Users\P\VirtualBox VMs\CDW Win7\Snapshots\2015-03-14T16-48-25-963707000Z.sav' is invalid (VERR_FILE_NOT_FOUND). Delete the saved state prior to starting the VM}, preserve=false
00:00:03.263825 UIMediumEnumerator: Medium-enumeration finished!
00:00:03.264472 UIMachineView::storeGuestSizeHint: Storing guest size-hint for screen 0 as 640x480
00:00:03.268691 UIMachineView::storeGuestSizeHint: Storing guest size-hint for screen 1 as 640x480
}}}
"	kc0tfb
15957	"GUI of guest Fedora 24 4.7.3-200.fc24.x86_64 freeze ""blank"" on login screen"	VirtualBox 5.1.6	2016-09-19T20:22:45Z	2016-09-21T22:39:03Z	2016-09-21T22:39:03Z	"I'm using VirtualBox version 5.1.6 r110634 on Windows with Fedora 24 4.7.3-200.fc24.x86_64 as guest, both updated to the last patch.

I have the last version of the Guest Additions installed.

And I operate the Guest full screen.

The guest GUI freeze on the login, leaving a blank screen, only the background color is visible, forbidding any action with the mouse or keyboard, apparently.

To refresh the GUI after a mouse or keyboard typing I have to click on the toolbar of the host, to restore the Windows screen.

When I switch back to the guest, the guest screen is updated.

After the login screen all comes back to normality.

"	par7133_2
17735	Guru crash with Redox 0.3.5	VirtualBox 5.2.10	2018-05-05T02:03:50Z	2018-10-13T14:26:18Z	2018-10-13T14:26:18Z	When I try to run Redox 0.3.5 in VirtualBox, I get a Guru crash.	mcandre
19419	Guru Mediation - Cent Os 7, when i start a local ant build	VirtualBox 6.1.4	2020-03-21T10:23:48Z	2020-03-21T10:33:31Z	2020-03-21T10:33:31Z	Guru Meditation is coming very frequently. Please help me to resolve the issue	mariswamy
20973	guru meditation	VirtualBox 6.1.32	2022-06-08T15:15:08Z	2022-06-08T15:15:08Z	2022-06-08T15:15:08Z	"Hello.

With the last update of the VirtualBox, I have a problem with the Virtual Machines.

The host is in Windows 7 - 64 bits.

When the Virtual Machine starts, sometimes show the guru meditation.

I attach the files if somebody can help me.

Thanks for all."	Ino
20068	Guru Meditation	VirtualBox 6.1.16	2020-11-26T06:12:00Z	2020-11-26T06:12:00Z	2020-11-26T06:12:00Z	Guru Meditation Error in windows host and Kali guest	Aqua
17617	guru meditation	VirtualBox 5.2.6	2018-03-12T16:01:22Z	2018-04-24T20:03:27Z	2018-04-24T20:03:27Z	"Hi,

Please am unable to install my new kali-linux-light-2018.1-i386 on windows 7 host which is giving me a guru meditation error.

Attached are details of error report.
Thank you."	swagalimo
10121	Guru Meditation (HostMemoryLow) when low memory	VirtualBox 4.1.8	2012-01-02T17:09:48Z	2015-06-26T14:10:12Z	2015-06-26T14:10:12Z	"I've resumed a virtual machine, but memory low. Expected result is a Paused VM state, but the VirtualBox simple crashed with guru mediation. 
(First occurence was founded in unofficial test build 4.1.7, see comment #9 of ticket #7929
"	wacher
19824	Guru Meditation (tripple fault) while using GNS3	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
17426	Guru Meditation -1668 (VERR_PGM_INVALID_CR3_ADDR)	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
16586	Guru Meditation -2701 (VERR_VMM_RING0_ASSERTION) on Ubuntu 16.04.2 LTS	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
17993	Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT) while debugging in guest 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
17818	Guru Meditation 1155 (VING_EM_TRIPLE_FAULT)	VirtualBox 5.2.12	2018-06-13T16:30:12Z	2018-06-15T18:49:56Z	2018-06-15T18:49:56Z	Getting the above message in the vbox log.  VBox v5.2.12.  Running a Windows 7 32 bit vm in a Windows 10 environment.	NateK
20200	Guru Meditation 1155 with v6.1.18 on Windows 10 host running Windows 98 guest	VirtualBox 6.1.18	2021-02-17T22:55:24Z	2021-02-20T13:47:30Z	2021-02-20T13:47:30Z	"Hi,

I am running the 64bit Version of VirtualBox 6.1.18 r142142 on Windows 10 Pro (20H2) and installed a fresh Windows 98 Second Edition as Guest VM. I use the default Windows 98 configuration and only modified it to set 256MB RAM and 32MB Video RAM.

The first time everything was running fine (no additional programs installed) but since yesterday I get a Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT). This happens sporadically but only during login. Once the system startup is finished everything is fine. Sporadically means that it sometimes works 2-3 times but then the other 5 times I get the Guru.

Regards,
stauberix"	stauberix
15216	Guru Meditation after installing FreeDOS	VirtualBox 5.0.16	2016-03-07T21:40:29Z	2016-03-08T08:27:22Z	2016-03-08T08:27:22Z	"Hi,

I've just installed the latest version of FreeDOS and get a Guru Meditation error when trying to boot that machine.

"	Mastropiero
20151	guru meditation appears when running two VMs	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
16933	"guru meditation at ""Starting Windows"" in Windows 7 guest"	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
21094	Guru Meditation Error	VirtualBox 6.1.38	2022-09-02T18:44:21Z	2022-09-02T18:44:21Z	2022-09-02T18:44:21Z	"I have downloaded the Quickstart Cloudera Vm 5.13.0-0- virtual box with Red Hat for VirtualBox 6.1.38 and when I ""start"" the iteration I get a Guru Meditation critical error. I do not have any chance of interaction. "	fhqwhgads
15989	Guru Meditation error	VirtualBox 5.0.2	2016-09-26T09:34:35Z	2016-09-27T20:14:56Z	2016-09-27T20:14:56Z	"Hi. I have built 2 test VMs using virtualbox. But, when I have one VM opened and trying to start another one, it throws me the attached Guru meditation error.

I'm new to virtualbox, so request you to guide me in this regard & solve the issue.


Thanks!"	RJD
20062	Guru Meditation Fault	VirtualBox 6.1.16	2020-11-24T13:18:39Z	2020-11-24T13:18:39Z	2020-11-24T13:18:39Z	"Received a Guru Meditation fault while running git status from the guest.
The Win 10 host was in the middle of its own startup activity and was quite busy. The Ubuntu 18.04 client had just started and was in the middle of an update when the fault occurred. Please see attachments."	TFR
20250	Guru Meditation on virtualbox	VirtualBox 6.1.18	2021-03-12T15:16:14Z	2021-03-17T18:31:36Z	2021-03-17T18:31:36Z	"On my Windows 10 laptop I have a Guru Meditation when I'm trying to create a windows 2019 vm. 

I've uploaded the logs file and the png image. 

Thanks for your help. "	Nicanor
17154	Guru meditation running OPENSTEP 4.2	VirtualBox 5.2.0 RC 1	2017-10-10T22:21:59Z	2017-10-11T17:36:33Z	2017-10-11T17:36:33Z	I've got a guru meditation when booting my OPENSTEP 4.2 virtual box on Version 5.2.0_RC1 r118302 (Qt5.6.3)	Lars Sonchocky-Helldorf
18627	Guru meditation when execute perf top on Linux	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
19352	Guru Meditation when using more than 1 CPU + EFI (VINF_EM_TRIPLE_FAULT)	VirtualBox 6.1.4	2020-02-27T00:07:14Z	2020-03-13T17:35:01Z	2020-03-13T17:35:01Z	"When I use EFI + CPU greater than 1 the client crashes with Guru Meditation (VINF_EM_TRIPLE_FAULT). From version 6.1.0 the issue starts to occur and is still present in version 6.1.4. In version 6.0.18- the error didnt't occur once. 

'''I made a lot of tests so I claim the trigger for this error is EFI enabled + vCPU > 1.'''

This is also discussed in forum where I attached log files directly after crash in version 6.1.0. Do you need log files for 6.0.18 (latest working version) and 6.1.4 (latest failing version)?

https://forums.virtualbox.org/viewtopic.php?f=6&t=96937"	Tommy Parker
19402	GuruMeditation in a simple hobby operating system	VirtualBox 6.1.0	2020-03-14T17:16:16Z	2020-03-14T17:33:49Z	2020-03-14T17:33:49Z	"I was developing a hobby operating system that only loads a doubleword from disk to print it, buteven though the value was correctly printed to screen, I also got a GuruMeditation error.

This is the command I execute every time I  make any change to the source code to compile and test my kernel:

{{{
mkdir vbox ; \
VBoxManage controlvm ""X"" poweroff ; \
sleep 1 ; \
VBoxManage unregistervm ""e0b08add-d834-4af5-89e8-05abec11aa78"" ; \
rm -r vbox/X kernel kernel.raw kernel.vdi ; \
VBoxManage createvm \
    --name ""X"" \
    --ostype ""Other"" \
    --register \
    --basefolder ""$(pwd)/vbox"" \
    --uuid ""e0b08add-d834-4af5-89e8-05abec11aa78"" \
    --default ; \
VBoxManage modifyvm ""e0b08add-d834-4af5-89e8-05abec11aa78"" \
    --usbxhci on \
    --memory 8 ; \
nasm -l kernel.lst kernel.asm ; \
dd if=/dev/zero of=kernel.raw bs=1024 count=2048 ; \
dd if=kernel of=kernel.raw conv=notrunc ; \
VBoxManage convertfromraw kernel.raw kernel.vdi --format VDI ; \
VBoxManage storageattach ""X"" \
    --storagectl ""IDE"" \
    --port 0 \
    --device 0 \
    --type hdd \
    --medium ""$(pwd)""/kernel.vdi ; \
VBoxManage startvm ""X"" ;
}}}

This is the source code of my kernel (also attached to this ticket as kernel.asm):

{{{
VGA_MEMORY equ 0xB8000

BLACK         equ 0x0
BLUE          equ 0x1
GREEN         equ 0x2
CYAN          equ 0x3
RED           equ 0x4
MAGENTA       equ 0x5
BROWN         equ 0x6
LIGHT_GREY    equ 0x7
DARK_GREY     equ 0x8
LIGHT_BLUE    equ 0x9
LIGHT_GREEN   equ 0xA
LIGHT_CYAN    equ 0xB
LIGHT_RED     equ 0xC
LIGHT_MAGENTA equ 0xD
LIGHT_BROWN   equ 0xE
WHITE         equ 0xF

org 0x7C00
bits 16

mov ax, VGA_MEMORY >> 4
mov es, ax
mov ax, 0x07E0
mov ss, ax
mov esp, 0xFFF0
mov ax, 0
mov ds, ax

; Disable the annoying cursor
mov ah, 0x01
mov ch, 001_11111b
int 0x10

reset_disk_hdd:
    mov ah, 0x00  ; reset function
    int 0x13      ; disk int
    jc reset_disk_hdd

mov ax, 00h
mov ds, ax
mov si, disk_address_packet

read_disk_hdd:
    mov ah, 42h   ; read function
    int 0x13      ; disk int
    jc read_disk_hdd

mov ax, VGA_MEMORY >> 4
mov es, ax
mov ax, [0x7E00]
mov [es:0x00], ax

jmp $

disk_address_packet:
db 10h          ; size of DAP (set this to 10h)
db 00h          ; unused, should be zero
dw 44h          ; number of sectors to be read
dd 0x0000_7E00  ; segment:offset pointer to the memory buffer to which sectors will be transferred
dq 01h          ; absolute number of the start of the sectors to be read

times 510-($-$$) db 0

dw 0xAA55
dw (RED << 4 | GREEN) << 8 | 'P'
}}}

Apparently, when the number of sectors to be read is lower than 44h the guru meditation error disappear, but when it is 43h instead of 44h, it only appear ''sometimes''."	Mariana89
17919	Hackshield doesn't work in Virtualbox	VirtualBox 5.2.16	2018-08-08T18:11:50Z	2018-08-08T18:40:01Z	2018-08-08T18:40:01Z	"The issue is related to this one: https://www.virtualbox.org/ticket/4572

Guest OS: Win 7
Host OS: OSX Sierra

After 5-6 minutes playing to AirFlyFF (https://airflyff.com/) the game crashes due to Ahnlab Hackshield game hack found, when there is nothing else running besides the game itself. The game works smoothly on a Windows PC, and crashes only with Virtualbox."	Gnemes
19055	Hang in VM after upgrade to 6.0.14	VirtualBox 6.0.14	2019-10-31T15:32:43Z	2019-10-31T15:38:58Z	2019-10-31T15:38:58Z	"My Ubuntu VM hangs after detecting the network card. This started after updating to 6.0.14, and has vanished when I stepped back to 6.0.12.
Network setup on the VM is Bridged to Intel Ethernet Connection (4)I219-V with Allow All and cable connected. "	hobson42
19844	hangul keyboard problem	VirtualBox 6.1.10	2020-08-30T05:44:13Z	2020-09-17T12:22:33Z	2020-09-17T12:22:33Z	"Hi.

In VB 6.0, Hangul & Hanja key is working.(guest Windows, Ubuntu, etc.)

In VB 6.1, Hangul & Hanja key is not working. (guest Winwods, Ubuntu, etc.)

In both, VB SoftKeyboard is working.

Please correct it."	test2020
19269	Hard Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)	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
16429	Hard lockup of Linux guests on Mac Host	VirtualBox 5.1.14	2017-01-26T13:19:16Z	2017-05-30T23:50:35Z	2017-05-30T23:50:35Z	"I am running an Ubuntu 16.04 guest on a MacOS Sierra host.  In my guest I am running a Yocto project build (https://yoctoproject.org/).  This is a fairly substantial workload and eventually the target apparently locks up.  I've try to get kernel logs out of dmesg, /var/log/syslog and the VT1 console but when the system is hung, there is nothing printed to any of those locations indicating any trouble.

I have seen this happen also on Ubuntu 14 and CentOS 7 targets.

It is reproducible 100% of the time with the Yocto project build.  When it is hung, the GUI is still displayed but nothing updates, not even the clock app.

I tested with both VirtualBox 5.1.14 and 5.0.32 and could reproduce the issue with both versions.  I'm testing now with the 5.1.15 nightly build"	drewmoseley
19829	Hard to move VirtualBox guest windows	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
20820	Hardening Issue since 6.1.32	VirtualBox 6.1.32	2022-02-10T02:04:36Z	2022-04-11T18:42:29Z	2022-04-11T18:42:29Z	"Since 6.1.32-149290 I have a hardening error. The last version without this issue was 6.1.31-148916. 

I get an error ""NtCreateFile(\Device\VBoxDrvStub) failed: 0xc0000034 STATUS_OBJECT_NAME_NOT_FOUND (0 retries) (rc=-101)"" when I try to start a VM. The nonworking versions are also 6.1.33-149396, 6.1.33-149686, 6.1.33-149825. The logs from the version 
6.1.33-149686 are attached. 

This is Windows 10 21H2 VM on Windows 10 21H2 machine.
"	boxer01
19743	Hardening rejects DLL because of expired certificate nvldumdx.dll	VirtualBox 6.1.10	2020-07-21T13:04:30Z	2020-10-18T10:05:42Z	2020-10-18T10:05:42Z	"Im using a Nvidia GTX960 video card and it seems like the driver loader dll gets rejected because of an expired certificate.

The thing is that nvldumdx.dll is signed 2 times:
1. by Nvidia SHA1  (expired cert, was valid from 2018-2019)
2. by Microsoft SHA256  (valid cert)

Since Nvidia releases the file like that, I assume it's ok that only one of the signatures is valid, which is the case. But VirtualBox complains about the expired cert in the hardening log and rejects the file.

(VBox and video drivers are both the most recent releases)

{{{
2bc0.d1c: supHardenedWinVerifyImageByHandle: -> -23033 (\Device\HarddiskVolume4\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_edab19158bdd0d0a\nvldumdx.dll) WinVerifyTrust
2bc0.d1c: Error (rc=0):
2bc0.d1c: supR3HardenedScreenImage/LdrLoadDll: rc=Unknown Status -23033 (0xffffa607) fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume4\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_edab19158bdd0d0a\nvldumdx.dll: Certificate is not valid (ValidTime=2020-07-05T18:39:56.000000000Z Validity=[2018-07-18T17:42:53.000000000Z...2019-07-18T17:42:53.000000000Z]): \Device\HarddiskVolume4\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_edab19158bdd0d0a\nvldumdx.dll
2bc0.d1c: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_edab19158bdd0d0a\nvldumdx.dll
2bc0.d1c: Error (rc=0):
2bc0.d1c: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_edab19158bdd0d0a\nvldumdx.dll' (C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_edab19158bdd0d0a\nvldumdx.dll): rcNt=0xc0000190
2bc0.d1c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0xc0000190 'C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_edab19158bdd0d0a\nvldumdx.dll'
2bc0.d1c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status -23033 (0xffffa607)) on \Device\HarddiskVolume4\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_edab19158bdd0d0a\nvldumdx.dll
2bc0.d1c: Error (rc=0):
2bc0.d1c: supR3HardenedScreenImage/LdrLoadDll: cached rc=Unknown Status -23033 (0xffffa607) fImage=1 fProtect=0x0 fAccess=0x0 cHits=1 \Device\HarddiskVolume4\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_edab19158bdd0d0a\nvldumdx.dll
2bc0.d1c: Error (rc=0):

}}}
"	Peter B
19491	have errors showing up trying to get into macOS Catalina	VirtualBox 6.1.4	2020-04-14T22:44:21Z	2020-04-16T09:49:23Z	2020-04-16T09:49:23Z	This is the first time I am trying to get into Catalina from my windows 10-64 bit environment.  I have tried several times but I am getting error codes.as shown.  	esams2
9052	Have Virtual Machines create .desktop icons for Gnome 3	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
18769	headless on server without xserver	VirtualBox 6.0.10	2019-07-18T07:00:19Z	2019-07-18T11:57:55Z	2019-07-18T11:57:55Z	"Also in version 6.0.8

can not compile headless on server without x11 server , fails for opengl lib, headfile gl.h.

is there a patch or a new switch "	WMOE
19735	headless start failed with vmsvga display	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
18002	Heap corruption in VBoxSVC.exe leading to a crash (possibly due to double free)	VirtualBox 5.2.18	2018-09-22T14:47:11Z	2018-10-08T14:28:45Z	2018-10-08T14:28:45Z	"I have encountered a crash of latest VBoxSVC.exe 5.2.18.24319 on a Windows 10 host while running two VMs in parallel (one Windows VM and one Linux VM). The crash happend while I was accessing internet resources from the Linux VM.

I have collected a crash dump which indicates that the crash is caused by a heap corruption in VBoxSVC.exe while calling free function from msvcr100.dll. So, this looks like a double-free issue in VBoxSVC.exe.

I could not find a way to reproduce this crash. Usually, I run 3 or 4 VMs at the same time but VBoxSVC never crashed but this time just with 2 VMs and no extensive CPU load (just internet browsing) and it crashed.

I'm attaching the full log from Linux machine. For the crash dump, I can post it but since it is related to potential double free issue in VBoxSVC which are sometime a security vulnerability I prefer to confirm with you first that it is ok to post here.

"	idrassi
16783	"held keypress causes ""flickering"" responses in VM"	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
21329	Help doc comes up behind new VM dialog and can't be accessed	VirtualBox-7.0.4	2022-12-09T21:46:55Z	2022-12-09T21:46:55Z	2022-12-09T21:46:55Z	"1) start a new VM
2) in the ""Create Virtual Machine"" dlg, click the Help button - the help doc opens but you can't get to it!

Also, the ""?"" in the title bar does nothing useful, so I couldn't even use that as an alternate."	Justinh
13731	High CPU load when smooth-scrolling	VirtualBox 4.3.20	2015-01-04T02:26:32Z	2015-01-04T02:26:32Z	2015-01-04T02:26:32Z	"I have noticed that when smooth-scrolling in either Firefox or Chrome, either by continuously running the mouse wheel, or by mid-click to activate auto-scroll and then moving the cursor slightly to slowly start scrolling, I get very high CPU load. At usual reading pace I can often get 70-80% CPU, slightly less when I scroll slower. This surprises me, since scrolling really shouldn't be a CPU intensive task! Under the Windows host, smooth scrolling never takes any CPU at all. Also, the Linux guest feels a bit more sluggish when scrolling compared to the Windows host. I am running Compiz, and 3D is generally working well (if using the 3D-box desktop, and it rotates nicely).

It is a bit of a bother, since this significantly reduces battery time: When just browsing the web, I scroll while reading, and this usually loads the CPU high enough to spin up the fan. Obviously, all that heat is a battery drain!

I am using a dual-boot Windows 8.1 and Windows 7 host with an Ubuntu 14.04 LTS guest on an ASUS 550JV laptop (Core I7-4700HQ, 16GB RAM and nVidia GT-750M). I have seen this on Virtualbox 4.3.12 (with guest additions 4.3.14) and on 4.3.20 (with guest additions 4.3.20). Virtualbox has one core and 6GB RAM. 3D in general is working well, as mentioned."	00prometheus
16543	High CPU load with MP Linux 4.10 guest	VirtualBox 5.1.16	2017-03-09T09:21:48Z	2018-08-22T07:53:27Z	2018-08-22T07:53:27Z	"When a Linux 32-bit guest is configured with 2 processors and uses the 4.10 kernel, it loads 100% a host processor core.
It doesn't happen with kernel 4.9 and before.
It doesn't happen with a single guest processor.

During boot the message {{{smpboot: do_boot_cpu failed(-1) to wakeup CPU#1}}} appears."	Urmas
16535	High CPU on Host while Low CPU on Guest	VirtualBox 5.1.14	2017-03-07T13:29:46Z	2017-03-07T13:29:46Z	2017-03-07T13:29:46Z	"I am referring here to very old bug found:
https://www.virtualbox.org/ticket/894

I am on Gentoo system with kernel 4.10.0 and guest is running Windows 10 x64 - hardware is Dell XPS 9550 with USB-C.

Situation is similar to that old bug, while having about 2-10% CPU usage in guest, the host VirtualBox processes consumes about 20-50%. I checked the USB config and I was using default OHCI 1.x, I switched it off, while GUI tells you that it will be enabled by default anyway on the start and tested again and voiala, the load dropped down. Note that I was experiencing this issue for few weeks.

Now I switched to xHCI and the load is still low. So it actually only happened on newly installed Windows 10 with default VM settings.

I think the only way to reproduce this behavior is to reinstall Windows in new guest again.

Regards,

Ladislav




"	archenroot
10611	High CPU usage from interrupts (20% on 8 idle processors)	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
20749	High cpu usage in guest on several cores causes severe host lagging.	VirtualBox 6.1.30	2021-12-24T18:55:56Z	2021-12-24T21:58:52Z	2021-12-24T21:58:52Z	"I have AMD Ryzen 3 3100 4-Core Processor hyperthreaded.
When I run atlas simulation job from lhc@home on virtualbox with 4 cores 
system starts to lag."	kotenok2000
12851	High cpu-load (up to 100%) on idle	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
10275	Horizontal tilting (in certain Guests) behaves like Vertical Scrolling		2012-02-24T05:06:30Z	2019-08-07T11:25:11Z	2019-08-07T11:25:11Z	"Under VBox, the Win7 guest and FreeBSD guest recognizes horizontal titling of the VBox mouse driver, but translates horizontal tilting of the mouse as vertical scrolls when it should be horizontal scrolls.

Horizontal tilting works out of the box for the Ubuntu guest -> i.e. horizontal tilting maps to a horizontal scroll."	rayne
10838	Horizontal wheel-scroll becomes alt-vertical-wheel-scroll	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
18785	Host Bluetooth Stops Working	VirtualBox 6.0.10	2019-07-24T11:51:03Z	2019-07-25T07:26:39Z	2019-07-25T07:26:39Z	"My Host PC is a LENOVO  ThinkPad P51s W10DG on a Microsoft Windows 10 Enterprise 10.0.18362 64-bit OS platform.
When upgrading to  VirtualBox Graphical User Interface
Version 6.0.10 r132072 (Qt5.6.2)
Copyright © 2019 Oracle Corporation and/or its affiliates. All rights reserved

Starting Guest PC causes the Host PC to lose Bluetooth connections to Mice, Keyboards, audio speakers, etc...


Able to open Windows 10 Bluetooth services - no connection showing.  Taskbar missing Bluetooth icon as well.

Reviewing older versions that had similar problems in the past.
Is there a patch that should be done?

By rolling back version to VirtualBox 5.2.30 - Bluetooth is enabled on Host while guest virtual is running.
"	Robbie2020
11509	Host CD passthrough not consistant	VirtualBox 4.2.6	2013-02-20T20:26:16Z	2013-02-21T16:59:29Z	2013-02-21T16:59:29Z	"When choosing the host CD as the attached media device to be able to view video or use as a writeable CD/DVD, I need to set this with the guest stopped.  After you change from the Host CD to an ISO, like the guest additions and then go back to the Host CD the passthrough is no longer enabled, requiring a complete shut-down of the guest to select and enable passthrough again.

I wonder if there is a way to make this default or at least add the CD/DVD passthrough as a VBoxManage controlvm function?"	Perry G
18089	Host CPU load 100% for idle guest	VirtualBox 5.2.20	2018-10-30T08:21:29Z	2020-06-10T16:51:40Z	2020-06-10T16:51:40Z	"Host: macOS 10.12.6
Guest: Linux (Ubuntu 16.04)

After upgrading Virtualbox to 5.2.20, I ran a single guest which I'd used many times before.  The guest decided to do an auto-update, which is fine.

However even after the update had finished, on the *host*, CPU used by the VirtualBox process remained stuck at 100%, as shown by Activity Monitor and (here) ""top -o cpu"":

{{{
Processes: 326 total, 3 running, 323 sleeping, 1550 threads                                                         08:15:02
Load Avg: 2.34, 2.50, 2.10  CPU usage: 31.47% user, 7.26% sys, 61.25% idle
SharedLibs: 229M resident, 51M data, 62M linkedit. MemRegions: 65898 total, 7787M resident, 147M private, 1418M shared.
PhysMem: 14G used (4448M wired), 2268M unused. VM: 879G vsize, 627M framework vsize, 0(0) swapins, 0(0) swapouts.
Networks: packets: 197313/179M in, 123489/30M out. Disks: 385658/8849M read, 161264/4111M written.

PID   COMMAND      %CPU  TIME     #TH   #WQ  #PORT MEM    PURG   CMPRS  PGRP PPID STATE    BOOSTS         %CPU_ME %CPU_OTHRS
1810  VirtualBoxVM 105.5 17:19.54 44/1  5    392   2193M  8048K  0B     1810 1805 running  *1[5]          0.00000 0.00000
335   iTerm2       14.6  01:56.18 11    5    281-  164M-  34M-   0B     335  1    sleeping *0[305]        0.04101 1.50065
}}}

But inside the *guest*, CPU was ~99% idle.  Again, here with ""top"" but inside the guest:

{{{
top - 08:16:00 up 44 min,  1 user,  load average: 0.00, 0.07, 0.11
Tasks: 583 total,   1 running, 582 sleeping,   0 stopped,   0 zombie
%Cpu(s):  0.3 us,  0.3 sy,  0.0 ni, 99.3 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
KiB Mem :  2048156 total,   238796 free,  1136680 used,   672680 buff/cache
KiB Swap:   786428 total,   747596 free,    38832 used.   554244 avail Mem

  PID USER      PR  NI    VIRT    RES    SHR S %CPU %MEM     TIME+ COMMAND
 4441 101001    20   0 2552704  62904  14900 S  0.3  3.1   0:05.32 java
 7579 brian     20   0   42240   4268   3172 R  0.3  0.2   0:00.02 top
    1 root      20   0   38320   6280   4016 S  0.0  0.3   0:02.16 systemd
}}}

After shutting down and restarting the guest, the problem went away. This again on the host:

{{{
Processes: 325 total, 3 running, 322 sleeping, 1501 threads                                                         08:18:39
Load Avg: 1.90, 2.28, 2.10  CPU usage: 2.68% user, 6.34% sys, 90.97% idle
SharedLibs: 229M resident, 51M data, 62M linkedit. MemRegions: 66300 total, 7793M resident, 150M private, 1428M shared.
PhysMem: 14G used (4458M wired), 2178M unused. VM: 876G vsize, 627M framework vsize, 0(0) swapins, 0(0) swapouts.
Networks: packets: 201757/182M in, 127536/32M out. Disks: 419879/9460M read, 166954/4317M written.

PID   COMMAND      %CPU TIME     #TH   #WQ  #PORT MEM    PURG   CMPRS  PGRP PPID STATE    BOOSTS          %CPU_ME %CPU_OTHRS
6140  VirtualBoxVM 7.8  00:49.13 41    4    396   2144M  18M    0B     6140 1805 sleeping *1[4]           0.00000 0.00000
0     kernel_task  7.1  07:13.29 134/4 0    2     1199M  0B     0B     0    0    running   0[0]           0.00000 0.00000
}}}
"	bcandler
20948	Host CPU very high when guest is idle	VirtualBox 6.1.32	2022-05-19T17:11:07Z	2022-05-19T17:11:07Z	2022-05-19T17:11:07Z	"Hi,
running Virtualbox on MAC OS X Monterrey (12.4) virtualbox gets very high CPU even when windows guest is completely idle, 1%-3% approx.

Right now I´ve set up Execution Tap to 50%, but nothing changes virtualbox process on running above 98%, when Execution Tap is 100%, cpu on host is above 200% and my mac sounds like an helicopter!

Logs here: https://logpaste.com/6c57FdSg

Note: All guest additions are installed on guest"	Raul
18424	Host crashes when using VirtualBox	VirtualBox 5.2.26	2019-02-11T03:19:50Z	2019-02-11T03:19:50Z	2019-02-11T03:19:50Z	"The problem I have is that sometimes my host (Windows 10 laptop) crashes sometimes when I am using VirtualBox. This only happens if I close the laptop or if it goes to sleep while a VM is still running. 

Whenever the laptop goes to sleep while a VM is running, the host will shut down all applications and restart the computer. Occasionally, there will be a BSOD instead of the host just restarting. I was wondering if this is a common issue when users leave a VM running. The VM was Ubuntu 18 and the host was Windows 10."	mttwh
18782	Host machine crashes when booting guest for installation	VirtualBox 6.0.10	2019-07-23T11:55:51Z	2019-07-25T08:29:22Z	2019-07-25T08:29:22Z	"I posted a couple of threads seeking help for my issue, someone suggested I post a bug report.

https://superuser.com/questions/1462614/oracle-virtualbox-host-machine-crashes-when-booting-guest-for-installation

https://forums.virtualbox.org/viewtopic.php?f=6&t=93933&sid=4632274c1fd7c536357bd0c7c7877e99
"	diamondpumpkin
16256	Host OS kernel panic when running Redox 0.0.3 in VirtualBox	VirtualBox 5.0.26	2016-12-01T21:14:35Z	2017-02-08T15:19:30Z	2017-02-08T15:19:30Z	"'''Reproduction:'''

* Start VirtualBox 5.0.26 for Mac OS X 10.12.1.
* Create a new virtual machine set to Unknown Linux 64-bit, with 1024 MB RAM; [https://gist.github.com/msikma/b2d3ea03d49c68ef4e72a16285f36394 everything else default].
* Start the virtual machine with the [https://github.com/redox-os/redox/releases/tag/0.0.3 Redox 0.0.3] iso as boot media.

'''Expected behavior:'''

Expect the ISO to boot into the Redox system.

'''Actual behavior:'''

[https://gist.github.com/msikma/ac688246fef0868a711778dc9a0cfa39 Host OS kernel panic], causing an immediate reboot.

'''Other information:'''

[https://github.com/redox-os/redox Redox] is a new OS in early stages of development. 0.0.3 is the first precompiled ISO release. Many others have managed to run it in VirtualBox just fine, so there might be something weird going on with my setup.

Unfortunately I can't seem to find a log file anywhere. Can't find it either in $HOME/Library/VirtualBox or in the VM directory itself.

I've linked my VM configuration and crash report above."	msikma
19109	Host resume and VM does not respond	VirtualBox 6.0.14	2019-11-26T16:34:45Z	2019-12-10T10:44:09Z	2019-12-10T10:44:09Z	"Twice today I've resumed my host (after the host has gone to sleep because I've been away from my desk) and the guest has been frozen. The screen display is restored but the mouse isn't active.

After a minute or so the VM crashes and I have to restart the VM.

Logs are attached from after second crash."	Iain Waddell
13749	Host Screen numbers are reversed in full screen mode	VirtualBox 4.3.20	2015-01-10T06:01:39Z	2015-11-21T09:06:25Z	2015-11-21T09:06:25Z	"I have two identical monitors. When I run a VM (with a single virtual monitor) in full screen mode, I can use Mini Toolbar, View->Virtual Screen 1 to move the VM from one monitor to the other. However the monitor number is wrong - when I select Host Screen 1 (the left monitor), it puts the VM on monitor 2 (on the right), and vice-versa. I've checked the host machine display properties (including ""Identify"") and verified that host monitor 1 is on the left and 2 is on the right.

It used to work correctly, however I recently swapped the two physical monitors, ie left to right and right to left, and so far as I can tell that's when the problem with virtual box started.

At the time I swapped the monitors, I was doing some fault finding, so the host PC was switched on/off a few times with various combinations of one or both monitors disconnected, primary monitor being one or the other, swapping cables between monitors etc. (Virtual Box was not run at any time during this.) The problem turned out to be a physical/optical defect in one monitor - which was originally my primary monitor (number 1, on the left), so that monitor is now my secondary (number 2, on the right). (Swapping them back is not an option.) After I finished, I went to Windows Control Panel and ensured that monitor 1 (eg as shown by the ""Identify"" button) is on the left and is my main display, and the monitor 2 on the right is the secondary - it had changed during the process of testing. The port on the video card that's used for the left monitor hasn't changed - only the monitors have swapped places.

The host machine appears to correctly identify the monitors, but now Virtual Box puts the full-screen VM on the opposite monitor to what the mini toolbar menu item says.

The problem is not user-specific. I can replicate it with a different user on the same host PC.

Uninstalling/reinstalling VirtualBox does not fix the problem.

I've tried assorted combinations of disconnecting one or other of the monitors, restarting the machine etc, to see if that will fix it, but it doesn't make any difference.

I even reverted to a (Windows Backup and Restore) system image taken before the monitors were swapped, and that didn't fix the problem either.

It's as if VirtualBox's ""host screen 1"" is tied to the original physical monitor 1, rather than the logical monitor 1 (ie as Windows identifies it after swapping them).

Technical details:

Host is Windows 7 Ultimate, SP1, 64-bit. (The problem appears to be independent of the guest OS - I can replicate it with Windows and Ubuntu guests, and no guest OS at all, just the VM BIOS on a newly created VM with no software installed.)

The monitors are both Dell 2209WA.

Video card is AMD Radeon HD 6670.
"	m6477
14436	Host screen saver do not start on VirtualBox 5	VirtualBox 5.0.0	2015-08-14T00:30:12Z	2015-09-10T16:20:44Z	2015-09-10T16:20:44Z	"When there is a virtual machine running and the relative window is active, the screen saver of the Host, when the time is elapsed, starts but terminates immediately.
Tested on VirtualBox v5.0 and v5.0.2
Host tested: Win 7 x64 Professional SP1
Guests tested: Win 7 x64 Ultimate SP1 and Windows XP x86 SP3
"	bmn
18720	Host system freezes as soon as the mouse pointer enters the VM on nVidia	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
18547	Host Win 10, Guest win XP works fine with 5.2.22. Win XP crash wtih 6.02 or higher	VirtualBox 6.0.2	2019-04-06T06:29:05Z	2019-04-12T22:52:50Z	2019-04-12T22:52:50Z		Trehin
19252	host Win10 crashes when guest Win10 reboots after update	VirtualBox 6.0.14	2020-01-22T02:56:05Z	2020-01-22T03:06:49Z	2020-01-22T03:06:49Z	"BSOD
DRIVER_IRQL_NOT_LESS_OR_EQUAL
VBoxDDR0.r0 

Happens only on guest restarts after it installed windows updates"	EugeneK
21455	Host with v7.0.6 seeing significantly higher cpu usage vs v6.1.40	VirtualBox-7.0.6	2023-02-03T01:26:40Z	2023-02-04T20:15:27Z	2023-02-04T20:15:27Z	"I just tested the latest version 7.06 running the same exact vm's. 20 vms in and it's already at 38% cpu.

I tried the same vm's again using v6.1.40 and I can run 40 vm's no problem while only using 18% cpu.

Host system

CPU: Dual EPYC 7742
Ram: 500G
Drive: U.3 SSD's


Windows 7 guest.
I'm running the 32-bit 4 wallets on each vm.
https://www.crypto-city.com/element-hyp/wallet/
https://www.crypto-city.com/truckcoin-trk/info
https://www.crypto-city.com/xra-rate-coin/info
https://www.crypto-city.com/bitflowers/wallet/"	VirtualBoxFan
15058	Host+<key> doesn't work if host layout not US	VirtualBox 5.0.14	2016-01-21T10:09:35Z	2016-01-27T08:28:45Z	2016-01-27T08:28:45Z	"On my host (OSX 10.9.5) I have a dual keyboard layout; US and Greek. If the host keyboard is set to Greek, Host+<key> combinations do not work, i.e. Host+""F"" (which is seen as Host+""Φ"") does not toggle fullscreen mode. Is there a way to have the keyboard recognized regardless of the layout? Keyboard shortcuts on the host (like Cmd+H for hide) work that way, i.e. they don't care for the current layout, it's the underlying key that's important. It would be really convenient.

NB. I tried the same operation on a Windows host and it works independently of the host keyboard layout."	Socratis
13141	Host+Tab support to switch between running VMs	VirtualBox 4.3.12	2014-06-24T20:15:34Z	2014-06-24T20:15:34Z	2014-06-24T20:15:34Z	Can you support Host+Tab support to switch between running VMs?  (i.e. right Control+Tab)  This would be similar to the Alt+Tab feature used by many operating systems.	Seann
16975	Host-Only network vboxnet0 unvaliable until reload kernel module (FreeBSD host)	VirtualBox 5.1.24	2017-08-03T11:47:26Z	2017-08-07T07:03:17Z	2017-08-07T07:03:17Z	"Such as the problem, My guest use 3 ethercard:1 bridged, 1 NAT and 1 host-only.
the guest can't boot and show a error message after I reboot my computer. I have to unload and reload module to boot the guest.


The OS & software
{{{
FreeBSD 11.1-RELEASE r321648 amd64
virtualbox-ose-5.1.24          General-purpose full virtualizer for x86 hardware
virtualbox-ose-kmod-5.1.24     VirtualBox kernel module for FreeBSD
}}}


forgive my poor english and THKS for fix."	rezo.chiang
16123	Host: Windows 10 x64, Guest: Debian x64. Host gets unusable, kind of freezes.	VirtualBox 5.1.8	2016-10-27T08:25:31Z	2016-12-07T09:59:30Z	2016-12-07T09:59:30Z	"Hi,

first my Setup:

Host:
CPU: Intel i7-6700K.
GPU: NVIDIA GeForce GTX 1060, Driver: 372.90.
Windows 10 64-Bit. Avira Antivirus.
VirtualBox 5.1.8

Guest:
Debian 8.6.0 amd64.


Basically most functionality works fine. The VM starts and works like a charm. But after a few minutes of using the Debian-Guest the Host begins to act strange. On the Windows 10 Host i can't start new Windows anymore. The Processes start, as seen in the Task-Manager, but no Windows appear. Already before started Programs in already running Windows are still working perfect, except something like System-Monitor Desktop-Widgets, which are freezing. Even the Start-Menu doesn't show up, if i click on the Windows-Banner. Ctrl+Alt+Del brings me a BlackScreen.
From this Point the VM still works great. But if i try to shut it down, VirtualBox freezes completely.
The only Way to get the Host back working from this Point is the Hard-Reset-Button.
Maybe a compatibility Problem between the Virtualization and the Graphics-Driver. I encountered a similiar Problem some time ago with another Virtualization Solution on another Platform, where it caused the NVIDIA Driver to collapse."	DenKr
20019	Hosted VM is restarting unexpectedly which contains VirtualBox	VirtualBox 6.1.16	2020-11-05T08:16:49Z	2020-11-05T08:16:49Z	2020-11-05T08:16:49Z	"We've a Windows 10 Azure VM  which we have installed latest VirtualBox on it. After starting image on VB, everything is fine. But, when we try to login to guest vm via filezilla/putty from hosted vm, it's restarting hosted VM suddenly. 

Please check log that belongs to guest vm that we having problem."	alpercelerce
18795	Hotmail messages not loaded	VirtualBox 6.0.10	2019-07-29T02:13:25Z	2019-08-14T20:54:54Z	2019-08-14T20:54:54Z	Just installed VB6 and can no longer open hotmail messages. Also, Inbox messages are not updated after items are deleted.	elclaudon
16174	HPE Smart Storage Administrator utility lockup error 851	VirtualBox 5.0.26	2016-11-09T17:01:13Z	2016-11-09T17:01:13Z	2016-11-09T17:01:13Z	"Long time we have curious trouble with virtualbox.
HOST W2012 64 SERVER HP ProLiant ML310e Gen8
When we use smart array gui or utility , this report on Dynamic Smart Array B120i RAID
851 Controller lockup error: Restart the server and run a diagnostic report. Install the latest version of controller firmware. If the condition persists, the controller may need to be replaced or require service 

This error ocurs when virtualbox is run and use direct hardware access with VTx.
Guest os is openSUSE 64 13.1 

Issue not change more as year and last four kernels...

When vbox is off lockup not present, when no hardware direct , too no lockup, but Linux guest system is unstable .

Raid Works ok with or without lockup, but with lockup we cant control raid status. HP utility show nothing in error state.

Dynamic Smart Array B120i RAID controller have latest drv and fw.
Issue tested on 5.0.4 - 5.0.26 i mean next too but not tested now.

Please help.
"	mguru
17379	https for download.virtualbox.org is wrongly configured	VirtualBox 5.2.2	2017-12-19T17:51:08Z	2017-12-21T16:09:52Z	2017-12-21T16:09:52Z	"see ticket #16757 configuration is wrong again and the certificate is returning the wrong name:

Common Name (CN)	a248.e.akamai.net

until resolved Chrome won't let you download extension pack"	ckcin
15812	Human Interface devices are not detected by the Virtual machine	VirtualBox 5.1.4	2016-08-17T16:25:59Z	2016-08-17T16:53:34Z	2016-08-17T16:53:34Z	"When I connect a Human interface device to my Windows 7 PC it is detected.  When I try to connect it to my Virtual Box machine, it is not detected.  An error appears when I try to pick in the Device menu - Unknown device.
It used to work when the USB settings were set to 2.0 on VB version 5.0.24
I have attached 2 images.
One from my working Win7 PC and one from the Win7 VB that does not work."	skh
18589	I am experiencing an issue starting my Windows 10 virtual machine	VirtualBox 6.0.6	2019-04-21T12:38:16Z	2019-04-21T12:38:16Z	2019-04-21T12:38:16Z	I downloaded a windows 10 virtual machine from their website and extracted the VM, I imported the virtual machine using the default settings and I received the error in the picture, I have increased my RAM dedicated to the machine and given it higher processing power, I use many VM's but only experiencing the issue with this virtual machine.	Erynh777
14097	I can not connect the drive to Virtualbox.	VirtualBox 4.3.26	2015-05-06T09:23:52Z	2015-05-06T13:08:09Z	2015-05-06T13:08:09Z	"Не удалось открыть файл виртуального жёсткого диска E:\arut-minimal.vdi.

After transferring from one resource to another error occurred.

Could not get the storage format of the medium 'E:\arut-minimal.vdi' (VERR_NOT_SUPPORTED).
{{{
Код ошибки: VBOX_E_IPRT_ERROR (0x80BB0005)
Компонент: Medium
Интерфейс: IMedium {05f2bbb6-a3a6-4fb9-9b49-6d0dda7142ac}
Вызванный интерфейс: IVirtualBox {fafa4e17-1ee2-4905-a10e-fe7c18bf5554}
Код ошибки метода: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)
}}}
I tried using vboxmanage for repair.
{{{
c:\Program Files\Oracle\VirtualBox>vboxmanage internalcommands repairhd -dry-run -format VDI e:\clients\arut-minimal.vdi
VBoxManage.exe: error: VDI: invalid pre-header in 'e:\clients\arut-minimal.vdi'
VBoxManage.exe: error: Error code VERR_VD_IMAGE_REPAIR_IMPOSSIBLE at F:\tinderbo
x\win-4.3\src\VBox\Storage\VDI.cpp(3039) in function int __cdecl vdiRepair(const char *,struct VDINTERFACE *,struct VDINTERFACE *,unsigned int)

c:\Program Files\Oracle\VirtualBox>vboxmanage internalcommands repairhd -format VDI e:\clients\arut-minimal.vdi
VBoxManage.exe: error: VDI: invalid pre-header in 'e:\clients\arut-minimal.vdi'
VBoxManage.exe: error: Error code VERR_VD_IMAGE_REPAIR_IMPOSSIBLE at F:\tinderbox\win-4.3\src\VBox\Storage\VDI.cpp(3039) in function int __cdecl vdiRepair(const char *,struct VDINTERFACE *,struct VDINTERFACE *,unsigned int)
}}}"	Speltor
20001	i can not start 64bit installation	VirtualBox 6.1.16	2020-10-26T17:44:05Z	2020-10-26T17:44:05Z	2020-10-26T17:44:05Z	i started virtual pc and then i put dvd disc for 64bit windows 10 and started virtual machine. then error ocured that say i do not have 64bit processor.	puppygamer1994
17530	I can not startup my Vbox, Somo time ago changed my computer and from the DVI backups cant run the machine	VirtualBox 5.2.6	2018-02-07T17:40:40Z	2018-02-08T10:50:46Z	2018-02-08T10:50:46Z	"Fallo al abrir una sesión para la máquina virtual Rockwell X64.

The virtual machine 'Rockwell X64' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\isr_p\VirtualBox VMs\Rockwell X64\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Componente: MachineWrap
Interfaz: IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}

"	Rocko
19814	I can't install Windows 2019 in a virtualbox machine	VirtualBox 6.1.10	2020-08-14T15:31:32Z	2020-08-14T15:50:11Z	2020-08-14T15:50:11Z	"When I try to add a virtualbox machine and start the instalation from The ISO image, I get ERROR

The Host where it runs virtualbox is Windows 2008R2 64bits with lasts updates"	LluisG
21042	I can't open the app	VirtualBox 6.1.36	2022-08-01T18:32:01Z	2022-08-01T19:06:00Z	2022-08-01T19:06:00Z	So I just tried to install the app but when I try to launch it after installing it it just keeps on the background and it doesnt start up, I tried everything I found on google but noyhing works	ZenZen
20101	I can't stat my virtual box machine	VirtualBox 6.1.16	2020-12-26T05:31:57Z	2020-12-26T05:31:57Z	2020-12-26T05:31:57Z	"Не удалось открыть сессию для виртуальной машины xp.

The native API dll was not found (C:\Windows\system32\WinHvPlatform.dll) (VERR_NEM_NOT_AVAILABLE).

VT-x is disabled in the BIOS for all CPU modes (VERR_VMX_MSR_ALL_VMX_DISABLED).

Код ошибки: E_FAIL (0x80004005)
Компонент: ConsoleWrap
Интерфейс: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

"	mikhasenko
20835	I cannot do normal start it only start as uncoupled start	VirtualBox 6.1.30	2022-02-21T06:45:18Z	2022-02-21T21:56:18Z	2022-02-21T21:56:18Z	"The virtual machine 'android32bvb_7_1_int11' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'G:\Virtual Machines\android32bvb_7_1_int11\Logs\VBoxHardening.log'.


Código resultado: 
E_FAIL (0x80004005)
Componente: 
MachineWrap
Interfaz: 
IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}
"	Jose Nunez
17906	I cant run my VM	VirtualBox 5.2.16	2018-07-31T13:55:46Z	2018-07-31T14:24:44Z	2018-07-31T14:24:44Z	"Good day,
I need your help solve my vm problem, it cant run, I have the message and the name error that printout.
""
Error in supR3HardNtChildWaitFor
Timed out after 2001 ms waiting for child request #0
(PurifyCuildAndCloseHandles).
(rc=258)

Please try reinstalling VirtualBox.

where supR3HardNtChildWaitFor what? 5 Unknow Status 258 (0x102)(258)-
Unknown Status 258 (0x102)
"""	BrADT23
18556	I can´t able to start a virtual machine	VirtualBox 6.0.4	2019-04-10T18:05:20Z	2019-04-10T21:59:36Z	2019-04-10T21:59:36Z	When I want to start a virtual machine whit Sas Univertisty, Virtual Box indicated me that is necessary to reinstall the program. I have done it several times, but the problem persists.  	couttolenc
19958	I double click on Virtual Box and it does not open	VirtualBox 6.1.14	2020-10-11T15:48:39Z	2020-10-11T15:48:39Z	2020-10-11T15:48:39Z	Hi, I've been with a problem with virtual box for a month, I install it correctly, but I double-click it and it does not open, nothing, it does nothing, I have tried everything, I have formatted the operating system (Windows 10) I have tried several versions of Windows 10, several versions of oracle Virtual Box, I have virtualization correctly activated, because it is intermittent, one day it opens for me, and the next for example not, sometimes the program opens and sometimes not, I'm desperate .	Víctor Sierra
16676	I get an error E_FAIL (0x80004005) when saving the state of my machine	VirtualBox 5.1.18	2017-04-20T13:47:11Z	2017-04-20T13:47:11Z	2017-04-20T13:47:11Z	I work on a virtual machine with a lot of things open and I like save the state of my machine instead of turn it off, but a few days ago that I get this error every time and i don't know why it is	rusoLoco22
18266	I met 0X00000000 error when I click the menu->device->usb on windows system.	VirtualBox 6.0.0	2019-01-03T12:30:18Z	2019-01-03T15:35:29Z	2019-01-03T15:35:29Z	"I met 0X00000000 error when I click the menu->device->usb on windows system.it happens if then mouse click on then menu ""device"" and moved to the ""USB device"" submenu,from version 5.2 to 6.0."	yihua2000
20244	I was attempting to import VM Appliance files	VirtualBox 6.1.18	2021-03-11T04:30:29Z	2021-03-12T09:29:03Z	2021-03-12T09:29:03Z	"I purchased a class “ OBIEE Developer course” on Udemy.

It requires downloading Virtual Box ( done) and VM Appliance files. No
matter, how many times I tried, it failed. Error message attached.

Kindly help me to overcome this obstacle, so I proceed with learning
the OBIEE Developer course.
 Error message. Result Code: INVALIDARG; 0x80070057
 "	Olechka
13022	I/O errors reported by kernel for device backed by VDI	VirtualBox 4.3.10	2014-05-09T05:28:05Z	2015-07-14T12:15:31Z	2015-07-14T12:15:31Z	"/dev/sda backed by a VDI

/dev/sdb backed by a vmdk, created with the command:
sudo VBoxManage internalcommands createrawvmdk -filename /Users/chris/VirtualBox\ VMs/Fedora\ Rawhide/320g.vmdk -rawdisk /dev/disk2

/media/sf_chris/ is a Shared Folder whose source is HFS+

During sustained copying from /media/sf_chris and writing to /dev/sdb, the kernel reports spurius read and write errors from /dev/sda which is essentially inactive in this process. Long file copies (10 minutes) eventually result in segfaults, the system will no longer respond to commands and I can't even get kernel messages out of the VM to see what's gone wrong other than it looks like the I/O errors are effectively corrupting the OS as it's running.

[  222.202808] rawhide.localdomain kernel: sd 0:0:0:0: [sda] Unhandled error code
[  222.203003] rawhide.localdomain kernel: sd 0:0:0:0: [sda]  
[  222.203287] rawhide.localdomain kernel: Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
[  222.203407] rawhide.localdomain kernel: sd 0:0:0:0: [sda] CDB: 
[  222.203528] rawhide.localdomain kernel: Write(10): 2a 00 00 58 a1 c8 00 02 00 00
[  222.203644] rawhide.localdomain kernel: end_request: I/O error, dev sda, sector 5808584
[  222.203746] rawhide.localdomain kernel: BTRFS: bdev /dev/sda3 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0
[  273.598086] rawhide.localdomain kernel: sd 0:0:0:0: [sda] Unhandled error code
[  273.598179] rawhide.localdomain kernel: sd 0:0:0:0: [sda]  
[  273.598255] rawhide.localdomain kernel: Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
[  273.598341] rawhide.localdomain kernel: sd 0:0:0:0: [sda] CDB: 
[  273.598437] rawhide.localdomain kernel: Read(10): 28 00 01 17 73 40 00 00 20 00
[  273.598533] rawhide.localdomain kernel: end_request: I/O error, dev sda, sector 18314048
[  273.598618] rawhide.localdomain kernel: BTRFS: bdev /dev/sda3 errs: wr 1, rd 1, flush 0, corrupt 0, gen 0

The host kernel messages report no IO related errors. But does report other things related to VirtualBox at the time the problem occurs:

May  8 23:04:16 ming kernel[0]: VBoxDrv: host_vmxoff -> vmx_use_count=0
May  8 23:04:44 ming kernel[0]: VirtualBox (map: 0xffffff8050dfec18) triggered DYLD shared region unnest for map: 0xffffff8050dfec18, region 0x7fff8ba00000->0x7fff8bc00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
May  8 23:04:48 ming kernel[0]: VirtualBoxVM (map: 0xffffff803cc1b138) triggered DYLD shared region unnest for map: 0xffffff803cc1b138, region 0x7fff8ba00000->0x7fff8bc00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
May  8 23:04:48 ming kernel[0]: VBoxDrv: host_vmxon  -> vmx_use_count=1 rc=0
May  8 23:04:48 ming kernel[0]: VBoxDrv: host_vmxoff -> vmx_use_count=0
May  8 23:04:48 ming kernel[0]: VBoxDrv: host_vmxon  -> vmx_use_count=1 rc=0
May  8 23:13:46 ming kernel[0]: VBoxDrv: host_vmxoff -> vmx_use_count=0

The vboxlog reports a lot of issues related to AHCI:

00:43:34.854982 AHCI#0P0: Cancelled task 7
00:43:34.855589 AHCI#0: Port 0 reset
00:43:50.165909 AHCI#0P0: Cancelled task 31
00:43:50.165928 AHCI#0: Port 0 reset
00:44:05.474666 AHCI#0P0: Cancelled task 31
00:44:05.474685 AHCI#0: Port 0 reset
00:44:35.781838 AHCI#0P0: Cancelled task 31
00:44:35.782117 AHCI#0: Port 0 reset
00:44:43.107712 AsyncCompletion: Task 0x00000131801a40 completed after 98 seconds
00:44:43.107728 AsyncCompletion: Task 0x00000131801ac0 completed after 98 seconds
00:44:43.107734 AsyncCompletion: Task 0x00000131801a80 completed after 98 seconds
00:44:43.108556 AsyncCompletion: Task 0x00000131801b40 completed after 98 seconds
00:44:43.108572 AsyncCompletion: Task 0x00000131801b00 completed after 98 seconds
00:44:43.108605 AsyncCompletion: Task 0x00000131801b80 completed after 98 seconds
00:44:43.148090 AHCI#0P0: Flush request was active for 98 seconds
00:44:43.148101 AHCI#0P0: Canceled flush returned rc=VINF_SUCCESS
00:44:43.148108 AsyncCompletion: Task 0x00000131801bc0 completed after 98 seconds
00:44:43.473168 AHCI#0P0: Flush request was active for 68 seconds
00:44:43.473183 AHCI#0P0: Canceled flush returned rc=VINF_SUCCESS
00:44:44.688476 AHCI#0P0: Flush request was active for 54 seconds
00:44:44.688495 AHCI#0P0: Canceled flush returned rc=VINF_SUCCESS
00:44:44.688838 AHCI#0P0: Flush request was active for 38 seconds
00:44:44.688850 AHCI#0P0: Canceled flush returned rc=VINF_SUCCESS

Since this is reporting the problem is with sda and not sdb, I don't think it's the physical external drive causing the problem, it's either a guest additions bug or how AHCI is implemented in VBox and interacting with Linux.

kernel-3.15.0-0.rc4.git0.1.fc21.x86_64"	Chris Murphy
20864	If Pause is set and Pause is canceled, Audio will not be output.	VirtualBox 6.1.32	2022-03-10T07:39:12Z	2022-03-10T07:39:12Z	2022-03-10T07:39:12Z	"If the guest OS is Windows XP and VirtualBox is set to Pause and Pause is canceled, Audio will not be output.
Thank you."	aokadak@…
729	If you delete an iso image,you can't remove it from the list	VirtualBox 1.5.0	2007-09-29T19:29:32Z	2019-02-14T19:17:46Z	2019-02-14T19:17:46Z	"If you delete an iso image,you can't remove it from the list of ""Virtual Disk Manager"" and, of course it refuses to start if he can't find the file.I trivially bipased it,by simply recreating an empty file of the same name,and only then i could remove it from the list and i just realized,that i forgot to delete it.

So,the request is that you should be able to remove a file from the list,even if he can't find it,maybe with an extra warning or something.I suppose that preventing it from starting it's a feature.

On, Linux,Ubuntu 32bits feisty."	michel
18360	iMac (mojave 10.14.2) repeated panic crashes	VirtualBox 6.0.2	2019-01-25T07:23:23Z	2019-01-26T08:01:33Z	2019-01-26T08:01:33Z	I am running 2 ubuntu desktop 18.04 machines, 2 kali linux ova's, and a VyOS distrubution. When all five are up and running everything is smooth until it randomly crashes. This usually happens in less than 5 minutes or so. I've looked for 3rd party extensions that may not be working well with VB but I can't seem to find anything that might be causing it. If someone else could take a look and maybe tell me what I'm looking at.	cjc955
17661	iMac High Sierra - host kernel panic when adding load to guest	VirtualBox 5.2.8	2018-04-03T09:50:43Z	2018-04-03T09:50:43Z	2018-04-03T09:50:43Z	"Steps to reproduce: Create a simple Virtualbox with vagrant:

{{{
Vagrant.configure(""2"") do |config|
  config.vm.box = ""bento/ubuntu-16.04""
  config.ssh.forward_agent = true
  config.vm.network :private_network, ip: ""192.168.91.21""
  config.vm.provider ""virtualbox"" do |v|
    v.name = ""maschinenring test""
    v.customize [""modifyvm"", :id, ""--memory"", ""4096""]
  end
end
}}}

ssh into it and install the stressapptest

{{{
sudo apt-get install stressapptest
}}}

Runn the stressapptest with

{{{
stressapptest -s 9000 -m 8 -C 8 -W --findfiles -i 2 -M 4500
}}}

Wait for one to two hours untill the host system rects with a cernel panic. I have also attached three panic reports. For me they it looks like the vm just create some random errors in the kernel memory space. I reproduced this bug on three iMacs. All software was up to date , the iMacs do not crash in normal usage or with load testing on the host system.

I haven't seen this happening before the upgrade from Sierra to High Sierra.

Softweare Versions:
* High Sierra version: 10.13.3 (17D102)
* Virtualbox: 5.2.8
* Vagrant: 2.0.3

As the test Version of Virtualbox on https://www.virtualbox.org/wiki/Testbuilds is linking to https://www.virtualbox.org/download/testcase/VirtualBox-5.2.9-121224-OSX.dmg and this gives me a 404 I was not able to test it with the latest Test version release.

It looks like this Problem is spcific to the iMac as I was not able to reproduce it on MacBooks.

Some data from my Host OS:
{{{
Hardware-Übersicht:

  Modellname:	iMac
  Modell-Identifizierung:	iMac14,2
  Prozessortyp:	Intel Core i5
  Prozessorgeschwindigkeit:	3,2 GHz
  Anzahl der Prozessoren:	1
  Gesamtanzahl der Kerne:	4
  L2-Cache (pro Kern):	256 KB
  L3-Cache:	6 MB
  Speicher:	16 GB
  Boot-ROM-Version:	IM142.0123.B00
  SMC-Version (System):	2.15f7
  Seriennummer (System):	DGKLQ07LF8J9
  Hardware-UUID:	4328169B-16AA-518C-B249-7CDD6179774A
}}}
"	codekunst
15163	iMac running 10.11.3 reboots everytime a VB image is started (host_vmxon)	VirtualBox 5.0.14	2016-02-20T22:59:01Z	2016-04-29T08:53:27Z	2016-04-29T08:53:27Z	After upgrading to the 5.0.14 version of VirtualBox, every time I attempt to launch an existing VB image, or create a new image and start that, the host machine reboots. 	Scott M Stark
17893	Image doesn't start under Windows 10	VirtualBox 5.2.16	2018-07-27T00:23:47Z	2018-07-29T08:33:03Z	2018-07-29T08:33:03Z	"I try to create a virtual box under Windows 10. I tried multiple OSs and also VirtualBox 5.1.38. I always get the following error code when I try to start the newly generated image:

Failed to open a session for the virtual machine UbuntuDon.

The virtual machine 'UbuntuDon' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005).  More details may be available in 'C:\Users\do991164\VirtualBox VMs\UbuntuDon\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}

"	Don83
15915	Image removed by snapshot restore still shown as attached in media manager	VirtualBox 5.1.4	2016-09-10T10:14:16Z	2016-09-23T19:04:43Z	2016-09-23T19:04:43Z	"Longstanding bug:

Steps to reproduce:
* select a VM with an empty virtual optical drive,
* create a snapshot of this VM,
* attach some new ISO image to the optical drive,
* restore the snapshot (do not create one for current state),
* check ""Attached to"" status of ISO image in virtual media manager.

Observed:
ISO image is still reported as ""Attached to: ''Name_of_VM''"". As a consequence, ""Remove"" button is disabled.

Expected:
ISO image should be reported as ""''Not Attached''"".

Workaround:
Re-add ISO image, and then remove it manually before restoring the snapshot.
"	chrfranke
19293	IMedium::getEncryptionSettings() variables are backwards when called via web service	VirtualBox 6.1.0	2020-02-06T05:39:08Z	2020-02-06T05:39:08Z	2020-02-06T05:39:08Z	"To start: this is a very minor issue and is really just for your awareness. SDKRef for API v6.1.0 page 268 shows IMedium::getEncryptionSettings() taking a variable reference for the cipher and returning the disk ID. When calling this method using the web service, however, it takes a variable reference for the disk ID and returns the cipher. I've confirmed the documentation matches the method when using the VirtualBox.VirtualBox COM object. I would imagine this needs to be changed in the WSDL and VBoxWebSrv. For now, I've simply reversed my variables and it works. My VirtualBox version is 6.1.0 and I'm using the 6.1.0 SDK via PowerShell on a Windows 7 host.

I'm creating the web service proxy in PowerShell using ""$global:vbox = New-WebServiceProxy -Uri ""$($env:VBOX_MSI_INSTALL_PATH)sdk\bindings\webservice\vboxwebService.wsdl"" -Namespace ""VirtualBox"" -Class ""VirtualBoxWebSrv"""". My call to getEncryptionSettings() as it works right now is ""$cipher = $global:vbox.IMedium_getEncryptionSettings($disk.Id, [ref]$diskid)"". $disk.Id is the web service reference ID string to that specific IMedium so is unimportant to this.

I'm creating the vbox COM object using ""$global:vbox = New-Object -ComObject VirtualBox.VirtualBox"". When calling getEncryptionSettings() from the COM, my call can be correct to the SDKRef like this: ""$diskid = $global:vbox.HardDisks[$disk.Id].getEncryptionSettings([string]@([ref]$cipher))"". $disk.Id here is the array index to that specific IMedium so is unimportant to this."	SmithersTheOracle
19258	import of freshly exported appliance fails	VirtualBox 6.1.2	2020-01-22T19:24:02Z	2020-01-22T19:24:02Z	2020-01-22T19:24:02Z	"i am migrating from one host to another.
on OLD machine, I export using standard/default settings in 6.0 (Mac OS 10.15)
i transfer to NEW machine via usb-Disk
i call import with default settings.
a popup appears declaring that appliance <somename>.ova could not be imported. Error Code  NS_ERROR_INVALID_ARG (0x80070057)

There seems to be a size dependency:
i was able to import one appliance with size 5,62GB, several others larger than 10GB all fail.

There is of course no space problem on the NEW machine, there are more than 500GB free.
FWIW, i detect nothing of interest in the system logs.

 "	MatsWolpers
20083	Import VM buttons below screen sized 1280x800	VirtualBox 6.1.16	2020-12-07T11:47:28Z	2020-12-07T11:47:28Z	2020-12-07T11:47:28Z	I'm trying to import a VM to an old MBP with screen size 1280x800. But the pull down has buttons below the screen. 	TimeRider
19700	Impossible d'installer le systeme de base	VirtualBox 6.1.10	2020-07-03T19:54:36Z	2020-07-03T20:17:57Z	2020-07-03T20:17:57Z	Je tente de créer une machine virtuelle sous Kali Linux depuis quelques semaines,A chaque tentative un message d'erreur s'Affiche disant: une erreur s'est produite lors de l'installation du noyau vers le système cible. 	Violon
19770	impossible to start restored machine	VirtualBox 6.1.10	2020-07-26T14:42:02Z	2020-07-26T14:42:02Z	2020-07-26T14:42:02Z	"Für die virtuelle Maschine Windoof konnte keine neue Sitzung eröffnet werden.

Failed to load unit 'vga' (VERR_SSM_LOADED_TOO_MUCH).

Fehlercode: NS_ERROR_FAILURE (0x80004005)
Komponente: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

running windows 10
Host:
Mac book 
10.15.5 (19F101) Catalina
Intel Iris 1536 MB"	blutigeranfaenger
9791	Improved support for Ubuntu Unity	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
9195	In machine list details view, show actual size of attached VDIs	VirtualBox 4.0.10	2011-07-12T18:17:24Z	2011-07-12T18:17:24Z	2011-07-12T18:17:24Z	"Suggestion: 
In the main window, in the details panel, in the Storage section: show the on-disk (actual) size of each vdi as well as the virtual size.

e.g. '''IDE Primary Master: abc.vdi (Normal, 160.00GB)''' 
might become '''IDE Primary Master: abc.vdi (Normal, 160.00GB, 22.87GB)'''

This would save having to open the virtual media manager and scroll through to find each vdi.

(This applies to all host types and guest types.)"	Joe
20443	In macOS Catalina, a virtual machine crashes when it loses focus.	VirtualBox 6.1.22	2021-07-01T12:18:05Z	2021-07-01T12:18:05Z	2021-07-01T12:18:05Z	"I am using macOS Catalina 10.15.7 and running a virtual Windows XP on it. If you switch to another application or to the main VirtualBox window, the virtual machine crashes, but not every time, but with some probability. This opens a form for writing a report about the problem. The main VirtualBox window remains open and indicates that the status of the virtual machine: ""Aborted"". This problem has been around for a very long time. Probably more than a year. And since it is not going anywhere , I decided to report it."	dik
20646	In the machine settings page system->acceleration hardware virtualization check box not responding.	VirtualBox 6.1.28	2021-10-29T15:29:36Z	2021-10-29T19:20:57Z	2021-10-29T19:20:57Z	For a virtual machine settings, a invalid setting is indicating on the system -> acceleration page , suggested that the hardware acceleration should be off. After uncheck it the OK button is not enabled , not able to save the configurations.	subhajit
20033	In Windows 10 Host with Hyper-V, setting processor to 2 CPU, installation of Windows 2004 guest stuck at Windows logo	VirtualBox 6.1.16	2020-11-12T04:48:06Z	2020-12-01T13:34:33Z	2020-12-01T13:34:33Z	"In Windows 10 Host (Windows 10 Home 20H2 and Windows 10 Home 2004), when setting processor to 2 CPU, installation of Windows 10 2004 guest stuck at Windows logo.

I have Hyper-V enabled, because I need to use WSL2 (which requires Hyper-V) and docker desktop (which requires WSL2).

Default processor is set to 1 CPU, Installation of Windows 2004 guest succeeded under 1 CPU, but it won't work with 2 CPU.

I have tested it in MacBook Pro 2020 Bootcamp and a Lenovo desktop PC, same results."	liuzhiyuan1225
19544	Inability to run 6.0-6.1.7 upgrading to 6.1.6	VirtualBox 6.1.6	2020-05-01T01:31:45Z	2020-05-01T01:31:45Z	2020-05-01T01:31:45Z	"After upgrading recently I am unable to launch vbox. The following error occurs on 6.1.6 and 6.1.7 (test). I tried rolling back versions and can successfully run 5.2.40 and lower. As soon as I cross  into 6.0+ the error occurs. The VBoxSDS doesn't seem to want to run and no files are written to the .VirtualBox directory on 6.0+. I did have 6.1.x installed and running before upgrading to 6.1.6 but I do not remember which version specifically. 


'''Failed to acquire the VirtualBox COM object.'''

The application will now terminate.

Completely failed to instantiate CLSID_VirtualBox: ERROR_SERVICE_REQUEST_TIMEOUT 0x8007041D.

Result Code: ERROR_SERVICE_REQUEST_TIMEOUT 0x8007041D (0x8007041D)
Component: VirtualBoxClientWrap
Interface: IVirtualBoxClient {d2937a8e-cb8d-4382-90ba-b7da78a74573}


I have tried:
1. Admin rights
2. Removing .VirtualBox directory
3. Cleaning registry
4. Comparability modes: Admin and older windows versions
5. Recover .VirtualBox files from backup
6. Update and verify all drivers
7. Remove all antivirus including defender
8. Hyper-V and VMware can run and have been removed
9. Extend service timeout length despite this being an immediate failure
10. Run bug report: WARNING: Failed to create the VirtualBox object (hr=0x8007041d)


Can provide bug report info if needed."	IamUSER
16981	Inaccessible Virtual Machines	VirtualBox 5.1.22	2017-08-04T20:12:21Z	2017-08-05T04:05:58Z	2017-08-05T04:05:58Z	"Hi, I have VirtualBox 5.1.22r115126 installed in my C drive. 
I set the Default Machine folder as: X:\Portable Installations\VirtualBox Saved Files. I store my VMs in my X Drive so that I don't lose my VMs when restoring a C drive backup with Macrium Reflect.

I recently restored a Macrium Reflect C Drive backup. Everything was fine and all my VMs were working. These are my VMs:

""Windows 7 64-bit New Install (Nothing Changed)"". As the name suggests this has Windows installed with nothing else on it.
""Windows 7 64-bit - Opera Portable"". This is a linked clone of the above which I then have Opera Portable on.

I had the linked clone running today and I saved a snapshot. I closed VirtualBox and restarted my PC. When I opened VirtualBox, both VMs are ""inaccessible"". It says a differencing image of snapshot ""snapshot name here"" could not be found. Could not find an open hard disk with UUID ""name here"".

How can I find out what caused the problem and how can I fix it?
Is there any reason why I can't have VMs on my X Drive but VirtualBox installed on the C Drive?
"	DaveyMames
17005	Inaccurate Translation to Chinese	VirtualBox 5.1.26	2017-08-12T07:18:07Z	2017-08-12T08:06:21Z	2017-08-12T08:06:21Z	"The label ""Name"" in the ""Network"" of ""Settings"" could be translated into ""接口名称""(""Interface Name"") rather than ""界面名称""."	kx_sun
15273	Inconsistent state of attached disks, cannot close medium	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
18648	Incorrect and unhelpful log reporting of VERR_PDM_DEVINS_UNKNOWN_CFG_VALUES details	VirtualBox 6.0.8	2019-05-15T20:42:03Z	2019-05-15T20:42:03Z	2019-05-15T20:42:03Z	"I set a bunch of EFI  ""Bios Dmi Information"" Key/Value pairs for a Windows 10 Guest on a(n arch) Linux host. I doubt very much that particular details of  VirtualBox, Host or Guest matter for what happened; but if they do, surely they are in the attached Log. When I started up the VM, the result was an abortion + pop-up as follows:

Configuration error: Invalid config value(s) for the EFI device (VERR_PDM_DEVINS_UNKNOWN_CFG_VALUES).
Result Code: 
NS_ERROR_FAILURE (0x80004005)
Component: 
ConsoleWrap
Interface: 
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

Clear Enough. But when I looked at the Log to see my error, the relevant line (line 663 in the attached log) was:´

00:00:00.993661 PDM: Failed to construct 'efi'/0! VERR_PDM_DEVINS_UNKNOWN_CFG_VALUES (-2801) - A device encountered an unknown configuration value. This means that the device is potentially misconfigured and the device construction or unit attachment failed because of this.

It was not possible to determine from this which assignment contained the error or why. Comparing strings for minute errors is extremely tedious and error-prone, **especiallly** when the were no obvious typos in any of the strings I had set. 

Eventually I realized that the problem was simply that I had set an entirely non-existent Bios Parameter. The mistaken command was

VBoxManage  setextradata ""Win10 raw""  ""VBoxInternal/Devices/efi/0/Config/DmiSystemBiosVersion""    ""DELL   - 1072009 1.7.0 American Megatrends - 500""

and I now see that there is no such key in the documentation. so entering 

VBoxManage  setextradata ""Win10 raw""  ""VBoxInternal/Devices/efi/0/Config/DmiSystemBiosVersion""  

unset the key and enabled my VM to start -- but that took me an exhausting 45 minutes, when it could/should have taken me a trivial 2-3 minutes. I understand that it is ""feature request"" to ask that the log file contain information that it doesn't contain today. It is also a feature request to ask that there be an error returned already from a ""setextradata"" request which is 100% certain to cause a failure at VM Runtime. But it is a Buig Report to state that the log contains information which is misleading  and unhelpful:  I doubt that ""PDM failed to construct 'efi'/o! "" (which is what the log reports), and even if it did, it's not useful or relevant to the reader of the log. And it also wasn't a an unknown configuration value that was the problem, it was an unknown NAME of a Dmi Information key that was the problem. And since the code knew that the particular name it didn know was DmiSystemBiosInformation, it could and should have shared this information with the user. 

Please at least remove the misinformation from the log ; but I hope you will also consider REPLACING that  with the actual offending key or value, as a welcome time-saver to the user. 

Please note that I filed this under ""other"" as the component.  There is no component of either ""Log"" or ""Configuration"". I thought to file it under ""EFI"", but i am sure that it applies to BIOS VMs as well.

With thanks,
scott

"	sbpetrack
19474	Incorrect checksum for freed object	VirtualBox 6.1.4	2020-04-09T17:09:53Z	2020-04-09T17:09:53Z	2020-04-09T17:09:53Z	Version 6.1.4 on Mac OS X 10.14.6 host with x64 Linux guest periodically causes the guest to summarily abort with the message Incorrect checksum for freed object.  Crash log will be attached.	mauricev
21274	Incorrect font size use sticks after virtualbox window is moved to the second display	VirtualBox-7.0.2	2022-11-15T12:44:41Z	2022-11-15T12:44:41Z	2022-11-15T12:44:41Z	"Host Windows 10 PRO
[[BR]]
VirtualBox 7.0.2[[BR]]
Guest: Debian GNU/Linux [[BR]]
uname -a[[BR]]
Linux ip030 6.0.0-2-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.0.5-1 (2022-10-28) x86_64 GNU/Linux[[BR]]

I have two monitors attached to the PC.
[[BR]]

I have experienced a very annoying font size problem.

When the VirtualBox window is moved to the second display,
virtualbox suddenly causes the guest linux to use very large font.[[BR]]

The problem is that even after I move the virtual box window back to the original 1st display, the large font size is still used and it is really unusable after this happens.
I think the change of font size on the 2nd display may be related to the
different display resolution and used font size (there is an multiplication factor I set using individual config of the display, etc. I am using the Japanese Window and so I don't know the menu names for these settings in English.)


The only reference related such a font size issue I can find is the comment in 
comment 3 of ticket Ticket #20282.
{{{
but it uses a wrong font size if it is on the 2nd screen. 
}}}

Please note that strange font size usage when the program window is moved from the 1st window to the 2nd window is observed for many applications.
MS EXCEL, MS WORD, Thunderbird mail client to name a few, especially only half the window is shifted to the 2nd window.
However, many programs resume to use the right font size once the program window is reverted to the 1st window, or completely moved to the 2nd window.

VirtualBox is the only program that keeps on using strangely large font size even if I move the window back to the original. And for that matter, it keeps on using the strangely large font and it becomes unusable for my purpose.
Once VBox is retarted, the problem goes away, but it is very undesirable.

I will attach screen captures to explain the problem, but I am not sure if I can get the screen dump when the VBox window is split between the two windows.
I will take a photo in that case.
 

"	ci-zephyurus
19417	incorrect power off handling with background vms	VirtualBox 6.1.4	2020-03-20T16:26:32Z	2020-03-20T16:26:32Z	2020-03-20T16:26:32Z	"if I have a background machine running and try to log out or poweroff without closing it, I have standard windows dialog about that the virtualbox don't let to shutdown.
vm powers off automaticly, but the VBoxSvc process stays running and don't let to shutdown.
when I kill it system shuts down normally."	ilyapashuk
15353	Incorrect quoting in balloon control startup script	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
17975	Input Capture Fails	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
19813	Instalation Windows2019	VirtualBox 6.1.10	2020-08-14T15:03:20Z	2020-08-14T15:52:02Z	2020-08-14T15:52:02Z	"When I try to install Windows2019 I get Error

Versión 6.1.12.r

The host is Windows 2008R2 Server 64 bits"	LluisG
20045	Install Debian not run	VirtualBox 6.1.14	2020-11-17T08:18:35Z	2020-11-17T08:18:35Z	2020-11-17T08:18:35Z	Installation of Debian will not run with VirtualBox 6.1.14r140239	christophedlr34
18256	Install failure for VB6.0.0 on openSUSE Tumbleweed	VirtualBox 6.0.0	2018-12-31T17:35:43Z	2018-12-31T17:35:43Z	2018-12-31T17:35:43Z	I expected that the binary for openSUSE Leap 15.0 would work with Tumbleweed, but installation with zypper fails because nothing provides libvpx.so.4()(64bit). This is due to Tumbleweed being supplied with libvpx.so.5 as the default.	Larry998
20501	Installation start crash of Win10 guest on Win7 host.	VirtualBox 6.1.26	2021-08-14T14:45:34Z	2021-08-14T14:45:34Z	2021-08-14T14:45:34Z	"Machine: LENOVO W701 with Win7 ultimate host OS. 
Win10 Iso image is open in BD-ROM virtual DVD drive. After configuration of the VM for Win10 guest OS clicking start. The VM starts running in VB 6.1.26 and the Win10 screen appears with blue window in mids the black screen. Roughly 10 seconds later an error message appears reporting the fatal error crash.
The log file does not make my sly. Anyone an idea what has happened?
A Win7 guest installation on this system works fine."	drghl
17754	Installation without disabling secureboot	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
17201	Installing 5.2 Extension pack disables the VB Shared Folders	VirtualBox 5.1.30	2017-10-22T21:55:51Z	2017-10-25T04:35:06Z	2017-10-25T04:35:06Z	"After upgrading to VB 5.2, all guests lost access to their shared folders (\\VBOXSVR\)defined under VB Machine Settings.  The shares are correctly defined and were working immediately prior to installing the VB 5.2 Extension Pack.

64 Bit Linux host various Windows clients."	Don Hughes
20549	installing virtual box on Linux  5.10.0-kali9-amd64	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
20343	instruction 0x00007FFD15769B2C	VirtualBox 6.1.22	2021-05-07T22:14:50Z	2021-05-07T22:14:50Z	2021-05-07T22:14:50Z	"Hello everybody

I am new with Virtualbox. I have downloaded the latest version of virtualBox and install and configure the latest lubuntu but finally when I exit of lubuntu an error message appears ""The instruction 0x00007FFD15769B2C do reference to the memory in 0windows and updatx00007FFD15769B2C. The memory can not written""
I have the latest windows version and also I updated all actualizations, but the error apperas again.
I have an hp laptop i7 11 generation with windows 10 home, i have the virtualization enabled but the problem continues

Van somebody help me with this error?

Best reagrds
Jose

  "	yuse
17016	instruction referenced at 0xe6826d43 referenced memory at 0x00000018 could not be read	VirtualBox 5.1.26	2017-08-15T16:12:23Z	2017-08-15T16:47:38Z	2017-08-15T16:47:38Z	"windows7 host ubuntu 16.04 guest
moved the vm from a win7 notebook to a win7 workstation
a repeatable crash during vm startup, various instruction address

apparently solved the issue by changing chipset type from PIIX3 to ICH9, all other changes to vm settings had no effect

"	devotip
5252	Intel vt-d/AMD IOMMU support	VirtualBox 3.0.8	2009-10-19T07:29:51Z	2012-05-20T13:58:21Z	2012-05-20T13:58:21Z	"I want to use the pci-e inside the guest os to accelerate the directx and opengl but virtualbox still not support it
and I found that intel vt-d can use the host pci-e in parallel workstatio 4.0 

Hope to support this in future version."	vizio
18209	Intel(R) Xeon(R) W-2102 is not recognized by VirtualBox	VirtualBox 6.0.0	2018-12-20T11:22:46Z	2018-12-20T11:25:32Z	2018-12-20T11:25:32Z	"Intel(R) Xeon(R) W-2102 is not recognized by VirtualBox, and it does not report to guest system that this CPU supports AVX512 instruction sets. I tried to modify CPUID data for guest, but after doing so Linux guest was not able to boot, so looks that some extra support on VBox side it needed too.

VBoxManage.exe list hostcpuids
Host CPUIDs:

Leaf no.  EAX      EBX      ECX      EDX
00000000  00000016 756e6547 6c65746e 49656e69
00000001  00050654 04100800 7ffefbff bfebfbff
00000002  76036301 00f0b6ff 00000000 00c30000
00000003  00000000 00000000 00000000 00000000
00000004  1c004121 01c0003f 0000003f 00000000
00000005  00000040 00000040 00000003 00002020
00000006  00000ef5 00000002 00000009 00000000
00000007  00000000 d39ffffb 00000000 9c000000
00000008  00000000 00000000 00000000 00000000
00000009  00000000 00000000 00000000 00000000
0000000a  07300804 00000000 00000000 00000603
0000000b  00000001 00000001 00000100 00000004
0000000c  00000000 00000000 00000000 00000000
0000000d  000000ff 00000a80 00000a80 00000000
0000000e  00000000 00000000 00000000 00000000
0000000f  00000000 0000002f 00000000 00000002
00000010  00000000 0000000a 00000000 00000000
00000011  00000000 00000000 00000000 00000000
00000012  00000000 00000000 00000000 00000000
00000013  00000000 00000000 00000000 00000000
00000014  00000001 0000000f 00000007 00000000
00000015  00000002 000000f2 00000000 00000000
00000016  00000b54 00000b54 00000064 00000000
00000017  00000b54 00000b54 00000064 00000000
80000000  80000008 00000000 00000000 00000000
80000001  00000000 00000000 00000121 2c100800
80000002  65746e49 2952286c 6f655820 2952286e
80000003  322d5720 20323031 20555043 2e322040
80000004  48473039 0000007a 00000000 00000000
80000005  00000000 00000000 00000000 00000000
80000006  00000000 00000000 01006040 00000000
80000007  00000000 00000000 00000000 00000100
80000008  0000302e 00000000 00000000 00000000
80000009  00000b54 00000b54 00000064 00000000"	SirZooro
15408	Interaction between VboxManage and Node.JS	VirtualBox 5.0.20	2016-05-11T11:25:35Z	2016-05-11T11:25:35Z	2016-05-11T11:25:35Z	"There is an interaction between VB and Node.JS that makes ""VboxManage guestcontrol run"" hang in v5.0.20 where version 4.x did not. Apparently it is possible for VBoxManage to be robust to this because it worked in version 4.

To reproduce, 
- install Node.JS v5.9 on a Windows 7 guest.
- create a file C:\test.js with just the content:
console.log('hi');
- create a .bat file with the following content (yes it needs to be two calls):
C:\Program Files\nodejs\node.exe C:\test.js
C:\Program Files\nodejs\node.exe C:\test.js

- Run the .bat file on the guest, you will see that it terminates.

- Now run the .bat file from the host with ""VboxManage guestcontrol run"".  It hangs. 

- Now run the same command with --no-wait-stdout and --no-wait-stderr. Both VBoxManage and also the process on the guest terminate.

This is almost certainly something that isn't OK in Node.JS. However apparently it is possible for VBoxManage to be robust to this. It has something to do with stdout/stderr not closing for some reason.




"	rogierschouten
20802	Interface Bug macOS Monterey and VirtualBOX 6.1.32 r149290	VirtualBox 6.1.32	2022-02-01T01:44:03Z	2022-02-01T08:12:35Z	2022-02-01T08:12:35Z	"Hi,

I use macOS Monterey and VirtualBOX 6.1.32 r149290 (Qt5.6.3).

This is a simple design bug only.

On preferences, when click first time in options (General, Input, Update, etc) are OK.
When second click the combobox reduce the size and its not good.

All options in Preferences occur the same bug design."	geraldotdsjr
16792	Internal network no connectiion between VM's on Windows10 host	VirtualBox 5.1.22	2017-05-27T15:08:23Z	2017-05-27T19:14:33Z	2017-05-27T19:14:33Z	"I'made 2 VM's both with an WS2012R2.
Connect the network both on Intern netwerk with the name intnet
Switched from both the firewall off.

Adresses

SERVER A
IP adress 10.0.0.10
Subnet mask 255.255.255.0
Default gateway 10.0.0.1

DNS blank

SERVER B
IP adress 10.0.0.12
Subnet mask 255.255.255.0
Default gateway 10.0.0.1

DNS blank

Can ping the machine itself correctly

Problem is 
On the command line prompt using the ping command it gives unreachble 4 time's on both sides."	Fanatic11
20688	invalid destination port	VirtualBox 6.1.30	2021-11-24T16:38:05Z	2021-11-24T16:38:05Z	2021-11-24T16:38:05Z	"On quitting a Linux guest, I got this problem report from Monterery..

-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Process:               VirtualBoxVM [983]
Path:                  /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM
Identifier:            org.virtualbox.app.VirtualBoxVM
Version:               6.1.30 (6.1.30)
Code Type:             X86-64 (Native)
Parent Process:        VBoxSVC [945]
Responsible:           VirtualBox [941]
User ID:               502

Date/Time:             2021-11-24 11:33:23.4080 -0500
OS Version:            macOS 12.0.1 (21A559)
Report Version:        12
Anonymous UUID:        D29E8D31-4B9E-1252-579C-6F6F7174505F


Time Awake Since Boot: 39000 seconds

System Integrity Protection: disabled

Notes:
thread_get_state(PAGEIN) returned 0x10000003: (ipc/send) invalid destination port
thread_get_state(EXCEPTION) returned 0x10000003: (ipc/send) invalid destination port
thread_get_state(FLAVOR) returned 0x10000003: (ipc/send) invalid destination port

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x000002c40000000c
Exception Codes:       0x0000000000000001, 0x000002c40000000c
Exception Note:        EXC_CORPSE_NOTIFY

Termination Reason:    Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process:   exc handler [983]

VM Region Info: 0x2c40000000c is not in any region.  Bytes after previous region: 3034110459917  Bytes before following region: 102512279420916
      REGION TYPE                    START - END         [ VSIZE] PRT/MAX SHRMOD  REGION DETAIL
      CoreServices                190e88000-190ec8000    [  256K] rw-/rwx SM=COW  
--->  GAP OF 0x5ffe6f138000 BYTES
      MALLOC_NANO              600000000000-600008000000 [128.0M] rw-/rwx SM=PRV  

Error Formulating Crash Report:
thread_get_state(PAGEIN) returned 0x10000003: (ipc/send) invalid destination port
thread_get_state(EXCEPTION) returned 0x10000003: (ipc/send) invalid destination port
thread_get_state(FLAVOR) returned 0x10000003: (ipc/send) invalid destination port

Thread 0 Crashed::  Dispatch queue: com.apple.main-thread
0   IOKit                         	    0x7ff81e78fae0 IOHIDDeviceCopyMatchingElements + 34
1   UICommon.dylib                	       0x10555efa8 0x10522c000 + 3354536
2   UICommon.dylib                	       0x10555ee4e DarwinHidDevicesApplyAndReleaseLedsState + 590
3   VirtualBoxVM.dylib            	       0x100581e92 0x100553000 + 192146
4   VirtualBoxVM.dylib            	       0x1005815ff 0x100553000 + 189951
5   VirtualBoxVM.dylib            	       0x100581575 0x100553000 + 189813
6   QtCoreVBox                    	       0x1018d943b QMetaObject::activate(QObject*, int, int, void**) + 2075
7   QtCoreVBox                    	       0x1018a5b76 QCoreApplication::exec() + 390
8   VirtualBoxVM.dylib            	       0x10055a42e TrustedMain + 1502
9   VirtualBoxVM                  	       0x10027ef01 0x10027b000 + 16129
10  dyld                          	       0x10bd144fe start + 462

Thread 1:: nspr-1
0   libsystem_kernel.dylib        	    0x7ff81be58e4a __select + 10
1   VBoxXPCOM.dylib               	       0x1009198a0 0x10088f000 + 567456
2   VBoxXPCOM.dylib               	       0x10091b6e5 PR_Poll + 1061
3   VBoxXPCOMIPCC.dylib           	       0x101623e75 0x101611000 + 77429
4   VBoxXPCOM.dylib               	       0x100920a96 0x10088f000 + 596630
5   VBoxRT.dylib                  	       0x100b365ac 0x100a47000 + 980396
6   VBoxRT.dylib                  	       0x100bf1ecc 0x100a47000 + 1748684
7   libsystem_pthread.dylib       	    0x7ff81be8d514 _pthread_start + 125
8   libsystem_pthread.dylib       	    0x7ff81be8902f thread_start + 15

Thread 2:: nspr-2
0   libsystem_kernel.dylib        	    0x7ff81be53506 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	    0x7ff81be8da89 _pthread_cond_wait + 1224
2   VBoxXPCOM.dylib               	       0x10091edfe PR_WaitCondVar + 254
3   VBoxXPCOM.dylib               	       0x10091f2ad PR_Wait + 61
4   VBoxXPCOMIPCC.dylib           	       0x10161c7b8 0x101611000 + 47032
5   VBoxXPCOM.dylib               	       0x1008f31f9 0x10088f000 + 410105
6   VBoxXPCOM.dylib               	       0x100920a96 0x10088f000 + 596630
7   VBoxRT.dylib                  	       0x100b365ac 0x100a47000 + 980396
8   VBoxRT.dylib                  	       0x100bf1ecc 0x100a47000 + 1748684
9   libsystem_pthread.dylib       	    0x7ff81be8d514 _pthread_start + 125
10  libsystem_pthread.dylib       	    0x7ff81be8902f thread_start + 15

Thread 3:: VBoxSVCWatcher
0   libsystem_kernel.dylib        	    0x7ff81be53506 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	    0x7ff81be8da89 _pthread_cond_wait + 1224
2   VBoxRT.dylib                  	       0x100bedf3c RTSemEventWait + 364
3   VBoxC.dylib                   	       0x10ab8eda1 0x10aa95000 + 1023393
4   VBoxRT.dylib                  	       0x100b365ac 0x100a47000 + 980396
5   VBoxRT.dylib                  	       0x100bf1ecc 0x100a47000 + 1748684
6   libsystem_pthread.dylib       	    0x7ff81be8d514 _pthread_start + 125
7   libsystem_pthread.dylib       	    0x7ff81be8902f thread_start + 15

Thread 4:: UIMainEventListeningThread
0   libsystem_kernel.dylib        	    0x7ff81be53506 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	    0x7ff81be8da89 _pthread_cond_wait + 1224
2   VBoxXPCOM.dylib               	       0x10091ede7 PR_WaitCondVar + 231
3   VBoxXPCOM.dylib               	       0x10091f2ad PR_Wait + 61
4   VBoxXPCOMIPCC.dylib           	       0x10161671b 0x101611000 + 22299
5   VBoxXPCOMIPCC.dylib           	       0x1016163ed 0x101611000 + 21485
6   VBoxXPCOMIPCC.dylib           	       0x10161b039 0x101611000 + 41017
7   VBoxXPCOM.dylib               	       0x1009022ed 0x10088f000 + 471789
8   VBoxXPCOM.dylib               	       0x1009014eb 0x10088f000 + 468203
9   UICommon.dylib                	       0x1054ff642 CEventSource::GetEvent(CEventListener const&, int) + 162
10  UICommon.dylib                	       0x105312a37 0x10522c000 + 944695
11  QtCoreVBox                    	       0x1016e796b 0x1016be000 + 170347
12  libsystem_pthread.dylib       	    0x7ff81be8d514 _pthread_start + 125
13  libsystem_pthread.dylib       	    0x7ff81be8902f thread_start + 15

Thread 5:: UIMainEventListeningThread
0   libsystem_kernel.dylib        	    0x7ff81be53506 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	    0x7ff81be8da89 _pthread_cond_wait + 1224
2   VBoxRT.dylib                  	       0x100bedf3c RTSemEventWait + 364
3   VBoxC.dylib                   	       0x10aada0d0 0x10aa95000 + 282832
4   VBoxC.dylib                   	       0x10aadb2fd 0x10aa95000 + 287485
5   VBoxC.dylib                   	       0x10ac7002a 0x10aa95000 + 1945642
6   UICommon.dylib                	       0x1054ff642 CEventSource::GetEvent(CEventListener const&, int) + 162
7   UICommon.dylib                	       0x105312a37 0x10522c000 + 944695
8   QtCoreVBox                    	       0x1016e796b 0x1016be000 + 170347
9   libsystem_pthread.dylib       	    0x7ff81be8d514 _pthread_start + 125
10  libsystem_pthread.dylib       	    0x7ff81be8902f thread_start + 15

Thread 6:: UIMainEventListeningThread
0   libsystem_kernel.dylib        	    0x7ff81be53506 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	    0x7ff81be8da89 _pthread_cond_wait + 1224
2   VBoxRT.dylib                  	       0x100bedf3c RTSemEventWait + 364
3   VBoxC.dylib                   	       0x10aada0d0 0x10aa95000 + 282832
4   VBoxC.dylib                   	       0x10aadb2fd 0x10aa95000 + 287485
5   VBoxC.dylib                   	       0x10ac7002a 0x10aa95000 + 1945642
6   UICommon.dylib                	       0x1054ff642 CEventSource::GetEvent(CEventListener const&, int) + 162
7   UICommon.dylib                	       0x105312a37 0x10522c000 + 944695
8   QtCoreVBox                    	       0x1016e796b 0x1016be000 + 170347
9   libsystem_pthread.dylib       	    0x7ff81be8d514 _pthread_start + 125
10  libsystem_pthread.dylib       	    0x7ff81be8902f thread_start + 15

Thread 7:: nspr-3
0   libsystem_kernel.dylib        	    0x7ff81be53506 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	    0x7ff81be8da89 _pthread_cond_wait + 1224
2   VBoxXPCOM.dylib               	       0x10091edfe PR_WaitCondVar + 254
3   VBoxXPCOM.dylib               	       0x10091f2ad PR_Wait + 61
4   VBoxXPCOMIPCC.dylib           	       0x10161c7b8 0x101611000 + 47032
5   VBoxXPCOM.dylib               	       0x1008f31f9 0x10088f000 + 410105
6   VBoxXPCOM.dylib               	       0x100920a96 0x10088f000 + 596630
7   VBoxRT.dylib                  	       0x100b365ac 0x100a47000 + 980396
8   VBoxRT.dylib                  	       0x100bf1ecc 0x100a47000 + 1748684
9   libsystem_pthread.dylib       	    0x7ff81be8d514 _pthread_start + 125
10  libsystem_pthread.dylib       	    0x7ff81be8902f thread_start + 15

Thread 8:: nspr-4
0   libsystem_kernel.dylib        	    0x7ff81be53506 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	    0x7ff81be8da89 _pthread_cond_wait + 1224
2   VBoxXPCOM.dylib               	       0x10091edfe PR_WaitCondVar + 254
3   VBoxXPCOM.dylib               	       0x10091f2ad PR_Wait + 61
4   VBoxXPCOMIPCC.dylib           	       0x10161c7b8 0x101611000 + 47032
5   VBoxXPCOM.dylib               	       0x1008f31f9 0x10088f000 + 410105
6   VBoxXPCOM.dylib               	       0x100920a96 0x10088f000 + 596630
7   VBoxRT.dylib                  	       0x100b365ac 0x100a47000 + 980396
8   VBoxRT.dylib                  	       0x100bf1ecc 0x100a47000 + 1748684
9   libsystem_pthread.dylib       	    0x7ff81be8d514 _pthread_start + 125
10  libsystem_pthread.dylib       	    0x7ff81be8902f thread_start + 15

Thread 9:: EMT
0   libsystem_kernel.dylib        	    0x7ff81be53fda __ioctl + 10
1   libsystem_kernel.dylib        	    0x7ff81be53fc7 ioctl + 150
2   VBoxRT.dylib                  	       0x100bfc4ad 0x100a47000 + 1791149
3   VBoxRT.dylib                  	       0x100bf46e6 SUPR3CallVMMR0Ex + 438
4   VBoxVMM.dylib                 	       0x102332681 0x102285000 + 710273
5   VBoxRT.dylib                  	       0x100b365ac 0x100a47000 + 980396
6   VBoxRT.dylib                  	       0x100bf1ecc 0x100a47000 + 1748684
7   libsystem_pthread.dylib       	    0x7ff81be8d514 _pthread_start + 125
8   libsystem_pthread.dylib       	    0x7ff81be8902f thread_start + 15

Thread 10:: com.apple.NSEventThread
0   libsystem_kernel.dylib        	    0x7ff81be50aba mach_msg_trap + 10
1   libsystem_kernel.dylib        	    0x7ff81be50e2b mach_msg + 59
2   CoreFoundation                	    0x7ff81bf53d51 __CFRunLoopServiceMachPort + 319
3   CoreFoundation                	    0x7ff81bf5240f __CFRunLoopRun + 1329
4   CoreFoundation                	    0x7ff81bf51809 CFRunLoopRunSpecific + 567
5   AppKit                        	    0x7ff81ea11cec _NSEventThread + 132
6   libsystem_pthread.dylib       	    0x7ff81be8d514 _pthread_start + 125
7   libsystem_pthread.dylib       	    0x7ff81be8902f thread_start + 15

Thread 11:: AMCP Logging Spool
0   libsystem_kernel.dylib        	    0x7ff81be50af6 semaphore_wait_trap + 10
1   caulk                         	    0x7ff824d4e1c0 caulk::mach::semaphore::wait_or_error() + 16
2   caulk                         	    0x7ff824d3508a caulk::concurrent::details::worker_thread::run() + 36
3   caulk                         	    0x7ff824d34d4e void* caulk::thread_proxy<std::__1::tuple<caulk::thread::attributes, void (caulk::concurrent::details::worker_thread::*)(), std::__1::tuple<caulk::concurrent::details::worker_thread*> > >(void*) + 41
4   libsystem_pthread.dylib       	    0x7ff81be8d514 _pthread_start + 125
5   libsystem_pthread.dylib       	    0x7ff81be8902f thread_start + 15

Thread 12:
0   libsystem_pthread.dylib       	    0x7ff81be8900c start_wqthread + 0

Thread 13:: VMPwrDwn
0   libsystem_kernel.dylib        	    0x7ff81be53506 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	    0x7ff81be8da89 _pthread_cond_wait + 1224
2   VBoxRT.dylib                  	       0x100bee9c6 0x100a47000 + 1735110
3   VBoxRT.dylib                  	       0x100b36f73 0x100a47000 + 982899
4   VBoxVMM.dylib                 	       0x10232d00e 0x102285000 + 688142
5   VBoxVMM.dylib                 	       0x10232e9be VMR3Destroy + 270
6   VBoxC.dylib                   	       0x10ab02581 0x10aa95000 + 447873
7   VBoxC.dylib                   	       0x10ab285f7 0x10aa95000 + 603639
8   VBoxC.dylib                   	       0x10aae8a9c 0x10aa95000 + 342684
9   VBoxRT.dylib                  	       0x100b365ac 0x100a47000 + 980396
10  VBoxRT.dylib                  	       0x100bf1ecc 0x100a47000 + 1748684
11  libsystem_pthread.dylib       	    0x7ff81be8d514 _pthread_start + 125
12  libsystem_pthread.dylib       	    0x7ff81be8902f thread_start + 15

Thread 14:
0   libsystem_pthread.dylib       	    0x7ff81be8900c start_wqthread + 0

Thread 15:
0   libsystem_pthread.dylib       	    0x7ff81be8900c start_wqthread + 0


No thread state (register information) available

Binary Images:
    0x7ff81e751000 -     0x7ff81e806fff com.apple.framework.IOKit (2.0.2) <7d46c110-4106-3280-9031-f7e035792f22> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
       0x10522c000 -        0x1072dcfff UICommon.dylib (*) <275d65cb-226c-39b5-a840-5143c6007a6b> /Applications/VirtualBox.app/Contents/MacOS/UICommon.dylib
       0x100553000 -        0x100676fff VirtualBoxVM.dylib (*) <3a6f5a29-74ff-313c-9220-82612f2b6fc7> /Applications/VirtualBox.app/Contents/MacOS/VirtualBoxVM.dylib
       0x1016be000 -        0x101be5fff org.qt-project.QtCoreVBox (5.6) <3a7a08e0-9422-393e-bd97-fd15e751434c> /Applications/VirtualBox.app/Contents/Frameworks/QtCoreVBox.framework/Versions/5/QtCoreVBox
       0x10027b000 -        0x100282fff org.virtualbox.app.VirtualBoxVM (6.1.30) <43e613e0-b296-3de8-92e1-fbee61a51a5e> /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM
       0x10bd0f000 -        0x10bd7afff dyld (*) <1a6ae033-9438-33c0-8077-988fd885250a> /usr/lib/dyld
    0x7ff81be50000 -     0x7ff81be86fff libsystem_kernel.dylib (*) <12bd6f13-c452-35ee-9069-51befef29f1a> /usr/lib/system/libsystem_kernel.dylib
       0x10088f000 -        0x100940fff VBoxXPCOM.dylib (*) <31c4ddec-f9f5-363e-ad9f-b8881543e336> /Applications/VirtualBox.app/Contents/MacOS/VBoxXPCOM.dylib
       0x101611000 -        0x101628fff VBoxXPCOMIPCC.dylib (*) <4e46eacb-3d27-3668-8e43-a455d494d839> /Applications/VirtualBox.app/Contents/MacOS/components/VBoxXPCOMIPCC.dylib
       0x100a47000 -        0x100fb1fff VBoxRT.dylib (*) <05fa665b-b1c8-3f62-861e-1b3579be4a9a> /Applications/VirtualBox.app/Contents/MacOS/VBoxRT.dylib
    0x7ff81be87000 -     0x7ff81be92fff libsystem_pthread.dylib (*) <29a2750e-f31b-3630-8761-242a6bc3e99e> /usr/lib/system/libsystem_pthread.dylib
       0x10aa95000 -        0x10aea3fff VBoxC.dylib (*) <7a8a2b64-5299-3eda-9b9b-85eac8f2d836> /Applications/VirtualBox.app/Contents/MacOS/components/VBoxC.dylib
       0x102285000 -        0x10258cfff VBoxVMM.dylib (*) <b600b9be-060e-373f-8e33-09248dd2c4b7> /Applications/VirtualBox.app/Contents/MacOS/VBoxVMM.dylib
    0x7ff81bed4000 -     0x7ff81c3d4fff com.apple.CoreFoundation (6.9) <afcc752e-074d-340f-890c-263efd2da77f> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
    0x7ff81e865000 -     0x7ff81f6f1fff com.apple.AppKit (6.9) <dd0028a3-78e3-3a8a-a51b-ddd68123adef> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
    0x7ff824d33000 -     0x7ff824d55fff com.apple.audio.caulk (1.0) <c5042b28-9206-337f-bfb2-dc0b37dd8632> /System/Library/PrivateFrameworks/caulk.framework/Versions/A/caulk
               0x0 - 0xffffffffffffffff ??? (*) <00000000-0000-0000-0000-000000000000> ???

External Modification Summary:
  Calls made by other processes targeting this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
  Calls made by this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
  Calls made by all processes on this machine:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0

VM Region Summary:
ReadOnly portion of Libraries: Total=971.6M resident=0K(0%) swapped_out_or_unallocated=971.6M(100%)
Writable regions: Total=2.2G written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=2.2G(100%)

                                VIRTUAL   REGION 
REGION TYPE                        SIZE    COUNT (non-coalesced) 
===========                     =======  ======= 
Accelerate framework               256K        2 
Activity Tracing                   256K        1 
CG backing stores                  640K        4 
CG image                            48K        3 
CG raster data                     140K        3 
ColorSync                          224K       25 
CoreAnimation                     3892K       12 
CoreGraphics                        12K        2 
CoreServices                       304K        2 
CoreUI image data                  332K        5 
Foundation                          16K        1 
Kernel Alloc Once                    8K        1 
MALLOC                           381.5M      105 
MALLOC guard page                   48K        9 
MALLOC_MEDIUM (reserved)           1.4G       12         reserved VM address space (unallocated)
MALLOC_NANO (reserved)           384.0M        1         reserved VM address space (unallocated)
STACK GUARD                       56.1M       16 
Stack                             16.1M       16 
VM_ALLOCATE                       8312K       17 
__DATA                            35.6M      344 
__DATA_CONST                      14.2M      192 
__DATA_DIRTY                       638K      110 
__FONT_DATA                          4K        1 
__LINKEDIT                       644.7M       30 
__OBJC_RO                         81.6M        1 
__OBJC_RW                         3120K        2 
__TEXT                           326.9M      354 
__UNICODE                          588K        1 
dyld private memory               1024K        1 
mapped file                       90.2M       24 
shared memory                      808K       19 
===========                     =======  ======= 
TOTAL                              3.4G     1316 
TOTAL, minus reserved VM space     1.6G     1316 



-----------
Full Report
-----------

{""app_name"":""VirtualBoxVM"",""timestamp"":""2021-11-24 11:33:27.00 -0500"",""app_version"":""6.1.30"",""slice_uuid"":""43e613e0-b296-3de8-92e1-fbee61a51a5e"",""build_version"":""6.1.30"",""platform"":1,""bundleID"":""org.virtualbox.app.VirtualBoxVM"",""share_with_app_devs"":1,""is_first_party"":0,""bug_type"":""309"",""os_version"":""macOS 12.0.1 (21A559)"",""incident_id"":""BC924093-ADDD-4947-94C1-823F46F11168"",""name"":""VirtualBoxVM""}
{
  ""uptime"" : 39000,
  ""procLaunch"" : ""2021-11-24 00:42:47.3044 -0500"",
  ""procRole"" : ""Background"",
  ""version"" : 2,
  ""userID"" : 502,
  ""deployVersion"" : 210,
  ""modelCode"" : ""MacPro6,1"",
  ""procStartAbsTime"" : 258600882589,
  ""coalitionID"" : 788,
  ""osVersion"" : {
    ""train"" : ""macOS 12.0.1"",
    ""build"" : ""21A559"",
    ""releaseType"" : ""User""
  },
  ""captureTime"" : ""2021-11-24 11:33:23.4080 -0500"",
  ""incident"" : ""BC924093-ADDD-4947-94C1-823F46F11168"",
  ""bug_type"" : ""309"",
  ""pid"" : 983,
  ""procExitAbsTime"" : 39296637478404,
  ""cpuType"" : ""X86-64"",
  ""procName"" : ""VirtualBoxVM"",
  ""procPath"" : ""\/Applications\/VirtualBox.app\/Contents\/Resources\/VirtualBoxVM.app\/Contents\/MacOS\/VirtualBoxVM"",
  ""bundleInfo"" : {""CFBundleShortVersionString"":""6.1.30"",""CFBundleVersion"":""6.1.30"",""CFBundleIdentifier"":""org.virtualbox.app.VirtualBoxVM""},
  ""storeInfo"" : {""deviceIdentifierForVendor"":""D2CBA99F-71A3-5B29-BC09-3089D1644C8E"",""thirdParty"":true},
  ""parentProc"" : ""VBoxSVC"",
  ""parentPid"" : 945,
  ""coalitionName"" : ""org.virtualbox.app.VirtualBox"",
  ""crashReporterKey"" : ""D29E8D31-4B9E-1252-579C-6F6F7174505F"",
  ""responsiblePid"" : 941,
  ""responsibleProc"" : ""VirtualBox"",
  ""sip"" : ""disabled"",
  ""vmRegionInfo"" : ""0x2c40000000c is not in any region.  Bytes after previous region: 3034110459917  Bytes before following region: 102512279420916\n      REGION TYPE                    START - END         [ VSIZE] PRT\/MAX SHRMOD  REGION DETAIL\n      CoreServices                190e88000-190ec8000    [  256K] rw-\/rwx SM=COW  \n--->  GAP OF 0x5ffe6f138000 BYTES\n      MALLOC_NANO              600000000000-600008000000 [128.0M] rw-\/rwx SM=PRV  "",
  ""isCorpse"" : 1,
  ""exception"" : {""codes"":""0x0000000000000001, 0x000002c40000000c"",""rawCodes"":[1,3040836845580],""type"":""EXC_BAD_ACCESS"",""signal"":""SIGSEGV"",""subtype"":""KERN_INVALID_ADDRESS at 0x000002c40000000c""},
  ""termination"" : {""flags"":0,""code"":11,""namespace"":""SIGNAL"",""indicator"":""Segmentation fault: 11"",""byProc"":""exc handler"",""byPid"":983},
  ""vmregioninfo"" : ""0x2c40000000c is not in any region.  Bytes after previous region: 3034110459917  Bytes before following region: 102512279420916\n      REGION TYPE                    START - END         [ VSIZE] PRT\/MAX SHRMOD  REGION DETAIL\n      CoreServices                190e88000-190ec8000    [  256K] rw-\/rwx SM=COW  \n--->  GAP OF 0x5ffe6f138000 BYTES\n      MALLOC_NANO              600000000000-600008000000 [128.0M] rw-\/rwx SM=PRV  "",
  ""extMods"" : {""caller"":{""thread_create"":0,""thread_set_state"":0,""task_for_pid"":0},""system"":{""thread_create"":0,""thread_set_state"":0,""task_for_pid"":0},""targeted"":{""thread_create"":0,""thread_set_state"":0,""task_for_pid"":0},""warnings"":0},
  ""faultingThread"" : 0,
  ""threads"" : [{""triggered"":true,""id"":9449,""queue"":""com.apple.main-thread"",""frames"":[{""imageOffset"":256736,""symbol"":""IOHIDDeviceCopyMatchingElements"",""symbolLocation"":34,""imageIndex"":0},{""imageOffset"":3354536,""imageIndex"":1},{""imageOffset"":3354190,""symbol"":""DarwinHidDevicesApplyAndReleaseLedsState"",""symbolLocation"":590,""imageIndex"":1},{""imageOffset"":192146,""imageIndex"":2},{""imageOffset"":189951,""imageIndex"":2},{""imageOffset"":189813,""imageIndex"":2},{""imageOffset"":2208827,""symbol"":""QMetaObject::activate(QObject*, int, int, void**)"",""symbolLocation"":2075,""imageIndex"":3},{""imageOffset"":1997686,""symbol"":""QCoreApplication::exec()"",""symbolLocation"":390,""imageIndex"":3},{""imageOffset"":29742,""symbol"":""TrustedMain"",""symbolLocation"":1502,""imageIndex"":2},{""imageOffset"":16129,""imageIndex"":4},{""imageOffset"":21758,""symbol"":""start"",""symbolLocation"":462,""imageIndex"":5}]},{""id"":9456,""name"":""nspr-1"",""frames"":[{""imageOffset"":36426,""symbol"":""__select"",""symbolLocation"":10,""imageIndex"":6},{""imageOffset"":567456,""imageIndex"":7},{""imageOffset"":575205,""symbol"":""PR_Poll"",""symbolLocation"":1061,""imageIndex"":7},{""imageOffset"":77429,""imageIndex"":8},{""imageOffset"":596630,""imageIndex"":7},{""imageOffset"":980396,""imageIndex"":9},{""imageOffset"":1748684,""imageIndex"":9},{""imageOffset"":25876,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":10},{""imageOffset"":8239,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":10}]},{""id"":9457,""name"":""nspr-2"",""frames"":[{""imageOffset"":13574,""symbol"":""__psynch_cvwait"",""symbolLocation"":10,""imageIndex"":6},{""imageOffset"":27273,""symbol"":""_pthread_cond_wait"",""symbolLocation"":1224,""imageIndex"":10},{""imageOffset"":589310,""symbol"":""PR_WaitCondVar"",""symbolLocation"":254,""imageIndex"":7},{""imageOffset"":590509,""symbol"":""PR_Wait"",""symbolLocation"":61,""imageIndex"":7},{""imageOffset"":47032,""imageIndex"":8},{""imageOffset"":410105,""imageIndex"":7},{""imageOffset"":596630,""imageIndex"":7},{""imageOffset"":980396,""imageIndex"":9},{""imageOffset"":1748684,""imageIndex"":9},{""imageOffset"":25876,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":10},{""imageOffset"":8239,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":10}]},{""id"":9458,""name"":""VBoxSVCWatcher"",""frames"":[{""imageOffset"":13574,""symbol"":""__psynch_cvwait"",""symbolLocation"":10,""imageIndex"":6},{""imageOffset"":27273,""symbol"":""_pthread_cond_wait"",""symbolLocation"":1224,""imageIndex"":10},{""imageOffset"":1732412,""symbol"":""RTSemEventWait"",""symbolLocation"":364,""imageIndex"":9},{""imageOffset"":1023393,""imageIndex"":11},{""imageOffset"":980396,""imageIndex"":9},{""imageOffset"":1748684,""imageIndex"":9},{""imageOffset"":25876,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":10},{""imageOffset"":8239,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":10}]},{""id"":9459,""name"":""UIMainEventListeningThread"",""frames"":[{""imageOffset"":13574,""symbol"":""__psynch_cvwait"",""symbolLocation"":10,""imageIndex"":6},{""imageOffset"":27273,""symbol"":""_pthread_cond_wait"",""symbolLocation"":1224,""imageIndex"":10},{""imageOffset"":589287,""symbol"":""PR_WaitCondVar"",""symbolLocation"":231,""imageIndex"":7},{""imageOffset"":590509,""symbol"":""PR_Wait"",""symbolLocation"":61,""imageIndex"":7},{""imageOffset"":22299,""imageIndex"":8},{""imageOffset"":21485,""imageIndex"":8},{""imageOffset"":41017,""imageIndex"":8},{""imageOffset"":471789,""imageIndex"":7},{""imageOffset"":468203,""imageIndex"":7},{""imageOffset"":2963010,""symbol"":""CEventSource::GetEvent(CEventListener const&, int)"",""symbolLocation"":162,""imageIndex"":1},{""imageOffset"":944695,""imageIndex"":1},{""imageOffset"":170347,""imageIndex"":3},{""imageOffset"":25876,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":10},{""imageOffset"":8239,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":10}]},{""id"":9460,""name"":""UIMainEventListeningThread"",""frames"":[{""imageOffset"":13574,""symbol"":""__psynch_cvwait"",""symbolLocation"":10,""imageIndex"":6},{""imageOffset"":27273,""symbol"":""_pthread_cond_wait"",""symbolLocation"":1224,""imageIndex"":10},{""imageOffset"":1732412,""symbol"":""RTSemEventWait"",""symbolLocation"":364,""imageIndex"":9},{""imageOffset"":282832,""imageIndex"":11},{""imageOffset"":287485,""imageIndex"":11},{""imageOffset"":1945642,""imageIndex"":11},{""imageOffset"":2963010,""symbol"":""CEventSource::GetEvent(CEventListener const&, int)"",""symbolLocation"":162,""imageIndex"":1},{""imageOffset"":944695,""imageIndex"":1},{""imageOffset"":170347,""imageIndex"":3},{""imageOffset"":25876,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":10},{""imageOffset"":8239,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":10}]},{""id"":9557,""name"":""UIMainEventListeningThread"",""frames"":[{""imageOffset"":13574,""symbol"":""__psynch_cvwait"",""symbolLocation"":10,""imageIndex"":6},{""imageOffset"":27273,""symbol"":""_pthread_cond_wait"",""symbolLocation"":1224,""imageIndex"":10},{""imageOffset"":1732412,""symbol"":""RTSemEventWait"",""symbolLocation"":364,""imageIndex"":9},{""imageOffset"":282832,""imageIndex"":11},{""imageOffset"":287485,""imageIndex"":11},{""imageOffset"":1945642,""imageIndex"":11},{""imageOffset"":2963010,""symbol"":""CEventSource::GetEvent(CEventListener const&, int)"",""symbolLocation"":162,""imageIndex"":1},{""imageOffset"":944695,""imageIndex"":1},{""imageOffset"":170347,""imageIndex"":3},{""imageOffset"":25876,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":10},{""imageOffset"":8239,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":10}]},{""id"":9574,""name"":""nspr-3"",""frames"":[{""imageOffset"":13574,""symbol"":""__psynch_cvwait"",""symbolLocation"":10,""imageIndex"":6},{""imageOffset"":27273,""symbol"":""_pthread_cond_wait"",""symbolLocation"":1224,""imageIndex"":10},{""imageOffset"":589310,""symbol"":""PR_WaitCondVar"",""symbolLocation"":254,""imageIndex"":7},{""imageOffset"":590509,""symbol"":""PR_Wait"",""symbolLocation"":61,""imageIndex"":7},{""imageOffset"":47032,""imageIndex"":8},{""imageOffset"":410105,""imageIndex"":7},{""imageOffset"":596630,""imageIndex"":7},{""imageOffset"":980396,""imageIndex"":9},{""imageOffset"":1748684,""imageIndex"":9},{""imageOffset"":25876,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":10},{""imageOffset"":8239,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":10}]},{""id"":9576,""name"":""nspr-4"",""frames"":[{""imageOffset"":13574,""symbol"":""__psynch_cvwait"",""symbolLocation"":10,""imageIndex"":6},{""imageOffset"":27273,""symbol"":""_pthread_cond_wait"",""symbolLocation"":1224,""imageIndex"":10},{""imageOffset"":589310,""symbol"":""PR_WaitCondVar"",""symbolLocation"":254,""imageIndex"":7},{""imageOffset"":590509,""symbol"":""PR_Wait"",""symbolLocation"":61,""imageIndex"":7},{""imageOffset"":47032,""imageIndex"":8},{""imageOffset"":410105,""imageIndex"":7},{""imageOffset"":596630,""imageIndex"":7},{""imageOffset"":980396,""imageIndex"":9},{""imageOffset"":1748684,""imageIndex"":9},{""imageOffset"":25876,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":10},{""imageOffset"":8239,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":10}]},{""id"":9579,""name"":""EMT"",""frames"":[{""imageOffset"":16346,""symbol"":""__ioctl"",""symbolLocation"":10,""imageIndex"":6},{""imageOffset"":16327,""symbol"":""ioctl"",""symbolLocation"":150,""imageIndex"":6},{""imageOffset"":1791149,""imageIndex"":9},{""imageOffset"":1758950,""symbol"":""SUPR3CallVMMR0Ex"",""symbolLocation"":438,""imageIndex"":9},{""imageOffset"":710273,""imageIndex"":12},{""imageOffset"":980396,""imageIndex"":9},{""imageOffset"":1748684,""imageIndex"":9},{""imageOffset"":25876,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":10},{""imageOffset"":8239,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":10}]},{""id"":9582,""name"":""com.apple.NSEventThread"",""frames"":[{""imageOffset"":2746,""symbol"":""mach_msg_trap"",""symbolLocation"":10,""imageIndex"":6},{""imageOffset"":3627,""symbol"":""mach_msg"",""symbolLocation"":59,""imageIndex"":6},{""imageOffset"":523601,""symbol"":""__CFRunLoopServiceMachPort"",""symbolLocation"":319,""imageIndex"":13},{""imageOffset"":517135,""symbol"":""__CFRunLoopRun"",""symbolLocation"":1329,""imageIndex"":13},{""imageOffset"":514057,""symbol"":""CFRunLoopRunSpecific"",""symbolLocation"":567,""imageIndex"":13},{""imageOffset"":1756396,""symbol"":""_NSEventThread"",""symbolLocation"":132,""imageIndex"":14},{""imageOffset"":25876,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":10},{""imageOffset"":8239,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":10}]},{""id"":9603,""name"":""AMCP Logging Spool"",""frames"":[{""imageOffset"":2806,""symbol"":""semaphore_wait_trap"",""symbolLocation"":10,""imageIndex"":6},{""imageOffset"":111040,""symbol"":""caulk::mach::semaphore::wait_or_error()"",""symbolLocation"":16,""imageIndex"":15},{""imageOffset"":8330,""symbol"":""caulk::concurrent::details::worker_thread::run()"",""symbolLocation"":36,""imageIndex"":15},{""imageOffset"":7502,""symbol"":""void* caulk::thread_proxy<std::__1::tuple<caulk::thread::attributes, void (caulk::concurrent::details::worker_thread::*)(), std::__1::tuple<caulk::concurrent::details::worker_thread*> > >(void*)"",""symbolLocation"":41,""imageIndex"":15},{""imageOffset"":25876,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":10},{""imageOffset"":8239,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":10}]},{""id"":341041,""frames"":[{""imageOffset"":8204,""symbol"":""start_wqthread"",""symbolLocation"":0,""imageIndex"":10}]},{""id"":341261,""name"":""VMPwrDwn"",""frames"":[{""imageOffset"":13574,""symbol"":""__psynch_cvwait"",""symbolLocation"":10,""imageIndex"":6},{""imageOffset"":27273,""symbol"":""_pthread_cond_wait"",""symbolLocation"":1224,""imageIndex"":10},{""imageOffset"":1735110,""imageIndex"":9},{""imageOffset"":982899,""imageIndex"":9},{""imageOffset"":688142,""imageIndex"":12},{""imageOffset"":694718,""symbol"":""VMR3Destroy"",""symbolLocation"":270,""imageIndex"":12},{""imageOffset"":447873,""imageIndex"":11},{""imageOffset"":603639,""imageIndex"":11},{""imageOffset"":342684,""imageIndex"":11},{""imageOffset"":980396,""imageIndex"":9},{""imageOffset"":1748684,""imageIndex"":9},{""imageOffset"":25876,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":10},{""imageOffset"":8239,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":10}]},{""id"":341263,""frames"":[{""imageOffset"":8204,""symbol"":""start_wqthread"",""symbolLocation"":0,""imageIndex"":10}]},{""id"":341264,""frames"":[{""imageOffset"":8204,""symbol"":""start_wqthread"",""symbolLocation"":0,""imageIndex"":10}]}],
  ""usedImages"" : [
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 140703639605248,
    ""CFBundleShortVersionString"" : ""2.0.2"",
    ""CFBundleIdentifier"" : ""com.apple.framework.IOKit"",
    ""size"" : 745472,
    ""uuid"" : ""7d46c110-4106-3280-9031-f7e035792f22"",
    ""path"" : ""\/System\/Library\/Frameworks\/IOKit.framework\/Versions\/A\/IOKit"",
    ""name"" : ""IOKit""
  },
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 4381130752,
    ""size"" : 34279424,
    ""uuid"" : ""275d65cb-226c-39b5-a840-5143c6007a6b"",
    ""path"" : ""\/Applications\/VirtualBox.app\/Contents\/MacOS\/UICommon.dylib"",
    ""name"" : ""UICommon.dylib""
  },
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 4300550144,
    ""size"" : 1196032,
    ""uuid"" : ""3a6f5a29-74ff-313c-9220-82612f2b6fc7"",
    ""path"" : ""\/Applications\/VirtualBox.app\/Contents\/MacOS\/VirtualBoxVM.dylib"",
    ""name"" : ""VirtualBoxVM.dylib""
  },
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 4318814208,
    ""CFBundleShortVersionString"" : ""5.6"",
    ""CFBundleIdentifier"" : ""org.qt-project.QtCoreVBox"",
    ""size"" : 5406720,
    ""uuid"" : ""3a7a08e0-9422-393e-bd97-fd15e751434c"",
    ""path"" : ""\/Applications\/VirtualBox.app\/Contents\/Frameworks\/QtCoreVBox.framework\/Versions\/5\/QtCoreVBox"",
    ""name"" : ""QtCoreVBox"",
    ""CFBundleVersion"" : ""5.6.3""
  },
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 4297568256,
    ""CFBundleShortVersionString"" : ""6.1.30"",
    ""CFBundleIdentifier"" : ""org.virtualbox.app.VirtualBoxVM"",
    ""size"" : 32768,
    ""uuid"" : ""43e613e0-b296-3de8-92e1-fbee61a51a5e"",
    ""path"" : ""\/Applications\/VirtualBox.app\/Contents\/Resources\/VirtualBoxVM.app\/Contents\/MacOS\/VirtualBoxVM"",
    ""name"" : ""VirtualBoxVM"",
    ""CFBundleVersion"" : ""6.1.30""
  },
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 4493209600,
    ""size"" : 442368,
    ""uuid"" : ""1a6ae033-9438-33c0-8077-988fd885250a"",
    ""path"" : ""\/usr\/lib\/dyld"",
    ""name"" : ""dyld""
  },
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 140703596609536,
    ""size"" : 225280,
    ""uuid"" : ""12bd6f13-c452-35ee-9069-51befef29f1a"",
    ""path"" : ""\/usr\/lib\/system\/libsystem_kernel.dylib"",
    ""name"" : ""libsystem_kernel.dylib""
  },
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 4303941632,
    ""size"" : 729088,
    ""uuid"" : ""31c4ddec-f9f5-363e-ad9f-b8881543e336"",
    ""path"" : ""\/Applications\/VirtualBox.app\/Contents\/MacOS\/VBoxXPCOM.dylib"",
    ""name"" : ""VBoxXPCOM.dylib""
  },
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 4318105600,
    ""size"" : 98304,
    ""uuid"" : ""4e46eacb-3d27-3668-8e43-a455d494d839"",
    ""path"" : ""\/Applications\/VirtualBox.app\/Contents\/MacOS\/components\/VBoxXPCOMIPCC.dylib"",
    ""name"" : ""VBoxXPCOMIPCC.dylib""
  },
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 4305743872,
    ""size"" : 5681152,
    ""uuid"" : ""05fa665b-b1c8-3f62-861e-1b3579be4a9a"",
    ""path"" : ""\/Applications\/VirtualBox.app\/Contents\/MacOS\/VBoxRT.dylib"",
    ""name"" : ""VBoxRT.dylib""
  },
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 140703596834816,
    ""size"" : 49152,
    ""uuid"" : ""29a2750e-f31b-3630-8761-242a6bc3e99e"",
    ""path"" : ""\/usr\/lib\/system\/libsystem_pthread.dylib"",
    ""name"" : ""libsystem_pthread.dylib""
  },
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 4473835520,
    ""size"" : 4255744,
    ""uuid"" : ""7a8a2b64-5299-3eda-9b9b-85eac8f2d836"",
    ""path"" : ""\/Applications\/VirtualBox.app\/Contents\/MacOS\/components\/VBoxC.dylib"",
    ""name"" : ""VBoxC.dylib""
  },
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 4331163648,
    ""size"" : 3178496,
    ""uuid"" : ""b600b9be-060e-373f-8e33-09248dd2c4b7"",
    ""path"" : ""\/Applications\/VirtualBox.app\/Contents\/MacOS\/VBoxVMM.dylib"",
    ""name"" : ""VBoxVMM.dylib""
  },
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 140703597150208,
    ""CFBundleShortVersionString"" : ""6.9"",
    ""CFBundleIdentifier"" : ""com.apple.CoreFoundation"",
    ""size"" : 5246976,
    ""uuid"" : ""afcc752e-074d-340f-890c-263efd2da77f"",
    ""path"" : ""\/System\/Library\/Frameworks\/CoreFoundation.framework\/Versions\/A\/CoreFoundation"",
    ""name"" : ""CoreFoundation"",
    ""CFBundleVersion"" : ""1855.105""
  },
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 140703640735744,
    ""CFBundleShortVersionString"" : ""6.9"",
    ""CFBundleIdentifier"" : ""com.apple.AppKit"",
    ""size"" : 15257600,
    ""uuid"" : ""dd0028a3-78e3-3a8a-a51b-ddd68123adef"",
    ""path"" : ""\/System\/Library\/Frameworks\/AppKit.framework\/Versions\/C\/AppKit"",
    ""name"" : ""AppKit"",
    ""CFBundleVersion"" : ""2113""
  },
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 140703746437120,
    ""CFBundleShortVersionString"" : ""1.0"",
    ""CFBundleIdentifier"" : ""com.apple.audio.caulk"",
    ""size"" : 143360,
    ""uuid"" : ""c5042b28-9206-337f-bfb2-dc0b37dd8632"",
    ""path"" : ""\/System\/Library\/PrivateFrameworks\/caulk.framework\/Versions\/A\/caulk"",
    ""name"" : ""caulk""
  },
  {
    ""size"" : 0,
    ""source"" : ""A"",
    ""base"" : 0,
    ""uuid"" : ""00000000-0000-0000-0000-000000000000""
  }
],
  ""sharedCache"" : {
  ""base"" : 140703593594880,
  ""size"" : 15215640576,
  ""uuid"" : ""b5084610-afe4-3485-bade-628c4468b057""
},
  ""vmSummary"" : ""ReadOnly portion of Libraries: Total=971.6M resident=0K(0%) swapped_out_or_unallocated=971.6M(100%)\nWritable regions: Total=2.2G written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=2.2G(100%)\n\n                                VIRTUAL   REGION \nREGION TYPE                        SIZE    COUNT (non-coalesced) \n===========                     =======  ======= \nAccelerate framework               256K        2 \nActivity Tracing                   256K        1 \nCG backing stores                  640K        4 \nCG image                            48K        3 \nCG raster data                     140K        3 \nColorSync                          224K       25 \nCoreAnimation                     3892K       12 \nCoreGraphics                        12K        2 \nCoreServices                       304K        2 \nCoreUI image data                  332K        5 \nFoundation                          16K        1 \nKernel Alloc Once                    8K        1 \nMALLOC                           381.5M      105 \nMALLOC guard page                   48K        9 \nMALLOC_MEDIUM (reserved)           1.4G       12         reserved VM address space (unallocated)\nMALLOC_NANO (reserved)           384.0M        1         reserved VM address space (unallocated)\nSTACK GUARD                       56.1M       16 \nStack                             16.1M       16 \nVM_ALLOCATE                       8312K       17 \n__DATA                            35.6M      344 \n__DATA_CONST                      14.2M      192 \n__DATA_DIRTY                       638K      110 \n__FONT_DATA                          4K        1 \n__LINKEDIT                       644.7M       30 \n__OBJC_RO                         81.6M        1 \n__OBJC_RW                         3120K        2 \n__TEXT                           326.9M      354 \n__UNICODE                          588K        1 \ndyld private memory               1024K        1 \nmapped file                       90.2M       24 \nshared memory                      808K       19 \n===========                     =======  ======= \nTOTAL                              3.4G     1316 \nTOTAL, minus reserved VM space     1.6G     1316 \n"",
  ""legacyInfo"" : {
  ""threadTriggered"" : {
    ""queue"" : ""com.apple.main-thread""
  }
},
  ""trialInfo"" : {
  ""rollouts"" : null,
  ""experiments"" : null
},
  ""reportNotes"" : [
  ""thread_get_state(PAGEIN) returned 0x10000003: (ipc\/send) invalid destination port"",
  ""thread_get_state(EXCEPTION) returned 0x10000003: (ipc\/send) invalid destination port"",
  ""thread_get_state(FLAVOR) returned 0x10000003: (ipc\/send) invalid destination port""
]
}

Model: MacPro6,1, BootROM 429.40.7.0.1, 6 processors, 6-Core Intel Xeon E5, 3.5 GHz, 32 GB, SMC 2.20f18
Graphics: AMD FirePro D300, AMD FirePro D300, PCIe, 2 GB
Graphics: AMD FirePro D300, AMD FirePro D300, PCIe, 2 GB
Display: DELL E207WFP, 1680 x 1050 (Widescreen Super eXtended Graphics Array Plus), Main, MirrorOff, Online
Memory Module: DIMM1, 8 GB, DDR3 ECC, 1866 MHz, 0x80AD, 0x484D54343147553741465238432D52442020
Memory Module: DIMM2, 8 GB, DDR3 ECC, 1866 MHz, 0x80AD, 0x484D54343147553741465238432D52442020
Memory Module: DIMM3, 8 GB, DDR3 ECC, 1866 MHz, 0x80AD, 0x484D54343147553741465238432D52442020
Memory Module: DIMM4, 8 GB, DDR3 ECC, 1866 MHz, 0x80AD, 0x484D54343147553741465238432D52442020
AirPort: spairport_wireless_card_type_wifi (0x14E4, 0x135), Broadcom BCM43xx 1.0 (7.77.111.1 AirPortDriverBrcmNIC-1710.2)
Bluetooth: Version (null), 0 services, 0 devices, 0 incoming serial ports
Network Service: Ethernet 2, Ethernet, en1
PCI Card: AMD FirePro D300, Display Controller, Slot-1
PCI Card: AMD FirePro D300, Display Controller, Slot-2
PCI Card: pci1b4b,9235, AHCI Controller, Thunderbolt@81,0,0
PCI Card: pci1b21,625, AHCI Controller, Thunderbolt@236,0,0
Serial ATA Device: WDC  WDS100T2B0A-00SM50, 1 TB
Serial ATA Device: TEAM T253A3001T, 1.02 TB
Serial ATA Device: HGST HDN726060ALE614, 6 TB
Serial ATA Device: HGST HUH728060ALE600, 6 TB
USB Device: USB30Bus
USB Device: 4-Port USB 3.0 Hub
USB Device: 4-Port USB 3.0 Hub
USB Device: Mercury Pro
USB Device: USB3.0 Hub
USB Device: JMS56x Series
USB Device: Elite Pro U3FW
USB Device: Elements 25A3
USB Device: 4-Port USB 2.0 Hub
USB Device: 4-Port USB 2.0 Hub
USB Device: USB2.0 Hub
USB Device: Keyboard Hub
USB Device: Apple Keyboard
USB Device: MFC-J450DW
USB Device: hub_device
USB Device: hub_device
USB Device: Flash Card Reader
USB Device: USB Camera
USB Device: USB20Bus
USB Device: hub_device
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
Thunderbolt Bus: Mac Pro, Apple Inc., 19.2
Thunderbolt Device: RocketStor 5212, HighPoint Technologies, Inc., 1, 7.1
Thunderbolt Bus: Mac Pro, Apple Inc., 19.2
Thunderbolt Bus: Mac Pro, Apple Inc., 19.2
Thunderbolt Device: Drive Dock, Other World Computing, 1, 25.1
"	mauricev
16184	Invisible Mouse Cursor	VirtualBox 5.1.8	2016-11-13T10:17:13Z	2016-11-15T02:20:51Z	2016-11-15T02:20:51Z	"Hi there,

I am using VBox 5.1.8 for Windows (also tried test build 5.1.9) but am unable to get the mouse to work on RHEL 7. The cursor is apparently there but its just not showing. When I press left ctrl key and move mouse around the ""show location of pointer"" gets highlighted as I move in different areas. My machine config -

HP Pavillion Laptop / Windows 10 (Home 64bit) / Intel i7-6700HQ / GPUs (Intel HD Graphics 530 & Nividia GeForce GTX 960M)

I will be upfront and open, I am very new to VBox and Linux but nonetheless, I have been reading into forums and bug tickets for the past 3 days but to no avail.

Will appreciate any and all help. Many thanks."	Dan J
17430	Invisible mouse pointer with remote control. (Linux host)	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
20458	Is kernel 5.14.0-0.rc0.20210709gitf55966571d5e.14.fc35.x86_64 supported?	VirtualBox 6.1.22	2021-07-14T02:30:54Z	2021-08-09T20:06:16Z	2021-08-09T20:06:16Z	"Hi,

My system is Fedora Core 35 (Rawhide). ""they"" seem to upgrade their kernels frequently. I know that it takes some time for VB to support a given new kernel. Is there a way I can find out exactly which kernel is supported?

Best regards and THANKS,

George...
"	George R. Goffe
14895	iscsi connection to QNAP failure / infinite loop	VirtualBox 5.0.10	2015-12-04T02:55:05Z	2016-08-22T15:21:20Z	2016-08-22T15:21:20Z	"Trying to configure a new VM to use iSCSI on my QNAP device.  Had a connection problem. 

Now when I launch the Virtual Box Manager, the Virtual Box Interface process goes into an infinite loop trying to connect / validate the drive.  

Continues to do so even after GUI is closed. Only way to stop is to terminate process.  Also because validation never completes, Virtual Media Manager never completes to the point where controls are enabled.

VBoxSVC.log is filled with entries like:
{{{
00:00:01.505171          iSCSI: connect from initiator iqn.2009-08.com.sun.virtualbox.initiator:01:192.168.11.3 with source port 49541
00:00:01.505171          iSCSI: disconnect from initiator iqn.2009-08.com.sun.virtualbox.initiator:01:192.168.11.3 with source port 49541
00:00:01.536408          iSCSI: connect from initiator iqn.2009-08.com.sun.virtualbox.initiator:01:192.168.11.3 with source port 49542
00:00:01.536408          iSCSI: disconnect from initiator iqn.2009-08.com.sun.virtualbox.initiator:01:192.168.11.3 with source port 49542
}}}"	melgish
19027	iSCSI-attached disks of size 0 or which cannot be read lead to VBoxSVC going into a 100% CPU loop	VirtualBox 5.2.34	2019-10-18T15:00:56Z	2019-10-18T15:00:56Z	2019-10-18T15:00:56Z	"Scenario 1:
- FreeBSD 12.0 as iSCSI server (machine A), exporting several block devices
- Misconfiguration results in these devices being exported with size 0 (reason in this case: the blocksize argument in /dev/ctl.conf was missing and needed to reflect the underlying device block size of 4096)
- FreeBSD 12.0 (machine C) hosts various VirtualBox clients

Scenario 2:
- Linux openSUSE Leap 15.1 as iSCSI server (machine B), exporting a block device
- Firewall misconfiguration leads to read failures when accessing the exported device
- FreeBSD 12.0 (machine C) hosts various VirtualBox clients

Result (both scenarios):
- On machine C, VBoxSVC goes into a tight loop retrying accesses to these devices
- All running VirtualBox client instances hang, including those not accessing the misconfigured iSCSI exports
- On a multiprocessor system, VBoxSVC uses n x 100% CPU (don't know how n happens, probably the number of concurrently running clients)

Expected result:
- The error should be treated reasonably, probably forwarded to the client (as a read error of the device)

Note:
- The same issue also happened with earlier releases.
"	wonko1953
18528	ISO Windows 7 SP 4 - USB visible in host, not showing up in tree	VirtualBox 6.0.4	2019-03-28T22:53:15Z	2019-03-28T23:30:52Z	2019-03-28T23:30:52Z	"Inserting USB, shows up in host tree, have USB 3.0 xHCI Controller selected 
select the correct USB in filter, select correct USB in the running VM Devices, but USB
never shows up as device in windows explorer tree?"	JoseyWales
18471	Issue with OEL 7.2 on Macbook Pro VB 5.2/6 with Guest additions	VirtualBox 5.2.26	2019-03-05T00:01:34Z	2019-03-05T10:23:10Z	2019-03-05T10:23:10Z	"OEL7.2. OBI guest 'dies' after running the Virtualbox Guest addition install and rebooting.  It hangs (dies) during the OS guest boot.

00:08:54.776986 VMMDev: Guest Log: vboxguest: misc device minor 58, IRQ 20, I/O port d020, MMIO at 00000000f0000000 (size 0x400000)
00:08:58.775194 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago"	LACanuck
2736	It is impossible to set a user's font table for text output in a graphics mode	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
18887	I´ll try to initiate de sesion for install a windows XP and fail	VirtualBox 6.0.10	2019-09-01T00:00:35Z	2019-09-01T01:00:36Z	2019-09-01T01:00:36Z	"this is the message

The virtual machine 'Windows XP SP3' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\jhonny\VirtualBox VMs\Windows XP SP3\Logs\VBoxHardening.log'.

Código resultado: E_FAIL (0x80004005)
Componente: MachineWrap
Interfaz: IMachine {5047460a-265d-4538-b23e-ddba5fb84976}


"	ponino
20798	JMicron Icy Box IB-G1826MF-C31 usb connect	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
20319	Just installed v6.1.20's guest additions freezes Mac OS X El Capitan v10.11.6 guest VM & then host.	VirtualBox 6.1.20	2021-04-23T08:33:00Z	2021-04-24T00:48:21Z	2021-04-24T00:48:21Z	"Successfully (install/upgrad)ing VB v6.1.20's guests additions in Mac OS X El Capitan v10.11.6 VM cause a lock up to VM and then VB v6.1.20 in an old 2012 13"" MBP. https://forums.virtualbox.org/viewtopic.php?f=8&t=102608&p=498505 for my forum thread in details including logs. To make guest additions install/upgrade not freeze its VM and VB, disabling audio before starting up this VM prevents it. Thanks to fth0 for the answer."	Ant
21463	Kali Linux	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
19139	Kali linux VM buggy cursor	VirtualBox 6.0.14	2019-12-09T07:14:33Z	2019-12-09T22:23:55Z	2019-12-09T22:23:55Z	"hello,
My problem is that the mouse integration bugs after a while on kali linux so i have to reebot all the time.
I still can move the cursor graphicaly but its position stays the same. I can click but always on the same spot. 
But when i deactivate the mouse integration option the cursor now disapear but moves."	FvckNorris
19687	Kali problem	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
15597	Kaspersky hangs VirtualBox 4.3, 5.0, 5.1 on C2Duo E6850, Xeon L5420	VirtualBox 5.1.0	2016-07-12T21:45:35Z	2017-03-09T06:35:58Z	2017-03-09T06:35:58Z	"Kaspersky EndPoint Security 6.0-10.2, Kaspersky Free 16
in VirtualBox 4.3, 5.0, 5.1 
HANGS on C2Duo E6850, Xeon L5420
work normally on i5

update antivirus databases is ok. if start any type of shield (file, network..) then hangs.

hosts:linux32,linux64,win7x64
guest:winxp

---

or hangs with 100% load of vm cpus,
or error (log file included)"	unicorp99
15655	KDE Active Screen Edge Actions of host are not disabled when running a guest OS in full screen mode	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
16696	KDE taskbar is not visible	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
20218	"Keep getting ""Kernel driver not installed (rc=-1908)"" error"	VirtualBox 6.0.16	2021-02-22T00:00:56Z	2021-03-01T19:32:16Z	2021-03-01T19:32:16Z	"I mac a MacBook pro still using the intel processor, BigSur 11.1

At first, when I was installing version 6.1.18, I would get this error after clicking ""add"" to add the .iso file for windows 10. I tried uninstalling and reinstalling with no success. I also tried opening the VM through my applications folder as I've read that opening through the shortcut might also cause issues. Still no success. I also tried installing an older version (6.0.16) and repeated the same steps and still got the error when clicking ""add"" to add the .iso file for windows 10. Now, I get the error after clicking ""start"" for my vm. I am not sure what to do at this point. I've also ran:
{{{
sudo su
csrutil clear
reboot
}}}
 and this also didnt work. I am stuck :( 

here is the link to the screenshot of the full error in my dropbox:
https://www.dropbox.com/s/srfcpmmyf7rlj9y/Screen%20Shot%202021-02-21%20at%203.53.03%20PM.png?dl=0



"	imagoat
20333	keep restarting vm windows 10 on linux host	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
20163	kernel 5.10.11 panic at VM start, when CONFIG_DEBUG_SPINLOCK=y in kernel .config	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
20117	Kernel 5.11 RC2: Error building modules with mainline kernel 5.11 RC2	VirtualBox 6.1.16	2021-01-06T17:39:29Z	2021-01-07T02:48:18Z	2021-01-07T02:48:18Z	"VirtualBox Version 6.1.97 r141967 (Qt5.6.3)

OS: Ubutnu MATE 20.10

Kernel: Ubuntu Mainline Kernel 5.11 RC2

Getting errors while building modules. Attaching vbox-setup.log."	Jags
20551	Kernel driver not installed (rc=-1908)	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
20234	Kernel driver not installed launching VM on Version 6.1.18 r142142 (Qt5.6.3)	VirtualBox 6.1.18	2021-03-04T20:57:18Z	2022-03-09T19:12:05Z	2022-03-09T19:12:05Z	"on startup of any OS:

Kernel driver not installed (rc=-1908)

Make sure the kernel module has been loaded successfully.

where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT. "	dkardell
20441	Kernel module compilation error - VirtualBox 6.1.22 kernel 5.12.13	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
20687	kernel module isn't loaded because the VBox drive is not installed	VirtualBox 6.1.28	2021-11-24T15:17:39Z	2021-11-24T16:26:51Z	2021-11-24T16:26:51Z	"I used without problems for about three years VM VBox 5.6.2 on an host Win 7-64 , but around a months ago the pc has had some malfunctions with fan and power supply that they caused problems in the management of windows on the desktop and the Explorer block. Moreover VM Vb has stop to run, showing the message enclosed.
Now I have fixed any HD or SW issues and updated the VM Vbox version to 6.1.28 but it still doesn't work due of same problem: VBOX Drive don't installed."	marcopro
20677	kernel module isn't loaded because the VBox drive is not installed	VirtualBox 5.2.6	2021-11-19T09:34:28Z	2021-11-22T20:15:36Z	2021-11-22T20:15:36Z	"After several months that I used the version 5.2.6 (with Win 7 - 64), one month ago, I had some Windows problems due pc overheating and to the power source. Despite I solved any Windows failure (in particular those related to the desktop windows managing and to explorer block) Since that moment VM has stopped to run and every time I try tro run my virtual machine (Windows XP 32) it show the attached error, as in summary. 
I'm not expert and my attemp to unblock the situation, even by uninstalling and reinstalling VB, have not been successful.
Thanks for all."	marcopro
18127	"Kernel Panic (""a freed zone element has been modified in zone kalloc.16) with 5.2.22 on Mac OSx"	VirtualBox 5.2.22	2018-11-13T10:16:51Z	2020-05-15T08:54:30Z	2020-05-15T08:54:30Z	"Hello,
after upgrading VirtualBox (including extensions) to 5.2.22 my MacBook runs into kernel panics as soon as I deleted some files in my VM Guest (OEL 6.7) and tried to recreate them.

Kernel panic looks like this (no additional messages in VBox.log) - just copied and pasted two of them.

{{{
Anonymous UUID:       82237E1E-63F4-6DBD-263D-F8CCD0BD2352

Tue Nov 13 11:07:05 2018

*** Panic Report ***
panic(cpu 0 caller 0xffffff80058b8ff7): ""a freed zone element has been modified in zone kalloc.16: expected 0xc0ffee0af45053f8 but found 0x10000c0ec035, bits changed 0xc0fffe0af85e93cd, at offset 0 of 16 in element 0xffffff804b1e5140, cookies 0x3f00118abf4e05f8 0x53521ec3d6d4d23""@/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-4570.71.13/osfmk/kern/zalloc.c:1122
Backtrace (CPU 0), Frame : Return Address
0xffffff81fdf7b980 : 0xffffff800586b1c6 
0xffffff81fdf7b9d0 : 0xffffff8005993a74 
0xffffff81fdf7ba10 : 0xffffff8005985d44 
0xffffff81fdf7ba80 : 0xffffff800581d1e0 
0xffffff81fdf7baa0 : 0xffffff800586ac3c 
0xffffff81fdf7bbd0 : 0xffffff800586a9fc 
0xffffff81fdf7bc30 : 0xffffff80058b8ff7 
0xffffff81fdf7bc90 : 0xffffff80058b8910 
0xffffff81fdf7bce0 : 0xffffff80058b7313 
0xffffff81fdf7be10 : 0xffffff8005876c44 
0xffffff81fdf7be80 : 0xffffff8005ce5ba3 
0xffffff81fdf7bed0 : 0xffffff8005ce5a50 
0xffffff81fdf7bf40 : 0xffffff8005e03008 
0xffffff81fdf7bfa0 : 0xffffff800581d9c6 

BSD process name corresponding to current thread: VirtualBoxVM

Mac OS version:
17G3025

Kernel version:
Darwin Kernel Version 17.7.0: Wed Oct 10 23:06:14 PDT 2018; root:xnu-4570.71.13~1/RELEASE_X86_64
Kernel UUID: 4C560F2C-3F3C-3423-B806-2C4D39D570A0
Kernel slide:     0x0000000005600000
Kernel text base: 0xffffff8005800000
__HIB  text base: 0xffffff8005700000
System model name: MacBookPro14,1 (Mac-B4831CEBD52A0C4C)

System uptime in nanoseconds: 519699934001
last loaded kext at 248994916223: com.apple.filesystems.msdosfs	1.10 (addr 0xffffff7f868a3000, size 69632)
loaded kexts:
org.virtualbox.kext.VBoxNetAdp	5.2.22
org.virtualbox.kext.VBoxNetFlt	5.2.22
org.virtualbox.kext.VBoxUSB	5.2.22
org.virtualbox.kext.VBoxDrv	5.2.22
com.apple.filesystems.msdosfs	1.10
com.apple.driver.AudioAUUC	1.70
com.apple.driver.AGPM	110.23.37
com.apple.driver.ApplePlatformEnabler	2.7.0d0
com.apple.driver.X86PlatformShim	1.0.0
com.apple.filesystems.autofs	3.0
com.apple.driver.AppleUpstreamUserClient	3.6.5
com.apple.driver.AppleGraphicsDevicePolicy	3.20.14
com.apple.AGDCPluginDisplayMetrics	3.20.0
com.apple.driver.AppleHV	1
com.apple.iokit.IOUserEthernet	1.0.1
com.apple.driver.AppleHDAHardwareConfigDriver	281.52
com.apple.driver.AppleHDA	281.52
com.apple.iokit.IOBluetoothSerialManager	6.0.7f11
com.apple.driver.pmtelemetry	1
com.apple.Dont_Steal_Mac_OS_X	7.0.0
com.apple.driver.AppleCameraInterface	6.01.2
com.apple.driver.AppleIntelKBLGraphics	10.3.6
com.apple.driver.AppleIntelSlowAdaptiveClocking	4.0.0
com.apple.driver.AppleIntelPCHPMC	2.0.1
com.apple.driver.ACPI_SMC_PlatformPlugin	1.0.0
com.apple.driver.eficheck	1
com.apple.driver.AppleFIVRDriver	4.1.0
com.apple.driver.AppleIntelKBLGraphicsFramebuffer	10.3.6
com.apple.driver.AGDCBacklightControl	3.20.0
com.apple.driver.AppleOSXWatchdog	1
com.apple.driver.AppleSMCLMU	211
com.apple.driver.AppleThunderboltIP	3.1.1
com.apple.driver.AppleBacklight	170.12.6
com.apple.driver.AppleMCCSControl	1.5.5
com.apple.driver.usb.AppleUSBHostBillboardDevice	1.0
com.apple.iokit.SCSITaskUserClient	404.30.2
com.apple.filesystems.apfs	748.51.0
com.apple.driver.AppleFileSystemDriver	3.0.1
com.apple.filesystems.hfs.kext	407.50.6
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless	1.0.0d1
com.apple.BootCache	40
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib	1.0.0
com.apple.AppleSystemPolicy	1.0
com.apple.driver.AppleTopCaseHIDEventDriver	135
com.apple.driver.AirPort.BrcmNIC	1241.31.1a9
com.apple.driver.AppleSmartBatteryManager	161.0.0
com.apple.driver.AppleACPIButtons	6.1
com.apple.driver.AppleRTC	2.0
com.apple.driver.AppleSMBIOS	2.1
com.apple.driver.AppleACPIEC	6.1
com.apple.driver.AppleAPIC	1.7
com.apple.nke.applicationfirewall	183
com.apple.security.TMSafetyNet	8
com.apple.security.quarantine	3
com.apple.iokit.IOUSBUserClient	900.4.1
com.apple.driver.usb.cdc.acm	5.0.0
com.apple.kext.triggers	1.0
com.apple.driver.AppleGraphicsControl	3.20.14
com.apple.iokit.IOAVBFamily	683.1
com.apple.plugin.IOgPTPPlugin	680.15
com.apple.iokit.IOEthernetAVBController	1.1.0
com.apple.driver.AppleSSE	1.0
com.apple.driver.DspFuncLib	281.52
com.apple.kext.OSvKernDSPLib	526
com.apple.AppleGPUWrangler	3.20.0
com.apple.iokit.IOSlowAdaptiveClockingFamily	1.0.0
com.apple.iokit.IOBluetoothHostControllerUARTTransport	6.0.7f11
com.apple.iokit.IOBluetoothHostControllerTransport	6.0.7f11
com.apple.driver.usb.cdc.ncm	5.0.0
com.apple.driver.IOPlatformPluginLegacy	1.0.0
com.apple.driver.X86PlatformPlugin	1.0.0
com.apple.driver.IOPlatformPluginFamily	6.0.0d8
com.apple.iokit.IOAcceleratorFamily2	378.26
com.apple.iokit.IOSurface	211.15
com.apple.AppleGraphicsDeviceControl	3.20.14
com.apple.driver.AppleSMBusPCI	1.0.14d1
com.apple.driver.AppleIntelLpssUARTv1	3.0.60
com.apple.driver.AppleIntelLpssUARTCommon	3.0.60
com.apple.driver.AppleOnboardSerial	1.0
com.apple.iokit.IOSkywalkFamily	1
com.apple.iokit.IOSerialFamily	11
com.apple.driver.AppleThunderboltEDMSink	4.1.4
com.apple.driver.AppleThunderboltDPOutAdapter	5.5.5
com.apple.driver.AppleHDAController	281.52
com.apple.iokit.IOHDAFamily	281.52
com.apple.iokit.IOAudioFamily	206.5
com.apple.vecLib.kext	1.2.0
com.apple.driver.AppleBacklightExpert	1.1.0
com.apple.iokit.IONDRVSupport	519.21
com.apple.driver.AppleSMBusController	1.0.18d1
com.apple.iokit.IOGraphicsFamily	519.21
com.apple.driver.usb.IOUSBHostHIDDevice	1.2
com.apple.driver.usb.cdc.ecm	5.0.0
com.apple.driver.AppleUSBMergeNub	900.4.1
com.apple.driver.usb.cdc	5.0.0
com.apple.driver.usb.networking	5.0.0
com.apple.driver.usb.AppleUSBHostCompositeDevice	1.2
com.apple.driver.usb.AppleUSBHub	1.2
com.apple.driver.AppleUSBHostMergeProperties	1.2
com.apple.driver.AppleXsanScheme	3
com.apple.filesystems.hfs.encodings.kext	1
com.apple.driver.AppleActuatorDriver	1614.1
com.apple.driver.AppleHIDKeyboard	205.1
com.apple.driver.AppleHSBluetoothDriver	135
com.apple.driver.IOBluetoothHIDDriver	6.0.7f11
com.apple.iokit.IOBluetoothFamily	6.0.7f11
com.apple.driver.AppleMultitouchDriver	1614.1
com.apple.driver.AppleInputDeviceSupport	1614.11
com.apple.driver.AppleHSSPIHIDDriver	53
com.apple.driver.AppleThunderboltDPInAdapter	5.5.5
com.apple.driver.AppleThunderboltDPAdapterFamily	5.5.5
com.apple.driver.AppleThunderboltPCIDownAdapter	2.1.3
com.apple.driver.AppleHPM	3.1.3
com.apple.driver.AppleIntelLpssI2CController	3.0.60
com.apple.driver.AppleHSSPISupport	53
com.apple.driver.AppleThunderboltNHI	4.7.3
com.apple.iokit.IOThunderboltFamily	6.7.9
com.apple.driver.AppleIntelLpssSpiController	3.0.60
com.apple.driver.AppleIntelLpssDmac	3.0.60
com.apple.iokit.IO80211Family	1200.12.2
com.apple.driver.mDNSOffloadUserClient	1.0.1b8
com.apple.driver.corecapture	1.0.4
com.apple.iokit.IONVMeFamily	2.1.0
com.apple.driver.AppleIntelLpssI2C	3.0.60
com.apple.driver.AppleIntelLpssGspi	3.0.60
com.apple.driver.usb.AppleUSBXHCIPCI	1.2
com.apple.driver.usb.AppleUSBXHCI	1.2
com.apple.driver.usb.AppleUSBHostPacketFilter	1.0
com.apple.iokit.IOUSBFamily	900.4.1
com.apple.driver.AppleEFINVRAM	2.1
com.apple.driver.AppleEFIRuntime	2.1
com.apple.iokit.IOSMBusFamily	1.1
com.apple.iokit.IOHIDFamily	2.0.0
com.apple.security.sandbox	300.0
com.apple.kext.AppleMatch	1.0.0d1
com.apple.driver.DiskImages	480.60.1
com.apple.driver.AppleFDEKeyStore	28.30
com.apple.driver.AppleEffaceableStorage	1.0
com.apple.driver.AppleKeyStore	2
com.apple.driver.AppleUSBTDM	439.70.3
com.apple.driver.AppleMobileFileIntegrity	1.0.5
com.apple.iokit.IOUSBMassStorageDriver	140.70.2
com.apple.iokit.IOSCSIBlockCommandsDevice	404.30.2
com.apple.iokit.IOSCSIArchitectureModelFamily	404.30.2
com.apple.iokit.IOStorageFamily	2.1
com.apple.driver.AppleCredentialManager	1.0
com.apple.driver.KernelRelayHost	1
com.apple.iokit.IOUSBHostFamily	1.2
com.apple.driver.usb.AppleUSBCommon	1.0
com.apple.driver.AppleBusPowerController	1.0
com.apple.driver.AppleSEPManager	1.0.1
com.apple.driver.IOSlaveProcessor	1
com.apple.iokit.IOReportFamily	31
com.apple.iokit.IOTimeSyncFamily	680.15
com.apple.iokit.IONetworkingFamily	3.4
com.apple.driver.AppleACPIPlatform	6.1
com.apple.driver.AppleSMC	3.1.9
com.apple.iokit.IOPCIFamily	2.9
com.apple.iokit.IOACPIFamily	1.4
com.apple.kec.pthread	1
com.apple.kec.Libm	1
com.apple.kec.corecrypto	1.0

EOF
}}}


{{{
Anonymous UUID:       82237E1E-63F4-6DBD-263D-F8CCD0BD2352

Tue Nov 13 10:58:16 2018

*** Panic Report ***
panic(cpu 2 caller 0xffffff8001cb903d): ""a freed zone element has been modified in zone kalloc.16: expected 0xe4988e3ed03a8352 but found 0xdeadbeef00000001, bits changed 0x3a3530d1d03a8353, at offset 0 of 16 in element 0xffffff8048db0cf0, cookies 0x3f00113912711a2e 0x53521e81ce62793""@/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-4570.71.13/osfmk/kern/zalloc.c:1122
Backtrace (CPU 2), Frame : Return Address
0xffffff91ffcbb750 : 0xffffff8001c6b1c6 
0xffffff91ffcbb7a0 : 0xffffff8001d93a74 
0xffffff91ffcbb7e0 : 0xffffff8001d85d44 
0xffffff91ffcbb850 : 0xffffff8001c1d1e0 
0xffffff91ffcbb870 : 0xffffff8001c6ac3c 
0xffffff91ffcbb9a0 : 0xffffff8001c6a9fc 
0xffffff91ffcbba00 : 0xffffff8001cb903d 
0xffffff91ffcbba60 : 0xffffff8001cb8910 
0xffffff91ffcbbab0 : 0xffffff8001cb7313 
0xffffff91ffcbbbe0 : 0xffffff8001c76c44 
0xffffff91ffcbbc50 : 0xffffff8002215d8c 
0xffffff91ffcbbc70 : 0xffffff8002215df2 
0xffffff91ffcbbc90 : 0xffffff800226779d 
0xffffff91ffcbbcb0 : 0xffffff800226780c 
0xffffff91ffcbbcd0 : 0xffffff80022638fc 
0xffffff91ffcbbd10 : 0xffffff80022c842f 
0xffffff91ffcbbd70 : 0xffffff8001d42b7b 
0xffffff91ffcbbdc0 : 0xffffff8001c706e0 
0xffffff91ffcbbe10 : 0xffffff8001c4da3d 
0xffffff91ffcbbe60 : 0xffffff8001c6054b 
0xffffff91ffcbbef0 : 0xffffff8001d6ff1d 
0xffffff91ffcbbfa0 : 0xffffff8001c1d9e6 

BSD process name corresponding to current thread: VBoxSVC

Mac OS version:
17G3025

Kernel version:
Darwin Kernel Version 17.7.0: Wed Oct 10 23:06:14 PDT 2018; root:xnu-4570.71.13~1/RELEASE_X86_64
Kernel UUID: 4C560F2C-3F3C-3423-B806-2C4D39D570A0
Kernel slide:     0x0000000001a00000
Kernel text base: 0xffffff8001c00000
__HIB  text base: 0xffffff8001b00000
System model name: MacBookPro14,1 (Mac-B4831CEBD52A0C4C)

System uptime in nanoseconds: 6013699815144
last loaded kext at 245870616385: com.apple.filesystems.msdosfs	1.10 (addr 0xffffff7f82ca3000, size 69632)
last unloaded kext at 403105650360: com.apple.driver.AppleFileSystemDriver	3.0.1 (addr 0xffffff7f82804000, size 8192)
loaded kexts:
org.virtualbox.kext.VBoxNetAdp	5.2.22
org.virtualbox.kext.VBoxNetFlt	5.2.22
org.virtualbox.kext.VBoxUSB	5.2.22
org.virtualbox.kext.VBoxDrv	5.2.22
com.apple.driver.AudioAUUC	1.70
com.apple.filesystems.autofs	3.0
com.apple.driver.AGPM	110.23.37
com.apple.driver.ApplePlatformEnabler	2.7.0d0
com.apple.driver.X86PlatformShim	1.0.0
com.apple.driver.AppleUpstreamUserClient	3.6.5
com.apple.driver.AppleHDA	281.52
com.apple.driver.AppleGraphicsDevicePolicy	3.20.14
com.apple.AGDCPluginDisplayMetrics	3.20.0
com.apple.driver.AppleIntelKBLGraphics	10.3.6
com.apple.driver.AppleHV	1
com.apple.iokit.IOUserEthernet	1.0.1
com.apple.driver.eficheck	1
com.apple.driver.AppleIntelPCHPMC	2.0.1
com.apple.iokit.IOBluetoothSerialManager	6.0.7f11
com.apple.driver.AppleThunderboltIP	3.1.1
com.apple.driver.AppleIntelKBLGraphicsFramebuffer	10.3.6
com.apple.driver.AppleOSXWatchdog	1
com.apple.driver.AppleSMCLMU	211
com.apple.driver.AppleCameraInterface	6.01.2
com.apple.driver.pmtelemetry	1
com.apple.Dont_Steal_Mac_OS_X	7.0.0
com.apple.driver.AppleIntelSlowAdaptiveClocking	4.0.0
com.apple.driver.AppleBacklight	170.12.6
com.apple.driver.AppleMCCSControl	1.5.5
com.apple.driver.usb.AppleUSBHostBillboardDevice	1.0
com.apple.filesystems.apfs	748.51.0
com.apple.filesystems.hfs.kext	407.50.6
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless	1.0.0d1
com.apple.BootCache	40
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib	1.0.0
com.apple.AppleSystemPolicy	1.0
com.apple.driver.AppleTopCaseHIDEventDriver	135
com.apple.driver.AirPort.BrcmNIC	1241.31.1a9
com.apple.driver.AppleSmartBatteryManager	161.0.0
com.apple.driver.AppleACPIButtons	6.1
com.apple.driver.AppleRTC	2.0
com.apple.driver.AppleSMBIOS	2.1
com.apple.driver.AppleACPIEC	6.1
com.apple.driver.AppleAPIC	1.7
com.apple.nke.applicationfirewall	183
com.apple.security.TMSafetyNet	8
com.apple.security.quarantine	3
com.apple.driver.usb.cdc.ncm	5.0.0
com.apple.iokit.IOUSBUserClient	900.4.1
com.apple.kext.triggers	1.0
com.apple.driver.DspFuncLib	281.52
com.apple.kext.OSvKernDSPLib	526
com.apple.driver.AppleGraphicsControl	3.20.14
com.apple.iokit.IOAVBFamily	683.1
com.apple.plugin.IOgPTPPlugin	680.15
com.apple.iokit.IOEthernetAVBController	1.1.0
com.apple.iokit.IOBluetoothHostControllerUARTTransport	6.0.7f11
com.apple.iokit.IOBluetoothHostControllerTransport	6.0.7f11
com.apple.driver.AppleSSE	1.0
com.apple.iokit.IOAcceleratorFamily2	378.26
com.apple.iokit.IOSurface	211.15
com.apple.driver.AppleHDAController	281.52
com.apple.iokit.IOHDAFamily	281.52
com.apple.iokit.IOAudioFamily	206.5
com.apple.vecLib.kext	1.2.0
com.apple.driver.AppleIntelLpssUARTv1	3.0.60
com.apple.driver.AppleIntelLpssUARTCommon	3.0.60
com.apple.driver.AppleOnboardSerial	1.0
com.apple.iokit.IOSkywalkFamily	1
com.apple.iokit.IOSerialFamily	11
com.apple.driver.X86PlatformPlugin	1.0.0
com.apple.driver.IOPlatformPluginFamily	6.0.0d8
com.apple.AppleGPUWrangler	3.20.0
com.apple.AppleGraphicsDeviceControl	3.20.14
com.apple.iokit.IOSlowAdaptiveClockingFamily	1.0.0
com.apple.driver.AppleBacklightExpert	1.1.0
com.apple.iokit.IONDRVSupport	519.21
com.apple.driver.AppleSMBusController	1.0.18d1
com.apple.iokit.IOGraphicsFamily	519.21
com.apple.driver.usb.IOUSBHostHIDDevice	1.2
com.apple.driver.usb.cdc.ecm	5.0.0
com.apple.driver.usb.cdc	5.0.0
com.apple.driver.usb.networking	5.0.0
com.apple.driver.usb.AppleUSBHostCompositeDevice	1.2
com.apple.driver.usb.AppleUSBHub	1.2
com.apple.driver.AppleUSBHostMergeProperties	1.2
com.apple.filesystems.hfs.encodings.kext	1
com.apple.driver.AppleActuatorDriver	1614.1
com.apple.driver.AppleHIDKeyboard	205.1
com.apple.driver.AppleHSBluetoothDriver	135
com.apple.driver.IOBluetoothHIDDriver	6.0.7f11
com.apple.iokit.IOBluetoothFamily	6.0.7f11
com.apple.driver.AppleMultitouchDriver	1614.1
com.apple.driver.AppleInputDeviceSupport	1614.11
com.apple.driver.AppleHSSPIHIDDriver	53
com.apple.driver.AppleThunderboltDPInAdapter	5.5.5
com.apple.driver.AppleThunderboltDPAdapterFamily	5.5.5
com.apple.driver.AppleThunderboltPCIDownAdapter	2.1.3
com.apple.driver.AppleHPM	3.1.3
com.apple.driver.AppleIntelLpssI2CController	3.0.60
com.apple.driver.AppleHSSPISupport	53
com.apple.driver.AppleThunderboltNHI	4.7.3
com.apple.iokit.IOThunderboltFamily	6.7.9
com.apple.driver.AppleIntelLpssSpiController	3.0.60
com.apple.driver.AppleIntelLpssDmac	3.0.60
com.apple.iokit.IONVMeFamily	2.1.0
com.apple.iokit.IO80211Family	1200.12.2
com.apple.driver.mDNSOffloadUserClient	1.0.1b8
com.apple.driver.corecapture	1.0.4
com.apple.driver.AppleIntelLpssI2C	3.0.60
com.apple.driver.AppleIntelLpssGspi	3.0.60
com.apple.driver.usb.AppleUSBXHCIPCI	1.2
com.apple.driver.usb.AppleUSBXHCI	1.2
com.apple.driver.usb.AppleUSBHostPacketFilter	1.0
com.apple.iokit.IOUSBFamily	900.4.1
com.apple.driver.AppleEFINVRAM	2.1
com.apple.driver.AppleEFIRuntime	2.1
com.apple.iokit.IOSMBusFamily	1.1
com.apple.iokit.IOHIDFamily	2.0.0
com.apple.security.sandbox	300.0
com.apple.kext.AppleMatch	1.0.0d1
com.apple.driver.DiskImages	480.60.1
com.apple.driver.AppleFDEKeyStore	28.30
com.apple.driver.AppleEffaceableStorage	1.0
com.apple.driver.AppleKeyStore	2
com.apple.driver.AppleUSBTDM	439.70.3
com.apple.driver.AppleMobileFileIntegrity	1.0.5
com.apple.iokit.IOUSBMassStorageDriver	140.70.2
com.apple.iokit.IOSCSIBlockCommandsDevice	404.30.2
com.apple.iokit.IOSCSIArchitectureModelFamily	404.30.2
com.apple.iokit.IOStorageFamily	2.1
com.apple.driver.AppleCredentialManager	1.0
com.apple.driver.KernelRelayHost	1
com.apple.iokit.IOUSBHostFamily	1.2
com.apple.driver.usb.AppleUSBCommon	1.0
com.apple.driver.AppleBusPowerController	1.0
com.apple.driver.AppleSEPManager	1.0.1
com.apple.driver.IOSlaveProcessor	1
com.apple.iokit.IOReportFamily	31
com.apple.iokit.IOTimeSyncFamily	680.15
com.apple.iokit.IONetworkingFamily	3.4
com.apple.driver.AppleACPIPlatform	6.1
com.apple.driver.AppleSMC	3.1.9
com.apple.iokit.IOPCIFamily	2.9
com.apple.iokit.IOACPIFamily	1.4
com.apple.kec.pthread	1
com.apple.kec.Libm	1
com.apple.kec.corecrypto	1.0

EOF
}}}

Mac OSx is 10.13.6 (17G3025)."	OracleSK
21338	Kernel Panic Boot2Docker Distro	VirtualBox-7.0.4	2022-12-14T16:44:28Z	2022-12-19T01:57:35Z	2022-12-19T01:57:35Z	Please see this [https://github.com/hashicorp/vagrant/issues/13011 Vagrant bug report]. The comment by phinze suggests this is a VirtualBox issue.	goldfita
17928	Kernel panic for 5.2.16 virtual box on MacOs	VirtualBox 5.2.16	2018-08-14T17:50:55Z	2018-08-15T05:22:35Z	2018-08-15T05:22:35Z	"Hey,

I have had this problem for two days ago twice - after a day working on macbook pro I've got an exception with version 5.2.6.
I've tried to update version to 5.2.16 but I've got the same issue.

All detailed information from the error report is below.

Anonymous UUID:       607DE2DB-3E7C-FBD7-3326-749B6B46673D

Tue Aug 14 20:31:58 2018

*** Panic Report ***
panic(cpu 4 caller 0xffffff8014099785): ""Graphics firmware encountered an exception: 0xd, from EIP = 0xfb57\n""@/Library/Caches/com.apple.xbs/Sources/GPUDriversIntel/GPUDriversIntel-10.36.19/Common/GLKernel/Intel/skl/sched3/IGGuC.cpp:800
Backtrace (CPU 4), Frame : Return Address
0xffffff9230e5bc20 : 0xffffff8013a6c1c6 
0xffffff9230e5bc70 : 0xffffff8013b95274 
0xffffff9230e5bcb0 : 0xffffff8013b87544 
0xffffff9230e5bd20 : 0xffffff8013a1e1e0 
0xffffff9230e5bd40 : 0xffffff8013a6bc3c 
0xffffff9230e5be70 : 0xffffff8013a6b9fc 
0xffffff9230e5bed0 : 0xffffff8014099785 
0xffffff9230e5bf30 : 0xffffff8014097ef2 
0xffffff9230e5bf70 : 0xffffff801409752c 
0xffffff9230e5bfa0 : 0xffffff8013a1d557 

BSD process name corresponding to current thread: kernel_task

Mac OS version:
17G65

Kernel version:
Darwin Kernel Version 17.7.0: Thu Jun 21 22:53:14 PDT 2018; root:xnu-4570.71.2~1/RELEASE_X86_64
Kernel UUID: 1AE5ACFD-3B6F-3D74-AD52-31F1430DBC6F
Kernel slide:     0x0000000013800000
Kernel text base: 0xffffff8013a00000
__HIB  text base: 0xffffff8013900000
System model name: MacBookPro13,3 (Mac-A5C67F76ED83108C)

System uptime in nanoseconds: 73926488455720
last loaded kext at 67979960957079: com.apple.driver.AppleXsanScheme	3 (addr 0xffffff7f9a680000, size 32768)
last unloaded kext at 68095936191994: com.apple.driver.AppleXsanScheme	3 (addr 0xffffff7f9a680000, size 32768)
loaded kexts:
org.virtualbox.kext.VBoxNetAdp	5.2.16
org.virtualbox.kext.VBoxNetFlt	5.2.16
org.virtualbox.kext.VBoxUSB	5.2.16
org.virtualbox.kext.VBoxDrv	5.2.16
com.apple.nke.l2tp	1.9
com.apple.driver.AudioAUUC	1.70
com.apple.driver.AGPM	110.23.37
com.apple.driver.ApplePlatformEnabler	2.7.0d0
com.apple.driver.X86PlatformShim	1.0.0
com.apple.filesystems.autofs	3.0
com.apple.driver.AppleUpstreamUserClient	3.6.5
com.apple.kext.AMDFramebuffer	1.6.8
com.apple.driver.AppleHDA	281.52
com.apple.kext.AMDRadeonX4000	1.6.8
com.apple.driver.AppleGraphicsDevicePolicy	3.20.13
com.apple.AGDCPluginDisplayMetrics	3.20.13
com.apple.driver.AppleHV	1
com.apple.driver.AppleHIDALSService	1
com.apple.iokit.IOUserEthernet	1.0.1
com.apple.iokit.IOBluetoothSerialManager	6.0.7f10
com.apple.driver.pmtelemetry	1
com.apple.Dont_Steal_Mac_OS_X	7.0.0
com.apple.driver.AGDCBacklightControl	3.20.13
com.apple.driver.AppleIntelSKLGraphics	10.3.6
com.apple.driver.eficheck	1
com.apple.driver.AppleIntelPCHPMC	2.0.1
com.apple.driver.AppleMuxControl	3.20.13
com.apple.driver.AppleGFXHDA	100.1.17
com.apple.driver.AppleEmbeddedOSSupportHost	1
com.apple.driver.SMCMotionSensor	3.0.4d1
com.apple.driver.AppleOSXWatchdog	1
com.apple.kext.AMD9500Controller	1.6.8
com.apple.driver.AppleIntelSKLGraphicsFramebuffer	10.3.6
com.apple.driver.AppleIntelSlowAdaptiveClocking	4.0.0
com.apple.driver.AppleMCCSControl	1.5.5
com.apple.driver.AppleThunderboltIP	3.1.1
com.apple.filesystems.hfs.kext	407.50.6
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless	1.0.0d1
com.apple.BootCache	40
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib	1.0.0
com.apple.AppleSystemPolicy	1.0
com.apple.driver.AppleTopCaseHIDEventDriver	133
com.apple.filesystems.apfs	748.51.0
com.apple.driver.AirPort.BrcmNIC	1241.31.1a9
com.apple.driver.AppleSmartBatteryManager	161.0.0
com.apple.driver.AppleACPIButtons	6.1
com.apple.driver.AppleRTC	2.0
com.apple.driver.AppleSMBIOS	2.1
com.apple.driver.AppleACPIEC	6.1
com.apple.driver.AppleAPIC	1.7
com.apple.nke.applicationfirewall	183
com.apple.security.TMSafetyNet	8
com.apple.security.quarantine	3
com.apple.nke.ppp	1.9
com.apple.iokit.IOUSBUserClient	900.4.1
com.apple.kext.triggers	1.0
com.apple.kext.AMDRadeonX4100HWLibs	1.0
com.apple.driver.DspFuncLib	281.52
com.apple.kext.OSvKernDSPLib	526
com.apple.kext.AMDRadeonX4000HWServices	1.6.8
com.apple.iokit.IOAVBFamily	680.2
com.apple.plugin.IOgPTPPlugin	680.15
com.apple.iokit.IOEthernetAVBController	1.1.0
com.apple.driver.AppleSSE	1.0
com.apple.iokit.IOBluetoothHostControllerUARTTransport	6.0.7f10
com.apple.iokit.IOBluetoothHostControllerTransport	6.0.7f10
com.apple.driver.AppleBacklightExpert	1.1.0
com.apple.driver.AppleGraphicsControl	3.20.13
com.apple.driver.AppleHDAController	281.52
com.apple.iokit.IOHDAFamily	281.52
com.apple.driver.usb.IOUSBHostHIDDevice	1.2
com.apple.iokit.IOAudioFamily	206.5
com.apple.vecLib.kext	1.2.0
com.apple.iokit.IONDRVSupport	519.20
com.apple.driver.AppleIntelLpssUARTv1	3.0.60
com.apple.driver.AppleIntelLpssUARTCommon	3.0.60
com.apple.driver.AppleOnboardSerial	1.0
com.apple.iokit.IOSkywalkFamily	1
com.apple.iokit.IOSerialFamily	11
com.apple.driver.X86PlatformPlugin	1.0.0
com.apple.driver.IOPlatformPluginFamily	6.0.0d8
com.apple.kext.AMDSupport	1.6.8
com.apple.iokit.IOAcceleratorFamily2	378.26
com.apple.iokit.IOSurface	211.15
com.apple.AppleGPUWrangler	3.20.13
com.apple.AppleGraphicsDeviceControl	3.20.13
com.apple.iokit.IOSlowAdaptiveClockingFamily	1.0.0
com.apple.driver.AppleSMBusController	1.0.18d1
com.apple.iokit.IOGraphicsFamily	519.20
com.apple.driver.usb.cdc.ncm	5.0.0
com.apple.driver.usb.AppleUSBiBridge	1.0
com.apple.driver.usb.cdc	5.0.0
com.apple.driver.usb.networking	5.0.0
com.apple.driver.usb.AppleUSBHostCompositeDevice	1.2
com.apple.driver.AppleUSBHostMergeProperties	1.2
com.apple.filesystems.hfs.encodings.kext	1
com.apple.driver.AppleActuatorDriver	1404.4
com.apple.driver.AppleHIDKeyboard	205
com.apple.driver.AppleHSBluetoothDriver	133
com.apple.driver.IOBluetoothHIDDriver	6.0.7f10
com.apple.iokit.IOBluetoothFamily	6.0.7f10
com.apple.driver.AppleMultitouchDriver	1404.4
com.apple.driver.AppleInputDeviceSupport	1404.3
com.apple.driver.AppleHSSPIHIDDriver	53
com.apple.driver.AppleThunderboltDPInAdapter	5.5.5
com.apple.driver.AppleThunderboltDPAdapterFamily	5.5.5
com.apple.driver.AppleThunderboltPCIDownAdapter	2.1.3
com.apple.driver.AppleHSSPISupport	53
com.apple.iokit.IONVMeFamily	2.1.0
com.apple.iokit.IO80211Family	1200.12.2
com.apple.driver.mDNSOffloadUserClient	1.0.1b8
com.apple.driver.corecapture	1.0.4
com.apple.driver.AppleIntelLpssSpiController	3.0.60
com.apple.driver.AppleThunderboltNHI	4.7.2
com.apple.driver.AppleHPM	3.1.3
com.apple.iokit.IOThunderboltFamily	6.7.8
com.apple.driver.AppleIntelLpssI2CController	3.0.60
com.apple.driver.AppleIntelLpssDmac	3.0.60
com.apple.driver.AppleIntelLpssI2C	3.0.60
com.apple.driver.AppleIntelLpssGspi	3.0.60
com.apple.driver.usb.AppleUSBXHCIPCI	1.2
com.apple.driver.usb.AppleUSBXHCI	1.2
com.apple.driver.usb.AppleUSBHostPacketFilter	1.0
com.apple.iokit.IOUSBFamily	900.4.1
com.apple.driver.AppleEFINVRAM	2.1
com.apple.driver.AppleEFIRuntime	2.1
com.apple.iokit.IOSMBusFamily	1.1
com.apple.iokit.IOHIDFamily	2.0.0
com.apple.security.sandbox	300.0
com.apple.kext.AppleMatch	1.0.0d1
com.apple.driver.DiskImages	480.60.1
com.apple.driver.AppleFDEKeyStore	28.30
com.apple.driver.AppleEffaceableStorage	1.0
com.apple.driver.AppleKeyStore	2
com.apple.driver.AppleUSBTDM	439.70.3
com.apple.driver.AppleMobileFileIntegrity	1.0.5
com.apple.iokit.IOUSBMassStorageDriver	140.70.2
com.apple.iokit.IOSCSIBlockCommandsDevice	404.30.2
com.apple.iokit.IOSCSIArchitectureModelFamily	404.30.2
com.apple.iokit.IOStorageFamily	2.1
com.apple.driver.AppleCredentialManager	1.0
com.apple.driver.KernelRelayHost	1
com.apple.iokit.IOUSBHostFamily	1.2
com.apple.driver.usb.AppleUSBCommon	1.0
com.apple.driver.AppleBusPowerController	1.0
com.apple.driver.AppleSEPManager	1.0.1
com.apple.driver.IOSlaveProcessor	1
com.apple.iokit.IOReportFamily	31
com.apple.iokit.IOTimeSyncFamily	680.15
com.apple.iokit.IONetworkingFamily	3.4
com.apple.driver.AppleACPIPlatform	6.1
com.apple.driver.AppleSMC	3.1.9
com.apple.iokit.IOPCIFamily	2.9
com.apple.iokit.IOACPIFamily	1.4
com.apple.kec.pthread	1
com.apple.kec.Libm	1
com.apple.kec.corecrypto	1.0

EOF
Model: MacBookPro13,3, BootROM MBP133.0247.B00, 4 processors, Intel Core i7, 2,7 GHz, 16 GB, SMC 2.38f7
Graphics: Intel HD Graphics 530, Intel HD Graphics 530, Built-In
Graphics: Radeon Pro 455, AMD Radeon Pro 455, PCIe
Memory Module: BANK 0/DIMM0, 8 GB, LPDDR3, 2133 MHz, 0x802C, 0x4D5435324C31473332443450472D30393320
Memory Module: BANK 1/DIMM0, 8 GB, LPDDR3, 2133 MHz, 0x802C, 0x4D5435324C31473332443450472D30393320
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x15A), Broadcom BCM43xx 1.0 (7.77.37.31.1a9)
Bluetooth: Version 6.0.7f10, 3 services, 18 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
USB Device: USB 3.0 Bus
USB Device: iBridge
Thunderbolt Bus: MacBook Pro, Apple Inc., 33.1
Thunderbolt Bus: MacBook Pro, Apple Inc., 33.1

"	wer32
16804	Kernel panic on Arch Linux guest	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
17063	Kernel panic on Other (Android-x86-4.4*) guest	VirtualBox 5.1.26	2017-09-08T06:57:07Z	2017-09-08T06:57:07Z	2017-09-08T06:57:07Z	Android-x86-4.4* kernel is producing a kernel panic. A screenshot and the log is provided. 	hwline
19089	Kernel Panic when running Ubuntu 18.04.03 inside VirtualBox 6.0.14 on macOS 10.14.6 host	VirtualBox 6.0.14	2019-11-16T16:56:27Z	2019-12-14T15:31:10Z	2019-12-14T15:31:10Z	While the installation of Ubuntu 18.04.03 went fine, a subsequent boot of this VM resulted in a kernel panic. See attached files.	Lars Sonchocky-Helldorf
10686	Kernel Panic: MONITOR/MWAIT	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
17355	Key fingerprint in downloads area cannot be verified	VirtualBox 5.2.0	2017-12-06T22:07:12Z	2017-12-06T22:07:12Z	2017-12-06T22:07:12Z	"https://www.virtualbox.org/wiki/Linux_Downloads

Lists two key fingerprints. However, there is no way to actually verify the fingerprints, even using methods from https://stackoverflow.com/questions/9607295/how-do-i-find-my-rsa-key-fingerprint - either it does not work, or a passphrase is requested.

Please list a method that works to verify the key fingerprints.

Thank you"	RoelV
13234	Key repeating does not work in OS/2 guest	VirtualBox 4.3.14	2014-07-24T05:40:52Z	2015-07-10T11:58:12Z	2015-07-10T11:58:12Z	"Hi/2.

Since 4.2.x, key repeating does not work in OS/2 guest.

How to reproduce,

    1. press a key
    2. press other key without releasing a previous key
    3. release a previous key

Then, a previous key is repeated, but a current key isn't repeated. Only first input is processed.

That is, if I press 'a' and press 'b' later, you can see the following.

    aaaaaab

'b' is not repeated.

I'm using OS/2 Warp 4.52, W4_104a kernel, and installed guest addition."	KO Myung-Hun
7646	Keyboard and mouseclick disabled at windows host with 'view login sceen at resume'	VirtualBox 3.2.10	2010-10-25T08:56:34Z	2010-10-25T08:56:58Z	2010-10-25T08:56:58Z	"If I use VirtualBox without the Guest drivers installed, I am experiencing a problem when I leave the VBox window focused and then don't use my computer for longer than 10 minutes, the time I've set before the screensaver activates. Because I've set the computer to prompt me to log in again, it shows up the login screen. But except moving my mouse around, I can't do anything; Ctrl+Alt+Del, pressing the power button shortly, nothing works and my only option is to press and hold the power button...
For some reason the log isn't available via Ctrl+L, but I think the problem is clear; when the login screen appears, VirtualBox is still stealing my keyboard and mouse clicks. Best solution for this in my opinion would be that VBox checks whether the user is still logged in each few seconds, or that the keyboard focus stops when the screensaver at the host becomes active."	Vbug
14302	Keyboard Caps lock, Num lock and Scroll Lock problems with Virtualbox 5.0	VirtualBox 5.0.0	2015-07-20T07:35:37Z	2018-06-12T00:40:49Z	2018-06-12T00:40:49Z	"Steps to reproduce the problem:
1) With no virtual machines running, activate Caps lock and/or Num lock and/or Scroll lock.
2) Start a virtual machines from saved state.
3) When I reduce the window of the virtual machine or I close it (by saving the state or by shut down the system) the state of Caps lock, Num lock and Scroll lock are deactivated.

Host: Windows 7 x64
Guest tested: Windows Xp SP3: Windows 7 x64 SP1; Windows 8.1 x64"	bmn
15767	"Keyboard capture often escapes to host when using the ""Windows"" key (Windows host, Linux guest)"	VirtualBox 5.1.2	2016-08-08T19:02:54Z	2016-08-08T19:02:54Z	2016-08-08T19:02:54Z	"I'm not quite sure when this started happening, but it happens to me a lot now (VBox 5.1.2).

My guest VM uses xmonad, and I set it so that using Win-1, Win-2, Win-3, switches desktops. Many times, when I am keyboard-captured, and I start switching desktops, one of them will suddenly escape and do stuff in my Windows host...

How to reproduce:
- Run a Linux guest, Windows host.
- Set it so that your keyboard is captured in the guest.
- Start mashing the Windows key with any other key, like 1, 2, 3, Left.

Effect:
- Within a few seconds of mashing, your host's Windows menu will pop-up.

I tested it with three different keyboards and two different machines."	Ptival
17668	Keyboard does not work in Linux Build 5.2.8 r121009	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
5076	Keyboard go crazy (miss map) after screen turn off and come back	VirtualBox 3.0.6	2009-09-25T01:35:08Z	2009-09-25T08:20:58Z	2009-09-25T08:20:58Z	"I just install the latest Virtualbox yesterday and i observed a very strange behavior. Below is the details description:

Virtualbox version: 3.0.6
Host: Windows 7 Pro RTM
Guest: Ubuntu 9.04
using seamless mode
Setting on Windows 7 to turn off the screen after 5 min (not sleep)

- Basically the problem is causing the host keyboard catching to go crazy. 
- Seem like the window key (special key) is lock up, so no matter what key i pressed, even is a single key (such as ""y"") but in the host window it seem like (window key + y).
- I try using VMware unity, it did not seem to have this problem. So i guess it is a bug. Has this bug being reported?"	ntyonline
15376	"Keyboard key sticks in ""down"" state, cannot be cleared"	VirtualBox 5.0.20	2016-05-02T01:25:06Z	2016-07-11T03:07:13Z	2016-07-11T03:07:13Z	"I am running Protel 99SE (a graphical electronic schematic/PCB capture suite) in a 32-bit mswindows guest.  The host OS is 64-bit Linux.  When in PCB mode one can select a ""component"" and use the arrow keys to move that component around.  If there is a long distance to move, holding down the applicable arrow key is common.  The component is redrawn after each button press event.

If the arrow key is held down for longer than about 5 seconds, the key ""sticks"" down.  Even after the key is lifted, the guest OS sees a continuous stream of key events (generated by keyboard autorepeat) and acts on these as best it can.  CPU usage by VirtualBox increases to 100%.  The guest OS becomes completely unresponsive to further mouse and keyboard events.  Pushing and releasing the arrow key (or any other key) has no effect.  The only way to recover is to use Virtualbox to send an ACPI power off event.  This is eventually seen by the guest OS and it shuts down normally.  Sending the event can take considerable time since VirtualBox's control window becomes very slow in the fault condition.

On one occasion during testing the ACPI event caused a dialog box to be displayed asking whether changes should be saved.  The keyboard focus rapidly cycled between the three buttons in a leftward direction.  Since it was the left arrow key that was pressed earlier on, this conclusively demonstrated that the key was stuck.  No mouse or keyboard events were being processed in this case either.

This problem does not occur in VirtualBox 4.1.x.  It was first observed in VirtualBox 4.2.x.  It is seen in every version of VirtualBox from 4.2.x on, up to and including 5.0.20 (all tested on the same 32-bit Linux host).  In the past we have worked around this by sticking with VirtualBox 4.1.x for this program.  However, since this no longer works on recent Linux hosts due to ongoing kernel changes there is a need to move to a later VirtualBox.  This key handling regression, however, is a show stopper.

The problem has been observed in both a win2k and winxp guest OS.  It has been observed with 32-bit and 64-bit Linux hosts.  It occurs with a USB wireless keyboard and a PS/2 wired keyboard (tested on the same machine).  The problem is not dependent on the graphics card (it can be replicated using onboard Intel graphics and PCIe AMD/Nvidia cards, all with the open source drivers).

In VirtualBox 5.0.x, capping the VM's CPU utilisation to 70% does not change the behaviour.

The problematic behaviour has not yet been observed in any other software.  It seems that Protel 99SE does something uncommon when handling these keyboard-induced moves.  A graphical redraw is done in response to every key down event, so maybe there's something about the way these are handled by Protel 99SE.
"	Jwoithe
8819	Keyboard layout 'Programmer Dvorak'	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
18590	keyboard losing functionality in guest	VirtualBox 6.0.6	2019-04-21T13:14:24Z	2019-04-21T13:14:24Z	2019-04-21T13:14:24Z	"host: Windows 10, guest: OS/2
HW: notebook, built in keyboard.

In the guest, I am regularily losing keyboard functionality. Once I hit the ""Windows"" key (which brings up the Windows menu) I regain keyboard functionality in the guest. The guest is set to automatically ""catch"" the keyboard. I did also have this problem with 6.0.4 but I did not have this problem with older VirtualBox versions."	lerdmann
19332	keyboard mapping problem on international MacBook Pro keyboard	VirtualBox 6.1.4	2020-02-21T18:22:34Z	2020-02-21T18:22:34Z	2020-02-21T18:22:34Z	"Keyboard mapping is complex. There are tons of components that have an opinion about what code needs to be mapped to what other code. But when using VirtualBox on MacBook Pro host with an Apple international ISO-like keyboard, something strange happens. The keys labeled ""§/±"" and ""`/~"" are not mapped correctly. It do not seem a problem of the guest operating system, it even shows when 'booting' a test virtual machine just into GRUB.

My keyboard layout on the host machine is correctly configured (Dutch) and working. 

The key labeled ""§/±"" (directly below the esc-key in the upper-right corner) assumingly produces the USB HID code 0x64 (""non US\|""). This  produces an macos key event with the apple key code 0x0a (and indeed leads to a ""§"" or ""±"" when typing on the host OS). The key labeled ""`/~"" (directly right to the left shift key) assumingly produces the the USB HID code 0x64 (""grave-tilde""). This produces an macos key event with apple key code 0x32 and indeed leeds to a '`' or '~' when typing on the host OS.

When typing these keys in a guest, I get '</>' for the '`/~' key and '`/~' when typing the ""§/±"" key.

Confusing indeed. The US ANSI-like MacBook Pro keyboard has no ""§/±"" key and the ""`/~"" is where the ""§/±"" is on an international MacBook Pro.

The problem is not caused by a mapping problem in Linux and/or X running inside the virtual machine. As said, the incorrect mapping is already visible in the GRUB console.

It can be _worked around_, of course, by fiddling with the Linux and/or X mappings, of course. But still I think there is a problem mapping the 'grave\tilde' key on a host MacBook Pro with international keyboard to the proper key in the guest."	duco
18537	Keyboard not working in Virtual box while installing ubuntu 18.04LTS on Windows10pro on Microsoft surface	VirtualBox 6.0.4	2019-04-02T22:27:31Z	2019-04-03T00:46:29Z	2019-04-03T00:46:29Z	"Installing Virutal box 6.0.4 was easily done, however when I set up the virtual machine with the USB multi touch tablet option (since the MSSurfasce laptop has a touch mouse pad and keyboard and a tablet modus) initially the mouse is captured, but once ubuntu wants me to enter which keyboard set up, I selected dutch (standard) and  tried the keyboard by entering some letters, from that moment on neither mouse nor keyboard works anymore in the ubuntu guest. Tried to use USB tablet option or the PS2/mouse option, still the same: it freezes once any keyboard key is pressed.
plz help 
"	BioMMM
9026	Keyboard problem on guest systems in w7 host	VirtualBox 4.0.8	2011-06-05T18:02:39Z	2011-06-10T04:53:11Z	2011-06-10T04:53:11Z	"I'm running VirtualBox 4.0.8 on 64-bit Windows 7 Home Premium with the latest updates.

After upgrading to 4.0.8: in both WinXP and Ubuntu 10.10 guests, which have worked for months, I find that characters typed on the keyboard produce random or sequential numbers. Holding the key down continually produces different numbers.

Holding down the ""Windows key"" while typing produces normal, correct results.

I attempted to go back to previous VirtualBox versions by downloading and installing old releases.  Going back as far as 3.2.1.2 did not fix the problem.  I suspect that this is because I haven't removed the defective software component and it is still being used by the older version I've installed.

I notice that there are other reports of this problem this week in the forum for Windows-hosted VirtualBox users, but no solutions. "	davidsmith
16734	Keyboard re-captured with no clear reason	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
18157	keys repeat (example: moving the cursor) will make shift or control key stick	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
18597	Large icons when i drag from small to big monitor	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
15878	LastNormalWindowPosition isn't correctly saved for a maximized window	VirtualBox 5.1.4	2016-09-02T18:10:59Z	2016-09-02T18:17:50Z	2016-09-02T18:17:50Z	"Up to VirtualBox 5.1.0 (don't know about 5.1.2), the LastNormalWindowPosition that was saved for a maximized window would contain the coordinates of the window prior to maximization. That is not the case anymore with VirtualBox 5.1.4. 

The way to reproduce:
1) start a vm with guest additions, wait for it to boot
2) resize the window. Let the guest resize as well
3) maximize the window. Let the guest maximize as well
4) save the machine state
5) start the machine from the saved state. It shoule start maximized
6) ""unmaximize"" the window. Expected behavior: window is resized to the same 
size as was in (2). But that doesn't happen (window stays full-screen size, but not maximized anymore)."	mskov
19396	Latest version (6.0.18) causes issues with DNS and VPN	VirtualBox 6.0.18	2020-03-12T12:52:09Z	2020-03-12T12:55:44Z	2020-03-12T12:55:44Z	"After I upgraded from 6.0.16 to 6.0.18 I started having network issues. After some futzing around and help from a friend I found a work around that forced me to be doing ipconfig /renew after connecting or disconnecting from our company's VPN. Just this morning I went back to 6.0.16 and the problem is gone which pretty much proves the latest version has broken something.

My host is Win 10 and my guest is Win 7."	WayneB64
18538	Launching Firefox crashes VM with The memory could not be read.	VirtualBox 6.0.4	2019-04-02T23:36:48Z	2019-04-03T00:49:12Z	2019-04-03T00:49:12Z	"Installed Virtual Box 6.0.4 on Windows 10 1803 64 bit. Installed Red Hat Linux
6.10 Guest OS. 

After all the updates to Firefox and OS, launching the firefox
gives the message

---------------------------
VirtualBoxVM.exe - Application Error
---------------------------
The instruction at 0x00007FFBEA84E889 referenced memory at 0x000000000000001C. The memory could not be read.


Click on OK to terminate the program
---------------------------
OK   
---------------------------

Please fix this issue. 
"	ketan
21074	launchVMProcess via MSCOM -- environment changes parameter type mismatch ambiguity	VirtualBox 6.1.30	2022-08-24T04:28:06Z	2022-08-24T04:28:06Z	2022-08-24T04:28:06Z	"
When calling launchVMProcess() through MSCOM by VBScript, JScript, Python, etc.. they all end up with a ""type mismatch"" error. After some process of limitation, it might be the third and final parameter the cause of it: the list of environment changes.

According to the source in c++, it supposed to accept a string array, but the source wants a specific type of array: a string (utf-8) array. It doesn't like variant arrays (I believe they're called safearrays?). Unfortunately, because the samples or examples provided in the SDK doc is too outdated -- i.e. using openRemoteSession rather than launchVMprocess -- I'm lost as to how to pass something to that third parameter that'll satisfy VirtualBox MSCOM.

I was referring to the definition of launchVMProcess() here:
//trunk/src/VBox/Main/src-server/MachineImpl.cpp#L7814

If there are new steps that weren't documented, they should be updated accordingly; especially the SDK doc.

It's worth mentioning that the issue from Ticket #20750 might be related to what was mentioned here."	jprogman
15165	"Leaving Full-Screen Mode resizes guest with ""Auto-resize Guest Display"" off"	VirtualBox 5.0.14	2016-02-22T01:33:49Z	2016-06-24T15:15:27Z	2016-06-24T15:15:27Z	"In older versions (when Auto-resize Guest Display could be toggled with Host+G), this worked fine, but when this shortcut toggle was removed, this bug was introduced.

To reproduce:

1. Leave full-screen mode if necessary.
2. Enable ""Auto-resize Guest Display"".
3. Guest resolution should change to match window.  If not, resize the window.
4. Enter full-screen mode (Host+F).
5. Guest resolution should change to match host resolution.
6. Use Host+Home to disable ""Auto-resize Guest Display"".
7. Exit full-screen mode (Host+F).
8. Notice that the guest resolution changes to match the window, but it should not.
"	Marc
18742	Left and right modifier keys mirrored on Mac OS X 10.14.5 (Mojave) as host	VirtualBox 6.0.8	2019-07-03T13:18:14Z	2019-07-17T08:26:35Z	2019-07-17T08:26:35Z	"Repro steps:
1. Connect external keyboard
2. Under System Preferences --> Keyboard --> Keyboard --> Modifier Keys
Change option to command and command to option
3. Start VirtualBox
4. Under Preferences -->  Input --> Virtual Machine 
Set ""Host Key Combination"" press command + option to the left 
Note:  it says right command + right option

Impact: on Windows guest running a non US keyboard, e.g. Swedish layout, the option key is now alt gr and not alt

Same thing on 5.2.30

Might be something in Mac OS which also affect Emacs: http://emacs.1067599.n8.nabble.com/bug-34984-ns-right-command-modifier-has-influence-to-left-td478781.html"	Lars
16296	Left half portion of the guest's widescreen desktop becomes unresponsive to left mouse button clicks	VirtualBox 5.1.10	2016-12-16T14:35:44Z	2022-11-30T22:57:40Z	2022-11-30T22:57:40Z	"I am not sure what causes this or how to manually reproduce this behavior; otherwise, I would have reported this issue a long time ago.  Almost every day (and after no particular amount of up-time), the left half of my Linux desktop becomes unresponsive to left mouse button clicks.  Left-mouse button clicks do continue to work on the right half portion of the screen.  Actually, it is not the entire left-half portion of the screen that is affected; more like approximately the left two/fifths (left 40%) portion of the entire screen.

This problem is very annoying because smaller windows running in the affected portion of the screen cannot be interacted with or dragged over to the responsive side of the screen.

When this problem occurs, nothing I have tried so far (e.g. restarting the window manager) will correct it.  I am forced to close out (as best as I can) all the running applications in the Linux guest and then reboot the guest OS.

I have no idea what is causing this.  A faulty screensaver timeout process?  Your guess is as good as mine.

Some specific details of my setup:

* Guest OS: 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u2 (2016-10-19) x86_64 GNU/Linux
* Guest window manager: Openbox 3.5.2
* Host OS: Windows 7 Enterprise 64-bit
* Host configuration: dual identical DELL P2414H widescreen monitors (1920x1080 resolution); VirtualBox is running as a maximized window on my right-side monitor

I believe that this strange behavior has been happening as far back as version 5.0.20 of Virtual Box."	Tony DeFusco
8070	Less reliance on absolute paths in VirtualBox	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
18447	libffi-d78936b1.so.6.0.4: cannot open shared object file: No such file or directory	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
14195	Linked clone does not keep saved state	VirtualBox 4.3.28	2015-06-15T17:18:13Z	2015-06-15T17:49:57Z	2015-06-15T17:49:57Z	"When trying to create a link clone of a VM which has live snapshot and has been restored to one of them, the saved state is not carried accross to the cloned VM.

Simple steps to reproduce:

Create, register & start an empty VM. Wait until the boot failure screen.
{{{
vboxmanage createvm --name test --register
vboxmanage startvm test --type gui
}}}
Take a live snapshot, power off the VM, restore the snapshot, check the state.
{{{
vboxmanage snapshot test take base
vboxmanage controlvm test poweroff
vboxmanage snapshot test restorecurrent
vboxmanage showvminfo test | grep State
}}}
State is now ""Saved""
Create a linked clone and check its state:
{{{
vboxmanage clonevm test --name test-clone --snapshot base --mode machine --options link --register
vboxmanage showvminfo test-clone | grep State
}}}
Reported state if ""powered off"" instead of ""Saved"".
Starting the linked clone brings us to the initial VBox boot and not to the failed boot screen of the parent VM."	Max D
13851	Linked clone not created in group subdirectory	VirtualBox 4.3.20	2015-02-18T01:14:24Z	2015-02-18T01:14:24Z	2015-02-18T01:14:24Z	"I have several VMs in a group.
I create a linked clone of one of the VMs in the group.
The linked clone VM appears in the group in the VirtualBox Manager GUI, but the directory containing the new VM does not appear in the group subdirectory, as I would expect it to.

Eg given virtual machines in groups (named ""Beta A testing"", ""Beta B testing""), with both groups and directory listing like this:
{{{
\---Virtual machines
    +---Beta A testing
    |   +---Version 10.1 SP2 updated to SP3 Beta A
    |   +---Version 10.1 SP3 Beta A
    |   +---XP Version 10.1 SP2 updated to SP3
    |   \---XP Version 10.1 SP3
    +---Beta B testing
    |   +---SP2 updated to SP3 beta B
    |   +---SP3 beta B
    |   +---XP SP2 updated to SP3 beta B
    |   \---XP SP3 beta B
    +---Build
    +---Version 10.1 SP1
    +---Version 10.1 SP2
    \---Windows 7
}}}
I made a linked clone of ""SP3 beta B"", called SFX-23779. The new directory SFX-23779 (containing the logs and snapshops for the new VM) appeared under ""Virtual machines"", whereas I expected it to appear under ""Beta B testing"" for consistency with the other grouped VMs."	m6477
14795	Linux (Centos-6 x64) guest regularly crashes	VirtualBox 5.0.6	2015-11-06T08:44:00Z	2015-11-06T09:21:47Z	2015-11-06T09:21:47Z	"Centos-6 x64 guest regularly crashes after several days of uptime. No any problems with adjacent windows VM (Windows Server 2003 x86).

VirtualBox: 5.0.6r103037 (same problem with many previous releases).
Host: Windows Server 2008 x64, with latest updates, 24 GB RAM.
Guest: Centos-6 x64, with latest updates, 2 GB RAM, no guest additions.

Kernel errors examples:

kernel BUG at mm/vmscan.c:1083! [[BR]]

invalid opcode: 0000 [#1] SMP[[BR]]

BUG: soft lockup - CPU#0 stuck for 67s! [updater:31994][[BR]]
"	Victor Abramoff
19688	Linux 5.7.x + VBox 6.1.10 driver install failure	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
20454	Linux cannot Log  user in with visual interface	VirtualBox 6.1.22	2021-07-12T12:11:04Z	2021-07-12T12:11:04Z	2021-07-12T12:11:04Z	"Since the 6.1.22 update I cannot log in to any visual interface anymore (Tested in Ubuntu 20.04.2 LTS ). 

CLI login is allowed and Linux console is fully functional but login attempts through the visual interface results in ""Oh no! Something has gone wrong"" screens. 

I have tested the same image exported to VMware Workstation 16 and works flawlessly.

Attached log file"	fizcris
16992	Linux filesystem through share folder will be data crash	VirtualBox 5.0.40	2017-08-08T18:53:35Z	2017-08-10T20:44:24Z	2017-08-10T20:44:24Z	"Host Windows 7, Phy 16 GB RAM[[br]]
Guest Linux Centos 6.8, Virtual 3 GB RAM[[br]]
/share is share folder on Windows NTFS.[[br]]
[[br]]
Reproduce command:[[br]]
*---------- Start[[br]]
dd if=/dev/zero of=/share/tmp_fs bs=1M count=300[[br]]
mkreiserfs -f /share/tmp_fs[[br]]
mount -o loop /share/tmp_fs ~/x[[br]]
touch ~/x/mark (or copy anything to there)[[br]]
umount ~/x[[br]]
*---------- End[[br]]
[[br]]
Now, if you re-mount tmp_fs, you will found nothing in filesystem, and if you fsck on it, it will show filesystem broken.[[br]]
[[br]]
On 5.0.28, all thing are fine[[br]]
On 5.0.40 and above 5.1.x (Note: I don't try on 5.0.30 - 5.0.38), you will catch the bug.[[br]]
"	C-MIKE
15291	Linux Gest - Console black in Full Screen	VirtualBox 5.0.16	2016-04-04T11:55:38Z	2016-04-04T11:55:38Z	2016-04-04T11:55:38Z	When running Debian (current version 8.3) on a Windows host (Windows 8.1 Pro) in fullscreen switching from Gnome desktop to one of the other ttys (e.g. Hostkey-F1 to get tty1) results in a black screen. Doing the same in window mode (but maximized) does work fine.	jeansen
21007	Linux Guest / No Audio in VBox >= 6.1.24	VirtualBox 6.1.24	2022-06-24T15:12:55Z	2022-06-24T15:12:55Z	2022-06-24T15:12:55Z	"When using VirtualBox >= 6.1.24 (Windows 10 host, Linux Mint Mate 20.2 guest), audio output does not work. It works with VirtualBox <= 6.1.22.

Audio players, video players, browsers, all seemingly work as intended (e.g., video is shown), just no sound.

I tried the following fix: added the line ""options snd-intel8x0 ac97_clock=48000"" to the file ""/etc/modprobe.d/alsa-base.conf"" .

This brought partial improvements: Video is now played with sound -- no matter whether from the internet or my own local .mp4 files. The test ""aplay /usr/share/sounds/alsa/Front_Center.wav"" works. However, my own .mp3 and .wav files, ripped from CD, still don't produce any output.

I also noticed that when I do ""aplay /usr/share/sounds/alsa/Front_Center.wav"" and immediately interrupt it with ctrl-z, audio output ''does'' work. So it seems this aplay provides some initializations that normally are missing.


Attached two log files: One before applying the above-mentioned fix, one after. There are Audio errors in there; however, I have no idea what can be done about them."	aabb
20393	Linux Guest [vmwgfx] *ERROR* SVGA device lockup	VirtualBox 6.1.18	2021-06-10T19:29:19Z	2021-07-12T16:35:51Z	2021-07-12T16:35:51Z	"Hi,

I'm running a Linux guest on a Windows host and every so often the display will lock up. It's happened maybe 3 times in the last month and I haven't been able to correlate it with anything specific.

By lock up, I mean that it appears that the display stops updating. Input (at least mouse events) appear to work, but when it starts to lock-up, the display does not update in response to any input events until a few seconds go by. Pretty quickly, this behavior degrades to the point where it appears completely frozen and no more updates occur.

I can ssh in from my host and interact, so it seems it is just a display driver issue. dmesg shows the following:

[70545.554435] [drm:vmw_fallback_wait [vmwgfx]] *ERROR* SVGA device lockup.
[70548.553727] [drm:vmw_fallback_wait [vmwgfx]] *ERROR* SVGA device lockup.
[70558.765785] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:38:crtc-0] flip_done timed out
[73420.314255] [drm:vmw_fallback_wait [vmwgfx]] *ERROR* SVGA device lockup.
[73423.314445] [drm:vmw_fallback_wait [vmwgfx]] *ERROR* SVGA device lockup.
[73433.384206] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:38:crtc-0] flip_done timed out

Not sure what else to check, but can do whatever is needed to debug next time it happens. Just let me know.

I also see these messages appearing occasionally before hand, but they look to occur fairly regularly in the log without any other symptoms, so I don't know if they are related or not.

[54955.536381] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.

I can provide more detailed hardware info (it's a Dell XPS 9500 using an i7-10857H w/ 32GB), os specifics (Win10, Ubuntu 20.04), and system config (I run 2 external displays on which I use my linux guest) or whatever else is needed.

I will attach my VBOX.log

Thanks for any help,
Brian

"	brian-vbox
20038	Linux guest GUI freeze or full VM hang after not being interracted with for some time	VirtualBox 6.1.16	2020-11-15T14:48:40Z	2020-11-24T11:17:52Z	2020-11-24T11:17:52Z	"
== Linux guest GUI freeze or full VM hang after not being interacted with for some time ==


'''Terms in use:'''

 - '''GUI Freeze''': The ''GUI inside the VM, XFCE, is not responsive''. ''The VM is still active, as can be seen by the activity indicators'' (disk, network, etc). A console can be brought up (ctl-alt-F2 for example), logged into, and all of my users processes killed with ""pkill -u myusername"". This causes the GUI to become responsive, giving me the fresh login screen. This is not optimal, however, at least it's a clean shutdown of programs. Alternately I can perform an ACPI shutdown and the system will shut down cleanly.
 
 - '''Full VM Hang''': The ''GUI inside the VM, XFCE, is not responsive. The VM is NOT active, as the activity indicators are inactive.'' A console can NOT be brought up (ctl-alt-F2 for example). Using the soft keyboard and trying the same has no effect. Sending ACPI shutdown signals has no effect. At the same time as this, ''sometimes the virtualbox GUI for managing the virtual machines hangs''. This can only be resolved by manually killing off the VM and anything virtualbox related, and rebooting the host.
 

'''VirtualBox information:'''

 - Version 6.1.16
 - Extension pack 6.1.16

'''Host information:'''

 - Windows 10 pro
 - Intel 4GHz corex CPU
 - 128GB RAM
 - Samsung SSD Disks
 - Nvidia GeForce RTX 2080 Ti using Nvidias drivers

'''Guest information:'''

 - Linux Mint 20
 - GUI: XFCE
 - Guest additions: 6.1.16
 - Virtual RAM: 9240 MB
 - Virtual processors: 6
 - Acceleration: default
 - Display: 128MB RAM, VMSVGA, Enable 3D Acceleration
 - Storage: SATA: Disk 1: Linux_Mint_19.vdi | Virtual size: 300GB | Actual size: 91GB
 - Storage: SATA: Disk 2: Linux_Mint_19_swap.vdi | Virtual size: 16GB | Actual size: 9GB
 
===

'''Issue Details:'''

Frequently after being away at least 10 or 15 minutes the guest will either experience a GUI freeze (see above for a description), or a full VM hang. The first situation can be recovered from, however in the second situation nothing can be done. For this reason I take frequent snapshots while the VM is powered on so that I can use them to restore from as setting everything back up again and again and again gets frustrating.

===

'''Solutions attempted:'''

Disable the screen saver / screen lock etc inside of the guest: The prior night I did this and returned in the morning to find that a full VM hang had taken place shortly after I had left to go to sleep. I know when it took place because of the time shown in the GUI (stuck).

Restore the latest snapshot, cleanly shut down, and power the VM on again: The issue still frequently occurs.

Disable 3D Acceleration: The issue still frequently occurs.


===

'''Logs:'''

''Note: For each of the logs, I prefix a string like ""round1"" and then refer to them that way. Please be sure to refer to them that way to me as well.''

The last log in round1 Vbox.log for this VM is: 
{{{
14:38:47.761976 GUI: UIMediumEnumerator: Medium-enumeration finished!
}}}


The full round1 Vbox.log will be attached. In addition I'll attach round1 VBox.log.1 , VBox.log.2 and VBox.log.3 .

round1 VBoxHardening.log doesn't really make sense to me so I'll just attach it.

Windows event log upon shutting down the host for round1, since it was both a full VM hang AND the virtualbox management interface became unresponsive:

{{{winlog.event_data.Caption:
    VirtualBox: VirtualBox.exe - Application Error
message:
    '''Application popup: VirtualBox: VirtualBox.exe - Application Error : The instruction at 0x0000000061F0162F referenced memory at 0x0000000000000008. The memory could not be read. Click on OK to terminate the program'''
agent.hostname:
    MY-SYSTEM-NAME
agent.name:
    MY-SYSTEM-NAME
agent.id:
    130ce1c1-0e0a-419c-9b7f-f4bf70a6c377
agent.type:
    winlogbeat
agent.ephemeral_id:
    002ca6d2-1396-44b0-9a31-ec9b95be97bc
agent.version:
    7.9.0
winlog.record_id:
    2,049
winlog.computer_name:
    MY-SYSTEM-NAME
winlog.process.pid:
    16,852
winlog.process.thread.id:
    2,196
winlog.event_id:
    26
winlog.task:
winlog.provider_guid:
    {47bfa2b7-bd54-4fac-b70b-29021084ca8f}
winlog.channel:
    System
winlog.event_data.Message:
    '''The instruction at 0x0000000061F0162F referenced memory at 0x0000000000000008. The memory could not be read. Click on OK to terminate the program'''
winlog.api:
    wineventlog
winlog.provider_name:
    Application Popup
winlog.opcode:
    Info
winlog.user.identifier:
    S-1-5-18
winlog.user.domain:
    NT AUTHORITY
winlog.user.name:
    SYSTEM
winlog.user.type:
    User}}}

===

'''Follow up:'''

What more can I provide to assist?"	Fieldy
16071	Linux Guest is aborting after some time of inactivity (when afk)	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
21405	Linux guest on Windows 10 host does not start in seamless mode	VirtualBox-7.0.4	2023-01-12T14:25:59Z	2023-01-12T14:25:59Z	2023-01-12T14:25:59Z	"When the Linux host is started, it ''always'' starts in windowed mode, not in seamless mode. I must manually switch to seamless. When I shut down the machine in seamless mode and restart it, I expect it to restart in that mode, as it did in former versions of VirtualBox (6.x).

"	reibi
15560	Linux guest on Windows 10 host keeps freezing	VirtualBox 5.0.24	2016-06-30T07:27:56Z	2016-11-15T22:38:46Z	2016-11-15T22:38:46Z	"I have a current Debian testing VM running on a current Windows 10 host.
It started to freeze very frequently with 5.0.22. 5.0.23 r108298 (and subsequently 5.0.24) reduced the frequency of the freezes, but did not quite eliminate them.

I experienced this freeze while running Knoppix 7.6.1 on 5.0.23 r108298 as well.

The kernel started out as a 4.5 version and was upgraded to 4.6 recently (shortly before VBox 5.0.24 was released but after my switch to 5.0.23 r108298).

It seems likely that this ticket is related to #15529, as the freezes started happening with the same release and the ACPI code change revert seems to have helped (reducing the frequency of the freeze from one every couple of minutes to once or twice a day).

The symptoms for the 5.0.24 freeze were:
* While actively working with the VM, it suddenly stopped responding.
* Most of the video was frozen, with the notable exception of an open but not focused tab in Chromium - the ""page is loading"" animation remained functional.
* The VM stopped responding to SSH login attempts.
* The VM stayed this way for about 15 mins, until I forcibly turned it off.
* I tried to see whether exiting fullscreen mode would make a difference - it did not.
* After the freeze, the VM displayed no apparent disk or CPU activity.

Unfortunately, neither my notebook not my keyboard have status indicator leds, so I cannot tell whether a kernel panic occurred."	ancow
19131	linux guest os does not recover from host sleep - Win 10 host	VirtualBox 6.0.14	2019-12-04T18:18:27Z	2022-09-15T08:26:09Z	2022-09-15T08:26:09Z	"Since 6.x, Ubuntu 18.04 guest does not recover from host (Win 10) going to sleep for around 30 min. 

If I send the host OS to sleep and immediately (within 5 min), everything is fine.

After a longer sleep, say 20 min, I get varying results:

1) the guest OS seems to have rebooted and I arrive at the login window.  My prior running apps and consoles are gone from the desktop.

2) the OS hangs, showing the login screen.  Mouse and keyboard are not working.  Software reboot (send a shutdown signal) does not work.  Must reboot the guest os. 


My computer is recovering from sleep mode and not hibernate mode.

This seems to have started since 16.x.  I created the guest OS in 15.x.
"	eyn
19913	linux guest processes terminated after win10 host sleep	VirtualBox 6.1.14	2020-09-24T14:48:43Z	2020-09-24T14:48:43Z	2020-09-24T14:48:43Z	"(similar to https://www.virtualbox.org/ticket/19131)

Windows 10 1904 host
Ubuntu 20.04-LTS guest (created with 6.1.10 IIRC)
virtualbox-6.1.14 with 6.1.14 extension pack

situation occurs when host goes into sleep on its own (my power settings are set never to hibernate when on line power)

result:
- running apps and windows in guest are all exited
- docker containers are exited
- system uptime seems to be correct

in attached log, the situation likely occurred starting at ""07:39:12.135290"" as this delta from the log opened time corresponds to the time docker reports my container exited
"	DanielH_
20971	Linux guest VM hangs after upgrading VirtualBox to 6.1.34	VirtualBox 6.1.34	2022-06-07T18:32:33Z	2022-06-07T18:32:33Z	2022-06-07T18:32:33Z	"I'm running VirtualBox on Windows 10.
I've recently updated VirtualBox from 6.1.30 to 6.1.34.
My Ubuntu 20.04 VM has hung during an upgrade to Ubuntu 22.04.
I had to force close the VM. This has caused the system to become unbootable, so I've installed Ubuntu 22.04 from scratch.
After installation the system started hanging during boot or just after fresh login. The hanging was so hard that the guest system became unusable - I had to force close it.
I've downgraded VirtualBox to 6.1.32, but the problem persisted.
The problem went away after a second downgrade to version 6.1.30.

I'm using a default hypervisor in the VM so it's probably Hyper-V."	Przemysław Kulczycki
20030	linux guests cannot be restored	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
17257	Linux host + Windows 10 + client tools results in minor display corruption	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
18403	Linux Host and Windows guest both consume same input event (windows/action key)	VirtualBox 6.0.4	2019-02-01T07:25:55Z	2019-02-07T09:08:40Z	2019-02-07T09:08:40Z	"Windows 10 Host
Linux Guest (Fedora 29 Workstation) 

Steps to reproduce:
Boot Fedora guest,
Press Windows Key

Observed behavior:
Windows start menu is opened and Gnome Activities is triggered at the same time

Expected behavior:
Only the guest receives the key event and the Gnome Activities is triggered without triggering the Windows start menu

Note:
This Problem did not exist in VirtualBox 5. "	nopaste
15525	Linux host hangs during compiling	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
15090	"Linux host running ""perf top"" kills Virtualbox vm's (VERR_PGM_INVALID_CR3_ADDR)"	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
9092	Linux host Windows XP guest virtual drive gets corrupted when installing service pack	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
16349	Linux host, Windows 10 guest: USB headset functions intermittently with Skype	VirtualBox 5.1.12	2017-01-03T13:13:02Z	2017-01-03T13:13:02Z	2017-01-03T13:13:02Z	"My system is the following.
Hardware: Lenovo ThinkPad T460
OS: Linux host (kernel 4.8.15, distribution Fedora 25) with Windows 10 guest
VirtualBox: 5.1.12 with extension packs on both ends of the same version
Additional hardware: Logitech USB headset H650e connected via xHCI USB 3.0 controller
Additional software: Skype 7.3.80.105 under Windows 10 guest

Symptoms
- during an audio call via Skype, the microphone of the USB headset will cease to function
- the Skype connection bars turn red and a warning appears that no microphone is connected
- the behaviour sometimes corrects itself but can not be predicted and is hard to reproduce

My VBox.log is attached."	aljperso
18180	Linux host, Windows and Linux guests: CPU does not exceed 1.99GHz	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
18634	Linux host, Windows guest: screen corruption; and once the pointer changes it does not change back	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
18017	Linux host, Windows guest: screen resolutions limited and fix messes up the pointer	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
18810	Linux Host: High CPU usage with idle Windows 10 guest	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
19853	Linux instalation during boot instalation ISO	VirtualBox 6.1.10	2020-09-03T11:01:37Z	2020-09-03T11:01:37Z	2020-09-03T11:01:37Z	critical error occured while running the virtual machine. The issue is probably related to windows 	jtach
15164	Linux kernel 4.4.0-7.22 (amd64, Ubuntu Xenial) locks up if not using serial output		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
20129	Linux kernel version 5.10 - we need changes	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
18076	Linux Mint 19 guest using Touch Keyboard in Windows 10 host not working with some keys	VirtualBox 5.2.20	2018-10-24T13:17:02Z	2018-10-26T00:42:48Z	2018-10-26T00:42:48Z	I am having problems with Windows 10 the full touch keyboard not the basic one with the arrow keys, Shift and space bar not working and it is in USB Tablet mode. The strange thing is that basic touch keyboard work with space bar, but arrow keys still not working.	Motoko
19776	Linux Mint 20 Vir Box 6.1 cant turn off Hardware Virtualization	VirtualBox 6.1.10	2020-07-28T16:56:31Z	2020-07-28T16:56:31Z	2020-07-28T16:56:31Z	"Can not turn off Hardware Virtualization and or make changes in settings.
Will not run and thing created."	Willie46151
19681	Linux Mint 32-bit Guest will not fully restart on Mac OS X Catalina host after installed Guest Additions	VirtualBox 6.1.10	2020-06-25T18:25:12Z	2020-06-30T14:37:01Z	2020-06-30T14:37:01Z	"After I installed the Guest Additions on my 32-bit Linux Mint virtual machine, the VM Guest will not restart properly. I can enter my user password, but then the operating system won't finish booting to the desktop, and it appears to hang on a blank screen. I left the Guest machine sitting for ~ 20 minutes on the blank screen before I give up and force it to stop.

Approximate steps
- Create a blank virtual machine: Ubuntu 32-bit, ~3.5GB Memory, 30GB hard drive (VDI, dynamic)
- Start the virtual machine, when prompted insert the Linux ISO
- Complete the operating system installation
- When prompted, remove the ISO from Optical drive and restart VM 
- Install operating system updates in Synaptic and restart VM
- Insert the Guest Additions CD and run the installer
- After Guest Additions finishes installation, restart the VM
- Enter the user password & Wait for the machine to finish boot

Observed; the Guest machine just appears to hang on blank black screen. Eventually give up waiting, and click the red dot to close Guest window and force shut down.

In case I made a mistake, I tried deleting & recreating the virtual machine guest again, but same issue occurs again after install Guest Additions.

Additional machine details:
- Host is Mac OS X Catalina 10.15.5
- VirtualBox Version 6.1.10 r138449 (Qt5.6.3)
- Oracle VM VirtualBox Extension Pack v6.1.10r138449 previously installed
- Guest installed with Linux Mint 19.3 Cinnamon 32-bit"	keffie
19408	Linux panic with a 'not-present page' when rebooting resumed VM	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
21310	Linux/arm64 guest	VirtualBox-7.0.4	2022-11-24T13:20:48Z	2022-11-24T13:20:48Z	2022-11-24T13:20:48Z	"hi,
please add support for guest ARM64 architecture at least with Linux (and maybe Android) as OS.

As so, as example, we can run a RaspberryOS/arm64 as guest."	Valerio Messina
19383	List virtual machines in specific group	VirtualBox 6.1.4	2020-03-06T20:09:16Z	2020-03-06T20:09:16Z	2020-03-06T20:09:16Z	"Please, implement command line option to list VMs from specific group.

Something like this:
VBoxManage list [--long|-l] [--sorted|-s] vms --group ""my_vm_group"""	1ns
18746	Live snaphot cloning (VBoxManage clonevm) fails when basefolder is SMB share	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
19414	ljmp (mem48) fails	VirtualBox 6.1.4	2020-03-18T19:02:47Z	2020-08-17T10:01:07Z	2020-08-17T10:01:07Z	"Consider the source code here:

https://github.com/joyent/ipxe/blob/master/src/arch/x86/image/multiboot2_entry.S#L65

Hardware and VMware execute that instruction (long-jump into 32-bit space using a 48-bit segment/addr pair) fine and move the machine into 32-bit mode.  VBox does not.

I'm attaching a VBox.log file as well."	danmcd
8830	Lock screen removes all clipboard data	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
20125	Loggin vboxdrv.sh fills syslog	VirtualBox 6.1.16	2021-01-12T23:54:12Z	2021-01-26T18:02:41Z	2021-01-26T18:02:41Z	"In Debian 10 the script vboxdrv.sh fills syslog with logs.

Looking in /var/log/ you can see the size of the files:

{{{
...
-rw-r-----   1 root              adm             103M gen 13 00:39 syslog
-rw-r-----   1 root              adm             2,0G gen 13 00:00 syslog.1
-rw-r-----   1 root              adm              20M gen 12 10:02 syslog.2.gz
...
}}}


The log is full of an neverending sequence of this writing:


{{{
Jan 13 00:42:17 Bisonx vboxdrv.sh[974]: Password non valida
Jan 13 00:42:17 Bisonx vboxdrv.sh[974]: La chiave per il Secure Boot inserita non è valida. La password utilizzata deve
Jan 13 00:42:17 Bisonx vboxdrv.sh[974]: contenere da 8 a 16 caratteri.
Jan 13 00:42:17 Bisonx vboxdrv.sh[974]: Inserire una password per configurare il Secure Boot UEFI.
Jan 13 00:42:17 Bisonx vboxdrv.sh[974]: Questa password verrà usata dopo il riavvio per confermare l'autorizzazione per
Jan 13 00:42:17 Bisonx vboxdrv.sh[974]: una modifica allo stato del Secure Boot.
Jan 13 00:42:17 Bisonx vboxdrv.sh[974]: Password per Secure Boot UEFI:
Jan 13 00:42:17 Bisonx vboxdrv.sh[974]: Inserire nuovamente la stessa password per verificare di averla digitata
Jan 13 00:42:17 Bisonx vboxdrv.sh[974]: correttamente.
Jan 13 00:42:17 Bisonx vboxdrv.sh[974]: Reinserire la password per verifica:
Jan 13 00:42:17 Bisonx vboxdrv.sh[974]: Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111.
Jan 13 00:42:17 Bisonx vboxdrv.sh[974]: Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111.
}}}

A clean and translated version is:

{{{
Invalid password. The Secure Boot key you entered is invalid. The password used must contain 8 to 16 characters.
Please enter a password to configure UEFI Secure Boot.
This password will be used after reboot to confirm authorization for a change in Secure Boot status.
Password for Secure Boot UEFI:
Enter the same password again to verify that you have typed it correctly.
Re-enter the password for verification:
Jan 13 00:42:17 Bisonx vboxdrv.sh[974]: Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111.
Jan 13 00:42:17 Bisonx vboxdrv.sh[974]: Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111.
}}}

I'm aware about the problem regarding the kernel signature, but I point out that this problem is about too intense logging and could fill the whole disk of some machines.  It would be enough if the warning did not repeat 23 times per second, as it does now.

I think that this problem, of which I am unable to give any indication on how to reproduce it, occurred after a bios firmware update.

Thank you,
Riccardo"	rickyx
21275	Login issue	VirtualBox-7.0.2	2022-11-15T16:53:58Z	2022-11-15T16:53:58Z	2022-11-15T16:53:58Z	"My email is heine.ferreira@gmail.com.
I used it as a username.
After I did a password reset it asked to change my nickname.
It won't allow me to change my nickname and therefore I can't log into the virtualbox forum.
There must be something wrong with my profile, but I know what my password is.
"	sreenath
20057	long loading initial ramdisk virtualbox	VirtualBox 6.1.16	2020-11-21T16:55:07Z	2020-11-21T16:55:07Z	2020-11-21T16:55:07Z	"Hello, here is my system : 
Host : Windows 10 x64 16GB RAM SSD 256
Guest: Ubuntu 20.04 x 64
The guest start but the boot time is very slow.
it takes long time here : long loading initial ramdisk virtualbox about 50 s

Any help?"	Spaccabbomm
11976	long paths  (>260chars) cannot be created using a host:win + guest:linux setup	VirtualBox 4.2.16	2013-07-19T17:23:19Z	2018-02-23T21:23:47Z	2018-02-23T21:23:47Z	"From https://github.com/mitchellh/vagrant/issues/1953 and https://github.com/isaacs/npm/issues/3670, VirtualBox on windows cannot generate paths longer than ~260 characters on windows, despite windows supposing UNC paths to allow for ~32k character paths. This means that using things like Vagrant, with a project that uses node/npm, is blocked by VirtualBox because node module dependencies (but also just any deeply nested software project being tested in a virtualbox VM) end up having paths that are longer than the standard 260 character limit.

Somewhere, VirtualBox is not communicating the correct error from host to guest OS; it would be extremely useful if this was solved somehow (allowing UNC paths by default? perhaps something else altogether)"	Urrich
9381	Lost keyboard control	VirtualBox 4.1.0	2011-08-05T10:19:18Z	2011-08-05T10:19:18Z	2011-08-05T10:19:18Z	With my external monitor plugged in and my external keyboard plugged into the USB hub in the monitor, I started a Windows 7 VM.  Everything worked great. Then I put the laptop to sleep, closed the screen, unplugged everything and took the laptop away.  opened it up again and the VM wouldn't respond to input from the built-in keyboard.	David Abrahams
14291	Lots of error entries in VBoxSVC.log	VirtualBox 5.0.0	2015-07-17T09:50:44Z	2020-09-08T05:33:38Z	2020-09-08T05:33:38Z	"Looking into VBoxSVC.log I find lots of error entries.

When starting the VM Virtualbox Manager GUI, the first entries appear (time stamps 00:00:00 in attached file)

Then, related to time stamps beginning with 00:18:59 I executed the following commands, that are embedded in a script:
{{{
vboxmanage createvm --name AMHS-Tester --groups ""/AMHS-CentOS-Eval"" --ostype RedHat_64 --register --basefolder ""E:\VMs\Eval-Testsuite\AMHS-CentOS-Eval\VMs""
vboxmanage modifyvm 5cb950aa-86e4-4f31-8a2b-9d0b580e3e4c --memory 3072 --boot1 dvd --boot2 disk --boot3 none --cpus 8 --vram 12 --audio pulse --usb on --usbehci on
vboxmanage createhd --filename ""E:\VMs\Eval-Testsuite\VMs\AMHS-CentOS-Eval\AMHS-Tester\AMHS-Tester"" --size 16384 --format VMDK --variant Split2G
vboxmanage storagectl 5cb950aa-86e4-4f31-8a2b-9d0b580e3e4c --name IDE-Controller --add ide
vboxmanage storageattach 5cb950aa-86e4-4f31-8a2b-9d0b580e3e4c --storagectl IDE-Controller --port 0 --device 0 --type dvddrive --medium ""E:\VMs\Eval-Testsuite\AMHSTESTER.iso""
vboxmanage storageattach 5cb950aa-86e4-4f31-8a2b-9d0b580e3e4c --storagectl IDE-Controller --port 0 --device 1 --type dvddrive --medium ""C:\Program Files\Oracle\VirtualBox\VBoxGuestAdditions.iso""
vboxmanage storagectl 5cb950aa-86e4-4f31-8a2b-9d0b580e3e4c --name SATA-Controller --add sata --portcount 1
vboxmanage storageattach 5cb950aa-86e4-4f31-8a2b-9d0b580e3e4c --storagectl SATA-Controller --port 0 --type hdd --medium ""E:\VMs\Eval-Testsuite\VMs\AMHS-CentOS-Eval\AMHS-Tester\AMHS-Tester.vmdk""
vboxmanage modifyvm 5cb950aa-86e4-4f31-8a2b-9d0b580e3e4c --nic1 hostonly --hostonlyadapter1 ""VirtualBox Host-Only Ethernet Adapter #2""
vboxmanage modifyvm 5cb950aa-86e4-4f31-8a2b-9d0b580e3e4c --nic2 natnetwork --nat-network2 NatAMHS
vboxmanage modifyvm 5cb950aa-86e4-4f31-8a2b-9d0b580e3e4c --nicpromisc2 allow-all
vboxmanage sharedfolder add 5cb950aa-86e4-4f31-8a2b-9d0b580e3e4c --name work --hostpath ""E:\VMs\Eval-Testsuite\work"" --automount
vboxmanage modifyvm 5cb950aa-86e4-4f31-8a2b-9d0b580e3e4c --clipboard bidirectional
vboxmanage modifyvm 5cb950aa-86e4-4f31-8a2b-9d0b580e3e4c --draganddrop bidirectional
vboxmanage modifyvm 5cb950aa-86e4-4f31-8a2b-9d0b580e3e4c --vcpfile ""E:\VMs\Eval-Testsuite\work\AMHS-Tester.webm"" --vcpwidth 1920 --vcpheight 1200
vboxmanage startvm 5cb950aa-86e4-4f31-8a2b-9d0b580e3e4c
}}}
And finally, starting at time stamp 00:18:59 the script checked the VM every five seconds using:
{{{
vboxmanage showvminfo 5cb950aa-86e4-4f31-8a2b-9d0b580e3e4c --machinereadable
}}}
The UUID is of course that of the newly created VM in the first command.
"	Reiner Brodbeck
21317	Mac dark mode makes it impossible to read help	VirtualBox-7.0.4	2022-11-28T02:10:54Z	2022-11-28T02:10:54Z	2022-11-28T02:10:54Z	I was trying to access the help for VB on my mac in which I run dark mode.  However dark mode only seems to apply to text in the help, resulting in white text on white background.	traisjames
17442	Mac OS High Sierra VM crash	VirtualBox 5.2.4	2018-01-10T01:57:23Z	2018-01-13T20:02:36Z	2018-01-13T20:02:36Z	"The VM keeps crashing when I run the Daedalus Wallet application (https://daedaluswallet.io/). It does not happen immediately but after a few minutes.
I am running VirtualBox on a Mac OS High Sierra fully patched. The very same version is running on the VM."	luca.b
15340	Mac OS X operating system running virtual box with Ubuntu cannot access internet	VirtualBox 5.0.18	2016-04-24T01:19:55Z	2016-04-25T09:59:14Z	2016-04-25T09:59:14Z	I've reconfigured the networks and looked under advanced options in preferences menu with no luck.  I've tried to connect the host static IP internet connection to the virtual machine through host-only network.  I cannot figure out how to get Wi-Fi on VBox.	whumphries88
4167	Mac OSX Host: Enable CD/DVD Eject Key in Guest	VirtualBox 2.2.4	2009-06-03T21:02:59Z	2010-01-05T21:13:50Z	2010-01-05T21:13:50Z	"My enhancement request is to enable the Mac keyboard CD/DVD eject key for the VM Guest when the CD/DVD-ROM is mounted.

Thanks for considering my suggestion."	Bill Geisler
15369	mac osx i5 crashes when 3+ vms are using > 90% cpu each	VirtualBox 5.0.18	2016-04-29T09:00:39Z	2016-05-03T10:18:16Z	2016-05-03T10:18:16Z	"mac osx i5 crashes (blackscreen + reboot + send error report to apple popup) when 3+ centos or xubuntu vms are using > 90% cpu each

seems more stable if KVM paravirtualisation is forced off in every vm"	clive darra
18503	Mac wireless keyboard causes crash while running windows server 2019	VirtualBox 6.0.4	2019-03-17T12:30:04Z	2019-03-24T04:35:58Z	2019-03-24T04:35:58Z	"Running macOS 10.14.3 Mojave on
MacBook Pro (Retina, 15-inch, Early 2013)
Memory 16GB 1600 MHz DDR3
Running VirtualBox 6.0
Windows Server 2019 installed from 
17763.253.190108-0006.rs5_release_svc_refresh_SERVER_EVAL_x64FRE_en-us.iso

After Windows Server starts up, I inserted a control-alt-del and a dialogue box appeared
asking for my password. As soon as a struck the first key on my apple wireless keyboard,
the Apple macOS crashed. This is repeatable. I must have been nuts to run windows on my mac."	DouglasGoodall
19260	Macbook doesnot open virtual machine	VirtualBox 6.0.16	2020-01-24T00:08:59Z	2020-01-24T00:08:59Z	2020-01-24T00:08:59Z	"I have got the following error always on my Macbook.   Headless is OK, and other mac(MacPRO) can open the same virtual machine.

-----------------------------------------------------
仮想マシン""Windows 10 Pro""のセッションを開けませんでした。

The virtual machine 'Windows 10 Pro' has terminated unexpectedly during startup because of signal 11.

終了コード : NS_ERROR_FAILURE (0x80004005)
コンポーネント: MachineWrap
インターフェース: IMachine {5047460a-265d-4538-b23e-ddba5fb84976}
-----------------------------------------------------

Process:               VirtualBoxVM [13245]
Path:                  /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM
Identifier:            org.virtualbox.app.VirtualBoxVM
Version:               6.0.15 (6.0.15)
Code Type:             X86-64 (Native)
Parent Process:        VBoxSVC [12917]
Responsible:           VirtualBoxVM [13245]
User ID:               501

Date/Time:             2020-01-24 09:05:22.750 +0900
OS Version:            Mac OS X 10.13.6 (17G11008)
Report Version:        12
Anonymous UUID:        7C4097BE-7489-5B43-4421-C7BC46185EEE


Time Awake Since Boot: 38000 seconds

System Integrity Protection: disabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Segmentation fault: 11
Termination Reason:    Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [0]

VM Regions Near 0:
--> 
    __TEXT                 000000010372d000-000000010374f000 [  136K] r-x/rwx SM=COW  ~2 [/Applications/VirtualBox.app/Contents/MacOS/VirtualBoxVM]

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   ???                           	000000000000000000 0 + 0
1   com.apple.CoreImage           	0x00007fff48219d81 -[CIKernel _initWithFirstKernelFromString:withCruftCompatibility:] + 108
2   com.apple.CoreImage           	0x00007fff48033699 +[CIColorKernel kernelWithString:] + 45
3   com.apple.CoreImage           	0x00007fff48033651 __31-[CIBlendWithAlphaMask _kernel]_block_invoke + 36
4   libdispatch.dylib             	0x00007fff6f502db8 _dispatch_client_callout + 8
5   libdispatch.dylib             	0x00007fff6f502d6b dispatch_once_f + 41
6   com.apple.CoreImage           	0x00007fff4803362b -[CIBlendWithAlphaMask _kernel] + 105
7   com.apple.CoreImage           	0x00007fff481eaa67 -[CIBlendWithMask outputImage] + 989
8   com.apple.Foundation          	0x00007fff4971986c -[NSObject(NSKeyValueCoding) valueForKey:] + 284
9   com.apple.coreui              	0x00007fff5b579fe5 -[CUIShapeEffectStack standardEffectCompositeWithShapeImage:] + 2348
10  com.apple.coreui              	0x00007fff5b5a6f51 CUIRenderer::CreateImageByApplyingEffectsToImage(CUIDescriptor const*, long, __CFArray const*, CGImage*, double, unsigned char, unsigned char, CGBlendMode&) const + 7841
11  com.apple.coreui              	0x00007fff5b5ab965 CUIRenderer::CreateImage(CGRect, long, CUIDescriptor const*, unsigned char, CGImage**, long long*, unsigned char*, CGBlendMode*) const + 11137
12  com.apple.coreui              	0x00007fff5b563eac CUIRenderer::DrawImage(CGRect, long, CUIDescriptor const*) const + 160
13  com.apple.coreui              	0x00007fff5b56353f CUICoreThemeRenderer::DrawMenuTitle(CUIDescriptor const*, CUIReturnInfo&) + 837
14  com.apple.coreui              	0x00007fff5b56257e CUIRenderer::Draw(CGRect, CGContext*, __CFDictionary const*, __CFDictionary const**) + 1824
15  com.apple.coreui              	0x00007fff5b561e2e CUIDraw + 278
16  com.apple.HIToolbox           	0x00007fff468de402 _HIThemeCUIDrawWithOptions + 81
17  com.apple.HIToolbox           	0x00007fff468de396 _HIThemeCUIDrawWithRenderer + 174
18  com.apple.HIToolbox           	0x00007fff468dd7e7 _HIThemeDrawAppleMenuTitle + 506
19  com.apple.HIToolbox           	0x00007fff468d9fbe HIMenuBarView::DrawOnce(CGRect, CGRect, bool, bool, CGContext*) + 1150
20  com.apple.HIToolbox           	0x00007fff468d9a46 HIMenuBarView::DrawSelf(short, __HIShape const*, CGContext*) + 582
21  com.apple.HIToolbox           	0x00007fff468d9482 HIMenuBarView::DrawWithoutCustomization(short, __HIShape const*, CGContext*) + 82
22  com.apple.HIToolbox           	0x00007fff468d941a HIMenuBarView::DrawingDelegateHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 236
23  com.apple.HIToolbox           	0x00007fff468bd904 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1541
24  com.apple.HIToolbox           	0x00007fff468bcc4d SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 374
25  com.apple.HIToolbox           	0x00007fff468bcac3 SendEventToEventTargetWithOptions + 45
26  com.apple.HIToolbox           	0x00007fff468d8fbb HIView::SendDraw(short, OpaqueGrafPtr*, __HIShape const*, CGContext*) + 337
27  com.apple.HIToolbox           	0x00007fff468d89d7 HIView::RecursiveDrawComposited(__HIShape const*, __HIShape const*, unsigned int, HIView*, CGContext*, unsigned char, double) + 571
28  com.apple.HIToolbox           	0x00007fff468d8c57 HIView::RecursiveDrawComposited(__HIShape const*, __HIShape const*, unsigned int, HIView*, CGContext*, unsigned char, double) + 1211
29  com.apple.HIToolbox           	0x00007fff468d842c HIView::DrawComposited(short, OpaqueGrafPtr*, __HIShape const*, unsigned int, HIView*, CGContext*) + 874
30  com.apple.HIToolbox           	0x00007fff468d80b0 HIView::Render(unsigned int, CGContext*) + 54
31  com.apple.HIToolbox           	0x00007fff468d776b WindowData::PrepareForVisibility() + 153
32  com.apple.HIToolbox           	0x00007fff468d6eab _ShowHideWindows + 275
33  com.apple.HIToolbox           	0x00007fff468d6d92 ShowHide + 35
34  com.apple.HIToolbox           	0x00007fff468c6af9 MBWindows::GetWindowOnDisplay(unsigned int, unsigned char) + 299
35  com.apple.HIToolbox           	0x00007fff468c6893 MenuBarInstance::ForEachWindowDo(unsigned char, bool (OpaqueWindowPtr*, unsigned int) block_pointer) + 167
36  com.apple.HIToolbox           	0x00007fff46a571bc MenuBarInstance::Hide(MenuBarAnimationStyle, unsigned char, unsigned char, unsigned char*, unsigned char) + 260
37  com.apple.HIToolbox           	0x00007fff468c6248 MenuBarInstance::UpdateAggregateUIMode(MenuBarAnimationStyle, unsigned char, unsigned char, unsigned char) + 800
38  com.apple.HIToolbox           	0x00007fff468c5e63 MenuBarInstance::ForEachMenuBarDo(void (MenuBarInstance*) block_pointer) + 47
39  com.apple.HIToolbox           	0x00007fff468c5df9 UpdateAllAggregateUIModes(MenuBarAnimationStyle, unsigned char) + 131
40  com.apple.HIToolbox           	0x00007fff468c5d50 SetSystemUIMode + 169
41  com.apple.AppKit              	0x00007fff44e69e4d -[NSApplication _setPresentationOptions:instance:flags:] + 1406
42  libqcocoa.dylib               	0x000000010a1c5ab9 QCocoaIntegration::QCocoaIntegration(QStringList const&) + 1433
43  libqcocoa.dylib               	0x000000010a1c416e QCocoaIntegrationPlugin::create(QString const&, QStringList const&) + 78
44  org.qt-project.QtGuiVBox      	0x000000010453afd6 QPlatformIntegrationFactory::create(QString const&, QStringList const&, int&, char**, QString const&) + 198
45  org.qt-project.QtGuiVBox      	0x00000001045484f5 QGuiApplicationPrivate::createPlatformIntegration() + 2549
46  org.qt-project.QtGuiVBox      	0x00000001045494bb QGuiApplicationPrivate::createEventDispatcher() + 27
47  org.qt-project.QtCoreVBox     	0x000000010412c82e QCoreApplicationPrivate::init() + 1790
48  org.qt-project.QtGuiVBox      	0x0000000104544f71 QGuiApplicationPrivate::init() + 49
49  org.qt-project.QtWidgetsVBox  	0x0000000104afdd4e QApplicationPrivate::init() + 14
50  VirtualBoxVM.dylib            	0x0000000103df577b TrustedMain + 923
51  org.virtualbox.app.VirtualBoxVM	0x0000000103730d36 0x10372d000 + 15670
52  libdyld.dylib                 	0x00007fff6f53c015 start + 1

Thread 1:
0   libsystem_kernel.dylib        	0x00007fff6f68d28a __workq_kernreturn + 10
1   libsystem_pthread.dylib       	0x00007fff6f85420e _pthread_wqthread + 1552
2   libsystem_pthread.dylib       	0x00007fff6f853be9 start_wqthread + 13

Thread 2:
0   libsystem_kernel.dylib        	0x00007fff6f68d28a __workq_kernreturn + 10
1   libsystem_pthread.dylib       	0x00007fff6f85420e _pthread_wqthread + 1552
2   libsystem_pthread.dylib       	0x00007fff6f853be9 start_wqthread + 13

Thread 3:
0   libsystem_kernel.dylib        	0x00007fff6f68d28a __workq_kernreturn + 10
1   libsystem_pthread.dylib       	0x00007fff6f85420e _pthread_wqthread + 1552
2   libsystem_pthread.dylib       	0x00007fff6f853be9 start_wqthread + 13

Thread 4:
0   libsystem_kernel.dylib        	0x00007fff6f68d28a __workq_kernreturn + 10
1   libsystem_pthread.dylib       	0x00007fff6f85420e _pthread_wqthread + 1552
2   libsystem_pthread.dylib       	0x00007fff6f853be9 start_wqthread + 13

Thread 5:
0   libsystem_kernel.dylib        	0x00007fff6f68d28a __workq_kernreturn + 10
1   libsystem_pthread.dylib       	0x00007fff6f854009 _pthread_wqthread + 1035
2   libsystem_pthread.dylib       	0x00007fff6f853be9 start_wqthread + 13

Thread 6:
0   libsystem_pthread.dylib       	0x00007fff6f853bdc start_wqthread + 0

Thread 0 crashed with X86 Thread State (64-bit):
  rax: 0x00007fca1d749490  rbx: 0x00007fffa187fc78  rcx: 0x0000000000000001  rdx: 0x0000000000000307
  rdi: 0x00007fffa7f6aad0  rsi: 0x0000000000000304  rbp: 0x00007ffeec4cea20  rsp: 0x00007ffeec4ce918
   r8: 0x000000000000000d   r9: 0x00000000fffffff3  r10: 0x00007ffeec4d2b88  r11: 0xffffffffffffff56
  r12: 0x00007fca1d744c30  r13: 0x00007fca1d748d10  r14: 0x0000000000000000  r15: 0x00007fff6e910e80
  rip: 0x0000000000000000  rfl: 0x0000000000010202  cr2: 0x0000000000000000
  
Logical CPU:     2
Error Code:      0x00000014
Trap Number:     14


Binary Images:
       0x10372d000 -        0x10374eff7 +org.virtualbox.app.VirtualBoxVM (6.0.15 - 6.0.15) <0ED710D1-15CE-3432-97C3-40B0DD778F9B> /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM
       0x10376a000 -        0x103ccb5e7 +VBoxRT.dylib (0) <444F2BE4-CFE1-30FC-AD97-143570F6FCB2> /Applications/VirtualBox.app/Contents/MacOS/VBoxRT.dylib
       0x103dee000 -        0x103edbff7 +VirtualBoxVM.dylib (0) <AEDB7533-264F-3FC3-B470-25ACCDDB8EDD> /Applications/VirtualBox.app/Contents/MacOS/VirtualBoxVM.dylib
       0x103f34000 -        0x103f3dff7 +org.qt-project.QtMacExtrasVBox (5.6 - 5.6.3) <AC6F0DC8-BF41-3A20-B803-656B301B8CDF> /Applications/VirtualBox.app/Contents/Frameworks/QtMacExtrasVBox.framework/Versions/5/QtMacExtrasVBox
       0x103f46000 -        0x10446dff7 +org.qt-project.QtCoreVBox (5.6 - 5.6.3) <3A7A08E0-9422-393E-BD97-FD15E751434C> /Applications/VirtualBox.app/Contents/Frameworks/QtCoreVBox.framework/Versions/5/QtCoreVBox
       0x104523000 -        0x1049feff7 +org.qt-project.QtGuiVBox (5.6 - 5.6.3) <80F8D761-23D7-381D-B8D5-1C0C130F7876> /Applications/VirtualBox.app/Contents/Frameworks/QtGuiVBox.framework/Versions/5/QtGuiVBox
       0x104af2000 -        0x104ffbfff +org.qt-project.QtWidgetsVBox (5.6 - 5.6.3) <5DFD063A-1901-39D3-90FB-138EFE7C6A9E> /Applications/VirtualBox.app/Contents/Frameworks/QtWidgetsVBox.framework/Versions/5/QtWidgetsVBox
       0x10515e000 -        0x105192fff +org.qt-project.QtPrintSupportVBox (5.6 - 5.6.3) <4C8D48EF-FC21-3BE7-895F-584399F0B308> /Applications/VirtualBox.app/Contents/Frameworks/QtPrintSupportVBox.framework/Versions/5/QtPrintSupportVBox
       0x1051b6000 -        0x1051f5fff +org.qt-project.QtOpenGLVBox (5.6 - 5.6.3) <F75D0235-BFE7-3966-A3C4-CFEA758B9A71> /Applications/VirtualBox.app/Contents/Frameworks/QtOpenGLVBox.framework/Versions/5/QtOpenGLVBox
       0x105218000 -        0x10526bfff +VBoxDDU.dylib (0) <E4AAEA3D-1208-36E2-9A3C-B66067285187> /Applications/VirtualBox.app/Contents/MacOS/VBoxDDU.dylib
       0x105277000 -        0x1054f9fff +VBoxVMM.dylib (0) <DAA0ACC4-A8AE-38A5-922F-2336A21B876E> /Applications/VirtualBox.app/Contents/MacOS/VBoxVMM.dylib
       0x10561e000 -        0x105668adf  dyld (551.5) <ACC6AC7F-EAD9-340E-B2A8-AD26FE5B387B> /usr/lib/dyld
       0x1056bc000 -        0x1077f2fff +VBoxGlobal.dylib (0) <7290F7C1-254E-3EED-9C62-2BB5B0AB7D92> /Applications/VirtualBox.app/Contents/MacOS/VBoxGlobal.dylib
       0x107995000 -        0x107a46ff7 +VBoxXPCOM.dylib (0) <8FAAE730-B275-3930-8FE9-C0BDBCDD83A4> /Applications/VirtualBox.app/Contents/MacOS/VBoxXPCOM.dylib
       0x10a1bd000 -        0x10a2fcfff +libqcocoa.dylib (0) <FA226E50-20A3-3C6D-B04E-9262D65300BC> /Applications/VirtualBox.app/Contents/plugins/platforms/libqcocoa.dylib
    0x7fff3faa6000 -     0x7fff3fac2ffb  libJapaneseConverter.dylib (70) <8E3CD8A2-3F6F-317D-BCA2-5E340217F225> /System/Library/CoreServices/Encodings/libJapaneseConverter.dylib
    0x7fff43745000 -     0x7fff43749ffb  com.apple.agl (3.3.1 - AGL-3.3.1) <3741CDE0-4030-32F2-A7B4-ACE7D2E92214> /System/Library/Frameworks/AGL.framework/Versions/A/AGL
    0x7fff43aea000 -     0x7fff43aeafff  com.apple.Accelerate (1.11 - Accelerate 1.11) <8632A9C5-19EA-3FD7-A44D-80765CC9C540> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
    0x7fff43aeb000 -     0x7fff43b01fef  libCGInterfaces.dylib (417.2) <E08ADB62-DF87-3BC8-81C6-60438991D4E1> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/Libraries/libCGInterfaces.dylib
    0x7fff43b02000 -     0x7fff44000fc3  com.apple.vImage (8.1 - ???) <A243A7EF-0C8E-3A9A-AA38-44AFD7507F00> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage
    0x7fff44001000 -     0x7fff4415bfe3  libBLAS.dylib (1211.50.2) <62C659EB-3E32-3B5F-83BF-79F5DF30D5CE> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib
    0x7fff4415c000 -     0x7fff4418afef  libBNNS.dylib (38.1) <7BAEFDCA-3227-3E07-80D8-59B6370B89C6> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBNNS.dylib
    0x7fff4418b000 -     0x7fff4454aff7  libLAPACK.dylib (1211.50.2) <40ADBA5F-8B2D-30AC-A7AD-7B17C37EE52D> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib
    0x7fff4454b000 -     0x7fff44560ff7  libLinearAlgebra.dylib (1211.50.2) <E8E0B7FD-A0B7-31E5-AF01-81781F71EBBE> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLinearAlgebra.dylib
    0x7fff44561000 -     0x7fff44566ff3  libQuadrature.dylib (3) <3D6BF66A-55B2-3692-BAC7-DEB0C676ED29> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libQuadrature.dylib
    0x7fff44567000 -     0x7fff445e7fff  libSparse.dylib (79.50.2) <0DC25CDD-F8C1-3D6E-B472-8B060708424F> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparse.dylib
    0x7fff445e8000 -     0x7fff445fbfff  libSparseBLAS.dylib (1211.50.2) <722573CC-31CC-34B2-9032-E4F652A9CCFE> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparseBLAS.dylib
    0x7fff445fc000 -     0x7fff447a9fc3  libvDSP.dylib (622.50.5) <40690941-CF89-3F90-A0AC-A4D200744A5D> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib
    0x7fff447aa000 -     0x7fff4485bfff  libvMisc.dylib (622.50.5) <BA2532DF-2D68-3DD0-9B59-D434BF702AA4> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib
    0x7fff4485c000 -     0x7fff4485cfff  com.apple.Accelerate.vecLib (3.11 - vecLib 3.11) <54FF3B43-E66C-3F36-B34B-A2B3B0A36502> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib
    0x7fff44b50000 -     0x7fff459aefff  com.apple.AppKit (6.9 - 1561.61.100) <44C1CF67-764C-39CD-B025-5D8EE6E62591> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
    0x7fff45a00000 -     0x7fff45a00fff  com.apple.ApplicationServices (48 - 50) <0E4AA883-7EFC-36EE-8B8E-E226E2C37965> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices
    0x7fff45a01000 -     0x7fff45a67fff  com.apple.ApplicationServices.ATS (377 - 445.5) <703CE7E4-426A-35C0-A229-F140F30F5340> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS
    0x7fff45b00000 -     0x7fff45c22fff  libFontParser.dylib (222.1.7) <9C4CEFB4-0F08-3B60-BD50-0120A37F6EA2> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontParser.dylib
    0x7fff45c23000 -     0x7fff45c6eff7  libFontRegistry.dylib (221.6) <30C6D1DE-C0E3-3447-A0EF-829443D95F0E> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib
    0x7fff45d13000 -     0x7fff45d46ff7  libTrueTypeScaler.dylib (222.1.7) <E401BD38-5F0E-382F-B4CB-AC6063871C0F> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libTrueTypeScaler.dylib
    0x7fff45db0000 -     0x7fff45db4ff3  com.apple.ColorSyncLegacy (4.13.0 - 1) <A5FB2694-1559-34A8-A3D3-2029F68A63CA> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSyncLegacy.framework/Versions/A/ColorSyncLegacy
    0x7fff45e54000 -     0x7fff45ea6ffb  com.apple.HIServices (1.22 - 625) <78A1FB4F-A39C-3159-B285-600C997335FB> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices
    0x7fff45ea7000 -     0x7fff45eb5fff  com.apple.LangAnalysis (1.7.0 - 1.7.0) <B65FF7E6-E9B5-34D8-8CA7-63D415A8A9A6> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis
    0x7fff45eb6000 -     0x7fff45f02fff  com.apple.print.framework.PrintCore (13.4 - 503.2) <B90C67C1-0292-3CEC-885D-F1882CD104BE> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore
    0x7fff45f03000 -     0x7fff45f3dfff  com.apple.QD (3.12 - 404.2) <38B20AFF-9D54-3B52-A6DC-C0D71380AA5F> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD
    0x7fff45f3e000 -     0x7fff45f4afff  com.apple.speech.synthesis.framework (7.8.1 - 7.8.1) <A08DE016-C8F2-3B0E-BD34-15959D13DBF0> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis
    0x7fff45f4b000 -     0x7fff461d9ff7  com.apple.audio.toolbox.AudioToolbox (1.14 - 1.14) <BAAB5625-A263-3ADD-9026-3F5F07E9171E> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
    0x7fff461db000 -     0x7fff461dbfff  com.apple.audio.units.AudioUnit (1.14 - 1.14) <294802B9-E24D-34EB-973F-6D2B8E2E86CB> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
    0x7fff464fe000 -     0x7fff4689bfff  com.apple.CFNetwork (902.5 - 902.5) <2D37E75A-42FD-3CDE-BAE3-D4228EF813F0> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
    0x7fff468b0000 -     0x7fff468b0fff  com.apple.Carbon (158 - 158) <F8B370D9-2103-3276-821D-ACC756167F86> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
    0x7fff468b1000 -     0x7fff468b4ffb  com.apple.CommonPanels (1.2.6 - 98) <2391761C-5CAA-3F68-86B7-50B37927B104> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels
    0x7fff468b5000 -     0x7fff46bbafff  com.apple.HIToolbox (2.1.1 - 911.10) <BF7F9C0E-C732-3FB2-9BBC-362888BDA57B> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox
    0x7fff46bbb000 -     0x7fff46bbeffb  com.apple.help (1.3.8 - 66) <DEBADFA8-C189-3195-B0D6-A1F2DE95882A> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help
    0x7fff46bbf000 -     0x7fff46bc4fff  com.apple.ImageCapture (9.0 - 9.0) <23B4916F-3B43-3DFF-B956-FC390EECA284> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture
    0x7fff46bc5000 -     0x7fff46c5affb  com.apple.ink.framework (10.9 - 221) <5206C8B0-22DA-36C9-998E-846EDB626D5B> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink
    0x7fff46c5b000 -     0x7fff46c75ff7  com.apple.openscripting (1.7 - 174) <1B2A1F9E-5534-3D61-83CA-9199B39E8708> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting
    0x7fff46c96000 -     0x7fff46c97fff  com.apple.print.framework.Print (12 - 267) <3682ABFB-2561-3419-847D-02C247F4800D> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print
    0x7fff46c98000 -     0x7fff46c9aff7  com.apple.securityhi (9.0 - 55006) <C1406B8D-7D05-3959-808F-9C82189CF57F> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI
    0x7fff46c9b000 -     0x7fff46ca1fff  com.apple.speech.recognition.framework (6.0.3 - 6.0.3) <2ED8643D-B0C3-3F17-82A2-BBF13E6CBABC> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition
    0x7fff46dc2000 -     0x7fff46dc2fff  com.apple.Cocoa (6.11 - 22) <17A98C08-64CF-3232-80EE-E10BAF68778F> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
    0x7fff46dd0000 -     0x7fff46e89fff  com.apple.ColorSync (4.13.0 - 3325) <D283C285-447D-3258-A7E4-59532123B8FF> /System/Library/Frameworks/ColorSync.framework/Versions/A/ColorSync
    0x7fff47016000 -     0x7fff470a9ff7  com.apple.audio.CoreAudio (4.3.0 - 4.3.0) <EB35D3EC-56EA-33E6-98DC-BDC3A5FA8ACE> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
    0x7fff47110000 -     0x7fff47139ffb  com.apple.CoreBluetooth (1.0 - 1) <E1335074-9D07-370E-8440-61C4874BAC56> /System/Library/Frameworks/CoreBluetooth.framework/Versions/A/CoreBluetooth
    0x7fff4713a000 -     0x7fff47490fef  com.apple.CoreData (120 - 851) <A2B59780-FB16-36A3-8EE0-E0EF072454E0> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
    0x7fff47491000 -     0x7fff47574fff  com.apple.CoreDisplay (99.14 - 99.14) <A1B91ADD-828D-33A0-8A92-CC3F83DF89D0> /System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay
    0x7fff47575000 -     0x7fff47a18fef  com.apple.CoreFoundation (6.9 - 1455.12) <DE73A96B-3187-3CAC-99BB-3AA2100CD755> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
    0x7fff47a1a000 -     0x7fff4802afef  com.apple.CoreGraphics (2.0 - 1161.21.3) <60EFD404-B50C-3B77-90CD-D610BC590E7C> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics
    0x7fff4802c000 -     0x7fff4831bfff  com.apple.CoreImage (13.0.0 - 579.5) <AAE2DFD0-9B0A-3D56-8A3E-C460BAF70394> /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage
    0x7fff486f0000 -     0x7fff486f0fff  com.apple.CoreServices (822.37 - 822.37) <7B04988B-C0D4-314E-8B3B-AE446B4A38CD> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
    0x7fff486f1000 -     0x7fff48765ffb  com.apple.AE (735.2 - 735.2) <690A6F47-1306-371F-B257-783D8F83EA9E> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE
    0x7fff48766000 -     0x7fff48a3dfff  com.apple.CoreServices.CarbonCore (1178.4.2 - 1178.4.2) <08AF7B7B-219B-3957-86CE-C96B423C823C> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
    0x7fff48a3e000 -     0x7fff48a72fff  com.apple.DictionaryServices (1.2 - 284.2) <6505B075-41C3-3C62-A4C3-85CE3F6825CD> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices
    0x7fff48a73000 -     0x7fff48a7bffb  com.apple.CoreServices.FSEvents (1239.50.2 - 1239.50.2) <FE465894-4235-3CE2-9A97-32D6C6C7D9AD> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/FSEvents.framework/Versions/A/FSEvents
    0x7fff48a7c000 -     0x7fff48c3aff7  com.apple.LaunchServices (822.37 - 822.37) <6AA93307-220A-3417-BBC2-FE1C0DE0B652> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices
    0x7fff48c3b000 -     0x7fff48cebfff  com.apple.Metadata (10.7.0 - 1191.7) <3DD530A7-E104-3469-98BB-20449834B2FE> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata
    0x7fff48cec000 -     0x7fff48d4cfff  com.apple.CoreServices.OSServices (822.37 - 822.37) <4AD2FC98-C6CB-392A-A22F-196A723D7FAE> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices
    0x7fff48d4d000 -     0x7fff48dbbfff  com.apple.SearchKit (1.4.0 - 1.4.0) <3662545A-B1CF-3079-BDCD-C83855CEFEEE> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit
    0x7fff48dbc000 -     0x7fff48de0ffb  com.apple.coreservices.SharedFileList (71.21 - 71.21) <1B5228EF-D869-3A50-A373-7F4B0289FADD> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SharedFileList.framework/Versions/A/SharedFileList
    0x7fff49081000 -     0x7fff491d1fff  com.apple.CoreText (352.0 - 578.22) <6129F39D-284D-3BBF-8999-7854AB61C01C> /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText
    0x7fff491d2000 -     0x7fff4920cfff  com.apple.CoreVideo (1.8 - 0.0) <86CCC036-51BB-3DD1-9601-D93798BCCD0F> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
    0x7fff4920d000 -     0x7fff49298ff3  com.apple.framework.CoreWLAN (13.0 - 1350.2) <DC9E1B0B-FD96-38A7-A6E0-820CA414AA94> /System/Library/Frameworks/CoreWLAN.framework/Versions/A/CoreWLAN
    0x7fff49513000 -     0x7fff49518fff  com.apple.DiskArbitration (2.7 - 2.7) <2F628584-8177-3894-92CE-9CA6089B61C6> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
    0x7fff496d9000 -     0x7fff49aa0ffb  com.apple.Foundation (6.9 - 1455.12) <3B5567E0-775C-36D2-8052-DA42CA319EEA> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
    0x7fff49b11000 -     0x7fff49b41ff3  com.apple.GSS (4.0 - 2.0) <FC69A120-3C19-3802-87B4-C29217758143> /System/Library/Frameworks/GSS.framework/Versions/A/GSS
    0x7fff49c53000 -     0x7fff49d57ffb  com.apple.Bluetooth (6.0.7 - 6.0.7f16) <74EC61E7-20E8-324C-8B5C-1D3129EEE675> /System/Library/Frameworks/IOBluetooth.framework/Versions/A/IOBluetooth
    0x7fff49db7000 -     0x7fff49e52fff  com.apple.framework.IOKit (2.0.2 - 1445.71.6) <C68CE7ED-85CA-3D1F-BAA0-908327BEC0DE> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
    0x7fff49e54000 -     0x7fff49e5bfff  com.apple.IOSurface (211.15 - 211.15) <9FD406F1-6BF2-35B0-8339-DF83A1A661EB> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface
    0x7fff49eb2000 -     0x7fff4a02cfef  com.apple.ImageIO.framework (3.3.0 - 1739.3.2) <604D4447-1D29-3B29-A2D0-FED25E1FC6B5> /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO
    0x7fff4a02d000 -     0x7fff4a031ffb  libGIF.dylib (1739.3.2) <4C4B82AB-2F5A-3B98-9A6A-4D8D6B79DA75> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib
    0x7fff4a032000 -     0x7fff4a119fe7  libJP2.dylib (1739.3.2) <A64CEB2C-3E18-3FFE-80B2-4F87233F3DF2> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib
    0x7fff4a11a000 -     0x7fff4a13dff7  libJPEG.dylib (1739.3.2) <48E918B8-2621-3002-9626-E89C10063104> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib
    0x7fff4a419000 -     0x7fff4a43ffeb  libPng.dylib (1739.3.2) <3708AFF8-776C-3EE5-A197-70A30A4FFD9E> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib
    0x7fff4a440000 -     0x7fff4a442ffb  libRadiance.dylib (1739.3.2) <A5585B3A-0A75-3401-B29F-24FA1A7B0977> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib
    0x7fff4a443000 -     0x7fff4a491fef  libTIFF.dylib (1739.3.2) <5F6ADFFB-0072-3176-9BA5-2313F2E2D99E> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib
    0x7fff4b34b000 -     0x7fff4b364ff7  com.apple.Kerberos (3.0 - 1) <F86DCCDF-93C1-38B3-82C2-477C12E8EE6D> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos
    0x7fff4bd46000 -     0x7fff4bdc7fff  com.apple.Metal (125.30 - 125.30) <6B9EBDEE-C64C-3C1C-922A-0363B642C9BC> /System/Library/Frameworks/Metal.framework/Versions/A/Metal
    0x7fff4bde4000 -     0x7fff4bdfffff  com.apple.MetalPerformanceShaders.MPSCore (1.0 - 1) <AD754E8F-CA00-3878-9AF3-208C224A230B> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSCore.framework/Versions/A/MPSCore
    0x7fff4be00000 -     0x7fff4be6ffef  com.apple.MetalPerformanceShaders.MPSImage (1.0 - 1) <338B7779-E608-3D68-8A07-2ACC11299744> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSImage.framework/Versions/A/MPSImage
    0x7fff4be70000 -     0x7fff4be94fff  com.apple.MetalPerformanceShaders.MPSMatrix (1.0 - 1) <9CE072D7-853B-3939-9645-7EB951376B87> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSMatrix.framework/Versions/A/MPSMatrix
    0x7fff4be95000 -     0x7fff4bf7cff7  com.apple.MetalPerformanceShaders.MPSNeuralNetwork (1.0 - 1) <0DE891AD-27E5-38FF-AEC8-4A95356C4357> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSNeuralNetwork.framework/Versions/A/MPSNeuralNetwork
    0x7fff4bf7d000 -     0x7fff4bf7dff7  com.apple.MetalPerformanceShaders.MetalPerformanceShaders (1.0 - 1) <2D2D261C-50B0-32F9-BF9A-5C01382BB528> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/MetalPerformanceShaders
    0x7fff4cf7c000 -     0x7fff4cf88ffb  com.apple.NetFS (6.0 - 4.0) <471DD96F-FA2E-3FE9-9746-2519A6780D1A> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS
    0x7fff4fd7a000 -     0x7fff4fdd4ff7  com.apple.opencl (2.8.24 - 2.8.24) <CF922AFD-CBA4-3B23-A0C1-E3E5362BB6C7> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL
    0x7fff4fdd5000 -     0x7fff4fdf1ffb  com.apple.CFOpenDirectory (10.13 - 207.50.1) <29F55F7B-379F-3053-8FF3-5C6675A3DD4D> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory
    0x7fff4fdf2000 -     0x7fff4fdfdfff  com.apple.OpenDirectory (10.13 - 207.50.1) <F895547D-4915-353F-9C1E-E95172BA803B> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory
    0x7fff50f7c000 -     0x7fff50f7efff  libCVMSPluginSupport.dylib (16.7.4) <6846D939-478C-3AE3-9DCD-CD4F4CD05409> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib
    0x7fff50f7f000 -     0x7fff50f84ffb  libCoreFSCache.dylib (162.9) <DD9DD721-2957-3D05-B361-70AF9EBFB280> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreFSCache.dylib
    0x7fff50f85000 -     0x7fff50f89fff  libCoreVMClient.dylib (162.9) <4E4F3EA2-5B53-31A3-8256-54EFAA94E4D6> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib
    0x7fff50f8a000 -     0x7fff50f93ff3  libGFXShared.dylib (16.7.4) <6187AD8B-1CD2-3775-84CD-76A0EA8BCDD4> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib
    0x7fff50f94000 -     0x7fff50f9ffff  libGL.dylib (16.7.4) <2BB333D3-5C61-33DF-8545-06DF2D08B83D> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
    0x7fff50fa0000 -     0x7fff50fdbfe7  libGLImage.dylib (16.7.4) <4DA003CE-0B74-3FE4-808C-B2FBCE517EB4> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib
    0x7fff5114a000 -     0x7fff51188ffb  libGLU.dylib (16.7.4) <BCB09CD8-EB0E-38FA-8B5A-9E29532EE364> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
    0x7fff51b00000 -     0x7fff51b0fff3  com.apple.opengl (16.7.4 - 16.7.4) <7B71A596-B6D8-335A-B7CA-8684D83B9C0E> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
    0x7fff52963000 -     0x7fff52bafff7  com.apple.QuartzCore (1.11 - 584.64.2) <DDA39332-DE09-3737-A332-0002AE05DD39> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
    0x7fff533e7000 -     0x7fff53712fff  com.apple.security (7.0 - 58286.70.15) <1481D55E-75C7-304D-AA12-D18A5197E508> /System/Library/Frameworks/Security.framework/Versions/A/Security
    0x7fff53713000 -     0x7fff5379fff7  com.apple.securityfoundation (6.0 - 55185.50.5) <EB62490A-AA77-3F51-86B3-03669C3897B3> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation
    0x7fff537d1000 -     0x7fff537d5ffb  com.apple.xpc.ServiceManagement (1.0 - 1) <E3146BBE-7F32-3605-AD2B-54C0E70759DC> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement
    0x7fff53b7a000 -     0x7fff53beaff3  com.apple.SystemConfiguration (1.17 - 1.17) <CD4A4C66-7886-3323-A3B9-0C8952500856> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration
    0x7fff56ae7000 -     0x7fff56b7aff3  com.apple.APFS (1.0 - 1) <70133D37-FDD3-3B2C-B295-00BECEA7EDA8> /System/Library/PrivateFrameworks/APFS.framework/Versions/A/APFS
    0x7fff577a7000 -     0x7fff577cffff  com.apple.framework.Apple80211 (13.0 - 1370.4) <B37A91A0-5823-3F97-B575-9BB804FCEB00> /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Apple80211
    0x7fff577d1000 -     0x7fff577e0fef  com.apple.AppleFSCompression (96.60.1 - 1.0) <A7C875C4-F5EE-3272-AFB6-57C9FD5352B3> /System/Library/PrivateFrameworks/AppleFSCompression.framework/Versions/A/AppleFSCompression
    0x7fff578df000 -     0x7fff578eaff7  com.apple.AppleIDAuthSupport (1.0 - 1) <2FAF5567-CDB3-33EF-AB71-05D37F2248B7> /System/Library/PrivateFrameworks/AppleIDAuthSupport.framework/Versions/A/AppleIDAuthSupport
    0x7fff57924000 -     0x7fff5796cff3  com.apple.AppleJPEG (1.0 - 1) <8DD410CB-76A1-3F22-9A9F-0491FA0CEB4A> /System/Library/PrivateFrameworks/AppleJPEG.framework/Versions/A/AppleJPEG
    0x7fff579a7000 -     0x7fff579cffff  com.apple.applesauce (1.0 - ???) <CCA8B094-1BCE-3AE3-A0A7-D544C818DE36> /System/Library/PrivateFrameworks/AppleSauce.framework/Versions/A/AppleSauce
    0x7fff57e22000 -     0x7fff580bbffb  com.apple.AuthKit (1.0 - 1) <6CA71A11-91C5-307C-B933-9FCDEDCB580A> /System/Library/PrivateFrameworks/AuthKit.framework/Versions/A/AuthKit
    0x7fff581f2000 -     0x7fff581f9ff7  com.apple.coreservices.BackgroundTaskManagement (1.0 - 57.1) <51A41CA3-DB1D-3380-993E-99C54AEE518E> /System/Library/PrivateFrameworks/BackgroundTaskManagement.framework/Versions/A/BackgroundTaskManagement
    0x7fff581fa000 -     0x7fff58281ff7  com.apple.backup.framework (1.9.6 - 1.9.6) <3C96FD26-C7F2-3F37-885A-5A71372FA8F4> /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup
    0x7fff59c3b000 -     0x7fff59c44ff3  com.apple.CommonAuth (4.0 - 2.0) <21AF4AC2-E650-35F9-AB33-3EBA2769FBC0> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth
    0x7fff5a758000 -     0x7fff5a768ff7  com.apple.CoreEmoji (1.0 - 69.3) <A4357F5C-0C38-3A61-B456-D7321EB2CEE5> /System/Library/PrivateFrameworks/CoreEmoji.framework/Versions/A/CoreEmoji
    0x7fff5aefc000 -     0x7fff5af04ff3  com.apple.CorePhoneNumbers (1.0 - 1) <A5D41251-9F38-3AB9-9DE7-F77023FAAA44> /System/Library/PrivateFrameworks/CorePhoneNumbers.framework/Versions/A/CorePhoneNumbers
    0x7fff5b08f000 -     0x7fff5b0c0ff3  com.apple.CoreServicesInternal (309.1 - 309.1) <4ECD14EA-A493-3B84-A32F-CF928474A405> /System/Library/PrivateFrameworks/CoreServicesInternal.framework/Versions/A/CoreServicesInternal
    0x7fff5b43a000 -     0x7fff5b4cbfff  com.apple.CoreSymbolication (9.3 - 64026.2) <A8D4315F-5DD5-3164-8672-ECDAF2766644> /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSymbolication
    0x7fff5b54e000 -     0x7fff5b683fff  com.apple.coreui (2.1 - 494.1) <B2C515C3-FCE8-3B28-A225-05AD917F509B> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI
    0x7fff5b684000 -     0x7fff5b7b5fff  com.apple.CoreUtils (5.6 - 560.11) <1A02D6F0-8C65-3FAE-AD63-56477EDE4773> /System/Library/PrivateFrameworks/CoreUtils.framework/Versions/A/CoreUtils
    0x7fff5b80a000 -     0x7fff5b86efff  com.apple.framework.CoreWiFi (13.0 - 1350.2) <50E8598A-0611-323D-B9A8-72A336424090> /System/Library/PrivateFrameworks/CoreWiFi.framework/Versions/A/CoreWiFi
    0x7fff5b86f000 -     0x7fff5b87fff7  com.apple.CrashReporterSupport (10.13 - 1) <A909F468-0648-3F51-A77E-3F9ADBC9A941> /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/CrashReporterSupport
    0x7fff5b8fe000 -     0x7fff5b90dff7  com.apple.framework.DFRFoundation (1.0 - 191.7) <9BBCCA62-F7BA-3B44-B044-E7C12ACC49F2> /System/Library/PrivateFrameworks/DFRFoundation.framework/Versions/A/DFRFoundation
    0x7fff5b910000 -     0x7fff5b914ffb  com.apple.DSExternalDisplay (3.1 - 380) <901B7F6D-376A-3848-99D0-170C4D00F776> /System/Library/PrivateFrameworks/DSExternalDisplay.framework/Versions/A/DSExternalDisplay
    0x7fff5b996000 -     0x7fff5ba0cfff  com.apple.datadetectorscore (7.0 - 590.3) <B4706195-CBE6-320D-A0E1-A9D4BDF52791> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDetectorsCore
    0x7fff5ba5a000 -     0x7fff5ba9aff7  com.apple.DebugSymbols (181.0 - 181.0) <299A0238-ED78-3676-B131-274D972824AA> /System/Library/PrivateFrameworks/DebugSymbols.framework/Versions/A/DebugSymbols
    0x7fff5ba9b000 -     0x7fff5bbcafff  com.apple.desktopservices (1.12.5 - 1.12.5) <7739C9A5-64D9-31A5-899B-5FFA242AD70D> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv
    0x7fff5c9df000 -     0x7fff5ce0dfff  com.apple.vision.FaceCore (3.3.2 - 3.3.2) <B574FE33-4A41-3611-9738-388EBAF03E37> /System/Library/PrivateFrameworks/FaceCore.framework/Versions/A/FaceCore
    0x7fff600d5000 -     0x7fff600dafff  com.apple.GPUWrangler (3.20.17 - 3.20.17) <BEA59DDE-A95A-3408-8FCE-6A74520E74AD> /System/Library/PrivateFrameworks/GPUWrangler.framework/Versions/A/GPUWrangler
    0x7fff60e50000 -     0x7fff60e5ffff  com.apple.GraphVisualizer (1.0 - 5) <B993B8A2-5700-3DFC-9EB7-4CCEE8F959F1> /System/Library/PrivateFrameworks/GraphVisualizer.framework/Versions/A/GraphVisualizer
    0x7fff60ee2000 -     0x7fff60f56fff  com.apple.Heimdal (4.0 - 2.0) <BAE3D978-2285-35DF-907E-02BC37986D02> /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal
    0x7fff61869000 -     0x7fff61870ff7  com.apple.IOAccelerator (378.28 - 378.28) <BE5CBEAA-314E-348B-BE85-7E4B2E4C42FF> /System/Library/PrivateFrameworks/IOAccelerator.framework/Versions/A/IOAccelerator
    0x7fff61874000 -     0x7fff6188bfff  com.apple.IOPresentment (1.0 - 35.1) <53B47F2A-9A9A-33F5-ADCB-FF766292B93A> /System/Library/PrivateFrameworks/IOPresentment.framework/Versions/A/IOPresentment
    0x7fff61c56000 -     0x7fff61c7cffb  com.apple.IconServices (97.6 - 97.6) <A56D826D-20D2-34BE-AACC-A80CFCB4E915> /System/Library/PrivateFrameworks/IconServices.framework/Versions/A/IconServices
    0x7fff61f01000 -     0x7fff61f14ff3  com.apple.security.KeychainCircle.KeychainCircle (1.0 - 1) <3A6D6354-9CD6-3EE5-B0AB-D25B02D4847D> /System/Library/PrivateFrameworks/KeychainCircle.framework/Versions/A/KeychainCircle
    0x7fff61f15000 -     0x7fff6200aff7  com.apple.LanguageModeling (1.0 - 159.5.3) <7F0AC200-E3DD-39FB-8A95-00DD70B66A9F> /System/Library/PrivateFrameworks/LanguageModeling.framework/Versions/A/LanguageModeling
    0x7fff6200b000 -     0x7fff6204dfff  com.apple.Lexicon-framework (1.0 - 33.5) <DC94CF9E-1EB4-3C0E-B298-CA1190885276> /System/Library/PrivateFrameworks/Lexicon.framework/Versions/A/Lexicon
    0x7fff62051000 -     0x7fff62058ff7  com.apple.LinguisticData (1.0 - 238.3) <49A54649-1021-3DBD-99B8-1B2EDFFA5378> /System/Library/PrivateFrameworks/LinguisticData.framework/Versions/A/LinguisticData
    0x7fff62d6b000 -     0x7fff62dd4ff7  com.apple.gpusw.MetalTools (1.0 - 1) <B4217182-B2AA-3AA3-80E8-F4C80B71BDDC> /System/Library/PrivateFrameworks/MetalTools.framework/Versions/A/MetalTools
    0x7fff62f64000 -     0x7fff62f7dfff  com.apple.MobileKeyBag (2.0 - 1.0) <7D657BC6-B779-3E51-B50D-07C95791DD04> /System/Library/PrivateFrameworks/MobileKeyBag.framework/Versions/A/MobileKeyBag
    0x7fff63009000 -     0x7fff63033ffb  com.apple.MultitouchSupport.framework (1614.1 - 1614.1) <A0709B43-FA9E-3617-8E7A-D68CDFAB2167> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport
    0x7fff6329a000 -     0x7fff632a5fff  com.apple.NetAuth (6.2 - 6.2) <2CFA1228-61A1-3708-988D-30499A1D6A9F> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth
    0x7fff64b3e000 -     0x7fff64b4effb  com.apple.PerformanceAnalysis (1.194 - 194) <8022ED1F-CE70-388E-B37B-6FB1E5F90CF2> /System/Library/PrivateFrameworks/PerformanceAnalysis.framework/Versions/A/PerformanceAnalysis
    0x7fff6690d000 -     0x7fff6692bfff  com.apple.ProtocolBuffer (1 - 260) <40704740-4A53-3010-A49B-08D1D69D1D5E> /System/Library/PrivateFrameworks/ProtocolBuffer.framework/Versions/A/ProtocolBuffer
    0x7fff66b06000 -     0x7fff66b29ffb  com.apple.RemoteViewServices (2.0 - 125) <592323D1-CB44-35F1-9921-4C2AB8D920A0> /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/RemoteViewServices
    0x7fff6844f000 -     0x7fff68564ff7  com.apple.Sharing (1050.22.6 - 1050.22.6) <4AACAE2C-C003-39B8-AE6F-28566E6B7598> /System/Library/PrivateFrameworks/Sharing.framework/Versions/A/Sharing
    0x7fff6858f000 -     0x7fff68590ff7  com.apple.performance.SignpostNotification (1.2.6 - 2.6) <8F04800F-3570-3392-A24D-B229FF03F7F9> /System/Library/PrivateFrameworks/SignpostNotification.framework/Versions/A/SignpostNotification
    0x7fff692ee000 -     0x7fff6958afff  com.apple.SkyLight (1.600.0 - 312.103.11) <A4D01EC8-6CED-3AA3-98EA-CD89E2B6559B> /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight
    0x7fff69d53000 -     0x7fff69d60fff  com.apple.SpeechRecognitionCore (4.6.1 - 4.6.1) <87EE7AB5-6925-3D21-BE00-F155CB457699> /System/Library/PrivateFrameworks/SpeechRecognitionCore.framework/Versions/A/SpeechRecognitionCore
    0x7fff6a906000 -     0x7fff6a98ffc7  com.apple.Symbolication (9.3 - 64033) <FAA17252-6378-34A4-BBBB-22DF54EC1626> /System/Library/PrivateFrameworks/Symbolication.framework/Versions/A/Symbolication
    0x7fff6aeff000 -     0x7fff6af07ff7  com.apple.TCC (1.0 - 1) <E1EB7272-FE6F-39AB-83CA-B2B5F2A88D9B> /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC
    0x7fff6b114000 -     0x7fff6b1d1ff7  com.apple.TextureIO (3.7 - 3.7) <F8BAC954-405D-3CC3-AB7B-048C866EF980> /System/Library/PrivateFrameworks/TextureIO.framework/Versions/A/TextureIO
    0x7fff6b282000 -     0x7fff6b432fff  com.apple.UIFoundation (1.0 - 547.9) <24E3999C-F515-3389-9A82-A13E624F8B89> /System/Library/PrivateFrameworks/UIFoundation.framework/Versions/A/UIFoundation
    0x7fff6cbae000 -     0x7fff6cbb0ffb  com.apple.loginsupport (1.0 - 1) <D1232C1B-80EA-3DF8-9466-013695D0846E> /System/Library/PrivateFrameworks/login.framework/Versions/A/Frameworks/loginsupport.framework/Versions/A/loginsupport
    0x7fff6cd17000 -     0x7fff6cd4aff7  libclosured.dylib (551.5) <112BC241-6626-3848-8DD8-B34B5B6F7ABC> /usr/lib/closure/libclosured.dylib
    0x7fff6ce04000 -     0x7fff6ce3dff7  libCRFSuite.dylib (41) <FE5EDB68-2593-3C2E-BBAF-1C52D206F296> /usr/lib/libCRFSuite.dylib
    0x7fff6ce3e000 -     0x7fff6ce49fff  libChineseTokenizer.dylib (28) <53633C9B-A3A8-36F7-A53C-432D802F4BB8> /usr/lib/libChineseTokenizer.dylib
    0x7fff6cedb000 -     0x7fff6cedcff3  libDiagnosticMessagesClient.dylib (104) <9712E980-76EE-3A89-AEA6-DF4BAF5C0574> /usr/lib/libDiagnosticMessagesClient.dylib
    0x7fff6cf13000 -     0x7fff6d0ddff3  libFosl_dynamic.dylib (17.8) <C58ED77A-4986-31C2-994C-34DDFB8106F0> /usr/lib/libFosl_dynamic.dylib
    0x7fff6d115000 -     0x7fff6d115fff  libOpenScriptingUtil.dylib (174) <610F0242-7CE5-3C86-951B-B646562694AF> /usr/lib/libOpenScriptingUtil.dylib
    0x7fff6d24c000 -     0x7fff6d250ffb  libScreenReader.dylib (562.18.5) <0FEFDAC8-0FDF-38A0-AB88-A84E0DBA058F> /usr/lib/libScreenReader.dylib
    0x7fff6d251000 -     0x7fff6d252ffb  libSystem.B.dylib (1252.50.4) <B01E90C7-20B7-3CB1-8AB8-881827B5544A> /usr/lib/libSystem.B.dylib
    0x7fff6d2e5000 -     0x7fff6d2e5fff  libapple_crypto.dylib (109.50.15) <A8DEA8E9-5769-3C78-824D-969A98B94086> /usr/lib/libapple_crypto.dylib
    0x7fff6d2e6000 -     0x7fff6d2fcff7  libapple_nghttp2.dylib (1.24) <01402BC4-4822-3676-9C80-50D83F816424> /usr/lib/libapple_nghttp2.dylib
    0x7fff6d2fd000 -     0x7fff6d327ff3  libarchive.2.dylib (54) <8FC28DD8-E315-3C3E-95FE-D1D2CBE49888> /usr/lib/libarchive.2.dylib
    0x7fff6d328000 -     0x7fff6d3a9fdf  libate.dylib (1.13.1) <178ACDAD-DE7E-346C-A613-1CBF7929AC07> /usr/lib/libate.dylib
    0x7fff6d3ad000 -     0x7fff6d3adff3  libauto.dylib (187) <A05C7900-F8C7-3E75-8D3F-909B40C19717> /usr/lib/libauto.dylib
    0x7fff6d3ae000 -     0x7fff6d467ffb  libboringssl.dylib (109.50.15) <416CBB92-632F-33C2-A774-86ECB4BE46AE> /usr/lib/libboringssl.dylib
    0x7fff6d468000 -     0x7fff6d478ff3  libbsm.0.dylib (39) <6BC96A72-AFBE-34FD-91B1-748A530D8AE6> /usr/lib/libbsm.0.dylib
    0x7fff6d479000 -     0x7fff6d486ffb  libbz2.1.0.dylib (38) <0A5086BB-4724-3C14-979D-5AD4F26B5B45> /usr/lib/libbz2.1.0.dylib
    0x7fff6d487000 -     0x7fff6d4ddfff  libc++.1.dylib (400.9) <7D3DACCC-3804-393C-ABC1-1A580FD00CB6> /usr/lib/libc++.1.dylib
    0x7fff6d4de000 -     0x7fff6d502ff7  libc++abi.dylib (400.8.2) <EF5E37D7-11D9-3530-BE45-B986612D13E2> /usr/lib/libc++abi.dylib
    0x7fff6d504000 -     0x7fff6d514fff  libcmph.dylib (6) <890DEC4C-4334-393C-8B56-7C8560BBED9D> /usr/lib/libcmph.dylib
    0x7fff6d515000 -     0x7fff6d52cfcf  libcompression.dylib (47.60.2) <543F07BF-2F2F-37D5-9866-E84BF659885B> /usr/lib/libcompression.dylib
    0x7fff6d7d7000 -     0x7fff6d7efff7  libcoretls.dylib (155.50.1) <D350052E-DC4D-3185-ADBA-BA48EDCEE955> /usr/lib/libcoretls.dylib
    0x7fff6d7f0000 -     0x7fff6d7f1ff3  libcoretls_cfhelpers.dylib (155.50.1) <B297F5D8-F2FE-3566-A752-E9D998B9C039> /usr/lib/libcoretls_cfhelpers.dylib
    0x7fff6dcc2000 -     0x7fff6dd17ff3  libcups.2.dylib (462.2.9) <749D90AB-0F1E-308C-81B6-EA1167F7F5CA> /usr/lib/libcups.2.dylib
    0x7fff6de57000 -     0x7fff6de57fff  libenergytrace.dylib (16) <A92AB8B8-B986-3CE6-980D-D55090FEF387> /usr/lib/libenergytrace.dylib
    0x7fff6de8e000 -     0x7fff6de93ff3  libheimdal-asn1.dylib (520.50.9) <EF65C17E-31CD-31DC-876C-BF3EF393099C> /usr/lib/libheimdal-asn1.dylib
    0x7fff6debf000 -     0x7fff6dfb0ff7  libiconv.2.dylib (51.50.1) <2FEC9707-3FAF-3828-A50D-8605086D060F> /usr/lib/libiconv.2.dylib
    0x7fff6dfb1000 -     0x7fff6e1d8ffb  libicucore.A.dylib (59181.0.1) <2CE6205F-D375-3BF5-AA0A-3254BC4773D0> /usr/lib/libicucore.A.dylib
    0x7fff6e225000 -     0x7fff6e226fff  liblangid.dylib (128) <39C39393-0D05-301D-93B2-F224FC4949AA> /usr/lib/liblangid.dylib
    0x7fff6e227000 -     0x7fff6e240ffb  liblzma.5.dylib (10) <3D419A50-961F-37D2-8A01-3DC7AB7B8D18> /usr/lib/liblzma.5.dylib
    0x7fff6e241000 -     0x7fff6e257ff7  libmarisa.dylib (9) <D6D2D55D-1D2E-3442-B152-B18803C0ABB4> /usr/lib/libmarisa.dylib
    0x7fff6e308000 -     0x7fff6e530ff7  libmecabra.dylib (779.7.6) <F462F170-E872-3D09-B219-973D5E99C09F> /usr/lib/libmecabra.dylib
    0x7fff6e708000 -     0x7fff6e883fff  libnetwork.dylib (1229.70.2) <E185D902-AC7F-3044-87C0-AE2887C59CE7> /usr/lib/libnetwork.dylib
    0x7fff6e90a000 -     0x7fff6ecf87e7  libobjc.A.dylib (723) <DD9E5EC5-B507-3249-B700-93433E2D5EDF> /usr/lib/libobjc.A.dylib
    0x7fff6ed0b000 -     0x7fff6ed0ffff  libpam.2.dylib (22) <7B4D2CE2-1438-387A-9802-5CEEFBF26F86> /usr/lib/libpam.2.dylib
    0x7fff6ed12000 -     0x7fff6ed4aff7  libpcap.A.dylib (79.20.3) <6A9D27FA-2780-3E96-8B2E-645638AC13AC> /usr/lib/libpcap.A.dylib
    0x7fff6edc9000 -     0x7fff6ede5ffb  libresolv.9.dylib (65.1) <D9BB6307-71E4-3A94-A745-1FCA114C6894> /usr/lib/libresolv.9.dylib
    0x7fff6ee36000 -     0x7fff6efc9ff7  libsqlite3.dylib (274.8.1) <FCAD6A57-829E-3701-B16E-1833D620E0E8> /usr/lib/libsqlite3.dylib
    0x7fff6f19d000 -     0x7fff6f1fdff3  libusrtcp.dylib (1229.70.2) <1E065228-D0E3-3808-9405-894056C6BEC0> /usr/lib/libusrtcp.dylib
    0x7fff6f1fe000 -     0x7fff6f201ffb  libutil.dylib (51.20.1) <216D18E5-0BAF-3EAF-A38E-F6AC37CBABD9> /usr/lib/libutil.dylib
    0x7fff6f202000 -     0x7fff6f20fff3  libxar.1.dylib (417.1) <351781D5-3CCF-320F-BB5A-4DFCC1CCD31D> /usr/lib/libxar.1.dylib
    0x7fff6f213000 -     0x7fff6f2faff7  libxml2.2.dylib (31.17) <84B491F5-35D4-384A-B224-9B5BF69E8CB7> /usr/lib/libxml2.2.dylib
    0x7fff6f2fb000 -     0x7fff6f323fff  libxslt.1.dylib (15.16) <57D56366-1E7B-356C-B2B8-F4688FF666E6> /usr/lib/libxslt.1.dylib
    0x7fff6f324000 -     0x7fff6f336ffb  libz.1.dylib (70) <48C67CFC-940D-3857-8DAD-857774605352> /usr/lib/libz.1.dylib
    0x7fff6f3d2000 -     0x7fff6f3d6ff7  libcache.dylib (80) <092479CB-1008-3A83-BECF-E115F24D13C1> /usr/lib/system/libcache.dylib
    0x7fff6f3d7000 -     0x7fff6f3e1ff3  libcommonCrypto.dylib (60118.50.1) <029F5985-9B6E-3DCB-9B96-FD007678C6A7> /usr/lib/system/libcommonCrypto.dylib
    0x7fff6f3e2000 -     0x7fff6f3e9fff  libcompiler_rt.dylib (62) <968B8E3F-3681-3230-9D78-BB8732024F6E> /usr/lib/system/libcompiler_rt.dylib
    0x7fff6f3ea000 -     0x7fff6f3f3ffb  libcopyfile.dylib (146.50.5) <3885083D-50D8-3EEC-B481-B2E605180D7F> /usr/lib/system/libcopyfile.dylib
    0x7fff6f3f4000 -     0x7fff6f479ffb  libcorecrypto.dylib (562.70.3) <37AF8EC6-BF34-3D15-BC3A-A9B98F2427D4> /usr/lib/system/libcorecrypto.dylib
    0x7fff6f501000 -     0x7fff6f53aff7  libdispatch.dylib (913.60.3) <BF368549-2DFB-3530-B4CB-31D5EDAC4F2F> /usr/lib/system/libdispatch.dylib
    0x7fff6f53b000 -     0x7fff6f558ff7  libdyld.dylib (551.5) <49BF9E96-8297-30CF-8AA6-128CC14054B2> /usr/lib/system/libdyld.dylib
    0x7fff6f559000 -     0x7fff6f559ffb  libkeymgr.dylib (28) <E34E283E-90FA-3C59-B48E-1277CDB9CDCE> /usr/lib/system/libkeymgr.dylib
    0x7fff6f55a000 -     0x7fff6f566ff3  libkxld.dylib (4570.71.64) <720D7429-BBC0-3ABC-81C5-EB3357802F13> /usr/lib/system/libkxld.dylib
    0x7fff6f567000 -     0x7fff6f567ff7  liblaunch.dylib (1205.70.12) <4950A0B3-5EE1-3F9A-8B1A-94FB85FCCA2C> /usr/lib/system/liblaunch.dylib
    0x7fff6f568000 -     0x7fff6f56cffb  libmacho.dylib (906) <1902A611-081A-3452-B11E-EBD1B166E831> /usr/lib/system/libmacho.dylib
    0x7fff6f56d000 -     0x7fff6f56ffff  libquarantine.dylib (86.70.1) <C8252924-BCB2-35D3-BBA3-CEFE4FCB506C> /usr/lib/system/libquarantine.dylib
    0x7fff6f570000 -     0x7fff6f571ff3  libremovefile.dylib (45) <711E18B2-5BBE-3211-A916-56740C27D17A> /usr/lib/system/libremovefile.dylib
    0x7fff6f572000 -     0x7fff6f589fff  libsystem_asl.dylib (356.70.1) <39E46A6F-B228-3E78-B83E-1779F9707A39> /usr/lib/system/libsystem_asl.dylib
    0x7fff6f58a000 -     0x7fff6f58afff  libsystem_blocks.dylib (67) <17303FDF-0D2D-3963-B05E-B4DF63052D47> /usr/lib/system/libsystem_blocks.dylib
    0x7fff6f58b000 -     0x7fff6f614ff7  libsystem_c.dylib (1244.50.9) <1187BFE8-4576-3247-8177-481554E1F9E7> /usr/lib/system/libsystem_c.dylib
    0x7fff6f615000 -     0x7fff6f618ffb  libsystem_configuration.dylib (963.50.9) <A5DC1AFC-2C3E-3113-BE20-48F96064DB0F> /usr/lib/system/libsystem_configuration.dylib
    0x7fff6f619000 -     0x7fff6f61cffb  libsystem_coreservices.dylib (51) <486000D3-D8CB-3BE7-8EE5-8BF380DE6DF7> /usr/lib/system/libsystem_coreservices.dylib
    0x7fff6f61d000 -     0x7fff6f61efff  libsystem_darwin.dylib (1244.50.9) <09C21A4A-9EE0-388B-A9D9-DFF8F6758791> /usr/lib/system/libsystem_darwin.dylib
    0x7fff6f61f000 -     0x7fff6f625ffb  libsystem_dnssd.dylib (878.70.4) <A94265A1-309C-3A13-B1FC-ED928FD50C3D> /usr/lib/system/libsystem_dnssd.dylib
    0x7fff6f626000 -     0x7fff6f66fff7  libsystem_info.dylib (517.30.1) <AB634A98-B8AA-3804-8436-38261FC8EC4D> /usr/lib/system/libsystem_info.dylib
    0x7fff6f670000 -     0x7fff6f696ff7  libsystem_kernel.dylib (4570.71.64) <6D7159C8-F724-3C47-B8BF-4AB9BF475944> /usr/lib/system/libsystem_kernel.dylib
    0x7fff6f697000 -     0x7fff6f6e2fcb  libsystem_m.dylib (3147.50.1) <17570F46-566C-39FC-BEF6-635A355DD549> /usr/lib/system/libsystem_m.dylib
    0x7fff6f6e3000 -     0x7fff6f702ff7  libsystem_malloc.dylib (140.50.7) <A45A484C-3BDE-3BC4-A219-726E3CB332D9> /usr/lib/system/libsystem_malloc.dylib
    0x7fff6f703000 -     0x7fff6f833ff7  libsystem_network.dylib (1229.70.2) <5E86B2DE-9E15-3354-8714-4094ED5F698D> /usr/lib/system/libsystem_network.dylib
    0x7fff6f834000 -     0x7fff6f83effb  libsystem_networkextension.dylib (767.70.2) <9DC03712-552D-3AEE-9519-B5ED70980B70> /usr/lib/system/libsystem_networkextension.dylib
    0x7fff6f83f000 -     0x7fff6f848ff3  libsystem_notify.dylib (172) <08012EC0-2CD2-34BE-BF93-E7F56491299A> /usr/lib/system/libsystem_notify.dylib
    0x7fff6f849000 -     0x7fff6f850ff7  libsystem_platform.dylib (161.50.1) <6355EE2D-5456-3CA8-A227-B96E8F1E2AF8> /usr/lib/system/libsystem_platform.dylib
    0x7fff6f851000 -     0x7fff6f85cfff  libsystem_pthread.dylib (301.50.1) <0E51CCBA-91F2-34E1-BF2A-FEEFD3D321E4> /usr/lib/system/libsystem_pthread.dylib
    0x7fff6f85d000 -     0x7fff6f860fff  libsystem_sandbox.dylib (765.70.1) <553DFCC6-9D31-3B9C-AB7C-30F6F265786D> /usr/lib/system/libsystem_sandbox.dylib
    0x7fff6f861000 -     0x7fff6f862ff3  libsystem_secinit.dylib (30) <DE8D14E8-A276-3FF8-AE13-77F7040F33C1> /usr/lib/system/libsystem_secinit.dylib
    0x7fff6f863000 -     0x7fff6f86aff7  libsystem_symptoms.dylib (820.60.3) <441C6CA0-5711-3BB1-8420-DDAC3D5272E1> /usr/lib/system/libsystem_symptoms.dylib
    0x7fff6f86b000 -     0x7fff6f87fff7  libsystem_trace.dylib (829.70.2) <EEDE7900-3FDB-3841-A47D-2BED9FFBBF5D> /usr/lib/system/libsystem_trace.dylib
    0x7fff6f881000 -     0x7fff6f886ff7  libunwind.dylib (35.3) <BEF3FB49-5604-3B5F-82B5-332B80023AC3> /usr/lib/system/libunwind.dylib
    0x7fff6f887000 -     0x7fff6f8b4ff7  libxpc.dylib (1205.70.12) <7B82608D-ED82-35C1-B13F-99855E25D6DC> /usr/lib/system/libxpc.dylib

External Modification Summary:
  Calls made by other processes targeting this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
  Calls made by this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
  Calls made by all processes on this machine:
    task_for_pid: 26549
    thread_create: 0
    thread_set_state: 0

VM Region Summary:
ReadOnly portion of Libraries: Total=395.2M resident=0K(0%) swapped_out_or_unallocated=395.2M(100%)
Writable regions: Total=62.9M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=62.9M(100%)
 
                                VIRTUAL   REGION 
REGION TYPE                        SIZE    COUNT (non-coalesced) 
===========                     =======  ======= 
Activity Tracing                   256K        2 
CG backing stores                  440K        2 
CG image                             8K        2 
CoreUI image data                  184K        3 
CoreUI image file                  280K        4 
Dispatch continuations            8192K        2 
Kernel Alloc Once                    8K        2 
MALLOC                            42.6M       15 
MALLOC guard page                   32K        9 
STACK GUARD                       56.0M        8 
Stack                             11.0M        8 
VM_ALLOCATE                         52K        5 
__DATA                            23.2M      243 
__FONT_DATA                          4K        2 
__LINKEDIT                       198.8M       17 
__TEXT                           196.5M      247 
__UNICODE                          560K        2 
mapped file                       64.1M       13 
shared memory                      868K       10 
===========                     =======  ======= 
TOTAL                            602.8M      577 

Model: MacBook10,1, BootROM 183.0.0.0.0, 2 processors, Intel Core i5, 1.3 GHz, 8 GB, SMC 2.42f10
Graphics: Intel HD Graphics 615, Intel HD Graphics 615, Built-In
Memory Module: BANK 0/DIMM0, 4 GB, LPDDR3, 1867 MHz, 0x80CE, 0x4B33514634463430424D2D41474346202020
Memory Module: BANK 1/DIMM0, 4 GB, LPDDR3, 1867 MHz, 0x80CE, 0x4B33514634463430424D2D41474346202020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x168), Broadcom BCM43xx 1.0 (7.77.37.33.1a1)
Bluetooth: Version 6.0.7f16, 3 services, 27 devices, 1 incoming serial ports
Network Service: USB 10/100/1000 LAN, Ethernet, en3
Network Service: Wi-Fi, AirPort, en0
USB Device: USB 3.0 Bus
USB Device: USB3.0 Hub
USB Device: USB 10/100/1000 LAN
USB Device: USB3.0 Hub
USB Device: USB2.0 Hub
USB Device: USB 2.0 BILLBOARD
USB Device: USB2.0 Hub
USB Device: ACR1251 CL Reader PICC
Thunderbolt Bus: 
"	chitentai
13336	MacBook Pro Retina 2014 crashes when connected to Thunderbolt display	VirtualBox 4.3.14	2014-09-01T14:25:01Z	2015-10-19T06:27:29Z	2015-10-19T06:27:29Z	"MacBook Pro Retina Mid-2014, OS X Mavericks 10.9.4 crashes with a kernel panic after it is connected to the Apple Thunderbolt Display.

Here is the head of the panic log:


{{{
Fri Aug 29 19:04:48 2014
panic(cpu 0 caller 0xffffff80162dc24e): Kernel trap at 0xffffff80162a87e3, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x0000000000000000, CR3: 0x00000000189d2000, CR4: 0x00000000001626e0
RAX: 0x0000000000000080, RBX: 0x0000000000000000, RCX: 0xffffff80168d0320, RDX: 0xffffff80168d01c0
RSP: 0xffffff8225723c70, RBP: 0xffffff8225723d80, RSI: 0xffffff80227b8dc8, RDI: 0xffffff80168d01c0
R8:  0x0000000000000021, R9:  0x0000000000000010, R10: 0x0000000000000001, R11: 0xffffff801622fe40
R12: 0xffffff80168d0420, R13: 0x00000000003bca45, R14: 0x0000000000000001, R15: 0x0000000000000010
RFL: 0x0000000000010202, RIP: 0xffffff80162a87e3, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x0000000000000000, Error code: 0x0000000000000000, Fault CPU: 0x0

Backtrace (CPU 0), Frame : Return Address
0xffffff8225723900 : 0xffffff8016222f79 
0xffffff8225723980 : 0xffffff80162dc24e 
0xffffff8225723b50 : 0xffffff80162f3746 
0xffffff8225723b70 : 0xffffff80162a87e3 
0xffffff8225723d80 : 0xffffff8016681300 
0xffffff8225723ef0 : 0xffffff80166e1f6f 
0xffffff8225723f00 : 0xffffff801669b8cc 
0xffffff8225723f20 : 0xffffff801624a20a 
0xffffff8225723fb0 : 0xffffff80162d7417 

BSD process name corresponding to current thread: kernel_task

Mac OS version:
13E28

Kernel version:
Darwin Kernel Version 13.3.0: Tue Jun  3 21:27:35 PDT 2014; root:xnu-2422.110.17~1/RELEASE_X86_64
Kernel UUID: BBFADD17-672B-35A2-9B7F-E4B12213E4B8
Kernel slide:     0x0000000016000000
Kernel text base: 0xffffff8016200000
System model name: MacBookPro11,2 (Mac-3CBD00234E554E41)

System uptime in nanoseconds: 3724286466644
last loaded kext at 3687521824681: com.apple.driver.AppleIntelMCEReporter	104 (addr 0xffffff7f984cc000, size 49152)
last unloaded kext at 3613279530786: com.apple.driver.AppleUSBOHCI	656.4.1 (addr 0xffffff7f9854f000, size 53248)
loaded kexts:
org.virtualbox.kext.VBoxNetAdp	4.3.14
org.virtualbox.kext.VBoxNetFlt	4.3.14
org.virtualbox.kext.VBoxUSB	4.3.14
org.virtualbox.kext.VBoxDrv	4.3.14
com.apple.driver.AppleIntelMCEReporter	104
com.apple.driver.AppleUSBDisplays	360.8.14
com.apple.driver.AppleUSBEHCI	660.4.0
com.apple.driver.AppleFWOHCI	5.0.2
com.apple.iokit.AppleBCM5701Ethernet
}}}

Apple Support suggested to contact VirtualBox support. If I remove VB from my machine it crashes no longer."	Kees de Kooter
20312	Machine does not terminate: VBOX_E_INVALID_VM_STATE (0x80BB0002)	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
20852	Machine guest freeze on the host	VirtualBox 6.0.22	2022-02-25T16:18:34Z	2022-02-25T16:18:34Z	2022-02-25T16:18:34Z	"I keep running guest machine and at any given time , [[BR]]

it freeze.[[BR]]
I should be restart session/ host machine[[BR]]
I join log[[BR]]

"	Sizy458
17100	Machine inaccessible after snapshot deletion	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
17002	Machine not running	VirtualBox 5.1.26	2017-08-11T16:01:10Z	2017-08-12T06:02:35Z	2017-08-12T06:02:35Z	"I loaded VB easily enough, had issues getting Kali Linux loaded and installed on VB but finally had success. However, now when I run the machine I get a blank screen:
 and Kali Linux does not open. Any ideas?"	Sailingonu
17398	Machine remains in aborted state with 3D enabled	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
18289	Machine unable to open	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
20085	MachineWrap	VirtualBox 6.1.16	2020-12-07T19:21:45Z	2020-12-07T19:21:45Z	2020-12-07T19:21:45Z	"Hi Team,

For somewhat, I have had an issue with Virtualbox. This message has appeared when I start the VM. 

Here is the message:

'''''The virtual machine 'AppDynamics' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\ferna\VirtualBox VMs\AppDynamics\Logs\VBoxHardening.log'.


Código de Resultado: 
E_FAIL (0x80004005)
Componente: 
MachineWrap
Interface: 
IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}'''''


Could you help me? I attached the logs here.

I already tried to uninstall and install again, but I haven't a success.

Kind Regards,
Fernando"	fernandofot
19892	macOS 10.15.6 Default Machine Folder Path Cannot be Updated	VirtualBox 6.1.14	2020-09-18T04:11:32Z	2020-09-18T04:11:32Z	2020-09-18T04:11:32Z	"I recently changed my username on my macOS host, and noticed this screen when starting VBox:

[[Image(https://imgur.com/a/anxePYT)]]

I then opened Preferences, and found the ""Default Machine Folder"" option, then changed the path to my new location, shown here:

[[Image(https://imgur.com/nOrw2Ey)]]


However, after confirming this multiple times, quitting and opening VirtualBox back up, completely reinstalling, and rebooting, VirtualBox seems to not take the Default Machine Folder into account at all. 

As a temporary workaround, I've remade my old home folder under my permissions and copied the VirtualBox VMs folder there. I'm not sure if this is only a macOS issue or not, but for those that don't have the know-how to work around this, it can completely break VBox for them.

"	lossdev
21009	macos 6.1.34 cannot change a static IP address in host-only mode	VirtualBox 6.1.32	2022-06-26T08:20:57Z	2022-06-26T11:52:22Z	2022-06-26T11:52:22Z	"yucf@yuchengfangdeMacBook-Pro ~ % VBoxManage hostonlyif ipconfig vboxnet0 --ip 192.168.19.1 --netmask 255.255.255.0
VBoxManage: error: Code E_ACCESSDENIED (0x80070005) - Access denied (extended info not available)
VBoxManage: error: Context: ""EnableStaticIPConfig(Bstr(pszIp).raw(), Bstr(pszNetmask).raw())"" at line 242 of file VBoxManageHostonly.cpp"	ycfjiushiwo
17622	MacOS host Debian 9 guest hangs on big load	VirtualBox 5.2.8	2018-03-14T19:54:59Z	2018-03-22T13:04:46Z	2018-03-22T13:04:46Z	"when I start the guest with vboxmanage --headless, I kick off a build script over ssh to the guest.  eventually, the guest will become unresponsive and use 100% of one cpu.  This does not happen in the dev build (5.2.97) but does happen in the test build (>=5.2.9).  This is not reproducible if I run the same script from a gui login session on the host.

VBox.log is from a run with 5.2.9 which ends with a heartbeat flatline, after which I power the machine off.  VBox.log.2 is from a run with 5.2.97 which finished successfully followed by a power down."	jkordani-lsa2
17873	macOS Host: dont work UAC windows 7 and 8.1 guest vm	VirtualBox 5.2.16	2018-07-19T06:40:06Z	2018-07-29T13:59:15Z	2018-07-29T13:59:15Z	"Hello! In the guest system Windows 7 and 8.1 the UAC request does not work!
"	@…
16344	macos sierra mouse focus	VirtualBox 5.1.12	2017-01-01T22:30:37Z	2017-01-01T22:30:37Z	2017-01-01T22:30:37Z	"macos sierra is riddled with idiotic new ""features"". One is that double clicking on a VB VM icon within the VB app does not change focus to the VM (it used to, prior to Sierra). Another is, the VM icon in the dock requires two clicks to change focus - the first changes focus to the VB app, and the second changes the window focus. Prior to Sierra, simply clicking once on the VM icon in the dock would have the desired effect."	littlerunningdeer
9570	MacOSX Menubar appearing in Fullscreen Client	VirtualBox 4.1.2	2011-09-08T06:50:16Z	2014-11-27T23:30:38Z	2014-11-27T23:30:38Z	"After the Host Screen is locked with the screensaver or the host goes to sleep, and is subsequently woken up, the MacOSX Menubar for VirtualBox appears in a full screen client, when the cursor moves to the very top of the screen. 

A workaround to keep the menubar from appearing again is to switch the guest out of fullscreen, minimize the guest to the dock, have the guest window come back up and switch back to fullscreen. Then the menubar does not reappear, until the next time the host display is locked. 

Host is MacOS X SnowLeopard, Guest is Ubuntu 11.04.
This also happened with VirtualBox 4.0.x."	srd
18156	MacOSX shutdown wedges VirtualBox	VirtualBox 5.2.22	2018-11-28T16:45:45Z	2018-11-28T16:45:45Z	2018-11-28T16:45:45Z	"With a running guest, shut down the host.
VirtualBox should deal with this or ask the user what to do
but instead, shutdown is aborted because VirtualBox becomes unresponsive.
Selecting the VirtualBox Manager or the guest system console
merely gets a spinning beachball.  Force quit seems the only way out
and, strangely, it didn't offer to phone home with a crash dump.
MacBookAir7,2 MacOSX 10.11.6 ""El Capitan"" VirtualBox 5.2.22 r126460 (Qt5.6.3)
running guest Ubuntu 16.04.3 LTS with host SD Card reader mounted via USB."	Devon7
17169	Magix Music Maker (Free) freezes current VM	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
18450	Main Window closes when second display has 150% scale	VirtualBox 6.0.4	2019-02-23T18:54:38Z	2019-02-23T18:54:38Z	2019-02-23T18:54:38Z	"OS: Windows 10 Po x64[[BR]]
Main display: 1920x1280, scale: 100%[[BR]]
Second display (extends to the left of main display): 1920x1080, scale: 150%

Steps to reproduce the bug:[[BR]]
Launch VirtualBox, its window appears on main display;[[BR]]
Move the window to the second display and '''resize''' it;[[BR]]
Close the window;[[BR]]
Launch VirtualBox again: the window appears and closes in several seconds;[[BR]]
Now you can't use VirtualBox: its window just closes after launch.


To get it working again change scale factor of the second display to 100%, launch VirtualBox, move its window to the main display."	mjohn
16370	Main window showing guest freezes after using virtualdesktop on Win7	VirtualBox 5.1.12	2017-01-10T17:09:01Z	2018-02-13T17:28:01Z	2018-02-13T17:28:01Z	"Host: Windows 7, running virtual desktop program Dexpot version 1.6.10, Build 2362. 
Host Video card: NVIDIA GeForce GTX 960
VirtualBox version 5.1.12r112440 (QT5.6.2)

Guest OS: KUbuntu 16.04.1

This behavior started after I just upgraded from VirtualBox version 5.0.?? to version 5.1.12. 

When VB is in fullscreen mode, on the host I switch virtual desktops away from the desktop showing VB guest OS. When I switch back to the host virtual desktop the guest OS screen is frozen. HOWEVER, the VB preview window works. I can see applications switch, and can use a console to tell the machine to reboot. 

The screen does not feeze if the VB guest OS is kept in Windowed mode (not full-screen mode). In fact, switching to windowed mode unfreezes the display. 

The attached log is after the guest screen freezes, then I switch VB to windows mode to unfreeze the display, then switch virtual desktops on the host a couple of times. 
"	P-Dog
13865	Make text from label in the overview of details of the machine copyable	VirtualBox 4.3.22	2015-02-20T01:47:28Z	2015-02-20T01:47:28Z	2015-02-20T01:47:28Z	Currently it's possible to see all the information, but not copy it which is unnecessary time waisting for the user.	krichter
9815	Mark virtual machines as excluded from backups	VirtualBox 4.1.4	2011-10-26T07:11:47Z	2011-10-27T10:20:35Z	2011-10-27T10:20:35Z	"Hi there,

please set the relevant metadata to exclude virtual machines from time machine backups. They are just huge and change so much that it doesn't make a lot of sense to back them up.

You could add an option to revert this default if you feel that is important, but I'd doubt it to be.

Regards,
Martin"	Martin Häcker
15903	Media not released after a snapshot revert	VirtualBox 5.1.4	2016-09-08T07:03:46Z	2016-09-26T07:45:19Z	2016-09-26T07:45:19Z	"If you revert to a snapshot where some media was not attached, it doesn't get released. The way to reproduce:[[BR]]
1) Create a snapshot without any media attached[[BR]]
2) Attach an iso image to the VM [[BR]]
3) Revert to a snapshot[[BR]]
4) The VM doesn't have the iso attached anymore (as expected). But in the ""Virtual media manager"" this iso is still shown as attached and ""release"" of the iso doesn't work.

If you kill VBoxSVC and start ""Virtual media manager"" again, then the iso is shown as ""not attached"" and can be released without problem."	mskov
20746	Memory can't be read	VirtualBox 6.1.30	2021-12-23T23:22:14Z	2021-12-23T23:22:14Z	2021-12-23T23:22:14Z	Memory can't be read	MikhailRokhin
20747	Memory can't be read after resuming VM from pause	VirtualBox 6.1.30	2021-12-23T23:25:05Z	2022-02-07T18:27:06Z	2022-02-07T18:27:06Z	Memory can't be read after resuming VM from pause	MikhailRokhin
20853	Memory can't be read after resuming VM from pause after few resumes	VirtualBox 6.1.32	2022-02-25T17:09:56Z	2022-02-25T17:09:56Z	2022-02-25T17:09:56Z	Memory can't be read after resuming VM from pause: this time after few successful resumes.	MikhailRokhin
19970	memory could not be written error	VirtualBox 6.1.14	2020-10-15T07:53:00Z	2020-10-15T07:53:00Z	2020-10-15T07:53:00Z	"The instruction at 0x00007FFE24C31330 referenced memory at 0x00007FFE24C31330. The memory could not be written. Click on OK to terminate the program.
Name[:]UX310UAK.312
SerialNumber[:]JAN0CV13113544F
Version[:]_ASUS_ - 1072009
ProcessorName[:]Intel(R) Core(TM) i3-7100U CPU @ 2.40GHz
OperatingSystemCaption[:]MS Windows 10 Home
VideoProcessor[:]Intel(R) HD Graphics Family
VideoDriverDate[:]20191007000000.000000-000
VideoDriverVersion[:]26.20.100.7325
InstalledDisplayDrivers[:]C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9f310939ec1eebf9\igdumdim64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9f310939ec1eebf9\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9f310939ec1eebf9\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9f310939ec1eebf9\igd12umd64.dll
VideoName[:]Intel(R) HD Graphics 620"	Gameexpert
17047	"Memory Issue since updated to 5.1.26 - ""Instruction at 0x4336d43 referenced memory at 0x00000018. The memory could not be read."""	VirtualBox 5.1.26	2017-08-31T06:59:07Z	2017-08-31T06:59:07Z	2017-08-31T06:59:07Z	"Host: Windows 7
Guest: Ubuntu Mate 16.04 LTS

Since I have updated to version 5.1.26, I often get a error message when starting the virtual machine (see attached picture).
After the error message, the virtual machine aborts.
After a few tries it finally starts."	TK87
18693	Memory Leak in VirtualBox 6.0.8	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
14158	Memory Leak on Windows 7 Host VBox  4.3.28 r100309. Host Mem 45%-90% in 3 Hrs.	VirtualBox 4.3.28	2015-05-29T17:47:50Z	2015-05-29T17:47:50Z	2015-05-29T17:47:50Z	"Vbox Details
 Version 4.3.28
 Guest Additions 4.3.28.iso
 Operating System: Ubuntu 14.04
 System:
  Base Memory: 3GB
  Processors: 4
  Execution Cap: 95%
  Acceleration: VT-x/AMD-V, Nested Paging, PAE/NX
 Display:
  Video Memory 64 MB
  Screens: 2
  Acceleration: 3D

Host Details:
 Operating System: Windows 7
 RAM: 8GB
 Processors: 8
 
After starting the Virtual Machine VirtualBox.exe Memory(Private Working Set) rises to about 416,416 K. Within 3 hours of working inside the VM It will rise to roughly 2,000,000 K at which point the host alerts me to low memory. If I don't restart the VM eventually it will completely freeze and crash.

Typical Programs running in VM
Firefox
Sublime-Text-2
Terminal
Libre Office Writer/Spreadsheet
File Manager

In the host VirtualBox is typically the only program I'm running. I was wondering if maybe not having Admin permissions on the account I'm using is causing a problem? Although I did give VirtualBox all the rights an admin account has. 
"	dduke22
13526	Memory leak with 3D acceleration with Ubuntu lens	VirtualBox 4.3.18	2014-10-17T15:24:42Z	2015-06-20T00:47:09Z	2015-06-20T00:47:09Z	"I have a Windows 7 host and Ubuntu 14.04 guest. If I enable 3D acceleration, there is a huge memory leak (about 100 MB per second) when the Ubuntu main system menu (Unity lens) is open. It is apparently related to the blurring effect, since there is no leak if I disable 3D acceleration and Ubuntu just shows a plain colour background. 

The strangest thing is that I can see the memory being eaten away in my host's performance monitor, but the guest's performance monitor doesn't show any problem and the memory use is stable there. I hope this can be a clue as to where the problem lies.

I can work with 3D disabled but the system is totally unusable with it enabled, since the memory leak is so severe.

I attach a log file"	rgargente
12279	Memory leak: VBoxService.exe slowly eats up RAM	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
18541	Memory Reference	VirtualBox 6.0.4	2019-04-03T16:12:40Z	2019-04-04T16:55:43Z	2019-04-04T16:55:43Z	"""The Instruction at 0x... referenced memory at 0x... The memory could not be read.""
IDK what happened?
Help please."	HadeedTheError
19708	Memory Reference Error	VirtualBox 6.1.10	2020-07-08T21:04:33Z	2020-07-08T21:04:33Z	2020-07-08T21:04:33Z	"When running Ubuntu 20 (Linux Mint AND Budgie) I get a memory reference error.  Seems something is trying to write to 0x0000.

I've reproduced this in 6.1.9 and 6.1.10.  Host os is Windows 10.  HW is HP ZBook G5, 48GB RAM and 800+ GB disk.  "	grpark
16302	memory usaly error on ubuntu-16.04.1-desktop-amd64	VirtualBox 5.1.10	2016-12-17T15:18:18Z	2016-12-20T12:29:13Z	2016-12-20T12:29:13Z	"1. run WarZone2100
2. Инструкция по адресу 0х0000000058383А30 обратилась к памяти по адресу 0x0000000000000008. Память не может быть read. ""OK"" — завершение приложения

p.s. https://yadi.sk/i/cDluGr-q33qgq8"	fix27
19595	memtest86 8.3 freezes	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
17980	Menuet64 network I8254X does not work anymore	VirtualBox 5.2.18	2018-09-11T08:49:31Z	2019-02-25T18:22:29Z	2019-02-25T18:22:29Z	"Menuet64 network Intel8254X doesn't work anymore when updating from 5.1.38 to 5.2.0. Driver initializes fine, but no packets are sent.

Network test Menuet64:

First in VirtualBox:

Enable NAT and PRO/1000 MT in VirtualBox

Then in Menuet:

Start Menu->System->Setup application

For network, press 'Apply' for ../I8254X

Result can be seen at Menu->System->Drivers

Start Menu->Network->Setup->StackCfg

Enable only 'ethernet' and press Apply

Start Menu->Network->Setup->DHCP

Press 'Send Request'

In VB 5.1.38, this step returns the IP values from server.

However, in later versions, no values are returned and also Bridged net fails.




"	MikaelM
13054	metric enhancement - autostart	VirtualBox 4.3.12	2014-05-22T11:04:11Z	2014-05-22T11:04:11Z	2014-05-22T11:04:11Z	"The ability to allow metric collection to '''auto start''' when the VM is started.  The metric will have to be predefined.

I use metrics to determine how busy the VM is so I can take/kill snapshots for backup purposes.

Also use metrics to monitor and alert if guests are running hot, out of resources, etc.

For the above and more reasons, it would benefit to have a predefined, auto-starting metric."	Senthil Nathan
20115	Microsoft Office hangs when opening a file in a network share	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
16932	Microsoft Office unusable in version 5.1.24, was working in 5.1.22 fairly well, not perfect though	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
14243	Mini toolbar is 'Always on top' for all windows, even when VM does not have focus	VirtualBox 4.3.28	2015-07-05T06:00:11Z	2015-07-05T06:00:11Z	2015-07-05T06:00:11Z	"A VM with ""Mini Toolbar: Show in Fullscreen/Seamless, & Show at Top of Screen"" set.

While the VM is running, the toolbar appears to have ""Always on Top"" set, and appears over the top of other programs running on the host, even when the VM does not have focus.

WinSpy++ (allows peeking at Window attributes) says about the toolbar window:
Extended Styles: 00080088 = WS_EX_TOPMOST + WS_EX_TOOLWINDOW + WS_EX_LAYERED
If I attempt to clear the WS_EX_TOPMOST bit (using WinSpy++) it can't be changed.

https://msdn.microsoft.com/en-us/library/windows/desktop/ff700543%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396
says:
""WS_EX_TOPMOST 0x00000008L 
The window should be placed above all non-topmost windows and should stay above them, even when the window is deactivated.""

I suspect that WS_EX_TOPMOST should be cleared when the VM window loses focus.

Host : Windows 7 SP1.
Guests : Windows 8.1, Windows Server 2008 R2."	Mark Cranness
18684	Mini Toolbar stop working in full srceen in 6.0.8	VirtualBox 6.0.8	2019-05-30T15:43:29Z	2019-05-30T15:43:29Z	2019-05-30T15:43:29Z	SuSE Linux host, Windows 10 guest. Dual monitors.  The Mini Tool bar no longer pops up from the bottom of the screen in full screen mode.  It was working in 6.0.6.  Ctrl-Home does bring up the tool bar.  I tried moving it to the top of the screen, which also did not work.	Don Hughes
8282	Mini Toolbar/Quickbar unavailable if fullscreen changed to other host screen	VirtualBox 4.0.2	2011-02-05T22:51:59Z	2011-02-05T22:51:59Z	2011-02-05T22:51:59Z	"I am using 4.0.2 on Windows Vista host. (guest should be irrelevant, but is linux in case)

My host has 2 Monitors.
The guest has one Monitor, and runs fullscreen.

The mini-toolbar appears on the bottom of the screen.

If I switch (vie mini-toolbar ""view"" / ""virtual screen"" / ""use host screen x"" to the other host screen, then the mini toolbar will no longer appear, if the mouse is moved to the bottom-middle position.

Switching temporarily to window mode, and back to fullscreen fixes the issue (as a work around) until the next host-monitor switch"	Martin
17871	Missing installation instructions at Web site (virtualbox.org) for openSUSE 15.0 -> fixed after 5.2.16	VirtualBox 5.2.16	2018-07-18T08:46:40Z	2018-07-26T05:50:24Z	2018-07-26T05:50:24Z	"https://www.virtualbox.org/wiki/Linux_Downloads
1. at paragraph ""VirtualBox 5.2.16 for Linux"" lists and links only 'openSUSE 13.2 (""Harlequin"") / Leap 42 (""Malachite"")', but 15.0 not.
2. at paragraph ""RPM-based Linux distributions"" at the end lists and links ... 13.2 / 42 only, missing 15.0-related virtualbox.repo file.

Meanwhile RPM file https://download.virtualbox.org/virtualbox/5.2.16/VirtualBox-5.2-5.2.16_123759_openSUSE150-1.x86_64.rpm exists, but not listed/linked at proper Linux Download page."	maestro
13921	Missing values from configuration validation function, Acpi	VirtualBox 4.3.24	2015-03-04T19:00:16Z	2015-03-04T19:00:16Z	2015-03-04T19:00:16Z	"Hi,

The configuration validation function: ""CFGMR3AreValuesValid"" does not include the following two ACPI extradata settings. The core functionality is available, but users are unable to set these via the extradata settings, as 3 out of 5 values are available to be configured. It is most likely a bug/oversight:

- Missing from the check:
AcpiOemTabId
AcpiOemRevision


- Included:
AcpiOemId
AcpiCreatorId
AcpiCreatorRev


Regards
Mikael   "	nsmfoo
15695	mod_timer_pinned will be dropped from linux kernel v4.8	VirtualBox 5.1.2	2016-07-26T14:30:36Z	2016-09-20T09:34:22Z	2016-09-20T09:34:22Z	"The Linux kernel is about to drop function mod_timer_pinned
See:

http://git.kernel.org/cgit/linux/kernel/git/tip/tip.git/commit/?id=177ec0a0a531695210b277d734b2f92ee5796303

This change has meanwhile already been adopted by realtime patch rt8, resulting in vbox modules being un-available for this patched kernel.
The function will be ultimately dropped from kernel series 48.

Current situation in vbox is this:
{{{
$ grep -re ""mod_timer_pinned""

src/VBox/Runtime/r0drv/linux/timer-r0drv-linux.c:# define mod_timer_pinned mod_timer
src/VBox/Runtime/r0drv/linux/timer-r0drv-linux.c: mod_timer_pinned(&pSubTimer->u.Std.LnxTimer, pSubTimer->u.Std.ulNextJiffies);
src/VBox/Runtime/r0drv/linux/timer-r0drv-linux.c: mod_timer_pinned(&pSubTimer->u.Std.LnxTimer, pSubTimer->u.Std.ulNextJiffies);
src/VBox/Runtime/r0drv/linux/timer-r0drv-linux.c: mod_timer_pinned(&pSubTimer->u.Std.LnxTimer, pSubTimer->u.Std.ulNextJiffies); 
}}}"	manjaro_oberon
15436	Modify description of a running VM from vboxmanage	VirtualBox 5.0.20	2016-05-20T16:45:43Z	2016-05-20T16:45:43Z	2016-05-20T16:45:43Z	"I want to modify VM description from vboxmanage. But it fails if VM is running at the time:
vboxmanage.exe modifyvm myVM --description ""new descr of myVM""
vboxmanage.exe: error: The machine 'att9-1034-slave-5' is already locked for a session (or being unlocked)
vboxmanage.exe: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MachineWrap, interface IMachine, callee IUnknown
vboxmanage.exe: error: Context: ""LockMachine(a->session, LockType_Write)"" at line 493 of file VBoxManageModifyVM.cpp

At the same time I can change VM description via virtualbox manager GUI.

Please, fix modifyvm (or controlvm) command to make it able change VM description while its running.
"	wasapl
10818	modifyhd --resize should warn users about existing snapshots	VirtualBox 4.1.18	2012-08-10T14:56:59Z	2017-09-13T12:31:15Z	2017-09-13T12:31:15Z	"When resizing an existing VM using vboxmanage modifyhd vm.vdi --resize 12345 a user should be warned if the VM to be resized has unmerged snapshots. Since neither the documentation nor the vast majority of tips on the internet mention this problem, a user will *naturally* run the command above on what they believe to be *the* associated VDI file, *not* on one of the snapshots.

Consequently, modifyhd should first check whether the VM in question uses unmerged snapshots and issue a warning if so.

A perfect solution would have modifyhd determine the latest snapshot and offer the user to resize that snapshot instead."	Lillo
15020	Modifyvm --hardwareuuid does incorrect validation of input.	VirtualBox 5.0.12	2016-01-10T09:59:22Z	2016-01-12T14:55:03Z	2016-01-12T14:55:03Z	"In order to help a user I tried to test the trick of fixing a VMs hardwareuuid using the VBoxManage ""modifyvm --hardwareuuid"" command.

First problem is that VBoxManage exited without giving an error message. If there is an error then it should give an error message. After a lot of double checking of syntax I finally guessed what the problem was.

VBoxManage wasn't letting me set a hardware UUID which conflicted with the VM UUID. Since these two UUIDs are in separate address spaces there should be no reason for this check.

To confirm that this check is unnecessary I used the command to set a non conflicting UUID, then edited the .VBox file to make it conflicting - with absolutely no ill effect. I then cloned the VM: the clone inherited the hardware uuid as intended, again with no ill effect.

Since this check blocks one of the obvious uses for this feature I would consider this an important error. Happily it must be trivial to fix.

No logs are attached, since I'm documenting a bug in VBoxManage, not describing a problem with a VM."	mpack
20817	Monterey Guest is unstable, reboots every few minutes	VirtualBox 6.1.32	2022-02-09T04:03:15Z	2022-02-09T04:03:15Z	2022-02-09T04:03:15Z	"From forums link:
https://forums.virtualbox.org/viewtopic.php?f=22&t=104998

- Apple MBA 2020 MakBookAir9,1 / Intel / x86_64 machine
- Host OS: macOS Big Sur 11.6.2
- Host OS Build: 20G314
- SW: VirtualBox 6.1.30 r148432
- Guest OS: macOS Monterey 12.1 (21C52)"	Captain Crunch
15314	More complete build number in log file.	VirtualBox 5.0.16	2016-04-18T10:09:12Z	2016-04-18T10:09:12Z	2016-04-18T10:09:12Z	"Would it be possible to give more precise Windows Host version in the VBox.log file?

Concrete example: VBoxHardening.log quotes a Windows version as 10.0.10586.122, whereas VBox.log quotes it as 10.0.10586.  From what I can gather, 10580.0 was released last November, whereas 10580.122 is the latest bleeding edge insider version released AFTER the current VBox version, so the minor build number is important information for support purposes.

This is an enhancement suggestion not a bug report, hence I'm not including log files."	mpack
9668	more facts, figures, and statistics	VirtualBox 4.1.2	2011-09-29T17:51:48Z	2011-09-29T17:51:48Z	2011-09-29T17:51:48Z	"I'd like to be able to see more facts figures and statistics associated with the VM (like VMware). I'd like to know things like

 * create time
 * modified time
 * last run time
 * total run time
 * io history
 * storage history
 * config change history
 * memory usage
 * etc.

Thanks."	Bob Bagwill
10676	mount.vboxsf does not support generic userspace mount options (nofail)	VirtualBox 4.1.16	2012-06-15T17:34:59Z	2020-12-17T16:18:53Z	2020-12-17T16:18:53Z	"Reference: https://bugzilla.redhat.com/show_bug.cgi?id=832217

""The mount helpers (including /sbin/mount.vboxsf) have to support generic userspace mount options.""

Guest OS: Fedora 17

I just 'yum upgrade'ed to the latest available kernel in Fedora 17, so the VirtualBox Extensions do not work after reboot until I can rebuild them again.

The problem I'm having is that I am now getting dumped into maintenance mode during boot, rather than being taken into the OS.

This happens because my share doesn't work due to the extensions not working. When I add 'nofail' to the mount options in /etc/fstab and then reboot without fixing the extensions, then I boot successfully but I still cannot access the share because of the fact that mount(8) wraps mount.vboxsf and mount.vboxsf doesn't support the generic mount options such as nofail.

When the next kernel comes out, I'm going to try using _netdev, but the fact of the matter is: mount.vboxsf should really support generic mount options.

"	Speeddymon
20794	Mouse (in both guest and host) behaves strangely when captured.	VirtualBox 6.1.32	2022-01-28T07:57:13Z	2022-07-02T07:27:42Z	2022-07-02T07:27:42Z	"This bug is new to version 6.x (not sure the exact version it started in, as I just upgraded to 6.1.32 from a 5.x version a few days ago). Also, this bug only happens when using mouse capture (not when using mouse integration). I don't think it's dependent on the guest OS, as it has an impact on the host mouse cursor as well as the guest, but it may be dependent on the host OS (not sure if Linux version of VBox has this bug, as my PC only has Windows on it). It also doesn't matter if it's using capture instead of integration due to Guest Additions not being installed, or due to the mouse integration part of Guest Additions being manually disabled.

The bug causes the the host mouse cursor to be locked into a rectangular region of the screen, which is located in the upper-left hand corner of the host computer screen. It doesn't matter where the guest window is. The locked in rectangle is always in the upper-left corner of the host screen. If you use the mouse to try scroll the cursor out it wraps around.

On the guest side, the moment you move the mouse after capturing the mouse, the guest mouse cursor completely disappears. This aspect of the bug may be dependent on the guest OS, but I haven't tried it in any guest OS other than Windows, so I can't verify this.

As I don't have technical knowledge of the internals of VirtualBox, I don't know what component is responsible for this bug, so I have left that set to ""other"" on this bug report form.

I've attached a video I recorded of my screen using my cellphone camera showing this issue. It shows how it only has an impact when mouse capture is being used, by running an OS with Guest Additions with mouse integration, and then I disable the integration and let the mouse get captured, where the bug then becomes immediately obvious."	Ben321
20499	mouse and keyboard stop working after a few seconds	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
20386	Mouse click stops working on host/guest due to window focusOutEvent problem in Qt GUI	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
19319	Mouse clicks unresponsive	VirtualBox 6.1.2	2020-02-17T20:31:40Z	2020-02-17T20:31:40Z	2020-02-17T20:31:40Z	"I running a Windows 10 VM under a Mac OSX host. Sporadically, the mouse click becomes unresponsive. The mouse is visible and the keyboard still works.  There is an error in the log with entry given below. The only way to resolve this issue is to shut down/restart the system, which I can do using the keyboard.

VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received ## seconds ago"	gsdeerfield
13821	mouse cursor changes to guest even when not capturing mouse	VirtualBox 4.3.20	2015-02-10T22:19:10Z	2015-02-10T22:21:11Z	2015-02-10T22:21:11Z	"I've used vboxmanage to set...

VBoxManage setextradata ""win7-32bit"" GUI/MouseCapturePolicy Disabled

I've tried seamless and windowed and though the mouse is not ""captured"" in the window, the mouse cursor still changes to the guest cursor when I click on a guest window.  I've seen it where the cursor did NOT change (it happened once, so I'm not sure if this is as designed or what) but the behavior seems to be inconsistent, and it's now changing again.  I would prefer that it doesn't change because I'm using a ""resized"" (accessibility settings) cursor in my macOS host, which distorts the guest cursor to a grotesque pixelated monstrosity.  I have the extensions installed, and behavior described in the user manual says that the cursor is not supposed to change, but it does anyway. :("	apocalysque
18449	Mouse Cursor Corrupts when running Citrix Session in VirtualBox	VirtualBox 5.2.26	2019-02-22T23:21:05Z	2019-02-22T23:21:05Z	2019-02-22T23:21:05Z	"When I load a Citrix session in my VirtualBox, the mouse cursor in each of my Citrix sessions change to a ""<<= =>>"" (left right arrow).

I have to click outside the Citrix session to get it to ""clean up"".

Running Citrix sessions on a ""normal"" Windows 10 desktop (i.e. NOT inside VirtualBox) work fine.


Steps to reproduce:

Create a Windows 10 VirtualBox.

Download and install Citrix Receiver.

Login to a Citrix Session.


Inside the session, the mouse cursor changes to a ""left arrow/right arrow"".  You have to click outside the Citrix session to ""fix it"".

"	Master VB Guru
20935	Mouse cursor rendered in low resolution	VirtualBox 6.1.34	2022-05-10T08:03:37Z	2023-01-06T09:36:53Z	2023-01-06T09:36:53Z	"As described in forum: https://forums.virtualbox.org/viewtopic.php?f=6&t=105871

Host: Windows 10 Pro 21H2, Vbox 6.1.34 (the free version, no Extension Pack)[[BR]]
Guest: Windows 7 + Guest Additions v6.1.34

The Pointer scheme selected in the guest Control Panel is ""(None)"".

The pointer inside the VM is very pixelated. See photos below. One is the pointer inside the VM window, very pixelated, the other shows it outside the VM window, not pixelated, smooth.

The DPI scaling in the guest is set to 100%, the host has also 100%.

The photos on imgur:
https://imgur.com/XOqHicD
https://imgur.com/DLEiCpp
"	xerces8
17103	Mouse direction locked in opengl programs	VirtualBox 5.1.28	2017-09-21T04:51:24Z	2017-09-21T04:51:24Z	2017-09-21T04:51:24Z	"Host Win10, Virtual box 5.1.28 with Ubuntu 16.04 installed.
After install the VBoxGuestAdditions, when i start an opengl Application, the mouse lost control, just pointting to the sky.
When I tried to move left/right, the picture just rotate, not looking around."	ffpwserver
15656	mouse disappears in virtualbox, linux installation menu	VirtualBox 5.1.0	2016-07-21T15:48:18Z	2016-07-21T15:48:18Z	2016-07-21T15:48:18Z	"First of all, Sorry for my bad English!

my mouse disappears in virtualbox, to be exact in the linux installation menu. I can't choose any of the option system. I mean I can't choose ""Install, or anything"" I've a laptop, I tried to use USB mouse, but it didn't work. I used the insert guest additions, and turned off/on the 3D acceleration. both isn't working. I changed my Pointing device, from USB Multi-Touch tablet to USB Tablet. 

Can anyone help me please? What should I do?"	Hisham
13509	Mouse does not work in full screen mode (HOST+F)	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
18644	mouse doesn't work in new version	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
8460	Mouse events don't come to the guest while snapshot deletion is in progress	VirtualBox 4.0.4	2011-02-28T18:36:42Z	2011-02-28T18:36:42Z	2011-02-28T18:36:42Z	"Ubuntu guest doesn't get any mouse events while snapshot deletion is running when launched from the main vbox window. Progress dialog is active.

This is unreasonable to affect guest this way since past snapshot deletion has nothing to do with the guest's current state."	yurivict
18434	Mouse Integration Issue version 6.0.4 r128413	VirtualBox 6.0.4	2019-02-13T12:38:11Z	2019-02-14T09:51:44Z	2019-02-14T09:51:44Z	"Hi, 

I'm experiencing an issue with the mouse pointer in the latest release. When mouse integration is enabled the mouse pointer is distorted and very difficult to use. If I disable the mouse integration it looks and behaves as expected. I have looked on the forums and can't see any bugs logged for this version. 

Regards
James "	JamestheOracle
20406	Mouse integration missing	VirtualBox 6.1.22	2021-06-15T19:57:49Z	2021-06-15T19:57:49Z	2021-06-15T19:57:49Z	After update to 6.1.22, the mouse click sometimes not workin proprealy, so i need to disable mouse integration to continuie using VM, current i'm running w10 vm in w10 host	Lmendes.cwb
19199	Mouse Integration Not working	VirtualBox 6.1.0	2020-01-06T15:35:40Z	2022-04-11T10:28:29Z	2022-04-11T10:28:29Z	Updated to VirtualBox 6.1 this morning and mouse integration is no longer working.  The Mouse Integration option is checked and grayed out.  Mouse integration is not working at all.	cmccarron
11357	Mouse Lag in Age of Empires 2	VirtualBox 4.2.6	2013-01-03T22:58:39Z	2017-01-12T19:19:10Z	2017-01-12T19:19:10Z	"I had this problem several years ago on virtualbox but it was fixed. In the last two public releases 4.18 4.20. The problem seems to have reappeared, and that is the mouse lags on Age of Empires II AOE2 during game play no matter which computer I use. Several months ago it was working fine. I've tried it on 4 different machines some are better, but none are right.

Host MacOSX Mountain Lion 10.8
Guest Windows XP SP3
DirectX 9c

It's only in game play that the mouse lags by .5 to 1 second. The game menu is fine. Network versus standalone is exactly the same.

Medal of Honor Breakthrough runs perfect. I've never had it run on a real PC as well as it does on Virtualbox 

the latest 4.2.6 still has the mouse lag in Age of Empires 2 in Windows XP. Same problem in both SP3 and SP2. I also did a clean install with no better results. Because it runs so well with 3d it makes me think it's in the 2d part of the directX video driver or something with the mouse driver

BUT I think I figured out what is going on. The video driver appears to have gained a bug in 4.18 or thereabouts and forward.

If I turn off all acceleration on the slide bar in troubleshooting in Windows XP advanced settings (even keeping Enable Write combining checked) it will play without any lag. I don't know how to address the issue though. It's not smooth anymore, but the lag is gone and makes it useable.

I don't have a log, but I could get one if needed. It doesn't crash at all or give any errors so I'm not sure what I would send."	BryceSteiner
19923	Mouse Middle-Scroll Click aborts Linux guest	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
19189	Mouse not captured by Windows 7 guest with VB 6.1.0, 6.0.14 or 5.2.10 on macOS Sierra host	VirtualBox 6.1.0	2019-12-29T20:14:12Z	2019-12-29T20:14:12Z	2019-12-29T20:14:12Z	"After migrating from guest Windows 7 to 10 with VB 6.0.14 on host macOS Sierra (which was working fine with guest Windows 7), the full-screen option host F would not work even after installing the guest addition on Windows 10.

So I reverted back to Windows 7 and the full-screen was no longer working.  I tried to uninstall and reinstall the guest addition and it destroyed the mouse integration which is now disabled after starting the VM even though it is enabled on the setting menu. 

Now I can't figure out how to install the guest additions without a working mouse as the it involves clicking on Windows buttons inaccessible from the arrow keys of the mac keyboards which just do not move the cursor from one button to the next. The mouse of the host does not merge with the mouse of the guest. So now I am stuck with a completely unusable VM. I tried to upgrade to VB 6.1.0 and downgrade to 5.2.10 from a backup but still no mouse integration with either of those. 

I tried to change the pointing device from USB tablet to  PS/2 Mouse, the graphic controller to VBoxVGA,  VBoxSVGA and even VMSVGA, the USB controller to 3, 2 and 1, disable my filters, enable and disable 3D and 2D acceleration,  but none of these attempts make neither the mouse integration nor the full screen option work.

Any suggestion?"	DamienDeville
19908	Mouse not working in Virtualbox 6.1.14 with Arch Linux as Host	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
16819	Mouse Pointer Issue - Constant left click	VirtualBox 5.1.22	2017-06-07T14:22:52Z	2022-04-16T03:23:16Z	2022-04-16T03:23:16Z	"After running Virtualbox 5.1 for a period of time (time varies) the mouse pointer will end up in a constant left click.  If I hover over anything it will try to open/click. If I open the start menu the first thing hovered over is what gets opened. Restarting the VM will temporarily fix the issue however it consistently recurs. I did not see the problem pre version 5.1.

Host: Windows 7 64bit pro
Guest:Windows 7 64bit pro"	surreal_life
9211	Mouse pointer not correctly showed on guest when using multiple displays.	VirtualBox 4.0.12	2011-07-16T02:18:34Z	2011-07-16T02:18:34Z	2011-07-16T02:18:34Z	"When using multiple displays on host system - in this case, Windows 7 Professional - on a guest system running Windows XP the mouse pointer is not correctly mapped. In other words, you can't reach all window with one ""normal"" mouse pass: sometimes, multiple mouse passes have to be done with some speed to get the other side of the guest window.

This problem only occurs on Windows - only tested on XP. On a linux distro, it doesn't happen.

Solution: Place the guest window on the top left corner of the main display - if extended and the left one is the main one.

I'm available to provide more information on this issue."	haZard0us
21215	Mouse scroll not working	VirtualBox-7.0.2	2022-10-29T07:33:59Z	2022-11-02T09:46:49Z	2022-11-02T09:46:49Z	If I work in GUI app VSCode and scroll my code, my code scroll some lines (about 5-10) and stoped. I mean reboot (anytime fix problem with clipboard), but not fixing problem/ Early version all work fine	vajarkov
21010	mouse sluggish	VirtualBox 6.1.32	2022-06-26T23:03:10Z	2022-06-26T23:03:10Z	2022-06-26T23:03:10Z	I have windows 10 on my main pc and windows 7 on vb. When I click on something my mouse gets sluggish and you can actually see where the arrow is through out the movement. I haven't been able to find a work around. 	novalore40
21207	Mouse snap behaves sticky on VB via a remote desktop	VirtualBox-7.0.2	2022-10-27T11:24:24Z	2022-11-10T11:48:40Z	2022-11-10T11:48:40Z	"Mouse snap behaves sticky on VB via a remote desktop

When I remote login via mstsc on a machine and use the VB on that machine the mouse snap behaves weird. It jumps instead of smooth moves. Sometimes it jumps to totally different places.

Guest Adition for 7.02 are also installed. VM OS is Win 11. Host OS is Win 10."	SecondBox
20316	Mouseclicks doesn't respond when attempting to install Fedora 33	VirtualBox 6.1.18	2021-04-22T21:10:56Z	2021-04-22T21:12:22Z	2021-04-22T21:12:22Z	"Steps to reproduce:

1. Download the Fedora 33 Everything (netinstall) ISO
2. Boot the system
3. The installer won't past the first screen, because the mouseclicks doesn't respond.

Operating System: Kubuntu 21.04
KDE Plasma Version: 5.21.4
KDE Frameworks Version: 5.80.0
Qt Version: 5.15.2
Kernel Version: 5.11.0-16-generic
OS Type: 64-bit
Graphics Platform: X11"	radulf
19101	Movie Maker with Windows Vista	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
21085	mp bios bug 8254	VirtualBox 6.1.36	2022-08-31T11:47:09Z	2022-08-31T11:47:09Z	2022-08-31T11:47:09Z	bende bios bug 8254  noapic hatası veriyor bana yardımcı olun tıkandım kaldım	seafflyy
13843	MSCOM Java Binding - Breakage	VirtualBox 4.3.22	2015-02-16T16:26:17Z	2015-02-17T21:09:03Z	2015-02-17T21:09:03Z	"MSCOM Java bindings are currently unusable as they fail on any method not returning a String.[[BR]]
[[BR]]
Test code[[BR]]

{{{
public class MsComTest {
   
   public static void main(String[] args) {
      VirtualBoxManager mgr = VirtualBoxManager.createInstance(null);
      try {
         mgr.getVBox().getRevision();
      } finally {
         mgr.cleanup();
      }
   }
   
}
}}}
"	Max D
19304	MSDOS MODE freezes under 98 SE in VBox on latest version	VirtualBox 6.1.2	2020-02-12T19:36:19Z	2020-02-12T19:36:19Z	2020-02-12T19:36:19Z	"Example:

https://youtu.be/GWq_it8qLc0"	ned33
18296	mtype multiattach does not work	VirtualBox 6.0.0	2019-01-10T16:56:00Z	2020-01-06T22:34:50Z	2020-01-06T22:34:50Z	"Linux cn3-vcl4 4.19.13-200.fc28.x86_64 #1 SMP Sat Dec 29 23:10:35 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

The VM was created and registered today. The VDI file is old, but I don't think it is earlier than 4.0. This command works on 5.2.22:

VBoxManage -q storageattach ""centos1"" --storagectl ""SATA Controller"" --port 0 --device 0 --type hdd --medium ""/classroom/vms/tinfo442/centos73.vdi"" --mtype multiattach

but yield the following error on 6.0:

VBoxManage: error: Cannot change type for medium '/classroom/vms/tinfo442/centos73.vdi': the media type 'MultiAttach' can only be used on media registered with a machine that was created with VirtualBox 4.0 or later
VBoxManage: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MediumWrap, interface IMedium, callee nsISupports
VBoxManage: error: Context: ""COMSETTER(Type)(enmMediumType)"" at line 708 of file VBoxManageStorageController.cpp
VBoxManage: error: Failed to set the medium type

Switching mtype to ""immutable"" is a workaround."	Stephen Rondeau
4087	Multimedia keys not passed through to guest	VirtualBox 2.2.2	2009-05-24T09:58:47Z	2022-07-15T10:43:12Z	2022-07-15T10:43:12Z	"I have a Cherry eVolution STREAM keyboard. The following buttons are not passed through to the guest when pressed:

volume down
mute
volume up
previous track
play/pause
next track

At least, according to xev. They work in the host just fine.

The host is Vista Home Basic x64. The guest is Debian using Linux 2.6.26."	Sam Morris
17029	Multiple Instances of VBoxXPCOMIPCD, VBoxSVC, VBoxHeadless	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
13601	multiple keyboard related issues	VirtualBox 4.3.18	2014-11-10T10:08:44Z	2014-11-10T11:28:49Z	2014-11-10T11:28:49Z	"1. Using Linux and Windows as guests, the Scroll Lock LED indicator doesn't turn on or off, to reflect the key state, if I press Scroll Lock inside the guest. The same indicator doesn't reflect the guest key state after pressing it in the host, then returning to the guest (Linux, console mode).[[br]]

2. Having enabled Toggle Keys (accessibility feature) in Windows 8.1/7, after pressing Caps Lock to enable it, the guest OS emits a ""key disabled"" sound every time. Then, after enabling it, if I press a character key, it emits the correct ""key enabled"" sound. With Windows as host, when pressing NumLock, the guest consistently emits the wrong sound on enabling/disabling the key, and a proper ""key enabled"" sound after pressing a character key. With Ubuntu as host, when pressing NumLock, the guest usually doesn't emit the sound (except maybe on enable) unless I press a character key.

3. The Caps Lock LED indicator doesn't reflect the key state in the guest, after pressing the Caps Lock in the host, then returning to the guest (Linux console mode only, not under the X server). Also, after starting and booting the guest, if I switch right away to the text mode console, without pressing CapsLock in the guest, then I return to the host, press the CapsLock in the host to enable it, then return again to the console of the guest, when pressing a letter key, it prints a capital letter, but the next ones are lower case.[[br]]

I don't know if any of the above issues are regressions. Maybe they are corner cases left from fixing bug #12758 I can reproduce the above issues with VirtualBox 4.3.19-96825 and 4.3.18-96516. [[br]]

Host OS: Windows 8.1 x64, Ubuntu 14.04 x64[[br]]
Guests: Windows XP x86, Windows 8.1 x64, Windows 7 x64, Debian 7 x86, Lubuntu live 14.04.1 x86[[br]]
"	Mihai Hanor
16560	Multiple password prompts for encrypted drives	VirtualBox 5.1.16	2017-03-14T14:31:29Z	2017-03-14T17:27:21Z	2017-03-14T17:27:21Z	"Hello,
I have a debian VM (windows 7 host) which is in encrypted drive images. When I boot it, it correctly asks for a password once. If I save the state, it asks twice (as the boot and home partitions are both encrypted is my guess).

- If I enter the password twice, the second attempt fails
- I have to cancel the second attempt, leading to the power off / save state / ... Menu, and then cancel that and the VM runs normally."	Nils
17446	Multiple pointing device reported when choosing USB Multi-Touch Tablet	VirtualBox 5.2.2	2018-01-10T18:14:05Z	2018-01-16T14:41:00Z	2018-01-16T14:41:00Z	"I'm running Android x86 in VirtualBox (I know, it is not a supported guest), on a Windows host, running on a machine with a touch screen. I'm trying to have a proper touch behavior in the virtual machine, ideally without having to forward the USB device of the touch screen to the VM (this is causing issues where the USB driver would eventually detach itself and stop responding. But this is not the point of my post). 

I've tried the differents ""Pointing device"" of the ""System/Motherboard"" settings tab. At first none of them seemed to give me the expected behavior in my host, but then I realized something:

If I enable USB Tablet, I can check from the Android command line (running the ""dumpsys input"" command) that this particular input device is present:

7: VirtualBox USB Tablet
    Classes: 0x800000004
    Path /dev/input/event3
    [...]

However, it doest not behave like a proper touch screen. 

If I enable USB Multi-Touch Tablet, the touch seems broken too. But if I inspect the available input devices in Android, I can see that both devices are present:

7. VirtualBox USB Multi-Touch
    Classes: 0x80000014
    Path: /dev/input/event4
    [...]

8. VirtualBox USB Tablet
    Classes: 0x800000004
    Path /dev/input/event3
    [...]


After inspecting the touch events in the Android guest, I realized that the presence of both devices is the cause of my incorrect touch behavior. When I touch the screen, the Virtual Box Multi-Touch device reports the event, but as soon as I move my finger around, the touch is ""intercepted"" by the VirtualBox USB Tablet device.

To confirm that, I deleted the /dev/input/event3 file (the one mapped to the VirtualBox USB Tablet device). After that everything was correct. The touch screen was working properly and only the proper device was handling the touch.

So, I think there is an issue with the actual pointing devices when choosing VirtualBox USB Multi-Touch tablet. VirtualBox USB Tablet shouldn't be reported by the guest OS in that case."	Cyrrus30
14628	Multiple Real Monitors/Screen-Sizing issue across multiple monitors	VirtualBox 5.0.4	2015-09-23T15:46:45Z	2015-09-23T15:46:45Z	2015-09-23T15:46:45Z	"Summary, VirtualBox does not handle real multiple monitors well and tries REALLY hard to confine itself to a single screen.

Issue Fix Proposal Summary: Maybe the simplest would be some type of way to toggle this auto resize back to ""full screen"" on and off.

Full Details:  

This is an issue that has been around for quite a few versions when using multiple real monitors.  In my case, I have 6 monitors setup as 3 on top and 3 on bottom.  The task is a lot more complicated then it needs to be in order to get the screen size to essentially take up more than 1 monitor.  In my case, my desired screen size would be over 4 monitors (2 on top and 2 on bottom).  Each of my monitors are 24 inch monitors and each are capable outputting 1920 X 1080 which is my desired resolution.

Main issue seems to be that the program gets stuck thinking that my main monitor is full screen mode.  So when I use Auto Reeize, whenever I try extending the window passed the first monitor, it always snaps back to extents of the single monitor.  I have confirmed that this isn't part of windows edge snap feature because I went in and turned that off.

I have limited success eventually getting it to work and it seems like I do something different each time.  Sometimes I found some vboxmanage commands that did the trick, but they didn't seem to work the next time.  For a while I stayed on a specific version of VirtualBox that seemed to handle this a lot better.  However, my hard drive crashed on Sunday so I don't know which version that was, but I think it was a build that was like 2 years old.  Last night, I tried enabled auto resize, and then dragged the corner to the size I wanted (while it was flashing back to the single screen), that tricked it into finally having the display dimensions that I needed so I turned off auto resize and was then able to size the window to how I want it.  But who knows if that trick will work again.

Anyways, it would be great if the resize on dragging the edge of the virtualbox window would recognize the extent of what all the real monitors are rather then what happens to be defined by clicking full screen.  Maybe the simplest would be some type of way to toggle this auto resize back to ""full screen"".  The Full screen issue is not an issue specific to VirtualBox.  All programs think that full screen is just one monitor.  However, they all seem to let me resize it past one monitor easily."	WileECoyote217
19382	Multiple Virtual Screen closes when changing a display	VirtualBox 6.1.2	2020-03-06T17:03:27Z	2020-03-06T17:06:26Z	2020-03-06T17:06:26Z	"I'm running Fedora 31 on Windows 10 with three monitors.
1. Dell XPS 15 (3840x2160 at 250% scaling which is recommended on Windows)
2. Dell Monitor (1920x1200 at 100% scaling)
3. Dell Monitor (1920x1200 at 100% scaling)
#2 and #3 are connected to XPS 15 via usb hub and daisy chained between #2 and #3.

These monitors are layout from left in above order.

I'm running the Fedora 31 using #2 and #3 monitors (so two virtual screens).

When I turn on the Auto-resize Guest Display option the second virtual screen crashes in a few operations.

Issue #1: When I drag and drop the second virtual screen window around above three monitors.  When I start the vm, the second virtual screen window appears in the monitor #1 (Dell XPS 15) and the first virtual screen windows appears in the monitor #2 (that is because I previously started in it).  I drag and drop the second virtual screen window to the monitor #3.  Then, the window blinks and planed in the monitor #1 and the windows is all grayed out.  Sometimes the window closes.  The first virtual screen window remains functional.

I can turn off the Auto-resize Guest Display options, and above issue does not happen.  After moving the second virtual screen window, I can turn on the option and use screens in the full screen mode.

Issue #2: After getting two virtual screens in the monitor #2 and #3 in the full screen mode.  The second virtual screen window closes if I getting out of the full screen mode.

There is the way around so not blocking issue, but this problem is annoying."	Takahiro
21203	multiple virtual screen issues	VirtualBox 6.1.40	2022-10-25T06:29:31Z	2022-10-27T17:27:15Z	2022-10-27T17:27:15Z	"I have 2 virtual screens (1440p main one and 1080p secondary on the right)

I once again have an issue with the cursor flickering and showing strange texture pixel behind it while it is on the secondary screen (I had this in the past, but it was resolved at some point and isn't present in 6.1.38)

also, if I scroll in the secondary screen, it also scrolls in the main screen
but if I scroll in the main screen it doesn't scroll in the secondary screen

I reverted to 6.1.38 and it's working fine there"	Bejito81
20584	Mutliple CPU's Stalls When Loading	VirtualBox 6.1.26	2021-09-29T14:21:44Z	2021-09-29T14:21:44Z	2021-09-29T14:21:44Z	"I am running VB on Windows 10, and when I use more than one processor for a VM is stalls when loading. This is true from Ubuntu 20 and RHEL 8, with encrypted drives and without encrypted drives. I am not sure it consistently stops in the same place, but here is what I have from my test:
* For Ubuntu
 * It is stopping when during the ""Loading essential drivers"". The last line is ""xor: measuring software checksum speed"".
 * When I click the X button to close the console, click ""Send shutdown signal"", and then ""OK"", and I repeat this 2 or more times, it will continue to boot again and I can use the server.
  *

* For RHEL 8
 * It does not display a prompt
 * I use the same process to boot Ubuntu on RHEL 8, but it does not boot and I close it down.
 * It is not consistent where it stalls. Once it was in the middle of the boot, then it goes to a black screen; another time it made it to the login prompt, but when I tried to enter my credentials, the console did not respond.



"	guidamedia
18051	My screen is all discombobulated! SOS	VirtualBox 5.2.18	2018-10-14T03:28:28Z	2018-10-17T08:20:08Z	2018-10-17T08:20:08Z	"When I start my VM for Linux Mint, my laptop cant seem to get
the display right. All I can see is a bunch of lines that seem
to make up my screensaver and I see my mouse divided into approx.
12 different slices along the lines that seem to make up my 
screensaver. I use the VM as a programming environment for my 
CS class and I have project due tomorrow but can't get it to run
so I can add the finishing touches... Please help. I would add a
pic if a knew how
"	Diddy
20599	my vbox show an error when I try save machine. What is the problem???	VirtualBox 6.1.26	2021-10-08T06:55:12Z	2021-10-19T19:11:49Z	2021-10-19T19:11:49Z	"Fallo al guardar el estado de la máquina virtual Sierra.

Código resultado: E_FAIL (0x80004005)

"	oberlus99
20436	my virtual box has a lot of bugs	VirtualBox 6.1.22	2021-06-29T22:53:59Z	2021-06-29T22:53:59Z	2021-06-29T22:53:59Z	the first bug is somany errors saying the hardrive is not detected but my hard drive is connacted to my mac second bug is the virtual drive is unstable but when i restart my mac the virtual drive is normal again 	kenzie
21064	My virtual machine half screen blank	VirtualBox 6.1.36	2022-08-15T16:03:08Z	2022-08-15T16:03:08Z	2022-08-15T16:03:08Z	"[[Image(https://i.postimg.cc/vTfcBVHY/IMG-20220815-211452.jpg)]]

"	Saikat
20260	My virtual machines are running slower	VirtualBox 6.1.18	2021-03-17T14:22:53Z	2021-03-17T14:22:53Z	2021-03-17T14:22:53Z	After a quick update to my computer, my virtual machines started to run slower, not sure why.	Guywithproblem
19725	my VM Centos 8 starting kicking me out	VirtualBox 6.1.10	2020-07-15T18:35:09Z	2020-07-15T18:49:56Z	2020-07-15T18:49:56Z	"This morning I  had a pop up to reboot my Window server for updates.

Before I rebooted Windows,  I went over to my Linux CentOS 8 VM and gracefully shut it down.

After it was completely down, I rebooted Windows.

After windows came backup, I started my Centos 8 VM,  it took a very long time to start, but eventually my sing on GUI was up, I was able to login and open a terminal and ran a few commands,  suddenly  it closed my terminal and went back to the sing on GUI.

I went to Oracle VM VirtualBox Manager, clicked on File, then clicked on Check for updates,  I received ""You are already running the most recent version..."". Since the version number did not show, I looked at Help - About VirtualBox - I was running 6.1.8.

I starting googling and found that the latest version is 6.1.12, so I downloaded and installed it.  I also install the latest extpack and the latest guest additions.

After the CentOS 8 reboot, I was able to login and work for about 15 minutes before it kicked me out again, back to the sign on GUI.

"	Saca
20286	máquina demorando para iniciar	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
13351	names of saved virtual machine's cannot be changed	VirtualBox 4.3.14	2014-09-06T16:59:21Z	2014-09-06T16:59:21Z	2014-09-06T16:59:21Z	I can understand not letting people change the amount of RAM or hard drive stuff but not letting people change the name of saved VM's seems...  silly.	queenzeal
20866	nao abre a sessao e consta esse erro	VirtualBox 6.1.32	2022-03-13T23:37:00Z	2022-03-13T23:38:14Z	2022-03-13T23:38:14Z	"Falha ao abrir uma sessão para a máquina virtual debian2.

Not in a hypervisor partition (HVP=0) (VERR_NEM_NOT_AVAILABLE).

VT-x is disabled in the BIOS for all CPU modes (VERR_VMX_MSR_ALL_VMX_DISABLED).

Código de Resultado: E_FAIL (0x80004005)
Componente: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

"	YuRi25
10242	Need a way to prune snapshot tree	VirtualBox 4.1.8	2012-02-10T20:02:44Z	2012-02-10T20:02:44Z	2012-02-10T20:02:44Z	"Note: This is ''not'' another complaint about ""Delete Snapshot"". I propose a new feature, regardless of what the snapshot operations are named.

When I have a tree of snapshots, I sometimes want to remove a branch, abandoning the snapshot states, deleting their differencing images and other new disks. I just want part of the machine's state zapped, just as if I had never created it in first place.

Other than hacking XML files, the only way to do this is documented here: 
[http://srackham.wordpress.com/2010/06/18/deleting-virtualbox-snapshots/ Convoluted Pruning Method] (Warning: contains an irrelevant gripe about the name of ""Delete Snapshot"".)


There are some design issues that I've thought of:

- Should the operation be on the parent snapshot (i.e, prune all children)? Or, should it be on the topmost snapshot to be removed?

- What if Current State is one of the decendents? Disallow or offer to restore to one of the snapshots that will remaing?

- There can be only one root snapshot. It necessarily has Current State as a decendent. And with all the snapshots being removed, it would seem appropriate to make the Current State the same as the the root snapshot and then remove all the snapshot. Again, just as if I had never created the root snapshot.

- I'm not looking for a one-click ""nuke it"" operation. As with the other snapshot operations, careful, informative UI design will help users be sure that they are doing the right thing and offer appropriate options or followup actions (e.g., delete disks or keep).
"	TomB
16193	Need a way to save machien state when Windows 10 restarts automatically	VirtualBox 5.1.8	2016-11-17T10:37:02Z	2016-11-17T10:37:02Z	2016-11-17T10:37:02Z	My computer restarted overnight, against my will. I don't expect VirtualBox to be able to override Microsoft's idiotic decisions WRT automatic restarts, but it would be really nice if it could suspend virtual machines during shutdown so that users' work is not lost.	Sam Morris
10557	Need an option to save a machine's state somewhere else	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
19584	Need for Speed Underground 2 causes Virtualbox.exe application error	VirtualBox 5.2.40	2020-05-14T14:15:34Z	2020-05-14T14:15:34Z	2020-05-14T14:15:34Z	When I run Need for Speed Underground 2, window VirtualBox.exe application error appears	Nikita Stepanov
10428	Need middle button simulation on MacBook Pro	VirtualBox 4.1.12	2012-04-10T18:13:02Z	2018-05-27T17:42:27Z	2018-05-27T17:42:27Z	The native X11 that comes with OS X will treat the combination of the option key + left trackpad click as a middle button press and command key + trackpad click as a right button press event. It would be nice if Virtual Box supported this as this would make my life a bit easier when working in a Solaris 11 guest session on my MacBook Pro OS X host.	Will Fiveash
4189	Need ot be able to chunk large VMDK files when exporting an appliance	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
20271	nested virtualisation with kvm cpu hits 100% then L2 guest crashes	VirtualBox 6.1.18	2021-03-23T13:57:56Z	2021-03-24T21:41:10Z	2021-03-24T21:41:10Z	"Hi,

It maybe that this is known not to work but in the 6.1 docs it mentions kvm as an L2 hypervisor so I thought I'd give it ago.

I have Intel I7 9th gen chip with 6 cores running windows 10 Enterprise build 18363 as my L0

I tried this originally on vbox 6.1.16 but upgraded to 6.1.18 after reading https://www.virtualbox.org/ticket/19315. This caused https://www.virtualbox.org/ticket/20199 so I'm currently running the 6.1.19 test build which fixes the crash but didnt resolve my problem first observed in 6.1.16 so I'm guessing its something different. 

Redhat mention they support some combinations in tech preview when the L0 is RHEL8.2. They say others eg: VMware, Xen, Amazon AWS, Nutanix AHV, Oracle VM are not. 

My use case for this is purely local lab environments mainly in vagrant so I'm more interested in if it work or not then support.

I'm trying to use packer inside a centos7 L1 VM to build with the qemu builder with kvm accelerator.

Packer is able to launch the VM and it starts the install. Its pretty slow but eventually fails installing this glibc.i686 package

{{{
Installing glibc.i686 (684/694)
[ 1354.721435] double fault: 0000 [#1] SMP
[ 1354.722093] Modules linked in: xfs fcoe libfcoe libfc scsi_transport_fc scsi_tgt zram sg pcspkr joydev i2c_piix4 parport_pc parport ext4 mbcache jbd2 loop nls_utf8 isofs sr_mod cdrom 8021q garp mrp stp llc virtio_net virtio_blk net_failover failover drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ttm ata_generic pata_acpi drm ata_piix libata serio_raw virtio_pci virtio_ring virtio drm_panel_orientation_quirks sunrpc xts lrw gf128mul dm_crypt dm_round_robin dm_multipath dm_snapshot dm_bufio dm_mirror dm_region_hash dm_log dm_zero dm_mod linear raid10 raid456 async_raid6_recov async_memcpy async_pq raid6_pq libcrc32c async_xor xor async_tx raid1 raid0 iscsi_ibft iscsi_boot_sysfs floppy iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi squashfs cramfs edd
[ 1354.722093] CPU: 0 PID: 17227 Comm: glibc_post_upgr Not tainted 3.10.0-1160.el7.x86_64 #1
[ 1354.722093] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 0.5.1 01/01/2011
[ 1354.722093] task: ffff9fa564fe8000 ti: ffff9fa562bdc000 task.ti: ffff9fa562bdc000
[ 1354.722093] RIP: 0010:[<00000000b5f97d80>]  [<00000000b5f97d80>] 0xb5f97d80
[ 1354.722093] RSP: 0018:0000000000000000  EFLAGS: 00010082
[ 1354.722093] RAX: 000000000000007a RBX: 00000000ffcc49ca RCX: 0000000000000000
[ 1354.722093] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000001
[ 1354.722093] RBP: 00000000ffcc495c R08: 0000000000000000 R09: 0000000000000000
[ 1354.722093] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
[ 1354.722093] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
[ 1354.722093] FS:  0000000000000000(0000) GS:ffff9fa5bcc00000(0000) knlGS:0000000000000000
[ 1354.722093] CS:  0010 DS: 002b ES: 002b CR0: 0000000080050033
[ 1354.722093] CR2: 00000000b5f97d80 CR3: 0000000022a7c000 CR4: 00000000000006f0
[ 1354.722093] Call Trace:
[ 1354.722093] Code:  Bad RIP value.
[ 1354.722093] RIP  [<00000000b5f97d80>] 0xb5f97d80
[ 1354.722093]  RSP <0000000000000000>
[ 1354.722093] ---[ end trace 6fd2b3e5f947f091 ]---
[ 1354.722093] Kernel panic - not syncing: Fatal exception
[ 1354.722093] Kernel Offset: 0x34800000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
}}}

I see some people are able to get kvm to run fine in vbox. But I'm wondering if they have AMD chips on the L0 or some other fundamental difference.

Any suggestions on how to try to debug this further?


"	aw125
19561	Nested virtualization BUG: soft lockup - CPU#4 stuck for 22s! [CPU 1/KVM:28838]	VirtualBox 6.1.6	2020-05-05T21:23:40Z	2020-12-16T07:19:30Z	2020-12-16T07:19:30Z	"I am running a KVM vm inside virtualbox. if the VM is set with 1 CPU, it works well. But if i increase the CPU to 2 or more, i am getting CPU stuck message inside virtualbox.

HOST OS: MAC OSX
Virtualbox Version: 6.1.6
Host have 12 cores and 64gb ram

Guest OS: Ubuntu 18.04
Guest CPU: 4
Guest Ram: 20GB
Nested VT-x/AMD-V and PAE/NX is enabled in processor settings

Nested VM Guest OS: debian
Nested VM Guest CPU: 2
Nested VM Guest Ram: 4GB

Partial syslog message and vbox.log is attached"	hamerins
19940	Nested Virtualization makes guest os freeze	VirtualBox 6.1.14	2020-10-05T13:57:58Z	2020-10-05T13:57:58Z	2020-10-05T13:57:58Z	"I have the last version of virtualbox and I have Kali Linux virtual machine and I want to start android virtual machine on it and I have done the setup for everything and enabled Nested virtualization in virtualbox and installed kvm on guest os for acceleration but every time I try to start the emulator, It appears with the message:-


""Emulator is running using nested virtualization. This is not recommended. It may not work at all. And typically the performance is not quite good.""


and the guest os suddenly freezes totally and no longer responds.

My PC's CPU is Intel core I7-8750H (6 cores) and 16GB ram.
What is the problem? How can I solve it?"	MINE
19997	Nested virtualization, Windows 8.1 64bit, multiple CPUs lead to crash	VirtualBox 6.1.14	2020-10-25T14:03:56Z	2020-10-25T14:03:56Z	2020-10-25T14:03:56Z	"Forum topic:[https://forums.virtualbox.org/viewtopic.php?f=6&t=100373]
Host Machie: Windows 10 64bit (i9 9900K 8core)
Guest Machine1: Debian 10 64bit (4core allocated)
Guest Machine2: Windows 8.1 64bit

Host Machie contains Guest Machine1, and Guest Machine1 contains Guest Machine2, it's nested virtualization.

When I run Windows 8.1 64bit in Host Machie with multiple CPUs, no crash, everything is fine.
But when I run Windows 8.1 64bit in Guest Machine1, I can only allocate 1 cpu, if more then 1 cpu are allocated, it will crash after I click start."	larisa_serova
20048	Nested VMs on Intel without VMCS Shadowing	VirtualBox 6.1.16	2020-11-18T14:31:01Z	2020-11-21T04:56:01Z	2020-11-21T04:56:01Z	"Having nested VMs as of 6.0 is great, but the requirement for Intel VMCS Shadowing means that it's only available on a limited set of CPUs.

Is there any chance of adding for support on CPUs that do not have VMCS Shadowing? At least for Linux guests?"	Grunthos
15642	Never fixed VBox 5.1/5.0.26/24 VGA: fixed an occasional hang when running Windows guests with 3D enabled	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
17994	New fearture: Clone with blank disk	VirtualBox 5.2.18	2018-09-18T12:45:52Z	2018-09-18T13:38:27Z	2018-09-18T13:38:27Z	I would like to propose a new feature. I would like to propose a ability to clone a machine with blank disk to have ability to create machine with the same settings.	xearo
17965	New Kali Linux Kernel 4.17.0 error	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
15422	New Linux kernel triggers udev hang	VirtualBox 5.0.20	2016-05-16T07:01:20Z	2016-05-20T03:32:02Z	2016-05-20T03:32:02Z	"Kernel: linux-image-4.5.0-0.bpo.1-686-pae

This is where it hangs:
http://s.natalian.org/2016-05-15/debug2.png

This is the strace screen capture:
http://s.natalian.org/2016-05-16/strace-usr-lib-systemd-systemd-udevd.png

Able to reproduce on Archlinux & Windows 10."	hendry
18775	New VM wizard fails to delete directory if going back one step in the wizard.	VirtualBox 6.0.10	2019-07-21T06:15:10Z	2019-07-21T06:15:10Z	2019-07-21T06:15:10Z	"
== Steps to reproduce ==

1. Menu ""Machine"" » ""New..."", ""Guided Mode"".
2. Enter the VM name, e.g. ""Windows 2012"".
3. Press ""Continue"", a directory with the same name is created in the default VM location.
4. __Press ""Back""__, because you realize that you actually wanted to be in ""Expert"" mode.
5. Switch to ""Expert Mode"".
6. Re-enter the VM name ""Windows 2012"", because the two wizards are independent, AFAIK.
7. Press ""Create"".
> ''Cannot create the machine folder '''Windows 2012''' in the parent folder '''/Users/Shared/VirtualBox/Machines'''.''
> 
> ''This folder already exists and possibly belongs to another machine.''

== Steps to reproduce, part deux ==

1. Menu ""Machine"" » ""New..."", ""Guided Mode"".
2. Enter the VM name, e.g. ""Windows 2012"".
3. Press ""Continue"", a directory with the same name is created in the default VM location.
4. __Press ""Back""__, because you realize that you inputted the wrong VM name.
5. Change the VM name to ""Windows 2012 (64)"".
6. You still have a directory named ""Windows 2012"" in the default location.

== Resolution ==
When backing up at step 4, make sure that the newly created empty directory is deleted.



=== Note ===

 I put in 6.0.10 as the version affected, but obviously this goes way, way back..."	Socratis
15005	no 3D accelaration when using WebService or VBoxManage startvm --headless (iGPU HD4000)	VirtualBox 5.0.12	2016-01-04T12:34:46Z	2016-01-11T12:36:14Z	2016-01-11T12:36:14Z	"{{{
Host:cat /etc/*-releaseDISTRIB_ID=LinuxMint
DISTRIB_RELEASE=17.3
DISTRIB_CODENAME=rosa
DISTRIB_DESCRIPTION=""Linux Mint 17.3 Rosa""
NAME=""Ubuntu""
VERSION=""14.04.3 LTS, Trusty Tahr""
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME=""Ubuntu 14.04.3 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/""
cat: /etc/upstream-release: Is een map
Linux Cinnamon 64 bit
}}}
 1. procedure: installed latest VB & extension pack
 2. installed phpvirtualbox 5.0.4
 3. import via webinterface a Win7 appliance

When starting appliance, following error occors:

''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)''

3D is working & enabled

glxgears work ok 
{{{
/usr/lib/nux/unity_support_test -p
OpenGL vendor string:   Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Ivybridge Mobile 
OpenGL version string:  3.0 Mesa 10.5.9

Not software rendered:    yes
Not blacklisted:          yes
GLX fbconfig:             yes
GLX texture from pixmap:  yes
GL npot or rect textures: yes
GL vertex program:        yes
GL fragment program:      yes
GL vertex buffer object:  yes
GL framebuffer object:    yes
GL version is 1.4+:       yesr

Unity 3D supported:       yes
}}}
is also ok. 

The appliance can only be started directly in VB interface, not via VboxManage or webinterface."	peter_temp
18406	no 64 bit guest support in VB on  intel 64bit CPU and 64bit Kubuntu 18.4 host	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
11508	No detection of screen size change in fullscreen when using xubuntu/xfce4 as host	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
14473	No emails from answers to my tickets, adding address to the CC field impossible		2015-08-19T09:41:06Z	2015-08-19T12:40:13Z	2015-08-19T12:40:13Z	"I just noticed that I don't receive emails from my ticked #14363, since my email address was not in the CC field. This is bad, since I missed answers. It should be the default.

Moreover I don't see a way to add my email address to the CC field later. It would be important to have this option."	Frank Breitling
20922	No Ethernet Ubuntu/Windows guest after computer wake host from sleep	VirtualBox 6.1.30	2022-04-30T13:37:42Z	2022-04-30T13:37:42Z	2022-04-30T13:37:42Z	"'''Problem'''
- Broken Ethernet TX/RX in Ubuntu/Windows guest after computer wake from sleep.
- Wireshark in the guest shows TX packets, but no incoming packets.
- Wireshark in the host does not show any network traffic from/to the guest.

'''Setup'''
- VirtualBox v6.1.30 or v6.1.32
- Windows 10 20H2 host (updates installed of today)
- Ubuntu 21.04 guest or Windows 10 guest (updates + guest additions installed)
- VM Intel (R) i211 Gigabit Network connection (default)
- VM Bridge network

'''Reproducible testcase'''
1. Make sure Ethernet works on the host and guest.
2. Set computer in sleep mode.
3. Wake computer.
4. Network on host works.
5. Network in guest broken: TX and RX failed according to WireShark logs.

'''Additional info'''
- Reproducible on AMD Ryzen 7/9 and Intel Core I7 laptops/desktops.
- Hyper-V on host not enabled.
- Disabling/enabling network in guest does not work.
- Ethernet cable disconnect/reconnect host does not work.
- Virtual Ethernet link down/up guest does not work.
- Set guest in paused mode before sleep/wake host does not work.
- Disconnect Ethernet before sleep/wake host does not work.

See forum: https://forums.virtualbox.org/viewtopic.php?f=6&t=105781"	Erwin
18815	No guest DHCP through host WiFi in bridged mode	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
19618	No hardware acceleration on Ryzen7 4800HS	VirtualBox 6.1.8	2020-05-24T12:47:57Z	2020-05-24T12:47:57Z	2020-05-24T12:47:57Z	"A fresh installation of VirtualBox 6.1.8 does not use hardware acceleration at it seems, rendering any virtual machines unusably slow. Hardware virtualization is enabled in the BIOS and confirmed to be enabled in Windows; WSL is not installed. Any ideas?

Relevant log sections:

00:00:01.644840 VirtualBox VM 6.1.8 r137981 win.amd64 (May 14 2020 20:30:31) release log
00:00:01.644845 Log opened 2020-05-24T12:33:30.149262000Z
00:00:01.644845 Build Type: release
00:00:01.644848 OS Product: Windows 10
00:00:01.644849 OS Release: 10.0.18363
00:00:01.644849 OS Service Pack: 
00:00:01.687333 DMI Product Name: ROG Zephyrus G14 GA401IU_GA401IU
00:00:01.690421 DMI Product Version: 1.0       
00:00:01.690432 Firmware type: UEFI
...
00:00:01.752227 HM: HMR3Init: Attempting fall back to NEM: AMD-V is not available
00:00:01.762066 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...
...
00:00:01.762195 NEM: Warning! Unknown CPU features: 0x77cb66f39fbf
00:00:01.762200 NEM: WHvCapabilityCodeProcessorClFlushSize = 2^8
00:00:01.762433 NEM: Warning! Unknown capability 0x1003 returning: 1f 38 00 00 00 00 00 00
00:00:01.762982 NEM: VidGetHvPartitionId            -> fun:0x2210a7 in:0x0 out:0x8
00:00:01.762986 NEM: VidStartVirtualProcessor       -> fun:0x221174 in:0x4 out:0x0
00:00:01.762989 NEM: VidStopVirtualProcessor        -> fun:0x221180 in:0x4 out:0x0
00:00:01.762993 NEM: VidMessageSlotHandleAndGetNext -> fun:0x2210df in:0x8 out:0x0
00:00:01.763178 NEM: Created partition 0000000001400120.
00:00:01.763186 NEM: Adjusting APIC configuration from X2APIC to APIC max mode.  X2APIC is not supported by the WinHvPlatform API!
00:00:01.763188 NEM: Disable Hyper-V if you need X2APIC for your guests!
00:00:01.763383 NEM: NEMR3Init: Active.
00:00:01.763389 MM: cbHyperHeap=0x280000 (2621440)
00:00:01.765079 CPUM: No hardware-virtualization capability detected
00:00:01.767312 CPUM: fXStateHostMask=0x7; initial: 0x7; host XCR0=0x7
00:00:01.771177 CPUM: Matched host CPU AMD 0x17/0x60/0x1 AMD_Zen_Ryzen with CPU DB entry 'AMD FX-8150 Eight-Core' (AMD 0x15/0x1/0x2 AMD_15h_Bulldozer)
..."	ebfe
20327	No instala máquina virtual de windows Server	VirtualBox 6.1.20	2021-04-28T08:58:12Z	2021-04-28T08:58:12Z	2021-04-28T08:58:12Z	Al iniciar la instalación de Windows Server, se producen un error en VirtualBox	Juanma
11451	no keyboard and mouse after sleep with Win7	VirtualBox 4.2.6	2013-02-03T16:31:02Z	2015-07-03T15:41:35Z	2015-07-03T15:41:35Z	"After opening the lid on my Macbook Air (13"" mid 2012, 1.8GHz, 8GB, running OSX 10.8.2) and waking up from sleep mode, keyboard and mouse input doesn't work any more. But the system itself is not frozen, it updates emails etc. The only way is to hard reboot. This happens only when the lid is closed for more than maybe 30min (can't tell exactly). 

The issue happens when the guest system Win7 Pro 32 Bit is running, even with no running application. deactivated sleep mode in Win 7 without any improvement. 
Virtualbox and extensions are Version 4.2.6. 

[https://forums.virtualbox.org/viewtopic.php?f=8&t=53947]"	maerz001
17346	No machine can be started on MacMini 10.12.6 host	VirtualBox 5.2.0	2017-12-05T07:50:18Z	2017-12-05T09:19:14Z	2017-12-05T09:19:14Z	"Hi, i wrote in the forum and they told me to open a bug.

I bought a macmini with 10.13 preinstalled and installed 10.12.6.
Virtualbox installer is running without errors, and i can add machines. As soon as i start a machine (xp, mac, ubuntu, any....) it write an error and guru meditation.

kextstat | grep -v com.apple

{{{
Index Refs Address            Size       Wired      Name (Version) UUID <Linked Against>
  132    3 0xffffff7f83292000 0x63000    0x63000    org.virtualbox.kext.VBoxDrv (5.2.2) 62C4748E-00E8-38C9-8820-3C8791212EA9 <7 5 4 3 1>
  134    0 0xffffff7f832f5000 0x8000     0x8000     org.virtualbox.kext.VBoxUSB (5.2.2) 9C6CEA90-40EE-323B-8A1F-AF84BC91E127 <133 132 40 7 5 4 3 1>
  135    0 0xffffff7f832fd000 0x5000     0x5000     org.virtualbox.kext.VBoxNetFlt (5.2.2) 5A0170AB-E76F-3CCE-A017-2FB020D6BFD0 <132 7 5 4 3 1>
  136    0 0xffffff7f83302000 0x6000     0x6000     org.virtualbox.kext.VBoxNetAdp (5.2.2) 5B0F7EF3-7B51-3AA7-B60C-5C9615288D9A <132 5 4 1>
}}}

Hope you can help me"	_michael
19999	no me deja aceptar las configuraciones que deseo aplicar en mi virtual box	VirtualBox 6.1.16	2020-10-26T04:21:42Z	2020-10-26T04:21:42Z	2020-10-26T04:21:42Z		roldan0314
20056	no mouse pointer or capture after login	VirtualBox 6.1.16	2020-11-21T15:17:33Z	2020-11-21T15:17:33Z	2020-11-21T15:17:33Z	"Until 11/17/20, my VM worked perfectly. Now, the mouse works UNTIL I login. But AFTER login, the capture is no longer working. There is NO mouse pointer on the virtual desktop, just the REAL mouse pointer, which moves anywhere, in or out of the Virtualbox.
The Vbox message (at the top of the window) saying the capture is effective shows and the capture icon indicates the mouse integration is on, but it is NOT being captured.
Using the CNTRL key to get the ""capture"" window and allowing capture, the mouse is NOT captured. 

I am using VBOX 6.1.16. My guest O/S is Ubuntu 20.04.1-AMD64. 
My HOST O/S is Windows 10 Pro 64-bit. I/O APIC was already on and I left it on.
I have tried:
*VMSVGA vs. VBOXSVGA vs VBOXVGA
*increase video memory to 128MB
*1 vs 2 CPUs
*USB tablet vs PS/2 Mouse
*paravirtualization: default vs minimal
*re-install Vbox extensions
* Enable PAE/NX
*3D accel on vs off
None of these make any difference. 
""File>send shutdown signal"" does NOT shut down the VM.

"	Dennis Foreman
15909	No notification of major new releases	VirtualBox 5.0.26	2016-09-08T13:06:06Z	2016-09-08T13:06:06Z	2016-09-08T13:06:06Z	VB 5.0.26 was released on July 18, 2016. It wasn't until I browsed virtualbox.org on Sept. 8, 2016 that I learned that there was a major dot release (x.0 to x.1) available that had two maintenance releases after July 18. It appears that the built in upgrade notification is failing to notify when stable dot releases are available (I am assuming that a second maintenance release of a dot release = stable).	Aren Cambre
17303	"No obvious way to exit snapshot ""Properties"" without changes"	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
21423	No repo for Fedora 37	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
17076	No sound from any guest OS	VirtualBox 5.1.26	2017-09-12T15:48:49Z	2019-02-13T11:16:00Z	2019-02-13T11:16:00Z	I never get any sound from guest OSs.  I have tried many Windows and Linux guests with the same result.  The Host OS is Windows 8.1.  This problem has existed for many versions of VirtualBox	mafw
19067	No sound from any guest when using ALSA (PulseAudio works)	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
15250	No sound in W2012-2008 Server	VirtualBox 5.0.16	2016-03-17T10:34:50Z	2016-03-18T14:38:57Z	2016-03-18T14:38:57Z	"Sound device is detected, but Audio Output is absent.

For Server version of Windows only. Workstation versions are emulated fine."	MikhailRokhin
18692	No sound or internet with Virtualbox 6	VirtualBox 6.0.8	2019-06-06T22:59:15Z	2019-06-27T14:13:57Z	2019-06-27T14:13:57Z	"Using ALSA and NAT. Tried an earlier version, sound also didn't work, had to revert to an old version of Virtualbox 5. Too many system-wide updates this time with my kernel and other software, can't revert, so if this is unfixable I'll probably have to go with VMWare until they can iron these bugs out. I've been using Virtualbox for years and years with occasional issues but now it seems I've hit a wall.

Also, for the record I have the same problems in the latest version of Virtualbox 5."	shillshocked
19046	"No Ubuntu 19.10 ""eoan"" packages"	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
17589	No virtual screen repaint when external monitor is connected to laptop.	VirtualBox 5.2.8	2018-03-05T10:44:33Z	2018-03-05T10:44:33Z	2018-03-05T10:44:33Z	"I have Windows 10 host with Ubuntu 16.04 guest. With enabled 3D acceleration (which is required because without that everything is laggy) and external monitor connected (tested with dvi and mini display port), the drawing on virtual screen freezes when in gnome. It does not matter whether monitor is an extension, clone or primary display. Immediately after monitor disconnection, the virtual screen starts to repaint.

Under the frozen screen the system is running (cursor changes with the windows even after repositioning which is not visible on the frozen screen, ctrl alt fx can be used to display working and visible shell).

When 3D acceleration is disabled, screen repaints fine with external monitor connected. 
I tested also development version 5.97 with the same result."	mvodolan
9926	No virtual system boot with grub2 on mbr for raw disk access to specific partitions	VirtualBox 4.1.6	2011-11-20T18:53:01Z	2013-04-04T06:48:32Z	2013-04-04T06:48:32Z	"Recent Linux systems, such as Fedora 16, use the newer grub2 boot loader.  The usual grub2 setup places the boot code on the mbr and on the unpartitioned sectors immediately follow the mbr partition.  If a virtual guest Linux system is made using raw parition access to Linux code on a partition(s) separate from the host system partition(s), the grub2 boot code is not accessible unless the whole disk is attached rather than just the partitions containing the guest system.

For example, with a Windows 7 64bit host on partition 3 of disk 0 and Fedora 16 on partitions 5 and 6, and with grub2 installed on the mbr of disk0, VirtualBox will not boot a Fedora 16 x86_64 guest unless the vmdk is created with whole disk access to disk0.  If the vmdk is created with access to only partitions 5 and 6, Fedora does not boot and hangs after the boot code in the mbr is executed.  The code in the sectors following the mbr sector is not reached.  Given that it is dangerous for the virtual system to have direct access to the host operating system code, the grub2 boot code should be accessible when only individual partitions are attached.  For Windows hosts, the -relative option is not available for createrawvmdk so this option cannot be tested as a solution with Windows hosts.
"	Leo Pilachowski
18303	No way in the GUI to reset the per-VM scale factor to follow the global one.	VirtualBox 6.0.0	2019-01-11T19:00:42Z	2019-01-11T19:00:42Z	2019-01-11T19:00:42Z	"If you set ''(even once)'' the per-VM scale factor in VM Settings > Display > Screen > Scale Factor, then an ExtraData item is inserted in the .vbox configuration file:
{{{
<ExtraDataItem name=""GUI/ScaleFactor"" value=""1.5""/>
}}}
Once that setting is there, there's no way to reset it back to follow the global scale factor from the GUI, only from the CLI:
{{{
VBoxManage setextradata <uuid|vmname> ""GUI/ScaleFactor""
}}}
A mechanism is needed, such as a ""`Reset to Defaults`"" or ""`Reset to Global`"" button, where the ExtraData item is removed, and the VM follows the global settings."	Socratis
16901	Non-driver certificates not handled correctly by hardening (OpenText SOCKS)	VirtualBox 5.1.22	2017-07-14T10:03:31Z	2017-09-15T13:22:10Z	2017-09-15T13:22:10Z	"I had originally raised an issue with OpenText socks that theri DLL was not signed and so did not work with VirtualBox. They have now provided a signed version, but it is not signed with a driver certificate. According to OpenText support VirtualBox is not handling the signing check correctly. Some of my correspondance with OpenText support pasted below.

----------------------------------------------------------------------------
---- From OpenText Support -----

Hello Lars,

In regards to ticket #3056978, I received input from Engineering.  This issue appears to be related to the third party application.

According to Engineering: 
If you used signtool, it would show DLL is properly signed.  Note, using the default option, will show a trust error because the default assumes driver signing and this is a not a driver with signed catalog file.  You need to use /pa argument for the signing to show as valid.  Since you use SigCheck (Sysinternals), you do not need to use any parameters to show the DLL is signed

C:\Users\xx>sigcheck64 ""c:\Program Files\Open Text\SOCKS Client\*"" > C:\xx\sigcheck_socks.14.0.16.txt

(Refer to the output in the attached file.)
 

The root issue is that Virtualbox process will have HumSOCKS.dll injected into its process space (this is simply how SOCKS works on Windows).  On startup it does a complicated self-validation on itself and all loaded DLLs in the main process space.  Essentially the rules force that all DLLs need to be signed properly (or a couple of other exceptions for specific location and owner of file).  It appears that their code fails the same way that signtool does without the /pa flag and ultimately will not start up when we are in their process space because of that.  In one sense this is correct behavior because there's no signed catalog file for us at all but it's definitely unwanted because it should not apply that logic for 3rd party dlls that are not drivers.

This appears to be a long standing issue with VirtualBox - check out https://www.virtualbox.org/ticket/13659.  The corrupted path it starts out as is not a problem for us but the exact same issue with failed trust for a correctly signed DLL is the main issue left.

Regards,
OpenText Support



---- From me to OpenText Support ---
To: support@opentext.com
Subject: Re: FW: OTCS Ticket 3056978 Socks 14:  VirtualBox does not work when SocksClient is installed

Hi, I have tried your recommendation of importing the certificate. I also tried disabling the virus scanner. I also tried importing the intermediate certificate and tried loosening some policy settings, but nothing solves the problem. SHA-256 certificates show up fine in Windows and the patch required for support is installed.   The error I'm getting in the VBoxHardening.log is:

{{{
14a4.1a9c: supHardenedWinVerifyImageByHandle: -> -23021 (\Device\HarddiskVolume1\Program Files\Open Text\SOCKS Client\HumSOCKS.dll) WinVerifyTrust
14a4.1a9c: Error (rc=0):
14a4.1a9c: supR3HardenedScreenImage/LdrLoadDll: rc=Unknown Status -23021 (0xffffa613) fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume1\Program Files\Open Text\SOCKS Client\HumSOCKS.dll: None of the 1 path(s) have a trust anchor.: \Device\HarddiskVolume1\Program Files\Open Text\SOCKS Client\HumSOCKS.dll 
14a4.1a9c: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Program Files\Open Text\SOCKS Client\HumSOCKS.dll
14a4.1a9c: Error (rc=0): 
14a4.1a9c: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Program Files\Open Text\SOCKS Client\HumSOCKS.dll' (C:\Program Files\Open Text\SOCKS Client\HumSOCKS.dll): rcNt=0xc0000190
14a4.1a9c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0xc0000190 'C:\Program Files\Open Text\SOCKS Client\HumSOCKS.dll'
}}}"	Lars Hupfeldt
21323	Non-mouse Integration	VirtualBox-7.0.4	2022-12-01T02:00:54Z	2022-12-01T02:00:54Z	2022-12-01T02:00:54Z	I have noticed that whenever I disable mouse integration on my virtual machines, my mouse would jump to the top left corner of my screen when I captured it. If I re-enable mouse integration it works as expected. Looking through the logs, I don't notice anything unusual, but I've attached them anyway. I've used a Windows 10 virtual machine as my test.	Harvey Walker
18260	Not able to Start VM in Virtual Box when Bridge Adapter Network Setting is Selected After latest update to Windows 10	VirtualBox 6.0.0	2019-01-01T07:40:50Z	2019-01-05T15:27:30Z	2019-01-05T15:27:30Z	"Hi Team,

I am Not able to start VM on virtual box when Bridge Adapter Network Setting is Selected and This is seen after latest update to Windows 10.

Have tried all the possible solutions listed in google, Nothing Worked.

Have tried 5.2.18, 5.2.22 and also 6.0 versions of VB but observing same Error on all these version.

Below Error is Observed:

Failed to open a session for the virtual machine .

Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter' (VERR_INTNET_FLT_IF_NOT_FOUND).

Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

"	Linda
20901	not letting me create a user name	VirtualBox 6.1.32	2022-04-14T23:15:31Z	1970-01-01T00:00:00Z	1970-01-01T00:00:00Z	Hi, Im trying to set up my account but am unable to create a user name	Alyssa
13836	Not rendering the window properly when in fullscreen	VirtualBox 4.3.22	2015-02-14T23:45:56Z	2015-02-14T23:45:56Z	2015-02-14T23:45:56Z	"I'm developing a small program (call it myProgram) with XWindow Server in Ubuntu 14 that uses fullscreen.

The problem is, if both VirtualBox and the myProgram are set to fullscreen, nothing re-renders.

If VirtualBox is not set to fullscreen (is set to windowed mode), it renders as it should even if the myProgram is in fullscreen.

'''How do I reproduce this issue:'''[[BR]]
    1 - Inside Guest OS in VirtualBox, in ""fullscreen mode"", run the myProgram in fullscreen;[[BR]]
    2 - Nothing redraws until exit fullscreen in the myProgram;

'''If, before running the  myProgram, I:'''[[BR]]
    1 - Uncheck ""Auto-resize Guest Display"";[[BR]]
    2 - Exit fullscreen mode from VirtualBox (enter Windowed mode); and[[BR]]
    3 - Run the myProgram in fullscreen;
Knowing that the Guest Display is with the same size as before, I can see that the myProgram renders perfectly.

Can't test in ""Seamless Mode"", and works great if in ""Scaled Mode"" too

Host System: Windows 8.1 (x64)[[BR]]
Guest System: Ubuntu 14.04.1 (x64)[[BR]]
Graphics Card: NVidia Geforce GTX560M (Drivers updated)[[BR]]
Display size: 1920x1080 (for Host and Guest OSs)[[BR]]
VirtualBox: v4.3.22[[BR]]
VirtualBoxGuestAditions: Installed (v4.3.22)"	FabioEMSM
17279	Not Responding when going to settings after upgrade	VirtualBox 5.2.0	2017-11-16T12:10:05Z	2017-11-16T12:10:05Z	2017-11-16T12:10:05Z	"Upgraded to 5.2 - When going to settings of any previous or new VM - it
freezes and says ""not responding"". it never recovers and you must force close
VirtualBox. Just had a couple of Windows updates prior to this upgrade.
(KB4049011) and (KB4048954)
Windows 10 Pro Version 1703
SurfaceBook"	marshef
16318	Not Signed with the Build Certificate error after installing 5.1.12 r112440	VirtualBox 5.1.12	2016-12-23T08:55:56Z	2020-05-07T22:15:45Z	2020-05-07T22:15:45Z	"I have just installed !VirtualBox 5.1.12 !r112440 on a Windows host running Windows 10 Professional, and when trying to run a VB image for the first time I get this error:

''!VirtualBox - Error In supR3HardenedWinReSpawn
NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status -5657 (0xffffe9e7) (rcNt=0xe986e9e7)
VBoxDrvStub error: Not signed with the build certificate.: \Device\HarddiskVolume4\Program Files\Oracle\!VirtualBox\!VirtualBox.exe (rc=-5657)
Make sure the kernel module has been loaded successfully.''

VERR_SUP_VP_NOT_SIGNED_WITH_BUILD_CERT (-5657) - The image is required to be signed with the same certificate as the rest of !VirtualBox.

Previous to installing this version, all !VirtualBox images have worked perfectly fine, with the only change to my machine between last night and this morning being that I've installed the new version of !VirtualBox."	Shaun Collier
4088	Noticeable audio latency	VirtualBox 2.2.2	2009-05-24T10:00:58Z	2016-10-22T15:52:58Z	2016-10-22T15:52:58Z	"There is a noticeable delay between when the guest operating system starts to play a sound, and when it actually becomes audible. Perhaps in the range of 100-200 ms--just a guess though, I'm not sure how to time it.

The host is Vista Home Basic x64 and the guest is Debian running Linux 2.6.26."	Sam Morris
21397	NS_ERROR_FAILURE (0X80004005) / signal 9 in VirtualBox 7.0.4 on macOS Ventura 13.1 host	VirtualBox-7.0.4	2023-01-06T21:00:09Z	2023-01-06T21:00:09Z	2023-01-06T21:00:09Z	"After upgrading first my host machine's OS to Ventura, and then my VirtualBox to 7.0.4 (from Monterey and 6.1.40, respectively), I can no longer start any virtual machine normally, regardless of host OS, including newly-created VMs.  Attempting to start one results in:

The virtual machine 'machine' has terminated unexpectedly during startup because of signal 9.

Result Code: NS_ERROR_FAILURE (0X80004005)
Component: MachineWrap
Interface: IMachine {300763af-5d6b-46e6-aa96-273eac15538a}

The crash report, which notes ""Exception Type:  EXC_CRASH (SIGKILL (Code Signature Invalid)),"" is attached.  As the host does not start, there is no data in the VBox.log.   I '''can''' start any VM in headless mode successfully and connect to it via Remote Desktop."	AndersenSilva
18929	NS_ERROR_INVALID_ARG (0x80070057)	VirtualBox 6.0.12	2019-09-15T19:23:17Z	2019-09-20T04:08:16Z	2019-09-20T04:08:16Z	"Virtual machine created with Windows 10 host, then I open it with linux host, shows this error:


{{{
Cannot register the DVD image '/mnt/vbox/drive/C:/Program Files/Oracle/VirtualBox/VBoxGuestAdditions.iso' {27740a7d-9e4a-43b6-a1be-5aa7f87287e7} because a CD/DVD image '/mnt/vbox/another/C:/Program Files/Oracle/VirtualBox/VBoxGuestAdditions.iso' with UUID {27740a7d-9e4a-43b6-a1be-5aa7f87287e7} already exists.


Result Code: 
NS_ERROR_INVALID_ARG (0x80070057)
Component: 
VirtualBoxWrap
Interface: 
IVirtualBox {d0a0163f-e254-4e5b-a1f2-011cf991c38d}
}}}

Doesn't give me any option to fix it, Vmware Workstation doesn't have these kind of problems, it handles it automatically.
"	DeGarden
20177	NtCreateFile(\Device\VBoxDrvStub) failed	VirtualBox 6.1.18	2021-02-09T23:18:44Z	2021-02-13T19:11:22Z	2021-02-13T19:11:22Z	"
Did the following:

1.) Downloaded the latest 6.1 test build from
    https://www.virtualbox.org/wiki/Testbuilds, and installed it.

    In VBoxHardening.log, this build is identified as
      10.0.19041.662 (WinBuild.160101.0800)

2.) Created a new, blank VM, and attempted to boot that VM via the Iso file
      CentOS-8.3.2011-x86_64-dvd1.iso

3.) Started the VM, got the error message

1d38.32f4: NtCreateFile(\Device\VBoxDrvStub) failed: 0xc0000034 STATUS_OBJECT_NAME_NOT_FOUND (0 retries)

Driver is probably stuck stopping/starting. Try 'sc.exe query vboxdrv' to get more information about its state. Rebooting may actually help.


I'll attach the VBoxHardening.log.
"	JochenW
17662	NtCreateFile(\Device\VBoxDrvStub) failed: 0xc0000034 STATUS_OBJECT_NAME_NOT_FOUND (0 retries)	VirtualBox 5.2.8	2018-04-03T17:57:25Z	2018-04-19T21:26:40Z	2018-04-19T21:26:40Z	"Unable to start the VM after system reboot

{{{

{{{
9d4.9d8: supR3HardNtChildPurify: Done after 1093 ms and 1 fixes (loop #1).
9d4.9d8: supR3HardNtEnableThreadCreation:
293c.2ac4: Log file opened: 5.2.8r121009 g_hStartupLog=0000000000000004 g_uNtVerCombined=0xa03ad700
293c.2ac4: supR3HardenedVmProcessInit: uNtDllAddr=00007ff906860000 g_uNtVerCombined=0xa03ad700
293c.2ac4: ntdll.dll: timestamp 0xb79b6ddb (rc=VINF_SUCCESS)
293c.2ac4: New simple heap: #1 0000000000c00000 LB 0x400000 (for 1945600 allocation)
293c.2ac4: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume1\Program Files\Oracle\VirtualBox'
293c.2ac4: System32:  \Device\HarddiskVolume1\Windows\System32
293c.2ac4: WinSxS:    \Device\HarddiskVolume1\Windows\WinSxS
293c.2ac4: KnownDllPath: C:\WINDOWS\System32
293c.2ac4: supR3HardenedVmProcessInit: Opening vboxdrv stub...
293c.2ac4: Error opening VBoxDrvStub:  STATUS_OBJECT_NAME_NOT_FOUND
293c.2ac4: supR3HardenedWinReadErrorInfoDevice: NtCreateFile -> 0xc0000034
293c.2ac4: Error -101 in supR3HardenedWinReSpawn! (enmWhat=3)
293c.2ac4: NtCreateFile(\Device\VBoxDrvStub) failed: 0xc0000034 STATUS_OBJECT_NAME_NOT_FOUND (0 retries)

Driver is probably stuck stopping/starting. Try 'sc.exe query vboxdrv' to get more information about its state. Rebooting may actually help.
9d4.9d8: supR3HardenedWinCheckChild: enmRequest=2 rc=-101 enmWhat=3 supR3HardenedWinReSpawn: NtCreateFile(\Device\VBoxDrvStub) failed: 0xc0000034 STATUS_OBJECT_NAME_NOT_FOUND (0 retries)

Driver is probably stuck stopping/starting. Try 'sc.exe query vboxdrv' to get more information about its state. Rebooting may actually help.
9d4.9d8: Error -101 in supR3HardenedWinReSpawn! (enmWhat=3)
9d4.9d8: NtCreateFile(\Device\VBoxDrvStub) failed: 0xc0000034 STATUS_OBJECT_NAME_NOT_FOUND (0 retries)

Driver is probably stuck stopping/starting. Try 'sc.exe query vboxdrv' to get more information about its state. Rebooting may actually help.
}}}

}}}
"	AshokMazumder
13991	NUL character with a value of 0 ^@ Shown In Linux Console	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
15722	Number Input in Guest System on Wayland Host	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
18389	numeric username issue	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
21290	nvme error	VirtualBox 6.1.38	2022-11-20T15:44:41Z	2022-11-20T15:44:41Z	2022-11-20T15:44:41Z	I am not able to work with a drive nvme. I have a nvme disk Samsung 970Evo Plus but if I try to use a disk connected to the nvme drive it does not work al all.	tiria
20447	NVMe fails in Windows 10/11 guest	VirtualBox 6.1.22	2021-07-04T23:47:12Z	2021-07-05T21:20:34Z	2021-07-05T21:20:34Z	It's impossible to start from bootable DVD-iso connected to NVMe and Windows 10/11 setup can't detect hdd attached to NVMe to install it to.	MikhailRokhin
7756	Occasional Hang when saving machine state - data loss	VirtualBox 3.2.10	2010-11-23T12:14:02Z	2019-07-16T01:27:55Z	2019-07-16T01:27:55Z	"Hi there.

Occasionally Virtualbox fails to save the machine and hangs on 100% on the ""... Saving the execution state of the virtual machine""

I am forced to kill the VirtualBox.exe process. This unfortunately corrupts the attached virtual disk and often leads to any work done during that session to be lost.

Host Windows XP SP2"	Nazar
16668	Office apps display error in seamless mode	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
20205	OL8 VM aborted - appears screen resize or USB related	VirtualBox 6.1.16	2021-02-19T12:24:44Z	2021-02-19T12:24:44Z	2021-02-19T12:24:44Z	"Two suspects for my VM aborting:

1. USB. I use a USB dongle and regularly attach/detach via the VBox device menu.

2. Screen resize.  I frequently resize my VM window as I shuffle windows around to different displays, snap to one side of the screen, etc."	mocooern
17424	Old Linux on Virtual Box 5.2.4 gets Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)	VirtualBox 5.2.4	2018-01-05T23:58:48Z	2018-01-08T21:38:36Z	2018-01-08T21:38:36Z	"Migrating a running (older) Linux guest from Mac OS hosted VirtualBox 5.2.3 to FreeBSD hosted
VirtualBox 5.2.4.

Exported all the machines as an appliance from 5.2.3 and imported them to the 5.2.4.

All virtual machines operate correctly except a rather ancient Linux that fails to boot
with a VCPU0: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)

I will attach the log files."	Dave Rivers
16045	On later RHEL6.8 kernels, hostonly networks stop working after just a few minutes	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
18757	On Windows!0 very often the VM Win10 or Win7 goes in stuck state	VirtualBox 6.0.8	2019-07-15T17:14:15Z	2019-07-16T00:49:02Z	2019-07-16T00:49:02Z	"Usually, on my Win10 laptop I use a VM with operative system Win10 and or Win7, because I need to work indifferente LAN via VPN connection.
3 or 4 time in a day this VM goes in stuck, I can't open or use any vindows in the VM, but the process uses about the 30% of the CPU.
The only way that I have to return to use the VM is to kill the Virtual Box process and restart the VM.
I did not have this problem in the past with VirtualBox 5.x, now I have installed the VirtualBox 6.0.8 release in my laptop.

Thanks for your support"	dzerlottin
14117	One Linux guest crashes on OS X (10.10.3) host in AioMgr0 or Port0 thread	VirtualBox 4.3.26	2015-05-15T09:23:34Z	2015-05-15T09:23:34Z	2015-05-15T09:23:34Z	"Having two VM on same machine with very similar (but not cloned) setup. 

One crashes frequently. Other one just keep going. 

I am seeing two different crashes. Both are attached. I have seem them both with headless and GUI guests-

"	Dennis Schafroth
21494	Only crashes and error messages since the update to 7.0.6	VirtualBox-7.0.6	2023-02-12T11:33:02Z	2023-02-12T11:33:02Z	2023-02-12T11:33:02Z	"The update has been around for a while, though I've always put it off until now. And as it turns out, for a good reason: since the latest update, I only get error messages. I don't know what the new ""update"" is supposed to bring, except some improvements in the GUI. 

PC was already restarted after the update, just as info. 

So, the problem is that sometimes I can start a new VM and sometimes not. The VM is W10, if relevant. Everything has remained as it is so far, nothing was changed at all after the update. It's even worse when I want to boot/activate a saved state, that doesn't work at all by now since the update. There come then error messages like:

Callee RC:


RPC_S_SERVER_UNAVAILABLE/0x800706ba (0X800706BA)


or


The instruction at 0x... referenced memory at 0x0000000000. The memory could not be written. Click on OK to terminate the program. Click on CANCEL to debug the program."	FrankKlein
21005	Only reserve needed RAM	VirtualBox 6.1.34	2022-06-23T09:57:38Z	2022-06-23T09:57:38Z	2022-06-23T09:57:38Z	"When VirtualBox 6.1.34 is configured On Windows 10 host, the amount of memory reserved is specified in the settings. And this amount of memory is reserved on the host by the VM when launched.

Would it be possible change the way this setting works, to define a MAX amount of memory available to the VM, and only reserve on-the-fly onto the host the real needed memory when the VM is running ?

In the way, you can launch without trouble on a 64 Gb system 10 (for example) VM that could use each one MAX 16 Gb of memory, if all of these VM only use less than 64 Gb (or better 32 Gb) of RAM in total."	Shine
12071	OpenGL 4.2 not supported	VirtualBox 4.2.16	2013-09-04T17:52:32Z	2013-09-04T19:16:38Z	2013-09-04T19:16:38Z	"Hello

Opengl in Guest machine VirtualBOX work good !
But opengl 4.2 is not supported by VirtualBOX on guest machines.
OpenGL 4.2 Function is not available.

Thank.



"	yann458
15491	opengl change of brightness not possible	VirtualBox 5.0.20	2016-06-09T08:43:35Z	2016-06-10T07:38:45Z	2016-06-10T07:38:45Z	"We have Quake 3 Demo install on our windows 7 x64 guest. The 3d acceleration is enabled. The screen is too dark and changing the brightness in display settings of game is not working.
The host machine is windows 7 x64 too."	trivalik
14513	OpenGL error with 3D acceleration enable with black screen	VirtualBox 4.3.30	2015-08-27T20:58:30Z	2015-08-27T20:58:30Z	2015-08-27T20:58:30Z	"Hi,

I'm running Ubuntu 14.04 lts trusty 64 bit on 4.3.30 r101610 on Win 7 host 64 bit.
I'm getting too many OpenGL warning and my rendering screen is going black. I'm
running gazebo robotic simulator. However if I do not use hardware acceleration then everything work fine and there are no warning. But then by simulation run very slow.
I've done almost everything regarding this issue as this is not new. I've installed the VBoxGuestAddition_4.3.30.iso. Before installing the guest addition the 3d hardware acceleration work fine and I do not get openGL warning. However I'm not able to go to fullscreen.
I've also installed latest virtual box extension pack.

Please share any suggestion."	AmitUbu
19193	Opening a photo using Windows Photo app crashes VirtualBox	VirtualBox 6.1.0	2020-01-01T20:56:44Z	2020-01-01T20:56:44Z	2020-01-01T20:56:44Z	"If I double click on a .png file in Windows Explorer, VirtualBox crashes. This happens every time I try it, so I switched to using Irfan View to view photos for now.

Host Windows 7 Pro SP1
Guest Windows 10 Pro Build 1909 (18363.535)"	Iain Waddell
15009	Opening the storage settings causes the font color to be temporary black	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
19665	OpenWRT locks up early in the kernel sequence on 6.1	VirtualBox 6.1.10	2020-06-14T18:50:19Z	2020-06-27T15:31:19Z	2020-06-27T15:31:19Z	"Tried in latest(r128535) build same thing. Something to do with # of CPUs - console log from kernel looks different between 2 vCPU and 1, but locks up regardless.
I'll attach the log and vdi, as it's reasonably small. Just in case something is wrong there, the vdi was built via ""convertfromraw"" of sourced from https://downloads.openwrt.org/releases/19.07.3/targets/x86/64/openwrt-19.07.3-x86-64-combined-ext4.img.gz, which is the latest released openwrt distro.

The image boots fine on hyper-V, vmware and physical.
"	novitk
13880	OperationalError: (1213, 'Deadlock found when trying to get lock; try restarting transaction')	VirtualBox 4.3.22	2015-02-22T13:50:42Z	2015-02-22T13:50:42Z	2015-02-22T13:50:42Z	"==== How to Reproduce ====

While doing a GET operation on `/timeline`, Trac issued an internal error.

''(please provide additional details here)''

Request parameters:
{{{
{'wiki': u'off', 'changeset': u'on', 'daysback': u'7'}
}}}

User agent: `#USER_AGENT#`

==== System Information ====
''System information not available''

==== Enabled Plugins ====
''Plugin information not available''

==== Python Traceback ====
{{{
Traceback (most recent call last):
  File ""/usr/lib/python2.4/site-packages/trac/web/main.py"", line 513, in _dispatch_request
    dispatcher.dispatch(req)
  File ""/usr/lib/python2.4/site-packages/trac/web/main.py"", line 258, in dispatch
    req.session.save()
  File ""/usr/lib/python2.4/site-packages/trac/web/session.py"", line 88, in save
    @self.env.with_transaction()
  File ""/usr/lib/python2.4/site-packages/trac/db/api.py"", line 77, in transaction_wrapper
    fn(ldb)
  File ""/usr/lib/python2.4/site-packages/trac/web/session.py"", line 137, in delete_session_cookie
    cursor.execute(""""""
  File ""/usr/lib/python2.4/site-packages/trac/db/util.py"", line 65, in execute
    return self.cursor.execute(sql_escape_percent(sql), args)
  File ""/usr/lib64/python2.4/site-packages/MySQL_python-1.2.4b4-py2.4-linux-x86_64.egg/MySQLdb/cursors.py"", line 202, in execute
    self.errorhandler(self, exc, value)
  File ""/usr/lib64/python2.4/site-packages/MySQL_python-1.2.4b4-py2.4-linux-x86_64.egg/MySQLdb/connections.py"", line 36, in defaulterrorhandler
    raise errorclass, errorvalue
OperationalError: (1213, 'Deadlock found when trying to get lock; try restarting transaction')
}}}"	Perry G
14483	Option to allocate memory dynamically	VirtualBox 5.0.2	2015-08-21T22:51:41Z	2015-08-21T22:51:41Z	2015-08-21T22:51:41Z	Similar to the ability to allocate disk space dynamically maybe this can be also implemented for the memory to make on average more of it available to the host while having the ability that the guest can still use it if needed.	Sworddragon
6752	Option to ask for password when leaving virtual machine	VirtualBox 3.2.0	2010-05-20T21:09:49Z	2010-05-20T21:09:49Z	2010-05-20T21:09:49Z	"It would sometimes be quiet useful to have an option which makes VirtualBox ask for a password when leaving a virtual machine. This feature would make it possible to let someone else use the computer (e.g. for surfing the Internet or trying out another operating system) without giving that person access to the host operating system. This way you can be sure that the other person can't access your data or do any harm to the host system (even if you give him root access in the guest system). A feature like this might also be useful for an Internet café so that customers can get full access to a virtual machine and install software on it.

This feature could possibly be implemented based on the lock screen functionality of the host operating system. When the user enters the host key, he could be asked whether he really wants to leave the virtual machine. When the user confirms, VirtualBox should lock the screen so that entering the password is required for getting back to the host system."	Jakob
17568	Option to bundle installation media into exported VM	VirtualBox 5.2.6	2018-02-26T17:51:34Z	2018-02-26T22:08:04Z	2018-02-26T22:08:04Z	"Some operating systems like SmartOS and TAILS rely on installation media continuing to be attached even after installation. Could VirtualBox include an option to bundle any attached floppies and ISO discs into the exported virtual machine, so that the virtual machine can successfully boot up?

Maybe `VBoxManage export` could get flags like --bundle-floppies, --bundle-iso (default false), that ensure these virtual devices are populated in the .OVF, and their virtual disk files (.IMG, .ISO) are copied to the exported output directory.

I see some (undocumented) iso-related flags for `VBoxManage export`, but I'm not sure if they're related."	mcandre
12440	Option to capture USB for whole VB run, or even globally	VirtualBox 4.3.4	2013-12-04T18:45:18Z	2013-12-04T18:45:18Z	2013-12-04T18:45:18Z	"Running on Windows, it seems USB capturing works on a per-VM invocation basis. You start the VM, insert the USB device, and it's captured until the VM exits. This means that multiple runs of the VM require removing and reinserting the USB device every time.

It would be useful to have an option to capture USB for the whole VirtualBox session, rather than a single VM run. 

Possibly, even a system-global capture would be useful, where the USB filter parameters would be stored by the host USB capture driver and acted upon even before VB runs. In such a case, the VB GUI (or maybe a property sheet for the USB capture driver) could have a ""release capture"" option. 

A system-global capture would prove useful in scenarios where a USB device is there exclusively for VM usage. A system-global capture would mean no removal/reinsertion at all.
"	emu1
1888	"Option to configure a VirtualBox VM to automatically ""save the machine state"" upon exciting - and do this minimized."	VirtualBox 1.6.2	2008-07-30T22:22:42Z	2008-07-30T22:22:42Z	2008-07-30T22:22:42Z	"I would like to be able to configure a particular virtual machine to automatically ""Save the Machine State"" upon closing the VM window (with the other Shutdown options still available via the host menu), I believe Paralles on the Mac works much the same way. I believe it would make for a more productive way of working with VM. Also it would be nice if the saving of the machine state would occur minimized rather than blocking my screen while it saves the machine state.

"	Joris Snellenburg
12089	Option to show host-side mouse pointer with mouse integration	VirtualBox 4.2.18	2013-09-09T19:55:11Z	2014-08-03T03:07:06Z	2014-08-03T03:07:06Z	"When mouse integration is enabled, the host-side mouse pointer is disabled and the guest OS is responsible for drawing it. This works well for desktop OSes.

However, I recently tried to run Android x86 in a VM. Being designed primarily for touch input, it does not provide a local mouse pointer at least with mouse integration enabled. Everything works well - if I move the mouse into the window, aim blindly and click, the UI will respond to the click - but since the mouse pointer is invisible, I cannot see where I am about to click.

If I disable mouse integration, Android will draw a mouse pointer - this works, but is less convenient.

Therefore I'd like to have this option - I suppose it's not too hard to implement (can be a config option in the VM settings causing the cursor not to be hidden when mouse integration is enabled) but would make things a bit more comfortable."	mvglasow
17908	Optional entries in the <MediaRegistry> section may prevent VM registration	VirtualBox 5.2.16	2018-08-02T08:32:48Z	2019-07-18T08:51:31Z	2019-07-18T08:51:31Z	"The <MediaRegistry> section of the .vbox file contains a registry of active and previously used media; HDs and DVDs, a.k.a. the Most Recently Used (MRU). The MRU list is nothing but a convenience for the end user.

'''Problem''': If there's an MRU entry that conflicts with an existing registered medium, the import/registration of a VM fails.

'''Example''': __Registered__ VM1 has an entry in the MediaRegistry section for a ''__previously used__'' DVD:
{{{
<MediaRegistry>
  <DVDImages>
    <Image uuid=""{11111111-1111-1111-1111-111111111111}"" location=""Test.iso""/>
  </DVDImages>
</MediaRegistry>
}}}
A second VM2 has the following in the MediaRegistry section for a ''__previously used__'' DVD:
{{{
<MediaRegistry>
  <DVDImages>
    <Image uuid=""{22222222-2222-2222-2222-222222222222}"" location=""Test.iso""/>
  </DVDImages>
</MediaRegistry>
}}}
The names of the DVDs are the same, the UUIDs are different (it happens more often than you think). Trying to register VM2 results in the following error:
> ''Failed to open virtual machine located in /Users/Shared/Test2.vbox.''
> 
> ''Cannot register the DVD image '/Users/Shared/Test.iso' {22222222-2222-2222-2222-222222222222} because a CD/DVD image '/Users/Shared/Test.iso' with UUID {11111111-1111-1111-1111-111111111111} already exists.''
> 
> ''Result Code: NS_ERROR_INVALID_ARG (0x80070057)''[[br]]
> ''Component: VirtualBoxWrap''[[br]]
> ''Interface: IVirtualBox {9570b9d5-f1a1-448a-10c5-e12f5285adad}''
and the import fails. Not good.

'''Workaround''': The only workaround so far is to ''manually'' edit the .vbox file and remove the __''optional''__ entry for the ""offending"" medium. Remember, this entry is purely optional, the DVD is __not__ actively attached.

'''Solution''': If an entry in the MediaRegistry section is solely used so that it can be displayed in the MRU, ignore that entry upon registration and delete that entry from the MediaRegistry section, as to not cause conflicts."	Socratis
5053	options that are unavailable should be deselected in addition to being grayed out	VirtualBox 3.0.6	2009-09-21T20:39:34Z	2009-09-21T20:46:57Z	2009-09-21T20:46:57Z	"In the VirtualBox GUI, it is confusing to have checkboxes that are selected and also grayed out (disabled).  This leads some users to think that an option is enabled, and cannot be turned off, instead of the intended meaning of ""this is not available on your system"".

This is seen for example with settings such as ""Enable VT-x/AMD-V"", where if hardware virtualization is not available on a system, a shared VM may show up with a checkbox for this setting, but the control is disabled.

I perosnally have been confused in the past with this, but I just saw it again today on the Haiku-OS bug tracker where someone posted that VirtualBox always runs with VT-X/AMD-V since the option is checked and grayed out and cannot be disabled."	Stéphane Charette
14427	Oracle 12.1.0.2 Grid Installation fails to relink VB5 on Oracle Linux 6.7 guest,OSX host	VirtualBox 5.0.0	2015-08-11T12:40:11Z	2016-01-12T09:18:00Z	2016-01-12T09:18:00Z	"When trying to install 12.1.0.2 Grid Infrastructure on Linux 6.7 guest on OS X (Yosemite) host using !VirtualBox 5 the installer hangs at 59% (after passing all the Oracle pre-requisites) with the error
{{{
error invoking target irman ioracle of makefile /u01/app/gi/12.1.0.2/grid/rdbms/lib/ins_rdbms.mk”
The logs provide further detail.

INFO: /usr/bin/ld: cannot find -ljavavm12
collect2: ld returned 1 exit status

INFO: make: *** [/u01/app/gi/12.1.0.2/grid/rdbms/lib/oracle] Error 1
}}}
It is possible to work around this by copying the libjavavm12.a library located in $ORACLE_HOME/javavm/jdk/jdk7/lib to $ORACLE_HOME/lib directory and retrying the install.

Once the workaround is applied, the installer continues but then the oracle root.sh script fails with a segmentation fault.
{{{
rootconfig.sh: line 131: 4562 Segmentation fault
}}}

A workaround can be applied by reinstalling the Perl binaries under the newly created ORACLE_HOME and the installation can continue.

Both errors and their work arounds are described here:
http://laurent-leturgez.com/2015/05/26/oracle-12c-vmware-fusion-and-the-perl-binarys-segmentation-fault/#comment-7644

Note, this is not my blog but has been very helpful in providing the 2 workarounds for the issue I report here.
It would be great if a permanent fix could be found is it seems this is something specific to Virtual Box 5 rather than an issue with the guest config."	MPMDBA
18613	Oracle account got not merged with the correct VirtualBox account		2019-05-01T12:53:40Z	2020-06-22T16:52:54Z	2020-06-22T16:52:54Z	"For about several weeks I'm trying to solve an account issue via 	info_de@oracle.com and profilehelp_ww@oracle.com and the latter has now forwarded me to https://www.virtualbox.org/newticket .

The issue began after I updated my email address of my Oracle account from sworddragon2@aol.com to sworddragon2@gmail.com and tried to login into my VirtualBox account ( https://www.virtualbox.org ). I got asked to choose a username as a protection to hide the email address and tried to choose Sworddragon but since this username was already in use I choosed Sworddragon2 instead. But then I noticed something was wrong as I did for example not find any of my existing tickets. Investigating a bit into it resulted that the account Sworddragon was already my account and instead of loging into it (which did work previously) a new one got created instead.

To solve the issue the account Sworddragon needs to get merged to my Oracle account and the account Sworddragon2 needs to get deleted."	Sworddragon2
20718	Oracle Linux 8.2 Guest Mouse Pointer Integration Ubuntu 20.10 Host	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
13841	Oracle Vbox crashes on full screen	VirtualBox 4.3.22	2015-02-16T15:22:58Z	2015-06-29T05:41:28Z	2015-06-29T05:41:28Z	"While trying to view in full screen Vbox crashes with error ""the instruction at 0x000000000 referenced memory at 0x000000000. The memory could not be written."" "	ddfedora21
20854	Oracle VM not booting	VirtualBox 6.1.32	2022-02-27T05:10:53Z	2022-03-03T21:38:35Z	2022-03-03T21:38:35Z	"failed to open a session for the virtual machine result code E_Fail
VM created and attached not booting "	Venkat Rangan
15351	Oracle VM VirtualBox Manager Crashes on Shutdown	VirtualBox 5.0.18	2016-04-25T19:53:35Z	2022-04-11T10:31:23Z	2022-04-11T10:31:23Z	"I know there are quite a bit of ticket dealing with Virtualbox crashing during shutdown.  This is not a problem with a guest but with the Oracle VirtualBox Manager.  This has been present since 5.0.0 was released.  I have tested every release since 5.0.0 including 5.0.18.

Host OS:  Windows 7 64bit
Guest OS:  Windows 7 32bit

How to Reproduce

1.  Open Oracle VM VirtualBox Manager, do not start a guest.
2.  Shutdown the Windows 7 Host computer.
3.  This should generate the errors attached.
"	cmccarron
18601	Oracle_VM_VirtualBox_Extension_Pack-6.0.6.vbox-extpack error	VirtualBox 6.0.6	2019-04-26T10:28:20Z	2019-04-26T10:34:02Z	2019-04-26T10:34:02Z	"Fallo al instalar el paquete de extensión D:/Downloads/www.virtualbox.og/Oracle_VM_VirtualBox_Extension_Pack-6.0.6.vbox-extpack.

The installer failed with exit code 1: VBoxExtPackHelperApp.exe: error: Membership in the Administrators group is required to perform this action.

Código resultado: E_FAIL (0x80004005)
Componente: ExtPackManagerWrap
Interfaz: IExtPackManager {70401eef-c8e9-466b-9660-45cb3e9979e4}

"	jfuente
19345	Oracle_VM_VirtualBox_Extension_Pack-6.1.4 Signature invalid (Mac OS X 10.10.5 Yosemite)	VirtualBox 6.1.4	2020-02-24T14:22:14Z	2020-03-22T00:50:11Z	2020-03-22T00:50:11Z	"Install ran smoothly without signature errors (as appeared in VB 6.1.2).

Now the signature error comes up with the Extension Pack:

Failed to load the main module ('/Applications/VirtualBox.app/Contents/MacOS/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/darwin.amd64/VBoxPuelMain.dylib'): VERR_FILE_NOT_FOUND - dlopen(/Applications/VirtualBox.app/Contents/MacOS/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/darwin.amd64/VBoxPuelMain.dylib, 6): no suitable image found. Did find:
/Applications/VirtualBox.app/Contents/MacOS/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/darwin.amd64/VBoxPuelMain.dylib: code signature invalid for '/Applications/VirtualBox.app/Contents/MacOS/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/darwin.amd64/VBoxPuelMain.dylib'
.


Fehlercode: 
NS_ERROR_FAILURE (0x80004005)
Komponente: 
ExtPackManagerWrap
Interface: 
IExtPackManager {70401eef-c8e9-466b-9660-45cb3e9979e4}
"	cdvk
18083	Ordering of groups (inside groups) gets lost upon GUI restart	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
15187	OS X 10.10 guest on 10.11 host, gurumediation after successful installation	VirtualBox 5.0.14	2016-02-29T03:35:00Z	2016-02-29T14:11:26Z	2016-02-29T14:11:26Z	"Macbook Pro 8,2 (2011) with 8G RAM running OS X 10.11.3
VirtualBox 5.0.14, guest OS X 10.10 with VM type set to Mac OS X and version set to 10.10 Yosemite (64-bit).
Base memory has been set from 1536M to 3072M with the same results.

Boot of installation image goes OK, installer runs fine, no errors, upon reboot there's gurumediation seemingly right at bootloader to kernel handoff."	Chris Murphy
15950	OS X host UI slowdown during Linux guest usage	VirtualBox 5.1.6	2016-09-18T08:46:11Z	2016-09-18T08:49:23Z	2016-09-18T08:49:23Z	"I am using VirtualBox on my OS X laptop since VirtualBox version 4.3.

When I updated my OS X to El Capitan I had to update VirtualBox to version 5.0 too (because vbox 4.x didn't support El Capitan when I applied OS X update).

Since my update to VirtualBox 5.0 I noticed that OS X User Interface (UI) slowdown in time during active guest usage.

First few days all looks OK, but after one week of active guest usage (my guest running CentOS 6 x86_64 with X Window System + Gnome, with VirtualBox guest utils) host system UI slowdown to unacceptable level. All OS X graphical effects lagging.

If I have little usage of my Linux guest, host system may slowdown very little - 1-3 weeks host may work before visible slowdown.

If I stop guest or suspend it and start again (without OS X restart), system will go back to normal state and slowdown will begin accumulate again.

One week ago I updated to Virtual Box 5.1, apply all available updates to OS X, update VirtualBox guest utils in hope to have no slowdowns. But it still happened again.

I had installed in my My OS X host: VirtualBox, Skype, Adium and nothing else, I use Safari very active. Linux guest has installed CentOS 6 with Graphical Interface, nothing special - I am using only gnome terminal + ssh.

"	osx-user
19606	OS X Virtual machine has async io problems causing iy to fail	VirtualBox 6.1.8	2020-05-20T10:56:29Z	2021-10-22T06:38:57Z	2021-10-22T06:38:57Z	"Getting these messages during the install.  It's accessing the ISO installation CD and the VDI disk. I've tried different chip types, and had best success using the same ATA controller for both the CD image and the installation drive.  When using the SATA, it seems to fail, but I haven't looked at the logs.  I assume it's the same problem. Here's a bit of the log file from the VM.

00:52:18.532264 PIIX3 ATA LUN#2: Async I/O thread probably stuck in operation, interrupting
00:52:20.452002 PIIX3 ATA LUN#2: Async I/O thread probably stuck in operation, interrupting
00:52:22.372029 PIIX3 ATA LUN#2: Async I/O thread probably stuck in operation, interrupting
00:52:24.292006 PIIX3 ATA LUN#2: Async I/O thread probably stuck in operation, interrupting
00:52:26.212237 PIIX3 ATA LUN#2: Async I/O thread probably stuck in operation, interrupting
00:52:27.112089 PIIX3 ATA: Ctl#1: RESET, DevSel=0 AIOIf=0 CmdIf0=0xa0 (51722074 usec ago) CmdIf1=0x00 (-1 usec ago)
00:52:28.172301 PIIX3 ATA LUN#2: Async I/O thread probably stuck in operation, interrupting
00:52:30.091945 PIIX3 ATA LUN#2: Async I/O thread probably stuck in operation, interrupting
00:52:32.011961 PIIX3 ATA LUN#2: Async I/O thread probably stuck in operation, interrupting
00:52:33.528271 AsyncCompletion: Task 0x00000113628f00 completed after 141 seconds
00:52:33.528418 PIIX3 ATA: execution time for ATA command 0xca was 141 seconds
00:52:33.528437 PIIX3 ATA: Ctl#0: finished processing RESET
00:52:33.528568 AsyncCompletion: Task 0x00000113628fc0 completed after 58 seconds
00:52:33.528585 PIIX3 ATA: execution time for ATAPI command 0x28 was 58 seconds
00:52:33.528604 PIIX3 ATA: Ctl#1: finished processing RESET

The VM Manager also SEGFAULTed when I powered off the machine, and I'll attach the crash dump output as well.

This is also present in versions 5.2 and 6.0 releases as well."	unixwzrd
3972	OS/2 guest cannot write to floppy disk	VirtualBox 2.2.2	2009-05-08T23:25:39Z	2016-08-13T20:25:48Z	2016-08-13T20:25:48Z	"I am using a Vista x64 SP2 host, and OS/2 ACP2 guest.
When I mount the floppy drive in the guest, I can read files from the floppy just fine. But I can't do any writes. All writes (such as COPY, DEL, etc) result in a SYS0039 ""The A: device is not ready"".

The floppy drive works fine in the host, and I am able to do those same operations in the host OS to the same floppy disk just fine (if I unmount the floppy from the guest, of course).
"	Julien Pierre
14754	OS/2 virtual machines crashes when pressing Ctrl-Alt-NumLock or Ctrl-Alt-F10 and restarting	VirtualBox 5.0.8	2015-10-26T20:09:16Z	2015-10-26T20:09:16Z	2015-10-26T20:09:16Z	"How to reproduce:
1. Start a virtual machine with OS/2 or eComStation installed as a guest.
2. Press Ctrl-Alt-NumLock or Ctrl-Alt-F10 twice.
3. You get the screen saying ""Insert a blank formatted diskette to begin dumping memory"".
4. Restart the virtual machine without inserting a floppy.

'''Actual:''' The virtual machine crashes with Guru Meditation after the boot blob.

'''Expected:''' The virtual machine won't be crashed."	Tae
17286	OSType and longmode don't stay in sync (eg OSType Debian_64 but longmode is off)	VirtualBox 5.2.0	2017-11-18T05:51:39Z	2017-11-18T05:51:39Z	2017-11-18T05:51:39Z	"I am working with a VM that has several snapshots taken when the OSType was set to Linux 32-bit but I have since switched the OSType to Debian 64-bit. What I have noticed is if I restore a snapshot that was taken with a 32-bit OSType it will still say Debian 64-bit, and it appears it is not a per-snapshot value.

If I want to boot with 64-bit support after working in a 32-bit snapshot (ie longmode disabled) I have to switch from Debian 64-bit to Debian 32-bit, click OK, go back again switch back to Debian 64-bit and click OK. That will set longmode on. This caused me a lot of confusion because when I had checked the OS I couldn't figure out why it was crashing, since it said Debian 64-bit, then I did some diffs comparing to a new VM and realized what happens.

I think OS_Type should be a per-snapshot value. Basically you shouldn't show Debian 64-bit when 64-bit is not actually supported (ie longmode disabled). I think that is a reasonable assumption.

Version 5.2.0 r118431 (Qt5.6.2)
"	quiettime
15612	OSX dock icon set to app icon, settings ignored	VirtualBox 5.1.0	2016-07-14T09:56:10Z	2017-02-20T07:06:10Z	2017-02-20T07:06:10Z	"All VM dock icons have switched from ""Show Monitor Preview"" to ""Show Application Icon"", so all you have is a generic icon, for all VMs. Furthermore, if you switch it back to ""Show Application Icon"", although it seems that this option is selected/checked the behavior remains the same; generic icon.

I don't believe a VBox.log will shed any more light, so to conserve space, I didn't attach one. If there is a need for it, please say so.

Host: MacBookPro 17"", early 2011. OSX 10.9.5."	Socratis
16182	osx host full screen window switching display errors	VirtualBox 5.1.8	2016-11-11T21:58:16Z	2016-11-11T21:58:16Z	2016-11-11T21:58:16Z	"VBox under OSX host, switching to a running full screen (for example windows 7) guest by double clicking on a VBox guest list item, results in the listed item's icon becoming a screen graphic artifact. This can be fixed/repaired/disappear by most keyboard operations (e.g. pressing the shift key) (making screen shots difficult). 
"	littlerunningdeer
19966	OSx host, Swedish keyboard, win 10 guest wakes up with VK_LWIN depressed on resume	VirtualBox 6.1.14	2020-10-14T07:41:35Z	2020-10-14T07:41:35Z	2020-10-14T07:41:35Z	"For a while I have noticed that my Windows 10 guest wakes up after a resume with the keyboard in a weird state.

Today I installed KeyboardStateView.exe on the guest to see what the keyboard state is after a resume, and it seems that the guest wakes up with the left window key depressed. Pressing the left Command key will get it in sync again.

It behaves the same on both my MacBook Pro keyboard and an external Apple USB keyboard, both with Swedish layout.

I have suffered from this for several versions and I can't remember when I first noticed it.

After a reboot of the client the keyboard is not in this weird state, only after a suspend/resume cycle.

After some more experimenting it appears to be caused by pressing the left Command key+Q to suspend the client and quit VBox. The left Command key appears to be mapped as the left Windows key. If I instead use the right Command key+Q, which seems dead in the client, then this does not happen.

Not sure if this is a bug or not"	Tipo
20703	OVA import from Windows Explorer (file manager) does not enable Import button	VirtualBox 6.1.30	2021-12-01T18:16:27Z	2021-12-01T18:16:27Z	2021-12-01T18:16:27Z	"Cheers, got an UI bug in Windows edition with 6.1.30, I think it behaved differently with earlier releases: if I take an OVA file from Explorer and double-click it, VB UI opens and shows info from that OVA, but the Import button stays gray.

Now I have to go to file selector on the left and pick the same OVA and then I can Import it. This kinda defeats the purpose of double-clicking ;)

IIRC with earlier 6.1.x versions the import window layout looked different, but import via integration with Explorer ""just worked"".

"	Jim Klimov
19864	OVERHEATING AND HIGH RISK TO DAMAGE MACHINE - MacBook Pro 2018 CATALINA OS	VirtualBox 6.1.14	2020-09-06T12:53:48Z	2020-09-07T10:22:59Z	2020-09-07T10:22:59Z	THE VIRTUALBOX WITH CATALINA AND MACBOOK PRO 2018 CREATES OVERHEATING PROBLEMS. THE PROCESSOR COMES TO WORK AT 80 90 CELSIUS DEGREES, THE PROCESS AS YOU CAN SEE WORKS AT> 160% OF THE CPU, WE ARE NOT THERE, SOMETHING IS NOT WORKING WITH THE SOURCE FOR MACOS CHECK THANK YOU CAN DAMAGE THE MACHINE!	nickslay@…
13507	Overwrite the MAC address of other virtual miniport adapter after wake up from sleep	VirtualBox 4.3.16	2014-10-14T07:29:28Z	2014-10-14T07:29:28Z	2014-10-14T07:29:28Z	"I have installed VirtualBox and an IPsec client SW on Windows7 host system. The client uses its own virtual miniport adapter. On this adapter is enabled the ""VirtualBox Bridged Networking Driver"" service.

The MAC address of client adapter:
 
before going sleep: 02:00:00:00:01:00 
after wake up:      08:00:27:00:70:1D

VirtualBox does overwrite the MAC address of foreign adapters!"	Beat O
20631	Panic in 6.1.28 attempting to boot minix3 ISO cdrom image	VirtualBox 6.1.28	2021-10-24T15:01:59Z	2021-10-25T18:12:16Z	2021-10-25T18:12:16Z	"Downloaded minix3 cdrom image. Created empty machine in VBox, mounting .iso as IDE and set machine to boot from IDE. 

Immediate panic 

""Kernel drive no installed (rc=1908)
Make sure the kernel module has been loaded successfully
where suplibOsInit what:3
VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT""

Installed Parallels, and was immediately successful in installing and configuring Minix3. (Implying the .iso image is not defective). "	LarryJW
10996	Parallel port interrupts can not be used	VirtualBox 4.2.0	2012-09-26T06:11:10Z	2012-09-26T14:00:40Z	2012-09-26T14:00:40Z	"I have tested software that uses (and requires) a parallel port interrupt to communicate with hardware. The software is never able to detect the interrupt while running in a Windows guest. The software will run fine in a Windows host (XP or 7).

"	jmb
15870	Parallel port passthrough support - bug in I/O resource scanning	VirtualBox 5.1.4	2016-08-30T22:41:16Z	2016-08-30T22:41:16Z	2016-08-30T22:41:16Z	"English is not my mother tongue; please excuse any errors on my part.

In certain circumstances, Virtualbox is unable to detect correct base I/O address of a parallel port. This happens when the parallel port is an add-on card (PCI, PCIe, ExpressCard). The device driver consists of two parts: bus enumerator and the parallel port itself. The first device has assigned all I/O and IRQ, while the LPT port has no resources at all.

There are two functions involved:

drvHostParallelGetWinHostIoPorts(PDRVHOSTPARALLEL pThis)

and

drvHostParallelGetWinHostIoPortsSub(const DEVINST DevInst)

The second function looks for a device and enumerates its I/O resources. As the LPT port lacks of any resources, the function fails. The caller then fails silently, there is no evidence in log files that the passthrough is defunct.

I don't have VS2010 and I cannot make a build environment to test my changes to the code. If I could only create a build environment, I would attempt to make a workaround to let user specify LPT's I/O base (IRQ is not important),
or fix it to make it list bus enumerators and query them for their I/O addresses."	lelekx
13137	Parent UUID ... of the medium ... does not match UUID... of its parent medium stored in the media registry ...	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
9792	Parent VM Still reports being parent of deleted VMs	VirtualBox 4.1.4	2011-10-20T13:12:42Z	2011-10-20T13:22:50Z	2011-10-20T13:22:50Z	"In Virtualbox 4.1.4 GUI if you have a VM that is a parent of a linked clone and you delete that linked clone it will still say ""Linked Base for [VM Name]""


"	Jeremy
18783	Patch VirtualBox 6.0.10 for Linux kernel 5.3.y	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
20498	PATH_SDK_QT5_INC auto-detects to .../QtGui	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
20862	PAUSEから再開した場合、オーディオが出力されない	VirtualBox 6.1.32	2022-03-09T07:31:57Z	2022-03-09T07:32:57Z	2022-03-09T07:32:57Z	"WindowsXPでVirtualBoxをPauseにしてPauseを解除した場合、Audioが出力されません。
"	aokadak@…
15548	PC speaker passthrough uses frequency tone from previous call	VirtualBox 5.0.22	2016-06-26T17:17:24Z	2016-07-10T21:49:32Z	2016-07-10T21:49:32Z	"Background:
https://www.virtualbox.org/ticket/627
https://www.virtualbox.org/wiki/Changelog

5.0.16 : PC speaker passthrough: new experimental feature, available on Linux host only
5.0.18 : PC speaker passthrough: fixes (Linux hosts only; bug #627)

Activation of feature:
https://www.virtualbox.org/changeset/59504/vbox
(did not find a real doc; internal search engine gave me this changelog)

Host: Debian Stretch, 4.6.0-1-amd64
VirtualBox 5.0.22 r108108
guest: Debian sarge, 2.6.21-2-486 , progressively upgraded to squeeze (I have Potatoe floppies in my backyard).

Command used: beep.

Beep works perfectly in the host.

In guest, things are more complicated:
while true ; do beep -f 220 -l 500 ; sleep 1 ; beep -f 440 -l 1000 ; sleep 1 ; beep -f 880 -l 2000 ; sleep 1 ; done

*** THE BUG: Duration of beep is always correct; but frequency tone is used from the previous call.

This is improtant to me, because I perform real time reports of live events via beeps (lag, lost frames) to monitor network, and machine state. Each tone I use has a specific meaning. The configuration is now 11 years old; I can not migrate it, and put it in VB because it can avoid me to migrate it (my old kernel refused to boot on my new motherboard). Still putting prio MINOR,  cause it should not cause any arm to other people.

Please add a tick box in the AUDIO tab of the conf pannel.

I am glad we can at last have (read only for obvious reasons) access to the guest conf pannel even when it's running. I have been waiting for this for years."	DoubleHP
14485	PCI IDE controller (PIIX4) has incorrect programming interface	VirtualBox 5.0.2	2015-08-22T10:50:10Z	2015-08-27T09:36:07Z	2015-08-27T09:36:07Z	"The programming interface field of the PCI configuration space for the PCI IDE controller (PIIX4) as configured in http://www.virtualbox.org/svn/vbox/trunk/src/VBox/Devices/Storage/DevATA.cpp is incorrectly specified as 0x8a.  The PIIX4 datasheet (e.g. http://www.microbe.cz/docs/82371AB%20PCI-TO-ISA_IDE%20XCELERATOR%20(PIIX4).pdf) page 91 states it should be 0x80 instead.

The current value 0x8a is invalid because it incorrectly informs drivers that the device supports switching to PCI native mode when by writing 0x8f back to the programming interface field when it does not (specifically, the emulated device does not honour writes to pci configuration space addresses 0x8 through 0xb).

The fix is to either change the current value to 0x80 (line 7446 of DevATA.cpp) or fully implement mode switching in the driver.  The former is probably better as it better emulates the PIIX4."	jncronin
16809	PCI MMIO Address Not Listed In Memory Map	VirtualBox 5.1.22	2017-06-03T17:14:19Z	2017-06-13T08:01:10Z	2017-06-13T08:01:10Z	"When using the ICH9 chipset, the ""MCFG"" table is added to the ACPI table list, and it has an address of 0xDC000000.  However, this address is not included in the memory map returned by INT 15h AX=E820h.  This causes Linux to ignore the MMIO PCI area, altogether, and it may cause issues if the OS tries to use this area when reassigning addresses to PCI devices.

Please add the PCI MMIO area, and any other chipset specific memory areas to the memory map returned by E820.

Thanks."	SpyderTL
18204	PCI passthrough :invalid region	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
17388	PCI passthrough fails with general protection fault in VBoxPciRawR3.so	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
16385	PCI passthrought works incorrectly with I/O ports	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
16753	Pen_Tablet.exe takes more and more memory when VM is on.	VirtualBox 5.1.22	2017-05-12T17:25:50Z	2018-09-06T19:28:55Z	2018-09-06T19:28:55Z	"Tablet is Wacom CTL-470.[[BR]]
Driver version 5.3.5-3 (newest for this tablet).[[BR]]
Memory leak occurs on host while VM is running and tablet is connected. Process name is Pen_Tablet.exe (Tablet service for consumer driver). The process gains around 20K memory every second.[[BR]]
Host is running Windows 10 build 15063.250 (Creators update).[[BR]]
Guest is Arch Linux.[[BR]]

"	snow
18140	perte du clavier après installation virtualbox Version 5.2.22 r126460 (Qt5.6.2)	VirtualBox 5.2.22	2018-11-20T14:51:47Z	2018-11-30T00:18:11Z	2018-11-30T00:18:11Z	" apres l'installation de la Version 5.2.22 r126460 (Qt5.6.2) et installation des guest sur mes machines virtuelles PX ,vista, linux, j'ai ce message d'erreur au lancement

The shared folder 'paul_Virtualbox_EXEetDOC' could not be set up: Shared folder path 'C:\paul_Virtualbox_EXEetDOC' does not exist on the host.
The shared folder setup will not be complete. It is recommended to power down the virtual machine and fix the shared folder settings while the machine is not running.


ID de l'erreur : 
BrokenSharedFolder
Sévérité : 
Avertissement

Ensuite une fois la machine lancée et si je fais un document word, excel ou autre, le clavier fonctionne bien, dés que je descends pour voir quelque chose dans la barre outils, USB, fichiers partagés ou autre, je reviens dans word ou bloc note ou autre je ne peux plus rien écrire, le clavier est bloqué, je ne peux même pas faire CTRL+F pour revenir sous Windows.
merci pour votre réponse rapide car je suis bloqué.
merci.
"	pbgmoto
20426	Pestaña de Aceptar No Activada	VirtualBox 6.1.22	2021-06-18T17:45:25Z	2021-06-18T17:45:25Z	2021-06-18T17:45:25Z	"1) Cuando instalo la imagen ISO la pestaña Aceptar no se activa
2) Cuando desactivo la virtualizacion del hardware tampoco se activa la pestaña Aceptar.
3) Por lo tanto, continua el Error sin poder avanzar.
"	honorio2021
19893	Plantage de la VM : Code d’arrêt : CRITICAL STRUCTURE CORRUPTION	VirtualBox 6.1.14	2020-09-18T09:14:21Z	2020-09-18T09:18:27Z	2020-09-18T09:18:27Z	Depuis le passage en 6.1.14 sur en un hôte en Windows 10 2004 et de l'invité en Windows 10 2004, plantage régulier de l'invité avec l'erreur -> Code d’arrêt : CRITICAL STRUCTURE CORRUPTION	LFX_LFX
18138	Please add a fedora 29 repo	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
4673	please add a machine configuration option to always show the boot device menu	VirtualBox 3.0.2	2009-08-04T09:39:02Z	2009-08-04T09:39:02Z	2009-08-04T09:39:02Z	"Hi,

for a virtual machine which is primarily used for testing, it would be good to not having to press F11 at the correct time of the system boot to get to the menu where one can choose the boot device.

Please add a checkbox in Settings/System which - when checked - makes a newly booted virtual machine behave as if F11 was pressed.

Greetings
Marc
"	Marc Haber
11687	Please add support for Guests to control Host Audio Volume (+/-)	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
14438	Please add support for Windows Server 2016	VirtualBox 5.0.2	2015-08-14T10:38:59Z	2017-10-28T11:09:51Z	2017-10-28T11:09:51Z	"Currently if you name your VM Windows Server 2016 VirtualBox doesn't detect it as Windows Server and doesn't use appropriate parameters.

Windows Server 2012 is suitable as a template."	Artem S. Tashkinov
11516	Please consider adopting the phpvirtualbox project	VirtualBox 4.2.6	2013-02-23T08:16:18Z	2013-05-02T12:20:23Z	2013-05-02T12:20:23Z	"phpvirtualbox (http://code.google.com/p/phpvirtualbox/) is quite a wonderful project, rendering the managing of vbox a breeze on servers.

But his author is not able anymore to sustain it for free due to personal issues.

Please consider to take over the project, or fund the developer for its development.

Phpvirtualbox is really a great bonus for virtualbox, don't let it go!"	Alex
13233	Please enable fPIC for libraries	VirtualBox 4.3.14	2014-07-23T13:39:02Z	2014-07-23T13:48:41Z	2014-07-23T13:48:41Z	"Hi, quoting from the debian lintian error:
I don't know if some applications already directly use the libraries, but anyway would be nice to have the fPIC support, to avoid broken libraries


 E shlib-with-non-pic-code

    usr/lib/virtualbox/VBoxDD.so
    usr/lib/virtualbox/VBoxDD2.so
    usr/lib/virtualbox/VBoxDDU.so
    usr/lib/virtualbox/VBoxREM.so
    usr/lib/virtualbox/VBoxRT.so
    usr/lib/virtualbox/VBoxVMM.so
    usr/lib/virtualbox/components/VBoxC.so
    usr/lib/virtualbox/components/VBoxSVCM.so

thanks

Gianfranco"	LocutusOfBorg
15388	Please enable HTTPS for downloads	VirtualBox 5.0.20	2016-05-04T19:12:08Z	2016-05-09T13:52:19Z	2016-05-09T13:52:19Z	"I submitted this security vulnerability to secalert_us@oracle.com but they feel it is mitigated by the existing practice of securely publishing checksums, and asked me to publish the vulnerability here.

As most users will not go through the trouble of manually verifying a checksum, please enable HTTPS for downloads.

This was suggested almost two years ago in https://www.virtualbox.org/ticket/13318 but this vulnerability still exists."	jared
7143	Please expose the IgnoreFlush option to the GUI	VirtualBox 3.2.6	2010-07-08T12:53:52Z	2011-02-02T13:14:04Z	2011-02-02T13:14:04Z	"Hello, 
As I already experienced some data loss, I decided to play safe and to disable the IgnoreFlush option (default is enabled) on all of the disks of my virtual machines with important data (like my personal VCS server). 
The command line I use is:
VBoxManage setextradata ""testvm"" ""VBoxInternal/Devices/ahci/0/LUN#[0]/Config/IgnoreFlush"" 0
That is a bit inconvenient and also error prone, as the disks doesn't take it, if for example the command above -which works for AHCI devices- is given to a disk connected to a different device (VM won't start anymore).
For convenience I'd like to be able to set this in the GUI.
"	ddehnhard
20123	Please find attachment, VM not started	VirtualBox 6.1.16	2021-01-11T14:30:15Z	2021-01-11T14:30:15Z	2021-01-11T14:30:15Z		vijay.hambir
17054	Please fix virtualbox causing bsod, thx.	VirtualBox 5.1.26	2017-09-05T09:03:42Z	2017-09-10T21:36:41Z	2017-09-10T21:36:41Z	"Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 15063 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 15063.0.amd64fre.rs2_release.170317-1834
Machine Name:
Kernel base = 0xfffff801`ef20c000 PsLoadedModuleList = 0xfffff801`ef5585c0
Debug session time: Tue Sep  5 04:45:48.116 2017 (UTC - 4:00)
System Uptime: 1 days 22:23:16.527
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000096, Exception code that caused the bugcheck
Arg2: ffffaa019a9a88b3, Address of the instruction which caused the bugcheck
Arg3: ffffaa0198e3dcc0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

EXCEPTION_CODE: (NTSTATUS) 0xc0000096 - {EXCEPTION}  Privileged instruction.

FAULTING_IP: 
+254d5
ffffaa01`9a9a88b3 0f22e0          mov     cr4,rax

CONTEXT:  ffffaa0198e3dcc0 -- (.cxr 0xffffaa0198e3dcc0)
rax=0000000000000274 rbx=ffffaa019a6a7340 rcx=0000000000000000
rdx=ffffaa019a6a7340 rsi=0000000000000000 rdi=0000000000000000
rip=ffffaa019a9a88b3 rsp=ffffaa0198e3e6b8 rbp=0000000000000000
 r8=0000000000024cc0  r9=ffffaa019a6a7000 r10=fffff80097a26900
r11=ffffc3023a6701e0 r12=0000000000000206 r13=0000000000000012
r14=ffffc3022ca60870 r15=0000000000000030
iopl=0         nv up di pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00000006
ffffaa01`9a9a88b3 0f22e0          mov     cr4,rax
Resetting default scope

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x3B

PROCESS_NAME:  VirtualBox.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from ffffaa019a9a8732 to ffffaa019a9a88b3

STACK_TEXT:  
ffffaa01`98e3e6b8 ffffaa01`9a9a8732 : 00000000`00000010 fffff800`97a254d5 00007ff8`25127a78 ffff9409`701900b8 : 0xffffaa01`9a9a88b3
ffffaa01`98e3e6c0 00000000`00000010 : fffff800`97a254d5 00007ff8`25127a78 ffff9409`701900b8 ffffc302`3931ec00 : 0xffffaa01`9a9a8732
ffffaa01`98e3e6c8 fffff800`97a254d5 : 00007ff8`25127a78 ffff9409`701900b8 ffffc302`3931ec00 ffffc302`323d6cc0 : 0x10
ffffaa01`98e3e6d0 00007ff8`25127a78 : ffff9409`701900b8 ffffc302`3931ec00 ffffc302`323d6cc0 ffffaa01`98e3eb00 : VMMR0+0x254d5
ffffaa01`98e3e6d8 ffff9409`701900b8 : ffffc302`3931ec00 ffffc302`323d6cc0 ffffaa01`98e3eb00 00000000`00000000 : 0x7ff8`25127a78
ffffaa01`98e3e6e0 ffffc302`3931ec00 : ffffc302`323d6cc0 ffffaa01`98e3eb00 00000000`00000000 00000000`00000000 : 0xffff9409`701900b8
ffffaa01`98e3e6e8 ffffc302`323d6cc0 : ffffaa01`98e3eb00 00000000`00000000 00000000`00000000 ffffc302`2ee00101 : 0xffffc302`3931ec00
ffffaa01`98e3e6f0 ffffaa01`98e3eb00 : 00000000`00000000 00000000`00000000 ffffc302`2ee00101 ffffaa01`00000000 : 0xffffc302`323d6cc0
ffffaa01`98e3e6f8 00000000`00000000 : 00000000`00000000 ffffc302`2ee00101 ffffaa01`00000000 fffff800`97a983c0 : 0xffffaa01`98e3eb00


MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE

STACK_COMMAND:  .cxr 0xffffaa0198e3dcc0 ; kb

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE

BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE

Followup: memory_corruption
---------

VirtualBox Graphical User Interface
Version 5.1.26 r117224 (Qt5.6.2)

"	bugtracjer
21228	Plenty of sav files in Snapshots without any snapshot	VirtualBox-7.0.2	2022-11-01T08:18:24Z	2022-11-02T14:05:48Z	2022-11-02T14:05:48Z	"On Windows 10 host (Ubuntu guest) I have had a plenty of snapshots over period of time I have used VirtualBox 6.1 and now VirtualBox 7.0.2. I created snapshots and deleted them, then creating new ones etc. But today I have deleted all of the snapshots.

Now looking into Snapshots folder and I expect no files are in this folder anymore, but to my surprise there are plenty of files all with SAV file extension (the problem I am reporting).

Command ""dir"" output on Windows host:
19/05/2022  22:08       712.041.461 2022-05-19T21-07-57-214718900Z.sav
31/05/2022  17:56       782.450.690 2022-05-31T16-56-50-903121400Z.sav
07/06/2022  21:46       665.091.925 2022-06-07T20-46-36-299478900Z.sav
22/06/2022  21:55       702.938.444 2022-06-22T20-55-17-961063100Z.sav
14/07/2022  21:12       843.395.181 2022-07-14T20-12-47-010062000Z.sav
06/08/2022  16:09       707.927.057 2022-08-06T15-09-23-494845800Z.sav
30/08/2022  18:16       836.501.505 2022-08-30T17-16-26-777190700Z.sav
02/10/2022  17:44       717.281.998 2022-10-02T16-44-24-007573200Z.sav
07/10/2022  18:45       757.231.318 2022-10-07T17-45-24-466885500Z.sav

From file's date (May, Jun, July and August) I assume this files are from VirtualBox 6.1.x times. From file extension it looks those files are some saved snapshot's states. Why does they still exists? I assume there is/was some bug that does/did not delete saved state when snapshots gets deleted.

I shut down the virtual machine and move those files away from virtual machine Snapshot directory to some directory outside of VirtualBox and I started virtual machine and it starts up successfully and virtual machine works just normally.

I assume those files are not needed anymore, are they? Can I permanently delete them without any harm?"	bobJ
20683	PNP DETECTED FATAL ERROR	VirtualBox 6.1.28	2021-11-22T10:12:49Z	2022-01-27T12:36:08Z	2022-01-27T12:36:08Z	"In version 6.1.28 of virtualbox, when connecting any usb device, even a headset while virtualbox is active, a screenshot of Windows 10 jumps with the PNP DETECTED FATAL ERROR error.
The compilation of windows that I have installed is 19044.1348"	Vicente Irala López
17342	PokerStars freezes up in Virtualbox 5.2+ but not in 5.1.30	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
11297	poor entropy performance	VirtualBox 4.2.4	2012-12-16T17:32:08Z	2013-09-22T14:59:16Z	2013-09-22T14:59:16Z	"Many cryptographic operations depend on entropy. Having too few entropy available results in slow cryptographic operations. (https, gpg, etc.)

A simple test in Virtual Box with Debian Linux guest (rng-tools package) takes ages.

{{{
cat /dev/random | rngtest -c 100
}}}

Installing packages for entropy collection, such as haveged and/or randomsound, will astronomically speed up this test.

Since the packages depend on hardware and Virtual Box implements only virtual hardware, it's impossible to know if these packages would actually improve or worsen security (entropy quality).

There is no information about this topic available on virtualbox.org.

(Security aspects when not extra package for entropy collection is installed have their own ticket #11296.)"	Tsso
17718	Poor network latency performance / consistency	VirtualBox 5.2.10	2018-04-28T21:02:15Z	2018-04-28T21:02:15Z	2018-04-28T21:02:15Z	"For VBox.log see the attached log from #17717.

Pinging a computer in the LAN from the host I get constant <1 ms RTT.

Pinging the same computer through from the guest I get ping times that fluctuate from >1 to 10ms. Sometimes it jumps to over 70ms, and even over 160 ms.

This is with both the host and guest essentially idle. Similarly poor performance is observed with TCP and UDP."	xnoreq
20609	Poor performance on 4k display with scale factor less than 200%	VirtualBox 6.1.26	2021-10-16T10:48:12Z	2021-10-16T10:48:12Z	2021-10-16T10:48:12Z	"I'm experiencing problems with VirtualBox 6.1.26 (tried other versions as well, very end of 5 series, and end of 6.0) and 4k external display. My laptop is Lenovo P53 with i7-9850H and Nvidia T2000 graphics card. 4k display needs scaling and when it's set 200% (effective resolution Full HD) then everything is smooth. If I go lower than 200% the screen gets choppy - even when dragging the explorer window very slow refresh rate is noticeable. When I change to 100% for the scale factor everything is very smooth again. My goal is to use 150% scaling and that will give me QHD resolution - but it's impossible to use due to lag. 

I tried all possible options. Adding more CPUs or enabling 3D acceleration doesn't make any difference.  Changing the scale factor from 200% to 199% like with flick of switch affects performance. 

I can't believe that this powerful laptop can't handle a 4k display with scaling. Something is not right here. 

Host: Windows 10 
Guest: Windows 7 

"	VB_User
20978	pop critical error	VirtualBox 6.1.34	2022-06-10T15:42:38Z	2022-06-10T15:42:38Z	2022-06-10T15:42:38Z	"when I open the virtual machine it tells me ""critical error"". I tried to uninstall and install virtualbox but the same thing always happens.
I attach log"	luzzillo
8730	Portability: please allow to move VMs with Bridged NIC attached	VirtualBox 4.0.4	2011-04-16T10:37:36Z	2011-04-16T10:37:36Z	2011-04-16T10:37:36Z	"The key point of v4.0 architecture is portability. However the situation with bridged NICs disallows to port to a different host.

From original author, ""NeBlackCat"":

""When moving VMs back and forth between Windows and Linux hosts, or using a dual boot configuration, you're faced with the issue that NIC names will be different. In Windows, VirtualBox uses the immutable Windows-assigned NIC names (eg. ""Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller(NDIS6.20)"") in its .vbox files, not the user rename-able friendly names (eg. ""LAN"", or even ""eth0""), so you can't make them the same.""

original forum thread: http://forums.virtualbox.org/viewtopic.php?f=1&t=40774&p=183435#p183435

-Technologov, NeBlackCat, and others... 16.04.2011."	Technologov
19057	powercfg fail operation	VirtualBox 6.0.8	2019-11-01T11:06:03Z	2019-11-02T09:57:47Z	2019-11-02T09:57:47Z	"When i execute powercfg -h on in root.[[BR]]

C:\Windows\system32>powercfg -h on[[BR]]

La mise en veille prolongée a échoué avec l'erreur suivante : Cette demande n'es
t pas prise en charge.

Les éléments suivants empêchent la mise en veille prolongée de ce système.
        Le microprogramme du système ne prend pas en charge la mise en veille pr
olongée.
[[BR]]

I have this error because function 'hibernation' is not implemented.[[BR]]

I need it[[BR]]

For information i have virtualbox additions 6.0.8 installed[[BR]]


Thank.[[BR]]
"	Sizy458
15652	PowerDown and DisplayRefresh race condition	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
18743	Poweroff, Delete prompt NEVER REMEMBERS PREFERENCE	VirtualBox 6.0.8	2019-07-03T18:35:41Z	2019-07-05T12:36:51Z	2019-07-05T12:36:51Z	Hi, I create, shutdown, and destroy VM's a lot. So I always check the option to not prompt. But every time I click through the GUI, the confirmation prompt returns!	mcandre
13118	Presenting compatible CPU architecture to Mac OS X guest VMs	VirtualBox 4.3.12	2014-06-11T20:29:16Z	2018-02-15T07:37:06Z	2018-02-15T07:37:06Z	"Running a Mac OS X guest VM on a Mac OS X host may result in the guest VM crashing at startup, due to incompatibilities between the particular kernel etc. in the VM and the actual guest hardware. The forums contain a workaround that appears to be valid, at least in some cases:

https://forums.virtualbox.org/viewtopic.php?f=8&t=61825#p289540

Is there a way to add a configuration option to Mac OS X VMs that allows the user to specify the ""vintage"" of Apple hardware that should be presented to the guest OS? Or perhaps incorporate a known-good ""cpuidset"" value into each type of base Mac OS X VM configuration?"	jlg89
13458	Prevent VM paging on host and zero memory on power off	VirtualBox 4.3.16	2014-10-01T21:32:24Z	2014-10-01T21:32:24Z	2014-10-01T21:32:24Z	"I run some VMs that I use for anonymity. I would like to make sure that nothing from these VMs appears on disk and I don't know if VirtualBox does that or has an option for that. I asked in the [https://forums.virtualbox.org/viewtopic.php?f=1&t=63606 forum] two weeks ago but did not receive a reply.

Currently I have the VMs on a portable USB drive. In my Windows 7 host I copy them to a RAM disk that does not page out (awealloc). I cannot run them from the USB drive directly as it's too slow. I have to be sure not to hibernate or sleep during this time because that would write the physical RAM to the hard drive. When I am done I wipe the drive.

I have some requests that could make my life easier and possibly anyone else who's doing the same thing.

I would like an option to zero memory on the host that was allocated by VirtualBox for the guest, after the guest is powered off or suspended. This could be done using ZeroMemory in Windows, for example.

I would like an option to prevent VM paging. In VMWare Workstation, which I am transitioning from, there is a separate level of paging. There's the level VMWare does itself and the level done by the OS (Windows in my case). Does VirtualBox have its own paging routine? In any case an option to prevent all paging would be helpful. 

In Windows it's likely that fully preventing paging out won't be possible without administrator privileges, because the only way to make sure allocated memory absolutely stays in RAM is by passing a special flag that that can only be done by a process that has special permissions. There are very good reasons for this, as if any application could allocate all RAM etc.

Also, related to the no paging suggestion, an option to prevent host sleep/hibernate while a VM is running. Thanks
"	quiettime
7546	Print Screen does not work on Windows XP if Virtual Box has Focus	VirtualBox 3.2.8	2010-10-07T16:20:37Z	2010-10-07T16:20:37Z	2010-10-07T16:20:37Z	"1. Open up Virtual Box and Paint on Windows XP.
2. Start up a virtual machine in Virtual Box.
3. Select the title bar for the virtual machine (so that it is the active window). You should not be in the VM's content area, but the VM should be the active window.
4. Press Print-Screen.
5. Go to paint and try to paste.
6. It fails.
7. Arrange the windows so that both Virtual Box and Paint are visible.
8. Make paint the active window (by clicking on its title bar).
9. Press printscreen.
10. This time it works. It should have worked at step 6 so steps 7-10 are a workaround."	davidVisitor
17025	Problem in Virtual Box	VirtualBox 5.1.26	2017-08-20T16:46:55Z	2017-08-22T07:05:07Z	2017-08-22T07:05:07Z	"Falha ao abrir uma sessão para a máquina virtual Ubuntu.

The virtual machine 'Ubuntu' has terminated unexpectedly during startup with exit code 1 (0x1).

Código de Resultado: NS_ERROR_FAILURE (0x80004005)
Componente: MachineWrap
Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}

"	Edigilson Ferreira de Albuquerque
20620	Problem moving VM	VirtualBox 6.1.28	2021-10-19T22:29:06Z	2021-10-19T22:29:06Z	2021-10-19T22:29:06Z	"Hi, so when I try to move my Windows 10 virtual machine to my SSD, it says
Failed to move the virtual machine Win10.

Can't create a test file test.txt in the /Volumes/SSD/. Check the access rights of the destination folder..

Result Code: E_ACCESSDENIED (0x80070005)
Component: SessionMachine
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}

Is there a way to fix this? (I did some research and nobody has the same problem) I'm on the latest version on MacOS if that helps."	ethan1
20080	Problem running Ubuntu VM	VirtualBox 6.1.16	2020-12-05T00:34:02Z	2020-12-05T00:34:02Z	2020-12-05T00:34:02Z	I was trying to set up Windows Subsystem for Linux on my laptop running on Windows 10. I switched on WSL options and restarted the machine. After that I started my Ubuntu VM on VirtualBox. It causes some errors and close the VM. I, then switches off the WLS which started the Ubuntu VM but recommended turning it off. Log file is attached herewith.	mshahin
17680	Problem Starting Windows 10 VM	VirtualBox 5.2.8	2018-04-12T16:02:05Z	2018-04-20T07:11:18Z	2018-04-20T07:11:18Z	"Dear, I use windows 10 pro (64-bit) on my physical machine in version 1709 and need to install install vm with windows 10 pro (32-bit). But when you start vm you have an error. Code: ""Failed to open a session for Win10 virtual machine.

VT-x is not available (VERR_VMX_NO_VMX).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

""

I have already changed the settings several times, but all to no avail.
Any help is welcome.

I have a dropbox link where I am sharing the error screens.
https://www.dropbox.com/sh/0tlbv6jkd30s2rm/AAAwI4y48RckShxbcYhFH-NRa?dl=0

[https://www.dropbox.com/sh/0tlbv6jkd30s2rm/AAAwI4y48RckShxbcYhFH-NRa?dl=0]

Thank you!"	macklains
19710	Problem to start VM Virtual Box	VirtualBox 6.1.10	2020-07-09T09:20:34Z	2020-07-30T06:39:47Z	2020-07-30T06:39:47Z	"2230.2724: Log file opened: 6.1.10r138449 g_hStartupLog=0000000000000094 g_uNtVerCombined=0xa047bb00
2230.2724: \SystemRoot\System32\ntdll.dll:
2230.2724:     CreationTime:    2020-06-07T17:31:58.885840700Z
2230.2724:     LastWriteTime:   2020-06-07T17:31:58.949862900Z
2230.2724:     ChangeTime:      2020-06-25T08:37:39.760182000Z
2230.2724:     FileAttributes:  0x20
2230.2724:     Size:            0x1e8460
2230.2724:     NT Headers:      0xd8
2230.2724:     Timestamp:       0xb29ecf52
2230.2724:     Machine:         0x8664 - amd64
2230.2724:     Timestamp:       0xb29ecf52
2230.2724:     Image Version:   10.0
2230.2724:     SizeOfImage:     0x1f0000 (2031616)
2230.2724:     Resource Dir:    0x17f000 LB 0x6f310
2230.2724:     [Version info resource found at 0xd8! (ID/Name: 0x1; SubID/SubName: 0x409)]
2230.2724:     [Raw version resource data: 0x17f0f0 LB 0x380, codepage 0x0 (reserved 0x0)]
2230.2724:     ProductName:     Microsoft® Windows® Operating System
2230.2724:     ProductVersion:  10.0.18362.815
2230.2724:     FileVersion:     10.0.18362.815 (WinBuild.160101.0800)
2230.2724:     FileDescription: NT Layer DLL
2230.2724: \SystemRoot\System32\kernel32.dll:
2230.2724:     CreationTime:    2020-06-11T06:59:29.817582200Z
2230.2724:     LastWriteTime:   2020-06-11T06:59:29.864748100Z
2230.2724:     ChangeTime:      2020-06-25T08:37:39.609181100Z
2230.2724:     FileAttributes:  0x20
2230.2724:     Size:            0xb0498
2230.2724:     NT Headers:      0xe8
2230.2724:     Timestamp:       0xce6bbd73
2230.2724:     Machine:         0x8664 - amd64
2230.2724:     Timestamp:       0xce6bbd73
2230.2724:     Image Version:   10.0
2230.2724:     SizeOfImage:     0xb2000 (729088)
2230.2724:     Resource Dir:    0xb0000 LB 0x520
2230.2724:     [Version info resource found at 0x90! (ID/Name: 0x1; SubID/SubName: 0x409)]
2230.2724:     [Raw version resource data: 0xb00b0 LB 0x3a4, codepage 0x0 (reserved 0x0)]
2230.2724:     ProductName:     Microsoft® Windows® Operating System
2230.2724:     ProductVersion:  10.0.18362.900
2230.2724:     FileVersion:     10.0.18362.900 (WinBuild.160101.0800)
2230.2724:     FileDescription: Windows NT BASE API Client DLL
2230.2724: \SystemRoot\System32\KernelBase.dll:
2230.2724:     CreationTime:    2020-06-07T17:32:00.083192000Z
2230.2724:     LastWriteTime:   2020-06-07T17:32:00.210561000Z
2230.2724:     ChangeTime:      2020-06-25T08:37:39.765179700Z
2230.2724:     FileAttributes:  0x20
2230.2724:     Size:            0x2a4068
2230.2724:     NT Headers:      0xf8
2230.2724:     Timestamp:       0xb89efff3
2230.2724:     Machine:         0x8664 - amd64
2230.2724:     Timestamp:       0xb89efff3
2230.2724:     Image Version:   10.0
2230.2724:     SizeOfImage:     0x2a4000 (2768896)
2230.2724:     Resource Dir:    0x27e000 LB 0x548
2230.2724:     [Version info resource found at 0x90! (ID/Name: 0x1; SubID/SubName: 0x409)]
2230.2724:     [Raw version resource data: 0x27e0b0 LB 0x3bc, codepage 0x0 (reserved 0x0)]
2230.2724:     ProductName:     Microsoft® Windows® Operating System
2230.2724:     ProductVersion:  10.0.18362.815
2230.2724:     FileVersion:     10.0.18362.815 (WinBuild.160101.0800)
2230.2724:     FileDescription: Windows NT BASE API Client DLL
2230.2724: \SystemRoot\System32\apisetschema.dll:
2230.2724:     CreationTime:    2019-03-19T04:43:54.837151500Z
2230.2724:     LastWriteTime:   2019-03-19T04:43:54.837151500Z
2230.2724:     ChangeTime:      2020-06-25T08:37:39.587181200Z
2230.2724:     FileAttributes:  0x20
2230.2724:     Size:            0x1d028
2230.2724:     NT Headers:      0xc8
2230.2724:     Timestamp:       0xd6ced080
2230.2724:     Machine:         0x8664 - amd64
2230.2724:     Timestamp:       0xd6ced080
2230.2724:     Image Version:   10.0
2230.2724:     SizeOfImage:     0x1e000 (122880)
2230.2724:     Resource Dir:    0x1d000 LB 0x408
2230.2724:     [Version info resource found at 0x48! (ID/Name: 0x1; SubID/SubName: 0x409)]
2230.2724:     [Raw version resource data: 0x1d060 LB 0x3a8, codepage 0x0 (reserved 0x0)]
2230.2724:     ProductName:     Microsoft® Windows® Operating System
2230.2724:     ProductVersion:  10.0.18362.1
2230.2724:     FileVersion:     10.0.18362.1 (WinBuild.160101.0800)
2230.2724:     FileDescription: ApiSet Schema DLL
2230.2724: NtOpenDirectoryObject failed on \Driver: 0xc0000022
2230.2724: supR3HardenedWinFindAdversaries: 0x0
2230.2724: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume8\Program Files\Oracle\VirtualBox'
2230.2724: Calling main()
2230.2724: SUPR3HardenedMain: pszProgName=VirtualBoxVM fFlags=0x2
2230.2724: supR3HardenedWinInitAppBin(0x2): '\Device\HarddiskVolume8\Program Files\Oracle\VirtualBox'
2230.2724: SUPR3HardenedMain: Respawn #1
2230.2724: System32:  \Device\HarddiskVolume8\Windows\System32
2230.2724: WinSxS:    \Device\HarddiskVolume8\Windows\WinSxS
2230.2724: KnownDllPath: C:\Windows\System32
2230.2724: supR3HardenedWinInit: Performing a limited self purification...
2230.2724: supHardNtVpScanVirtualMemory: enmKind=SELF_PURIFICATION
2230.2724:  *0000000000000000-0000000000caffff 0x0001/0x0000 0x0000000
2230.2724:  *0000000000cb0000-0000000000cbffff 0x0004/0x0004 0x0040000
2230.2724:   0000000000cc0000-0000000000ccffff 0x0001/0x0000 0x0000000
2230.2724:  *0000000000cd0000-0000000000ceafff 0x0002/0x0002 0x0040000
2230.2724:   0000000000ceb000-0000000000ceffff 0x0001/0x0000 0x0000000
2230.2724:  *0000000000cf0000-0000000000da8fff 0x0000/0x0004 0x0020000
2230.2724:   0000000000da9000-0000000000dabfff 0x0104/0x0004 0x0020000
2230.2724:   0000000000dac000-0000000000deffff 0x0004/0x0004 0x0020000
2230.2724:  *0000000000df0000-0000000000df3fff 0x0002/0x0002 0x0040000
2230.2724:   0000000000df4000-0000000000dfffff 0x0001/0x0000 0x0000000
2230.2724:  *0000000000e00000-0000000000f0bfff 0x0000/0x0004 0x0020000
2230.2724:   0000000000f0c000-0000000000f0efff 0x0004/0x0004 0x0020000
2230.2724:   0000000000f0f000-0000000000ffffff 0x0000/0x0004 0x0020000
2230.2724:  *0000000001000000-0000000001001fff 0x0004/0x0004 0x0020000
2230.2724:   0000000001002000-000000000100ffff 0x0001/0x0000 0x0000000
2230.2724:  *0000000001010000-0000000001010fff 0x0004/0x0004 0x0020000
2230.2724:   0000000001011000-0000000001029fff 0x0000/0x0004 0x0020000
2230.2724:   000000000102a000-000000000102ffff 0x0001/0x0000 0x0000000
2230.2724:  *0000000001030000-0000000001031fff 0x0004/0x0004 0x0020000
2230.2724:   0000000001032000-0000000001049fff 0x0000/0x0004 0x0020000
2230.2724:   000000000104a000-00000000010affff 0x0001/0x0000 0x0000000
2230.2724:  *00000000010b0000-00000000010c0fff 0x0004/0x0004 0x0020000
2230.2724:   00000000010c1000-00000000011affff 0x0000/0x0004 0x0020000
2230.2724:  *00000000011b0000-0000000001276fff 0x0002/0x0002 0x0040000
2230.2724:   0000000001277000-000000000127ffff 0x0001/0x0000 0x0000000
2230.2724:  *0000000001280000-000000000129cfff 0x0004/0x0004 0x0020000
2230.2724:   000000000129d000-000000000137ffff 0x0000/0x0004 0x0020000
2230.2724:   0000000001380000-00000000013bffff 0x0001/0x0000 0x0000000
2230.2724:  *00000000013c0000-00000000013cefff 0x0004/0x0004 0x0020000
2230.2724:   00000000013cf000-00000000013cffff 0x0000/0x0004 0x0020000
2230.2724:  *00000000013d0000-00000000013ddfff 0x0000/0x0004 0x0020000
2230.2724:   00000000013de000-00000000015cefff 0x0004/0x0004 0x0020000
2230.2724:   00000000015cf000-00000000015cffff 0x0000/0x0004 0x0020000
2230.2724:   00000000015d0000-000000007ffdffff 0x0001/0x0000 0x0000000
2230.2724:  *000000007ffe0000-000000007ffe0fff 0x0002/0x0002 0x0020000
2230.2724:   000000007ffe1000-000000007ffecfff 0x0001/0x0000 0x0000000
2230.2724:  *000000007ffed000-000000007ffedfff 0x0002/0x0002 0x0020000
2230.2724:   000000007ffee000-00007ff4100effff 0x0001/0x0000 0x0000000
2230.2724:  *00007ff4100f0000-00007ff4100f4fff 0x0002/0x0002 0x0040000
2230.2724:   00007ff4100f5000-00007ff4101effff 0x0000/0x0002 0x0040000
2230.2724:  *00007ff4101f0000-00007ff51020ffff 0x0000/0x0004 0x0020000
2230.2724:  *00007ff510210000-00007ff51220ffff 0x0000/0x0004 0x0020000
2230.2724:   00007ff512210000-00007ff512210fff 0x0004/0x0004 0x0020000
2230.2724:   00007ff512211000-00007ff51221ffff 0x0001/0x0000 0x0000000
2230.2724:  *00007ff512220000-00007ff512220fff 0x0002/0x0002 0x0040000
2230.2724:   00007ff512221000-00007ff51222ffff 0x0001/0x0000 0x0000000
2230.2724:  *00007ff512230000-00007ff512252fff 0x0002/0x0002 0x0040000
2230.2724:   00007ff512253000-00007ff708b4ffff 0x0001/0x0000 0x0000000
2230.2724:  *00007ff708b50000-00007ff708b50fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume8\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
2230.2724:   00007ff708b51000-00007ff708bc6fff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume8\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
2230.2724:   00007ff708bc7000-00007ff708bc7fff 0x0080/0x0080 0x1000000  \Device\HarddiskVolume8\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
2230.2724:   00007ff708bc8000-00007ff708c0ffff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume8\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
2230.2724:   00007ff708c10000-00007ff708c12fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume8\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
2230.2724:   00007ff708c13000-00007ff708c15fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume8\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
2230.2724:   00007ff708c16000-00007ff708c18fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume8\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
2230.2724:   00007ff708c19000-00007ff708c19fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume8\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
2230.2724:   00007ff708c1a000-00007ff708c1bfff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume8\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
2230.2724:   00007ff708c1c000-00007ff708c1cfff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume8\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
2230.2724:   00007ff708c1d000-00007ff708c65fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume8\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
2230.2724:   00007ff708c66000-00007ff8cc4affff 0x0001/0x0000 0x0000000
2230.2724:  *00007ff8cc4b0000-00007ff8cc4b0fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume8\Windows\System32\apphelp.dll
2230.2724:   00007ff8cc4b1000-00007ff8cc4fdfff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume8\Windows\System32\apphelp.dll
2230.2724:   00007ff8cc4fe000-00007ff8cc51ffff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume8\Windows\System32\apphelp.dll
2230.2724:   00007ff8cc520000-00007ff8cc522fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume8\Windows\System32\apphelp.dll
2230.2724:   00007ff8cc523000-00007ff8cc53efff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume8\Windows\System32\apphelp.dll
2230.2724:   00007ff8cc53f000-00007ff8ce62ffff 0x0001/0x0000 0x0000000
2230.2724:  *00007ff8ce630000-00007ff8ce630fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume8\Windows\System32\KernelBase.dll
2230.2724:   00007ff8ce631000-00007ff8ce735fff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume8\Windows\System32\KernelBase.dll
2230.2724:   00007ff8ce736000-00007ff8ce898fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume8\Windows\System32\KernelBase.dll
2230.2724:   00007ff8ce899000-00007ff8ce89cfff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume8\Windows\System32\KernelBase.dll
2230.2724:   00007ff8ce89d000-00007ff8ce89dfff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume8\Windows\System32\KernelBase.dll
2230.2724:   00007ff8ce89e000-00007ff8ce8d3fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume8\Windows\System32\KernelBase.dll
2230.2724:   00007ff8ce8d4000-00007ff8cf85ffff 0x0001/0x0000 0x0000000
2230.2724:  *00007ff8cf860000-00007ff8cf860fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume8\Windows\System32\kernel32.dll
2230.2724:   00007ff8cf861000-00007ff8cf8d5fff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume8\Windows\System32\kernel32.dll
2230.2724:   00007ff8cf8d6000-00007ff8cf907fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume8\Windows\System32\kernel32.dll
2230.2724:   00007ff8cf908000-00007ff8cf908fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume8\Windows\System32\kernel32.dll
2230.2724:   00007ff8cf909000-00007ff8cf909fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume8\Windows\System32\kernel32.dll
2230.2724:   00007ff8cf90a000-00007ff8cf911fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume8\Windows\System32\kernel32.dll
2230.2724:   00007ff8cf912000-00007ff8d149ffff 0x0001/0x0000 0x0000000
2230.2724:  *00007ff8d14a0000-00007ff8d14a0fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume8\Windows\System32\ntdll.dll
2230.2724:   00007ff8d14a1000-00007ff8d15b7fff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume8\Windows\System32\ntdll.dll
2230.2724:   00007ff8d15b8000-00007ff8d15fefff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume8\Windows\System32\ntdll.dll
2230.2724:   00007ff8d15ff000-00007ff8d15fffff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume8\Windows\System32\ntdll.dll
2230.2724:   00007ff8d1600000-00007ff8d1601fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume8\Windows\System32\ntdll.dll
2230.2724:   00007ff8d1602000-00007ff8d160afff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume8\Windows\System32\ntdll.dll
2230.2724:   00007ff8d160b000-00007ff8d168ffff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume8\Windows\System32\ntdll.dll
2230.2724:   00007ff8d1690000-00007ffffffeffff 0x0001/0x0000 0x0000000
2230.2724: kernel32.dll: timestamp 0xce6bbd73 (rc=VINF_SUCCESS)
2230.2724: kernelbase.dll: timestamp 0xb89efff3 (rc=VINF_SUCCESS)
2230.2724: apphelp.dll: timestamp 0xff74693c (rc=VINF_SUCCESS)
2230.2724: VirtualBoxVM.exe: timestamp 0x5ed9201b (rc=VINF_SUCCESS)
2230.2724: '\Device\HarddiskVolume8\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe' has no imports
2230.2724: '\Device\HarddiskVolume8\Windows\System32\ntdll.dll' has no imports
2230.2724: apphelp.dll: Differences in section #2 (.rdata) between file and memory:
2230.2724:   00007ff8cc4ffe98 / 0x004fe98: a0 != e0
2230.2724:   00007ff8cc4ffe99 / 0x004fe99: e1 != ed
2230.2724:   00007ff8cc4ffe9a / 0x004fe9a: 6a != 87
2230.2724:   00007ff8cc4ffe9b / 0x004fe9b: ce != cf
2230.2724:   00007ff8cc4ffea0 / 0x004fea0: 10 != 50
2230.2724:   00007ff8cc4ffea1 / 0x004fea1: 0a != 5e
2230.2724:   00007ff8cc4ffea2 / 0x004fea2: 68 != 87
2230.2724:   00007ff8cc4ffea3 / 0x004fea3: ce != cf
2230.2724:   00007ff8cc4ffea8 / 0x004fea8: 10 != b0
2230.2724:   00007ff8cc4ffea9 / 0x004fea9: 48 != 1d
2230.2724:   00007ff8cc4ffeaa / 0x004feaa: 69 != 88
2230.2724:   00007ff8cc4ffeab / 0x004feab: ce != cf
2230.2724:   00007ff8cc4ffeb0 / 0x004feb0: 60 != 50
2230.2724:   00007ff8cc4ffeb1 / 0x004feb1: a7 != b7
2230.2724:   00007ff8cc4ffeb2 / 0x004feb2: 69 != 87
2230.2724:   00007ff8cc4ffeb3 / 0x004feb3: ce != cf
2230.2724:   00007ff8cc4ffeb8 / 0x004feb8: d0 != c0
2230.2724:   00007ff8cc4ffeb9 / 0x004feb9: 22 != 1d
2230.2724:   00007ff8cc4ffeba / 0x004feba: 69 != 88
2230.2724:   00007ff8cc4ffebb / 0x004febb: ce != cf
2230.2724:   00007ff8cc4ffec0 / 0x004fec0: a0 != 40
2230.2724:   00007ff8cc4ffec1 / 0x004fec1: bc != be
2230.2724:   00007ff8cc4ffec2 / 0x004fec2: 68 != 87
2230.2724:   00007ff8cc4ffec3 / 0x004fec3: ce != cf
2230.2724:   00007ff8cc4ffec8 / 0x004fec8: c0 != 60
2230.2724:   00007ff8cc4ffec9 / 0x004fec9: 66 != a1
2230.2724:   00007ff8cc4ffeca / 0x004feca: 69 != 87
2230.2724:   00007ff8cc4ffecb / 0x004fecb: ce != cf
2230.2724:   00007ff8cc4ffed8 / 0x004fed8: 20 != a0
2230.2724:   00007ff8cc4ffed9 / 0x004fed9: 72 != a1
2230.2724:   00007ff8cc4ffeda / 0x004feda: 65 != 87
2230.2724:   00007ff8cc4ffedb / 0x004fedb: ce != cf
2230.2724:   Restored 0x2000 bytes of original file content at 00007ff8cc4fe000
2230.2724: supR3HardenedWinInit: SUPHARDNTVPKIND_SELF_PURIFICATION_LIMITED -> VINF_SUCCESS, cFixes=1
2230.2724: '\Device\HarddiskVolume8\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe' has no imports
2230.2724: supHardenedWinVerifyImageByHandle: -> 24202 (\Device\HarddiskVolume8\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe)
2230.2724: supR3HardNtEnableThreadCreationEx:
2230.2724: supR3HardNtDisableThreadCreation: pvLdrInitThunk=00007ff8d1511770 pvNtTerminateThread=00007ff8d153cac0
2230.2724: supR3HardenedWinDoReSpawn(1): New child 12a0.18b0 [kernel32].
2230.2724: supR3HardNtChildGatherData: PebBaseAddress=00000000011f9000 cbPeb=0x388
2230.2724: supR3HardNtPuChFindNtdll: uNtDllParentAddr=00007ff8d14a0000 uNtDllChildAddr=00007ff8d14a0000
2230.2724: supR3HardenedWinSetupChildInit: uLdrInitThunk=00007ff8d1511770
2230.2724: supR3HardenedWinSetupChildInit: Initial context:
  rax=0000000000000000 rbx=0000000000000000 rcx=00007ff708b57900 rdx=00000000011f9000
  rsi=0000000000000000 rdi=0000000000000000 r8 =0000000000000000 r9 =0000000000000000
  r10=0000000000000000 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
  r14=0000000000000000 r15=0000000000000000  P1=0000000000000000  P2=0000000000000000
  rip=00007ff8d150ce30 rsp=00000000012ff8c8 rbp=0000000000000000    ctxflags=0010001b
  cs=0033 ss=002b ds=0000 es=0000 fs=0000 gs=0000    eflags=00000200   mxcrx=00001f80
   P3=0000000000000000  P4=0000000000000000  P5=0000000000000000  P6=0000000000000000
  dr0=0000000000000000 dr1=0000000000000000 dr2=0000000000000000 dr3=0000000000000000
  dr6=0000000000000000 dr7=0000000000000000 vcr=0000000000000000 dcr=0000000000000000
  lbt=0000000000000000 lbf=0000000000000000 lxt=0000000000000000 lxf=0000000000000000
2230.2724: supR3HardenedWinSetupChildInit: Start child.
2230.2724: supR3HardNtChildWaitFor: Found expected request 0 (PurifyChildAndCloseHandles) after 0 ms.
2230.2724: supR3HardNtChildPurify: Startup delay kludge #1/0: 266 ms, 17 sleeps
2230.2724: supHardNtVpScanVirtualMemory: enmKind=CHILD_PURIFICATION
2230.2724:  *0000000000000000-0000000000f9ffff 0x0001/0x0000 0x0000000
2230.2724:  *0000000000fa0000-0000000000fbffff 0x0004/0x0004 0x0020000
2230.2724:  *0000000000fc0000-0000000000fdafff 0x0002/0x0002 0x0040000
2230.2724:   0000000000fdb000-0000000000fdffff 0x0001/0x0000 0x0000000
2230.2724:  *0000000000fe0000-0000000000fe3fff 0x0002/0x0002 0x0040000
2230.2724:   0000000000fe4000-0000000000feffff 0x0001/0x0000 0x0000000
2230.2724:  *0000000000ff0000-0000000000ff1fff 0x0004/0x0004 0x0020000
2230.2724:   0000000000ff2000-0000000000ffffff 0x0001/0x0000 0x0000000
2230.2724:  *0000000001000000-00000000011f8fff 0x0000/0x0004 0x0020000
2230.2724:   00000000011f9000-00000000011fbfff 0x0004/0x0004 0x0020000
2230.2724:   00000000011fc000-00000000011fffff 0x0000/0x0004 0x0020000
2230.2724:  *0000000001200000-00000000012fafff 0x0000/0x0004 0x0020000
2230.2724:   00000000012fb000-00000000012fdfff 0x0104/0x0004 0x0020000
2230.2724:   00000000012fe000-00000000012fffff 0x0004/0x0004 0x0020000
2230.2724:   0000000001300000-000000007ffdffff 0x0001/0x0000 0x0000000
2230.2724:  *000000007ffe0000-000000007ffe0fff 0x0002/0x0002 0x0020000
2230.2724:   000000007ffe1000-000000007ffecfff 0x0001/0x0000 0x0000000
2230.2724:  *000000007ffed000-000000007ffedfff 0x0002/0x0002 0x0020000
2230.2724:   000000007ffee000-00007ff546deffff 0x0001/0x0000 0x0000000
2230.2724:  *00007ff546df0000-00007ff546df0fff 0x0002/0x0002 0x0040000
2230.2724:   00007ff546df1000-00007ff546dfffff 0x0001/0x0000 0x0000000
2230.2724:  *00007ff546e00000-00007ff546e22fff 0x0002/0x0002 0x0040000
2230.2724:   00007ff546e23000-00007ff708b4ffff 0x0001/0x0000 0x0000000
2230.2724:  *00007ff708b50000-00007ff708b50fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume8\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
2230.2724:   00007ff708b51000-00007ff708bc6fff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume8\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
2230.2724:   00007ff708bc7000-00007ff708bc7fff 0x0080/0x0080 0x1000000  \Device\HarddiskVolume8\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
2230.2724:   00007ff708bc8000-00007ff708c0ffff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume8\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
2230.2724:   00007ff708c10000-00007ff708c10fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume8\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
2230.2724:   00007ff708c11000-00007ff708c11fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume8\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
2230.2724:   00007ff708c12000-00007ff708c16fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume8\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
2230.2724:   00007ff708c17000-00007ff708c17fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume8\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
2230.2724:   00007ff708c18000-00007ff708c18fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume8\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
2230.2724:   00007ff708c19000-00007ff708c1cfff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume8\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
2230.2724:   00007ff708c1d000-00007ff708c65fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume8\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
2230.2724:   00007ff708c66000-00007ff8d149ffff 0x0001/0x0000 0x0000000
2230.2724:  *00007ff8d14a0000-00007ff8d14a0fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume8\Windows\System32\ntdll.dll
2230.2724:   00007ff8d14a1000-00007ff8d15b7fff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume8\Windows\System32\ntdll.dll
2230.2724:   00007ff8d15b8000-00007ff8d15fefff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume8\Windows\System32\ntdll.dll
2230.2724:   00007ff8d15ff000-00007ff8d160afff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume8\Windows\System32\ntdll.dll
2230.2724:   00007ff8d160b000-00007ff8d1619fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume8\Windows\System32\ntdll.dll
2230.2724:   00007ff8d161a000-00007ff8d161afff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume8\Windows\System32\ntdll.dll
2230.2724:   00007ff8d161b000-00007ff8d161dfff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume8\Windows\System32\ntdll.dll
2230.2724:   00007ff8d161e000-00007ff8d168ffff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume8\Windows\System32\ntdll.dll
2230.2724:   00007ff8d1690000-00007ffffffeffff 0x0001/0x0000 0x0000000
2230.2724: supR3HardNtChildPurify: Done after 266 ms and 0 fixes (loop #0).
12a0.18b0: Log file opened: 6.1.10r138449 g_hStartupLog=0000000000000004 g_uNtVerCombined=0xa047bb00
12a0.18b0: supR3HardenedVmProcessInit: uNtDllAddr=00007ff8d14a0000 g_uNtVerCombined=0xa047bb00 (stack ~00000000012ff358)
12a0.18b0: ntdll.dll: timestamp 0xb29ecf52 (rc=VINF_SUCCESS)
12a0.18b0: New simple heap: #1 0000000001400000 LB 0x400000 (for 2031616 allocation)
2230.2724: supR3HardNtEnableThreadCreationEx:
12a0.18b0: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume8\Program Files\Oracle\VirtualBox'
12a0.18b0: System32:  \Device\HarddiskVolume8\Windows\System32
12a0.18b0: WinSxS:    \Device\HarddiskVolume8\Windows\WinSxS
12a0.18b0: KnownDllPath: C:\Windows\System32
12a0.18b0: supR3HardenedVmProcessInit: Opening vboxdrv stub...
12a0.18b0: Error opening VBoxDrvStub:  STATUS_OBJECT_NAME_NOT_FOUND
12a0.18b0: supR3HardenedWinReadErrorInfoDevice: NtCreateFile -> 0xc0000034
12a0.18b0: Error -101 in supR3HardenedWinReSpawn! (enmWhat=3)
12a0.18b0: NtCreateFile(\Device\VBoxDrvStub) failed: 0xc0000034 STATUS_OBJECT_NAME_NOT_FOUND (0 retries)

Driver is probably stuck stopping/starting. Try 'sc.exe query vboxdrv' to get more information about its state. Rebooting may actually help.
2230.2724: supR3HardenedWinCheckChild: enmRequest=2 rc=-101 enmWhat=3 supR3HardenedWinReSpawn: NtCreateFile(\Device\VBoxDrvStub) failed: 0xc0000034 STATUS_OBJECT_NAME_NOT_FOUND (0 retries)

Driver is probably stuck stopping/starting. Try 'sc.exe query vboxdrv' to get more information about its state. Rebooting may actually help.
12a0.18b0: KiUserExceptionDispatcher: 0xc0000005 (0000000000000001, 0000000000000024) @ 00007ff8d14a72a6 (flags=0x0)
  rax=0000000000000000 rbx=00007ff8d16052c0 rcx=00007ff8d16052c0 rdx=00000000fffffffa
  rsi=0000000000000000 rdi=00007ff8d1604f00 r8 =0000000000000000 r9 =00007ff8d1605200
  r10=0000000000000000 r11=00000000012f8bf0 r12=0000000000000000 r13=00000000011fa000
  r14=0000000000000001 r15=0000000000000000  P1=00000000ffffffff  P2=0000000000002010
  rip=00007ff8d14a72a6 rsp=00000000012f8a50 rbp=00000000ffffff00    ctxflags=0010005f
  cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b    eflags=00010213   mxcrx=00001f80
   P3=0000000000000000  P4=0000000000000000  P5=0000000000000000  P6=0000000000000000
  dr0=0000000000000000 dr1=0000000000000000 dr2=0000000000000000 dr3=0000000000000000
  dr6=0000000000000000 dr7=0000000000000000 vcr=0000000000000000 dcr=0000000000000000
  lbt=0000000000000000 lbf=0000000000000000 lxt=0000000000000000 lxf=0000000000000000
2230.2724: Error -101 in supR3HardenedWinReSpawn! (enmWhat=3)
2230.2724: NtCreateFile(\Device\VBoxDrvStub) failed: 0xc0000034 STATUS_OBJECT_NAME_NOT_FOUND (0 retries)

Driver is probably stuck stopping/starting. Try 'sc.exe query vboxdrv' to get more information about its state. Rebooting may actually help.
"	narsiteo
18727	Problem when boot a VM	VirtualBox 6.0.6	2019-06-25T21:11:35Z	2019-06-26T20:44:59Z	2019-06-26T20:44:59Z	I instal a Virtual Box to another PC and copy a VMs Folder. I add the VM. When i start the VM after few minute an error occurred	Giampiero1972
16862	problem with eCS (OS/2) guest on copy	VirtualBox 4.2.36	2017-06-28T17:38:20Z	2017-06-28T21:51:05Z	2017-06-28T21:51:05Z	"I have an eCS 2.1 (OS/2) guest virtual machine that I set up on a virtualbox linux 4.3.40 r110317 host that runs as intended. I am attempting to clone this to another host running virtualbox linux 4.2.38 r110681 and encountering issues with one program. I copied the virtual machine configuration over and the guest will boot, but one program in particular generates SYS3175 and SYS3176 errors when I attempt to run it. I have confirmed via md5 that the executable file encountering the errors is unchanged and that all required dlls appear to be available to it.

I have attached displays of the two virtualbox configurations. Any suggestions how to determine the problem and correct it?

Dave"	DHDurgee
16390	Problem with graphic interface	VirtualBox 5.1.10	2017-01-16T08:38:40Z	2017-01-18T10:24:08Z	2017-01-18T10:24:08Z	"Hi,

I have since last week a problem with my VM. When I launched it, the graphic interface doesn't seems to start. A teammate helped me, we look in log files to see if we got an error message. It seems that gnome have a problem but we only got this message ""CRITICAL: We failed, but the fail whale is dead. Sorry...."". I try to pass to version 5.1.12 but I still got issues.. 
I don't know if it is a recurrent problem or if I've told you enough to see where it comes from. Tell me if you need any extra information.
Thanks."	GarennePb
17609	problem with kernel	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
16491	Problem with Open Semantic Desktop Search	VirtualBox 5.1.14	2017-02-16T20:54:04Z	2017-02-17T08:36:19Z	2017-02-17T08:36:19Z	"Für die virtuelle Maschine Open Semantic Desktop Search (de) konnte keine neue Sitzung eröffnet werden.

VT-x is disabled in the BIOS for all CPU modes (VERR_VMX_MSR_ALL_VMX_DISABLED).

Fehlercode:E_FAIL (0x80004005)
Komponente:ConsoleWrap
Interface:IConsole {872da645-4a9b-1727-bee2-5585105b9eed}"	Peter Feininger
18222	Problem with VBoxAutostart and possible workaround	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
15132	Problems getting native resolution on Windows 10	VirtualBox 5.0.14	2016-02-09T21:24:04Z	2016-02-16T19:06:25Z	2016-02-16T19:06:25Z	"This ticket concerns how to get native resolution in the Virtualbox graphical frontend when running under a Windows 10 host.

By ""native resolution"", I mean a 1-1 mapping between pixels on the display and pixels in the frontend fullscreen window.

My setup is a laptop with a 2736x1824 screen. Connected to this, I have an external monitor with a 2560x1440 resolution.

The behavior I expect from the frontend is that I always get native resolution when I select a scale factor of 100% in the View menu.

The behavior I get is somewhat complicated. It seems like there are two states: I either get native resolution on the laptop monitor or the external monitor. The switch between these two states goes through Windows display settings:

Assume that we have everything working as expected on the laptop display, with native resolution in the Virtualbox frontend.

Now we connect the external monitor and choose to use only that monitor. When we now select fullscreen in the frontend we only get some scrambled rectangles on the screen. However, if we go from a scale factor of 100% to 125%, we get a screen with proper content, but with a high resolution (higher than the display) from the point of view of the guest, scaled down to fit the display.

Going now to Windows display settings, there is a red sentence saying that we need to sign out in order for all apps to adjust to the new scaling (resolution?). Doing that and restarting the guest and the graphical frontend, we now get (for a 100% frontend scale factor) native resolution.

The same thing happens again when going back to the laptop display.

This is clearly a bug since one shouldn't have to save the machine state, sign out and in again, and restart the vm for every monitor switch. I wish there was a way for Virtualbox to ignore the Windows weirdness and simply have a hard mapping between 100% scale factor and native resolution.

I attach a log from a run where I fail to get native resolution on my laptop display (but do get it on the external monitor)."	Mikael Djurfeldt
19475	Problems in guest settings with too many CPUs present at the host.	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
19549	Problems in restoring VM window size from saved states	VirtualBox 6.1.6	2020-05-02T15:56:59Z	2020-05-02T15:56:59Z	2020-05-02T15:56:59Z	"Since upgrading to VBox 6.1.x (Win10 64)I noticed that the program frequently fails in correctly restoring the VM window size (especially if non maximized) when starting a VM from a saved state.

The VM starts normally (although with much less precision in the progress indicator, also since VBox 6.1x) but the VM window, after flashing for a moment at the saved size, shrinks to 640x480 and has to be manually resized, while obviously all the guest's desktop icons get rearranged and any open program windows gets shrunk as well.
This doesn't happen always but often (on an apparently random basis) and never happened, as far as I remember, with previous releases. I couldn't yet spot any clear and reproducible cause.

This is not a major problem, obviously.
However it actually IS some kind of malfunction.
At first I thought it could be just a momentary little regression in the new major update, but since it's still there in the latest 6.1.6 I thought I'd report it here too."	Armando
17875	problems with win10 1803 and virtualbox	VirtualBox 5.2.16	2018-07-19T15:42:57Z	2018-07-29T13:57:44Z	2018-07-29T13:57:44Z	"After upgrading to Win10 1803, I can not load the virtual operating system into VirtualBox 5.2.16
I have a message:

VT-x is not available (VERR_VMX_NO_VMX).
 
E_FAIL (0x80004005)
Компонент: 
ConsoleWrap
Интерфейс: 
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

Can you help me?
"	Userpog
20887	Problème de démarrage de la machine	VirtualBox 6.1.32	2022-03-28T08:09:37Z	2022-03-28T08:09:37Z	2022-03-28T08:09:37Z	"Lors du démarrage de la machine virtuelle  ""sous windows XP,ce message apparait :  ""ERREUR CRITIQUE""
"	tanguy
266	Process priority selectable...	VirtualBox 1.3.8	2007-04-12T12:41:20Z	2021-09-28T21:17:52Z	2021-09-28T21:17:52Z	The user should be able to set the process priority directly in the GUI :)	jens
17696	Processor ID and MotherBord ID Missing	VirtualBox 5.2.8	2018-04-19T09:18:06Z	2021-07-26T05:31:58Z	2021-07-26T05:31:58Z	"Hello,

We need some hardware information to do software licensing.
In a Windows 10 VM, Processor ID and MotherBord ID cannot be requested.

These commands return default or empty values. 
wmic PATH Win32_Processor GET ProcessorId /VALUE
wmic PATH Win32_BaseBoard GET SerialNumber /VALUE

My expectation :
- When the VM is creator, random ProcessorId and MotherBordId are attributed.
- When the VM is moves/dupplicated, ProcessorId and MotherBordId are randomly updated

Please tell me if you plan to resolve this ticket because similar tickets are quite old and were never treated."	Nicolas M
20186	Program need tools for obsfucate logs and send it to developers.	VirtualBox 6.1.18	2021-02-13T16:31:45Z	2021-02-13T16:31:45Z	2021-02-13T16:31:45Z	"Each time I send logs, I manually replace virtual machine names, file paths, user and host user names, virtual machine disk file names - anything that may contain NDA information.
  I believe that developers will receive much more reports on the work of VirtualBox if users are sure that there is nothing confidential in the transmitted logs."	Дмитро
15885	Proposed Memory for openSUSE Linux installs is too small	VirtualBox 5.0.26	2016-09-05T01:55:28Z	2016-09-05T09:24:27Z	2016-09-05T09:24:27Z	"Current openSUSE Memory requirements are 1GB of ram while Virtual box currently proposes 768mb so this number should be increased. 

As openSUSE enables its own filesystem snapshots with btrfs users may also run into issues on the 8GB default hard drive size as well."	simotek
9438	Provide a mechinism to set a guest OS's process priority to idle	VirtualBox 4.1.0	2011-08-15T14:54:43Z	2011-08-16T10:06:27Z	2011-08-16T10:06:27Z	"I work on the BOINC project (http://boinc.berkeley.edu).  We have begun working on our client-side and server-side code to integrate using VirtualBox to execute CPU bound applications within a Linux guest VM.

BOINC's overall approach to running applications is to run them as the idle process priority class of the host operating system.

Our testers have reported that they have noticed that VM's start with the normal priority class thereby the system sometimes gets a little sluggish when responding to user input.

We would like a way to start a VM guest so that it is running in the hosts idle process priority class."	Rom Walton
10343	Provide emulated hardware devices for video camera, scanners and video capture	VirtualBox 4.1.8	2012-03-17T16:47:54Z	2012-04-04T21:02:27Z	2012-04-04T21:02:27Z	"Virtualbox should add a virtual emulated device that a guest OS can use inside the VM to access video input and output devices and imaging devices such as scanners and video cameras, and capture cards, virtualbox would use the  application API of the host OSs to access the hardware through the Host OS driver, the application API for accessing the hardware drivers used by the  host OS as the backend for emulated devices provided to the guest OS. 

This is already what virtualbox does for sound cards, video cards, and network interfaces.

This in many cases is better than attempting to use the USB pass through. USB pass through does not work well when multiple OSs including many VMs need to share the device. Very rarely does pass through work right. It is just asking for trouble to occur to have many different drivers trying to directly cntrol the device. 

This is why it is best to only have one driver directly talk to the device, the Host OS driver, and then provide emulated devices inside the VMs that use the Host OS driver as a backend. The guest Os then only needs to load the driver for the device that virtualbox emulates. Virtualbox should choose to emulate a brand and model of each type of hardware that is particularly common and widely supported by many OSs.

What I suggest is have virtualbox emulate some hardware devices, like a scanner, USB web cam and a happauge video capture card. The emulation would then use the Host OSs application driver APIs as a backend and provide a virtual device in the VM for every real device accessible via the application driver APIs. Guest OSs would load the driver for the scanner, video capture card and camera device that would talk to the emulated hardware device. 

This would provide much smoother operation than  the horrid and buggy USB pass through. This is already done with video cards, network adapters and so on. "	David
21402	PXE boot gets stuck and does not hand over to next boot option	VirtualBox-7.0.4	2023-01-09T22:41:52Z	2023-01-09T22:41:52Z	2023-01-09T22:41:52Z	"On Fedora Workstation 36 with VirtualBox 6.1.40 I can set a VM boot order of:1=PXE, 2=HDD  AND  if PXE boot is done (let's assume it did not receive a reply), then the next boot option is tried, i.e. HDD boot. With all previous VirtualBox 6.x versions PXE boot ended and handed over to HDD boot. When the HDD is empty you can read after PXE boot output:
FATAL: No bootable medium found! System halted.


Installation of latest updates installed VirtualBox 7.0.4 and I noticed that the PXE boot gets stuck at its end, i.e. does not continue to HDD boot. The FATAL line does not appear. The VM is still responsive, though.
I use RPMFusion to install VirtualBox. The problem can be reproduced with packages from virtualbox.org too: 7.0.0, 7.02, 7.0.4, and test build:
https://www.virtualbox.org/download/testcase/VirtualBox-7.0.5-155126-Linux_amd64.run

Attached is the log of the VM when PXE boot is done, but does not continue to HDD.

To reproduce issue:
1. create VM
2. set boot order (System -- Motherboard -- Boot Order): 1=PXE, 2=HDD
3. start VM
4. wait for PXE boot to finish"	Sobek
20622	Python wrapper of VirtualBox API under Debian Bullseye doesn't work	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
18596	QT Recursive repaint detected -> Segmentation fault (core dumped)	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
18134	Qt5 interface does not start with hardening, with qt-xcb enabled.	VirtualBox 5.2.22	2018-11-15T15:16:16Z	2018-11-15T15:16:16Z	2018-11-15T15:16:16Z	"Hi,
trying to package VirtualBox for OpenIndiana given that stack clash mitigation in illumos broken compatibility (VirtualBox panics).

https://github.com/OpenIndiana/oi-userland/pull/4569

Non-hardened builds run as expected while hardened builds fail to bring up the Qt5 interface.

alarcher@helios:/home/alarcher$ VirtualBox 
ld.so.1: VirtualBox: fatal: libQt5XcbQpa.so.5: open failed: No such file or directory
ld.so.1: VirtualBox: fatal: relocation error: file /usr/lib/qt/5.8/plugins/amd64/platforms/libqxcb.so: symbol _ZN15QXcbIntegrationC1ERK11QStringListRiPPc: referenced symbol not found
Killed

This runs properly as root and symbols were verified to be OK.

Trussing the execution does not help due to hardening.

The only reason I could come up with is that libqtxcb.so's RUNPATH uses $ORIGIN to pick the location of libQt5XcbQpa.so.5.

Is there a hard limitation in the hardening code regarding RUNPATH or is it a bug?

Thanks

"	alarcher
14581	RAM Mapping	VirtualBox 5.0.4	2015-09-13T08:59:42Z	2015-09-13T08:59:42Z	2015-09-13T08:59:42Z	"It would be great to include RAM Mapping to disk for a VM.

So the VM would allocate RAM directly to disk (mapping) instead of using the host RAM if specified (even though it may be slow but there are SSDs). It would be funny to see VMs with 208 Gb of RAM.

**Preview of how it would look like if implemented** : [[Image(http://zupimages.net/up/15/37/9lgj.png)]]"	Ley0k
15237	random BSOD on Win7 x64	VirtualBox 5.0.16	2016-03-11T17:12:10Z	2016-03-23T03:51:32Z	2016-03-23T03:51:32Z	"Got several random BSOD on my WIN7 Dell Laptop while having Vbox running.


"	theetete
17214	Random Crash	VirtualBox 5.1.18	2017-10-26T16:34:25Z	2017-10-27T04:40:23Z	2017-10-27T04:40:23Z	Middle of Entering Data on a web form when crash occurred.	Modem56k
16107	Random Freeze of Ubuntu 16.04 guest under 16.04 Host	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
17071	Random memory reading errors on Windows XP VMs	VirtualBox 5.1.26	2017-09-10T21:40:10Z	2017-09-14T17:15:32Z	2017-09-14T17:15:32Z	"Hello.

When I set a Windows XP VM, it crashes randomly (after setup, when installing Guest additions) with the message ""The instruction at 0x0000... referenced memory at 0x00000... the memory could not be read"".

Tested with 2 different Windows XP ISOs : Same problem
Tested on another Windows computer host : Same problem
Updated the graphics card driver to the latest version : Same problem
Tested with all antivirus softwares uninstalled : Same problem

Both of the hosts OS is Windows 10 Pro v.1703 x64"	Kakoussnight
16589	Raw mode release assertion	VirtualBox 5.1.18	2017-03-21T11:05:16Z	2017-03-23T11:00:33Z	2017-03-23T11:00:33Z	"Ubuntu Linux 16.04 server as guest,
Windows 7 as host

Virtualbox version 5.1.18r114002

While updating the Linux kernel (using apt), the following error stopped the virtual machine:

{{{
The exception Breakpoint
A breakpoint has been reached.
(0x80000003) occurred in the application at location 0xe555a9ac.

Click OK to terminate the program
Click CANCEL to debug the program
}}}


[[Image(https://i.imgur.com/K0duG4a.png)]]
[[Image(https://i.imgur.com/SRYeDD0.png)]]"	Brianetta
17741	Raw-mode is unavailable courtesy of Hyper-V	VirtualBox 5.2.10	2018-05-07T16:01:44Z	2018-06-30T15:09:58Z	2018-06-30T15:09:58Z	"Hi,
I am getting the famous error when trying to boot a VM:

""Raw-mode is unavailable courtesy of Hyper-V. (VERR_SUPDRV_NO_RAW_MODE_HYPER_V_ROOT)""

Here are all the steps I have already done with no success:
1  - bcdedit /set hypervisorlaunchtype off
2 - Remove all ""hyper-v"" features through the add/remove programs GUI
3 - Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All
4 - dism.exe /Online /Disable-Feature:Microsoft-Hyper-V-All
5 - sfc /scannow
6 - A few other DISM commands to clean the file system.
7 - Un/re installed virtualox

I'm not sure what else I can try? My guess is this happened at some point after I installed RSAT package for Windows which may have also installed Hyper-V with it despite me disabling it all. I would be happy to attach logs or other items you need to help.

Thanks!"	micahagilent
17784	Raw-mode is unavailable courtesy of Hyper-V. (VERR_SUPDRV_NO_RAW_MODE_HYPER_V_ROOT).	VirtualBox 5.2.12	2018-05-23T01:42:44Z	2018-05-23T13:11:53Z	2018-05-23T13:11:53Z	"Result Code:  E_FAIL (0x80004005) Component:  ConsoleWrap Interface:  IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
"	P
20131	rcu_sched detected stalls on CPUs/tasks: linux guest and host ?ryzen issue	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
19484	Reacting to host shutdown	VirtualBox 6.1.4	2020-04-13T16:36:26Z	2020-04-13T16:39:11Z	2020-04-13T16:39:11Z	"1. run Windows 10x64 virtual machine in Windows 10x64 host
2. in host Windows session, start Notepad and type something
3. in host Windows session, initiate shutdown
4. observe the message ""these applications prevent shutdown"" - showing Notepad
5. press ""cancel"" thus terminating the shutdown of the host
6. observe what happens to the virtual machine:

- error message ""failed to pause the execution of the virtual machine""
Callee RC: 
RPC_S_SERVER_UNAVAILABLE 0x800706BA (0x800706BA)
- the console of the virtual machine remains connected and showing the desktop, but it's not working anymore

open VirtualBox Manager, and check the status of the virtual machine - it's ""aborted""

What was expected: if virtual machine was reacting to the host shutdown, it probably should have either shut down itself, or gracefully terminated; there should be no attempt to pause (which failed); the GUI probably should disappear -  rather than stayed on the screen while being non-operational.


"	vad
5598	ReactOS not listed under OS	VirtualBox 3.0.12	2009-11-30T09:57:45Z	2017-12-08T15:30:40Z	2017-12-08T15:30:40Z	"Dear VirtualBox support,
I test ReactOS with VirtualBox, it works ver well, it's even listed in the OS matrix, but it isn't available as an OS in VirtualBox itself, could you please add it?
Best regards.

Gabriel."	gabriel
19720	Rebooting causes colored stripes in the VM and a Guru meditation	VirtualBox 6.1.10	2020-07-15T02:15:48Z	2020-07-15T02:15:48Z	2020-07-15T02:15:48Z	Every time I reboot my guest it has colored stripes on the top of the VM's screen then goes into guru meditation, this happens less on BIOS VMs, mostly happens on linux but also happens on Windows (Mostly 7,8,8.1)	OakBricks
17390	"Received a ""VirtualBox Manager has stopped working"" error when I click on import appliance or ""New"""	VirtualBox 5.2.4	2017-12-22T13:30:06Z	2017-12-22T13:30:06Z	2017-12-22T13:30:06Z	"I'm receiving an error whenever I click on Import Appliance or ""New"". I downloaded the Kali Linux for windows ova file and tried to import it using VirtualBox but I received an error that says ""VirtualBox Manager has stopped working"". Not sure why this is happening, I tried uninstalling virtualbox and reinstalling a few times but it didn't help. 

"	Michaelman
18921	Received critical error on new VM	VirtualBox 6.0.12	2019-09-10T13:15:57Z	2019-09-10T13:15:57Z	2019-09-10T13:15:57Z	Log files attached	broberts160
21216	Recovery Mode is not Accessible in Newer MacOS Guests	VirtualBox-7.0.2	2022-10-29T17:34:03Z	2022-10-29T17:34:03Z	2022-10-29T17:34:03Z	"IF you install Monterey on VirtualBox, you're not able to boot into Recovery Mode via the VB BIOS (e.g. ""Boot from file"") because there's no boot.efi file shown under the GUID in the Recovery Mode partition.  This issue appears to have started with BIg Sur.  If you access the filesystem with the UEFI Shell, you'll see that there are a bunch of files names boot.efi.<some string> in that partition, but this new naming system is obviously not recognized by VirtualBox.

This problem reproduces with the latest VirtualBox, VB 7."	ThomasF
18375	Red Hat Linux 7.6 VM kernel panic running under Windows 10 host	VirtualBox 6.0.2	2019-01-28T17:28:55Z	2019-01-28T17:28:55Z	2019-01-28T17:28:55Z	"When I try running a Red Hat 7.6 VM under Windows 10 using Oracle VirtualBox 6.0.0 or 6.0.2 I get a Kernel Panic.

If the guest is configured for Enable I/O APIC unchecked and so 1 CPU I get a panic in: __native_set_fixmap
If the guest is configured for 4 CPUs I get a panic in: __lookup_address_in_pgd

I have Hyper-V disabled in Windows Features. I have Windows Hypervisor Platform enabled (as without that I get errors reported in my VirtualBox config and can't even get the VM to start).

Prior to a reboot on Jan 17th 2019 I'd not had a problem. After the reboot Windows Hypervisor Platform was disabled and that stopped the VM running at all. When I enabled that setting I got the kernel panic. I tried reinstalling the Red Hat 7.6 VM, but that also suffered from the kernel panic during the install.

Between the previous reboot and the Jan 17th reboot the only things installed on my machine were:

* Dell SupportAssistAgent 3.1.0.142
* Adobe Acrobat Reader DC (19.101.20069) 

I tried uninstalling the Dell utility. However it did not resolve the issue.


Attached is a log from a startup with 4 CPUs."	David Castell
19757	Referenced memory at 0x000000... yadayadayada	VirtualBox 6.1.10	2020-07-24T10:32:19Z	2020-07-28T12:56:06Z	2020-07-28T12:56:06Z	It seems Windows 10 2004 and VirtualBox 6.1.12 is a real messy combination with all sorts of rubbish popping out. I've had one previous calamity (#19744) which forced me to re-install both windows and virtualbox. That made my critical errors go away in the virtual machine but i now have regular ocurrences of application error referenced memory at 0x000000000000000010 and then the papaya hits the fan. As it stands now, virtualbox is useless to me and if it is so for me with fresh everything then i suspect it is even more so for paying customers which could not refresh everything.	Tiaan
17420	Regression: Cannot compile VirtualBox 5.2.4 on Ubuntu 16.04, Qt5 not found	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
17419	Regression: VirtualBox 5.1.30 can not be compiled without kernel build/source directory	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
8764	Regression: VirtualBox and VM configuration broken if VM folder exists	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
17122	Regular freezing of (windows 7) guest on macosx host (high sierra)	VirtualBox 5.1.28	2017-09-29T16:10:08Z	2017-10-13T12:03:03Z	2017-10-13T12:03:03Z	I develop in a windows 7 guest system with java and eclipse. For several weeks now the guest freezes after an arbitrary time. After minimalising and restoring the guest window it shows the state as it had when the guest freezed. The same I had with 5.1.26 too. It is similar to reported ticket 8511.	chrigel
17123	Regular freezing of (windows 7) guest on macosx host (high sierra)	VirtualBox 5.1.28	2017-09-29T16:10:09Z	2017-09-30T17:28:28Z	2017-09-30T17:28:28Z	I develop in a windows 7 guest system with java and eclipse. For several weeks now the guest freezes after an arbitrary time. After minimalising and restoring the guest window it shows the state as it had when the guest freezed. The same I had with 5.1.26 too. It is similar to reported ticket 8511.	chrigel
18655	Release of shift key not recognised in Guest when Hostkey is Shift-Ctrl	VirtualBox 6.0.8	2019-05-17T19:30:06Z	2019-05-17T19:30:06Z	2019-05-17T19:30:06Z	"When the Host Key is set to Right-Shift+Right-Ctrl, the release of the right shift key is not recognised when both shift keys are pressed and released. This leads to a behavior as if Caps Lock is active. Pressing and releasing the right shift key again ends this Caps Lock behavior.

The behavior has been observed with a Linux (Debian) Guest in an X11-Session as well as on the Linux Console. Even on the Grub Command Line this behavior occurred.

Using xev I could observe that there was no release event for the right shift key after pressing and releasing both shift keys.

Choosing a different Host Key solved the problem for me."	vbu
14157	Removing snapshot fails and leave VM in unbootable state	VirtualBox 4.3.28	2015-05-28T11:24:14Z	2015-05-28T11:24:14Z	2015-05-28T11:24:14Z	"The VM had 2 snapshots and was running. I started the removal of the
first snapshot from the GUI.  This removal aborted with an error, and the running VM was somehow stopped (or killed).
Unfortunately, I don't have the error message any longer.

The bigger problem is that the VM was not bootable any longer; I think this is the error message in VBox.log.2:
{{{
00:00:04.189066 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={8ab7c520-2442-4b66-8d74-4ff1e195d2b6} aComponent={Console} aText={The object is not ready}, preserve=false
}}}

The next attempt to start the VM resulted in an error messag that a required snapshot file was missing (in VBox.1.log):
{{{
00:00:02.948345 AIOMgr: Endpoint for file 'C:\Users\voelkerb\VirtualBox VMs\opensuse13.2\os13.2.vdi' (flags 000c0781) created successfully
00:00:02.983231 VMSetError: F:\tinderbox\win-4.3\src\VBox\Storage\VD.cpp(6370) int __cdecl VDOpen(struct VBOXHDD *,const char *,const char *,unsigned int,struct VDINTERFACE *); rc=VERR_FILE_NOT_FOUND
}}}

Creating a new snapshot in order to preserve the current state failed
with the same message.

The only way out was to revert to the last snapshot - without taking
a snapshot of the current state and thus loosing the work until that
last snapshot. ;-(

After that, the machine was still not bootable, but the media manager
complained about 2 missing differencing images.
After removing that, the VM could be started again, yet some work was
lost.

I experienced the same already 2-3 times in the past.

Host: Windows 7, guest: openSUSE-13.2"	berny
17338	Rename repository name in virtualbox.repo (for Fedora distro)	VirtualBox 5.2.0	2017-12-01T19:34:59Z	2017-12-01T19:34:59Z	2017-12-01T19:34:59Z	"Repo file provided for Fedora (see link below) defines the repo's name as:


{{{
name=Fedora $releasever - $basearch - VirtualBox
}}}


Example: ''Fedora 26 - x86_64 - VirtualBox''

From a user perspective, in my personal opinion, it would make more sense to print something like

''VirtualBox - Fedora 26 - x86_64''


{{{
name=VirtualBox - Fedora $releasever - $basearch
}}}

This order would be more consistent with other repositories provided for Fedora, first naming the repository, followed by some info about release version and architecture.


Link: http://download.virtualbox.org/virtualbox/rpm/fedora/virtualbox.repo
"	F
12312	Rendering in Civilization IV is broken on Windows 8 guests	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
19901	Reopen #6650 closed on 08/14/2016	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
16331	Repairing Windows' VirtualBox v5.1.12 r112440 (Qt5.6.2) reverts back to default path.	VirtualBox 5.1.12	2016-12-27T19:17:33Z	2016-12-27T19:17:33Z	2016-12-27T19:17:33Z	"Repairing virtualbox failed since it used its default ""C:\Program Files\Oracle\VirtualBox\"" path instead of my custom ""C:\winstuff\VirtualBox\VirtualBox.exe"" location. It should reuse the custom path I had. I had to uninstall and reinstall it to fix it. Originally, I installed in my couple months old 64-bit W7 HPE SP1 machine."	Ant
18097	Repeatable Kernel Panic OSX Host 10.13.6, 5.2.18/5.2.20	VirtualBox 5.2.18	2018-11-02T15:13:04Z	2018-11-02T15:20:03Z	2018-11-02T15:20:03Z	"Hi there. I've been contributing to a forum topic about this here: https://forums.virtualbox.org/viewtopic.php?f=8&t=89890&sid=71ba74a8550785a1228b2d0ccdcefa74&p=432426#p432426

I have a Mac Mini (10.13.6, 16GB RAM) which is having regular kernel panics while running three Ubuntu VMs, particularly when under load. The three instances are Ubuntu 16.04 and serve as a three-node Graylog cluster (one master, two additional nodes). Perhaps complicating matters is that the .vdi's being written to are not on the local disk; rather they are saved to a Pegasus R2 RAID-5 array connected over (Apple standard) Thunderbolt cable. This allows them to be 2TB each with battery-backed writes, or believe me I'd be keeping them on the boot disk.

I've tried, to no avail:
* Moving to 5.2.20
* Wild ass guess that the repeated appearance of com.apple.msdosfs as a last-loaded/uloaded kernel extension was somehow the problem, boot into recovery to disable SIP and move aside that kext (when this didn't work, put it back in place again). 
* Altering the paravirtualization settings on the Ubuntu guests (Default, None, KVM) - currently sitting at the recommended KVM option
* Finally, added the ""keepsyms=1"" nvram parameter to at least get the backtrace symbolicated.

I'd be *beyond* happy to take any wild suggestions for additional logging to help diagnose this in any way. The full panic is attached, but this is the top relevant section I believe: 

{{{
Anonymous UUID:       8C247A86-017F-C949-405A-1CFF90AF12B3

Thu Nov  1 15:15:43 2018

*** Panic Report ***
panic(cpu 0 caller 0xffffff8006f8776f): Kernel trap at 0xffffff80072d36b0, type 14=page fault, registers:
CR0: 0x0000000080010033, CR2: 0x0000000100000008, CR3: 0x00000003a8a860ea, CR4: 0x00000000001627e0
RAX: 0xffffff8025937610, RBX: 0x0000000100000000, RCX: 0x0000000009000000, RDX: 0xffffff80076a5128
RSP: 0xffffff91f69dbea0, RBP: 0xffffff91f69dbef0, RSI: 0x0000000000000002, RDI: 0x0000000000000000
R8:  0x0000000000000000, R9:  0x0000000000000400, R10: 0x0000000000000061, R11: 0xffffff91f6b07770
R12: 0xffffff91f69dbea0, R13: 0x0000000000000000, R14: 0xffffff802b6025f0, R15: 0xffffff800782b8d0
RFL: 0x0000000000010206, RIP: 0xffffff80072d36b0, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x0000000100000008, Error code: 0x0000000000000000, Fault CPU: 0x0, PL: 0, VF: 1

Backtrace (CPU 0), Frame : Return Address
0xffffff91f69db970 : 0xffffff8006e6c1c6 mach_kernel : _handle_debugger_trap + 0x4c6
0xffffff91f69db9c0 : 0xffffff8006f95274 mach_kernel : _kdp_i386_trap + 0x114
0xffffff91f69dba00 : 0xffffff8006f87544 mach_kernel : _kernel_trap + 0x4e4
0xffffff91f69dba70 : 0xffffff8006e1e1e0 mach_kernel : _return_from_trap + 0xe0
0xffffff91f69dba90 : 0xffffff8006e6bc3c mach_kernel : _panic_trap_to_debugger + 0x21c
0xffffff91f69dbbc0 : 0xffffff8006e6b9fc mach_kernel : _panic + 0x5c
0xffffff91f69dbc20 : 0xffffff8006f8776f mach_kernel : _kernel_trap + 0x70f
0xffffff91f69dbd90 : 0xffffff8006e1e1e0 mach_kernel : _return_from_trap + 0xe0
0xffffff91f69dbdb0 : 0xffffff80072d36b0 mach_kernel : _audit_mac_free + 0xa0
0xffffff91f69dbef0 : 0xffffff80072c5a65 mach_kernel : _audit_free + 0x115
0xffffff91f69dbf10 : 0xffffff80072c6676 mach_kernel : _audit_syscall_exit + 0x46
0xffffff91f69dbf40 : 0xffffff8007403987 mach_kernel : _unix_syscall64 + 0x287
0xffffff91f69dbfa0 : 0xffffff8006e1e9c6 mach_kernel : _hndl_unix_scall64 + 0x16

BSD process name corresponding to current thread: VBoxHeadless
Boot args: -v keepsyms=1

Mac OS version:
17G65

Kernel version:
Darwin Kernel Version 17.7.0: Thu Jun 21 22:53:14 PDT 2018; root:xnu-4570.71.2~1/RELEASE_X86_64
Kernel UUID: 1AE5ACFD-3B6F-3D74-AD52-31F1430DBC6F
Kernel slide:     0x0000000006c00000
Kernel text base: 0xffffff8006e00000
__HIB  text base: 0xffffff8006d00000
System model name: Macmini7,1 (Mac-35C5E08120C7EEAF)

System uptime in nanoseconds: 2300159388101
last loaded kext at 246145680169: com.apple.filesystems.msdosfs	1.10 (addr 0xffffff7f8a1c3000, size 69632)
last unloaded kext at 306907560558: com.apple.filesystems.msdosfs	1.10 (addr 0xffffff7f8a1c3000, size 69632)
loaded kexts:
org.virtualbox.kext.VBoxNetAdp	5.2.18
org.virtualbox.kext.VBoxNetFlt	5.2.18
org.virtualbox.kext.VBoxUSB	5.2.18
org.virtualbox.kext.VBoxDrv	5.2.18
com.promise.driver.stex	6.2.9
com.apple.iokit.SCSITaskUserClient	404.30.2
<SNIP>
}}}

Best regards, and much respect: VirtualBox is a wonderful technology.
./scc"	Scott Corscadden
15843	"Repeated crashes with ""The memory could not be read"""	VirtualBox 5.1.4	2016-08-22T09:34:26Z	2016-08-25T20:08:49Z	2016-08-25T20:08:49Z	"Virtual Box used to work fine but since I upgraded to 5.1.0 I'm experiencing crashes of the guest system several times a day and I can't see a pattern.
Every time a new version got released I immediately upgraded my system but the crashes still occur."	schnesim
19712	Repeatedly adding file extensions in disk creation	VirtualBox 6.1.10	2020-07-09T21:31:27Z	2020-07-09T21:31:27Z	2020-07-09T21:31:27Z	"In the ""Create Virtual Hard Disk"" dialog during the creation of a new virtual machine in expert mode, selecting any of the hard disk file type options adds an extra extension to the name of the file. For example, if ""VDI (Virtual Disk Image)"" is selected and the file location displays ""C:/Users/user/VirtualBox VMs/os/disk.vdi"", and the user then selects ""VHD (Virtual Hard Disk)"" then the file location is changed to ""C:/Users/user/VirtualBox VMs/os/disk.vdi.vhd"" instead of ""C:/Users/user/VirtualBox VMs/os/disk.vhd"". Repeated switching back and forth between the two will yield ""C:/Users/user/VirtualBox VMs/os/disk.vdi.vhd.vdi.vhd.vdi.vhd"". Note that the bug also occurs while switching between the other options.

This error occurs during hard disk creation during the creation of a new VM, or by creating a new hard disk in the settings dialogue of an existing VM. This only occurs in expert mode in both cases.

Steps to reproduce:
1. Open VirtualBox click the ""New"" button to create a new VM.
2. Ensure that Expert Mode is selected.
3. Select ""Create a virtual hard disk now""
4. Name the VM.
5. Select any operating system type and version, the bug occurs for any of them.
6. Click create.
7. Select a hard disk file type other than the one currently selected e.g. ""HDD (Parallels Hard Disk)""
8. Observe that an additional file extension was added to the ""File Location"" text field.

This bug initially occurred hosted on Windows 10 Version 2004 using a fresh installation of VirtualBox 6.1.10. I was also able to reproduce the error on Xubuntu 18.04 with VirtualBox 6.1.10 following the exact same steps."	tarix29
19726	Reported memory usage doubled in 6.1.4 on MacOS Mojave and later	VirtualBox 6.1.10	2020-07-16T02:32:29Z	2022-10-26T07:51:41Z	2022-10-26T07:51:41Z	"Hi there,

we recently noticed that memory usage doubled on Catalina (confirmed on 10.15.5). Upon investigating the problem we figured out that this issue began with 6.1.4. The problem is still present in 6.1.10.

Up until 6.1.2 memory and real memory were basically the same. Allocating 4GB in the VM resulted in a memory usage of 4GB.

From 6.1.4 onwards, memory is always twice as large as real memory:

- allocating 4GB results in 8GB being used
- allocating 8GB results in 16GB being used
and so on (see attached images)

Reverting back to 6.1.2 fixes the problem. We couldn't find a bug report about it, but we did find a few reports on the forums:

- https://forums.virtualbox.org/viewtopic.php?f=8&t=97149
- https://forums.virtualbox.org/viewtopic.php?f=8&t=97181

It's possible this bug might specific to Catalina, as I personally only noticed running out on memory after upgrading from Mojave. I '''think''' I was already on 6.1.4, but I don't have a Mojave machine so I can't test this theory.

Everyone in our development team had to install 6.1.2 because we generally allocate 8GB to the virtual machine, which ended up using 16GB. As most of us have 16GB of ram, this made our machines unusable.

Please let me know if you need further information

"	arthens
19167	Repository metadata broken for Fedora	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
20159	Reproducible fatal crash of a Linux Mint 20 XFCE VM (VirtBox running on Win10)	VirtualBox 6.1.18	2021-01-29T10:47:30Z	2021-01-29T10:47:30Z	2021-01-29T10:47:30Z	"I have configured several virtual machines running the latest Linux Mint 20 XFCE4 edition. The display configuration is VMSVGA + 3D acceleration. After installing g++, make, and 6.1.8 guest additions I rebooted them. Then I installed the Atom editor. On every machine the same error occurred reproducibly: When I tore off a tab to attach it to another pane the vm crashed with an error message: 

The instruction at 0x00007FFE673EE652 referenced memory at 0x0000000000000000. 
The memory could not be written. 
Click OK to terminate the program. 

The error seems not to occur when I use another virtual graphics card, but due to the performance lack this is not solution to the problem. 

As I said: I have set up several machines from scratch, the error occurs everytime, absolutely reproducible within Atom. "	Dude McGee
20824	Reproducible split lock / freeze	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
18477	Request for VBox to pass through Speculative Store Bypass (SSB) mitigations to guest => duplicate of #17987	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
14220	Resized differential drives causes guest crash	VirtualBox 4.3.28	2015-06-24T19:16:54Z	2015-06-24T19:16:54Z	2015-06-24T19:16:54Z	"I wanted to resize (expand) guest hard drive. So:
1. I made snapshot of guest 
2. resize snapshot vdi file with {{{VBoxManage modifyhd ~/vb/vm/work/deuter/Snapshots/\{5c558b0f-1ea6-4c48-92e0-9095747529b1\}.vdi --resize 20000}}}
3. tried to resize windows partition on disk. 
And guest start to behave undeterministic. 
- with gparted ran in guest I saw a lot disk error messages
- windows guest (which normally works in this machine) aborts in random moments

Seems that ""use host IO cache"" has some impact on this (witch cache on, machine aborts earlier)"	Kamil Jońca
10153	Resizing from the left and top borders is erratic	VirtualBox 4.1.8	2012-01-10T02:34:34Z	2016-01-21T07:16:15Z	2016-01-21T07:16:15Z	When a VM window is resized from the left or top border, the behavior is very erratic. The left and top edges do not stay under the mouse, rather, they jump around, sometimes ending up well away from where the mouse is. Resizing from the right or bottom edges is fine. Refer to the demonstration video at [http://youtu.be/92kP45LPe_E].	Fls'Zen
18466	Resizing VDI with VBoxManage, shows incorrect value in the Details pane and/or MediaManager	VirtualBox 5.2.0	2019-03-01T22:35:33Z	2019-03-02T03:55:23Z	2019-03-02T03:55:23Z	"'''__Summary__'''\\
Resizing a dynamic VDI (no snapshots) from the CLI, does not reflect the new size in the Details pane and/or the MediaManager.

'''__Setup__'''
* __Host__: OSX 10.9.5, 10.11.6, 10.13.6
* __!VirtualBox__: 5.2.0, 5.2.27, 6.0.5 and 6.0.97, didn't try even earlier, they're EOLed.
* __Guest__: a Win7-32 and a FreeDOS VM, doesn't really matter.
* __VDI size__: 80 GB and 500 MB respectively.
Example with the Win7 / 80 GB VDI:
{{{
$ VBoxManage showmediuminfo /Users/Shared/VirtualBox/Machines/Win/Win.vdi 
UUID:           6b59350c-5ca0-4265-9920-0805864801dd
Parent UUID:    base
State:          created
Type:           normal (base)
Location:       /Users/Shared/VirtualBox/Machines/Win/Win.vdi
Storage format: VDI
Format variant: dynamic default
Capacity:       81920 MBytes
Size on disk:   14473 MBytes
Encryption:     disabled
In use by VMs:  Win (UUID: 54c42cec-1890-4ec1-ae7a-aacb7677e6db)

$ VBoxManage modifymedium /Users/Shared/VirtualBox/Machines/Win/Win.vdi --resize 102400
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%

$ VBoxManage showmediuminfo /Users/Shared/VirtualBox/Machines/Win/Win.vdi 
...
Capacity:       102400 MBytes     <-- That's correct!
...
}}}
The problem is that in the Details of the !VirtualBox Manager the newly 100 GB ($NEW_SIZE) is '''__not__''' reflected. It still shows the VDI as being 80 GB ($OLD_SIZE).

Using the latest test/development builds at the writing of the ticket, 2019-03-01:
* '''5.2.0 !r118431, 5.2.27 !r129042''' \\
 Not even the MediaManager shows the correct size, it shows 80 GB. Only a ''__complete restart__'' of !VirtualBox correctly identifies the VDI as being 100 GB on both the Details pane and the MediaManager.


* '''6.0.5 !r129045, 6.0.97 !r129043'''\\
 Just opening MediaManager ""forces"" the Details pane to be updated to 100 GB, otherwise it's still identified as 80 GB in the Details."	Socratis
15777	Resolution issues across 2 versions and the test build	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
20063	Resources misuse on Ubuntu 20.04LTS host with a Windows 10 guest	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
20720	Restart with snapshot	VirtualBox 6.1.28	2021-12-10T07:56:30Z	2021-12-10T22:13:28Z	2021-12-10T22:13:28Z	"Hi,

A nice feature should whem closing a VM a dialog popup ups wich the three options:
  - Save the machine state
  - Send the shutdown signal
  - Power Off the machine
       + Restore current snapshot xyz
A fourth option should be nice to have.
  - Restart the machine with the current snapshot xyz. 

The machine should then be powered off, snapshot restored and restarted.

Regards,
Luc"	viglu
18399	restore an acronis (.tib )backup of solaris10 OS into VM	VirtualBox 6.0.4	2019-01-31T06:34:04Z	2019-02-10T08:23:57Z	2019-02-10T08:23:57Z	"hello
i got a backup of my solaris10 OS with acronis 2018 and restored in VirtualBox.
the system comes up and restart periodictly !
please help"	bakia
21491	Restore current snapshot checkbox missing when closing down the VM	VirtualBox-7.0.6	2023-02-10T23:05:13Z	2023-02-10T23:05:13Z	2023-02-10T23:05:13Z	This was really useful, I used it almost every time I shut down the VM, total pain having to do it, then restore the last snapshot, then say I don't want to create a new snapshot... please add it back, guard it with an option that you have to turn on to enable it if you must but PLEASE put it back	vbuora1
15230	Restore VM: VERR_TOO_MUCH_DATA	VirtualBox 5.0.16	2016-03-10T06:46:32Z	2016-03-10T06:46:32Z	2016-03-10T06:46:32Z	"Can not restore Virtual Machine: Always getting this error:

Failed to load unit 'vga' (VERR_TOO_MUCH_DATA).


Fehlercode:
NS_ERROR_FAILURE (0x80004005)
Komponente:
ConsoleWrap
Interface:
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
"	fr
15929	"Restored VM stays ""darkened"" if switching workspaces while restoring"	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
21119	Restoring a saved Guest does not restore the saved display size	VirtualBox 6.1.38	2022-10-08T15:07:17Z	2022-10-08T15:07:17Z	2022-10-08T15:07:17Z	"To produce the error. Start a Windows 10 Guest and when idle save the guest, noting the screen display size. Restart the guest VM and note the screen size after allowing time for guest to become idle. Note the screen size is NOT the same as the saved guest VM was.
This happens whether the guest VM is Windows 10 or Windows 11.
In some cases, the correct screen display size is created at the beginning of the restore but is changed to 640x480 when the restore is completed."	MacNala2
14152	restoring my snapshot made web pages cannot connect to mysql	VirtualBox 4.3.28	2015-05-25T20:24:18Z	2015-05-26T12:52:01Z	2015-05-26T12:52:01Z	"Restoring snapshot made my webpages connection to Ubuntu guest cannot connect to Ubuntu guest mysql anymore

"	virtualguys
17825	Restoring VM goes from running to Guru Mediation state	VirtualBox 5.1.30	2018-06-16T03:05:14Z	2018-06-16T14:06:50Z	2018-06-16T14:06:50Z	"I have created saved state and restoring it. It works fine on Windows 10 Host OS where as in Windows 8.1 Host it gives below error [[BR]]
''aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={02326f63-bcb3-4481-96e0-30d1c2ee97f6} '''aComponent={DisplayWrap} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}''', preserve=false''

before this line log shows that guest is getting some fatal condition [[BR]]
''00:00:37.170678 GIM: HyperV: Guest indicates a fatal condition! P0=0x7e P1=0xffffffffc000001d P2=0xfffff803462b21ec P3=0xffff9e0187736768 P4=0xffff9e0187735f90
''[[BR]]

System configuration is:[[BR]]

Guest OS: Windows 10 64 bit[[BR]]

Host OS: Windows 8 64 bit[[BR]]


I have attached log for more information. Not sure what is the reason of failure."	Jeet15
19668	Result Code: E_INVALIDARG (0x80070507)	VirtualBox 6.1.10	2020-06-16T01:04:22Z	2020-06-16T01:04:22Z	2020-06-16T01:04:22Z	"Hi,

im having trouble installing the pyimagesearch ova file. i have installed and reinstalled VM box a few times now and have used different unzip programmes ( currently recommended to use 7 zip). i get the same message which i understand could be to do with disk spare capacity. i made space and reinstalled with the same output. it took maybe 45 seconds to come up with the error code. I moved the installation to my D drive and now the error message comes up instantaneously. Same error. Copy of settings in the attached file,

Any ideas?

Matt"	Matt Lumb
17252	Resume fails with 0x80004005, sometimes after an hour	VirtualBox 5.2.0	2017-11-07T14:03:53Z	2017-12-12T07:24:52Z	2017-12-12T07:24:52Z	"I'm having, and I always had as far as I can remember, issues resuming virtual machines. Sometimes it works, but usually fails with 0x80004005 and I have to discard the state. This happened with mixed host machines and host os. In this moment I'm on a linux host with an xp guest.

I noticed a difference in the detected gl library version between the vbox log files when the machine fails resuming and when it starts correctly:

This is a normal startup:
{{{
00:00:00.714721 Console: Machine state changed to 'Running'
...
00:00:19.772224 gl version string: 03.0 Mesa 17.0.7
00:00:19.772243 gl version: 0x30000
00:00:19.772246 gl extensions: GL_ARB_multisample GL_EXT_abgr GL_EXT_bgra GL_EXT_blend_color [...]
}}}

This is a failed resume (immediate crash):
{{{
00:00:05.617476 Console: Machine state changed to 'Running'
00:00:05.618122 gl version string: 04.5 (Core Profile) Mesa 17.0.7
00:00:05.618129 gl version: 0x40500
00:00:05.618133 gl extensions: <NULL>
<<crash>>
}}}

This is a ""working"" resume where there is no reference to gl version in the logs up to 52 minutes after the resume, and then immediately we have a crash:
{{{
00:00:02.483845 Console: Machine state changed to 'Running'
00:00:02.503065 GUI: UIMachineView::storeGuestSizeHint: Storing guest-screen size-hint for screen 0 as 1920x1107
00:00:02.510500 OpenGL: Set 3D content scale factor to (10000, 10000), multiplier 10000 (rc=VINF_SUCCESS)
00:00:02.510527 OpenGL: Set OpenGL scale policy on HiDPI displays (fUnscaledHiDPI=0)
00:00:02.510986 OpenGL: Set 3D content scale factor to (10000, 10000), multiplier 10000 (rc=VINF_SUCCESS)
00:00:02.511007 OpenGL: Set OpenGL scale policy on HiDPI displays (fUnscaledHiDPI=0)
00:00:02.579089 GUI: UIMachineViewNormal::adjustGuestScreenSize: Adjust guest-screen size if necessary.
00:00:02.579105 GUI: UIMachineViewNormal::adjustGuestScreenSize: Adjust guest-screen size if necessary.
00:00:02.579686 GUI: 2D video acceleration is enabled
00:00:02.579695 GUI: HID LEDs sync is not supported on this platform
00:00:02.583994 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=0, Machine-state=5
<<After 52 minutes of normal work>>
00:52:02.223175 gl version string: 04.5 (Core Profile) Mesa 17.0.7
00:52:02.223247 gl version: 0x40500
00:52:02.223267 gl extensions: <NULL>
<<crash>>
From dmesg:
[ 3335.532765] VirtualBox[2688]: segfault at 0 ip 00007f5db4a390bd sp 00007ffc7916fd78 error 4 in libc-2.23.so[7f5db498f000+1c0000]
}}}

glxinfo says:

{{{
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel Open Source Technology Center (0x8086)
    Device: Mesa DRI Intel(R) Kabylake GT3  (0x5926)
    Version: 17.0.7
    Accelerated: yes
    Video memory: 3072MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 4.5
    Max compat profile version: 3.0
}}}

So when it detects 04.5 core profile it crashes, when it detects 03.0 compatibility profile it works. I now disabled 3D accel but I used to have it disabled so I'm not sure this will change anything.
"	ctrl
21082	RETBleed: WARNING: Spectre v2 mitigation leaves CPU vulnerable to RETBleed attacks, data leaks possible!	VirtualBox 6.1.36	2022-08-28T20:20:24Z	2022-11-27T18:44:59Z	2022-11-27T18:44:59Z	"On VirtualBox 6.1.36, Debian, Windows builds, upon starting both exiting Debian and Ubuntu virtual machines, the warning  '''RETBleed: WARNING: Spectre v2 mitigation leaves CPU vulnerable to RETBleed attacks, data leaks possible! ''' comes up on boot after grub2.  Porting Debian virtual machine to VMWare Workstation Pro 15.5.7, Windows 11 build base contains no such boot errors.  Creation of new Ubuntu virtual machine from latest iso , virtualbox 6.1.36 gives same warning  RETBleed: WARNING: Spectre v2 mitigation leaves CPU vulnerable to RETBleed attacks, data leaks possible! Creation of a new Ubuntu virtual machine in VMware gives no such warning.

PHY HW is Intel i5 (i5-8250u) and cpuinfo shows no cpu_insecure flag.

Did not test a Windows virtual machine in virtualbox to see if warning occurred.  

Suspect virtualbox code base is not patched against Spectre v2 or warning message not correct in conditional tree.  

Others reporting similar, see https://ubuntuforums.org/showthread.php?t=2477938"	stdperson
18934	RFE: smart card sharing aka Shared mode	VirtualBox 6.0.12	2019-09-17T09:08:42Z	2019-09-17T09:08:42Z	2019-09-17T09:08:42Z	"Being used to sharing smart cards between virtual guests in vmWare it seems to be one of the few things that VirtualBox is lacking.


https://pubs.vmware.com/workstation-11/index.jsp?topic=%2Fcom.vmware.ws.using.doc%2FGUID-6F6D2C78-F28C-4553-8E46-F337599174DB.html

 I found this https://pcsclite.apdu.fr/api/group__API.html they seem to be using the functionality of pcscd to achieve it as the daemon has to be stopped to enable passthrough instead of shared mode https://communities.vmware.com/thread/498792"	variona
21319	Ring Zero Assertion Error on virtual machine after upgrade to 7.0.x	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
13698	Rotating the host window	VirtualBox 4.3.20	2014-12-18T09:49:43Z	2015-02-05T09:02:54Z	2015-02-05T09:02:54Z	"It would be great if VirtualBox can rotate the host window.
This is needed because of Android guests.
The guest content can rotate, but the host window does not.

There should by a menu entry to rotate the host window 90°:
Independing of the guest system."	E88
21219	RPC_S_SERVER_UNAVAILABLE when closing down VirtualBox GUI before virtual machine starts (regression)	VirtualBox-7.0.2	2022-10-30T13:00:37Z	2023-02-12T15:38:45Z	2023-02-12T15:38:45Z	"Problem description:
1. In Oracle VM VirtualBox Manager (GUI tool) click on virtual machine and then Start button.
2. Because I don't need VirtualBox Manager GUI anymore I close it down.
3. Like 2 to 3 seconds later I get error:
Failed to open a session for the virtual machine <vm name>
and Details:
Callee RC: RPC_S_SERVER_UNAVAILABLE/0x800706ba (0X800706BA)

It looks to me this problem only appears if VirtualBox Manager is closed down before virtual machine is getting started.

If I wait for few seconds and the virtual machine's window appears before I close down VirtualBox Manager, it looks like error never appears.

This problem started to happen now that after using VirtualBox 6.1 for years I upgraded directly to VirtualBox 7.0.2.

I am very used to closing down VirtualBox Manager after I click on Start virtual machine button. It gets supper annoying that I get this error, because I just forget that now for some reason I have to wait before virtualbox machine GUI appears.

It looks like a regression in v7.0 comparing to v6.1.

My host is: Windows 10
My guest is: Ubuntu 22.04"	bobJ
15347	RPC_S_SERVER_UNAVAILABLE when logging off host while VirtualBox.exe is running	VirtualBox 5.0.18	2016-04-25T13:18:14Z	2016-04-25T13:18:14Z	2016-04-25T13:18:14Z	"Host machine is Windows 7 Ultimate, SP1 64-bit.

1. Start VirtualBox Manager (VirtualBox.exe) - no need to actually start a VM
2. Log off from host machine.
3. VirtualBox Manager then gives the following series of error message boxes:

Failed to set the global VirtualBox extra data for key GUI/Toolbar to value {}.

Callee RC: RPC_S_SERVER_UNAVAILABLE 0x800706BA (0x800706BA)

Failed to set the global VirtualBox extra data for key GUI/Statusbar to value {}.

Callee RC: RPC_S_SERVER_UNAVAILABLE 0x800706BA (0x800706BA)

Failed to set the global VirtualBox extra data for key GUI/SplitterSizes to value {469,568}.

Callee RC: RPC_S_SERVER_UNAVAILABLE 0x800706BA (0x800706BA)

Failed to set the global VirtualBox extra data for key GUI/LastWindowPosition to value {319,152,1041,745}.

Callee RC: RPC_S_SERVER_UNAVAILABLE 0x800706BA (0x800706BA)

Failed to set the global VirtualBox extra data for key GUI/DetailsPageBoxes to value {general,system,display,storage,network,sharedFolders,description}.

Callee RC: RPC_S_SERVER_UNAVAILABLE 0x800706BA (0x800706BA)

Failed to set the global VirtualBox extra data for key GUI/LastItemSelected to value {m=FL Pro}.

Callee RC: RPC_S_SERVER_UNAVAILABLE 0x800706BA (0x800706BA)

At this point the VirtualBox Manager window has disappeared, but Task Manager shows that VBoxSVC.exe and (1 instance of) VirtualBox.exe is still running.

Attached are the log files that existed after:
- the aforementioned error messages
- I used Task Manager to kill the VBoxSVC and VirtualBox (so that WinZip did not complain about trying to read the log files)

This looks like it might be related to https://www.virtualbox.org/ticket/12933"	m6477
16181	RTC not updated when VM is resumed.	VirtualBox 5.1.8	2016-11-11T18:19:07Z	2016-11-11T18:19:07Z	2016-11-11T18:19:07Z	"Actual:
When a vm is suspended, unlike real hardware, both the RTC and the system clock are stopped.

Expected:
Like on actual hardware the RTC should continue, or should appear to do so by virtue of being synchronized with the host when the VM is resumed.

If the VM is power cycled, VirtualBox resets the virtual RTC to the correct time."	DaVinci
19925	"RTEXITCODE handleControlVM(HandlerArg *)"" at line 622 of file VBoxManageControlVM.cpp"	VirtualBox 6.1.14	2020-09-28T15:06:45Z	2020-10-02T07:00:31Z	2020-10-02T07:00:31Z	"In cycling testing I have got two the same errors. The are looked the same:
+ VBoxManage controlvm tuchanka3a poweroff
0%...10%...20%...30%...40%...50%...
Progress state: NS_ERROR_FAILURE
VBoxManage: error: Failed to power off machine
VBoxManage: error: The VM session was aborted
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component SessionMachine, interface ISession
VBoxManage: error: Context: ""RTEXITCODE handleControlVM(HandlerArg *)"" at line 622 of file VBoxManageControlVM.cpp

The same with tuchanka4d. VirtualBox is 6.1.12 r139181 (Qt5.6.3). MacOS is 10.15.6 (19G2021). Logs are attached."	Olleg
15487	Running Linux guest caused udisksd to fail host mounts	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
12180	running slow	VirtualBox 4.3.0	2013-10-15T14:02:45Z	2015-06-17T13:51:31Z	2015-06-17T13:51:31Z	I installed the version 4.3 of virtualbox. After installing virtualbox my vm's started running slow. So slow that I had to uninstall it and re install 4.2.18. attached is the log file from the vm that I was running.	CompTech
16511	Running VBox prevents notebook from switching into sleeping mode	VirtualBox 5.1.14	2017-02-25T09:32:07Z	2017-02-25T12:42:30Z	2017-02-25T12:42:30Z	"Running VBox (any guest) prevents notebook from switching into sleeping mode.

It looks like Windows can't set on pause or VBox fails to catch that signal from OS. May it be very exclusive usage of CPU by VBox?

For e.g., you can start compiling kernel in guest FreeBSD and try to switch notebook into sleeping mode to see it fails to."	MikhailRokhin
11375	Running Virtualbox causes high CPU usage in Elan Touchpad drivers	VirtualBox 4.2.6	2013-01-09T23:24:08Z	2017-05-16T18:05:57Z	2017-05-16T18:05:57Z	"Seeing high cpu usage on etdctrl.exe on Win 8 64bit host when any VM is started. Process must be killed manually and restarted to regain touchpad features. 

etdctrl.exe is part of the Elan Touchpad driver suite.

Host is on Win 8 64bit, Acer Aspire S7-391. "	tmk
17155	Running VirtualBox on Ubuntu 17.04 with guest Ubuntu 16.04 crashes VM during apt-get update	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
19697	Running VM crashes on macOS 10.13.6 with VirtualBox 6.1.10 r138449	VirtualBox 6.1.10	2020-07-02T23:35:34Z	2020-07-02T23:51:46Z	2020-07-02T23:51:46Z	"I'm running a Ubuntu 20.04 guest VM on a mac host. Guest addition already installed. The VM crashes frenquently.

Crash log attached."	wlnirvana
15905	Running Windows 10 as a guest in Xubuntu 16.04.1 host freezes the machine (3D-related)	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
6602	runtime change remembered through First Run Wizard	VirtualBox 3.1.6	2010-04-27T12:24:01Z	2010-04-27T12:24:01Z	2010-04-27T12:24:01Z	"""Remember Runtime Changes"" (under General -> Advanced) is unchecked.
In spite of this, when the ""First Run Wizard"" runs, and with it you mount an ISO or use the host drive for the CD-ROM, then this is remembered after the virtual machine is shutdown.
"	Jelle Geerts
18166	Ryzen 1700x - no 64 bit option	VirtualBox 5.2.22	2018-12-03T00:28:38Z	2018-12-03T05:56:39Z	2018-12-03T05:56:39Z	"Hello,
- I have windows 10
- I have a ryzen 1700X.
- SVM is enabled in the BIOS.
- HyperV is not installed.
VirtualBox won't let me chose a 64 bit option for guestn or even if i try 32bit it won't let me give it more than 1 core.
thanks for the help."	Wolfkiller
16861	Safenet Sentinel Driver	VirtualBox 5.1.22	2017-06-28T08:02:59Z	2017-06-28T08:31:04Z	2017-06-28T08:31:04Z	"Hi,
I am using Safenet Sentinel Drivers (security dongles).
Since Virtual Box V5.0 the driver is no longer usable on my Windows Virtual Box machines (W7 64 bits).
So I used to stay on V4.3.40 version.
Unfortunately, last W10 update forced me to upgrade my Virtual Box version cause V4.3.40 does not work anymore.
Could you make Safenet Sentinel Drivers work again please?
Thanks a lot.
Regards,"	Zikbull
12495	Sampling profiling method not usable in Visual Studio 2013	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
8311	SATA AHCI Errors: READ FPDMA QUEUED	VirtualBox 4.0.2	2011-02-09T15:53:00Z	2021-08-23T04:41:22Z	2021-08-23T04:41:22Z	"My guest OS hangs periodically with a harddrive command error followed by an attempt to reset the HD (reproduced with Ubuntu and !ArcLinux). This issue does not occur in the host OS (Windows 7), only in the Guest OS.

Environment:

 * Ubuntu running in a Virtual Box 4.0.2 running on Windows 7 64bit.
 * Asus G53JW Laptop
 * Intel X25 SSD HD

Log excerpts:
{{{
Jan 17 14:48:32 vm kernel: [ 1513.120252] ata3: hard resetting link
Jan 17 14:48:33 vm kernel: [ 1513.470345] ata3: SATA link up 3.0 Gbps (SStatus
123 SControl 300)
Jan 17 14:48:33 vm kernel: [ 1513.471232] ata3.00: configured for UDMA/133
Jan 17 14:48:33 vm kernel: [ 1513.471241] ata3.00: device reported invalid CHS
sector 0
Jan 17 14:48:33 vm kernel: [ 1513.471255] ata3: EH complete
}}}
{{{
[ 1513.120200] ata3.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x6 frozen
[ 1513.120210] ata3.00: failed command: READ FPDMA QUEUED
[ 1513.120222] ata3.00: cmd 60/08:00:30:66:4c/00:00:00:00:00/40 tag 0 ncq 4096
in
[ 1513.120224]          res 40/00:00:00:00:00/00:00:00:00:00/40 Emask 0x4
(timeout)
[ 1513.120230] ata3.00: status: { DRDY }
[ 1513.120252] ata3: hard resetting link
[ 1513.470345] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 1513.471232] ata3.00: configured for UDMA/133
[ 1513.471241] ata3.00: device reported invalid CHS sector 0
[ 1513.471255] ata3: EH complete
}}}"	andornaut
20882	SATA Controller Option Cause jbd2 blocking the disk access	VirtualBox 6.1.30	2022-03-26T07:19:18Z	2022-03-26T07:19:18Z	2022-03-26T07:19:18Z	"I use VirtualBox 6.1 In Ubuntu 20.04
when I create a new virtual machine with SATA disk controller , but have not  set the ""Use Host I/O Cache""  option (the default setting) 
if I intall a lot of debs, I will get very high disk I/O consumption at host machine, but have very very low disk throughput. 

useing  ittop, I find The reason is the jbd2 process blocking the disk access
Maybe it is a bug !!!"	BlackSmith
15821	sata disk not seen at guest install	VirtualBox 5.1.4	2016-08-18T16:05:44Z	2016-08-18T16:05:44Z	2016-08-18T16:05:44Z	"Trying to create windoww 7 64bit guest on macbook air.  Virtualbox 5.1.4.  Using pxe boot.  error reads:

FAILURE (5456): Unable to Determine Destination Disk, Partition and/or Drive.

This is with SATA enabled.  if i switch to sas, ide, or scsi, i can run the install without a problem.  Worked in vbox 5.0.n without problems.

"	ascott
7736	SATA disks not found after reboot into linux (ICH9 only)	VirtualBox 3.2.10	2010-11-19T10:25:07Z	2015-01-07T22:26:38Z	2015-01-07T22:26:38Z	"Situation:
 * I have a IDE hdd with a linux installation on it, as well as grub.
 * I have a IDE cdrom with an image of windows XP on it.
 * I have a SATA hdd with windows XP on it, or nothing

I want to boot the linux OS, which will determine if the windows XP partition is available and has booted correctly. If this is the case, a grub-reboot is issued to boot into windows XP once, otherwise the image is restored onto the HDD.
If I reboot from windows XP, the linux OS should do the above again.

On an actual machine, the procedure works without a hitch.

However after a reboot from windows XP to linux (Start | Shut Down... | Restart) the linux suddenly can't find the SATA disks.
dmesg has the following lines:
{{{
[    6.166426] ata1.00: qc timeout (cmd 0xec)
[    6.166426] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[    6.516437] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   16.517619] ata1.00: qc timeout (cmd 0xec)
[   16.517619] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[   16.517619] ata1: limiting SATA link speed to 1.5 Gbps
[   16.866406] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   46.866424] ata1.00: qc timeout (cmd 0xec)
[   46.866424] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[   47.216399] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   47.566424] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   52.566425] ata2.00: qc timeout (cmd 0xec)
[   52.566425] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[   52.916425] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   62.916398] ata2.00: qc timeout (cmd 0xec)
[   62.916398] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[   62.916398] ata2: limiting SATA link speed to 1.5 Gbps
[   63.266424] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   93.266437] ata2.00: qc timeout (cmd 0xec)
[   93.266437] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[   93.616439] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
}}}
Attached is the full vbox.log and the full dmesg as I have it."	Mike Musterd
20247	save machine state to disk and when resume the window is the smallest possible	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
21152	Save state and snapshot functionality is broken in version 7.0.0	VirtualBox 7.0.0	2022-10-14T22:00:23Z	2022-10-24T17:15:51Z	2022-10-24T17:15:51Z	"As I already wrote in the beta forum, I can't use neither save state nor snapshot functions in the new version.
After saving the state or making a snapshot, the next start of the guest causes an exception in the Vbox.

The saved state also can't be dropped. The drop function gives you ok, but after starting the VM, it tries to start from the saved state. Which is still on the disk.

Here is my original forum [https://forums.virtualbox.org/viewtopic.php?f=15&t=107200 post], and another [https://forums.virtualbox.org/viewtopic.php?f=2&t=107367 post] after release. I also append my logs."	boxer01
14913	Saved vm: Clone + reinitialize network doesn't really change MAC	VirtualBox 5.0.10	2015-12-09T13:34:48Z	2015-12-09T13:34:48Z	2015-12-09T13:34:48Z	"Steps to reproduce:
* make a VM, run it, pause it, save it (mac xxx7a)
* clone this VM, tick ""reinitialise all network interfaces""
* start the clone
* clone's setting - network - adapter 1 shows new mac (xxxb5)
* clone's kernel still sees old mac xxx7a
* reboot clone from it's shell
* clone's setting - network - adapter 1 shows new mac (xxxb5)
* clone's kernel still sees old mac xxx7a"	dimaqq
17853	Sayign that Virtualisation is disabled when it is definitely enabled	VirtualBox 5.2.14	2018-07-03T16:54:53Z	2018-07-12T21:59:26Z	2018-07-12T21:59:26Z	"When i try to load a virtual machine i get the following error

    ''Failed to open a session for the virtual machine Linux.
    
    VT-x is not available (VERR_VMX_NO_VMX).
        
    Result Code: E_FAIL (0x80004005)
    Component: ConsoleWrap
    Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
''
This is also happening for my Windows 7 Virtual machine (Both machines are 64-bit)

I have checked all the the things i could think of, and anything that came up after a quick google search and all seems okay to me.

So far i have checked:

Virtualisation Enabled in BIOS - Yes ->(https://imgur.com/gallery/cxYxs7d)

Hyper-V disabled in Windows - Yes -> (https://imgur.com/gallery/rO8u0j9)

Windows sees that Virtualisation is enabled in the Task Manager ->(https://imgur.com/gallery/92A0Ebb)

I have tried enabled and disabling Hyper-V to no avail.
I have also tried with both VT-D enable and disabled - Yet it makes no difference"	TheBritishBoi
12816	Scale Mode reworked into Zoom function	VirtualBox 4.3.6	2014-03-13T13:06:55Z	2014-03-25T09:01:44Z	2014-03-25T09:01:44Z	"
An essential feature for applications where host resolution cannot be changed at will.
Examples are old games and environments where fonts cannot be enlargened to be readable on modern displays with high resolutions.

It has been stated several times that VirtualBox shall not switch host resolution to match the guest. I guess we will have to do with scaling.

Current Scale Mode (as of VirtualBox 4.3.6) is not a proper fullscreen experience, as it retains the host window decorations and cannot truly occupy full screen. But it could be reworked a bit.

What I propose is that Scale Mode does not exist as a separate mode, but only as a specific setting.
The setting becomes active whenever the guest resolution and host resolution mismatch in both width and height. Host resolution here means the area which the host gives the guest to use, be it whole screen (fullscreen mode) or VM window client area in window mode.

Options:
A. 1:1 (note: black borders, as currently in 4.3.6)
B. Scale the image (with proper aspect ratio)

If user resizes the VM window or enters fullscreen, it works the same as until now:
VirtualBox tries to resize the guest desktop to achieve matching.
But if the resize fails, scaling is performed (according to user settings).

To put it simply: with scaling enabled, VirtualBox would scale the image in some of the current 'black border' situations.

Note that aspect ratio should be kept unchanged. I cannot imagine a single valid situation when you would want to distort the scaled image. Perhaps as an additional option to scale without regard to ratio, if someone needs it.

At this point, calling it ""Zoom"" begins to make more sense, as < 100% (reducing) would also be useful. A menu could be introduced to enable selecting specific zooms, similar to text editors, 100% option being most important to enable restoring the exact 1:1 pixel zoom.



VirtualBox already has a fullscreen mode and a working, but not ideal, Scale Mode. These should just be brought together.

Note: there are other fullscreen scaling/zooming enhancements proposed (like #10852), yes. But here I'm describing more precisely how the current Scale Mode can be reworked and become much more useful.

This enhancement is future-proof, as it can be further upgraded if required: adding additional modes, less-than-100% zooming (reducing), etc. It's about moving scaling from the current Scale Mode to where it belongs.
"	bostjan
17317	scaled mode in ubuntu 17.10	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
20997	Scancode returned by int15h call in BIOS keyboard handler(int09h) is ignored.	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
17667	Screen freezes above 1439p	VirtualBox 5.2.6	2018-04-05T19:37:59Z	2018-04-10T10:19:16Z	2018-04-10T10:19:16Z	"Ubuntu guest, Windows 8 host, 2560x1440 screen, I have had screen freezing when going into full-screen mode until leaving leaving full-screen mode. So I've done some tests with xrandr. Turns out if I set the resolution up to 2560x1438, everything works as expected, but 2560x1439 and up and the screen freezes until resolution is lowered again.

Tried many different configuration including 3d acceleration with same 1439 landmark. Size Hint doesn't help.

You can see in the log file there is a IFrameBufferPrivate::performResize when i set resolution to 1438 but nothing is logged when i set to 1439 and up.

Regards,
Thanks for your work
"	yrup
21025	Screen lock in Windows 10 Host makes the Linux Guest unresponsive (regression)	VirtualBox 6.1.36	2022-07-20T10:59:23Z	2022-07-20T10:59:23Z	2022-07-20T10:59:23Z	"After upgrading from 6.1.30 to 6.1.34, I've started to notice that my Centos 7.8 Guest goes unresponsive on regular basis.

I've been able to pinpoint it to the screen lock in the Windows 10 21H2 Host. Whenever I unlock the screen the VBoxHeadless.exe process uses 100% of all of the cores available to the Guest machine. Guest is unreachable neither by ssh nor by GUI.

This happens regardless of the graphic display used, and also in the headless start. Also changing hypervisor between the Hyper-V and KVM does not make a difference.

VirtualBox 6.1.36 behaves the same as 6.1.34, however downgrading to the 6.1.30 solves the issue.

Logs do not contain anything except repeating pattern of:
00:02:22.924401 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
00:02:24.627881 VMMDev: GuestHeartBeat: Guest is alive (gone 5 713 045 344 ns)
00:03:09.694062 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
00:03:15.648850 VMMDev: GuestHeartBeat: Guest is alive (gone 9 990 252 305 ns)
00:03:30.642448 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
00:03:30.792413 VMMDev: GuestHeartBeat: Guest is alive (gone 4 159 194 451 ns)
00:03:47.088470 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
00:03:52.836984 VMMDev: GuestHeartBeat: Guest is alive (gone 9 762 953 270 ns)
00:03:56.874575 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
00:03:57.771949 VMMDev: GuestHeartBeat: Guest is alive (gone 4 934 966 056 ns)
00:04:01.784622 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
"	MichalBrz
10620	screen locks in host OS, despite actively working in fullscreen guest OS	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
14899	Screen resolution defaults to 1024x768 and not to the selected before the reboot	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
18642	Screen Video Recorder	VirtualBox 6.0.6	2019-05-14T23:51:32Z	2019-05-18T11:52:21Z	2019-05-18T11:52:21Z	"Create a ReactOS VM, or Ubuntu WM, all standard config, and activate the Screen Recorder.

VirtualBox Aditions Intalled, same version.

In the first start, select ISO of ReactOS, and no boot, crash in start VM splash.

In the VirtualBox 6.0.4, with VB Additions, works fine."	wgtapia84
17689	Screen zoom Bug	VirtualBox 5.2.6	2018-04-16T17:49:04Z	2018-04-16T17:49:04Z	2018-04-16T17:49:04Z	Hey, I have a problem with the screen in virtualbox, is not only when I run a virtual machine, the problem starts when starting virtualbox. The thing is that everything is execesive zoomed even the virtualbox application. I tried all about changing the screen scale and all those things... 	AnxoOD
18946	Screenshot is causing the disk size update to fail	VirtualBox 6.0.12	2019-09-19T15:08:23Z	2019-09-23T15:49:09Z	2019-09-23T15:49:09Z	"Hi, 
I am running a host PC Windows 10. Using the virtualbox to launch a Cent OS. 
I was trying to update my disk size on the CentOS as i had reached 100% utilisation. So i used (as recommended by many sites to update this) below command:
{https://stackoverflow.com/questions/8141045/virtualbox-extend-partition
/mnt/c/Program\ Files/Oracle/VirtualBox/VBoxManage.exe modifymedium CentOSVD.vdi --resize 120000}

Idea was to increase the vdi size from 60Gb to 120Gb. 
But after this command, it was not directly reflecting in the Cent OS after restart (also windows restart). The increased volume succeeded on windows side without any errors. But CentOS was not showing this. 
After a lot of debug i found that i had a snapshot stored somewhere on the PC and this was preventing the additional disk to be shown on the CentOS.  {lsblk
NAME            MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda               8:0    0 68.3G  0 disk 
├─sda1            8:1    0     1G  0 part /boot
└─sda2            8:2    0 63.2G  0 part 
}
The sda partition was always showing 68.3G. Even though i increased the VDI to 120G, it was not reflecting here. Then i deleted the snapshot and then i saw the correct results. 
{ lsblk
NAME            MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda               8:0    0 117.2G  0 disk 
├─sda1            8:1    0     1G  0 part /boot
└─sda2            8:2    0 63.2G  0 part }
So somehow the process in the snapshot is preventing the process of disk space update. Please check.
Steps to reproduce:
1. Run Virtual Box on a windows 10 machine. 
2. Install the Cent OS running as guest OS on Virtual Box. 
3. Check the VDI disk size (Virtual and actual size)
4. Take a snapshot (Ctrl + Shift + T). Notice another VDI file is created in another location
5. Increase VDI disk size with above command (VBoxManage.exe modifymedium)
6. Reboot both windows and VBox. 
7. Check the disk space on guest OS (CentOS) it will not show the increase
8. Delete Snapshot. Newly created VDI file is deleted from Step 4.
9. Reboot both windows and VBox. 
10. Check the disk space on guest OS (CentOS) it will show the increase"	aanche
19624	Scroll bars missing in VirtualBox 6	VirtualBox 6.1.6	2020-05-26T18:24:52Z	2020-05-26T18:24:52Z	2020-05-26T18:24:52Z	"Hi,

I use scroll bars.  So it sucks when they constantly disappear.

There should be an option to permanently enable them.

Thanks.

Windows 8.1 64-bit
VirtualBox 6.1
"	veganaiZe
11329	SDK - IGuestSession - (conceptual) bug with CopyTo/From()	VirtualBox 4.2.4	2012-12-25T01:44:17Z	2015-02-03T17:14:39Z	2015-02-03T17:14:39Z	"There seems to be a (conceptual) bug with the IGuestSession::CopyTo() and CopyFrom(). The internal code is relying on a 30 seconds timeout for the whole copy operation to finish (because it's counting on some vbox_cat internal process spawn within the Guest). Obviously that fixed timeout is not realistic for large files such as 500MB-1GB long. Not to mention that the host file may not be really on the physical host itself, but located somewhere on the network.

I get into the same issue when I'm using the equivalent VBoxManage command."	smihaila
15036	SDK Python webserver bindings IMachine::setGroups() inconsistent signature	VirtualBox 5.0.12	2016-01-14T13:33:59Z	2016-01-26T20:31:03Z	2016-01-26T20:31:03Z	"Hi everybody,

Virtualbox 5.0 introduced the Grouping feature, but the SDK api seems to be not aligned to the new feature. In particular I have experienced a problem with the VirtuaBox_wrappers.py generated from the Virtualbox.xidl for the IMachine::setGroups() method.

Indeed, the following code is generated:


{{{
def setGroups(self, value):
       req=IMachine_setGroupsRequestMsg()
       req._this=self.handle
       if type(value) in [int, bool, basestring, str]:
            req._groups = value
       else:
            req._groups = value.handle
       self.mgr.getPort().IMachine_setGroups(req)
}}}

According to the method signature, the user has to pass a list/array of groups to set. This code will fail in that case: passing an array will make control enter the else clause, causing invalid access to undefined ""handle"" attribute. The generated code should only accept list/tupes and not strings. 
This requires some modification to the xidl file so the generated code reflects the method signature."	Alberto Geniola
17814	Seamless mode & sleep	VirtualBox 5.1.30	2018-06-11T18:37:51Z	2018-06-11T18:37:51Z	2018-06-11T18:37:51Z	"After wake up in seamless mode, the taskbar is not shown (guest OS is XP).
In addition when I tried to log off the saved state of VM was lost. It is better to do hibernate of shut down when host OS is logging off or shutting down.

"	386sx
17692	Seamless mode not available with MacOS 10.13.4 and Windows 1	VirtualBox 5.2.6	2018-04-17T17:16:55Z	2018-04-20T08:40:58Z	2018-04-20T08:40:58Z	I have downloaded VB Version 5.2.8 r121009 (Qt5.6.3) to my MacBook Pro running Macos 10.13.4. I have downloaded a version of Windows 10 for use on VB. When I try to use seamless mode, the option is greyed out under View.  	johnskeffington
14838	Search bar on VirtualBox website too small.		2015-11-17T02:26:23Z	2015-11-17T02:26:23Z	2015-11-17T02:26:23Z	"On the VirtualBox website, the search bar is too small, which is an issue for people with bad vision.
I know I can just simply zoom in, but it's a pain to zoom in and out just to search for something on the VirtualBox website."	Bug Tracker
21404	SECOND LINUX GUEST CRASHES ON WINDOWS STARTUP - VBOX 7.04 BUG	VirtualBox-7.0.4	2023-01-12T10:53:01Z	2023-01-12T10:53:01Z	2023-01-12T10:53:01Z	"When i am trying to automatically start a second Linux guest on windows 10 startup (through shell:startup), i get an error and the second Linux guest crashes.

The error message is ""The exception Breakpoint A Breakpoint has been reached (0x0000sFFCF66B225A. Click OK to terminate the program""

This bug  (or similarwith same results) occurs in all updates after 6.1.34 version, so i can't start e second guest automatically.

Please fix it !!!

Thank you "	Tasos Skarpathakis
11577	Secure Boot doesn't allow 'vboxdrv' module to load (now works for Ubuntu and Debian 10+ hosts)	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
19652	Segfault in vmsvgaR3PortReportMonitorPositions (vboxvga)	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
19031	Segfault on Fedora 30.	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
16266	Segmentation fault	VirtualBox 5.1.10	2016-12-05T07:23:06Z	2016-12-08T10:30:53Z	2016-12-08T10:30:53Z	"I don't know what prompted it, unfortunately. A couple minutes earlier I had attached a USB external storage device to the VM (which seemed to be handled by the guest OS without incident), then I told Windows 10 to check for updates. While it was doing that the VM window disappeared and I found a crash file. That VM session had been running for a while and been through at least one sleep–wake cycle of the host machine and the accompanying wireless network disconnections and reconnections.

I restarted the VM, and tried to reproduce by attaching the same USB device and telling Windows to check for updates again, but the crash did not repeat.

VirtualBox version: 5.1.10 r112026
Host OS: macOS 10.12.1
Guest OS: Windows 10 Pro Insider Preview version 1607 build 14965.1001"	terry
19628	Segmentation fault KERN_INVALID_ADDRESS, MacOS host	VirtualBox 6.1.8	2020-05-28T09:36:45Z	2020-05-28T09:36:45Z	2020-05-28T09:36:45Z	"MacOS host, Linux (OpenSUSE Tumbleweed) guest.
VM starts up, but segfaults when GUI startup happens. Crashes both VBox 6.1.6 and 6.1.8.

Part of the crashreport for easier searching:

{{{
Process:               VirtualBoxVM [867]
Path:                  /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM
Identifier:            org.virtualbox.app.VirtualBoxVM
Version:               6.1.8 (6.1.8)
Code Type:             X86-64 (Native)
Parent Process:        VBoxSVC [796]
Responsible:           VirtualBox [785]
User ID:               501

Date/Time:             2020-05-28 12:29:59.960 +0300
OS Version:            Mac OS X 10.15.5 (19F96)
Report Version:        12
Bridge OS Version:     3.0 (14Y908)
Anonymous UUID:        7F0F4F94-AA59-F9D4-DA55-099371894FD2


Time Awake Since Boot: 140 seconds

System Integrity Protection: enabled

Crashed Thread:        11  EMT-1

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000068
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Segmentation fault: 11
Termination Reason:    Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [867]
}}}"	Richlv
18679	Segmentation fault on startup up of `VirtualBox` under sway-wm using Wayland	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
9420	Selection for optical drives in the boot menu	VirtualBox 4.1.0	2011-08-11T23:32:21Z	2011-08-11T23:32:21Z	2011-08-11T23:32:21Z	"If I start a virtual machine and press F12 at the beginning the entry ""c) CD-ROM"" can only boot from one optical drive. I think there should appear a selection menu after ""c) CD-ROM"" is choosen that list all configured optical drives for this virtual machine."	Sworddragon
14053	separate caps-lock state between host & guest	VirtualBox 4.3.26	2015-04-16T07:51:31Z	2019-07-30T19:56:24Z	2019-07-30T19:56:24Z	"I'd like to suggest that each VM settings page have an additional setting for linking and unlinking the caps-lock state from the host to the guest (might as well include num-lock and scroll-lock states too).

The setting could be: ['''''linked to host'''''] or ['''''unlinked to host''''']. Unlinked would permit completely different states between the host and guest. But the default would be [linked to host].

I'm thinking that having it as an automatic switch (like with mouse cursor capture and release) would be easiest for the user. Each VM would have to keep track of its own caps-lock state. When the user returns to that VM, caps-lock is in the same state as when they left it.

A minor convenience? Yes.

More trouble than it's worth? Quite possibly.

Thanks for reading.

''':)'''"	RandomName123
18539	Serial Interface doesn´t work correctly	VirtualBox 6.0.4	2019-04-03T06:04:35Z	2020-01-20T08:53:09Z	2020-01-20T08:53:09Z	"Hi,

I installed VB 6.0.4 (Host W10 17763.379) and I use an old equiqment to transfer data to a virtual XP using the serial interface. I am using Port 1, COM1, Host-Interface, Pipe/Socket aktivated, Adresse COM1.
The transfer starts but after a fewsecond it terminats.
If I downgrad to VB 5.2.26 it work correctly.

Sorry about my bad enlish.

Best regards
Jürgen"	motog
20179	serial port freeze	VirtualBox 6.1.18	2021-02-10T08:51:46Z	2021-02-10T08:51:46Z	2021-02-10T08:51:46Z	hello, I work with a PC under w10 (20H2) and a virtual image in OS/2 WARP. when I'm in version 5.2.44 the series communication between OS2 and my automaton works fine (full load without worries loading time about 10 minutes). when I migrate to version 6 (all versions), the communication no longer works (doesn't start at all or hangs after a while). if I go back to version 5, it works again. what I see is that the transfer speed is much faster as if it did not take into account the transfer speed. can you tell me what to do to make it work in version 6. Thank you	COLLAUDIN
20713	Serial Port Hangs after xxxx Time	VirtualBox 6.1.30	2021-12-02T19:18:50Z	2021-12-02T19:18:50Z	2021-12-02T19:18:50Z	"An old VB6 application runs under Win XP which communicates with a controller via COM port 2.
The application always stops working after a certain period of time.
There was simply no more data sent.
The application was also unable to close the Com Port.
We tried 6.1.30 and 6.1.28 without success.
Now it has been running for several days thanks to version 5.2.44

It is certainly not a problem for the VB6 application, the error could also be reproduced with the HTERM program"	mbi
17078	Serial ports	VirtualBox 5.1.26	2017-09-13T00:48:44Z	2017-09-13T00:48:44Z	2017-09-13T00:48:44Z	Phisical serial port works under host OS and does not work under guest OS (Mode: Host Device). At the same time there is everithing OK in Device Manager of Guest OS (The device is working properly). Once the guest OS being launched the serial port vanishes from Host OS. Host and Guest OSes are Windows 7 SP1. I have checked with different motherboards.	MIke
20326	Server 2019 guest hangs	VirtualBox 6.1.20	2021-04-26T15:21:30Z	2021-04-28T12:42:29Z	2021-04-28T12:42:29Z	"
Ubuntu 20.04 VirtualBox 6.1.16 using Microsoft's Server 2019 Eval hangs after loading the GUI 
"	BobTheElderGeek
20915	SessionState never unlocked	VirtualBox 6.1.32	2022-04-26T07:24:01Z	2022-04-26T07:24:01Z	2022-04-26T07:24:01Z	"The step to reproduce the problem:

* Start a VM in ""headless""
* When the state is Running I stop it

The session state never go back to Unlocked.

Attached a .cpp that reproduce the problem.

From the log I see:
{{{
00:00:01.819978 Changing the VM state from 'DESTROYING' to 'TERMINATED'
00:00:01.824010 Console: Machine state changed to 'PoweredOff'
00:00:01.937393 VBoxHeadless: starting event loop
}}}

I suspect that VBoxHeadless do not exit becaus the event loop is started after the machine go to PoweredOff.

Using a ""gui"" session type do not reproduce the problem.

In VirtualBox 6.0 this works as expected also for ""headless"" session type.

"	mbono
3461	Settings saved in wrong place (WinXP)	VirtualBox 2.1.4	2009-03-01T14:48:20Z	2010-07-11T00:08:07Z	2010-07-11T00:08:07Z	"Hi, 

Currently Virtualbox save its settings here:[[BR]]
{{{%userprofile%\.VirtualBox}}}

Unfortunately, this is the wrong place under Windows XP. Applications are supposed to store their settings, etc. in {{{%appdata%}}}.

So it should be this way:[[BR]]
{{{%appdata%\.VirtualBox}}}

And, by the way, on a Windows system it's a bit unusual to use folder names with a leading dot (okay, I am a bit fussy now).

Therefore, to be even more Windows-like, it should be:[[BR]]
{{{%appdata%\VirtualBox}}}
"	David
19842	Settings' 'OK' button not working.	VirtualBox 6.1.10	2020-08-29T06:53:59Z	2020-08-29T06:53:59Z	2020-08-29T06:53:59Z	The 'OK' button in settings is not working for the Virtual Box Manager	H3
16353	Sever Clock Drift	VirtualBox 5.1.12	2017-01-04T03:11:31Z	2017-01-04T03:11:31Z	2017-01-04T03:11:31Z	"MacOS Sierra Host - Virtualbox Version 5.1.12 r112440 (Qt5.6.2)

Problem on both:

  Guest: ubuntu/xenial64 - 16.04


  Guest: boot2docker (docker-machine create -d virtualbox)

This does not seem to be related to other tickets I found.


Here are some examples:


30 seconds on guest -- 1min40 real time
{{{
ubuntu@ubuntu-xenial:~$ 
while true; do echo $(date -u -Iseconds) == $(curl --silent http://www.timeapi.org/utc/now) ;sleep 10; done
2017-01-04T02:48:35+00:00 == 2017-01-04T03:02:31+00:00
2017-01-04T02:48:46+00:00 == 2017-01-04T03:02:49+00:00
2017-01-04T02:48:56+00:00 == 2017-01-04T03:03:06+00:00
2017-01-04T02:49:06+00:00 == 2017-01-04T03:03:23+00:00
}}}

And here is another: 17 seconds on guest --> 30 seconds on host (real time)
{{{
daniel@darwin:~$ while true; do echo $(docker-machine ssh dev date) == $(date); sleep 10; done
Wed Jan 4 03:01:28 UTC 2017 == Tue 3 Jan 2017 22:06:10 EST
Wed Jan 4 03:01:32 UTC 2017 == Tue 3 Jan 2017 22:06:20 EST
Wed Jan 4 03:01:38 UTC 2017 == Tue 3 Jan 2017 22:06:31 EST
Wed Jan 4 03:01:45 UTC 2017 == Tue 3 Jan 2017 22:06:41 EST
}}}

"	daneroo
15179	Severe time drift in guest OS	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
16252	Share clipboard cause host copy and paste stuck	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
19266	Shared Clipboard not working bi-directionally	VirtualBox 6.0.16	2020-01-25T09:17:59Z	2020-01-25T09:17:59Z	2020-01-25T09:17:59Z	Hi, I am running a Windows XP SP3 VM on a Windows 10 64bit Host machine and. I am struggling to make the shared clipboard functionality work. The actual shared clipboard function doesn't work at all but i can drag and drop files from the host machine to the guest machine. The other way round this doesn't work. Am attaching a log file. Would really appreciate any advice on this.	alexKite
20585	Shared Clipboard, guest win10 aborted, or host ubuntu cliboard hangs	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
21260	shared folder does not work.  modprobe vboxfs fails due to  missing symbol (Debian kernel 6.0.0.2)	VirtualBox-7.0.2	2022-11-10T07:32:09Z	2022-11-15T06:42:14Z	2022-11-15T06:42:14Z	"Host Windows 10 Pro
22H2 
19045.2251

Guest: Debian GNU Linux
$ uname -a
inux ip030 6.0.0-2-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.0.5-1 (2022-10-28) x86_64 GNU/Linux

VirtualBox:
7.0.2 r154219 (Qt5.15.2)

---
Problem: Shared folder between host and guest no longer works.

I have noticed that file sharing between the host no longer works.
I *think* this is  related to the local upgrade of the kernel to 6.0.0.2.

I installed the guesttools.
However, after some investigation, I realized vboxsf module is not loaded.
The reason is the missing symbols when vboxsf is loaded.

modprobe vboxsf fails:
{{{
root@ip030:/var/log# modprobe vboxsf
modprobe: ERROR: could not insert 'vboxsf': Unknown symbol in module, or unknown parameter (see dmesg)
}}}
dmesg shows:
{{{
[ 1992.940391] Spectre V2 : System may be vulnerable to spectre v2
[ 1992.940396] vboxsf: loading module not compiled with retpoline compiler.
[ 1992.940527] vboxsf: Unknown symbol VBoxGuest_RTLogRelGetDefaultInstanceEx (err -2)
[ 1992.940535] vboxsf: Unknown symbol VBoxGuest_RTLogLoggerEx (err -2)
[ 1992.940541] vboxsf: Unknown symbol VBoxGuest_RTErrConvertToErrno (err -2)
[ 1992.940554] vboxsf: Unknown symbol VBoxGuest_RTStrNLen (err -2)
[ 1992.940589] vboxsf: Unknown symbol VBoxGuest_RTLogBackdoorPrintf (err -2)
[ 1992.940600] vboxsf: Unknown symbol VBoxGuest_rtR0MemObjLinuxVirtToPage (err -2)
[ 1992.940631] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexCreate (err -2)
[ 1992.940637] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexDestroy (err -2)
[ 1992.940643] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexRequest (err -2)
[ 1992.940649] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexRelease (err -2)
[ 1992.940655] vboxsf: Unknown symbol VBoxGuest_RTAssertMsg1Weak (err -2)
[ 1992.940661] vboxsf: Unknown symbol VBoxGuest_RTAssertMsg2Weak (err -2)
[ 1992.940667] vboxsf: Unknown symbol VBoxGuest_RTAssertShouldPanic (err -2)
[ 1992.940673] vboxsf: Unknown symbol VBoxGuest_RTStrCopy (err -2)
[ 1992.940679] vboxsf: Unknown symbol VBoxGuestIDC (err -2)
[ 1992.940685] vboxsf: Unknown symbol VBoxGuest_RTSemMutexRequest (err -2)
[ 1992.940691] vboxsf: Unknown symbol VBoxGuest_RTSemMutexRelease (err -2)
[ 1992.940697] vboxsf: Unknown symbol VBoxGuest_RTSemMutexCreate (err -2)
[ 1992.940702] vboxsf: Unknown symbol VBoxGuest_RTSemMutexDestroy (err -2)
[ 1992.940708] vboxsf: Unknown symbol VBoxGuest_RTMemContAlloc (err -2)
[ 1992.940714] vboxsf: Unknown symbol VBoxGuest_RTMemContFree (err -2)


}}}

It seems that vboxsf is not compiled locally using retpoline compiler?
But I am not sure if it matters or not.

"	ci-zephyurus
8195	Shared folder error with long filename after snapshot restore	VirtualBox 4.0.0	2011-01-27T07:06:28Z	2017-02-28T13:18:45Z	2017-02-28T13:18:45Z	"- Snapshot created during running (WinXP) gast

- Snapshot restored (with vboxmanage startvm)

- Create an ordner on shared folders with more than 8 characters --> failes

- Access on files with more than 8 charcters in filenames failes

- Sometimes after a while (I don't know why and after which action), it is possible to access some longer filenames

- For Example:

  - Start Windows Explorer an try to create an (default) ordner.

  - It will be create ""ordn"" only, instead ""Neuer Ordner"".

- Hint:

  - An other program tell, the shared folder support only 8 standard characters.
"	vbdevtest
15670	Shared folder is not mounted at VM start	VirtualBox 5.1.2	2016-07-23T09:22:10Z	2016-08-09T07:12:10Z	2016-08-09T07:12:10Z	Under Windows 2000, shared folders are not automatically mounted at system start whereas it was the case with virtualbox 5.0.24. Manual mapping is required.	PBT78
418	Sharing a single VM on multiuser accounts (Ubuntu)	VirtualBox 1.4.0	2007-06-13T13:28:56Z	2010-05-03T18:30:32Z	2010-05-03T18:30:32Z	"Sorry for the poor english... let's try it :

I'm using Vbox since a few weeks, on ubuntu. I've created 4 accounts on my ubuntu. On the VM, I've winXP PRo installed, with the same 4 accounts.
The VM is installed on a shared directory with full acces rwx to the vbox users, outside the /home/user/.VirtualBox...

Problem :
I wish I can have full access to the VM with all 4 users of ubuntu, but it's not totally possible... Indeed, there's a file which is created (each time you modify something in the VM config) in the user's  directory/home/userA/.virtualBox/VirtualBox.xml   
When you logout the VM, and the user A session, and login on a userB session & restart the VM, if something has changed on the VM config, an error occurs. I assumed that's why it's impossible to use the snapshot fonction when you have more than 1 user on ubuntu...

To solve the problem, I'm editing the VirtuaBox.xml files, on my 4 account and copy/paste the up-to-date file... But that's pretty boring...

It will be great if we could have only ONE VirtualBox.xml file, in a share place...

possible enhancement 1: 
Make possible an install on a share directory, outside the /home/user/.virtualbox/ directory, with ALL the necessary files in it... 
possible enhancement 2:
Make possible to use a single .vdi file for 2 different VM... Then, it will be possible to create a different VM for each users of ubuntu, which can access to the same ""harddrive"".

If you have something to propose, I can beta test it for you...

Hope you understood my poor english...

Seb

"	seb.kempf
15269	shift + scroll wheel inoperative	VirtualBox 5.0.16	2016-03-23T20:58:40Z	2019-08-16T05:48:22Z	2019-08-16T05:48:22Z	"Mouse scroll wheel events do not get passed to the guest if Shift key is being held down. This only seems to happen when the host OS is OS X; same VM works as expected if hosted on a Linux host instead. Very inconvenient, as some applications use Shift-scroll to perform specific actions, e.g. horizontal scrolling of a window.

Misbehavior has been noted in multiple applications which use Shift-scroll to perform UI actions. Lack of mouse scroll events when Shift is held has also been verified via the xev tool.

Host is OS X 10.11.3 (El Capitan), guest is Debian 8 (Jessie) running KDE, with up-to-date patches and Guest Additions installed."	MikeUatCS
13417	Shortcut doesn't start VM window in the foreground	VirtualBox 4.3.16	2014-09-19T17:55:39Z	2014-10-14T19:38:21Z	2014-10-14T19:38:21Z	"I'm running Windows XP SP3 as guest OS in a Windows 7 Ultimate 64-bit host. I've created a shortcut to the VM using the feature in VirtualBox Manager.

When starting the VM using the shortcut, the VM window is not brought to the foreground. Although it will appear on top of the desktop (if the shortcut is on the desktop), it will not have focus until you click in it or switch to it using Alt-Tab.

However, the VM window is brought to the foreground when started from VirtualBox Manager.

This seems to be a side effect of the recent Windows hardening changes, but I'm not sure."	bogdan
17216	Should be able to add USB filesystem dump	VirtualBox 5.0.40	2017-10-27T09:29:45Z	2017-10-27T18:21:16Z	2017-10-27T18:21:16Z	"dd if=/dev/sdb of=myusb.bin bs=512

There seems to be no way to attach this. only VMDK, VDI etc are supported. Surely this is a really common use case?

if I force to add it, I get an error popup. There is a bug in the error popup, the [X] does not work. Can that be fixed too?
"	Jonny
20899	show the VM logs from the running machine window	VirtualBox 6.1.30	2022-04-12T07:53:38Z	2022-04-12T07:53:38Z	2022-04-12T07:53:38Z	It would be handy to have the Show Log... menu item in the Machine menu of the running VM window.	xerces8
13235	Shutdown hangs in OS/2 guest	VirtualBox 4.3.14	2014-07-24T05:43:48Z	2015-07-15T01:59:27Z	2015-07-15T01:59:27Z	"Hi/2.

Since 4.2.x, shutdown hangs in OS/2 guest.

I'm using OS/2 Warp 4.52, W4_104a kernel, and installed guest addition."	KO Myung-Hun
7142	SHUTDOWN=acpibutton fails to wait for shutdown of headless/vrdp guest with parrallel boot activated on host	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
18139	SIGINT (or Ctrl-C) on Mac Host not passed to Guest	VirtualBox 5.2.22	2018-11-19T15:53:36Z	2018-11-29T23:59:14Z	2018-11-29T23:59:14Z	"When running a CentOS 7 guest on Max OS X (High Sierra & Mojave), any Ctrl-C command on the terminal is not captured and passed to the guest.

I ran into this issue originally via the terminal app when running the VirtualBox instance with Vagrant. However, i enabled the VBox Gui and then logged in directly. The Ctrl-C command is not being captured correctly and passed to the foreground process. 

You can see in the attached image the keyboard input as i tail a log file. The command should have terminated the tail, instead the key combination is displayed. "	BStopp
21428	Signal 9	VirtualBox-7.0.6	2023-01-22T22:18:31Z	2023-01-22T22:18:31Z	2023-01-22T22:18:31Z	"I was trying to boot android 9 on macOS Ventura 13.2 beta but this happened 
VM Name: Android 9
The virtual machine
'Android 9° has
terminated unexpectedly during startup because of signal 9.
Result code: NS_ERROR_FAILURE(0X80004005)
Component: MachineWrap
Interface: IMachine
{300763af-5d6b-46e6-aa96-273eac155381}

I dunno what to do And I scoured the inter webs and could not find anything

Also no one has said anything on this before at least not of my knowledge.

Please help"	UKNOWN VM
19944	SIGSEGV on poweron	VirtualBox 6.1.14	2020-10-06T13:11:56Z	2020-10-08T06:29:40Z	2020-10-08T06:29:40Z	"VM rarely aborts on start. Output:
{{{
PowerOn tuchanka2b
+ VBoxManage startvm tuchanka2b
Waiting for VM ""tuchanka2b"" to power on...
VM ""tuchanka2b"" has been successfully started.
}}}
In working dir:
{{{
$ less ~/2020-10-06-00-11-53.074-VBoxHeadless-75716.log
Log created: 2020-10-06T00:11:53.740794000Z
Process ID:  75716 (0x127c4)
Parent PID:  36508 (0x8e9c)
Executable:  /Applications/VirtualBox.app/Contents/MacOS/VBoxHeadless
00000001034f4000 <NULL>: ffffffffffffffff != 0000700005eba000; cLockers=-1 cNestings=1
}}}
VBoxSVC:
{{{
08:08:03.353022 Watcher  Reaper: Pid 3948 (f6c) was signalled: 11 (0xb)
}}}

Full logs will be attached."	Olleg
19672	Single step emulation bug	VirtualBox 6.1.10	2020-06-19T08:52:30Z	2020-06-19T08:52:30Z	2020-06-19T08:52:30Z	"Single stepping code in a guest VM doesn't work correctly with I/O instructions.

I first noticed the problem in the built in kernel debugger in my OS. By further examination I also noted that the problem could be reproduced in Windows XP with both the 16-bit command line debugger and an a free 32-bit version of the same. Thus the problem is general.

The problem was detected with single stepping the out instruction. The instruction following the out instruction will also be single stepped, causing the guest VMs exception #1 to point to the wrong instruction.

out 80,al
call Foo

will point to first instruction in Foo instead of the call Foo line.

As RDTSC instruction has been fixed in a similar situation, I assume you have not applied the fix on all privileged instructions like IN, OUT, INT nn etc. The VM emulator should check the TF flag in the instruction emulator and emulate exception #1 in addition if it's set.

I have included the VBOXBUG.COM file that reproduce the problem in Windows XP debug command.

debug VBOXBUG.COM will load the program.

Write U for disassembling and you see what it does. For every out instruction we trace into the subroutine that is called after the OUT instruction instead of stopping at the CALL instruction following it.

You use the T (TRACE INTO)command for single stepping. Perhaps P (TRACE OVER) generates the same problem.

Best regards,

B-O Bergman
PQURE Technology"	B-O
18550	SIP has to be disable	VirtualBox 6.0.4	2019-04-08T04:58:34Z	2019-04-08T05:31:24Z	2019-04-08T05:31:24Z	"hi,
Im using VirtualBox for some time now on a MacMini.
Last week after an upgrade of OSX 10.13.16. I think since automatic update is activated. I got kernel errors as soon as I opened my windows guests.
Installation of new VirtualBox 6 wasn't possible, neither old versions
I disabled SIP, and All issues were solved.
After installation of VirtualBox 6. the Windows guest worked again
Enabled SIP again and the kernel errors appeared again
Can there be a setting change in my host that Im unaware of? I found other cases where users turned off SIP some time ago. So I think SIP is the strong medicine for another small issue.
Have you seen this before? I might have surged with the wrong key words. I dont know which rights need to be set for the kernel. I didnt change any settings actively so this must have happend during the update.
"	itIsMe
14084	Sketch feature.	VirtualBox 4.3.26	2015-04-28T11:14:05Z	2015-05-04T07:51:02Z	2015-05-04T07:51:02Z	"I would like to propose a group of new features. I would have ability to create a new machine simply and fast from created earlier sketch. In my opinion the best solution is give ability to create compete scratch with disk image. Afterwards we can create new machine from scratch with checkbox ""use blank disk"" to give user ability to create blank machines with same settings. "	xearo
10953	Slow Guest Desktop	VirtualBox 4.2.0	2012-09-17T23:38:58Z	2015-01-15T23:04:04Z	2015-01-15T23:04:04Z	"After upgrading to 4.2.0 by first uninstalling 4.1.22 guest tools, rebooting and installing 4.2.0 and rebooting clean, I see very slow desktop. Dragging any guest windows (Win7 x32) are lagging behind mouse. I know this is not a good measurement but on 4.1.x is was much much faster. Also dragging window around leaves dirty lines (from dragged window) on desktop all over. At some point it desktop will get refreshed. I try to get screenshot but whenever I try to get screenshot desktop is refreshed.
When I mean drag window in circle motion mouse stops and window still is in motion following circle.
I did try to uninstall guest tools. Reboot Guest and Host and nothing works.
Host is Mt Lion 10.8.1"	oxoocoffee
17746	"Slow I/O when ""Use Host I/O Cache"" is switched on"	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
20760	Slow performance since last update	VirtualBox 6.1.30	2022-01-06T03:47:51Z	2022-01-06T03:47:51Z	2022-01-06T03:47:51Z	"update to windows 11 slowed things down and since the las vbox update, my VM are unusable

extreme slow speed (response,Latency,Loading)
CPU usage is high for no apparent reason (Firefox use 60% CPU (8cores)

crashes

ive installed vmware to test if it was due to windows 11 but vmware work like vbox when no probleme were existing"	dparadis
18582	Slow startup	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
18940	Smart hide, auto-hide, hot corners and etc.. not working	VirtualBox 6.0.10	2019-09-18T04:26:48Z	2019-09-20T16:50:19Z	2019-09-20T16:50:19Z	Docks, top bars and title bars can be easily hidden by configuring the system from the settings or by downloading extensions. But none of them showing up when pointing/pushing/triggering their hot corners or places....	centaurusa
16294	Snapshot confirmation after closing virtual machine	VirtualBox 5.1.10	2016-12-15T14:41:11Z	2016-12-20T18:36:10Z	2016-12-20T18:36:10Z	"Hello, I just deleted about 30GB of data restoring a virtual machine, I mistakenly chose ""Restore snapshot"" from the closing dialog and the application did not poped up a confirmation to restore it.

Thanks...!"	hds
11205	snapshot management on toolbar	VirtualBox 4.2.4	2012-11-15T21:46:56Z	2012-11-18T14:05:22Z	2012-11-18T14:05:22Z	tried searching, didn't find anything similar.  VMWare's ability to revert to snapshots from the menubar+utility bar (the tab bar providing quick options w/in the guest session) is very handy.  Best way I've found to revert to snapshots in VBox is to power down the machine and then revert to the snapshot, or click all over the VBox Manager window to get to the snapshot pane. Neither of which are at all convenient.  Would be nice to have fewer-click shopping for snapshots.	dorklord
12567	snapshot to a remote iSCSI volume (builtin initiator) broken since 4.3.0 (verified on Windows and Mac hosts)	VirtualBox 4.3.6	2014-01-03T11:34:57Z	2016-12-14T23:05:17Z	2016-12-14T23:05:17Z	"Hello,

I used to have workstations running local !VirtualBox VMs which base disk are connected to the same remote iSCSI read-only lun. It use to work because each VM also have a default snapshot to the base disk meaning disk writes are redirected to the local differential disk created by the snapshot.[[BR]]
This worked correctly from version 4.0 to latest 4.2.20 and seems broken starting from 4.3.0, including latest 4.3.6.[[BR]]
I could verify this on a Mac host (OSX 10.9) and a Windows host (Windows 7 Prof.). I expect it to be the same on a Linux Host but didn't have a chance to verify.

How to reproduce:[[BR]]
machine 1: iSCSI server (I used ietd on SLES). IP address 192.168.0.19[[BR]]
machine 2: !VirtualBox host (Windows or OSX using Virtualbox 4.3.6). IP address 192.168.0.23

 1. machine 1: 
  - create an iSCSI target and a read-write 20GB Lun [[BR]]
  target: iqn.1995-09.fr.univ-lr:storage.win7 [[BR]]
  lun: 2

 2. machine 2:
  - create a VB VM 'win7' without a hard disk
  - attach the iSCSI volume from machine 1 with VBoxManage:
  {{{
VBoxManage storageattach ""win7"" --storagectl IDE --port 0 --device 1
  --type hdd --medium iscsi --mtype normal --server ""192.168.0.19""
  --target ""iqn.1995-09.fr.univ-lr:storage.win7"" --lun 2
}}}
  - install the guest OS (Windows 7 Pro.)
  - start the guest OS once after install to make sure booting read-write from the remote target works fine
  - poweroff the VM and create a snapshot

 3. machine 1:
  - make the previous Lun 2 read-only

 4. machine 2:
  - start the VM

With !VirtualBox 4.3.6, the VM hangs just after starting and the associated host process is using 100% CPU time. The diffential disk never grows and there isn't any iSCSI network traffic on machine 1.
Unfortunately, nothing interresting in the VM log file (Windows host or Mac host).

With !VirtualBox 4.2.20, the guest OS starts and differential disk of the snapshot starts to grow while block are written

If I downgrade from 4.3.6 to 4.2.20 everything works fine again.
So it's clearly related to something changed starting from 4.3.0
Note, I also tried with immutable disk wich avoid creating a snapshot manually and makes the VM revert to its pristine state at each start (which is the desired behaviour) and the results are the same.

Thanks for you help and ready to provide any additional details as needed.

Happy new year

Alban
"	Alban
16420	Snapshots present but required Machine/@currentSnapshot attribute is missing.	VirtualBox 5.1.14	2017-01-24T11:29:01Z	2017-01-30T11:58:24Z	2017-01-30T11:58:24Z	"Hello,

since morning I receive this issue when starting directly into Virtualbox.
Yesterday I used my Ubuntu VM, took a snapshot and closed it.

Everything looked fine.

Please tell me a solution.

Thank you.

Regards

Andreas"	Haemma
16612	Snapshots: Inheritance of options from parent snapshot should be improved (wishlist?)	VirtualBox 5.1.18	2017-03-26T20:04:06Z	2017-03-26T20:08:42Z	2017-03-26T20:08:42Z	"The situation:

1)

VM with immutable disk. Created a (visible) snapshot on top of that, set it to ""autoreset OFF"".

This works as expected. When the VM is restore to that snapshot, the snapshot file gets replaced with a new one, with ""autoreset ON"". OK, this is based on the invisible snapshot (to facilitate an immutable base image). I kinda understand the behaviour.

2) same as 1) but another snapshot layer.

* base-image (immutable)
* user-snapshot-1 (autoreset OFF)
* user-snapshot-2 (autoreset OFF)

When restoring the current state to user-snapshot-2 I expect it to inherit (autoreset OFF) from its parent user-snapshot-1, but it doesn't! This irks me a lot.
"	robert spitzenpfeil
20351	SNMP Issues & Mgmt	VirtualBox 6.1.22	2021-05-09T19:50:47Z	2021-05-11T20:39:52Z	2021-05-11T20:39:52Z	"1) Virtualbox 6.122 on MACOS Provides SNMP Interfaces to a Third Party SNMP Manager but Virtualbox 6.122 on Windows has identically configured virtual machines inaccessible to the same management station.

2) WE need the Hypervisor(VirtualBoxManager) to get an IP address assignment, and have its own SNMP Mib support.

3) The Hypervisor MIB should identify the status, name, and performance of the VM's installed on the machine.

Working with HPOV/Microfocus NNMI and have tried the same issues to both Ivanti, and Opensource PandoraFMS with same result.

4) Without SNMP support, this product is not deployable in a large enterprise.

Sincerely,
Greenville Associates Consulting."	greenville02
15204	Soft lockup - CPU stuck for 22s	VirtualBox 5.0.14	2016-03-04T18:01:29Z	2016-03-04T18:15:53Z	2016-03-04T18:15:53Z	"After running a Virtualbox VM brought up with Vagrant for a long period of time, we are eventually unable to reach the host. We are forced to restart the VM in order to be able to connect to it again. The kernel log contains soft lockup errors.

Host: OS X 10.10.4
Guest: Ubuntu 14.04 3.19.0-51-generic:amd64"	mdelillo
20255	Solaris 11.4 gnome continuous restarting - application 'org.gnome.Shell.desktop' killed by signal 11	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
11720	Solaris Autostart service can only work for 1st user in staff group => fixed in SVN	VirtualBox 4.2.12	2013-04-15T18:20:24Z	2017-04-17T07:21:00Z	2017-04-17T07:21:00Z	"
First:
The use of ""exec"" in smf-vboxautostart.sh breaks the loop through the users as it replaces the current process with the ""su"" process. It also prevents the immediately following exit status check from functioning.

Second:
The smf-vboxautostart.sh script loops over the ""staff"" Unix group instead of the ""vboxuser"" Unix group to determine which users to look for to start autostart-enabled VMs.
The use of the ""vboxuser"" group makes more sense than ""staff"" as not all companies use ""staff"" for their users, and the ""vboxuser"" group is a required group for anyone running VirtualBox anyways.

Third:
Looping through ""logins -g ''group''"" includes 5 columns of data (including the GECOS field), so it will be looping over UID, group, GID, first name, last name, etc. as well as the username. At a minimum, it should be piped through ""cut -d' '  -f1"" to strip out the irrelevant data.
{{{
        # Get all users
        for VW_USER in `logins -g staff`
        do
            exec su - ""$VW_USER"" -c ""/opt/VirtualBox/VBoxAutostart --background --start --config \""$VW_CONFIG\"" --logrotate \""$VW_ROTATE\"" --logsize \""$VW_LOGSIZE\"" --loginterval \""$VW_LOGINTERVAL\""""

            VW_EXIT=$?
            if [ $VW_EXIT != 0 ]; then
                echo ""VBoxAutostart failed with $VW_EXIT.""
                VW_EXIT=1
                break
            fi
        done
}}}

I suggest changing it to the following (diff attached):
{{{
        for VW_USER in `logins -g vboxuser | cut -d' ' -f1`
        do
            su - ""$VW_USER"" -c ""/opt/VirtualBox/VBoxAutostart --background --start --config \""$VW_CONFIG\"" --logrotate \""$VW_ROTATE\"" --logsize \""$VW_LOGSIZE\"" --loginterval \""$VW_LOGINTERVAL\""""

            VW_EXIT=$?
            if [ $VW_EXIT != 0 ]; then
                echo ""VBoxAutostart failed with $VW_EXIT.""
                VW_EXIT=1
                break
            fi
        done
}}}

The above fixes all three problems: autostart VMs not starting unless you're 1st in the list; users not in ""staff"" group not having VMs started); and attempting to su to groups, numbers, etc.
(diff attached)

Note the diff also contains a clarification of error output for the top section where it checks if a file is executable, then if it exists. I reversed those and changed the error to make more sense.
{{{
--- /opt/VirtualBox/smf-vboxautostart.sh.orig   Fri Apr 12 12:19:08 2013
+++ /opt/VirtualBox/smf-vboxautostart.sh        Mon Apr 15 19:23:31 2013
@@ -24,13 +24,13 @@
 
 case $VW_OPT in
     start)
-        if [ ! -x /opt/VirtualBox/VBoxAutostart ]; then
+        if [ ! -f /opt/VirtualBox/VBoxAutostart ]; then
             echo ""ERROR: /opt/VirtualBox/VBoxAutostart does not exist.""
             return $SMF_EXIT_ERR_CONFIG
         fi
 
-        if [ ! -f /opt/VirtualBox/VBoxAutostart ]; then
-            echo ""ERROR: /opt/VirtualBox/VBoxAutostart does not exist.""
+        if [ ! -x /opt/VirtualBox/VBoxAutostart ]; then
+            echo ""ERROR: /opt/VirtualBox/VBoxAutostart is not executable.""
             return $SMF_EXIT_ERR_CONFIG
         fi
 
@@ -51,9 +51,9 @@
         [ -z ""$VW_LOGINTERVAL"" ] && VW_LOGINTERVAL=86400
 
         # Get all users
-        for VW_USER in `logins -g staff`
+        for VW_USER in `logins -g vboxuser | cut -d' ' -f1`
         do
-            exec su - ""$VW_USER"" -c ""/opt/VirtualBox/VBoxAutostart --background --start --config \""$VW_CONFIG\"" --logrotate \""$VW_ROTATE\"" --logsize \""$VW_LOGSIZE\"" --loginterval \""$VW_LOGINTERVAL\""""
+            su - ""$VW_USER"" -c ""/opt/VirtualBox/VBoxAutostart --background --start --config \""$VW_CONFIG\"" --logrotate \""$VW_ROTATE\"" --logsize \""$VW_LOGSIZE\"" --loginterval \""$VW_LOGINTERVAL\""""
 
             VW_EXIT=$?
             if [ $VW_EXIT != 0 ]; then
}}}


I started a forum post on this, originally thinking the problem was the use of null arguments to options when calling VBoxAutostart (before I noticed the ""exec""), as VBoxAutostart fails under those conditions.
[https://forums.virtualbox.org/viewtopic.php?f=11&t=55006]

"	kburtch
16366	Solaris x86 Host - Centos 7 Guest hangs after using all the memory	VirtualBox 5.1.12	2017-01-08T11:24:22Z	2017-01-26T22:18:55Z	2017-01-26T22:18:55Z	Solaris x86 Host has 64GB Memory. Centos7 Guest VM given 16GB. After about 3-4 days the VirtualBox process consumes all 16GB and the VM is unavailable. Am able to stop and start the VM and it will stay running for another 3-4 days.	Buster Gonad
19434	some characters are not rendered in QML Application	VirtualBox 6.1.4	2020-03-27T09:12:20Z	2020-03-27T09:12:20Z	2020-03-27T09:12:20Z	"Hi 
The webs emulator use VirtualBox.

In webOS with following configuration,  some characters are not rendered in QML application.
 * Mac OS Mojave
 * VirtualBox 6.1.4

If OS is changed to Linux or Window in same configuration, It works fine.

I'm creating the issue to find out what to investigate. 
 * VirtualBox in host OS or webOS emulator image (A.K.A. guest OS)

If you have any opinion, please let me know.  "	Taehoon Lee
20804	Some keystrokes dont get recognized in vm [Windows-Host]	VirtualBox 6.1.32	2022-02-02T14:44:06Z	2022-02-02T14:44:06Z	2022-02-02T14:44:06Z	"## Setup
I am running a Windows 11 64-bit host, with virtualbox 6.1.32 64bit. 
The host is running headless with windows remote desktop access to it.

## How to recreate 
1. connect to the windows host via rdp
2. check that keyboard and mouse are working. (i.e. against a browser writing this issue)
3. install virtualbox
4. create a vm (in my case linux)
5. start the vm 
6. try to input text into the vm (tried with captured pointer and without)

## What happens

When pressing any key from (""a"",...,""z"",""1"",...,""0"") no press seems to be registered by the vm.
Pressing enter or backspace the vm seems to register the key being pressed.

## What should happen

""Any"" keypress except the ""hostkey"" should be send to the vm.


## What kinda worked as a workaround

All displayable chars as keypresses from the ""onscreen keyboard"" seem to be recognized and send to the vm.
But it is a pain in the bum.



I would love to hear back, help where i can, would love to recieve feedback and a fix would be aweasome."	Nickmato
20927	Some nested qemu VM crashes at grub if launched in dozens	VirtualBox 6.1.32	2022-05-04T18:28:04Z	2022-05-04T18:28:04Z	2022-05-04T18:28:04Z	"Hello,

I'm using gns3 inside vbox with multiple virtual nodes (openwrt running as qemu vms). If I start all nodes at the same time, some of them crashes during the grub countdown (or a even little bit before) with:

{{{
KVM: entry failed, hardware error 0x80000021

If you're running a guest on an Intel machine without unrestricted mode
support, the failure can be most likely due to the guest entering an invalid
state for Intel VT. For example, the guest maybe running in big real mode
which is not supported on less recent Intel processors.

EAX=00000010 EBX=0000c866 ECX=00040000 EDX=0ff8f7c0
ESI=0ff8f760 EDI=00000005 EBP=00001ff0 ESP=00001ff0
EIP=000082fd EFL=00010006 [-----P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
CS =0008 00000000 ffffffff 00c09b00 DPL=0 CS32 [-RA]
SS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
DS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
FS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
GS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
LDT=0000 00000000 0000ffff 00008200 DPL=0 LDT
TR =0000 00000000 0000ffff 00008b00 DPL=0 TSS32-busy
GDT=     00008280 00000027
IDT=     00000000 000003ff
CR0=00000011 CR2=00000000 CR3=00000000 CR4=00000000
DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 
DR6=00000000ffff0ff0 DR7=0000000000000400
EFER=0000000000000000
Code=ef 82 00 00 08 00 66 b8 10 00 8e d8 8e c0 8e e0 8e e8 8e d0 <8b> 04 24 a3 f0 1f 00 00 a1 64 82 00 00 89 c4 89 c5 a1 f0 1f 00 00 89 04 24 31 c0 0f 01 0d
}}}

If I restart that nested VM, it should work as expected.

I didn't test 6.1.34 but this bug has been happening at least since 2020. 

I also opened an issue with gns3, but it is more likely to be a virtualbox issue:
https://github.com/GNS3/gns3-gui/issues/3330"	Luiz Angelo Daros de Luca
15689	Some time the guest crash	VirtualBox 5.1.2	2016-07-26T01:58:22Z	2016-09-28T21:14:07Z	2016-09-28T21:14:07Z	"Host: Windows 7 x64 professional SP1 with all other updates; 32 GB of RAM; processor Intel I7.

Guest: Windows 7 x64 Ultimate SP1.

Some time the guest crash with a messagebox (image attached).

I attach also VBox.log

"	bmn
19949	Some VirtualBox EFI Boot Menu entries do nothing when booting from ISO	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
15910	Sound delay	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
18879	Sound issues since 5.2.20 - Win98+Fifa98	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
16720	Sound randomly stops working until vm restarted (Fedora vm on Debian host running VirtualBox 5.1.18)	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
17615	spectre v2 mitigation: lfence not serializing. switching to generic retpoline	VirtualBox 5.2.8	2018-03-11T07:41:27Z	2018-03-11T07:41:27Z	2018-03-11T07:41:27Z	Error to install ubuntu-16.04.4-desktop-i386. See attach...	starvit
18829	spontaneously causes host to reboot	VirtualBox 6.0.10	2019-08-11T14:39:22Z	2019-10-08T21:45:16Z	2019-10-08T21:45:16Z	"This has been an issue I've encountered since VB 6.0.8 and has continued through to VB 6.0.11.  
My host is an iMac running macOS 10.14.6, but issue started when it was on 10.14.5.
I run several linux guest VMs.  
Sometimes when I'm updating one or two, my iMac spontaneously reboots.  Sometimes when I'm booting a guest VM my iMac spontaneously reboots.  Sometimes when I'm shutting down a guest VM my iMac spontaneously reboots.

Here's the latest crash log from my iMac:

Anonymous UUID:       F3719D15-7DCA-7343-A61F-B939BEF8FF8D

Sun Aug 11 09:25:35 2019

*** Panic Report ***
panic(cpu 6 caller 0xffffff80120daadd): Kernel trap at 0xffffffa426926f56, type 14=page fault, registers:
CR0: 0x0000000080010033, CR2: 0x00007f89184a6000, CR3: 0x00000005a79581a0, CR4: 0x00000000003626e0
RAX: 0x0000000000000000, RBX: 0x00007f88f8423d44, RCX: 0x0000000000000200, RDX: 0x00000000000004dd
RSP: 0xffffffa3e8581c60, RBP: 0xffffffa3e8581d00, RSI: 0x00007f88f83f0000, RDI: 0x00007f89184a6000
R8:  0x00007f88f8423d18, R9:  0x00007f88f8423d78, R10: 0x0000000000000000, R11: 0x00007f88f8423d42
R12: 0x00007f88f8423d40, R13: 0x0000000000023c00, R14: 0x00007f88f8423d38, R15: 0x00007f88f8423d18
RFL: 0x0000000000050246, RIP: 0xffffffa426926f56, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x00007f89184a6000, Error code: 0x0000000000000002, Fault CPU: 0x6, PL: 1, VF: 5

Backtrace (CPU 6), Frame : Return Address
0xffffffa3e8581730 : 0xffffff8011fad6ed 
0xffffffa3e8581780 : 0xffffff80120e9185 
0xffffffa3e85817c0 : 0xffffff80120da8ba 
0xffffffa3e8581830 : 0xffffff8011f5ab40 
0xffffffa3e8581850 : 0xffffff8011fad107 
0xffffffa3e8581970 : 0xffffff8011facf53 
0xffffffa3e85819e0 : 0xffffff80120daadd 
0xffffffa3e8581b50 : 0xffffff8011f5ab40 
0xffffffa3e8581b70 : 0xffffffa426926f56 
0xffffffa3e8581d00 : 0xffffffa426912735 
0xffffffa3e8581dc0 : 0xffffffa426859da9 
0xffffffa3e8581df0 : 0xffffffa42684ee55 
0xffffffa3e8581e30 : 0xffffffa426843f05 
0xffffffa3e8581fb0 : 0xffffffa42692e168 
0xffffffa3ea993860 : 0xffffffa42685b906 
0xffffffa3ea9939f0 : 0xffffff7f9578342f 
0xffffffa3ea993a00 : 0xffffff7f957961db 
0xffffffa3ea993ac0 : 0xffffff7f95795ac6 
0xffffffa3ea993b40 : 0xffffff801223a163 
0xffffffa3ea993b80 : 0xffffff801222e8df 
0xffffffa3ea993c00 : 0xffffff8012220544 
0xffffffa3ea993e00 : 0xffffff801249b68b 
0xffffffa3ea993e30 : 0xffffff80124f1839 
0xffffffa3ea993f40 : 0xffffff80125b92ad 
0xffffffa3ea993fa0 : 0xffffff8011f5b306 
      Kernel Extensions in backtrace:
         org.virtualbox.kext.VBoxDrv(6.0.11)[09081CCC-AD27-3F66-A7FB-68A23B0D18F7]@0xffffff7f95781000->0xffffff7f95870fff

BSD process name corresponding to current thread: VirtualBoxVM

Mac OS version:
18G87

Kernel version:
Darwin Kernel Version 18.7.0: Thu Jun 20 18:42:21 PDT 2019; root:xnu-4903.270.47~4/RELEASE_X86_64
Kernel UUID: 982F17B3-0252-37FB-9869-88B3B1C77335
Kernel slide:     0x0000000011c00000
Kernel text base: 0xffffff8011e00000
__HIB  text base: 0xffffff8011d00000
System model name: iMac18,2 (Mac-77F17D7DA9285301)

System uptime in nanoseconds: 844208412176885
last loaded kext at 750269373847264: com.apple.driver.AppleXsanScheme	3 (addr 0xffffff7f942a8000, size 32768)
last unloaded kext at 750399941670990: com.apple.driver.AppleXsanScheme	3 (addr 0xffffff7f942a8000, size 32768)
loaded kexts:
com.goldenfrog.VyprVPNMalwareFilter	1
com.goldenfrog.SplitTunnel	1
org.virtualbox.kext.VBoxNetAdp	6.0.11
org.virtualbox.kext.VBoxNetFlt	6.0.11
net.sf.tuntaposx.tun	1
org.virtualbox.kext.VBoxUSB	6.0.11
net.sf.tuntaposx.tap	1
org.virtualbox.kext.VBoxDrv	6.0.11
com.promise.driver.stex	6.2.9
com.apple.filesystems.afpfs	11.1
com.apple.nke.asp-tcp	8.0.2
com.apple.filesystems.msdosfs	1.10
com.apple.driver.AppleTopCaseHIDEventDriver	138.4
com.apple.driver.AppleUpstreamUserClient	3.6.5
com.apple.kext.AMDFramebuffer	2.1.1
com.apple.kext.AMDRadeonX4000	2.1.1
com.apple.driver.AudioAUUC	1.70
com.apple.fileutil	20.036.15
com.apple.driver.AppleGraphicsDevicePolicy	3.50.12
com.apple.filesystems.autofs	3.0
com.apple.AGDCPluginDisplayMetrics	3.50.12
com.apple.driver.AppleHV	1
com.apple.iokit.IOUserEthernet	1.0.1
com.apple.iokit.IOBluetoothSerialManager	6.0.14d3
com.apple.driver.AGPM	110.25.11
com.apple.driver.ApplePlatformEnabler	2.7.0d0
com.apple.driver.X86PlatformShim	1.0.0
com.apple.driver.pmtelemetry	1
com.apple.driver.AppleIntelKBLGraphics	12.1.0
com.apple.Dont_Steal_Mac_OS_X	7.0.0
com.apple.driver.AppleHDA	282.54
com.apple.kext.AMD9500Controller	2.1.1
com.apple.driver.AppleThunderboltIP	3.1.2
com.apple.driver.AppleMCCSControl	1.5.9
com.apple.iokit.AppleBCM5701Ethernet	10.3.3
com.apple.iokit.BroadcomBluetooth20703USBTransport	6.0.14d3
com.apple.driver.eficheck	1
com.apple.driver.AppleIntelPCHPMC	2.0.1
com.apple.driver.AppleGFXHDA	100.1.414
com.apple.driver.AppleOSXWatchdog	1
com.apple.driver.AirPort.BrcmNIC	1400.1.1
com.apple.driver.AppleIntelKBLGraphicsFramebuffer	12.1.0
com.apple.driver.AppleSMCLMU	212
com.apple.driver.AppleIntelSlowAdaptiveClocking	4.0.0
com.apple.driver.AppleUSBODD	456.260.3
com.apple.iokit.SCSITaskUserClient	408.250.3
com.apple.driver.AppleUSBStorageCoexistentDriver	456.260.3
com.apple.driver.AppleVirtIO	2.1.3
com.apple.filesystems.hfs.kext	407.200.4
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless	1.0.0d1
com.apple.BootCache	40
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib	1.0.0
com.apple.AppleSystemPolicy	1.0
com.apple.filesystems.apfs	945.275.7
com.apple.driver.AppleSDXC	1.7.6
com.apple.driver.AppleAHCIPort	329.260.5
com.apple.private.KextAudit	1.0
com.apple.driver.AppleACPIButtons	6.1
com.apple.driver.AppleRTC	2.0
com.apple.driver.AppleSMBIOS	2.1
com.apple.driver.AppleACPIEC	6.1
com.apple.driver.AppleAPIC	1.7
com.apple.nke.applicationfirewall	201
com.apple.security.TMSafetyNet	8
com.apple.security.SecureRemotePassword	1.0
com.apple.driver.AppleHIDKeyboard	208
com.apple.driver.AppleActuatorDriver	2450.1
com.apple.driver.AppleMultitouchDriver	2450.1
com.apple.driver.AppleInputDeviceSupport	2440.2
com.apple.driver.AppleHSBluetoothDriver	138.4
com.apple.driver.IOBluetoothHIDDriver	6.0.14d3
com.apple.kext.AMDRadeonX4200HWLibs	1.0
com.apple.kext.AMDRadeonX4000HWServices	2.1.1
com.apple.iokit.IOUSBUserClient	900.4.2
com.apple.driver.AppleGraphicsControl	3.50.12
com.apple.kext.triggers	1.0
com.apple.iokit.IOAVBFamily	760.6
com.apple.plugin.IOgPTPPlugin	740.2
com.apple.iokit.IOSkywalkFamily	1
com.apple.driver.AppleSSE	1.0
com.apple.driver.DspFuncLib	282.54
com.apple.kext.OSvKernDSPLib	528
com.apple.AppleGPUWrangler	3.50.12
com.apple.driver.X86PlatformPlugin	1.0.0
com.apple.driver.AppleSMBusController	1.0.18d1
com.apple.driver.AppleHDAController	282.54
com.apple.iokit.IOHDAFamily	282.54
com.apple.iokit.IOEthernetAVBController	1.1.0
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport	6.0.14d3
com.apple.iokit.IOBluetoothHostControllerUSBTransport	6.0.14d3
com.apple.iokit.IOBluetoothHostControllerTransport	6.0.14d3
com.apple.iokit.IOBluetoothFamily	6.0.14d3
com.apple.driver.IOPlatformPluginFamily	6.0.0d8
com.apple.iokit.IOAudioFamily	206.5
com.apple.vecLib.kext	1.2.0
com.apple.iokit.IONDRVSupport	530.51
com.apple.driver.AppleSMBusPCI	1.0.14d1
com.apple.iokit.IO80211Family	1200.12.2
com.apple.driver.mDNSOffloadUserClient	1.0.1b8
com.apple.driver.corecapture	1.0.4
com.apple.kext.AMDSupport	2.1.1
com.apple.AppleGraphicsDeviceControl	3.50.12
com.apple.iokit.IOAcceleratorFamily2	404.14
com.apple.iokit.IOSurface	255.6.1
com.apple.iokit.IOGraphicsFamily	530.66
com.apple.iokit.IOSlowAdaptiveClockingFamily	1.0.0
com.apple.iokit.IOSCSIMultimediaCommandsDevice	408.250.3
com.apple.iokit.IOBDStorageFamily	1.8
com.apple.iokit.IODVDStorageFamily	1.8
com.apple.iokit.IOCDStorageFamily	1.8
com.apple.driver.usb.AppleUSBHub	1.2
com.apple.driver.AppleUSBHostMergeProperties	1.2
com.apple.iokit.IOUSBMassStorageClass	4.0.4
com.apple.driver.usb.networking	5.0.0
com.apple.driver.usb.AppleUSBHostCompositeDevice	1.2
com.apple.iokit.IOSerialFamily	11
com.apple.filesystems.hfs.encodings.kext	1
com.apple.driver.AppleThunderboltDPInAdapter	5.6.9
com.apple.driver.AppleThunderboltDPOutAdapter	5.6.9
com.apple.driver.AppleThunderboltDPAdapterFamily	5.6.9
com.apple.driver.AppleThunderboltPCIUpAdapter	2.1.5
com.apple.driver.AppleThunderboltPCIDownAdapter	2.1.5
com.apple.driver.AppleHPM	3.4.1
com.apple.driver.AppleIntelLpssI2CController	3.0.60
com.apple.driver.AppleIntelLpssDmac	3.0.60
com.apple.driver.AppleIntelLpssI2C	3.0.60
com.apple.iokit.IOAHCIFamily	288
com.apple.iokit.IONVMeFamily	2.1.0
com.apple.driver.AppleThunderboltNHI	4.7.9
com.apple.iokit.IOThunderboltFamily	6.8.6
com.apple.iokit.IOSCSIParallelFamily	3.0.0
com.apple.driver.usb.AppleUSBXHCIPCI	1.2
com.apple.driver.usb.AppleUSBXHCI	1.2
com.apple.driver.usb.AppleUSBHostPacketFilter	1.0
com.apple.iokit.IOUSBFamily	900.4.2
com.apple.driver.AppleEFINVRAM	2.1
com.apple.driver.AppleEFIRuntime	2.1
com.apple.iokit.IOSMBusFamily	1.1
com.apple.iokit.IOHIDFamily	2.0.0
com.apple.security.quarantine	3
com.apple.security.sandbox	300.0
com.apple.kext.AppleMatch	1.0.0d1
com.apple.driver.DiskImages	493.0.0
com.apple.driver.AppleFDEKeyStore	28.30
com.apple.driver.AppleEffaceableStorage	1.0
com.apple.driver.AppleKeyStore	2
com.apple.driver.AppleUSBTDM	456.260.3
com.apple.driver.AppleMobileFileIntegrity	1.0.5
com.apple.iokit.IOUSBMassStorageDriver	145.200.2
com.apple.iokit.IOSCSIBlockCommandsDevice	408.250.3
com.apple.iokit.IOSCSIArchitectureModelFamily	408.250.3
com.apple.iokit.IOStorageFamily	2.1
com.apple.kext.CoreTrust	1
com.apple.driver.AppleCredentialManager	1.0
com.apple.driver.KernelRelayHost	1
com.apple.iokit.IOUSBHostFamily	1.2
com.apple.driver.usb.AppleUSBCommon	1.0
com.apple.driver.AppleBusPowerController	1.0
com.apple.driver.AppleSEPManager	1.0.1
com.apple.driver.IOSlaveProcessor	1
com.apple.iokit.IOTimeSyncFamily	740.2
com.apple.iokit.IONetworkingFamily	3.4
com.apple.iokit.IOReportFamily	47
com.apple.driver.AppleACPIPlatform	6.1
com.apple.driver.AppleSMC	3.1.9
com.apple.iokit.IOPCIFamily	2.9
com.apple.iokit.IOACPIFamily	1.4
com.apple.kec.pthread	1
com.apple.kec.Libm	1
com.apple.kec.corecrypto	1.0

EOF
Model: iMac18,2, BootROM 175.0.0.0.0, 4 processors, Intel Core i7, 3.6 GHz, 32 GB, SMC 2.40f0
Graphics: kHW_AMDRadeonPro560Item, Radeon Pro 560, spdisplays_pcie_device, 4 GB
Memory Module: BANK 0/DIMM0, 16 GB, DDR4, 2400 MHz, 0x859B, 0x435431364734534644383234412E433136464844
Memory Module: BANK 1/DIMM0, 16 GB, DDR4, 2400 MHz, 0x859B, 0x435431364734534644383234412E433136464844
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x16E), Broadcom BCM43xx 1.0 (7.77.61.2 AirPortDriverBrcmNIC-1305.8)
Bluetooth: Version 6.0.14d3, 3 services, 27 devices, 1 incoming serial ports
Network Service: Ethernet, Ethernet, en0
Network Service: Wi-Fi, AirPort, en1
PCI Card: pci105a,8760, RAID Controller, Thunderbolt@133,0,0
USB Device: USB 3.0 Bus
USB Device: Elements 25A2
USB Device: USB3.0 Hub
USB Device: Ultra Fit
USB Device: USB3.0 Hub
USB Device: Bluetooth USB Host Controller
USB Device: FaceTime HD Camera (Built-in)
USB Device: USB2.0 Hub
USB Device: HL-2040 series
USB Device: USB2.0 Hub
USB Device: EPSON Scanner
USB Device: Amazon Kindle
USB Device: E-USB Bridge for LS-120
USB Device: Apple USB SuperDrive
Thunderbolt Bus: iMac, Apple Inc., 41.1
Thunderbolt Device: Pegasus2-R, Promise Technology, Inc., 1, 19.2
"	Jim Kelley
12969	SSL authentication failed	VirtualBox 4.3.10	2014-04-22T11:33:45Z	2018-03-17T12:18:05Z	2018-03-17T12:18:05Z	"1. Launch new installed VirtualBox.
2. Check for updates - everything ОК.
3. In Windows Explorer find the image *.vbox from old HDD, which already in folder ""VirtualBox VMs"" and add it to the list in application (two clicks).
4. Check for updates - '''SSL authentication failed'''
5. Deleting recently added vritual machine from list.
6. Restart of application.
7. Checking update - everything ОК."	Rmplstltskn
15208	SSL certificate error on update check	VirtualBox 5.0.16	2016-03-05T19:10:31Z	2016-05-06T19:06:33Z	2016-05-06T19:06:33Z	"The update check process on VirtualBox on my MAC fails due to an error with the SSL certificate (Wrong SSL certificate). I already found ticket #13380 which sounds like my problem but none of the stated solutions works for me.

I ended up using Wireshark to debug the problem. The error message I got was ""Unknown CA"" when VirtualBox tried to check for an update. The server connected was 137.254.60.34, but I don't know which CA is used so I can't check my key chain for the respective root CA and its certificates.

"	Christoph Franke
20480	SSM: Giving up: Too many passes! (1048576)	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
19840	stable NS_ERROR_FAILURE on starting vm	VirtualBox 6.1.10	2020-08-27T19:43:08Z	2021-01-30T20:45:52Z	2021-01-30T20:45:52Z	"macos 10.13.6
VB throws stable error on starting of any VM (new or existing):

Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
MachineWrap
Interface:
IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}

The problem has began after installing the last macos update 10.13.6
Compleete removing and reinstalling VB does't help.


"	r5d1
18488	standard tty control sequences ignored in all VM's	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
17785	Start Kali Linux	VirtualBox 5.2.12	2018-05-23T14:11:23Z	2018-05-23T16:25:01Z	2018-05-23T16:25:01Z	I installed kali linux virtual machine and the error occurs during startup	LucaFaggiani
14173	Starting a Virtual Machine in Jenkins via batch script causes immediate crash and result in aborted state	VirtualBox 4.3.22	2015-06-03T23:29:33Z	2015-06-03T23:29:33Z	2015-06-03T23:29:33Z	"== Symptom ==
Whenever I try and start a VM from the Execute Windows Batch Command inside a freestyle Jenkins job, my VM immediately crashes.

== Details ==
Trying to execute a batch script inside a Jenkins job that starts a Virtual Machine via a batch script will immediately crash and go to the aborted state.

However, the same exact batch script can be ran by the host machine with the same variable and parameters perfectly fine manually. 

Also another workaround is to have the Virtual Box GUI interface open and running and the VM will seem to start.

Is this a permissions issue?

== Steps to be able to duplicate the bug ==
1. Have an instance of Jenkins running on the host machine.
2. Create a freestyle Job that will allow you to execute Windows batch scripts
3. Then create a batch script as such 

{{{
cd ""C:\Program Files\Oracle\VirtualBox""
VBoxManage.exe ""Name_OF_VM""
}}}

4. save and build the job
5. Observer that it starts up but then immediately crashes and goes to the abort state.

== Versions Affected ==

 * Windows 8.1 64-bit (Host and Guest)
 * Version 4.3.22

== Workaround ==
Please see Details for any workarounds at the moment.

"	MTaylor
20781	starting guest with --type headless fails on macOS Mojave host	VirtualBox 6.1.32	2022-01-20T06:16:31Z	2022-01-20T06:16:31Z	2022-01-20T06:16:31Z	"{{{
sh-3.2$ VBoxManage startvm bigapple-solaris10 --type headless
Waiting for VM ""bigapple-solaris10"" to power on...
VBoxManage: error: The VM session was aborted
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component SessionMachine, interface ISession
}}}

failed! But

{{{
sh-3.2$ VBoxManage startvm bigapple-solaris10 --type gui
Waiting for VM ""bigapple-solaris10"" to power on...
VM ""bigapple-solaris10"" has been successfully started.
}}}

succeeded. I've seen headless work on the same host with a Solaris 11 guest, but I'm not saying headless is ever reliable on there.

This was present in at least VirtualBox 6.1.30 and 6.1.32. It seems to be ok with a macOS Catalina host.
"	rlhamil
13920	Starting guest with multiple monitors on a different workspace causes virtual screens to disappear	VirtualBox 4.3.24	2015-03-04T16:24:10Z	2015-03-04T16:24:10Z	2015-03-04T16:24:10Z	"Starting or restarting guest with multiple monitors on Gnome workspace X while user is on a workspace not X causes guest virtual screens > 1 to disappear.

For example, if I start a guest on workspace 3 and that guest has two monitors but I switch to workspace 7 while the guest is booting, then the guest will only show virtual screen 1. Virtual screen 2 will completely disappear. This is true in windowed or fullscreen mode.

The workaround is to toggle to and from fullscreen, at which point the other virtual screens will reappear.

This is really only an issue when virtual machines receive updates and reboot."	Marty
16049	Starting the operating system	VirtualBox 5.1.6	2016-10-08T16:43:57Z	2016-10-08T18:52:48Z	2016-10-08T18:52:48Z	When i try to start ANY operating system, it says FATAL: No boot medium found! System Halted	DingerToaster220
18826	Starting VirtualBox on Windows 10 gives error	VirtualBox 6.0.10	2019-08-10T03:43:31Z	2019-08-17T05:06:20Z	2019-08-17T05:06:20Z	"When I start VB 6.0 on Windows 10 I get an error:

Failed to open a session for the virtual machine Ubuntu-19.04.

The virtual machine 'Ubuntu-19.04' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\dschul001c\VirtualBox VMs\Ubuntu-19.04\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {5047460a-265d-4538-b23e-ddba5fb84976}

Log file:


"	DeanInCO
15234	Starting virutalbox causes ctrl, shift, alt and super key to stay pressed	VirtualBox 5.0.16	2016-03-11T00:12:59Z	2016-03-11T03:12:30Z	2016-03-11T03:12:30Z	"When starting VirtualBox, before launching any guest whatsoever, Windows starts behaving very peculiar. First, the VirtualBox window does not appear on top of other windows, but instead behind all open windows. Then the keyboard mostly stops working (I can't write anything anywhere, use alt+tab etc), and clicking anywhere there is text (for example a browser) starts marking text and I can't use my scroll wheel for scrolling through web pages. My left mouse button still works, but most right click menus disappear as quickly as they appear. If I try to launch anything (or switch to a running program) in the taskbar this causes a UAC window to appear. This behaviour continues after closing virtualbox, and the only way I've discovered to get rid of it is a complete reboot.

Thinking this seemed like ctrl+shift were pressed I proceeded to log some keys. Using autohotkey I managed to check what happens when I start Virtualbox, and it seems LAlt, LWin, RControl, RShift and F3 all get pressed down (but not up). This also seems to repeat 8 times (with a ~30ms delay in between each iteration).

This problem started happening sporadically for me about a month ago or so, when running my virtual machine (although quite rarely). I could not seem to identify any particular behaviour triggering this at the time. Today I upgraded to VirtualBox 5.0.16 and now the issue somehow turned permanent, and happens every time I launch, and it really renders the host pretty much unusable until next restart.

Although it is very clear that this change happened during my upgrade to 5.0.16, now it happens for more versions. I tried unistalling and reinstalling several times, with the problem remaining, and even tried 5.0.14 and 4.3.36, with the same issue happening on every startup of Virtualbox. I have made sure to turn off any program (including autohotkey) runnning in the background both during installation and running the program.

I run on a 64-bit version of Windows 10, using a swedish keyboard layout. The problem starts happening before any VM launch, but if it's of interest I only have one Ubuntu guest that I use for development sometimes. I can still launch my VM with this behaviour, but I can't seem to be able to use the keyboard in it. I'll attach a VBox.log of that running, in case it is of interest."	rubicus
16253	Starting vm hides itself and all apps on 2 desktops	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
16714	starting with 5.1.20 the mini toolbar does not appear	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
16093	Startvm --type headless on detached guest -> show window	VirtualBox 5.1.8	2016-10-20T15:16:53Z	2023-01-03T09:31:28Z	2023-01-03T09:31:28Z	"After one starts a guest in Headless/Detachable mode and hides the window, this command can show the window:

{{{
Vboxmanage startvm ""vmname"" --type separate
}}}

At present there is no way to hide the guest's window again with the command line. I propose adding this ability to:

{{{
Vboxmanage startvm ""vmname"" --type headless
}}}

At present (version 5.1.6) this command run against a running guest started in Detachable mode throws an error. Under this enhancement the ""--type headless"" command would show the guest window if it has been hidden, and do nothing if the window is already showing.
"	scottgus1bug
17720	State/Powered off since ??	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
17691	Status Window for .OVA Appliance Import as .VDI shows .VMDK File Extension	VirtualBox 5.2.8	2018-04-17T06:21:48Z	2018-05-09T06:48:19Z	2018-05-09T06:48:19Z	When importing a .OVA appliance as a .VDI (.VDI file extension manually specified instead of .VMDK file extension in the Virtual Disk Image column), the file name in the status window shows as .VMDK instead of .VDI. The appliance correctly imports as a .VDI file so the bug is just the status window for the import. The attached screenshot shows the .VMDK file name despite the fact that a .VDI file was correctly generated as specified.	slikzzz
14624	STATUS_OBJECT_NAME_NOT_FOUND	VirtualBox 5.0.4	2015-09-22T12:15:12Z	2015-09-22T12:15:12Z	2015-09-22T12:15:12Z	"VirtualBox build: 5.0.5-102800-Win

Host: Windows 10
Guest: any VM (Windows XP, Ubuntu, CentOS)

Message error:
""NtCreateFile(\Device\VBoxDrvStub) failed: 0xc0000034 STATUS_OBJECT_NAME_NOT_FOUND (0 retries) (rc=-101)Make sure the kernel module has been loaded successfully.
where: supR3HardenedWinReSpawn
what:  3
VERR_OPEN_FAILED (-101) - File/Device open failed.
Driver is probably stuck stopping/starting. Try 'sc.exe query vboxdrv' to get more information about its state. Rebooting may actually help.""

Driver verifier disabled for :
vboxnetadp6.sys
vboxnetlwf.sys
vboxusbmon.sys

I can boot any VM with the driver verifier disabled for all drivers, not when only disabled for the oracle drivers above.

Wich  others drivers must get out  of Driver Verifier ?

"	Leonardo Lira
18217	Stealing ram	VirtualBox 6.0.0	2018-12-20T21:22:04Z	2018-12-24T08:32:17Z	2018-12-24T08:32:17Z	I don't know english very well.. Soo what i want to tell you guys is, i installed VirtualBox then i created windows 3.1 and i took 52 mb from my ram now i deleted it but i had 8.00 gb ram but after that i have 7.98 and i can't fix it anyway i tried to delete even the VirtualBox, i tried to system backup even that didn't worked. My ram is 7.98 now. Can you guys help me to fix?	CartmanXK
20108	Strange freeze in Linux host	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
16896	strange slow behavior in highly specific example	VirtualBox 5.1.22	2017-07-11T21:01:12Z	2017-07-26T19:20:14Z	2017-07-26T19:20:14Z	"We use a program Plexon Offline Sorter to manipulate acquired data. Specifically, on an iMac with an i5 (identifier 15,1), the most recent version of Virtualbox (5.1.22), the program is impossible to manipulate data because it's too slow. It's not clear at which version of Virtualbox the program became unusably slow. 5.0.36 works fine. In addition, and quite oddly, the current version works fine when tested on a Mac Pro using the same vdi file. I tried to maintain the same settings in the vbox.

To reproduce this requires a number of steps.

The program is available for download at http://www.plexon.com/sites/default/files/OFSx64v3w7Setup.exe. 

It is installed on a Windows 7 SP1 x64 guest machine with security updates current as of 6/17. The RAM is set to 3072 MB.

An example data file can be found at https://drive.google.com/file/d/0B9hWBqS8eh_QUkZlYVNla0c3ODQ/view?usp=sharing

We configure Plexon to open this file by selecting for its extension, .nev, in the open file dialog.

Once the file is open, click on the channel 1 marker to select that channel. The center window is where manipulation takes place. Hold down the control key and drag shapes around the data with the left mouse button held down. The mouse should draw in real-time and then fill in the shapes once the mouse is released.

As mentioned above, on this particular iMac, this worked with older versions of Virtualbox such as 5.0.36. In the current version, the mouse dragging barely registers because the program can't keep up. "	mauricev
16124	Sudden crash of VirtualBox.exe	VirtualBox 5.1.8	2016-10-27T13:21:29Z	2016-10-29T12:18:35Z	2016-10-29T12:18:35Z	"It happens from time to time that the running Virtual Machine suddenly crashes, without any particular action on the guest system other than using it normally.
For example, last time I was just about to enter a search term into the address bar of the Firefox Browser of my Ubuntu 14.04LTE guest system when it crashed. The moment I clicked on the address bar, VirtualBox crashed. This was only one example of many crashes.

Unfortunately, the appearing error message doesn't say much (see attached screenshot) and from the log file I couldn't find an answer either. It looks like it didn't log anything.
"	tacarrie
20583	Sudden failure	VirtualBox 6.1.26	2021-09-28T22:37:38Z	2021-09-28T22:37:38Z	2021-09-28T22:37:38Z	"Échec de l'ouverture de session pour la machine virtuelle XP Virtuel.

The VM session was closed before any attempt to power it on.

Code d'erreur : E_FAIL (0x80004005)
Composant : SessionMachine
Interface : ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}

"	osmond
12064	Suddenly no VM's will start - all give a RPC_S_SERVER_UNAVAILABLE error at 0%	VirtualBox 4.2.16	2013-09-03T14:11:55Z	2015-07-06T19:51:53Z	2015-07-06T19:51:53Z	"I was in the process of creating a new machine, and it wouldn't start (more in a bit) - I then tried to start up a few old, reliable machines, and got the same behavior.  The only change was that on startup a new version was mentioned; I installed it and saw this behavior.  After some web research I went back to version 4.2.12, and still see the same problem - but this may have to do with having installed the 4.2.16 version and then, perhaps, and incomplete removal.  I suppose technically this applies to both versions, as the problem shows up in both.

When I try to start any machine, I see a small popup, ""Starting virtual machine..."" and ""0%"" - that never changes.  My host OS is Windows 7 Ultimate; I have to kill the process for that machine manually.  When I do, I get a popup from Virtualbox; the detailed error message is:
Result Code: 
  RPC_S_SERVER_UNAVAILABLE 0x800706BA (0x800706BA)
  Component: 
  ProgressProxy
  Interface: 
  IProgress {c20238e4-3221-4d3f-8891-81ce92d9f913}
Web searching shows this, or something like it, was a problem years ago, but apparently fixed.  I found current ticket #10747 that looks similar.

The VM I was trying to start as the main test case is a Windows 98 machine, fairly vanilla.  I certainly haven't changed any of its attributes (e.g., hardware acceleration options) since it last ran.

I have 17 VM's, all of some level of importance; it would not be a minor effort to recreate them, even if that helped.  I tried to create a new Windows 2000 machine from scratch and had the same problem, that is the exact same hang and detailed error message.

I'm willing to invest some time to help fix it, if any testing I can do on this end might help."	Bryan Bentz
5628	"Suggestion: Add a ""minimise writes"" option to Windows Guest Additions"	VirtualBox 3.0.12	2009-12-01T16:50:30Z	2009-12-01T16:50:30Z	2009-12-01T16:50:30Z	"When using dynamically-expanding hard disk files, it's really useful to reduce the amount of writes performed by the guest OS. That reduces the size of the VDI file on the host and improves performance. Doing that is also useful for use when the host drive is a flash-based SSD.

For example, optimisations performed automatically by Windows XP and later move the location of data on the disk for faster access. That would most likely actually reduce performance, as well as waste disk space, when using a dynamically-expanding VDI in VirtualBox.

When installing the Windows guest additions, it would be very helpful to be presented with an option to adjust the various settings automatically. Performing the changes manually takes time and it's easy to forget one or more adjustments, especially when setting up several Windows VMs. And typically, installing the guest additions is the first thing done after installing the OS in a VM. Perhaps show checkboxes to either apply all settings, or allow the user to select which.

Some changes which reduce the amount of disk writes:

 - Disable the NTFS change journal. That can be done using the command fsutil.exe usn deletejournal C:. See http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/fsutil_usn.mspx

 - On Vista, disable SuperFetch.

 - Disable the Windows XP prefetcher.
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\PrefetchParameters]
""EnablePrefetcher""=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Dfrg\BootOptimizeFunction]
""Enable""=""N""
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\OptimalLayout]
""EnableAutoLayout""=dword:00000000

 - Using the Microsoft dskcache.exe tool, enable the ""power protected"" write cache option. Get that via http://support.microsoft.com/kb/Q811392
Use it like this: dskcache.exe +p c:
There is probably a registry key which can be changed, instead of having to use that Microsoft program.

 - Disable hibernation in the guest OS (optional, but there isn't much need for it and doing that prevents the user accidentally hibernating and causing a lot of data to be written to disk).

 - Disable System Restore (optional)

 - Disable 8.3 filename creation on NTFS partitions: fsutil.exe behavior set disable8dot3 1
In Windows 2000 and earlier you need to change a registry value:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem]
Change NtfsDisable8dot3NameCreation from 0 to 1.

- Disable updating file last-accessed timestamps: fsutil.exe behavior set disablelastaccess 1

- Disable indexing on all drives
"	Donuts
5582	Suggestion: allow disk image data to be aligned in VDI files, for optimal use with SSDs	VirtualBox 3.0.12	2009-11-28T10:55:19Z	2016-08-14T15:15:33Z	2016-08-14T15:15:33Z	"First, see this blog post which has some background information: http://thunk.org/tytso/blog/2009/02/20/aligning-filesystems-to-an-ssds-erase-block-size/

In summary, the smallest chunk of data that SSDs (solid-state flash drives) can write is larger than the 512-byte size that the SSD emulates/fakes for the host computer. The smallest chunk size might be 4KB, for example. If filesystem writes are not aligned to 4KB boundaries performance will suffer, especially for first-generation SSDs.

For example, if the host computer writes 4KB to (512-byte) sectors 63 to 70, the SSD will read the 4KB corresponding to sectors 56-63, update the sector 63 data and write it to flash. Similarly with the 4KB block corresponding to sectors 64-71. This read-modify-write causes more wear on the SSD.

Windows XP and earlier (and probably most non-Windows partitioning software) by default creates the first partition starting at (512-byte) sector 63. That is an ""odd"" alignment, not aligned on a 1KB boundary let alone 4KB or more.

What does this have to do with VirtualBox? My suggestion is that the VDI format be updated to allow the user to specify the alignment of the data. VirtualBox would add a few sectors worth of padding before the actual data. For use with SSDs, the user could set the alignment so sector 63 is on a 4KB boundary in the VDI file. The fixed-size VDI header appears to be $600 bytes long, so an extra $C00 bytes padding would be needed in that case.
 
Doing that might also be a minor performance win for conventional hard drives, if the host filesystem uses a 4KB cluster size. Of course the exact amount of padding to use needs to be user-configurable; for a Vista VDI it would be $A00 bytes.
"	Donuts
20380	Suggestions for development for a Mac Host	VirtualBox 6.1.22	2021-05-25T20:30:55Z	2021-05-26T16:20:20Z	2021-05-26T16:20:20Z	"1. It is not clear if Vbox is compatible with the new M1 chips. Please say if it is compatible and if not make it so.

2.I have a big investment in 32-bit mac software and would like to see a a way for a 64bit macOS host to run a MacOS with 32 Bit capability, smoothly with credible speed. This means at minimum that a finished Additions be available. 

3. I'd be willing to test #2 when I upgrade to a 64-bit only MacOS host. "	jvbeaupre
16036	supHardenedWinVerifyProcess failed with VERR_SUP_VP_REPLACE_VIRTUAL_MEMORY_FAILED	VirtualBox 5.1.6	2016-10-05T18:56:56Z	2016-10-06T12:09:17Z	2016-10-06T12:09:17Z	"Hi, I have downloaded VirtualBox Versión 5.1.6 r110634 (Qt5.5.1) and installed on Windows 10. 

So, I created a new VM, but at start moment, this message appears:

supHardenedWinVerifyProcess failed with VERR_SUP_VP_REPLACE_VIRTUAL_MEMORY_FAILED: (rc=-5673)

Have you any solution?

Thanks."	Facundo
13042	Support for Spice		2014-05-17T19:00:40Z	2014-05-17T19:00:40Z	2014-05-17T19:00:40Z	It would be great if VirtualBox could support [http://www.spice-space.org/ Spice] like QEMU does. It would be an alternative for the existing RDP support.	jschwart
19517	Support Sparkle application update framework on macOS	VirtualBox 6.1.6	2020-04-20T17:04:40Z	2020-04-20T17:04:40Z	2020-04-20T17:04:40Z	"I don't know how easy it would be to add Sparkle update framework (GitHub sparkle-project/Sparkle) to VirtualBox , but it would definitely be a welcome feature on macOS.

I know this has already been posted on #11211 and #3869 but I'd still like to propose it again as it seems a very interesting way to keep the program updated."	gio91ber
15185	Support to use mounted devices	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
17953	supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status -22900 (0xffffa68c)) on \Device\HarddiskVolume3\Windows\System32\shell32.dll	VirtualBox 5.2.18	2018-08-23T21:16:34Z	2018-08-24T14:12:37Z	2018-08-24T14:12:37Z	"VM boot fails with following error in the VBoxHardening.log

768.1808: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status -22900 (0xffffa68c)) on \Device\HarddiskVolume3\Windows\System32\shell32.dll

768.1808: Error (rc=0):

768.1808: supR3HardenedScreenImage/LdrLoadDll: cached rc=Unknown Status -22900 (0xffffa68c) fImage=1 fProtect=0x0 fAccess=0x0 cHits=4 \Device\HarddiskVolume3\Windows\System32\shell32.dll

768.1808: Fatal error:

768.1808: supR3HardenedDllNotificationCallback: supR3HardenedScreenImage failed on 'C:\Windows\system32\SHELL32.dll' / '\??\C:\Windows\system32\SHELL32.dll': 0xc0000190

1d50.15d4: supR3HardNtChildWaitFor[2]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 1651 ms, the end);

1b18.ac8: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 2014 ms, the end);
"	IvanP2017
17640	supR3HardenedWinReSpawn VERR_INVALID_NAME on specific driver paths	VirtualBox 5.2.8	2018-03-26T17:13:11Z	2018-04-19T18:09:38Z	2018-04-19T18:09:38Z	"When Hardening rejecting DLL with name like ""\Device\HarddiskVolume6\opt\adguolvds\glhp64.dll"", an error will always show as below and none of the VM can be started.


VirtualBox - Error In supR3HardenedWinReSpawn 
Error relaunching VirtualBox VM process: 5 Command line: '60eaff78-4bdd-042d-2e72-669728efd737-suplib-3rdchild --comment Windows10 --startvm 1e2c22cb-276b-43b0-9049-1e50628f9490 --no-startvm-errormsgbox ""--sup-hardening-log=C:\Users\latifrons\VirtualBox VMs\Windows10\LogsWBoxHardening.log's (rc=-104) 
Please try reinstalling VirtualBox. 
where: supR3HardenedWinReSpawn what: 5 '''VERR_INVALID_NAME''' (-104) -Invalid (malformed) file/path name. 


VBoxHardening.log:
{{{
4530.4674: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status -23021 (0xffffa613)) on \Device\HarddiskVolume6\opt\adguolvds\glhp64.dll [lacks WinVerifyTrust]
4530.4674: Error (rc=0):
4530.4674: supR3HardenedScreenImage/LdrLoadDll: cached rc=Unknown Status -23021 (0xffffa613) fImage=1 fProtect=0x0 fAccess=0x0 cHits=1024 \Device\HarddiskVolume6\opt\adguolvds\glhp64.dll
4530.4674: Error (rc=0):
4530.4674: supR3HardenedMonitor_LdrLoadDll: rejecting 'D:\opt\adguolvds\glhp64.dll' (D:\opt\adguolvds\glhp64.dll): rcNt=0xc0000190
4530.4674: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0xc0000190 'D:\opt\adguolvds\glhp64.dll'
4530.4674: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status -23021 (0xffffa613)) on \Device\HarddiskVolume6\opt\adguolvds\glhp64.dll [lacks WinVerifyTrust]
4530.4674: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status -23021 (0xffffa613)) on \Device\HarddiskVolume6\opt\adguolvds\glhp64.dll [lacks WinVerifyTrust]WinVerifyTrust]\Device\HarddiskVolume6\opt\adguolvds\glhp64.dll [lacks WinVerifyTrust]
4530.4674: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status -23021 (0xffffa613)) on \Device\HarddiskVolume6\opt\adguolvds\glhp64.dll [lacks WinVerifyTrust]
4788.4444: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 129076 ms, the end);
}}}


Seems that file path beginning with \Device is not supported?

How to get this dll:
Goto http://www.admon.cn and download the installer at the bottom of the page. This software is a low level ad removing tool which hooks many processes. D:\opt\adguolvds\glhp64.dll is its dll hook.

For those who comes here from Google:
Just remove this software and your VirtualBox will be fine."	latifrons
17422	Switching away from guest alters NumLock state of host	VirtualBox 5.2.4	2018-01-05T09:27:40Z	2018-01-05T18:55:21Z	2018-01-05T18:55:21Z	"Host: Windows 7 Enterprise, initial NumLock state at ""On""
Guest: KDE Neon, initial NumLock state at ""On""

Steps:
Ensure NumLock is on for the host.
Start the guest.
Observe that the host's NumLock remains on.
Enter the guest (e.g. click within the window).
Ensure NumLock remains on.
Return to the host (click the task bar or something that causes VBox to lose focus).

Expected outcome:
Host's NumLock remains on.

Actual outcome:
Host's NumLock turns off.

VBox version first observed: 5.1
Is 5.2.4 affected: Yes

After running a search, I wonder if these bugs are related in some way:
https://www.virtualbox.org/ticket/14614
https://www.virtualbox.org/ticket/14302

I am happy to provide any logs that might be needed."	Twisted Lucidity
21330	Switching between Guided and Expert mode clears populated fields	VirtualBox-7.0.4	2022-12-09T22:06:53Z	2022-12-10T18:13:56Z	2022-12-10T18:13:56Z	If you start a new VM, put in some basics, like name, ISO, etc., then switch modes, those inputs are cleared and you have to start over.	Justinh
15013	Symbolic Links	VirtualBox 5.0.12	2016-01-06T18:48:19Z	2016-01-10T01:09:00Z	2016-01-10T01:09:00Z	"VirtualBox 5.0.12 is erasing Symbolic Links after installation.

Never thought by simply installing VirtualBox something like this would happen. I don´t have a vbox.log because I just installed it successfully (VBox didn't crash)"	Henrique Madson
19698	System Boot	VirtualBox 6.1.10	2020-07-03T13:29:48Z	2020-07-03T13:29:48Z	2020-07-03T13:29:48Z	"I am new on VM 6.1.10
I have no idea how to handle the problem. Please see Logfile
"	LisaLa
20883	System doesn't boot up	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
17560	System Unstable	VirtualBox 5.2.6	2018-02-22T18:08:14Z	2018-02-28T06:44:13Z	2018-02-28T06:44:13Z	"I am running a Windows 10 Pro system with AMD 1700x processor, 64 Gig memory, 512SSD (OS drive), 4tb 7200 RPM drive, and just added 120SSD to see if another drive would help.  

At first I thought I might have a bad hard drive, replaced it and I continue to have issues which tells me it is software. 

I am unable to import any machines and when I export and test it on another machine it tells me the file is corrupt. When I build a machine from scratch it runs for a few hours then crashed to the point it won't boot. 

I have tried to uninstall and reinstall, along with reinstalling an older version with no success. 




"	SilentWraith
16364	SYSTEM_SERVICE_EXCEPTION BSD in Windows 10 x64 guest on Windows 7 x64 host	VirtualBox 5.1.12	2017-01-07T19:23:27Z	2017-01-07T19:23:27Z	2017-01-07T19:23:27Z	"I'm getting a SYSTEM_SERVICE_EXCEPTION blue screen in Windows Pro 10 x64 guest on Windows 7 x64 host after I've updated VB to ver. 5.1.8. Until then (in ver. 5.1.6) everything was working just fine. Back then I couldn't find a ticket or a topic about a similar issue and I thought will be fixed in the next changes but it didn't. I've updated VB to the latest 5.1.12 version and I'm having the same issue. I've tried to reinstall the Windows 10 guest but the process crashes at some point with the same blue screen error.

I have 2 other VB machines running without issues with the latest VB 5.1.12 (Windows ThinPC x86 and Windows 7 Ultimate x64 same as the host OS).

HOST: Notebook HP Pavilion DV7-1005TX (with Virtualization Support enabled in Bios), Windows 7 Ultimate x64, 8 Gb RAM, video Nvidia 9600M GT on 17 inch display, Bitdefender Antivirus Free Edition.

GUEST: Windows 10 Pro x64 (September 2015)

I'm not an IT professional or expert (just a mechanical engineer). I usually don't change anything that is working, unless it's a critical update available. I never tried to boost, overclock, tune-up or anything beyond my limits as a simple regular Windows PC user.

Thank you."	Mike Skywalker
17594	Tela azul	VirtualBox 5.2.8	2018-03-06T08:50:05Z	2018-03-06T11:45:43Z	2018-03-06T11:45:43Z	"Bom dia,

Após restaurar meu Windows 10 e reinstalar o VirtualBOX, 
a minha VM com Windows 2008 R2 fica dando tela azul.

Vocês tem alguma solução?

Obrigado,

Renato.
"	renatosp
21507	Test, please ignore	VirtualBox-7.0.6	2023-03-27T20:38:52Z	2023-03-28T16:07:15Z	2023-03-28T16:07:15Z	Checking if the notifications work properly.	Klaus Espenlaub
14079	The Application failed to initialize properly (0xc000007b)	VirtualBox 4.3.26	2015-04-27T07:34:28Z	2015-04-27T07:35:35Z	2015-04-27T07:35:35Z	"i recently updated the virtualbox from 4.3.18 to 4.3.26
and suddenly i cannot start the virtualbox, error show the application failed to initialized properly (0xc000007b)
how can i repair this, i already use the sfc /scannow on command prompt, uninstall the .net framework (2.0, 3.0, 3.5)
fyi my OS was windows xp SP3 and before the update my virtualbox was running smoothly.
"	Handi
21211	The command wmic memorychip returns no instances available on Windows server 2019 and Windows 10.	VirtualBox-7.0.2	2022-10-27T22:23:40Z	2022-10-27T22:23:40Z	2022-10-27T22:23:40Z	"The following windows command returns ""no instances available"" on Windows server 2019. The command returns the memory card information on Windows 2012 R2.

   wmic memorychip

Issue occurred on v6 and v7 of VirtualBox.
Issue occurred with VirtualBox running on both Linux and Windows hosts.
Issue also occurs on Windows 10 and Server 2022 VMs.
The command returns valid information on VMware VMs.

This breaks apps and scripts that use this to get memory information."	Nick3213
21420	The create button is not showing when creating a new Virtual Machine.	VirtualBox-7.0.6	2023-01-21T07:03:24Z	2023-01-26T09:05:30Z	2023-01-26T09:05:30Z	"[[Image(X:/downloads/Screenshots/ss1.png)]]I have tried re-installing and tried other versions of Virtual box too, But I am not able to create a Virtual Machine :(.

can someone please help me with this

I am running Virtual box on Windows 11"	tuglukbaba
19218	The driver detected an internal driver error on \Device\VBoxNetLwf.	VirtualBox 6.1.0	2020-01-12T09:57:19Z	2020-01-12T09:57:19Z	2020-01-12T09:57:19Z	"I have been having some BSOD issues and as part of investigating I found this in my event viewer. Please help with troubleshooting this problem
Event[30748]:
  Log Name: System
  Source: VBoxNetLwf
  Date: 2020-01-11T16:51:45.998
  Event ID: 12
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: MICHAEL-10
  Description: 
The driver detected an internal driver error on \Device\VBoxNetLwf."	microbe
20347	The error message appear when the virual machine shut down	VirtualBox 6.1.22	2021-05-08T06:14:02Z	2021-05-08T06:14:02Z	2021-05-08T06:14:02Z	"It always show error message ""The instruction at 0x00007FFE199F9B2C referenced memory. The memory could not be written."" I try to reinstall the application, but didn't work. I use portable usb to store most of vm and ISO files. I think it wouldn't a problem for the vm, but I am not sure what happened. I hope your teams can look at this problem, I would very appreciate if you could solve this problem I currently facing with. Thank you and have a great day"	jetAngel
18862	The Guest window will flicker with the package virtualbox-guest-additions	VirtualBox 6.0.10	2019-08-23T05:15:00Z	2019-08-23T05:43:46Z	2019-08-23T05:43:46Z	"Since version 28 of Fedora, the package comes with the distribution but with VirtualBox 6; when using Fedora 30 the package Guest Additions is having issues with the VBoxSVGA graphics card, as it start to wake up the guest window (it turns white and then goes back to normal), but if I use the VMSVGA controller it does not do it.  However the screen does not dinamically resizes, whereas with the VBoxSVGA it does it but then it fails.  I have had to remove the package and install the Guest Additions CD Image.

My OS: MacOS as Host. 
Guest: Fedora 30
Package: virtualbox-guest-additions"	luispautt
14752	The GUI and the command line vboxmanage report different status of VM	VirtualBox 5.0.8	2015-10-26T19:54:43Z	2015-11-09T14:11:26Z	2015-11-09T14:11:26Z	"I have RHEL 7 and VirtualBox-5.0-5.0.6_103037_el7-1.x86_64.rpm installed.

I found that the GUI and the cli(vboxmanage) are reporting the VM as ""powered off"" but as you can see from the attachment and the ""ps"" below it is indeed running. If I ""start"" the VM from either the GUI or the cli, while the VM is running, it will start another instance of the VM.  

{{{
#> ps -ef |grep VB
cgreen    3637  3619  2 Oct15 ?        05:16:13 /usr/lib/virtualbox/VBoxHeadless --comment dhcp02-mmr --startvm 6f889019-5659-4587-836e-1044e8f30703 --vrde config
}}}"	Hammerhead2006
13580	The Instruction at 0x... referenced memory at 0x... The memory could not be read	VirtualBox 4.3.18	2014-10-31T15:11:02Z	2016-12-12T17:22:47Z	2016-12-12T17:22:47Z	"As of version 4.3.16 and 4.3.18 I cannot start my Ubuntu guest on Windows 7 64 Bit.

Instead I receive the Error message:

""Die Anweisung in 0x... verweist auf Speicher 0x.... Der Vorgan read konnte nicht im Speicher durchgeführt werden.""

The English version according to Google should be:

""The Instruction at 0x... referenced memory at 0x... The memory could not be read.""
"	Frank Breitling
14363	The Instruction at 0x... referenced memory at 0x... The memory could not be read	VirtualBox 5.0.0	2015-08-01T10:57:34Z	2016-07-06T17:58:43Z	2016-07-06T17:58:43Z	"As of version 4.3.16 I cannot start my Ubuntu guest on Windows 7 64 Bit.

Instead I receive the Error message:

""Die Anweisung in 0x... verweist auf Speicher 0x.... Der Vorgan read konnte nicht im Speicher durchgeführt werden.""

The English version according to Google should be:

""The Instruction at 0x... referenced memory at 0x... The memory could not be read.""

This is just an update of Ticket #13580 because I cannot update its version number to 5.0.0."	Frank Breitling
16066	The instruction at 0x... referenced memory at 0x.... The memory could not be read.	VirtualBox 5.1.6	2016-10-13T08:53:31Z	2017-03-03T18:22:55Z	2017-03-03T18:22:55Z	"Hello, after some weeks ago my virtual machine start crashing many times per day with error:

'''The instruction at 0x00007FFCCB3949F9 referenced memory at 0x0000000001C9196C. The memory could not be read.'''

It happened in old and new version too. As host I use Windows 10 with '''Anniversary update'''. '''Probably problems come after this update'''. Guest operating system is Windows Server 2012 R2.

I tried to create mini dump via instructions on link https://www.virtualbox.org/wiki/Core_dump but it is not working in Windows 10 Anniversary update. I did it via Process Explorer.

Attached Dumps.zip file contains mini dumps from all processes in process tree of problematic VirtualBox.exe process:

{{{
- VBoxSVC.exe (VBoxSVC_Mini.dmp)
  - VirtualBox.exe (VirtualBox1_Mini.dmp)
    - VirtualBox.exe (VirtualBox2_Mini.dmp)
      - VirtualBox.exe (VirtualBox3_Mini.dmp - VM process)
}}}

Thanks for any suggestion/help."	Paul B.
19303	The instruction at 0x00007..referenced memory at 0x000..The memory could not be read.	VirtualBox 6.0.14	2020-02-12T15:48:53Z	2020-02-12T15:48:53Z	2020-02-12T15:48:53Z	"The instruction at 0x00007..referenced memory at 0x000..The memory could not be read. This statement is happening to me with Virtual Box 6.0.14 version.

And interrupts my work.  "	kingor
15795	The instruction at 0xd756278e referenced memory at 0x00000010. The memory could not be read.	VirtualBox 5.1.2	2016-08-15T10:54:37Z	2016-10-07T14:32:02Z	2016-10-07T14:32:02Z	"This happened twice now with the exact same message.

I don't recognise having done anything particular - if anything, I was browsing in Windows Explorer to the Downloads folder, from the Tree View.

Guest: Windows 7 SP1 x86.
Host: Windows 7 SP1 x64.
"	danf84
20667	The keyboard not working after the complete installation of Linux Mint 20.2.	VirtualBox 6.1.28	2021-11-14T12:42:18Z	2022-09-07T08:31:06Z	2022-09-07T08:31:06Z	The keyboard not working after the complete installation of Linux Mint 20.2. When the installation is completed & said press enter keys I pressed but not working please solve this problem this is a bug!	Cannon1000
15696	"The memory could not be ""read"""	VirtualBox 5.1.2	2016-07-27T08:44:06Z	2016-10-09T20:45:37Z	2016-10-09T20:45:37Z	"Hello,
With new 5.1.2 version, I've got this error:

{{{The instruction at ""0xcc47278e"" referenced memory at ""0x00000010"". The memory could not be ""read"".}}}

This occurs only with a specific software (Movicon 11.4) when I start his runtime. But the error is not report in guest side. This crash Guest and error is reported in host.
"	DenisFR
21081	The mouse crashes with VirtualBox 6.1 and Debian 11 with kernel 5.18	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
20236	The mouse is hide on text fill area on the second monitor.	VirtualBox 6.1.18	2021-03-05T14:52:53Z	2021-03-05T14:52:53Z	2021-03-05T14:52:53Z	"Stand:
Host: Windows 10 20H2 (laptop)
Guest: Windows 7 (x64)

The mouse stay invisible when placed on any text fill place (notepad.exe for example). This problem reproduces only on second monitor when mouse in integration mode.

If change mouse mode as hooked, the problem disappears."	Nitron
16339	"The State of the VM has changed from RUNNING to ' GURU_MEDITATION '. Error ""(VERR_PATM_IPE_TRAP_IN_PATCH_CODE)"""	VirtualBox 5.1.12	2016-12-30T11:50:25Z	2017-01-18T10:13:27Z	2017-01-18T10:13:27Z	"Gentlemen/Ladies,

Good morning.

I have a 32-bit Windows Vista Home Basic operating system (host) with Service Pack 2 installed, as well as all the updates for this system. The computer has Intel Pentium (R) Dual CPU T2370 and 1.73Ghz, with RAM of 2.00 GB. In this machine I created a virtual machine with the Windows 7 Home Premium 32-bit operating system (guest), with Service Pack 1 installed, as well as all the updates for this system. The computer has Intel Pentium (R) Dual CPU T2370 and 1.73Ghz, with RAM of 1.22 GB. The virtual machine was created using the ""!VirtualBox-5.1.2-108956-Win.exe"" version, since I have been updating !VirtualBox with each release version until I get the version ""!VirtualBox-5.1.12-112440-Win.exe"" . I noticed that the error messages were intencificated from the ante-penultimate version. The virtual machine was in ""Save State"" by the ""!VirtualBox-5.1.10-112026-Win.exe"" version, when I upgraded to the ""!VirtualBox-5.1.12-112440-Win.exe"" version. And several times this week, I entered the ""Machine / Close / Save State"" menu. Saving the state of the machine so I could continue my work from where I left off. In the last two days after starting the machine to continue my work in the state where I stopped, there were some errors, but I would close everything and then start the process again and the virtual machine would go up normally. Before Yesterday after this procedure, I worked normally and when restarting Virtual Machine, a screen appeared informing that the virtual machine suffered serious failures and suggested to me that I pressed the ""Ok"" button to leave the virtual machine and to contact the community !VirtualBox to get help with the problem. Referring to the ""VBox.log"" and ""VBox.png"" files in the ""C: \ Users \ Administrator \ !VirtualBox VMs \ Logs"" directory. Editing the file ""VBox.log"" I extract the following text below:
{{{
Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'
04: 57: 53.186726 Console: Machine state changed to 'GuruMeditation'
04: 57: 53.480547

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!
04: 57: 53.480551 !!
04: 57: 53.480552 !! VCPU0: Guru Meditation -1432 (VERR_PATM_IPE_TRAP_IN_PATCH_CODE)
}}}
I will forward you these and the other log files contained in this
folder.

Note: In the virtual machine I made the Microsoft SQL Server 2014 Service Pack 1 Express Downloads, all the Microsoft SQL Server 2014 SP1 Feature Packs files, and the IIS 10 Express download and installation, after that I rebooted the machine and then the error already described appeared. I wonder If this virtual machine is compromised because of these errors and if has how to recover it?"	MFS68
19162	The virtual machine 'Windows XP' has terminated unexpectedly during startup with exit code 1 (0x1)	VirtualBox 6.0.14	2019-12-15T14:17:02Z	2019-12-15T14:17:02Z	2019-12-15T14:17:02Z	"Не удалось открыть сессию для виртуальной машины Windows XP.
The virtual machine 'Windows XP' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'E:\Установка\Система\VirtualBox VMs\Windows XP\Logs\VBoxHardening.log'.
Код ошибки: 	E_FAIL (0x80004005)
Компонент: 	MachineWrap
Интерфейс: 	IMachine {5047460a-265d-4538-b23e-ddba5fb84976}
"	superneftegaz
19161	The virtual machine 'Windows XP' has terminated unexpectedly during startup with exit code 1 (0x1)	VirtualBox 6.0.14	2019-12-15T14:16:28Z	2019-12-15T14:16:28Z	2019-12-15T14:16:28Z	"Не удалось открыть сессию для виртуальной машины Windows XP.
The virtual machine 'Windows XP' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'E:\Установка\Система\VirtualBox VMs\Windows XP\Logs\VBoxHardening.log'.
Код ошибки: 	E_FAIL (0x80004005)
Компонент: 	MachineWrap
Интерфейс: 	IMachine {5047460a-265d-4538-b23e-ddba5fb84976}
"	superneftegaz
19569	The virtual machine 'XXX has terminated unexpectedly during startup with exit code 1		2020-05-07T07:52:54Z	2020-05-07T07:52:54Z	2020-05-07T07:52:54Z	"I upgraded to VirtualBox 6.1.7r137622 to escape the bug https://www.virtualbox.org/ticket/19496.
Now, all my VM doesn't start : I have the message bellow.
[[Image(https://i.postimg.cc/nVwkVjK4/supR3.png)]]
"	Vbox43532
18861	The virtual machine has terminated unexpectedly during startup	VirtualBox 6.0.10	2019-08-22T08:18:27Z	2019-08-22T09:13:58Z	2019-08-22T09:13:58Z	"Не удалось открыть сессию для виртуальной машины МЗНП_10.

The virtual machine 'МЗНП_10' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005).  More details may be available in 'C:\Users\bxz\VirtualBox VMs\МЗНП_10\Logs\VBoxHardening.log'.

Код ошибки: E_FAIL (0x80004005)
Компонент: MachineWrap
Интерфейс: IMachine {5047460a-265d-4538-b23e-ddba5fb84976}

"	bxz
18412	The Virtual Machine Won't Start Unless Run Headless Start	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
18351	The VM session was aborted	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
20751	Theme incompatiblity makes fonts invisible	VirtualBox 6.1.30	2021-12-28T05:48:20Z	2021-12-28T05:48:20Z	2021-12-28T05:48:20Z	"in MX Linux while using dark theme fonts are invisible...
VBox must have there own theme or fully take OS theme... 
as VBox only taking font  color from os theme, it makes invisble font if OS font color is white."	ZishanHackerThandarpara
19547	Three crashes of VirtualBoxVM in a row when trying to boot an Ubuntu 18.04 guest on a macOS 10.14.6 host	VirtualBox 6.1.6	2020-05-02T11:29:01Z	2020-05-02T11:29:01Z	2020-05-02T11:29:01Z	"Hi,

I've got three crashes of VirtualBoxVM in a row when trying to boot an Ubuntu 18.04 guest on a macOS 10.14.6 host. See attached crash logs and VBox.logs"	Lars Sonchocky-Helldorf
11514	Time sync: incorrect host time	VirtualBox 4.2.6	2013-02-22T13:49:40Z	2013-02-26T15:01:24Z	2013-02-26T15:01:24Z	"I have noticed that I do not get the time set correctly on my virtuals machines. They do sync but are always behind the host's time (which is set per ntp correctly) and funnily the times between several VMs running on the same host vary.

When I started to dig for the reason I started VBoxService with -vvv and saw that the Host time displayed there was not the actual time of the host (i.e. the windows machine on which the VMs are running).

I expected the time shown in the log as ""Host:"" would be the host time, e.g:
{{{
00:00:00.005246 timesync VBoxServiceTimeSyncWorker: Host:    2013-02-22T13:39:47.465000000Z
}}}
Unfortunately it differs from the hosts time. Even more suspicious: it differs differently on various VMs of the same host.
Could this be the reason why time sync does not work correctly?

Below more debug output.

{{{
root@orpdm-03:~#  /usr/sbin/VBoxService -f -vvv --enable-timesync --timesync-interval 1000
VBoxService 4.2.4 r81684 (verbosity: 3) linux.amd64 (Oct 26 2012 19:49:17) release log
00:00:00.002083 main     Log opened 2013-02-22T13:37:48.290070000Z
00:00:00.002159 main     OS Product: Linux
00:00:00.002180 main     OS Release: 3.2.0-37-generic
00:00:00.002199 main     OS Version: #58-Ubuntu SMP Thu Jan 24 15:28:10 UTC 2013
00:00:00.002388 main     OS Service Pack: #58-Ubuntu SMP Thu Jan 24 15:28:10 UTC 2013
00:00:00.002412 main     Executable: /opt/VBoxGuestAdditions-4.2.4/sbin/VBoxService
00:00:00.002415 main     Process ID: 31071
00:00:00.002418 main     Package type: LINUX_64BITS_GENERIC
00:00:00.002608 main     4.2.4 r81684 started. Verbose level = 3
00:00:00.002766 main     Initializing services ...
00:00:00.003517 main     Service client ID: 0x24
00:00:00.003767 main     VMInfo: Property Service Client ID: 0x25
00:00:00.003810 main     VBoxServiceBalloonInit
00:00:00.003847 main     MemBalloon: VbglR3MemBalloonRefresh failed with VERR_PERMISSION_DENIED
00:00:00.003942 main     Service 'memballoon' was disabled because of missing functionality
00:00:00.003965 main     VBoxServiceVMStatsInit
00:00:00.004058 main     VBoxStatsInit: New statistics interval 0 seconds
00:00:00.004102 main     VBoxServiceAutoMountInit
00:00:00.004353 main     VBoxServiceAutoMountInit: Service Client ID: 0x26
00:00:00.004393 main     Starting services ...
00:00:00.004414 main     Starting service     'control' ...
00:00:00.004706 control  Waiting for host msg ...
00:00:00.004831 main     Starting service     'timesync' ...
00:00:00.005097 main     Starting service     'vminfo' ...
00:00:00.005246 timesync VBoxServiceTimeSyncWorker: Host:    2013-02-22T13:39:47.465000000Z    (MinAdjust: 100 ms)
00:00:00.005341 vminfo   Writing guest property ""/VirtualBox/GuestInfo/OS/Product"" = ""Linux""
00:00:00.005413 timesync VBoxServiceTimeSyncWorker: Guest: - 2013-02-22T13:37:48.293063000Z => 119 171 937 000 ns drift
00:00:00.005509 timesync VBoxServiceTimeSyncAdjust: adjtime by 119 171 937 000 ns
}}}"	Markus
20826	tinycore 1.4 crashes VirtualBox	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
16471	TinyCore 7.2 boots on VB 5.0.32 but not on 5.1.14	VirtualBox 5.1.14	2017-02-09T10:41:13Z	2017-02-09T10:41:13Z	2017-02-09T10:41:13Z	"On a first machine: Win10 - VB 5.1.6, TinyCore-7.2.iso boots fine.

On a second machine: Win8 - VB 5.1.14, CorePlus-7.2.iso or TinyCore-7.2.iso fail with:

{{{
Code:  Bad EIP value.
EIP: [<fefa201c>]  SS:ESP 0068:c703bea4
---[ end trace 91cd7754bf702e09 ]---
Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b

}}}

Full console log attached. The VB log is no more available.

For trial, I uninstalled 5.1.14 and installed 5.0.32, and it worked."	Psam
18654	Todas as Máquinas Virtual Apresentando:  Código de Resultado:  E_FAIL (0x80004005)	VirtualBox 6.0.8	2019-05-17T18:52:45Z	2019-05-17T18:52:45Z	2019-05-17T18:52:45Z	"Todas as Máquinas Virtual Apresentando:  Código de Resultado:  E_FAIL (0x80004005).

'''Já tentei várias dicas tentar resolver este mesmo problema:'''

1. Desativar as USB´s das VMs;
2. Editar os arquivos com final *.vbox-prev, só para *.vbox;
3. Várias alterações do registro;
4 Atualizar para versão mais recente, para, ver são mais antiga também;

Nâo sei mais o que fazer.

Desde Já agraço.



------------
'''Inglês:'''

All Presenting Virtual Machines: Result Code: E_FAIL (0x80004005).

I have tried several tips to solve this same problem:

1. Disable the USB's of the VMs;
2. Edit the files with final * .vbox-prev, only for * .vbox;
3. Various registry changes;
4 Upgrade to newer version, for, see are older too;

I do not know what else to do.

From now on.[[Image()]]"	kleytonklaus
19716	Total freeze VM after resume PC from sleep with multi-display	VirtualBox 6.1.10	2020-07-11T12:03:15Z	2021-06-05T22:35:10Z	2021-06-05T22:35:10Z	"I have notebook with additional display connected. After resume PC from sleep i have grayscaled VM (not resumed). After any manipulation (manual click to resume or power off) i have total freeze VM, any keys and menus do not work, I can stop it only from windows process manager. I see this bug only if I use additional display, and not always. Host - Windows 10 Pro. Guest - Ubuntu 20.04.

Last log messages:
{{{
19:20:59.444238 Pausing VM execution, reason 'host suspend'
19:20:59.445534 Changing the VM state from 'RUNNING' to 'SUSPENDING'
19:20:59.455506 AIOMgr: Endpoint for file 'D:\VM\u20d\u20d.vdi' (flags 000c0781) created successfully
19:20:59.459381 AIOMgr: Async flushes not supported
19:20:59.460061 AIOMgr: Endpoint for file 'D:\VM\minerdev.vhd' (flags 000c0781) created successfully
19:21:00.435103 PDMR3Suspend: 988 580 745 ns run time
19:21:00.435115 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'
19:21:00.435665 Console: Machine state changed to 'Paused'
19:21:01.289288 Audio: Device configuration of driver 'DSoundAudio' has changed
35:23:09.706882 Resuming VM execution, reason 'host resume'
35:23:09.706982 Changing the VM state from 'SUSPENDED' to 'RESUMING'
35:23:09.708188 AIOMgr: Endpoint for file 'D:\VM\u20d\u20d.vdi' (flags 000c0723) created successfully
35:23:09.716841 AIOMgr: Endpoint for file 'D:\VM\minerdev.vhd' (flags 000c0723) created successfully
35:23:27.908281 GUI: UIMachineLogic: Host-screen count changed
35:23:28.567910 GUI: UIMachineLogic: Host-screen count changed
35:23:28.921678 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenResized: Screen 1 is formally resized to: 0x0 x 1920x1080
35:23:28.921702 GUI: UIMachineLogic: Host-screen geometry changed
35:23:28.971593 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenWorkAreaResized: Screen 1 work area is formally resized to: 0x0 x 1920x1080
35:23:28.971614 GUI: UIMachineLogic: Host-screen available-area changed
35:23:28.972004 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenResized: Screen 1 is formally resized to: -1920x1072 x 1920x1080
35:23:28.972039 GUI: UIMachineLogic: Host-screen geometry changed
35:23:28.972572 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenWorkAreaResized: Screen 1 work area is formally resized to: -1920x1072 x 1920x1080
35:23:28.972590 GUI: UIMachineLogic: Host-screen available-area changed
35:23:33.526775 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenWorkAreaResized: Screen 0 work area is formally resized to: 0x0 x 3840x2130
35:23:33.526800 GUI: UIMachineLogic: Host-screen available-area changed
35:23:33.527365 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenWorkAreaResized: Screen 1 work area is formally resized to: -1920x1072 x 1920x1050
35:23:33.527380 GUI: UIMachineLogic: Host-screen available-area changed
35:23:37.709638 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Invalid machine state Paused when checking if the guest entered the ACPI mode)}, preserve=false aResultDetail=0
35:23:41.938981 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Invalid machine state Paused when checking if the guest entered the ACPI mode)}, preserve=false aResultDetail=0
35:23:43.170192 GUI: Request for close-action to power VM off.
35:23:43.170209 GUI: Passing request to power VM off from machine-logic to UI session.
35:23:43.170453 GUI: Powering VM down on UI session power off request...
35:23:43.173091 Console: Machine state changed to 'Stopping'
35:23:43.174650 Console::powerDown(): A request to power off the VM has been issued (mMachineState=Stopping, InUninit=0)
}}}

{{{
19:20:59.444238 - I sleep (or hibernate) PC.
35:23:09.706882 - Resume PC - VM is grayscaled, after any manipulation - total freeze.
}}}"	PDZ
16153	Trac detected an internal error.	VirtualBox 5.1.8	2016-11-05T15:10:30Z	2016-11-05T15:10:30Z	2016-11-05T15:10:30Z	It happened when I was finishing to create my VirtualBox account.	Nelson Sampaio Jr
20292	Trackpad and mouse failure on using trackpad gestures in Gnome 40	VirtualBox 6.1.18	2021-04-08T10:51:50Z	2021-04-08T10:53:49Z	2021-04-08T10:53:49Z	Trackpad, Mouse and any sort of pointing devices fail to click on UI elements both in and outside Virtualbox, if the new trackpad gestures in Gnome40 are used when a guest is running. This issue does not pop up until the gestures are used and they only pop when used with Virtualbox running a guest.	mithun
13840	Trailing spaces in VM names are not handled consistently when grouping	VirtualBox 4.3.22	2015-02-16T01:56:59Z	2015-02-16T01:56:59Z	2015-02-16T01:56:59Z	"1. Create 3 new VMs ""test1"", ""test2"", ""test3 "". The VM names do not include the quotation marks, but test 3 has a trailing space in its name.
2. Select all three new VMs and create a new group for them.

The VMs all appear in the group in the Virtual Box Manager GUI, but when I look at the directories where the data is stored, I see that test1 and test2 have been moved into a subdirectory named ""new group"", but test3_ (directory name has underscore instead of space) has not been moved into the subdirectory - it remains in its original parent directory
"	m6477
20078	Trend FDE Post Login Fault	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
16795	TRIM on SSD not stable with Linux, Windows 10, FreeBSD	VirtualBox 5.1.22	2017-05-28T06:59:33Z	2021-08-24T16:07:04Z	2021-08-24T16:07:04Z	"Linux TRIM timeouts sometimes, FreeBSD same, Windows 10 doesn't boot at all

See below and attachments for details:[[BR]]

Linux Fedora 25 latest updates
1. Attach an image:
{{{
VBoxManage storageattach ""Fedora 25"" --storagectl ""SATA"" --port 0 --device 0 --nonrotational on --discard on --medium ""Fedora 25.vdi"" --type hdd
}}}
2. check trim enabled
{{{
hdparm -I /dev/sda | grep TRIM
           *    Data Set Management TRIM supported (limit unknown)
}}}
3. Enable it in the mount options and reboot afterwards
{{{
/dev/mapper/fedora-root /                       ext4    defaults,discard        1 1
}}}
4. run fstrim /
Hangs sometimes with timeouts


FreeBSD 11 latest updates
1. Attach disk as under Linnux
2. Check for TRIM support
{{{
camcontrol identify /dev/ada0 | grep -i trim
Data Set Management (DSM/TRIM) yes
}}}
3. Enable TRIM support on filesystem
{{{
mount | grep -i ufs
/dev/ada0p2 on / (ufs, local, journaled soft-updates)

# Boot into single user mode
tunefs -t enable /dev/ada0p2
tunefs: issue TRIM to the disk set

bash -c 'tunefs -p /dev/ada0p2 2>&1 | grep -i trim'
tunefs: trim: (-t)                                         enabled
}}}"	linuxguru
14149	Trivial macro bug in SDK in bindings/c/include/VBoxCAPI_v4_3.h	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
16143	Trouble attaching Intel HD 530 from linux host to win7 guest via PCI passthrough.	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
20259	Trouble shotting with connecting Print (forced reboot)	VirtualBox 6.1.18	2021-03-17T02:21:28Z	2021-03-17T02:21:28Z	2021-03-17T02:21:28Z	"# Environment
- Ubuntu 20.04
- VBOX 6.18
- Win 10
- Print driver Kyocera Taskcalfa 3253ciG

For printing, connect to print driver, (not reboot in select the print (with PDF))
then, VBOX is forced reboot"	kimyoungjin06
20258	Trouble shotting with connecting Print (forced reboot)	VirtualBox 6.1.18	2021-03-17T02:21:23Z	2021-03-17T02:21:23Z	2021-03-17T02:21:23Z	"# Environment
- Ubuntu 20.04
- VBOX 6.18
- Win 10
- Print driver Kyocera Taskcalfa 3253ciG

For printing, connect to print driver, (not reboot in select the print (with PDF))
then, VBOX is forced reboot"	kimyoungjin06
17595	Try to attach USB device to VM crashes the VM	VirtualBox 5.2.8	2018-03-06T14:51:24Z	2018-03-06T14:51:24Z	2018-03-06T14:51:24Z	"When enabling access to intel USB device (Vendor ID: 8087 Product ID: 07dc) the VM gets totally stucked and a reboot of the host is necessary. That is easily reprocible and happens each time.

The logs displays this error message:
ERROR [COM]: aRC=E_INVALIDARG (0x80070057) aIID={c19073dd-cc7b-431b-98b2-951fda8eab89} aComponent={HostUSBDeviceWrap} aText={USB device 'Intel Corp.' with UUID {674944f8-07e8-4224-b303-cb4161d16cb4} is busy (state 'CapturingForVM[Detach]'). Please try again later}, preserve=false aResultDetail=0

Tried with Lubuntu & Debian Guest OS. Of course guest Add-ons have been properly installed.

The bluetooth device works properly on the host.

"	jeanbox
19488	Trying to start a new instance of Ubuntu Server	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
20801	trying to start video recording of a new VM makes the entire application crash	VirtualBox 6.1.32	2022-01-31T17:02:47Z	2022-02-03T00:01:31Z	2022-02-03T00:01:31Z	"recording can be pre-set in the settings, so the machine will start recording as soon as it starts, which in this case crashes immediately.
or recording can be done manually by using the provided menu item, in which case it crashes in that instant.

=-=-=

Failed to get a console object from the direct session (RPC_S_SERVER_UNAVAILABLE 0x800706BA)

Result Code: VBOX_E_VM_ERROR (0x80BB0003)
Component: MachineWrap
Interface: IMachine {85632c68-b555bb-4316-a900-555eb28d3413df}

=-=-=

there are various combination I have checked, 
and non seems to matter for that.

but it is a (completely empty before any installation) Windows 10 based machine.
nothing unusual other than that it is set to UEFI, and 
and I have also set modifyvm (machine name) --nested-hw-virt on

"	Elad Karako
20686	Turkish translate	VirtualBox 6.1.30	2021-11-23T20:39:45Z	2021-11-26T22:29:44Z	2021-11-26T22:29:44Z	"[[Image(https://gcdn.pbrd.co/images/N8h1Icpv8HsI.png?o=1)]]

Internet is already connected. but it says ""connect"".... it should say ""disconnect"" this was also a bug in 6.1.28 version. i hoped u guys would fix this in 6.1.30. but u didn't."	Crypticus
21475	TwinCAT conflict	VirtualBox-7.0.6	2023-02-08T09:28:46Z	2023-02-08T09:28:46Z	2023-02-08T09:28:46Z	"VirtualBox  doesnt start guest OS if TwinCAT software is running.
TwinCAT is known to exclusively occupy the virtualization capability of the HOST processor, however Virtual Machine is set not to use Para-virtualization interface or nested pages. 
"	Arsham Atonyan
13468	Typo in FR and LT critical error titles	VirtualBox 4.3.16	2014-10-03T13:40:52Z	2014-10-03T13:40:52Z	2014-10-03T13:40:52Z	"There is a typo in VirtualBox 4.3.16 in the critical error titles in the FR and LT translation files.

I attached a patch fixing the typo. It is released under MIT license [https://www.virtualbox.org/wiki/MIT%20license].

It replaces: ""Virt'''i'''alBox - Erreur Critique"" by ""Virt'''u'''alBox - Erreur Critique"".
Same for the LT translation file.

Hope it helps somehow. If I did anything wrong, please let me know."	depierre
14538	Ubuntu 15.04 Desktop - vboxautostart does not work on boot (no output)	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
19040	ubuntu 16 guest aborted when restoring	VirtualBox 6.0.14	2019-10-23T01:03:01Z	2019-10-23T01:03:01Z	2019-10-23T01:03:01Z	"How to produce:
1. Open VirtualBox;
2. select the saved machine ""ubuntu-16"", and click ""start"" button;
3. New vm window comes up and then loading is processing;
4. when the progress bar almost finished the vm disappeared and aborted 

Host OS: Windows 7 SP1
I've been experienced this aborted situation since upgrade my virtualbox was upgraded to version 6, hope the information I've provided is helpful."	buffy
17707	Ubuntu 16.04 guest fails to start after upgrade to VirtualBox 5.2.10	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
16118	Ubuntu 16.04.1 crash of UI	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
19570	Ubuntu 18.04 guest crashes regularly	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
19379	Ubuntu 18.04 guest Vbox 6.1.4 crash on macOS 10.14.6 / MacBook Pro 15'' 2018 host	VirtualBox 6.1.4	2020-03-04T22:28:35Z	2020-03-04T22:28:35Z	2020-03-04T22:28:35Z	I've got a crash of a Vbox 6.1.4 while rebooting an Ubuntu 18.04 guest after a system update. See attached log files	Lars Sonchocky-Helldorf
19581	Ubuntu 20.04 guest VirtualBoxVM 6.1.6 crash on macOS 10.14.6 host	VirtualBox 6.1.6	2020-05-14T01:10:53Z	2020-05-14T01:10:53Z	2020-05-14T01:10:53Z	"I got a crash of an Ubuntu 20.04 guest VirtualBoxVM 6.1.6 running on macOS 10.14.6 host when trying to remove the guest additions image after a reboot after installing the 6.1.6 guest additions.

See attached log files"	Lars Sonchocky-Helldorf
20515	Ubuntu 20.04 host hangs if I copy/paste clipboard to Win10 guest	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
20999	Ubuntu 22.04 freezes - Windows 11	VirtualBox 6.1.32	2022-06-21T16:26:35Z	2022-07-09T23:40:51Z	2022-07-09T23:40:51Z	"I have windows 11, and I downloaded virtualbox 6.1 and installed Ubuntu 22 04. I followd this tutorial (https://www.youtube.com/watch?v=EQy9AUVuyF0&t=1s) step by step.

Ubuntu finished installation without any issues, but when I try to run it, it seems to get stuck. A snapshot is visible at (https://askubuntu.com/questions/1415045/ubuntu-22-04-seems-to-freeze-in-virtualbox-6-1-on-windows-11)

I have tried restarting my computer, but nothing seems to work. Can anyone help with the solution? Thanks in advance.

"	user17302
20917	Ubuntu 22.04 Server unattended install fails with error isolinux.cfg not found	VirtualBox 6.1.34	2022-04-26T14:13:24Z	2022-04-27T07:14:03Z	2022-04-27T07:14:03Z	"Trying to perform an unattended install of Ubuntu 22.04 Server AMD64 on an Intel CPU MacBook Pro 2011 and I am getting the error message below.

Setup:
    - macOS 12.3.1 on MacBook Pro 2018 (with Intel CPU)
    - VirtualBox 6.1.34
    - Ubuntu Live Server 20.04 AMD64: ubuntu-22.04-live-server-amd64.iso

Serving up user-data and meta-data with a python server on port 3003, based on a Ubuntu Server doc called autoinstall-quickstart.

Getting the following error message:

VBoxManage: info: Preparing unattended installation of Ubuntu_64 in machine 'axxxxx' (b7e7ff1a-1f41-4320-8e9f-c84a2cxxxxxx).[[br]]
VBoxManage: error: Failed to open '/isolinux/isolinux.cfg' on the ISO '/Users/sxxxxx/dev/vm/iso/ubuntu-22.04-live-server-amd64.iso' (VERR_PATH_NOT_FOUND)[[br]]
VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component UnattendedWrap, interface IUnattended, callee nsISupports[[br]]
VBoxManage: error: Context: ""ConstructMedia()"" at line 1859 of file VBoxManageMisc.cpp[[br]]

The files in the isolinux folder are no longer needed, because the server autoinstall is no longer based on the debian-installer (aka d-i), but rather it is based on Subiquity. Therefore, the VBoxManage unattended installer should not be looking for these. I'm afraid that this might require a VBoxManage upgrade or patch to support the new 'cloud-init' and 'curtin' with 'subiquity' based installer, unless someone can come up with a neat workaround or maybe a new unattended install template.

From browsing the source code under UnattendedTemplates/ubuntu_preseed.cfg that the template is entirely based on the debian-installer (ubiquity) and seems to have no knowledge of the new installer (subiquity).

See the source code under: /browser/vbox/trunk/src/VBox/Main/UnattendedTemplates/ubuntu_preseed.cfg on VirtualBox dot org.

Thanks in advance!"	stcp
21277	Ubuntu 22.10 Freeze/Crash	VirtualBox 6.1.40	2022-11-16T08:43:58Z	2023-01-04T12:43:43Z	2023-01-04T12:43:43Z	"I am currently using virtualbox version 6.1.40, and tried to install ubuntu 22.10 from https://ubuntu.com/download/desktop quite a few times, but every time there is a crash which i can reproduce it the easiest way like this:
1)Fire up virtualbox
2)Click ""Try Ubuntu""
3)Let it boot
4)Open Nautilus/File explorer
5)Right click on Music on left pane
6)The context menu starts glitching
7)VM hangs or crashes
8)Trying to close the VM using Close button causes it to stop responding

HOST: windows 10 21H2
GUEST: Ubuntu 22.10"	thehardgamer
20093	ubuntu doesnt starts	VirtualBox 6.1.16	2020-12-14T05:34:49Z	2020-12-14T05:34:49Z	2020-12-14T05:34:49Z	coming black screen after starting the ubuntu os	mrun
13844	Ubuntu guest on Mac OS X stops tracking battery status after full charge	VirtualBox 4.3.22	2015-02-16T16:49:36Z	2015-02-16T16:49:36Z	2015-02-16T16:49:36Z	"As the subject says, an Ubuntu guest tracks the battery status of the Mac host but stops if the host is charged to 100% of the battery. After that point, the Ubuntu guest reports a 100% charged battery regardless of the status of the host (plugged or unplugged).

This issue '''is not present''' with a Windows 7 guest, for example. The Windows client continues to track battery status without problems after a full charge.

Some details about my setup:[[BR]]

'''Guest'''[[BR]]
Ubuntu 14.04 LTS
4 Processors 2GB of memory

'''Host'''[[BR]]
MacBookPro Intel Core i7 4GB of Memory
Mac OS X 10.10.3 (14D72i), but the problem was observed with 10.10.2 public release version as well."	SototaSoft
20606	Ubuntu Guest randomly and frequently aborts.	VirtualBox 6.1.26	2021-10-15T13:01:17Z	2021-10-25T14:52:35Z	2021-10-25T14:52:35Z	"I have a guest virtual machine running Ubuntu Server 20.04.3 LTS
It aborts few times per week apparently at random.
For testing I created a new VM with the same SO and happens the same thing.
The other day this happened twice in one day.
Everything to up to date.
The Host OS is Windows 10 64bit pro.
You can see the rest in the logs."	Miguel Santos
17467	Ubuntu host does not start after 5.2.6 GUest Additions installed	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
18432	Ubuntu is failing to install	VirtualBox 6.0.4	2019-02-12T15:45:41Z	2019-02-12T15:45:41Z	2019-02-12T15:45:41Z	"When installing Ubuntu (32x) the installation will hit a large error sending the following text in the attached files. I can sometimes get to the installation page where Ubuntu asks where I am from, and then the installation fails with the same error message. I believe this issue may be unrelated, however, Ubuntu will freeze continually. I managed to reduce the freezing-frequency by changing the video source component to 128MB instead of 12MB. 

I supply roughly 4GBs of RAM to Ubuntu."	ChachiChamp
18650	Ubuntu Issues	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
15772	Ubuntu Mini ToolBar causes problems	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
19848	Ubuntu new installation not booting	VirtualBox 6.1.10	2020-08-31T20:18:24Z	2020-08-31T20:18:24Z	2020-08-31T20:18:24Z	Ubuntu 20.04.1 new installation not booting sometimes. Logs attached for two incidents.	009
11104	Ubuntu Quantal package: migrate from libpython2.7 to libpython3	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
18812	Ubuntu virtual machine fails to start	VirtualBox 6.0.10	2019-08-05T05:11:06Z	2019-08-05T05:11:06Z	2019-08-05T05:11:06Z		bobocc
20685	Ubuntu VM crash	VirtualBox 6.1.28	2021-11-23T09:05:01Z	2021-11-23T13:57:48Z	2021-11-23T13:57:48Z	My Ubuntu VM crashed for an unknown reason	mediawiz
18411	ubuntu-bionic-server does not work with 'VBoxManage unattended install' because of preseeding post-install errors	VirtualBox 6.0.4	2019-02-05T09:16:36Z	2019-09-20T06:35:25Z	2019-09-20T06:35:25Z	"[attached script: reproduce-bug.sh] # 111 lines[[BR]]
[attached patch: fix.patch] # 4 lines[[BR]]

It was reported here (and includes this fix):[[BR]]
https://forums.virtualbox.org/viewtopic.php?f=8&t=86798[[BR]]
I'm WildSAR[[BR]]

This is a single line change in .../UnattendedTemplates/ubuntu_preseed.cfg which is consistent with debian_preseed.cfg in the same directory.

The text of the error is:[[BR]]
---[[BR]]
!! Finish the installation[[BR]]

Failed to run preseeded command[[BR]]
Execution of preseeded command ""cp /cdrom/vboxpostinstall.sh[[BR]]
/target/root/vboxpostinstall.sh && chmod +x /target /root/vboxpostinstall.sh && /bin/bash[[BR]]
/root/vboxpostinstall.sh --preseed-late-command"" failed with exit code 127.[[BR]]
---[[BR]]

This is the patch which fixes ubuntu_preseed.cfg:

{{{
<  && /bin/bash /root/vboxpostinstall.sh --preseed-late-command
---
>  && /bin/sh /target/root/vboxpostinstall.sh --need-target-bash --preseed-late-command
}}}
There are *three* bugs in this single line of code:

/bin/bash should be /bin/sh[[BR]]
/root/vboxpostinstall.sh should be /target/root/vboxpostinstall.sh[[BR]]
--need-target-bash is missing[[BR]]

The above solution is the same as in .../UnattendedTemplates/debian_preseed.cfg (a peer file of ubuntu_preseed.cfg).

# to see the bug, do this[[BR]]
./reproduce-bug.sh[[BR]]

# to see my fix, do this[[BR]]
fix=1 ./reproduce-bug.sh[[BR]]"	Robert Nielsen
19104	Ubuntu18.04 NS_ERROR_FAILURE	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
19351	Ubunutu 18.04 kernel 5.4.0 suplibOsInit VERR_VM_DRIVER_NOT_INSTALLED ENOENT	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
17212	UEFI Hybrid	VirtualBox 5.1.30	2017-10-26T01:52:01Z	2017-10-26T01:52:01Z	2017-10-26T01:52:01Z	"'''UEFI Hybrid boot mode''',  enable UEFI in vbox bios... 

boot up , Linux or windows , some Linux can do EFI , however have to build first.  also if you care to migrate to U/EFI ,  from a legacy boot image.''''''

if efi isn't up on iso count down , or skip. then use can build ie Gentoo /Arch Linux  

anyhow this has been a wishlist feature for sometime... @ Work VMware 12 dose this .. 

however less i have 200 bucks... "	necrose99
14092	Ufter upgrade from 4.1.12 to 4.3.26 stops to run VM from PhysicalDrive	VirtualBox 4.3.26	2015-05-02T08:38:16Z	2015-05-02T08:38:16Z	2015-05-02T08:38:16Z	"subj

I had working system, ufter upgrade that stopping to work. No config is changed. Logs and configurations attached"	KES
20602	UI not working when Win10 User resize scale.	VirtualBox 6.1.26	2021-10-11T17:13:53Z	2021-10-11T17:13:53Z	2021-10-11T17:13:53Z	"Hi there,

When I need to import / export  or create New VM, need UI window to complete.

BUT it is not working when User set win10 windows scale in 150% (not 100%)

Workaround is set windows = 100%, then adjust to 150% after completed.

PLEASE HELP let it can support WIN10 WINDOWS SCALE. thx"	MorrisTW
20940	Unable to boot any VM (Ubuntu): kernel panic - not syncing attempted to kill the idle task	VirtualBox 6.1.32	2022-05-13T09:25:19Z	2022-06-08T08:42:34Z	2022-06-08T08:42:34Z	"Hello everyone.

I can't boot any of my VMs in Virtualbox. I have several VMs with different versions of Ubuntu, specifically Ubuntu 12 and Ubuntu 20. The same problem occurs in all of them when starting, getting on the screen: ""kernel panic - not syncing attempted to kill the idle task "". Attached log. I have tried to generate a new VM with Ubuntu 12, but I get the same problem. Thanks for your help."	pmartinezOracle
20517	Unable to connect 2TB seagate external USB drives to RHEL7 Guest	VirtualBox 6.1.26	2021-08-21T23:06:43Z	2021-08-21T23:06:43Z	2021-08-21T23:06:43Z	"Hi Team, 
I'm having issues connecting multiple different 1.7 TB seagate external USB drives to my RHEL7 guest vms. 

The error and a drive properties view from windows is attached for your review. 

Also, I can attach a 1TB external drive just fine, so I'm thinking that it's a driver compatibility issue with the larger drives that's the problem? 

Thanks!"	hanch0
15111	Unable to create a Virtual machine	VirtualBox 5.0.14	2016-02-04T10:57:21Z	2016-02-04T10:57:21Z	2016-02-04T10:57:21Z	"I am unable to create a for the first time a Virtual Machine .
After creating a Virtual machine call eWinXP  I click on the Machine and I get the following:
A small appeared  saying “You have the Auto capture”
A second message saying : “Creating process for for virtual machine eWinXP (GUI/QT)...(1/2)” and e progress bar with no Progress activity shown.(after 20 min) and no activity on the CD player.
He Mouse pointer shown the only activity.
I could not stop any running program . The only way I cuold regaing control of the computer is by using the “Task Manager”
The “Task Manager” show hat :
eWinXP (Power Off) and Oracle VM VitualBox  Running.
After closing both task the following ERROR message apeared:
Fail to open a session for virtual machine eWinXP
The VM sessuion was closed
Result Code : E_FAIL (0x8004005)
Component : SessionMachine
Interface: ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}
 a Copy of “VboxHardening” file attached  for your information.

I am using Windows 7 Enterprise on a HP Mini5102
 
Thank you for your help 
Ferruccio       






"	Ferruccio
19479	Unable to create Host-Only Network on Virtual Box	VirtualBox 6.1.4	2020-04-12T01:03:51Z	2020-04-12T01:03:51Z	2020-04-12T01:03:51Z	"Hi,

I know there are emany posts on this topic and i have gone through almost all of them but my issue still persists.

I am unable to create a host-only network on my Virtual Box. Many of the posts suggested to reinstall the Virtual Box and I did perform the following steps:
.
1) Uninstalled Virtual Box 6.1.4
2) Uninstalled norton AV on my machine (Windows 10 - 16GB RAM)
3) Disabled Windows Defender (Both AV & Forewall)
4) Rebooted the machine many a times.
5) Reinsalled Virtual Box (Run as administrator)

The problem still persists

'''Failed to create a host network interface.

Querying NetCfgInstanceId failed (0x00000002).

Result Code: E_FAIL (0x80004005)
Component: HostNetworkInterfaceWrap
Interface: IHostNetworkInterface {455f8c45-44a0-a470-ba20-27890b96dba9}
'''


I also tried to download to a lower version (5.2.34) but to no avail.


"	Sheezan
18455	Unable to create VM: Error in sup3RHardenedWinReSpawn	VirtualBox 5.2.26	2019-02-26T03:33:39Z	2019-02-26T07:02:47Z	2019-02-26T07:02:47Z	"I'm trying to run the VM that I created, unfortunately, there's a frequent error that I received. ""VirtualBox - Error in sup3RHardenedWinReSpawn"", hope to hear from y]ou soon. Thanks in advance,
"	LMPadolina
20133	Unable to delete or add extensions	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-
13633	Unable to delete snapshot - Hard disk 'Disk location' has more than one child hard disk (3)	VirtualBox 4.3.20	2014-11-21T20:45:49Z	2014-11-21T20:45:49Z	2014-11-21T20:45:49Z	"Hi,

I am trying to delete snapshot on VM but getting error message - Hard disk 'Disk location' has more than one child hard disk (3)

VM Version - 4.3.20 r96996
OS - Windows 7
OS on VM- windows server2003

Details about the error:
Failed to delete the snapshot Snapshot 1 of the virtual machine XXXXXXXXXXXXX.

Hard disk 'H:\infor.vdi' has more than one child hard disk (3).

Result Code: E_FAIL (0x80004005)
Component: SessionMachine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

Please take a look.
"	Mahi
13707	Unable to delete snapshot with 2 child snapshots	VirtualBox 4.3.20	2014-12-21T04:04:52Z	2014-12-21T04:07:09Z	2014-12-21T04:07:09Z	"When I tried to delete a snapshot I got this error:

Failed to delete the snapshot 1 of the virtual machine Windows XP chs.

Snapshot '1' of the machine 'Windows XP chs' cannot be deleted, because it has 2 child snapshots, which is more than the one snapshot allowed for deletion.

Result Code: VBOX_E_INVALID_OBJECT_STATE (0x80BB0007)
Component: SessionMachine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}
Callee: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}
"	Edward Yang
18726	Unable to export	VirtualBox 6.0.8	2019-06-25T08:12:22Z	2019-06-25T08:12:22Z	2019-06-25T08:12:22Z	"VirtualBox cannot export virtual machines on qcow disks. This affects Windows, MacOS and Linux versions. 



Failed to export appliance /Users/tianyl/Documents/Initial_gui.ova.

Could not create the exported medium 'Initial_gui-disk001.vmdk' (VERR_INVALID_PARAMETER).

Result Code: VBOX_E_FILE_ERROR (0x80BB0004)
Component: MediumWrap
Interface: IMedium {ad47ad09-787b-44ab-b343-a082a3f2dfb1}

"	tianyl
16468	Unable to fix the mislocated vboxguestadditions.iso file in Virtual Media Manager.	VirtualBox 5.1.14	2017-02-08T22:41:51Z	2017-02-08T22:41:51Z	2017-02-08T22:41:51Z	"Since I was uninstalling and reinstalling VirtualBox into their new (location/path/directorie)s in my updated 64-bit W7 HPE SP1 OS host desktop, VirtualBox's Virtual Media Manager kept the old vboxguestadditions.iso's location, but I was unable to remove/modify/remove it. I had to edit my VM's .vbox file to change/remove it. VirtualBox's Virtual Media Manager needs to let users modify this without manually editing .vbox file.

Thank you in advance. :)"	Ant
13556	Unable to get out of scaled mode in Mac OS X	VirtualBox 4.3.18	2014-10-26T19:06:20Z	2014-10-26T19:06:20Z	2014-10-26T19:06:20Z	"When running VirtualBox on Mac OS X, it is impossible to get out of scaled mode once entered. Neither pressing host-c nor using the menu allows one to return to the normal windowed mode. The only way to return to windowed mode is to shut down the virtual machine and restart it. I have attached a screenshot with the menu showing scaled mode is not enabled, yet the VM still displays in scaled mode.

My machine is a 13.3 inch MacBook Pro running OS X 10.9 Mavericks. My guest is a Windows 10 machine."	wwelchj
17180	Unable to get properly into full screen after VM resume	VirtualBox 5.1.28	2017-10-19T18:47:51Z	2017-11-30T22:15:48Z	2017-11-30T22:15:48Z	"I recently noticed the following issue, after a recent update (version 5.1.28 r117968 (Qt5.6.2) under macOS):
after I resume a VM, it is unable to go to full screen; it also show two windows, one of which shows the state before resume and is frozen.

Steps:
- Run a VM (I had this happen with several Linux Guests)
- Have it work in full screen
- Save the machine
- Resume it; then the first anomaly occurs: two windows show the status of the VM; the first one is not full screen, and reacts to inputs; the other is full screen and does not react to inputs

After that it is sometimes possible to put back to full screen the window that started as non full screen, but the frozen full screen view never goes away."	Merrilin
20837	Unable to get Virtualbox to run	VirtualBox 6.1.32	2022-02-22T04:50:44Z	2022-02-22T04:50:44Z	2022-02-22T04:50:44Z	"I am receiving an error when I try to activate virtualbox. I am running windows 10. I am not an advanced user so I was not able to understand possible answers to the issue. I will need step by step instructions on how to correct the problem. The error is 

Failed to open a session for the virtual machine Gamez.

Not in a hypervisor partition (HVP=0) (VERR_NEM_NOT_AVAILABLE).

AMD-V is disabled in the BIOS (or by the host OS) (VERR_SVM_DISABLED).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

"	Onlygamez
20671	Unable to import	VirtualBox 6.1.28	2021-11-17T02:00:11Z	2021-11-18T19:14:44Z	2021-11-18T19:14:44Z	Unable to import appliance to VirtualBox, had imported the same file before but now it shows error while in importing.	veer_14
18343	Unable to import OVA with error NS_ERROR_INVALID_ARG	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
18241	unable to install centos in VM. Facing error which says kernel panic	VirtualBox 6.0.0	2018-12-27T21:28:06Z	2018-12-28T02:23:58Z	2018-12-28T02:23:58Z	"installed virtual box
created Virtual machine.
tried to install centos 7 but i facing issue over here. getting an error which says kernel panic - not syncing : fatal exception
"	Vishal Pokala
18467	Unable To Install VM's	VirtualBox 6.0.4	2019-03-03T20:52:05Z	2019-03-05T09:38:02Z	2019-03-05T09:38:02Z	"I recently installed virtualbox version 6 upgrading from version 5 which worked fine. Since installing version 6 when I try to install a new vm for example Linux I set my boot cd and start to install the os. When I get to the screen to select language options etc i'm unable to click anything on the screen and  the cursor vanishes. Can you please advise if this is a known issue that there is a fix for.

Regards,

Andrew"	AJROBI71
8426	Unable to lock down VBOX COM using DCOMCNFG	VirtualBox 4.0.4	2011-02-24T19:59:23Z	2011-02-24T19:59:23Z	2011-02-24T19:59:23Z	"I need to install VirtualBox in an environment that permits only a special user (vboxuser) to control virtual box.[[BR]]
[[BR]]
The problem is that on Windows XP, locking down VirtualBox is not working (could be a windows bug), any user can launch with VBOXSVC and then have complete control over VirtualBox (if the set VBOX_USER_HOME properly). Windows 7 works fine (UAC on and off).[[BR]]
[[BR]]
[[BR]]
Here are the steps to lock down the COM service:[[BR]]
1- Install virtualbox under any admin user[[BR]]
2- Create a new user (vboxuser), make it an admin.[[BR]]
3- Login to vboxuser and start DCOMCNFG as admin[[BR]]
4- Select Component Services --> Computers --> My Computer --> DCOM Config[[BR]]
5- Locate VirtualBox then right click on open Properties[[BR]]
6- Select Security Tab[[BR]]
7- Change Launch/Activation to SYSTEM and vboxuser (local launch and activation)[[BR]]
8- Change Access to SELF,SYSTEM and vboxuser (local access)[[BR]]
9- Change Configuration to SYSTEM, vboxuser (full control)[[BR]]
10- Click OK and make sure that virtualbox.exe can start under vboxuser[[BR]]
11- logoff from vboxuser and then log back in to your user.[[BR]]
12- Start virtual box, and it starts! That is the problem.[[BR]]
[[BR]]
On Windows 7 you would get an error (Access Denied) and it would only work if I use runas /user:vboxuser virtualbox.exe.[[BR]]
[[BR]]
The problem happens only on Windows XP SP3 x86 (I haven't tested any x64 versions)[[BR]]
[[BR]]
I tested another COM service, and the permissions seem to work on Windows XP.[[BR]]
Please let me know if you have any questions[[BR]]
[[BR]]
I was able to reproduce this problem using VBOX 4.0.4 and VBOX-OSE 3.2.18 (self compiled/installed)"	rbhkamal
16744	Unable to open virtual machines after upgrading	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
20060	Unable to read complete notification	VirtualBox 6.1.16	2020-11-23T03:27:52Z	2020-11-23T03:27:52Z	2020-11-23T03:27:52Z	"I am running macOS 10.15.7 with VirtualBox Version 6.1.16 r140961 (Qt5.6.3). When I try to install CentOS-8.2.2004-x86_64-minimal I am seeing this incomplete message in the installation window. The message is ""The Virtual Machine reports that the guest OS does not"". I cannot read the rest. This appears to be a bug."	SyedA
19858	Unable to resize guest window with multi-monitor	VirtualBox 6.1.10	2020-09-04T10:39:56Z	2020-09-04T10:39:56Z	2020-09-04T10:39:56Z	"I have a multi monitor setup. There appears to be a bug when I resize the guest vm window if you have one monitor above the other. 

My monitors are like this 

        MON1 


        MON2           MON3 


If i resize the window on monitor 3 , no problem. 
If i resize the window on monitor 2, it will flicker, flash then instantly jump to monitor 1 and I will have to drag it back down to monitor 2 at which point it resizes itself again and I have to try to resize the window, going right back to the same problem. 

I have tried re-arranging the monitors so they are side by side, and this problem goes away. "	MattF
19390	Unable to restart VM after loading it from a saved state	VirtualBox 6.1.4	2020-03-09T19:51:22Z	2020-03-09T19:53:06Z	2020-03-09T19:53:06Z	"This is occurring on multiple systems. Windows 7 & 10 hosts, Windows 7,8,10 & Linux guests

'''Recreation:'''
1) Boot up a Windows 7, Windows 8, Windows 10, or Linux VM.
2) Once loaded to the desktop, close the VM with the ""Save machine state"" option.
3) Start up the VM from the saved state.
4) Restart the VM. (ex: Start -> Power -> Restart)

 '''Problem:''' Soon after the VM begins to reload, a Guru Meditation error results. 
Log files are attached. The last recorded error is VERR_PGM_HANDLER_NOT_FOUND.

Point of interest: For Windows guests, a Windows Vista style boot screen (black w/ just a bar) is shown, instead of the usual Windows logo. So ''something'' is set a couple of seconds prior to the failure that is causing it."	JMH1
12680	Unable to restore saved state after sleeping host	VirtualBox 4.3.6	2014-02-08T19:31:03Z	2020-02-28T11:06:37Z	2020-02-28T11:06:37Z	"Windows 7 x64 host, Windows 7 x64 guest, VirtualBox 4.3.6 r91406

If I save the state of the guest, and then put the host PC to sleep, when I wake it back up and attempt to resume the guest, I get:

Failed to open a session for the virtual machine Win7.
Failed to load unit 'pgm'
(Verr_SSM_INTEGRITY_REC_TERM_CRC).

The details are:

Result Code: E_FAIL (0x80004005)
Component: Console
Interface: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}

If I shut down the host and reboot, I can then resume the guest from it's saved state.

This is repeatable every time.  I saw another ticket from months (years?) ago with the same issue; it's how I knew to reboot in order to be able to resume the saved state."	Kiran Otter
5828	Unable to restore VM's saved state	VirtualBox 3.1.2	2009-12-23T15:30:06Z	2016-05-18T08:10:31Z	2016-05-18T08:10:31Z	"Information duplicated from this forum post: [http://forums.virtualbox.org/viewtopic.php?f=6&t=26019&p=116632#p116632].

With 3.1.2 and snapshots taken since installing 3.1.2, I get the following when restoring from a saved state:

    00:00:06.170 Changing the VM state from 'DESTROYING' to 'TERMINATED'.
    00:00:06.419 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={6375231a-c17c-464b-92cb-ae9e128d71c3} aComponent={Console} aText={Failed to load unit 'pgm' (VERR_SSM_INTEGRITY_REC_TERM_CRC)} aWarning=false, preserve=false
    00:00:06.420 Power up failed (vrc=VERR_SSM_INTEGRITY_REC_TERM_CRC, rc=E_FAIL (0X80004005))


When discarding saved state information, I'm able to start the machine without issue. Restored to earlier snapshot and am able to save and restore states without issue.

I'm seeing this on two different XP VMs. Have not tried to take a new snapshot of my Ubuntu VM yet, but did notice that when attempting to take a snapshot of one of my XP VMs that was powered off, the VBoxGUI crashed."	Wipeout
19867	Unable to run Windows 7 64 Bit OS Virtual Machine	VirtualBox 6.1.14	2020-09-07T10:15:34Z	2020-09-07T10:29:53Z	2020-09-07T10:29:53Z	Unable to run Windows 7 64 Bit OS Virtual Machine	rdua
12933	unable to save machine state in case of host reboot/shutdown event	VirtualBox 4.3.10	2014-04-10T17:04:46Z	2016-04-25T13:20:37Z	2016-04-25T13:20:37Z	"Host: Windows 7 SP1 x64[[br]]

When a shutdown/reboot event is issued on the host OS, the VirtualBox frontend presents, to the user, the Close VM window, allowing the user to save or properly shutdown the guest. But saving the VM state isn't possible, because the VirtualBox COM service (VBoxSVC) exits immediately. The user is only able to shut down or power off the VM. When choosing to save the state, the user encounters this error:[[br]]

{{{
Failed to save the state of the virtual machine .

Callee RC: RPC_S_SERVER_UNAVAILABLE 0x800706BA (0x800706BA)
}}}"	Mihai Hanor
18231	unable to see mouse pointer in guest	VirtualBox 6.0.0	2018-12-24T21:56:53Z	2018-12-24T21:56:53Z	2018-12-24T21:56:53Z		kapstone
21287	Unable to Show Windows Side by Side	VirtualBox-7.0.4	2022-11-19T08:33:54Z	2022-11-19T08:33:54Z	2022-11-19T08:33:54Z	I have multiple VMs opened and I want to show them side by side, so in the task bar I clicked on Show Windows Side by Side option but it is not working, it used to work for the previous version but after I updated it in the new version it doesn't work anymore!	stevenrolando
20052	Unable to start any VM since BigSur installation	VirtualBox 6.1.16	2020-11-19T22:21:39Z	2020-12-16T23:06:31Z	2020-12-16T23:06:31Z	"Hi,

I has several VM running fine in virtualbox on my Mac.

Since, I've upgrade my os to Macos Big sur, I'm not able to run any of my VM. It fails with the error:
{{{
Échec de l'ouverture de session pour la machine virtuelle Samsung Galaxy S6.

The virtual machine 'Samsung Galaxy S6' has terminated unexpectedly during startup with exit code 1 (0x1).

Code d'erreur : NS_ERROR_FAILURE (0x80004005)
Composant : MachineWrap
Interface : IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}
}}}

I did try to change virtualbox network configuration, and also change network interface of my VM, with no success.

Even the creation of new VM fails with same error at first start up.

In logs, I can find only:
{{{
00:19:40.821687 nspr-3   Launched VM: 1750348368 pid: 856 (0x358) frontend: GUI/Qt name: Debian2
00:19:41.322953 Watcher  ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={85632c68-b5bb-4316-a900-5eb28d3413df} aComponent={MachineWrap} aText={The virtual machine 'Debian2' has terminated unexpectedly during startup with exit code 1 
(0x1)}, preserve=false aResultDetail=0
}}}

What's wrong?"	Raoul555
17376	unable to start vm: VERR_SUP_VP_EXE_VS_PROC_NAME_MISMATCH		2017-12-18T14:07:49Z	2019-03-28T09:33:28Z	2019-03-28T09:33:28Z	"I'm getting the following error again when trying to restore a saved machine. Same machine worked fine a couple of days ago.
No update or reinstall of VirtualBox in the meantime.

{{{
supHardenedWinVerifyProcess failed with
VERR_SUP_VP_EXE_VS_PROC_NAME_MISMATCH: (rc=-5618)

Please try reinstalling VirtualBox.

where: supR3HardNtChildPurify what: 5
VERR_SUP_VP_EXE_VS_PROC_NAME_MISMATCH: (rc=-5618)- Process Verification 
Failure: Executable file name and process image name does not match up.
}}}

After reinstalling VirtualBox by choosing ""repair"" when running the executable, and rebooting Windows, I was able to start the vm guest just fine from the saved state.

VirtualBox: 5.2.3r119650

Host: Windows 10 64bits"	rosch
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	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
14120	unable to startvm with high priority on windows	VirtualBox 4.3.26	2015-05-15T14:39:58Z	2015-05-15T14:39:58Z	2015-05-15T14:39:58Z	"Reference forum: https://forums.virtualbox.org/viewtopic.php?f=6&t=67715#p320669

I recently upgraded to 4.3.26 and now I'm unable to run my batch file that launched my VM with high priority because it seems that there are now 3 different processes that end up getting run. The parent process has the high priority but the actual VM does not which makes it slow. Here is the batch file, not much to it. Anyone found a workaround for this, or should I report it as a bug? 

Batch File contents:
start ""name"" /high ""C:\Program Files\Oracle\VirtualBox\VirtualBox.exe"" --comment name --startvm 1941c965-3dc5-4326-85ae-4400ea58b90d

Things that I've tried without any success:
- running the batch file as admin
- setting VirtualBox.exe to always run as Admin"	p1234
15633	Unable to uninstall VirtualBox	VirtualBox 5.0.22	2016-07-18T06:31:49Z	2017-10-31T06:59:46Z	2017-10-31T06:59:46Z	"See screenshot.

""The feature you are trying to use is on a network resource that is unavailable""."	Umanamente
17335	unattended install uses wrong path for UnattendedTemplates dir	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
17627	Unconditional upscaling of display on HIDPI systems	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
17553	Une erreur critique est survenue pendant l'execution de la machine virtuelle		2018-02-19T17:28:55Z	2020-10-11T12:57:45Z	2020-10-11T12:57:45Z	"Hi!
after an update of the version ubuntu 17.04 and restart my virtual machine is not accessible anymore and a window appear containing this words "" Une erreur critique est survenue pendant l'execution de la machine virtuelle et cette derniere a été suspendue"" .
thanks"	mohamed degaci
19212	Unexpected exception: std::bad_alloc [St9bad_alloc]	VirtualBox 6.1.0	2020-01-09T03:10:45Z	2020-01-20T12:14:08Z	2020-01-20T12:14:08Z	"Reduced RAM from 5000 MB to 2500 MB and pressed OK. 

VirtualBox displays ""Unexpected exception: std::bad_alloc [St9bad_alloc]""

Details:

Unexpected exception: std::bad_alloc [St9bad_alloc]
/Users/vbox/tinderbox/mac-rel/src/VBox/Main/src-server/MachineImpl.cpp[9943] (nsresult Machine::i_saveSettings(bool *, int)).

Result Code: 
NS_ERROR_FAILURE (0x80004005)
Component: 
SessionMachine
Interface: 
IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}
"	crvi
16634	Unexpected opening of a subwindow causes annoyance	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
16144	"Unhelpful feedback ""DrvVD: Configuration error: keys incorrect at level 0"""	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
20072	uninstall option missing from help menu	VirtualBox 6.1.16	2020-11-29T07:01:42Z	2020-11-29T07:01:59Z	2020-11-29T07:01:59Z	"When I run:


{{{
    sudo ./VirtualBox-6.1.16-140961-Linux_amd64.run --help
    Makeself version 2.1.5
     1) Getting help or info about ./VirtualBox-6.1.16-140961-Linux_amd64.run :
      ./VirtualBox-6.1.16-140961-Linux_amd64.run --help   Print this message
      ./VirtualBox-6.1.16-140961-Linux_amd64.run --info   Print embedded info : title, default target directory, embedded script ...
      ./VirtualBox-6.1.16-140961-Linux_amd64.run --lsm    Print embedded lsm entry (or no LSM)
      ./VirtualBox-6.1.16-140961-Linux_amd64.run --list   Print the list of files in the archive
      ./VirtualBox-6.1.16-140961-Linux_amd64.run --check  Checks integrity of the archive
     
     2) Running ./VirtualBox-6.1.16-140961-Linux_amd64.run :
      ./VirtualBox-6.1.16-140961-Linux_amd64.run [options] [--] [additional arguments to embedded script]
      with following options (in that order)
      --confirm             Ask before running embedded script
      --noexec              Do not run embedded script
      --keep                Do not erase target directory after running
                            the embedded script
      --nox11               Do not spawn an xterm
      --nochown             Do not give the extracted files to the current user
      --target NewDirectory Extract in NewDirectory
      --tar arg1 [arg2 ...] Access the contents of the archive through the tar command
      --                    Following arguments will be passed to the embedded script
}}}

The '''uninstall''' option is clearly missing, which I think should be present. How can this be?
"	DeGarden
18155	Unknown fatal error!	VirtualBox 5.2.22	2018-11-28T15:28:51Z	2018-11-30T01:55:31Z	2018-11-30T01:55:31Z	Virtual box for Windows 7 x64.	AlnXpr
18527	Updated MacOS Mojave to 10.14.4 - VirtualBox Crashes	VirtualBox 5.2.26	2019-03-27T14:27:08Z	2019-03-28T19:54:50Z	2019-03-28T19:54:50Z	"Using VirtualBox 5.2.26 and have extension pack installed.  There was a MacOS for Mojave this past week (10.14.4) and after installing VirtualBox opens but once I login it shows desktop for a brief second and goes back to the login screen.   The VirtualBox is running CentOS 7.

I am attaching the log file which contains a CFGM dump, CPUID dumps.   I don't see anything obvious in the log file "	dduck721
19017	Updated to 5.2.34 and now VM constantly crashes	VirtualBox 5.2.34	2019-10-16T03:26:26Z	2019-10-16T03:29:55Z	2019-10-16T03:29:55Z	"See attached log.

This is running Win9x DOS and using dos network support.
"	dfatvb
14859	updeted vbox and guestadd. to version 5, randomly stop working	VirtualBox 5.0.10	2015-11-23T13:45:37Z	2015-12-05T06:25:34Z	2015-12-05T06:25:34Z	"used firefox, randomly guest stop working, total blocking
note, I also work at host at same time and go to guest short times.
"	Mjau
15592	"Upgrade from 5.0.8 to 5.0.24 causes ""FATAL: no bootable disk found"""	VirtualBox 5.0.24	2016-07-10T22:39:59Z	2016-07-10T22:39:59Z	2016-07-10T22:39:59Z	"In a Windows 7 64bit host, running a guest Windows Standard 2012 virtual machine would not boot with ""no bootable disk found"" error.  Reverted back to 5.0.16, and started working again.  Noticed Storage changed on 5.0.24 from SATA to IDE, suspect this is the cause of the ""no bootable disk found"" error, but did not confirm."	Lula
20814	Upgrade from 6.1.3 to 6.1.32 causes VT-x detection to fail	VirtualBox 6.1.32	2022-02-07T15:03:39Z	2022-02-07T15:03:39Z	2022-02-07T15:03:39Z	"I have virtualbox running on windows 10

I have a VM that requires nested virtualization.

It ran fine under 6.1.30 but since upgrading to 6.1.32 it fails saying:

not in hypervisor partition
VT-x is disabled in the BIOS for all CPU modes

Downgrade to 6.1.30 cured the problem
I have replicated the symptoms on two different devices:

Intel Core i3-2350M 2.3GHz running Windows 10 Pro 21H2
Intel core i3-2370M 2.4 GHz Running Windows 10 Pro 21H2

"	Pcrossley
15761	Upgrade to 5.1.2 destroyed all VM	VirtualBox 5.1.2	2016-08-08T07:56:30Z	2016-08-17T08:44:02Z	2016-08-17T08:44:02Z	"After upgrading from version 5.0.24, 5.0.26 and 5.1.0 directly to 5.1.2 destroyed all my virtual machines on three independent Macintosh systems after the first start up, using version 5.1.2 of VirtualBox.

As I was able to see, what's going on, an error with the chipset was displayed with an error message, that the virtual machine was damaged or Could behave like having technical trouble, while there is an issue within the audio codec/ chipset/ driver.

Microsoft Windows VM (7 Ultimate and 10 Pro, both 64-bit) crashed at first and displayed the sad smily. Then the Ubuntu Server, Linux Mint and a FreeNAS crashed after additional reboot. One Windows VM restarted again and again - while the guest addition image was mounted. After ejecting it, a blue screen appeared at the next boot loop.

I've tried to downgrade the version or use the virtual machines on another computer, where no update has been done, but the machines was destroyed, we weren't able to recover it. For sure we've used snapshots before upgrading, but a roll back to the last working snapshot was not successful.

Fortunately, we keep all important data outside the virtual machines, so we only lost the virtual systems, but that was very annoying.

And it doesn't matter, what you change in the virtual machines configuration, the same error messages appears, only with your changed configuration of chipset and audio codec.

We've tried to identify some logs, but what we found is not useful.

May be you can take a look of your structure and another one knows this issue too and can give further informations, why and when his happens exactly.

We've also tried a fresh install of MacOS X (10.10.5 and 10.11.6) with a newly downloaded 5.1.2 of VirtualBox and by creating a new VM, the issue persists even out of the box.

The last working versions of VirtualBox are 5.0.26 and 5.1.0 - so the issue must be directly located in the code of version 5.1.2

May be, you can find the bug and fix it, because we wanna upgrade securely to the next version."	TH3rb5t
19662	Upgrade to 6.1.10 breaks all VMs on Windows 10	VirtualBox 6.1.10	2020-06-12T09:46:24Z	2020-11-16T08:53:58Z	2020-11-16T08:53:58Z	"Just upgraded from to 6.1.10 on Windows 10 and am not unable to start any VM, the error received is:
More specifically, the error is:

{{{
NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status -5600 (0xffffea20) (rcNt=0xe986ea20)
VBoxDrvStub error: ntdll.dll: 11 differences between 0xa34e2 and 0xa34ec in #1 (.text), first 8b != b8 (rc=-5600)

Make sure the kernel module has been loaded successfully.

where: supR3HardenedWinReSpawn what: 3
VERR_SUP_VP_MEMORY_VS_FILE_MISMATCH (-5600) - Process Verification Failure: The memory content does not match the image file.
}}}
"	Twisted Lucidity
15467	Upgrade to Windows 10 fails	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
18481	Upgraded to 6.x and now VB is broken	VirtualBox 6.0.4	2019-03-08T14:49:07Z	2019-03-09T05:16:02Z	2019-03-09T05:16:02Z	"I had as good running system with v 5.2 installed and several VMs 
1) Win 10 64 bit / Win Defender off except for Fire wall / Malware bytes 
2) I have downgraded and removed all ""User"" files and program files several times
3) I have tried in safe mode and also disabled malware bytes / same error 
4) I do not have any new Windows Updates installed 

System was fully functioning until I ran the 6.x update which took 15 minutes and hung / now system is 
dead 
Will attach hardening log and screenshot / I have read the forums on this and none of the ""fixes"" work 

Result Code: 
E_FAIL (0x80004005)
Component: 
MachineWrap
Interface: 
IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}
"	brentd36
20136	"upon resume getting ""VBoxClient: Crtc disable failed 63"""	VirtualBox 6.1.16	2021-01-19T17:15:10Z	2021-01-19T17:15:10Z	2021-01-19T17:15:10Z	"6.1.16 r140961 (Qt 5.6.2)

Sometime reactivating the ""full screen"" fixes it, sometimes I have to reboot"	ralfhauser
17860	USB 3.1 support	VirtualBox 5.2.14	2018-07-09T11:44:14Z	2018-07-09T12:17:10Z	2018-07-09T12:17:10Z	"The usb camera that reports as USB 3.1 will not be recognized by Virtual box while every things working fine with USB 3.0 camera. 

I am not sure if anyone has already reported this. But I did not find any thing in google search.

I am using latest version of Virtual box 5.xx and USB extension package.  "	T1000
21267	USB devices are not recognized in the guest machine	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
21406	USB devices not being enumerated on 7.0.4	VirtualBox-7.0.4	2023-01-12T15:58:10Z	2023-01-12T15:58:10Z	2023-01-12T15:58:10Z	"Host Windows 11, upgraded VB to 7.0.4 from 7.0.2 and all VM's could not have access to external USB devices. Without the VM turned on, Settings, USB devices kept saying 'no USB devices'. 

Downgrade and the USB enumeration is working again. "	Telboy
14751	USB flash driver not working on Windows 7	VirtualBox 5.0.8	2015-10-26T18:33:05Z	2015-10-26T18:33:05Z	2015-10-26T18:33:05Z	USB flash driver attach to Windows 7 guest does not work, but working in Windows XP guest.	Steely Wing
15271	"USB mouse ""dies"" - pointer still moving but no function"	VirtualBox 5.0.16	2016-03-24T11:21:45Z	2021-08-13T05:38:52Z	2021-08-13T05:38:52Z	"I am using a kubuntu 15.10 64 bit guest on Windows 7 Enterprise SP 1 with Version 5.0.16 r105871.

About every day, the USB mouse kinda dies in the guest - it still works normal on the Windows host and the pointer still moves in the kubuntu guest, but focus follows mouse and clicks don't do anything any more. Keyboard and everything else still works fine.

Logging off from KDE and on again fixes the problem.

In the attached dmesg, there is an issue with IRQ 22 and a stack trace which I am quite sure are related. The relevant VBox.log is also attached."	Torsten Römer
15328	usb mouse does not work after migrating to 5.0.18	VirtualBox 5.0.18	2016-04-21T07:18:46Z	2016-08-03T09:47:26Z	2016-08-03T09:47:26Z	"if I setup guest 5.0.18 addons in linux guest , mouse seems available but no cursor is displayed.
if I remove completely guest kernel modules addons, mouse is working.
if I setup 5.0.16 guest addons and run 5.0.18 host , the mouse does not work , graphic system runs badly.


"	sancelot
14200	USB not detected when VBox running	VirtualBox 4.3.28	2015-06-16T11:11:42Z	2015-06-22T18:49:08Z	2015-06-22T18:49:08Z	I have a Canon IX8000 series USB printer connected directly to my PC. If I run VBox the printer is reported offline and cannot be accessed. As soon as I close VB the printer starts working again	MarkT
16019	USB Problem in Windows 7 Gust System	VirtualBox 5.1.6	2016-10-03T12:11:15Z	2016-10-03T14:11:43Z	2016-10-03T14:11:43Z	"Dear Sir

I am using macbook Pro 13 inch and have installed Windows 7 using Virtual Box (my current version 5.1.6). I am not able to use my Flash Drives, Printer there is some '''error will using Usb'''.. 
Request to fix my problem."	Sanjeevkumar
15364	USB shadowing to a temp drive (USB boot drive testing capability)	VirtualBox 5.0.18	2016-04-27T19:00:36Z	2016-04-27T19:13:47Z	2016-04-27T19:13:47Z	"USB to Temporary drive shadow would be nice, 
https://www.ntlite.com/ > iso > updates > drivers > deploys. USB...

bind USB to VM pull data to temp drive, test the USB for boot etc. 
or a name???.usbdrive for image. 

currently one has to iso the files , back or need a few machines. "	necrose99
18871	User Account delete	VirtualBox 6.0.10	2019-08-27T06:19:02Z	2019-08-27T06:19:02Z	2019-08-27T06:19:02Z	"Dear virtualbox team

I did a big mistake by registering my account ch.eick@arcor.de .
There was an issue be entering my alias and the registration process did only accept my mail an mail address as alias.
Okay, now my mail address is visible directly.

Would you please delete my account. In addition I opened a ticket for the Oracle SSO, but first you have to delete the vBox account-

Is there a way, to delete an account by my self? There is nothing to find in the online documentation

Thanks a lot
     Christian"	ch_eick
18103	User-manual amendment regarding DHCP IP / NAT networking	VirtualBox 5.2.20	2018-11-04T18:03:23Z	2018-11-05T08:27:54Z	2018-11-05T08:27:54Z	"There should be a _stern_ warning in the dhcpserver section not to use the gateway IP for the dhcp server! It kinda-sorta works, but completely messes up port forwarding of ""NAT Network"".

What would be even better is an error message, stating that IP so and so is already in use by the gateway + a suggestion to use something else, e.g. ""192.168.15.3"" (not .1 and .2)."	robert spitzenpfeil
11081	Using Bridged Adapter, Allow Option for Host Cable/Connection State to Passthrough to Guest	VirtualBox 4.2.2	2012-10-19T02:14:44Z	2013-11-25T17:28:31Z	2013-11-25T17:28:31Z	While the ability to set the cable connection state is helpful for testing, I find (especially on a laptop with wired and wireless adapters) that most often I want the host cable state (or equivalent wireless connection state) to pass through to the guest, such as going for home to work and back to home networks, a typical daily example. Currently, I run a batch file on the new network to issue VBoxManage command to do this manually. For guests that obtain their own address from the physical network, it would be a convenient option to have the guest detect the host's connection state and pick-up a new address config on the connection to a new network.	CM7
10993	Using cmd+<key> in Mac OS X host executes the command but also the <key> to the guest	VirtualBox 4.2.0	2012-09-24T20:41:24Z	2012-10-20T10:16:45Z	2012-10-20T10:16:45Z	"With the latest hotfix 4.2.1 when I do cmd+e (to start Explorer in a Windows XP guest) it starts Explorer but also inputs the character 'e' in the current focused application (ex: Notepad). 

This also is true for any other cmd+<key> combination."	kimus
20803	Using Greenshot for screenshot management on Host crash VirtualBox	VirtualBox 6.1.32	2022-02-01T19:09:35Z	2022-02-01T19:13:32Z	2022-02-01T19:13:32Z	"Hello,

I use greenshot on my computer and also open Virtualbox with an Ubuntu Guest

I launch virtual box and my guest is running.

I use Greenshot to do a screenshot and open in image editor

I go on the greenshot software and copy the image to the clickboard button

Then my virtualbox software is killed When I copy this 
Environment

I use 

Windows 10 

Greenshot 1.2.10 Build 6

Virtualbox 6.1.32 r149290

Greenshot support is saying :
https://greenshot.atlassian.net/browse/BUG-2892
Greenshot places an image to the clipboard, which to our knowledge is according to the specifications from Microsoft itself.
"	Greggreg
17439	Using Intel Realsense SR300 camera causes VM Abort	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
14111	Using SaveState is corrupting disk image when VirtualBox has been opened more than once (by multiple users)	VirtualBox 4.3.26	2015-05-12T22:13:04Z	2015-05-13T07:24:15Z	2015-05-13T07:24:15Z	"We have had a clients production VM disk image get corrupted twice so have spent a fair amount of time investigating the issue and trying to reproduce it. Can now reproduce fairly easily (see below).

Corruption original occurred on the client machine configured as followed:[[BR]]
Host = Win Server 2007 Web edition [[BR]]
Guest = Centos 6.5[[BR]]
Virtual Box 4.3.12-93773[[BR]]
Other Info = On the client machine we are running VBoxVMService to run the VM as a service on the host. Which can result in two VBoxSVC processes running if the service is running and you open the VBox control panel GUI.

I have also been able to reproduce corrupting the VM disk on my dev machine just by using the Virtual box control panel as two separate users:[[BR]]
Host = Windows 8.1 Pro 64[[BR]]
Guest = Centos 6.5[[BR]]
VBox Version = 4.3.12-93773  and also uninstalled and reinstalled latest version (VBox 4.3.26) and could still reproduce.

The easiest way to reproduce the problem is:
1. Open Vbox as userA and start the virtual machine.
2. Open Vbox as userB  (this creates a second VBoxSVC.exe process)
3. Stop the VM as userA using SaveState (which saves the state of the VM to a .SAV file in the snapshots folder). See attached screenshot 'userA.png' for what the control panel looks like at this point.
4. Swap to userB and you will see in the control panel it doesn't show the saved state of the VM. (see screenshot userB.png). 
5. Start the VM using the userB control panel. Which starts the VM from scratch, and does NOT use the saved state of the VM from userA.
6. Make any changes to the VM – e.g. change something in the DB, generate some files etc
7. Stop the VM in control panel (userB) using either full shutdown or save state
8. Swap back to userA and start VM again - this will load the VM’s savestate from Step 3, and will apply it to the disk file which has been changed by step 4-7, which results in corrupting the disk image.   
9. On restarting the guest OS, it does a disk scan and shows the file system is corrupted (see screenshot DiskCorruption.png). How bad the corruption is seems to depend on the amount of changes made to the disk in steps 4-7 above. 

Basically anytime there are two VBoxSVC.exe processes running at the same time, if one of them saves the state of the VM, the other process doesn't know about this saved state, so the 2nd proces then start the VM and make changes to the disk, 
which can then corrupt the disk when the 1st process starts the VM again.

The biggest issue can see with this is where VirtualBox is running on a server which multiple users log into the server, and some users leave the control panel open. When a user stops the VM using savestate other users who had the control panel open could modify the disk without loading the saved state. 

From hunting around online it looks like others people have had similar issues where two separate processes modify the disk image where one process stopped the VM using save state. Here is example of similar issue where savestate corrupts the VM, but in a very different scenario. https://forums.virtualbox.org/viewtopic.php?f=1&t=56109


Have also attached the VBox.log from the last time the VM was started (where it shows the disk corruption)."	jphiggs
17314	V 5.2.2 doesn't work and cannot be unistalled	VirtualBox 5.2.0	2017-11-26T20:37:33Z	2017-11-26T22:03:29Z	2017-11-26T22:03:29Z	I downloaded and installed the latest release over a 5.1 release under Win10. When I attempted to run an XP VM used 15 mins earlier it saied teh Extensions were out of date. I attempted to installed the new extensions but it failed with an URL error on the validation. So now I could not run my XP machine. I deleted the VM and tried to uninstall VirtualBox. That was rejected - cannot access path - you may not have authority, (I run as administrator). Nor would it let me modify the installation. Can anyone tell me how to get out of this mess, please? 	Benjiboy
9639	v4.1.2 and previous: amplified OpenGL mouse movements	VirtualBox 4.1.2	2011-09-23T12:15:21Z	2022-01-04T21:25:37Z	2022-01-04T21:25:37Z	"Host:
System   -- Dell E6510: 8GB, 1.7GHz Core i7 Q720; Win7 Pro SP1 x64
Graphics -- Nvidia NVS 3100M; Forceware v270.61
Mouse -- Microsoft USB IntelliMouse Optical; IntelliPoint v8.20.409.0
VirtualBox v4.1.2

Guests:
Win7 Ultimate SP1 x64 with Guest Additions installed
Win8 Developer Preview x64 with NO Guest Additions installed


Symptoms:

When running the OpenGL program Celestia v1.6.1
which is available at http://sourceforge.net/projects/celestia/files/ 
dragging the mouse in its window with either or both mouse buttons held 
down seems to cause the application to receive many more mouse evemts
than it should or to receive unrealistically large mouse motion values.

When the LMB is dragged, the selected object should move the same amount
of distance that the mouse is dragged. Instead it ""leaps off the screen""

When the RMB is dragged, the selected object should rotate smoothly.
Instead it rotates by unpredictably large amounts.

When both buttons are held down simultaneously, the selected object
should move at a moderate speed toward or away from the viewpoint.
Instead it immediately becomes extremely close or invisibly distant.

Exactly the same symptoms are seen when running Celestia in both guests
and whether or not 2D or 3D graphics acceleration is enabled.

These symptoms are not seen when running on the host.

I am attaching a zip file containing VirtualBox logs recorded while 
running Celestia under Win8.
"	Selden Ball
21389	v7.0.0 + v7.0.2 + v7.0.4 hang-up and damages vms of v6.1.38	VirtualBox-7.0.4	2023-01-02T19:13:51Z	2023-01-02T19:13:51Z	2023-01-02T19:13:51Z	My host machine is Windows11Pro with the last updates installed. I use various virtual machines with virtualbox 6.1.38 and they work fine. I tried to update to v7.0.0 + v7.0.2 + v7.0.4 and the old machines not only do not work with the new release but were damaged! I have been complelled to reinstall again v6.1.38 and recover the virtual machines by backups. The guest operating systems are: WindowsXP + Windows7_32 + Windows7_64 + Windows10Pro + Windows11Pro. What happens is that the virtual machine locks during boot, the cpu goes to 100% and the memory load remains the same. It seems that during the startup something goes wrong, the hypervisor hang-up and damage the boot disk. The biggest problem is that of the damage of the virtual machine.	tiria
17524	Various VBox binaries use a SHA1-timestamped SHA2 signature	VirtualBox 5.2.6	2018-02-05T01:10:59Z	2020-04-17T07:08:14Z	2020-04-17T07:08:14Z	"When an app set a stronger SHA1 deprecation policy on my Windows 10 system than Microsoft currently sets themselves, I found myself unable to start any VM, nor able to re-install VirtualBox.

I tracked the issue down to a flag that deprecates SHA1 timestamp signatures. What I found is that when VirtualBox is being signed by the Oracle certs, when it comes to applying the SHA256 digest with the SHA256 certificate, that signature is being timestamped by the SHA1 Symantec timestamp server. This means that in future, if Microsoft were to roll out a more comprehensive SHA1 deprecation, VirtualBox would break.

Symantec provides a SHA256 timestamping resource that should be used to timestamp SHA256 signatures:

{{{
http://sha256timestamp.ws.symantec.com/sha256/timestamp
}}}


I'm not sure what tool VBox uses to sign with, but if it happens to be Microsoft's SignTool, you would want to use ""/tr"" instead of ""/t"", and add ""/td SHA256"".

I detailed the issue on the forum here:
[https://forums.virtualbox.org/viewtopic.php?f=6&t=86574]

To reproduce, first record your current deprecation flags (from elevated CMD prompt):

{{{
certutil -getreg chain\Default\WeakSha1ThirdPartyFlags 0x84400000
}}}


Next set flags that include CERT_CHAIN_DISABLE_TIMESTAMP_WEAK_FLAG:

{{{
certutil -setreg chain\Default\WeakSha1ThirdPartyFlags 0x84400000
}}}


Now try to start a VM or install VirtualBox. Both will fail because (at minimum) VBoxDrv.sys has a SHA256 signature with a SHA1 timestamp.

Finally, restore your original deprecation policy. For most up-to-date systems, this should be as follows:

{{{
certutil -setreg chain\Default\WeakSha1ThirdPartyFlags 80040000
}}}


"	Diggie_OC
15081	VB 5.0.14 disables bluetooth on OSX 10.11.3 host	VirtualBox 5.0.14	2016-01-26T18:51:11Z	2017-12-24T18:17:39Z	2017-12-24T18:17:39Z	"VB 5.0.14 disables bluetooth on an iMac running OSX 10.11.3 thereby preventing the use of the wireless keyboard and trackpad. Hence the loss of control of both host and guest! [[BR]]
[[BR]]
The only(?) way out of this is to force a reboot of the system using power switch.[[BR]]
[[BR]]
This is not a problem with VB 5.0.10"	esLivingston
16870	VB 5.1.22 Aborts and issues running Outlook 2016 on Windows 10 Guest	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
15993	VB 5.1.6 + Solaris 11.3 + SunRay + Multihead + Fullscreen = only first monitor shown	VirtualBox 5.1.6	2016-09-27T20:58:25Z	2016-09-27T20:58:25Z	2016-09-27T20:58:25Z	When going to fullscreen using VirtualBox 5.1.6 on Solaris 11.3 using SunRay on a multihead Windows 7 instance, only the first (left) screen is drawn. Going back to windowed mode produces the remaining screens.	Marty
20094	VB Blank screen after one day.	VirtualBox 6.1.16	2020-12-16T21:46:23Z	2020-12-17T14:52:09Z	2020-12-17T14:52:09Z	"
While running VB version Versie 6.1.16 r140961 (Qt5.6.2) on Windows host computer (windows 10 pro) after one day the VB screen will turn blank.

Only closing the program and restarting it will show the regular screen again.

Is there a fix ?

[img]https://imgur.com/3s39bcD[/img]
"	VB-box
20724	VB crashed after a while on company computer	VirtualBox 6.1.26	2021-12-14T13:21:57Z	2021-12-14T13:21:57Z	2021-12-14T13:21:57Z	"Every time I try to launch my VM with Ubuntu, it's crashes after couple of seconds (sometimes after couples of minutes).
This problem is caused by my company's computer setup. When my administrator has temporarily disabled some Credential Guard, my virtual machine works great."	stefek
7896	VB creates wrong .vmdk on Mac OSX	VirtualBox 4.0.0	2010-12-23T20:31:57Z	2010-12-23T20:55:02Z	2010-12-23T20:55:02Z	"Here on mac we all have one restrictions: you can't access /dev/disk0 even from root account. And when you need to access local hard drive under from VB you need to take a dance with scripts.

I'll be short.

vmdk file created with following command are look like this:

{{{
# VBoxManage internalcommands createrawvmdk -filename ~/Library/VirtualBox/HardDisks/localhost-fedora.vmdk -rawdisk /dev/disk0 -partitions 0,1,3,4
}}}

{{{
# Disk DescriptorFile
version=1
CID=08ee3126
parentCID=ffffffff
createType=""partitionedDevice""

# Extent description
RW 1 FLAT ""localhost-fedora-pt.vmdk"" 0
RW 409639 FLAT ""/dev/disk0s1"" 0
RW 105505120 ZERO 
RW 262144 ZERO 
RW 616930936 FLAT ""/dev/disk0s3"" 0
RW 155900928 ZERO 
RW 97502216 FLAT ""/dev/disk0s4"" 0
RW 262184 ZERO 

# The disk Data Base 
#DDB

ddb.virtualHWVersion = ""4""
ddb.adapterType=""ide""
ddb.geometry.cylinders=""16383""
ddb.geometry.heads=""16""
ddb.geometry.sectors=""63""
ddb.uuid.image=""a6aeccaa-3aef-4beb-87b5-8b589dccc940""
ddb.uuid.parent=""00000000-0000-0000-0000-000000000000""
ddb.uuid.modification=""00000000-0000-0000-0000-000000000000""
ddb.uuid.parentmodification=""00000000-0000-0000-0000-000000000000""
}}}

but to works correctly it should be this:

{{{
# Disk DescriptorFile
version=1
CID=08ee3126
parentCID=ffffffff
createType=""partitionedDevice""

# Extent description
RW 40 FLAT ""localhost-fedora-pt.vmdk"" 0
RW 409600 FLAT ""/dev/disk0s1"" 0
RW 105505120 ZERO
RW 262144 ZERO
RW 616930936 FLAT ""/dev/disk0s3"" 0
RW 155900928 ZERO
RW 97502216 FLAT ""/dev/disk0s4"" 0
RW 262151 ZERO 
RW 33 ""localhost-fedora-bt.vmdk"" 0

# The disk Data Base
#DDB

ddb.virtualHWVersion = ""4""
ddb.adapterType=""ide""
ddb.geometry.cylinders=""16383""
ddb.geometry.heads=""16""
ddb.geometry.sectors=""63""
ddb.uuid.image=""a6aeccaa-3aef-4beb-87b5-8b589dccc940""
ddb.uuid.parent=""00000000-0000-0000-0000-000000000000""
ddb.uuid.modification=""00000000-0000-0000-0000-000000000000""
ddb.uuid.parentmodification=""00000000-0000-0000-0000-000000000000""
}}}

just to mention, wrong lines are (ala diff):

{{{
[...]
RW 40 FLAT ""localhost-fedora-pt.vmdk"" 0
RW 409600 FLAT ""/dev/disk0s1"" 0
[...]
RW 262151 ZERO 
RW 33 ""localhost-fedora-bt.vmdk"" 0
[...]
}}}

some additional info:
{{{
sh-3.2# VBoxManage internalcommands listpartitions -rawdisk /dev/disk0
Number  Type   StartCHS       EndCHS      Size (MiB)  Start (Sect)
1       0xee  1023/254/63  1023/254/63           200            1
2       0xaf  1023/254/63  1023/254/63         51516       409640
3       0x83  1023/254/63  1023/254/63        301235    106176904
4       0x07  1023/254/63  1023/254/63         47608    879008768
}}}

{{{
sh-3.2# gpt -r show /dev/disk0
gpt show: /dev/disk0: Suspicious MBR at sector 0
      start       size  index  contents
          0          1         MBR
          1          1         Pri GPT header
          2         32         Pri GPT table
         34          6         
         40     409600      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
     409640  105505120      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC
  105914760     262144         
  106176904  616930936      3  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
  723107840  155899904      5  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
  879007744       1024         
  879008768   97502216      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
  976510984     262151         
  976773135         32         Sec GPT table
  976773167          1         Sec GPT header
sh-3.2#
}}}

and finely, how to create the right -pt, and -bt files:

{{{
dd if=/dev/disk0 of=localhost-fedora-pt.vmdk count=40 bs=512
dd if=/dev/disk0 of=localhost-fedora-bt.vmdk skip=976773135 count=33 bs=512
}}}
"	Alexey Kuznetsov
20607	VB host kernel drivers fail to build on CentOS 8 Stream kernel 4.18.0-338	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
19281	VB issue with multiple cores for Xeon 5450	VirtualBox 6.1.2	2020-01-30T17:10:23Z	2020-01-30T17:10:23Z	2020-01-30T17:10:23Z	"I have an ""older"" server running a motherboard with two Xeon 5450 (4 cores each) with 16 Gb of ram running W2016. I have installed the current version of VB and installed W7, W10 and Ubuntu (all latest versions) in respective VMs. All settings in VB work OK (as expected), except when I add more than 2 CPU cores to any VM. When that happens, CPU utilization (for the VM) goes to 100% (all cores - after a little while) the VM slows down to a crawl and/or freezes. This is most certainly not the expected behavior."	globus999
20360	VB launches for two seconds then closes	VirtualBox 6.1.22	2021-05-11T23:50:53Z	2021-05-11T23:50:53Z	2021-05-11T23:50:53Z	When I launch the VB, it comes on for two seconds, the loading hour glass displays, then the VB shell closes. I've rebooted the system and the VB. The shell does eventually becomes stable after I try many different things (clicking everywhere, ctrl/alt/delete, no other apps open, etc). It has differed each time. It has occurred four 0 five times.	matsumoto808
21036	VB Startup after Host Shutdown without VB Guest Shutdown	VirtualBox 6.1.36	2022-07-26T12:35:31Z	2022-07-26T15:22:24Z	2022-07-26T15:22:24Z	"VirtualBox doesn't show up after a host shutdown (Start/Shutdown) without VB guest shutdown (VB was running and killed by windows shutdown)

The Windows 11 VM was perfectly running prior to this accidently caused shutdown. 

Host:
  Windows 10 Enterprise / 21H2 / 19044.1826[[BR]]
  AMD Ryzen 9 3950X 16-Core Processor[[BR]]
  RAM 64,0 GB[[BR]]
 
Guest:
  Winwows 11 Professional / latest updates (yesterday)

VB Processes running:
 VBoxSDS.exe: ~ 1.8 MB

 VBoxSVC.exe: continously increasing -> >100GB

 VirtualBox.exe: 6.6 MB 

In task manager one can see continuously increasing memory consumption of VBoxSVC.exe which results in a host crash (in my case at over 100GB (64GB RAM installed)  

"	Pigo
17209	VB Unusably slow	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
16917	vb virtual display adapter not VGA Compatible	VirtualBox 5.1.22	2017-07-19T18:01:25Z	2017-07-24T10:09:32Z	2017-07-24T10:09:32Z	"Is there a Video Debugging script?
Video freezes and guest must be cold started to restore functionality: both audio and video.
'''Version 5.1.24 r117012 (Qt5.6.2)'''[[BR]]
My Computer> Manage> Device Manager
Win2Ksp3, Win2Ksp4, WinXPsp3x32
?Other Devices: ?!device not functioning 
?! Base System Device (understandable)
'''?! Video Controller (VGA Compatible disabled)'''

WinXPsp1x64
?! Base System Device
OK Standard VGA Graphics Adapter 01OCT2002 v5.2.3790.1830 driver:vgapnp.sys srv03_sp1_rtf.050324-1447
"	Tracey
19221	"VBox ""crashes"" on restart"	VirtualBox 6.1.0	2020-01-13T22:22:15Z	2020-01-17T09:25:52Z	2020-01-17T09:25:52Z	"After a big Kali VM Update VBox crashed when restarting

{{{VCPU0: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)}}}
(around line 1417 in the attached log file)

running on macOS High Sierra 10.13.6. VBox asked me to report the crash :-)

Restarting worked and the guest now runs.

VBox 6.1.0 seems to be pretty unstable. I had a handful of freezes the last two days (hadn't used it for some time). 
Especially when I resized the guest window
The image was previously an VMWare image which I converted to OVA and imported in VBox. The Graphics Controller was initially set to VBoxSVGA which lead to an Invalid Setting Detected warning (therefore I changed it)
"	C.L
11032	VBox 4.2 on Solaris 11/11 with bonding locks up network adapter	VirtualBox 4.2.0	2012-10-05T23:11:30Z	2012-10-22T17:20:54Z	2012-10-22T17:20:54Z	"I am running Solaris 11/11 SRU 11.

I have two onboard network adapters which I had bonded.  Both e1000e drivers.

I understood that virtualbox would not work properly with bond0 without vnics created.  So I created a vnic for each Guest with the guests mac.  After aprox 2 days of operation, the entire host machine will no longer be network accessible.  There are no system log messages about any issues and VBoxSvr does not have any information. This of course crashes any VBox that is using iSCSI harddrives.

I was able to reproduce this issue twice. Each time taking 2 to 3 days for the problem to manifest.

I have since unbonded the adapters and set net0 as the primary bridgeadapter for all VMs and let the vbox network driver create its own vnics over net0.  This has been running stable for 2 weeks now.

I have an identical hardware box also running Solaris 11/11 SRU 11 with bonding turned on. This box ONLY serves up iSCSI targets and has not exhibited the same behavior.

Hopefully I can get a third box where I can try reproducing it on that without disrupting production."	norchem
13466	VBox 4.3.16 dies when laptop w/ external monitor undocks	VirtualBox 4.3.16	2014-10-03T00:26:51Z	2016-09-28T06:50:46Z	2016-09-28T06:50:46Z	"VirtualBox running on a Windows 7 host (Mint 17 guest) dies when I undock the laptop. Before that happens, the guest would be running on the external monitor, either full screen or not, doesn't matter.

At the moment of undocking, the guest could either be in a window on the external monitor or in a window moved to the laptop screen, or minimized, that doesn't matter either.

I'll attach a screen shot of the error message."	Wei
12287	VBox 4.3.2 Video Capture without cursor	VirtualBox 4.3.2	2013-11-02T00:49:33Z	2013-11-18T14:49:39Z	2013-11-18T14:49:39Z	The VBox 4.3.2 Video Capture cannot capture the cursor as well.	Samiux
14898	VBox 5.0.10 Aborts Guest session on resume	VirtualBox 5.0.10	2015-12-04T04:37:18Z	2017-08-23T16:15:41Z	2017-08-23T16:15:41Z	"May be similar to #13874 but that was resolved...
I am running VBox for over a year and never experienced this, until running v5.0.10. All of a sudden now my guest session (Ubuntu 12.04 LTS with kernel 3.2.0-95) aborts when my MacBook Pro awakens (OS Mavericks).
This has happened several times and while I cannot reproduce at will, it is quite frequent."	RobCIQ
14501	VBox 5.0x unresponsive running VS1015 (or other WPF?)	VirtualBox 5.0.2	2015-08-26T13:42:13Z	2017-02-21T02:08:38Z	2017-02-21T02:08:38Z	"I had installed VBox version 5.0.2 on a Mac OSX machine running 10.10.5.

I created two (one from clean under 5.0.2 and one from clone of a machine installed under 4.3) windows 8.1 guest images each updated with latest windows updates and VBox guest additions.

On each of these I installed Visual Studio 2015.

When run up, Visual studio gets as far as openning the screen, at this point the host machine indicates that the process is fully utilising the four cores it is allocated and the windows machine becomes almost completely unresponsive. I have to power off to shut them down.

I have tried the following:

1) Disable 3d acceleration in the guest definition.
2) enable and disable the Hyper-V integration.
3) Apply the registry setting to disable WPF hardware acceleration usage: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Avalon.Graphics\DisableHWAcceleration
4) upgrade to latest build: 5.0.3 (with matching guest additions) same issues.
5) downgrade to build 5.0.0 (with matching guest additions) same issues.

finally downgrading to build 4.3.30.r101610 (with matching guest additions) Visual studio will now run as expected.

All experiments carried out on the same virtual machines.

I have during these experiments concentrated on Visual Studio, though the machines also appeared to occasionally lockup in the same manner with other causes. On one occasion the machine froze with the guest additions prompt on the screen.
But on most occassions windows ran sufficiently to start Studio before hanging.
"	wuzzy
16811	VBox 5.1.12.12440 immediately crashes - Win10 x64 Home	VirtualBox 5.1.12	2017-06-04T20:04:30Z	2017-06-05T14:25:59Z	2017-06-05T14:25:59Z	"I cannot run VirtualBox 5.1.12.12440 x64. It crashes immediately when launced. I can't confirm, but I suspect the recent Windows 10 Creators update maybe did something to harm VBox, only becuase VBox worked fine until that Windows update was applied to my computer.

I've attached a crash dump of the most recent launch. I've also attached the most recent logs."	Malchore
16864	VBox 5.1.22 Does Not Start VM after Upgrade from Win7 to Win10	VirtualBox 5.1.22	2017-06-29T22:42:33Z	2017-07-06T14:39:40Z	2017-07-06T14:39:40Z	"VM's created with Manager 5.1.22 r115126 were working in Win7.
Upgraded to Win10 Enterprise, ver 1703, build 15063.0.
VMs will not start.
VMs are Ubuntu Xenial 16.04.
Tried running the repair VM Manager from the VBox installer.  Did not work.

On VM ""Start"", I get 2 popups.  
The 1st popup refers to running a cmd 'sc.exe', the results of which are posted.
The 2nd popup refers to a file that I pasted below.
I could not find a button to attach the file.

COMMAND - SC.EXE
{{{
sc.exe query vboxdrv
[SC] EnumQueryServicesStatus:OpenService FAILED 1060:

The specified service does not exist as an installed service.
}}}"	jkAB
16875	VBox 5.1.22 on intel i3 samsung laptiop virtualbox fails to start	VirtualBox 5.1.22	2017-07-05T16:41:16Z	2017-07-06T14:24:46Z	2017-07-06T14:24:46Z	(pasted log file removed)	Robert Fernando
17026	VBox 5.1.26.117224 crashing guest with error	VirtualBox 5.1.26	2017-08-20T21:39:39Z	2017-08-20T21:39:39Z	2017-08-20T21:39:39Z	"Hello,
as noted in summary there is some situations with my VirtualBox which often lead to crashing guest.
Host is Windows 7 Ent, X64.
Guest is Windows XP SP3.
Any other info please message me.
Log is attached.
Any help would be appreciated.
"	H4rDw4rE
16086	VBOX 5.1.8 is crashing	VirtualBox 5.1.8	2016-10-20T09:58:45Z	2016-11-22T08:17:51Z	2016-11-22T08:17:51Z	"My Windows 10 box upgraded on Monday. I'm running Windows 10 Pro 10.0.14393 Build 14393 x64 now. My vbox did not work after the upgrade, so I downloaded the latest version (5.1.6) and upgraded vbox
Since the upgraded, vbox is crashing. It crashed once on Tuesday, once yesterday, and already 5 times this morning. I've upgraded to 5.1.8 this morning, and disabled Audio, but it crashed again.

Is there something that I can do to prevent this?"	Jaques
18531	Vbox 6.0.4 / HOST - Windows 10 ( 1809 ) / GUEST - Raspbian Stretch Kernal v4.14 / Surface Pro 6	VirtualBox 6.0.4	2019-03-29T21:38:24Z	2019-03-30T09:25:11Z	2019-03-30T09:25:11Z	"Bug noted regarding Mouse Visibility in reagrds to Virtual Machine Suspend as oposed to Shut Down.

Mouse integration on the Guest is Visible and Function upon Machine Startup.

If the machine is Shut Down ( Power off the machine ) then the mouse is Visible and Functional when restarted.

If the machine is Suspended ( Save the machine state ) then the mouse is Not Visible but Functional when restarted.

The condition is Repeatable and Consistent regardless of any changes in settings ( ie: PS2 Mouse vs Tablet ... )

NOTE: With the machine having been Resumed from a Suspended ( Saved State ) the mouse is visible on the host system and when hovering over the guest window. Once any region of the guest window is clicked on, then the mouse pointer disappears and only the effects of izems on the guest being hovered over is present. Mouse functionality is present, Only the Pointer is Not Visible."	ZAR
18624	Vbox 6.0.6 build failure on Linux with gcc 9.1.0	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
20847	Vbox 6.1 guest crashes when monitor powers off	VirtualBox 6.1.32	2022-02-24T14:42:54Z	2022-02-24T14:42:54Z	2022-02-24T14:42:54Z	"Also happens if monitor input is switched to a different computer!

"	mark4th
20296	vbox 6.1.18: virt-install cause vm crash (guru meditation)	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
17528	vbox always aborts KDE sesssion shutdown when machine is running	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
16527	vbox autostart-enable on deletes the autostart file /etc/vbox/[user].start	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
17935	VBox crash restarting after Windows guest put into fullscreen mode, and VM unusable after that	VirtualBox 5.2.18	2018-08-16T23:18:36Z	2018-08-19T08:19:45Z	2018-08-19T08:19:45Z	"I'm using Virtualbox 5.2.18 to run a new Windows 10 VM on Mac OS 10.13.6 on a 12"" MacBook. If I take the Windows 10 guest full screen, then save the machine state, I am unable to restart it. I get:

Failed to open a session for the virtual machine Win10.
The VM session was aborted.
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: SessionMachine
Interface: ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}

After that, Virtualbox itself crashes, and the machine has a status of Aborted. I've not found a way to get the machine started after that, short of restoring from a Time Machine backup. Even if I delve into the vbox file and change fullscreen to false, I get the same crash trying to restart the machine. I've attached a zip archive of the Mac OS crash log, and the Virtualbox log. This is entirely repeatable, and I get the same error on an old Windows 7 VM."	SDD
17721	Vbox crashes under heavy disk IO	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
18718	VBox crashes using 32 bit Linux guest on a 64 bit Windows 10 host	VirtualBox 6.0.8	2019-06-20T14:38:24Z	2019-06-22T17:04:28Z	2019-06-22T17:04:28Z	"I've created a virtual machine with a 32 bit Linux on a Windows 7 64 bit host.
Now I tried to use the same VDI disk file on a Windows 10 64 bit host computer.
But when I created a new virtual machine in the current Version of VirtualBox
using the existing VDI disk Image an exactly the same settings as on the
Windows 7 host the virtual machine crashes (""Guru Meditation"" - Fatal error)
immediately after selecting the GRUB boot options in the guest.

This problem could be fixed by choosing ""Linux 2.6 / 3.x / 4.x ('''64 bit''')"" as
the guest OS in the ""general settings"" for the virtual machine -- although the
Linux guest has only 32 bit (80386 32 bit ELF binaries).
"	Martin_G
17011	VBox crashes; Host Win 8.1, Guest Debian Strech; amd64	VirtualBox 5.1.26	2017-08-13T15:30:16Z	2017-08-15T08:35:23Z	2017-08-15T08:35:23Z	"VBox crashes on my new installation of Debian Stretch amd64 as guest system. My host system is Win 8.1, amd64. The crash happens after the installation of the Virtualbox Guest Additions during booting the guest. It is a permanent fault and happens during every boot.

Appended is the Win error message as image (part of a screen dump)."	hwkraus
14073	vbox doesn't know how to use my kernel signature to sign its modules	VirtualBox 4.3.26	2015-04-22T19:23:45Z	2015-04-23T11:29:22Z	2015-04-23T11:29:22Z	"I have signed modules on my kernel.
I have the sources and the private key in /usr/src/linux-xxx (which are found by dkms when the modules are built)
Could you improve the module build so that it signs your modules with signing_key.* when they are built with /etc/init.d/vboxdrv setup ?

I understand it will not work for a binary only kernel that I didn't build, but if I build my own kernels and I have the signing key, it should work.

Thanks."	marcmerlin
18665	VBOX doesn't work	VirtualBox 6.0.6	2019-05-21T14:15:29Z	2019-06-12T12:16:28Z	2019-06-12T12:16:28Z	"Until yesterday it works, now no.
Thanks 
Mattia"	mattia.bonini@…
17373	vbox driver does not compile with kernel 4.14.5	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
13703	"VBox generates constant ""psynch_cvwait"" #316 errors on OSX"	VirtualBox 4.3.20	2014-12-20T00:34:58Z	2014-12-20T00:34:58Z	2014-12-20T00:34:58Z	"Tonight I noticed that when I have a VM running (Ubuntu, Windows, or TinyCoreLinux),  `errinfo` on OSX (the host machine) returns constantly flowing errors like so:

{{{
$ sudo errinfo -n VBox
            EXEC          SYSCALL  ERR  DESC
    VBoxHeadless    psynch_cvwait  316 
    VBoxHeadless    psynch_cvwait  316 
    VBoxHeadless    psynch_cvwait  316 
    VBoxHeadless    psynch_cvwait  316 
    VBoxHeadless    psynch_cvwait  316 
    VBoxHeadless    psynch_cvwait  316 
    VBoxHeadless __semwait_signal   60  Operation timed out 
...
}}}

And when no VMs are running, having the VirtualBox GUI open returns constant stream of these errors (which go away when I exit it):

{{{
...
         VBoxSVC    psynch_cvwait  316 
         VBoxSVC    psynch_cvwait  316 
         VBoxSVC    psynch_cvwait  316 
...
}}}

I first noticed this when I was profiling an intensive ~8 second task in a VirtualBox VM. I used `dtruss` to trace system calls during the task, and found that about 25% of the time was spent in these `psynch_cvwait` calls, which was output like this (where 13035 is the VBoxHeadless PID):

{{{
sudo dtruss -f -a -p 13035
PID/THRD  RELATIVE  ELAPSD    CPU SYSCALL(args) 		 = return
...
13035/0x41f17:  10017630    1170     45 psynch_cvwait(0x100118610, 0x3D22A0103D22B00, 0x0)     = -1 Err#316
...
}}}

I can't find much info about Err # 316 on OSX. The XNU repo has a definition for it, but no info that I can find about this specific error:

https://github.com/opensource-apple/xnu

OSX Version: 10.10.1 (4-core Macbook Pro -- all 4 cores enabled for the VMs)
VBox Version: 4.3.20r96996
Guest OS's: Windows8, TinyCoreLinux, Ubuntu

Lmk if I can provide any more info! Thanks for your time.
"	tzaharia
17858	VBox Guest Additions make crash VM VB during take VM snapshots	VirtualBox 5.2.14	2018-07-05T18:46:11Z	2018-11-07T05:58:14Z	2018-11-07T05:58:14Z	"Hi All!

I have a VBox VM with Ubuntu 18.04 as guest on WIndows 10 Host. Before installing the VBox Guest Addition (VB GA) on Ubuntu VM, the VM snapshots all worked very well! But after installing it, all the snapshots that are made cause a crash of the same VM (they interrupt its functioning). In practice, the snapshot process stops and crashes as soon as it reaches 96% of the acquisition of the same. I need the VB GA to implement the shared network folder between guest and host.

In my opinion this is a bug of the VB GA.

  - What's the cause of this crash? Is it possible to fix it?

Thank you.

Greetings,

Lorenzo"	Kowa92
17581	Vbox Guest Additions support for kernel-4.16.0-rc2	VirtualBox 5.2.6	2018-03-02T08:24:33Z	2018-03-02T08:24:33Z	2018-03-02T08:24:33Z	"1> Virtual Box version - 5.2.6 r120293

2> Created Virtual Machine  ( CentOS Linux (3.10.0-693.el7.x86_64) 7 ).

3> Default Guest additions image ( which comes when we mount it from devices options ) is working fine.  

4> Downloaded Linux Kernel  ( version - 4.16.0-rc2 )

5> Compiled Linux Kernel ( version - 4.16.0-rc2 ) and booted with it.

6> Guest Additions stopped working, so I debugged around it.

7> And re-installed default guest addition, but its not working ( auto-size guest display is not working  )

8> Downloaded Guest Addition iso image ( VBoxGuestAdditions_5.2.8.iso ) from ""http://download.virtualbox.org/virtualbox/5.2.8/"".

9> Run the Vbox Guest additions agains. I see some compilation errors. Attaching logs.

So I just want to understand if I did something wrong here or is the kernel with which I have booted is still not supported in Virtual Box guest additions 5.2.8.
  

"	Zubraj
20242	VBox Hangs when trying to create VM with 2 CPUs using a Ubuntu cloud image	VirtualBox 6.1.18	2021-03-10T12:14:27Z	2021-03-10T12:14:27Z	2021-03-10T12:14:27Z	"I'm trying to create a VM with 2 vCPUs that boots from a (converted) Ubuntu cloud image. When I launch the machine, VirtualBox hangs and I have to reboot the host, which is a Ubuntu inux 20.04
"	paaguti-u
15052	VBox Manager icons don't adequately distinguish VMs - icons almost useless	VirtualBox 5.0.14	2016-01-20T16:01:41Z	2016-01-21T14:21:06Z	2016-01-21T14:21:06Z	"A VirtualBox VM is a terrific way to isolate development environments.  Most of our team have VirtualBox Manager screens with fifteen or twenty separate VMs.  In such a case visual distinction of the VMs in the list becomes important for efficient use.

VirtualBox manager currently has icons only distinguishing the guest operating system.  This was appropriate for the longstanding use case of desktop virtualization, namely, to provide a user with one or two guest environments in which to run different from the host environment - especially, running a Windows PC in an OS X or Linux host. 

For developing server-level software the operating system distinction among VMs is zero.  I have 9 boot2docker VMs all with the Tux's-foot icon.  Not only should there be a Docker icon (or Vagrant or whatever) but it should be possible to customize or replace the icon to provide highly specific visual distinction among VMs.

This is part of the rationale behind the implementation of the VM folders request.  And in the same way it is probably desirable to provide icons for the VM folders as well."	SchemaCzar
16403	VBox on linux host randomly power off.	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
20939	VBox on Windows 11 kernel panic - unable to sync on every VM	VirtualBox 6.1.32	2022-05-11T21:09:47Z	2022-08-04T12:46:14Z	2022-08-04T12:46:14Z	"Hi,
  I am running VBox 6.1 on a Windows 11 Pro Version 21H2 on a Dell Inspiron with a 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz   2.42 GHz processor.

I am getting a kernel panic - not syncing error.  I have verified my Hyper-V setting is disabled and am getting this problem both on a standard distribution of Ubuntu and an image my company has as a baseline. 

Interestingly, this system was working fine last night when I left the office and was scrogged this morning.  I have uninstalled and reinstalled VBox repeatedly, wiping out all traces of the prior installation and of course cold rebooted multiple times.  Every 'fix' I have found on the internet isn't applicable and I can't find a relevant bug report on the website so here I am.

  I am attaching the VBox.log file for both the Ubuntu VM and the Quectel SDK which is the VM our company uses to develop.  Thank you in advance for your help!!
      David
"	David from Sarasota FL
17008	VBOX running RHEL aborting	VirtualBox 5.1.26	2017-08-12T19:37:34Z	2017-08-14T19:17:59Z	2017-08-14T19:17:59Z	"I am running the following version of VBox:

'''VirtualBox VM 5.1.26 r117224 darwin.amd64 (Jul 27 2017 14:04:15) release log''

I am running RHEL guest from a Mac host. This has been working perfectly for almost 2 years now. However, recently I upgraded from a prior version (unfortunately I am not sure what the previous version was) to the current 5.1.26 version and ever since then I the guest OS aborts after a few hours of being up. I am not certain what is causing this, however, I do have a crash dump that I will attach from my Mac OS host."	Garfield-LzLabs
18183	vbox-dkms  modules (vboxnetadp vboxdrv) compilation error  against kernel 4.20.0-rc6 -> fixed after (not in) 5.2.22	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
16083	VBox/Devices/EFI/Firmware/VBoxPkg/VBoxVgaDxe/Edid.c:401: bad sizeof ?	VirtualBox 5.1.8	2016-10-19T18:34:40Z	2016-10-19T18:34:40Z	2016-10-19T18:34:40Z	"src/VBox/Devices/EFI/Firmware/VBoxPkg/VBoxVgaDxe/Edid.c:401]: (warning) Found calculation inside sizeof().

Source code is

    EdidOverrideDataBlock = AllocatePool (sizeof (EDID_BLOCK_SIZE * 2));

Maybe better code

    EdidOverrideDataBlock = AllocatePool (sizeof (EDID_BLOCK_SIZE) * 2);
"	dcb
17561	VBOX_E_FILE_ERROR	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
19696	VBOX_E_IPRT_ERROR 0x80BB0005 when cloning a vm that is in savestate	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
17036	VBOX_WITH_EXTPACK_VBOXDTRACE fails to build with glibc >= 2.26-2.fc27	VirtualBox 5.1.26	2017-08-24T17:33:59Z	2017-08-24T17:33:59Z	2017-08-24T17:33:59Z	"
http://koji.rpmfusion.org/kojifiles/work/tasks/6178/146178/build.log

http://koji.rpmfusion.org/koji/taskinfo?taskID=146178

the workaround is add VBOX_WITH_EXTPACK_VBOXDTRACE=  to make 

{{{
In file included from /builddir/build/BUILD/VirtualBox-
5.1.24/src/VBox/ExtPacks/VBoxDTrace/onnv/uts/common/sys/dtrace.h:55:0,
                 from /builddir/build/BUILD/VirtualBox-

5.1.24/src/VBox/ExtPacks/VBoxDTrace/onnv/lib/libdtrace/common/dtrace.h:
38,
                 from /builddir/build/BUILD/VirtualBox-
5.1.24/src/VBox/ExtPacks/VBoxDTrace/onnv/cmd/dtrace/dtrace.c:37:
/builddir/build/BUILD/VirtualBox-
5.1.24/src/VBox/ExtPacks/VBoxDTrace/include/VBoxDTraceTypes.h:59:37:
error: conflicting types for 'greg_t'
 typedef RTCCINTREG                  greg_t;
                                     ^~~~~~
In file included from /usr/include/signal.h:302:0,
                 from /usr/include/sys/wait.h:36,
                 from /builddir/build/BUILD/VirtualBox-
5.1.24/src/VBox/ExtPacks/VBoxDTrace/onnv/cmd/dtrace/dtrace.c:34:
/usr/include/sys/ucontext.h:37:37: note: previous declaration of
'greg_t' was here
 __extension__ typedef long long int greg_t;
                                     ^~~~~~
kmk: *** [/builddir/build/BUILD/VirtualBox-
5.1.24/obj/obj/VBoxDTraceCmd/src/VBox/ExtPacks/VBoxDTrace/onnv/cmd/dtra
ce/dtrace.o] Error 1
}}}

"	sergiomb
20032	vboxautostart-service (auto-start) ignores guest settings and blocks guest VMs audio output.	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
21449	vboxautostartsvc config file issue with windows domain account	VirtualBox-7.0.6	2023-01-31T08:00:56Z	2023-01-31T08:00:56Z	2023-01-31T08:00:56Z	"Following the directions in documentation 2.21.4 Windows: Starting the Autostart Service, I have run into the issue where it is NOT accepting a domain account in the autostart configuration file.  I keep getting ""Unexpected token, expected '='"" error in the windows event log.  My domain user is ""raptor"" in the ""truck"" domain.  Permutations of domain\user, user@domain do not work.  It only works if default_policy=allow, which may be a huge risk.


Config file contains only the following:

{{{
default_policy=deny
raptor@truck={
allow=true
startup_delay=10
}
}}}


Looking at the code, I believe the issue is in src/vbox/frontends/vboxautostart/vboxautostartcfg.cpp in the static function autostartConfigTokenizerCreateToken where getting complete token is checking for RT_C_IS_ALNUM which does not allow for either the \ or the @ part of user name and domain since those are not in the alphanumeric range defined in vbox/include/iprt/ctype.h."	RobertV
20851	VBoxDispD3D.dll Crash Trying to run Flutter programs	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
17847	vboxdrv failed to build - Virtualbox 5.2.12 r122591 Linux Fedora 28 x86_64	VirtualBox 5.2.12	2018-07-02T15:34:52Z	2018-07-10T15:49:27Z	2018-07-10T15:49:27Z	"Kernel module vboxdrv is VERY broken on Fedora 28
Cannot build on Fedora 28 - 4.17.3-200.fc28.x86_64

Please see dmesg log and output from /var/log/vbox-install.log"	Max E
21435	Vboxdrv module triggers IBT protection. VM's fail to start	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
20504	vboxdrv: linux kernel errors on debug kernel and vbox modules built by akmods	VirtualBox 6.1.26	2021-08-16T19:53:43Z	2022-08-04T20:38:02Z	2022-08-04T20:38:02Z	"Have several ""WARNING"" and ""BUG"" from debug Linux kernel on Fedora 34:

{{{
WARNING: CPU: 3 PID: 5680 at kernel/smp.c:874 smp_call_function_many_cond+0x1c7/0x3c0
WARNING: CPU: 3 PID: 6837 at arch/x86/include/asm/kfence.h:44 kfence_unprotect+0x2a/0x90
WARNING: CPU: 3 PID: 6837 at mm/kfence/core.c:135 kfence_unprotect+0x2c/0x90
BUG: kernel NULL pointer dereference, address: 0000000000000018
BUG: sleeping function called from invalid context at include/linux/percpu-rwsem.h:49
}}}

Linux kernel is installed from Fedora repos and vbox modules built locally by akmods package.[[BR]]
First warning (smp_call_function_many_cond) occurs at vboxdrv module load.[[BR]]
Rest of errors occur while starting VM -- it does not start after this, hanging on ""Starting virtual machine...""[[BR]]
Attaching screenshot and dmesg.

When trying same version of non-debug kernel (from main Fedora repo) and prebuilt vbox modules (from rpmfusion repo) -- there are no such errors and VM starts fine.

Package versions:
{{{
kernel-debug-5.13.9-200.fc34.x86_64
akmods-0.5.6-27.fc34.noarch
akmod-VirtualBox-6.1.26-1.fc34.x86_64
VirtualBox-kmodsrc-6.1.26-2.fc34.noarch
VirtualBox-server-6.1.26-2.fc34.x86_64
VirtualBox-6.1.26-2.fc34.x86_64
}}}"	Andrew.N
16999	VBoxDrv: Too many CPUs (288) for the GIP (max 256)	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
16448	VBoxHardening issue (AV software)	VirtualBox 5.1.14	2017-02-03T20:17:44Z	2017-10-04T09:15:23Z	2017-10-04T09:15:23Z	"Windows 7 Enterprise SP1
Virtual Box 5.1.10 was working fine until company pushed an update to my workstation.

I think the issue is related to Cylance Protect as that software seems to have been updated the day VB broke.
It's also possible kernel32.dll was updated by a windows update.

Error starting ALL VMs..

The virtual machine 'DeleteMe' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005). More details may be available in 'C:\Users\MyProfile\VirtualBox VMs\DeleteMe\Logs\VBoxHardening.log'.

Result Code: 
E_FAIL (0x80004005)
Component: 
MachineWrap
Interface: 
IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}


The workstation/host has Cylance Protect and Symantec Endpoint Protection enabled (and I can't disable them to test).

I tried test builds.

5.1.10 original had the issue.
5.1.14 - same issue
5.1.15 - test build same issue.
5.1.51 - dev build same issue

"	gingleby
17440	VBoxHardening- Exit Code 0x1	VirtualBox 5.2.4	2018-01-09T21:41:58Z	2018-01-09T22:41:16Z	2018-01-09T22:41:16Z	"I have a few different VMs on my current laptop which I am trying to move to my new laptop. However, after importing the machines, I am getting an error message when I try to open the VMs:

[[Image(ticket:1:ErrorMessage.gif)]]

and

[[Image(ticket:1:ErrorMessage2.gif)]]

My previous laptop is running Win7x64 and I am using VirtualBox 5.1.30 r11838. This has been upgraded as releases have come out so I am not sure what version of VirtualBox I was using when I created the VMs. Each machine is running a similar copy of Windows Server 2008 R2.

I have attached the VBoxHardening.log file for one of the VMs- they are all causing the same error.

I was able to open a few of the VMs once, but then after either powering off  (no saved state) or saving, I get the error message again on restart. I  have tried headless, normal, and detached starts. 

I know this issue has been raised on past versions of VirtualBox, but I didn't see a method for fixing the error which worked- I have un-installed and re-installed VirtualBox, I have tried to recreate the VMs using the same hard disk image, I have turned off my virus software, I have confirmed that I do not have the layout registry key (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers), and I have done a software scan (sfc /scannow). I would appreciate any assistance in trying to solve this issue."	mdr
17644	VBoxHeadless crash	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
15097	VBoxHeadless Crashes OSX El Captain on Host Suspend	VirtualBox 5.0.14	2016-02-02T04:08:53Z	2016-07-06T16:37:25Z	2016-07-06T16:37:25Z	"
"	jwaldrip
13531	"VBoxManage ""c:\"" argument handling"	VirtualBox 4.3.18	2014-10-20T14:04:36Z	2014-10-20T14:04:36Z	2014-10-20T14:04:36Z	"on the Microsoft Windows host I run 'cmd' and enter:[[BR]]
cd %programfiles%[[BR]]
cd Oracle[[BR]]
cd VirtualBox[[BR]]
VBoxManage setproperty machinefolder ""c:\""[[BR]]
[[BR]]
[[BR]]
The quotes are straight. In[[BR]]
VirtualBox -- File -- Preferences... -- General -- Default Machine Folder[[BR]]
this is displayed as:[[BR]]
c:\[[BR]]
in the textbox. There is no icon to the left side of the text.[[BR]]
[[BR]]
[[BR]]
In the file[[BR]]
%userprofile%\.VirtualBox\VirtualBox.xml[[BR]]
it is stored as:[[BR]]
<SystemProperties defaultMachineFolder=""c:&quot;"" ...[[BR]]
[[BR]]
[[BR]]
[[BR]]
This will lead to:[[BR]]
a) wrong folders being used.[[BR]]
New virtual machines created with VirtualBox.exe will be stored in[[BR]]
""%userprofile%\%VBOXNAME%\""[[BR]]
instead of[[BR]]
""c:\%VBOXNAME%\""[[BR]]
[[BR]]
The snapshot folder of the virtual machine is wrong as well.[[BR]]
[[BR]]
[[BR]]
b) errors if you programmatically create a virtual machine.[[BR]]
If you set the machinefolder:[[BR]]
VBoxManage setproperty machinefolder ""c:\""[[BR]]
[[BR]]
The VM creation/registration command :[[BR]]
VBoxManage createvm --name ""%VBOXNAME%"" --ostype Windows7 --register[[BR]]
[[BR]]
will fail with the error message:[[BR]]
VBoxManage.exe: error: Invalid machine settings file name 'C:\Users\user\""\VB-USER\VB-USER.vbox' (VERR_INVALID_NAME)[[BR]]
VBoxManage.exe: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component Machine, interface IMachine, callee IUnknown[[BR]]
VBoxManage.exe: error: Context: ""CreateMachine(bstrSettingsFile.raw(), bstrName.raw(), ComSafeArrayAsInParam(groups), bstrOsTypeId.raw(), createFlags.raw(), machine.asOutParam())"" at line 275 of file VBoxManageMisc.cpp[[BR]]
[[BR]]
[[BR]]
Note: the problem applies to the following parameters as well:[[BR]]
VBoxManage createvm --basefolder[[BR]]
VBoxManage modifyvm --snapshotfolder[[BR]]
[[BR]]
[[BR]]
For example, if you run[[BR]]
VBoxManage setproperty machinefolder ""c:\""[[BR]]
and[[BR]]
VBoxManage createvm --basefolder ""c:\""[[BR]]
The settings file will be stored in:[[BR]]
%userprofile%\%VBOXNAME%\%VBOXNAME%.vbox[[BR]]
The Snapshot folder will be stored in:[[BR]]
%userprofile%\%VBOXNAME%\%VBOXNAME%\Snapshots[[BR]]
[[BR]]
I leave out the example of the snapshotfolder.[[BR]]
[[BR]]
[[BR]]
The workaround I found is instead of[[BR]]
""c:\""[[BR]]
use[[BR]]
{{{
""c:\\""
}}}
OR[[BR]]
{{{
c:\
}}}
as argument to machinefolder/basefolder/snapshotfolder parameter.[[BR]]
[[BR]]
In ""%userprofile%\.VirtualBox\VirtualBox.xml""[[BR]]
{{{
""c:\\""
}}}
is stored as[[BR]]
<SystemProperties defaultMachineFolder=""c:\""[[BR]]
[[BR]]
c:\ is stored as[[BR]]
<SystemProperties defaultMachineFolder=""c:\""[[BR]]
[[BR]]
Either workaround will display a folder icon in[[BR]]
VirtualBox -- File -- Preferences... -- General -- Default Machine Folder[[BR]]
[[BR]]
[[BR]]
[[BR]]
[[BR]]
Note:[[BR]]
on Fedora 20 x86_64 you can use ""/"" as a machine folder without problem.[[BR]]
I had to start VirtualBox with root-permissions to work with this, though.[[BR]]"	Sobek
14709	VBoxManage (Windows) doesn't accept paths with spaces using quotation marks	VirtualBox 5.0.6	2015-10-17T01:44:29Z	2015-10-17T01:44:29Z	2015-10-17T01:44:29Z	"I need to resize a disk urgently and cannot due to this stupid bug. Can't rename folders and vdi filename to have no spaces as that causes a different error.  eg.

VBoxManage modifyhd ""Windows 10 (64-bit).vdi"" --resize 40960
returns
Syntax error: Invalid parameter '10'
"	Ross
17570	vboxmanage cli - Segmentation fault	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
20208	vboxmanage clonevm crashes VBoxSVC	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
6132	VBoxManage confuses VM names starting with dash character (-) with command line option names	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
15406	VBoxManage copyto file->file rather odd	VirtualBox 5.0.20	2016-05-11T11:17:09Z	2016-05-11T11:17:09Z	2016-05-11T11:17:09Z	"My use case is to copy a file from host to guest and rename it in the process.

The way to do this is:

VBoxManage.exe guestcontrol ""my-machine"" --username user --password secret copyto C:\\foo.txt --target-directory ""C:\bar.txt""

Apart from this looking rather strange (a file name in the --target-directory), it is also not described in the manual. Either the manual or the CLI could be fixed.

Host: Windows 7
Guest: Windows Server 2012 R2
"	rogierschouten
4703	VBoxManage creterawvmdk on osx only allows first 4 partitions.	VirtualBox 3.0.4	2009-08-06T18:18:29Z	2011-10-01T13:50:20Z	2011-10-01T13:50:20Z	"VBoxManage creterawvmdk on osx only allows first 4 partitions to be used.
Also allows nonexistitng partitions with too high numbers
on the commandline without any error message. Example command:
{{{
sudo VBoxManage internalcommands  createrawvmdk  -filename /tmp/foo.vmdk -rawdisk /dev/disk0 -partitions 1,2,3,4,5,6,7,8,9,10,11,12,13
}}}

partition table (gpt)
{{{
sudo gpt -r show /dev/disk0
Password:
gpt show: /dev/disk0: Suspicious MBR at sector 0
      start       size  index  contents
          0          1         MBR
          1          1         Pri GPT header
          2         32         Pri GPT table
         34          6         
         40     409600      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
     409640   26542320      2  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
   26951960     262150         
   27214110   10586832      3  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
   37800942          3         
   37800945   24659775      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
   62460720  455432536      5  GPT part - 48465300-0000-11AA-AA11-00306543ECAC
  517893256   95864960      6  GPT part - 48465300-0000-11AA-AA11-00306543ECAC
  613758216     262149         
  614020365    4128705      7  GPT part - 0657FD6D-A4AB-43C4-84E5-0933C84B4F4F
  618149070    6988275      8  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
  625137345       5070         
  625142415         32         Sec GPT table
  625142447          1         Sec GPT header
}}}

Resulting vmdk file
{{{
# Disk DescriptorFile
version=1
CID=4dd10ca2
parentCID=ffffffff
createType=""partitionedDevice""

# Extent description
RW 1 FLAT ""foo-pt.vmdk""
RW 409639 FLAT ""/dev/disk0s1""
RW 26542320 FLAT ""/dev/disk0s2""
RW 262150 ZERO 
RW 10586832 FLAT ""/dev/disk0s3""
RW 3 ZERO 
RW 24659775 FLAT ""/dev/disk0s4""
RW 562681728 ZERO 
snipped from here
}}}"	Bengt-Arne Fjellner
14846	VBoxManage Error about Machine XXX is not currently running and Machine XXX is really running in Windows Task Manager	VirtualBox 5.0.10	2015-11-19T17:15:54Z	2018-04-05T20:10:43Z	2018-04-05T20:10:43Z	"Hi, I'm trying to launch the command ""vboxmanage controlvm XXX savestate"" (or controlvm XXX poweroff) after to have been executed succesfully, about 15 or 20 minutes before <if you try to reproduce this issue I explain but starting the VM follow by shutting down inmediatly via commands curiosely it works fine..>, the command ""vboxmanage startvm XXX --type headless"" (as well as without headless modifier) from a Scheduled Task of Windows Task Scheduler. I'm involved whith this issue for several days, perhaps two weeks... I've tried all I know about it... It seems to be that transcurred some minutes from starting the machine, she (the machine) disappears from the runnig list machines as I can positively test: just now I have my three-VBoxHeadlexx processes plus one VBoxSVC process running on my Windows 7 x64, and if I run ""vboxmanage list runningvms"" I get no machines running message. So, when I try to run ""vboxmanage controlvm XXX savestate"" manually or through a Scheduled Task, I get a no running machine with that name in the first case, or a 0x01 code in the Windows Task Scheduler saying ""the command-task finished but with warnings"". Thanks for support and best regards."	aZtk-laga
20626	VboxManage Error: Code E_ACCESSDENIED (0x80070005) - Access denied	VirtualBox 6.1.28	2021-10-22T21:01:31Z	2022-06-26T06:16:22Z	2022-06-26T06:16:22Z	"Hi

When I attempt to run the following command:

VBoxManage hostonlyif ipconfig vboxnet0 --ip 172.28.128.1 --netmask 255.255.255.0

I got the message:

""VBoxManage: error: Code E_ACCESSDENIED (0x80070005) - Access denied (extended info not available)""

I downgraded to 6.1.26 version and it is working fine, as it is expected.

My host operative system is MacOS Big Sur

Thanks
"	hesevo
17792	vboxmanage guestcontrol run --exe doesn't display any output	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
18480	VBoxManage hangs after some parallel operations	VirtualBox 5.2.22	2019-03-07T17:10:16Z	2019-03-07T17:23:30Z	2019-03-07T17:23:30Z	"This sometimes happens when I run some commands in parallel.

Processes:
{{{
(ins)george@gsovetov:~/Development/***$ ps -AlF | grep --color -i vbox 
1 S root      1321     2  0  60 -20 -     0 -          0   4 Jan30 ?        00:00:00 [iprt-VBoxWQueue]
1 S root      1341     2  0  80   0 -     0 -          0   7 Jan30 ?        00:00:00 [iprt-VBoxTscThr]
0 S george    7401 32042  0  80   0 -  3196 -        992   1 19:53 pts/4    00:00:00 grep --color -i vbox
0 S george   15921 23446  0  80   0 - 596033 -     919504  6 17:22 ?        00:00:59 /usr/lib/virtualbox/VBoxHeadless --comment ***-001 --startvm e03278fd-e235-594b-8ad9-*** --vrde config
0 S george   16040 23446  0  80   0 - 595039 -     913772  1 17:22 ?        00:01:29 /usr/lib/virtualbox/VBoxHeadless --comment ***-002 --startvm a2221747-de55-5022-b579-*** --vrde config
0 S george   23441     1  0  80   0 - 47323 SyS_po 37212  10 Jan30 ?        07:07:13 /usr/lib/virtualbox/VBoxXPCOMIPCD
0 S george   23446     1  1  80   0 - 512180 core_s 1102356 2 Jan30 ?       11:12:08 /usr/lib/virtualbox/VBoxSVC --auto-shutdown
0 S george   25549     1  0  80   0 - 98202 -      16452  11 18:11 tty2     00:00:00 /usr/lib/virtualbox/VBoxManage controlvm ***-001 nic3 intnet 4c8cf59c-40eb-11e9-a5eb-e8de2706accd 10.254.254.0/28 flat
0 S george   25593     1  0  80   0 - 98202 -      16392   1 18:11 tty2     00:00:20 /usr/lib/virtualbox/VBoxManage createmedium disk --filename /home/george/***-004.vmdk --diffparent /home/george/***-template.vmdk
0 S george   25697     1  0  80   0 - 98202 -      16668   3 18:11 tty2     00:00:00 /usr/lib/virtualbox/VBoxManage list vms
}}}
Three last commands are hanging.

There are always four threads, one of which is hanging in `poll`. Typical backtrace of hanging command (with lots of ""??"" unfortunately):
{{{
pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225

Thread 4 (Thread 0x7ff0dc331700 (LWP 25603)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x00007ff0e76d327e in RTSemEventWait () from /usr/lib/virtualbox/VBoxRT.so
...

Thread 3 (Thread 0x7ff0ddc49700 (LWP 25602)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007ff0e729ccfb in VBoxNsprPR_WaitCondVar () from /usr/lib/virtualbox/VBoxXPCOM.so
#2  0x00007ff0e729cf3b in VBoxNsprPR_Wait () from /usr/lib/virtualbox/VBoxXPCOM.so
...

Thread 2 (Thread 0x7ff0ddcca700 (LWP 25601)):
#0  0x00007ff0e69856ad in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x00007ff0e729a134 in ?? () from /usr/lib/virtualbox/VBoxXPCOM.so
#2  0x00007ff0e729bb8f in VBoxNsprPR_Poll () from /usr/lib/virtualbox/VBoxXPCOM.so
...

Thread 1 (Thread 0x7ff0e8037680 (LWP 25593)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x00007ff0e729c881 in ?? () from /usr/lib/virtualbox/VBoxXPCOM.so
#2  0x00007ff0e729cc9e in VBoxNsprPR_WaitCondVar () from /usr/lib/virtualbox/VBoxXPCOM.so
#3  0x00007ff0e729cf3b in VBoxNsprPR_Wait () from /usr/lib/virtualbox/VBoxXPCOM.so
...
#11 0x0000000000000000 in ?? ()
}}}

I have Windows and Linux guests but it seems it doesn't matter what the guests are."	georgesovetov
20261	VBoxManage import without eula acceptance returns exit code zero	VirtualBox 6.1.18	2021-03-17T16:03:06Z	2021-03-17T16:03:06Z	2021-03-17T16:03:06Z	"Hello!  I have just noticed, when doing a VBoxManage import, the command exits with exit code zero (success) even when there is a license-acceptance error.

I am running VirtualBox 6.1.18r142142.  To ensure I was up-to-date, I downloaded the 6.1.18 .dmg, used the uninstall script to uninstall, rebooted, and then used the installer to install VirtualBox (including all optional components).

Here are steps to reproduce:

1. Download the [https://www.linuxvmimages.com/images/debian-10/ Debian 10 VirtualBox image] from [https://www.linuxvmimages.com/ linuxvmimages.com] (direct link: https://sourceforge.net/projects/linuxvmimages/files/VirtualBox/D/10/Debian_10.7.0_VB.zip/download).
2. Unzip the .zip file, and get the path to the .ova file.
3. Run the command `VBoxManage import PATH_TO_OVA_FILE`.

Here is the output of what happens:

{{{
ITS-C02C91G0MD6R:~ akkornel(nc)$ VBoxManage --version
6.1.18r142142
ITS-C02C91G0MD6R:~ akkornel(nc)$ VBoxManage import /Users/akkornel/Downloads/Debian_10.7.0_VB/Debian_10.7.0_VB_LinuxVMImages.COM.ova
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interpreting /Users/akkornel/Downloads/Debian_10.7.0_VB/Debian_10.7.0_VB_LinuxVMImages.COM.ova...
OK.
Disks:
  vmdisk1	549755813888	-1	http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized	Debian_10.7.0_VB_LinuxVMImages.COM-disk001.vmdk	-1	-1

Virtual system 0:
 0: Suggested OS type: ""Debian_64""
    (change with ""--vsys 0 --ostype <type>""; use ""list ostypes"" to list all possible values)
 1: Suggested VM name ""Debian_10.7.0_VB_LinuxVMImages.COM""
    (change with ""--vsys 0 --vmname <name>"")
 2: Suggested VM group ""/""
    (change with ""--vsys 0 --group <group>"")
 3: Suggested VM settings file name ""/Users/akkornel/VirtualBox VMs/Debian_10.7.0_VB_LinuxVMImages.COM/Debian_10.7.0_VB_LinuxVMImages.COM.vbox""
    (change with ""--vsys 0 --settingsfile <filename>"")
 4: Suggested VM base folder ""/Users/akkornel/VirtualBox VMs""
    (change with ""--vsys 0 --basefolder <path>"")
 5: Product (ignored): Debian 10.7.0
 6: Vendor (ignored): Debian Community
 7: Version (ignored): 10.7.0
 8: ProductUrl (ignored): https://www.linuxvmimages.com/debian-10
 9: VendorUrl (ignored): https://debian.org
10: Description ""Debian 10.7.0 VirtualBox Image
User Name: debian
Password: debian""
    (change with ""--vsys 0 --description <desc>"")
11: End-user license agreement
    (display with ""--vsys 0 --eula show"";
    accept with ""--vsys 0 --eula accept"")
12: Number of CPUs: 2
    (change with ""--vsys 0 --cpus <n>"")
13: Guest memory: 2048 MB
    (change with ""--vsys 0 --memory <MB>"")
14: Sound card (appliance expects """", can change on import)
    (disable with ""--vsys 0 --unit 14 --ignore"")
15: USB controller
    (disable with ""--vsys 0 --unit 15 --ignore"")
16: Network adapter: orig Bridged, config 3, extra slot=0;type=Bridged
17: CD-ROM
    (disable with ""--vsys 0 --unit 17 --ignore"")
18: IDE controller, type PIIX4
    (disable with ""--vsys 0 --unit 18 --ignore"")
19: IDE controller, type PIIX4
    (disable with ""--vsys 0 --unit 19 --ignore"")
20: SATA controller, type AHCI
    (disable with ""--vsys 0 --unit 20 --ignore"")
21: Hard disk image: source image=Debian_10.7.0_VB_LinuxVMImages.COM-disk001.vmdk, target path=Debian_10.7.0_VB_LinuxVMImages.COM-disk001.vmdk, controller=20;channel=0
    (change target path with ""--vsys 0 --unit 21 --disk path"";
    disable with ""--vsys 0 --unit 21 --ignore"")
VBoxManage: error: Cannot import until the license agreement listed above is accepted.
ITS-C02C91G0MD6R:~ akkornel(nc)$ echo $?
0
}}}

Notice how VBoxManage returns exit code zero.

I think the problem is in [https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Frontends/VBoxManage/VBoxManageAppliance.cpp?rev=73217#L940 VBox/Frontends/VBoxManage/VBoxManageAppliance.cpp around line 940].  It looks like although `RTMsgError` is called to report the problem, `rc` is never set to indicate a problem, so `RTEXITCODE_SUCCESS` ends up bring returned."	akkornel
20246	vboxmanage modifymedium lock not released immediately	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
11489	vboxmanage showhdinfo does not work with relative pathes	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
9077	VBoxManage showhdinfo fails on hdd with same uuid as different existing hdd	VirtualBox 4.0.8	2011-06-15T11:01:29Z	2011-06-16T10:33:58Z	2011-06-16T10:33:58Z	"Short story:
{{{
$ /usr/bin/VBoxManage --nologo showhdinfo /tank/vm/admin/osol167_full/osol167.vdi
VBoxManage: error: Cannot register the hard disk '/tank/vm/admin/osol167_full/osol167.vdi' {931723e7-389c-412e-b9b7-2e2e5ac7f88f} because a hard disk '/tank/vm/admin/osol167/osol167.vdi' with UUID {931723e7-389c-412e-b9b7-2e2e5ac7f88f} already exists
VBoxManage: error: Details: code NS_ERROR_INVALID_ARG (0x80070057), component VirtualBox, interface IVirtualBox, callee nsISupports
Context: ""OpenMedium(Bstr(pszFilenameOrUuid).raw(), enmDevType, AccessMode_ReadWrite, pMedium.asOutParam())"" at line 209 of file VBoxManageDisk.cpp
}}}

I don't want to register the hard disk, I just want to know it's UUID.


Long story:

I have running virtual machine. I want to duplicate the machine using zfs snapshot/clone . (reason for this is that it's very fast, lest than second, and occupies no additional space as it uses copy on write). What I have been doing in the past:

 * read hdd's UUID
 * modify hdd's UUID via internalcommand setvduuid/sethduuid
 * read new hdd's UUID
 * edit machine's configuration *.xml so that I replace the old UUID by new UUID.

All this in a script. This has been working with VirtualBox 3.x. After upgrade to latest 4.x it shows the error I'm complaining about.


Possible workarounds:
 * ignore that showhdinfo failed and read the disk's UUID from error message. This is what I'm doing now. I don't like it, as I have hard time distinguishing what is actual error, and what is new behavior.
 * read the disk's uuid from the first machine. That's not very handy for me, as in my case I don't know where the machine is zfs cloned from.
 * change the disk's UUID prior to read it's old value. That's not possible, as in my case I'm cloning machines with several disks attached, and I wouldn't know which disk is which when editing the *.xml later.

I just need to read the disks uuid

Thank you
-- 
  Vlad"	Vladimir Marek
15407	VboxManage slash/backslash handling	VirtualBox 5.0.20	2016-05-11T11:19:45Z	2016-05-11T11:19:45Z	2016-05-11T11:19:45Z	"I use VirtualBox with a Windows host and Windows guest. Still, I find that VBoxManage guestcontrol removes backslashes from various arguments in various sub-commands, but not all. Sometimes forward slashes are the solution, sometimes double backslashes are the solution. 

Please make slash handling the same for all commands and arguments, and preferably allow Windows style CLI when using Windows host and Windows guest and CMD terminal. "	rogierschouten
20301	vboxmanage startvm fails if new Linux Kernel is installed	VirtualBox 6.1.18	2021-04-13T08:09:30Z	2021-04-13T08:09:30Z	2021-04-13T08:09:30Z	"Hello!

I have created a autorun entry 'vboxmanage startvm ""My VM Name""' under Linux Mint 19.3 Cinnamon. Its working fine until a new kernel or kernel update is installed. Then i see a error message that the Kernel Driver loading is failed when the system tries to run the autorun entry. 

I can workaround this issue when I start the VBox GUI and run the VM from there. Next time starting the system my autorun entry works properly again (until next Kernel update...)

Greets
Cody"	Codehunter
11143	vboxmanage startvm fails with E_ACCESSDENIED	VirtualBox 4.2.4	2012-10-29T15:20:41Z	2019-03-31T06:53:20Z	2019-03-31T06:53:20Z	"I upgraded from VirtualBox 4.1.x to 4.2.4 and now I am unable to start VMs from batch files using the command line.

C:\Program Files\Oracle\VirtualBox>VBoxManage.exe startvm b7a6f624-1fe0-43e7-b0ce-75f2de26a80e
VBoxManage.exe: error: The object functionality is limited
VBoxManage.exe: error: Details: code E_ACCESSDENIED (0x80070005), component Machine, interface IMachine, callee IUnknown
VBoxManage.exe: error: Context: ""LaunchVMProcess(a->session, sessionType.raw(),env.raw(), progress.asOutParam())"" at line 580 of file VBoxManageMisc.cpp

I am running the command as the administrator (as I always have).
I am running on a Windows 7 host.

I can start my VMs fine from the GUI, and I can list the VMs and their properties fine from the command line."	Brian
13040	VBoxManage storageattach --medium additions bug	VirtualBox 4.3.12	2014-05-17T09:30:01Z	2022-01-24T22:35:10Z	2022-01-24T22:35:10Z	"VBoxManage storageattach assumes an empty drive when the special case ""--medium additions"" (added by changeset 44131 on 2012-12-14) is used.

In VBoxManageStorageController.cpp:handleStorageAttach, the additions handling code is only executed if GetMediumAttachment was successful.

That means the drive needs to exist (as an emptydrive or with some image already attached) for this special case. If, on the other hand, the user provides the ISO file location, there is no such requirement.

{{{
# this succeeds (path given)
VBoxManage storageattach base --storagectl ""SATA"" --medium none --port 3
VBoxManage storageattach base --storagectl ""SATA"" --type dvddrive --medium /path/to/VBoxGuestAdditions.iso --port 3

# this succeeds (emptydrive created before adding additions)
VBoxManage storageattach base --storagectl ""SATA"" --medium none --port 3
VBoxManage storageattach base --storagectl ""SATA"" --medium emptydrive --port 3
VBoxManage storageattach base --storagectl ""SATA"" --medium additions --port 3

# this fails (complains about missing ""--type"", but that's misleading)
VBoxManage storageattach base --storagectl ""SATA"" --medium none --port 3
VBoxManage storageattach base --storagectl ""SATA"" --medium additions --port 3
}}}

This behavior has been observed on Linux and Windows hosts before being tracked down in the source code (svn checkout as of 2014-05-17).
"	rluethi
13516	VBoxManage stucks on long operations	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
18141	VBoxManage usbfilter add/modify --product does not set value	VirtualBox 5.2.22	2018-11-21T04:03:05Z	2018-11-21T04:03:05Z	2018-11-21T04:03:05Z	"Hi Folks,

Virtualbox 5.2.22 on Ubuntu Linux, but the bug is non-OS specific.

= Issue =

`--product` for `VBoxManage usbfilter add or modify` is not working

{{{
VBoxManage usbfilter \
  add 0 \
  --target ""test"" \
  --name ""SunplusIT Inc Integrated Camera [0010]"" \
  --product ""Integrated Camera"" \
;
}}}

Output in test.vbox
{{{
<DeviceFilter
  name=""SunplusIT Inc Integrated Camera [0010]"" 
  active=""true"" 
/>
}}}

The expected result is
{{{
<DeviceFilter
  name=""SunplusIT Inc Integrated Camera [0010]"" 
  product=""Integrated Camera""
  active=""true"" 
/>
}}}

= Research =

I looked over code in https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Frontends/VBoxManage/VBoxManageUSB.cpp#L405

and it looks that:
{{{
if (!f.mProduct.isEmpty())
  CHECK_ERROR_BREAK(flt, COMSETTER(Product)(f.mProduct.raw()));
}}}

if missing for add/modify cases for global and vm specific cases.
"	anothervboxuser
16684	VBoxManage.exe extpack command exhausts StdOut buffer	VirtualBox 5.1.20	2017-04-21T22:04:06Z	2017-04-24T16:26:10Z	2017-04-24T16:26:10Z	"After having added a license agreement to the extension pack, automating has become quite the challenge. The problem is that the license message hits a 4K limit of the stdout/stderr buffer (which I actually didn't know existed until today).

Consider the following:

%comspec% /C ""C:\Program Files\Oracle\VirtualBox\VBoxManage.exe"" extpack install --replace Oracle_VM_VirtualBox_Extension_Pack-5.1.20-114628.vbox-extpack 1> %temp%\1.txt 2> %temp%\2.txt

.. which should write the entire license agreement into the %temp%\1.txt file. That does not happen, as the output (and VBoxmanage.exe) halts when hitting a 4K limit. My guess is that the message is sent as one big chunck of data, instead of being flushed each line.

(At first I though that it was my VBS script having trouble, as WScript.Shell actually does a have 4K limit with StdOut / StdErr, but the limit seems to exist in the shell itself)

No .. using --accept-license=xyz.. to circumvent the issues isn't an option (at least I think), as Im automating installation for multiple customers. Please have a look at this strange behavior, and let me know what you think."	Schimkat
19278	"Vboxmanage.exe fails when using ""quoted\folder\path\to""vboxmanage.exe"	VirtualBox 6.0.16	2020-01-29T13:51:09Z	2020-01-29T13:51:09Z	2020-01-29T13:51:09Z	"On a Windows 7 host running 5.2.28, and Windows 10 hosts running 6.0.14, and 6.1.2, this vboxmanage command line:


{{{
""C:\Program Files\Oracle\VirtualBox\vboxmanage.exe"" showvminfo ""<vmname>""
}}}


finishes correctly.

This command line:


{{{
""C:\Program Files\Oracle\VirtualBox""\vboxmanage.exe showvminfo ""<vmname>""
}}}


errors out with the vboxmanage full help printout and this error:


{{{
Syntax error: Invalid command '\vboxmanage.exe'
}}}


Note the difference in the command lines:

{{{
""C:\Program Files\Oracle\VirtualBox\vboxmanage.exe"" showvminfo ""<vmname>""  <-- good
""C:\Program Files\Oracle\VirtualBox""\vboxmanage.exe showvminfo ""<vmname>""  <-- bad
}}}

The difference is in where the double-quotes are put after the space-named folder path.
The second command line was made by drag-n-dropping the Virtualbox install folder onto the command window, then adding the backslash and vboxmanage.exe.

These Windows command lines all work: (""calc.exe was copied to the ""test dir"" folder, ""InSpectre.exe"" is a stand-alone 3rd-party exe.)


{{{
""c:\users\snc\test dir\calc.exe""
""c:\users\snc\test dir""\calc.exe
""c:\users\snc\test dir\inspectre.exe""
""c:\users\snc\test dir""\inspectre.exe
}}}


Note that either with the ""\ or \..."", the command lines work.

It appears that Vboxmanage.exe does not parse the command line correctly. "	scottgus1
21148	VBoxManage: error: Invalid command 'hostonlynet'	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
17515	VBoxManager gets into a bad state	VirtualBox 5.2.4	2018-01-31T21:28:23Z	2020-08-19T18:56:17Z	2020-08-19T18:56:17Z	"
simple repro on windows, foo.bat:


    set VBOX=""C:\Program Files\Oracle\VirtualBox\VBoxManage.exe""

    :loop
    %VBOX% controlvm ""%1"" poweroff
    %VBOX% snapshot ""%1"" restorecurrent
    %VBOX% startvm ""%1""

    goto loop


this results in a bunch off issues, including:


VBoxManage.exe: error: The machine 'box' is already locked by a session (or being locked or unlocked)
VBoxManage.exe: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MachineWrap, interface IMachine, callee IUnknown
VBoxManage.exe: error: Context: ""LaunchVMProcess(a->session, sessionType.raw(), Bstr(strEnv).raw(), progress.asOutParam())"" at line 600 of file VBoxManageMisc.cpp


VBoxManage.exe: error: Invalid machine state: PoweredOff (must be Running, Paused or Stuck)
VBoxManage.exe: error: Details: code VBOX_E_INVALID_VM_STATE (0x80bb0002), component ConsoleWrap, interface IConsole, callee IUnknown
VBoxManage.exe: error: Context: ""PowerDown(progress.asOutParam())"" at line 578 of file VBoxManageControlVM.cpp


and eventually it dies:

Progress state: E_ACCESSDENIED
VBoxManage.exe: error: Snapshot operation failed
VBoxManage.exe: error: The object is not ready
VBoxManage.exe: error: Details: code E_ACCESSDENIED (0x80070005), component SessionMachine, interface IMachine
VBoxManage.exe: error: Context: ""enum RTEXITCODE __cdecl handleSnapshot(struct HandlerArg *)"" at line 539 of file VBoxManageSnapshot.cpp
VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error (extended info not available)
VBoxManage.exe: error: Context: ""LaunchVMProcess(a->session, sessionType.raw(), Bstr(strEnv).raw(), progress.asOutParam())"" at line 600 of file VBoxManageMisc.cpp

at this point a full restart of all VBox processes is required.
"	spongman
11517	VBoxSDL error before launching VM	VirtualBox 4.2.6	2013-02-23T11:11:45Z	2019-12-15T12:32:47Z	2019-12-15T12:32:47Z	"In version 4.2.6 under Windows 7 SP1 x64, when trying to start a VM using VBoxSDL, I get the following error (regardless of the VM) :
{{{
SDL Error: 'DirectInputDevice::SetDataFormat: Invalid parameters'
}}}
[[BR]]
It also happens from a freshly created VM :

{{{
C:\Program Files\Oracle\VirtualBox>vboxmanage createvm --name test --ostype Debian_64 --register
Virtual machine 'test' is created and registered.
UUID: 2cbfe35a-fd26-44e3-90a3-9a6e31f406f3
Settings file: 'D:\VMs\VirtualBox\test\test.vbox'

C:\Program Files\Oracle\VirtualBox>vboxsdl --startvm test
Oracle VM VirtualBox SDL GUI version 4.2.6
(C) 2005-2012 Oracle Corporation
All rights reserved.

SDL Error: 'DirectInputDevice::SetDataFormat: Invalid parameters'
}}}
No VBox.log is generated and nothing appears in the VBoxSVC.log."	Max D
6600	VBoxService.exe does not terminate in os/2 guest	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
15963	VBoxSVC continues to run after closing Virtualbox manager / wakes host PC	VirtualBox 5.1.6	2016-09-21T11:14:52Z	2016-09-21T11:41:26Z	2016-09-21T11:41:26Z	"This is how to replicate (on W10 pro v1607):
Start Virtualbox manager
start a vm
put host to sleep
host will wake up , in the system event logs it will show that the system has returned from a lowpower state & that the Wake Source is ""Timer - VBoxSVC.exe""
if you close the virtualbox manager then the VirtualBox interface service (VBoxSVC) continues to run further causing the issue and also causing issues if you shutdown or restart the host (errormessage about active connections)"	Frank Bevers
14191	VBoxSVC crashing, VirtualBox broken in several ways	VirtualBox 4.3.28	2015-06-12T02:58:18Z	2015-06-17T01:39:10Z	2015-06-17T01:39:10Z	"It's tough to explain what's going on, but here's a post I made on the forum which has screenshots and explanations:

https://forums.virtualbox.org/viewtopic.php?f=8&t=68309

Basically everything is broken. I'm unable to add new guests, and the ones I load up act oddly. It would be great if someone could walk me through some debugging/troubleshooting steps. Something is badly broken here, even after a complete uninstall and fresh install."	CaptSaltyJack
14109	VBoxSVC lingering after VBoxWebSrv	VirtualBox 4.3.26	2015-05-12T08:56:39Z	2015-06-23T13:51:58Z	2015-06-23T13:51:58Z	"'''Context'''[[BR]]
Windows 8.1 64 bits
VirtualBox 4.3.26

'''Scenario'''[[BR]]
Without any VirtualBox process already running, start VBoxWebSrv in a prompt in verbose mode, wait for it to start, wait another 2 sec, then press Ctrl+C to quit.
In the Task Manager or via cygwin ps -W, check how long VBoxSVC will remain running before auto shutdown.

'''Issue'''[[BR]]
VBoxSVC remains running for about 6 min then auto exit

'''Expected behaviour'''[[BR]]
VBoxSVC remains running 5-10 sec then auto exit, like when VirtualBox.exe or VBoxManage are run.

'''Detection command in cygwin'''

{{{
while true; do sleep 1; isStarted=1; isFinished=0; while [ $isStarted -ne 0 ]; do sleep 0.5; ps -W | grep -qi vboxsvc; isStarted=$?; done; echo ""VBoxSVC started""; startTime=$(date ""+%s""); while [ $isFinished -eq 0 ]; do sleep 0.5; ps -W | grep -iq vboxsvc; isFinished=$?; done; echo ""VBoxSVC finished""; endTime=$(date ""+%s""); runTime=$(($endTime-$startTime)); echo ""VBoxSVC ran for $runTime seconds""; done;
}}}


'''VBoxSVC average runtime as per the command above'''[[BR]]
367 sec

'''Extra info'''[[BR]]
Behaviour is also visible on Win 7.[[BR]]
Logs & memory dump of lingering VBoxSVC can be found at https://kamax.io/vbox/vboxsvc-lingering_with_vboxwebsrv.zip"	Max D
12780	VBoxSVC.exe crashes on Windows with VBox 4.3.8 when setting VBOX_USER_HOME	VirtualBox 4.3.8	2014-03-05T10:29:38Z	2014-07-01T08:45:29Z	2014-07-01T08:45:29Z	"Unable to set a dedicated different VBOX home path. Virtual Box COM Server is unable to work with new settings.

{{{
C:\Users\dyle>""C:\Program Files\Oracle\VirtualBox\VBoxManage.exe"" --version
4.3.8r92456

C:\Users\dyle>""C:\Program Files\Oracle\VirtualBox\VBoxManage.exe"" list systemproperties
API version:                     4_3
Minimum guest RAM size:          4 Megabytes
Maximum guest RAM size:          2097152 Megabytes
Minimum video RAM size:          1 Megabytes
Maximum video RAM size:          256 Megabytes
Maximum guest monitor count:     64
Minimum guest CPU count:         1
Maximum guest CPU count:         32
Virtual disk limit (info):       2199022206976 Bytes
Maximum Serial Port count:       2
Maximum Parallel Port count:     2
Maximum Boot Position:           4
Maximum PIIX3 Network Adapter count:   8
Maximum ICH9 Network Adapter count:   36
Maximum PIIX3 IDE Controllers:   1
Maximum ICH9 IDE Controllers:    1
Maximum IDE Port count:          2
Maximum Devices per IDE Port:    2
Maximum PIIX3 SATA Controllers:  1
Maximum ICH9 SATA Controllers:   8
Maximum SATA Port count:         30
Maximum Devices per SATA Port:   1
Maximum PIIX3 SCSI Controllers:  1
Maximum ICH9 SCSI Controllers:   8
Maximum SCSI Port count:         16
Maximum Devices per SCSI Port:   1
Maximum SAS PIIX3 Controllers:   1
Maximum SAS ICH9 Controllers:    8
Maximum SAS Port count:          8
Maximum Devices per SAS Port:    1
Maximum PIIX3 Floppy Controllers:1
Maximum ICH9 Floppy Controllers: 1
Maximum Floppy Port count:       1
Maximum Devices per Floppy Port: 2
Default machine folder:          C:\Users\dyle\VirtualBox VMs
Exclusive HW virtualization use: off
Default hard disk format:        VDI
VRDE auth library:               VBoxAuth
Webservice auth. library:        VBoxAuth
Remote desktop ExtPack:
Log history count:               3
Default frontend:
Autostart database path:
Default Guest Additions ISO:     C:\Program Files\Oracle\VirtualBox/VBoxGuestAdditions.iso

C:\Users\dyle>del .VirtualBox
Möchten Sie ""C:\Users\dyle\.VirtualBox\*"" löschen (J/N)? j

C:\Users\dyle>set VBOX_USER_HOME=""C:\Users\dyle\AppData\Local\Temp""

C:\Users\dyle>""C:\Program Files\Oracle\VirtualBox\VBoxManage.exe"" list systemproperties
VBoxManage.exe: error: Failed to create the VirtualBox object!
VBoxManage.exe: error: Code CO_E_SERVER_EXEC_FAILURE (0x80080005) - Server execution failed (extended info not available)
VBoxManage.exe: error: Most likely, the VirtualBox COM server is not running or failed to start.
}}}

I've deleted the ~/.VirtualBox folder in between to start with a new fresh instance.

For us this is a project killer, as I'm unable to work with a dedicated VBox machine and environment path not located at the standard user paths. This sets our project at risk."	dyle71
15879	VBoxSVC.exe prevents logoff	VirtualBox 5.1.4	2016-09-02T18:16:52Z	2018-04-17T20:31:24Z	2018-04-17T20:31:24Z	"If you kill a running virtualbox.exe process, then VBoxSVC.exe would stay running (as it always did) and would prevent logoff/shutdown saying that it ""Has active connections"". That was never the case at least up to VirtualBox 5.1.0. The way to reproduce:
1) start any VM
2) kill the running virtualbox.exe process 
3) try to logoff. 

I can always reproduce the problem (at least) on a Win7 x64 host.
"	mskov
19237	VBoxSVGA OpenGL upsidedown	VirtualBox 6.0.16	2020-01-16T14:42:07Z	2022-02-04T22:13:46Z	2022-02-04T22:13:46Z	"I'm seeing a problem where Photoshop shows images upsidedown when using VBoxSVGA instead of VBoxVGA.

On the forum there are users seeing the same problem with various apps and environments:
https://forums.virtualbox.org/viewtopic.php?f=2&t=92944"	htrex
20759	VBoxTpG: error: Failed to start 'yasm' (assembler): VERR_ACCESS_DENIED	VirtualBox 6.1.30	2022-01-05T17:05:08Z	2022-01-05T17:05:08Z	2022-01-05T17:05:08Z	build error see log file in attach.	custom
16166	vboxusers group disappeared after last update	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
16297	vboxweb and vboxbaloonctrl service scripts depend on 'killall', which is not installed by default on CentOS7	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
18870	vboxwebsrv IPerformanceCollector.queryMetricsData failed.	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
20318	VCPU0: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)	VirtualBox 6.1.20	2021-04-23T07:25:42Z	2021-04-23T07:25:42Z	2021-04-23T07:25:42Z	"Hi,
any help please"	olfat
17982	VCPU0: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)	VirtualBox 5.2.18	2018-09-12T09:53:20Z	2018-09-12T09:53:20Z	2018-09-12T09:53:20Z	"Hello, i have virtual machine with Win 7 Pro x64, on Win 10 x64 host. Last week it was fully functional, but when I started it today it shows me an error VCPU0: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT) and virtual machine stops working. When I start virtual machine in safe mode, it is working fine, but in normal mode don't :(
I' ve attached logs.
Thanks for any advice."	petrsk
20898	VCPU0: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT) during Windows 11 update	VirtualBox 6.1.32	2022-04-11T15:58:00Z	2022-04-11T15:58:00Z	2022-04-11T15:58:00Z	Just got a guru meditation during the update of the Windows 11 in VM. Here are the logs and the picture.	boxer01
17504	VCPU1: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)	VirtualBox 5.2.6	2018-01-27T10:53:10Z	2018-02-05T11:35:34Z	2018-02-05T11:35:34Z	"Upgraded VB on VirtualBox 5.2.6 version.
Run Guest Ubuntu 16.04 host (has not been running/updated for about a month)
Executed ubuntu updates with:

{{{
sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade
}}}

Was unable to create a symlinks in my shared directory.
Executed the following command which was supposed to help:


{{{
VBoxManage.exe setextradata VM_NAME VBoxInternal2/SharedFoldersEnableSymlinksCreate/SHARE_NAME 1
}}}

Then unable to start the Guest machine because of GURU error from the subject."	Faly
21461	ver 7.0.6 failed to install	VirtualBox-7.0.6	2023-02-05T22:17:05Z	2023-02-05T22:17:05Z	2023-02-05T22:17:05Z	"I tried to update Oracle VM from 6.140 to 7.06 155176 WIN and it kept failing because it said I needed Microsoft visual C++ 2019 Redistributable package installed. The program was closed when I tried to update it. 
I never had any issues updating it before.  
I am running windows 10 Pro
I even unistalled the older version but that didn't work. I put the older version back and it is working."	Greg Siemasz
21236	VERR_CR_KEY_FORMAT_NOT_SUPPORTED	VirtualBox-7.0.2	2022-11-02T18:56:30Z	2022-11-03T21:01:05Z	2022-11-03T21:01:05Z	"
{{{
Failed to create cloud client.
Failed to read signing key from ""/home/user/api.pem"": VERR_CR_KEY_FORMAT_NOT_SUPPORTED.
Result Code:
NS_ERROR_FAILURE (0X80004005)
Component:
CloudClientWrap
Interface:
ICloudClient {c2db178a-7485-11ec-aec4-2fbf90681a84}
Callee:
ICloudProfile {b1d978b8-f7b7-4b05-900e-2a9253c00f51}
}}}
"	habakuk
21443	VERR_HGCM_SERVICE_NOT_FOUND vbox 7.0.6	VirtualBox-7.0.6	2023-01-28T19:57:36Z	2023-02-10T09:58:56Z	2023-02-10T09:58:56Z	"After downloading the update for 7.0.6, installed over the top of my version 6. On completion, booted my Fedora guest.  Got to the login.  Entered credentials.  At this point I can only assume that it was connecting to resources and preparing audio and graphics for the desktop. One or two seconds after entering credentials, got an error message that the guest had crashed. The only options were to click OK to terminate the guest or to debug the guest.

Reverted back to 6.1.42, tweaked audio driver from WAS (not sure how that setting made it into the vbox file) to DirectSound (had to do this since it failed to add the guest due to driver error), booted the guest and was just fine."	Kronos1776
7067	VERR_INTERNAL_ERROR: Inexistent host networking interface, named 'vboxnet0'	VirtualBox 3.2.6	2010-06-25T19:52:31Z	2015-01-22T20:48:44Z	2015-01-22T20:48:44Z	"VirtualBox 3.2.x appears to have introduced a bug related to OVF files whereby appliances exported from VirtualBox 3.2.x (on, e.g., a Mac host) no longer import properly on other platforms (e.g., a Windows host).  Specifically, when we export an appliance with VirtualBox 3.2.6 (and 3.2.4) on a Mac 10.6.4 host, we then get this error when trying to start that appliance after importing it on a Windows 7 host running VirtualBox 3.2.6 (and 3.2.4):

VERR_INTERNAL_ERROR: Inexistent host networking interface, named 'vboxnet0'

The appliance we're exporting is configured with two virtual NICs: Adapter 1 is NAT, Adapter 2 is Host-Only.  The above pertains to the latter.

A workaround appears to be, on the Windows host, to remove Adapter 2, then re-add it.  Then the appliance starts.

The problem appears to derive from 3.2.x's introduction of the vbox namespace in OVF files.  When we export an appliance on a Mac host, within the OVF file is this XML element:

<HostOnlyInterface name=""vboxnet0""/>

However, the Windows version of VirtualBox 3.2.x appears to call that interface ""VirtualBox Host-Only Ethernet Adapter"".  It *seems*, then, that, during import, VirtualBox 3.2.x might be relying unduly heavily on the vbox: namespace metadata, inasmuch as Windows expects that host to be called ""VirtualBox Host-Only Ethernet Adapter"" but instead sees it described as ""vboxnet0""?

It's worth noting that removing all XML elements in the vbox: namespace from the OVF file prior to import also fixes the problem.

(A similar cross-platform problem appears to happen with AudioAdapter because of the vbox: metadata.)

Happy to provide additional details as needed."	David J. Malan
14210	VERR_INTERNAL_ERROR_3 when loading custom device plugin	VirtualBox 4.3.28	2015-06-18T14:32:22Z	2015-07-13T11:15:57Z	2015-07-13T11:15:57Z	"Hi folks, I use a custom virtual PCI device plugin. Unfortunately, even though I've signed it with a code-signing key from GoDaddy, VirtualBox 4.3.28 refuses to load my DLL. It gives the following error..

{{{
00:00:03.302562 VMSetError: F:\tinderbox\win-4.3\src\VBox\VMM\VMMR3\PDMLdr.cpp(307) int __cdecl pdmR3LoadR3U(struct UVM *,const char *,const char *); rc=VERR_INTERNAL_ERROR_3
00:00:03.302569 VMSetError: Unable to load R3 module C:\VMs\custom_device.dll (custom_device): : \Device\HarddiskVolume2\VMs\custom_device.dll
00:00:03.429194 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={8ab7c520-2442-4b66-8d74-4ff1e195d2b6} aComponent={Console} aText={Unable to load R3 module C:\VMs\custom_device.dll (custom_device): : \Device\HarddiskVolume2\VMs\custom_device.dll (VERR_INTERNAL_ERROR_3)}, preserve=false
00:00:03.475155 Power up failed (vrc=VERR_INTERNAL_ERROR_3, rc=E_FAIL (0X80004005))
}}}

I've had a look at the source code for VBox and unfortunately this error is returned in many different situations. To make matters worse the pdmR3LoadR3U function obliterates the original error string which makes it impossible to discover the root cause. All you get is ""Unable to load R3 module"", which is about as useful as a chocolate teapot.

Given that the same DLL works with older versions of VBox (prior to the hardening update) and that the DllMain is never called, I have to assume that this error is related to signature verification issues. However, every tool I've tried tells me that my DLL is signed correctly and that the certificate chain is OK."	Kaloth
19412	Verr_io_gen_failure in Windows XP Pro and Win 7 Pro	VirtualBox 6.1.4	2020-03-17T13:50:20Z	2020-03-17T13:50:20Z	2020-03-17T13:50:20Z	"Hello,

i get this Verr_io_gen_failure when i connect a Telenot comXline 3516-1 to the usb port. This happened in Windows XP Pro and Windows 7 Pro.
I see no possiibility to connect the Telenot to the guest systems.

I tried all i can, the usb filter is set right. I tried different settings in the filter.

The usb filter generally works perfect, exept the Telenot conection :("	alsk1
18536	VERR_NEM_VM_CREATE_FAILED with Win10 10.0.18362	VirtualBox 6.0.4	2019-04-02T20:26:38Z	2019-08-25T01:21:31Z	2019-08-25T01:21:31Z	"dear oracle team,

no matter which bios settings or windows settings (hyper-v on off, virtualization on off, sandbox on off, all windows additional functions on (normal) or off) I think I get this error: VERR_NEM_VM_CREATE_FAILED

I do not know any more and hope for your support. here is an inserted log to my normal settings.

Yours sincerely
roman prosek

sehr geehrtes oracle team, 

egal welche bios einstellungen oder windows einstellungen (hyper-v an aus, virtualisation an aus, sandbox an aus, alle windows zusatz funktionen an (normal) oder aus) ich vornehme ich bekomme diesen fehler: VERR_NEM_VM_CREATE_FAILED 

ich weis nicht mehr weiter und hoffe auf ihre unterstützung. hier noch ein eingefügter log zu meinen normalen einstellungen.

mit freundlichen grüßen 
roman prosek
"	supra
19007	VERR_PGM_HANDLER_NOT_FOUND	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
16878	VERR_SUP_VP_EXE_VS_PROC_NAME_MISMATCH error on Windows 10	VirtualBox 5.1.22	2017-07-06T02:31:12Z	2018-01-04T11:44:53Z	2018-01-04T11:44:53Z	"Hello

I keep getting the above mentioned error when I start a guest. I remove and reinstall VirtualBox and the error goes away, but after a few days it comes back again (usually after a restart of my PC). I am attaching the screen shot of error box and VBoxHardening log. A shorter error message is below:


{{{
Failed to open a session for the virtual machine Ubuntu-16.04.

The virtual machine 'Ubuntu-16.04' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\arshad.khan\VirtualBox VMs\Ubuntu-16.04\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
}}}


Any help is greatly appreciated.

Thanks
Arshad"	arshad01
20693	VERR_VERSION_MISMATCH in VBoxExtPackRegister on 6.1.30	VirtualBox 6.1.30	2021-11-26T09:00:39Z	2021-12-01T15:14:02Z	2021-12-01T15:14:02Z	"After upgrading to 6.1.30, I can't install the matching Extension Pack on macOS Monterey (12.0.1)


{{{
VBoxExtPackRegister returned VERR_VERSION_MISMATCH, pReg=0000000000000000 ErrInfo='Helper version mismatch - expected 0x3 got 0x30000'.


Result Code: 
NS_ERROR_FAILURE (0x80004005)
Component: 
ExtPackManagerWrap
Interface: 
IExtPackManager {70401eef-c8e9-466b-9660-45cb3e9979e4}

}}}

The culprit seems clearly visible in the error message: 0x3 vs 0x30000"	rgaudin
20975	VERR_VMX_VMXON_FAILED during install of CentOS 7	VirtualBox 6.1.34	2022-06-08T23:22:16Z	2022-06-08T23:22:16Z	2022-06-08T23:22:16Z	While installing CentOS 7 VM failed with VERR_VMX_VMXON_FAILED and  NtOpenDirectoryObject failed on \Driver: 0xc0000022. Unable to restart VM. 	Tony_Z
15744	Version 5.1.2 Machine Wrap Error	VirtualBox 5.1.2	2016-08-04T08:22:59Z	2016-08-17T11:09:08Z	2016-08-17T11:09:08Z	"I am currently using version 5.0.26, I have tried upgrading to version 5.1.2 but it never starts, I always get a ""Machine Wrap"" error.

Result Code: 
E_FAIL (0x80004005)
Component: 
MachineWrap
Interface: 
IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
"	Solrac42
18809	Version 6.0 - Scale	VirtualBox 6.0.10	2019-08-03T13:24:35Z	2019-08-04T14:57:59Z	2019-08-04T14:57:59Z	"The view mode is all messed up.  No matter what I change to, all of the icons either grow or shrink into a water mess when moving the mouse cursor.  The windows taskbar is no where to be seen.  No changes have been done to my VMs other than installing the new 6.0 version.

Guest system is a Windows machine
Host is the latest MAC OS.

"	Mordy
20649	Version 6.1.97 r147979 for Win 11	VirtualBox 6.1.28	2021-11-04T20:44:44Z	2021-11-04T20:44:44Z	2021-11-04T20:44:44Z	"Unfortunately, VBoxGuestAdditions.iso cannot be installed. After the installation and restart, Win11 can no longer be started in the VM. Win11 tries to repair itself, but brings up the message that no repair is possible. There is no other option than to delete the VM and set it up again, including reinstalling Win11.
Unfortunately, the screen resolution and other things cannot be set without the GuestAddition. The Win11 installation cannot really be used on the VM.
Can you help me?"	icewater
19809	Very bad latency numbers with more than 1 vCPU	VirtualBox 6.1.10	2020-08-12T23:22:25Z	2020-08-13T22:11:28Z	2020-08-13T22:11:28Z	"VirtualBox 6.1.12 verified on Win10 host (or openSUSE TW host), with Linux guests Ubuntu 16/18 or openSUSE TW.

Basically, I have distilled this down to a small perl script, that sleeps for 1ms for 1000 times.  Ideally, this would be 1000ms total -- but on real hardware, the script takes just a shade under 1100ms per iteration (perl overhead, etc), and when VirtualBox is behaving, about 1350-1425ms per iteration.

On real hardware, 100% of 1ms sleeps are <2ms.  When VirtualBox is behaving, 99% of 1ms sleeps are <2ms, and the upper bound is around 10-15ms for a few outliers.

The problem is when vCPU is 2+ ... the more added, the worse latency gets.  1ms sleeps start taking 100ms, 300ms, 500ms, occasionally even 900ms to return."	JasonM
19607	Very high energy consumption by 6.1.8 on Mac OS X	VirtualBox 6.1.8	2020-05-20T17:26:02Z	2020-05-22T14:52:01Z	2020-05-22T14:52:01Z	"With 6.1.8 on MacOS I'm was seeing very high energy consumption, so much so that my battery level was dropping despite being plugged in. I had to downgrade to 6.1.6.
"	tg7747
18998	Very laggy performance on MacOSX Mojave host caused display scaling setting	VirtualBox 6.0.12	2019-10-10T04:58:59Z	2019-10-10T05:02:50Z	2019-10-10T05:02:50Z	"Host: MacOSX Mojave 10.14.6
Guest: Windows 10 Pro
VirtualBox: 6.0.12 r133076 (Qt5.6.3)

On host if set display scale to smaller font and set scale to 200% or 300% then guest Windows OS going very slow. If I click button h then it printing hhhhh. 
I set host's display setting to biggest font scale and VB scale to 100% then it is working better."	Almas
18108	Very poor performance on iMac 2017 5K	VirtualBox 5.2.20	2018-11-05T20:06:31Z	2018-11-05T22:42:10Z	2018-11-05T22:42:10Z	IiMac 2017, 27 inch, 5K, 32 GB RAM. It is impossible to work properly on virtual machines. The virtual machines are Windows 10, Windows 7 and Windows XP. All systems run badly.	macjacke
12382	Very slow guest OS performance when Windows XP Guest guest has more than 1 VCPU	VirtualBox 4.3.2	2013-11-21T14:15:55Z	2016-11-20T11:10:30Z	2016-11-20T11:10:30Z	"My hardware and software configuration is mentioned in bug 12381.

When I enabled more than 1CPU for my guest OS, it becomes extremely slow - my favorite test is when I simply run mspaint.exe from Win + R dialog.

When I have just one VCPU enabled, mspaint runs inconstantly.

When I have two or more VCPUs enabled, mspaint takes two full seconds to start.

The guest OS is ''completely'' (!) idle - I have no active applications running, the Windows Update service is disabled altogether."	Artem S. Tashkinov
20777	Very slow guest VMs in 64-bit Windows (10 & 11) hosts after upgrading VirtualBox v6.1.30 to v6.1.32.	VirtualBox 6.1.32	2022-01-19T09:50:38Z	2022-03-09T15:47:55Z	2022-03-09T15:47:55Z	https://forums.virtualbox.org/viewtopic.php?f=6&t=104993&p=512044 for my forum thread with our details, logs, etc. Basically, our guest VMs are unusable due to being very slow.  We had to downgrade back to v6.1.30 to reuse them. :(	Ant
18011	Video capture doesn't work after upgrade from 5.1.38 to 5.2.18	VirtualBox 5.2.18	2018-09-26T09:53:53Z	2018-09-30T03:22:51Z	2018-09-30T03:22:51Z	"Hello, I upgrade virtualbox from 5.1.38 to 5.2.18 in macOS，When I select video capture, the logo in circling as usual，but when I select the video capture menu to stop record, virtualbox accidental exit, and report error logs:

Process:               VirtualBoxVM [2415]
Path:                  /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM
Identifier:            org.virtualbox.app.VirtualBoxVM
Version:               5.2.18 (5.2.18)
Code Type:             X86-64 (Native)
Parent Process:        VBoxSVC [2398]
Responsible:           VirtualBoxVM [2415]
User ID:               501

Date/Time:             2018-09-26 17:53:06.105 +0800
OS Version:            Mac OS X 10.14 (18A391)
Report Version:        12
Anonymous UUID:        C4C75F89-7917-7BF9-E78F-33B91F94813E

Sleep/Wake UUID:       675035FF-A6C2-4DF2-989F-A72F323ED416

Time Awake Since Boot: 29000 seconds
Time Since Wake:       3300 seconds

System Integrity Protection: enabled

Crashed Thread:        4  nspr-2

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Segmentation fault: 11
Termination Reason:    Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [2415]"	liuqunrui
13806	Video capture in Linux does not work (small file with empty green .webm video)	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
16031	Video capture on 4K monitors is broken; bitrate too low producing blurry video	VirtualBox 5.0.26	2016-10-05T09:43:47Z	2016-10-06T10:21:44Z	2016-10-06T10:21:44Z	"Host: Win 10, VBox 5.0.26, 1 monitor

Guest: Win 10, 1 monitor 

Steps to reproduce: 
1. Requirements: one display with 4K / Ultra HD resolution (3840x2160)
2. Setup video capture in your guests; Currently it's limited to 2880x1800 resolution and a joke bitrate of 2 Mbps.

Expected results:
1. Video capture must support max. resolution of 4K (3840x2160) -and- 60 FPS -and- *much* higher bitrate.
2. Bitrate table recommendations: 2 Mbps for HD 720p (1280x720) or 2.5 Mbps per Megapixel. 5 megapixel for FullHD (1920x1080), 20 megapixels for UltraHD (and 40 megapixels for UltraHD-at-60 FPS.)

You need to double the maximums for high quality rendering of text and for 60 fps and double bitrate again due to real-time encoding (which is much less accurate than slow video encoding).
My suggestion is to allow for a 80 Mbps video capture. (at any resolution).

-Technologov, 5.10.2016. "	Technologov
13073	Video Captures are Blank / Green	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
8332	Video controller VirtualBox guest additions 4.0.2 don't work with windows 2003 /3GB switch enable	VirtualBox 4.0.2	2011-02-13T05:09:14Z	2014-09-03T14:41:26Z	2014-09-03T14:41:26Z	"Windows 2003 SP2 32bits work fine with VirtualBox guest additions, but when enable /3GB switch video only supports lowest color profile (4 bits) and 640x480 resolution.

Unistall VirtualBox additions and video works again with /3GB switch enable"	Sistemas
13870	Video driver for Windows 10 is turned off	VirtualBox 4.3.22	2015-02-20T07:14:21Z	2015-02-23T14:38:17Z	2015-02-23T14:38:17Z	"Система Windows остановила это устройство, так как оно сообщило о возникновении неполадок. (Код 43)

Windows is stopped this device because it has reported problems. (Code 43)"	ruslandh
18323	Video Memory Expanding to 256 MB Fail	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
14348	Video playback freezes in Linux guests with KVM paravirtualization enabled	VirtualBox 5.0.0	2015-07-30T00:49:30Z	2016-09-15T11:36:18Z	2016-09-15T11:36:18Z	When KVM paravirtualization is enabled in VirtualBox 5.0.0 Linux guest operating systems fail to playback video. This is apparent with all video tested, including web video using Flash or HTML5. This has been tested on Antergos, Mint 17.2, and Fedora 22. Host Operating systems used to confirm this bug were Windows 8.1 and Windows 10.	Markon101
20371	Video recording settings not saved	VirtualBox 6.1.22	2021-05-19T09:15:39Z	2022-07-28T19:33:56Z	2022-07-28T19:33:56Z	"It seems that video recording settings of VMs are not saved. At least this is true for file path and frame size. Leaving VirtualBox Manager and restarting it, video recording settings are back to default.

In the .vbox file of the VM, I found the entry VideoCapture never reflecting these settings.

Maybe this is related to [ticket:20297], because depending on the modification history of video recording settings I experience the same crash. "	Reiner Brodbeck
17349	VINF_EM_TRIPLE_FAULT	VirtualBox 5.2.0	2017-12-05T22:41:28Z	2017-12-07T02:13:13Z	2017-12-07T02:13:13Z	"I get guru meditation immediately after the Virtualbox BIOS screen and the log says VINF_EM_TRIPLE_FAULT. This is in a guest machine where I just freshly installed RHEL 7.4 64 bit running on Windows 7 64 bit host. The guest started to boot the first start after I installed RHEL but triple fault occurred before boot finished. Every other boot gets triple fault immediately after the Virtualbox BIOS screen. I see lots of other triple fault bugs but none for Red Hat.

Error occurs on latest stable and latest testing builds

Stable
VirtualBox-5.2.2-119230-Win.exe

Testing
Version 5.2.3 r119405 (Qt5.6.2)"	ke
16812	VINF_EM_TRIPLE_FAULT (Win 10 guest on Linux Mint 18.1)	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
19622	VINF_EM_TRIPLE_FAULT on Server 2019 initial boot and install	VirtualBox 6.1.8	2020-05-25T19:14:15Z	2021-06-19T20:03:18Z	2021-06-19T20:03:18Z	VT-v enabled in host bios, attempted with guest efi enabled as well as disabled. Host Hyper-V platform disabled. After parsing the logs with an untrained eye, it looks as if it might be an issue with the cpu. Attempted with 1, 4 and 8 threads allocated, and 4gb and 8gb memory allocated. 	moumoku
19456	VINF_EM_TRIPLE_FAULT when starting Ubuntu 16.04 on Win10 2004	VirtualBox 6.1.4	2020-04-02T12:00:21Z	2020-04-02T12:50:53Z	2020-04-02T12:50:53Z	"Win 10 2004 host, with Hyper-V enabled
VBox 6.1.4
Fresh Ubuntu Server 160406 64-bit install
Ubuntu boots and then ""hangs"" during the boot process
Intermittently, not always, it will throw a VINF_EM_TRIPLE_FAULT when this happens
Played around with various system / processor settings, no change. Reverted to defaults."	yorickdowne
19871	virtio-nic has been removed?	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?	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_
19601	virtio-scsi issue feedback	VirtualBox 6.1.8	2020-05-19T02:33:31Z	2020-05-19T02:33:31Z	2020-05-19T02:33:31Z	"1. virtio-scsi controller install windows 10, vioscsi driver can't detect HDD.
2. eject iso, the virtualbox abnormal exit."	sakurayz
20573	Virtio-scsi shows HDD instead of SSD Virtualbox 6.1.97 r146677	VirtualBox 6.1.26	2021-09-22T18:04:45Z	2022-11-30T12:05:42Z	2022-11-30T12:05:42Z	"Issue:
in Virtualbox 6.1.97 r146677 I've set Virtio-scsi as disk and flagged it as Solid State Drive inside Virtualbox, however Windows 10 x64 Enterprise sees it as HDD...
(Yes the latest virtio drivers are installed in Windows 10)

[[Image(https://forums.virtualbox.org/download/file.php?id=44340)]]
[[Image(https://forums.virtualbox.org/download/file.php?id=44341)]]

Operative System:

Host  - Fedora Workstation 34 x64
Guest - Windows 10 x64 Enterprise

Virtio Drivers version: 2021-09-13 05:07
From:
https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.208-1/


How to reproduce:
create a virtual machine and install Windows 10 x64 using IDE or Sata.
Install the Virtualbox guest additions.
Insert an empty Virtio-scsi disk and install the virtio drivers.
Shut down the Virtual Machine.
Change the IDE or Sata disk to Virtio-scsi and flag ""Solid State Drive"" in the Virtualbox UI.
Boot the Windows 10 x64 VM.
Open the Task Manager Windows and it will show HDD."	FranceBB
17199	Virtual appliance of Debian Stretch 32 bit fsails to boot on a native  64 bit	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
13669	Virtual Box 4.3.20 stuck on creating process for virtual machine	VirtualBox 4.3.20	2014-12-04T07:15:16Z	2019-03-14T16:03:24Z	2019-03-14T16:03:24Z	"Hi,
I have updated my Version from 4.3.12 to 4.3.20. since then I can´t start the VM. I stuck in creating process in Virtual Machines.
As Antivir I am using Symantec. 
My Host is Windows 7 64 bit Enterprise and the VM is a Win 7 32-bit
"	cyberoner1
16087	Virtual Box 5.0.28 prevents Windows 7 Guests from Opening	VirtualBox 5.1.8	2016-10-20T10:07:34Z	2016-10-20T10:07:34Z	2016-10-20T10:07:34Z	"i upgraded VirtualBox  5.0.26 to 5.0.28 on my MacPro Host running macoSiera.
No problem opening my Oracle Linux guest VM s but my 2 Windows 7 64 bit guest VMs failed to open.

I tried removing the Windows VMs and the files and copying over clean backups i maintain however the same Abort error always appeared when i tried to start the Windows machines.

I reinstalled version 5.0.26 Virtual Box and i have no problem opening the Windows 7 guests

I have attached a file with the complete error dump and state of my machine

The VM session was aborted.

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: SessionMachine
Interface: ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}




Failed to open a session for the virtual machine Windows7x64_03

Process:               VirtualBoxVM [782]
Path:                  /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM
Identifier:            org.virtualbox.app.VirtualBoxVM
Version:               5.0.28 (5.0.28)
Code Type:             X86-64 (Native)
Parent Process:        VBoxSVC [776]
Responsible:           VirtualBoxVM [782]
User ID:               501

Date/Time:             2016-10-20 11:01:53.125 +0200
OS Version:            Mac OS X 10.12 (16A323)
Report Version:        12
Anonymous UUID:        FE311170-EE45-253B-B0E6-8B3C837663FC

Crashed Thread:        32  CAQUEUE

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x00000001202bc64b
Exception Note:        EXC_CORPSE_NOTIFY

Model: MacBookPro11,3, BootROM MBP112.0138.B17, 4 processors, Intel Core i7, 2.6 GHz, 16 GB, SMC 2.19f12
Graphics: Intel Iris Pro, Intel Iris Pro, Built-In
Graphics: NVIDIA GeForce GT 750M, NVIDIA GeForce GT 750M, PCIe, 2048 MB
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x02FE, -
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x02FE, -
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x134), Broadcom BCM43xx 1.0 (7.21.171.10.1a16)
Bluetooth: Version 5.0.0f18, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
PCI Card: pci1b21,612, AHCI Controller, Thunderbolt@194,0,0
Serial ATA Device: APPLE SSD SM1024F, 1 TB
Serial ATA Device: ST6000DX000-1H217Z, 6 TB
USB Device: USB 3.0 Bus
USB Device: Apple Internal Keyboard / Trackpad
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
Thunderbolt Bus: MacBook Pro, Apple Inc., 17.1
Thunderbolt Device: d2 TBT2 USB3, LaCie, 3, 24.3"	dba789
18777	Virtual Box 6 Crashes Windows due to Network device error	VirtualBox 6.0.10	2019-07-21T17:30:37Z	2019-07-21T19:34:54Z	2019-07-21T19:34:54Z	I run a vitural XP session and within 3 minutes of opening the VM, Windows crashes with this error: (see picture)[[Image()]]	wjones40
21307	Virtual Box 6.1.40 r154048(Qt5.6.2) freezing	VirtualBox 6.1.40	2022-11-24T00:20:32Z	2022-11-24T10:05:03Z	2022-11-24T10:05:03Z	I recently upgraded VM to the summary version. Subsequently I have had guest system freezes at random times, usually when idle. I am running Linux LinuxMint 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux. I had on problems with previous versions.  Log should be attached.	Aiki451
21270	VIRTUAL BOX 7.0.2  Bug	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
18306	Virtual box causes the PC to restart many times	VirtualBox 6.0.0	2019-01-13T01:55:44Z	2019-01-14T19:15:28Z	2019-01-14T19:15:28Z	"Since one year ago I observed that my PC, when left in stand-by, restarted continuously at night after 2.00 p.m.. 
After many attempts I verified that whenever VirtualBox was open, this continuous restart happened. When it was closed, it did not. 

Recently, I upgraded to VB 6.0 and tried again: same result.

I've observed this behaviour n two different PCs, both using up-to-date Windows 10 64 bit."	ceraolo
15059	Virtual box crash when host pc reboots	VirtualBox 5.0.14	2016-01-21T11:33:32Z	2016-01-21T14:17:55Z	2016-01-21T14:17:55Z	"tested using 5.0.14 on W7 / 64 , W10 32 & 64 bit.
Start Virtualbox, do not start any vm in virtual box
Reboot the host PC
Virtual box will stop the host pc from booting

The first error being displayed is ""Failed to set the global Virtualbox extra data for key GUI/Toolbar to value {}""

"	Frank Bevers
18848	Virtual box crashes MacOS Mojave	VirtualBox 6.0.10	2019-08-17T04:37:57Z	2019-08-19T07:01:38Z	2019-08-19T07:01:38Z	"MacOS crash when I start a vm on Virtual Box.

Mac 
  cpu is 2.4 GHz Intel Core i9.
  DDR4
  macOs Mojave  10.14.5

vm Guset OS
  CentOS-7-x86_64-DVD-1810
  installed as  DataServer

"	iwweyl
17538	Virtual Box displays black screen	VirtualBox 5.2.6	2018-02-11T22:31:28Z	2018-02-12T11:31:18Z	2018-02-12T11:31:18Z	I have been using Virtual Box for a class I am in for college. The other day I tried to bring up my Virtual Box VM program and only had a black screen. I have attached a picture showing what my screen has. It just sits there and not doing anything. I have loaded up a new OVA file for my VM program and still get same thing. What can I do to fix this or what is causing this. I have been using Virtual Box and this program for about 4 weeks now.	fuzzwuzzy13
17102	Virtual Box does not list Virtual USB device (created by fallocate)	VirtualBox 5.1.28	2017-09-20T21:46:46Z	2017-09-20T21:54:18Z	2017-09-20T21:54:18Z	"As previously i was not able to install Mac OS Sierra from iso, i was keen to try again because of https://www.virtualbox.org/ticket/16644#comment:21, after i have seen that it's now supported by 5.28. It's not even mentioned in the change log anyway.

The cdr.dmg image, what i have created shown not supported format. (even if the dmg is supported file format - the created iso from that was starting up, but hanging at some point - it hasn't been solved, when i tested again)

I have realized that i can make an official USB installer on Mac,
that i don't need to hack dmg and iso, but i haven't 8GB USB stick.

So i created a virtual usb with fallocate and mounted successfully (i can write on that disk with normal user), unfortunatelly it's not been listed by VBoxManage list usbhost.

Either way even if i try this with mac, it's a basic problem, it does not work even with ubuntu guest.

Other problem is that when i added my integrated camera (it's listed as USB device), it's starting up, but makes a blank screen on Mac OSX. (10.12.6 - Sierra)"	raxim
20058	Virtual Box encounters error while Ubuntu 20.04 VM is running	VirtualBox 6.1.16	2020-11-22T23:49:02Z	2020-11-22T23:49:02Z	2020-11-22T23:49:02Z	I can't give an idea on how to reproduce it as it happenend as i was just browsing, was idle in a programm or was just starting it, tabbed out while waiting for it to be done and seeing the error message roght after boot was done.	zandatsu
18336	Virtual Box Extension Pack 6.0.0 Installation Error	VirtualBox 6.0.0	2019-01-19T13:49:22Z	2019-01-20T08:10:14Z	2019-01-20T08:10:14Z	"Every time I update VirtualBox and install extension pack I got an error message.In previous update when I update VirtualBox to 6.0.0 and then I install Extension Pack I got the same error message.
I have detailed video link of this error message on youtube:- https://youtu.be/orHQHsoe6NY

Can any one help me?"	Binoy
18774	Virtual Box is causing random host reboots	VirtualBox 6.0.10	2019-07-19T13:01:56Z	2019-07-20T15:39:34Z	2019-07-20T15:39:34Z	When I turn on three virtual machines windows 7, windows vista, windows 8.1 pro my computer just reboots after 10 minutes. When I only run Windows 8.1 pro I get a BSOD system service exception error. Also, in vmware that happens. Hyper-V on my computer was disabled and also Virtualization Based Security in Device Guard was disabled. Can anyone help me with this?	obedyaw
20800	Virtual Box Machine fails on startup	VirtualBox 6.1.32	2022-01-31T16:52:10Z	2022-01-31T16:52:10Z	2022-01-31T16:52:10Z	"Exactly as Ticket #19282

message:
------------------------------------------------
Échec de l'ouverture de session pour la machine virtuelle W10-V.

The virtual machine 'W10-V' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\Administrateur\VirtualBox VMs\W10-V\Logs\VBoxHardening.log'.

Code d'erreur : E_FAIL (0x80004005)
Composant : MachineWrap
Interface : IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}
-----------------------------------------------------------

To solve the problem, I had to uninstall '''Trusteer Endpoint Protection by IBM''' as suggested in the aforementioned ticket"	Malbec
18160	Virtual Box machines fail to start after migration from Win7 to Win10	VirtualBox 5.2.22	2018-11-30T12:33:32Z	2018-11-30T14:31:46Z	2018-11-30T14:31:46Z	I upgraded to Windows 10, turned off hyper-v, rebooted, etc.: I can create new 64bit machines, I can run rescue disk .iso in them but existing machines fail to start.	aivarsk
17669	Virtual Box not saving Default Machine Folder after closing app	VirtualBox 5.2.8	2018-04-06T03:55:38Z	2018-04-06T03:55:38Z	2018-04-06T03:55:38Z	The version of VBox I have is 5.2.8. I have Windows 10 as my host. I have an SSD as my C drive and a HDD as my D drive. Both internal drives. When I go to file-> Preferences->Default Machine Folder->Other and select a folder on my D drive. It changes. However, when I close the application, all the preferences revert back to the default, and the VMs that were save to the D drive are removed from the main list of VMs.	Joe5232
18043	Virtual box starts up in the background	VirtualBox 5.2.18	2018-10-11T07:55:54Z	2018-10-11T08:58:33Z	2018-10-11T08:58:33Z	"I have tree different locations/workplaces with different monitor setup using dockingstations.
on two of the locations virtualbox won't start so it is visible. 
I can see it virtualbox is active in the background and first thought is that it didn't double click 
and endend up starting it several times in the background.
However i found out can disconnect the dockingstation 
and virtualbox startup/is visible on my screen.
Now i can connect the dockingstation again and work with virtualbox.
Anyway to avoid this behavior?
"	Carevad
20911	Virtual box unable to start VM failing with error (rc=-5640)	VirtualBox 6.1.32	2022-04-23T09:11:32Z	2022-04-23T09:11:32Z	2022-04-23T09:11:32Z	"(rc=-5640)
Please try reinstalling VirtualBox.
where: supR3HardenedWinReSpawn what: 1
VERR_SUP_VP_THREAD_NOT_ALONE (-5640) - Process Verification Failure: The process has more than one thread."	Prateek DA
16821	Virtual Box won't load existing or new VMs	VirtualBox 5.1.22	2017-06-08T13:52:02Z	2017-06-08T14:00:52Z	2017-06-08T14:00:52Z	"Hi,

For the last week I've been having an issue where Virtualbox is refusing to load VMs and gives an error whilst creating the process.

It was working perfectly fine and suddenly this problem has started appearing.

Please check attached documents.

I'm running a W7x64 Host."	jdoe3618
17789	Virtual computer failed to start	VirtualBox 5.2.8	2018-05-30T13:36:22Z	2018-05-30T14:21:39Z	2018-05-30T14:21:39Z		zhangwei01
18896	Virtual hard disk UI often discards decimal point	VirtualBox 6.0.10	2019-09-02T19:45:49Z	2019-09-02T23:09:50Z	2019-09-02T23:09:50Z	"When specifying values such as ""1.95 GB"", the virtual hard disk UI tends to silently drops the period, resulting in ""195 GB""."	mcandre
18320	Virtual Hard Disk wizard defaults to file size less than recommended for Ubuntu 18	VirtualBox 6.0.0	2019-01-17T00:28:43Z	2019-01-19T20:51:09Z	2019-01-19T20:51:09Z	"Using VirtualBox 6.0.0 r127566 (Qt5.6.2) on host Windows 7 SP1 amd64.

I am creating a new VM using the GUI wizard. The Create Virtual Machine wizard detects I am intending to install Ubuntu and set the ""Version"" to ""Ubuntu (64-bit)"". The Virtual Hard Disk wizard defaults to a 10GB hard disk.

The download page for Ubuntu 18 (Desktop) at https://www.ubuntu.com/download/desktop suggests 25Gb of free hard drive space.

"	Adam Piggott
15374	Virtual HDD becomes unavailable for guest : with AHCI#0: Port x reset	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
19551	Virtual Machine can not start	VirtualBox 6.1.6	2020-05-03T18:01:39Z	2020-09-04T14:39:12Z	2020-09-04T14:39:12Z	"Hi,

After Virtual Box upgrade to 6.1.6 r137129 (Qt5.6.2) many machines stop to work. Virtual BOX and Guest Aditional upgrade were performed fine. But after few days, in some VMachine the screen stay black after the power on. The issue happened in some WINDOWS10 and FEDORA Virtual Machine, but not on all.

I tried to uninstall and install VIRTUAL BOX but the black screen issue is still present. The only solution is delete and create the Machine from scratch.

Could some one help me to debug the issue to understand why it is happen?"	Ivan_70
20582	Virtual Machine cannot be started with Linux host kernel 5.14	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
19554	Virtual machine closes unexpectingly	VirtualBox 6.1.6	2020-05-04T16:09:37Z	2020-10-05T15:45:46Z	2020-10-05T15:45:46Z	"I use BirtualBox 6.1.6 r137129 (Qt5.6.1) under Linux Sabayon 64 bit (up to date) with KDE:

Operating System: Gentoo Linux 
KDE Plasma Version: 5.18.4
KDE Frameworks Version: 5.69.0
Qt Version: 5.14.1
Kernel Version: 5.4.0-sabayon
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7 CPU 920 @ 2.67GHz
Memory: 23,5 GiB of RAM

The guest is KDE Neon also up to date, for KDE development.

When I switch to KRDC, after an undetermined time, the guest is closed unexpectingly.

"	----------
14886	Virtual Machine crash	VirtualBox 5.0.10	2015-12-02T15:24:59Z	2015-12-03T11:46:39Z	2015-12-03T11:46:39Z	"After several hours of working on mac os x virtual machine with installed ubuntu 12.04 server crashed.
Crash is stable 2-3 time during working day."	grustem7
17142	Virtual machine crashed while installing IBM Maximo	VirtualBox 5.1.28	2017-10-05T18:18:29Z	2017-10-06T09:13:04Z	2017-10-06T09:13:04Z	"I'm hoping somebody can help me figure out this problem. I created a Windows 2012 Server as a guest and tried to install IBM Maximo and the VM crashed.  The log and png file are attached.

I am using VirtualBox v5.1.28 on a older Windows 7 system with 32Gb of RAM."	Al Menendez
21123	Virtual machine crashes while installing the Guest addons	VirtualBox 7.0.0	2022-10-10T23:40:16Z	2022-10-12T21:19:15Z	2022-10-12T21:19:15Z	"I've just installed v7.0, however, while installing the guest additions, the machine crashes.

Specifically:

- I was using a machine created with v6.1; in general, it works fine also on 7.0 - the crash happens specifically while installing the guest additions
- The host is Ubuntu 20.04 (with a 5.19 kernel), the guest is Windows 10
- I've enabled 3D acceleration on the host, and set 256 MB of video memory
- The machine crashes when the video blips for a moment (I presume that in that moment, the guest O/S is switching the video driver)
- There is nothing seemingly relevant in the VB log, however, the crash is visible in the syslog (attached)"	sap239048
21044	Virtual Machine does not open VMDK-file from VMWare	VirtualBox 6.1.36	2022-08-02T18:10:21Z	2022-08-08T19:07:35Z	2022-08-08T19:07:35Z	"On a MacBook Pro with Monterey 12.4, a virtual machine (*.vmdk) was created by an installation of VMWare Fusion Player. The guest system is Windows 7. The MacBook Pro has an Intel i7-processor.

The vmdk was copied to a Linux-notebook with Tuxedo 1.1.5 (an Ubuntu-derivate) with VirtualBox 6.1.36. This computer has an AMD Ryzen 7-processor.
A session was created for the vmdk along https://medium.com/riow/how-to-open-a-vmdk-file-in-virtualbox-e1f711deacc4. 
VirtualBox started the vmdk, tried to start the guest system but failed: It tried to repair Windows unsuccessfully. 
Using ""VBoxManage clonehd --format VDI mySource.vmdk myTarget.vdi"", the vmdk was converted into a vdi-file. Same problem: Start-up of Windows failed, repair failed.

VirtualBox was installed on the MacBook and a session was created for the vmdk as above. Same problem: Start-up of Windows failed, repair failed.

After reading that on Linux the VirtualBox-Extensions were missing, installed the current version 6.1.36. Now, VirtualBox does not even start the vmdk or vdi, but writes an error message (my translation):

Für die virtuelle Maschine XXX konnte keine neue Sitzung eröffnet werden.
(No new session could be created for the virtual machine XXX.)
The VM session was aborted.

Fehlercode: NS_ERROR_FAILURE (0x80004005)
Komponente: SessionMachine
Interface: ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}

According to the manual, a vmdk should be opened an run easily? "	nachtkrabb
20670	virtual machine does not start	VirtualBox 6.1.28	2021-11-17T01:02:14Z	2021-11-20T08:32:38Z	2021-11-20T08:32:38Z	Version 6.1.28 r147628 (Qt5.6.2)	altair_kusanagi
20192	Virtual Machine does not start on M1 Mac	VirtualBox 6.1.18	2021-02-15T15:03:13Z	2021-02-27T12:08:53Z	2021-02-27T12:08:53Z	"Device: MacBook Pro 13-inch, 2020, M1

Software: macOs 11.1





Installation of VirtualBox is working. 
Trying to create and start an Ubuntu-Machine with VirtualMachine by using the following command in existing project: 
{{{
vagrant up
}}}

After short time the following message appears: 

{{{
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: [""hostonlyif"", ""create""]

Stderr: 0%...
Progress state: NS_ERROR_FAILURE
VBoxManage: error: Failed to create the host-only adapter
VBoxManage: error: VBoxNetAdpCtl: Error while adding new interface: failed to open /dev/vboxnetctl: No such file or directory
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
VBoxManage: error: Context: ""RTEXITCODE handleCreate(HandlerArg *)"" at line 95 of file VBoxManageHostonly.cpp
}}}

There is no file like /dev/vboxnetctl. When  installing VirtualBox there is no option in the security settings to accept. Related posts recommend reinstalling of VirtualBox. Tried multiple times without success. There is still no possibility to adjust the privacy settings of Big Sur for VirtualBox.

Other way to resolve the problem: 
Trying to restart with:
{{{
sudo ""/Library/Application Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh"" restart 
}}}

This doesn’t work and leads to following error:
{{{
Error Domain=KMErrorDomain Code=71 ""Incompatible architecture: Binary is for x86_64, but needed arch arm64e"" UserInfo={NSLocalizedDescription=Incompatible architecture: Binary is for x86_64, but needed arch arm64e}
}}}


It seems that VirtualBox is not compatible to the newest Mac ARM architecture. Is there a plan to fix that in the upcoming releases?


"	mheimqpm
14064	Virtual Machine fails to start from a saved state or restored snapshot at 97% progress	VirtualBox 4.3.26	2015-04-21T12:47:14Z	2015-04-21T19:06:53Z	2015-04-21T19:06:53Z	"Cannot start a VM from a saved state or from a restored snapshot with the same error:
----------------------------------------------------------------------------------------------------------------------
Failed to open a session for the virtual machine Windows8.1.

No error info.

Result Code: NS_ERROR_CALL_FAILED (0x800706BE)
Component: ProgressProxy
Interface: IProgress {c20238e4-3221-4d3f-8891-81ce92d9f913}
------------------------------------------------------------------------------------------------------------------------
Host OS: Linux Ubuntu 14.10
Virtual box version: 4.3.26r98988
Guest OS: Windows 8.1 64 bit
Laptop: System 76
-----------------------------------------------------------------------
Configuration file to be renamed to Windows8.1.vbox and the log file are attached.
-----------------------------------------------------------------------

Export to .vmdk and import back both work. I can start the imported VM. 
But cannot started it from a saved state or a snapshot as well: so both VMs 
1. Original .vbox + .vdi
2. Exported to and imported back from a .vmdk
can't be started from a saved state or restored snapshot.
"	mduberstein
18659	Virtual Machine Freezes after host desktop switched	VirtualBox 6.0.6	2019-05-19T13:50:32Z	2019-05-19T14:24:43Z	2019-05-19T14:24:43Z	"I have a Windows 2000 VM running under VirtualBox 6.0.6 r130049 (Qt5.6.2)

This is upon a fully up-to-date Windows 7 Ultimate host machine, using a  tool called Dexpot to switch host desktops upon a three-monitor system.

When I switch back to the desktop upon which the previously functional and running VM is displayed, the VM is locked up.  The only way to recover it is to pause and snapshot the VM, close it and then start it up again (not always successful in such cases).

As I have been using Dexpot for some years and can definitely say that the only software on the host affected by this problem (out of literally hundreds of software engineering tools, including VMWare, and office applications) is VirtualBox.

Is this a known problem and can it be fixed?
"	Alex Tidmarsh
18321	Virtual Machine has terminated unexpectedly.	VirtualBox 6.0.2	2019-01-17T07:01:18Z	2019-01-19T21:14:17Z	2019-01-19T21:14:17Z	"The virtual machine 'Windows 10 Test' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005). More details may be available in 'D:\Program Files (x86)\Oracle\VirtualBox VMs\Windows 10 Test\Logs\VBoxHardening.log'.

Result Code: 
E_FAIL (0x80004005)
Component: 
MachineWrap
Interface: 
IMachine {5047460a-265d-4538-b23e-ddba5fb84976}
"	Excaluburjmk
16617	Virtual Machine Launching Causes Touch Bar to Disappear	VirtualBox 5.1.18	2017-03-28T16:30:45Z	2017-03-28T17:13:00Z	2017-03-28T17:13:00Z	It appears that when launching a virtual machine in VirtualBox, the Touch Bar functionality disappears system wide until the virtual machine is terminated.	Ben.S
20370	Virtual machine running slow and lagging.	VirtualBox 6.1.22	2021-05-19T05:23:25Z	2021-05-19T05:23:25Z	2021-05-19T05:23:25Z	I am experiencing a lot of lag while running my system. Especially when I start the browser in the guest os. I cannot run any other program and my screen freezes. The refresh rate and the response speed are also very slow. And when I start the VM box I need to minimize it first or else the guest os won't load up. I hope you can look into this issue and get to me back with a proper fix for this issue. I also tried seeking help from the forum but those solutions don't seem to work for me. Thank you in advance. 	red66
19790	virtual machine startup error (0x80004005)	VirtualBox 5.2.40	2020-08-04T18:37:56Z	2020-08-04T18:53:27Z	2020-08-04T18:53:27Z	"Не удалось открыть сессию для виртуальной машины deb1.

The virtual machine 'deb1' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\Melchiorre\VirtualBox VMs\deb1\Logs\VBoxHardening.log'.

Код ошибки: E_FAIL (0x80004005)
Компонент: MachineWrap
Интерфейс: IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}

"	Megasort
17761	Virtual machine stuck at initializing (windows logo)	VirtualBox 5.2.12	2018-05-14T02:49:17Z	2018-05-14T06:01:19Z	2018-05-14T06:01:19Z	"-Create a windows 10 32 bits virtual machine
-2 GB of hard disk + ISO Image (SATA)
-128 MB graphics
-4 GB of dedicated TAM"	Leviathan
17328	Virtual Machine work very slowly	VirtualBox 5.2.0	2017-11-29T14:21:05Z	2017-11-29T23:59:00Z	2017-11-29T23:59:00Z	"Hi, 
I have a very big problem with my VM's. Before installing the extensions pack, my virtual machines worked very well, did not jam, worked properly. I wanted to run USB 2.0 so I installed the Extension pack. After installing machines have slowed down, clipping. They have allocated 4GB of RAM, an Intel i5-3360M processor, 128MB of graphics memory and walk slower than computers before 15 years ago. What can I do to speed it up? On the I have an SSD hard drive installed. Please help me.

Karina

P.S. I have now Virtual Box 5.2.2 with extensions pack for this version. It still work very slowly."	Inka
14648	"Virtual machines are aborted when selecting ""Contents"" from the Help menu"	VirtualBox 5.0.4	2015-09-30T20:16:26Z	2015-09-30T20:36:20Z	2015-09-30T20:36:20Z	"How to reproduce

* Start any virtual machine with the Manager.
* Once started, click Help in the menu.
* Select Contents.

Result:

The virtual machine(s) you're running is ""Aborted"" and comes up with this warning saying:

""unknown has generated errors and will be closed by Windows.  You will need to restart the program.

An error log is being created.""

But it works in previous versions of !VirtualBox and in the !VirtualBox GUI Manager.

Actual:

The help contents are displayed."	Tae
18599	Virtual machines VBOX 6 works extremely slowly on iscsi.	VirtualBox 6.0.6	2019-04-26T04:34:35Z	2019-04-26T04:34:35Z	2019-04-26T04:34:35Z	"After updating virtualbuox for version 6, virtual machines with 
disks, connected via a protocol iscsi, began to work extremely slowly.
Network storage, showed that the iscsi-target opens 4 connections
at once."	Bigfut
20031	Virtual Ram feature idea		2020-11-10T23:04:29Z	2020-11-10T23:04:29Z	2020-11-10T23:04:29Z	Can you add a feature for Virtual Ram where it does not use the computer's physical ram and instead uses hard drive space on the host computer for ram, also select which drive to use for ram, ex: USB connected to the host computer and the user wants to use 4gb of its space for ram, so the user can go and create a ram disk by creating a virtual hard disk and use it for ram while stored on the USB	BSoD
19661	virtual sanal makine hatası önemlid	VirtualBox 6.1.10	2020-06-12T04:37:12Z	2020-06-15T07:49:32Z	2020-06-15T07:49:32Z	Merhaba, görsel ektedir.	ferittrn
18886	Virtual screen 2 crashes after update to virtualbox 6.0.10, but only when running ubuntu	VirtualBox 6.0.10	2019-08-31T00:10:05Z	2019-08-31T16:08:46Z	2019-08-31T16:08:46Z	"I usually run ubuntu 18.04 in a virtual box on a Windows 10 host and use two virtual screens, i.e. virtual screen 1 and virtual screen 2. Today I updated my virtualbox to 6.0.10. When I restarted the virtual machine with ubuntu, virtual screen 1 and virtual screen 2 opens as usual, see screen shot here: https://imgur.com/a/owwjNnL

Furthermore, I can move the windows with virtual screen 1 and virtual screen 2 around. However, when I try to go to full screen or to resize the windows, screen 2 closes/crashes. It is then impossible to restart it by choosing view->virtual screen 2 -> enable. 

To see where the problem lies I also installed ubuntu 19.04 and windows 10 in virtual machines. With ubuntu 19.04 I still got the same problem. But with the windows 10 virtual machine everything worked, even if the graphics of window is flickering a couple of seconds before adapting to the new size. What can I do?
"	haggle
15756	Virtual USB Drive information	VirtualBox 5.1.2	2016-08-06T21:41:45Z	2016-08-10T07:52:21Z	2016-08-10T07:52:21Z	"Hello, Thank you for taking time to read my question. 

I'd like to know how to assign a serial number to virtual USB drives or request it as a feature.

I love the new virtual USB feature, It's something I've been dreaming of for years. 

In the attached screen shot you can see Vbox assign's a model and vendor name but leaves the serial number blank. 

Thank you for your time! "	Griz
18821	VirtualBox (VirtualVM.exe) crashes on Xubuntu 18.04 guest shutdown	VirtualBox 6.0.10	2019-08-08T11:18:44Z	2019-08-08T11:18:44Z	2019-08-08T11:18:44Z	"More often than not, my Xubuntu 18.04 guest OS does not shutdown cleanly. The host OS is running the latest version of Windows 10. A crash is raised in VirtualVM.exe. An example screenshot of the 'Application Error' is attached.

Attached are the following files:
* VBox Manager log
* Link (not actual attachment) to compressed, '''full''' crash dump (generated via Task Manager) - [https://drive.google.com/file/d/1CiOAs_8KejRZzMYjGd3UtA71kUOobv5a/view?usp=sharing Google Drive].
* Screenshot of application error raised by Windows. For the record, this screenshot does not (unfortunately) correspond to the attached crashdump.

I initially suspected the issue was related to Graphics acceleration, but I have disabled both 2d/3d but it has not changed the resulting behaviour."	zerodefect
21412	Virtualbox + Hyper-V + 1GB Paging doesn't seem to be supported?	VirtualBox-7.0.4	2023-01-16T19:54:28Z	2023-01-17T19:00:38Z	2023-01-17T19:00:38Z	"I have a toy OS in which I use 1GB pages. 

The hardware supports 1GB. 
It works correctly on my Linux machine within VirtualBox. 
It works correctly on windows when Hyper-V is disabled.
It works correctly on windows using their Hyper-V VM manager.
It works correctly in qemu.

My conclusion so far is that the specific combination of VirtualBox + Hyper-V + 1GB paging is simply not yet supported correctly.

The result is a triple fault the moment the page is accessed for any reason. I'm not on my development machine at the moment, but I will post a log and a bootable ISO demonstrating the issue as soon as I can.

I'd definitely prefer to use VirtualBox for this as the Hyper-V VMs are quite limited.

Thanks!"	Evan Teran
9480	VirtualBox + VirtualPC2007 = crash	VirtualBox 4.1.2	2011-08-21T19:47:56Z	2012-02-03T18:53:48Z	2012-02-03T18:53:48Z	"Host:[[BR]]
Win7 SP1 x64[[BR]]
Core2 Quad CPU[[BR]]
[[BR]]
VirtualBox:[[BR]]
WinXP x32 SP3[[BR]]
Hardware acceleration enabled[[BR]]
[[BR]]
VirtualPC 2007:[[BR]]
Win98 SE[[BR]]
Hardware acceleration enabled[[BR]]
[[BR]]
VirtualBox started first with WinXP. Once VirtualPC is booting Win98, VirtualPC crashes (log included). If I try to start the crashed WinXP, the host crashes with BSOD (see included minidump)[[BR]]
The issue seems to be the hardware acceleration: if I deactivate the support in VirtualPC2007, no crash occurs."	HackAR
20184	VirtualBox - Ubuntu (20.04.1) error	VirtualBox 6.1.18	2021-02-13T14:09:46Z	2021-02-13T14:09:46Z	2021-02-13T14:09:46Z	When I enter to the menu of my Ubuntu machine, some widgets are shaking and I can't move through the menu	Bohosul01
10764	VirtualBox 4.1.18r78361 prevents Windows 7 host from sleeping/entering standby	VirtualBox 4.1.18	2012-07-15T17:20:19Z	2015-11-17T06:22:45Z	2015-11-17T06:22:45Z	While VirtualBox is running, my Windows 7 host OS will not enter standby/sleep after the time of inactivity specified in my Windows power scheme has elapsed.  When I close VirtualBox, Windows sleeps after the time specified in the power scheme.  This problem started after I upgraded to 4.1.18r78361.  This is very inconvenient because I like to keep my guest OS running, so I have to remember to put my host computer into standby whenever I leave the computer or it will needlessly stay on.	bgx90
13187	VirtualBox 4.3.14 can't start VMs on certain Windows hosts	VirtualBox 4.3.14	2014-07-16T11:22:16Z	2018-12-30T10:39:56Z	2018-12-30T10:39:56Z	"Both new and existing VMs cannot be started with VirtualBox 4.3.14 under Win 8.1 x64. Double-clicking on a stopped VM in the GUI gives a popup containing CLI arguments and a message that it failed. Vagrant is broken too. Restarting the system does not fix the issue. Uninstalling and reinstalling 4.3.14 does not fix the issue.

The only fix is to uninstall and reinstall 4.3.12."	AxelFontaine
13557	Virtualbox 4.3.18 disable logging	VirtualBox 4.3.18	2014-10-27T08:52:34Z	2014-11-14T11:41:47Z	2014-11-14T11:41:47Z	"I have set system user variables:
{{{
VBOX_RELEASE_LOG_DEST=nofile
VBOXSVC_RELEASE_LOG_DEST=nofile
VBOX_GUI_SELECTORWINDOW_RELEASE_LOG_DEST=nofile
}}}

But one file still appears. ""VBoxStartup.log"" under `\VirtualBox VMs\(Machine name)\Logs`. How can I disable all log files?"	karlsson
14121	VirtualBox 4.3.28 auf Windows Server 2012 Datacenter - kein VM-Start mehr nach Windows-Updates	VirtualBox 4.3.28	2015-05-15T14:53:50Z	2015-05-15T15:27:10Z	2015-05-15T15:27:10Z	"I have updated VirtualBox from 4.3.20 to 4.3.26 and later to 4.3.28.
The operating system is Windows Server 2012 Datacenter (German).
When I install all current Windows updates, my
VM (Windows Server 2008 R2 German with all Windows updates) does
not start.

The error after installing VirtualBox 4.3.28 is:
Die Anweisung in 0xe3ff0ab1 verweist auf Speicher 0x041af0bd. Der
Vorgang read konnte nicht im Speicher durchgeführt werden.
Klicken Sie auf ""OK"", um das Programm zu beenden.

"	clearth
16164	VirtualBox 5.0 causes lost interrupts / disk stalls on a Linux system	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
14629	VirtualBox 5.0.4-102546~Unbuntu~trusty Crashes when running more then 2 Windows Vm's	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
14701	Virtualbox 5.0.6 Slow Loading & Desktop Flickers	VirtualBox 5.0.6	2015-10-15T02:02:53Z	2015-11-09T03:40:06Z	2015-11-09T03:40:06Z	"My System Specs;

Slackware 14.1 x86_64
Openbox 3.6.1
Nvidia 352.41
xorg-server-1.14.3
compton

I noticed that when starting Virtualbox it loads slowly, taking around 5-10 seconds before it appears on the desktop. Once it loads the entire desktop flickers.

I'm running the compton composite manager and the last safe version I could use without the slow loading and flicker was 5.0.2

Has something changed in virtualbox that is creating a problem when running a composite manager like compton?"	VBoxGrl
14323	Virtualbox 5.0: Blackscreen in fullscreen mode with i3wm host.	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
16815	VirtualBox 5.1 disables iSight camera on MacBook Air with MacOS Sierra	VirtualBox 5.1.22	2017-06-05T17:00:12Z	2017-12-20T15:15:04Z	2017-12-20T15:15:04Z	"Steps to reproduce:

1. On a clean system, launch the FaceTime app to verify the camera is working
2. Install VirtualBox 5.1.22 using the downloaded dmg
3. Reboot
4. Launch the FaceTime app again

Observed:
The FaceTime app launches with a black screen. The Camera LED does not turn on and the system information indicates the camera is not detected.

Expected:
The camera turns on and in unaffected by the virtualbox installation.


Similar issue with Parallels: https://forum.parallels.com/threads/parallels-desktop-disables-isight-camera-on-macbook-pro-with-os-x-sierra.338294/"	bulgur
16387	virtualbox 5.1 not reading properly certain box.ovf files?	VirtualBox 5.1.12	2017-01-15T15:39:30Z	2017-03-10T16:04:42Z	2017-03-10T16:04:42Z	"Reported also at https://github.com/redhat-imaging/imagefactory/issues/393

Virtualbox 5.1 seems unable to read the settings from the box.ovf file https://atlas.hashicorp.com/centos/boxes/7 but reads the settings from https://atlas.hashicorp.com/puppetlabs/boxes/centos-7.2-64-puppet

Tested on

OS X 10.11.6
VirtualBox 5.1.10 r112026 (Qt5.6.2)

Ubuntu 14.04
VirtualBox 5.1.10r112026, 5.1.12r112440

{{{
$ xmllint --format ~/.vagrant.d/boxes/centos-VAGRANTSLASH-7/1611.01/virtualbox/box.ovf | grep -E 'Order|(StorageController )'
      <ns0:Order device=""HardDisk"" position=""1""/>
      <ns0:Order device=""DVD"" position=""2""/>
      <ns0:Order device=""None"" position=""3""/>
      <ns0:Order device=""None"" position=""4""/>
    <ns0:StorageController Bootable=""true"" PortCount=""2"" name=""IDE Controller"" type=""PIIX4"" useHostIOCache=""true"">

$ vboxmanage import ~/.vagrant.d/boxes/centos-VAGRANTSLASH-7/1611.01/virtualbox/box.ovf
$ vboxmanage showvminfo --machinereadable centos-7-1-1.x86_64 | grep -E 'storagecontrollername0|(boot.=)'
boot1=""floppy""
boot2=""dvd""
boot3=""disk""
boot4=""none""
storagecontrollername0=""IDE""

$ xmllint --format ~/.vagrant.d/boxes/puppetlabs-VAGRANTSLASH-centos-7.2-64-puppet/1.0.1/virtualbox/box.ovf | grep -E 'Order|(StorageController )'
      <Order position=""1"" device=""HardDisk""/>
      <Order position=""2"" device=""DVD""/>
      <Order position=""3"" device=""None""/>
      <Order position=""4"" device=""None""/>
    <StorageController name=""IDE Controller"" type=""PIIX4"" PortCount=""2"" useHostIOCache=""true"" Bootable=""true"">
$ vboxmanage import ~/.vagrant.d/boxes/puppetlabs-VAGRANTSLASH-centos-7.2-64-puppet/1.0.1/virtualbox/box.ovf
$ vboxmanage showvminfo --machinereadable packer-centos-7.2-x86_64-virtualbox-vagrant-puppet-1457544893 | grep -E 'storagecontrollername0|(boot.=)'
boot1=""disk""
boot2=""dvd""
boot3=""none""
boot4=""none""
storagecontrollername0=""IDE Controller""
}}}

"	marcindulak
15666	VirtualBox 5.1.0 and 5.1.2 fails to import digitally signed appliance (OVA file)	VirtualBox 5.1.2	2016-07-22T19:20:52Z	2016-10-30T21:07:22Z	2016-10-30T21:07:22Z	"When attempting to import appliance from ova file, VBoxMAnage.exe fails with:


{{{
C:\Users\...\Downloads>""C:\Program Files\VirtualBox\VBoxManage.exe"" import <path to OVA file>
0%...
Progress state: E_FAIL
VBoxManage.exe: error: Appliance read failed
VBoxManage.exe: error: Certificate path validation failed (VERR_CR_PKIX_SIGNATURE_MISMATCH, EVP_VerifyFinal failed)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ApplianceWrap, interface IAppliance
VBoxManage.exe: error: Context: ""enum RTEXITCODE __cdecl handleImportAppliance(struct HandlerArg *)"" at line 307 of file VBoxManageAppliance.cpp
}}}

Import from GUI ends with error dialog:

{{{
Failed to import appliance <path to OVA file>.

Certificate path validation failed (VERR_CR_PKIX_SIGNATURE_MISMATCH, EVP_VerifyFinal failed).

Result Code: E_FAIL (0x80004005)
Component: ApplianceWrap
Interface: IAppliance {8398f026-4add-4474-5bc3-2f9f2140b23e}
}}}

There is no relevant information in logs except:

{{{
00:40:08.764715 ApplRead ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={8398f026-4add-4474-5bc3-2f9f2140b23e} aComponent={ApplianceWrap} aText={Certificate path validation failed (VERR_CR_PKIX_SIGNATURE_MISMATCH, EVP_VerifyFinal failed)}, preserve=false aResultDetail=0
}}}


I have seen the same behavior on Windows 7 x64 and Windows 10 x64. On another Windows 7 appliance import finished with information popup stating that certificate cannot be verified. 

The same OVA file can be successfully imported using VirtualBox 5.0.X and software of other vendors. 

Content of ""*.mf"": 

{{{
SHA1(ERA_Appliance-disk1.vmdk)= 44f1d187daa9f6ed129381eec155ece99530bfee
}}}

and content of ""*.cert"":

{{{
SHA1(ERA_Appliance.mf)= 7334b00ada502ae4420c9c01ba5c6baf1809e0539a0ca74da780d00b38c89c8fedc6be81f8d8e2e4626a7e0d1e5c19dae2beaded0abde864584b4b1a8dc80294a42e92960ee40a0065a5dfb06a088b8435690475c14a828256b2137c433f868b0bb284c343e84c55c0bc609ea1269f773cbd24269e98b89a2d98332a0aad49d147f3246d47183ee9bf916a4a0b3a774afa49aa885953e1c4535199c86ac59579d07f02a34a68c466becf471cec3d3de7c46fc859740e3cb7dbc7cf8ece6afecbe2baa4072dbe8e7692e58e8a596f2a76499f7c886ab45281608c22e7e4be47da67800eba89627365febeb40bed86c01b3c1706fffc5685bda2d840c3f1c64169
-----BEGIN CERTIFICATE-----
MIIFTjCCBDagAwIBAgIQHeEN7VQdUec7xIb0kkmINjANBgkqhkiG9w0BAQUFADCB
tDELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQL
ExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2Ug
YXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykxMDEuMCwGA1UEAxMl
VmVyaVNpZ24gQ2xhc3MgMyBDb2RlIFNpZ25pbmcgMjAxMCBDQTAeFw0xNjA0MTkw
MDAwMDBaFw0xOTA3MTkyMzU5NTlaMIGvMQswCQYDVQQGEwJTSzERMA8GA1UECBMI
U2xvdmFraWExEzARBgNVBAcTCkJyYXRpc2xhdmExGzAZBgNVBAoUEkVTRVQsIHNw
b2wuIHMgci5vLjE+MDwGA1UECxQ1RGlnaXRhbCBJRCBDbGFzcyAzIC0gTWljcm9z
b2Z0IFNvZnR3YXJlIFZhbGlkYXRpb24gdjIxGzAZBgNVBAMUEkVTRVQsIHNwb2wu
IHMgci5vLjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAKW9l/iFn1Y/
BJouXaVLHs6+TlhWgZztdjUWtyuF6FHJaHk8eaU3UbtZJuKzINeg+VLdVCk1O8RN
w2P1XRoDecxb5W2m7rX4sUrBHvYY62G6KDYHxzWYqfCLNkgC8R5gpkKtYHROwg4W
HP0h+OnRBv0ojYoP8q/lNma1pTcABOQVmYVm8Rg7/NaAmqAAquk0n03Y2+y5rfh2
G2FM3xlLzjBocephZeS30ZxkUhm12TnTf9P+0ZB7j0f8V7N9ecZy8NeUaTSWmjkW
czxbwjphePpK9A4xAaca5uoNrvQV4SarnAM1iVJb+zyA/qMRhR78giyfOVQjDGoX
Q2U0XovY/HECAwEAAaOCAV0wggFZMAkGA1UdEwQCMAAwDgYDVR0PAQH/BAQDAgeA
MCsGA1UdHwQkMCIwIKAeoByGGmh0dHA6Ly9zZi5zeW1jYi5jb20vc2YuY3JsMGEG
A1UdIARaMFgwVgYGZ4EMAQQBMEwwIwYIKwYBBQUHAgEWF2h0dHBzOi8vZC5zeW1j
Yi5jb20vY3BzMCUGCCsGAQUFBwICMBkMF2h0dHBzOi8vZC5zeW1jYi5jb20vcnBh
MBMGA1UdJQQMMAoGCCsGAQUFBwMDMFcGCCsGAQUFBwEBBEswSTAfBggrBgEFBQcw
AYYTaHR0cDovL3NmLnN5bWNkLmNvbTAmBggrBgEFBQcwAoYaaHR0cDovL3NmLnN5
bWNiLmNvbS9zZi5jcnQwHwYDVR0jBBgwFoAUz5mp6nsm9EvJjo/X8AUm7+PSp50w
HQYDVR0OBBYEFIKSJNBoZdrPFMTF6cPzFNk4c63aMA0GCSqGSIb3DQEBBQUAA4IB
AQDzz/hCjjc1kc15nqKjnFy/oiRPDhQpM+C5/bputO8q0AE0uUv17DcGuPQgbQsG
7gfDr4x2suxJfxasRBU2OKKWZfpUfuALqIC5oHviD/8UPU3gk8m+LiwgYr13i5sN
ujbBeUaa4WfzrQo+7+GvdfKPw/NpHnmrDSSRadM0AckpyhrLRqMkgVjvIz7t00Yd
AQoBhFvQTaOk/I8iIQqsQcK0qyVbdOJFnO7Wu16XNeSb0TxqFzXCsGoI0qDUCatm
1uDWPzIKL7omFDrKNxxGZhCoJAV4btgZE1Ys6NFWazUa43//lGl11f6pncXv7BQf
sIlwnYi5uqq1MvtD1mV57wWh
-----END CERTIFICATE-----
}}}"	koso
17264	Virtualbox 5.1.30 Error	VirtualBox 5.1.30	2017-11-10T16:19:35Z	2022-04-11T10:30:15Z	2022-04-11T10:30:15Z	"After installing a program in the virtual machine when I reboot the virtual machine I get the following error:

Failed to get a console object from the direct session (RPC_E_DISCONNECTED).


Result Code: 
VBOX_E_VM_ERROR (0x80BB0003)
Component: 
MachineWrap
Interface: 
IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
"	cmccarron
15830	virtualbox 5.1.4 on debian 8 crashed while plugging/unplugging usb phone in flashing mode	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
16639	Virtualbox 5.1.X prevents Mac Sierra from sleeping / recognizing attached screen on resume from sleep	VirtualBox 5.1.18	2017-04-05T22:02:51Z	2017-04-05T22:02:51Z	2017-04-05T22:02:51Z	"If you install Virtualbox on Mac OS Sierra (e.g. 10.12.x) on a Mac Mini (2012), the following occur:

* The system may not enter energy-saver (sleep) mode based on the timer settings reliably
* If the system does sleep, on resume, attached external monitors may no longer be recognized until system restart (e.g. ""detect monitor"" does not work)."	PhillyDevGuy
17226	Virtualbox 5.2 crashed	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
17223	virtualbox 5.2 win nt 4 sp1	VirtualBox 5.2.0	2017-10-29T04:28:55Z	2017-10-29T04:34:24Z	2017-10-29T04:34:24Z	"it gives misc error if type set to win nt 4

if type set to other unknown i get this error"	jammak
17863	VirtualBox 5.2.12 on Mac OS X 10.13.5 stalling while installing Windows Server 2016	VirtualBox 5.2.12	2018-07-10T20:22:46Z	2018-07-10T22:12:49Z	2018-07-10T22:12:49Z	"Hey guys,

I was trying to install Windows Server 2016 and when the file copy finished and the VM restarted to start recognizing hardware, this never happened, it got stalled there and did not move (I waited for about 45 min), finally I had to switch the type of VM from Windows 2016 to Windows 10, then the installation of Windows Server 2016 finished correctly, but this is something you should look into.

Thanks."	jfha73
17947	Virtualbox 5.2.18 (and 5.2.19) crash on OpenIndiana Hipster	VirtualBox 5.2.18	2018-08-22T13:01:22Z	2018-11-20T09:01:19Z	2018-11-20T09:01:19Z	"Hi,
ref: https://www.illumos.org/issues/9752

When starting a VM on 5.2.18/19 from hostOS openindiana (illumOS) it crashes in 

rtR0SegVBoxSolCreate().

#echo disable_smap/d | mdb -k
disable_smap:
disable_smap: 1
"	Espen Martinsen
17987	VirtualBox 5.2.18 vulnerable to spectre/meltdown despite microcode being installed	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
17377	VirtualBox 5.2.2 issues on Xubuntu 16.04 x64	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
18091	virtualbox 5.2.20 fails to compile with glibc 2.26 because xlocale.h was removed	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
18429	VirtualBox 5.2.26 fails to build due to VBoxFUSE	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
17414	Virtualbox 5.2.4 crashed	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
17542	VirtualBox 5.2.6 Guru Meditation Error	VirtualBox 5.2.6	2018-02-13T17:37:21Z	2018-02-13T17:37:21Z	2018-02-13T17:37:21Z	"Since VirtualBox 5.2.6 my VirtualBox keeps crashing with a Guru Meditation Error on Windows 10 Host with Debian guest.
My Log.txt is attached."	Frank Breitling
18386	VirtualBox 6.0 crash and make Windows reboot	VirtualBox 6.0.4	2019-01-30T06:35:38Z	2019-01-30T06:35:38Z	2019-01-30T06:35:38Z	"Hi. I have problem for latest VirtualBox.
Yesterday my VirtualBox still working. But today after I update VirtualBox from 6.0.2 to 6.0.4, when I run virtual I have, they crash and directly reboot my PC.

I just reinstall all component of VirtualBox. Delete all VMs. Create new VMs like before crash. But still crash.

Did VBox 6.0.4 have problem compability with Windows 10 build 18323.19H1?
(NB : I use Insider Preview for my Windows 10).

My spec :
* RAM 4GB Dual Channel PC-3-10700 (667 MHz)
* Processor Core i3-2120 @3.30Ghz (4 core)
* Internal VGA Intel HD Graphics 256MB
* All Virtualization Setting On (Hyper-V or else)

I attach log for my VMs."	Kuroneko93
19050	VirtualBox 6.0 on macOS 10.14 crashes on suspend/resume	VirtualBox 6.0.14	2019-10-26T17:25:02Z	2019-10-28T09:05:49Z	2019-10-28T09:05:49Z	"Host: Macbook Pro 2015 retina 13"", macOS 10.14.6, vbox 6.0.14
Guest: Ubuntu 18.04.3 server

When the macbook lid is closed and then reopened:
- the VM says it has ""unexpectedly quit""
- when I click on the VirtualBox icon, that has ""unexpectedly quit"" as well

Possibly related to #16486; however, I never had this problem with vbox 5.x.  It seems to happen every time now, although this is with a freshly-installed 18.04 guest so possibly the guest is different.

Since the laptop has a retina display, with vbox 6.0 I select View > Scaled Mode otherwise the console text is too small.  With vbox 5.x the console size was fine without adjustments.  I don't know if this is related."	bcandler
18767	VirtualBox 6.0.10 segfaults at startup on CentOS 7.6	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
18808	VirtualBox 6.0.10 Segmentation fault in openSUSE 13.2	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
19084	Virtualbox 6.0.12 crash when running Windows guest	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
18958	virtualbox 6.0.12 update doesn´t allow Fedora 30 VM start	VirtualBox 6.0.12	2019-09-23T12:52:01Z	2019-09-25T04:49:39Z	2019-09-25T04:49:39Z	"Vm perfectly running on windows with version from 5.x to ""6.0.10 r132072 (Qt5.6.2)"" after 6.0.12 update was not able to start the vm. On configuration were displayed some problems about ""unsupported hardware acceleration"".

A fast roll-back to previous 6.0.10 fixed the proble,m, but seems that 6.10.12 have some problem.
 
Test environment: Windows 10 pro, notebook fujitsu lifebook i7-8650U, 32Gb ram, sss, lan"	Piero Gerletti
18361	VirtualBox 6.0.2 assertion failed while starting a macOS VM	VirtualBox 6.0.2	2019-01-26T10:57:54Z	2019-03-08T17:16:24Z	2019-03-08T17:16:24Z	"My physical computer is a Mac Mini running macOS 10.13.6 and VirtualBox 5.2.2. Among several VMs I have, one is a macOS 10.10.

Today I tried to upgrade VirtualBox to 6.0.2, including the extpack, but when I tried to start the macOS VM, I got a meesage box with an error and the session did not start.

Checking the log, the only lines that seem to be related to VirtualBox are:

{{{
ilg-mini-harlescu:tmp ilg$ grep Virtual ~/Desktop/system.log
Jan 20 18:10:48 ilg-mini-harlescu VirtualBox[92143]: assertion failed: 17G4015: libxpc.dylib + 75013 [0BC7AD67-671D-31D4-8B88-C317B8379598]: 0x89
Jan 20 18:10:48 ilg-mini-harlescu VirtualBox[92143]: objc[92143]: Class FIFinderSyncExtensionHost is implemented in both /System/Library/PrivateFrameworks/FinderKit.framework/Versions/A/FinderKit (0x7fffa2078cd0) and /System/Library/PrivateFrameworks/FileProvider.framework/OverrideBundles/FinderSyncCollaborationFileProviderOverride.bundle/Contents/MacOS/FinderSyncCollaborationFileProviderOverride (0x11caa6cd8). One of the two will be used. Which one is undefined.
Jan 20 18:11:24 ilg-mini-harlescu VirtualBox[92143]: BUG in libdispatch client: kevent[mach_recv] monitored resource vanished before the source cancel handler was invoked

Jan 20 18:20:52 ilg-mini-harlescu VirtualBox[914]: assertion failed: 17G4015: libxpc.dylib + 75013 [0BC7AD67-671D-31D4-8B88-C317B8379598]: 0x89
Jan 20 18:20:52 ilg-mini-harlescu VirtualBox[914]: objc[914]: Class FIFinderSyncExtensionHost is implemented in both /System/Library/PrivateFrameworks/FinderKit.framework/Versions/A/FinderKit (0x7fff9413fcd0) and /System/Library/PrivateFrameworks/FileProvider.framework/OverrideBundles/FinderSyncCollaborationFileProviderOverride.bundle/Contents/MacOS/FinderSyncCollaborationFileProviderOverride (0x1214becd8). One of the two will be used. Which one is undefined.
Jan 20 18:25:47 ilg-mini-harlescu VirtualBox[914]: BUG in libdispatch client: kevent[mach_recv] monitored resource vanished before the source cancel handler was invoked
}}}

I removed 6.0.2, reinstalled 5.2.22 and the same macOS VM started normally, so at least 6.x did not damage it.

My understanding of the log lines is that this new version of VirtualBox running on macOS has a problem and an assert is triggered.

The condition to have the class FIFinderSyncExtensionHost defined in two frameworks seems to be a known problem of macOS (https://stackoverflow.com/questions/46999695/class-fifindersyncextensionhost-is-implemented-in-both-warning-in-xcode-si), and I think it should not trigger the assert, the program should find a way to cope with this condition, as versions 5.x already did.

"	ilg
18619	VirtualBox 6.0.6 VM guest boot hangs with customized Fedora 30 Remix	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
19429	VirtualBox 6.1 + Whonix 15 = Aborted	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
19860	VirtualBox 6.1.13 (testbuild) tiggers BLUE SCREEN on Windows when UAC Required	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
19952	Virtualbox 6.1.14 breaks compatibility on Mac OSX	VirtualBox 6.1.14	2020-10-09T20:03:11Z	2020-12-13T12:11:41Z	2020-12-13T12:11:41Z	"I'm on an iMac here with Mojave 10.14.6.
Virtualbox 6.1.12 was running fine until today. When I started VB I was informed about the available update 6.1.14. So I downloaded it and tried to install. Installation aborted at some stage, no detailed information why. Since then VB doesn't work any longer on my Mac.
When I try to start a virtual machine, an error comes up:
Kernel driver not installed (rc=-1908)
Make sure the kernel module has been loaded successfully.
where: suplibOsInit what: 3
VERR_VM_DRIVER_NOT_INSTALLED (-1908)
- The support driver ist not installed. On linux, open returned ENOENT.

When I turn off SIP, Virtualbox can be installed and executed. As soon as I enable SIP again, VB refuses to run."	Dirk.K
19979	Virtualbox 6.1.14 crashes on Windows 10 Home, 6.1.4 does not	VirtualBox 6.1.14	2020-10-18T16:58:38Z	2020-10-18T17:04:31Z	2020-10-18T17:04:31Z	"I've been using 6.1.4 about 10 hours a day for 6 months on my Windows 10 Pro laptop, without *any* crashes (ok maybe once once but I'm not going to complain, awesome software). Recently I got a new laptop with Windows 10 Home and installed VirtualBox 6.1.14. VM crashed several times and behaved strangely, like Firefox in the VM would crash, or after being in ""screensave"" mode then login would crash and once re-logged in my apps would be gone I would have to restart them, that kind of stuff. I tried a few things, like upgrading Windows 10 to Pro, turning off audio etc. But the only that worked was to rollback to VirtualBox 6.1.4. I did not try 6.1.6, 8, 10 or 12, but clearly a bug got introduced in one of those or in 6.1.14.  "	schollii
19941	virtualbox 6.1.14 on Ubuntu 20.04 (5.4.0-48-generic)	VirtualBox 6.1.14	2020-10-05T22:36:28Z	2020-10-05T22:57:44Z	2020-10-05T22:57:44Z	"Hi,
Please can you help me install VirtualBox 6.1.14 on Ubuntu 20.04 (5.4.0-48-generic)
I am getting following errors during installation.
######
udo /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.  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.
#######
dmesg here

$ tail -f /var/log/dmesg
[   24.025100] kernel: audit: type=1400 audit(1601929395.857:4): apparmor=""STATUS"" operation=""profile_load"" profile=""unconfined"" name=""/usr/lib/NetworkManager/nm-dhcp-helper"" pid=733 comm=""apparmor_parser""
[   24.025102] kernel: audit: type=1400 audit(1601929395.857:5): apparmor=""STATUS"" operation=""profile_load"" profile=""unconfined"" name=""/usr/lib/connman/scripts/dhclient-script"" pid=733 comm=""apparmor_parser""
[   24.025105] kernel: audit: type=1400 audit(1601929395.857:6): apparmor=""STATUS"" operation=""profile_load"" profile=""unconfined"" name=""/{,usr/}sbin/dhclient"" pid=733 comm=""apparmor_parser""
[   24.075158] kernel: audit: type=1400 audit(1601929395.905:7): apparmor=""STATUS"" operation=""profile_load"" profile=""unconfined"" name=""/usr/bin/evince"" pid=736 comm=""apparmor_parser""
[   24.075161] kernel: audit: type=1400 audit(1601929395.905:8): apparmor=""STATUS"" operation=""profile_load"" profile=""unconfined"" name=""/usr/bin/evince//sanitized_helper"" pid=736 comm=""apparmor_parser""
[   24.075163] kernel: audit: type=1400 audit(1601929395.905:9): apparmor=""STATUS"" operation=""profile_load"" profile=""unconfined"" name=""/usr/bin/evince-previewer"" pid=736 comm=""apparmor_parser""
[   24.075164] kernel: audit: type=1400 audit(1601929395.905:10): apparmor=""STATUS"" operation=""profile_load"" profile=""unconfined"" name=""/usr/bin/evince-previewer//sanitized_helper"" pid=736 comm=""apparmor_parser""
[   24.075166] kernel: audit: type=1400 audit(1601929395.905:11): apparmor=""STATUS"" operation=""profile_load"" profile=""unconfined"" name=""/usr/bin/evince-thumbnailer"" pid=736 comm=""apparmor_parser""
[   25.601812] kernel: usb 2-5: New USB device found, idVendor=04ca, idProduct=300b, bcdDevice= 0.02
[   25.601815] kernel: usb 2-5: New USB device strings: Mfr=0, Product=0, SerialNumber=0
#######

"	prabh
20020	VirtualBox 6.1.16 Ubuntu 20.04 Guest freezes when windows 10 screensaver or screen lock	VirtualBox 6.1.16	2020-11-05T15:37:23Z	2020-11-22T10:54:59Z	2020-11-22T10:54:59Z	When I lock screen on Windows 10 host and then unlock and log back in my VirtualBox Ubuntu 20.04 Guest v6.1.16 freezes (I even have issues closing the main window of VirtualBox guest). Totally unresponsive. Only closing guest (after putting in some effort) main window with quite a few attempts including VirtualBox Manager on host freezing at the same time and restarting gets the VM back to life only to be unusable after host screen lock again...	SamH
20277	VirtualBox 6.1.18 freezes when trying to start a Ubuntu installation from CD image	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
19300	VirtualBox 6.1.2 crashes on startup with Mac OS X 10.10.5	VirtualBox 6.1.2	2020-02-11T13:35:02Z	2020-02-12T10:14:41Z	2020-02-12T10:14:41Z	"VirtualBox 6.1.2 crashes on startup with Mac OS X 10.10.5 due to invalid code siganture ""/Applications/VirtualBox.app/Contents/Frameworks/QtMacExtrasVBox.framework/Versions/5/QtMacExtrasVBox""

VirtualBox 6.0.16 works just fine.

----------------------------------------
LOGS:

Process:               VirtualBox [22213]
Path:                  /Applications/VirtualBox.app/Contents/MacOS/VirtualBox
Identifier:            org.virtualbox.app.VirtualBox
Version:               ???
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           VirtualBox [22213]
User ID:               501

Date/Time:             2020-02-11 14:24:34.192 +0100
OS Version:            Mac OS X 10.10.5 (14F2511)
Report Version:        11

Crashed Thread:        0

Exception Type:        EXC_BREAKPOINT (SIGTRAP)
Exception Codes:       0x0000000000000002, 0x0000000000000000

Application Specific Information:
dyld: launch, loading dependent libraries

Dyld Error Message:
  Library not loaded: /Applications/VirtualBox.app/Contents/Frameworks/QtMacExtrasVBox.framework/Versions/5/QtMacExtrasVBox
  Referenced from: /Applications/VirtualBox.app/Contents/MacOS/VirtualBox
  Reason: no suitable image found.  Did find:
	/Applications/VirtualBox.app/Contents/Frameworks/QtMacExtrasVBox.framework/Versions/5/QtMacExtrasVBox: code signature invalid for '/Applications/VirtualBox.app/Contents/Frameworks/QtMacExtrasVBox.framework/Versions/5/QtMacExtrasVBox'

Binary Images:
    0x7fff63536000 -     0x7fff6356c92f  dyld (353.2.4) <3C068A0D-69D5-3AD6-86D9-6261D3B1564E> /usr/lib/dyld
..."	cdvk
20342	VirtualBox 6.1.20/6.1.22 breaks audio output on a Fedora 33 system	VirtualBox 6.1.22	2021-05-07T21:41:10Z	2022-10-21T12:58:22Z	2022-10-21T12:58:22Z	"Each time I launch a VM ('''regardless''' whether it has audio output enabled or not), my Linux host audio completely breaks: it starts crackling and making noises. VirtualBox 6.1.18 and 6.1.16 were free from this bug.

6.1.20 and 6.1.22 are both affected.

Restarting pulseaudio fixes the issue but it's incredibly annoying.

My system configuration:
* Fedora 33 (fully updated as of right now)
* Linux 5.11.16 (vanilla, zero patches applied)
* PulseAudio Server, no PipeWire (Host Audio Driver in a VM settings: PulseAudio), almost default configuration
{{{
$ cat ~/.config/pulse/default.pa
#!/usr/bin/pulseaudio -nF

.include /etc/pulse/default.pa

load-module module-native-protocol-unix auth-anonymous=1 socket=/tmp/pulse-socket
}}}
* Audio device: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller

{{{
09:00.4 Audio device: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller
	Subsystem: ASUSTeK Computer Inc. Device 8797
	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-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin D routed to IRQ 119
	IOMMU group: 26
	Region 0: Memory at f7900000 (32-bit, non-prefetchable) [size=32K]
	Capabilities: [48] Vendor Specific Information: Len=08 <?>
	Capabilities: [50] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [64] Express (v2) Endpoint, MSI 00
		DevCap:	MaxPayload 256 bytes, PhantFunc 0, Latency L0s <4us, L1 unlimited
			ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset+ SlotPowerLimit 0.000W
		DevCtl:	CorrErr- NonFatalErr- FatalErr- UnsupReq-
			RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ FLReset-
			MaxPayload 256 bytes, MaxReadReq 512 bytes
		DevSta:	CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend-
		LnkCap:	Port #0, Speed 16GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <64ns, L1 <1us
			ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+
		LnkCtl:	ASPM L0s L1 Enabled; RCB 64 bytes, Disabled- CommClk+
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 16GT/s (ok), Width x16 (ok)
			TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
		DevCap2: Completion Timeout: Range ABCD, TimeoutDis+ NROPrPrP- LTR-
			 10BitTagComp+ 10BitTagReq- OBFF Not Supported, ExtFmt- EETLPPrefix-
			 EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
			 FRS- TPHComp+ ExtTPHComp-
			 AtomicOpsCap: 32bit- 64bit- 128bitCAS-
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR- OBFF Disabled,
			 AtomicOpsCtl: ReqEn-
		LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete- EqualizationPhase1-
			 EqualizationPhase2- EqualizationPhase3- LinkEqualizationRequest-
			 Retimer- 2Retimers- CrosslinkRes: unsupported
	Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
		Address: 00000000fee00000  Data: 0000
	Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
	Capabilities: [150 v2] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UESvrt:	DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr-
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
		AERCap:	First Error Pointer: 00, ECRCGenCap- ECRCGenEn- ECRCChkCap- ECRCChkEn-
			MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
		HeaderLog: 00000000 00000000 00000000 00000000
	Capabilities: [2a0 v1] Access Control Services
		ACSCap:	SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans-
		ACSCtl:	SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans-
	Capabilities: [370 v1] Transaction Processing Hints
		Device specific mode supported
		Steering table in TPH capability structure
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel

Codec: Realtek ALCS1200A
Address: 0
AFG Function Id: 0x1 (unsol 1)
Vendor Id: 0x10ec0b00
Subsystem Id: 0x10438797
Revision Id: 0x100001
No Modem Function Group found
Default PCM:
    rates [0x5f0]: 32000 44100 48000 88200 96000 192000
    bits [0xe]: 16 20 24
    formats [0x1]: PCM
Default Amp-In caps: N/A
Default Amp-Out caps: N/A
State of AFG node 0x01:
  Power states:  D0 D1 D2 D3 CLKSTOP EPSS
  Power: setting=D0, actual=D0
GPIO: io=2, o=0, i=0, unsolicited=1, wake=0
  IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
  IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out
  Control: name=""Front Playback Volume"", index=0, device=0
    ControlAmp: chs=3, dir=Out, idx=0, ofs=0
  Device: name=""ALCS1200A Analog"", type=""Audio"", device=0
  Amp-Out caps: ofs=0x57, nsteps=0x57, stepsize=0x02, mute=0
  Amp-Out vals:  [0x4c 0x56]
  Converter: stream=5, channel=0
  PCM:
    rates [0x560]: 44100 48000 96000 192000
    bits [0xe]: 16 20 24
    formats [0x1]: PCM
  Power states:  D0 D1 D2 D3 EPSS
  Power: setting=D0, actual=D0
Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out
  Control: name=""Surround Playback Volume"", index=0, device=0
    ControlAmp: chs=3, dir=Out, idx=0, ofs=0
  Amp-Out caps: ofs=0x57, nsteps=0x57, stepsize=0x02, mute=0
  Amp-Out vals:  [0x56 0x56]
  Converter: stream=5, channel=0
  PCM:
    rates [0x560]: 44100 48000 96000 192000
    bits [0xe]: 16 20 24
    formats [0x1]: PCM
  Power states:  D0 D1 D2 D3 EPSS
  Power: setting=D0, actual=D0
Node 0x04 [Audio Output] wcaps 0x41d: Stereo Amp-Out
  Control: name=""Center Playback Volume"", index=0, device=0
    ControlAmp: chs=1, dir=Out, idx=0, ofs=0
  Control: name=""LFE Playback Volume"", index=0, device=0
    ControlAmp: chs=2, dir=Out, idx=0, ofs=0
  Amp-Out caps: ofs=0x57, nsteps=0x57, stepsize=0x02, mute=0
  Amp-Out vals:  [0x56 0x56]
  Converter: stream=5, channel=0
  PCM:
    rates [0x560]: 44100 48000 96000 192000
    bits [0xe]: 16 20 24
    formats [0x1]: PCM
  Power states:  D0 D1 D2 D3 EPSS
  Power: setting=D0, actual=D0
Node 0x05 [Audio Output] wcaps 0x41d: Stereo Amp-Out
  Control: name=""Headphone Playback Volume"", index=0, device=0
    ControlAmp: chs=3, dir=Out, idx=0, ofs=0
  Amp-Out caps: ofs=0x57, nsteps=0x57, stepsize=0x02, mute=0
  Amp-Out vals:  [0x00 0x00]
  Converter: stream=5, channel=0
  PCM:
    rates [0x560]: 44100 48000 96000 192000
    bits [0xe]: 16 20 24
    formats [0x1]: PCM
  Power states:  D0 D1 D2 D3 EPSS
  Power: setting=D0, actual=D0
Node 0x06 [Audio Output] wcaps 0x611: Stereo Digital
  Control: name=""IEC958 Playback Con Mask"", index=0, device=0
  Control: name=""IEC958 Playback Pro Mask"", index=0, device=0
  Control: name=""IEC958 Playback Default"", index=0, device=0
  Control: name=""IEC958 Playback Switch"", index=0, device=0
  Control: name=""IEC958 Default PCM Playback Switch"", index=0, device=0
  Device: name=""ALCS1200A Digital"", type=""SPDIF"", device=1
  Converter: stream=5, channel=0
  Digital:
  Digital category: 0x0
  IEC Coding Type: 0x0
  PCM:
    rates [0x5f0]: 32000 44100 48000 88200 96000 192000
    bits [0xe]: 16 20 24
    formats [0x1]: PCM
  Power states:  D0 D1 D2 D3 EPSS
  Power: setting=D0, actual=D0
Node 0x07 [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x08 [Audio Input] wcaps 0x10051b: Stereo Amp-In
  Control: name=""Capture Volume"", index=0, device=0
    ControlAmp: chs=3, dir=In, idx=0, ofs=0
  Control: name=""Capture Switch"", index=0, device=0
    ControlAmp: chs=3, dir=In, idx=0, ofs=0
  Device: name=""ALCS1200A Analog"", type=""Audio"", device=0
  Amp-In caps: ofs=0x17, nsteps=0x3f, stepsize=0x02, mute=1
  Amp-In vals:  [0x27 0x27]
  Converter: stream=1, channel=0
  SDI-Select: 0
  PCM:
    rates [0x560]: 44100 48000 96000 192000
    bits [0xe]: 16 20 24
    formats [0x1]: PCM
  Power states:  D0 D1 D2 D3 EPSS
  Power: setting=D0, actual=D0
  Connection: 1
     0x23
Node 0x09 [Audio Input] wcaps 0x10051b: Stereo Amp-In
  Control: name=""Capture Volume"", index=1, device=0
    ControlAmp: chs=3, dir=In, idx=0, ofs=0
  Control: name=""Capture Switch"", index=1, device=0
    ControlAmp: chs=3, dir=In, idx=0, ofs=0
  Device: name=""ALCS1200A Alt Analog"", type=""Audio"", device=2
  Amp-In caps: ofs=0x17, nsteps=0x3f, stepsize=0x02, mute=1
  Amp-In vals:  [0x80 0x80]
  Converter: stream=0, channel=0
  SDI-Select: 0
  PCM:
    rates [0x560]: 44100 48000 96000 192000
    bits [0xe]: 16 20 24
    formats [0x1]: PCM
  Power states:  D0 D1 D2 D3 EPSS
  Power: setting=D0, actual=D0
  Connection: 1
     0x22
Node 0x0a [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x0b [Audio Mixer] wcaps 0x20010b: Stereo Amp-In
  Control: name=""Front Mic Playback Volume"", index=0, device=0
    ControlAmp: chs=3, dir=In, idx=1, ofs=0
  Control: name=""Front Mic Playback Switch"", index=0, device=0
    ControlAmp: chs=3, dir=In, idx=1, ofs=0
  Control: name=""Rear Mic Playback Volume"", index=0, device=0
    ControlAmp: chs=3, dir=In, idx=0, ofs=0
  Control: name=""Rear Mic Playback Switch"", index=0, device=0
    ControlAmp: chs=3, dir=In, idx=0, ofs=0
  Control: name=""Line Playback Volume"", index=0, device=0
    ControlAmp: chs=3, dir=In, idx=2, ofs=0
  Control: name=""Line Playback Switch"", index=0, device=0
    ControlAmp: chs=3, dir=In, idx=2, ofs=0
  Control: name=""Beep Playback Volume"", index=0, device=0
    ControlAmp: chs=3, dir=In, idx=5, ofs=0
  Control: name=""Beep Playback Switch"", index=0, device=0
    ControlAmp: chs=3, dir=In, idx=5, ofs=0
  Amp-In caps: ofs=0x17, nsteps=0x1f, stepsize=0x05, mute=1
  Amp-In vals:  [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80]
  Connection: 8
     0x18 0x19 0x1a 0x1b 0x14 0x15 0x16 0x17
Node 0x0c [Audio Mixer] wcaps 0x20010b: Stereo Amp-In
  Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-In vals:  [0x00 0x00] [0x80 0x80]
  Connection: 2
     0x02 0x0b
Node 0x0d [Audio Mixer] wcaps 0x20010b: Stereo Amp-In
  Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-In vals:  [0x00 0x00] [0x80 0x80]
  Connection: 2
     0x03 0x0b
Node 0x0e [Audio Mixer] wcaps 0x20010b: Stereo Amp-In
  Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-In vals:  [0x00 0x00] [0x80 0x80]
  Connection: 2
     0x04 0x0b
Node 0x0f [Audio Mixer] wcaps 0x20010b: Stereo Amp-In
  Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-In vals:  [0x00 0x00] [0x80 0x80]
  Connection: 2
     0x05 0x0b
Node 0x10 [Audio Output] wcaps 0x611: Stereo Digital
  Converter: stream=0, channel=0
  Digital:
  Digital category: 0x0
  IEC Coding Type: 0x0
  PCM:
    rates [0x5f0]: 32000 44100 48000 88200 96000 192000
    bits [0xe]: 16 20 24
    formats [0x1]: PCM
  Power states:  D0 D1 D2 D3 EPSS
  Power: setting=D0, actual=D0
Node 0x11 [Pin Complex] wcaps 0x400781: Stereo Digital
  Pincap 0x00000014: OUT Detect
  Pin Default 0x411111f0: [N/A] Speaker at Ext Rear
    Conn = 1/8, Color = Black
    DefAssociation = 0xf, Sequence = 0x0
    Misc = NO_PRESENCE
  Pin-ctls: 0x40: OUT
  Unsolicited: tag=00, enabled=0
  Power states:  D0 D1 D2 D3 EPSS
  Power: setting=D0, actual=D0
  Connection: 1
     0x10
Node 0x12 [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x13 [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x14 [Pin Complex] wcaps 0x40058d: Stereo Amp-Out
  Control: name=""Front Playback Switch"", index=0, device=0
    ControlAmp: chs=3, dir=Out, idx=0, ofs=0
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals:  [0x00 0x00]
  Pincap 0x0001003e: IN OUT HP EAPD Detect Trigger
  EAPD 0x2: EAPD
  Pin Default 0x01014010: [Jack] Line Out at Ext Rear
    Conn = 1/8, Color = Green
    DefAssociation = 0x1, Sequence = 0x0
  Pin-ctls: 0x40: OUT
  Unsolicited: tag=05, enabled=1
  Power states:  D0 D1 D2 D3 EPSS
  Power: setting=D0, actual=D0
  Connection: 1
     0x0c
Node 0x15 [Pin Complex] wcaps 0x40058d: Stereo Amp-Out
  Control: name=""Surround Playback Switch"", index=0, device=0
    ControlAmp: chs=3, dir=Out, idx=0, ofs=0
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals:  [0x00 0x00]
  Pincap 0x00000036: IN OUT Detect Trigger
  Pin Default 0x01011012: [Jack] Line Out at Ext Rear
    Conn = 1/8, Color = Black
    DefAssociation = 0x1, Sequence = 0x2
  Pin-ctls: 0x40: OUT
  Unsolicited: tag=06, enabled=1
  Power states:  D0 D1 D2 D3 EPSS
  Power: setting=D0, actual=D0
  Connection: 1
     0x0d
Node 0x16 [Pin Complex] wcaps 0x40058d: Stereo Amp-Out
  Control: name=""Center Playback Switch"", index=0, device=0
    ControlAmp: chs=1, dir=Out, idx=0, ofs=0
  Control: name=""LFE Playback Switch"", index=0, device=0
    ControlAmp: chs=2, dir=Out, idx=0, ofs=0
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals:  [0x00 0x00]
  Pincap 0x00000036: IN OUT Detect Trigger
  Pin Default 0x01016011: [Jack] Line Out at Ext Rear
    Conn = 1/8, Color = Orange
    DefAssociation = 0x1, Sequence = 0x1
  Pin-ctls: 0x40: OUT
  Unsolicited: tag=07, enabled=1
  Power states:  D0 D1 D2 D3 EPSS
  Power: setting=D0, actual=D0
  Connection: 1
     0x0e
Node 0x17 [Pin Complex] wcaps 0x40058d: Stereo Amp-Out
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals:  [0x80 0x80]
  Pincap 0x00000036: IN OUT Detect Trigger
  Pin Default 0x40170000: [N/A] Speaker at Ext N/A
    Conn = Analog, Color = Unknown
    DefAssociation = 0x0, Sequence = 0x0
  Pin-ctls: 0x20: IN
  Unsolicited: tag=00, enabled=0
  Power states:  D0 D1 D2 D3 EPSS
  Power: setting=D0, actual=D0
  Connection: 1
     0x0f
Node 0x18 [Pin Complex] wcaps 0x40058f: Stereo Amp-In Amp-Out
  Control: name=""Rear Mic Boost Volume"", index=0, device=0
    ControlAmp: chs=3, dir=In, idx=0, ofs=0
  Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
  Amp-In vals:  [0x00 0x00]
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals:  [0x80 0x80]
  Pincap 0x00003736: IN OUT Detect Trigger
    Vref caps: HIZ 50 GRD 80 100
  Pin Default 0x01a19050: [Jack] Mic at Ext Rear
    Conn = 1/8, Color = Pink
    DefAssociation = 0x5, Sequence = 0x0
  Pin-ctls: 0x24: IN VREF_80
  Unsolicited: tag=03, enabled=1
  Power states:  D0 D1 D2 D3 EPSS
  Power: setting=D0, actual=D0
  Connection: 5
     0x0c* 0x0d 0x0e 0x0f 0x26
Node 0x19 [Pin Complex] wcaps 0x40058f: Stereo Amp-In Amp-Out
  Control: name=""Front Mic Boost Volume"", index=0, device=0
    ControlAmp: chs=3, dir=In, idx=0, ofs=0
  Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
  Amp-In vals:  [0x00 0x00]
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals:  [0x80 0x80]
  Pincap 0x0000373e: IN OUT HP Detect Trigger
    Vref caps: HIZ 50 GRD 80 100
  Pin Default 0x02a19060: [Jack] Mic at Ext Front
    Conn = 1/8, Color = Pink
    DefAssociation = 0x6, Sequence = 0x0
  Pin-ctls: 0x24: IN VREF_80
  Unsolicited: tag=02, enabled=1
  Power states:  D0 D1 D2 D3 EPSS
  Power: setting=D0, actual=D0
  Connection: 5
     0x0c* 0x0d 0x0e 0x0f 0x26
Node 0x1a [Pin Complex] wcaps 0x40058f: Stereo Amp-In Amp-Out
  Control: name=""Line Boost Volume"", index=0, device=0
    ControlAmp: chs=3, dir=In, idx=0, ofs=0
  Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
  Amp-In vals:  [0x00 0x00]
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals:  [0x80 0x80]
  Pincap 0x00003736: IN OUT Detect Trigger
    Vref caps: HIZ 50 GRD 80 100
  Pin Default 0x0181305f: [Jack] Line In at Ext Rear
    Conn = 1/8, Color = Blue
    DefAssociation = 0x5, Sequence = 0xf
  Pin-ctls: 0x20: IN VREF_HIZ
  Unsolicited: tag=04, enabled=1
  Power states:  D0 D1 D2 D3 EPSS
  Power: setting=D0, actual=D0
  Connection: 5
     0x0c* 0x0d 0x0e 0x0f 0x26
Node 0x1b [Pin Complex] wcaps 0x40058f: Stereo Amp-In Amp-Out
  Control: name=""Headphone Playback Switch"", index=0, device=0
    ControlAmp: chs=3, dir=Out, idx=0, ofs=0
  Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
  Amp-In vals:  [0x00 0x00]
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals:  [0x80 0x80]
  Pincap 0x0001373e: IN OUT HP EAPD Detect Trigger
    Vref caps: HIZ 50 GRD 80 100
  EAPD 0x2: EAPD
  Pin Default 0x02214020: [Jack] HP Out at Ext Front
    Conn = 1/8, Color = Green
    DefAssociation = 0x2, Sequence = 0x0
  Pin-ctls: 0xc0: OUT HP VREF_HIZ
  Unsolicited: tag=01, enabled=1
  Power states:  D0 D1 D2 D3 EPSS
  Power: setting=D0, actual=D0
  Connection: 5
     0x0c 0x0d 0x0e 0x0f* 0x26
Node 0x1c [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x1d [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x1e [Pin Complex] wcaps 0x400781: Stereo Digital
  Pincap 0x00000014: OUT Detect
  Pin Default 0x01456140: [Jack] SPDIF Out at Ext Rear
    Conn = Optical, Color = Orange
    DefAssociation = 0x4, Sequence = 0x0
    Misc = NO_PRESENCE
  Pin-ctls: 0x40: OUT
  Unsolicited: tag=00, enabled=0
  Power states:  D0 D1 D2 D3 EPSS
  Power: setting=D0, actual=D0
  Connection: 1
     0x06
Node 0x1f [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x20 [Vendor Defined Widget] wcaps 0xf00040: Mono
  Processing caps: benign=0, ncoeff=32
Node 0x21 [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x22 [Audio Mixer] wcaps 0x20010b: Stereo Amp-In
  Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-In vals:  [0x80 0x80] [0x00 0x00] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80]
  Connection: 9
     0x18 0x19 0x1a 0x1b 0x14 0x15 0x16 0x17 0x0b
Node 0x23 [Audio Mixer] wcaps 0x20010b: Stereo Amp-In
  Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-In vals:  [0x80 0x80] [0x00 0x00] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80]
  Connection: 9
     0x18 0x19 0x1a 0x1b 0x14 0x15 0x16 0x17 0x0b
Node 0x24 [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x25 [Audio Output] wcaps 0x41d: Stereo Amp-Out
  Amp-Out caps: ofs=0x57, nsteps=0x57, stepsize=0x02, mute=0
  Amp-Out vals:  [0x57 0x57]
  Converter: stream=0, channel=0
  PCM:
    rates [0x560]: 44100 48000 96000 192000
    bits [0xe]: 16 20 24
    formats [0x1]: PCM
  Power states:  D0 D1 D2 D3 EPSS
  Power: setting=D0, actual=D0
Node 0x26 [Audio Mixer] wcaps 0x20010b: Stereo Amp-In
  Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-In vals:  [0x00 0x00] [0x80 0x80]
  Connection: 2
     0x25 0x0b
}}}"	Artem S. Tashkinov
20464	Virtualbox 6.1.22 crashes on windows 10 host	VirtualBox 6.1.22	2021-07-20T02:50:25Z	2021-07-20T02:50:25Z	2021-07-20T02:50:25Z	"My virtual box crashes after booting as well as after hibernation. It works fine after the first crash, but it surely crashes for the first time. I am using Virtualbox version 6.1.22, my host machine is Windows 10 and the guest machine is Kali.
"	jishu
20894	VirtualBox 6.1.30 & 6.1.32 VM terminated returning from hibernate	VirtualBox 6.1.32	2022-04-08T18:27:43Z	2022-04-08T18:27:43Z	2022-04-08T18:27:43Z	"Hello,

I have a Ubuntu VM on a Windows 10 Host on a laptop.
When returning from hibernate status while powered on battery, the VM cannot be resumed and a VirtualBox error window states a critical error has occurred and the VM must be terminated.

I get the same result with both VirtualBox 6.1.30 and 6.1.32.
VirtualBox log is only showing ""emR3Debug: rc=VERR_VMX_INVALID_VMXON_PTR"" as last info before the PC goes to hibernate state.
All rest of the log file does not exhibit any meaningful message.

Any help is very appreciated as I suspect more a VM setting issue than a bug but I am not certain and I do not know what kind of VM setting has to be tuned.

Thanks

Laurent"	Laurentzed
21116	VirtualBox 6.1.38 keeps crashing	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
19469	VirtualBox 6.1.4 New Cloud VM (OCI) wizard  - missing options	VirtualBox 6.1.4	2020-04-08T15:32:38Z	2020-04-08T15:32:38Z	2020-04-08T15:32:38Z	"I'd like to deploy a VM to OCI and have the same controls in VirtualBox as I have on the OCI Console or Python SDK:
Options that are missing in VirtualBox 6.1.4:
Availability Domain
custom images
VM shape

"	BernieD
19466	VirtualBox 6.1.4 New Cloud VM (OCI) wizard does not display sub compartments	VirtualBox 6.1.4	2020-04-08T13:30:31Z	2020-04-08T13:30:31Z	2020-04-08T13:30:31Z	"I want to launch a cloud VM in a sub compartment of a compartment of a tenancy.

Your wizard only goes down 1 level to the compartment level and does NOT show the sub compartments (or beyond).

Please e-mail me for more info: bernie.doehner@oracle.com. 
Thanks,
Bernie
"	BernieD
19467	VirtualBox 6.1.4 New Cloud VM (OCI) wizard does not handle errors gracefully	VirtualBox 6.1.4	2020-04-08T13:36:01Z	2020-04-08T13:36:01Z	2020-04-08T13:36:01Z	"At first, I attempted to launch a new cloud VM without creating a profile first.
I made several errors entering key value pairs, but the wizard also shortened my private key filename so that it subsequently couldn't find it. The New Cloud VM wizard just kept erroring out when I attempted to fix my errors instead of actually accepting my corrections.

I had to delete my profile and enter it into the cloud profile directly and correctly (to avoid erroring out)."	BernieD
19468	VirtualBox 6.1.4 New Cloud VM (OCI) wizard public network radio button doesn't work	VirtualBox 6.1.4	2020-04-08T14:20:49Z	2020-04-08T14:20:49Z	2020-04-08T14:20:49Z	I want to create a cloud VM with public facing interface. The radio button for public network in the new cloud VM wizard doesn't work.	BernieD
19446	Virtualbox 6.1.4 r136177. -under MacOS Catalina - Host Only Does not work	VirtualBox 6.1.4	2020-03-30T04:11:01Z	2020-03-30T04:11:01Z	2020-03-30T04:11:01Z	"Virtualbox 6.1.4 r136177. -under MacOS Catalina - Host Only Does not work
1)Created a vboxnet0 (No DHCP)
2)Tried Manually setting IP address
the guest VM is ""Oracle Express VM""
(Infact I am using Oracle's Oracle Express VM downloaded) 

note: Oracle server up & running under VM
But I can't access it from HOST SQLDeveloper 
Even If I set Manual ip address, 
gets the following error
An error was encountered performing the requested operation:

IO Error: The Network Adapter could not establish the connection

Vendor code 17002"	spereira
21503	VirtualBox 6.1.42 failed to install on MacOS 10.13.6 (High Sierra)	VirtualBox-6.1.42	2023-02-14T08:28:09Z	2023-02-14T08:28:09Z	2023-02-14T08:28:09Z	The installation of virtualbox failed on MacOS 10.13.6 (High Sierra), however the VM manager UI can run but report error when starting up VM	richso
19602	VirtualBox 6.1.6 and 6.1.8 failled to start virtual machines	VirtualBox 6.1.8	2020-05-19T14:43:29Z	2020-08-23T06:17:42Z	2020-08-23T06:17:42Z	"Hello,

I have used VirtualBox successfully under Illumos/OpenIndiana (the open version of Solaris). However, today I upgraded my system and I
cannot run VirtualBox version 6.1.6 r137129. My system has ab AMD FX-6300 Six-core processor and AMD-V is enable. When the I try to run
either Windows XP or Windows 7 I get the following message:

Failed to open a session for the virtual machine Win7.

VirtualBox can't enable the AMD-V extension. Please close all other virtualization programs. (VERR_SVM_IN_USE).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

KVM is not installed in my system:

$ pkg list kvm

pkg list: no packages matching the following patterns are installed:
kvm

Also bhyve is not installed inthis system:

$ pkg list bhyve

pkg list: no packages matching the following patterns are installed:
bhyve

Since I have no idea what is going I thouggt someone here might be able to help fixing this problem.

Regards,

Apostolos

PS Setting export VBOX_HWVIRTEX_IGNORE_SVM_IN_USE=true on a terminal and running VBox from there does not solve the problem...

PSS I have also used a build of VBox 6.1.8 and I see exactly the same behavior"	asyropoulos
19496	Virtualbox 6.1.6 guest screen resize broken	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
19704	VirtualBox 6.1.8 machine restart crash	VirtualBox 6.1.8	2020-07-07T09:25:48Z	2020-07-09T08:15:09Z	2020-07-09T08:15:09Z	"Hello.
VirtualBox 6.1.8-137981 works fine, but randomly when restarting crash the machine being only possible close the machine window and start an new machine window.
LOG are here added.
Excuse not is possible for me in moment test current version, but perhaps has the same issue because that crash when restart is since more of 2 previous versions.
Have an nice day."	Augusto
21448	VirtualBox 7 VM Freezes or UI glitches	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
21336	VirtualBox 7.0.2 interferes with LG Curved UltraWide 40WP95C audio	VirtualBox-7.0.2	2022-12-13T18:39:05Z	2022-12-13T18:39:05Z	2022-12-13T18:39:05Z	"I recently bought a LG Curved UltraWide 40WP95C monitor which is hooked up via DisplayPort to an NVidia 1080 graphics card. I use the built-in speakers in the monitor, which appear as 'LG ULTRAWIDE (NVIDIA High Definition Audio)'

System worked fine until I upgraded to VirtualBox 7.0.2 from 6.1.30. After this the audio device above would disappear if the screen blanked. On unblanking, Windows would have selected a different output device. To get the audio device back I had to start the Windows Device Manager and do a 'Scan for hardware changes'. This then found the device which I could then re-select as the output device.

A few seconds after doing the 'Scan for hardware changes' aI would get an error saying 'USB device not recognized', and an 'Unknown USB Device (Port Reset Failed)' would appear in the Device Manager under 'USB controllers'. Looking in the Windows Event Viewer I found an Error, Information and Error at the approx time this occurred. The messages below have a vendor id in them that maps to Virtual Box.


# Error

Device USB\VID_0000&PID_0001\6&1144d9c0&0&3 was not migrated due to partial or ambiguous match.

Last Device Instance Id: USB\Vid_80EE&Pid_CAFE\5&9a1cce4&0&6
Class Guid: {36fc9e60-c465-11cf-8056-444553540000}
Location Path: 
Migration Rank: 0xF000FFFFFFFFF122
Present: false
Status: 0xC0000719

# information

Device USB\VID_0000&PID_0001\6&1144d9c0&0&3 was configured.

Driver Name: usb.inf
Class Guid: {36fc9e60-c465-11cf-8056-444553540000}
Driver Date: 06/21/2006
Driver Version: 10.0.19041.1949
Driver Provider: Microsoft
Driver Section: BADDEVICE.Dev.NT
Driver Rank: 0xFF0000
Matching Device Id: USB\RESET_FAILURE
Outranked Drivers: usb.inf:USB\RESET_FAILURE:00FF2000
Device Updated: false
Parent Device: USB\ROOT_HUB30\5&24955ba6&0&0


# Error

Device USB\VID_0000&PID_0001\6&1144d9c0&0&3 had a problem starting.

Driver Name: usb.inf
Class Guid: {36fc9e60-c465-11cf-8056-444553540000}
Service: 
Lower Filters: 
Upper Filters: 
Problem: 0x2B
Problem Status: 0x0


After uninstalling VirtualBox completely the problem disappeared and the 'LG ULTRAWIDE (NVIDIA High Definition Audio)' device has remained available, and selected as the default device, whenever the screen blanks.
"	DaveCleland
21496	VirtualBOx 7.0.6 warning for macOS 10.13.x or earlier	VirtualBox-7.0.6	2023-02-12T18:54:14Z	2023-02-12T18:54:14Z	2023-02-12T18:54:14Z	VirtualBOx 7.0.6 installer should render an error if the host system is macOS High Sierra or earlier. The installer should halt and provide option to quit, and should not proceed with a success then render a popup box that it requires macOS Catalina or higher.	danskoya
21191	VirtualBox 7.0.x aborts VM using Windows XP	VirtualBox-7.0.2	2022-10-22T14:08:39Z	2022-10-31T02:04:50Z	2022-10-31T02:04:50Z	VM hosting WinXPSP3 created using VBox 6.1 fails to start (aborts systematically) on VBox 7.0 and 7.0.2	Kyle_Katarn
21291	Virtualbox 7.04: Windows 11 guest hangs with hyper-V paravirtualization enabled	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
21476	Virtualbox 7.x wrong Guest Additions info at Runtime Information	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
20220	VirtualBox Aborts/Crashes without message with Shared Clipboard enabled	VirtualBox 6.1.18	2021-02-24T16:04:44Z	2021-02-24T16:04:44Z	2021-02-24T16:04:44Z	"Since I started using shared clipboard my VirtualBox has been crashing every day or two.  There is no obvious pattern nor activity (from user, me) at time of crash.  My Virtual Box is running a VB6 data upload program 24-7 to upload PV data to internet. There is no message produced by Virtual Box.  There is an Apple crash report.

I referred to this problem on the forum
https://forums.virtualbox.org/viewtopic.php?f=8&t=101856&sid=fcc584fc50e9ceeae4624f76b923a35a

I have attached the Apple Crash.log and VBox.log files.  I have not attached a core dump.  I don't understand the instructions and am not sure if the core dump has to be initialised before the crash or can be collected after the event.
"	MisterWooley
14070	Virtualbox all guest operating system crashed	VirtualBox 4.3.26	2015-04-22T13:11:58Z	2015-09-19T04:30:29Z	2015-09-19T04:30:29Z	"Hi!

My Virtualbox version 4.3.26.98988
My config: Asroc H55M-LE, Intel(R) Core(TM) i3 CPU 540 @ 3.07GHz, 8GB RAM Windows 8.1 Professional 64 bit, ATI RADEON HD 5570

If running guest computer, a few seconds freeze. The same problem 32 or 64 bit.

The work is still in version 4.0.26.

(pasted log file removed)"	agostonl119
1944	VirtualBox Amazon EC2 Integration	VirtualBox 1.6.4	2008-08-12T14:42:57Z	2009-10-20T22:35:18Z	2009-10-20T22:35:18Z	"Hello VirtualBox,

I had an idea for a new feature for VirtualBox.  I think it would be cool if there was an addition to the virtual machine manager that provided seemless upload and interaction with Amazon EC2 services.  I could, for example, upload my virtual machine image through the VirtualBox UI, provided I had an Amazon account.  

Thanks!"	Timothy J. Wisniewski
20947	VirtualBox and VirtualBoxVM segfault when focus changes	VirtualBox 6.1.34	2022-05-19T04:27:42Z	2022-05-19T04:27:42Z	2022-05-19T04:27:42Z	"I'm getting very frequent crashes of both Virtualbox and VirtualBoxVM (the currently running machine) on MacOS 10.15

Usually it happens when the focus enters or leaves the VM, and very frequently when the window of the VM is being closed (either before or after saving the machine state)

I'll attach logs of both crashes as well as the one from Virtualbox

"	Sebbo
18062	VirtualBox Application Error - memory could not be read	VirtualBox 5.2.20	2018-10-18T15:34:24Z	2018-10-18T15:34:24Z	2018-10-18T15:34:24Z	"Updated from 5.2.18 to 5.2.20 last night (with Guest Additions) and left for the day.  Since this morning, two similar crashes - the second is below and attached.  I've updated to Win10 Pro (1809) last week (from previous patch level).  Some additional information that I suspect as relevant ... Dell laptop with Dell D1000 USB3.0 Dock (DisplayLink driver).  Main video, Wired Internet, and USB is run through the dock.

The instruction at 0x00007FFF24DBD680 referenced memory at 0x0000000000000010. The memory could not be read."	Brewsters
14766	VirtualBox breaks USB Drives Permanently Connected	VirtualBox 5.0.6	2015-10-30T11:14:37Z	2015-10-30T11:14:37Z	2015-10-30T11:14:37Z	"I have a Western Digital MyBook 2TB Drive that I have permanently attached to a USB port on my machine.

When I install VirtualBox 5.x, everytime I login to Windows 10 (Administrator account as well as user account with Admin Privileges) and double-click on the drive's folders (i.e. attempting to ""drill down"" into sub-folders on the drive), I get the message ""Device is not ready"".

I have to physically unplug the drive from the USB port and plug it back in again in order to get it to work.

When I restored my Windows 10 system from a system image prior to installing VirtualBox 5.x, the problem went away.
"	Master VB Guru
8991	Virtualbox breaks virtual machines if the host dies unexpectedly	VirtualBox 3.0.8	2011-05-30T19:50:14Z	2011-05-30T19:50:14Z	2011-05-30T19:50:14Z	"If a virtual machine is running and the host shuts down unexpectedly from processor overheating, BSoD or power failure, about 50% of the time, it breaks the VM.
It breaks the actual settings file and not the HD image.
Sometimes it shows
----------------------------------------------------------------------------
Could not load the settings file 'C:\Users\XXXX\.VirtualBox\Machines\Debian\Debian.xml'.
Premature end of data in tag VirtualBox line 3.
Location: 'C:\Users\XXXX\.VirtualBox\Machines\Debian\Debian.xml', line 77 (3), column 5.
Result Code: 
VBOX_E_XML_ERROR (0x80BB000A)
Component: 
VirtualBox
Interface: 
IVirtualBox {3f4ab53a-199b-4526-a91a-93ff62e456b8}
---------------------------------------------------------------------------
And sometimes it hangs for no apparent reason when trying to start of modify the VM.
I can create a new VM with similar settings and reattach the disk image and it works fine but this is an annoyance. The VMs seem excessively fragile.
BTW I just realized I am using a very old version.

"	smeezekitty
17348	Virtualbox built-in debugger does not work	VirtualBox 5.2.0	2017-12-05T17:54:56Z	2017-12-05T17:54:56Z	2017-12-05T17:54:56Z	I am trying to debug an EFI application. The built-in debugger does not stop on any set break points of either kind (br or  bp). Also there is no way to step through the debugging process. First, the VM starts paused, so you must unpause it in order to run any commands in the debugger, otherwise you get an error about VERR_SEM_OUT_OF_TURN. Once the VM is unpaused though, there is no way to stop it from continuously executing until completion even if a breakpoint is set on the entry point, or anywhere really because the break points are never triggered. The stop command causes the debugger and VM to stop functioning all together. To allow stepping through the the code, the debugger should automatically cause a breakpoint when the firmware hands off to the boot option or add a command to enable/disable stepping (the help says there is a command remstep but it does not work because apparently it's external(?) and I can't find information anywhere on how to add this functionality).	apianti
16446	Virtualbox can only use one core with isolcpus	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
19957	Virtualbox can't co-exist with python3 on Ubuntu 20.10 (even though python2 is also installed)	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
16237	VirtualBox can't find Virtual adapters for vlans on Windows 7	VirtualBox 5.1.10	2016-11-28T02:59:11Z	2022-04-17T10:17:19Z	2022-04-17T10:17:19Z	"VirtualBox 5.1.10 , 5.0 and 4.0 can't find Realtek Virtual adapters on Windows 7. It is not possible install ""VirtualBox NDIS6 Bridged Networking Driver"" service on these adapters.
I need these adapters to communicate vlans with virtual machines.
Two realtek physical adapters are used with 7.82.317.2014 driver version.
I use Realtek Ethernet Diagnostic utility ver 2.0.2.8 to create virtual adapters over physical adapters."	cdlt
16705	VirtualBox cannot read partititon scheme on a Win10/Bootcamp combination	VirtualBox 5.1.20	2017-04-27T08:40:27Z	2017-04-28T12:03:08Z	2017-04-28T12:03:08Z	"This is a bug according to the forum topic ''VBoxManage internalcommands createrawvmdk error: Cannot read the partition info...'' ([https://forums.virtualbox.org/viewtopic.php?f=8&t=82508])[[BR]]
On a fresh Win10 partition installed with Bootcamp, the VirtualBox command {{{sudo VBoxManage internalcommands listpartitions -rawdisk /dev/diskX}}} does not list any partitions.
This was tested on VB 5.1.12 to 5.1.20 and on macOS 10.12.2 to 10.12.4."	quantor
18669	Virtualbox causes a leak in cursors as reported by xrestop	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
18744	Virtualbox causes an abend Windows when it opens a Linux VM	VirtualBox 6.0.8	2019-07-05T14:24:23Z	2019-07-05T16:51:53Z	2019-07-05T16:51:53Z	"I Use Virtualbox since several years. My host is a Windows seven with 8 Go RAM. I tried several linux with success until some days. 
I had Linux Mint Plasma, Windows 10 as VM. Windows 10 works ithout problem. But when i tried to access Linux Mint, it abends Windows Seven. I get out Linux Mint from Virtualbox, and tried to re-install it. No success. Each try Abends Windows. 
I tried the Virtualbox 6.0.6 .... : same effects.

'''The message in Windows events is :
'''
Nom du journal :System
Source :       VBoxNetLwf
Date :         05/07/2019 16:08:37
ID de l’événement :12
Catégorie de la tâche :Aucun
Niveau :       Erreur
Mots clés :    Classique
Utilisateur :  N/A
Ordinateur :   Daniel-PC
Description :
Le pilote a détecté une erreur de pilote interne sur \Device\VBoxNetLwf.
XML de l’événement :
<Event xmlns=""http://schemas.microsoft.com/win/2004/08/events/event"">
  <System>
    <Provider Name=""VBoxNetLwf"" />
    <EventID Qualifiers=""49156"">12</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime=""2019-07-05T14:08:37.444012300Z"" />
    <EventRecordID>794248</EventRecordID>
    <Channel>System</Channel>
    <Computer>Daniel-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>\Device\VBoxNetLwf</Data>
    <Binary>0000080001000000000000000C0004C0080000000000000000000000000000000000000000000000BCAEC55CB4500000</Binary>
  </EventData>
</Event>

I Hope to understand this problem, and resolve it !
Thanks."	Speedycool
15268	Virtualbox causes SYSTEM_SERVICE_EXCEPTION on Win10	VirtualBox 5.0.16	2016-03-23T19:24:19Z	2019-08-04T09:26:22Z	2019-08-04T09:26:22Z	"==== How to Reproduce ====

While trying to restart a VM with a saved state computer turns off and a blue screen shows the 
SYSTEM_SERVICE_EXCEPTION message then it restarts.

==== System Information ====

I am running:
VirtualBox VM 5.0.17 r106155 win.amd64 
Windows 10
DMI Product Name: Dell Precision M3800
Host RAM: 16286MB total, 12942MB available
Package type: WINDOWS_64BITS_GENERIC

==== Enabled Plugins ====
No plugins installed
"	Nayz
17476	Virtualbox causes SYSTEM_SERVICE_EXCEPTION on Win10	VirtualBox 5.2.6	2018-01-18T08:41:55Z	2018-02-23T21:22:58Z	2018-02-23T21:22:58Z	"When starting an imported OVA on a fresh install of WinBox my Win10 machine ends up in a BSOD.

Winbox 5.2.6r120293
Windows 10 Enterprise 64bit

"	woli
18828	VirtualBox client crash when opening VBox shared folder	VirtualBox 6.0.10	2019-08-11T09:57:22Z	2019-08-17T09:28:11Z	2019-08-17T09:28:11Z	"Server-OS: Win-10
VirtualBox 6.0
Client-OS: WIN-7

WHen double-click/open a VBOX shared folder in the client, the client chrashes.
"	LarsHes
15814	Virtualbox closes unexpectedly.	VirtualBox 5.1.4	2016-08-17T23:18:11Z	2016-09-27T12:55:22Z	2016-09-27T12:55:22Z	100% reproducible on my x86 Win7 host. Open attached VM, then ''vm settings -> Storage -> select any controller -> click on the blue thingy (add new stor. controller) on the window's bottom -> choose optical drive or hard disk''. After that the whole vbox gui closes.	tico-tico
17243	VirtualBox COM service process doesn't exit on its own	VirtualBox 5.2.0	2017-11-05T11:00:38Z	2017-11-05T16:34:33Z	2017-11-05T16:34:33Z	"I can easily reproduce the issue on my PC using Windows 10 64 bit 1703 and Debian Sid (64 bit), each as a host OS. I was able to bring the COM service in that state were it won't terminate on its own, without involving the NAT/DHCP services (associated with NAT Network), but it's much more difficult, I can't time it properly.[[br]]

The easiest way for me to reproduce the problem is to start my Windows 10 x64 and Windows 7 x64 VMs (both have a saved snapshot), both using NAT Network. I close the VirtualBox Manager and there are no other VirtualBox processes running, except those related to my two VMs. After each guest OS is up and running, I initiate a Windows 10 guest OS shutdown from within the guest. After 3-4 seconds from initiating the Windows 10 guest shutdown, I forcefully terminate the Windows 7 guest using the Close VM dialog (with a restore to the snapshot). The Windows 10 VM takes a few more seconds to shutdown (both VMs are stored on a standard 7200rpm hard-disk drive). After it too has closed, I'm left with the VBoxSVC/VBoxNetNAT/VBoxNetDHCP process tree.[[br]]

I'm attaching some debug logs, from my own Windows debug build of VirtualBox OSE 5.2.0. If someone requires them, I offer the VMs for upload, or process dumps for the release build, logs, or even stack traces for each thread (OSE)."	Mihai Hanor
19362	VirtualBox crash on start ReactOS with BTRFS	VirtualBox 6.1.4	2020-02-29T01:13:37Z	2020-02-29T01:13:37Z	2020-02-29T01:13:37Z	"Install ReactOS 0.4.12 russian language with btrfs guest filesystem. After reboot run is crash.

ReactOS you can get from reactos.org"	kotenok2000
18112	VirtualBox crash on start ReactOS with BTRFS	VirtualBox 5.2.20	2018-11-06T11:47:22Z	2018-11-12T21:35:46Z	2018-11-12T21:35:46Z	"Install ReactOS 0.4.10 russian language with btrfs filesystem. After reboot run is crash.

ReactOS you can get from reactos.org"	seven_vb
18935	VirtualBox Crash When Powering Off / Shutting Down Debian VM on macOS Catalina	VirtualBox 6.0.12	2019-09-17T09:40:49Z	2019-10-10T04:48:45Z	2019-10-10T04:48:45Z	"When powering off and/or sending the shutdown signal to my Debian VM, VirtualBox crashes and leaves the VM in an 'Aborted' status. I have a Windows VM which I can shutdown/power off without any resulting VirtualBox application crash.

This is the stack trace thrown:
{{{
Process:               VirtualBoxVM [4041]
Path:                  /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM
Identifier:            org.virtualbox.app.VirtualBoxVM
Version:               6.0.12 (6.0.12)
Code Type:             X86-64 (Native)
Parent Process:        VBoxSVC [4019]
Responsible:           VirtualBox [4015]
User ID:               501

Date/Time:             2019-09-17 05:10:40.199 -0400
OS Version:            Mac OS X 10.15 (19A558d)
Report Version:        12
Anonymous UUID:        8CD22061-DD5E-08D6-5768-B3DD7D7C0AC5

Sleep/Wake UUID:       CD3BEF75-0E78-4B26-8AAB-FC908122A280

Time Awake Since Boot: 26000 seconds
Time Since Wake:       390 seconds

System Integrity Protection: enabled

Crashed Thread:        12  VMSVGA FIFO

Exception Type:        EXC_CRASH (SIGKILL)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Reason:    LIBSYSTEM, [0x2]

Application Specific Information:
assertion failure: ""((void *)0) == tsd->NSCurrentOpenGLContext"" -> %lld

Thread 0:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        	0x00007fff6f02af76 mach_msg_trap + 10
1   libsystem_kernel.dylib        	0x00007fff6f02b4dc mach_msg + 60
2   com.apple.framework.IOKit     	0x00007fff3a8eef34 io_connect_method + 383
3   com.apple.framework.IOKit     	0x00007fff3a8eed47 IOConnectCallMethod + 186
4   com.apple.framework.IOKit     	0x00007fff3a8ef629 IOConnectCallStructMethod + 35
5   com.apple.IOAccelerator       	0x00007fff5bda2d16 IOAccelGLContextClearDrawable + 50
6   libGPUSupportMercury.dylib    	0x00007fff5868f01e gldAttachDrawable + 1587
7   GLEngine                      	0x00007fff4272ce6c gliAttachDrawableWithOptions + 257
8   com.apple.opengl              	0x00007fff4270ed4d CGLClearDrawable + 116
9   com.apple.AppKit              	0x00007fff353a7f56 __32-[NSOpenGLContext clearDrawable]_block_invoke + 34
10  com.apple.AppKit              	0x00007fff34d2b726 NSPerformVisuallyAtomicChange + 132
11  com.apple.AppKit              	0x00007fff3505da9d -[NSOpenGLContext clearDrawable] + 65
12  VBoxSVGA3DObjC.dylib          	0x000000011d102821 0x11d0fe000 + 18465
13  libdispatch.dylib             	0x00007fff6ee924de _dispatch_client_callout + 8
14  libdispatch.dylib             	0x00007fff6ee9dbd3 _dispatch_main_queue_callback_4CF + 1105
15  com.apple.CoreFoundation      	0x00007fff37ac4540 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9
16  com.apple.CoreFoundation      	0x00007fff37ac3c8a __CFRunLoopRun + 2370
17  com.apple.CoreFoundation      	0x00007fff37ac30c3 CFRunLoopRunSpecific + 499
18  com.apple.HIToolbox           	0x00007fff36650f2d RunCurrentEventLoopInMode + 292
19  com.apple.HIToolbox           	0x00007fff36650c6d ReceiveNextEventCommon + 600
20  com.apple.HIToolbox           	0x00007fff366509f7 _BlockUntilNextEventMatchingListInModeWithFilter + 64
21  com.apple.AppKit              	0x00007fff34cfaee4 _DPSNextEvent + 990
22  com.apple.AppKit              	0x00007fff34cf9c50 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1352
23  com.apple.AppKit              	0x00007fff34cf4395 -[NSApplication run] + 658
24  libqcocoa.dylib               	0x000000010c487eed QCocoaEventDispatcher::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 2205
25  org.qt-project.QtCoreVBox     	0x00000001056d2791 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 401
26  org.qt-project.QtCoreVBox     	0x00000001056d6b4a QCoreApplication::exec() + 346
27  VirtualBoxVM.dylib            	0x000000010539ef93 TrustedMain + 1315
28  org.virtualbox.app.VirtualBoxVM	0x0000000104ce4d36 0x104ce1000 + 15670
29  libdyld.dylib                 	0x00007fff6eee22a5 start + 1

Thread 1:
0   libsystem_pthread.dylib       	0x00007fff6f0eb5b4 start_wqthread + 0

Thread 2:: nspr-1
0   libsystem_kernel.dylib        	0x00007fff6f0325f6 __select + 10
1   VBoxXPCOM.dylib               	0x0000000108e7c8b0 0x108df2000 + 567472
2   VBoxXPCOM.dylib               	0x0000000108e7e6e5 PR_Poll + 1061
3   VBoxXPCOMIPCC.dylib           	0x000000010db72e75 0x10db60000 + 77429
4   VBoxXPCOM.dylib               	0x0000000108e83a96 0x108df2000 + 596630
5   VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
6   VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
7   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
8   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 3:: nspr-2
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   VBoxXPCOM.dylib               	0x0000000108e81dfe PR_WaitCondVar + 254
3   VBoxXPCOM.dylib               	0x0000000108e822ad PR_Wait + 61
4   VBoxXPCOMIPCC.dylib           	0x000000010db6b7b8 0x10db60000 + 47032
5   VBoxXPCOM.dylib               	0x0000000108e56209 0x108df2000 + 410121
6   VBoxXPCOM.dylib               	0x0000000108e83a96 0x108df2000 + 596630
7   VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
8   VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
9   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
10  libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 4:: VBoxSVCWatcher
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x0000000104eb8a3c RTSemEventWait + 364
3   VBoxC.dylib                   	0x000000010dc7f221 0x10db85000 + 1024545
4   VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
5   VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
6   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
7   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 5:: UIMainEventListeningThread
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   VBoxXPCOM.dylib               	0x0000000108e81de7 PR_WaitCondVar + 231
3   VBoxXPCOM.dylib               	0x0000000108e822ad PR_Wait + 61
4   VBoxXPCOMIPCC.dylib           	0x000000010db6571b 0x10db60000 + 22299
5   VBoxXPCOMIPCC.dylib           	0x000000010db653ed 0x10db60000 + 21485
6   VBoxXPCOMIPCC.dylib           	0x000000010db6a039 0x10db60000 + 41017
7   VBoxXPCOM.dylib               	0x0000000108e652fd 0x108df2000 + 471805
8   VBoxXPCOM.dylib               	0x0000000108e644fb 0x108df2000 + 468219
9   VBoxGlobal.dylib              	0x0000000106ab1842 CEventSource::GetEvent(CEventListener const&, int) + 162
10  VBoxGlobal.dylib              	0x00000001068d23b7 0x106820000 + 730039
11  org.qt-project.QtCoreVBox     	0x000000010551896b 0x1054ef000 + 170347
12  libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
13  libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 6:: UIMainEventListeningThread
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x0000000104eb8a3c RTSemEventWait + 364
3   VBoxC.dylib                   	0x000000010dbc6d90 0x10db85000 + 269712
4   VBoxC.dylib                   	0x000000010dbc7fcd 0x10db85000 + 274381
5   VBoxC.dylib                   	0x000000010dd599aa 0x10db85000 + 1919402
6   VBoxGlobal.dylib              	0x0000000106ab1842 CEventSource::GetEvent(CEventListener const&, int) + 162
7   VBoxGlobal.dylib              	0x00000001068d23b7 0x106820000 + 730039
8   org.qt-project.QtCoreVBox     	0x000000010551896b 0x1054ef000 + 170347
9   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
10  libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 7:: TimerLR
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x0000000104eb8a3c RTSemEventWait + 364
3   VBoxRT.dylib                  	0x0000000104e6fb15 0x104d22000 + 1366805
4   VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
5   VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
6   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
7   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 8:: UIMainEventListeningThread
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x0000000104eb8a3c RTSemEventWait + 364
3   VBoxC.dylib                   	0x000000010dbc6d90 0x10db85000 + 269712
4   VBoxC.dylib                   	0x000000010dbc7fcd 0x10db85000 + 274381
5   VBoxC.dylib                   	0x000000010dd599aa 0x10db85000 + 1919402
6   VBoxGlobal.dylib              	0x0000000106ab1842 CEventSource::GetEvent(CEventListener const&, int) + 162
7   VBoxGlobal.dylib              	0x00000001068d23b7 0x106820000 + 730039
8   org.qt-project.QtCoreVBox     	0x000000010551896b 0x1054ef000 + 170347
9   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
10  libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 9:: EMT-0
0   libsystem_kernel.dylib        	0x00007fff6f02b8ea __ioctl + 10
1   libsystem_kernel.dylib        	0x00007fff6f02b8d7 ioctl + 150
2   VBoxRT.dylib                  	0x0000000104ec6d5d 0x104d22000 + 1723741
3   VBoxRT.dylib                  	0x0000000104ec0974 SUPR3PageFreeEx + 292
4   VBoxVMM.dylib                 	0x0000000108b75df8 PGMR3PhysMMIOExDeregister + 488
5   VBoxVMM.dylib                 	0x0000000108b50aa0 0x108af9000 + 359072
6   VBoxVMM.dylib                 	0x0000000108ba438d 0x108af9000 + 701325
7   VBoxVMM.dylib                 	0x0000000108baa317 0x108af9000 + 725783
8   VBoxVMM.dylib                 	0x0000000108baa828 0x108af9000 + 727080
9   VBoxVMM.dylib                 	0x0000000108ba7623 0x108af9000 + 714275
10  VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
11  VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
12  libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
13  libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 10:: com.apple.NSEventThread
0   libsystem_kernel.dylib        	0x00007fff6f02af76 mach_msg_trap + 10
1   libsystem_kernel.dylib        	0x00007fff6f02b4dc mach_msg + 60
2   com.apple.CoreFoundation      	0x00007fff37ac444b __CFRunLoopServiceMachPort + 322
3   com.apple.CoreFoundation      	0x00007fff37ac39e7 __CFRunLoopRun + 1695
4   com.apple.CoreFoundation      	0x00007fff37ac30c3 CFRunLoopRunSpecific + 499
5   com.apple.AppKit              	0x00007fff34d0251a _NSEventThread + 132
6   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
7   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 11:: PDMNsTx
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x0000000104eb9601 0x104d22000 + 1668609
3   VBoxRT.dylib                  	0x0000000104eb9383 0x104d22000 + 1667971
4   VBoxVMM.dylib                 	0x0000000108b6615f PDMR3ThreadIAmSuspending + 79
5   VBoxVMM.dylib                 	0x0000000108b666f8 0x108af9000 + 448248
6   VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
7   VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
8   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
9   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 12 Crashed:: VMSVGA FIFO
0   libsystem_kernel.dylib        	0x00007fff6f031f6e __terminate_with_payload + 10
1   libsystem_kernel.dylib        	0x00007fff6f04c4ba abort_with_payload_wrapper_internal + 119
2   libsystem_kernel.dylib        	0x00007fff6f04c4c5 abort_with_payload + 9
3   libsystem_c.dylib             	0x00007fff6efb8a07 _os_crash_fmt.cold.1 + 55
4   libsystem_c.dylib             	0x00007fff6ef4b876 _os_crash_fmt + 154
5   com.apple.AppKit              	0x00007fff34ebd994 __NSAppKitFinalizeThreadData + 663
6   libsystem_pthread.dylib       	0x00007fff6f0ec413 _pthread_tsd_cleanup + 551
7   libsystem_pthread.dylib       	0x00007fff6f0ef16f _pthread_exit + 70
8   libsystem_pthread.dylib       	0x00007fff6f0ec1cc pthread_exit + 27
9   VBoxRT.dylib                  	0x0000000104ebc14a 0x104d22000 + 1679690
10  libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
11  libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 13:: AioMgr0-N
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x0000000104eb8aeb RTSemEventWait + 539
3   VBoxVMM.dylib                 	0x0000000108c8a66b 0x108af9000 + 1644139
4   VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
5   VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
6   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
7   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 14:: Port0
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x0000000104eb9601 0x104d22000 + 1668609
3   VBoxRT.dylib                  	0x0000000104eb9383 0x104d22000 + 1667971
4   VBoxVMM.dylib                 	0x0000000108b6615f PDMR3ThreadIAmSuspending + 79
5   VBoxVMM.dylib                 	0x0000000108b666f8 0x108af9000 + 448248
6   VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
7   VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
8   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
9   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 15:: ATA-0
0   libsystem_kernel.dylib        	0x00007fff6f02b8ea __ioctl + 10
1   libsystem_kernel.dylib        	0x00007fff6f02b8d7 ioctl + 150
2   VBoxRT.dylib                  	0x0000000104ec6d5d 0x104d22000 + 1723741
3   VBoxRT.dylib                  	0x0000000104ec3e27 SUPSemEventWaitNoResume + 135
4   VBoxDD.dylib                  	0x0000000113cdc71a 0x113cb0000 + 182042
5   VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
6   VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
7   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
8   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 16:: ATA-1
0   libsystem_kernel.dylib        	0x00007fff6f02b8ea __ioctl + 10
1   libsystem_kernel.dylib        	0x00007fff6f02b8d7 ioctl + 150
2   VBoxRT.dylib                  	0x0000000104ec6d5d 0x104d22000 + 1723741
3   VBoxRT.dylib                  	0x0000000104ec3e27 SUPSemEventWaitNoResume + 135
4   VBoxDD.dylib                  	0x0000000113cdc71a 0x113cb0000 + 182042
5   VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
6   VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
7   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
8   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 17:: INTNET-RECV
0   libsystem_kernel.dylib        	0x00007fff6f02b8ea __ioctl + 10
1   libsystem_kernel.dylib        	0x00007fff6f02b8d7 ioctl + 150
2   VBoxRT.dylib                  	0x0000000104ec6d5d 0x104d22000 + 1723741
3   VBoxRT.dylib                  	0x0000000104ebf878 SUPR3CallVMMR0Ex + 312
4   VBoxDD.dylib                  	0x0000000113d1ad28 0x113cb0000 + 437544
5   VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
6   VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
7   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
8   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 18:: INTNET-XMIT
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x0000000104eb9601 0x104d22000 + 1668609
3   VBoxRT.dylib                  	0x0000000104eb9383 0x104d22000 + 1667971
4   VBoxVMM.dylib                 	0x0000000108b6615f PDMR3ThreadIAmSuspending + 79
5   VBoxVMM.dylib                 	0x0000000108b666f8 0x108af9000 + 448248
6   VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
7   VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
8   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
9   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 19:: AMCP Logging Spool
0   libsystem_kernel.dylib        	0x00007fff6f02afb2 semaphore_wait_trap + 10
1   com.apple.audio.caulk         	0x00007fff6b109ec6 caulk::mach::semaphore::wait() + 16
2   com.apple.audio.caulk         	0x00007fff6b105442 caulk::semaphore::timed_wait(double) + 106
3   com.apple.audio.caulk         	0x00007fff6b108a14 caulk::concurrent::details::worker_thread::run() + 30
4   com.apple.audio.caulk         	0x00007fff6b108b64 void* caulk::thread_proxy<std::__1::tuple<caulk::thread::attributes, void (caulk::concurrent::details::worker_thread::*)(), std::__1::tuple<caulk::concurrent::details::worker_thread*> > >(void*) + 45
5   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
6   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 20:
0   libsystem_kernel.dylib        	0x00007fff6f02afb2 semaphore_wait_trap + 10
1   com.apple.audio.caulk         	0x00007fff6b109ec6 caulk::mach::semaphore::wait() + 16
2   com.apple.audio.caulk         	0x00007fff6b105442 caulk::semaphore::timed_wait(double) + 106
3   com.apple.audio.caulk         	0x00007fff6b108a14 caulk::concurrent::details::worker_thread::run() + 30
4   com.apple.audio.caulk         	0x00007fff6b108b64 void* caulk::thread_proxy<std::__1::tuple<caulk::thread::attributes, void (caulk::concurrent::details::worker_thread::*)(), std::__1::tuple<caulk::concurrent::details::worker_thread*> > >(void*) + 45
5   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
6   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 21:: EhciFramer
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x0000000104eb9601 0x104d22000 + 1668609
3   VBoxRT.dylib                  	0x0000000104eb9383 0x104d22000 + 1667971
4   VBoxVMM.dylib                 	0x0000000108b6615f PDMR3ThreadIAmSuspending + 79
5   VBoxVMM.dylib                 	0x0000000108b666f8 0x108af9000 + 448248
6   VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
7   VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
8   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
9   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 22:: nspr-3
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   VBoxXPCOM.dylib               	0x0000000108e81dfe PR_WaitCondVar + 254
3   VBoxXPCOM.dylib               	0x0000000108e822ad PR_Wait + 61
4   VBoxXPCOMIPCC.dylib           	0x000000010db6b7b8 0x10db60000 + 47032
5   VBoxXPCOM.dylib               	0x0000000108e56209 0x108df2000 + 410121
6   VBoxXPCOM.dylib               	0x0000000108e83a96 0x108df2000 + 596630
7   VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
8   VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
9   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
10  libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 23:: VUsbPeriodFrm
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x0000000104eb9601 0x104d22000 + 1668609
3   VBoxRT.dylib                  	0x0000000104eb9383 0x104d22000 + 1667971
4   VBoxVMM.dylib                 	0x0000000108b6615f PDMR3ThreadIAmSuspending + 79
5   VBoxVMM.dylib                 	0x0000000108b666f8 0x108af9000 + 448248
6   VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
7   VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
8   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
9   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 24:
0   libsystem_pthread.dylib       	0x00007fff6f0eb5b4 start_wqthread + 0

Thread 25:
0   libsystem_pthread.dylib       	0x00007fff6f0eb5b4 start_wqthread + 0

Thread 26:
0   libsystem_pthread.dylib       	0x00007fff6f0eb5b4 start_wqthread + 0

Thread 27:: UIThreadWorker
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   org.qt-project.QtCoreVBox     	0x000000010551a170 0x1054ef000 + 176496
3   org.qt-project.QtCoreVBox     	0x0000000105519fab 0x1054ef000 + 176043
4   org.qt-project.QtCoreVBox     	0x0000000105519e82 QWaitCondition::wait(QMutex*, unsigned long) + 162
5   VBoxGlobal.dylib              	0x00000001068fb029 UIThreadPool::dequeueTask(UIThreadWorker*) + 121
6   VBoxGlobal.dylib              	0x00000001068fb190 0x106820000 + 897424
7   org.qt-project.QtCoreVBox     	0x000000010551896b 0x1054ef000 + 170347
8   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
9   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 28:: UIThreadWorker
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   org.qt-project.QtCoreVBox     	0x000000010551a170 0x1054ef000 + 176496
3   org.qt-project.QtCoreVBox     	0x0000000105519fab 0x1054ef000 + 176043
4   org.qt-project.QtCoreVBox     	0x0000000105519e82 QWaitCondition::wait(QMutex*, unsigned long) + 162
5   VBoxGlobal.dylib              	0x00000001068fb029 UIThreadPool::dequeueTask(UIThreadWorker*) + 121
6   VBoxGlobal.dylib              	0x00000001068fb190 0x106820000 + 897424
7   org.qt-project.QtCoreVBox     	0x000000010551896b 0x1054ef000 + 170347
8   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
9   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 29:
0   libsystem_kernel.dylib        	0x00007fff6f02afca semaphore_timedwait_trap + 10
1   libdispatch.dylib             	0x00007fff6ee929eb _dispatch_sema4_timedwait + 76
2   libdispatch.dylib             	0x00007fff6ee92e12 _dispatch_semaphore_wait_slow + 58
3   libdispatch.dylib             	0x00007fff6eea0645 _dispatch_worker_thread + 318
4   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
5   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 30:: VMPwrDwn
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x0000000104eb8aeb RTSemEventWait + 539
3   VBoxVMM.dylib                 	0x0000000108baa24e VMR3ReqWait + 110
4   VBoxVMM.dylib                 	0x0000000108baa1bf VMR3ReqQueue + 623
5   VBoxVMM.dylib                 	0x0000000108baa00f VMR3ReqQueue + 191
6   VBoxVMM.dylib                 	0x0000000108ba938c VMR3ReqCallVU + 380
7   VBoxVMM.dylib                 	0x0000000108ba91d2 0x108af9000 + 721362
8   VBoxVMM.dylib                 	0x0000000108ba3cc9 VMR3Destroy + 249
9   VBoxC.dylib                   	0x000000010dbf08c3 0x10db85000 + 440515
10  VBoxC.dylib                   	0x000000010dc17047 0x10db85000 + 598087
11  VBoxC.dylib                   	0x000000010dbd510c 0x10db85000 + 327948
12  VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
13  VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
14  libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
15  libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 12 crashed with X86 Thread State (64-bit):
  rax: 0x0000000000000000  rbx: 0x0000000000000200  rcx: 0x0000700007a7eda8  rdx: 0x0000000000000000
  rdi: 0x0000000000000fc9  rsi: 0x0000000000000012  rbp: 0x0000700007a7edf0  rsp: 0x0000700007a7eda8
   r8: 0x0000000000000054   r9: 0x00007fea858919e0  r10: 0x0000700007a7ee60  r11: 0x0000000000000206
  r12: 0x0000000000000054  r13: 0x0000700007a7ee60  r14: 0x0000000000000002  r15: 0x0000000000000012
  rip: 0x00007fff6f031f6e  rfl: 0x0000000000000206  cr2: 0x00007fff6f0371dd
  
Logical CPU:     0
Error Code:      0x02000208
Trap Number:     133


Binary Images:
       0x104ce1000 -        0x104d02ff7 +org.virtualbox.app.VirtualBoxVM (6.0.12 - 6.0.12) <0ED710D1-15CE-3432-97C3-40B0DD778F9B> /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM
       0x104d22000 -        0x105282347 +VBoxRT.dylib (0) <44B42923-83C4-366C-AE1F-813AE54FEE60> /Applications/VirtualBox.app/Contents/MacOS/VBoxRT.dylib
       0x105397000 -        0x105484ff7 +VirtualBoxVM.dylib (0) <2B18B9FF-A9BA-35AC-94F4-2EF406259714> /Applications/VirtualBox.app/Contents/MacOS/VirtualBoxVM.dylib
       0x1054dd000 -        0x1054e6ff7 +org.qt-project.QtMacExtrasVBox (5.6 - 5.6.3) <AC6F0DC8-BF41-3A20-B803-656B301B8CDF> /Applications/VirtualBox.app/Contents/Frameworks/QtMacExtrasVBox.framework/Versions/5/QtMacExtrasVBox
       0x1054ef000 -        0x105a16ff7 +org.qt-project.QtCoreVBox (5.6 - 5.6.3) <3A7A08E0-9422-393E-BD97-FD15E751434C> /Applications/VirtualBox.app/Contents/Frameworks/QtCoreVBox.framework/Versions/5/QtCoreVBox
       0x105acc000 -        0x105fa7ff7 +org.qt-project.QtGuiVBox (5.6 - 5.6.3) <80F8D761-23D7-381D-B8D5-1C0C130F7876> /Applications/VirtualBox.app/Contents/Frameworks/QtGuiVBox.framework/Versions/5/QtGuiVBox
       0x10609b000 -        0x1065a4fff +org.qt-project.QtWidgetsVBox (5.6 - 5.6.3) <5DFD063A-1901-39D3-90FB-138EFE7C6A9E> /Applications/VirtualBox.app/Contents/Frameworks/QtWidgetsVBox.framework/Versions/5/QtWidgetsVBox
       0x106707000 -        0x10673bfff +org.qt-project.QtPrintSupportVBox (5.6 - 5.6.3) <4C8D48EF-FC21-3BE7-895F-584399F0B308> /Applications/VirtualBox.app/Contents/Frameworks/QtPrintSupportVBox.framework/Versions/5/QtPrintSupportVBox
       0x10675f000 -        0x10679efff +org.qt-project.QtOpenGLVBox (5.6 - 5.6.3) <F75D0235-BFE7-3966-A3C4-CFEA758B9A71> /Applications/VirtualBox.app/Contents/Frameworks/QtOpenGLVBox.framework/Versions/5/QtOpenGLVBox
       0x1067c1000 -        0x106814fff +VBoxDDU.dylib (0) <5DCF996A-036C-3DF7-A65F-4FDA755B5DFA> /Applications/VirtualBox.app/Contents/MacOS/VBoxDDU.dylib
       0x106820000 -        0x108956fff +VBoxGlobal.dylib (0) <66B224F5-CBE3-3D76-9DB1-A9D430E041A5> /Applications/VirtualBox.app/Contents/MacOS/VBoxGlobal.dylib
       0x108af9000 -        0x108d7bfff +VBoxVMM.dylib (0) <1A356DAB-4305-30E8-84C1-579E86EEF107> /Applications/VirtualBox.app/Contents/MacOS/VBoxVMM.dylib
       0x108df2000 -        0x108ea3ff7 +VBoxXPCOM.dylib (0) <817EE585-D05F-373A-B68D-200A0C997CDF> /Applications/VirtualBox.app/Contents/MacOS/VBoxXPCOM.dylib
       0x10a4e5000 -        0x10a4e9ff7 +VDPluginCrypt.dylib (0) <1D1D34F1-0821-34FB-8998-9888E46D6C5A> /Applications/VirtualBox.app/Contents/MacOS/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/darwin.amd64/VDPluginCrypt.dylib
       0x10a52b000 -        0x10a5b991f  dyld (732.2) <BAB55B81-E18F-3129-BD61-CC42B9F21198> /usr/lib/dyld
       0x10c465000 -        0x10c5a4fff +libqcocoa.dylib (0) <FA226E50-20A3-3C6D-B04E-9262D65300BC> /Applications/VirtualBox.app/Contents/plugins/platforms/libqcocoa.dylib
       0x10db52000 -        0x10db55047  libobjc-trampolines.dylib (779) <81578FF6-5EE6-3FE5-B69F-31B977F45D58> /usr/lib/libobjc-trampolines.dylib
       0x10db60000 -        0x10db77fff +VBoxXPCOMIPCC.dylib (0) <3F5A7F5F-392A-3855-8091-EAD834051036> /Applications/VirtualBox.app/Contents/MacOS/components/VBoxXPCOMIPCC.dylib
       0x10db85000 -        0x10df7dfff +VBoxC.dylib (0) <B1A67512-FDC8-38A5-84F2-D8AA9EB23C53> /Applications/VirtualBox.app/Contents/MacOS/components/VBoxC.dylib
       0x10dfc2000 -        0x10dfc5ff7 +VBoxSVCM.dylib (0) <55D3234B-0B5B-3AED-AA2E-3F0528414687> /Applications/VirtualBox.app/Contents/MacOS/components/VBoxSVCM.dylib
       0x10e02f000 -        0x10e031ff7 +VBoxPuelMainVM.dylib (0) <CE286393-79E4-3E6E-8922-4A933C4397E5> /Applications/VirtualBox.app/Contents/MacOS/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/darwin.amd64/VBoxPuelMainVM.dylib
       0x10e2ab000 -        0x10e2bcffb  com.apple.iokit.IOHIDLib (2.0.0 - 2.0.0) <70FBC258-44BF-3C42-A997-3D0EDF27BC59> /System/Library/Extensions/IOHIDFamily.kext/Contents/PlugIns/IOHIDLib.plugin/Contents/MacOS/IOHIDLib
       0x113171000 -        0x113194ff7 +VBoxHostWebcam.dylib (0) <17590F9F-9794-362E-8C62-578DC28C0EEC> /Applications/VirtualBox.app/Contents/MacOS/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/darwin.amd64/VBoxHostWebcam.dylib
       0x113cb0000 -        0x113ffffff +VBoxDD.dylib (0) <94B8B3E4-5B8D-342A-9E6D-0CEDC6BBC4F5> /Applications/VirtualBox.app/Contents/MacOS/VBoxDD.dylib
       0x114691000 -        0x1146e8ff7 +VBoxDD2.dylib (0) <8AE831BF-11EF-3DC0-B31E-BC1B6EFC13CF> /Applications/VirtualBox.app/Contents/MacOS/VBoxDD2.dylib
       0x1146ee000 -        0x1146fffff +VBoxEhciR3.dylib (0) <8EBE5D51-1BB4-39F0-99FA-2D9FD22510DD> /Applications/VirtualBox.app/Contents/MacOS/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/darwin.amd64/VBoxEhciR3.dylib
       0x114704000 -        0x11470fff7 +VBoxNvmeR3.dylib (0) <BE5FF50A-1122-3A61-8504-FC19E2E5F988> /Applications/VirtualBox.app/Contents/MacOS/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/darwin.amd64/VBoxNvmeR3.dylib
       0x114713000 -        0x11471ffff +VBoxUsbCardReaderR3.dylib (0) <AD3E1939-B325-3A8D-A571-A3179BB0CD32> /Applications/VirtualBox.app/Contents/MacOS/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/darwin.amd64/VBoxUsbCardReaderR3.dylib
       0x114722000 -        0x11472eff7 +VBoxUsbWebcamR3.dylib (0) <4CC64783-6A10-3ED0-B5C9-B759CFFAE3EB> /Applications/VirtualBox.app/Contents/MacOS/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/darwin.amd64/VBoxUsbWebcamR3.dylib
       0x11d0bf000 -        0x11d0f2fff +VBoxSVGA3D.dylib (0) <C997472A-A9F8-3F84-B18F-9FDFEEBC2397> /Applications/VirtualBox.app/Contents/MacOS/VBoxSVGA3D.dylib
       0x11d0fe000 -        0x11d104fff +VBoxSVGA3DObjC.dylib (0) <94F57D1A-3216-3E5D-90C9-5C29EAE73BD1> /Applications/VirtualBox.app/Contents/MacOS/VBoxSVGA3DObjC.dylib
       0x14b5f0000 -        0x14b73dff7  com.apple.audio.units.Components (1.14 - 1.14) <0CAF1178-C08B-3A0D-BE03-6D1A376CD37F> /System/Library/Components/CoreAudio.component/Contents/MacOS/CoreAudio
    0x7fff2b013000 -     0x7fff2b262ff8  com.apple.RawCamera.bundle (9.00.1 - 1200.22) <4E4BD2AA-ABAF-3CC3-B070-D877CA4EBEB9> /System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera
    0x7fff2e758000 -     0x7fff2ec5cff7  com.apple.driver.AppleIntelBDWGraphicsGLDriver (14.0.67 - 14.0.0) <5FF8F09F-EFE6-3D81-8FB8-4DF5843665EF> /System/Library/Extensions/AppleIntelBDWGraphicsGLDriver.bundle/Contents/MacOS/AppleIntelBDWGraphicsGLDriver
    0x7fff2ec5d000 -     0x7fff2ed5dffd  com.apple.driver.AppleIntelBDWGraphicsMTLDriver (14.0.67 - 14.0.0) <C75B3FE7-984B-3842-A18F-F97778C22FE0> /System/Library/Extensions/AppleIntelBDWGraphicsMTLDriver.bundle/Contents/MacOS/AppleIntelBDWGraphicsMTLDriver
    0x7fff3343b000 -     0x7fff3343fffb  com.apple.agl (3.3.3 - AGL-3.3.3) <EEB8C1EE-479A-3DA6-93D0-B8117D289146> /System/Library/Frameworks/AGL.framework/Versions/A/AGL
    0x7fff33440000 -     0x7fff33698ffa  com.apple.avfoundation (2.0 - 1722.27.4.4) <2EFEF1B1-CDC8-38BA-BA29-0B467ED109D0> /System/Library/Frameworks/AVFoundation.framework/Versions/A/AVFoundation
    0x7fff33699000 -     0x7fff33764ff8  com.apple.audio.AVFAudio (1.0 - ???) <D0AEA054-EC5B-3A92-B672-F9CA22E8EB23> /System/Library/Frameworks/AVFoundation.framework/Versions/A/Frameworks/AVFAudio.framework/Versions/A/AVFAudio
    0x7fff33884000 -     0x7fff33884fff  com.apple.Accelerate (1.11 - Accelerate 1.11) <229BBA70-25E1-363C-9A46-B27BD69269F6> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
    0x7fff33885000 -     0x7fff3389bff7  libCGInterfaces.dylib (524.2) <7F08322A-4AA0-3677-91CD-9D1588BDBE39> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/Libraries/libCGInterfaces.dylib
    0x7fff3389c000 -     0x7fff33f07fdf  com.apple.vImage (8.1 - 524.2) <45A48EA9-49AA-33A0-B830-AF754BD01009> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage
    0x7fff33f08000 -     0x7fff34170fff  libBLAS.dylib (1303) <112B19CC-925A-3E28-8B32-2002D30A37FA> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib
    0x7fff34171000 -     0x7fff34460fdf  libBNNS.dylib (144.11.2) <726C490D-8BDB-3488-9B5A-531F15E42259> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBNNS.dylib
    0x7fff34462000 -     0x7fff34807fff  libLAPACK.dylib (1303) <5C248B39-F233-3074-A3A5-AF8F436FBF87> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib
    0x7fff34808000 -     0x7fff3481dff8  libLinearAlgebra.dylib (1303) <C21931B4-F6BD-324D-A2D9-F13EE8AFB29E> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLinearAlgebra.dylib
    0x7fff3481e000 -     0x7fff34823ff3  libQuadrature.dylib (7) <826897ED-B7AD-33DC-B9CB-F9787784F312> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libQuadrature.dylib
    0x7fff34824000 -     0x7fff34894fff  libSparse.dylib (103) <55467C29-2096-36AB-8A6D-5231A342809D> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparse.dylib
    0x7fff34895000 -     0x7fff348a7fef  libSparseBLAS.dylib (1303) <3244FCAF-A1FE-3248-AF22-BFB3E9D12555> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparseBLAS.dylib
    0x7fff348a8000 -     0x7fff34a81ffb  libvDSP.dylib (735) <EE2CBD92-EA9A-3288-B9B4-D61AA08F1114> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib
    0x7fff34a82000 -     0x7fff34b3dfd3  libvMisc.dylib (735) <3859618E-D36E-3190-8BC8-7AF170C7A6C8> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib
    0x7fff34b3e000 -     0x7fff34b3efff  com.apple.Accelerate.vecLib (3.11 - vecLib 3.11) <79C1A1C7-E97A-3B7A-8737-444B402A7AA0> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib
    0x7fff34b3f000 -     0x7fff34b9dffe  com.apple.Accounts (113 - 113) <57677F31-13F3-3197-B97A-DE57BD03BFC8> /System/Library/Frameworks/Accounts.framework/Versions/A/Accounts
    0x7fff34ce3000 -     0x7fff35a8eff4  com.apple.AppKit (6.9 - 1877) <9E8E14EA-7B3B-3412-A5C5-B7DC97D5FAD2> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
    0x7fff35ade000 -     0x7fff35adefff  com.apple.ApplicationServices (48 - 50) <981D6A76-AA72-3203-98F5-4989FF2F6058> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices
    0x7fff35adf000 -     0x7fff35b4afff  com.apple.ApplicationServices.ATS (377 - 492) <B5739AFF-FF49-3EF7-B123-922300E3E5BE> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS
    0x7fff35be3000 -     0x7fff35c21ffa  libFontRegistry.dylib (273) <9E8A133C-1DE1-3902-A513-2D474A95CDF0> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib
    0x7fff35c7c000 -     0x7fff35cabff7  com.apple.ATSUI (1.0 - 1) <9391C527-15CE-3108-8922-CF0C2A50C082> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATSUI.framework/Versions/A/ATSUI
    0x7fff35cac000 -     0x7fff35cb0ff3  com.apple.ColorSyncLegacy (4.13.0 - 1) <EBA4F56C-3C82-3788-A168-3E77E116724B> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSyncLegacy.framework/Versions/A/ColorSyncLegacy
    0x7fff35d4b000 -     0x7fff35da1ff2  com.apple.HIServices (1.22 - 671) <E744DE5F-F775-3BFA-BBCB-4D38ADFCAA2A> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices
    0x7fff35da2000 -     0x7fff35db0fff  com.apple.LangAnalysis (1.7.0 - 1.7.0) <02AE4AE3-1CD9-3193-B5F3-2C1C6D435F18> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis
    0x7fff35db1000 -     0x7fff35df6ff2  com.apple.print.framework.PrintCore (15 - 516) <43213BE5-C5E1-3AA8-8AFD-949AFF9FB2C5> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore
    0x7fff35df7000 -     0x7fff35e01fff  com.apple.QD (4.0 - 413) <EFC01D3C-9012-3FCF-9149-457F530A43F0> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD
    0x7fff35e02000 -     0x7fff35e0fff0  com.apple.speech.synthesis.framework (9.0.20 - 9.0.20) <A5CCADE3-B307-3FAD-A7E8-A77DDFF026CA> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis
    0x7fff35e10000 -     0x7fff35eddff2  com.apple.audio.toolbox.AudioToolbox (1.14 - 1.14) <1961714B-4533-3C6E-836C-1C73511EF4D3> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
    0x7fff35edf000 -     0x7fff35edffff  com.apple.audio.units.AudioUnit (1.14 - 1.14) <4CD694DA-A074-3BC0-BB50-724D16345F18> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
    0x7fff36255000 -     0x7fff365cbffe  com.apple.CFNetwork (1110 - 1110) <EC97BFD7-8745-30F4-9DB4-FD8281C84CC9> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
    0x7fff36641000 -     0x7fff36641fff  com.apple.Carbon (160 - 162) <09CEF7B7-0113-32C3-A3DF-4177A1CFD97C> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
    0x7fff36642000 -     0x7fff36645ffb  com.apple.CommonPanels (1.2.6 - 101) <930A9DD4-B4BF-3D73-8B81-2D46018BB2E4> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels
    0x7fff36646000 -     0x7fff3693affc  com.apple.HIToolbox (2.1.1 - 987.1) <2AD583EF-7EB9-3EFB-BA74-D230BE62F0CC> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox
    0x7fff3693b000 -     0x7fff3693eff3  com.apple.help (1.3.8 - 68) <CA52ABA0-636A-39AA-98C0-A1B901A5F4F4> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help
    0x7fff3693f000 -     0x7fff36944ff7  com.apple.ImageCapture (9.0 - 1600.1) <D4515843-F958-3910-A738-576FD43D3C78> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture
    0x7fff36945000 -     0x7fff36945fff  com.apple.ink.framework (10.15 - 227) <BA11FA6C-AEAA-3688-8812-9CA16EA11D03> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink
    0x7fff36946000 -     0x7fff36960ff2  com.apple.openscripting (1.7 - 185) <7CFD4E50-FD41-39C7-BA76-6BA260BD91F9> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting
    0x7fff36981000 -     0x7fff36981fff  com.apple.print.framework.Print (15 - 271) <CB0E6F07-19E3-3207-9B7B-267F04DF6F73> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print
    0x7fff36982000 -     0x7fff36984ff7  com.apple.securityhi (9.0 - 55008) <E8AE6A05-5F07-3300-9FEA-8C29C0B45566> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI
    0x7fff36985000 -     0x7fff3698bff7  com.apple.speech.recognition.framework (6.0.3 - 6.0.3) <819268CF-2A9D-3321-A826-535CB1F1E694> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition
    0x7fff36b25000 -     0x7fff36b25fff  com.apple.Cocoa (6.11 - 23) <F8489AB5-835B-3637-B8A1-64FCF8AB5F7A> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
    0x7fff36b33000 -     0x7fff36d1eff7  com.apple.ColorSync (4.13.0 - 3394.1.4.1) <32A1AEE9-C3AA-3535-9C72-D89955D2DE85> /System/Library/Frameworks/ColorSync.framework/Versions/A/ColorSync
    0x7fff3700a000 -     0x7fff37519ffa  com.apple.audio.CoreAudio (5.0 - 5.0) <7A785340-4CE5-3130-94AB-DFA51C69A4E7> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
    0x7fff3756c000 -     0x7fff375a3ff2  com.apple.CoreBluetooth (1.0 - 1) <6767CD70-533B-3114-9F9E-733B9E72C828> /System/Library/Frameworks/CoreBluetooth.framework/Versions/A/CoreBluetooth
    0x7fff375a4000 -     0x7fff3797efe8  com.apple.CoreData (120 - 969.2) <BFA70A01-DC83-3A1A-A7DE-8DFEB4269304> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
    0x7fff3797f000 -     0x7fff37a88ffe  com.apple.CoreDisplay (1.0 - 107) <91C74B12-4357-3717-B00B-A21DD0C722CE> /System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay
    0x7fff37a89000 -     0x7fff37f08fff  com.apple.CoreFoundation (6.9 - 1671.12) <6500A498-7434-3C1C-A9EB-1FDB75CB2CC1> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
    0x7fff37f0a000 -     0x7fff38582ff0  com.apple.CoreGraphics (2.0 - 1348.4.4.3) <E16AE614-C7B6-3DC4-904D-B130C7B9CF72> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics
    0x7fff38590000 -     0x7fff388ebffe  com.apple.CoreImage (15.0.0 - 900.4) <63DB7953-3DD0-3CA2-9709-68A9A09837B0> /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage
    0x7fff38caa000 -     0x7fff38e1aff4  com.apple.CoreMedia (1.0 - 2501.27.4.3) <056F96CA-82E5-3DD0-97D8-A700F12D16BB> /System/Library/Frameworks/CoreMedia.framework/Versions/A/CoreMedia
    0x7fff38e1b000 -     0x7fff38e7cff6  com.apple.CoreMediaIO (1000.0 - 5125.1) <70E47B45-B017-3893-97E4-E72729A4F936> /System/Library/Frameworks/CoreMediaIO.framework/Versions/A/CoreMediaIO
    0x7fff38f03000 -     0x7fff38f03fff  com.apple.CoreServices (1068.2 - 1068.2) <46CA4F06-5983-3D08-B972-1382381CDAC1> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
    0x7fff38f04000 -     0x7fff38f87ff7  com.apple.AE (836 - 836) <E65EB197-5D66-3EBC-BCA0-A9D8B4F6EC2B> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE
    0x7fff38f88000 -     0x7fff39269fff  com.apple.CoreServices.CarbonCore (1216 - 1216) <FCE3A1CF-EE79-3FF7-A12F-8AFF74607E8A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
    0x7fff3926a000 -     0x7fff392b7ff1  com.apple.DictionaryServices (1.2 - 321) <648A5391-99DC-3AD1-B68A-9EB26AED62C1> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices
    0x7fff392b8000 -     0x7fff392c0ff7  com.apple.CoreServices.FSEvents (1268.0.6 - 1268.0.6) <78D2AB1A-9053-3D32-8C18-C1DD31FF9400> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/FSEvents.framework/Versions/A/FSEvents
    0x7fff392c1000 -     0x7fff394f8ffd  com.apple.LaunchServices (1068.2 - 1068.2) <DCB37CF3-15A4-3A97-94B9-7EC6788BAEB7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices
    0x7fff394f9000 -     0x7fff39591ff9  com.apple.Metadata (10.7.0 - 2064.1) <A8603546-69B1-39C4-B4D5-83F2E21013D9> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata
    0x7fff39592000 -     0x7fff395bfff7  com.apple.CoreServices.OSServices (1068.2 - 1068.2) <CB16982C-826A-3444-BCDB-754E48EFEA6E> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices
    0x7fff395c0000 -     0x7fff39627fff  com.apple.SearchKit (1.4.1 - 1.4.1) <0068BD72-CF2B-34E4-B461-002D5E56C31C> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit
    0x7fff39628000 -     0x7fff3964cffd  com.apple.coreservices.SharedFileList (130 - 130) <F55A2C27-F648-3608-8B71-43E8EC225F2E> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SharedFileList.framework/Versions/A/SharedFileList
    0x7fff39972000 -     0x7fff39b25ff6  com.apple.CoreText (643.1 - 643.1) <02D49B30-84A8-32E0-9DD5-06E304B0D498> /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText
    0x7fff39b26000 -     0x7fff39b6afff  com.apple.CoreVideo (1.8 - 334.0) <54CC4AD8-7F5C-37D5-A26D-9C8C8A72BD41> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
    0x7fff39b6b000 -     0x7fff39bf8ff1  com.apple.framework.CoreWLAN (13.0 - 1448) <2894EC6A-F29E-393F-9105-7436B83C2E57> /System/Library/Frameworks/CoreWLAN.framework/Versions/A/CoreWLAN
    0x7fff39dc2000 -     0x7fff39dcdff7  com.apple.DirectoryService.Framework (10.15 - 220.11.1) <EADC285E-3166-3474-915B-F905F840D19E> /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryService
    0x7fff39dce000 -     0x7fff39e79ff0  com.apple.DiscRecording (9.0.3 - 9030.4.5) <6F1FE0D6-907E-3309-A53E-B4B01F9355E5> /System/Library/Frameworks/DiscRecording.framework/Versions/A/DiscRecording
    0x7fff39e9e000 -     0x7fff39ea4ff7  com.apple.DiskArbitration (2.7 - 2.7) <23104F29-F120-354B-97BE-4514A675BB14> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
    0x7fff3a097000 -     0x7fff3a1b9ff3  com.apple.FileProvider (252 - 252) <FEF218FA-EAEA-32C5-82DB-5B3843FB7446> /System/Library/Frameworks/FileProvider.framework/Versions/A/FileProvider
    0x7fff3a1d1000 -     0x7fff3a598ff3  com.apple.Foundation (6.9 - 1671.12) <D1CCD387-08E0-338D-B93D-C3BA470CE727> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
    0x7fff3a605000 -     0x7fff3a634ff3  com.apple.GSS (4.0 - 2.0) <9520F096-C643-36D7-B8CB-3922B6E6D7EC> /System/Library/Frameworks/GSS.framework/Versions/A/GSS
    0x7fff3a76a000 -     0x7fff3a882ffd  com.apple.Bluetooth (7.0.0 - 7.0.0f4) <D130CB4B-1350-3278-8D3F-A11114A996DC> /System/Library/Frameworks/IOBluetooth.framework/Versions/A/IOBluetooth
    0x7fff3a8e6000 -     0x7fff3a989ff3  com.apple.framework.IOKit (2.0.2 - 1726.0.14) <E23D2220-479C-3DCC-8CF5-A9A6B497ECE4> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
    0x7fff3a98b000 -     0x7fff3a99bff4  com.apple.IOSurface (269.6 - 269.6) <1E49AD7D-6067-3599-B015-765047D58C13> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface
    0x7fff3aa0e000 -     0x7fff3ab69fee  com.apple.ImageIO.framework (3.3.0 - 1972.3.4.2) <9770B095-F95D-328B-A1DE-6978C434ABA0> /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO
    0x7fff3ab6a000 -     0x7fff3ab6dfff  libGIF.dylib (1972.3.4.2) <F89D4FB5-AFA1-3617-B740-D148B5D635A1> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib
    0x7fff3ab6e000 -     0x7fff3ac28fe7  libJP2.dylib (1972.3.4.2) <33CC7F2A-1E5A-3302-8A96-0C8EA38E5F90> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib
    0x7fff3ac29000 -     0x7fff3ac4dfef  libJPEG.dylib (1972.3.4.2) <FA7B791A-9F06-30B7-917F-94E022A2AE20> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib
    0x7fff3aecb000 -     0x7fff3aee5fe7  libPng.dylib (1972.3.4.2) <576BD7D2-FCBF-31AB-BCB3-8935AD9CAD2C> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib
    0x7fff3aee6000 -     0x7fff3aee7fff  libRadiance.dylib (1972.3.4.2) <06F8438E-10A6-3D6D-BC00-AB49CD5CE602> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib
    0x7fff3aee8000 -     0x7fff3af31fef  libTIFF.dylib (1972.3.4.2) <5535A3DB-501F-36B0-830E-108684CFA4DA> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib
    0x7fff3c34a000 -     0x7fff3c35cff3  com.apple.Kerberos (3.0 - 1) <91DF5D16-E721-39F0-A77B-87DA6032F870> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos
    0x7fff3c35d000 -     0x7fff3c35dfff  libHeimdalProxy.dylib (77) <51DB9CFB-808F-32E8-BB34-39F6702DBDED> /System/Library/Frameworks/Kerberos.framework/Versions/A/Libraries/libHeimdalProxy.dylib
    0x7fff3c35e000 -     0x7fff3c394fff  com.apple.LDAPFramework (2.4.28 - 194.5) <32FAF82F-BA91-366A-83A3-CDFF6CDD1AF9> /System/Library/Frameworks/LDAP.framework/Versions/A/LDAP
    0x7fff3c6ee000 -     0x7fff3c6f8fff  com.apple.MediaAccessibility (1.0 - 125) <DAF5DD8F-A725-320E-8D7E-2C39CBE33F44> /System/Library/Frameworks/MediaAccessibility.framework/Versions/A/MediaAccessibility
    0x7fff3c7c1000 -     0x7fff3d287ffb  com.apple.MediaToolbox (1.0 - 2501.27.4.3) <1BA60E69-C647-3073-850A-BDC3DAD01BC8> /System/Library/Frameworks/MediaToolbox.framework/Versions/A/MediaToolbox
    0x7fff3d289000 -     0x7fff3d34bff1  com.apple.Metal (211.53 - 211.53) <EA59DEFD-F6DD-3DC5-9E6F-8152CD5F121C> /System/Library/Frameworks/Metal.framework/Versions/A/Metal
    0x7fff3d368000 -     0x7fff3d3a4ff3  com.apple.MetalPerformanceShaders.MPSCore (1.0 - 1) <54EC6486-7A3E-39D3-B213-EFCC4110E511> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSCore.framework/Versions/A/MPSCore
    0x7fff3d3a5000 -     0x7fff3d42bfe6  com.apple.MetalPerformanceShaders.MPSImage (1.0 - 1) <144A9994-9AD3-340D-A890-C7F10DDEF489> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSImage.framework/Versions/A/MPSImage
    0x7fff3d42c000 -     0x7fff3d451ff0  com.apple.MetalPerformanceShaders.MPSMatrix (1.0 - 1) <6F07D520-B36C-38D5-810B-A95BA5F79B04> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSMatrix.framework/Versions/A/MPSMatrix
    0x7fff3d452000 -     0x7fff3d467ffc  com.apple.MetalPerformanceShaders.MPSNDArray (1.0 - 1) <73DBE1D5-89C4-3410-95DA-A384BF9C2C1E> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSNDArray.framework/Versions/A/MPSNDArray
    0x7fff3d468000 -     0x7fff3d5c7ff4  com.apple.MetalPerformanceShaders.MPSNeuralNetwork (1.0 - 1) <24338B34-481D-3564-917C-CD1DB243FD12> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSNeuralNetwork.framework/Versions/A/MPSNeuralNetwork
    0x7fff3d5c8000 -     0x7fff3d616ff7  com.apple.MetalPerformanceShaders.MPSRayIntersector (1.0 - 1) <75ABA9EB-752E-3E7E-BFBA-19806FB65924> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSRayIntersector.framework/Versions/A/MPSRayIntersector
    0x7fff3d617000 -     0x7fff3d618ff5  com.apple.MetalPerformanceShaders.MetalPerformanceShaders (1.0 - 1) <5EA47648-76E9-37CD-A2FC-A0083A769665> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/MetalPerformanceShaders
    0x7fff3e55e000 -     0x7fff3e56affe  com.apple.NetFS (6.0 - 4.0) <10ECF7E4-98A5-3751-B7AC-0AAAF0050777> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS
    0x7fff3e56b000 -     0x7fff3e6aeff6  com.apple.Network (1.0 - 1) <5C29B0D5-3811-32A8-9FF4-CA112F9526F4> /System/Library/Frameworks/Network.framework/Versions/A/Network
    0x7fff410cc000 -     0x7fff410d4fff  libcldcpuengine.dylib (2.12.7) <A9ECDF96-4888-35CB-9BEF-96D8A84E5106> /System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/libcldcpuengine.dylib
    0x7fff410d5000 -     0x7fff4112dff7  com.apple.opencl (3.5 - 3.5) <0F4232DF-854F-3852-8881-D48FF303D4D3> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL
    0x7fff4112e000 -     0x7fff4114afff  com.apple.CFOpenDirectory (10.15 - 220.11.1) <90901E88-47DC-3DDA-AF53-FD0A0B22078A> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory
    0x7fff4114b000 -     0x7fff41156fff  com.apple.OpenDirectory (10.15 - 220.11.1) <5AAE71B0-892A-3813-BDCF-C364B61D500B> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory
    0x7fff41ab1000 -     0x7fff41ab3fff  libCVMSPluginSupport.dylib (17.10.22) <026644DF-3221-3AB0-8DA9-DA9B56A8B38D> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib
    0x7fff41ab4000 -     0x7fff41ab9fff  libCoreFSCache.dylib (176.7) <A10565BE-6728-3BCA-9A9A-095CC09A5F25> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreFSCache.dylib
    0x7fff41aba000 -     0x7fff41abefff  libCoreVMClient.dylib (176.7) <DF6A2BF6-7775-3ED8-B425-772499BE2BB7> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib
    0x7fff41abf000 -     0x7fff41ac7ff7  libGFXShared.dylib (17.10.22) <2DBB6DC3-4027-3A0E-AEA7-809399CFFEFA> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib
    0x7fff41ac8000 -     0x7fff41ad2fff  libGL.dylib (17.10.22) <95746D0C-9347-37C0-88E2-6BA4A3584816> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
    0x7fff41ad3000 -     0x7fff41b08fff  libGLImage.dylib (17.10.22) <B8EE902C-6692-3E32-949B-C193AC944D31> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib
    0x7fff41b09000 -     0x7fff41c9bff7  libGLProgrammability.dylib (17.10.22) <02CCAAE9-9B38-352C-A854-026D02ABB7E9> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLProgrammability.dylib
    0x7fff41c9c000 -     0x7fff41cd8fff  libGLU.dylib (17.10.22) <43DADBAD-9F65-33CE-94DA-654F24817313> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
    0x7fff42708000 -     0x7fff42717ff7  com.apple.opengl (17.10.22 - 17.10.22) <C3E682E0-413B-3134-9107-C45B897E8CDA> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
    0x7fff42718000 -     0x7fff42891ff7  GLEngine (17.10.22) <B67C43C3-77C1-3233-98F5-A5062B14FE70> /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLEngine.bundle/GLEngine
    0x7fff42892000 -     0x7fff428bafff  GLRendererFloat (17.10.22) <DA488EF2-6318-3376-8616-26CE79640666> /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLRendererFloat.bundle/GLRendererFloat
    0x7fff436c7000 -     0x7fff43944ff7  com.apple.QuartzCore (1.11 - 815.6.4.2) <0459F92C-5C1C-3B32-BCE8-9526AF5BC8D1> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
    0x7fff444cf000 -     0x7fff44812ff1  com.apple.security (7.0 - 59306.11.12) <54D99D96-7E50-3EEA-BCB3-7E73973B131C> /System/Library/Frameworks/Security.framework/Versions/A/Security
    0x7fff44813000 -     0x7fff4489bff7  com.apple.securityfoundation (6.0 - 55236) <A1B5CC71-E988-3529-AA03-539C02340DAD> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation
    0x7fff448ca000 -     0x7fff448ceff8  com.apple.xpc.ServiceManagement (1.0 - 1) <EF42F840-AF78-38A4-B6E1-FDF445CA3477> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement
    0x7fff456bc000 -     0x7fff45726ff7  com.apple.SystemConfiguration (1.19 - 1.19) <C0C089C3-FC64-3107-B23E-4073E800C5D2> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration
    0x7fff459a2000 -     0x7fff45d49ff1  com.apple.VideoToolbox (1.0 - 2501.27.4.3) <522DF280-7ADE-3467-B4EE-06B7ED84C1F2> /System/Library/Frameworks/VideoToolbox.framework/Versions/A/VideoToolbox
    0x7fff494bf000 -     0x7fff49583ff7  com.apple.APFS (1412.11.4 - 1412.11.4) <B66C6042-E929-3A33-83A0-9199E132FE1E> /System/Library/PrivateFrameworks/APFS.framework/Versions/A/APFS
    0x7fff49d3c000 -     0x7fff49d44ff6  com.apple.AccessibilityBundles (1.0 - 128) <242ACD03-D41C-38AA-AEB5-D0EC462C548E> /System/Library/PrivateFrameworks/AccessibilityBundles.framework/Versions/A/AccessibilityBundles
    0x7fff4a5b4000 -     0x7fff4a5b5ff1  com.apple.AggregateDictionary (1.0 - 1) <92777CAE-3C90-39A4-A8AE-0273A262F875> /System/Library/PrivateFrameworks/AggregateDictionary.framework/Versions/A/AggregateDictionary
    0x7fff4a93f000 -     0x7fff4a95bff2  com.apple.AppContainer (4.0 - 448.0.3) <EFE68289-FFE6-3453-89AF-E637CD47A2D0> /System/Library/PrivateFrameworks/AppContainer.framework/Versions/A/AppContainer
    0x7fff4a9af000 -     0x7fff4a9bdff7  com.apple.AppSandbox (4.0 - 448.0.3) <1E6E9594-4988-32EC-86C2-CDDA7DBB7E66> /System/Library/PrivateFrameworks/AppSandbox.framework/Versions/A/AppSandbox
    0x7fff4ae3f000 -     0x7fff4ae63ff3  com.apple.framework.Apple80211 (13.0 - 1453) <C355D394-9489-3C14-856C-A4818B003FE1> /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Apple80211
    0x7fff4af97000 -     0x7fff4afa6fdf  com.apple.AppleFSCompression (119 - 1.0) <725908C4-7585-3AB6-8A1A-691B8A9074B8> /System/Library/PrivateFrameworks/AppleFSCompression.framework/Versions/A/AppleFSCompression
    0x7fff4b0a5000 -     0x7fff4b0b0ff7  com.apple.AppleIDAuthSupport (1.0 - 1) <6BD125A5-9820-3176-AB79-8B612CCD6956> /System/Library/PrivateFrameworks/AppleIDAuthSupport.framework/Versions/A/AppleIDAuthSupport
    0x7fff4b0f2000 -     0x7fff4b13afff  com.apple.AppleJPEG (1.0 - 1) <8051B4A3-7658-3003-82D1-41CA5C83CBEC> /System/Library/PrivateFrameworks/AppleJPEG.framework/Versions/A/AppleJPEG
    0x7fff4b50e000 -     0x7fff4b512ff7  com.apple.AppleSRP (5.0 - 1) <B251E119-3F06-3CDB-9559-8CC8BBAF1529> /System/Library/PrivateFrameworks/AppleSRP.framework/Versions/A/AppleSRP
    0x7fff4b513000 -     0x7fff4b535ffb  com.apple.applesauce (1.0 - 16.22) <88BFDA72-8D13-3481-B4FA-62215F6E2E43> /System/Library/PrivateFrameworks/AppleSauce.framework/Versions/A/AppleSauce
    0x7fff4b5f5000 -     0x7fff4b5f8fff  com.apple.AppleSystemInfo (3.1.5 - 3.1.5) <AF8A3953-4D1A-38C2-B38D-1E21F326B0C7> /System/Library/PrivateFrameworks/AppleSystemInfo.framework/Versions/A/AppleSystemInfo
    0x7fff4b5f9000 -     0x7fff4b649ff7  com.apple.AppleVAFramework (6.1.2 - 6.1.2) <282CA618-1F44-3160-9078-B48D70AEDE36> /System/Library/PrivateFrameworks/AppleVA.framework/Versions/A/AppleVA
    0x7fff4b692000 -     0x7fff4b6a1ffd  com.apple.AssertionServices (1.0 - 223.11.1) <8A45663E-E9C8-3611-BD4C-710700920F14> /System/Library/PrivateFrameworks/AssertionServices.framework/Versions/A/AssertionServices
    0x7fff4bbd3000 -     0x7fff4bfd1ff4  com.apple.audio.AudioResourceArbitration (1.0 - 1) <2639564C-1435-3DA2-A0CB-F288617219BC> /System/Library/PrivateFrameworks/AudioResourceArbitration.framework/Versions/A/AudioResourceArbitration
    0x7fff4c110000 -     0x7fff4c161ffd  com.apple.audio.AudioSession (1.0 - 17) <627167E8-D05D-3851-A5E5-FBA38C8E72D3> /System/Library/PrivateFrameworks/AudioSession.framework/Versions/A/AudioSession
    0x7fff4c162000 -     0x7fff4c18fff7  libSessionUtility.dylib (17) <28EC4408-4F7C-3C73-A9E2-AD976BE1C1D4> /System/Library/PrivateFrameworks/AudioSession.framework/libSessionUtility.dylib
    0x7fff4c228000 -     0x7fff4c45dff7  com.apple.audio.AudioToolboxCore (1.0 - 1104.14) <4591B856-C8D0-3FFD-B783-70707D18E91A> /System/Library/PrivateFrameworks/AudioToolboxCore.framework/Versions/A/AudioToolboxCore
    0x7fff4c45e000 -     0x7fff4c576ff8  com.apple.AuthKit (1.0 - 1) <2650CED9-1F9F-3C76-A6B9-B0589F986830> /System/Library/PrivateFrameworks/AuthKit.framework/Versions/A/AuthKit
    0x7fff4c72c000 -     0x7fff4c735ff3  com.apple.coreservices.BackgroundTaskManagement (1.0 - 104) <42FAB6B3-D02C-3264-9066-2B81DC62A529> /System/Library/PrivateFrameworks/BackgroundTaskManagement.framework/Versions/A/BackgroundTaskManagement
    0x7fff4c736000 -     0x7fff4c7d7ff8  com.apple.backup.framework (1.11 - 1296.1) <B6B83178-3F01-3DCB-BC72-70F8F6BCFAD8> /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup
    0x7fff4c7d8000 -     0x7fff4c857fff  com.apple.BaseBoard (460 - 460) <E2B2C09D-7CA3-3BCF-AE84-E636CBC139CB> /System/Library/PrivateFrameworks/BaseBoard.framework/Versions/A/BaseBoard
    0x7fff4c957000 -     0x7fff4c993ff7  com.apple.bom (14.0 - 219) <1AFE57DF-F512-39A7-9C53-1AF0490D38BB> /System/Library/PrivateFrameworks/Bom.framework/Versions/A/Bom
    0x7fff4d4fe000 -     0x7fff4d54dfff  com.apple.ChunkingLibrary (302 - 302) <157DF88D-CCA1-3431-AB8F-E8B7A62D652C> /System/Library/PrivateFrameworks/ChunkingLibrary.framework/Versions/A/ChunkingLibrary
    0x7fff4e3d2000 -     0x7fff4e3dbff7  com.apple.CommonAuth (4.0 - 2.0) <BDE39131-6389-3243-9C4A-DBA165B8A2F9> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth
    0x7fff4e3ef000 -     0x7fff4e406ff1  com.apple.commonutilities (8.0 - 900) <A64C20B3-6860-3CCA-BB89-E8B9B589282A> /System/Library/PrivateFrameworks/CommonUtilities.framework/Versions/A/CommonUtilities
    0x7fff4eae5000 -     0x7fff4eebafc8  com.apple.CoreAUC (280.0.0 - 280.0.0) <4D5184AB-F60A-3C95-82C1-A283FB15C072> /System/Library/PrivateFrameworks/CoreAUC.framework/Versions/A/CoreAUC
    0x7fff4eebb000 -     0x7fff4eee9ffb  com.apple.CoreAVCHD (6.1.0 - 6100.4.1) <B7C10F1C-B3DE-3F2C-B2B8-1CD37DA7298F> /System/Library/PrivateFrameworks/CoreAVCHD.framework/Versions/A/CoreAVCHD
    0x7fff4ef0b000 -     0x7fff4ef2aff4  com.apple.analyticsd (1.0 - 1) <A712828F-84FB-302B-BAA8-D2776AB623EB> /System/Library/PrivateFrameworks/CoreAnalytics.framework/Versions/A/CoreAnalytics
    0x7fff4f1f2000 -     0x7fff4f1fdff7  com.apple.frameworks.CoreDaemon (1.3 - 1.3) <76AC1239-46B1-387E-B053-ED56BDF55DE7> /System/Library/PrivateFrameworks/CoreDaemon.framework/Versions/B/CoreDaemon
    0x7fff4f473000 -     0x7fff4f483ff3  com.apple.CoreEmoji (1.0 - 100) <9AB89183-635C-3859-9DC6-7BCE3A94D15E> /System/Library/PrivateFrameworks/CoreEmoji.framework/Versions/A/CoreEmoji
    0x7fff4facf000 -     0x7fff4fb39ff8  com.apple.CoreNLP (1.0 - 211) <8F08AEF6-A380-3811-BAF0-D80E7C84B5AD> /System/Library/PrivateFrameworks/CoreNLP.framework/Versions/A/CoreNLP
    0x7fff4ff9f000 -     0x7fff4ffa7ff8  com.apple.CorePhoneNumbers (1.0 - 1) <0C242322-DB33-3764-9B44-74FA00AA3702> /System/Library/PrivateFrameworks/CorePhoneNumbers.framework/Versions/A/CorePhoneNumbers
    0x7fff506f1000 -     0x7fff50714fff  com.apple.CoreSVG (1.0 - 129) <1716AD1F-A94F-309D-9598-C7B65F5965A0> /System/Library/PrivateFrameworks/CoreSVG.framework/Versions/A/CoreSVG
    0x7fff50715000 -     0x7fff50748ff7  com.apple.CoreServicesInternal (446.1 - 446.1) <D5620418-A66F-300B-BE02-6254206C6B3E> /System/Library/PrivateFrameworks/CoreServicesInternal.framework/Versions/A/CoreServicesInternal
    0x7fff50749000 -     0x7fff50777ff7  com.apple.CSStore (1068.2 - 1068.2) <C8AEEE68-B040-39B9-9B52-6496497B19A8> /System/Library/PrivateFrameworks/CoreServicesStore.framework/Versions/A/CoreServicesStore
    0x7fff50c72000 -     0x7fff50cf9fff  com.apple.CoreSymbolication (11.0 - 64509.98.1) <2E90AD17-CEAC-3AE8-A960-DA83D3F3A071> /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSymbolication
    0x7fff50d91000 -     0x7fff50ebdff4  com.apple.coreui (2.1 - 605) <74EF8323-1769-3BF8-A0F3-30A89E5B8454> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI
    0x7fff50ebe000 -     0x7fff5105cffd  com.apple.CoreUtils (6.0 - 600.30) <60C366EC-D7C4-300A-B794-12D84952D6B6> /System/Library/PrivateFrameworks/CoreUtils.framework/Versions/A/CoreUtils
    0x7fff51190000 -     0x7fff511a3ff1  com.apple.CrashReporterSupport (10.13 - 15010) <94F94549-D6F8-35A5-8FEE-026E079C3B2C> /System/Library/PrivateFrameworks/C"	dfuentes
19755	VirtualBox crashed with EXC_CRASH (SIGABRT) after resuming on macOS 10.14.6 - malloc: Incorrect checksum for freed object	VirtualBox 6.1.10	2020-07-23T14:24:24Z	2020-07-23T20:16:23Z	2020-07-23T20:16:23Z	"Running two Windows VMs simultaneously, with internal networking, VirtualBox crashed on sleep and resume (reopening lid) of macOS 10.14.6

abort() called
VirtualBoxVM(14390,0x70000d07f000) malloc: Incorrect checksum for freed object 0x7fe3f2011800: probably modified after being freed.
Corrupt value: 0x0

#19050 ? 

{{{
Process:               VirtualBoxVM [14390]
Path:                  /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM
Identifier:            org.virtualbox.app.VirtualBoxVM
Version:               6.1.10 (6.1.10)
Code Type:             X86-64 (Native)
Parent Process:        VBoxSVC [13937]
Responsible:           VirtualBoxVM [14390]
User ID:               501

Date/Time:             2020-07-23 10:08:50.261 -0400
OS Version:            Mac OS X 10.14.6 (18G6020)
Report Version:        12
Bridge OS Version:     4.6 (17P6065)
Anonymous UUID:        

Sleep/Wake UUID:       

Time Awake Since Boot: 31000 seconds
Time Since Wake:       10 seconds

System Integrity Protection: enabled

Crashed Thread:        8  EMT-0

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Application Specific Information:
abort() called
VirtualBoxVM(14390,0x70000d07f000) malloc: Incorrect checksum for freed object 0x7fe3f2011800: probably modified after being freed.
Corrupt value: 0x0
 

Thread 0:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        	0x00007fff5a60e21a mach_msg_trap + 10
1   libsystem_kernel.dylib        	0x00007fff5a60e768 mach_msg + 60
2   com.apple.CoreFoundation      	0x00007fff2e55b882 __CFRunLoopServiceMachPort + 328
3   com.apple.CoreFoundation      	0x00007fff2e55adf0 __CFRunLoopRun + 1612
4   com.apple.CoreFoundation      	0x00007fff2e55a552 CFRunLoopRunSpecific + 455
5   com.apple.HIToolbox           	0x00007fff2d7b91ab RunCurrentEventLoopInMode + 292
6   com.apple.HIToolbox           	0x00007fff2d7b8ee5 ReceiveNextEventCommon + 603
7   com.apple.HIToolbox           	0x00007fff2d7b8c76 _BlockUntilNextEventMatchingListInModeWithFilter + 64
8   com.apple.AppKit              	0x00007fff2bb5077d _DPSNextEvent + 1135
9   com.apple.AppKit              	0x00007fff2bb4f46b -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1361
10  com.apple.AppKit              	0x00007fff2bb49588 -[NSApplication run] + 699
11  libqcocoa.dylib               	0x0000000115808eed QCocoaEventDispatcher::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 2205
12  org.qt-project.QtCoreVBox     	0x000000010ea34791 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 401
13  org.qt-project.QtCoreVBox     	0x000000010ea38b4a QCoreApplication::exec() + 346
14  VirtualBoxVM.dylib            	0x000000010e6ccd4e TrustedMain + 1502
15  org.virtualbox.app.VirtualBoxVM	0x000000010de05951 0x10de02000 + 14673
16  libdyld.dylib                 	0x00007fff5a4d93d5 start + 1

Thread 1:: nspr-1
0   libsystem_kernel.dylib        	0x00007fff5a615616 __select + 10
1   VBoxXPCOM.dylib               	0x00000001121b18a0 0x112127000 + 567456
2   VBoxXPCOM.dylib               	0x00000001121b36e5 PR_Poll + 1061
3   VBoxXPCOMIPCC.dylib           	0x000000011827be75 0x118269000 + 77429
4   VBoxXPCOM.dylib               	0x00000001121b8a96 0x112127000 + 596630
5   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
6   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
7   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
8   libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
9   libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 2:: nspr-2
0   libsystem_kernel.dylib        	0x00007fff5a611866 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5a6d056e _pthread_cond_wait + 722
2   VBoxXPCOM.dylib               	0x00000001121b6dfe PR_WaitCondVar + 254
3   VBoxXPCOM.dylib               	0x00000001121b72ad PR_Wait + 61
4   VBoxXPCOMIPCC.dylib           	0x00000001182747b8 0x118269000 + 47032
5   VBoxXPCOM.dylib               	0x000000011218b1f9 0x112127000 + 410105
6   VBoxXPCOM.dylib               	0x00000001121b8a96 0x112127000 + 596630
7   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
8   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
9   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
10  libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
11  libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 3:: VBoxSVCWatcher
0   libsystem_kernel.dylib        	0x00007fff5a611866 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5a6d056e _pthread_cond_wait + 722
2   VBoxRT.dylib                  	0x000000010dfeaa9c RTSemEventWait + 364
3   VBoxC.dylib                   	0x0000000118388711 0x118291000 + 1013521
4   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
5   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
6   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
7   libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
8   libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 4:: UIMainEventListeningThread
0   libsystem_kernel.dylib        	0x00007fff5a611866 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5a6d056e _pthread_cond_wait + 722
2   VBoxXPCOM.dylib               	0x00000001121b6de7 PR_WaitCondVar + 231
3   VBoxXPCOM.dylib               	0x00000001121b72ad PR_Wait + 61
4   VBoxXPCOMIPCC.dylib           	0x000000011826e71b 0x118269000 + 22299
5   VBoxXPCOMIPCC.dylib           	0x000000011826e3ed 0x118269000 + 21485
6   VBoxXPCOMIPCC.dylib           	0x0000000118273039 0x118269000 + 41017
7   VBoxXPCOM.dylib               	0x000000011219a2ed 0x112127000 + 471789
8   VBoxXPCOM.dylib               	0x00000001121994eb 0x112127000 + 468203
9   UICommon.dylib                	0x000000010fdca172 CEventSource::GetEvent(CEventListener const&, int) + 162
10  UICommon.dylib                	0x000000010fbde2f7 0x10faf8000 + 942839
11  org.qt-project.QtCoreVBox     	0x000000010e87a96b 0x10e851000 + 170347
12  libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
13  libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
14  libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 5:: UIMainEventListeningThread
0   libsystem_kernel.dylib        	0x00007fff5a611866 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5a6d056e _pthread_cond_wait + 722
2   VBoxRT.dylib                  	0x000000010dfeaa9c RTSemEventWait + 364
3   VBoxC.dylib                   	0x00000001182d52f0 0x118291000 + 279280
4   VBoxC.dylib                   	0x00000001182d651d 0x118291000 + 283933
5   VBoxC.dylib                   	0x000000011845e90a 0x118291000 + 1890570
6   UICommon.dylib                	0x000000010fdca172 CEventSource::GetEvent(CEventListener const&, int) + 162
7   UICommon.dylib                	0x000000010fbde2f7 0x10faf8000 + 942839
8   org.qt-project.QtCoreVBox     	0x000000010e87a96b 0x10e851000 + 170347
9   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
10  libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
11  libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 6:: UIMainEventListeningThread
0   libsystem_kernel.dylib        	0x00007fff5a611866 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5a6d056e _pthread_cond_wait + 722
2   VBoxRT.dylib                  	0x000000010dfeaa9c RTSemEventWait + 364
3   VBoxC.dylib                   	0x00000001182d52f0 0x118291000 + 279280
4   VBoxC.dylib                   	0x00000001182d651d 0x118291000 + 283933
5   VBoxC.dylib                   	0x000000011845e90a 0x118291000 + 1890570
6   UICommon.dylib                	0x000000010fdca172 CEventSource::GetEvent(CEventListener const&, int) + 162
7   UICommon.dylib                	0x000000010fbde2f7 0x10faf8000 + 942839
8   org.qt-project.QtCoreVBox     	0x000000010e87a96b 0x10e851000 + 170347
9   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
10  libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
11  libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 7:: MainHGCMthread
0   libsystem_kernel.dylib        	0x00007fff5a611866 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5a6d056e _pthread_cond_wait + 722
2   VBoxRT.dylib                  	0x000000010dfeab4b RTSemEventWait + 539
3   VBoxC.dylib                   	0x0000000118424ef5 0x118291000 + 1654517
4   VBoxC.dylib                   	0x00000001184255e6 0x118291000 + 1656294
5   VBoxC.dylib                   	0x00000001184293eb 0x118291000 + 1672171
6   VBoxC.dylib                   	0x0000000118424ccf 0x118291000 + 1653967
7   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
8   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
9   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
10  libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
11  libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 8 Crashed:: EMT-0
0   libsystem_kernel.dylib        	0x00007fff5a6142c2 __pthread_kill + 10
1   libsystem_pthread.dylib       	0x00007fff5a6cfbf1 pthread_kill + 284
2   libsystem_c.dylib             	0x00007fff5a57e6a6 abort + 127
3   libsystem_malloc.dylib        	0x00007fff5a68d077 malloc_vreport + 545
4   libsystem_malloc.dylib        	0x00007fff5a6a5e0d malloc_zone_error + 183
5   libsystem_malloc.dylib        	0x00007fff5a6895c8 small_free_list_remove_ptr_no_clear + 1177
6   libsystem_malloc.dylib        	0x00007fff5a6881db small_malloc_from_free_list + 152
7   libsystem_malloc.dylib        	0x00007fff5a687afc small_malloc_should_clear + 284
8   libsystem_malloc.dylib        	0x00007fff5a685245 szone_malloc_should_clear + 120
9   libsystem_malloc.dylib        	0x00007fff5a686444 malloc_zone_calloc + 99
10  libsystem_malloc.dylib        	0x00007fff5a6863c4 calloc + 30
11  VBoxDD.dylib                  	0x000000011fe387b6 0x11fde1000 + 358326
12  VBoxDD.dylib                  	0x000000011fe37d3e 0x11fde1000 + 355646
13  VBoxDD.dylib                  	0x000000011fe348d9 0x11fde1000 + 342233
14  VBoxVMM.dylib                 	0x0000000111f03798 IOMIOPortWrite + 312
15  VBoxVMM.dylib                 	0x0000000111df000d 0x111da1000 + 323597
16  VBoxVMM.dylib                 	0x0000000111de69fc 0x111da1000 + 285180
17  VBoxVMM.dylib                 	0x0000000111dea70a 0x111da1000 + 300810
18  VBoxVMM.dylib                 	0x0000000111de808c 0x111da1000 + 290956
19  VBoxVMM.dylib                 	0x0000000111e4d2ee 0x111da1000 + 705262
20  VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
21  VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
22  libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
23  libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
24  libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 9:: EMT-1
0   libsystem_kernel.dylib        	0x00007fff5a60eb56 __ioctl + 10
1   libsystem_kernel.dylib        	0x00007fff5a60eb40 ioctl + 151
2   VBoxRT.dylib                  	0x000000010dff88ed 0x10de4b000 + 1759469
3   VBoxRT.dylib                  	0x000000010dff11c6 SUPR3CallVMMR0Ex + 438
4   VBoxVMM.dylib                 	0x0000000111e4eb32 0x111da1000 + 711474
5   VBoxVMM.dylib                 	0x0000000111e4db01 0x111da1000 + 707329
6   VBoxVMM.dylib                 	0x0000000111de847b 0x111da1000 + 291963
7   VBoxVMM.dylib                 	0x0000000111e4d2ee 0x111da1000 + 705262
8   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
9   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
10  libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
11  libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
12  libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 10:: ShClipboard
0   libsystem_kernel.dylib        	0x00007fff5a611866 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5a6d056e _pthread_cond_wait + 722
2   VBoxRT.dylib                  	0x000000010dfeab4b RTSemEventWait + 539
3   VBoxC.dylib                   	0x0000000118424ef5 0x118291000 + 1654517
4   VBoxC.dylib                   	0x00000001184255e6 0x118291000 + 1656294
5   VBoxC.dylib                   	0x000000011842613d 0x118291000 + 1659197
6   VBoxC.dylib                   	0x0000000118424ccf 0x118291000 + 1653967
7   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
8   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
9   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
10  libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
11  libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 11:: SHCLIP
0   libsystem_kernel.dylib        	0x00007fff5a611866 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5a6d056e _pthread_cond_wait + 722
2   VBoxRT.dylib                  	0x000000010dfeb526 0x10de4b000 + 1705254
3   VBoxRT.dylib                  	0x000000010df351d9 RTThreadUserWait + 73
4   VBoxSharedClipboard.dylib     	0x0000000117921bd7 0x11791a000 + 31703
5   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
6   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
7   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
8   libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
9   libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 12:: DragAndDropSvc
0   libsystem_kernel.dylib        	0x00007fff5a611866 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5a6d056e _pthread_cond_wait + 722
2   VBoxRT.dylib                  	0x000000010dfeab4b RTSemEventWait + 539
3   VBoxC.dylib                   	0x0000000118424ef5 0x118291000 + 1654517
4   VBoxC.dylib                   	0x00000001184255e6 0x118291000 + 1656294
5   VBoxC.dylib                   	0x000000011842613d 0x118291000 + 1659197
6   VBoxC.dylib                   	0x0000000118424ccf 0x118291000 + 1653967
7   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
8   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
9   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
10  libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
11  libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 13:: Timer
0   libsystem_kernel.dylib        	0x00007fff5a611866 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5a6d056e _pthread_cond_wait + 722
2   VBoxRT.dylib                  	0x000000010dfeaa9c RTSemEventWait + 364
3   VBoxRT.dylib                  	0x000000010dfdbd4d 0x10de4b000 + 1641805
4   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
5   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
6   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
7   libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
8   libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 14:: PDMNsTx
0   libsystem_kernel.dylib        	0x00007fff5a611f2e __semwait_signal + 10
1   libsystem_c.dylib             	0x00007fff5a59d914 nanosleep + 199
2   VBoxRT.dylib                  	0x000000010dfeea33 RTThreadSleep + 67
3   VBoxVMM.dylib                 	0x0000000111f3c35a 0x111da1000 + 1684314
4   VBoxVMM.dylib                 	0x0000000111e0e49f 0x111da1000 + 447647
5   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
6   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
7   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
8   libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
9   libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 15:: com.apple.NSEventThread
0   libsystem_kernel.dylib        	0x00007fff5a60e21a mach_msg_trap + 10
1   libsystem_kernel.dylib        	0x00007fff5a60e768 mach_msg + 60
2   com.apple.CoreFoundation      	0x00007fff2e55b882 __CFRunLoopServiceMachPort + 328
3   com.apple.CoreFoundation      	0x00007fff2e55adf0 __CFRunLoopRun + 1612
4   com.apple.CoreFoundation      	0x00007fff2e55a552 CFRunLoopRunSpecific + 455
5   com.apple.AppKit              	0x00007fff2bb584a2 _NSEventThread + 175
6   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
7   libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
8   libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 16:: ShFolders
0   libsystem_kernel.dylib        	0x00007fff5a611866 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5a6d056e _pthread_cond_wait + 722
2   VBoxRT.dylib                  	0x000000010dfeab4b RTSemEventWait + 539
3   VBoxC.dylib                   	0x0000000118424ef5 0x118291000 + 1654517
4   VBoxC.dylib                   	0x00000001184255e6 0x118291000 + 1656294
5   VBoxC.dylib                   	0x000000011842613d 0x118291000 + 1659197
6   VBoxC.dylib                   	0x0000000118424ccf 0x118291000 + 1653967
7   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
8   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
9   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
10  libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
11  libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 17:: GuestControlSvc
0   libsystem_kernel.dylib        	0x00007fff5a611866 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5a6d056e _pthread_cond_wait + 722
2   VBoxRT.dylib                  	0x000000010dfeab4b RTSemEventWait + 539
3   VBoxC.dylib                   	0x0000000118424ef5 0x118291000 + 1654517
4   VBoxC.dylib                   	0x00000001184255e6 0x118291000 + 1656294
5   VBoxC.dylib                   	0x000000011842613d 0x118291000 + 1659197
6   VBoxC.dylib                   	0x0000000118424ccf 0x118291000 + 1653967
7   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
8   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
9   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
10  libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
11  libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 18:: GuestPropSvc
0   libsystem_kernel.dylib        	0x00007fff5a611866 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5a6d056e _pthread_cond_wait + 722
2   VBoxRT.dylib                  	0x000000010dfeab4b RTSemEventWait + 539
3   VBoxC.dylib                   	0x0000000118424ef5 0x118291000 + 1654517
4   VBoxC.dylib                   	0x00000001184255e6 0x118291000 + 1656294
5   VBoxC.dylib                   	0x000000011842613d 0x118291000 + 1659197
6   VBoxC.dylib                   	0x0000000118424ccf 0x118291000 + 1653967
7   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
8   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
9   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
10  libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
11  libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 19:: GstPropNtfy
0   libsystem_kernel.dylib        	0x00007fff5a611866 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5a6d056e _pthread_cond_wait + 722
2   VBoxRT.dylib                  	0x000000010dfeab4b RTSemEventWait + 539
3   VBoxRT.dylib                  	0x000000010df325e2 RTReqQueueProcess + 146
4   VBoxGuestPropSvc.dylib        	0x0000000122093081 0x12208d000 + 24705
5   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
6   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
7   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
8   libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
9   libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 20:: VMSVGA FIFO
0   libsystem_kernel.dylib        	0x00007fff5a60eb56 __ioctl + 10
1   libsystem_kernel.dylib        	0x00007fff5a60eb40 ioctl + 151
2   VBoxRT.dylib                  	0x000000010dff88ed 0x10de4b000 + 1759469
3   VBoxRT.dylib                  	0x000000010dff56f7 SUPSemEventWaitNoResume + 135
4   VBoxDD.dylib                  	0x000000011fe759bf 0x11fde1000 + 608703
5   VBoxVMM.dylib                 	0x0000000111e0e493 0x111da1000 + 447635
6   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
7   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
8   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
9   libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
10  libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 21:: ATA-0
0   libsystem_kernel.dylib        	0x00007fff5a60eb56 __ioctl + 10
1   libsystem_kernel.dylib        	0x00007fff5a60eb40 ioctl + 151
2   VBoxRT.dylib                  	0x000000010dff88ed 0x10de4b000 + 1759469
3   VBoxRT.dylib                  	0x000000010dff56f7 SUPSemEventWaitNoResume + 135
4   VBoxDD.dylib                  	0x000000011fe0e3f9 0x11fde1000 + 185337
5   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
6   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
7   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
8   libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
9   libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 22:: ATA-1
0   libsystem_kernel.dylib        	0x00007fff5a60eb56 __ioctl + 10
1   libsystem_kernel.dylib        	0x00007fff5a60eb40 ioctl + 151
2   VBoxRT.dylib                  	0x000000010dff88ed 0x10de4b000 + 1759469
3   VBoxRT.dylib                  	0x000000010dff56f7 SUPSemEventWaitNoResume + 135
4   VBoxDD.dylib                  	0x000000011fe0e3f9 0x11fde1000 + 185337
5   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
6   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
7   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
8   libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
9   libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 23:: TaskSet0
0   libsystem_kernel.dylib        	0x00007fff5a60eb56 __ioctl + 10
1   libsystem_kernel.dylib        	0x00007fff5a60eb40 ioctl + 151
2   VBoxRT.dylib                  	0x000000010dff88ed 0x10de4b000 + 1759469
3   VBoxRT.dylib                  	0x000000010dff56f7 SUPSemEventWaitNoResume + 135
4   VBoxVMM.dylib                 	0x0000000111e0d067 0x111da1000 + 442471
5   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
6   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
7   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
8   libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
9   libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 24:: NATRX
0   libsystem_kernel.dylib        	0x00007fff5a611866 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5a6d056e _pthread_cond_wait + 722
2   VBoxRT.dylib                  	0x000000010dfeab4b RTSemEventWait + 539
3   VBoxDD.dylib                  	0x000000011ff1a63a 0x11fde1000 + 1283642
4   VBoxVMM.dylib                 	0x0000000111e0e493 0x111da1000 + 447635
5   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
6   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
7   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
8   libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
9   libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 25:: NATURGRX
0   libsystem_kernel.dylib        	0x00007fff5a611866 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5a6d056e _pthread_cond_wait + 722
2   VBoxRT.dylib                  	0x000000010dfeab4b RTSemEventWait + 539
3   VBoxDD.dylib                  	0x000000011ff1a69a 0x11fde1000 + 1283738
4   VBoxVMM.dylib                 	0x0000000111e0e493 0x111da1000 + 447635
5   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
6   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
7   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
8   libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
9   libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 26:: HOSTRES
0   libsystem_kernel.dylib        	0x00007fff5a611866 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5a6d056e _pthread_cond_wait + 722
2   VBoxRT.dylib                  	0x000000010dfeab4b RTSemEventWait + 539
3   VBoxRT.dylib                  	0x000000010df325e2 RTReqQueueProcess + 146
4   VBoxDD.dylib                  	0x000000011ff1a701 0x11fde1000 + 1283841
5   VBoxVMM.dylib                 	0x0000000111e0e493 0x111da1000 + 447635
6   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
7   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
8   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
9   libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
10  libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 27:: NAT
0   libsystem_kernel.dylib        	0x00007fff5a61636a poll + 10
1   VBoxDD.dylib                  	0x000000011ff1a83b 0x11fde1000 + 1284155
2   VBoxVMM.dylib                 	0x0000000111e0e493 0x111da1000 + 447635
3   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
4   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
5   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
6   libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
7   libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 28:: INTNET-RECV
0   libsystem_kernel.dylib        	0x00007fff5a60eb56 __ioctl + 10
1   libsystem_kernel.dylib        	0x00007fff5a60eb40 ioctl + 151
2   VBoxRT.dylib                  	0x000000010dff88ed 0x10de4b000 + 1759469
3   VBoxRT.dylib                  	0x000000010dff1148 SUPR3CallVMMR0Ex + 312
4   VBoxDD.dylib                  	0x000000011fe52638 0x11fde1000 + 464440
5   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
6   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
7   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
8   libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
9   libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 29:: INTNET-XMIT
0   libsystem_kernel.dylib        	0x00007fff5a60eb56 __ioctl + 10
1   libsystem_kernel.dylib        	0x00007fff5a60eb40 ioctl + 151
2   VBoxRT.dylib                  	0x000000010dff88ed 0x10de4b000 + 1759469
3   VBoxRT.dylib                  	0x000000010dff56f7 SUPSemEventWaitNoResume + 135
4   VBoxDD.dylib                  	0x000000011fe53400 0x11fde1000 + 467968
5   VBoxVMM.dylib                 	0x0000000111e0e493 0x111da1000 + 447635
6   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
7   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
8   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
9   libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
10  libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 30:: nspr-3
0   libsystem_kernel.dylib        	0x00007fff5a611866 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5a6d056e _pthread_cond_wait + 722
2   VBoxXPCOM.dylib               	0x00000001121b6dfe PR_WaitCondVar + 254
3   VBoxXPCOM.dylib               	0x00000001121b72ad PR_Wait + 61
4   VBoxXPCOMIPCC.dylib           	0x00000001182747b8 0x118269000 + 47032
5   VBoxXPCOM.dylib               	0x000000011218b1f9 0x112127000 + 410105
6   VBoxXPCOM.dylib               	0x00000001121b8a96 0x112127000 + 596630
7   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
8   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
9   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
10  libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
11  libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 31:: VUsbPeriodFrm
0   libsystem_kernel.dylib        	0x00007fff5a611866 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5a6d056e _pthread_cond_wait + 722
2   VBoxRT.dylib                  	0x000000010dfeb661 0x10de4b000 + 1705569
3   VBoxRT.dylib                  	0x000000010dfeb3e3 0x10de4b000 + 1704931
4   VBoxDD.dylib                  	0x000000011fea1f22 0x11fde1000 + 790306
5   VBoxVMM.dylib                 	0x0000000111e0e493 0x111da1000 + 447635
6   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
7   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
8   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
9   libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
10  libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 32:: CAQUEUE
0   libsystem_kernel.dylib        	0x00007fff5a60e21a mach_msg_trap + 10
1   libsystem_kernel.dylib        	0x00007fff5a60e768 mach_msg + 60
2   com.apple.CoreFoundation      	0x00007fff2e55b882 __CFRunLoopServiceMachPort + 328
3   com.apple.CoreFoundation      	0x00007fff2e55adf0 __CFRunLoopRun + 1612
4   com.apple.CoreFoundation      	0x00007fff2e55a552 CFRunLoopRunSpecific + 455
5   VBoxDD.dylib                  	0x000000011ff17fb5 0x11fde1000 + 1273781
6   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
7   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
8   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
9   libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
10  libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 33:: AQConverterThread
0   libsystem_kernel.dylib        	0x00007fff5a611866 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5a6d056e _pthread_cond_wait + 722
2   com.apple.audio.toolbox.AudioToolbox	0x00007fff2ce821ca CAGuard::Wait() + 72
3   com.apple.audio.toolbox.AudioToolbox	0x00007fff2ce7e575 AQConverterManager::AQConverterThread::Run() + 375
4   com.apple.audio.toolbox.AudioToolbox	0x00007fff2ce7e3f3 AQConverterManager::AQConverterThread::ConverterThreadEntry(void*) + 9
5   com.apple.audio.toolbox.AudioToolbox	0x00007fff2ce5b741 CAPThread::Entry(CAPThread*) + 77
6   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
7   libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
8   libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 34:: CAQUEUE
0   libsystem_kernel.dylib        	0x00007fff5a60e21a mach_msg_trap + 10
1   libsystem_kernel.dylib        	0x00007fff5a60e768 mach_msg + 60
2   com.apple.CoreFoundation      	0x00007fff2e55b882 __CFRunLoopServiceMachPort + 328
3   com.apple.CoreFoundation      	0x00007fff2e55adf0 __CFRunLoopRun + 1612
4   com.apple.CoreFoundation      	0x00007fff2e55a552 CFRunLoopRunSpecific + 455
5   VBoxDD.dylib                  	0x000000011ff17fb5 0x11fde1000 + 1273781
6   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
7   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
8   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
9   libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
10  libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 35:
0   libsystem_pthread.dylib       	0x00007fff5a6cc3f0 start_wqthread + 0

Thread 36:
0   libsystem_pthread.dylib       	0x00007fff5a6cc3f0 start_wqthread + 0

Thread 37:
0   libsystem_pthread.dylib       	0x00007fff5a6cc3f0 start_wqthread + 0

Thread 38:
0   libsystem_pthread.dylib       	0x00007fff5a6cc3f0 start_wqthread + 0

Thread 39:
0   libsystem_kernel.dylib        	0x00007fff5a60e26e semaphore_timedwait_trap + 10
1   libdispatch.dylib             	0x00007fff5a48cc99 _dispatch_sema4_timedwait + 76
2   libdispatch.dylib             	0x00007fff5a48d377 _dispatch_semaphore_wait_slow + 58
3   libdispatch.dylib             	0x00007fff5a49a1fd _dispatch_worker_thread + 317
4   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
5   libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
6   libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 40:: com.apple.audio.IOThread.client
0   libsystem_kernel.dylib        	0x00007fff5a60e21a mach_msg_trap + 10
1   libsystem_kernel.dylib        	0x00007fff5a60e768 mach_msg + 60
2   com.apple.audio.CoreAudio     	0x00007fff2dfcaeda HALB_MachPort::SendMessageWithReply(unsigned int, unsigned int, unsigned int, unsigned int, mach_msg_header_t*, bool, unsigned int) + 122
3   com.apple.audio.CoreAudio     	0x00007fff2dfcae4f HALB_MachPort::SendSimpleMessageWithSimpleReply(unsigned int, unsigned int, int, int&, bool, unsigned int) + 45
4   com.apple.audio.CoreAudio     	0x00007fff2dfc739f HALC_ProxyIOContext::IOWorkLoop() + 1017
5   com.apple.audio.CoreAudio     	0x00007fff2dfc6df4 HALC_ProxyIOContext::IOThreadEntry(void*) + 122
6   com.apple.audio.CoreAudio     	0x00007fff2dfc6956 HALB_IOThread::Entry(void*) + 72
7   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
8   libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
9   libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 41:
0   libsystem_pthread.dylib       	0x00007fff5a6cc3f0 start_wqthread + 0

Thread 42:
0   libsystem_pthread.dylib       	0x00007fff5a6cc3f0 start_wqthread + 0

Thread 43:
0   libsystem_pthread.dylib       	0x00007fff5a6cc3f0 start_wqthread + 0

Thread 44:
0   libsystem_pthread.dylib       	0x00007fff5a6cc3f0 start_wqthread + 0

Thread 45:
0   libsystem_pthread.dylib       	0x00007fff5a6cc3f0 start_wqthread + 0

Thread 46:
0   libsystem_pthread.dylib       	0x00007fff5a6cc3f0 start_wqthread + 0

Thread 47:
0   libsystem_pthread.dylib       	0x00007fff5a6cc3f0 start_wqthread + 0

Thread 48:
0   libsystem_pthread.dylib       	0x00007fff5a6cc3f0 start_wqthread + 0

Thread 8 crashed with X86 Thread State (64-bit):
  rax: 0x0000000000000000  rbx: 0x000070000d07f000  rcx: 0x000070000d07b6f8  rdx: 0x0000000000000000
  rdi: 0x000000000000b707  rsi: 0x0000000000000006  rbp: 0x000070000d07b730  rsp: 0x000070000d07b6f8
   r8: 0x0000000000000000   r9: 0x000070000d07b650  r10: 0x0000000000000000  r11: 0x0000000000000206
  r12: 0x000000000000b707  r13: 0x0000000115b29000  r14: 0x0000000000000006  r15: 0x000000000000002d
  rip: 0x00007fff5a6142c2  rfl: 0x0000000000000206  cr2: 0x00007ffecbc7f570
  
Logical CPU:     0
Error Code:      0x02000036
Trap Number:     133


Binary Images:
       0x10de02000 -        0x10de23ff7 +org.virtualbox.app.VirtualBoxVM (6.1.10 - 6.1.10) <E16212EC-8D76-3B0C-814C-7BFCC94C0A11> /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM
       0x10de4b000 -        0x10e3a151f +VBoxRT.dylib (0) <62894218-58E3-3537-8ED0-A5D0BAA9580E> /Applications/VirtualBox.app/Contents/MacOS/VBoxRT.dylib
       0x10e4c7000 -        0x10e4d0ff7 +org.qt-project.QtMacExtrasVBox (5.6 - 5.6.3) <AC6F0DC8-BF41-3A20-B803-656B301B8CDF> /Applications/VirtualBox.app/Contents/Frameworks/QtMacExtrasVBox.framework/Versions/5/QtMacExtrasVBox
       0x10e4dc000 -        0x10e510fff +org.qt-project.QtPrintSupportVBox (5.6 - 5.6.3) <4C8D48EF-FC21-3BE7-895F-584399F0B308> /Applications/VirtualBox.app/Contents/Frameworks/QtPrintSupportVBox.framework/Versions/5/QtPrintSupportVBox
       0x10e537000 -        0x10e576fff +org.qt-project.QtOpenGLVBox (5.6 - 5.6.3) <F75D0235-BFE7-3966-A3C4-CFEA758B9A71> /Applications/VirtualBox.app/Contents/Frameworks/QtOpenGLVBox.framework/Versions/5/QtOpenGLVBox
       0x10e5fa000 -        0x10e66470f  dyld (655.1.1) <91A01B2E-622F-3FBC-8D67-AC6D5D1C0023> /usr/lib/dyld
       0x10e6c5000 -        0x10e7e8fff +VirtualBoxVM.dylib (0) <D8B020D2-66AF-3BBC-88E1-E4DBB2812AD9> /Applications/VirtualBox.app/Contents/MacOS/VirtualBoxVM.dylib
       0x10e851000 -        0x10ed78ff7 +org.qt-project.QtCoreVBox (5.6 - 5.6.3) <3A7A08E0-9422-393E-BD97-FD15E751434C> /Applications/VirtualBox.app/Contents/Frameworks/QtCoreVBox.framework/Versions/5/QtCoreVBox
       0x10ee3c000 -        0x10f317ff7 +org.qt-project.QtGuiVBox (5.6 - 5.6.3) <80F8D761-23D7-381D-B8D5-1C0C130F7876> /Applications/VirtualBox.app/Contents/Frameworks/QtGuiVBox.framework/Versions/5/QtGuiVBox
       0x10f418000 -        0x10f921fff +org.qt-project.QtWidgetsVBox (5.6 - 5.6.3) <5DFD063A-1901-39D3-90FB-138EFE7C6A9E> /Applications/VirtualBox.app/Contents/Frameworks/QtWidgetsVBox.framework/Versions/5/QtWidgetsVBox
       0x10fa93000 -        0x10fae8ff7 +VBoxDDU.dylib (0) <936C11CF-0353-3300-AA7B-3A5DC55F5D0A> /Applications/VirtualBox.app/Contents/MacOS/VBoxDDU.dylib
       0x10faf8000 -        0x111b9ffff +UICommon.dylib (0) <1C0A76C2-1EAE-33E9-81AA-9A2DD1A3FE73> /Applications/VirtualBox.app/Contents/MacOS/UICommon.dylib
       0x111da1000 -        0x1120a6fff +VBoxVMM.dylib (0) <84DD54C0-07CC-39A1-AF76-DEF4D6AE9771> /Applications/VirtualBox.app/Contents/MacOS/VBoxVMM.dylib
       0x112127000 -        0x1121d8ff7 +VBoxXPCOM.dylib (0) <F1D3A14D-4D3A-3FB0-823E-4E2798EF4CEF> /Applications/VirtualBox.app/Contents/MacOS/VBoxXPCOM.dylib
       0x1157e6000 -        0x115925fff +libqcocoa.dylib (0) <FA226E50-20A3-3C6D-B04E-9262D65300BC> /Applications/VirtualBox.app/Contents/plugins/platforms/libqcocoa.dylib
       0x11791a000 -        0x117923ff7 +VBoxSharedClipboard.dylib (0) <83275893-F5C7-34FE-94FB-DBBFC51DFA78> /Applications/VirtualBox.app/Contents/MacOS/VBoxSharedClipboard.dylib
       0x11792b000 -        0x117932fff +VBoxDragAndDropSvc.dylib (0) <0A99CD2D-48E3-3D18-8484-A8DF8929E939> /Applications/VirtualBox.app/Contents/MacOS/VBoxDragAndDropSvc.dylib
       0x117958000 -        0x11795b047  libobjc-trampolines.dylib (756.2) <5795A048-3940-3801-90CE-33D1B1AF81F4> /usr/lib/libobjc-trampolines.dylib
       0x118269000 -        0x118280fff +VBoxXPCOMIPCC.dylib (0) <4EC687AC-51DB-3E34-BD49-3AAE70D51BA5> /Applications/VirtualBox.app/Contents/MacOS/components/VBoxXPCOMIPCC.dylib
       0x118291000 -        0x11868eff7 +VBoxC.dylib (0) <81E94F5F-830A-3D42-B77A-A9970A794448> /Applications/VirtualBox.app/Contents/MacOS/components/VBoxC.dylib
       0x1186dd000 -        0x1186e0ff7 +VBoxSVCM.dylib (0) <BF1D7EBF-3313-3963-A66A-C5A4D3FF9453> /Applications/VirtualBox.app/Contents/MacOS/components/VBoxSVCM.dylib
       0x11989b000 -        0x1198a3ff7  com.apple.iokit.IOUSBLib (900.4.2 - 900.4.2) <A4432BC7-3694-3666-A3B2-B338CDB5A5B6> /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/IOUSBLib.bundle/Contents/MacOS/IOUSBLib
       0x119975000 -        0x119982fff  com.apple.iokit.IOHIDLib (2.0.0 - 2.0.0) <E77B604A-8C73-382E-AC8A-62E9ADE73E9D> /System/Library/Extensions/IOHIDFamily.kext/Contents/PlugIns/IOHIDLib.plugin/Contents/MacOS/IOHIDLib
       0x119ea9000 -        0x119eb6ff7 +VBoxSharedFolders.dylib (0) <919BF239-5930-3A63-9E8F-603AE9394A6C> /Applications/VirtualBox.app/Contents/MacOS/VBoxSharedFolders.dylib
       0x119ec0000 -        0x119ec5ff7 +VBoxGuestControlSvc.dylib (0) <BEEAA3B8-91CB-3B2E-A597-70D43A8CC8DF> /Applications/VirtualBox.app/Contents/MacOS/VBoxGuestControlSvc.dylib
       0x11fde1000 -        0x120143fff +VBoxDD.dylib (0) <EEB6BA71-4040-30C1-825F-FB907F5900A7> /Applications/VirtualBox.app/Contents/MacOS/VBoxDD.dylib
       0x1207e0000 -        0x120837ff7 +VBoxDD2.dylib (0) <481FD166-F49E-3A8D-B4C1-703F21AA6C95> /Applications/VirtualBox.app/Contents/MacOS/VBoxDD2.dylib
       0x12208d000 -        0x122094fff +VBoxGuestPropSvc.dylib (0) <3E171A9E-4125-3C1A-AECE-B47ABD39EAF3> /Applications/VirtualBox.app/Contents/MacOS/VBoxGuestPropSvc.dylib
       0x20d1cd000 -        0x20d362fff  com.apple.audio.units.Components (1.14 - 1.14) <D7C7C00C-202E-3F6B-A395-129A1A69A233> /System/Library/Components/CoreAudio.component/Contents/MacOS/CoreAudio
    0x7fff22c82000 -     0x7fff22fdbfff  com.apple.RawCamera.bundle (8.15.0 - 1031.4.4) <AB6E8A8F-0BFE-37EE-A135-44ABA4FCB559> /System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera
    0x7fff22fde000 -     0x7fff230eafff  com.apple.AMDMTLBronzeDriver (2.11.22 - 2.1.1) <E84F9A71-99A7-3879-A943-0B39816B7649> /System/Library/Extensions/AMDMTLBronzeDriver.bundle/Contents/MacOS/AMDMTLBronzeDriver
    0x7fff27ac5000 -     0x7fff27df5ff7  com.apple.driver.AppleIntelKBLGraphicsMTLDriver (12.10.22 - 12.1.0) <9F5D7B3C-027F-3E8D-A808-F212DDA36314> /System/Library/Extensions/AppleIntelKBLGraphicsMTLDriver.bundle/Contents/MacOS/AppleIntelKBLGraphicsMTLDriver
    0x7fff2a553000 -     0x7fff2a557fff  com.apple.agl (3.3.2 - AGL-3.3.2) <A5954DED-265B-395D-B907-3CEC000B10B6> /System/Library/Frameworks/AGL.framework/Versions/A/AGL
    0x7fff2a902000 -     0x7fff2a902fff  com.apple.Accelerate (1.11 - Accelerate 1.11) <762942CB-CFC9-3A0C-9645-A56523A06426> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
    0x7fff2a903000 -     0x7fff2a919ff7  libCGInterfaces.dylib (506.22) <1B6C92D9-F4B8-37BA-9635-94C4A56098CE> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/Libraries/libCGInterfaces.dylib
    0x7fff2a91a000 -     0x7fff2afb3fef  com.apple.vImage (8.1 - ???) <53FA3611-894E-3158-A654-FBD2F70998FE> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage
    0x7fff2afb4000 -     0x7fff2b22dff3  libBLAS.dylib (1243.200.4) <417CA0FC-B6CB-3FB3-ACBC-8914E3F62D20> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib
    0x7fff2b22e000 -     0x7fff2b2a0ffb  libBNNS.dylib (38.250.1) <538D12A2-9B9D-3E22-9896-F90F6E69C06E> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBNNS.dylib
    0x7fff2b2a1000 -     0x7fff2b64aff3  libLAPACK.dylib (1243.200.4) <92175DF4-863A-3780-909A-A3E5C410F2E9> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib
    0x7fff2b64b000 -     0x7fff2b660feb  libLinearAlgebra.dylib (1243.200.4) <CB671EE6-DEA1-391C-9B2B-AA09A46B4D7A> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLinearAlgebra.dylib
    0x7fff2b661000 -     0x7fff2b666ff3  libQuadrature.dylib (3.200.2) <1BAE7E22-2862-379F-B334-A3756067730F> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libQuadrature.dylib
    0x7fff2b667000 -     0x7fff2b6e3ff3  libSparse.dylib (79.200.5) <E78B33D3-672A-3C53-B512-D3DDB2E9AC8D> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparse.dylib
    0x7fff2b6e4000 -     0x7fff2b6f7fe3  libSparseBLAS.dylib (1243.200.4) <E9243341-DB77-37C1-97C5-3DFA00DD70FA> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparseBLAS.dylib
    0x7fff2b6f8000 -     0x7fff2b8dfff7  libvDSP.dylib (671.250.4) <7B110627-A9C1-3FB7-A077-0C7741BA25D8> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib
    0x7fff2b8e0000 -     0x7fff2b993ff7  libvMisc.dylib (671.250.4) <D5BA4812-BFFC-3CD0-B382-905CD8555DA6> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib
    0x7fff2b994000 -     0x7fff2b994fff  com.apple.Accelerate.vecLib (3.11 - vecLib 3.11) <74288115-EF61-30B6-843F-0593B31D4929> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib
    0x7fff2bb36000 -     0x7fff2c8ebffb  com.apple.AppKit (6.9 - 1671.60.109) <942F1512-A819-347B-90B4-075F2367950C> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
    0x7fff2c93d000 -     0x7fff2c93dfff  com.apple.ApplicationServices (50.1 - 50.1) <FBE56E8E-9B8A-3B04-A0C6-20CBA0E6CED6> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices
    0x7fff2c93e000 -     0x7fff2c9a9fff  com.apple.ApplicationServices.ATS (377 - 453.11.2.2) <A258DA73-114B-3102-A056-4AAAD3CEB9DD> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS
    0x7fff2ca42000 -     0x7fff2cb59ff7  libFontParser.dylib (228.6.2.5) <CEDF1D5A-8897-3621-A1DC-558301F8BE05> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontParser.dylib
    0x7fff2cb5a000 -     0x7fff2cb9cfff  libFontRegistry.dylib (228.12.2.4) <6DDE44EC-FF6B-3893-9209-45E0955ABDD5> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib
    0x7fff2cbf6000 -     0x7fff2cc28fff  libTrueTypeScaler.dylib (228.6.2.5) <E17ABF05-EC1E-3042-BBE2-C2E2909D3875> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libTrueTypeScaler.dylib
    0x7fff2cc8d000 -     0x7fff2cc91ff3  com.apple.ColorSyncLegacy (4.13.0 - 1) <E8E9342C-47EB-359D-A373-554AC19B174A> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSyncLegacy.framework/Versions/A/ColorSyncLegacy
    0x7fff2cd2c000 -     0x7fff2cd7eff7  com.apple.HIServices (1.22 - 628) <2BE461FF-80B9-30D3-A574-AED5724B1C1B> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices
    0x7fff2cd7f000 -     0x7fff2cd8efff  com.apple.LangAnalysis (1.7.0 - 1.7.0) <F5617A2A-FEA6-3832-B5BA-C2111B98786F> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis
    0x7fff2cd8f000 -     0x7fff2cdd8ff7  com.apple.print.framework.PrintCore (14.7 - 503.8) <E1D0FCBC-155E-372E-A90F-4A20B94FC114> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore
    0x7fff2cdd9000 -     0x7fff2ce12ff7  com.apple.QD (3.12 - 407.2) <28C7D39F-59C9-3314-BECC-67045487229C> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD
    0x7fff2ce13000 -     0x7fff2ce1ffff  com.apple.speech.synthesis.framework (8.1.3 - 8.1.3) <5E7B9BD4-122B-3012-A044-3259C97E7509> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis
    0x7fff2ce20000 -     0x7fff2d097fff  com.apple.audio.toolbox.AudioToolbox (1.14 - 1.14) <32487CB2-246B-3B80-8F60-D65DFC367DDC> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
    0x7fff2d099000 -     0x7fff2d099fff  com.apple.audio.units.AudioUnit (1.14 - 1.14) <B489CFDA-DEF3-38F5-A815-23EC30B8DA03> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
    0x7fff2d3f2000 -     0x7fff2d794fff  com.apple.CFNetwork (978.4 - 978.4) <2D4EEB80-0C17-34E0-B2B5-E24308CF9359> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
    0x7fff2d7a9000 -     0x7fff2d7a9fff  com.apple.Carbon (158 - 158) <BE5FB24D-510F-3AE6-A455-79BFDEB99AEC> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
    0x7fff2d7aa000 -     0x7fff2d7adffb  com.apple.CommonPanels (1.2.6 - 98) <1CD6D56D-8EC7-3528-8CBC-FC69533519B5> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels
    0x7fff2d7ae000 -     0x7fff2daa5fff  com.apple.HIToolbox (2.1.1 - 918.7) <88D7F19C-8C9D-384B-BAB5-8205CA282F2C> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox
    0x7fff2daa6000 -     0x7fff2daa9ff3  com.apple.help (1.3.8 - 66) <A08517EB-8958-36C9-AEE0-1A8FEEACBE3F> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help
    0x7fff2daaa000 -     0x7fff2daafff7  com.apple.ImageCapture (9.0 - 1534.2) <DB063E87-ED8F-3E4E-A7E2-A6B45FA73EF7> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture
    0x7fff2dab0000 -     0x7fff2db45ff3  com.apple.ink.framework (10.9 - 225) <7C7E9483-2E91-3DD3-B1E0-C238F42CA0DD> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink
    0x7fff2db46000 -     0x7fff2db5eff7  com.apple.openscripting (1.7 - 179.1) <9B8C1ECC-5864-3E21-9149-863E884EA25C> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting
    0x7fff2db7e000 -     0x7fff2db7fff7  com.apple.print.framework.Print (14.2 - 267.4) <A7A9D2A0-D4E0-35EF-A0F7-50521F707C33> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print
    0x7fff2db80000 -     0x7fff2db82ff7  com.apple.securityhi (9.0 - 55006) <05717F77-7A7B-37E6-AB3E-03F063E9095B> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI
    0x7fff2db83000 -     0x7fff2db89ff7  com.apple.speech.recognition.framework (6.0.3 - 6.0.3) <3CC050FB-EBCB-3087-8EA5-F378C8F99217> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition
    0x7fff2dcab000 -     0x7fff2dcabfff  com.apple.Cocoa (6.11 - 23) <F6FA8C4A-40B6-30CB-ABD2-FDD165F3ECC4> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
    0x7fff2dcb9000 -     0x7fff2de08ff7  com.apple.ColorSync (4.13.0 - 3345.6) <356BA478-76DE-3087-86BE-5E884276AB83> /System/Library/Frameworks/ColorSync.framework/Versions/A/ColorSync
    0x7fff2df94000 -     0x7fff2e01afff  com.apple.audio.CoreAudio (4.3.0 - 4.3.0) <1E8E64E6-0E58-375A-97F7-07CB4EE181AC> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
    0x7fff2e07e000 -     0x7fff2e0a8ffb  com.apple.CoreBluetooth (1.0 - 1) <4F2DDEF0-1F92-384B-8CDA-4958725D0A8E> /System/Library/Frameworks/CoreBluetooth.framework/Versions/A/CoreBluetooth
    0x7fff2e0a9000 -     0x7fff2e42efef  com.apple.CoreData (120 - 866.6) <132CB39B-8D58-30FA-B8AD-49BFFF34B293> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
    0x7fff2e42f000 -     0x7fff2e51fff7  com.apple.CoreDisplay (101.3 - 110.18) <6DD41271-E145-3E99-9D49-7CC8AC1C65B6> /System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay
    0x7fff2e520000 -     0x7fff2e965fff  com.apple.CoreFoundation (6.9 - 1575.300) <2ABD4A7D-6C28-3594-8584-4D7445911EAA> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
    0x7fff2e967000 -     0x7fff2eff7fe7  com.apple.CoreGraphics (2.0 - 1265.11) <B433DE85-643A-3A48-AE01-2BE1F4E888D1> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics
    0x7fff2eff9000 -     0x7fff2f319fff  com.apple.CoreImage (14.4.0 - 750.0.140) <11026E39-D2FF-3CF6-8ACE-7BA293F9853E> /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage
    0x7fff2f616000 -     0x7fff2f71afff  com.apple.CoreMedia (1.0 - 2290.14) <2C7A5348-7F19-3E28-97E4-6065A64B1DC9> /System/Library/Frameworks/CoreMedia.framework/Versions/A/CoreMedia
    0x7fff2f777000 -     0x7fff2f777fff  com.apple.CoreServices (946 - 946) <FA85ED71-4375-319B-BDC8-AD6231653280> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
    0x7fff2f778000 -     0x7fff2f7f4ff7  com.apple.AE (773 - 773) <55AE7C9E-27C3-30E9-A047-3B92A6FD53B4> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE
    0x7fff2f7f5000 -     0x7fff2faccfff  com.apple.CoreServices.CarbonCore (1178.33 - 1178.33) <CB87F0C7-2CD6-3983-8E32-B6A2EC925352> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
    0x7fff2facd000 -     0x7fff2fb15ff7  com.apple.DictionaryServices (1.2 - 284.16.4) <746EB200-DC51-30AE-9CBC-608A7B4CC8DA> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices
    0x7fff2fb16000 -     0x7fff2fb1effb  com.apple.CoreServices.FSEvents (1239.200.13 - 1239.200.13) <5913F08D-4AA2-3200-B998-012E6A19A66D> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/FSEvents.framework/Versions/A/FSEvents
    0x7fff2fb1f000 -     0x7fff2fcd0ff7  com.apple.LaunchServices (946 - 946) <A0C91634-9410-38E8-BC11-7A5A369E6BA5> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices
    0x7fff2fcd1000 -     0x7fff2fd6fff7  com.apple.Metadata (10.7.0 - 1191.58) <89DA10B4-5695-3FD9-A920-C34C33957868> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata
    0x7fff2fd70000 -     0x7fff2fdbaff7  com.apple.CoreServices.OSServices (946 - 946) <20C4EEF8-D5AC-39A0-9B4A-78F88E3EFBCC> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices
    0x7fff2fdbb000 -     0x7fff2fe22ff7  com.apple.SearchKit (1.4.0 - 1.4.0) <DA08AA6F-A6F1-36C0-87F4-E26294E51A3A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit
    0x7fff2fe23000 -     0x7fff2fe44ff3  com.apple.coreservices.SharedFileList (71.28 - 71.28) <487A8464-729E-305A-B5D1-E3FE8EB9CFC5> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SharedFileList.framework/Versions/A/SharedFileList
    0x7fff3014f000 -     0x7fff302b1ff3  com.apple.CoreText (352.0 - 584.26.3.4) <7247EA49-9F90-3258-AABF-932C6343BD6A> /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText
    0x7fff302b2000 -     0x7fff302f2ff3  com.apple.CoreVideo (1.8 - 281.4) <10CF8E52-07E3-382B-8091-2CEEEFFA69B4> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
    0x7fff302f3000 -     0x7fff30382fff  com.apple.framework.CoreWLAN (13.0 - 1375.2) <A476486C-B863-3941-BAE6-A78BDFED4A3B> /System/Library/Frameworks/CoreWLAN.framework/Versions/A/CoreWLAN
    0x7fff305d9000 -     0x7fff305deffb  com.apple.DiskArbitration (2.7 - 2.7) <A31C207C-8255-3E93-9DD7-D80C4B179050> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
    0x7fff307a5000 -     0x7fff30b52ffb  com.apple.Foundation (6.9 - 1575.300) <CA3584DA-A8AF-3931-9B53-3B1EA240575C> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
    0x7fff30bc1000 -     0x7fff30bf0ffb  com.apple.GSS (4.0 - 2.0) <E2B90D08-3857-3155-9FCC-07D778988EC9> /System/Library/Frameworks/GSS.framework/Versions/A/GSS
    0x7fff30cf0000 -     0x7fff30dfafff  com.apple.Bluetooth (6.0.14 - 6.0.14d11) <C2CE7A31-E7A1-3058-AA32-F80297C04FFC> /System/Library/Frameworks/IOBluetooth.framework/Versions/A/IOBluetooth
    0x7fff30e5d000 -     0x7fff30eecfff  com.apple.framework.IOKit (2.0.2 - 1483.260.4) <8A90F547-86EF-3DFB-92FE-0E2C0376DD84> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
    0x7fff30eee000 -     0x7fff30efdffb  com.apple.IOSurface (255.6.1 - 255.6.1) <85F85EBB-EA59-3A8B-B3EB-7C20F3CC77AE> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface
    0x7fff30f51000 -     0x7fff310ddfef  com.apple.ImageIO.framework (3.3.0 - 1850.2.7) <9C059297-033F-3441-BDC1-46CC1139DBCB> /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO
    0x7fff310de000 -     0x7fff310e2ffb  libGIF.dylib (1850.2.7) <1F60E131-3255-324F-A73D-87B8B66A51F9> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib
    0x7fff310e3000 -     0x7fff311bffe7  libJP2.dylib (1850.2.7) <209FEE0C-319C-3B13-90BF-D36C9A8D621C> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib
    0x7fff311c0000 -     0x7fff311e5feb  libJPEG.dylib (1850.2.7) <AB1D6EDF-FB59-34F9-81D4-ED01B965BD1B> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib
    0x7fff314bb000 -     0x7fff314e1feb  libPng.dylib (1850.2.7) <85AFD5DD-D842-3F6C-A6D6-147A283B97EE> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib
    0x7fff314e2000 -     0x7fff314e4ffb  libRadiance.dylib (1850.2.7) <3C77681E-A94B-314B-BD85-95067016E204> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib
    0x7fff314e5000 -     0x7fff31532fff  libTIFF.dylib (1850.2.7) <7D9DC37B-7855-3344-A12C-DFF588B78BDA> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib
    0x7fff326a5000 -     0x7fff326befff  com.apple.Kerberos (3.0 - 1) <DB1E0679-37E1-3B93-9789-32F63D660C3B> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos
    0x7fff32978000 -     0x7fff32982fff  com.apple.MediaAccessibility (1.0 - 114.4) <76C449C5-DB45-3D7F-BFAD-3DACEF15DA21> /System/Library/Frameworks/MediaAccessibility.framework/Versions/A/MediaAccessibility
    0x7fff32a32000 -     0x7fff330d8fff  com.apple.MediaToolbox (1.0 - 2290.14) <927F9E24-32DB-33F9-9866-4DD8092A51F4> /System/Library/Frameworks/MediaToolbox.framework/Versions/A/MediaToolbox
    0x7fff330da000 -     0x7fff33182ff7  com.apple.Metal (162.2 - 162.2) <B65C71BF-D40E-3BB3-940C-117DDD203551> /System/Library/Frameworks/Metal.framework/Versions/A/Metal
    0x7fff3319e000 -     0x7fff331bdff7  com.apple.MetalPerformanceShaders.MPSCore (1.0 - 1) <44CE8362-E972-3697-AD6F-15BC863BAEB8> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSCore.framework/Versions/A/MPSCore
    0x7fff331be000 -     0x7fff3323afe7  com.apple.MetalPerformanceShaders.MPSImage (1.0 - 1) <EE8440DA-66DF-3923-ABBC-E0543211C069> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSImage.framework/Versions/A/MPSImage
    0x7fff3323b000 -     0x7fff33262fff  com.apple.MetalPerformanceShaders.MPSMatrix (1.0 - 1) <E64450DF-2B96-331E-B7F4-666E00571C70> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSMatrix.framework/Versions/A/MPSMatrix
    0x7fff33263000 -     0x7fff3338eff7  com.apple.MetalPerformanceShaders.MPSNeuralNetwork (1.0 - 1) <F2CF26B6-73F1-3644-8FE9-CDB9B2C4501F> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSNeuralNetwork.framework/Versions/A/MPSNeuralNetwork
    0x7fff3338f000 -     0x7fff333a9fff  com.apple.MetalPerformanceShaders.MPSRayIntersector (1.0 - 1) <B33A35C3-0393-366B-ACFB-F4BB6A5F7B4A> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSRayIntersector.framework/Versions/A/MPSRayIntersector
    0x7fff333aa000 -     0x7fff333abff7  com.apple.MetalPerformanceShaders.MetalPerformanceShaders (1.0 - 1) <69F14BCF-C5C5-3BF8-9C31-8F87D2D6130A> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/MetalPerformanceShaders
    0x7fff341a4000 -     0x7fff341b0ff7  com.apple.NetFS (6.0 - 4.0) <E917806F-0607-3292-B2D6-A15404D61B99> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS
    0x7fff36c4e000 -     0x7fff36ca5ff7  com.apple.opencl (2.15.3 - 2.15.3) <3F72F3B0-F607-39E5-BDF6-5C37C9B67430> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL
    0x7fff36ca6000 -     0x7fff36cc1ff7  com.apple.CFOpenDirectory (10.14 - 207.200.4) <F03D84EB-49B2-3A00-9127-B9A269824026> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory
    0x7fff36cc2000 -     0x7fff36ccdffb  com.apple.OpenDirectory (10.14 - 207.200.4) <A8020CEE-5B78-3581-A735-EA2833683F31> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory
    0x7fff3761d000 -     0x7fff3761ffff  libCVMSPluginSupport.dylib (17.7.3) <83C36A70-5F35-37D1-A124-A2CD497F1915> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib
    0x7fff37620000 -     0x7fff37625ff3  libCoreFSCache.dylib (166.5) <5BC99EE7-7FFD-3F30-9AEE-EEDC25067AC4> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreFSCache.dylib
    0x7fff37626000 -     0x7fff3762afff  libCoreVMClient.dylib (166.5) <B8FA5858-8185-3992-AD3B-A81AF08C3CDD> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib
    0x7fff3762b000 -     0x7fff37633ff7  libGFXShared.dylib (17.7.3) <09F50639-F0CB-3312-8BAC-5AA8083350F6> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib
    0x7fff37634000 -     0x7fff3763ffff  libGL.dylib (17.7.3) <4EEC82D4-A3C6-336D-9F90-67F1D24ED35B> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
    0x7fff37640000 -     0x7fff3767afef  libGLImage.dylib (17.7.3) <B175F261-69D1-3366-A009-DF75CB32E2F9> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib
    0x7fff377ee000 -     0x7fff3782cfff  libGLU.dylib (17.7.3) <5BB2F84A-4D96-35A1-8A5B-99AE39CD9E59> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
    0x7fff381c9000 -     0x7fff381d8ffb  com.apple.opengl (17.7.3 - 17.7.3) <9C1FCE6E-FED6-3A09-9FDC-4C81F8CDB2A6> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
    0x7fff38fe2000 -     0x7fff39239ff7  com.apple.QuartzCore (1.11 - 701.14) <1E82D0E6-EB06-3CC6-AEB5-06E3365887D0> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
    0x7fff39a6f000 -     0x7fff39d6fff7  com.apple.security (7.0 - 58286.270.10) <990FF42E-0726-318F-94ED-A8FDF7F41402> /System/Library/Frameworks/Security.framework/Versions/A/Security
    0x7fff39d70000 -     0x7fff39dfcfff  com.apple.securityfoundation (6.0 - 55185.260.1) <964F1F81-D8F1-3952-8137-EF21CDD3A7A6> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation
    0x7fff39e2e000 -     0x7fff39e32fff  com.apple.xpc.ServiceManagement (1.0 - 1) <B0B6F84E-2892-346B-A7D3-BAEE726DA4BF> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement
    0x7fff3a1cb000 -     0x7fff3a238fff  com.apple.SystemConfiguration (1.17 - 1.17) <30C8327F-3EFF-3520-9C50-016F8B6B954F> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration
    0x7fff3a497000 -     0x7fff3a7f8fff  com.apple.VideoToolbox (1.0 - 2290.14) <30C690CF-8935-39E8-B343-ADB009C84FC5> /System/Library/Frameworks/VideoToolbox.framework/Versions/A/VideoToolbox
    0x7fff3d474000 -     0x7fff3d519fff  com.apple.APFS (1.0 - 1) <06284DE8-5883-39F8-B04D-0D5EA74D12ED> /System/Library/PrivateFrameworks/APFS.framework/Versions/A/APFS
    0x7fff3df2e000 -     0x7fff3df2fff7  com.apple.AggregateDictionary (1.0 - 1) <A6AF8AC4-1F25-37C4-9157-A02E9C200926> /System/Library/PrivateFrameworks/AggregateDictionary.framework/Versions/A/AggregateDictionary
    0x7fff3e530000 -     0x7fff3e55cff7  com.apple.framework.Apple80211 (13.0 - 1380.2) <E4D12303-8B12-303C-91E2-3B40F60832BA> /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Apple80211
    0x7fff3e684000 -     0x7fff3e693fc7  com.apple.AppleFSCompression (96.200.3 - 1.0) <3CF60CE8-976E-3CB8-959D-DD0948C1C2DE> /System/Library/PrivateFrameworks/AppleFSCompression.framework/Versions/A/AppleFSCompression
    0x7fff3e78f000 -     0x7fff3e79afff  com.apple.AppleIDAuthSupport (1.0 - 1) <2E9D1398-DBE6-328B-ADDA-20FA5FAD7405> /System/Library/PrivateFrameworks/AppleIDAuthSupport.framework/Versions/A/AppleIDAuthSupport
    0x7fff3e7db000 -     0x7fff3e824ff3  com.apple.AppleJPEG (1.0 - 1) <4C1F426B-7D77-3980-9633-7DBD8C666B9A> /System/Library/PrivateFrameworks/AppleJPEG.framework/Versions/A/AppleJPEG
  "	wesinator
17383	VirtualBox crashed with SIGABRT	VirtualBox 5.2.4	2017-12-20T19:11:05Z	2017-12-21T15:52:29Z	2017-12-21T15:52:29Z	"Hello,

Open report in launchpad.net
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1739458

""I'm working with kernel 4.15-RC4 and kernel default.""



BackTrace:
{{{
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
        set = {__val = {8192, 272, 206158430232, 140720591186048, 140720591185856, 40, 48, 4887535095258628352, 94146280617152, 94146279598128, 94146279598432, 139833995275296, 0, 144, 128, 139833991812372}}
        pid = <optimized out>
        tid = <optimized out>
#1  0x00007f2da3638f5d in __GI_abort () at abort.c:90
        save_stage = 2
        act = {__sigaction_handler = {sa_handler = 0x7ffc10d9a880, sa_sigaction = 0x7ffc10d9a880}, sa_mask = {__val = {139833792439968, 140720591186064, 3, 0, 140720591186576, 140720591186544, 139833999716348, 140720591186168, 139833999740728, 140720591186400, 139833785431219, 140720591186544, 0, 140720591186576, 4887535095258628352, 140720591186576}}, sa_flags = 282700024, sa_restorer = 0x7ffc10d9aa90}
        sigs = {__val = {32, 0 <repeats 15 times>}}
#2  0x00007f2d971bcfe7 in qt_message_fatal (context=..., message=<synthetic pointer>...) at global/qlogging.cpp:1690
No locals.
#3  QMessageLogger::fatal (this=this@entry=0x7ffc10d9a9e0, msg=msg@entry=0x7f2d9755ac28 ""Cannot mix incompatible Qt library (version 0x%x) with this library (version 0x%x)"") at global/qlogging.cpp:796
        message = <optimized out>
        ap = {{gp_offset = 32, fp_offset = 48, overflow_arg_area = 0x7ffc10d9a9e0, reg_save_area = 0x7ffc10d9a920}}
#4  0x00007f2d973dc01e in QObjectPrivate::QObjectPrivate (this=<optimized out>, version=<optimized out>) at kernel/qobject.cpp:215
        this = <optimized out>
        version = <optimized out>
#5  0x00007f2d70d8a05d in QSvgRendererPrivate::QSvgRendererPrivate (this=0x55a023938540) at qsvgrenderer.cpp:110
No locals.
#6  QSvgRenderer::QSvgRenderer (this=0x7ffc10d9aa90, filename=..., parent=0x0) at qsvgrenderer.cpp:137
No locals.
#7  0x00007f2d7034712c in QSvgIconEngine::addFile (this=this@entry=0x55a0234e6660, fileName=..., mode=mode@entry=QIcon::Normal, state=state@entry=QIcon::Off) at qsvgiconengine.cpp:239
        renderer = {<QObject> = {_vptr.QObject = 0x55a0234e6660, static staticMetaObject = {d = {superdata = 0x0, stringdata = 0x7f2d9755b720 <qt_meta_stringdata_QObject>, data = 0x7f2d9755b600 <qt_meta_data_QObject>, static_metacall = 0x7f2d973e6630 <QObject::qt_static_metacall(QObject*, QMetaObject::Call, int, void**)>, relatedMetaObjects = 0x0, extradata = 0x0}}, d_ptr = {d = 0x55a02317b010}, static staticQtMetaObject = {d = {superdata = 0x0, stringdata = 0x7f2d9755e3a0 <qt_meta_stringdata_Qt>, data = 0x7f2d9755b840 <qt_meta_data_Qt>, static_metacall = 0x0, relatedMetaObjects = 0x0, extradata = 0x0}}}, static staticMetaObject = {d = {superdata = 0x7f2d97860a00 <QObject::staticMetaObject>, stringdata = 0x7f2d70d94d00 <qt_meta_stringdata_QSvgRenderer>, data = 0x7f2d70d94b80 <qt_meta_data_QSvgRenderer>, static_metacall = 0x7f2d70d8a5a0 <QSvgRenderer::qt_static_metacall(QObject*, QMetaObject::Call, int, void**)>, relatedMetaObjects = 0x0, extradata = 0x0}}}
        fi = {d_ptr = {d = 0x55a0239c5590}}
        abs = {static null = {<No data fields>}, d = 0x55a0239a6660}
        state = QIcon::Off
        mode = QIcon::Normal
        fileName = @0x7ffc10d9ac20: {static null = {<No data fields>}, d = 0x55a0239a6660}
        this = 0x55a0234e6660
#8  0x00007f2d70345329 in QSvgIconPlugin::create (this=<optimized out>, file=...) at main.cpp:68
        engine = 0x55a0234e6660
#9  0x00007f2d96b45d42 in iconEngineFromSuffix (fileName=..., suffix=...) at image/qicon.cpp:1036
        index = 0
#10 0x00007f2d96b4ab7d in QIcon::addFile (this=0x7ffc10d9ac10, fileName=..., size=..., mode=QIcon::Normal, state=QIcon::Off) at image/qicon.cpp:1081
        info = {d_ptr = {d = 0x55a0239c53b0}}
        engine = <optimized out>
        atNxFileName = {static null = {<No data fields>}, d = 0x55a0239387b0}
        state = QIcon::Off
        this = 0x7ffc10d9ac10
        mode = QIcon::Normal
        size = @0x7ffc10d9abf0: {wd = -1, ht = -1}
        fileName = @0x7ffc10d9ac20: {static null = {<No data fields>}, d = 0x55a0239a6660}
#11 0x00007f2d96b4ad03 in QIcon::QIcon (this=<optimized out>, fileName=...) at image/qicon.cpp:716
No locals.
#12 0x00007f2d98dee4b6 in UISelectorWindow::prepareIcon (this=this@entry=0x55a0239c8690) at /build/virtualbox-SNwOtQ/virtualbox-5.2.4-dfsg/src/VBox/Frontends/VirtualBox/src/selector/UISelectorWindow.cpp:1371
        icon = {d = 0x0}
#13 0x00007f2d98dfad34 in UISelectorWindow::prepare (this=0x55a0239c8690) at /build/virtualbox-SNwOtQ/virtualbox-5.2.4-dfsg/src/VBox/Frontends/VirtualBox/src/selector/UISelectorWindow.cpp:1332
No locals.
#14 0x00007f2d98dfae12 in UISelectorWindow::create () at /build/virtualbox-SNwOtQ/virtualbox-5.2.4-dfsg/src/VBox/Frontends/VirtualBox/src/selector/UISelectorWindow.cpp:96
No locals.
#15 0x00007f2d98d296af in VBoxGlobal::showUI (this=<optimized out>) at /build/virtualbox-SNwOtQ/virtualbox-5.2.4-dfsg/src/VBox/Frontends/VirtualBox/src/globals/VBoxGlobal.cpp:4297
        vboxVersion = {static null = {<No data fields>}, d = 0x55a0239c4fb0}
#16 0x00007f2d990817a5 in VBoxGlobal::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at /build/virtualbox-SNwOtQ/virtualbox-5.2.4-dfsg/out/obj/VirtualBox/qtmoc/VBoxGlobal.cpp:137
        _t = <optimized out>
#17 0x00007f2d973df7e2 in QObject::event (this=0x55a023424800, e=<optimized out>) at kernel/qobject.cpp:1246
        mce = <optimized out>
        sw = {receiver = 0x55a023424800, previousSender = 0x0, currentSender = {sender = 0x0, signal = -1, ref = 1}, switched = true}
#18 0x00007f2d962ce59c in QApplicationPrivate::notify_helper (this=this@entry=0x55a0232ed810, receiver=receiver@entry=0x55a023424800, e=e@entry=0x55a02398d800) at kernel/qapplication.cpp:3722
        consumed = <optimized out>
#19 0x00007f2d962d5e64 in QApplication::notify (this=0x7ffc10d9b380, receiver=0x55a023424800, e=0x55a02398d800) at kernel/qapplication.cpp:3481
        w = 0x55a023424800
        extra = <optimized out>
        isProxyWidget = <optimized out>
        res = false
#20 0x00007f2d973b0178 in QCoreApplication::notifyInternal2 (receiver=0x55a023424800, event=event@entry=0x55a02398d800) at kernel/qcoreapplication.cpp:1018
        selfRequired = true
        result = false
        cbdata = {0x55a023424800, 0x55a02398d800, 0x7ffc10d9afcf}
        d = <optimized out>
        threadData = 0x55a0232ed980
        scopeLevelCounter = {threadData = 0x55a0232ed980}
#21 0x00007f2d973b28ed in QCoreApplication::sendEvent (event=0x55a02398d800, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:233
No locals.
#22 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x55a0232ed980) at kernel/qcoreapplication.cpp:1678
        e = 0x55a02398d800
        pe = <optimized out>
        r = <optimized out>
        unlocker = {m = <synthetic pointer><error reading variable>}
        event_deleter = {d = 0x55a02398d800}
        locker = {val = 94146273401264}
        startOffset = 0
        i = @0x55a0232ed9a4: 65
        cleanup = {receiver = 0x0, event_type = 0, data = 0x55a0232ed980, exceptionCaught = true}
#23 0x00007f2d973b2e78 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1532
        data = <optimized out>
#24 0x00007f2d974099e3 in postEventSourceDispatch (s=s@entry=0x55a023463f50) at kernel/qeventdispatcher_glib.cpp:276
        source = 0x55a023463f50
#25 0x00007f2d9347afb7 in g_main_dispatch (context=0x7f2d88005000) at ../../../../glib/gmain.c:3148
        dispatch = 0x7f2d974099d0 <postEventSourceDispatch(GSource*, GSourceFunc, gpointer)>
        prev_source = 0x0
        was_in_call = 0
        user_data = 0x0
        callback = 0x0
        cb_funcs = <optimized out>
        cb_data = 0x0
        need_destroy = <optimized out>
        source = 0x55a023463f50
        current = 0x55a02336e940
        i = 4
#26 g_main_context_dispatch (context=context@entry=0x7f2d88005000) at ../../../../glib/gmain.c:3813
No locals.
#27 0x00007f2d9347b1f0 in g_main_context_iterate (context=context@entry=0x7f2d88005000, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../../../../glib/gmain.c:3886
        max_priority = 0
        timeout = 0
        some_ready = 1
        nfds = <optimized out>
        allocated_nfds = 6
        fds = 0x55a023994210
#28 0x00007f2d9347b27c in g_main_context_iteration (context=0x7f2d88005000, may_block=may_block@entry=1) at ../../../../glib/gmain.c:3947
        retval = <optimized out>
#29 0x00007f2d9740900f in QEventDispatcherGlib::processEvents (this=0x55a02345cd20, flags=...) at kernel/qeventdispatcher_glib.cpp:423
        d = 0x55a023463ea0
        canWait = true
        savedFlags = {i = 0}
        result = <optimized out>
#30 0x00007f2d973ae1ca in QEventLoop::exec (this=this@entry=0x7ffc10d9b2b0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
        d = 0x55a0239dba30
        locker = {val = 94146273401456}
        ref = {d = 0x55a0239dba30, locker = @0x7ffc10d9b238, exceptionCaught = true}
#31 0x00007f2d973b7134 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1291
        threadData = 0x55a0232ed980
        eventLoop = {<QObject> = {_vptr.QObject = 0x7f2d978684c8 <vtable for QEventLoop+16>, static staticMetaObject = {d = {superdata = 0x0, stringdata = 0x7f2d9755b720 <qt_meta_stringdata_QObject>, data = 0x7f2d9755b600 <qt_meta_data_QObject>, static_metacall = 0x7f2d973e6630 <QObject::qt_static_metacall(QObject*, QMetaObject::Call, int, void**)>, relatedMetaObjects = 0x0, extradata = 0x0}}, d_ptr = {d = 0x55a0239dba30}, static staticQtMetaObject = {d = {superdata = 0x0, stringdata = 0x7f2d9755e3a0 <qt_meta_stringdata_Qt>, data = 0x7f2d9755b840 <qt_meta_data_Qt>, static_metacall = 0x0, relatedMetaObjects = 0x0, extradata = 0x0}}}, static staticMetaObject = {d = {superdata = 0x7f2d97860a00 <QObject::staticMetaObject>, stringdata = 0x7f2d97556300 <qt_meta_stringdata_QEventLoop>, data = 0x7f2d975562a0 <qt_meta_data_QEventLoop>, static_metacall = 0x7f2d973adec0 <QEventLoop::qt_static_metacall(QObject*, QMetaObject::Call, int, void**)>, relatedMetaObjects = 0x0, extradata = 0x0}}}
        returnCode = <optimized out>
#32 0x00007f2d96ab635c in QGuiApplication::exec () at kernel/qguiapplication.cpp:1679
No locals.
#33 0x00007f2d962ce4f5 in QApplication::exec () at kernel/qapplication.cpp:2910
No locals.
#34 0x00007f2d98c98e93 in TrustedMain (argc=<optimized out>, argv=<optimized out>) at /build/virtualbox-SNwOtQ/virtualbox-5.2.4-dfsg/src/VBox/Frontends/VirtualBox/src/main.cpp:485
        fHelpShown = false
        a = {<QGuiApplication> = {<QCoreApplication> = {<QObject> = {_vptr.QObject = 0x7f2d9698ffd0 <vtable for QApplication+16>, static staticMetaObject = {d = {superdata = 0x0, stringdata = 0x7f2d9755b720 <qt_meta_stringdata_QObject>, data = 0x7f2d9755b600 <qt_meta_data_QObject>, static_metacall = 0x7f2d973e6630 <QObject::qt_static_metacall(QObject*, QMetaObject::Call, int, void**)>, relatedMetaObjects = 0x0, extradata = 0x0}}, d_ptr = {d = 0x55a0232ed810}, static staticQtMetaObject = {d = {superdata = 0x0, stringdata = 0x7f2d9755e3a0 <qt_meta_stringdata_Qt>, data = 0x7f2d9755b840 <qt_meta_data_Qt>, static_metacall = 0x0, relatedMetaObjects = 0x0, extradata = 0x0}}}, static staticMetaObject = {d = {superdata = 0x7f2d97860a00 <QObject::staticMetaObject>, stringdata = 0x7f2d97556960 <qt_meta_stringdata_QCoreApplication>, data = 0x7f2d97556840 <qt_meta_data_QCoreApplication>, static_metacall = 0x7f2d973b1bb0 <QCoreApplication::qt_static_metacall(QObject*, QMetaObject::Call, int, void**)>, relatedMetaObjects = 0x0, extradata = 0x0}}, static self = 0x7ffc10d9b380}, static staticMetaObject = {d = {superdata = 0x7f2d97868660 <QCoreApplication::staticMetaObject>, stringdata = 0x7f2d96e4f6e0 <qt_meta_stringdata_QGuiApplication>, data = 0x7f2d96e4f480 <qt_meta_data_QGuiApplication>, static_metacall = 0x7f2d96ac0e20 <QGuiApplication::qt_static_metacall(QObject*, QMetaObject::Call, int, void**)>, relatedMetaObjects = 0x0, extradata = 0x0}}}, static staticMetaObject = {d = {superdata = 0x7f2d97111200 <QGuiApplication::staticMetaObject>, stringdata = 0x7f2d96642720 <qt_meta_stringdata_QApplication>, data = 0x7f2d966425a0 <qt_meta_data_QApplication>, static_metacall = 0x7f2d962d3530 <QApplication::qt_static_metacall(QObject*, QMetaObject::Call, int, void**)>, relatedMetaObjects = 0x0, extradata = 0x0}}}
        fontDataBase = {static staticMetaObject = {d = {superdata = 0x0, stringdata = 0x7f2d96e8c7e0 <qt_meta_stringdata_QFontDatabase>, data = 0x7f2d96e8c640 <qt_meta_data_QFontDatabase>, static_metacall = 0x0, relatedMetaObjects = 0x0, extradata = 0x0}}, d = 0x7f2d97121780 <(anonymous namespace)::Q_QGS_privateDb::innerFunction()::holder>}
        currentFamily = {static null = {<No data fields>}, d = 0x55a0234520c0}
        isSubScaleable = true
        isCurrentScaleable = true
        subFamily = {static null = {<No data fields>}, d = 0x55a0234520c0}
        iResultCode = 1
#35 0x00007f2da36211c1 in __libc_start_main (main=0x55a021f6c7b0 <main(int, char**, char**)>, argc=1, argv=0x7ffc10d9b4d8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffc10d9b4c8) at ../csu/libc-start.c:308
        result = <optimized out>
        unwind_buf = {cancel_jmp_buf = {{jmp_buf = {0, 7313289449763357345, 94146252949744, 140720591189200, 0, 0, 3586664500010533537, 3487196971051238049}, mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x7ffc10d9b4e8, 0x7f2da402c150}, data = {prev = 0x0, cleanup = 0x0, canceltype = 282703080}}}
        not_first_call = <optimized out>
#36 0x000055a021f6c91a in _start ()
No symbol table info available.
}}}
Regards,
--
Cristian"	Cristian
19083	Virtualbox Crashes after waking from Sleep macOS High Sierra	VirtualBox 6.0.14	2019-11-13T19:54:25Z	2019-11-14T01:17:15Z	2019-11-14T01:17:15Z	"I have an early 2011 15"" MacBook Pro running High Sierra 10.13.6. Virtualbox 6.0.14 is installed and used to run  an Ubuntu Desktop virtual machine.

When waking my computer from sleep, the virtual machine crashes within seconds. At the next occurrence, I'll attach crash report files. I suspect the issue is related to https://www.virtualbox.org/ticket/11425 https://www.virtualbox.org/ticket/11444 and maybe others.

The other tickets mention a change in networking being the cause of the crash. I.e., the computer sleeps on one network and wakes on another. I'll monitor for that and update with further findings. I'm at a university with four different networks and multiple gateway devices for each network. If networking is the cause of these crashes, it may be related to different gateway devices since each wifi network has multiple access points but the same network name."	www139
20385	VirtualBox crashes by accessing 0xFFFFFFFFFFFFFFFF when USB dongle is unplugged/plugged.	VirtualBox 6.1.22	2021-06-03T04:19:48Z	2021-06-03T04:29:34Z	2021-06-03T04:29:34Z	"I am using virtualbox 6.1.22: 6.1.22 r144080 (Qt5.6.2) to be exact.
Host is Windows 10 Pro 64-bit., 20H2, OS build is 19042.985
Guest is Debian GNU/Linux, 5.10.0-4-amd64 

I have a USB Wi-Fi dongle NEC Aterm WL300NU-AG adaptor.
This works fine under Windows 10.

I tried to use this dongle from within linux to test my Wi-Fi devices at home against fragattacks (recently found Wi-Fi vulnerability).
So I removed the driver under Windows 10 for this USB. 
(It is plugged and no messing from Windoes 10 itself without the driver, I suppose.)
I intend to use the dongle via the native linux driver.

Under guest linux, I could somehow make the dongle recognized initially,
and eventually was able to assign IP address to it (manually, not by DHCP) and ping the interface address from other PCs via Wi-Fi. 
So experimentally it works, but the device went off-line unexpectedly.
The driver seems to have a known issue.
In order to reset the device, I tried unplugging and plugging it a few times. 
Then VBox crashed saying it accessed 0xFFFFFFFFFFFFFFFF address. 
(Actually I did this a lot initially, but at that time VBox did not crash.)

Alright, I saved a log. (The experiment took a couple of hours).

Now, I rebooted the guest linux by restarting VBox and see if I can continue testing the dongle. Nope.
The device was not visible from within guest linux using lsusb anymore(?!).
So I tried unplugging and unplugging only a couple of times when I get the same address violation and VBox crashed. This time I got the capture on the screen to show the address. 

I think there is a problem with USB handling.
I am attaching the first log (crash that occurred after a couple of hours testing. Actually, it was at the tail end of a very long session.)
and the second log along with the screen dump.

"	ci-zephyurus
13720	Virtualbox Crashes in r600_dri.so Mesa Graphics Driver When Running Ubuntu Guest With Guest Additions Installed	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
17172	VirtualBox crashes on adding new disk to VM	VirtualBox 5.1.30	2017-10-17T10:45:27Z	2018-01-25T06:36:08Z	2018-01-25T06:36:08Z	"I upgraded from VirtualBox 5.1.22 to 5.1.28 on my workstation (Windows 7 64-bit), and starting then, when I open the dialog for adding a disk to a VM, the dialog box opens, and before I can click anything, VirtualBox crashes.

I tried upgrading to 5.1.30, but it still crashes.

A full dump from 5.1.30 can be found at https://www.dropbox.com/s/mk59axufq9c7ijo/VirtualBox.exe.9068.dmp?dl=1 (since I think 130MB is probably too large to attach to a report).

The relevant Event Viewer entry says:
{{{
Faulting application name: VirtualBox.exe, version: 5.1.30.18389, time stamp: 0x59e48079
Faulting module name: Qt5GuiVBox.dll, version: 5.6.2.0, time stamp: 0x58e261e1
Exception code: 0xc0000005
Fault offset: 0x0000000000241bf4
Faulting process id: 0x236c
Faulting application start time: 0x01d34755ff5ce0f8
Faulting application path: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
Faulting module path: C:\Program Files\Oracle\VirtualBox\Qt5GuiVBox.dll
Report Id: 6baa816b-b349-11e7-be2c-005056c00008
}}}
"	rincebrain
20643	Virtualbox crashes on install of Win11	VirtualBox 6.1.28	2021-10-27T12:00:20Z	2021-10-27T12:00:20Z	2021-10-27T12:00:20Z	win11-DVDs starts normaly, copy his files to the disk and after an reboot, the vm crashes. see attached vm-log.	tomec5189
20900	VirtualBox crashes on startup: Completely failed to instantiate CLSID_VirtualBox: REGDB_E_CLASSNOTREG.	VirtualBox 6.1.32	2022-04-14T06:08:29Z	2022-04-14T06:08:29Z	2022-04-14T06:08:29Z	"When I start VirtualBox it crashes immediate.
Message is:
Het is niet gelukt het VirtualBox COM-object te verkrijgen.
Het programma wordt nu afgesloten.

Completely failed to instantiate CLSID_VirtualBox: REGDB_E_CLASSNOTREG.
Resultaatcode: REGDB_E_CLASSNOTREG (0x80040154)
Component: VirtualBoxClientWrap
Interface: IVirtualBoxClient {d2937a8e-cb8d-4382-90ba-b7da78a74573}

Un- and reinstalled VB, but still same problem.
I added a bugreport file

"	A3aan
18090	Virtualbox crashes on taking a snapshot	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
16272	VirtualBox crashes out when attempting to boot Windows Me	VirtualBox 5.1.10	2016-12-06T23:03:07Z	2016-12-23T04:53:07Z	2016-12-23T04:53:07Z	"When attempting to use Windows Me on one of my machines, VirtualBox crashes out with the message (from Windows host):

VirtualBox.exe - Application Error
The instruction at 0x758BA614 referenced memory at 0x000C000C. The memory could not be written.
Click on OK to terminate the program
Click on CANCEL to debug the program

The result is quite predictable. It happens when I attempt to boot a Windows Me floppy. I can use a Windows 95 floppy to get the VM started, and so install Me from source files, but the resulting hard disk crashes out with the same error.

I’m using VirtualBox 5.1.10 in Windows 10 on an Acer Extensa 5635Z laptop, with a T4200 processor (32-bit, no VT-x) and 2Mb RAM.
The problem does not happen on my other machine, which has a Core i5 (2500) processor amd 16Gb RAM.

I have managed to pin down the problem on the floppy to the disk boot sector, and the particular block of 54 bytes starting at offset 0x8D.
"	dlharper
20742	VirtualBox crashes when restoring from saved state	VirtualBox 6.1.30	2021-12-22T20:13:18Z	2021-12-22T20:15:48Z	2021-12-22T20:15:48Z	"... then hangs when attempted to stop the VM.

"	TomerB
14208	Virtualbox crashes when undocking	VirtualBox 4.3.28	2015-06-17T10:00:07Z	2016-11-11T10:23:05Z	2016-11-11T10:23:05Z	"Hi,

I am using a docking station and most of the time (I would say 80%) virtual box crashes when I undock.

I am using VB version 4.3.28 r100309 under windows 7 enterprise SP1.

After having investigated a little bit this seems to happen when 2D acceleration is enabled (never tried with 3D) 

I attached the logs in case it can help to investigate."	thedavix
20524	VirtualBox crashes with FreeBSD guest	VirtualBox 6.1.24	2021-08-25T12:50:16Z	2021-09-06T20:17:55Z	2021-09-06T20:17:55Z	See attached log.	DeGarden
20107	VirtualBox crashes with hardened memory allocator Hardened Malloc on the host	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
20203	VirtualBox crashing	VirtualBox 6.1.18	2021-02-18T16:34:22Z	2021-02-18T16:34:22Z	2021-02-18T16:34:22Z	"When I start VistualBox, I receive the error:

VirtualBox - Error In supR3HardNtChildScrewUpPebForInitialImageEvents
NtWriteVirtualMemory/Peb failed: 0xc0000022 (rc=-1073741790)
Please try reinstalling VirtualBox. where: supR3HardNtChildScrewUpPebForInitialImageEvents
what:  5
Unknown Status -1073741790 (0xc0000022) (-1073741790) - Unknown Status -1073741790 (0xc0000022)

It might be a conflict with Avecto Defendpoint"	sphag
20354	VirtualBox crashing on Big Sur 11.3.1	VirtualBox 6.1.22	2021-05-10T03:18:34Z	2021-05-26T18:29:39Z	2021-05-26T18:29:39Z	"Greetings VirtualBox team.

I just recently applied the latest apple patch to my macbook pro.
The OS version I am running is Big Sur 11.3.1 and after that version was installed, I am unable to run my windows 10 VM.

The error I am getting is the following:

Kernel driver not installed (rc=-1908)
Make sure the kernel module has been loaded successfully.

where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT. 



VirtualBox version: 6.1.22

Any pointers on how to fix this issue would be highly appreciated.
Best."	QuattroXL
4661	VirtualBox creates folder in /Volumes/ directory when disk with virtual machines is not present	VirtualBox 3.0.2	2009-07-31T17:58:59Z	2009-07-31T17:58:59Z	2009-07-31T17:58:59Z	"== Steps to reproduce problem under Mac OS X ==

 1. Connect external hard drive
 1. Specify that VirtualBox should use this drive as Default Hard Disk and Default Machine folder (in my case ""/Volumes/Hosomaki/VirtualBox/HardDisks"", a volume called ""Hosomaki"")
 1. Create virtual machine A on external drive
 1. Shut down VirtualBox and disconnect/umnount external drive
 1. Start up VirtualBox. Machine A is unavailable, as expected.
 1. Create new virtual machine B. This is where VirtualBox fails and creates the folder called ""/Volumes/Hosomaki/"" and subdirectories, as they do not exist. (Optionally install and set up machine B). Exit VirtualBox
 1. Reconnect external drive. Mac OS X fails to mount disk at proper mount point since VirtualBox has created a folder here. Mac OS X mounts the drive (in my case) as /Volumes/Hosomaki 1/
 1. Start VirtualBox. Machine A is now permanently unavailable with the following error message:[[BR]]

{{{
Assertion failed at '/Users/vbox/tinderbox/3.0-mac-rel/src/VBox/Main/MachineImpl.cpp' (5034) in nsresult Machine::loadSettings(bool).
Unexpected exception 'N3xml11EInvalidArgE' (In 'xml::File::File(RTFILE, const char*)', '/Users/vbox/tinderbox/3.0-mac-rel/src/VBox/Main/xml/xml.cpp' at #207).
Please contact the product vendor!.
Result Code: 
NS_ERROR_FAILURE (0x80004005)
Component: 
VirtualBox
Interface: 
IVirtualBox {3f4ab53a-199b-4526-a91a-93ff62e456b8}
}}}

== Temporary fix ==

The problem is resolved by:

 1. Mounting the external drive. In Finder, navigate to /Volumes/ with Go -> ""Go to Folder..."".[[BR]]
 1. Move files from the folder with the same name as the disk to the corresponding folders on the disk.[[BR]]
 1. Delete the folder.[[BR]]
 1. Unmount and remount drive.[[BR]]
 1. Start VirtualBox. Enjoy.

== Resolution ==

VirtualBox should be modified so that it never creates folders directly under /Volumes/ on Mac OS X. If the path to the default disk and machines stores do not exist, VirtualBox should present an error message saying so.

VirtualBox should also be modified so that it presents a more human-readable error message when a machines configuration file is not found. The above included error message is very complicated versus for example ""VirtualBox could not find the machine at the specified location. It may have been moved or deleted. Would you like to try to locate the files yourself, or would you like VirtualBox to remove the virtual machine from the inventory?"" with options (Ignore, Delete Machine, Locate files)."	Wilhelm
20892	VirtualBox critical errors occur since VirtualBox 6.1.32	VirtualBox 6.1.32	2022-04-04T11:31:18Z	2022-04-04T11:31:18Z	2022-04-04T11:31:18Z	VirtualBox critical errors occur since 6.1.32 from both Windows and Linux guests on both Windows and Linux hosts. When a critical error occurs, VirtualBox displays a popup asking whether I want to ignore the error for debugging or stop the VM. I had to downgrade to 6.1.30 to keep my VMs safe from those errors.	a587730
19897	Virtualbox depends on deprecated pyhton version	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
13409	VirtualBox does not allow releasing media when a snapshot references it	VirtualBox 4.3.16	2014-09-16T15:20:02Z	2014-09-16T15:20:02Z	2014-09-16T15:20:02Z	"I have created a snapshot of a VM a while ago while it had the guest additions attached to it. Now I cannot get the old ISO virtual media removed. It should be possible for snapshots only reference certain VM settings and ""release"" others (such as unneeded virtual media).
"	rbu
16854	virtualbox does not build reproducibly	VirtualBox 5.1.22	2017-06-23T06:39:11Z	2017-12-10T21:40:47Z	2017-12-10T21:40:47Z	"meaning, it creates different results on every build.
See https://reproducible-builds.org/ why that matters.

This comes from multiple sources:

1. gzip needs to be called with -n (patch attached)

2. tar does not sort file lists by default (newer version have the --sort=name option but there are other solutions as well)

3. various .o files contain a 'VTG Object Header v1.7'
added in src/bldprogs/VBoxTpG.cpp:574
via src/VBox/Runtime/generic/RTUuidCreate-generic.cpp RTUuidCreate
via src/VBox/Runtime/common/rand/rand.cpp RTRandBytes

IMHO, it would be better to replace that with some digest over source files, so that it changes whenever one of the inputs changes, but remains constant across builds."	bmwiedemann2
18903	VirtualBox does not start when docked	VirtualBox 6.0.10	2019-09-04T10:16:31Z	2019-09-04T10:16:31Z	2019-09-04T10:16:31Z	"VirtualBox starts invisible when launched from a Windows 10 PC docked to a Thunderbolt 3 docking station. Disconnecting the docking cable (before or after launching VirtualBox) makes the app visible. The cable can then be reinserted, the app stays open and works OK.

Environment:
- Dell Precision 5530
- Dell Thunderbolt TB16 docking station
- Windows 10 Pro (1903)"	p2r
20430	VirtualBox does not uninstall correctly under Fedora 34 (dnf/PackageKit)	VirtualBox 6.1.22	2021-06-25T18:15:39Z	2021-06-25T18:15:39Z	2021-06-25T18:15:39Z	"When installing VirtualBox from within the PackageKit software library under Fedora 34 and try to uninstall it again, dnf keeps listing the following package marked as dependency that will be removed (but isn´t):

kmod-VirtualBox-5.12.9-300.fc34.x86_64"	AnonYmous
13408	VirtualBox does not warn that Extension Pack is out of date	VirtualBox 4.3.16	2014-09-16T15:16:59Z	2014-09-18T12:37:46Z	2014-09-18T12:37:46Z	"VirtualBox is upgraded by my system's package management, while the extension pack needs to be downloaded manually. While that makes perfect sense, VirtualBox should really check that versions for these packages are the same if it needs this constraint to work flawlessly.

I only noticed I had an outdated extension pack since I was getting random machine aborts and found several forum entries with this solution.
"	rbu
19366	virtualbox does not work	VirtualBox 6.1.4	2020-03-01T12:59:02Z	2020-03-01T12:59:02Z	2020-03-01T12:59:02Z	"OS: Astra Linux

The virtual machine '1' has terminated unexpectedly during startup with exit code 1 (0x1).

Код ошибки: NS_ERROR_FAILURE (0x80004005)
Компонент: MachineWrap
Интерфейс: IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}

"	Yuriy Davidenko
9842	virtualbox doesn't list USB device with zero vendor and product ID	VirtualBox 4.1.4	2011-11-01T22:13:02Z	2011-11-05T00:39:10Z	2011-11-05T00:39:10Z	"[174272.347309] usb 2-1.2: new high speed USB device number 23 using ehci_hcd
[174272.425986] usb 2-1.2: New USB device found, idVendor=0000, idProduct=0000
[174272.425993] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[174272.425998] usb 2-1.2: Product: USB
[174272.426000] usb 2-1.2: Manufacturer: SMI Corporation
[174272.426004] usb 2-1.2: SerialNumber: AA6270950J5000000873


The device is a USB stick. I unmount it on the host (Linux), and would like to use it inside the VM. However, neither before nor after unmounting it, the virtualbox GUI doesn't want to show it in the list of USB devices.


I admit that a zero vendor and product Id is somewhat weired. However, the USB drive works just fine."	Sven
18703	VirtualBox doesn't record the video/audio on FreeBSD: the .webm file isn't saved	VirtualBox 6.0.8	2019-06-12T05:57:58Z	2019-06-12T05:57:58Z	2019-06-12T05:57:58Z	The user can enable it, the rolling icon is displayed, but the .webm file is never saved. It just isn't there.	yurivict1
15442	Virtualbox doesn't refresh any window, unless you resize it. Can't use any vm at all.	VirtualBox 5.0.20	2016-05-24T11:01:19Z	2016-05-24T16:35:03Z	2016-05-24T16:35:03Z	After installing 5.0.18, because 5.0.20 would give a critical error while installing. I tried to load my vm into virtualbox, however, nothing in virtualbox seem to refresh, so when i click on the map to import my vm, it doesn't refresh, i have to resize the window in order to refresh. When i run the vm i get a black screen, while in the preview view of virtual box i see that it works. (using windows 10, virtualization is enabled in bios, 16gb ram, 980m GT video card, should work)	TheCodeKing
9983	Virtualbox doesn't start on Windows 7 x64	VirtualBox 4.1.6	2011-12-02T14:26:12Z	2016-02-13T16:48:29Z	2016-02-13T16:48:29Z	"Hello,

If I start VirtualBox GUI and launch Virtual Machine after restart it starts OK, but when I close the virtual machine and VirtualBox GUI. It I try to start VirtualBox GUI to launch some virtual machine, process starts, but no GUI shows. If I look at task manager the process VirtualBox and VBoxSVC are running.

After reading some info on site I added two environment variables VBOX_GUI_DBG_AUTO_SHOW=true, VBOX_GUI_DBG_ENABLED=true, but that doesn't help, when I look in VBoxSVC.log.

I also tried running virtual machine by using VirtualBox --startvm --debug <machine name>, but it doesn't work as well. Same goes if i try to run from VBoxManage. When this happens VBoxManage hangs on every command I try to pass, like listing or starting virtual machines. Hangs like it sits on command line and nothing happens.

In all the cases started application VirtualBox/VBoxManage doesn't consume resources or processor time according to task manager.

I don't know if you use windows events, but there are no warning or error messages in windows event viewer.

I tried downgrading to versions 4.1.4, 4.1.2, 4.1.0. While downgrading I uninstall VirtualBox from ""Programs and Features"" then install the older version. In all installations I also install VirtualBox Extension Packs for the corresponding version I am installing.

I am attaching two VBoxSVC.logs -
First is on hanged VirtualBox.
Second is on last started guest - Which is Windows 2003 R2 server."	Philip Bonev
17147	VirtualBox doesn't work and can't finish reinstall	VirtualBox 5.1.28	2017-10-09T03:26:29Z	2017-10-09T08:52:07Z	2017-10-09T08:52:07Z	"After I upgrade my macbook pro(2015mid) to High Sierra, the virtualbox does not work any more. When i start a vm, it alarted ""Kernel driver not installed (rc=-1908)"". And when I reinstall virtualbox with pkg, (with or without VirtualBox_Uninstall.tool), the progress failed near finish. install log in attach.
Reinstall High Sierra (without format disk) doesn't help.
No Button appare in Security & Privacy when installation failed.
I found some simular question in tickets and forum, but the solutions does not work at all..."	ply_xyz
17868	VirtualBox doesn't work and can't finish reinstall (but booting virtual box still works) (cant boot my vm)	VirtualBox 5.2.14	2018-07-14T11:58:34Z	2018-07-28T16:27:02Z	2018-07-28T16:27:02Z	"After I upgrade my macbook pro(2015mid) to High Sierra, the virtualbox does not work any more. When i start a vm, it alarted ""Kernel driver not installed (rc=-1908)"". And when I reinstall virtualbox with pkg, (with or without VirtualBox_Uninstall.tool), the progress failed near finish. install log in attach. Reinstall High Sierra (without format disk) doesn't help. No Button appare in Security & Privacy when installation failed. I found some simular question in tickets and forum, but the solutions does not work at all...

Now, when I load my VM and try to start it it says
Kernel driver not installed (rc=-1908)  Make sure the kernel module has been loaded successfully.  where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT

I have googled / loooked on the forums, but nothing is helping. I have tried nearly anything. Now I am not a huge computer wiz so I need some guidance...

"	Valor773
18833	Virtualbox doesn´t work with new Windows update	VirtualBox 6.0.10	2019-08-13T05:54:58Z	2019-08-17T06:26:54Z	2019-08-17T06:26:54Z	"I have updated my OS to the latest Windows 10 version, after that I can´t run open any virtual OS.

The virtual machine 'Pintura WinCC 7.3' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\Usuario\VirtualBox VMs\Pintura WinCC 7.3\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005) Component: MachineWrap Interface: IMachine {5047460a-265d-4538-b23e-ddba5fb84976} "	erjefe
17539	VirtualBox driver crashes when rebooting with kexec on Ubuntu 16.04	VirtualBox 5.2.6	2018-02-12T02:54:03Z	2018-02-12T11:33:03Z	2018-02-12T11:33:03Z	"Restarting into another kernel is faster with kexec. There's a crash when I try to reboot into another kernel with kexec. The problem (says the screenshot) is because VirtualBox.

The commands I issued were:

diwou@diwou-VirtualBox:~$ sudo kexec -l /boot/vmlinuz-`uname -r` --reuse-cmdline
[sudo] password for diwou:
diwou@diwou-VirtualBox:~$ sudo systemctl kexec

Then I can see a crash on the GUI screen...

This bug was reported 5 years ago, I read it was marked as obsolete, but I think it's not fixed."	D1W0U
20362	VirtualBox Error using Ubuntu	VirtualBox 6.1.22	2021-05-13T05:25:59Z	2021-05-13T05:25:59Z	2021-05-13T05:25:59Z	"Version used 6.1.22
MAC OS X el capitan 10.11.6
EDD: Error 0c00 reading sector 1345901
EDD: Error 0c00 reading sector 1350645
EDD: Error 0c00 reading sector 1350646
EDD: Error 0c00 reading sector 1397132

Booting Kernel Failed: Invalid Argument"	Gustavo Flores Gutierrez
19268	VirtualBox Extension Pack 6.0.16 installation failure	VirtualBox 6.0.16	2020-01-26T00:58:10Z	2020-01-26T00:58:10Z	2020-01-26T00:58:10Z	"the posted extension pack fails to install due to a down rev driver.

Incompatible library version: VBoxPuelMain.dylib requires version 6.0.16 or later, but VBoxVMM.dylib provides version 6.0.15."	BFRG
17310	virtualbox extension pack accept-license issue	VirtualBox 5.2.0	2017-11-24T19:26:28Z	2017-11-24T20:36:15Z	2017-11-24T20:36:15Z	"Hello, I want to point out a misbehave of the extension pack installer.
You recently added the accept-license flag, to avoid issues when it is installed in batch mode.

Unfortunately, batch mode means no console available, and in case the accept-license checksum is wrong, you just point the license to the user, expecting it to manually press ""yes"".

This is really submoptimal, because it breaks automatic installations (e.g. with apt), when the license checksum changes.
Maybe, instead of printing the license, would be really better to exit with an error code, to make the user aware of the issue, or maybe add a new ""--exit-failure"" flag, for people who install automatically the extension pack via scripts."	LocutusOfBorg
13407	VirtualBox Extension pack fails to install due to missing privileges	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
10771	VirtualBox Extension Pack installation failed exit code 128 E_FAIL (0x80004005)	VirtualBox 4.1.18	2012-07-19T09:57:35Z	2021-06-19T14:31:42Z	2021-06-19T14:31:42Z	"Problem happens in a fresh install VirtualBox 4.1.8-75467 on host Microsoft Windows Server 2003 Standard R2 with Service Pack 2 64-bit with No antivirus installed.

Failed to install the Extension Pack 

The installer failed with exit code 128: .

Result Code: E_FAIL (0x80004005)
Component: ExtPackManager
Interface: IExtPackManager {3295e6ce-b051-47b2-9514-2c588bfe7554}


VirtualBox (XP)COM Server 4.1.18 r78361 win.amd64 (Jun  5 2012 15:58:59) release log
00:00:00.031 main     Log opened 2012-07-18T17:03:02.358332400Z
00:00:00.031 main     OS Product: Windows 2003
00:00:00.031 main     OS Release: 5.2.3790
00:00:00.031 main     Executable: C:\Program Files\Oracle\VirtualBox\VBoxSVC.exe
00:00:00.031 main     Process ID: 2236
00:00:00.031 main     Package type: WINDOWS_64BITS_GENERIC
00:00:01.063          VDInit finished
00:00:28.234 ExtPackInst ExtPack: Executing 'C:\Program Files\Oracle\VirtualBox/VBoxExtPackHelperApp.exe' '--display-info-hack' 'hwnd=0x210122''install' '--base-dir' 'C:\Program Files\Oracle\VirtualBox/ExtensionPacks' '--cert-dir' 'C:\Program Files\Oracle\VirtualBox/ExtPackCertificates' '--name' 'Oracle VM VirtualBox Extension Pack' '--tarball' 'D:/Software/Virtualbox/Oracle_VM_VirtualBox_Extension_Pack-4.1.18-78361.vbox-extpack' '--sha-256' '1c8cf8d67d9adf75fd02d529c03ee2f960ec4be08970fd8030ba7912ef1e3198'
00:00:28.234 ExtPackInst ExtPack: enmReason=1 iStatus=128 stderr=''
00:00:28.234 ExtPackInst ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={3295e6ce-b051-47b2-9514-2c588bfe7554} aComponent={ExtPackManager} aText={The installer failed with exit code 128: }, preserve=false
00:00:45.656 Watcher  ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={c28be65f-1a8f-43b4-81f1-eb60cb516e66} aComponent={VirtualBox} aText={The object is not ready}, preserve=false


I made many test (all as user Administrator):

1. Uninstall program Oracle VM VirtualBox
2. Delete folder .VirtualBox in Documents and Settings/Administrator
3. Verify Oracle folder not exist anymore in Program Files
4. Install VirtualBox version X
5. Install the extension pack version X
6. Same messages error as above

This made for X = All available version 4 (4.1.4-74291, 4.1.6-74713, 4.1.8-75467, 4.1.10-76836, 4.1.12-77245, 4.1.14-77440, 4.1.16-78094, 4.1.18-78361). No one works fine.

Another problem I suppose related is that for every above Virtualbox version the command: ""vboxmanage extpack cleanup"" returns

VBoxManage.exe: error: The installer failed with exit code 128:
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ExtPackManager, interface IExtPackManager, callee IUnknown
Context: ""Cleanup()"" at line 1148 of file VBoxManageMisc.cpp
"	davipena
17629	Virtualbox failed on VM startup	VirtualBox 5.2.6	2018-03-20T01:40:46Z	2018-04-19T15:24:15Z	2018-04-19T15:24:15Z		Josh99
19967	VirtualBox fails to boot Ubuntu 20.10 beta ISO in EFI mode	VirtualBox 6.1.14	2020-10-14T09:22:04Z	2022-02-04T20:08:54Z	2022-02-04T20:08:54Z	VirtualBox fails to boot Ubuntu 20.10 beta ISO in EFI mode. Using BIOS mode, on the other hand, works fine. I am using the VirtualBox version from Oracle's repository.	Thomas Dreibholz
12958	Virtualbox fails to start in headless mode with 3d acceleration enabled.	VirtualBox 4.3.10	2014-04-18T00:47:53Z	2014-04-18T00:47:53Z	2014-04-18T00:47:53Z	Virtualbox fails with uninformative message when 3d acceleration is enabled and guest OS is started in headless mode using shift+Start.	berkovskyy
20158	"VirtualBox falsely claims that using hyperthreaded cores is an ""invalid setting"""	VirtualBox 6.1.18	2021-01-29T00:28:58Z	2021-08-12T10:30:59Z	2021-08-12T10:30:59Z	"Intel CPUs often have ''x'' physical cores and 2''x'' hyper-threaded cores. From the view of applications running on the bare metal OS, the system typically has 2''x'' cores.

If I am configuring a VM guest in VirtualBox, and on the '''System''' > '''Processor''' tab I select more than ''x'' cores for the '''Processor(s)''' slider, an `Invalid settings detected` notice appears on the bottom. Clicking on the adjacent icon reveals a terse warning that exceeding ''x'' cores is ""likely to degrade performance of your virtual machine"".

This seems false:

* Intel generally intends that you act as if your CPU has 2''x'' cores. With this, hyper-threading helps the chip increase performance.
* In [https://unix.stackexchange.com/a/325959], a person conducted a few raw-performance tests on VMs with ''x'' and 2''x'' cores. The finding was that giving the guest OS 2''x'' cores caused significant performance gains.

Unless there is convincing evidence that giving a guest OS more than ''x'' cores is harmful, then it should not be assumed that there is any benefit to limiting guest core use to ''x'' cores. The warning for exceeding ''x'' cores should go away, and the slider should not be themed red at the point where you exceed ''x''."	Aren Cambre
19477	Virtualbox fatal error while using DisplayLink	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
17782	"Virtualbox for Windows 5.2.12: ""Failed to aquire the Virtualbox COM object"""	VirtualBox 5.2.12	2018-05-21T23:46:51Z	2018-05-22T20:35:51Z	2018-05-22T20:35:51Z	"Hi,
I have been having this issue for multiple weeks, and I was hoping someone could help.
I understand that many people have had this issue, and I have tried almost every fix, repair, and etc. that I have the power to do.
"	MaxMega12
20433	Virtualbox freeze	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
18925	Virtualbox freeze all guest system (32, 64 bit, linux, windows, other)	VirtualBox 6.0.12	2019-09-12T13:06:01Z	1970-01-01T00:00:00Z	1970-01-01T00:00:00Z	"The Virtualbox freeze after running guest operating system.
"	agostonl119
21489	VirtualBox Freeze Issue	VirtualBox-7.0.6	2023-02-09T23:52:07Z	2023-02-09T23:52:07Z	2023-02-09T23:52:07Z	"Hi,

I'm trying to run Whonix in a VirtualBox on a USB stick with Kali Linux OS.

I need to run the gateway before I can run the actual version of Whonix. Once the gateway is running and I go to run the usable Whonix version, after loading a little, the entire OS freezes and crashes until Kali Linux is rebooted. 

Running the latest version of Kali and VirtualBox. "	johnphxa
11862	VirtualBox freezes on btrfs / add check for COW	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
17488	virtualbox freezing the my system linux mint 18.3	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
17449	Virtualbox general protection fault	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
19013	VirtualBox Graphical User Interface Version 6.0.12 r133076 (Qt5.6.2)	VirtualBox 6.0.12	2019-10-13T21:50:45Z	2019-10-16T03:40:36Z	2019-10-16T03:40:36Z	"I am using VirtualBox Graphical User Interface Version 6.0.12 r133076 (Qt5.6.2)  installed on windows 10 64 bit and my host oracle linux 6.6 x86_64.
here problem is view ( resizing windows is not working in full screen).

kindly ! provide me solution "	gaurav12
19761	VirtualBox guest OpenWrt OS crashed when using the nmap to scan the wireless network through the USB port	VirtualBox 6.1.10	2020-07-25T06:04:07Z	2020-07-31T02:05:45Z	2020-07-31T02:05:45Z	"Guest OpenWrt OS crashed with the following configuration and operation
Host is the Lenovo ThinkCentre M920t desktop PC, WIN 10 professional OS.
The VirtualBox v6.1.12 with extension pack 6.1.12 is installed. 
The Guest OS is Linux 64bit(OpenWrt Lede 17.01). Using the MediaTek USB wifi dongle MT7601U to act as a AP(AccessPoint). It works well, I can connct it by my mobile phone and surf the Internet without problem, but it will be crashed once I use the nmap(v7.31) to scan the wifi network. I have the exactly same configuration with my HP laptop and the sympton won't happen in it, don't why it's crashed with my Lenovo desktop PC."	MercyLin
19928	VirtualBox hangs on shutdown	VirtualBox 6.1.14	2020-09-30T08:43:51Z	2020-10-04T00:00:14Z	2020-10-04T00:00:14Z	"I am experiencing a similar problem as described in https://forums.virtualbox.org/viewtopic.php?f=8&t=19085

I found that topic while searching for ""End of Guest state at power off"", which is the last line of VBox.log of the machine I just shut down.

The cli reports the VM is still running and the GUI freezes when selecting this VM.

I notice the following processes running when this happens:
 1081 ?        00:00:00 iprt-VBoxWQueue
 1085 ?        00:00:00 iprt-VBoxTscThr
 3530 ?        00:00:49 VBoxXPCOMIPCD
 3536 ?        00:02:05 VBoxSVC
12694 ?        00:29:30 VBoxHeadless

The problem occurs in different versions of VirtualBox, at least 6.0 and 6.1.

I did not try yet to turn off VT-x/AMD-V acceleration, but will do after reboot.

I will save append the log in the current state."	NickGuus
16531	VirtualBox has issue With my Windows 10 Build 15046	VirtualBox 5.1.14	2017-03-03T09:13:41Z	2017-04-08T12:42:43Z	2017-04-08T12:42:43Z	"Hello

I have Windows 10 Build 15046 Installed in my Host, I also Installed VirtualBox. but When I started The Virtual Machine, It only show Windows 10 boot screen and VirtualBox BIOS initial screen, and It only Preview can Display Desktop, And the virtual machine window cannot display Windows 10 Guest desktop.

My Host: Windows 10 Build 15046

My Guest Windows 10 (1607)

Hope The issues will be resolved soon.

Thank you

-htjywf2008"	htjywf2008
19401	Virtualbox host Windows 10 - CRASH	VirtualBox 6.1.4	2020-03-14T09:25:50Z	2020-03-14T09:25:50Z	2020-03-14T09:25:50Z	"Virtualbox 6.1.4
Windows 10 Host
1) Open Virtualbox
2) Virtualbox is open but coming 6 popup error -> VBOX_E_FILE_ERROR (0x80BB0004)
3) I click ok 6 time
4) then i can see virtualbox manager and start one of my vm, but one vm (win7 32 bit) is inaccessible.
5) If i click on this vm machine, the result is appear of a lot of msgbox vith the same error described on step 2, and after a few seconds the virtualbox manager program closes unexpectedly.
"	elsabz
7187	VirtualBox huge log file harvesting disk	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
17872	virtualbox in text-only mode (for a better Accessibility of old guest systems, especially when using a Braille display on the host)	VirtualBox 5.2.16	2018-07-18T21:49:34Z	2018-07-18T21:49:34Z	2018-07-18T21:49:34Z	"Hi guys,

When setting up older (or text-only) guest operating systems like freedos or freebsd, it would be very helpful to have some slimline text-only frontend, which would even display the vm's bios, Efi or Boot Menu. 

When working with my Pc, I'm using a braille display <https://en.wikipedia.org/wiki/Refreshable_braille_display>. in Windows 10, The Braille display is driven by NVDA <http://www.nvda-project.org>. on Linux, it is driven by Brltty <https://brltty.app/index.html> and Orca <https://en.wikipedia.org/wiki/Orca_(assistive_technology)>. 

A text-based frontend for virtualbox would have some Advantages:

At first, it would be much much more accessible to install text-based operating systems like freedos or freebsd or older linux Distros. With such a frontend, it would even be possible to control the vm's Bios or the boot menu in an accessible way. 

In practice, I imagine an alternative frontend for Virtualbox which should be called like this:

vboxmanage startvm freedos --type textonly

During bootup, all messages should be written directly to the text console. If the Vm has to switch into a graphic mode, it can write something like ""1024x768 Graphics oe"" to the text console. 

I think a text-only frontend would close a very big gap in the Accessibility of virtualbox (especially when using a braille display).

greetings

Dave
"	dave090679
15774	VirtualBox incorrectly counts processors on AMD products	VirtualBox 5.1.2	2016-08-10T01:37:02Z	2017-09-24T05:21:17Z	2017-09-24T05:21:17Z	"VirtualBox incorrectly counts processors on AMD products.  I have an AMD CPU with 8 physical processors.  This processor has 8 full processor cores.  Evidently, VirtualBox assumes this processor is an Intel product with Hyper-Threading, but this assumption is not correct.
"	Kriston
13896	virtualbox installing rolling back in the end of the install	VirtualBox 4.3.22	2015-02-25T20:49:57Z	2015-02-25T20:49:57Z	2015-02-25T20:49:57Z	"I'm a new user and my device hadnt insall virtualbox before that time and when I try to install the program in the last of the installation i see next to status rolling back
I had tried the latest version 4.3.22 ( I had restart download for two time but the same proplem)
and the older last virson
and the beta 4.3.23
and every time I delete setupapi.*.log
I had windows 7 64bit 
I read about msi log I dont know where I found it"	mrvmv
14230	VirtualBox ISession get_Console returns S_OK but IConsole ptr is NULL	VirtualBox 4.3.28	2015-06-29T15:52:54Z	2015-06-29T15:52:54Z	2015-06-29T15:52:54Z	"Hi,

I am running into a strange thing here. My (pseudo) code (see below) works fine on Windows 7 SP1 / 64bit with 64bit VirtualBox and 64bit app binary.
But when I compile the stuff not as x64 but Win32 (32bit binary on SysWOW64), the app crashes because get_Session returns S_OK but the delivered pointer IConsole * is NULL !!!
Is this a bug or is it not possible to run a Win32 binary on Win7/64 with VirtualBox/64? I thought that it should be completely transparent using Microsoft COM?
Here is the pseudo code:

{{{
BSTR machineName = SysAllocString(L""VMName"");
IMachine *pMachine = NULL;
if (FAILED(pVBOX->FindMachine(machineName,&pMachine)))
{//do error stuff}
if (FAILED(pMachine->LockMachine(pVBOXSession,LockType_Write)))
{//do error stuff}
pMachine->Release, pMachine = NULL;
if (FAILED(pVBOXSession->get_Machine(&pMachine))) // get mutable one
{// do error stuff}
IConsole *pConsole = NULL;
if (FAILED(pVBOXSession->get_Console(&pConsole)))
{// do error stuff }
}}}

[...]
At this position, pConsole is NULL on Win32 (SysWOW64) and not NULL on Win64 (x64).
Any ideas?

Thank you.




"	vboxcomapijunkie
13574	VirtualBox keeps resizing the guest to 1 screen	VirtualBox 4.3.18	2014-10-30T11:15:06Z	2014-12-18T19:39:20Z	2014-12-18T19:39:20Z	"Since updating to VB 4.3.16 and 4.3.18 from 4.3.12 it is impossible to resize the guest operating system to more than 1 screen.

I run Windows 7 and I have 3 screens and I have enabled Auto-Resize Guest Display.

It is possible to drag the bottom right corner of the guest window, but as soon as it is released there are some flickering and the window is resized to be as width as 1 screen.
The guest OS display is internally of the size I resized to, but there is a horizontal scrollbar.

The guest OS is Fedora 19 fully updated.

Guest OS additions are installed.

As soon as I downgradeto 4.3.12 the problem goes away and it is 100% reproducible with 4.3.16 and 4.3.18. I have never tried 4.3.14.

I have a NVIDIA NVS 310 card.

Some other users have reported it here

https://forums.virtualbox.org/viewtopic.php?f=6&t=63634"	mariolino
14614	Virtualbox kills keyboard when running on Windows 10	VirtualBox 5.0.4	2015-09-21T04:56:50Z	2015-09-29T17:11:19Z	2015-09-29T17:11:19Z	"OS: Windows 10 build 10240
Virtualbox version: 5.0.4-102546 and 5.0.5-102676

Description:

VirtualBox kills my keyboard every time it is run. Note that this happens when VirtualBox is running for some time, even without starting any VM. 

I fresh installed VirtualBox in my new Windows 10 machine (it's a newly built PC with no PS/2 port on the motherboard, so I am using a USB keyboard). Since it's a fresh install the first thing I do is to create a new VM. The keyboard suddenly died out when I attempt to specify where to store the VM files. All LED went off, and pressing the NumLock/CapsLock/ScrollLock keys won't trigger any LED back on. At first I thought it may be the cable of my keyboard got loose. So I checked but found no problem. Unplugging and plugging the keyboard to the same or different USB ports didn't help. Windows even didn't play any sound that indicate a device is being plugged in/unplugged.

I was afraid that it is the motherboard having some issues, but luckily the keyboard came back when I reboot the machine. I tried several times and the result is still the same.

It seems that only the USB keyboard is affected. The mouse still works.

In my experience, keyboard dies after about 1-2 minutes of usage in the stable (5.0.4-102546) build. Using the latest test build (5.0.5-102676). keyboard dies out after about 10 minutes of usage.

I found one similar case in the forum [1]. The op is working on a laptop, while I am working on a desktop.

Not sure if related to the issue, my Windows 10 machine also runs VMWare workstation . 

[1] https://forums.virtualbox.org/viewtopic.php?f=6&t=70081"	cytam
13053	VirtualBox linked cloned machine (link lost when deleted)	VirtualBox 4.3.12	2014-05-22T07:49:57Z	2016-12-27T05:01:42Z	2016-12-27T05:01:42Z	"When a linked clone machine is created and deleted it loses the link because the virtual disk uuid is detached from the original machine and it doesn't have enough information in the .vbox xml file to reattach it to the original machine.

solutions that could be deployed:
you could implement a new button in properties menu to ""move a machine from one path to another"". So when we want to move cloned linked machine, we wouldn't have to delete it, move it to the new path and then open the .vbox file to add it again to the virtualbox machines list.


ERROR MESSAGE:
======================================================================
Failed to open virtual machine located in C:/BACKUP/VIRTUAL_MACHINES_1/VirtualBox/win81x32LinkedClone1/win81x32LinkedClone1.vbox.

Could not find an open hard disk with UUID {eaa88706-e2ce-4170-95a5-dbdc78e297fd}.

Result Code: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)
Component: VirtualBox
Interface: IVirtualBox {fafa4e17-1ee2-4905-a10e-fe7c18bf5554}
======================================================================

"	willianmai
19393	Virtualbox Linux Guest crashes when opening Eclipse IDE	VirtualBox 6.1.4	2020-03-11T07:57:30Z	2020-03-11T08:18:17Z	2020-03-11T08:18:17Z	"Hi,

if I open the Eclipse IDE under my Linux guest, then the guest crashes.

The guest is ArchLinux 64bit and the host Windows 10. I use the official Virtualbox guest extensions and kernel modules. The Linux Kernel of the guest is 5.5.8

I will attach the Logfiles"	JMeier12
20013	VirtualBox locks up when host resumes from sleep	VirtualBox 6.1.16	2020-11-02T11:36:16Z	2020-11-02T11:36:16Z	2020-11-02T11:36:16Z	"I have had an issue with VirtualBox locking up on Host resume from sleep for years, but it seemed to be a bit random. However I did notice that in v6.1.14 it hardly occurred any more, perhaps once a fortnight.

Once I upgraded to v6.1.16, VirtualBox was locking up almost every time the Host resumed from sleep.

After a few days of these lockups I decided to revert to v6.1.14 (29th October) and since then I've not had a single lock up and I've probably resumed the Host from sleep a dozen times.

I've attached the logs from v6.1.16 but from my quick look, I don't think anything gets logged after the sleep as it locks up before that can happen.

The Host is Windows 10 Home 1909 Build 18363.1139
The Guest is Windows 10 Pro 1909 Build 18363.1139"	Iain Waddell
19204	Virtualbox Manager Crashes when moved to 2nd monitor on Linux Host.	VirtualBox 6.1.0	2020-01-06T23:12:16Z	2020-01-14T17:15:01Z	2020-01-14T17:15:01Z	"Running Ubuntu 16.04 (fully patched), and when I attempt to move the window for the Virtualbox Manager to a second physical screen, the Manager crashes with various segfaults.  The Manager does NOT crash if moved to a second desktop workspace on the host (and the VM starts just fine).  The Manager also does NOT crash if I simply mirror the primary display (which I'll have to use for my current workaround.

Basically, no matter what I attempt, when I move any Virtualbox (6.1.0 and 6.0.14) window to a different physical screen, there is a segfault.  Some dmesg output is pasted here:

{{{
[ 2668.255651] VirtualBox[21052]: segfault at 7ffd96641fe8 ip 00007fc21b9932b6 sp 00007ffd96641ff0 error 6 in libQt5GuiVBox.so.5[7fc21b86b000+5f3000]
[ 2673.511188] device vboxnet0 left promiscuous mode
[ 2673.538944] vboxnetflt: 0 out of 69 packets were not sent (directed to host)
[ 2949.375093] vboxdrv: 0000000000000000 VMMR0.r0
[ 2949.584145] VBoxNetFlt: attached to 'vboxnet0' / 0a:00:27:00:00:00
[ 2949.584944] device vboxnet0 entered promiscuous mode
[ 2949.687535] vboxdrv: 0000000000000000 VBoxDDR0.r0
[ 2949.829857] vboxdrv: 0000000000000000 VBoxEhciR0.r0
[ 3447.396061] VirtualBoxVM[22573]: segfault at 7ffe8e46fff8 ip 00007ff3849896f2 sp 00007ffe8e470000 error 6 in libQt5WidgetsVBox.so.5[7ff3846e7000+676000]
[ 3462.001978] vboxdrv: 0000000000000000 VBoxDDR0.r0
[ 3462.149045] vboxdrv: 0000000000000000 VBoxEhciR0.r0
[ 3499.044449] VirtualBoxVM[23316]: segfault at 7fff4881fff0 ip 00007f9c9fa39c29 sp 00007fff4881ffc0 error 6 in ld-2.23.so[7f9c9fa26000+26000]
}}}

I attempted to attach a CoreDump, but the CoreDump was ~100 MB, and the max upload was ~512KB.  I've never created a CoreDump before, so I may have done it incorrectly and would appreciate clarification.
"	mop
18804	VirtualBox Manager terminating without notice after start	VirtualBox 6.0.10	2019-08-02T08:58:57Z	2019-08-02T08:58:57Z	2019-08-02T08:58:57Z	When I start the VirtualBox Manager, it briefly shows the selector window, then terminates without any notice. I have a single Linux VM in the list.	sgiesecke
15198	Virtualbox misses keypress isuued just after capture	VirtualBox 5.0.14	2016-03-03T19:22:51Z	2016-03-03T19:26:11Z	2016-03-03T19:26:11Z	"Whenever I switch to my guest, either using Alt+tab or just clicking with the mouse inside the guest window, the first and sometimes second keypresses are lost.
This only happens if the keypresses are sent very fast after switching
To reproduce:
Open notepad on guest
Place the mouse cursor inside the notepad window
Host should have focus
Click inside notepad and just as you do that, press 1 2 3 on the keyboard
If you're fast enough, 1 is lost 80-90 % of the time and 2 is lost 50 % of the time
This also happens if you alt+tab from host to the guest

Tested on two different hosts"	noir04
17902	VirtualBox non funziona	VirtualBox 5.2.16	2018-07-28T16:23:31Z	2018-07-28T16:23:31Z	2018-07-28T16:23:31Z	"ho effettuato una pulizia con CCleaner e non riesco a fare ripartire VirtualBox.
Il log che esce è:
VirtualBox COM Server 5.2.16 r123759 win.amd64 (Jul 16 2018 15:52:14) release log
00:00:00.015619 main     Log opened 2018-07-26T11:32:49.851605900Z
00:00:00.015619 main     Build Type: release
00:00:00.015619 main     OS Product: Windows 10
00:00:00.015619 main     OS Release: 10.0.17134
00:00:00.015619 main     OS Service Pack: 
00:00:00.031240 main     DMI Product Name: System Product Name
00:00:00.031240 main     DMI Product Version: System Version
00:00:00.031240 main     Host RAM: 4016MB (3.9GB) total, 1812MB available
00:00:00.031240 main     Executable: C:\Program Files\Oracle\VirtualBox\VBoxSVC.exe
00:00:00.031240 main     Process ID: 13232
00:00:00.031240 main     Package type: WINDOWS_64BITS_GENERIC
00:00:00.031240          VirtualBox: object creation starts
00:00:00.046862          Home directory: 'C:\Users\piero\.VirtualBox'
00:00:00.046862          Installed Drivers:
00:00:00.046862            C:\WINDOWS\system32\DRIVERS\VBoxNetLwf.sys (Version: 5.2.16.23759)
00:00:00.046862            C:\WINDOWS\system32\DRIVERS\VBoxUSBMon.sys (Version: 5.2.16.23759)
00:00:00.046862            C:\WINDOWS\system32\DRIVERS\VBoxDrv.sys (Version: 5.2.16.23759)
00:00:00.046862            C:\WINDOWS\System32\drivers\VBoxNetAdp6.sys (Version: 5.2.16.23759)
00:00:00.062483          Loading settings file ""C:\Users\piero\.VirtualBox\VirtualBox.xml"" with version ""1.12-windows""
00:00:00.062483          Getting USB descriptor failed with error 31
00:00:00.078104          USB: Unknown USB device detected (idVendor: 0x0a5c, idProduct: 0x21ec)
00:00:00.171832          HostDnsMonitor: old information
00:00:00.171832            no server entries
00:00:00.171832            no domain set
00:00:00.171832            no search string entries
00:00:00.171832          HostDnsMonitor: new information
00:00:00.171832            server 1: 192.168.1.1
00:00:00.171832            domain: station
00:00:00.171832            no search string entries
00:00:00.171832          HostDnsMonitorProxy::notify
00:00:00.203076          SUPR0QueryVTCaps -> VERR_VMX_MSR_ALL_VMX_DISABLED
00:00:00.250013          VD: VDInit finished with VINF_SUCCESS
00:00:00.250013          Loading settings file ""C:\Users\piero\VirtualBox VMs\Windows Xp\Windows Xp.vbox"" with version ""1.15-windows""
00:00:00.265565          VirtualBox: object created
00:00:01.653184          Saving settings file ""C:\Users\piero\.VirtualBox\VirtualBox.xml"" with version ""1.12-windows""
00:00:01.663208          Saving settings file ""C:\Users\piero\.VirtualBox\VirtualBox.xml"" with version ""1.12-windows""
00:00:05.471174          Load [C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\win.amd64\VBoxHostWebcam.DLL] rc VINF_SUCCESS
00:00:05.714537          ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={SessionMachine} aText={Saved screenshot data is not available (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=0
01:21:15.783203 USBPROXY Getting USB descriptor failed with error 31
02:59:48.161337 MainPower Host suspending: Paused 1 VMs
03:01:39.953430 MainPower Host resumed: Resumed 1 VMs
03:01:41.573588 dns-monitor HostDnsMonitor: old information
03:01:41.573588 dns-monitor   server 1: 192.168.1.1
03:01:41.573588 dns-monitor   domain: station
03:01:41.573588 dns-monitor   no search string entries
03:01:41.573588 dns-monitor HostDnsMonitor: new information
03:01:41.573588 dns-monitor   no server entries
03:01:41.573588 dns-monitor   no domain set
03:01:41.573588 dns-monitor   no search string entries
03:01:41.573588 dns-monitor HostDnsMonitorProxy::notify
03:02:05.331431 USBPROXY Getting USB descriptor failed with error 31
03:02:05.332406 USBPROXY USB: Unknown USB device detected (idVendor: 0x0a5c, idProduct: 0x21ec)
03:02:05.896003 dns-monitor HostDnsMonitor: old information
03:02:05.896003 dns-monitor   no server entries
03:02:05.896003 dns-monitor   no domain set

Ho provato anche a fare la riparazione reinstallando il programma ma non funziona ugualmente. 
Qualcuno mi può aiutare? Ringrazio. Piero"	Piero
16486	VirtualBox on macOS crashes when laptop suspends/resumes	VirtualBox 5.1.14	2017-02-15T18:19:43Z	2017-08-21T17:33:28Z	2017-08-21T17:33:28Z	"I have a Macbook Pro (2015 retina display, switchable graphics) running a Windows 10 guest that crashes frequently when the laptop decides to suspend. Usually this is associated with me unplugging external displays and power while the lid is closed. However, it can happen even without the external displays, and just the laptop itself going to sleep.

I have tried:

- Reducing virtual CPUs to 1 and RAM to 4096.
- Enabling and disabling switchable graphics
- 2D acceleration and no 2D acceleration
- VirtualBox 5.1.8 and 5.1.14 (guest additions always at the appropriate matching level)
- Two external displays, one external display, no external display

I cannot solve the problem, and the regular crashes are causing major interruptions. I can't always control when the laptop suspends, as the power cord might be bumped or I might have it with me during a meeting and long enough gap between usage results in sleep.

I have attached the logs and macOS problem report from both 5.1.8 and 5.1.14."	Jason Hagar
14449	"VirtualBox replaces the ""\"" to ""/"" in file names of disks on Linux"	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
19500	VirtualBox should now prohibit assigning all physical CPUs to a VM and/or fix VirtualBox CPU assignment manual		2020-04-16T13:00:32Z	2020-04-16T13:00:32Z	2020-04-16T13:00:32Z	"Quote VirtualBox manual https://www.virtualbox.org/manual/ch03.html#settings-processor

> You should not configure virtual machines to use more CPU cores than are available physically.

So I concluded ""i have 4 physical CPUs so let's assign 4 virtual CPUs to VM.

----

As I've learned today, VirtualBox forum moderators disagree.

Quote https://forums.virtualbox.org/viewtopic.php?f=7&t=77663#p362084

> You have 4 CPUs and you assign all of them to your guest. Expect turbulence and bumpy flight.

Quote https://forums.virtualbox.org/viewtopic.php?f=1&t=88864#p425929

> You should not assign all of them to the VM however - the host OS needs CPU time to run host apps, particularly VirtualBox!

----

Therefore, for example, if there are 4 physical CPUs, the maximum CPUs one can assign should be limited to 3.

In any case, please update VirtualBox manual accordingly. Or if these forums moderators are in fact wrong, please kindly point that out too.

----

Minor details if you agree with above:

Maybe you could allow the user to ignore that warning but I you will know best.

Please consider not breaking existing installations of VirtualBox with lets say 4 physical CPUs and 4 virtual CPUs assigned to VMs. Please either:

* leave it as is (user might notice one day looking into settings), or
* automatically reduce number of virtual CPUs to 3 (if that isn't considered intrusive)
* a popup that asks the user if that reduction should be applied before next start of VM (ugly?)
"	adrelanos
19323	"VirtualBox show me error when i click on ""Start"" button (it was working perfectly 3 month ago)"	VirtualBox 6.1.0	2020-02-19T22:31:09Z	2020-02-19T22:31:09Z	2020-02-19T22:31:09Z	"Hello, 
Could you help please ? 
Host system Macbook Pro + High sierra 
I tried to reinstall Virtualbox from scratch to reinstall a clean Windows 7(removed all settings files), but still have the same problem, VirtualBox return me this error when i try to click start button...
Thanks 
Ced

Code d'erreur : 
NS_ERROR_FAILURE (0x80004005)
Composant : 
MachineWrap
Interface : 
IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}
"	fced
19833	virtualbox showing : The VM session was aborted.   Result Code:  E_FAIL (0x80004005) Component:  SessionMachine Interface:  ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}		2020-08-26T06:27:01Z	2020-08-26T06:27:01Z	2020-08-26T06:27:01Z	The VM session was aborted	TGT
20219	VirtualBox starts up OK. Failed to open a session for the virtual machine. Result Code: E_FAIL (0x80004005) Component: MachineWrap Interface: IMachine.	VirtualBox 6.1.18	2021-02-22T17:07:19Z	2021-02-22T17:07:19Z	2021-02-22T17:07:19Z	"I am experiencing the same problem as #20191. VirtualBox starts up fine. Existing VM fails to start with same error as this ticket describes. Failed to open a session for the virtual machine C7.
I have attached the log file, in addition to pasting it below.

The virtual machine 'C7' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'D:\VirtualBox VMs\C7\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005) Component: MachineWrap Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}

From VboxHardening.log:

16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'combase.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'combase.dll' -> '\Device\HarddiskVolume3\Windows\System32\combase.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\combase.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\wdmaud.drv (Input=wdmaud.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d5b0000 'C:\windows\System32\wdmaud.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\MMDevAPI.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\MMDEVAPI.DLL (Input=MMDEVAPI.DLL, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb99190000 'C:\windows\System32\MMDEVAPI.DLL' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\wdmaud.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\wdmaud.drv (Input=wdmaud.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d5b0000 'C:\windows\System32\wdmaud.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\wdmaud.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\wdmaud.drv (Input=wdmaud.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d5b0000 'C:\windows\System32\wdmaud.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\wdmaud.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\wdmaud.drv (Input=wdmaud.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d5b0000 'C:\windows\System32\wdmaud.drv' 16e0.312c: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'msvcp_win.dll'. 16e0.312c: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #5 'rpcrt4.dll'. 16e0.312c: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #7 'oleaut32.dll'. 16e0.312c: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #29 'mmdevapi.dll'. 16e0.312c: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume3\Windows\System32\AudioSes.dll) 16e0.312c: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume3\Windows\System32\AudioSes.dll 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'mmdevapi.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'mmdevapi.dll' -> '\Device\HarddiskVolume3\Windows\System32\mmdevapi.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\MMDevAPI.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'oleaut32.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'oleaut32.dll' -> '\Device\HarddiskVolume3\Windows\System32\oleaut32.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\oleaut32.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'rpcrt4.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'rpcrt4.dll' -> '\Device\HarddiskVolume3\Windows\System32\rpcrt4.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\rpcrt4.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'msvcp_win.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'msvcp_win.dll' -> '\Device\HarddiskVolume3\Windows\System32\msvcp_win.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\msvcp_win.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\AUDIOSES.DLL (Input=AUDIOSES.DLL, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling] 16e0.312c: supR3HardenedScreenImage/NtCreateSection: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\AudioSes.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #12 'rpcrt4.dll'. 16e0.312c: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume3\Windows\System32\powrprof.dll) 16e0.312c: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume3\Windows\System32\powrprof.dll 16e0.312c: supR3HardenedDllNotificationCallback: load 00007ffba0030000 LB 0x0004b000 C:\windows\SYSTEM32\powrprof.dll [fFlags=0x0] 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\powrprof.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedDllNotificationCallback: load 00007ffb99220000 LB 0x00185000 C:\windows\System32\AUDIOSES.DLL [fFlags=0x0] 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\AudioSes.dll [lacks WinVerifyTrust] 16e0.312c: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume3\Windows\System32\umpdc.dll) 16e0.312c: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume3\Windows\System32\umpdc.dll 16e0.312c: supR3HardenedDllNotificationCallback: load 00007ffb9ffb0000 LB 0x00012000 C:\windows\SYSTEM32\UMPDC.dll [fFlags=0x0] 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\umpdc.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb99220000 'C:\windows\System32\AUDIOSES.DLL' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\wdmaud.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'rpcrt4.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'rpcrt4.dll' -> '\Device\HarddiskVolume3\Windows\System32\rpcrt4.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\rpcrt4.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\wdmaud.drv (Input=wdmaud.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d5b0000 'C:\windows\System32\wdmaud.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\wdmaud.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\wdmaud.drv (Input=wdmaud.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d5b0000 'C:\windows\System32\wdmaud.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\wdmaud.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d5b0000 'C:\windows\System32\wdmaud.drv' 16e0.312c: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'msvcrt.dll'. 16e0.312c: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #12 'mmdevapi.dll'. 16e0.312c: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #13 'msacm32.dll'. 16e0.312c: supHardenedWinVerifyImageByHandle: -> 22900 (\Device\HarddiskVolume3\Windows\System32\msacm32.drv) 16e0.312c: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume3\Windows\System32\msacm32.drv 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'msacm32.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'msacm32.dll' -> '\Device\HarddiskVolume3\Windows\System32\msacm32.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'msvcrt.dll'. 16e0.312c: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume3\Windows\System32\msacm32.dll) 16e0.312c: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume3\Windows\System32\msacm32.dll 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'mmdevapi.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'mmdevapi.dll' -> '\Device\HarddiskVolume3\Windows\System32\mmdevapi.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\MMDevAPI.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'msvcrt.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'msvcrt.dll' -> '\Device\HarddiskVolume3\Windows\System32\msvcrt.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\msvcrt.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'msvcrt.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'msvcrt.dll' -> '\Device\HarddiskVolume3\Windows\System32\msvcrt.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\msvcrt.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\msacm32.drv (Input=msacm32.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedScreenImage/NtCreateSection: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\msacm32.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedScreenImage/NtCreateSection: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\msacm32.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedDllNotificationCallback: load 00007ffb8d650000 LB 0x0001e000 C:\windows\SYSTEM32\MSACM32.dll [fFlags=0x0] 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\msacm32.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedDllNotificationCallback: load 00007ffb8d9c0000 LB 0x0000d000 C:\windows\System32\msacm32.drv [fFlags=0x0] 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\msacm32.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d9c0000 'C:\windows\System32\msacm32.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\msacm32.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\msacm32.drv (Input=msacm32.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d9c0000 'C:\windows\System32\msacm32.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\msacm32.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\msacm32.drv (Input=msacm32.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d9c0000 'C:\windows\System32\msacm32.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\msacm32.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\msacm32.drv (Input=msacm32.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d9c0000 'C:\windows\System32\msacm32.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\msacm32.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\msacm32.drv (Input=msacm32.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d9c0000 'C:\windows\System32\msacm32.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\msacm32.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\msacm32.drv (Input=msacm32.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d9c0000 'C:\windows\System32\msacm32.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\msacm32.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\msacm32.drv (Input=msacm32.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d9c0000 'C:\windows\System32\msacm32.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\msacm32.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d9c0000 'C:\windows\System32\msacm32.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\msacm32.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d9c0000 'C:\windows\System32\msacm32.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\msacm32.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d9c0000 'C:\windows\System32\msacm32.drv' 16e0.312c: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'msvcrt.dll'. 16e0.312c: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #1 'winmmbase.dll'. 16e0.312c: supHardenedWinVerifyImageByHandle: -> 22900 (\Device\HarddiskVolume3\Windows\System32\midimap.dll) 16e0.312c: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume3\Windows\System32\midimap.dll 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'winmmbase.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'winmmbase.dll' -> '\Device\HarddiskVolume3\Windows\System32\winmmbase.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\winmmbase.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'msvcrt.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'msvcrt.dll' -> '\Device\HarddiskVolume3\Windows\System32\msvcrt.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\msvcrt.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\midimap.dll (Input=midimap.dll, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedScreenImage/NtCreateSection: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\midimap.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedDllNotificationCallback: load 00007ffb8d640000 LB 0x0000b000 C:\windows\System32\midimap.dll [fFlags=0x0] 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\midimap.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d640000 'C:\windows\System32\midimap.dll' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\midimap.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\midimap.dll (Input=midimap.dll, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d640000 'C:\windows\System32\midimap.dll' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\midimap.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\midimap.dll (Input=midimap.dll, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d640000 'C:\windows\System32\midimap.dll' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\midimap.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\midimap.dll (Input=midimap.dll, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d640000 'C:\windows\System32\midimap.dll' 16e0.1aa0: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\MMDevAPI.dll [lacks WinVerifyTrust] 16e0.1aa0: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\MMDevApi.dll (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000002009:<flags> [calling] 16e0.1aa0: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb99190000 'C:\windows\System32\MMDevApi.dll' 11a8.438: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 109337 ms, the end);

I have tried some suggestions found using Google and sometimes they help, but next reboot or start of VirtualBox results in same bad behavior. I also have uninstalled VirtualBox 6.1.18 and re-installed. It sometimes seems to let the VM start up and other times the same error appears. Both the install of VirtualBox 6.1.18 and the startup of VirtualBox 6.1.18 were done as administrator. Anti-Virus Used is: EseT Nod32 14.0.22.0 Windows Info: OS Name Microsoft Windows 10 Pro Version 10.0.19041 Build 19041 Other OS Description Not Available OS Manufacturer Microsoft Corporation System Name DESKTOP-H70PDLJ System Manufacturer HP System Model HP EliteBook 855 G7 Notebook PC System Type x64-based PC System SKU 3E780AV Processor AMD Ryzen 7 PRO 4750U with Radeon Graphics, 1700 Mhz, 8 Core(s), 16 Logical Processor(s) BIOS Version/Date HP S77 Ver. 01.02.03, 11/27/2020 SMBIOS Version 3.2 Embedded Controller Version 7.44 BIOS Mode UEFI BaseBoard Manufacturer HP BaseBoard Product 8760 BaseBoard Version KBC Version 07.2C.00 Platform Role Mobile Secure Boot State On PCR7 Configuration Elevation Required to View Windows Directory C:\windows System Directory C:\windows\system32 Boot Device \Device\HarddiskVolume1 Locale United States Hardware Abstraction Layer Version = ""10.0.19041.488"" User Name DESKTOP-H70PDLJ\willh Time Zone Central Standard Time Installed Physical Memory (RAM) 32.0 GB Total Physical Memory 31.3 GB Available Physical Memory 27.9 GB Total Virtual Memory 36.1 GB Available Virtual Memory 32.6 GB Page File Space 4.75 GB Page File C:\pagefile.sys Kernel DMA Protection Off Virtualization-based security Not enabled Device Encryption Support Elevation Required to View Hyper-V - VM Monitor Mode Extensions Yes Hyper-V - Second Level Address Translation Extensions Yes

Hyper-V - Virtualization Enabled in Firmware Yes Hyper-V - Data Execution Protection Yes"	WillH
19578	VirtualBox startup failure under win10	VirtualBox 6.1.6	2020-05-13T01:38:27Z	2020-05-14T05:44:48Z	2020-05-14T05:44:48Z	"VirtualBox startup failure under win10

I have checked BIOS virtual settings
I have set Hyper-V off
I have stopped all Hyper-V services
"	oracle-lover
21401	VirtualBox stops operation. Log attached.	VirtualBox-7.0.4	2023-01-08T22:53:54Z	2023-01-08T22:53:54Z	2023-01-08T22:53:54Z	"Vbox 7.0.4 r154605
Host: Windows 10 Pro 64-bit
Guest: Debian GNU/Linux

While I was executiong a testing thunderbird mailing client, virtualbox stopped its execution.
The error pop up suggested I should post VBox.log (attached) and VBox.png (which  does not seem to exist).

I used to run this test without issue even under low-memory condition and so something is wrong with 7.0.4's error handling.

"	ci-zephyurus
19283	VirtualBox stuck zoomed in on Windows 10	VirtualBox 6.0.16	2020-01-31T20:37:42Z	2020-01-31T20:37:42Z	2020-01-31T20:37:42Z	"Hello, 
I am running virtual box through vagrant on Windows 10. I cannot perform many functions on VirtualBox that I need to for school and work projects because the screen is zoomed in and I can't click or see many of the things I need to. I have tried some of the recommended fixes mentioned online at stackexchange and others but none have worked. Please let me know what I can do to make this work.

Thank you!"	BallsMahoney
17150	VirtualBox triggers a kernel panic in macOS 10.13.1 public beta 1	VirtualBox 5.1.28	2017-10-09T18:27:55Z	2017-10-28T15:58:41Z	2017-10-28T15:58:41Z	"Using the first public beta of 10.13.1, a kernel panic and system crash occurs as soon as you start VirtualBox.  This happens with both VirtualBox 5.1.28 and the 5.2 release candidate.

I found  workaround that works for me:

1.  Run ""VBoxManage list vms” to list your VM’s along with their display names and kids
2.  Run your VM in headless mode by running “VBoxManage startvm your-vm-name —type headless” where your-vm-name is the name listed in step 1.
3.  Run virtualbox to bring up its UI
4.  Select the running VM in VirtualBox and click “Show”.  At this point the UI for your running VM should appear.

After that the virtual machine (Windows 10) ran as expected and I was able to shut it down in the normal way from its UI."	Matt L.
19642	Virtualbox UI freezes after clicking VM in list and corresponding VM is not properly booting	VirtualBox 6.1.10	2020-06-07T10:29:01Z	2020-08-28T14:35:15Z	2020-08-28T14:35:15Z	"Observed behaviour:
--------------------

When I start the VM with ""vagrant up"" (while having Virtualbox GUI open), the VM is created and booted in Virtualbox. Then vagrant hangs at the point, when it tries to access the VM via SSH in order to configure the VM. At the same time in Virtualbox, when I click on the VM in the list, the GUI of Virtualbox freezes and does not unfreeze anymore. I need to end the Virtualbox Manager Process in Windows Task manager in order to make Virtualbox work again.
The Problem occurs with several Vagrant Boxes with recent Ubuntu versions (e.g. ubuntu/focal64, ubuntu/eoan64). It seems to work (at least most of the time) with older Ubuntu versions (e.g. ubuntu/trusty64).

I have the feeling that I experience problems with Virtualbox since upgrading Windows to 2004 (Spring 2020 Update) and/or enabling WSL2, but I cannot prove since I haven't used Virtualbox immediately before the upgrade / WSL 2 enabling.

Expected bahaviour:
-------------------

The Virtualbox GUI does not freeze when I click on the VM in the list of VMs and Vagrant is able to finish the prozess of configuring the VM.


Additional Information:
-----------------------

- Windows 10 Pro (2004, Spring 2020 Update)
- Windows Subsystem for Linux (WSL) 2 enabled 
- Virtualbox 6.1.10 r138449 (Qt5.6.2)
- Vagrant 2.2.9
- Vagrant Box: ubuntu/focal64, 20200605.1.0"	chrizzzt
16320	Virtualbox uses 100% of CPU when suspending PC	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
17185	VirtualBox v5.x & nVidia Graphics Card: Driver reverts to VGASave upon VB Installation	VirtualBox 5.2.0	2017-10-20T12:04:38Z	2017-10-20T12:04:38Z	2017-10-20T12:04:38Z	"My system:

MS-WinXP with SP3 and fully Updated

Palit nVidia GeForce 7300GT AGP 8X 512MB DDR2 128bit

nVidia Driver Packages tried:
  * 306.81-desktop-winxp-32bit-english-whql.exe
  * 307.74-desktop-winxp-32bit-english-whql.exe
  * 307.83-desktop-winxp-32bit-english-whql.exe

Example nVidia driver details output:

{{{
CMD>filever -v \WINDOWS\system32\nv4_disp.dll
--a-- W32i   DRV ENU     6.14.13.774 shp  4,493,440 01-03-2013 nv4_disp.dll
        Language        0x0409 (English (United States))
        CharSet         0x04b0 Unicode
        OleSelfRegister Disabled
        CompanyName     NVIDIA Corporation
        FileDescription NVIDIA Windows XP Display driver, Version 307.74
        InternalName    nv4_disp.dll
        OriginalFilenam nv4_disp.dll
        ProductName     NVIDIA Windows XP Display driver, Version 307.74
        ProductVersion  6.14.13.0774
        FileVersion     6.14.13.0774
        LegalCopyright  (C) 2012 NVIDIA Corporation. All rights reserved.

        VS_FIXEDFILEINFO:
        Signature:      feef04bd
        Struc Ver:      00010000
        FileVer:        0006000e:000d0306 (6.14:13.774)
        ProdVer:        0006000e:000d0306 (6.14:13.774)
        FlagMask:       0000003f
        Flags:          00000008 private
        OS:             00040004 NT Win32
        FileType:       00000003 Driver
        SubType:        00000004 DisplayDrv
        FileDate:       00000000:00000000
}}}

The problem:

Using VirtualBox v5.1.28 [VirtualBox-5.1.28-117968-Win.exe] with the corresponding extension pack, also previous versions, also with two other, GeForce 6200 nVidia cards, I was experiencing the following:

  a. occasional screen blanking, which, after a few seconds, was restored

  b. my graphics card driver was spontaneously reverting to VGASave [the Microsoft “failsafe” generic driver, that is not able to provide my graphics card & monitor optimal native resolution] after rebooting my system, but a re-installation of the driver package would return things to normal

After having upgraded to the current version of VirtualBox [VirtualBox-5.2.0-118431-Win.exe (with the corresponding extension pack)] my graphics card driver permanently reverted to the VGASave and consistently does so immediately after I install VirtualBox, ever since [I have also tried installing two previous versions, v5.1.30 and v5.0.40, to no avail]. After I uninstall VirtualBox, things magically return to normal."	Pol_JS
20942	"VirtualBox v6.1.34 shows ""Make sure the kernel module has been loaded successfully"" and VM wont start"	VirtualBox 6.1.32	2022-05-13T21:04:23Z	2022-08-08T11:48:52Z	2022-08-08T11:48:52Z	"VM no longer starts after:
- a VirtualBox upgrade
- then a Windows Update

- had VirtualBox-6.1.32-149290-Win.exe installed since 01/31/2022
- On 05/09/2022, I upgraded it with VirtualBox-6.1.34-150636-Win.exe
- VM working perfectly. Saved, or closed and reopened...
- on 05/12/2022, I rebooted windows, and a Windows Update took place.
- Then, VM no longer starts with message:

{{{
VirtualBox - Error In supR1HardenedWinReSpawn
NtCreateFile(\Device\VBoxDrvStub) failed: 0xc0000034
STATUS_OBJECT_NAME_NOT_FOUND (0 retries) (rc=-101)

Make sure the kernel module has been loaded successfully.

where: supR3HardenedWinReSpawn what: 3 VERR_OPEN_FAILED (-101) - File/ Device open failed. driver is probably stuck stopping/starting. Try 'sc.exe query vboxdrv' to get more information about its state. Rebooting may actually help.
}}}


I rebooted windows. Same issue.

- I just discovered that downgrading fixed the problem.
I looked in windows update history and saw:
- on 05/11/2022, (one day before my ""Update and restart"" though this one http://support.microsoft.com/kb/890830. Others are too old

Also, working on a professional laptop, with windows administration by our IT team, I saw this notification after the ""update and restart"" of windows (did not have time to screenshot it), it was saying something like ""an administrator has changed the rights on some path...""
Don't know if it helps.

Hardware:
Intel(R) Core(TM) i7-10750H CPU @ 2.60Ghz
64Go
Windows 11 professional
Version 21H2
Build 22000.675
Experience 1000.22000 675.0"	Syl20
16098	VirtualBox Version 5.1.8 r111374 (Qt5.6.1) does not remember screen size	VirtualBox 5.1.8	2016-10-21T08:54:52Z	2016-10-21T09:20:17Z	2016-10-21T09:20:17Z	On Linux amd64 Mint 13 Maya / (equivalent to) Ubuntu 12.04 Precise Pangolin as Host System, running a Debian x86-32bit Wheezy in windowed mode as Guest System, VirtualBox forgets about the screen size between reboots forcing me to stretch the window or running in full-screen mode.	Geppo61
19921	VirtualBox Version 6.1.14 r140239 (Qt5.6.2) will not work with Windows Preview	VirtualBox 6.1.14	2020-09-27T11:31:44Z	2020-09-29T08:32:15Z	2020-09-29T08:32:15Z	"Edition	Windows 10 Pro Insider Preview
Version	2004
Installiert am	‎24.‎09.‎2020
Betriebssystembuild	20221.1000
Leistung	Windows Feature Experience Pack 120.22800.0.0
"	DKKABG
19795	Virtualbox VM (Windows or Linux) crashes on Mac OS Bigsur host	VirtualBox 6.1.10	2020-08-05T15:14:30Z	2021-09-30T04:28:40Z	2021-09-30T04:28:40Z	"When I try to open a VM (does not matter if Windows or Linux), the error occur

Kernel driver not installed (rc=-1908)

Make sure the kernel module has been loaded successfully.

where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT."	hoshikawa2
20082	Virtualbox VM crashes with macOS Catalina host and High Sierra guest	VirtualBox 6.1.16	2020-12-05T20:11:13Z	2020-12-05T20:56:59Z	2020-12-05T20:56:59Z	"This crash occurs with VirtualBox 6.1.16 r140961 (Qt5.6.3).
I have attached the crash report which says:

abort() called
VirtualBoxVM(2751,0x700009f62000) malloc: Incorrect checksum for freed object 0x7feb1d5627f8: probably modified after being freed.
Corrupt value: 0x0

A different crash occurs with the same program running on a macOS Mojave
guest.  That crash is reported on the guest as a bus error 10, but only
after the VM window stops responding, and the VM is then paused and unpausing.  This crash occurs in a restored snapshot from July 23.  The
program ran without errors at the time the snapshot was taken, as
verified by log files generated at that time.

The program which is running when these crashes occur is the Tk
regression test suite.  I am trying to use the VMs to verify that
the Tk regression tests pass on older versions of macOS."	culler
18191	VirtualBox VM start crashes Win10 host inside a Linux KVM	VirtualBox 5.2.22	2018-12-17T13:28:25Z	2018-12-18T12:47:45Z	2018-12-18T12:47:45Z	When I start a VirtualBox VM in a Win10 host, which is in turn a Linux KVM guest, the Win10 host crashes right away (it hard resets itself without even showing a BSOD). It doesn't seem to matter if I am doing nested virtualization (i.e. kvm_intel loaded with nested=1). It appears to be a regression introduced in 5.2.8.	tomty89
20489	virtualbox vms are no longer finctioning	VirtualBox 6.1.26	2021-08-05T04:36:11Z	2021-08-05T04:36:11Z	2021-08-05T04:36:11Z	I updated virtualbox when prompted from then onwards the VM's that I made are no longer functional	Adhu
20907	VirtualBox window doesn't move or resize	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
18780	VirtualBox-6.0.10-132072-Win  BSOD	VirtualBox 6.0.10	2019-07-22T17:55:40Z	2019-07-25T05:16:39Z	2019-07-25T05:16:39Z	"Steps to reproduce:
-create or use an existing Windows7 VM
-download VNC viewer standalone
-run it inside the VM => BSOD

No BSOD with VirtualBox-5.2.30-130521"	jcstaquet
20719	VirtualBox-6.1-6.1.31_148688_el7-1.x86_64.rpm fail to build on Kylin Linux Advanced Server V10	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
21299	VirtualBox-7.0.4 kernel module build fails on RHEL9.1 host => fixed in svn	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
15024	VirtualBox-GuruMeditation error in Ubuntu	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
16645	"VirtualBox.dll"" failed, rc=1790"	VirtualBox 5.1.18	2017-04-10T16:23:33Z	2017-04-13T15:06:28Z	2017-04-13T15:06:28Z	"The virtual machine 'test' has terminated unexpectedly during 
startup with exit code 1 (0x1). More details may be available in 
'C:\Users\David\VirtualBox VMs\test\Logs\VBoxHardening.log'."	David Popple
18700	Virtualbox.exe - application error when running dxdiag or hl2 in Windows XP sp3 guest	VirtualBox 5.2.30	2019-06-09T19:36:13Z	2019-06-09T19:36:13Z	2019-06-09T19:36:13Z	When running dxdiag or hl2 in windows xp sp3 guest, appears window Virtualbox.exe - application error	nikitastepanov
18729	virtualbox.exe - application error when running steam on windows xp sp3 guest	VirtualBox 5.2.30	2019-06-27T18:39:54Z	2019-06-27T18:39:54Z	2019-06-27T18:39:54Z	when running steam on windows xp sp3 guest, appears window: virtualbox.exe - application error	nikitastepanov
12087	VirtualBox.exe fails to run	VirtualBox 4.2.18	2013-09-09T11:42:00Z	2016-09-28T10:54:18Z	2016-09-28T10:54:18Z	"VirtualBox.exe failed with the message:[[BR]]
Callee RC: E_NOINTERFACE (0x80004002)[[BR]]

VBoxSVC.log reports:[[BR]]
Watcher  ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={3b2f08eb-b810-4715-bee0-bb06b9880ad2} aComponent={VirtualBox} aText={The object is not ready}, preserve=false[[BR]]

Running as administrator -> no error[[BR]]

Previous version (4.2.16) does not have this issue."	yefkov
19671	VirtualBoxVM crash, rtR3WinUnhandledXcptFilter caught an exception	VirtualBox 6.1.10	2020-06-19T08:48:49Z	2020-06-19T08:48:49Z	2020-06-19T08:48:49Z	"At time VirtualBoxVM.exe crashes with a pop-up, ""The instruction at '0xXX' referenced memory at '0xXX'. The memory could not be read.

And this issue can be easily reproduced if I use Google chrome within VM.

Vbox is installed in Window 10 & Ubuntu 18.04 is installed Vbox.

Hereby I'm attaching the log file as well."	pearleye
16719	Virtualization not working without VT-x in the newer versions (5)	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
14172	Virturalbox doesn't start	VirtualBox 4.3.28	2015-06-03T17:13:48Z	2015-06-03T17:13:48Z	2015-06-03T17:13:48Z	"I have win 7 ultimate running on my laptop. VirtualBox was running great until about a week ago. when I clicked on it nothing happened. so i uninstalled and reinstalled. and it worked but did not recognize any usb drive like it did before. after  a day or two it went back to nothing happening when I click on it  vboxSVC.exe and VirtualBox.exe are running in task manager after I try to start VirtualBox. i did a complete uninstall cleaning every thing out on the registry and every folder off c: with VirtualBox or xbox in the name. then i reinstalled it still no luck. last night i did get some hope when i disabled the VirtualBox host only network connection and started VirtualBox. it started so i closed it and enabled VirtualBox host only network connection it still worked. Now the next morning I'm back to square one and nothing I try seems to work it just will not open. 

i'm running VirtualBox 4.3.28 for Windows
"	bnerny
16006	virutal machine paused with clonezilla	VirtualBox 5.0.24	2016-09-30T10:32:21Z	2016-09-30T10:32:21Z	2016-09-30T10:32:21Z	"when i'm trying to clone from a vmdk image to a physical disk, the virtual box pause itself with warning when clonezilla has written the partition table to the new disk and ""informing the OS of partition table changes...""

The I/O cache encountered an error while updating data in medium ""ahci-0-1"" (rc=VERR_ACCESS_DENIED). Make sure there is enough free space on the disk and that the disk is working properly. Operation can be resumed afterwards.


Fehler ID: 
BLKCACHE_IOERR
Dringlichkeit:
Normaler Fehler
"	mholzer
20064	Vista VM not functioning properly.	VirtualBox 6.1.16	2020-11-24T20:19:09Z	2020-11-24T20:19:09Z	2020-11-24T20:19:09Z	I have my windows Vista VM set up following the instructions of someone who’s been successful with vms, however, I can’t get past the loading screen before the vm gets a BSOD. [[Image()]]	MetaKnightmare
14524	VisualStudio 2013 Professional on Windows 10	VirtualBox 5.0.2	2015-08-31T09:12:59Z	2015-10-31T02:15:37Z	2015-10-31T02:15:37Z	"I have Windows 10 installed and Visual Studio 2013 Professional. 
Also the host has Windows 10 installed. 
When my computer goes to sleep and starts-up again the screen size 
of the virtual environment is decreased to 800x600.
Before that screen size it was 1600x860. 
To fix this I can only reboot the virtual environment.

When I used Windows 8.1 and VirtualBox 4.2 this problem did not occured.  "	UserVirtualBox
17429	VM  Manager crash crash when creating new VM Machine	VirtualBox 5.2.4	2018-01-07T14:39:51Z	2018-01-18T23:50:32Z	2018-01-18T23:50:32Z	When I attempt to create a new VM machine the manager crashes. Virtual box has been installed in WInd 7 Prof 32 bit. Cannot provide log file as it can't create the VM machine first time.. I have reinstalled virtual box a few times and makes no difference.	porsha
19508	VM (not) terminated with exit code 0	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
20388	VM aborted while saving state	VirtualBox 6.1.22	2021-06-05T10:43:51Z	2021-06-05T10:43:51Z	2021-06-05T10:43:51Z	"I tried to save the state of the VM by selecting File → Close from the popup menu (invoked via a custom Host key shortcut) and, with the “Save state” radio button selected, pressing OK. At first, the VM seemed to save normally, but then the save process appeared to stop prematurely and the VirtualBox interface showed the VM state as “Aborted”.

This occurred after upgrading VirtualBox from 6.0.24 to 6.1.22. Before the incident, the VM had been running for several days and, if I recall correctly, was successfully saved and restored once, and also paused and resumed once."	mgrzegor
19123	VM Aborts On Laptop Suspend OR Machine Pause	VirtualBox 6.0.14	2019-12-02T12:53:20Z	2020-01-18T16:29:41Z	2020-01-18T16:29:41Z	"Hello,

Recently updated to 6.0.14 on Windows 10, hosting a Centos guest.

Two scenarios trigger a VM abort, maybe 50% of the time:
[1] pause VM (Machine -> Pause)
]2] send laptop to sleep

A dialog will pop up (immediately for [1]  and on resume for [2]).

Attaching logs and a screenshot of the dialog.

Cheers,
yato
"	yato
21040	VM blocked on humongus amounts of disk read	VirtualBox 6.1.36	2022-07-28T16:20:26Z	2022-08-02T12:01:44Z	2022-08-02T12:01:44Z	"Problem occurring since updating to 6.1.36 from 6.1.34

running condition tested for reproduction:
  - on a old windows 10 host install, run old or new Linux guests (both EFI, and non EFI) that were working on 6.1.34
  - on a fresh windows 10 host install (21H2), with the same scenarios.

steps to reproduce:
  - from a system without VirtualBox installed, or with VirtualBox 6.1.34 installed:
    - install or update to 6.1.36,
    - try to run any linux guest

observed behavior:
  - at startup a 19GB vdi guest generates a 100 second read @ 600+ MB/s (so about 60GB read) blocking the guest execution for the whole time,
  - after logging in, a second wave of read is triggered (about 30s, so 20GB), 
  - and on shutdown the read is also triggered for about 90 seconds rendering the whole process very cumbersome and sluggish.
  - note: using the menu to insert guest additions CD also triggers a read freeze."	os19000
20712	VM Cannot Start	VirtualBox 6.1.30	2021-12-02T16:15:00Z	2021-12-02T16:15:00Z	2021-12-02T16:15:00Z	"{{{
virtualbox-6.1:
  Installed: 6.1.30-148432~Debian~buster
  Candidate: 6.1.30-148432~Debian~buster
  Version table:
 *** 6.1.30-148432~Debian~buster 500
        500 http://download.virtualbox.org/virtualbox/debian buster/contrib amd64 Packages
        100 /var/lib/dpkg/status

Linux office-markm 5.10.0-0.bpo.8-rt-amd64 #1 SMP PREEMPT_RT Debian 5.10.46-4~bpo10+1 (2021-08-07) x86_64 GNU/Linux


00:00:00.927460 VirtualBox VM 6.1.30 r148432 linux.amd64 (Nov 22 2021 15:33:42) release log
00:00:00.927462 Log opened 2021-12-02T16:04:38.932286000Z
00:00:00.927463 Build Type: release
00:00:00.927465 OS Product: Linux
00:00:00.927466 OS Release: 5.10.0-0.bpo.8-rt-amd64
00:00:00.927467 OS Version: #1 SMP PREEMPT_RT Debian 5.10.46-4~bpo10+1 (2021-08-07)
00:00:00.927487 DMI Product Name: OptiPlex 9020
00:00:00.927494 DMI Product Version: 00
00:00:00.927503 Firmware type: BIOS
00:00:00.927536 Host RAM: 32054MB (31.3GB) total, 10660MB (10.4GB) available
00:00:00.927539 Executable: /usr/lib/virtualbox/VirtualBoxVM
00:00:00.927539 Process ID: 20302
00:00:00.927540 Package type: LINUX_64BITS_DEBIAN_10_0
00:00:00.943981 Installed Extension Packs:
00:00:00.943981   Oracle VM VirtualBox Extension Pack (Version: 6.1.30 r148432; VRDE Module: VBoxVRDP)
00:00:00.948269 Console: Machine state changed to 'Starting'
00:00:00.948404 Qt version: 5.11.3
00:00:00.948412 X11 Window Manager code: 0
00:00:01.009079 GUI: UIMediumEnumerator: Medium-enumeration finished!
00:00:01.010328 X Server details: vendor: The X.Org Foundation, release: 12004000, protocol version: 11.0, display string: :0
00:00:01.010350 Using XKB for keycode to scan code conversion
00:00:01.049341 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated: Screen 2 work area is actually resized to: 0x20 x 2558x1398
00:00:01.050343 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated: Screen 1 work area is actually resized to: 0x20 x 2558x1398
00:00:01.051380 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated: Screen 0 work area is actually resized to: 0x20 x 2558x1398
00:00:01.115832 GUI: Machine-window #0 activated
00:00:01.115895 GUI: Machine-view #0 focused, reason=3
00:00:03.056026 GUI: Machine-window #0 deactivated
00:00:03.056026 GUI: Releasing mouse on focus out
00:00:03.056026 GUI: Machine-view #0 unfocused, reason=3
00:00:03.123844 GUI: Machine-window #0 activated
00:00:03.123890 GUI: Machine-view #0 focused, reason=3
00:00:03.659742 GUI: Machine-window #0 deactivated
00:00:03.659774 GUI: Releasing mouse on focus out
00:00:03.660287 GUI: Machine-view #0 unfocused, reason=3
00:00:14.430220 GUI: Machine-window #0 activated
00:00:14.430254 GUI: Machine-view #0 focused, reason=3
00:00:16.189701 GUI: Machine-window #0 deactivated
00:00:16.189731 GUI: Releasing mouse on focus out
00:00:16.190252 GUI: Machine-view #0 unfocused, reason=3

<VirtualBox xmlns=""http://www.virtualbox.org/"" version=""1.15-linux"">
  <Machine uuid=""{1d0f8da1-4e95-471b-b001-632dfe4697cd}"" name=""Windows 10"" OSType=""Windows10_64"" snapshotFolder=""Snapshots"" lastStateChange=""2021-12-02T16:03:48Z"" aborted=""true"">
    <MediaRegistry>
      <HardDisks>
        <HardDisk uuid=""{8a59a0b2-ab28-4cb8-b4a3-90b34179e741}"" location=""/home/vbox/Win10-64-disk1.vdi"" format=""VDI"" type=""Normal""/>
      </HardDisks>
    </MediaRegistry>
    <Hardware>
      <CPU>
        <PAE enabled=""true""/>
        <LongMode enabled=""true""/>
        <HardwareVirtExLargePages enabled=""false""/>
      </CPU>
      <Memory RAMSize=""6105""/>
      <HID Pointing=""USBTablet""/>
      <Paravirt provider=""Default""/>
      <Display controller=""VBoxSVGA"" VRAMSize=""50""/>
      <VideoCapture file=""."" fps=""25""/>
      <RemoteDisplay enabled=""false""/>
      <BIOS>
        <IOAPIC enabled=""true""/>
        <SmbiosUuidLittleEndian enabled=""true""/>
      </BIOS>
      <USB>
        <Controllers>
          <Controller name=""XHCI"" type=""XHCI""/>
        </Controllers>
      </USB>
      <Network>
        <Adapter slot=""0"" enabled=""true"" MACAddress=""0800274DED3F"" cable=""true"" type=""82540EM"">
          <NAT/>
        </Adapter>
      </Network>
      <AudioAdapter controller=""HDA"" driver=""Pulse"" enabled=""true"" enabledIn=""false""/>
      <Clipboard/>
    </Hardware>
    <StorageControllers>
      <StorageController name=""SATA"" type=""AHCI"" PortCount=""2"" useHostIOCache=""false"" Bootable=""true"" IDE0MasterEmulationPort=""0"" IDE0SlaveEmulationPort=""1"" IDE1MasterEmulationPort=""2"" IDE1SlaveEmulationPort=""3"">
        <AttachedDevice type=""HardDisk"" hotpluggable=""false"" port=""0"" device=""0"">
          <Image uuid=""{8a59a0b2-ab28-4cb8-b4a3-90b34179e741}""/>
        </AttachedDevice>
        <AttachedDevice passthrough=""false"" type=""DVD"" hotpluggable=""false"" port=""1"" device=""0""/>
      </StorageController>
    </StorageControllers>
  </Machine>
</VirtualBox>



[Thu Dec  2 11:02:12 2021] BUG: kernel NULL pointer dereference, address: 0000000000000018
[Thu Dec  2 11:02:12 2021] #PF: supervisor write access in kernel mode
[Thu Dec  2 11:02:12 2021] #PF: error_code(0x0002) - not-present page
[Thu Dec  2 11:02:12 2021] PGD 0 P4D 0
[Thu Dec  2 11:02:12 2021] Oops: 0002 [#1] PREEMPT_RT SMP PTI
[Thu Dec  2 11:02:12 2021] CPU: 7 PID: 11334 Comm: EMT Tainted: G        W  OE     5.10.0-0.bpo.8-rt-amd64 #1 Debian 5.10.46-4~bpo10+1
[Thu Dec  2 11:02:12 2021] Hardware name: Dell Inc. OptiPlex 9020/0PC5F7, BIOS A25 05/30/2019
[Thu Dec  2 11:02:12 2021] RIP: 0010:rt_spin_lock+0x10/0x30
[Thu Dec  2 11:02:12 2021] Code: 01 00 00 00 f0 0f b1 13 75 02 5b c3 89 c6 48 89 df e8 e4 9a 83 ff 66 90 5b c3 0f 1f 44 00 00 65 48 8b 14 25 40 7c 01 00 31 c0 <f0> 48 0f b1 57 18 48 85 c0 75 0a e8 e0 a8 85 ff e9 9b 7b 80 ff e8
[Thu Dec  2 11:02:12 2021] RSP: 0018:ffffb1c9cdd67d30 EFLAGS: 00010246
[Thu Dec  2 11:02:12 2021] RAX: 0000000000000000 RBX: ffff90b016b63548 RCX: 0000000000000000
[Thu Dec  2 11:02:12 2021] RDX: ffff90af46f80000 RSI: 000fffffffe00000 RDI: 0000000000000000
[Thu Dec  2 11:02:12 2021] RBP: ffffb1c9d3ef6000 R08: ffffb1c9cdd67dd0 R09: 0000000000000001
[Thu Dec  2 11:02:12 2021] R10: 0000000000000001 R11: 0000000000000001 R12: ffff90af4019f4f8
[Thu Dec  2 11:02:12 2021] R13: ffffb1c9d3ef6000 R14: ffffb1c9d3ea9000 R15: ffff90af44a293d0
[Thu Dec  2 11:02:12 2021] FS:  00007f9bc228a700(0000) GS:ffff90b63ddc0000(0000) knlGS:0000000000000000
[Thu Dec  2 11:02:12 2021] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[Thu Dec  2 11:02:12 2021] CR2: 0000000000000018 CR3: 0000000219252006 CR4: 00000000001706e0
[Thu Dec  2 11:02:12 2021] Call Trace:
[Thu Dec  2 11:02:12 2021]  __apply_to_page_range+0x2a7/0x680
[Thu Dec  2 11:02:12 2021]  ? rtR0TermNative+0x40/0x40 [vboxdrv]
[Thu Dec  2 11:02:12 2021]  rtR0MemObjNativeProtect+0x74/0xb0 [vboxdrv]
[Thu Dec  2 11:02:12 2021]  VBoxHost_RTR0MemObjProtect+0xad/0xc0 [vboxdrv]
[Thu Dec  2 11:02:12 2021]  supdrvIOCtl+0x335b/0x3810 [vboxdrv]
[Thu Dec  2 11:02:12 2021]  ? _copy_from_user+0x26/0x50
[Thu Dec  2 11:02:12 2021]  VBoxDrvLinuxIOCtl_6_1_30+0x156/0x230 [vboxdrv]
[Thu Dec  2 11:02:12 2021]  __x64_sys_ioctl+0x84/0xc0
[Thu Dec  2 11:02:12 2021]  do_syscall_64+0x33/0x80
[Thu Dec  2 11:02:12 2021]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[Thu Dec  2 11:02:12 2021] RIP: 0033:0x7f9c0cd99427
[Thu Dec  2 11:02:12 2021] Code: 00 00 90 48 8b 05 69 aa 0c 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 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 39 aa 0c 00 f7 d8 64 89 01 48
[Thu Dec  2 11:02:12 2021] RSP: 002b:00007f9bc2288c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
[Thu Dec  2 11:02:12 2021] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f9c0cd99427
[Thu Dec  2 11:02:12 2021] RDX: 00007f9bc1db2010 RSI: 0000000000005684 RDI: 0000000000000008
[Thu Dec  2 11:02:12 2021] RBP: 00007f9bc2288c80 R08: 0000000000000000 R09: 0000000000000000
[Thu Dec  2 11:02:12 2021] R10: 0000000000000010 R11: 0000000000000246 R12: 00007f9bc2288de0
[Thu Dec  2 11:02:12 2021] R13: 00007f9bc22890e0 R14: 00007f9bc1db2010 R15: 0000000000000004
[Thu Dec  2 11:02:12 2021] Modules linked in: cfg80211 vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) fuse ufs qnx4 hfsplus hfs cdrom minix vfat msdos fat jfs xfs ext4 mbcache jbd2 dm_mod c ufreq_userspace cpufreq_powersave cpufreq_ondemand cpufreq_conservative bnep bluetooth jitterentropy_rng drbg ansi_cprng ecdh_generic rfkill ecc crc16 binfmt_misc uinput nfsd auth_rpcg s nfs_acl nfs lockd grace nfs_ssc fscache sunrpc radeon loop parport_pc ppdev lp parport intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel uvcvi eo snd_hda_codec_realtek videobuf2_vmalloc snd_usb_audio videobuf2_memops videobuf2_v4l2 snd_hda_codec_generic videobuf2_common kvm ledtrig_audio snd_hda_codec_hdmi snd_usbmidi_lib vid odev irqbypass snd_hda_intel crc32_pclmul snd_rawmidi snd_intel_dspcfg snd_seq_device soundwire_intel amdgpu ghash_clmulni_intel joydev mc soundwire_generic_allocation snd_soc_core aes i_intel snd_compress soundwire_cadence libaes crypto_simd cryptd dell_wmi evdev mei_wdt
[Thu Dec  2 11:02:12 2021]  mei_hdcp glue_helper snd_hda_codec rapl gpu_sched snd_hda_core intel_cstate ttm snd_hwdep dell_smbios soundwire_bus sg dcdbas drm_kms_helper snd_pcm_oss spa se_keymap dell_wmi_descriptor wmi_bmof intel_uncore cec snd_mixer_oss at24 iTCO_wdt intel_pmc_bxt snd_pcm iTCO_vendor_support drm snd_timer watchdog mei_me i2c_algo_bit snd pcspkr soun core mei button btrfs blake2b_generic xor hid_microsoft ff_memless hid_generic usbhid hid raid6_pq libcrc32c crc32c_generic sd_mod t10_pi crc_t10dif crct10dif_generic xhci_pci xhci_hcd ehci_pci ahci ehci_hcd libahci libata crct10dif_pclmul e1000e crct10dif_common i2c_i801 usbcore ptp scsi_mod crc32c_intel i2c_smbus lpc_ich pps_core usb_common wmi video
[Thu Dec  2 11:02:12 2021] CR2: 0000000000000018
[Thu Dec  2 11:02:12 2021] ---[ end trace 0000000000000003 ]---
[Thu Dec  2 11:02:12 2021] RIP: 0010:rt_spin_lock+0x10/0x30
[Thu Dec  2 11:02:12 2021] Code: 01 00 00 00 f0 0f b1 13 75 02 5b c3 89 c6 48 89 df e8 e4 9a 83 ff 66 90 5b c3 0f 1f 44 00 00 65 48 8b 14 25 40 7c 01 00 31 c0 <f0> 48 0f b1 57 18 48 85 c0 75 0a e8 e0 a8 85 ff e9 9b 7b 80 ff e8
[Thu Dec  2 11:02:12 2021] RSP: 0018:ffffb1c9cdd67d30 EFLAGS: 00010246
[Thu Dec  2 11:02:12 2021] RAX: 0000000000000000 RBX: ffff90b016b63548 RCX: 0000000000000000
[Thu Dec  2 11:02:12 2021] RDX: ffff90af46f80000 RSI: 000fffffffe00000 RDI: 0000000000000000
[Thu Dec  2 11:02:12 2021] RBP: ffffb1c9d3ef6000 R08: ffffb1c9cdd67dd0 R09: 0000000000000001
[Thu Dec  2 11:02:12 2021] R10: 0000000000000001 R11: 0000000000000001 R12: ffff90af4019f4f8
[Thu Dec  2 11:02:12 2021] R13: ffffb1c9d3ef6000 R14: ffffb1c9d3ea9000 R15: ffff90af44a293d0
[Thu Dec  2 11:02:12 2021] FS:  00007f9bc228a700(0000) GS:ffff90b63ddc0000(0000) knlGS:0000000000000000
[Thu Dec  2 11:02:12 2021] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[Thu Dec  2 11:02:12 2021] CR2: 000000de09e0d000 CR3: 0000000219252004 CR4: 00000000001706e0

VirtualBox Guest Freezes while showing 'Starting'
}}}"	iMarkM
19201	"VM changes from good to ""inaccessible"" after about a minute"	VirtualBox 6.1.0	2020-01-06T20:54:29Z	2020-01-06T20:54:29Z	2020-01-06T20:54:29Z	"With VirtualBox 6.1 on Fedora 30 and all updates applied, I create a VM and attach an existing virtual disk (Centos 7.6 is the guest operating system) as ""immutable"". I snapshot it twice afterwards, first to make a differencing disk image and next to allow students to roll back their changes. I have been doing this for nearly a decade across many VirtualBox releases, and it usually works. I can list the VMs associated with a user account:

VBoxManage list vms

and it will show the correct name of the VM for a minute or two of repeated ""list vms"", then it will change to ""inaccessible"".

When I revert to 5.2.34, this behavior goes away and the VM remains accessible and usable."	Stephen Rondeau
10851	VM config file lost after host power off	VirtualBox 4.1.20	2012-08-22T08:52:36Z	2018-03-07T08:09:42Z	2018-03-07T08:09:42Z	"VBox: 4.1.16 (and 4.1.20)

Host: Windows 7 x64 (and other Windows)

When shutting down host, (after Windows update, or sudden power off) in some cases VBox does delete the *.vbox meta-data file, and the VM becomes ""inaccessible"" state. In some cases the file becomes corrupted and zero-bytes, and there are no *.vbox-tmp and no *.vbox-prev files to recover from.

Workaround: copy [VM].vbox-tmp or [VM].vbox-prev as [VM].vbox can restore the VM in most cases. (something new users can't do)

Recommended real fix: VBoxSVC must write down a history of transactions into the VM folder, per VM, [VM].vbox-transactions file, which should list all changes to the *.vbox file meta-data in a patch/diff format, and then, when VM becomes ""inaccessible"", VBoxSVC must attempt to recover the file until last transaction automatically, plus will allow manual recover and debug.

NOTE: This bug is an old one, and AFAIK happens once every several weeks since v4.0.0 (but rarely) - still losing VM is *really* bad.

Log attached.

-Technologov, 2012-08-22."	Technologov
16754	VM config lost after saving state	VirtualBox 5.1.22	2017-05-12T22:28:17Z	2017-06-12T23:32:35Z	2017-06-12T23:32:35Z	"I've had this issue happen several times recently. I click to save the state of a VM. It saves the state completely and the window closes. I then close out of VirtualBox (UI). 

The next time I open the Vbox UI, the VM looks normal. However, when I attempt to start the VM, I'm greeted with ""Fatal: no boot media"". It seems that the *.vbox file may have been saved incorrectly as a result of the previous shutdown. What I see in the UI is that the entire Storage area is blank (it's lost all of the hard drives, CD, etc). It also has reset the memory and possibly other settings. It's almost like it's overwritten the *.vbox file with a generic template. Or, perhaps a generic template is created because the original *.vbox file has gone missing... not sure which?

I have encountered this bug at least 3 times since 5.1.18. I am still seeing it in the latest version (5.1.22). So, whatever is causing this issue is not fixed. Two of the times, I could easily recreate the VMs. However in this latest one, I need to recover some information for reference.

As an FYI, the *.vdi hard drive files exist. In the snapshot director, I see the *.sav file and the various snapshot files. Unfortunately, trying to hand recreate the working *.vbox file for this VM the way that it was is probably next to impossible.

Note that this VM began its life as a linked clone from another VM. I have not modified the original from which it was cloned, so it shouldn't be related to that. However, for each of these I have encountered, they have all been from linked clones making recreating the *.vbox file more complicated.

It would be great if there were a repair tool included to scan the VM's directory and attempt to repair or recreate the *.vbox file using the files it can find. If such a tool already exists, please let me know. If there's an easy way to recreate this *.vbox file, that would be helpful.

As an FYI, I've also looked at the 'backup' *.vbox file and it also appears to be a generic template. So, I can't even recover from that."	commorancy0
17641	VM console not displayed properly	VirtualBox 5.2.6	2018-03-27T10:22:39Z	2018-03-27T10:22:39Z	2018-03-27T10:22:39Z	"Version: VirtualBox-5.2.9-121224-Linux_amd64.run

Problem: The vm console generated at vm start is not displayed properly. All
         that appears is the top part of the widget title bar. This problem
         appears with WindowMaker running. The problem does not appear with
         KDE running."	George R. Goffe
17672	VM crash after winXP resumes from hibernation	VirtualBox 5.2.6	2018-04-09T11:30:26Z	2018-04-09T11:30:26Z	2018-04-09T11:30:26Z	WinXP install > hibernate it via windows's own hibernation > start VM back up > VM crashes with the 'critical error' dialogue.	Paul17041993
21069	VM crash diuring install lazarus or anower big packageset	VirtualBox 6.1.36	2022-08-18T12:13:01Z	2022-08-18T14:01:39Z	2022-08-18T14:01:39Z	"Hello.

BEFORE, latest activity:
I maked before crushes disk shrunked: VBoxManage modifyhd /path/to/VDI/VM.vdi --compact  (path are different, instructions https://askubuntu.com/questions/1092812/zerofree-on-ubuntu-18-04)

then i see excelent resul: VDI file set to 21GB from 500GB 

After somes reboot i try to launth TLauncher und try to install java 8 -- VM crush.
Then i try to install new lazarus - VM crush.  

"	Дмитро
15669	VM crash during start (Intel Atom D525)	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
17361	VM Crash on Android USB (debug+tether) unplug	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
15942	vm crash on macos upon cmd+c	VirtualBox 5.0.26	2016-09-16T10:21:42Z	2016-09-16T19:10:50Z	2016-09-16T19:10:50Z	"virtualbox 5.0.26 on macos.
sometimes, the vm crashes (maybe once every two months or so).
last time it specifically happened when (accidentally) pressing cmd+c.

the vm log ends like this :

{{{
92:22:28.521238 VBVA: InfoScreen: [0] @0,0 1440x900, line 0x1680, BPP 32, flags 0x1
92:22:28.521254 Display::handleDisplayResize: uScreenId=0 pvVRAM=00000001251ee000 w=1440 h=900 bpp=32 cbLine=0x1680 flags=0x1
92:22:28.521277 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=1440x900, Sending to async-handler
92:22:28.521337 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=1440x900
92:22:28.521342 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=1440x900
92:22:28.521346 GUI: UIFrameBufferPrivate::performResize: Size=1440x900, Directly using source bitmap content
92:22:28.521470 VBVA: InfoScreen: [0] @0,0 1440x900, line 0x1680, BPP 32, flags 0x1
92:53:54.885280 VBVA: InfoScreen: [0] @0,0 1440x900, line 0x1680, BPP 32, flags 0x1
92:53:54.885336 VBVA: InfoScreen: [0] @0,0 1440x900, line 0x1680, BPP 32, flags 0x5
92:53:54.885344 Display::handleDisplayResize: uScreenId=0 pvVRAM=00000001251ee000 w=1440 h=900 bpp=32 cbLine=0x1680 flags=0x5
92:53:54.885369 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=1440x900, Sending to async-handler
92:53:54.885369 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=1440x900
92:53:54.885369 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=1440x900
92:53:54.885369 GUI: UIFrameBufferPrivate::performResize: Size=1440x900, Using fallback buffer since no source bitmap is provided
92:53:54.885610 VBVA: InfoScreen: [0] @0,0 1440x900, line 0x1680, BPP 32, flags 0x1
92:53:54.885626 Display::handleDisplayResize: uScreenId=0 pvVRAM=00000001251ee000 w=1440 h=900 bpp=32 cbLine=0x1680 flags=0x1
92:53:54.885656 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=1440x900, Sending to async-handler
92:53:54.886947 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=1440x900
92:53:54.886955 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=1440x900
92:53:54.886959 GUI: UIFrameBufferPrivate::performResize: Size=1440x900, Directly using source bitmap content
92:56:51.703893 VBVA: InfoScreen: [0] @0,0 1440x900, line 0x1680, BPP 32, flags 0x1
92:56:51.703989 VBVA: InfoScreen: [0] @0,0 1440x900, line 0x1680, BPP 32, flags 0x1
93:43:17.399764 GUI: UIMachineWindow::handleNativeNotification: Notification 'NSWindowWillExitFullScreenNotification' received
93:43:17.401758 UIMachineWindow::handleNativeNotification: Redirecting 'NSWindowWillExitFullScreenNotification' notification to corresponding machine-window...
93:43:17.401775 UIMachineWindowFullscreen::handleNativeNotification: Notification 'NSWindowWillExitFullScreenNotification' received.
93:43:17.401778 UIMachineWindowFullscreen::handleNativeNotification: Native fullscreen mode about to exit, notifying listener...
93:43:17.441045 GUI: UIMachineLogicFullscreen::sltHandleNativeFullscreenWillExit: Machine-window #0 will exit native fullscreen
93:43:17.968714 GUI: UIMachineWindow::handleNativeNotification: Notification 'NSWindowDidExitFullScreenNotification' received
93:43:17.968735 UIMachineWindow::handleNativeNotification: Redirecting 'NSWindowDidExitFullScreenNotification' notification to corresponding machine-window...
93:43:17.968740 UIMachineWindowFullscreen::handleNativeNotification: Notification 'NSWindowDidExitFullScreenNotification' received.
93:43:17.968743 UIMachineWindowFullscreen::handleNativeNotification: Native fullscreen mode exited, notifying listener...
93:43:17.970210 GUI: UIMachineLogicFullscreen::sltHandleNativeFullscreenDidExit: Machine-window #0 exited native fullscreen, changing visual-state to requested...
}}}"	Richlv
21352	"VM crash with ""Memory could not be read"" error when usb-c monitors are disconnected"	VirtualBox-7.0.4	2022-12-21T21:27:54Z	2022-12-21T21:27:54Z	2022-12-21T21:27:54Z	"Hi,

I am working on a laptop with USB-C port extender. There are two monitors connected via this hub. 
Host system is Windows 11. 
Guest system is Debian Bullseye with guest additions installed.

I usually wok with VM open in either maximized window or full screen mode on one of external monitors, sometimes on two of them. 

When I unplug the usb-c port extender without moving VM windows to internal laptop dislay, the VM throws error that says something in the spirit of:
 
> Instruction at 0x00007FF9F8D215FE referred to memory at address 0x0000029E2900F000. Memory could not be read. 

The exact error message is attached to this ticket, but it is in polish unfortunatelly. 

The problem was present in Virtualbox 6.something. I have upgraded to 7.0.4, but the problem perssts. 

I happens almost every time I unplug the hub without moving the vm windows to main screen or minimizing them. It never happens if I have vm window only on internal screen. 

I have VM set up with:
RAM: 32GB
CPU: 6
EFI: on
Accelleration: Hyper-V
Video memory: 128MB
Screens: 2
GFX: VMSVGA
Accelleration: 3D

"	SWilk
20633	VM Crashed	VirtualBox 6.1.28	2021-10-25T01:13:06Z	2021-10-25T20:35:24Z	2021-10-25T20:35:24Z	"I am running Ubuntu with the latest update ( i believe it is version 20). I was downloading the Bitcoin Blockchain and it crashed on me during normal operations...

here is the log files. I hope that this helps. 
I will donate some ETH or BTC after you guys work through the issue. "	Chiefy
20086	VM crashed when updating Windows 10 guest	VirtualBox 6.1.16	2020-12-08T18:39:35Z	2020-12-10T04:38:41Z	2020-12-10T04:38:41Z	See the logs attached.	fandrei
19153	VM crashes - Virtualbox vm quit unexpectedly	VirtualBox 6.0.14	2019-12-13T09:24:38Z	2021-09-20T11:54:02Z	2021-09-20T11:54:02Z	"Virtualbox vm quit unexpectedly 

Steps to Reproduce:

1. Run VM
2. Keep VM window focused 
3. Lock computer using key-shortcut  Control +Command +Q

Result: VM crashes with below MAC error log


Logs:

{{{
Process:               VirtualBoxVM [22199]
Path:                  /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM
Identifier:            org.virtualbox.app.VirtualBoxVM
Version:               6.0.14 (6.0.14)
Code Type:             X86-64 (Native)
Parent Process:        VBoxSVC [22198]
Responsible:           VirtualBox [22194]
User ID:               502

Date/Time:             2019-12-13 14:24:11.055 +0530
OS Version:            Mac OS X 10.15.1 (19B88)
Report Version:        12
Anonymous UUID:        C1836D25-58A9-7B75-6D08-8464AFECFB2C


Time Awake Since Boot: 17000 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x00000001137fead8
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Segmentation fault: 11
Termination Reason:    Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [22199]

VM Regions Near 0x1137fead8:
    mapped file            00000001137ef000-00000001137fd000 [   56K] r--/r-- SM=ALI  
--> 
    CoreImage              000000011380a000-000000011380b000 [    4K] rw-/rwx SM=PRV  

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_platform.dylib      	0x00007fff6803fdc6 _platform_memmove$VARIANT$Haswell + 198
1   com.apple.framework.IOKit     	0x00007fff3375f00b _IOHIDValueCopyToElementValuePtr + 91
2   com.apple.iokit.IOHIDLib      	0x0000000115226dd3 0x11521a000 + 52691
3   com.apple.iokit.IOHIDLib      	0x0000000115227b63 0x11521a000 + 56163
4   com.apple.framework.IOKit     	0x00007fff33763998 IOHIDDeviceSetValue + 33
5   VBoxGlobal.dylib              	0x000000010d83a149 0x10d559000 + 3019081
6   VBoxGlobal.dylib              	0x000000010d839cd5 0x10d559000 + 3017941
7   VBoxGlobal.dylib              	0x000000010d839aae DarwinHidDevicesApplyAndReleaseLedsState + 590
8   VirtualBoxVM.dylib            	0x000000010bf9dccb 0x10bf69000 + 216267
9   org.qt-project.QtCoreVBox     	0x000000010c2b064d QCoreApplicationPrivate::sendThroughApplicationEventFilters(QObject*, QEvent*) + 205
10  org.qt-project.QtWidgetsVBox  	0x000000010cdcd682 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 66
11  org.qt-project.QtWidgetsVBox  	0x000000010cdd0cde QApplication::notify(QObject*, QEvent*) + 8558
12  org.qt-project.QtCoreVBox     	0x000000010c2b0467 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 167
13  org.qt-project.QtWidgetsVBox  	0x000000010cdcc4ce QApplication::setActiveWindow(QWidget*) + 942
14  org.qt-project.QtWidgetsVBox  	0x000000010cdcc9e2 QApplicationPrivate::notifyActiveWindowChange(QWindow*) + 50
15  org.qt-project.QtGuiVBox      	0x000000010c80af7a QGuiApplicationPrivate::processActivatedEvent(QWindowSystemInterfacePrivate::ActivatedWindowEvent*) + 618
16  org.qt-project.QtGuiVBox      	0x000000010c8072e7 QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) + 1383
17  org.qt-project.QtGuiVBox      	0x000000010c7f0feb QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 411
18  libqcocoa.dylib               	0x00000001134d70b1 QCocoaEventDispatcherPrivate::postedEventsSourceCallback(void*) + 33
19  com.apple.CoreFoundation      	0x00007fff30984b81 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
20  com.apple.CoreFoundation      	0x00007fff30984b20 __CFRunLoopDoSource0 + 103
21  com.apple.CoreFoundation      	0x00007fff309681b0 __CFRunLoopDoSources0 + 301
22  com.apple.CoreFoundation      	0x00007fff30967760 __CFRunLoopRun + 1272
23  com.apple.CoreFoundation      	0x00007fff30966fe3 CFRunLoopRunSpecific + 499
24  com.apple.HIToolbox           	0x00007fff2f4ee67d RunCurrentEventLoopInMode + 292
25  com.apple.HIToolbox           	0x00007fff2f4ee2c9 ReceiveNextEventCommon + 356
26  com.apple.HIToolbox           	0x00007fff2f4ee147 _BlockUntilNextEventMatchingListInModeWithFilter + 64
27  com.apple.AppKit              	0x00007fff2db73864 _DPSNextEvent + 990
28  com.apple.AppKit              	0x00007fff2db725d4 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1352
29  com.apple.AppKit              	0x00007fff2db6cd76 -[NSApplication run] + 658
30  libqcocoa.dylib               	0x00000001134d5eed QCocoaEventDispatcher::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 2205
31  org.qt-project.QtCoreVBox     	0x000000010c2ac791 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 401
32  org.qt-project.QtCoreVBox     	0x000000010c2b0b4a QCoreApplication::exec() + 346
33  VirtualBoxVM.dylib            	0x000000010bf70f13 TrustedMain + 1315
34  org.virtualbox.app.VirtualBoxVM	0x000000010b8a4d36 0x10b8a1000 + 15670
35  libdyld.dylib                 	0x00007fff67e412e5 start + 1

Thread 1:: nspr-1
0   libsystem_kernel.dylib        	0x00007fff67f917e6 __select + 10
1   VBoxXPCOM.dylib               	0x000000010fc058b0 0x10fb7b000 + 567472
2   VBoxXPCOM.dylib               	0x000000010fc076e5 PR_Poll + 1061
3   VBoxXPCOMIPCC.dylib           	0x0000000114c9be75 0x114c89000 + 77429
4   VBoxXPCOM.dylib               	0x000000010fc0ca96 0x10fb7b000 + 596630
5   VBoxRT.dylib                  	0x000000010b9cc6dc 0x10b8e4000 + 952028
6   VBoxRT.dylib                  	0x000000010ba7e162 0x10b8e4000 + 1679714
7   libsystem_pthread.dylib       	0x00007fff6804dd36 _pthread_start + 125
8   libsystem_pthread.dylib       	0x00007fff6804a58f thread_start + 15

Thread 2:: nspr-2
0   libsystem_kernel.dylib        	0x00007fff67f8d916 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6804e040 _pthread_cond_wait + 701
2   VBoxXPCOM.dylib               	0x000000010fc0adfe PR_WaitCondVar + 254
3   VBoxXPCOM.dylib               	0x000000010fc0b2ad PR_Wait + 61
4   VBoxXPCOMIPCC.dylib           	0x0000000114c947b8 0x114c89000 + 47032
5   VBoxXPCOM.dylib               	0x000000010fbdf209 0x10fb7b000 + 410121
6   VBoxXPCOM.dylib               	0x000000010fc0ca96 0x10fb7b000 + 596630
7   VBoxRT.dylib                  	0x000000010b9cc6dc 0x10b8e4000 + 952028
8   VBoxRT.dylib                  	0x000000010ba7e162 0x10b8e4000 + 1679714
9   libsystem_pthread.dylib       	0x00007fff6804dd36 _pthread_start + 125
10  libsystem_pthread.dylib       	0x00007fff6804a58f thread_start + 15

Thread 3:: VBoxSVCWatcher
0   libsystem_kernel.dylib        	0x00007fff67f8d916 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6804e040 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x000000010ba7aa6c RTSemEventWait + 364
3   VBoxC.dylib                   	0x0000000114dab221 0x114cb1000 + 1024545
4   VBoxRT.dylib                  	0x000000010b9cc6dc 0x10b8e4000 + 952028
5   VBoxRT.dylib                  	0x000000010ba7e162 0x10b8e4000 + 1679714
6   libsystem_pthread.dylib       	0x00007fff6804dd36 _pthread_start + 125
7   libsystem_pthread.dylib       	0x00007fff6804a58f thread_start + 15

Thread 4:: UIMainEventListeningThread
0   libsystem_kernel.dylib        	0x00007fff67f8d916 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6804e040 _pthread_cond_wait + 701
2   VBoxXPCOM.dylib               	0x000000010fc0ade7 PR_WaitCondVar + 231
3   VBoxXPCOM.dylib               	0x000000010fc0b2ad PR_Wait + 61
4   VBoxXPCOMIPCC.dylib           	0x0000000114c8e71b 0x114c89000 + 22299
5   VBoxXPCOMIPCC.dylib           	0x0000000114c8e3ed 0x114c89000 + 21485
6   VBoxXPCOMIPCC.dylib           	0x0000000114c93039 0x114c89000 + 41017
7   VBoxXPCOM.dylib               	0x000000010fbee2fd 0x10fb7b000 + 471805
8   VBoxXPCOM.dylib               	0x000000010fbed4fb 0x10fb7b000 + 468219
9   VBoxGlobal.dylib              	0x000000010d7ea862 CEventSource::GetEvent(CEventListener const&, int) + 162
10  VBoxGlobal.dylib              	0x000000010d60b3e7 0x10d559000 + 730087
11  org.qt-project.QtCoreVBox     	0x000000010c0f296b 0x10c0c9000 + 170347
12  libsystem_pthread.dylib       	0x00007fff6804dd36 _pthread_start + 125
13  libsystem_pthread.dylib       	0x00007fff6804a58f thread_start + 15

Thread 5:: UIMainEventListeningThread
0   libsystem_kernel.dylib        	0x00007fff67f8d916 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6804e040 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x000000010ba7aa6c RTSemEventWait + 364
3   VBoxC.dylib                   	0x0000000114cf2d90 0x114cb1000 + 269712
4   VBoxC.dylib                   	0x0000000114cf3fcd 0x114cb1000 + 274381
5   VBoxC.dylib                   	0x0000000114e859aa 0x114cb1000 + 1919402
6   VBoxGlobal.dylib              	0x000000010d7ea862 CEventSource::GetEvent(CEventListener const&, int) + 162
7   VBoxGlobal.dylib              	0x000000010d60b3e7 0x10d559000 + 730087
8   org.qt-project.QtCoreVBox     	0x000000010c0f296b 0x10c0c9000 + 170347
9   libsystem_pthread.dylib       	0x00007fff6804dd36 _pthread_start + 125
10  libsystem_pthread.dylib       	0x00007fff6804a58f thread_start + 15

Thread 6:: TimerLR
0   libsystem_kernel.dylib        	0x00007fff67f8d916 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6804e040 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x000000010ba7aa6c RTSemEventWait + 364
3   VBoxRT.dylib                  	0x000000010ba31b45 0x10b8e4000 + 1366853
4   VBoxRT.dylib                  	0x000000010b9cc6dc 0x10b8e4000 + 952028
5   VBoxRT.dylib                  	0x000000010ba7e162 0x10b8e4000 + 1679714
6   libsystem_pthread.dylib       	0x00007fff6804dd36 _pthread_start + 125
7   libsystem_pthread.dylib       	0x00007fff6804a58f thread_start + 15

Thread 7:: UIMainEventListeningThread
0   libsystem_kernel.dylib        	0x00007fff67f8d916 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6804e040 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x000000010ba7aa6c RTSemEventWait + 364
3   VBoxC.dylib                   	0x0000000114cf2d90 0x114cb1000 + 269712
4   VBoxC.dylib                   	0x0000000114cf3fcd 0x114cb1000 + 274381
5   VBoxC.dylib                   	0x0000000114e859aa 0x114cb1000 + 1919402
6   VBoxGlobal.dylib              	0x000000010d7ea862 CEventSource::GetEvent(CEventListener const&, int) + 162
7   VBoxGlobal.dylib              	0x000000010d60b3e7 0x10d559000 + 730087
8   org.qt-project.QtCoreVBox     	0x000000010c0f296b 0x10c0c9000 + 170347
9   libsystem_pthread.dylib       	0x00007fff6804dd36 _pthread_start + 125
10  libsystem_pthread.dylib       	0x00007fff6804a58f thread_start + 15

Thread 8:: MainHGCMthread
0   libsystem_kernel.dylib        	0x00007fff67f8d916 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6804e040 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x000000010ba7ab1b RTSemEventWait + 539
3   VBoxC.dylib                   	0x0000000114e439b5 0x114cb1000 + 1649077
4   VBoxC.dylib                   	0x0000000114e440a6 0x114cb1000 + 1650854
5   VBoxC.dylib                   	0x0000000114e484bb 0x114cb1000 + 1668283
6   VBoxC.dylib                   	0x0000000114e4378f 0x114cb1000 + 1648527
7   VBoxRT.dylib                  	0x000000010b9cc6dc 0x10b8e4000 + 952028
8   VBoxRT.dylib                  	0x000000010ba7e162 0x10b8e4000 + 1679714
9   libsystem_pthread.dylib       	0x00007fff6804dd36 _pthread_start + 125
10  libsystem_pthread.dylib       	0x00007fff6804a58f thread_start + 15

Thread 9:: EMT
0   libsystem_kernel.dylib        	0x00007fff67f8aada __ioctl + 10
1   libsystem_kernel.dylib        	0x00007fff67f8aac7 ioctl + 150
2   VBoxRT.dylib                  	0x000000010ba88d8d 0x10b8e4000 + 1723789
3   VBoxRT.dylib                  	0x000000010ba81926 SUPR3CallVMMR0Ex + 438
4   VBoxVMM.dylib                 	0x000000010f929db2 0x10f87a000 + 720306
5   VBoxVMM.dylib                 	0x000000010f928d81 0x10f87a000 + 716161
6   VBoxVMM.dylib                 	0x000000010f8c019a 0x10f87a000 + 287130
7   VBoxVMM.dylib                 	0x000000010f928556 0x10f87a000 + 714070
8   VBoxRT.dylib                  	0x000000010b9cc6dc 0x10b8e4000 + 952028
9   VBoxRT.dylib                  	0x000000010ba7e162 0x10b8e4000 + 1679714
10  libsystem_pthread.dylib       	0x00007fff6804dd36 _pthread_start + 125
11  libsystem_pthread.dylib       	0x00007fff6804a58f thread_start + 15

Thread 10:: ShClipboard
0   libsystem_kernel.dylib        	0x00007fff67f8d916 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6804e040 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x000000010ba7ab1b RTSemEventWait + 539
3   VBoxC.dylib                   	0x0000000114e439b5 0x114cb1000 + 1649077
4   VBoxC.dylib                   	0x0000000114e440a6 0x114cb1000 + 1650854
5   VBoxC.dylib                   	0x0000000114e44c4d 0x114cb1000 + 1653837
6   VBoxC.dylib                   	0x0000000114e4378f 0x114cb1000 + 1648527
7   VBoxRT.dylib                  	0x000000010b9cc6dc 0x10b8e4000 + 952028
8   VBoxRT.dylib                  	0x000000010ba7e162 0x10b8e4000 + 1679714
9   libsystem_pthread.dylib       	0x00007fff6804dd36 _pthread_start + 125
10  libsystem_pthread.dylib       	0x00007fff6804a58f thread_start + 15

Thread 11:: SHCLIP
0   libsystem_kernel.dylib        	0x00007fff67f8d916 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6804e040 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x000000010ba7b4f6 0x10b8e4000 + 1668342
3   VBoxRT.dylib                  	0x000000010b9ccee9 RTThreadUserWait + 73
4   VBoxSharedClipboard.dylib     	0x0000000117553134 0x11754f000 + 16692
5   VBoxRT.dylib                  	0x000000010b9cc6dc 0x10b8e4000 + 952028
6   VBoxRT.dylib                  	0x000000010ba7e162 0x10b8e4000 + 1679714
7   libsystem_pthread.dylib       	0x00007fff6804dd36 _pthread_start + 125
8   libsystem_pthread.dylib       	0x00007fff6804a58f thread_start + 15

Thread 12:: DragAndDropSvc
0   libsystem_kernel.dylib        	0x00007fff67f8d916 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6804e040 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x000000010ba7ab1b RTSemEventWait + 539
3   VBoxC.dylib                   	0x0000000114e439b5 0x114cb1000 + 1649077
4   VBoxC.dylib                   	0x0000000114e440a6 0x114cb1000 + 1650854
5   VBoxC.dylib                   	0x0000000114e44c4d 0x114cb1000 + 1653837
6   VBoxC.dylib                   	0x0000000114e4378f 0x114cb1000 + 1648527
7   VBoxRT.dylib                  	0x000000010b9cc6dc 0x10b8e4000 + 952028
8   VBoxRT.dylib                  	0x000000010ba7e162 0x10b8e4000 + 1679714
9   libsystem_pthread.dylib       	0x00007fff6804dd36 _pthread_start + 125
10  libsystem_pthread.dylib       	0x00007fff6804a58f thread_start + 15

Thread 13:: Timer
0   libsystem_kernel.dylib        	0x00007fff67f8d916 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6804e040 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x000000010ba7aa6c RTSemEventWait + 364
3   VBoxRT.dylib                  	0x000000010ba6d0dd 0x10b8e4000 + 1609949
4   VBoxRT.dylib                  	0x000000010b9cc6dc 0x10b8e4000 + 952028
5   VBoxRT.dylib                  	0x000000010ba7e162 0x10b8e4000 + 1679714
6   libsystem_pthread.dylib       	0x00007fff6804dd36 _pthread_start + 125
7   libsystem_pthread.dylib       	0x00007fff6804a58f thread_start + 15

Thread 14:: PDMNsTx
0   libsystem_kernel.dylib        	0x00007fff67f8e032 __semwait_signal + 10
1   libsystem_c.dylib             	0x00007fff67f110fa nanosleep + 196
2   VBoxRT.dylib                  	0x000000010ba7e313 RTThreadSleep + 67
3   VBoxVMM.dylib                 	0x000000010fa0d8aa 0x10f87a000 + 1652906
4   VBoxVMM.dylib                 	0x000000010f8e76bf 0x10f87a000 + 448191
5   VBoxRT.dylib                  	0x000000010b9cc6dc 0x10b8e4000 + 952028
6   VBoxRT.dylib                  	0x000000010ba7e162 0x10b8e4000 + 1679714
7   libsystem_pthread.dylib       	0x00007fff6804dd36 _pthread_start + 125
8   libsystem_pthread.dylib       	0x00007fff6804a58f thread_start + 15

Thread 15:: ShFolders
0   libsystem_kernel.dylib        	0x00007fff67f8d916 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6804e040 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x000000010ba7ab1b RTSemEventWait + 539
3   VBoxC.dylib                   	0x0000000114e439b5 0x114cb1000 + 1649077
4   VBoxC.dylib                   	0x0000000114e440a6 0x114cb1000 + 1650854
5   VBoxC.dylib                   	0x0000000114e44c4d 0x114cb1000 + 1653837
6   VBoxC.dylib                   	0x0000000114e4378f 0x114cb1000 + 1648527
7   VBoxRT.dylib                  	0x000000010b9cc6dc 0x10b8e4000 + 952028
8   VBoxRT.dylib                  	0x000000010ba7e162 0x10b8e4000 + 1679714
9   libsystem_pthread.dylib       	0x00007fff6804dd36 _pthread_start + 125
10  libsystem_pthread.dylib       	0x00007fff6804a58f thread_start + 15

Thread 16:: GuestControlSvc
0   libsystem_kernel.dylib        	0x00007fff67f8d916 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6804e040 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x000000010ba7ab1b RTSemEventWait + 539
3   VBoxC.dylib                   	0x0000000114e439b5 0x114cb1000 + 1649077
4   VBoxC.dylib                   	0x0000000114e440a6 0x114cb1000 + 1650854
5   VBoxC.dylib                   	0x0000000114e44c4d 0x114cb1000 + 1653837
6   VBoxC.dylib                   	0x0000000114e4378f 0x114cb1000 + 1648527
7   VBoxRT.dylib                  	0x000000010b9cc6dc 0x10b8e4000 + 952028
8   VBoxRT.dylib                  	0x000000010ba7e162 0x10b8e4000 + 1679714
9   libsystem_pthread.dylib       	0x00007fff6804dd36 _pthread_start + 125
10  libsystem_pthread.dylib       	0x00007fff6804a58f thread_start + 15

Thread 17:: GuestPropSvc
0   libsystem_kernel.dylib        	0x00007fff67f8d916 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6804e040 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x000000010ba7ab1b RTSemEventWait + 539
3   VBoxC.dylib                   	0x0000000114e439b5 0x114cb1000 + 1649077
4   VBoxC.dylib                   	0x0000000114e440a6 0x114cb1000 + 1650854
5   VBoxC.dylib                   	0x0000000114e44c4d 0x114cb1000 + 1653837
6   VBoxC.dylib                   	0x0000000114e4378f 0x114cb1000 + 1648527
7   VBoxRT.dylib                  	0x000000010b9cc6dc 0x10b8e4000 + 952028
8   VBoxRT.dylib                  	0x000000010ba7e162 0x10b8e4000 + 1679714
9   libsystem_pthread.dylib       	0x00007fff6804dd36 _pthread_start + 125
10  libsystem_pthread.dylib       	0x00007fff6804a58f thread_start + 15

Thread 18:: GstPropNtfy
0   libsystem_kernel.dylib        	0x00007fff67f8d916 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6804e040 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x000000010ba7ab1b RTSemEventWait + 539
3   VBoxRT.dylib                  	0x000000010b9ca342 RTReqQueueProcess + 146
4   VBoxGuestPropSvc.dylib        	0x000000011b786081 0x11b780000 + 24705
5   VBoxRT.dylib                  	0x000000010b9cc6dc 0x10b8e4000 + 952028
6   VBoxRT.dylib                  	0x000000010ba7e162 0x10b8e4000 + 1679714
7   libsystem_pthread.dylib       	0x00007fff6804dd36 _pthread_start + 125
8   libsystem_pthread.dylib       	0x00007fff6804a58f thread_start + 15

Thread 19:: com.apple.NSEventThread
0   libsystem_kernel.dylib        	0x00007fff67f8a166 mach_msg_trap + 10
1   libsystem_kernel.dylib        	0x00007fff67f8a6cc mach_msg + 60
2   com.apple.CoreFoundation      	0x00007fff3096836b __CFRunLoopServiceMachPort + 322
3   com.apple.CoreFoundation      	0x00007fff30967907 __CFRunLoopRun + 1695
4   com.apple.CoreFoundation      	0x00007fff30966fe3 CFRunLoopRunSpecific + 499
5   com.apple.AppKit              	0x00007fff2db7adba _NSEventThread + 132
6   libsystem_pthread.dylib       	0x00007fff6804dd36 _pthread_start + 125
7   libsystem_pthread.dylib       	0x00007fff6804a58f thread_start + 15

Thread 20:: AioMgr0-N
0   libsystem_kernel.dylib        	0x00007fff67f8d916 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6804e040 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x000000010ba7ab1b RTSemEventWait + 539
3   VBoxVMM.dylib                 	0x000000010fa0b66b 0x10f87a000 + 1644139
4   VBoxRT.dylib                  	0x000000010b9cc6dc 0x10b8e4000 + 952028
5   VBoxRT.dylib                  	0x000000010ba7e162 0x10b8e4000 + 1679714
6   libsystem_pthread.dylib       	0x00007fff6804dd36 _pthread_start + 125
7   libsystem_pthread.dylib       	0x00007fff6804a58f thread_start + 15

Thread 21:: Port0
0   libsystem_kernel.dylib        	0x00007fff67f8aada __ioctl + 10
1   libsystem_kernel.dylib        	0x00007fff67f8aac7 ioctl + 150
2   VBoxRT.dylib                  	0x000000010ba88d8d 0x10b8e4000 + 1723789
3   VBoxRT.dylib                  	0x000000010ba85e57 SUPSemEventWaitNoResume + 135
4   VBoxDD.dylib                  	0x000000011a630726 0x11a54b000 + 939814
5   VBoxVMM.dylib                 	0x000000010f8e76b3 0x10f87a000 + 448179
6   VBoxRT.dylib                  	0x000000010b9cc6dc 0x10b8e4000 + 952028
7   VBoxRT.dylib                  	0x000000010ba7e162 0x10b8e4000 + 1679714
8   libsystem_pthread.dylib       	0x00007fff6804dd36 _pthread_start + 125
9   libsystem_pthread.dylib       	0x00007fff6804a58f thread_start + 15

Thread 22:: Port1
0   libsystem_kernel.dylib        	0x00007fff67f8aada __ioctl + 10
1   libsystem_kernel.dylib        	0x00007fff67f8aac7 ioctl + 150
2   VBoxRT.dylib                  	0x000000010ba88d8d 0x10b8e4000 + 1723789
3   VBoxRT.dylib                  	0x000000010ba85e57 SUPSemEventWaitNoResume + 135
4   VBoxDD.dylib                  	0x000000011a630726 0x11a54b000 + 939814
5   VBoxVMM.dylib                 	0x000000010f8e76b3 0x10f87a000 + 448179
6   VBoxRT.dylib                  	0x000000010b9cc6dc 0x10b8e4000 + 952028
7   VBoxRT.dylib                  	0x000000010ba7e162 0x10b8e4000 + 1679714
8   libsystem_pthread.dylib       	0x00007fff6804dd36 _pthread_start + 125
9   libsystem_pthread.dylib       	0x00007fff6804a58f thread_start + 15

Thread 23:: NATRX
0   libsystem_kernel.dylib        	0x00007fff67f8d916 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6804e040 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x000000010ba7ab1b RTSemEventWait + 539
3   VBoxDD.dylib                  	0x000000011a675a09 0x11a54b000 + 1223177
4   VBoxVMM.dylib                 	0x000000010f8e76b3 0x10f87a000 + 448179
5   VBoxRT.dylib                  	0x000000010b9cc6dc 0x10b8e4000 + 952028
6   VBoxRT.dylib                  	0x000000010ba7e162 0x10b8e4000 + 1679714
7   libsystem_pthread.dylib       	0x00007fff6804dd36 _pthread_start + 125
8   libsystem_pthread.dylib       	0x00007fff6804a58f thread_start + 15

Thread 24:: NATURGRX
0   libsystem_kernel.dylib        	0x00007fff67f8d916 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6804e040 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x000000010ba7ab1b RTSemEventWait + 539
3   VBoxDD.dylib                  	0x000000011a675a69 0x11a54b000 + 1223273
4   VBoxVMM.dylib                 	0x000000010f8e76b3 0x10f87a000 + 448179
5   VBoxRT.dylib                  	0x000000010b9cc6dc 0x10b8e4000 + 952028
6   VBoxRT.dylib                  	0x000000010ba7e162 0x10b8e4000 + 1679714
7   libsystem_pthread.dylib       	0x00007fff6804dd36 _pthread_start + 125
8   libsystem_pthread.dylib       	0x00007fff6804a58f thread_start + 15

Thread 25:: HOSTRES
0   libsystem_kernel.dylib        	0x00007fff67f8d916 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6804e040 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x000000010ba7ab1b RTSemEventWait + 539
3   VBoxRT.dylib                  	0x000000010b9ca342 RTReqQueueProcess + 146
4   VBoxDD.dylib                  	0x000000011a675ad1 0x11a54b000 + 1223377
5   VBoxVMM.dylib                 	0x000000010f8e76b3 0x10f87a000 + 448179
6   VBoxRT.dylib                  	0x000000010b9cc6dc 0x10b8e4000 + 952028
7   VBoxRT.dylib                  	0x000000010ba7e162 0x10b8e4000 + 1679714
8   libsystem_pthread.dylib       	0x00007fff6804dd36 _pthread_start + 125
9   libsystem_pthread.dylib       	0x00007fff6804a58f thread_start + 15

Thread 26:: NAT
0   libsystem_kernel.dylib        	0x00007fff67f925be poll + 10
1   VBoxDD.dylib                  	0x000000011a675c14 0x11a54b000 + 1223700
2   VBoxVMM.dylib                 	0x000000010f8e76b3 0x10f87a000 + 448179
3   VBoxRT.dylib                  	0x000000010b9cc6dc 0x10b8e4000 + 952028
4   VBoxRT.dylib                  	0x000000010ba7e162 0x10b8e4000 + 1679714
5   libsystem_pthread.dylib       	0x00007fff6804dd36 _pthread_start + 125
6   libsystem_pthread.dylib       	0x00007fff6804a58f thread_start + 15

Thread 27:: AMCP Logging Spool
0   libsystem_kernel.dylib        	0x00007fff67f8a1a2 semaphore_wait_trap + 10
1   com.apple.audio.caulk         	0x00007fff64040ec6 caulk::mach::semaphore::wait() + 16
2   com.apple.audio.caulk         	0x00007fff6403c442 caulk::semaphore::timed_wait(double) + 106
3   com.apple.audio.caulk         	0x00007fff6403fa14 caulk::concurrent::details::worker_thread::run() + 30
4   com.apple.audio.caulk         	0x00007fff6403fb64 void* caulk::thread_proxy<std::__1::tuple<caulk::thread::attributes, void (caulk::concurrent::details::worker_thread::*)(), std::__1::tuple<caulk::concurrent::details::worker_thread*> > >(void*) + 45
5   libsystem_pthread.dylib       	0x00007fff6804dd36 _pthread_start + 125
6   libsystem_pthread.dylib       	0x00007fff6804a58f thread_start + 15

Thread 28:
0   libsystem_kernel.dylib        	0x00007fff67f8a1a2 semaphore_wait_trap + 10
1   com.apple.audio.caulk         	0x00007fff64040ec6 caulk::mach::semaphore::wait() + 16
2   com.apple.audio.caulk         	0x00007fff6403c442 caulk::semaphore::timed_wait(double) + 106
3   com.apple.audio.caulk         	0x00007fff6403fa14 caulk::concurrent::details::worker_thread::run() + 30
4   com.apple.audio.caulk         	0x00007fff6403fb64 void* caulk::thread_proxy<std::__1::tuple<caulk::thread::attributes, void (caulk::concurrent::details::worker_thread::*)(), std::__1::tuple<caulk::concurrent::details::worker_thread*> > >(void*) + 45
5   libsystem_pthread.dylib       	0x00007fff6804dd36 _pthread_start + 125
6   libsystem_pthread.dylib       	0x00007fff6804a58f thread_start + 15

Thread 29:: VUsbPeriodFrm
0   libsystem_kernel.dylib        	0x00007fff67f8d916 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6804e040 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x000000010ba7b631 0x10b8e4000 + 1668657
3   VBoxRT.dylib                  	0x000000010ba7b3b3 0x10b8e4000 + 1668019
4   VBoxDD.dylib                  	0x000000011a603902 0x11a54b000 + 755970
5   VBoxVMM.dylib                 	0x000000010f8e76b3 0x10f87a000 + 448179
6   VBoxRT.dylib                  	0x000000010b9cc6dc 0x10b8e4000 + 952028
7   VBoxRT.dylib                  	0x000000010ba7e162 0x10b8e4000 + 1679714
8   libsystem_pthread.dylib       	0x00007fff6804dd36 _pthread_start + 125
9   libsystem_pthread.dylib       	0x00007fff6804a58f thread_start + 15

Thread 30:: hdaAIO4
0   libsystem_kernel.dylib        	0x00007fff67f8d916 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6804e040 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x000000010ba7ab1b RTSemEventWait + 539
3   VBoxDD.dylib                  	0x000000011a664091 0x11a54b000 + 1151121
4   VBoxRT.dylib                  	0x000000010b9cc6dc 0x10b8e4000 + 952028
5   VBoxRT.dylib                  	0x000000010ba7e162 0x10b8e4000 + 1679714
6   libsystem_pthread.dylib       	0x00007fff6804dd36 _pthread_start + 125
7   libsystem_pthread.dylib       	0x00007fff6804a58f thread_start + 15

Thread 31:: nspr-3
0   libsystem_kernel.dylib        	0x00007fff67f8d916 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6804e040 _pthread_cond_wait + 701
2   VBoxXPCOM.dylib               	0x000000010fc0adfe PR_WaitCondVar + 254
3   VBoxXPCOM.dylib               	0x000000010fc0b2ad PR_Wait + 61
4   VBoxXPCOMIPCC.dylib           	0x0000000114c947b8 0x114c89000 + 47032
5   VBoxXPCOM.dylib               	0x000000010fbdf209 0x10fb7b000 + 410121
6   VBoxXPCOM.dylib               	0x000000010fc0ca96 0x10fb7b000 + 596630
7   VBoxRT.dylib                  	0x000000010b9cc6dc 0x10b8e4000 + 952028
8   VBoxRT.dylib                  	0x000000010ba7e162 0x10b8e4000 + 1679714
9   libsystem_pthread.dylib       	0x00007fff6804dd36 _pthread_start + 125
10  libsystem_pthread.dylib       	0x00007fff6804a58f thread_start + 15

Thread 32:: CAQUEUE
0   libsystem_kernel.dylib        	0x00007fff67f8a166 mach_msg_trap + 10
1   libsystem_kernel.dylib        	0x00007fff67f8a6cc mach_msg + 60
2   com.apple.CoreFoundation      	0x00007fff3096836b __CFRunLoopServiceMachPort + 322
3   com.apple.CoreFoundation      	0x00007fff30967907 __CFRunLoopRun + 1695
4   com.apple.CoreFoundation      	0x00007fff30966fe3 CFRunLoopRunSpecific + 499
5   VBoxDD.dylib                  	0x000000011a6732e5 0x11a54b000 + 1213157
6   VBoxRT.dylib                  	0x000000010b9cc6dc 0x10b8e4000 + 952028
7   VBoxRT.dylib                  	0x000000010ba7e162 0x10b8e4000 + 1679714
8   libsystem_pthread.dylib       	0x00007fff6804dd36 _pthread_start + 125
9   libsystem_pthread.dylib       	0x00007fff6804a58f thread_start + 15

Thread 33:
0   libsystem_pthread.dylib       	0x00007fff6804a56c start_wqthread + 0

Thread 34:
0   libsystem_pthread.dylib       	0x00007fff6804a56c start_wqthread + 0

Thread 35:
0   libsystem_pthread.dylib       	0x00007fff6804a56c start_wqthread + 0

Thread 36:
0   libsystem_pthread.dylib       	0x00007fff6804a56c start_wqthread + 0

Thread 0 crashed with X86 Thread State (64-bit):
  rax: 0x00000001137fead8  rbx: 0x00007fd74e1a83d8  rcx: 0x0000000000000000  rdx: 0x0000000000000001
  rdi: 0x00000001137fead8  rsi: 0x00007fd74e1a83d8  rbp: 0x00007ffee435b630  rsp: 0x00007ffee435b630
   r8: 0x0000000000000000   r9: 0x000000000000007f  r10: 0x0000000115230d58  r11: 0xffff8029c5656700
  r12: 0x00000001137fead8  r13: 0x0000000000000000  r14: 0x00000001137feac4  r15: 0x0000000000000001
  rip: 0x00007fff6803fdc6  rfl: 0x0000000000010246  cr2: 0x00000001137fead8
  
Logical CPU:     6
Error Code:      0x00000006 (no mapping for user data read)
Trap Number:     14


Binary Images:
       0x10b8a1000 -        0x10b8c2ff7 +org.virtualbox.app.VirtualBoxVM (6.0.14 - 6.0.14) <0ED710D1-15CE-3432-97C3-40B0DD778F9B> /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM
       0x10b8e4000 -        0x10be455e7 +VBoxRT.dylib (0) <C5B1604B-E6AF-38CF-96B2-97ED25DFBC4A> /Applications/VirtualBox.app/Contents/MacOS/VBoxRT.dylib
       0x10bf69000 -        0x10c056ff7 +VirtualBoxVM.dylib (0) <5397318E-6C31-3E12-9A49-98E3EA9EDDBE> /Applications/VirtualBox.app/Contents/MacOS/VirtualBoxVM.dylib
       0x10c0b4000 -        0x10c0bdff7 +org.qt-project.QtMacExtrasVBox (5.6 - 5.6.3) <AC6F0DC8-BF41-3A20-B803-656B301B8CDF> /Applications/VirtualBox.app/Contents/Frameworks/QtMacExtrasVBox.framework/Versions/5/QtMacExtrasVBox
       0x10c0c9000 -        0x10c5f0ff7 +org.qt-project.QtCoreVBox (5.6 - 5.6.3) <3A7A08E0-9422-393E-BD97-FD15E751434C> /Applications/VirtualBox.app/Contents/Frameworks/QtCoreVBox.framework/Versions/5/QtCoreVBox
       0x10c6dc000 -        0x10c76cb5f  dyld (733.6) <DAFEA246-2F9A-3DCB-A37C-4246D4F92770> /usr/lib/dyld
       0x10c7e0000 -        0x10ccbbff7 +org.qt-project.QtGuiVBox (5.6 - 5.6.3) <80F8D761-23D7-381D-B8D5-1C0C130F7876> /Applications/VirtualBox.app/Contents/Frameworks/QtGuiVBox.framework/Versions/5/QtGuiVBox
       0x10cdbc000 -        0x10d2c5fff +org.qt-project.QtWidgetsVBox (5.6 - 5.6.3) <5DFD063A-1901-39D3-90FB-138EFE7C6A9E> /Applications/VirtualBox.app/Contents/Frameworks/QtWidgetsVBox.framework/Versions/5/QtWidgetsVBox
       0x10d437000 -        0x10d46bfff +org.qt-project.QtPrintSupportVBox (5.6 - 5.6.3) <4C8D48EF-FC21-3BE7-895F-584399F0B308> /Applications/VirtualBox.app/Contents/Frameworks/QtPrintSupportVBox.framework/Versions/5/QtPrintSupportVBox
       0x10d492000 -        0x10d4d1fff +org.qt-project.QtOpenGLVBox (5.6 - 5.6.3) <F75D0235-BFE7-3966-A3C4-CFEA758B9A71> /Applications/VirtualBox.app/Contents/Frameworks/QtOpenGLVBox.framework/Versions/5/QtOpenGLVBox
       0x10d4f7000 -        0x10d54afff +VBoxDDU.dylib (0) <425E29E4-3654-3466-9FA4-74595831D829> /Applications/VirtualBox.app/Contents/MacOS/VBoxDDU.dylib
       0x10d559000 -        0x10f68ffff +VBoxGlobal.dylib (0) <CC52AD54-E3B4-3B53-9E1A-7A8E944E35FF> /Applications/VirtualBox.app/Contents/MacOS/VBoxGlobal.dylib
       0x10f87a000 -        0x10fafcfff +VBoxVMM.dylib (0) <02F0512A-A779-3AC5-896B-A824F1A0F97B> /Applications/VirtualBox.app/Contents/MacOS/VBoxVMM.dylib
       0x10fb7b000 -        0x10fc2cff7 +VBoxXPCOM.dylib (0) <4B77E0EB-C98A-38B9-9545-903EDE0007DD> /Applications/VirtualBox.app/Contents/MacOS/VBoxXPCOM.dylib
       0x1134b3000 -        0x1135f2fff +libqcocoa.dylib (0) <FA226E50-20A3-3C6D-B04E-9262D65300BC> /Applications/VirtualBox.app/Contents/plugins/platforms/libqcocoa.dylib
       0x114c7b000 -        0x114c7e047  libobjc-trampolines.dylib (781) <6CF41A53-C75E-3AAA-9E47-E35C1EE56CE4> /usr/lib/libobjc-trampolines.dylib
       0x114c89000 -        0x114ca0fff +VBoxXPCOMIPCC.dylib (0) <09CCD92F-2AB6-3E5D-B826-A374C8B253D8> /Applications/VirtualBox.app/Contents/MacOS/components/VBoxXPCOMIPCC.dylib
       0x114cb1000 -        0x1150a9fff +VBoxC.dylib (0) <5721F352-F17F-3D3D-A25E-D16DFCDAA945> /Applications/VirtualBox.app/Contents/MacOS/components/VBoxC.dylib
       0x1150f8000 -        0x1150fbff7 +VBoxSVCM.dylib (0) <BA39D3BF-CEA7-3321-8615-AE868B2B95C4> /Applications/VirtualBox.app/Contents/MacOS/components/VBoxSVCM.dylib
       0x11521a000 -        0x11522cfff  com.apple.iokit.IOHIDLib (2.0.0 - 2.0.0) <0CBAD74B-19D4-3410-95CB-445D773F8A28> /System/Library/Extensions/IOHIDFamily.kext/Contents/PlugIns/IOHIDLib.plugin/Contents/MacOS/IOHIDLib
       0x1155a3000 -        0x1155abff3  com.apple.iokit.IOUSBLib (900.4.2 - 900.4.2) <F72291D9-8D97-3AD1-8DCC-D671C7F3EFF1> /System/Library/Extensions/IOUSBHostFamily.kext/Contents/PlugIns/IOUSBLib.bundle/Contents/MacOS/IOUSBLib
       0x11754f000 -        0x117554fff +VBoxSharedClipboard.dylib (0) <DFB36DFF-B6DC-3221-850E-88F48A842373> /Applications/VirtualBox.app/Contents/MacOS/VBoxSharedClipboard.dylib
       0x11755c000 -        0x117563fff +VBoxDragAndDropSvc.dylib (0) <B77C4219-B37E-31DB-B6B5-93C0DFDC68FE> /Applications/VirtualBox.app/Contents/MacOS/VBoxDragAndDropSvc.dylib
       0x11a54b000 -        0x11a89cfff +VBoxDD.dylib (0) <01A23CCD-DFCC-3BBD-AB92-9C7D73D4622D> /Applications/VirtualBox.app/Contents/MacOS/VBoxDD.dylib
       0x11af38000 -        0x11af8fff7 +VBoxDD2.dylib (0) <7958A7DF-CB44-35A1-8647-1466490844F0> /Applications/VirtualBox.app/Contents/MacOS/VBoxDD2.dylib
       0x11b630000 -        0x11b63dff7 +VBoxSharedFolders.dylib (0) <AFAA8860-B157-36F9-BB5B-CDD3828C9203> /Applications/VirtualBox.app/Contents/MacOS/VBoxSharedFolders.dylib
       0x11b773000 -        0x11b778ff7 +VBoxGuestControlSvc.dylib (0) <292B1CFD-F5BC-3258-86B9-6317E69B1703> /Applications/VirtualBox.app/Contents/MacOS/VBoxGuestControlSvc.dylib
       0x11b780000 -        0x11b787fff +VBoxGuestPropSvc.dylib (0) <58CA2692-E844-3B5D-BC83-478DFCE69960> /Applications/VirtualBox.app/Contents/MacOS/VBoxGuestPropSvc.dylib
       0x1c89ea000 -        0x1c8b46fff  com.apple.audio.units.Components (1.14 - 1.14) <A5AC33CF-21E6-38FB-9A8B-48CD77AA336C> /System/Library/Components/CoreAudio.component/Contents/MacOS/CoreAudio
    0x7fff2500a000 -     0x7fff25216ff7  com.apple.RawCamera.bundle (9.00.1 - 1310.23) <A0E1BB1F-4D68-3415-90E8-79ACA52791A8> /System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera
    0x7fff25219000 -     0x7fff25339ff5  com.apple.AMDMTLBronzeDriver (3.2.24 - 3.0.2) <63C45CEB-4AD1-396E-90C5-9A09B90C2584> /System/Library/Extensions/AMDMTLBronzeDriver.bundle/Contents/MacOS/AMDMTLBronzeDriver
    0x7fff2878f000 -     0x7fff28822ffb  com.apple.driver.AppleIntelHD5000GraphicsMTLDriver (14.2.16 - 14.0.2) <C52C62F0-1280-34FE-9086-8EDADE7D16CA> /System/Library/Extensions/AppleIntelHD5000GraphicsMTLDriver.bundle/Contents/MacOS/AppleIntelHD5000GraphicsMTLDriver
    0x7fff2c312000 -     0x7fff2c316ffb  com.apple.agl (3.3.3 - AGL-3.3.3) <2DAAE917-6792-35B7-8BCE-C785ACDF8174> /System/Library/Frameworks/AGL.framework/Versions/A/AGL
    0x7fff2c6fd000 -     0x7fff2c6fdfff  com.apple.Accelerate (1.11 - Accelerate 1.11) <956D070C-B522-3A08-891A-CAD6BA4082D1> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
    0x7fff2c6fe000 -     0x7fff2c714ff7  libCGInterfaces.dylib (524.2) <23142415-0CD0-3020-B17E-F600C3889856> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/Libraries/libCGInterfaces.dylib
    0x7fff2c715000 -     0x7fff2cd80fdf  com.apple.vImage (8.1 - 524.2) <DCF3349F-1159-3F46-81E0-C18E041DC940> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage
    0x7fff2cd81000 -     0x7fff2cfe9fff  libBLAS.dylib (1303) <B950B953-116A-3C78-91A9-F983F61BC795> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib
    0x7fff2cfea000 -     0x7fff2d2d9ff7  libBNNS.dylib (144.40.3) <BAE2A5E4-14A1-3C54-86DF-888FA26C745E> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBNNS.dylib
    0x7fff2d2db000 -     0x7fff2d680fff  libLAPACK.dylib (1303) <5C248B39-F233-3074-A3A5-AF8F436FBF87> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib
    0x7fff2d681000 -     0x7fff2d696ff8  libLinearAlgebra.dylib (1303) <3AEC87AB-568C-3D88-959A-D6D8C2776FEC> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLinearAlgebra.dylib
    0x7fff2d697000 -     0x7fff2d69cff3  libQuadrature.dylib (7) <7EE59014-8FC5-3369-868B-8A87E590BF78> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libQuadrature.dylib
    0x7fff2d69d000 -     0x7fff2d70dfff  libSparse.dylib (103) <093F97A4-47DE-38DF-BB7A-FF5A3FB0BB3B> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparse.dylib
    0x7fff2d70e000 -     0x7fff2d720fef  libSparseBLAS.dylib (1303) <4536B3F7-7017-36F5-B500-1A63F691CE03> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparseBLAS.dylib
    0x7fff2d721000 -     0x7fff2d8faffb  libvDSP.dylib (735) <E849AEB0-2995-38A4-B0C3-4ACEAF434D12> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib
    0x7fff2d8fb000 -     0x7fff2d9b6fd3  libvMisc.dylib (735) <18B48679-444E-3680-A9B2-006A8D1DE3EB> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib
    0x7fff2d9b7000 -     0x7fff2d9b7fff  com.apple.Accelerate.vecLib (3.11 - vecLib 3.11) <79C1A1C7-E97A-3B7A-8737-444B402A7AA0> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib
    0x7fff2d9b8000 -     0x7fff2da17ffc  com.apple.Accounts (113 - 113) <93F6714C-3028-3F7B-AA9B-82ED89D20D88> /System/Library/Frameworks/Accounts.framework/Versions/A/Accounts
    0x7fff2db5c000 -     0x7fff2e914ffe  com.apple.AppKit (6.9 - 1894.10.126) <76EB4086-CA3D-3448-8CE0-9812F9A94F3A> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
    0x7fff2e964000 -     0x7fff2e964fff  com.apple.ApplicationServices (48 - 50) <0748E453-524B-33BA-806B-22786DED2958> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices
    0x7fff2e965000 -     0x7fff2e9d0fff  com.apple.ApplicationServices.ATS (377 - 493) <CF8434BF-B51D-3A68-B6FC-AFB0765530A2> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS
    0x7fff2ea69000 -     0x7fff2eaa7ffa  libFontRegistry.dylib (274) <A512DEE5-A697-3EE6-AF9D-606C9D9156A0> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib
    0x7fff2eb02000 -     0x7fff2eb31ff7  com.apple.ATSUI (1.0 - 1) <50DC5F09-5336-3718-AEE9-490773BA3070> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATSUI.framework/Versions/A/ATSUI
    0x7fff2eb32000 -     0x7fff2eb36ff3  com.apple.ColorSyncLegacy (4.13.0 - 1) <D4F7C969-FE2C-3036-94E3-FD2882F89C6F> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSyncLegacy.framework/Versions/A/ColorSyncLegacy
    0x7fff2ebd1000 -     0x7fff2ec27ffa  com.apple.HIServices (1.22 - 672) <0B1FD2E8-DEBD-3ED3-82F7-E0F80F21621A> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices
    0x7fff2ec28000 -     0x7fff2ec36fff  com.apple.LangAnalysis (1.7.0 - 1.7.0) <72ECDBB9-F607-3FB3-ABC3-882C9EFB3245> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis
    0x7fff2ec37000 -     0x7fff2ec7cff2  com.apple.print.framework.PrintCore (15 - 516) <78F4A9D5-82F5-3578-A78F-CDD438DB6A6C> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore
    0x7fff2ec7d000 -     0x7fff2ec87fff  com.apple.QD (4.0 - 413) <63CCC6D7-659A-341A-A8A4-55B596EEFE9C> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD
    0x7fff2ec88000 -     0x7fff2ec95ff0  com.apple.speech.synthesis.framework (9.0.22 - 9.0.22) <202F6033-A76D-3B2C-9BA9-9CCF4493AB4D> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis
    0x7fff2ec96000 -     0x7fff2ed76ff2  com.apple.audio.toolbox.AudioToolbox (1.14 - 1.14) <CAE6B655-8D07-3040-811E-CE5DE42249AE> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
    0x7fff2ed78000 -     0x7fff2ed78fff  com.apple.audio.units.AudioUnit (1.14 - 1.14) <FE7A9727-7F3F-3E0F-B827-DF421993ED12> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
    0x7fff2f0ee000 -     0x7fff2f465ffb  com.apple.CFNetwork (1120 - 1120) <5EA797F3-2F7A-3E0C-8DBC-DBE145004EC5> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
    0x7fff2f4df000 -     0x7fff2f4dffff  com.apple.Carbon (160 - 162) <56A09CBE-D5EB-3918-B42B-B3ABFF52E1D1> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
    0x7fff2f4e0000 -     0x7fff2f4e3ffb  com.apple.CommonPanels (1.2.6 - 101) <9286951D-8B2F-3A4B-86B2-767AFCC6A591> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels
    0x7fff2f4e4000 -     0x7fff2f7d8ff3  com.apple.HIToolbox (2.1.1 - 993.4) <AB2DC9D2-6A2A-3EB0-8ED9-8053CFEEC0A9> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox
    0x7fff2f7d9000 -     0x7fff2f7dcff3  com.apple.help (1.3.8 - 68) <64630D33-B292-3FD1-A3B7-AE98D4157EF1> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help
    0x7fff2f7dd000 -     0x7fff2f7e2ff7  com.apple.ImageCapture (9.0 - 1600.18) <4B628CBB-65EC-3A36-8EBB-2F9D7D328744> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture
    0x7fff2f7e3000 -     0x7fff2f7e3fff  com.apple.ink.framework (10.15 - 227) <ED29C75F-6E14-352E-ACB9-AA899E2F5429> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink
    0x7fff2f7e4000 -     0x7fff2f7feff2  com.apple.openscripting (1.7 - 185.1) <D300E418-CF0F-3127-BCBA-A7553F2F1E88> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting
    0x7fff2f81f000 -     0x7fff2f81ffff  com.apple.print.framework.Print (15 - 271) <4DDF3DC5-A69B-3BB8-B5F3-42ECC341A0B4> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print
    0x7fff2f820000 -     0x7fff2f822ff7  com.apple.securityhi (9.0 - 55008) <8E09C68A-87BB-3D55-A52F-AB1B249D06F8> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI
    0x7fff2f823000 -     0x7fff2f829ff7  com.apple.speech.recognition.framework (6.0.3 - 6.0.3) <E2CECD92-568A-3C7A-AD98-D99CEF1BBCBF> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition
    0x7fff2f9c4000 -     0x7fff2f9c4fff  com.apple.Cocoa (6.11 - 23) <EB4AD4EA-3212-385A-876E-9F8B30F8CA56> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
    0x7fff2f9d2000 -     0x7fff2fbbdff7  com.apple.ColorSync (4.13.0 - 3394.3) <DCAECEC5-F7D0-3A28-AE9D-3FA59CC9FB26> /System/Library/Frameworks/ColorSync.framework/Versions/A/ColorSync
    0x7fff2fea7000 -     0x7fff303b6ffa  com.apple.audio.CoreAudio (5.0 - 5.0) <73C7F0DD-8919-3056-AB1F-67705F942A04> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
    0x7fff30409000 -     0x7fff30440ff0  com.apple.CoreBluetooth (1.0 - 1) <E57B1D4A-DF7A-37F3-833A-CD440EB58685> /System/Library/Frameworks/CoreBluetooth.framework/Versions/A/CoreBluetooth
    0x7fff30441000 -     0x7fff3081fffc  com.apple.CoreData (120 - 973.1) <AC3856BC-894E-30C4-BA99-25C06A3D9FE8> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
    0x7fff30820000 -     0x7fff3092cff6  com.apple.CoreDisplay (1.0 - 186.2.4) <AD10EEEB-9A5F-3904-A487-50F13E4B2357> /System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay
    0x7fff3092d000 -     0x7fff30dacfe7  com.apple.CoreFoundation (6.9 - 1673.126) <15D61616-B29B-3BDB-8624-4B84A4956485> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
    0x7fff30dae000 -     0x7fff31426ff0  com.apple.CoreGraphics (2.0 - 1348.12.4.3) <B8D7910C-0C72-315F-8CE1-C257FD0ADD84> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics
    0x7fff31434000 -     0x7fff31791ff5  com.apple.CoreImage (15.0.0 - 910.8) <CE3DB305-25FF-31FE-9334-C2370473BAAF> /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage
    0x7fff31b55000 -     0x7fff31c2fffc  com.apple.CoreMedia (1.0 - 2510.17.4.6) <A455F944-F862-3668-AA2C-008106F9814F> /System/Library/Frameworks/CoreMedia.framework/Versions/A/CoreMedia
    0x7fff31d1a000 -     0x7fff31d1afff  com.apple.CoreServices (1069.11 - 1069.11) <C8F86BE7-AAED-30A6-BBC2-550446137E7C> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
    0x7fff31d1b000 -     0x7fff31da0ff7  com.apple.AE (838 - 838) <3301AF1B-D178-306A-9641-B57AA03FB1BE> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE
    0x7fff31da1000 -     0x7fff32082fff  com.apple.CoreServices.CarbonCore (1217 - 1217) <FAA1467B-6D39-3EBE-9810-A4DF49478F10> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
    0x7fff32083000 -     0x7fff320d0ffd  com.apple.DictionaryServices (1.2 - 323) <C1798F09-36D3-3C8E-AF72-A3DE63962AF1> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices
    0x7fff320d1000 -     0x7fff320d9fff  com.apple.CoreServices.FSEvents (1268.40.5 - 1268.40.5) <9BB76885-7CD7-3369-B759-33F7E5DA5392> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/FSEvents.framework/Versions/A/FSEvents
    0x7fff320da000 -     0x7fff32313ff0  com.apple.LaunchServices (1069.11 - 1069.11) <88F59BD5-412A-35EE-AD45-E6BF80B24891> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices
    0x7fff32314000 -     0x7fff323acff9  com.apple.Metadata (10.7.0 - 2074.4) <028AC15A-35B7-3E1F-BCDC-470C8EA0CA09> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata
    0x7fff323ad000 -     0x7fff323daff7  com.apple.CoreServices.OSServices (1069.11 - 1069.11) <A667F007-A599-3869-99F7-1F8460011015> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices
    0x7fff323db000 -     0x7fff32442fff  com.apple.SearchKit (1.4.1 - 1.4.1) <F0A931E4-0C31-36BA-8DD7-01FDF9813FB7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit
    0x7fff32443000 -     0x7fff32467ffd  com.apple.coreservices.SharedFileList (131 - 131) <62C3066A-3991-313F-AE2D-75B2B5934D52> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SharedFileList.framework/Versions/A/SharedFileList
    0x7fff3278f000 -     0x7fff32943ff6  com.apple.CoreText (643.1.1.5 - 643.1.1.5) <4525DC61-0B5B-33B2-A249-68C6A1267EE7> /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText
    0x7fff32944000 -     0x7fff32988fff  com.apple.CoreVideo (1.8 - 334.0) <52692CD0-764F-3D77-9087-2825ED39AD0F> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
    0x7fff32989000 -     0x7fff32a16ff1  com.apple.framework.CoreWLAN (13.0 - 1455.3) <3F7DCCA2-A5E2-3196-B2C7-31491192E75C> /System/Library/Frameworks/CoreWLAN.framework/Versions/A/CoreWLAN
    0x7fff32bdc000 -     0x7fff32be7ff7  com.apple.DirectoryService.Framework (10.15 - 220.40.1) <71100385-C865-3DEE-9B4E-B78E918E542B> /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryService
    0x7fff32be8000 -     0x7fff32c93ff0  com.apple.DiscRecording (9.0.3 - 9030.4.5) <F200BFE6-5AF1-34BA-8A87-B06753141358> /System/Library/Frameworks/DiscRecording.framework/Versions/A/DiscRecording
    0x7fff32cb8000 -     0x7fff32cbeff7  com.apple.DiskArbitration (2.7 - 2.7) <A3D2B0A0-3C72-3893-87BF-D45FE398A905> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
    0x7fff32eb1000 -     0x7fff32fd8ff7  com.apple.FileProvider (257 - 257) <E6755796-E58D-3C24-A0E9-0029521120C4> /System/Library/Frameworks/FileProvider.framework/Versions/A/FileProvider
    0x7fff32ff0000 -     0x7fff333b7ff4  com.apple.Foundation (6.9 - 1673.126) <470C2315-3047-39BB-BB6B-2C620087091C> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
    0x7fff33424000 -     0x7fff33474ff3  com.apple.GSS (4.0 - 2.0) <A149061D-5893-35B5-AE7F-BA889DFEADB2> /System/Library/Frameworks/GSS.framework/Versions/A/GSS
    0x7fff335ae000 -     0x7fff336c6ff8  com.apple.Bluetooth (7.0.1 - 7.0.1f1) <61A2BDF8-E3AC-3714-A967-92404AC52389> /System/Library/Frameworks/IOBluetooth.framework/Versions/A/IOBluetooth
    0x7fff3372d000 -     0x7fff337d0ffb  com.apple.framework.IOKit (2.0.2 - 1726.41.1) <FBB4A97B-D7CF-3B8C-932D-672343D63260> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
    0x7fff337d2000 -     0x7fff337e2ff4  com.apple.IOSurface (269.6 - 269.6) <DB88C9C2-0F53-3C77-98F0-1D8A1DFA9CB1> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface
    0x7fff33859000 -     0x7fff339b5ffe  com.apple.ImageIO.framework (3.3.0 - 1972.11.4.4) <2809F8D6-7B13-3703-B266-C5B7A6B62D97> /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO
    0x7fff339b6000 -     0x7fff339b9fff  libGIF.dylib (1972.11.4.4) <2BFC7FDD-4A4F-323C-B60A-3B4AE526F7CE> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib
    0x7fff339ba000 -     0x7fff33a74fef  libJP2.dylib (1972.11.4.4) <214BCCF5-2A06-3B4A-B2B8-4ECCB4B32D1C> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib
    0x7fff33a75000 -     0x7fff33a99fef  libJPEG.dylib (1972.11.4.4) <DBE9F84B-D9A2-3044-BFE2-B3853025FD9F> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib
    0x7fff33d17000 -     0x7fff33d31fe7  libPng.dylib (1972.11.4.4) <BD63D82F-55E5-32DB-96F9-8D7A3CDDA272> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib
    0x7fff33d32000 -     0x7fff33d33fff  libRadiance.dylib (1972.11.4.4) <2454AEBE-BE87-3D0F-BE68-6ECA3FCA361C> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib
    0x7fff33d34000 -     0x7fff33d7dfff  libTIFF.dylib (1972.11.4.4) <73A90FA4-9A51-3653-8F14-2EBBFEED3F78> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib
    0x7fff351a2000 -     0x7fff351b4ff3  com.apple.Kerberos (3.0 - 1) <8018F664-0026-3CC3-8685-3E2FE0BF2C7F> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos
    0x7fff351b5000 -     0x7fff351b5fff  libHeimdalProxy.dylib (77) <51DB9CFB-808F-32E8-BB34-39F6702DBDED> /System/Library/Frameworks/Kerberos.framework/Versions/A/Libraries/libHeimdalProxy.dylib
    0x7fff351b6000 -     0x7fff351ecfff  com.apple.LDAPFramework (2.4.28 - 194.5) <33F235C9-B0D4-3005-B395-DACE6DD93855> /System/Library/Frameworks/LDAP.framework/Versions/A/LDAP
    0x7fff35548000 -     0x7fff35552fff  com.apple.MediaAccessibility (1.0 - 125) <DD6304A2-1692-3C69-9FEA-B51F92510D5B> /System/Library/Frameworks/MediaAccessibility.framework/Versions/A/MediaAccessibility
    0x7fff3561e000 -     0x7fff35d61ff7  com.apple.MediaToolbox (1.0 - 2510.17.4.6) <3F852775-C302-3EE8-8631-31D96375BD73> /System/Library/Frameworks/MediaToolbox.framework/Versions/A/MediaToolbox
    0x7fff35d63000 -     0x7fff35e26ff9  com.apple.Metal (212.2.3 - 212.2.3) <AA7DE079-2DFD-3E9F-A041-464CFBE1ABAE> /System/Library/Frameworks/Metal.framework/Versions/A/Metal
    0x7fff35e43000 -     0x7fff35e7fff3  com.apple.MetalPerformanceShaders.MPSCore (1.0 - 1) <FB95B500-E5A3-3FAD-882E-D12FD9CA0964> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSCore.framework/Versions/A/MPSCore
    0x7fff35e80000 -     0x7fff35f06fe6  com.apple.MetalPerformanceShaders.MPSImage (1.0 - 1) <C0E349E7-ADE3-3353-8CFF-3DAD653F810E> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSImage.framework/Versions/A/MPSImage
    0x7fff35f07000 -     0x7fff35f2bff8  com.apple.MetalPerformanceShaders.MPSMatrix (1.0 - 1) <8665FDF1-210F-3A8C-9D5D-FA0C49FD8C8C> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSMatrix.framework/Versions/A/MPSMatrix
    0x7fff35f2c000 -     0x7fff35f41fff  com.apple.MetalPerformanceShaders.MPSNDArray (1.0 - 1) <EE7CF802-BF7F-3EEC-9EC2-26A3B3432275> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSNDArray.framework/Versions/A/MPSNDArray
    0x7fff35f42000 -     0x7fff360a1ff4  com.apple.MetalPerformanceShaders.MPSNeuralNetwork (1.0 - 1) <46C9BDBB-1FB9-3E1A-A02C-818D16E472D9> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSNeuralNetwork.framework/Versions/A/MPSNeuralNetwork
    0x7fff360a2000 -     0x7fff360f0fff  com.apple.MetalPerformanceShaders.MPSRayIntersector (1.0 - 1) <7CFEE008-E1AD-30FE-B0B7-9A7459701234> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSRayIntersector.framework/Versions/A/MPSRayIntersector
    0x7fff360f1000 -     0x7fff360f2ff5  com.apple.MetalPerformanceShaders.MetalPerformanceShaders (1.0 - 1) <241617D0-E5E7-3E36-971E-E278D15990A9> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/MetalPerformanceShaders
    0x7fff37038000 -     0x7fff37044ffe  com.apple.NetFS (6.0 - 4.0) <5C3C3672-2549-316E-9AC6-A1CFDCD16E9C> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS
    0x7fff37045000 -     0x7fff37188ff6  com.apple.Network (1.0 - 1) <38F65393-1393-3888-9F02-C4087F19CA0D> /System/Library/Frameworks/Network.framework/Versions/A/Network
    0x7fff39bb1000 -     0x7fff39c09ff7  com.apple.opencl (3.5 - 3.5) <D734AF0C-0EA3-3264-BBF9-D3099ACF47E3> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL
    0x7fff39c0a000 -     0x7fff39c26fff  com.apple.CFOpenDirectory (10.15 - 220.40.1) <AA81FC34-A7F6-3DA2-A275-B34F75099C7B> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory
    0x7fff39c27000 -     0x7fff39c32fff  com.apple.OpenDirectory (10.15 - 220.40.1) <ECFA2FFB-D5B6-3916-96F7-9F3A1EB1E534> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory
    0x7fff3a58d000 -     0x7fff3a58ffff  libCVMSPluginSupport.dylib (17.10.22) <48C3CA4F-69EF-31E7-9120-0BA8E9162ACA> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib
    0x7fff3a590000 -     0x7fff3a595fff  libCoreFSCache.dylib (176.9) <D5D62F22-9099-370B-B264-B5398554EF0B> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreFSCache.dylib
    0x7fff3a596000 -     0x7fff3a59afff  libCoreVMClient.dylib (176.9) <31DA9263-05A0-35A5-9CB8-40F8311B964B> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib
    0x7fff3a59b000 -     0x7fff3a5a3ff7  libGFXShared.dylib (17.10.22) <B153F11B-C10F-38FE-AB8D-9E6C5315F210> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib
    0x7fff3a5a4000 -     0x7fff3a5aefff  libGL.dylib (17.10.22) <59E124FF-8F56-3028-9816-40699F152B3B> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
    0x7fff3a5af000 -     0x7fff3a5e4fff  libGLImage.dylib (17.10.22) <7EC55D26-7FA5-3B7B-A552-C50FA0308101> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib
    0x7fff3a778000 -     0x7fff3a7b4fff  libGLU.dylib (17.10.22) <A4C86485-7CDF-30B0-ACB5-B0D11CA88ED0> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
    0x7fff3b1e4000 -     0x7fff3b1f3ff7  com.apple.opengl (17.10.22 - 17.10.22) <0142B045-DCF8-3554-A7FB-48A173541E40> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
    0x7fff3c1ad000 -     0x7fff3c42bff0  com.apple.QuartzCore (1.11 - 815.19.4.2) <5F492A40-BBBC-3A31-83A8-32462A7B1FB4> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
    0x7fff3cf78000 -     0x7fff3d2beff6  com.apple.security (7.0 - 59306.41.2) <FB3774D5-C940-35FB-960A-86253A01BDAE> /System/Library/Frameworks/Security.framework/Versions/A/Security
    0x7fff3d2bf000 -     0x7fff3d347ff7  com.apple.securityfoundation (6.0 - 55236) <6482C994-4DB4-320D-8FD4-50C998EA8856> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation
    0x7fff3d3a1000 -     0x7fff3d3a5ff8  com.apple.xpc.ServiceManagement (1.0 - 1) <2B80E13A-AFFC-355A-AA82-CCDEF4718E66> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement
    0x7fff3e132000 -     0x7fff3e19cff7  com.apple.SystemConfiguration (1.19 - 1.19) <A52A533D-DA25-3607-A18E-CA7C539E1C52> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration
    0x7fff3e418000 -     0x7fff3e772ff4  com.apple.VideoToolbox (1.0 - 2510.17.4.6) <D8DDFD1A-003E-399A-9469-E6E55551726D> /System/Library/Frameworks/VideoToolbox.framework/Versions/A/VideoToolbox
    0x7fff41ef8000 -     0x7fff41fbcfef  com.apple.APFS (1412.41.1 - 1412.41.1) <0319F563-43AE-3F80-9107-7F0056E726DB> /System/Library/PrivateFrameworks/APFS.framework/Versions/A/APFS
    0x7fff43098000 -     0x7fff43099ff1  com.apple.AggregateDictionary (1.0 - 1) <93D38CEB-C8F2-3011-8810-64D1E33B0D62> /System/Library/PrivateFrameworks/AggregateDictionary.framework/Versions/A/AggregateDictionary
    0x7fff435a9000 -     0x7fff435c6ffc  com.apple.AppContainer (4.0 - 448.40.2) <1A1D23EF-A9CA-3D46-ABAC-E87628E3DF26> /System/Library/PrivateFrameworks/AppContainer.framework/Versions/A/AppContainer
    0x7fff4361b000 -     0x7fff43629ff7  com.apple.AppSandbox (4.0 - 448.40.2) <19B46F6D-3F13-3679-81E0-C626E7E9749D> /System/Library/PrivateFrameworks/AppSandbox.framework/Versions/A/AppSandbox
    0x7fff43ab0000 -     0x7fff43ad4ff3  com.apple.framework.Apple80211 (13.0 - 1460.1) <5290ABDC-D781-31CF-AD23-C39D3BA3FBD6> /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Apple80211
    0x7fff43c0a000 -     0x7fff43c19fdf  com.apple.AppleFSCompression (119 - 1.0) <7EEDBF8A-8812-33D6-A5B0-F7D36825EE73> /System/Library/PrivateFrameworks/AppleFSCompression.framework/Versions/A/AppleFSCompression
    0x7fff43d18000 -     0x7fff43d23ff7  com.apple.AppleIDAuthSupport (1.0 - 1) <B84D3BAB-BCF7-3DD8-A656-498D5444DC9D> /System/Library/PrivateFrameworks/AppleIDAuthSupport.framework/Versions/A/AppleIDAuthSupport
    0x7fff43d65000 -     0x7fff43dadfff  com.apple.AppleJPEG (1.0 - 1) <CFE57DD6-F663-3DBF-8D37-BEFABF557D1F> /System/Library/PrivateFrameworks/AppleJPEG.framework/Versions/A/AppleJPEG
    0x7fff44186000 -     0x7fff4418aff7  com.apple.AppleSRP (5.0 - 1) <77EB08CE-419B-38D5-9160-C1D4D3EE5131> /System/Library/PrivateFrameworks/AppleSRP.framework/Versions/A/AppleSRP
    0x7fff4418b000 -     0x7fff441adffb  com.apple.applesauce (1.0 - 16.22) <EFF69698-9566-3957-B3F5-CEC2B206EE7C> /System/Library/PrivateFrameworks/AppleSauce.framework/Versions/A/AppleSauce
    0x7fff4426d000 -     0x7fff44270ffb  com.apple.AppleSystemInfo (3.1.5 - 3.1.5) <F4F1A097-C691-38BC-B91B-FFD828C3EA4E> /System/Library/PrivateFrameworks/AppleSystemInfo.framework/Versions/A/AppleSystemInfo
    0x7fff44271000 -     0x7fff442c1ff7  com.apple.AppleVAFramework (6.1.2 - 6.1.2) <C380FF1E-965E-3F05-BDCF-BB9EAC7F7B74> /System/Library/PrivateFrameworks/AppleVA.framework/Versions/A/AppleVA
    0x7fff4430a000 -     0x7fff44319ff1  com.apple.AssertionServices (1.0 - 223.40.19) <73B5C0D9-AB04-3961-A01D-FFBC94D1348E> /System/Library/PrivateFrameworks/AssertionServices.framework/Versions/A/AssertionServices
    0x7fff44855000 -     0x7fff44c53ff4  com.apple.audio.AudioResourceArbitration (1.0 - 1) <D51DC94A-FFDE-3B61-8E71-A05298853297> /System/Library/PrivateFrameworks/AudioResourceArbitration.framework/Versions/A/AudioResourceArbitration
    0x7fff44d92000 -     0x7fff44de3ffd  com.apple.audio.AudioSession (1.0 - 17) <95ED0F4C-FE5E-3401-82CC-3ADC19120CE8> /System/Library/PrivateFrameworks/AudioSession.framework/Versions/A/AudioSession
    0x7fff44de4000 -     0x7fff44e11ff7  libSessionUtility.dylib (17) <B39432B4-506A-3FBE-A512-8E4780CD9A03> /System/Library/PrivateFrameworks/AudioSession.framework/libSessionUtility.dylib
    0x7fff44eaa000 -     0x7fff450e7fff  com.apple.audio.AudioToolboxCore (1.0 - 1104.26) <9D7C2174-0854-3C13-AF80-E814A9EC013C> /System/Library/PrivateFrameworks/AudioToolboxCore.framework/Versions/A/AudioToolboxCore
    0x7fff450e8000 -     0x7fff45201ff0  com.apple.AuthKit (1.0 - 1) <F190E8C4-1D9B-34F2-9255-902509534E6A> /System/Library/PrivateFrameworks/AuthKit.framework/Versions/A/AuthKit
    0x7fff453bc000 -     0x7fff453c5ff3  com.apple.coreservices.BackgroundTaskManagement (1.0 - 104) <5E2B9000-49D6-3BFA-97F1-3B47A8A7418D> /System/Library/PrivateFrameworks/BackgroundTaskManagement.framework/Versions/A/BackgroundTaskManagement
    0x7fff453c6000 -     0x7fff45467ff8  com.apple.backup.framework (1.11.1 - 1298.1.2) <3C069796-5360-32F6-8841-BC263B94B2A3> /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup
    0x7fff45468000 -     0x7fff454e9ffd  com.apple.BaseBoard (464.1 - 464.1) <1A44B522-904F-3541-BC8C-5EDF0C6EE49C> /System/Library/PrivateFrameworks/BaseBoard.framework/Versions/A/BaseBoard
    0x7fff455eb000 -     0x7fff45627ff7  com.apple.bom (14.0 - 219.1) <4D4C4ACA-A1DD-3D0B-B362-8D202EBE8D9B> /System/Library/PrivateFrameworks/Bom.framework/Versions/A/Bom
    0x7fff4619c000 -     0x7fff461ebfff  com.apple.ChunkingLibrary (302 - 302) <593921FE-7EFE-36F6-8B05-4E89B00EABD6> /System/Library/PrivateFrameworks/ChunkingLibrary.framework/Versions/A/ChunkingLibrary
    0x7fff47074000 -     0x7fff47085fff  com.apple.CommonAuth (4.0 - 2.0) <1D04F654-22B1-37EF-90AD-3ADB5238806A> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth
    0x7fff47099000 -     0x7fff470b0fff  com.apple.commonutilities (8.0 - 900) <0B13423D-84E7-394A-8E2A-62D815B5BC4B> /System/Library/PrivateFrameworks/CommonUtilities.framework/Versions/A/CommonUtilities
    0x7fff477a9000 -     0x7fff47b7efc8  com.apple.CoreAUC (283.0.0 - 283.0.0) <505292C7-A6F0-392F-A94D-03D74F61F717> /System/Library/PrivateFrameworks/CoreAUC.framework/Versions/A/CoreAUC
    0x7fff47b7f000 -     0x7fff47badffb  com.apple.CoreAVCHD (6.1.0 - 6100.4.1) <BB2011D9-77DB-3C50-9228-C0A7B3880821> /System/Library/PrivateFram"	Pramoda S
21068	VM crashes after a while when pressing Tab/Return in terminal	VirtualBox 6.1.36	2022-08-16T13:05:24Z	2022-08-16T16:21:56Z	2022-08-16T16:21:56Z	"Hi,

VirtualBox: 6.1.36 r152435 (Qt5.6.3)

I am on an Ubuntu 20.04 VM (running on a macOS host). I turn it on and open up its terminal (bash). After ~10-15 minutes of playing around, I press the tab key (for autocompletion). I've notices this also sometimes happens with the return key in a Find/Replace dialogue in CLion.

The VM freezes so I have to manually shut down.

The same happens when I am in zsh, so it's not the terminal itself.

Could you please help,
Thanks,
Mihai"	mihai_mc
20297	VM crashes after starting recording	VirtualBox 6.1.18	2021-04-10T09:31:42Z	2021-04-10T09:31:42Z	2021-04-10T09:31:42Z	"VM immediately crashes when starting recording:

---------------------------
VirtualBoxVM.exe - Application Error
---------------------------
The instruction at 0x00007FFE918E77E3 referenced memory at 0xFFFFFFFFFFFFFFFF. The memory could not be read.


Click on OK to terminate the program
---------------------------
OK   
---------------------------


Host: Windows 10 x64
Guest: Arch Linux x64 (UEFI boot)

To reproduce:
1. Boot from Arch Linux iso
2. Start recording (View\Recording)

PS. Starting recording via command line works just fine.
"	1ns
19988	VM crashes or restarts during package upgrade on FreeBSD guest	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
17481	VM crashes when allocating memory at MSR_LSTAR address range	VirtualBox 5.2.6	2018-01-19T10:45:07Z	2018-01-19T22:32:20Z	2018-01-19T22:32:20Z	"Hi,

I'm developing a Linux LKM, and I tried to reserve memory in the same range of MSR_LSTAR (SYSCALL handler), with __vmalloc_node_range().

On the 3rd execution of that function, returning first NULL, second an address and third time NULL, the Guru Mediation spawns.

I'm attaching the source code to reproduce the bug, the log and the screenshot.

Thanks for help."	D1W0U
16228	"VM crashes with ""Aborted"" status when host machine connects to bluetooth device"	VirtualBox 5.1.2	2016-11-24T17:17:28Z	2016-11-24T17:29:21Z	2016-11-24T17:29:21Z	"Hello,

I'm working on an Ubuntu 14.04 VM and I kind of noticed a very strange issue. Whenever my JBL bluetooth speaker connects/disconnects to host (Mac OS X El Capitan), my linux VM just crashes unexpectedly with ""Aborted"" status (screenshot included) even though I am not using this speaker as an audio device in my VM. The issue is resolved when either the audio device is disabled or changed in the VM settings."	baalali
9337	VM defaults for a new windows 95/98 image seem off	VirtualBox 4.1.0	2011-07-28T19:45:10Z	2011-07-28T19:45:10Z	2011-07-28T19:45:10Z	"As described here:
http://forums.virtualbox.org/viewtopic.php?f=9&t=42960

If somebody creates a ""new virtual machine"" with type windows 95/98
NIC should probably slightly better to default to PCI-net II, and sound card to sound blaster by default."	Roger Pack
18576	VM disables bluetooth	VirtualBox 6.0.6	2019-04-18T18:24:54Z	2019-04-18T19:32:53Z	2019-04-18T19:32:53Z	After upgrade to new Version 6.0.6 bluetooth on iMac is turned off. Hence BT mouse and keyboard can't be used anymore. Connecting a wired mouse helps turn off VN and VB then bluetooth turns back on by itself. This problem did at first not exist with 6.0.4. But when going back to 6.0.4 from 6.0.6 with Time Machine the problem with BT still existed. The update must have changed something outside the VB itself. How can I solve the problem?	ALG
17295	VM doesn't works after last windows10 upgrade on Host	VirtualBox 5.2.0	2017-11-19T23:57:44Z	2017-11-19T23:57:44Z	2017-11-19T23:57:44Z	"Windows 10 running on host, and VMs (Windows10) works fine until the last Windows10 on host
After this update, VM can be launch (I have a Virtual Box 5.0 installed),
So I upgrade Virtual Box to 5.2 and I can launch the VM.
The problem is VM have a black screen ...
I remove the additional guest on my vm, no change.
from now all my VMs are out of order

"	dingdingdong
17807	VM fails to start	VirtualBox 5.2.12	2018-06-06T18:55:20Z	2018-06-11T16:32:38Z	2018-06-11T16:32:38Z	"Running Version 5.1.14 r112924 (Qt5.6.2) on Windows 7 64bit, suddenly it fails to start with below error:

The virtual machine 'Oracle Linux 6.7' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'D:\Virtual_Machines\Oracle Linux 6.7\Logs\VBoxHardening.log'.
"	Abdelj
17810	vm fails to stop or reset	VirtualBox 5.2.8	2018-06-08T00:41:01Z	2018-06-10T16:51:34Z	2018-06-10T16:51:34Z	"Running vbox virtualbox-ose-5.2.8_1 on freebst 11.1 host.
VM hangs on attempt to reset or to poweroff it"	Dian
13752	VM freezes after leaving Haiku operating system running for several hours	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
16445	VM gets stuck at online snapshotting	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
19793	VM Guest Windows-7 Freezes after loading Operating System	VirtualBox 6.1.10	2020-08-05T11:50:31Z	2020-09-22T16:36:38Z	2020-09-22T16:36:38Z	I have Laptop with this configuration AMD Ryzen 5 PRO 3500U w/ Radeon Vega Mobile Gfx, 2100 Mhz, 4 Core(s), 8 Logical Processor(s) Installed Windows-10 on  it. Installed latest Virtual Box 6.1.12r Installed Windows-7 as VM guest frequently operating system crashes with in 2-3 days and need to get a new copy of it and observed that after load operating system VM freezes with no activity for 20-30 Min than starts responds. If I reboot laptop same issue reports. More issue in setting up Display settings adjustments. Can any one help me out it. 2 CPU's and 4 GB memory allocated.	Madhava
17254	VM inaccessible due to guest additions attach issue	VirtualBox 5.2.0	2017-11-08T05:10:21Z	2017-11-22T02:32:25Z	2017-11-22T02:32:25Z	"After upgrading to version 5.2 initially there was no issue with the guest (eComStation) and I was able to start it a few times and also installed the new guest additions in it. Last time it seemed to shut down fine, but now I'm unable to start the guest. In the GUI is shows as inaccessible.[[BR]]
The error message is:[[BR]]
Cannot attach medium 'C:\Program Files\Oracle\VirtualBox\VBoxGuestAdditions.iso' {a2ff5d7d-6ede-4ade-80df-1ffc0ccfa03c}: medium is already associated with the current state of machine uuid {ee69103a-fec1-489f-adf2-25eb10922ba1}!.[[BR]]
Result Code: 
VBOX_E_OBJECT_IN_USE (0x80BB000C)[[BR]]
I don't understand how this non-essential medium can make the guest inaccessible, however the worst thing is that the Settings icon is disabled for the client, so I can't detach the guest addition image nor make any changes. And the guest addition image is there and I even re-installed it with no effect.[[BR]]
The log file seems to be from the time the last successful launch of the guest.
"	Rafcio
20446	VM intermittently freezing	VirtualBox 6.1.22	2021-07-02T19:08:59Z	2022-03-03T03:31:57Z	2022-03-03T03:31:57Z	"Virtual Box Version 6.1.22 r144080 (Qt5.6.2)

Operating System = Windows 10 (OS Build 19042.1052)
                   VM simulating operating system = XP

Works fine for a while then freezes when repeating the same action that had worked fine just before.  

Only way to get it to unfreeze is to Close down application completely.  

Had been working on Lotus spreadsheet when it freezes.  Have had 6 freezes in 2 days.


All worked perfectly 2 versions ago, but see no way to go back to an earlier version.  Started having the problem previous version and updated to this version since it was causing the same problem.
"	Sooz C
19214	VM is aborted on normal shutdown	VirtualBox 6.1.0	2020-01-09T03:36:33Z	2020-01-09T03:36:33Z	2020-01-09T03:36:33Z	"VM is aborted on normal shutdown. The state changes to ""Powered Off"" and then to ""Aborted"".

Last few lines from VBox.log:

02:31:14.797187 E1000#0: TX frames up to 1514: 107844
02:31:14.797197 E1000#0: TX frames up to 2962: 682
02:31:14.797207 E1000#0: TX frames up to 4410: 0
02:31:14.797216 E1000#0: TX frames up to 5858: 0
02:31:14.797226 E1000#0: TX frames up to 7306: 0
02:31:14.797234 E1000#0: TX frames up to 8754: 0
02:31:14.797252 E1000#0: TX frames up to 16384: 0
02:31:14.797276 E1000#0: TX frames up to 32768: 0
02:31:14.797292 E1000#0: Larger TX frames    : 0
02:31:14.797302 E1000#0: Max TX Delay        : 0
02:31:14.799059 GIM: KVM: Resetting MSRs
02:31:14.804435 Changing the VM state from 'DESTROYING' to 'TERMINATED'
02:31:14.811282 Console: Machine state changed to 'PoweredOff'
02:31:14.812640 GUI: Request to close Runtime UI because VM is powered off already.
02:31:14.812665 GUI: Passing request to close Runtime UI from machine-logic to UI session. 
"	crvi
20357	VM launch fail on Windows 10 when WSL2 and Docker is enabled	VirtualBox 6.1.22	2021-05-11T10:16:02Z	2022-08-01T18:37:28Z	2022-08-01T18:37:28Z	"We are using Docker containers and Vagrant + VirtualBox virtual machines in Windows 10 (now 20H2). Would be very convenient to make both parties (Docker+WSL2 and VirtualBox) working together on same machine. However when Docker Desktop with WSL2 support is installed, existing VirtualBox virtual machines (Linux 64-bit quests with installed VirtualBox Guest additions) fail to launch. Instead error message appear:

''WHvCapabilityCodeHypervisorPresent is FALSE! Make sure you have enabled the 'Windows Hypervisor Platform' feature. (VERR_NEM_NOT_AVAILABLE).
VT-x is not available (VERR_VMX_NO_VMX).
''

""Windows Hypervisor Platform"" feature enabling in Windows features does not change anything. It is not possible to change paravirtualization interface type under VM ""Settings - System - Acceleration"" too - OK button remain disabled.

To get VirtualBox VMs running again either ""hypervisorlaunchtype"" must be disabled through Windows Command Prompt with command
{{{
bcdedit /set hypervisorlaunchtype off
}}}
or Docker Desktop must be uninstalled together with ""Windows Hypervisor Platform"", ""Virtual Machine Platform"" and ""Windows Subsystem for Linux"" feature disabling in Windows Features with subsequential Windows restart. Both actions obviously permit Docker container using together with VirtualBox. Are there is another way how to use VirtualBox 64-bit VMs in Windows host together with WSL2 + Docker installed in same Windows host?

I seen Hyper-V virtualization support appearing in VirtualBox changelog starting from version 6.1.18 with Hyper-V related fixes in 6.1.22. However it does not help for us. Didn't found any useful information about how to run Docker+WSL2 and VirtualBox together in Internet either.

Environment info:
{{{
Host: Windows 10 20H2, 64-bit
Guests: Ubuntu Linux 18.04 LTS, 64-bit
Hardware: Dell OptiPlex 980, Intel Core i5-750 CPU (has VT-x support), 16 GB RAM
Dell BIOS, version A18, VT-x is enabled
}}}"	Janis Baumanis
19400	VM Locks Up When Running x64dbg	VirtualBox 6.1.4	2020-03-14T00:13:21Z	2020-03-14T00:13:21Z	2020-03-14T00:13:21Z	"If one runs x64dbg https://github.com/x64dbg/x64dbg in a windows 10 VM and opens any PE executable to debug, after stepping through a few instructions the VM locks up.

virtualbox 6.1.4 and macos 10.15.3 and most recent x64dbg from the github releases."	rj45
17462	VM Lockup with evernote screenshot	VirtualBox 5.2.4	2018-01-16T20:01:22Z	2018-01-16T20:01:22Z	2018-01-16T20:01:22Z	"Version 5.2.4 r119785 (Qt5.6.2)
Windows 7 VM 32 bit. 
Windows 10 Host. 

I have evernote 6.7.5.5825 on my host machine. 

I can use the VM all day long with no issues whatsoever. 
As soon as i use evernote to take a screenshot of either the VM or the host, any pert of either, it locks up the VM to the point that it is nearly un-responsive. Only a left click works, and it only marginally works at that.

Evernote is the only application that i have seen cause this, and it is only when a screenshot is taken. "	link81
21322	VM loses connection to Host	VirtualBox-7.0.4	2022-11-30T15:08:06Z	2022-12-20T09:13:49Z	2022-12-20T09:13:49Z	"After some time the guest OS (Windows 11 Pro 22H2 22621.819 Windows Feature Experience Pack 1000.22636.1000.0) loses connection to the host OS (Windows 11 Enterprise 21H2 22000.1219).
Keyboard and mouse are unresponsive, ACPI shutdown doesn't work either, although the guest os seems to work normally.
The log (attached) reports several 'vmmDevHeartbeatFlatlinedTimer'"	Matt G
14033	VM Losing time guest running network backups	VirtualBox 4.3.26	2015-04-08T10:33:55Z	2015-04-10T12:24:41Z	2015-04-10T12:24:41Z	"One of my VMs is seeing major loss of time when it runs backups.

It does not have this issue at any other time.

I did not see this behavior until I upgraded from the last pre-packaged version of VirtualBox for Fedora 17 to built-from-sources 4.3.(the one before 26).

The host:

`Linux hagrid.sb.litts.net 2.6.43.8-1.fc15.x86_64 #1 SMP Mon Jun 4 20:33:44 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux`

The guest:

`Linux overkill.sb.litts.net 2.6.22.14-72.fc6 #1 SMP Wed Nov 21 15:12:59 EST 2007 i686 i686 i386 GNU/Linux`

''VirtualBox:''
`4.3.26_OSE r98988 built from sources`

I do not see this on other VMs, but this one has the most data.  The other VMs also run Fedora, but not this exact version.

Disk being backed-up:

`/dev/hda3              415G    79G   316G  20% /`

Resulting backup (on an NFS-mounted NAS):

`-rw-rw---- 1 root root 58G Apr  8 05:18 /mnt/backup/overkill/Wed.tar.z`

The host and the NAS both have Gb ethernet connections to the same (switched) physical LAN.

The virtual adapter is ""Bridged"", Intel PRO/1000 MT Desktop (8254OEM).

The virtual disk is a normal VDI 400GB (170.94 actual) dynamic disk on an (emulated) IDE controller.  It is the only disk configured on this VM (except for an empty CDROM).

The VM runs headless.

The tar command:

{{{
tar --totals --exclude var/www/servers/PhotoGallery/FileCache --anchored --wildcards --wildcards-match-slash --exclude proc --exclude sys --exclude dev/pts --exclude dev/shm --exclude var/lib/nfs/rpc_pipefs --exclude proc/fs/nfsd --exclude proc/sys/fs/binfmt_misc --exclude mnt/castaway --exclude mnt/hagrid --exclude mnt/CindyTV --exclude mnt/nas148001 --exclude mnt/backup --exclude etc/lvm --exclude etc/mtab --exclude dev --exclude proc --exclude run --exclude sys --exclude mnt --exclude tmp --exclude var/cache -czpf /mnt/backup/overkill/Wed.tar.z bin boot dev etc home lib lost+found media misc mnt net opt proc root sbin selinux srv sys tftpboot tmp usr var
}}}

The backup runs for several hours.  In today's case, from about 0100 to about 0515.  Accumulated drift is about 40 minutes:

{{{
date
Wed Apr  8 04:43:05 EDT 2015
 Stop/restart NTP (to get correct time from network)
date
Wed Apr  8 05:23:13 EDT 2015
}}}

The VM runs NTP, but the time drift is too large for NTP to compensate.

NTP ends up locking to the local time-of-year clock, which is also slow.

VBox.log (attached) contains lines showing the drift accumulating of the form:

{{{
124:38:08.239525 TM: Giving up catch-up attempt at a 60 001 255 770 ns lag; new total: 60 001 255 770 ns

124:44:06.724982 TM: Giving up catch-up attempt at a 60 001 273 374 ns lag; new total: 120 002 529 144 ns
}}}



"	Timothe Litt
20384	VM not staring, was working perfectly two months ago.	VirtualBox 6.1.22	2021-06-01T13:56:27Z	2021-06-01T13:56:27Z	2021-06-01T13:56:27Z	"Failed to open a session for the virtual machine MANU2071 (2020 Sem2) 1.

The virtual machine 'MANU2071 (2020 Sem2) 1' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\Arjun\VirtualBox VMs\MANU2071 (2020 Sem2) 1\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}

This VM was working fine 2 months ago. Not sure what is wrong now. Based on the forums, Virtualization in Bios is on, HyperV is off, windows virtual platform is off, Linux subsystem is off. I have attached the log file
"	aj123456
17233	vm not start	VirtualBox 5.2.0	2017-11-01T09:06:17Z	2017-11-15T10:50:17Z	2017-11-15T10:50:17Z	"real OS Win7x64 I install VirtualBox 5.2 and create new VM win7x32
i push ""normal start"" button, but VM win7x32 not start. error message:

The virtual machine '2' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'D:\Users\romall.rainb\VirtualBox VMs\2\Logs\VBoxHardening.log'.
Код ошибки: E_FAIL (0x80004005)
Компонент: MachineWrap
Интерфейс: IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}

BUT if push ""headless Start"" VM start!, next push ""show"" i see VM running and normal work.

"	romall
19295	"VM reset (""HeartbeatFlatlinedTimer"") under load"	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
20161	VM running Windows 10 20H2 guest, VM one time freeze	VirtualBox 6.1.18	2021-01-29T18:39:34Z	2021-01-29T18:39:34Z	2021-01-29T18:39:34Z	"Hi,
This hang occurred once. See attached for logs and minidumps for VirtualBoxVM processes in process tree. Host is Windows 10 20H2 64 bit
The guest was running a Remote Desktop Connection session and the Pulse Secure VPN application, which I left, then came back 50 minutes later to find it unresponsive, with black screen (that may be the last display from the RD client)."	Mihai Hanor
19834	VM slow down when video recording enabled	VirtualBox 6.1.10	2020-08-26T20:09:56Z	2020-08-26T20:15:19Z	2020-08-26T20:15:19Z	"To reproduce bug you can try create VM with one core and start it with and without video recording. With video recording enabled you must see some slow down of working VM.

This happens because of slow working vpx_codec_encode call under lock inside RecordingStream::Process:

https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Main/src-client/RecordingStream.cpp#L373

{{{
int RecordingStream::Process(RecordingBlockMap &mapBlocksCommon)
{
    LogFlowFuncEnter();

    lock();

    ...
                    rc2 = writeVideoVPX(msTimestamp, pVideoFrame);
    ...

    unlock();

    LogFlowFuncLeaveRC(rc);
    return rc;
}

}}}

And writeVideoVPX calls vpx_codec_encode:
https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Main/src-client/RecordingStream.cpp#L1161

{{{
vpx_codec_err_t rcv = vpx_codec_encode(&pCodec->VPX.Ctx,
                                           &pCodec->VPX.RawImage,
                                           pts                          /* Timestamp */,
                                           this->Video.uDelayMs         /* How long to show this frame */,
                                           0                            /* Flags */,
                                           pCodec->VPX.uEncoderDeadline /* Quality setting */);
}}}

In fact vpx_codec_encode working slow beacuse of last parameter ""deadline"" by default is zero (which means infinite deadline for encoding)

Interesting part is that in 5.x virtualbox branch there was a code which fill the default value of uEncoderDeadline but this code not present in 6.0/6.1  branches...


{{{
/**
 * Invalidates the video recording configuration.
 */
void Display::i_videoRecInvalidate(void)
{
    AssertPtr(mParent);
    ComPtr<IMachine> pMachine = mParent->i_machine();
    Assert(pMachine.isNotNull());

    mVideoRecCfg.enmDst = VIDEORECDEST_FILE; /** @todo Make this configurable once we have more variations. */

    /*
     * Cache parameters from API.
     */
    com::SafeArray<BOOL> aScreens;
    HRESULT hrc = pMachine->COMGETTER(VideoCaptureScreens)(ComSafeArrayAsOutParam(aScreens));
    AssertComRCReturnVoid(hrc);

    mVideoRecCfg.aScreens.resize(aScreens.size());
    for (size_t i = 0; i < aScreens.size(); ++i)
        mVideoRecCfg.aScreens[i] = aScreens[i];

    hrc = pMachine->COMGETTER(VideoCaptureWidth)((ULONG *)&mVideoRecCfg.Video.uWidth);
    AssertComRCReturnVoid(hrc);
    hrc = pMachine->COMGETTER(VideoCaptureHeight)((ULONG *)&mVideoRecCfg.Video.uHeight);
    AssertComRCReturnVoid(hrc);
    hrc = pMachine->COMGETTER(VideoCaptureRate)((ULONG *)&mVideoRecCfg.Video.uRate);
    AssertComRCReturnVoid(hrc);
    hrc = pMachine->COMGETTER(VideoCaptureFPS)((ULONG *)&mVideoRecCfg.Video.uFPS);
    AssertComRCReturnVoid(hrc);
    hrc = pMachine->COMGETTER(VideoCaptureFile)(mVideoRecCfg.File.strName.asOutParam());
    AssertComRCReturnVoid(hrc);
    hrc = pMachine->COMGETTER(VideoCaptureMaxFileSize)((ULONG *)&mVideoRecCfg.File.uMaxSizeMB);
    AssertComRCReturnVoid(hrc);
    hrc = pMachine->COMGETTER(VideoCaptureMaxTime)((ULONG *)&mVideoRecCfg.uMaxTimeS);
    AssertComRCReturnVoid(hrc);
    BSTR bstrOptions;
    hrc = pMachine->COMGETTER(VideoCaptureOptions)(&bstrOptions);
    AssertComRCReturnVoid(hrc);

    /*
     * Set sensible defaults.
     */
    mVideoRecCfg.Video.fEnabled = true; /* Enabled by default. */

    if (!mVideoRecCfg.Video.uFPS) /* Prevent division by zero. */
        mVideoRecCfg.Video.uFPS = 15;

#ifdef VBOX_WITH_LIBVPX
    mVideoRecCfg.Video.Codec.VPX.uEncoderDeadline = 1000000 / mVideoRecCfg.Video.uFPS;
#endif

#ifdef VBOX_WITH_AUDIO_VIDEOREC
    mVideoRecCfg.Audio.fEnabled  = false; /* Disabled by default, unless set otherwise below. */
    /* By default we use 48kHz, 16-bit, stereo for the audio track. */
    mVideoRecCfg.Audio.uHz       = 48000;
    mVideoRecCfg.Audio.cBits     = 16;
    mVideoRecCfg.Audio.cChannels = 2;
#endif

}}}


Here is:
>mVideoRecCfg.Video.Codec.VPX.uEncoderDeadline = 1000000 / mVideoRecCfg.Video.uFPS;
"	gim
20065	VM Starting with grey screen	VirtualBox 6.1.16	2020-11-25T05:21:10Z	2020-11-25T07:17:36Z	2020-11-25T07:17:36Z	"Hello ,

Today I have upgraded VirtualBox to latest release ""VirtualBox-6.1.16-140961-Win"" and also updated the extensions.

I started my VM and it has OS Openfiler 2.99 , but today I see a grey screen and I cannot log into my system. I have three VM with this OS and all are not starting.

I can see boot screen and after boot I see a grey screen. Screenshots attached

I have others VM with different OS ( Windows 2016 , Oracle Linux 6.2 , Redhat Linux 5.5) and those are working fine.

I have done some troubleshooting after checking some google links. Issue still persists
> restarted my laptop multiple times
> Started VM as administrator , but still same issue
> Changed display Graphics controller . Tried all options VBoxVGA , VMSVGA, VboxSVGA. Still same issue.
> Increase Display Video Memory , still same issue
> Increase System Base Memory , Still same issue
"	vinodp
17389	VM starts, but UI stuck at creating process	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
21227	VM stop on error	VirtualBox-7.0.2	2022-10-31T20:56:18Z	2022-10-31T20:56:18Z	2022-10-31T20:56:18Z	Crash during guest OS upgrade.	Дмитро
17985	VM stop working	VirtualBox 5.2.18	2018-09-13T08:01:33Z	2018-09-13T08:01:33Z	2018-09-13T08:01:33Z	"Hi.
Very often a Windows 10 virtual machine crashes.
The error message says to open a ticket and send the log files.
From the logs I could not understand why.

I attach log files.

Best Regards
Paolo"	paolo_len
18794	VM stopped scaling correctly ater update to 6.0.10 from 6,0,08	VirtualBox 6.0.10	2019-07-26T15:08:10Z	2019-07-26T17:57:20Z	2019-07-26T17:57:20Z	"Hi there 
I updated VMBox vom 6.0.8 to 6.0.10
this went well.- 
Then I started the Guest Cd 6.0.10 , after that the scaling of the desktop in the VM stoppend working. 
the size is set and is not changeable. 
I counter checked via a recent clone of the VM and there the scaling of the screen still works.-  
I am not sure what else I can give. please let me know.
cheers
   Me"	Baros
20275	VM stops when installation of WinSvr2019 on Windows10 (mac dual boot)	VirtualBox 6.1.18	2021-03-26T11:18:58Z	2021-03-26T11:18:58Z	2021-03-26T11:18:58Z	"Hi There,

The VM freeze when I install Windows Server 2019 on windows 10 (dual boot from Mac).  The Error can be found in attached.

Appreciated if you can advice a solution.

Regards,
NelNel"	NelNel
15513	VM stuck when attempting to open a Microsoft Office file from network	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
15691	VM stuck when restoring the session	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
13629	VM SUP startup log creation	VirtualBox 4.3.18	2014-11-20T16:30:45Z	2014-11-20T16:30:45Z	2014-11-20T16:30:45Z	VirtualBox creates VM shortcuts without adding the --sup-startup-log command line parameter. A VM receives the --sup-startup-log parameter only when it is started from the VirtualBox Manager. Most users will not be aware of this and they will provide whatever log resides in the VM folder. Maybe it should be better to use a per VM property, that defaults to enabled. An example of such a situation can be found [[https://www.virtualbox.org/ticket/13295#comment:20|here]].	Mihai Hanor
14504	VM VirtualBox crashes on Windows Server 2008 r2	VirtualBox 5.0.2	2015-08-27T07:34:29Z	2015-08-27T08:19:42Z	2015-08-27T08:19:42Z	"As soon as I open the application, it crashes with the following information:

Problem signature:
  Problem Event Name:	APPCRASH
  Application Name:	VirtualBox.exe
  Application Version:	0.0.0.0
  Application Timestamp:	555369a5
  Fault Module Name:	ntdll.dll
  Fault Module Version:	6.1.7601.18247
  Fault Module Timestamp:	521eaf24
  Exception Code:	c0000005
  Exception Offset:	000000000005320e
  OS Version:	6.1.7601.2.1.0.274.10
  Locale ID:	7177
  Additional Information 1:	c042
  Additional Information 2:	c042b26446d5b704c80f7a33d8431df8
  Additional Information 3:	d71e
  Additional Information 4:	d71e92005cc3ffc26e9fe64612607c50

Any advise on what it could be? Don't even know where to start! Version 4.3.28-100309."	cverster
7919	VM VirtualBox Manager GUI crash when deleting snapshot	VirtualBox 4.0.0	2010-12-27T13:54:39Z	2016-08-26T10:56:07Z	2016-08-26T10:56:07Z	"Host: Win7 x64[[BR]]
Guest: SLES 10 SP3 x64 w/o GA[[BR]]

Manager GUI crashes when trying to delete (merge) snapshot for running machine.[[BR]]
It is reproducible on new machine.[[BR]]
If snapshot has saved state it loses it before crash.
That VM and other ones are not affected and are running."	Alil
12570	VM window appears off screen; not accessible	VirtualBox 4.3.6	2014-01-03T15:11:01Z	2020-11-14T10:18:07Z	2020-11-14T10:18:07Z	"Virtual box remembers guest window location and uses it at next start-up for a VM.  This is a good thing.  However, what it doesn't do is confirm upon start-up that the remembered location is still valid and will display the window off screen and not viewable.  Worse, it does not respond to the typical Windows move commands in order to move the window back into viewable space.  This leads to not being able to correct the condition and the user is stuck with a window they cannot access.

Specifics:
At home, I have an additional monitor that is positioned vertically above my laptop screen and is oriented that way in Windows ""Screen Resolution"" where one identifies monitors and their relative locations.  At the office, I have three external monitors, all side-by-side, and do not use the laptop screen.

I had worked at home and placed the VM window in the ""top"" monitor in scaled mode.  I shut down the guest and then shut-down the host laptop in that condition and went to the office.  There, I started the host laptop, opened VirtualBox, and started the guest.  Initially, the guest window came up in my main monitor.  I then switched it to scaled mode and the window disappeared.  Attempts to move it via the Windows Move option from the System menu was not successful.

I ended up having to go into ""Screen Resolution"" and orienting my monitors to place one of them ""above"" my main monitor -- thus replicating the condition under which the scaled guest window last appeared.  Doing this, I was able to then access the guest window and drag it ""down"" to the main monitor.  I then reverted the monitor orientation to side-by-side and moved the guest window to the monitor on the side.

Certainly not an insurmountable issue but until I thought about trying the re-orienting of my monitors, I was really stuck."	RodBarnes
16660	VM window freezes and process keeps running after manual savestate	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
14222	VM window should not be brought to front when it becomes active in full-screen mode	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
13808	VM window should stay maximized when moving to a screen with a different resolution	VirtualBox 4.3.20	2015-02-03T21:32:50Z	2015-02-04T13:51:56Z	2015-02-04T13:51:56Z	"VirtualBox: 4.3.20 r96997

Host: Windows 8.1 Enterprise 64-bit

Guest: Windows 7 Enterprise 64-bit

Problem:  I am running VirtualBox on a laptop with a secondary monitor connected via a display-port to VGA adapter coming out of the laptop and VGA in on the monitor.  The resolution of the laptop is 3200x1800 and the resolution of the secondary monitor is 1680x1050.  When I move the guest machine from the laptop screen to the secondary monitor I expect the VirtualBox window to resize to the new resolution but it does not. All other applications do this.  This is a bit confusing to explain but bear with me here...

Example:
I start Virtualbox and start my guest machine.  These windows are on my laptop screen and maximized, so running at 3200x1800.  I move the guest machine window over to my secondary monitor but the window does not resize.  I believe the window is still running at 3200X1800 instead of resizing to 1680x1050 when moved.  This is causing issues because the guest machine is pretty much unusable as everything is at a very high resolution but running on a monitor that does not have that resolution.  I can adjust the window or the resolution of the guest machine, but nothing changes.  The window still is running at 3200x1800 thus causing the guest machine to appear very tiny."	gregv
19677	VM window size not restored after exiting save state	VirtualBox 6.1.10	2020-06-21T21:06:22Z	2022-09-24T09:48:47Z	2022-09-24T09:48:47Z	"Host Windows 10 1909
Guest Windows 10 2004
Set resolution to required size (1152 x 864) save machine state, start saved VM. Result is VM window initially set to preset resolution but changes after restore to 640 x 480.

Steps tested with other VMs various builds but does not fail."	MacNala2
19433	VM's Constantly going into Guru Mediation state	VirtualBox 6.1.4	2020-03-26T14:41:08Z	2020-03-27T19:56:51Z	2020-03-27T19:56:51Z	"Im trying configure a Virtual environment for testing but whenever I start my vis up they all starts dropping into guru mediation state and im getting frustrated. I have a MacBook Pro running Catalina and the box versions is 6.14

"	gazza2217
21107	VM's keep freezing	VirtualBox 6.1.38	2022-09-17T15:40:23Z	2023-02-03T08:53:27Z	2023-02-03T08:53:27Z	"Have several different VM's.  They all keep freezing unless I click the mouse pointer in the VM window.  Even tried pausing VM from menu, then unpausing.  Each time the VM runs for about a second or two before it freezes up.  The VM's boot up okay, and windows desktop runs and initializes, but after a few minutes the VM's keep pausing.

Very repeatable.  LMK if more information is needed.  Attached log here from one VM.
Thank you"	ArtZ
20846	Vmbox is running too slow	VirtualBox 6.1.32	2022-02-24T07:20:23Z	2022-02-24T07:20:23Z	2022-02-24T07:20:23Z	After latest update vm box is running too slow. Even it is not installing iso file properly. After installing it get stucked.	sudip234
20845	Vmbox is running too slow	VirtualBox 6.1.32	2022-02-24T07:20:23Z	2022-02-24T07:20:23Z	2022-02-24T07:20:23Z	After latest update vm box is running too slow. Even it is not installing iso file properly. After installing it get stucked.	sudip234
20844	Vmbox is running too slow	VirtualBox 6.1.32	2022-02-24T07:20:23Z	2022-02-24T07:20:23Z	2022-02-24T07:20:23Z	After latest update vm box is running too slow. Even it is not installing iso file properly. After installing it get stucked.	sudip234
20843	Vmbox is running too slow	VirtualBox 6.1.32	2022-02-24T07:20:22Z	2022-02-24T07:20:22Z	2022-02-24T07:20:22Z	After latest update vm box is running too slow. Even it is not installing iso file properly. After installing it get stucked.	sudip234
20842	Vmbox is running too slow	VirtualBox 6.1.32	2022-02-24T07:20:22Z	2022-02-24T07:20:22Z	2022-02-24T07:20:22Z	After latest update vm box is running too slow. Even it is not installing iso file properly. After installing it get stucked.	sudip234
20841	Vmbox is running too slow	VirtualBox 6.1.32	2022-02-24T07:20:20Z	2022-02-24T07:20:20Z	2022-02-24T07:20:20Z	After latest update vm box is running too slow. Even it is not installing iso file properly. After installing it get stucked.	sudip234
20840	Vmbox is running too slow	VirtualBox 6.1.32	2022-02-24T07:20:01Z	2022-02-24T07:20:01Z	2022-02-24T07:20:01Z	After latest update vm box is running too slow. Even it is not installing iso file properly. After installing it get stucked.	sudip234
20839	Vmbox is running too slow	VirtualBox 6.1.32	2022-02-24T06:58:15Z	2022-02-24T06:58:15Z	2022-02-24T06:58:15Z	After recent update vm box running too slow . I am not able to install any iso file. 	sudip234
17433	VMMR0.r0 Bluescreen on HP Laptop Win10 v1709	VirtualBox 5.2.4	2018-01-08T19:22:33Z	2018-01-11T18:49:56Z	2018-01-11T18:49:56Z	"VMMR0.r0 ( VMMR0!VMMR0EntryFast+13de )
Virtual Box 5.2.4 (fresh install)
Windows 10 v1709 10.0.16299.125 (Enterprise) (fresh install)
HP EliteBook 840 G3 W4S08UC#ABL (bios and drivers updated 2018-01-08)

Starting a fresh VM on this configuration triggers a bluescreen.
May also occur on HP Elite X2. Not on HP Z230.
Computer available for remoting

"	Patrick_BNC
19929	VMs only start in headless mode on Big Sur		2020-10-01T02:07:16Z	2020-11-20T10:27:34Z	2020-11-20T10:27:34Z	"I’m using the latest beta of Big Sur (20A5384c) and the latest test build of VirtualBox (6.1.15 r140592 (Qt5.6.3)). I was able to overcome the errors caused by unloaded kernel extensions as posted elsewhere here; however, I can only start virtual machines in headless mode. Normal mode gives me a generic error of  NS_ERROR_FAILURE (0x80004005) in MachineWrap and detachable mode doesn’t seem to react at all. This applies to both the GUI and VBoxManage.

Steps to reproduce:
1. Make a new VM. It doesn’t need a boot disc or hard drive.
2. Load it in normal or detachable mode.
3. Notice that in normal mode, an error appears, and in detachable mode, VirtualBox seems to ignore the button press.
4. Now try the same VM in headless mode. It will boot.

I’m using a 2018 Mac mini. I saw in VBox.log that the last thing shown before the VM errors out is about resizing a window:


{{{
Display::i_handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0 flags=0x0 origin=0,0
}}}

Expected results:

I should get a window with the VM's display, even if I have no bootable media attached. The BIOS should still show, but it doesn't.
"	tyll
15043	VMSetError for ACPI tables < 64k	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
20263	VMSVGA FIFO[350]: segfault at 4 ip 00007f92a1a969a7 sp 00007f923d3ef9a0 error 4 in nouveau_dri.so[7f92a0dc9000+dfa000]	VirtualBox 6.1.18	2021-03-19T18:58:01Z	2021-03-19T18:58:01Z	2021-03-19T18:58:01Z	"i have a gentoo with kernel 5.11.7 and mesa version 21.0.0 and virtualbox 6.1.18
when i enable 3D acceleration the windows 10 virtual machine suddenly crash and shuts down

this is the kernel message
[ 1228.206773] VMSVGA FIFO[10733]: segfault at 4 ip 00007f7e7b90f9a7 sp 00007f7e07d329a0 error 4 in nouveau_dri.so[7f7e7ac42000+dfa000]
[ 4207.297884] VMSVGA FIFO[13888]: segfault at 4 ip 00007f9016eb59a7 sp 00007f8fb28269a0 error 4 in nouveau_dri.so[7f90161e8000+dfa000]
[ 8372.489017] VMSVGA FIFO[350]: segfault at 4 ip 00007f92a1a969a7 sp 00007f923d3ef9a0 error 4 in nouveau_dri.so[7f92a0dc9000+dfa000]"	custom
13891	VNC output scrambled during Ubuntu installation	VirtualBox 4.3.22	2015-02-24T22:34:02Z	2015-02-26T09:18:36Z	2015-02-26T09:18:36Z	"I ran VirtualBox headless on a FreeBSD 10.1 server (host) and tried to install Ubuntu 14.10 as a guest from the live iso image. I connect to the VirtualBox VNC server to get the VM output. The Ubuntu VM boots up, my VNC client shows the Ubuntu splash screen but as soon as the Ubuntu desktop gets started I get a scrambled image.
I can confirm the problem on FreeBSD 9.3 / VirtualBox 4.2.16 and FreeBSD 10.1 / VirtualBox 4.2.16 & VirtualBox 4.2.22. I have tried different VNC viewer @ Ubuntu (ssvncviewer) and Windows (RealVNC), no difference.

VM VNC output

[[Image(http://www.directupload.net/file/d/3908/adgfi9ld_png.htm)]]


Steps to create the VM:
- set VM='Ubuntu_14.10'
- VBoxManage createvm --name $VM --ostype ""Ubuntu_64"" --register
- VBoxManage storagectl $VM --name ""SATA Controller"" --add sata --controller IntelAHCI
- VBoxManage storageattach $VM --storagectl ""SATA Controller"" --port 1 --type dvddrive --medium ~/ubuntu-14.10-desktop-amd64.iso
- VBoxManage modifyvm $VM --memory 2048 --vram 128
- VBoxManage modifyvm $VM --vrdeproperty VNCPassword=password
- VBoxHeadless -s $VM


Output from VBoxHeadless
{{{
Oracle VM VirtualBox Headless Interface 4.3.22_OSE
(C) 2008-2015 Oracle Corporation
All rights reserved.

24/02/2015 22:28:30 Listening for VNC connections on TCP port 3389
24/02/2015 22:28:30 Listening for VNC connections on TCP6 port 5900
VRDE server is listening on port 3389.
24/02/2015 22:28:34   other clients:
24/02/2015 22:28:34 Client Protocol Version 3.8
24/02/2015 22:28:34 Protocol version sent 3.8, using 3.8
24/02/2015 22:28:34 rfbProcessClientSecurityType: executing handler for type 2
24/02/2015 22:28:34 Pixel format for client 192.168.0.109:
24/02/2015 22:28:34   32 bpp, depth 24, little endian
24/02/2015 22:28:34   true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0
24/02/2015 22:28:34 Enabling X-style cursor updates for client 192.168.0.109
24/02/2015 22:28:34 Enabling full-color cursor updates for client 192.168.0.109
24/02/2015 22:28:34 Enabling cursor position updates for client 192.168.0.109
24/02/2015 22:28:34 Enabling KeyboardLedState protocol extension for client 192.168.0.109
24/02/2015 22:28:34 Enabling NewFBSize protocol extension for client 192.168.0.109
24/02/2015 22:28:34 Enabling SupportedMessages protocol extension for client 192.168.0.109
24/02/2015 22:28:34 Enabling SupportedEncodings protocol extension for client 192.168.0.109
24/02/2015 22:28:34 Enabling ServerIdentity protocol extension for client 192.168.0.109
24/02/2015 22:28:34 Enabling Xvp protocol extension for client 192.168.0.109
24/02/2015 22:28:34 Using hextile encoding for client 192.168.0.109
24/02/2015 22:28:38 Sending rfbEncodingNewFBSize for resize to (720x400)
24/02/2015 22:29:04 Sending rfbEncodingNewFBSize for resize to (1024x768)
24/02/2015 22:29:06 Sending rfbEncodingNewFBSize for resize to (1152x400)
}}}


Output from ssvncviewer (VNC client)
{{{
Proto: RFB 003.008

Connected to RFB server, using protocol version 3.8

SelectSecurityType:
  sec-type[0]    2  (rfbSecTypeVncAuth)
Security-Type:   2  (rfbSecTypeVncAuth)  Latency: 3.01 ms

Performing standard VNC authentication
VNC Password: 
VNC authentication succeeded

Desktop name ""VBoxVNC""

VNC server default format:
  32 bits per pixel.  Least significant byte first in each pixel.
  True colour: max red 255 green 255 blue 255, shift red 0 green 8 blue 16
Warning: Cannot convert string ""-*-helvetica-medium-r-*-*-12-*-*-*-*-*-*-*"" to type FontStruct
Using default colormap which is TrueColor.  Pixel format:
  32 bits per pixel.  Least significant byte first in each pixel.
  True colour: max red 255 green 255 blue 255, shift red 16 green 8 blue 0
geometry: 720x400+358+238 ycrop: 0
create_image()
try_create_image: shm image create fail: image == NULL
try_create_image: created *non-shm* image: 720x400
try_create_image: image->bytes_per_line: 2880

guessed: -compresslevel 1
guessed: -qualitylevel  9
enabling 'delay_sync' mode for faster local drawing,
disable via env SSVNC_DELAY_SYNC=0 if there are painting errors.
New Size: 1024x768 at (0, 0)
ReDoDesktop: ycrop: 0
reset_image: destroyed 'image'
create_image()
try_create_image: shm image create fail: image == NULL
try_create_image: created *non-shm* image: 1024x768
try_create_image: image->bytes_per_line: 4096
New Size: 1152x400 at (0, 0)
ReDoDesktop: ycrop: 0
reset_image: destroyed 'image'
create_image()
try_create_image: shm image create fail: image == NULL
try_create_image: created *non-shm* image: 1152x400
try_create_image: image->bytes_per_line: 4608
}}}
"	MrSmith
9038	VNC Screen Repaint Delay	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
7570	VNC shows password in commandline	VirtualBox 3.2.10	2010-10-12T11:55:46Z	2010-10-18T09:47:21Z	2010-10-18T09:47:21Z	"Hi,

the vnc password is shown in the commandline. This is very insecure.
Because with a quick ps -aux every user can view it.
This patch adds a option to read the password from a file.

"	evermind
20225	Voice synthesis software rhvoice doesn't work in VirtualBox	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
5392	VRDP Multiconn looses track of connection details	VirtualBox 3.0.10	2009-11-05T04:43:42Z	2009-11-05T04:43:42Z	2009-11-05T04:43:42Z	"Virtual Machine with VRDP !MultiConn set to On. 

 * Connect from one client, VBoxManage showvminfo display the VRDP connection details (user, speed, IP etc)
 * Connect from a second client with the first client still connected. showvminfo will now display the details for the second user
 * Disconnect second user. VRDP info is now reset to 0 or blank for most values, no user info, IP, speed, etc, however first user is still connected.

It appears that the variables used for tracking connection info do not take into account multiple connections, the second connection is overwriting the first connections information and then clearing the values on disconnect.

Distribution is RHEL5
"	James Lucas
18747	vt-x imbricate grayed	VirtualBox 6.0.8	2019-07-08T19:27:24Z	2019-07-12T17:59:28Z	2019-07-12T17:59:28Z	"Hello, [[BR]]
I have AMD processor , the checkbox 'VT-X imbricate' is accessible on the host machine [[BR]] okay [[BR]]


When i install virtualbox on the guest machine virtualbox , then VT-X is recognized [[BR]] but 'VT-X imbricate' is grayed on virtualbox installed on the  [[BR]]
 guest machine Virtualbox.

[[BR]]


Thank."	Sizy458
17832	Vt-x is not available.  What tool will identify the problem?	VirtualBox 5.2.12	2018-06-21T11:00:09Z	2018-06-22T05:08:43Z	2018-06-22T05:08:43Z	"Failed to open a session for the virtual machine GreyCampus Big Data and Hadoop Developer Virtual Machine.

VT-x is not available (VERR_VMX_NO_VMX).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

I am trying to complete an online course in Hadoop that has a Virtualbox VM as part of the course.  My computer is a Dell XPS 15 (2017) and it has run VirtualBox VMs before. The Bios has this turned on and Hyper-V in the Windows 10 OS is turned off.  I also have Visual Studio 2017 installed but have gone in and uninstalled any features in it I can find that might use this.  Perhaps there still is something, but it is like finding a needle in a haystack.  There should be a tool or a log description can point a finger at precisely what has captured the virtualization so I can fix this.  "	superdml
16254	VxWorks guest broken on v5.X	VirtualBox 5.1.10	2016-12-01T16:49:51Z	2016-12-01T21:59:08Z	2016-12-01T21:59:08Z	"Upgraded from VirtualBox v4.3.40 to v5.1.10 on OS X host and I am no longer able to run my VxWorks simulators. The problem seems to be related to the network interface, when I disable the network interface the virtual machine behaves differently (hangs versus crashing), otherwise the virtual machine crashes. I’ve attached log files for each of the versions of VirtualBox, just in case it helps in debugging why one is working and the other is not.

P.S.
There are no issues when running the VxWorks simulators on VirtualBox v5.1.10 on both Windows and Linux hosts."	pcabral
19071	W10 Guest crash when watching youtube videos		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
19288	W2003 32 bit in VM stops responding in 6.0.16	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
20535	W64 host, Ubuntu guest: mouse cursor corrupt in Terminal on secondary 4K screen	VirtualBox 6.1.26	2021-09-06T11:45:41Z	2021-09-08T09:41:15Z	2021-09-08T09:41:15Z	"System details at the end.

Whether the VB container window is sized very small or large, there is a glitch with the mouse cursor inside Terminal windows in the guest OS.

Note that there are two 4K monitors attached. **This bug only appears if the VB container window is on one of the secondary monitors.** If it is on the laptop's main screen, the cursor simply disappears when typing, which I believe is the desired behaviour.

The specific issue is as follows: once the mouse cursor is moved inside the Terminal window, it is at first correct. However, type as much as one character, and it turns into a block of glitched data, 8-10 characters wide and one character tall. If the cursor is moved even a tiny amount, it returns to normal, until the user types once again.

I've attached images of the before and after effects within a small VB container window.

It appears that when the cursor is being removed, the underlying pixels are being bitblt'ed from the wrong part of video memory.

**System details**

VB 6.1.26 build 145957 (Qt5.6.2)

Host:
* Edition	Windows 10 Pro
* Version	20H2
* Installed on	‎06/‎07/‎2021
* OS build	19042.1165
* Experience	Windows Feature Experience Pack 120.2212.3530.0

Guest:
* Ubuntu 64 bit Hirsute, all patches current
* VM Additions installed.

PC:
* Processor	Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz   2.71 GHz
* Installed RAM	8.00 GB (7.88 GB usable)
System type	64-bit operating system, x64-based processor

Config:
* HP EliteBook 840 G4
* 3 GiB RAM assigned to guest
* Main screen: 1080p inbuilt
* Secondary screens:
 * 2x 28"" 4K
 * full resolution
 * 125% scaling
 * both connected using DisplayPort."	JonAtFS
19533	wacom clicks not registered in virtualbox manager window	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
17086	Webcam crash in Ubuntu 16.0.4 and VirtualBox 5.1.28 running Android-x86	VirtualBox 5.1.28	2017-09-16T05:23:17Z	2020-04-15T15:10:37Z	2020-04-15T15:10:37Z	"I've created a VM with Android 6.0-r3 from www.android-x86.org using VirtualBox 5.1.28 and Ubuntu 16.04 LTS. The VM works great, but every time I try to use a fake webcam it crashes.

Basically if in the host I perform:

# After installing v4l2loopback-dkms
modprobe v4l2loopback
# Init the video stream (/tmp/i.png can be any image and /dev/video0 is the loopback device that can have a different number if you have other connected webcams)
while [ 42 ]; do cat /tmp/i.png ; done | ffmpeg -y -i - -f image2pipe -r 15 -s 1920x1080 -vcodec rawvideo -pix_fmt yuv420p -threads 0 -f v4l2 /dev/video0

=> Run the VM and manually stop at the GRUB boot loader
=> Assign the webcam to the machine (Devices => Webcams => Dummy Video Device)
=> Continue to boot the machine

(the steps above are important, otherwise Android will not recognize the webcam)

=> Run some camera app, I use Open Camera from https://play.google.com/store/apps/details?id=net.sourceforge.opencamera&hl=en

=> The APP should show the image
=> Just try to leave the APP

=> The VM will crash and if you run the 'dmesg' command, it will appear something like

[202894.416980] HWCMONITOR[14932]: segfault at 7f5554b17800 ip 00007f55dc0beb35 sp 00007f55b017bb80 error 4 in VBoxHostWebcam.so[7f55dc0b8000+3a000]"	aliedis87.rhyta
19510	Webcam Lenovo P50 doesn't work => insufficient information provided	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
14398	webcam on Lenovo T550 with CentOS 7.1 guest	VirtualBox 5.0.0	2015-08-05T18:53:20Z	2015-11-04T15:32:51Z	2015-11-04T15:32:51Z	"Hi.

I'm running VirtualBox 5.0.0 under Win7 on a Lenovo T550 laptop. 
My guest O/S is CentOS 7.1.
On the Win7 system, the integrated laptop webcam works perfectly.
If I export the webcam to the Linux guest O/S (ie. in the ""Devices"" menu, under Webcams, ""Integrated Camera"" is selected.), then the guest O/S sees the webcam as well (uvcvideo, 04ca:703c).
In the guest O/S, if I start ""cheese"" (a tool to take pictures and video from the webcam), I should see a live preview of the webcam input.  The light on the camera does go on and stays on, but rather than displaying the live preview, I get the first frame that cheese saw when it was started.  That frame doesn't change.  I can click ""take picture"" over and over but it will capture the identical frame.
If I change the video resolution in cheese, then the frame changes one more time.

I tried on an older VirtualBox version 4.3.18, and the problem is identical.
I tried with CentOS 6, under both VirtualBox versions 4.3 and 5.0 (with proper guest extensions), and had the same problem.
I tried with a Lenovo T540p laptop (previous generation of this laptop), and the live preview in cheese worked on both 4.3 and 5.0.

It's important to note that the problem is not explicit to just ""cheese"".  For example, if I visit the following URL in Firefox:

http://mdn-samples.mozilla.org/s/webrtc-capturestill/

This is a WebRTC demo.  In the left box, I should see a live preview of my webcam.  I get the same problem (1 frame).  The same demo works properly on the underlying Linux box, and from the T540p laptop.

I installed a CentOS 7.1 system from scratch with no vbox, and the camera works fine with cheese (and demo above).
I installed VirtualBox 5 on this CentOS 7.1 system, and then installed the same VM that was having the cheese problem, and the video passes through perfectly as well!
I would guess this means that the issue is in the Windows Extension pack.

I'm really really anxious to resolve this issue soon because I really need it for later this month.  If there's any help that I can provide, please let me know.

Jason."	kangaroo
18725	WebCam passtrough doesn't properly pass format capabilities to guest GStreamer	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
10957	"website: add link to ""vboxsvc"" project (enhanced SMF management of VMs on Solaris-based hosts)"	VirtualBox 4.2.0	2012-09-18T08:59:16Z	2012-09-18T08:59:16Z	2012-09-18T08:59:16Z	"The http://www.virtualbox.org site lists some useful open-source projects that can be used along with VirtualBox. I suggest adding there a link to the ""vboxsvc"" project, which is hosted on SourceForge at http://sourceforge.net/projects/vboxsvc/ and its discussion is in VirtualBox forum, thread ""[Free as in beer] SMF service for VirtualBox VM's"" http://forums.virtualbox.org/viewtopic.php?f=11&t=33249.

This project provides an SMF method script and manifest to wrap execution/hibernation/shutdown of each VM as a separate SMF service instance, and lifetime monitoring (i.e. a frozen VM can be forced to reboot), as well as optional automated ZFS snapshot creation upon VM startup/shutdown, and many other administrative features. An SVR4 package of the project deliverables is also available.

In comparison with VirtualBox 4.2.0 automated VM startup support there are a few differences which may be important in more advanced setups - but available only for solutions built on Solaris 10, OpenSolaris and its relatives (using SMF and ZFS):
* With vboxsvc, each VM is an SMF instance, which allows to enable-disable them independently, and to build SMF dependency graphs between VMs and/or other system services and resources for automatic startup and shutdown/savestate of VMs.
* You can monitor the VM's functionality (i.e. test that it is ""pingable"" or that a webserver inside it responds), and accordingly restart the SMF service or put it into maintenance; you can also delay the exit is start-method until the VM actually works (needed for dependencies to start at a right moment in time and not after a delay randomly selected by admins).
* You can automate taking snapshots of ZFS-backed VM filesystem resources (including those on remote storage hosts available to VBox host via NFS or perhaps CIFS) before start/after stop to keep track of relatively stable points in time.
* There are some other differences, such as getting X11 control of a VM and then passing its execution back to headless SMF controller and various other ""nifty features"", all with configurable SMF attributes."	Jim Klimov
16443	Weston doesn't render a cursor.	VirtualBox 5.1.14	2017-02-02T18:23:40Z	2017-02-06T17:25:57Z	2017-02-06T17:25:57Z	"Arch guest with wayland on an Arch host.

If you launch weston it shows no pointer even though if you move the mouse over an icon it highlights it. This means -according to wayland people- that cursor planes are broken in Vbox. "	ApBB
16225	When I Change Network setting to “Bridge” Mode, Virtual Machine isn't available again.	VirtualBox 5.1.10	2016-11-24T11:35:38Z	2016-11-24T11:42:58Z	2016-11-24T11:42:58Z	"OSX 10.11.6
VirtualBox: Ver5.1.10 / Ver5.1.8 

When I Change any virtual machine's network setting to “Bridge” Mode, Virtual Machine isn't available again.

Virtual Box Report>>>>>>>>>>>>>>>>>>>>>>>

PCDATA invalid Char value 1.

Location: '/Users/admin/VirtualBox VMs/WorkWin7/WorkWin7.vbox', line 47 (1), column 65.

/Users/vbox/tinderbox/5.1-mac-rel/src/VBox/Main/src-server/MachineImpl.cpp[745] (nsresult Machine::i_registeredInit()).

返回 代码:

NS_ERROR_FAILURE (0x80004005)

组件:

MachineWrap

界面:

IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}


<<<<<<<<<<<<<<<<<<<<<<<<<<<Virtual Box Report

line 47 (1), column 65 of vbox file:
          <BridgedInterface name=""en0: &#x4EE5;&#x592A;&#x7F51; ""/>

If I delete the last space. the virtual machine is available again. But virtual box will report network setting is illegal. I need set the network setting again. then the virtual machine lunch correctly. "	xxxsinger
20486	When I download an 18GB file	VirtualBox 6.1.26	2021-08-03T19:26:57Z	2021-08-03T19:26:57Z	2021-08-03T19:26:57Z	"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 ""ahci-0-0"" (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 "	QFairy1214
18031	when i start the virtualbox I see a errore message that say tu send here vbox.log and vbox.png. can you help me?	VirtualBox 5.2.18	2018-10-05T12:14:22Z	2018-10-06T00:40:34Z	2018-10-06T00:40:34Z		turi
19935	"When I try to install Windows Server 2019 with ISO, it goes to ""guru meditation state""."	VirtualBox 6.1.14	2020-10-04T09:04:41Z	2020-12-07T12:40:27Z	2020-12-07T12:40:27Z	"
Hello team.

Every time I try to install Windows server 2019 it goes to guru meditation, with the other machines I have no problems, it is only with Windows server 2019."	David3333
13380	When I try to look for updates I get Wrong SSL certificate format	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
5335	When running a VM, Hard Disks should be opened ShareMode=0 to prevent other processes writing to them	VirtualBox 3.0.8	2009-10-30T00:11:59Z	2009-10-30T00:11:59Z	2009-10-30T00:11:59Z	"While a VM is running, the Hard Disk file (VDI) is opened in a mode that allows shared read-write by other processes.
The hard disk files should be opened in locked/exclusive write/no write sharing mode to ensure safe access.

e.g. In Windows, while a VM is running, the following test C code succesfully opens the VDI for writing (but should be blocked): 
{{{
CreateFile(TEXT(""Play.vdi"")
  ,GENERIC_READ | GENERIC_WRITE
  ,FILE_SHARE_READ | FILE_SHARE_WRITE
  ,NULL, OPEN_EXISTING, FILE_ATTRIBUTE_NORMAL, NULL)
}}}

Existing behaviour of allowing other processes write access allows another VM on a remote PC to boot a VDI on a network share, resulting in two VMs having concurrent access to the VDI which causes a BSOD.  Instead an error message prevent starting of the second remote VM. See [http://forums.virtualbox.org/viewtopic.php?f=6&t=23927 Windows XP Guest BSOD]"	Mark Cranness
16832	When running any machine in VirtualBox 5.1.22 Windows bluescreens	VirtualBox 5.1.22	2017-06-15T12:41:35Z	2017-06-20T08:54:26Z	2017-06-20T08:54:26Z	When I try and run a machine on VirtualBox Windows bluescreens and shuts down. I'm running Windows 10 Enterprise version 1703 build 15063.413.	Allan Kjær
15473	When started any virtual machine - VirtualBox crashes and pulls the machine down	VirtualBox 5.0.20	2016-06-02T06:20:05Z	2016-06-02T07:12:49Z	2016-06-02T07:12:49Z	When started any virtual machine - VirtualBox crashes and pulls the machine down	terrybrn
14180	when trying to open sagemath in oracle vm virtual box in windows 8.1 64 bit Blue screen of death happening	VirtualBox 4.3.28	2015-06-07T17:57:00Z	2015-06-08T14:12:35Z	2015-06-08T14:12:35Z	Installation of Oracle VM Virtual Box and importing the sage ova file in it was not a problem. But when I started the sage machine Blue Screen of Death (DRIVER_VERIFIER_DETECTED_VIOLATION) happened. Otherwise my machine works fine. I was using Sage-6.7 ova file and Virtual Box 4.3.28.100309-win in a windows 8.1 64 bit machine. The problem persists for 4.3.12.93733-Win version also. For my machine OS, drivers BIOS everything is up to date. Hard disk health is good. No issue of Virus or malware. I have not installed the guest additions.More than 100 GB space is available in machine. Any help will be appreciated.	amritendu
15946	When upgrading virtualbox, icon is removed from the taskbar and unnecessary desktop shortcut created.	VirtualBox 5.1.6	2016-09-16T19:13:50Z	2016-10-19T20:26:39Z	2016-10-19T20:26:39Z	"OS: Windows 10 64-bit, version 1607, build 14393.105.

VirtualBox Version: Both 5.1.4 and 5.1.6.

When upgrading virtualbox, the icon for virtualbox is removed from it's pinned location on the windows taskbar, and a new icon was added to the desktop.

I normally have desktop icons set to not display, but noticed this errata when going through ""This PC"" -> ""Desktop""
"	Samuel Flint
8360	when using existing ubuntu as a guest, vbox replaces xorg.conf	VirtualBox 4.0.4	2011-02-17T23:23:52Z	2011-04-13T13:39:34Z	2011-04-13T13:39:34Z	"I have a win7/ubuntu10.10 dual-boot. I installed virtualbox on win7 (host)
I followed these instructions http://chaits.accosted.net/?p=54 and created an instance out of an existing linux partition.
after I installed vb additions and extension, everything worked great in virtualbox. when i tried to boot into linux, the windows manager didn't lunch. xorg.conf was overwritten. 

Currently I have to sitch xorg.conf file manually if i want a graphical interface. 
i documented my experience [http://kirilligum.wordpress.com/2011/02/17/run-existing-linux-ubuntu-10-10-partition-in-virtualbox-under-host-windows-7-system-on-thinkpad-x201t/ here]."	kirill
14272	When VM run, Wacom_Tablet.exe consume much more memory	VirtualBox 5.0.0	2015-07-13T20:57:43Z	2018-09-06T19:33:10Z	2018-09-06T19:33:10Z	"I notice '''Wacom_Tablet.exe''' have strange memory consumption for a while. Now I'm sure Wacom_Tablet.exe memory increase continuously when VM run.

''Wacom_Tablet.exe is system service named ""TouchServiceWacom"" (Wacom Professional Touch Service)[[BR]]Since Wacom_Tablet.exe behave normally while VM turn OFF, I can not assume this case wacom can help.''

Wacom Driver Version: 6.2.0w5[[BR]]HOST is Windows 7 64bit[[BR]]GUEST is Windows XP

According my post at forums, I described this behavior when I work with version 4.3.26.

After I upgrade to version 5.0.0 still got similar behavior."	NoNoNo
21173	When Windows XP (Guest OS) is PAUSE and restarted, AUDIO is not output.	VirtualBox 7.0.0	2022-10-21T02:38:16Z	2022-10-21T02:38:16Z	2022-10-21T02:38:16Z	"When Windows XP (Guest OS) is PAUSE and restarted, AUDIO is not output.

  1. Start up Windows XP
  2. Windows XP is set to PAUSE
  3. (1 minutes elapse)
  4. (Release PAUSE)
  5. (AUDIO is output)
  6. (Set to PAUSE)
  7. 1 hour to 3 hours elapse
  8. Release PAUSE
  9. AUDIO is not output

Thank you very much for your cooperation. 
"	aokadak@…
21026	When Windows XP (Guest OS) is PAUSE and restarted, AUDIO is not output.	VirtualBox 6.1.36	2022-07-20T12:29:17Z	2022-07-20T12:29:17Z	2022-07-20T12:29:17Z	"When Windows XP (Guest OS) is PAUSE and restarted, AUDIO is not output.

  1. Start up Windows XP
  2. Windows XP is set to PAUSE
  3. (1 minutes elapse)
  4. (Release PAUSE)
  5. (AUDIO is output)
  6. (Set to PAUSE)
  7. 1 hour to 3 hours elapse
  8. Release PAUSE
  9. AUDIO is not output

Thank you very much for your cooperation. 
"	aokadak@…
20876	When Windows XP (Guest OS) is PAUSE and restarted, AUDIO is not output.	VirtualBox 6.1.32	2022-03-18T13:53:57Z	2022-03-18T13:53:57Z	2022-03-18T13:53:57Z	"When Windows XP (Guest OS) is PAUSE and restarted, AUDIO is not output. The procedure is shown below.
1.Start up Windows XP
2. Windows XP is set to PAUSE
3. 1 hour and 10 minutes elapse
4. Release PAUSE
5. AUDIO is not output
Thank you very much for your cooperation."	aokadak@…
16367	"When you start the VM that is in the ""Save State"", i receive the error message ""Failed to look for handy pages; rc = VERR_NO_MEMORY""."	VirtualBox 5.1.12	2017-01-08T19:35:44Z	2017-01-09T08:31:07Z	2017-01-09T08:31:07Z	"Ladies and Gentlemen,

Good Morning.

I have a machine with the Windows Vista Home Basic 32-bit operating system (host) with Service Pack 2 installed, as well as all the updates for this system. The computer has an Intel Pentium (R) Dual CPU T2370 of 1.73Ghz, with RAM of 2.00 GB, in this machine. I created a virtual machine with the Windows 7 Home Premium 32-bit (guest) operating system, with Service Pack 1 installed, as well as all the updates for that system. The computer has Intel Pentium (R) Dual CPU T2370 and 1.73Ghz, with RAM of 1.22 GB. The virtual machine was created using the version ""VirtualBox-5.1.2-108956-Win.exe"", since then I have updated VirtualBox with every release version, until the version ""VirtualBox-5.1.12-112440-Win.exe "". The virtual machine was in ""Save State"" in the ""VirtualBox-5.1.12-112440-Win.exe"" version. When I started Virtual Machine again with the following error message:

00: 00: 47.280263 PGM: Failed to look for handy pages; Rc = VERR_NO_MEMORY rcAlloc = VINF_SUCCESS rcSeed = VINF_SUCCESS cHandyPages = 0x8
00: 00: 47.280287 cAllPages = 0x5624d cPrivatePages = 0x4adb7 cSharedPages = 0x0 cZeroPages = 0xb46d"	MFS68
18050	White screen after Windows or other VM restart	VirtualBox 5.2.18	2018-10-13T11:50:13Z	2018-12-06T13:05:22Z	2018-12-06T13:05:22Z	Every time I restart Windows to install an update to Windows or another Vm running Linux, it displays a white screen in MacOS Mojave	Neptune BSC LLC
20520	White screen when 3D Acceleration enabled	VirtualBox 6.1.26	2021-08-22T17:17:49Z	2022-12-13T07:38:20Z	2022-12-13T07:38:20Z	"I get a white desktop screen after logging into Linux with 3D Acceleration enabled.

VM was working as expected until the August update to VirtualBox.

VirtualBox Version 6.1.26 r145957 (Qt5.6.2)
Oracle VM VirtualBox Extension Pack (Version: 6.1.26 r145957; VRDE Module: VBoxVRDP)

{{{
00:00:19.820085 VMSVGA3d: cap[9]=failed rc=VERR_INVALID_PARAMETER! {S23E8_TEXTURES}
00:00:19.820088 VMSVGA3d: cap[10]=failed rc=VERR_INVALID_PARAMETER! {S10E5_TEXTURES}
00:00:19.820301 VMSVGA3d: cap[62]=failed rc=VERR_INVALID_PARAMETER! {MISSING62}
00:00:19.820348 VMSVGA3d: cap[82]=failed rc=VERR_INVALID_PARAMETER! {SURFACEFMT_BC4_UNORM}
00:00:19.820350 VMSVGA3d: cap[83]=failed rc=VERR_INVALID_PARAMETER! {SURFACEFMT_BC5_UNORM}

00:00:20.333005 GUI: 2D video acceleration is disabled

00:04:46.441670 VMSVGA: PIXEL shader: Failed to create:
00:04:46.441718 0xFFFF0300, 0x0200001F, 0x80010005, 0x900F0000, 0x05000051, 0xA00F0001, 0x00000000, 0x3F000000,
00:04:46.441828 0xBF800000, 0x3F800000, 0x0200001F, 0x80000000, 0xA00F0800, 0x03000042, 0x800F0003, 0x90E40000,
00:04:46.441939 0xA0E40800, 0x02000001, 0x80080000, 0x80E40003, 0x02000001, 0x80070000, 0xA0000001, 0x03000005,
00:04:46.442043 0x800F0001, 0xA0E40000, 0x80FF0000, 0x02000001, 0x800F0002, 0x80E40001, 0x02000001, 0x800F0800,
00:04:46.442146 0x80E40002, 0x0000FFFF,

}}}"	Lynda
20644	Whonix Workstation is not working	VirtualBox 6.1.28	2021-10-27T17:55:04Z	2021-10-28T12:01:35Z	2021-10-28T12:01:35Z	Hello, I tried to use Whonix on VirtualBox. I started whonix gateway and it opened, then I tried to start whonix workstation while the gateway is open. I saw the boot screen and started but after the boot screen it does not open and freeze the screen and give me some bugs and logs (I added below). I tried to open workstation while the gateway is closed and it opened, but I need to use both gateway and workstation at same time. I was wondering how can I fix it, my virtualbox version is the newest one	Se
19766	Why can't I install Ubunut 20.04 (Mate) when WSL2 and Hyper-V is enabled?	VirtualBox 6.1.10	2020-07-25T18:19:39Z	2020-12-01T13:33:35Z	2020-12-01T13:33:35Z	"Why can't I install Ubunut 20.04 (Mate) when WSL2 and Hyper-V is enabled?

Windows 10 Pro, Insider, 2004, 20175.1000
VirtualBox 6.1.12
Ubuntu Mate 20.04 ISO

When the ISO boots, it runs a disk check which fails with 1 error.
This error has been like this for many months now.
It's not the ISO, as same ISO installs perfectly well with with VMWare Player 15.5.6

VB very nearly works - it boots to Try/Install screen. Quiting that screen allows the ISO to be ""tried"".
But starting the Install, it fails with a read-error.

"	jradxl
17567	why can't played  camera video  in windows 7  guest  by  web browser  with  DirectX	VirtualBox 5.1.30	2018-02-26T15:48:06Z	2018-03-04T22:48:41Z	2018-03-04T22:48:41Z	"we are developing a project based on virtualBox,
it's development  environment is: 
1. ubuntu-16.04 host
2. virtualBox-5.1.30
3. windows7  guest

if we set 3D accelerate In virtualBox-5.1.30,
when We play  camera video in windows7  guest by  web browser  with  DirectX11, the  video can't be played in windows 7  guest,
the windows 7  guest screen only show black, nothing can't be played.

Why does this happen?  How to resolved this problem?"	andy_fu800
19403	Why??? if i deactivated why can't i save ???	VirtualBox 6.1.4	2020-03-15T06:42:25Z	2020-03-15T06:58:32Z	2020-03-15T06:58:32Z	https://imgur.com/d7BYRWu	Fe-lipelinux
17023	Win 10 Surface Book and multiple Host screens, cannot start on Screen 3	VirtualBox 5.1.26	2017-08-19T22:03:11Z	2018-06-05T13:29:33Z	2018-06-05T13:29:33Z	I just bought a MS Surface Book laptop it run windows 10 Pro 64bit with Surface Doc. All OS patches and firmware has been updated. I have 16Gig of Ram and 1TB SSD.  WHen I launch a guest I get it to start on Vir screen 1 or 2, it sees Vir screen 3 but I cannot get into full screen on that monitor.  I have repeated this with 2 Windows guests that did run on another PC just hours ago. I've uninstalled Guest additions on the one Guest, Win 10 pro also, and reinstalled. I then goto VBox menu select View, Virtual Screen 1, and select Use Host screen 3, Screen stays stuck to Screen 2.  but the screen is indicated.	Mudoch
14634	Win 10 VM dual screen terminates to a single screen		2015-09-24T19:00:03Z	2016-10-17T04:41:11Z	2016-10-17T04:41:11Z	"I am using test build Version 5.0.5 r102814. The win 10 VM loses the second screen intermittently. i have to restart the VM in order to get 2 screens again. The Display setting on the Win 10 VM are as follows:

Video Memory - 256 MB
Monitor Count - 2
Scale Factor - 100%
No 3D or 2D acceleration
no Remote Display
no Video Capture
VM Memory allocated: 3072 MB
VM processors: 2

Current laptop system: Windows 10 Professional
laptop memory 32 GB
"	Centurion
19514	Win 10 x64 guest setup hangs on Win 7 x64 host if CPU count > 1	VirtualBox 5.2.40	2020-04-20T07:08:45Z	2020-04-21T14:19:46Z	2020-04-21T14:19:46Z	"If CPU count is more than one Windows 10 x64 guest hangs during setup on Windows 7 x64 host, while Windows 10 x32 and Windows 7 x64 guests are running fine. If CPU count is one Windows 10 x64 guest is running fine too. Problem exists regardless of chipset is ICH9 or PIIX3, EFI is enabled or disabled. Versions 5.2.38.136252, 6.0.18.136238 and 6.1.4.136177 are also affected.

Related tickets: #19352 (?), #18856, #15529."	Researcher
15083	Win 7 / Linux Guest - Cannot delete backup file on shared folder.	VirtualBox 5.0.14	2016-01-27T17:29:59Z	2016-01-27T17:29:59Z	2016-01-27T17:29:59Z	When a backup~ file is created in a directory within a VirtualBox's shared folder, the program that created the backup~ file cannot remove the file preventing the original file from being saved. Trying to remove the backup~ file manually via 'rm' results in an 'Operation not permitted.' message. The only way to remove the backup~ file is navigating to the directory from the Host system and removing the file that way.	agilis
19389	win 7 problemes	VirtualBox 6.1.4	2020-03-09T16:33:17Z	2020-03-09T17:11:43Z	2020-03-09T17:11:43Z	"Bonjour depuis quelques jours, windows 7 ne fonctionne plus complètement et s'arrête. Il me demande de terminer le processus alors que je n'ai pas utilisé du tout, les programmes internes. Je suis dans l'impossibilité de redémarrer windows et je dois arrêter la machine virtuelle.
Je suis sous la dernière version (Version 6.1.4 r136177 (Qt5.6.2).
Dois-je essayer de supprimer la machine virtuelle et la recharger ou bien tout désinstaller et recommencer le processus d'installation.
j'ai une version normale de windows 7 ?
Cordialement.
"	pascal28
11590	Win 7 VM slows down when presenting in GoToMeeting	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
14036	Win 8.1 guest vm machine hangs with VBoxGuestAdditions	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
14205	Win guests on Dell laptops have black display for integrated webcam via passthrough	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
20534	Win server 2008 does not autostart after update to 6.1.22_Ubuntur144080	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
19604	Win XP Crash during AVG Install	VirtualBox 6.1.8	2020-05-20T00:07:06Z	2020-05-20T00:07:06Z	2020-05-20T00:07:06Z	"Hi,
I was installing AVG AV in Win XP Box, which is running on a Win 8.1 machine. It resulted in a critical error which stopped the VM. The program prompted me to log a ticket and post the log and image.  How do I correct this?  I have been retrieving data from old FDDs in the VM.  Now my data is trapped in the VM.

Thanks,
JC-bnm "	JC-bnm
15559	Win-XP fails to start in normal/last-working-breakpoint 9 of 10 times	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
17114	Win10 guest hangs when USB attached	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
15638	Win10 Guests stopped working with upgrade to 5.1.	VirtualBox 5.1.0	2016-07-18T18:42:30Z	2019-02-25T17:38:24Z	2019-02-25T17:38:24Z	"I updated to V5.1.0 from V5.0.24 and my Win10 Guests stopped working.
During startup it detects a hardware change and tries to fix it.  there is of course no hardware change, just the VM change.

I had to roll back to V5.0.24 but will include a zip ups of a couple of VM Logs (including the definitions).  If there is anything else You could use let me know.  

Here is some basic systeminfo from the host windows 7 64bit computer.
{{{
Host Name:                 TWILIGHT
OS Name:                   Microsoft Windows 7 Ultimate 
OS Version:                6.1.7601 Service Pack 1 Build 7601
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
Registered Owner:          Thx
Registered Organization:   
Product ID:                00426-065-1786231-86699
Original Install Date:     15/12/2009, 4:51:11 PM
System Boot Time:          11/07/2016, 11:05:55 AM
System Manufacturer:       System Manufacturer
System Model:              System Product Name
System Type:               x64-based PC
Processor(s):              2 Processor(s) Installed.
                           [01]: Intel64 Family 6 Model 23 Stepping 6 GenuineIntel ~1995 Mhz
                           [02]: Intel64 Family 6 Model 23 Stepping 6 GenuineIntel ~1995 Mhz
BIOS Version:              American Megatrends Inc. 1009, 02/03/2009
Windows Directory:         C:\Windows
System Directory:          C:\Windows\system32
Boot Device:               \Device\HarddiskVolume3
System Locale:             en-ca;English (Canada)
Input Locale:              en-us;English (United States)
Time Zone:                 (UTC-06:00) Central Time (US & Canada)
Total Physical Memory:     24,575 MB
Available Physical Memory: 22,157 MB
Virtual Memory: Max Size:  49,223 MB
Virtual Memory: Available: 46,389 MB
Virtual Memory: In Use:    2,834 MB
Page File Location(s):     C:\pagefile.sys
Domain:                    GULFSTREAM
Logon Server:              \\TWILIGHT
Hotfix(s):                 536 Hotfix(s) Installed.
                           [01]: KB2849697
                           [01]: bla bla bla lots of hot fixes;
Network Card(s):           6 NIC(s) Installed.
                           [01]: Intel(R) PRO/1000 PL Network Connection
                                 Connection Name: Local Area Connection
                                 DHCP Enabled:    Yes
                                 DHCP Server:     10.0.0.75
                                 IP address(es)
                                 [01]: 10.0.0.30
                                 [02]: fe80::74fb:2690:81de:ce4d
                           [02]: Intel(R) PRO/1000 PL Network Connection
                                 Connection Name: Local Area Connection 2
                                 Status:          Media disconnected
                           [03]: Intel(R) PRO/1000 EB Network Connection with I/O Acceleration
                                 Connection Name: Local Area Connection 3
                                 Status:          Media disconnected
                           [04]: Intel(R) PRO/1000 EB Network Connection with I/O Acceleration
                                 Connection Name: Local Area Connection 4
                                 Status:          Media disconnected
                           [05]: Microsoft Loopback Adapter
                                 Connection Name: Local Area Connection 5
                                 Status:          Hardware not present
                           [06]: VirtualBox Host-Only Ethernet Adapter
                                 Connection Name: VirtualBox Host-Only Network
                                 DHCP Enabled:    No
                                 IP address(es)
                                 [01]: 192.168.56.1
                                 [02]: fe80::ad41:e302:b3e2:8e0f
}}}"	isgdre
16024	Win10 host Ubuntu 16.04 guest random crashes	VirtualBox 5.0.26	2016-10-04T08:05:56Z	2016-12-07T10:02:03Z	2016-12-07T10:02:03Z	"I am using Ubuntu 16.04 with X on Win10 host. It randomly crashes from time to time. I found a remedy. If I select Other 64bit OS from the settings, it does not crash anymore. Below is the Vbox.log file from a crashed machine (after machine was force shut down).
"	yurtesen
19784	Win10 Quick Assist screen-share shows corrupted desktop	VirtualBox 6.1.4	2020-07-30T23:43:15Z	2020-07-30T23:46:36Z	2020-07-30T23:46:36Z	"If Windows 10 guest shares its screen with a remote user using the built-in ""Quick Assist"" utility, the other user sees a corrupted screen.  Specifically, everything is slanted at a 45 degree angle (see screenshot).   It looks like each horizontal row of pixels is offset slightly from the previous one.   

HOST: Ubuntu linux 20.04, X-org, Intel graphics
GUEST: Windows 10 64-bit

STEPS TO REPRODUCE:
In some other Win10 machine (VM or real):
1. Start the ""Quick Assist"" app.
2. Click the ""Assist another person"" button at the bottom
   (sign in to a microsoft account if prompted)
   Note the ""Security code"" number displayed

In the Vbox VM Win10 guest:
3. Start ""Quick Assist""
4. Enter the Security code in the ""Code from assistant"" box

RESULTS: The remote Win10 sees the VM guest's desktop in an unusably skewed form
"	Jim Avera
18740	Win7 64 bit  guest crashes	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
13658	Win7 64bit guest changing color scheme, nothing happens	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
19645	Win7 VM (from p2v) freezes at random intervals	VirtualBox 6.1.10	2020-06-08T12:04:53Z	2020-06-08T12:46:06Z	2020-06-08T12:46:06Z	"I have a Win7 VM which is a P2V result from a laptop (i used VMWare Converter Standalone for the task). I then created a new VBox VM and used the .VMDK as a HDD.

I turned on the VM, let it discover all the drivers it wanted, restarted, etc. Finally i installed VBox drivers from the VM, restarted and everything seemed to work OK. Also performed several old drivers cleanup (uninstallations and removals from device driver), to minimize possible issues.

The VM works fine, except that after some time (randomly, usually 10-20 minutes), it just freezes. VBox's window is responsive but the guest OS is completely frozen. Trying to close the VM from the VBox's close window button, i select ""Send the shutdown signal"" and then press OK. It waits a few seconds and then it just closes the window.

Of course, the next time i start it, Windows report they had not been shutdown properly the last time. Also, the original laptop works just fine."	Wand
13758	Win7-64 install fro SCCM image	VirtualBox 4.3.20	2015-01-14T14:35:23Z	2015-01-14T14:35:23Z	2015-01-14T14:35:23Z	"new VM WIn7Ent64. install always fails after loading boot image from SCCM.
pls. see attached log."	Papika
16282	Win7: Cannot start a virtual box machine	VirtualBox 5.1.10	2016-12-12T10:56:06Z	2016-12-20T15:38:57Z	2016-12-20T15:38:57Z	"Cannot start a virtual box machine (configured for Windows 10) in Window 7 - it worked, but now it causes BSOD - APC_INDEX_MISMATCH (probably after Windows update).

The very same problem when I created a new (empty) virtual machine.

(Computer DELL Optiplex. I was using VirtualBox 5.0.x, but update for 5.1.10 did not solve the issue.)"	hrondra
15822	window guest on os x host, select multiple items with ctl right mouse click not torking	VirtualBox 5.1.4	2016-08-18T16:15:13Z	2016-09-15T16:33:14Z	2016-09-15T16:33:14Z	"if the control key is held down while single left clicking on an item in windows 7, it brings up the same menu that right clicking will bring up. The desired behavior is for the user to be able to select multiple items separately out of a group.  This has changed since vbox 5.0.n.  If the user has a trackpad or a laptop, and enables ""3 finger drag"", you can hold the ctl key and select the individual items by pointing to each item and doing a 3 finger drag with the ctl key held down.  however, this won't work with a mouse, not even the current touch sensitive apple mouse."	ascott
16623	Window position not saved correctly...	VirtualBox 5.1.18	2017-03-29T20:02:58Z	2017-12-24T10:37:01Z	2017-12-24T10:37:01Z	"VirtualBox Manager window will not save where placed by about a menu bar's height. Any place you put it on the desktop will place it approximately 20 pixels down from where you actually last left it upon relaunch of VirtualBox.

Others have tested that this bug currently exists in the 5.1.x series.

See community forum post entitled ""Window position not saved correctly...""."	starion
15766	Windows 10 - Black Screen After Logic	VirtualBox 5.1.2	2016-08-08T18:18:38Z	2016-08-08T18:18:38Z	2016-08-08T18:18:38Z	"Hello,

I have been able to reproduce this bug 3 times over the last few days. Essentially I would install VirtualBox. I would try to launch it, and it would not. I would restart my computer. It would take a very long time to reach the login screen. Once logged in, it would be only a black screen with cursor. CTRL +ALT+DEL will bring up the menu, but Task Manager only leads back to the black screen. Trying to shut down is blocked by an application, but Windows does not have a name for it, nor does it have an icon. Therefore I had to force shutdown.

Safe Mode opens, but trying to interact with anything crashes File Explorer. I have launched Windows PE and recovered from backup. However this problem occurs every time I install VirtualBox. Unfortunately this means I can't use it.

Hardware:
32 GB of DDR4
i5 6600k
GTX 1070
ASUS Z170-A

I was thinking maybe there is some issue with compatibility of the display drivers that VB installs?

"	Grimakis
16231	Windows 10 - Problem with brightness and 2D/3D	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
18681	Windows 10 1903 + VirtualBox 6.0.8	VirtualBox 6.0.8	2019-05-29T19:00:57Z	2019-05-30T16:39:49Z	2019-05-30T16:39:49Z	"I recently installed Windows 10 1903 (May 2019) update and installed VirtualBox 6.08 and non of my VMs load any more:

'Failed to open a session for the virtual machine Windows'.

I have re-installed Virtualbox 6.0.8 - no change
Tried starting vboxdrv driver - fails to load.
Removed VB 6.0.8 and installed VB 6.0.6 - no change.
Checked that Hyper-V is not installed, removed Windows Sandbox - no change.
Stopped AV and Firewall software - no change.

Any ideas on how to fix this?
"	Peter Hutchison
19464	Windows 10 64bit Not Available In The Guest Templates	VirtualBox 6.1.4	2020-04-07T01:20:06Z	2020-04-08T11:06:27Z	2020-04-08T11:06:27Z	"I am facing an issue with version 6.1.4 r136177 (Qt5.6.2). I installed it, enabled the virtualization in BIOS then Windows 64bit guest became available in the OS list. I installed it, but after restart my host Machine the option to create a new Windows 64bit guest is not available anymore. I tried to uninstall, removed registers, path, etc but nothing is working. I tried all the suggestions of the VirutalBox forum but nothing is working. 

Please find below my current configuration:

Host Information:

-> Lenovo T440
-> Windows 10 Enterprise Version 1703 OS Build 15063.2108
-> Virtual Box Version 6.1.4 r136177 (Qt5.6.2)
-> Windows Hyper-V is disabled
-> Virtualization BIOS is enabled (VT-X)
-> CPU virtualization is enabled
-> Containers is disabled
-> Windows Subsystem for Linux is disabled"	Naua
15591	Windows 10 and Host Only Networking	VirtualBox 5.0.24	2016-07-10T20:35:10Z	2016-07-10T20:35:10Z	2016-07-10T20:35:10Z	"I cannot telent to my Fedora WS 23 64 bit guest from a Windows 10 host. I have tried the folowing:
Turn off Windows firewall completely (just temporarily)
Configure Fedora (guest) firewall to allow post 23 and telnet, tcp
Ping guest from host, this works
Reinstall vbox driver for host only (already up to date)
changing the network adapter type
Turning it off and on again

I have had the same problem when using Ubuntu. 
The adapter appears in the guest if I do ifconfig.
The address appears if I do ipconfig (from windows)

I am at my wits end with this, any help appreciated.
"	big nose
15663	Windows 10 BSDO in VirtualBox 5.1	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
17143	Windows 10 BSOD if Guest OS started	VirtualBox 5.1.28	2017-10-06T09:47:15Z	2017-10-06T09:47:15Z	2017-10-06T09:47:15Z	"Hello.
If I start guest operation system - I tried FreeBSD, Ubuntu, my laptop got BSOD. Windows 10 Enterpise  1703 (OS Build 15063.384). I made searh about this type of issues - WTx - instructions enabled in BIOS and HYPER-V uninstalled.
"	lvesel
18175	"Windows 10 build 1709 build 16299 64bit VM is not working showing error as ""Error In supR3HardenedWinReSpawn"""	VirtualBox 5.2.22	2018-12-10T10:11:10Z	2018-12-10T16:19:24Z	2018-12-10T16:19:24Z	"Windows 10 build 1709 , Virtualbox is not working showing error as ""Error In supR3HardenedWinReSpawn"". Windows 10 build 1703 it was working good. After updation it's not working. Please solve the issue."	Ekanath
15556	Windows 10 consistent video freeze	VirtualBox 5.0.24	2016-06-29T10:45:21Z	2016-06-29T10:49:43Z	2016-06-29T10:49:43Z	"Running on Windows 10 guest on a Windows 10 host with VB 5.0.24, updated extensions on the guest.

Under load, the video freezes requiring the VM to be restarted.
This happens constantly and makes the VMs unusable.

Tried to run VM with debug but the console command doesn't show any console.
Attaching the relevant vbox.log."	EPinci
16903	Windows 10 crashes on VirtualBox session startup	VirtualBox 5.1.22	2017-07-14T21:03:03Z	2017-08-17T15:27:49Z	2017-08-17T15:27:49Z	"VirtualBox: 5.1.22
Host: Windows 10
Guest: Kali

Windows 10 crashes when starting Kali - the blue screen shows error IRQL_UNEXPECTED_VALUE.

"	caveman14
17736	Windows 10 displays random BSOD with 0x00000109	VirtualBox 5.2.10	2018-05-05T15:33:48Z	2018-05-05T22:31:11Z	2018-05-05T22:31:11Z	"In Windows 10 version 1803 and 1709 it displays random BSODs with 0x00000109. the module is ntoskrnl.exe. in 5.2.8 it would also freeze the VM until you reopen the VM. 5.2.10 fixed the freezing when the BSOD appears bug.
"	Neptune BSC LLC
17404	Windows 10 guest aborts on 5.2.4	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
21127	windows 10 guest crash	VirtualBox 6.1.38	2022-10-11T08:46:51Z	2022-10-11T08:46:51Z	2022-10-11T08:46:51Z	"I running VB on linux-mint 21. kernal: 5.15.0-46.
Windows 10 guest crashed after running for a while
upgrade kernal to 5.15.0-50, still crash  "	virtTheWorld
16555	Windows 10 guest crashes during USB disk access after upgrade to v5.1.16	VirtualBox 5.1.16	2017-03-13T04:35:53Z	2017-03-13T15:59:09Z	2017-03-13T15:59:09Z	"I have been running a Windows 10 Pro 64-bit virtual machine on my early 2016 MacBook Pro for several months with no issues. I am running the latest macOS Sierra. 
Today I upgraded from v5.1.14 to v5.1.16. Now the machine will crash (abort) at random times but usually coinciding with access to my USB external drive. 
I had to revert to v5.1.14 and roll Guest Additions back, then the system was back to normal and no crashes.
I will be sticking to v5.1.14 until the broken update is fixed."	S_Vbox_User
20463	Windows 10 guest crashes on startup	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
17758	Windows 10 guest crashes when Settings are opened	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
15620	Windows 10 guest freeze on startup (Linux x64 host)	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
18334	Windows 10 guest freeze or crash	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
19141	windows 10 guest hangs on linux 5.3.12 host	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
19669	Windows 10 Guest just crshed, no idea why	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
17546	Windows 10 guest keeps hanging	VirtualBox 5.2.6	2018-02-16T19:53:37Z	2018-02-16T19:53:37Z	2018-02-16T19:53:37Z	"I'm using VirtualBox v5.2.6r120293. My host and guest are Windows 10. The guest is frequently hanging, becoming completely unresponsive; when it does, VirtualBox Manager will oftentimes be unresponsive, too. My only recourse is to close either the guest or the VirtualBox Manager, sometimes having to resort to doing so via Task Manager. After such an event, the guest has a status of ""Aborted"" but I can re-start it without apparent issue.

The guest just froze again; VirtualBox Manager didn't freeze this time. The VirtualBox Log Viewer lists five log files; however, I don't see much of interest therein except the last line which reads (in VBox.log and VBox.log.2) ""GUI: Request to close machine-window."", (in VBoxHardening.log) ""4a88.4ccc: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0xcfffffff (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 1429056 ms, the end);"", and (in VBox.log.3) ""GUI: Passing request to close Runtime UI from machine-logic to UI session."" I've attached the log from Machine > Show Log > Save.

Any suggestions on how to resolve this issue?"	CGW
21049	Windows 10 Guest login on Fedora 36 crashes after mouse movement	VirtualBox 6.1.36	2022-08-05T20:56:09Z	2022-08-08T20:16:28Z	2022-08-08T20:16:28Z	"Linux cn1-vcl2 5.18.15-200.fc36.x86_64 #1 SMP PREEMPT_DYNAMIC Sun Jul 31 21:30:34 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

VirtualBox 6.1.36 with 6.1.36 extension pack installed

Windows 10 is 21H2, with Microsoft updates up to June 2022.

Linux display manager: gdm

Have been using a script for over 10 years to start the VM and provide it a video hint for a 1920x1080 screen about a minute after starting. The way it is started:

VBoxSDL --startvm win10 --fullscreen --nohostkey

Prior to Fedora 36, we were on Fedora 34 and running VB 6.1.34 with no issues. After upgrading to Fedora 36 and installing VB 6.1.36, we noticed that the Windows 10 VMs previously running could not be logged into, since they crash immediately upon user input, and the script restarts the VM again.

There is nothing in the VBox.log file to indicate what happened. It may be related to the random changes in Linux 5.17.11+, per:

https://lore.kernel.org/lkml/YoTVIGiXUO2l8Czm@zx2c4.com/

and the fixed 20914 ticket [https://www.virtualbox.org/ticket/20914]

but the Linux 5.18 patches are in 6.1.36.

I have found a workaround for it -- use the VMSVGA graphics controller for the Windows 10 VM. The VBoxVGA and the VBoxSVGA graphics controllers are sensitive to mouse movements. The guest additions can be 6.1.34 or 6.1.36 -- either work with VMSVGA. I had also increased the VRAM to 256 (MB), but feel that is not part of the solution and did not test without it, as I had changed VRAM to 256 before without the graphicscontroller change and it failed, using VBoxVGA.

VBoxManage modifyvm win10 --graphicscontroller VMSVGA --vram 256

before my VBoxSDL command now fixes the problem, but VMSVGA's possible performance problem and its lack of ability to handle video hints via:

VBoxManage controlvm win10 setvideomodehint 1280 1024 32

make it less desirable.


"	Stephen Rondeau
20453	Windows 10 guest on Ubuntu host is extremely slow if cpu > 1	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
20180	Windows 10 guest OS crashes with STATUS_DATATYPE_MISALIGNMENT exception	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
19200	Windows 10 Guest wastes (constantly uses) a full CPU core on the Host, non-stop, even when Guest is not using CPU	VirtualBox 6.1.0	2020-01-06T20:48:17Z	2020-03-02T04:57:12Z	2020-03-02T04:57:12Z	"==============================================[[BR]]
Problem:

Windows 10 Guest wastes (constantly uses) a full CPU core on the Host, non-stop, even when Guest is not using CPU.[[BR]]
Windows 8.1 Guest does not waste a full CPU core on the Host.[[BR]]

==============================================[[BR]]
VMs: [https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/][[BR]]

==============================================[[BR]]
Problem Behavior:[[BR]][[BR]]
Guest: MSEdge.Win10.VirtualBox - v1809 - Build 17763.379 - October 2018 Update (VM Build 20190311)[[BR]]
-> Guest used CPU non-stop for ~30 mins (mscorsvw, ngen, wsappx, Windows Update, Antimalware Service Executable)[[BR]]
-> Host showed VirtualBox.exe/VirtualBoxVM.exe using a full core non-stop[[BR]]
-> Even after ~30 mins, when Guest stopped using CPU, host STILL showed a full core being used by VirtualBox.exe/VirtualBoxVM.exe[[BR]]
-> Guest - Went to Windows Update and clicked Restart, which updated to: v1809 Build 17763.379[[BR]]
-> Host STILL showed a full core being used by VirtualBox.exe/VirtualBoxVM.exe[[BR]]
-> Repeated for another Windows Update, updating to v1809 Build 17763.914[[BR]]
-> Host STILL showed a full core being used by VirtualBox.exe/VirtualBoxVM.exe[[BR]]
-> Tried Shutdown then Start -> Normal Start[[BR]]
-> Host STILL showed a full core being used by VirtualBox.exe/VirtualBoxVM.exe[[BR]]

For all tests:[[BR]]
Paravirtualization Interface: Hyper-V[[BR]]

==============================================[[BR]]
Host: Windows 10 Insider Fast v2004 Build 19041.1, Oracle VirtualBox v5.2.35 Test Build 135314[[BR]]

Guest: MSEdge.Win10.VirtualBox - v1809 - Build 17763.379 - October 2018 Update (VM Build 20190311)[[BR]]
-> VirtualBox.exe using a full core non-stop!

Guest: IE11.Win81.VirtualBox (VM Build 20180102)[[BR]]
-> VirtualBox.exe does NOT use a full core! (Guest uses some CPU, but when Guest stops using it, host stops using it)

==============================================[[BR]]
Host: Windows 10 Insider Fast v2004 Build 19041.1, Oracle VirtualBox v6.0.15 Test Build 135299[[BR]]

Guest: MSEdge.Win10.VirtualBox - v1809 - Build 17763.379 - October 2018 Update (VM Build 20190311)[[BR]]
-> VirtualBoxVM.exe using a full core non-stop!

Guest: IE11.Win81.VirtualBox (VM Build 20180102)[[BR]]
-> VirtualBoxVM.exe does NOT use a full core! (Guest uses some CPU, but when Guest stops using it, host stops using it)

==============================================[[BR]]
Host: Windows 10 Insider Fast v2004 Build 19041.1, Oracle VirtualBox v6.1.0 Build 135406[[BR]]

Guest: MSEdge.Win10.VirtualBox - v1809 - Build 17763.379 - October 2018 Update (VM Build 20190311)[[BR]]
-> VirtualBoxVM.exe using a full core non-stop!

Guest: IE11.Win81.VirtualBox (VM Build 20180102)[[BR]]
-> VirtualBoxVM.exe does NOT use a full core! (Guest uses some CPU, but when Guest stops using it, host stops using it)

==============================================[[BR]]
Host: Windows 10 Release v1909 Build 18363.535, Oracle VirtualBox v5.2.35 Test Build 135314[[BR]]

Guest: MSEdge.Win10.VirtualBox - v1809 - Build 17763.379 - October 2018 Update (VM Build 20190311)[[BR]]
-> VirtualBox.exe using a full core non-stop!

Guest: IE11.Win81.VirtualBox (VM Build 20180102)[[BR]]
-> VirtualBox.exe does NOT use a full core! (Guest uses some CPU, but when Guest stops using it, host stops using it)

==============================================[[BR]]
Host: Windows 10 Release v1909 Build 18363.535, Oracle VirtualBox v6.0.15 Test Build 135299[[BR]]

Guest: MSEdge.Win10.VirtualBox - v1809 - Build 17763.379 - October 2018 Update (VM Build 20190311)[[BR]]
-> VirtualBoxVM.exe using a full core non-stop!

Guest: IE11.Win81.VirtualBox (VM Build 20180102)[[BR]]
-> VirtualBoxVM.exe does NOT use a full core! (Guest uses some CPU, but when Guest stops using it, host stops using it)

==============================================[[BR]]
Host: Windows 10 Release v1909 Build 18363.535, Oracle VirtualBox v6.1.0 Build 135406[[BR]]

Guest: MSEdge.Win10.VirtualBox - v1809 - Build 17763.379 - October 2018 Update (VM Build 20190311)[[BR]]
-> VirtualBoxVM.exe using a full core non-stop!

Guest: IE11.Win81.VirtualBox (VM Build 20180102)[[BR]]
-> VirtualBoxVM.exe does NOT use a full core! (Guest uses some CPU, but when Guest stops using it, host stops using it)
"	Jacob Klein
18460	Windows 10 guest works very slowly. This defect appeared with 6.0.x versions.	VirtualBox 6.0.4	2019-02-28T12:34:32Z	2019-04-15T01:51:59Z	2019-04-15T01:51:59Z	"Host: Win10 Pro x64 1809 17763.316

Guest: Win10 Pro x86 1809 17763.316

Guest works correctly on 5.2.24.

This defect with guest performance appeared with 6.0.x versions. 

I have tested on 6.0.5 revision 128999 test build because I previously created ticket #18319. The defect of serial ports has probably been fixed.  

There is a performance problem with the guest machine.
It utilizes 50% of host CPU (4 cores), the guest works very slowly.
The log file is full of 
""TM: Giving up catch-up attempt at a ""x"" ns lag; new total: ""y"" ns""

The guest has a delay in every operation. Sometimes it freezes and suddenly unfreezes, makes some operations and freezes again.

Guest virtual hard disc blinks red/green dot on status bar most of the time but host hard disc is not active.  
"	Vonkaz
14897	Windows 10 handles VBoxManage.exe incorrectly when importing and listing	VirtualBox 5.0.10	2015-12-04T03:50:35Z	2015-12-09T12:11:43Z	2015-12-09T12:11:43Z	"I was able to reproduce this with 2 PC's, both Windows 10, trying both an older version (4.3.20) and latest version (5.0.10):

When using VBoxManage.exe to import or list vms (possibly others), the following happens:

 1. The item is reported to be imported successfully
 2. The .vbox file shows in \VirtualBox VMs\xx.vbox
 3. The new VM is NOT added to the GUI
 4. Typing 
{{{
vboxmanage.exe list vms
}}}
 shows 0 vms
 5. Trying to manage the VM using vboxmanage.exe fails since the VM isn't detected
 6. However, if I were to elevate my prompt and type 
{{{
vboxmanage list vms
}}}
, the vm shows up.
 7. As a workaround, if I were to double click the \VirtualBox VMs\xx.vbox file, it would add it successfully to the GUI and 
{{{
vboxmanage.exe list vms
}}}
 would then list them successfully in non-elevated prompt.

This blocker bug breaks all batch files that use vboxmanage to import a VM and configure it. The only workaround is to launch the .vbox file directly, but that will launch the GUI and is very unprofessional when using scripting."	dylanh724
18856	Windows 10 hangs with High CPU Usage after changing number of Cores	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
16203	Windows 10 Pro 64Bit crashes when VirtualBox 5.1 loads	VirtualBox 5.1.8	2016-11-19T01:12:05Z	2016-11-21T11:04:15Z	2016-11-21T11:04:15Z	"I installed VirtualBox 5.1 successfully 
but when it starts, the computer crashes.
"	tonyc49
19609	Windows 10 Pro failed to work inside Ubuntu 20 VirtualBox	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
18154	Windows 10 Pro Host 64-bit only supports 32-bit OS	VirtualBox 5.2.22	2018-11-28T01:45:33Z	2018-11-30T01:38:59Z	2018-11-30T01:38:59Z	I already checked in the BIOS and I have the intel virtual technology option enabled, what additional information do you need to help me with this case, thanks	jesusemarquezz
13937	Windows 10 TP network bridge causes major fault	VirtualBox 4.3.24	2015-03-07T19:11:33Z	2015-04-02T09:32:55Z	2015-04-02T09:32:55Z	"This is similar to ticket number 13912. When VB is installed in the latest beta of Windows 10 technical preview, the host machine halts upon restart. The only thing working is the mouse, nothing else works.

The computer works fine if the network cards are disabled in Windows, but this leaves end users unable to access any network."	dhrida
20221	windows 10 unmountable boot volume	VirtualBox 6.1.18	2021-02-24T16:18:44Z	2021-02-24T16:48:37Z	2021-02-24T16:48:37Z	"I have an HP Envy 17 that has two disk drives, the original 1TB hard disk, and a second 480GB SSD. I have been running Windows 7 on the SSD with the hard drive as backup.

I just updated the hard disk to Windows 10 which I boot by popping out the SSD (which is in the DVD slot) so that Windows then boots from the second drive. 

I want to be able to run Windows 7 normally and use VirtualBox to boot up Windows 10 to run one application which won't run on Windows 7.

I have created a virtual raw disk for Drive 1 and when I attempt to boot it, I get the error message about the boot volume not being mountable. This happens after I get the windows logo and circle for a while.

Anyone have any suggestions how I can get this to work ? 
"	Wewebb14
19427	windows 10 virtualbox 6.1.2 wierd cant copy / move webm files	VirtualBox 6.1.2	2020-03-24T11:05:34Z	2022-09-05T14:45:36Z	2022-09-05T14:45:36Z	"windows 10 virtualbox 6.1.2 wierd cant copy / move webm files out of vbox subdir 

windows 10 file manager just hangs !

is this a windows 10 bug or is virtualbox locking the files in some strange way ?
[[Image()]]"	clive darra
19038	Windows 10 VirtualBox uninstallation required for 6.0.12, or application within VM crashes.	VirtualBox 6.0.12	2019-10-22T17:14:21Z	2019-10-22T17:14:21Z	2019-10-22T17:14:21Z	"Submitted for third-party in order to document rare issue encountered by a third party.

Third-party virtualizes a physical classroom disk image with VirtualBox for portability, deployment, and testing, and has done so for years.

A recent upgrade from 6.0.10 to 6.0.12 caused a commercial application within the VM to crash when accessing HTML files. We determined that UNINSTALLING 6.0.10 and then conducting a fresh installation of 6.0.12 solved this application crash, so something is not being uninstalled properly during the upgrade process.

I apologize for the lack of log files. Third party encountered this bug on a production machine and deadlines prevented retrieval of additional troubleshooting assistance. 6.0.12 was already uninstalled and 6.0.14 freshly installed, without issue."	.
20116	Windows 10 VirtualBoxVM guest crashes when updating Windows 10 inside	VirtualBox 6.1.16	2021-01-04T17:31:01Z	2021-01-04T17:31:01Z	2021-01-04T17:31:01Z	"My Windows 10 VirtualBoxVM guest crashed when running a Windows 10 update. An attempted boot after this also crashed. Booting in turn after the second crash resulted in a hang.

See attached log files."	Lars Sonchocky-Helldorf
20241	Windows 10 Vm always crashes on startup	VirtualBox 6.1.18	2021-03-09T12:30:21Z	2021-03-10T00:03:18Z	2021-03-10T00:03:18Z	"I downloaded the 20H2 windows 10 iso from Microsoft, and created a 64-bit Vm with that iso. However, every time the Vm starts up, I am told that a critical error has occurred and my Vm stops. I tried to increase Ram, and redownload the iso among other things, but I am not good at debugging. I would really appreciate if somebody could help me.
Thanks"	ceddub
18254	Windows 10 VM disconnected shared drive drive Z:	VirtualBox 6.0.0	2018-12-31T14:41:05Z	2018-12-31T18:57:40Z	2018-12-31T18:57:40Z	"This communication concerns an issue whereby subsequent logins to a Windows 10 Pro based VM show a disconnected drive Z:, even though you can still navigate to it.

Please be kind enough to see the attached (I hope ;) ) PDF file, which explains the whole issue, together with images.

With kindest regards

David"	DJB
18099	Windows 10 won't start	VirtualBox 5.2.20	2018-11-03T06:55:39Z	2018-11-03T06:55:39Z	2018-11-03T06:55:39Z	I've got other virtual machines running without any problems (windows server 2008, ubuntu, centos, windows 7) but windows 10 won't even start.	AlexFlynn
13912	Windows 10(host) and virtual box	VirtualBox 4.3.24	2015-03-03T05:06:52Z	2015-03-04T22:41:18Z	2015-03-04T22:41:18Z	Host pc-surface pro (i5) causing black screen after install of virtual box.	Bluwolf024
18188	WINDOWS 10/HP UPDATED CAN NOT OPEN VIRTUAL BOX	VirtualBox 5.2.22	2018-12-16T16:34:41Z	2018-12-18T23:14:41Z	2018-12-18T23:14:41Z	"AFTER WINDOWS 10/HP UPDATE VIRTUAL BOX WOULD NOT OPEN.
I TRIED THE VIRTUAL BOX 6.0 TEST BUILD BUT FILE RUN HAD ERRORS.
I TRIED UPDATING VIRTUAL BOX 5.2.23 EXE, EXT AND GUEST ADDITIONS.
I ATTACHED A SCREEN SHOT OF THE VIRTUAL BOX OPENING SCREEN.
I DO NOT HAVE A LOG FILE AVAILABLE.

REALLY APPRECIATE ANY HELP.
THANKS, DANNY."	dannyo1
18190	WINDOWS 10/HP UPDATED CAN NOT OPEN VIRTUAL BOX	VirtualBox 5.2.22	2018-12-16T18:22:02Z	2018-12-17T12:03:43Z	2018-12-17T12:03:43Z	"AFTER WINDOWS 10/HP UPDATE VIRTUAL BOX WOULD NOT OPEN.
I TRIED THE VIRTUAL BOX 6.0 TEST BUILD BUT FILE RUN HAD ERRORS.
I TRIED UPDATING VIRTUAL BOX 5.2.23 EXE, EXT AND GUEST ADDITIONS.
I ATTACHED A SCREEN SHOT OF THE VIRTUAL BOX OPENING SCREEN.
I DO NOT HAVE A LOG FILE AVAILABLE.

REALLY APPRECIATE ANY HELP.
THANKS, DANNY."	dannyo1
16978	Windows 10: scan for hardware changes freezes after loading Virtual Box manager	VirtualBox 5.1.26	2017-08-03T21:53:05Z	2019-09-04T20:44:46Z	2019-09-04T20:44:46Z	"Windows 10 Pro
Virtual Box  5.1.26 r117224 (Qt5.6.2)

Restart windows 10
Open device manager
Action: Scan for Hardware Changes

The scan completes normally

Open the Virtual Box manager (doesn't matter if we run a session)
Close virtual box manager
Open device manager
Action: Scan for Hardware Changes

The scan never seems to complete.  The ""Scanning plug and play compliant hardware..."" dialog stays on screen.

Plugging in a new device (such as a USB device) does nothing.   It is not recognized by Windows.

Something happens to windows when the virtual box application is loaded.

"	K1MGY
21387	Windows 11 BSOD	VirtualBox 6.1.28	2022-12-31T17:03:15Z	2023-01-04T12:24:24Z	2023-01-04T12:24:24Z	"After upgrading to Windows 11 and performing the installation steps below, I repeatedly got BSOD after issuing 'vagrant up' command. Since I need a working VB and could not find a working solution using Windows 11, I downgraded to Windows 10.

Upgraded from Windows 10 21h2 to Windows 11 22h2, upgraded Vagrant to 2.3.4 (required for Windows 11), upgraded Virtualbox to 6.1.28 (required for Windows 11), using Homestead box version 11.3.0 (unchanged), using existing homestead.yaml."	white-tiger
21135	Windows 11 guest hangs at startup on Linux host	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
21506	Windows 11 guest is freezing when trying to install an Windows Update	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
21242	Windows 11 screen freeze with CPUs 100% busy	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
17943	Windows 2000 image does not start	VirtualBox 5.2.18	2018-08-21T09:42:13Z	2018-08-22T16:22:12Z	2018-08-22T16:22:12Z	"Hi,

I'm trying to run Windows 2000 image, but i'm stuck just after the Windows 2000 start (black screen with no error)

Find vbox.log attached"	Regis Pedros
20831	Windows 2008 R2 issues.	VirtualBox 6.1.32	2022-02-17T10:33:10Z	2022-03-02T07:28:34Z	2022-03-02T07:28:34Z	"Good day.
We have windows 2008 R2 enterprise as a host running on dual Xeon Silver 4210 processor mounted on ASUS motherboard Z11PR-D16 with 392 Gb of memory.
All guest machines are Windows 7 x64 with 6 Gb memory.
We faced this issue: we can run 23 VMs concurrently, but when we start 24-th VM an error appears: 
""The virtual machine 'xxx' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\VMs\XXX\Logs\VBoxHardening.log'.
E_FAIL (0x80004005)
MachineWrap
IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}""
There are two logs attached, with successful start and failed one.
VirtualBox version: 6.1.32.
Successful start log
https://www.mediafire.com/file/t38s7g1r0bt4j1j/Logs-success.zip/file
Failed start log
https://www.mediafire.com/file/2v2yrjyna8toyrl/Logs-error.zip/file
"	ZMKS
20647	Windows 3.11 not working with hardware virtualization	VirtualBox 6.1.28	2021-10-30T17:22:22Z	2021-10-30T17:29:23Z	2021-10-30T17:29:23Z	If you install MSDOS 6.22 and Windows 3.11 in a Virtualbox machine, Windows 3.11 cannot start when hardware virtualization is enabled (mandatory in VB 6.1). The same virtual machine works OK in VB 6.0 with the hardware virtualization disabled. Windows 3.1 is not affected, only Windows 3.11 (Windows for Workgroups). Is there any workaround for this problem?	Iker Rodriguez
14262	WIndows 7 64 bits guests crash on 32 bits Linux host with VirtualBox v5.0	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
18628	Windows 7 crash (blue screen) on start VM	VirtualBox 6.0.6	2019-05-08T12:26:26Z	2019-05-08T12:26:26Z	2019-05-08T12:26:26Z	On start VM, Widows 7 crash (blue screen).	akurgan
16536	Windows 7 guest - cannot control-click to select items	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
15281	Windows 7 guest hangs reading hard disk	VirtualBox 5.0.16	2016-03-29T18:12:37Z	2016-12-29T20:31:35Z	2016-12-29T20:31:35Z	"Hi,

I used to use a Windows XP guest on my MacBook host so I could use some Windows-only software in school projects and works, and I kept using this older version of Windows just because it was lighter to run and because it required less HDD space. But now that I need some software that requires a more recent version of Windows, I created a new VM with Windows 7.
The problem is that my new VM sometimes hangs and becomes inoperational! Even in VirtualBox's menu I can't shut it down (a timer appears saying that it will be shutdown, but said timer keeps increasing and it never shuts down). When this happens, if I check the Activity Monitor on the Disk section, it says that it is reading at over 300MB/s!! And it only stops if I force stop the VirtualBox VM process...
This happens quite randmly, because even if I just turn the VM on and leave it without oppening anything, after some time the Activity Monitor shows a rising reading activity and then the VM hangs. My Mac keeps pretty responsive, as usual, though.

Host OS: OS X El Capitan 10.11.4
Guest OS: Windows 7 Professional x64
VirtualBox guest settings:
    Chipset: PIIX3
    I/O APIC: enabled
    CPUs: 1
    PAE/NX: enabled
    Storage Controller: SATA AHCI without Host I/O Cache, show as SSD

I tried changing the chipset, I even changed from 2 CPUs to 1 (saw in a post that it could cause ""over comitment"")... I'm getting desperate, because I need to finish my projects. Please help me.

Thank you in advance!
Best regards"	alexivia
13599	Windows 7 guest renders Linux host unresponsive; uncompleted fence warnings	VirtualBox 4.3.18	2014-11-07T10:52:40Z	2014-11-07T13:14:19Z	2014-11-07T13:14:19Z	"Host: Ubuntu 12.04.5 LTS, running Virtualbox 4.3.18-96516~Ubuntu~precise from your repo.

Guest: Windows 7 64-bit, 3D accelleration on, WDDM driver, using Aero. Guest additions are up to date.

After some time the host system will almost completely stop responding to UI input---screen repaints and mouse moves by tiny amounts every few seconds or so (think: forkbombs or paging hell). SSHing in and the text console remain responsive. The host has not run out of memory, the only notable CPU usage is the VirtualBox process for that guest maxing a single core, there is no substantial disk activity. Trying to close the VM via the UI didn't managed to finish painting the power-off dialogue in a timely fashion. The VM does not appear to be able to complete processing VBoxManage commands either although the log does show they are getting through.

The log contains:
{{{
75:18:45.743604 Guest Log: VBoxMP::vboxCmdVbvaCheckCompletedIrqCb: WARNING! :no vbva
75:18:45.743733 Guest Log: VBoxMP::VBoxVBVAExAllocContiguous: WARNING! :Host did not clean up the buffer!
75:18:45.743863 Guest Log: VBoxMP::VBoxCmdVbvaSubmitLock: WARNING! :failed to allocate contiguous buffer, trying nopping the tail
92:07:13.526281 Guest Log: VBoxMP::DxgkDdiQueryCurrentFenceNew: WARNING! :=>DxgkDdiQueryCurrentFenceNew
92:07:13.526395 Guest Log: VBoxMP::DxgkDdiQueryCurrentFenceNew: WARNING! :uncompleted fences, u32FenceSubmitted(2961375), u32FenceCompleted(2961374) u32FenceProcessed(2961374)
}}}

The last line repeats. (Will attach full logs.)

Host binary nVidia drivers recently upgraded to 304.123-0ubuntu0.0.1, but have been running them all week; problem has only occured overnight Thursday, and repeated again Friday morning. Disabling 3D accelleration seems to have stopped the problem for now but this may be a red herring. Guest has not had any other changes recently, although has experienced graphical flickering since VirtualBox (I think) 4.3.14. Otherwise has been working for months.

A Kubuntu 14.04.1LTS guest with 3D accelleration running at the same time (all week) has not been affected. No occurences of ""WARNING"" in its current log.

Ticket #13510 is about the same log error message but with different symptoms."	Philip Boulain (SW)
16946	Windows 7 Home Premium with VirtualBox 5.1.24 64-bit VMs not offered	VirtualBox 5.1.24	2017-07-26T13:07:16Z	2017-07-28T12:48:36Z	2017-07-28T12:48:36Z	"Problem:
- When I click New in VirtualBox, no matter which Type I select, there are no 64-bit choices listed in the Version, only 32-bit choices.

This is what I have:
- ASUS laptop
- Windows 7 Home Premium, 64-bit

This is what I did:
- Upgraded to VirtualBox 5.1.24.
- Ran this successfully in an elevated cmd window:
    bcdedit /set hypervisorlaunchtype off
- Enabled VT-d in my BIOS.  I do not see any setting named Virtualization.

Priority is 'blocker', because I cannot install Windows Server 2016."	clairestreb
13705	Windows 7 Host and Linux guest, BSOD on host	VirtualBox 4.3.20	2014-12-20T05:41:09Z	2015-10-05T22:30:45Z	2015-10-05T22:30:45Z	"I ran 4.3.12 for quite awhile.  After I jumped to 4.3.20, I am now getting BSOD every now and then.  I've done a memory scan, just to be sure I don't have failing RAM.  Anything else I can do to get more information?

I'm not sure if the windows event viewer files are useful or not, but I'm attaching them."	Trent
13998	Windows 8 - VirtualBox Disables Wireless Display Support	VirtualBox 4.3.26	2015-03-27T14:31:59Z	2016-02-29T07:26:12Z	2016-02-29T07:26:12Z	"See https://forums.virtualbox.org/viewtopic.php?f=2&t=66827

I found this out after struggling with my Microsoft Wireless Display Adapter no longer being detected in Windows 8. It didn't matter which machine I used - my Surface or my Laptop. I came across an article that suggested I remove VirtualBox, and voila - ""Connect to a wireless display"" came back. I want to keep using VirtualBox, but I also need WiDi for teaching. Hey Oracle, would you fix this, or suggest a setting I can disable so I can have my wireless display while using your software, please?
"	Auri A. Rahimzadeh
18565	Windows 8.1 host, Linux Mint 19 Cinnamon guest, seamless mode: no menu bar, no host key	VirtualBox 6.0.6	2019-04-16T23:09:09Z	2019-04-17T09:36:27Z	2019-04-17T09:36:27Z	"On the lastest release of Virtual Box (6.0.6), and the one before that, I see the VirtualBox menu bar when booting Mint on my Windows 8.1 machine but, once Mint Cinnamon has finished booting, the menu bar disappears, seemingly never to return. Nor do the host keys (e.g. <host>+a) do anything. Thus, since I have the VM set to run in seamless mode, the only way to move outside the VM is to shut it down.

The version of Mint Cinnamon that I am booting is fairy vanilla: I have not customised it much or installed much software on it. It is running a 4.15 Linux kernel.

I do not seem to have the latest Guest Additions installed. I did, via Windows, download them and run them, but then my guest tells me they are not installed - and, it's the case that, because of the aforementioned problems, I cannot install them from within the guest."	JN
18542	Windows 8.1 Pro host freezes and reboots	VirtualBox 6.0.4	2019-04-03T20:11:51Z	2019-04-03T20:49:53Z	2019-04-03T20:49:53Z	The Windows 8.1 Pro host freezes and reboots at random times with the Windows Server 2003 guest I had. I'm not sure whether this is related to VirtualBox or not. I have OpenShell/ClassicShell installed on the host computer and I don't know whether that's relevant. I without thinking deleted the virtual machine. I'll be creating a new virtual machine with the same setup and uploading the logs.	Eddy Smith
14523	Windows 98 boot Crashes straight to Guru debugging.	VirtualBox 5.0.2	2015-08-30T21:59:15Z	2015-09-05T19:33:17Z	2015-09-05T19:33:17Z	When i load up windows 98 and attempts to load the GUI/System, It crashes stright to Guru debugging. I have the log attached. For the screenshot? Just black. Not the worth if its black. Can you please find out whats going on?	HSF3232
17339	Windows 98 can't be installed on windows xp, but can on windows 10	VirtualBox 5.2.0	2017-12-02T16:27:34Z	2017-12-02T22:42:05Z	2017-12-02T22:42:05Z	"When I put windows 98 se iso which is itself bootable, immediately, even before anything is read from it, app in my host windows xp os says ""VirtualBox.exe . Application Error"", ""The instruction at ""0x77c47631"" referenced memory at ""0x000c000c"". The memory could not be ""written"".""
Click on OK to terminate the program...

This is an all versions. Tested on xp pro sp3 with or without windows updates and addons like net framework, dx, vc redists...
I was never since i was born able to install windows 98 while using windows xp.

Windows XP cd boots when used in for win98 settings."	nijazxp
21063	Windows 98 not running on windows 11	VirtualBox 6.1.36	2022-08-14T21:52:02Z	2022-08-14T21:52:02Z	2022-08-14T21:52:02Z	Getting error messages when running windows 98 on windows 11 works fine on windows 10	EJ
17654	Windows 98 VM won't boot	VirtualBox 5.2.8	2018-03-30T22:01:22Z	2018-04-19T20:37:39Z	2018-04-19T20:37:39Z	"Every time that I try to install Windows 98 on a VM, the VM would not boot at all, showing two different errors: [https://imgur.com/3m4qkX5] [https://imgur.com/xQWl2HV]

The only two OSs that I know of that do this when I try to install them are Windows 98 and Windows ME, any help?"	GenericUsername
19409	Windows 98: Arbitrary corruption of files in guest OS	VirtualBox 5.2.38	2020-03-16T23:48:11Z	2020-03-17T00:01:31Z	2020-03-17T00:01:31Z	"1. Create a VM for Win98 and install Windows 98SE there.
2. Inside this VM, install Total Commander 9.51rc3 (the exact version is important!).
3. Make a backup copy of the TC installation folder.
4. Start TC, then exit it (if you're lucky enough that it does not crash).
5. Compare the TOTALCMD.EXE file contents with the one from the backup copy (for example, you can have another version of TC installed into another directory; there is a built-in function for comparing files).

Result: The file contents is different from what it was initially.

Expected result: The file should not change, because Total Commander does not modify its own executable. This was confirmed by the author of TotalCmd, but just in case I also monitored the situation with Sysinternals FileMon. During the whole period from launching Total Commander to its exit, FileMon showed absolutely NONE write operations to the totalcmd.exe file by any process in the system. And still, the file ended up being modified.

The corruption always happens on cluster-level; that is, the changes always consist of one or more cluster-sized chunks (4096 bytes on my guest file system). The exact position and contents of the corrupted data may vary in different experiments.

The issue can be reproduced in VirtualBox 5.2.36 and 5.2.38. With 5.2.34 I could not reproduce it. For some reason, I could reproduce this issue only with that particular version of Total Commander; neither rc2 nor rc4 seem to trigger the corruption scenario. If the version 9.51rc3 is no longer available at the official web site at some later time, it can still be downloaded from here: http://totalcmd.net/beta/tc951x32_rc3.exe (the authenticity can be validated by the digital signature).

I understand that Win98 is completely outdated, but it's a really serious bug causing data loss! And since I don't know what causes it, I cannot be sure if it does not affect any other guest OS.

I've looked at the log files, but they contain nothing at all at the moment of the experiment. Just in case, I'll attach the log file, but you can see it's empty between 13.5 seconds (when the OS started) and 26-something minutes, when I shut down the guest OS after performing the experiments."	Konstantin Vlasov
17690	Windows 98SE will not install	VirtualBox 5.2.8	2018-04-17T03:15:20Z	2018-04-26T09:19:52Z	2018-04-26T09:19:52Z	"Hi, Windows 98SE won't install on my system.

Here's the sitation.

I have two Win 98SE installation packages.  One is a bootable CD, the other a non-bootable one.

With the bootable installation CD, the error appears immediately.  With the non-booable one (where setup is started with MS-DOS), the machine goes a fair way through the process..installing the system on the hard drive. The error appear when the system reboots to load WIN98 from the hard drive to complete the installation .

The error is the same in both cases. It says ""

VirtualBox.exe - Application Error

The instruction at 0x77839A95 referenced memory at 0x000C000C.  The memory could not be written.""

Installation cannot proceed from this point.

I'm using Virtual Box Version 5.2.8 r121009 (Qt5.6.2)

The machine I am using is a 32-bit Intel(R) Core TM i5 CPU running Windows 10.  

In the virtual machine, the acceleration tab in the System property is greyout out (I've checked CMOS and it looks as if the motherboard doesn't support hardware virtualisation). All extended features (PAE/NX, I/O APIC) are switched off.  RAM is set for 64MB.

Other OS's (MS-DOS, Windows 95, Windows 2000, Xp and 7) install just fine.

The Log attached is that produced from the bootable CD."	tezza
20156	Windows BSOD	VirtualBox 6.1.18	2021-01-27T09:05:24Z	2021-01-27T09:21:00Z	2021-01-27T09:21:00Z	"Host: Windows 10 v1909, Hyper-V enabled, Intel i7-4790 [[BR]]

Guest Windows 10 v20H2 (newly install), 1 vCPU, 4 GB RAM, Nested Paging disabled[[BR]]

Symptoms: Random BSOD on guest OS, with something like following in Vbox.log


{{{
00:01:06.583527 GIM: HyperV: Guest indicates a fatal condition! P0=0xa P1=0x1 P2=0x2 P3=0x0 P4=0xfffff8002069dfa3
00:01:06.583631 GIMHv: BugCheck a {1, 2, 0, fffff8002069dfa3}
00:01:06.583632 IRQL_NOT_LESS_OR_EQUAL
00:01:06.583633 P1: 0000000000000001 - memory referenced
00:01:06.583633 P2: 0000000000000002 - IRQL
00:01:06.583634 P3: 0000000000000000 - bitfield
00:01:06.583634     b0: 0 - read operation
00:01:06.583634     b3: 0 - execute operation
00:01:06.583634 P4: fffff8002069dfa3 - EIP/RIP
00:01:10.260332 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
00:01:10.933294 AHCI#0: Reset the HBA
}}}

"	ACH
20638	Windows does not start	VirtualBox 6.1.28	2021-10-26T13:56:37Z	2021-10-26T13:56:37Z	2021-10-26T13:56:37Z	"I have a bug that i cant solve because mi pc does not start virtualbox this is the log File:

00:00:00.002638 main     VirtualBox COM Service 6.1.28 r147628 win.amd64 (Oct 18 2021 18:49:03) release log
00:00:00.002641 main     Log opened 2021-10-26T11:33:41.760766100Z
00:00:00.002641 main     Build Type: release
00:00:00.002643 main     OS Product: Windows 11
00:00:00.002644 main     OS Release: 10.0.22000
00:00:00.002645 main     OS Service Pack: 
00:00:00.014185 main     DMI Product Name: MS-7C37
00:00:00.020329 main     DMI Product Version: 1.0
00:00:00.020333 main     Firmware type: UEFI
00:00:00.020525 main     Secure Boot: Disabled
00:00:00.020530 main     Host RAM: 16305MB (15.9GB) total, 11461MB (11.1GB) available
00:00:00.020534 main     Executable: C:\Program Files\Oracle\VirtualBox\VBoxSDS.exe
00:00:00.020534 main     Process ID: 16736
00:00:00.020535 main     Package type: WINDOWS_64BITS_GENERIC
00:00:00.021118 main     WinMain: VBoxSDS: InitializeSecurity: 0
00:00:00.024852          registerVBoxSVC: aVBoxSVC=0000000000c75818 aPid=16848 (0x41d0)
00:00:00.025051          i_lookupOrCreatePerUserData: Created new entry for S-1-5-21-4179917506-290648088-1681930059-1001 (RubenAguado/Ruben Aguado)
00:00:00.025058          registerVBoxSVC: Making aPid=16848 (0x41d0) the chosen one for user S-1-5-21-4179917506-290648088-1681930059-1001 (RubenAguado/Ruben Aguado)!
00:03:09.773444          registerVBoxSVC: aVBoxSVC=0000000000c753b8 aPid=5360 (0x14f0)
00:03:09.773960          registerVBoxSVC: Seems VBoxSVC instance died.  Dropping it and letting caller take over. (hrc=RPC_S_SERVER_UNAVAILABLE 0x800706BA)
00:03:09.774327          i_unchooseTheOne: Irregular release ... (pid=16848 (0x41d0) user=RubenAguado/Ruben Aguado sid=S-1-5-21-4179917506-290648088-1681930059-1001)
00:03:09.774368          i_unchooseTheOne: ... done.
00:03:09.774372          registerVBoxSVC: Making aPid=5360 (0x14f0) the chosen one for user S-1-5-21-4179917506-290648088-1681930059-1001 (RubenAguado/Ruben Aguado)!
"	RubenAguado
18158	Windows does not start when the virtual machine is allocated 9 or more processors	VirtualBox 5.2.22	2018-11-29T10:33:26Z	2018-11-30T02:29:22Z	2018-11-30T02:29:22Z	"I use 

* AMD Ryzen Threadripper 1950X 16-Core Processor ← it have 32 thread
* NVMe SSD

{{{
% lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda           8:0    0   2.7T  0 disk 
├─sda1        8:1    0   199M  0 part /boot
├─sda2        8:2    0     2T  0 part 
│ └─bcache0 253:0    0     2T  0 disk /
└─sda3        8:3    0    20G  0 part [SWAP]
sdb           8:16   0 465.8G  0 disk 
└─sdb1        8:17   0 465.8G  0 part 
sr0          11:0    1  1024M  0 rom  
nvme0n1     259:0    0 953.9G  0 disk 
├─nvme0n1p1 259:1    0   499M  0 part 
├─nvme0n1p2 259:2    0   100M  0 part /boot/efi
├─nvme0n1p3 259:3    0    16M  0 part 
├─nvme0n1p4 259:4    0   683G  0 part 
└─nvme0n1p5 259:5    0 270.3G  0 part 
  └─bcache0 253:0    0     2T  0 disk /
}}}

I install Windows to nvme0n1p4.
And I usually boot Linux natively.

The problem occurred when I tried booting a different partition of Windows from Linux.

In that case I will execute the following command to make the disk of the virtual machine.


{{{
VBoxManage internalcommands createrawvmdk -filename ""nvme0n1.vmdk"" -rawdisk /dev/nvme0n1
}}}

When you enable EFI of the virtual machine, it normally starts up.

However, because it did not move this time,
I explored the cause,
We discovered that if you allocate more than 9 processors to the virtual machine it will not start.
Even at the processor bar, 16 is assigned to the safe zone,
I did not notice that this was dangerous.
I think that it is a natural act that a user of a CPU with 32 threads trying to allocate half 16 threads.

[[Image(https://www.ncaq.net/asset/screenshot-2018-11-29-19-00-26.png)]]

If it is difficult to deal with systematically,
In the meantime, I thought that it would be better to warn with 8 or more processors in the red zone.
"	ncaq
17643	Windows dosn't start 7 or 10	VirtualBox 5.2.6	2018-03-27T19:36:46Z	2018-04-19T18:39:56Z	2018-04-19T18:39:56Z	"Failed to open a session for the virtual machine Win8 007.

VT-x is not available (VERR_VMX_NO_VMX).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

"	KHS
16770	Windows failure to boot after VirtualBox hangs up	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
16079	Windows guest freezes when partitioning/formatting NVMe drive	VirtualBox 5.1.8	2016-10-19T12:59:54Z	2017-01-12T18:05:47Z	2017-01-12T18:05:47Z	Windows 10 1607 guest freezes when trying to partition/format a blank NVMe drive. This happens if the VM has only n=1 processor. If the VM has n=4 processors, then the guest does not freeze. Other values for n have not been tried.	Sven
20888	Windows guest hangs completely (possible cause: Split lock detected)	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
21504	windows guest on linux host unresponsive with high cpu	VirtualBox-7.0.6	2023-02-15T07:41:22Z	2023-02-15T13:30:24Z	2023-02-15T13:30:24Z	"I had upgraded to Virtualbox 7 and installed a new Windows Image. After installing Guest editions and reboot i opened Edge with the result that guest cpu was at 98%.
In host linux top shows 400% (4 CPU assigned).
The second running VM with Windows and Guestadditions not upgraded (6.1.42) was not affected until now.

After restarting the VM and waiting some Minutes after login to windows Edge starts without problem.

I attache Logs after Stop of VM."	Herwig Wiesinger
19613	Windows Guest on Windows 7+ loses focus during mouse capture.	VirtualBox 6.1.8	2020-05-22T15:09:04Z	2020-05-22T15:09:04Z	2020-05-22T15:09:04Z	"Mouse capture on Windows Guest (actually Android x86 also has issues):

If the start menu is hidden and is brought up during mouse movement, causes mouse capture to break free of the window, using the mouse after that causes odd behavior (wrong mouse click, etc).

High mouse acceleration also causes mouse capture to break free.

P/S2 Mouse, USB Tablet, USB Multi-Touch Tablet produce the same results.

To test:  Use the Windows 98 SE from Archives.org, mouse will refuse to stay in window after the start menu appears after hidden and will continue to become unusable after the initial break free."	BBISOFT
20668	Windows guest startup text mode scrambled, unreadable for all Windows guests	VirtualBox 6.1.28	2021-11-14T15:57:20Z	2021-11-14T15:57:20Z	2021-11-14T15:57:20Z	"During startup Windows guests used to show text information between the graphical screens before the login pops up. This was working well up to version 5. When version 6 came along there were a lot of problems, which were gradually fixed, but this one has never been addressed and I assume this has not been even filed here.

The reason for the textual stage is if there is something, which has been scheduled to run and the user will have to see the status of this. Typical example is when a disk check is run or startup optimizations are performed.

When this information is scrambled/garbled/unreadable and this particular screen takes a long time (see attached screen) users are lost and don't know if something is happening and they need to wait or simply reset the guest OS or what..."	wellitisspeedy
18181	Windows guest, Linux host: copying directories from host to guest copies top-level directories only, not contents	VirtualBox 5.2.22	2018-12-13T17:36:44Z	2018-12-13T18:25:21Z	2018-12-13T18:25:21Z	"Virtual Box test build 5.2.23
Host: Windows 8.1 x64
Guest: Linux Mint 19.1 x64 beta, Cinnamon.

Guest Additions installed. Bidirectional clipboard enabled.

Copying directory D1, with contents directory D2 and file F1, copies only D1.

The same setup, but with a Linux Mint 19.0 host, does not seem to have the problem."	JN
18784	Windows guests hang exactly once after each host reboot	VirtualBox 5.2.32	2019-07-23T21:53:30Z	2019-12-17T01:21:03Z	2019-12-17T01:21:03Z	"At some point during the 5.2.x series (I don't remember exactly which version), I started consistently experiencing the following problem with VirtualBox on my (64-bit) Windows 10 host.  It occurs only with my Windows (10) guests, not with my (Manjaro) Linux guest.

Whenever I reboot the host, after restarting VirtualBox and my VMs, each Windows guest (but not the Linux one) will freeze exactly once, very soon after its first startup.  When it freezes, if I try to close the window, which causes the ""power off / send reset / etc."" dialog box to come up, then whatever I choose, nothing happens; instead, that dialog box also freezes.  If I choose ""power off"", for example, the guest window does not close.  Then I click the 'x' to close either the dialog box or the host window, and it simply disappears (leaving the guest in the aborted state).

After I restart the guest, it remains up for a very long time.  It never freezes again on the second or ensuing startups, until after I reboot the host again.

This has been happening on all 5.2.x versions since the first one on which it happened (alas I don't remember which one that was).  I'm unable to use 6.0.x because of ticket #14366, so I'm not sure whether the bug also exists there or not.  I think I have had at least one VM freeze on 6.0.10 while checking to see whether ticket #14366 still existed there (it does), so perhaps this bug does still exist on 6.0.x, but I didn't run long enough (because of ticket #14366) to confirm that it was the same behavior (i.e. successful long-term operation on the second and ensuing guest reboots, with the problem recurring only after the next host reboot)."	rokopt
16180	windows host crashes when memory is full	VirtualBox 5.1.8	2016-11-11T14:08:48Z	2016-11-11T15:03:37Z	2016-11-11T15:03:37Z	"I have recently started to get windows BSODs when the guest VMs are trying to allocate too much memory.

I am running Win 8.1 64bit on a laptop with 16GB of RAM, and have 2 VMs open at the same time with 8GB of memory set to each, so there is obviously some over-provisioning going one.
This works fine until some heavy-duty operation starts in one of the VMs. What happens then is:
- windows slows down to a crawl - I can see screen and cursor refreshes
- I can briefly see the 'vm has been suspended because of lack of memory' dialog box popping up
- the win BSOD kicks in

This did not happen until recently (version 5.1.8) at the moment, but it might be simply due to the fact that I was not using intensively 2 VMs with memory over-provisioning before.

The windows event log says:

L’ordinateur a redémarré après une vérification d’erreur. La vérification d’erreur était : 0x0000007e (0xffffffffc0000005, 0xfffff8015d657f50, 0xffffd0005c195d78, 0xffffd0005c195580)

The guest OS is dDebian 8.6

Note that the VM additions inside the VMs might not correspond exactly to the version of VBox running."	gggeek
15864	Windows Host not start with virtualbox 5.1.4	VirtualBox 5.1.4	2016-08-30T07:20:21Z	2016-09-01T12:10:44Z	2016-09-01T12:10:44Z	Hi, I have updated to version 5.1.4-110228 but the windows xp host crashes on startup. I attach the logs. The pc has windows 10 pro	Sergio
18185	"Windows host removes HardDisks section if the version attribute is ""1.15-macosx"""	VirtualBox 5.2.22	2018-12-15T11:32:36Z	2018-12-15T17:30:39Z	2018-12-15T17:30:39Z	"I have a Windows guest that I open in both Mac and Windows hosts. The Mac is the laptop that I use when I'm working remotely, and the Windows is my home office computer.

Usually, there isn't a problem with that, as long as I do a full shutdown of the guest before switching.

However, it seems that the Windows host will sometimes delete the MediaRegistry/HardDisks section in the .vbox file on opening if it has a version of ""1.15-macosx"". The same file is untouched if it has a version of ""1.15-windows"".

All of the changes that it does:
 - Removes MediaRegistry/HardDisks section
 - Sets Memory RAMSize from 8192 to 128
 - Removes Hardware/Display
 - Removes Hardware/VideoCapture
 - Removes Hardware/BIOS
 - Removes child elements and all attributes except type=""Am79C973"" from Network/Adapter slot=""0""
 - Removes Hardware/Clipboard
 - Removes Hardware/DragAndDrop
 - Removes StorageControllers"	Shonn
14780	Windows host, multiple monitors, 1 virtual screen, fullscreen not working correctly	VirtualBox 5.0.8	2015-11-03T15:29:01Z	2015-11-03T15:29:01Z	2015-11-03T15:29:01Z	"My setup is roughly this:
- Windows 7 as host.
- 3 real monitors: 1680x1050, 1920x1200 (main), 1280x1024, in that order from left to right.
- VirtualBox version 5.0.8, same effect with 4.3.30 and 5.0.6.

I have several clients installed, Linux Mint, Ubuntu, Windows 7, Windows 8, Windows 10, and I have this problem under all of them. The clients are all configured to have one display. As long as the client is windowed (both floating and maximized) everything works fine. 

When i switch to fullscreen (Host-F), the client gets the wrong display resolution. What i would expect to see is it beeing maximized on my main monitor (the same where the client window is at that time) and have its resolution (1920x1200) (*1). But what happens is that the resolution is set to 4880x1200 in Windows (1680+1920+1280) and 784x1200 in Linux (seems to be 4880 mod 4096) (*2). The vertical pixel count seems to be ok with 1200 (it takes either the maximum of the pixels of the current displays, or it's the height of the main display). To be more exact, the clients left margin is where my left margin is on the main screen, the screen extends to the right, some of it beeing on the right monitor, some of it invisible, but it looks like it exists. I can't move the mouse there, but that might be because the host blocks mouse movement. When i maximize progams inside the client, they seem to behave as if there is just one screen with the resolution of 4880x1200 (*3)

One other issue (no problem for me, but it might be for others), is that when the window of the client is on another of my monitors (either in a window or maximized), the fullscreen always goes so the exact same place, that is, it starts on my main monitor and extends to the right from there. I would expect that i could run a client in fullscreen on one of my side monitors somehow, like if the window is on that screen at the time i press Host-F. There might be another way to do this, but i haven't looked into this much, since it's pointless without fixing the first problem.

There might be some configuration option i overlooked, but i doubt it. My guess is, the virtual box host retrieves the wrong pixel count for the display to send to the client when going fullscreen. It should only take the pixels of the one monitor where it is going fullscreen, but instead takes the total pixels of the display area.

To clear up a few things:
- I have installed client additions on all clients, version matching the host.
- I tested it with only one monitor connected, everything works fine and as expected in this case.
- I have not tested other hosts for this effect. I can only guess that the Windows version on the host (7, 8.1 or 10) does not affect this problem, but it might be that a Linux host does not have this.
- I googled about this issue, and i checked the already existing bug reports, i didn't find anything describing this exact problem.
- ""Host-F"" is the keyboard shortcut for fullscreen, in my case right-ctrl-F. I use this terminology since it's called like that in the documentation as well. The described effect is the same when i use the menu entry for fullscreen. I have not tried remapping the host key, but i can't imagine this changing anything about the issue.
- I have not tried to swap the order of monitors around (especially having a monitor with less height as main monitor), but i had a similar effect with only 2 monitors. I doubt trying different monitor configurations will give any more insight to this problem, and if so, it has to be done by a developer/tester who is more familiar with virtualbox in that area.

Notes:
- (*1) I check what the client ""sees"" as its resolution with something like rightclick and ""screen resolution"" in Windows, and xdpyinfo in Linux
- (*2) I tested this in Linux before, when i had only 2 monitors connected (1680+1920) and then the resolution in Linux was 3600.
- (*3) It's hard to explain why it looks like this, it would be much easier for someone else to just try it. For example, when i maximize firefox, the middle of the windows is about 2440 pixels (half of 4880) away from the left margin (of my main monitor), which appears towards the right on my left monitor. It implies the total screen area goes beyond the right edge of that monitor."	waldemar
17719	"Windows installer for 5.2.10 fails with dozens of ""Could not write value to key"" registry errors"	VirtualBox 5.2.10	2018-04-30T03:50:26Z	2018-04-30T07:04:35Z	2018-04-30T07:04:35Z	"Windows installer for 5.2.10 fails with dozens of ""Could not write value to key"" registry errors.

Representative screen shots attached.

"	Kriston
17340	Windows PosReady 2009 doesn't work	VirtualBox 5.2.0	2017-12-02T16:40:26Z	2017-12-02T22:49:27Z	2017-12-02T22:49:27Z	"I do not even know did i install it, but i think there were various errors even during isntall, hell I forgot...
Anyway now when I start os it's giving bsod in guest os DRIVER UNLOADED WITHOUT CANCELLING PENDING OPERATIONS. And at the same time my host os windows xp pro sp3 says The instruction at ""0x121d39d4"" referenced memory at ""0x00000008"". The memory could not be ""read"".

So let's conclude: Posready 2009 is not supported by virtualbox???
Regardless is it install or running of that os or somewhere in between or both.

Posready 2009 is downloaded as preview directly from microsoft.com and size is less than GB, or few hundreds MB.
https://www.microsoft.com/en-us/download/details.aspx?id=11196"	nijazxp
14313	Windows resizes to the smallest size	VirtualBox 5.0.0	2015-07-21T18:42:40Z	2015-07-21T18:42:40Z	2015-07-21T18:42:40Z	"Virtual machine starts in the tiny winndow (smallest possible size). With guest additions installed and without them.

If the auto adjust option is on and trying to resize with the mouse the window is blinking and right after the mouse buttom is up the window resizes to the smallest size again.

But with fully expanded window and in the full screen everything works correct.

As I suppose VirtualBox fails o detect curent guest screen size and sets the smallest windows size every time exept full screen and expanded cases.

Tested with:[[BR]]
VirtualBox 5.0 (4.3.38, 4.3.30) tested with (and without) guest addition of corresponding versions[[BR]] 
Host Windows 7 (latest updates) fresh install [[BR]]
Guest Windows 7 (latest updates)[[BR]]
Intel hd graphics 4600 drivers 10.18.14.4222[[BR]]"	Lester
20004	Windows Server 2012 R2 guest freezes after each resume and some reboots	VirtualBox 6.1.14	2020-10-27T19:54:38Z	2020-12-29T15:14:03Z	2020-12-29T15:14:03Z	I have a Windows Server 2012 R2 guest I have used for several months, within the last month I began experiencing intermittent freeze ups of the guest.  I would have to power it down and restart.  Sometimes it would be stable the rest of the day but freeze after resuming it the next day.  Now it is freezing after every resume and sometime after restart.  I've gone back a few snapshots but not change.  Checking for updates says I am on the latest version.  No 3D acceleration enabled.  Host is Windows 10 Pro fully patched.  Guest if fully patched.  Minidump and log attached.	David Shower
17684	Windows Server 2016 guest freezes after a few minutes	VirtualBox 5.2.8	2018-04-13T12:22:13Z	2018-04-13T12:22:13Z	2018-04-13T12:22:13Z	"VirtualBox Version:
5.2.8 r121009 (Qt5.6.2)

Host:
Microsoft Windows 10 Pro
64-bit
Version        : 10.0.16299
BuildNumber    : 16299

Guest:
Windows Server 2016 (64-bit)

Problem:
Guest freezes after a few minutes. Happens every time I restart the guest.

Host & guest up-to-date with updates.

Host has been rebooted and problem continues.

Log attached."	rafinnerty
20226	Windows VBox dev. build 6.1.19 142917 host won't start VMs but 6.1.19 142777 does	VirtualBox 6.1.18	2021-02-25T09:39:35Z	2021-04-26T11:55:39Z	2021-04-26T11:55:39Z	"Bug report:

Am running Windows 8.1 Pro x64 fully patched (build 9600.19941).
Symantec Endpoint Protection: Version: 14.0.3929.1200 (14.0.3929.1200.105 to be exact)

With developer build Virtual Box 6.1.19 142917, I receive the following (or similar) when trying to start any VM 
(XP 32 bit, but also same for a 64 bit Windows 10 guest and 32 bit Windows 7 guests)
The previous developer build: 6.1.19 142777 was fine.
The only change is the build of Virtual Box, and indeed reverting back from 142917 to 142777 fixes the problem.

Error messages:

Failed to open a session for the virtual machine XP.

The virtual machine 'XP' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\VBoxMachines\XP\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}

Note: The following bug report against 142917 also looks relevant:
https://forums.virtualbox.org/viewtopic.php?f=38&t=101896"	MikeDiack
14075	"Windows VM crashes Debian host, NMI for unknown reason points to ""vboxdrv"""	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
15098	Windows VM defaults are well below the required minimum values to run the OS	VirtualBox 5.0.14	2016-02-02T05:53:55Z	2016-02-02T11:55:04Z	2016-02-02T11:55:04Z	"Basically, If you're creating a Windows 7 VM, the default settings for the allotted RAM for the VM is 512 MB.

Windows 7 has a minimum '''required''' RAM for a 64-bit install of 2 GB. (see [here](http://windows.microsoft.com/en-us/windows7/products/system-requirements)).

It's probably about time to upgrade the VM defaults to at least the minimum required values to run the OS that VirtualBox already has logos and everything for, and has been available for 6 years now, don't you think?

If you're installing windows 8, it properly sets the default to 2 GB.

Additionally, the default HD size is *also* really, '''really''' tiny. W7x64 requires 20 GB, and with a default of 25 GB, that's basically zero headroom, and the OS alone puts you right at the 80% disk occupation point where you start getting a lot more fragmentation. Defaulting to a disk size of 100 GB would also probably be a lot more sensible."	Fake-Name
19861	Windows XP 32bit does not start	VirtualBox 6.1.10	2020-09-04T18:21:23Z	2020-09-04T18:21:23Z	2020-09-04T18:21:23Z	"The system (Win XP 32bit) was working well. After trying to create a shared directory, the system is not able to start. After the initial BIOS page, nothing is happening.

Could you please kindly help me? Log-file is attached."	zbynektul
9913	Windows XP Guest application causes hang of VirtualBox Guest & Windows 7 Host	VirtualBox 4.1.6	2011-11-17T08:32:28Z	2011-11-17T15:27:55Z	2011-11-17T15:27:55Z	"I am running Virtualbox 4.0.10 successfully with a Window 7 host and a Windows XP guest.

Any version of Virutalbox newer than the above suffers the following issue:

When starting an application on the guest called ""Cisco IP Communicator v7.0.5.4"" the guest hangs and does not respond and also the Virtualbox.exe process running on the host hits a constant 25% of CPU (which is one full CPU as I have a quad core system) and cannot be terminated via windows task manager, also of course Virtualbox GUI on the host also fails to respond - the only way to recover from this situation is to reboot the host.

I have tried things like trying a different networking adapter rather than PCnet FAST III, disabling the VTx, nested paging options, switching back to 1 CPU for the guest but it always causes this hang.

Attached are logs from a successful run of the guest on 4.0.10 obviously as it hangs I cannot attach from when a newer version suffers the hang.

I have held off logging a bug until now as I was hoping newer versions may resolve the issue but the fault is still present."	starfire
16361	Windows XP guest keeps crashing in recent releases	VirtualBox 5.1.12	2017-01-06T05:08:15Z	2018-03-22T02:34:05Z	2018-03-22T02:34:05Z	"I can't tell exactly when this started, but the XP guest was very stable in versions 4.3 and 5.0 (at least the early ones). The guest keeps crashing now at random intervals, so the regression could have been introduced with version 5.1. I didn't upgrade to version 5.1 from 5.0 right away as there were audio issues initially, and when the audio was ""fixed"" the 5.1.x version was already ""broken"" for that XP client. That XP client heavily uses network adapter, but I'm not sure if that's a contributing factor or not. The host is Windows 10 version 1607.

BTW, this is not related to this issue, but I want to mention this for clarity. Bug #16221 did not concern Linux client only. I had major issues with transmit pauses (between few seconds to few minutes) on Windows 10 host. So the bug affected Windows also and also host network interface. It seems to be fixed now, so I'm not going to open a new ticket unless I notice a troubling network interface behavior, but the comment that bug #16221 was concerning Linux only (wrong) client (wrong again) troubles me that there could be things not fixed correctly. Like I said, no issue with pausing after upgrading to 5.1.12.
"	Rafcio
14512	Windows XP guest OS does not start	VirtualBox 5.0.2	2015-08-27T20:15:18Z	2015-09-09T14:49:55Z	2015-09-09T14:49:55Z	"I'm using Ubuntu Trusty. Under VirtualBox 4.3.10_Ubuntu R93012, my other OSs (e.g. Debian, openSuse) startup OK. However, Windows XP (my only Windows OS) starts up OK but then displays a window with details of NS_ERROR_FAILURE (0x80004005).

Carried out install of VirtualBox 5.0.2 from LocutusOfBorg's ppa (https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/). Once I'd removed old Extension Pack & installed Extension Pack 5.0.2 from Oracle's site, Windows XPp & other guest OSs started OK.

It's OK on my desktop as detailed above. However, I've just tried the same updates on my laptop. It installs VirtualBox 5.0.2 & its Extension Pack OK. However, starting Windows XP gives a slightly different error:
Failed to open a session for the virtual machine WindowsXP.
Unsupported version 56 of data unit 'PATM' (instance #0, pass 0xffffffff) (VERR_SSM_UNSUPPORTED_DATA_UNIT_VERSION).
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

PS this is logged on Launchpad (for Ubuntu) as bug 1489279"	John Rose
18034	Windows XP Guest Random Aborting	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
16893	Windows XP guests hang/freeze during and after setup with choppy audio	VirtualBox 5.1.22	2017-07-09T21:14:26Z	2017-07-28T06:17:40Z	2017-07-28T06:17:40Z	"The Windows XP guest stops responding and hangs for while and then continues to work normally. After a little time it freezes/hangs again and the cycle continues. The mouse won't move whenever Windows XP freezes. This cycle starts of hangs start during the part of setup that occurs after entering the product key and while getting the dialog for network settings. Additionally, I get cycles of extremely choppy audio that almost sounds like a chainsaw during the ""welcome to microsoft windows"" screen. I haven't experienced any of this behavior with Windows Server 2003 guests so far which is weird given that the two OSes are similar."	Eddy Smith
19646	Windows XP Machine freeze	VirtualBox 6.1.10	2020-06-08T20:04:10Z	2020-09-22T16:35:58Z	2020-09-22T16:35:58Z	"My XP machine always freezes without any visible reason. I tried a few things but don't know what to do now....

Please can you help me?

Best regards
Herbert"	Herby_ITS
8855	"Windows XP netcard doesnt work with ""VirtualBox Bridged network driver"" enabled"	VirtualBox 4.0.6	2011-05-06T05:29:01Z	2011-05-10T02:24:05Z	2011-05-10T02:24:05Z	"after upgrade version 4.0.4 to 4.0.6 get troubles with networking of Host system (Windows XP SP2).
after booting up a systyem local (physical) netcard properties fields ""IP"", ""netmask"" & ""gateway"" showed empty strings, inspite of ""tcp/ip properties"" are configured as ""manual"". changing properties of netcard didnt help (changes even didnt ""appended"" successfully). only turning ""VirtualBox Bridged network driver"" to ""disabled"" state allowed successful conection to local network (& internet).

"	GG
17009	Windows XP SP3 VM application error on VirtualBox 5.1.26 on Windows hosts	VirtualBox 5.1.26	2017-08-13T04:48:38Z	2017-11-22T02:42:41Z	2017-11-22T02:42:41Z	"Windows XP SP3 VM consistently causes application error within 10 minutes from startup on VirtualBox 5.1.26. This error happened on three different Windows host PCs.  Error occurs with VirtualBox 5.1.26 running on Windows 10 64 bit host or on Windows 7 64 bit host.  The error message from a Windows 10 host PC is ""The instruction at 0x00007FFADAF76D43 referenced memory at 0x0000000000000018. The memory count not be read."" (see attached image). Windows 7 host may of had a different instruction address but it still had the ""referenced memory at 0x00000018"" text.  No special action was performed to cause the error. I downgraded to 5.1.24 on a Windows 10 host and the XP VM ran very stable with the error happening only once after days of use. I only tested on Windows hosts and not on Linux hosts."	Nick1
17591	windows10 host failed to open a session for virtual machine	VirtualBox 5.2.8	2018-03-06T06:50:10Z	2018-03-08T07:35:24Z	2018-03-08T07:35:24Z	"host:
OS name:          Microsoft Windows 10 enterprise
OS edtion:          10.0.16299  
manufactor:       Dell Inc. OptiPlex 790    x64-based PC

BIOS edtion:        Dell Inc. A18, 2013-9-24


The virtual machine 'win10'
 has terminated unexpectedly
 during startup with exit code -1073741819


Result Code: 
E_FAIL (0x80004005)
Component: 
MachineWrap
Interface: 
IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}
"	eiddy
18253	Windows10 sleep, wake up, VirtualBox(V6.0.0) display: abnormal exit.	VirtualBox 6.0.0	2018-12-31T12:14:04Z	2019-01-07T05:10:39Z	2019-01-07T05:10:39Z	"Host Machine System: Windows10 1809
Virtual Machine System: CentOS7.0
Virtual machine running, and then wait 10 minutes not to use Windows system, then Win sleep... Then, wake up Windows, VirtualBox shows: abnormal exit."	solan
20229	Windows10 will not boot after upgrading to 6.1.18	VirtualBox 6.1.18	2021-02-28T14:10:07Z	2021-02-28T14:59:25Z	2021-02-28T14:59:25Z	I see a critical error as Windows is booting and the logs indicate a 'Gutu meditation'	simgr
19965	Windows7 virtual machine stops	VirtualBox 6.1.14	2020-10-14T07:12:21Z	2020-10-14T07:12:21Z	2020-10-14T07:12:21Z	I tried to start Beckhoff plc in run mode, it has been running earlier in this VM. But now in this version i onlny come to this stop mode of the VM.	GoranP
18473	Windows7 VM keeps crashing	VirtualBox 6.0.4	2019-03-05T05:54:26Z	2019-03-05T08:55:24Z	2019-03-05T08:55:24Z	"Good Day. Since I upgraded to V6.04 my Windows7(32bit) VMs keep crashing/freezing. It sometimes happens while I'm using one of my apps and almost all the time when I'm working in windows explorer. It is extremely frustrating and corrupts my projects, which means engineering time lost.

I though it is a problem on only one VM but I started working on another VM wit the same OS and it does exactly the same. At the moment it is unbearable and causes a lot of lost time."	Omega
19543	WinVerifyTrust failed to start virtualbox 5.x.x	VirtualBox 5.2.40	2020-04-29T20:10:30Z	2020-04-29T20:10:30Z	2020-04-29T20:10:30Z	"hi , i install last 6month ago about 20 virtualbox 5 series without problem in windows server 2003 and vista sp1 , server 2008 and already running
now i cant install 32bit virtualbox in this windows
i try all version 4,5 but not sloved
just runing in windows xp , 2008 r2 , 7 , 2012 , 2016 , 2019 , 10 without problem
how to slove problem in 2003 ?
my host virtualbox in hetzner cloud and cant install virtualbox 6.1 64bit series ,
please see image :
http://uupload.ir/files/92_353_(1).jpg

please help me for this problem , thanks"	soheil
19542	WinVerifyTrust failed to start virtualbox 5.x.x	VirtualBox 5.2.40	2020-04-29T20:08:10Z	2020-04-29T20:08:10Z	2020-04-29T20:08:10Z	"hi , i install last 6month ago about 20 virtualbox 5 series without problem in windows server 2003 and vista sp1 , server 2008 and already running
now i cant install 32bit virtualbox in this windows
i try all version 4,5 but not sloved
just runing in windows xp , 2008 r2 , 7 , 2012 , 2016 , 2019 , 10 without problem
how to slove problem in 2003 ?
my host virtualbox in hetzner cloud and cant install virtualbox 6.1 64bit series ,
please see image :
http://uupload.ir/files/92_353_(1).jpg

please help me for this problem , thanks"	soheil
20181	WinVerifyTrust for MMDevAPI.dll	VirtualBox 6.1.18	2021-02-10T16:39:32Z	2021-02-19T13:00:07Z	2021-02-19T13:00:07Z	"Microsoft updated this dll on 09/02/2021 and since then all virtualbox guests are falling over unexpectedly during startup with exit code 1 (0x1). the cause in the VBoxHardening.log file is MMDevAPI.dll lacks WinVerifyTrust.
Attached is the VBoxHardening.log for a newly created Fedora Linux host.
Version of Windows is Windows 10 Pro Ver 20H2 OS build 19042.804"	Tim_B
16758	winxp	VirtualBox 5.1.22	2017-05-15T10:17:11Z	2017-05-15T10:29:38Z	2017-05-15T10:29:38Z	Problem run VB	keriks
15694	WinXP guest BSOD after start from saved state in 5.1.2	VirtualBox 5.1.2	2016-07-26T14:26:04Z	2018-02-18T14:49:56Z	2018-02-18T14:49:56Z	After I update from 5.0.26 to 5.1.2 my WinXP guest is BSODing just after start from saved state.	tico-tico
17164	wireless mouse stopped working	VirtualBox 5.1.28	2017-10-13T13:57:06Z	2017-10-16T14:58:02Z	2017-10-16T14:58:02Z	I installed the new 5.1.28 version and it caused my wireless mouse to stop working in BOTH the HOST and the virtual computers.  I tested this with both a wired and wireless mouse and several virtual computers, rebooted several times.  Each time this was the cause of the interference.  This was not present in previous versions of virtualbox and I previously was using 5.0.46.	3_laws
21143	with 2 monitor with different display resolution the mouse does't works	VirtualBox 7.0.0	2022-10-13T10:12:39Z	2022-10-13T10:23:09Z	2022-10-13T10:23:09Z	Using the version 7 of Virtualbox, configured with two screens as per the attached images, configured to the maximum occupancy of the video, the mouse moves everywhere but the click is not located in the correct place on the X axis so it becomes impossible to select or open and close windows or interact with the system. The further you move away from the left side of the first screen, the more the error increases. Fortunately, you can select the windows menu and shut down the operating system. Conversely, if I use only one monitor, even on the ultrawide screen I have no problems.	JamesTKirk
12562	With dual monitor setup, VirtualBox Crashes when in seamless mode and try to a phsical monitor is removed. Win7-64 host, linux guest	VirtualBox 4.3.4	2014-01-02T07:17:44Z	2017-08-30T22:05:37Z	2017-08-30T22:05:37Z	"How to reproduct. 
On a windows 7 64bit host with two physical monitor. 
Setup a VM with two Vmonitors, boot up the VM and login, then ctrl+L to go into seamless mode, each Vmonitor will use one physical monitor.
Then disconnect one physcial monitor (by unplugging the cable), windows 7 will detect its gone.
Then try click on anywhere inside the VM Vmonitor, it will hang, then crash. 

However, if it is not in seamless mode when removing the physical monitor, it won't crash.

I don't think the graphic cards matters, I had this issue on a few different machines with nvidia/intel graphics.

This is especially anonying on laptops conntected to an external monitor. When I put the laptop to sleep, and go somewhere and wake up again without the external monitor, the VBox would crash. 

I'm programmer, so if there's any information needed, I'm glad to help."	zzxt
17364	With python3 find_machine always throws TypeError	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
14557	with windows 7 hosts in a windows domain virtualbox saves some info in roaming profile	VirtualBox 4.2.32	2015-09-08T15:50:40Z	2015-09-08T15:54:29Z	2015-09-08T15:54:29Z	with windows 7 hosts in a windows domain virtualbox saves some info in roaming profile which then break vms when logging into another pc on same domain	clive darra
20391	With Windows host,Bridged Adapter Oracle VirtualBox (6.1) doesn't work if the VM Opterating system is Ubuntu 16.04	VirtualBox 6.1.22	2021-06-09T22:57:39Z	2021-06-09T22:57:39Z	2021-06-09T22:57:39Z	"Here is an outline of the problem:

Parameters:
•	I’m using Windows 7
•	I’m using Oracle VirtualBox 6.1
•	I’m running Ubuntu 16.04 on Oracle VirtualBox VM’s

Outline of the Problem:

•	Can’t connect to the internet if I select “Bridged Adapter” in 
        the Networking Options of an Oracle VirtualBox VM.
•	Can connect to the Internet via the NAT Adapter.
•	When I try to communicate between Oracle VirtualBox VM’s via 
        the Bridged Adapter, I get the error message “Host not Found.
"	intelidrift
17094	Won't install on Ubuntu 16.04	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
20481	Working VM suddenly stop loading in GUI mode (F7) but working  in tty1 to tty6 mode	VirtualBox 6.1.24	2021-07-31T13:40:58Z	2021-08-02T12:33:23Z	2021-08-02T12:33:23Z	"Hi,
I ahve few(3) VMS based out of ubuntu 18.04(bionic) which were all functional from at least a year now. But yesterday, one of the 3 VM stops booting up in GUI mode(F7). It ends up ina blinking curson on the screen.
I can login into machine from tty1,ty2 to tty6 '''but not  getting anything on tty7 but a blinking cursor only'''.

Attaching vbox logs for someone to take a look urgently.

Note: I have checked some existing issues:
1. My host(windows 10) hypervisor is disabled.
2. I can  successfully run other 2 VMs
3. My VM has sufficient RAM/Space(from df and free output)
4. Virtualisation is enabled in BIOS settings.
5. Uptodate Vbox version and extension pack.
6. Done apt-get update  from tty1 and rebooted multiple times.
7. 3D acceleration is in disabled mode.

Please check my logs attached. "	vas
17757	writev() blocks over vboxsf on Linux 4.16 guest	VirtualBox 5.2.12	2018-05-11T09:08:29Z	2018-05-11T09:08:29Z	2018-05-11T09:08:29Z	"VirtualBox 5.2.8

{{{
# uname -r
4.16.8-1-ARCH
}}}

{{{
# cat test.c
#include <sys/stat.h>
#include <fcntl.h>
#include <unistd.h>
#include <sys/uio.h>

char data[8192];

int main() {
	struct iovec iov[2];
	int fd = open(""/media/sf_sf/test.txt"", O_WRONLY|O_CREAT|O_TRUNC|O_CLOEXEC, 0666);
	iov[0].iov_base = data;
	iov[0].iov_len = sizeof(data);
	iov[1].iov_base = data;
	iov[1].iov_len = sizeof(data);
	writev(fd, iov, 2);
	close(fd);
	return 0;
} 
}}}

Result:

{{{
# strace ./a.out
openat(AT_FDCWD, ""/media/sf_sf/test.txt"", O_WRONLY|O_CREAT|O_TRUNC, 0666) = 3
writev(3, [{iov_base=""\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0""..., iov_len=8192}, {iov_base=""\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0""..., iov_len=8192}], 2
}}}

This blocks forever. Writing with write() works. Only writev() blocks.

Kernel modules are from either virtualbox-guest-modules-arch or virtualbox-guest-dkms (Arch Linux).

Downgrading to 4.14.x kernel works around the problem with same version of VirtualBox & host.

Was unable to test with guest additions CD (doesn't compile on 4.16.8).
"	larsch2
21497	Wrong Bus Frequency and DRAM Frequency	VirtualBox-7.0.6	2023-02-12T19:48:51Z	2023-02-12T19:48:51Z	2023-02-12T19:48:51Z	Using CPU-Z 2.02 in a Win2K3 (or ReactOS 0.4.15) guest using VBox 7.0.6 on a Win11 host, incorrect Bus Frequency and DRAM Frequency is being reported	Kyle_Katarn
17131	Wrong core count on THREADRIPPER system	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
14699	"Wrong icon for ""Other Linux (64-bit)"""	VirtualBox 5.0.2	2015-10-14T18:54:55Z	2015-10-14T18:54:55Z	2015-10-14T18:54:55Z	"Choose[[BR]]
Type: '''Linux'''[[BR]]
Version: '''Other Linux (64-bit)'''[[BR]]


Icon the same as for '''Other Linux (32-bit)''' without 64 in left top corner."	bmx666
10098	Wrong manual entries for setting up VRDP authentication in the VBox end-user documentation	VirtualBox 3.2.14	2011-12-28T16:30:03Z	2011-12-28T16:31:41Z	2011-12-28T16:31:41Z	"Filenames appears to have been changed since this manual was written. One problem is that the procedure for configuring RDP Authentication varies with the version of VirtualBox.

As for VirtualBox 3.2.14 which was updated recently, if using the VBoxAuth'''Simple''' module, the password does not use a hash whereas 4.0 and later does use this. This is not addressed properly in the documentation.

The names of the external modules are wrong. The documentation refers to VBoxAuth and VBoxAuthSimple which don't exist in /opt/VirtualBox/amd64/ of the 3.2.14 installation. Their proper names are instead VRDPAuth and VRDPAuthSimple.  This means that the suggested commands in the manual are wrong:

VBoxManage setproperty vrdeauthlibrary ""VBoxAuthSimple""

VBoxManage setextradata <vm> ""VBoxAuthSimple/users/<user>"" <hash>

First of all there is no such thing as vrdeauthlibrary in 3.2.14, it should be named vrd'''p'''authlibrary and VBoxAuthSimple should be changed to VRDPAuthSimple. Also 3.2.14 does not use <hash> but has the passwords expressed explicitly as mentioned above. So a correct set up would instead be:

VBoxManage setextradata <vm> ""VRDPAuthSimple/users/<user>"" ""<password>""

Perhaps the documentation is proper for 4.x users but for users who opt to use 3.2.x (for stability or compatibility reasons) this documentation is very unhelpful for setting up VRDP authentication."	gu99roax
10986	Wrong mtime on shared folders	VirtualBox 4.2.0	2012-09-22T17:45:52Z	2012-09-24T12:07:45Z	2012-09-24T12:07:45Z	"Linux ""vboxsf"" shared folder system does not set correct modification time. It only happens then file is written with some data.
attachment contains repro code (gcc testts.c ; ./a.out)
"	ajax16384
15456	Wrong screen geometry reported to Linux guest for unscaled HiDPI	VirtualBox 5.0.20	2016-05-29T16:26:24Z	2016-05-29T16:26:24Z	2016-05-29T16:26:24Z	"I have a MacBook Pro 13"" retina with a resolution of 2560x1600 pixel and a physical screen size of around 286x177 mm.

When activation the ""unscaled HiDPI"" option, the full resolution of 2560x1600 px is reported to the Linux guest (debian jessie).

However, the physical screen size is reported as 677x423 mm, which gives the guest operation system no chance to correctly estimate the DPI resolution.

More over, the reported screen size is not reduced by MacOSX's Menu bar in seamless mode, so the bottom menus inside the linux guest are misplaced below the effective screen area.

I already use guest additions 5.0.21-r107220, because of the cursor displacement issue fixed in this snapshot version compared to the 5.0.20 release of the Linux Guest Additions."	Wolfgang Glas
18988	Wrong time synchronization	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
16650	WXP VM crashs at startup after upgrade VB to 5.1.18 (raw mode)	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
18640	xoBV tag memory leak	VirtualBox 6.0.6	2019-05-14T07:07:28Z	2020-04-22T20:54:53Z	2020-04-22T20:54:53Z	"Just to save some time, here is the link to virtualbox discussion about this:

https://forums.virtualbox.org/viewtopic.php?f=6&t=93104&p=448516

Let me know if I can help somehow to solve the problem!"	supsup
12646	XP Guest GPF in WIN87EM.DLL at 0001:02C9 or 0001:02C6 => Fixed in SVN	VirtualBox 4.3.4	2014-01-27T17:56:46Z	2020-07-11T19:27:22Z	2020-07-11T19:27:22Z	"When running 16 bit Apps in XP, there is an occasional GPF in WIN87EM.DLL at 0001:02C9 or 0001:02C6.  Same app sometimes works OK.
For me, this problem did not exist through many version of VB through 4.2.18 and started with 4.3.4.

The only web research I have was from a VMWare post that may or may not apply here (quoted from cwsault original post):

""There are a few applications which may fail with this error when executed in a VM. The problem is that the library tries to read the instruction bytes of the last FPU instruction executed based on the code segment and instruction pointer saved in the FPU environment. Unfortunately, the code segment saved in the FPU environment may be NULL.

When we switch between the virtual machine monitor and the host operating system, we use the primitive hardware instructions to save and restore the FPU state. These instructions were not really designed for an environment that mixes 32-bit and 64-bit execution. When the instructions are executed in 64-bit mode, they don't keep track of the code segment, since segments have little meaning in 64-bit mode. The virtual machine monitor, which saves and restores the FPU state for the guest VM, executes in 64-bit mode. Hence, the FPU code segment is lost.

Fortunately, there is a workaround for this issue. If you add the following option to your configuration file, we will make sure that the FPU code segment is properly saved and restored when switching between the virtual machine monitor and the host operating system (at some small performance penalty):
    
monitor_control.enable_rigorous_fpu_save_restore = TRUE""
"	SteveDeveloper
19428	XP VM unexpected error	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
14147	XPCOM init failure when using CAPI from go on OSX	VirtualBox 4.3.28	2015-05-25T02:12:37Z	2015-08-13T01:08:23Z	2015-08-13T01:08:23Z	"I'm writing a VirtualBox client in go that uses the XPCOM API. It seems like the XPCOM initialization code in pfnClientInitialize fails under go's runtime environment in OSX. The same code works fine in Linux (Fedora 22 x64).

Go is gaining popularity as a systems configuration tool, so I think you should take a look.

GitHub repository with full information on reproducing the bug:
https://github.com/pwnall/vbox_bug"	pwnall
19043	XWayland breaks mouse behavior on Linux/Wayland Hosts	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
13945	Yosemite 10.10.2 and Virtualbox 4.3.X Crash System	VirtualBox 4.3.24	2015-03-09T14:02:28Z	2015-06-12T02:25:39Z	2015-06-12T02:25:39Z	"After migration from 4.2.28 to any version of 4.3.X the Yosemite OS crash with memory fault error.
This event is just with this version and Guest Windows 7.
"	tekmanforce
17341	~30% keyboard strokes reach VM for vbox 5.2.2 only		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
20049	Испорченный образ Guest Addition Addon	VirtualBox 6.1.16	2020-11-18T21:11:55Z	2020-11-18T21:11:55Z	2020-11-18T21:11:55Z	Отсутствует компонент NTDLL.DLL:NtQueryObject в файле VBoxWindowsAdditions.exe	IBw
18698	Проблема с запуском Kali-Linux	VirtualBox 6.0.8	2019-06-07T19:54:33Z	2019-06-08T08:55:32Z	2019-06-08T08:55:32Z	"Не удалось открыть сессию для виртуальной машины Kali-Linux-2019.2-vbox-amd64.

The virtual machine 'Kali-Linux-2019.2-vbox-amd64' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\1\VirtualBox VMs\Kali-Linux-2019.2-vbox-amd64\Logs\VBoxHardening.log'.

Код ошибки: E_FAIL (0x80004005)
Компонент: MachineWrap
Интерфейс: IMachine {5047460a-265d-4538-b23e-ddba5fb84976}

Все чисти и удалял, и заново переустанавливал, но ничего не помогает "	Gramm23
