﻿ticket	summary	host	version	type	created	modified	_changetime	_description	_reporter
21497	Wrong Bus Frequency and DRAM Frequency	Windows	VirtualBox-7.0.6	defect	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
21495	A critical error has occurred while running the virtual machine	Windows	VirtualBox-7.0.6	defect	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
21475	TwinCAT conflict	Windows	VirtualBox-7.0.6	defect	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
21334	arcaos hard disks not recognized	Windows	VirtualBox-7.0.4	defect	2022-12-12T04:35:48Z	2023-01-31T17:31:12Z	2023-01-31T17:31:12Z	In Arcaos (OS/2) guests, hard disks are no longer recognized with Win ver 7.x.  The hard disks worked normally with ver 6.x.  The hard disks fail to be seen and partitioned. This defect is in BIOS or EFI installations.  This defect is seen with SATA, IDE, NVME type virtual storage.  The CD ROM is recognized and works normal in SATA. I had to revert back to 6.1.40.  Everything works in ver 6.x.	Rich87
21412	Virtualbox + Hyper-V + 1GB Paging doesn't seem to be supported?	Windows	VirtualBox-7.0.4	defect	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
21387	Windows 11 BSOD	Windows	VirtualBox 6.1.28	defect	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
21356	Guest addtions update issue in WIN 7	Windows	VirtualBox-7.0.4	defect	2022-12-29T10:06:27Z	2022-12-29T10:06:27Z	2022-12-29T10:06:27Z	"Name: C:\Program Files\Oracle\VirtualBox/VBoxGuestAdditions.iso

Could not open guest session: VERR_NOT_FOUND.
Result Code:
VBOX_E_IPRT_ERROR (0X80BB0005)
Component:
GuestWrap
Interface:
IGuest {00892186-a4af-4627-b21f-fc561ce4473c}
"	iRabbit_Jimmy
21352	"VM crash with ""Memory could not be read"" error when usb-c monitors are disconnected"	Windows	VirtualBox-7.0.4	defect	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
21348	VM with Linux crashes worse than DOS or Windows 95. Your dog can crash it	Windows	VirtualBox 6.1.40	defect	2022-12-19T16:05:33Z	2022-12-21T12:56:29Z	2022-12-21T12:56:29Z	"Just write elementary program which creates large files, say, 1GB in size or one large file larger than 32 GB. And when your program running created 32GB of data in files VM part with Linux 100% crashes. 

Or if you have already large files aaa1, aaa2... and you combine them into one large file bbb which will be larger than 32GB this will also crash VB with its Linux like it is a dumb DOS 2.1. Here is syntax how to do that.   

$ ssh aaa* > bbb

I can try to attach this few lines Fortran program which is creating multiple files 1GB but if this will fail (because i  do not see any links or buttons how attach the file) you also can take it from the Forum (Windows Host part) where i was just published it.

P.S.
I failed to attach the file. OK here is the text. Just compile it with gFortran or any other Fortran compiler and run telling it to create more than 32 files (each will be 1 GB size file). It will crash at file #31"	DanV
21343	Keeps losing linked disk	Windows	VirtualBox-7.0.4	defect	2022-12-16T11:16:33Z	2022-12-16T11:16:33Z	2022-12-16T11:16:33Z	"I had cause to delete a linked clone (not the files ..) to investigate something. Now, having re-added the clone (successfully ..), I'm having to keep adding the clone's disk snapshot to the list of hard disks (it appears under the parent as expected).

A restart of the application retains the added disk and the VM boots, but it seems that whenever I restart the host (I normally just sleep/resume), the snapshotted disk disappears from the list of registered disks and has to be added by hand again. The 'add' doesn't seem to be retained through a host restart - or at least I've only so far seen the phenomenon after restarts. Will add to the report if I see it on other occasions."	Granta
21330	Switching between Guided and Expert mode clears populated fields	Windows	VirtualBox-7.0.4	defect	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
21331	Delete of a VM does not delete unattended files, so can't recreate VM	Windows	VirtualBox-7.0.4	defect	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
21329	Help doc comes up behind new VM dialog and can't be accessed	Windows	VirtualBox-7.0.4	defect	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
21287	Unable to Show Windows Side by Side	Windows	VirtualBox-7.0.4	defect	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
19326	VirtualBox Manager 6.1.x causes BSOD when docking into HP Universal dock G2	Windows	VirtualBox 6.1.4	defect	2020-02-20T16:25:26Z	2022-11-09T21:56:24Z	2022-11-09T21:56:24Z	"Host Operating system is newly imaged Windows 10.

To reproduce:

* download and install VirtualBox 6.1.4 with all defaults
* start the VirtualBox Manager
* plug the HP Univeral G2 into the laptop

This will crash the Windows 10 host with a Blue Screen Of Death: ""PNP DETECTED FATAL ERROR"".

The problem happens only when docking.
Operations while undocked are fine.
Operations while docked are fine.
Undocking works fine.

There isn't any VM involved (therefore no VM log). This is only from having the VirtualBox Manager started.

This is specific to versions 6.1.x. I have checked with 6.1.0, 6.1.2 and 6.1.4. I have tried installing VirtualBox both docked and undocked. I have also installed as an Administrator. The BSOD happened in all cases.

The problem does not happen with 6.0.x. I am currently using 6.0.16 without any problems.

This has been verified on two different HP Zbook 15u G5 (i7-8650u - 32GB RAM) and one HP EliteBook 840 G5. I tried both with the factory BIOS and the latest available BIOS (Jan 17 2020). It has also been verified on two different universal docks G2 - again, both with the factory firmware and with the latest available firmware.

I am attaching one of the VBoxSVC log file right agter undocking and docking. The last 3 lines of the log files were produced while undocking. No additional logging was produced when docking.
"	come_raczy
21241	Almalinux 8.6 aborts (virt-what)	Windows	VirtualBox-7.0.2	defect	2022-11-06T07:57:59Z	2022-11-08T14:43:45Z	2022-11-08T14:43:45Z	"After installing AlmaLinux 8.6 (RHEL 64-bit), normal start fails.
When using systemd.unit=rescue.target, I can get to a shell and when executing virt-what, the VM is aborted. Works on VirtualBox 6.1.40."	mtheiss
21251	Deleting snapshot's still available to Clone	Windows	VirtualBox-7.0.2	defect	2022-11-07T18:58:21Z	2022-11-07T18:58:21Z	2022-11-07T18:58:21Z	"VirtualBox 7.0.2 on Windows 10 host.

1. Create snapshot that has plenty of changes from previous snapshot.
2. In VirtualBox Manager click on snapshot and Delete button. Problem appears Clone icon is still enable for currently deleting snapshot and if clicked Clone wizard appears.

It doesn't make sense to enable Clone for currently deleting snapshot. Probably clone would not even finish."	bobJ
21165	Turtle != Snail	Windows	VirtualBox 7.0.0	defect	2022-10-18T21:23:38Z	2022-10-18T21:23:38Z	2022-10-18T21:23:38Z	"One of the long awaited features of VirtualBox 7.0 only made it halfway into VirtualBox 7.0.0:

In the VBox.log file, it says: ""NEM: NEMR3Init: Snail execution mode is active!"". But the icon in the VM's window status bar still shows a green turtle. ;)"	fth0
21157	Virtual box 7.0 oversize interface with DPI setup in Host	Windows	VirtualBox 7.0.0	defect	2022-10-17T12:05:44Z	2022-10-17T12:05:44Z	2022-10-17T12:05:44Z	"The buttons and text is too large under 150% DPI setting in Windows 10 Host.

Interface image attached
[https://freeimage.host/i/tz2nMF]"	tester_2022
21118	USB isochronous transfers cause problems under OS/2 guest	Windows	VirtualBox 6.1.38	defect	2022-10-03T07:04:10Z	2022-10-03T07:15:20Z	2022-10-03T07:15:20Z	"Host: Windows 11, guest: OS/2

If I try to play sounds via a USB connected audio 1.0 or audio 2.0 sound device, the sound always is extremely choppy.
This directly relates to ticket #18947, but this time I selected ""USB"" as the component instead of ""Audio"" because this clearly is a USB issue with isochronous transfers.
If needed, I could provide tracing information from the guest USB audio driver or I could provide additional analysis if requested (thinking about the ""samples per microframe"" value that the USB audio 2.0 device reports back on its ""sync isochronous in"" endpoint)."	lerdmann
21117	Windows 11 host machine's touchscreen stops working while running a Linux guest VM.	Windows	VirtualBox 6.1.38	defect	2022-10-02T19:05:07Z	2022-10-02T19:05:07Z	2022-10-02T19:05:07Z	"I have a HP Windows 11 ""All-in-One"" PC with a touchscreen. When I attempt to run Home Assistant in VirtualBox, the host's touchscreen stops responding, requiring the use of a mouse instead. Is there a fix for this?"	WillD
21101	installation folder is not remembered when upgraded	Windows	VirtualBox 6.1.38	defect	2022-09-08T23:42:16Z	2022-09-08T23:42:16Z	2022-09-08T23:42:16Z	"the folder is not remembered when updated it falls bach to
the default on every time  tried several versions even the latest 6.1.38"	sphinxios
19427	windows 10 virtualbox 6.1.2 wierd cant copy / move webm files	Windows	VirtualBox 6.1.2	defect	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
21032	Crash on start up	Windows	VirtualBox 6.1.36	defect	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
21064	My virtual machine half screen blank	Windows	VirtualBox 6.1.36	defect	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
20879	Error creating a new Host Network Manager	Windows	VirtualBox 6.1.32	defect	2022-03-24T11:15:50Z	2022-08-06T09:35:15Z	2022-08-06T09:35:15Z	"When I try to create a new Host Network Manager I receive this error:

Assertion failed: [!aInterfaceName.isEmpty()] at 'F:\tinderbox\win-6.1\src\VBox\Main\src-server\HostNetworkInterfaceImpl.cpp' (76) in long __cdecl HostNetworkInterface::init(class com::Utf8Str,class com::Utf8Str,class com::Guid,enum __MIDL___MIDL_itf_VirtualBox_0000_0000_0046).
Please contact the product vendor!.

I am running a 6.1.3 version on a Windows 11 Microsoft Surface Laptop."	mestebanpt
21035	Upgrading from VirtualBox 6.1.34 to 6.1.36 on Windows results in incorrect drivers	Windows	VirtualBox 6.1.36	defect	2022-07-26T06:49:05Z	2022-07-26T06:49:05Z	2022-07-26T06:49:05Z	"Windows 11 Home. No previous installations of VirtualBox. Steps to reproduce:

Install 6.1.34. Install Extensions for 6.1.34. Create a VM (does not matter what it contains). Upgrade to 6.1.36. Install Extensions for 6.1.36.

Inspect \Windows\System32\drivers\vbox*.sys. You should see: VBoxNetAdp6.sys, VBoxNetLwf.sys and VBoxUSB.sys.

Uninstall VirtualBox. Reboot. Inspect \Windows\System32\drivers\vbox*.sys. You should see: VBoxNetAdp6.sys, VBoxNetLwf.sys and VBoxUSB.sys.

Manually remove VBoxNetAdp6.sys, VBoxNetLwf.sys and VBoxUSB.sys. Reboot.

Install 6.1.36. Install Extensions for 6.1.36 (confirm re-installation of extensions). Inspect \Windows\System32\drivers\vbox*.sys. You should see: VBoxNetAdp6.sys, VBoxNetLwf.sys, VBoxSup.sys and VBoxUSBMon.sys.

It would appear that (1) the upgrade code in the 6.1.36 installer does not correctly remove the older drivers, (2) the 6.1.36 uninstaller does not correctly remove the (older) drivers, and (3) the upgrade code in the 6.1.36 installer does not correctly install the new drivers."	weird_stuff_happens
21023	Trying to run bluestacks in  vbox - cant increase cpu cores inside my bluestacks	Windows	VirtualBox 6.1.14	task	2022-07-18T04:39:22Z	2022-07-18T04:39:22Z	2022-07-18T04:39:22Z	"'''vbox is running win 10 home
 vbox is hyper v enabled in settings 
 cpu is 6 and ram is 8000'''


'''I am unable to increase my CPU cores in msi app player''' ( a bluestacks emulator) using windows 10 both in host and inside my virtual box to run msi app player

when i enable hyper v settings from app and features settings in windows 10 i get an error your pc doesn't support hardware assisted virtualization.

Attachment screen shots of my vbox and msi app player)
[https://drive.google.com/drive/folders/1uyX9agIlk3C0wjAKJe3tmf3g4tqKZWZq?usp=sharing]"	adamya
21001	la instalacion viene rota	Windows	VirtualBox 6.1.32	defect	2022-06-21T18:56:31Z	2022-06-21T19:10:27Z	2022-06-21T19:10:27Z	lo intalo despues de mucho tiempo sin instalarlo (pq antes el año pasado lo tenia instalado) viene con error critico y no abria asi q  abri el setup para repararlo y me encuentro q no se puede reparar	xd64
20966	Ova/Ovf Signature Verification Issue	Windows	VirtualBox 6.1.34	defect	2022-06-03T14:10:11Z	2022-06-03T14:10:11Z	2022-06-03T14:10:11Z	"I sign my ovf file with my own code signing certificate. I am getting a certificate validation error while importing the resulting signed ovf file. I am getting this error even though I upload the SubCA and CA certificates of the signing certificate to the Windows Certificate Store.

I downloaded the source code of the 6.1.34 version of VirtualBox and debug it on my windows machine. And I found that the problem was because of the Name Constraints extension in the SubCA certificate of the certificate I signed.

While reading SubCA certificate from Windows Certificate Store on rtCrStoreAddCertsFromNative method, RTCrX509Certificate_DecodeAsn1 method gives an error in the relevant SubCA certificate. The error message reads: 0x00000000033ae4e8 ""CurCtx.Cert.TbsCertificate.T3.Extensions.papItems[#].ExtnValue.NameConstraings. It gives error 0x80 (expected 0x10/0x20)'

What kind of a problem is there in the SubCA certificate, can you help with this?"	MustafaBayrak
20854	Oracle VM not booting	Windows	VirtualBox 6.1.32	defect	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
20837	Unable to get Virtualbox to run	Windows	VirtualBox 6.1.32	defect	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
20799	Duplicate packages in the guest OS when bridging to the LACP adapter in Windows	Windows	VirtualBox 6.1.32	defect	2022-01-31T16:13:58Z	2022-01-31T17:17:23Z	2022-01-31T17:17:23Z	"In VirtualBox version 6.1.32, when using a bridge to the LACP adapter in Windows Server 2012 R2, duplicate packages appear in the guest OS.

Tested on Debian 11 using ping.



The host PC running Windows Server 2012 R2 is connected to the router via a Zyxel GS1900-8 switch using the LACP protocol via 2 Intel I350 NICs.
If you send a ping from any guest OS, for example, to a router, then several packets will be returned in response - 1 + 3 duplicates.
At the same time, there is an increase in the load on the CPU and RAM of both the guest OS and the host OS, respectively.





Previous versions of VirtualBox did not have this problem, including 6.1.30.

The versions of the expansion packs used were the corresponding versions of VirtualBox.



VMware Workstation had the same problem for a long time, and now it has reached VirtualBox. :(

I tested this effect earlier in VMware Workstation Pro 16 with Linux and Windows guest OS - the result is the same, there are duplicates."	Konstantin.P
20683	PNP DETECTED FATAL ERROR	Windows	VirtualBox 6.1.28	defect	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
20778	Game crashing when VirtualBox Host-Only Adapter is present and enabled	Windows	VirtualBox 6.1.32	defect	2022-01-19T19:05:56Z	2022-01-21T23:19:25Z	2022-01-21T23:19:25Z	"The game XIII from GoG crashes on startup when the VirtualBox Host-Only adapter is installed and enabled.  This is 100% reproducible on my system, and has been confirmed on another system.  The game is installed and running on the host, not VirtualBox.  VirtualBox doesn't have to be running for the crash to occur.

When the game starts, it apparently enumerates all of the active network adapters and attempts to check something on each one.  The response from the VirtualBox Host-Only Adapter results in the game crashing.

This was determined by launching the game in a debugger and stepping backward from the crash with time-travel debugging.  The code just before the crash was making network related calls.

I don't know if this is a defect in the game, or a defect in the adapter, just that disabling the adapter fixes the problem, and enabling it causes the issue to return."	g051051
20729	High definition audio: cannot control volume with standard pin widgets	Windows	VirtualBox 6.1.28	defect	2021-12-15T02:09:15Z	2021-12-15T02:09:15Z	2021-12-15T02:09:15Z	I was writing a driver for High definition audio controller, I found that standard HD audio pin widgets cannot control the volume/mute of Sigmatel codec for output. Even direct output widgets cannot control the volume/mute of output converter. To control the volume/mute we need to communicate with the stac codec directly through controller interface. This need fixes as the standard method described by intel, should work. 	Manas Kamal
18668	Problem with sharing serial port after upgrade from 5.2.28 to 6.0.X	Windows	VirtualBox 6.0.8	defect	2019-05-22T12:00:47Z	2021-12-05T20:33:25Z	2021-12-05T20:33:25Z	"When I try to use a shared COM port (host device) on a guest running DOS 6.22 (using a legacy software for PLCs), on VirtualBox 6.0.8 (and also 6.0.6) I get errors like:
Serial#0: Failed to change parameters to 2400,NONE,5,1 -> VERR_INVALID_PARAMETER
and the software cannot communicate.

Everything works fine if I use VirtualBox 5.2.28 instead, with the same virtual machine.

The full log is attached."	stagadet
20692	No signature was present in the subject	Windows	VirtualBox 6.1.30	defect	2021-11-26T02:00:10Z	2021-11-26T04:14:03Z	2021-11-26T04:14:03Z	"Cannot install VirtualBox due to failure installing VBoxUSB driver:
{{{
Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
}}}

When viewing the properties of VBoxUSB.inf it reports the following for the sha256 cert:
{{{
No signature was present in the subject
}}}

I have attached signtool output comparing VBoxUSB.sys and VBoxUSB.cat. The same cert is successfully validated on the .sys but fails on the .cat with ""No signature found"".

I am running a dev build of Windows 11, not currently sure whether this issue affects all Windows 11.

Forum thread: https://forums.virtualbox.org/viewtopic.php?f=6&t=104557"	sgadsby
20638	Windows does not start	Windows	VirtualBox 6.1.28	defect	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
20602	UI not working when Win10 User resize scale.	Windows	VirtualBox 6.1.26	defect	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
20581	Accessibility. Inaccessible shut down virtual machine screen with screen readers enabeled.	Windows	VirtualBox 6.1.26	defect	2021-09-28T08:51:51Z	2021-09-30T16:15:26Z	2021-09-30T16:15:26Z	"When navigating the virtual machine shut down screen with screen reader enabeled, none of the elements can be announced by screen reader. All of the elements are announced as ""Unknown"".
Steps to reproduce:
1. Launch NVDA. You can get it from:
 https://nvaccess.org/
2. Launch virtual box and launch virtual machine in it.
3. When the virtual machine is launched, press right CTRL+q key combination.
You will here: close virtual machine.
4. Tab between elements.
You will here ""Unknown"".
Expected result:
Screen reader should announce the element's name, role and value. In this case: Okay and cancel buttons and the set of radiobuttons: ""Save the machine state, Send the shutdown signal, Power off the machine"".
Actual result: Screen reader doesn't announce any elements, it keeps saying ""Unknown"" while tabbing and moving with up and down arrows between radio buttons, so it is impossible to shut down the virtual machine using the screen reader.
See standards and guidelines:
https://www.w3.org/WAI/WCAG21/Understanding/name-role-value.html"	Vsevolod Popov
20584	Mutliple CPU's Stalls When Loading	Windows	VirtualBox 6.1.26	defect	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
20576	Installer must be able to update VBoxSDS windows service entry	Windows	VirtualBox 6.1.26	defect	2021-09-25T18:05:32Z	2021-09-25T18:05:32Z	2021-09-25T18:05:32Z	"When VBoxSDS erxists in windows service list, installer fails. 

It's not so hard to invoke ""sc delete VBoxSDS"" command, report to user(write log entry) if necessary and successfully proceed. As it happens after manual ""sc delete"".

In case there was a failure with loss of previously installed files, simple over-[writing-existent-system-entries-]installation - the most obvious and easy solution - becomes troublesome and painful."	KDV
20575	Installer must never rely on trash, left by previous version	Windows	VirtualBox 6.1.26	defect	2021-09-25T17:54:34Z	2021-09-25T17:54:34Z	2021-09-25T17:54:34Z	"Installing VBox of newer version into windows after ${user profile}/Local/Temp cleanup fails.
Installer starts to beg for previous version MSI package, providing no workarounds.

Installation process must flow successfully instead. Installer must be able to upgrade or eradicate previous version traces at least. No trash, especially (installing sub-)system critical one must be left. A warning(never blocking failure) message about eradicating previous version could be provided to user, if necessary."	KDV
20550	Failed to save machine state	Windows	VirtualBox 6.1.26	defect	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
20531	The CentOs screen is getting stuck after starting it	Windows	VirtualBox 6.1.18	defect	2021-09-01T06:36:30Z	2021-09-07T09:57:41Z	2021-09-07T09:57:41Z	"After starting the CentOS in the virtual box, it buffers and gets stuck at this screen for a long time.
Windows was restarted, shutdown and started again and the same for the virtual box but the issue remains. I have a lot of data which i need to retain after this issue is fixed.
"	ishwarya
20505	Wrong System Time in OS/2 Guest	Windows	VirtualBox 6.1.24	defect	2021-08-18T16:23:17Z	2021-08-18T16:23:17Z	2021-08-18T16:23:17Z	"There is a problem with the ""Guest Additions TimeSync Service"" for OS/2 when using the long format for the TZ environment variable on the guest like

TZ=MET-1DST,3,-1,0,7200,10,-1,0,10800,3600

I've posted a detailed description to the forum, please see [https://forums.virtualbox.org/viewtopic.php?f=4&t=103491 this thread].

The problem seems to be an issue in the underlying libc, see the replies from user LewisR in the same thread and especially [https://github.com/bitwiseworks/libc/issues/109 here] and [https://github.com/bitwiseworks/libc/issues/109#issuecomment-882764025 there].

A workaround is to start vboxservice.exe with the ""Guest Additions TimeSync Service"" disabled.

Probably the Guest Additons for OS/2 should be liked against a fixed version of libc once it gets available.


Thank you,

Michael
"	mipri
17696	Processor ID and MotherBord ID Missing	Windows	VirtualBox 5.2.8	defect	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
20470	Enabled VB Host Only Network adapter causes Internet Connection Icon to show No Internet on Windows 10	Windows	VirtualBox 6.1.24	defect	2021-07-23T08:26:45Z	2021-07-23T08:31:45Z	2021-07-23T08:31:45Z	"When having VirtualBox Host Only Network adapter enabled across reboots on Windows 10, the Internet Connection Icon soon (time varies somewhat) starts to show no internet connection even though the internet connection works correctly.

Took me some time to find out that the adapter was the cause for this problem. Now I always disable the adapter before rebooting."	loxia_01
20454	Linux cannot Log  user in with visual interface	Windows	VirtualBox 6.1.22	defect	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
20442	XHCI has wrong PCI config space and runtime register settings	Windows	VirtualBox 6.1.22	defect	2021-06-30T21:17:30Z	2021-07-05T07:24:04Z	2021-07-05T07:24:04Z	"host: Win-10, guest: OS/2

These PCI config space registers contain incorrect values (without being touched by any driver):
SBRN: is=0x20 should be=0x30 (only allowed value)
FLADJ: is=0x00 should be=0x20 (default value)

Additionally, runtime register MFINDEX is upcounting and wrapping even though the operational USBCMD register does not have the ""R/S"" bit set (""run"").

This is according to XHCI spec. I am not enough of a virtual machine expert to know if it is the USB HW that is not working according to spec or if it is the virtualization.

I have tried to get XHCI working with the corresponding XHCI driver (for OS/2) but it would not work. Not sure if that's the HW/virtualization or the HC driver doing the wrong thing."	lerdmann
10771	VirtualBox Extension Pack installation failed exit code 128 E_FAIL (0x80004005)	Windows	VirtualBox 4.1.18	defect	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
20379	6.1.18 to 6.1.20 Intel pro/1000 changes	Windows	VirtualBox 6.1.20	defect	2021-05-25T12:45:54Z	2021-05-30T09:54:08Z	2021-05-30T09:54:08Z	"Hello,

Current Menuet64 network driver (bridged) for i8254x works fine with 
VirtualBox 6.1.18, but not anymore with 6.1.20.

I've read from previous tickets that for example the 
RDT register and interrupts are handled differently in 6.1.20.

So could you provide some (bit-level) details about the RDT 
register (and possibly other) changes, so I can debug the driver here ?

Thank you.
"	AndrewMC
20352	[Guest - windows 7] Cannot detect Qualcomm MMC Storage USB device	Windows	VirtualBox 6.1.22	defect	2021-05-09T22:30:33Z	2021-05-09T22:30:33Z	2021-05-09T22:30:33Z	"*This is a CRITICAL issue related to Android embeded development on Windows guest machine;[[BR]]
Universal Qualcomm USB Driver: [https://gsmusbdrivers.com/download/qualcomm-hs-usb-qdloader-9008-driver-64-bit-windows/] [[BR]]
Steps to reproduce:
1. Access Edl mode on a Qualcomm-insided Android device (by ADB, test point on board, etc ...) [[BR]]
2. Open Device management on Windows guest OS and check detected usb passthrought devices; [[BR]]
Results:
1. Only host machine detects successfully Qualcomm MMC USB Storage device, we can check in Disk Management programme, it shows all related partitions on on-board MMC storage; [[BR]]
2. Guest machine can NOT detect Qualcomm MMC USB Storage device and all related MMC partitions; [[BR]]

Expectations:
The guest machine should detects Qualcomm MMC USB Storage device and all related MMC partitions [[BR]]

Screenshots: [https://drive.google.com/drive/folders/1MKIm7xnrIDJ0BfPKRLfOJzZmK3z61DGk?usp=sharing]
References:
1. https://www.thecustomdroid.com/qualcomm-edl-mode-guide/ [Adb commandline approach]
2. http://andrux-and-me.blogspot.com/2015/09/bringing-lg-g2-back-from-dead.html [Onboard test point approach]
Thanks team,"	Kelvin
20343	instruction 0x00007FFD15769B2C	Windows	VirtualBox 6.1.22	defect	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
16844	DRIVER_POWER_STATE_FAILURE VirtualBox 5.1.22	Windows	VirtualBox 5.1.22	defect	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
20314	0x00007FF874BF9B2C address	Windows	VirtualBox 6.1.18	defect	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
20179	serial port freeze	Windows	VirtualBox 6.1.18	defect	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
20164	Error while trying to use VM for SAS University Studio	Windows	VirtualBox 6.0.22	defect	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
20124	Unable to add Guest Addition in macOS Big Sur 11.1	Windows	VirtualBox 6.1.16	defect	2021-01-12T09:45:29Z	2021-01-12T09:45:29Z	2021-01-12T09:45:29Z	"Host - Windows 10 20H2
Guest - macOS Big Sur 11.1

Unable to add Guest Addition. After double-clicking VBoxDarwinAdditions.pkg installer fails with the message - The installation failed. The installation encountered an error that caused the installation to fail. Contact the software manufacturer for assistance."	hrk
20100	BSOD caused by VirtualBox and USBNetworkGate	Windows	VirtualBox 6.1.16	defect	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
19766	Why can't I install Ubunut 20.04 (Mate) when WSL2 and Hyper-V is enabled?	Windows	VirtualBox 6.1.10	defect	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
20058	Virtual Box encounters error while Ubuntu 20.04 VM is running	Windows	VirtualBox 6.1.16	defect	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
20046	Host-Only Adapter not migrated during Windows 10 inplace upgrade	Windows	VirtualBox 6.1.16	defect	2020-11-17T13:20:49Z	2020-11-17T13:20:49Z	2020-11-17T13:20:49Z	during an inplace upgrade of Windows 10 (doesn't matter which version) the VB Host-Only Adapter does not getting migrated (also it doesn't matter which VB version). Logfiles says driver is not supported and is therefore excluded from migration. (see screenshot attached) As consequence the adapter doesn't exist anymore after feature update and also cannot be created with the same IP settings since some keys remain in the registry (which can basically be deleted as a workaround).	csps
19955	VirtualBox Manager crashes when opening	Windows	VirtualBox 6.1.14	defect	2020-10-10T18:08:05Z	2020-10-10T18:09:03Z	2020-10-10T18:09:03Z	"Occasionally, the VirtualBox Manager crashes when starting. Host - Windows 10 x64.

Stack trace:


{{{
>	Qt5GuiVBox.dll!QPainter::PixmapFragment::create() + 2312 bytes	Unknown
 	Qt5WidgetsVBox.dll!QGraphicsScene::wheelEvent() + 1864 bytes	Unknown
 	Qt5WidgetsVBox.dll!QGraphicsScene::removeItem() + 2447 bytes	Unknown
 	Qt5WidgetsVBox.dll!QGraphicsScene::destroyItemGroup() + 823 bytes	Unknown
 	Qt5WidgetsVBox.dll!QGraphicsView::paintEvent() + 1570 bytes	Unknown
 	Qt5WidgetsVBox.dll!QAbstractSlider::event() + 1439 bytes	Unknown
 	Qt5WidgetsVBox.dll!QFrame::event() + 55 bytes	Unknown
 	Qt5WidgetsVBox.dll!QGraphicsView::viewportEvent() + 164 bytes	Unknown
 	Qt5CoreVBox.dll!QCoreApplicationPrivate::sendThroughObjectEventFilters() + 222 bytes	Unknown
 	Qt5WidgetsVBox.dll!QApplicationPrivate::notify_helper() + 254 bytes	Unknown
 	Qt5WidgetsVBox.dll!QApplication::notify() + 7243 bytes	Unknown
 	Qt5CoreVBox.dll!QCoreApplication::notifyInternal2() + 168 bytes	Unknown
 	Qt5WidgetsVBox.dll!QWidgetPrivate::drawWidget() + 2267 bytes	Unknown
 	Qt5WidgetsVBox.dll!QWidgetPrivate::paintSiblingsRecursive() + 913 bytes	Unknown
 	Qt5WidgetsVBox.dll!QWidgetPrivate::drawWidget() + 2731 bytes	Unknown
 	Qt5WidgetsVBox.dll!QWidgetPrivate::paintSiblingsRecursive() + 913 bytes	Unknown
 	Qt5WidgetsVBox.dll!QWidgetPrivate::drawWidget() + 2731 bytes	Unknown
 	Qt5WidgetsVBox.dll!QWidgetPrivate::paintSiblingsRecursive() + 913 bytes	Unknown
 	Qt5WidgetsVBox.dll!QWidgetPrivate::paintSiblingsRecursive() + 678 bytes	Unknown
 	Qt5WidgetsVBox.dll!QWidgetPrivate::drawWidget() + 2731 bytes	Unknown
 	Qt5WidgetsVBox.dll!QWidgetPrivate::paintSiblingsRecursive() + 913 bytes	Unknown
 	Qt5WidgetsVBox.dll!QWidgetPrivate::drawWidget() + 2731 bytes	Unknown
 	Qt5WidgetsVBox.dll!QWidgetPrivate::paintSiblingsRecursive() + 913 bytes	Unknown
 	Qt5WidgetsVBox.dll!QWidgetPrivate::drawWidget() + 2731 bytes	Unknown
 	Qt5WidgetsVBox.dll!QWidgetPrivate::invalidateBuffer_resizeHelper() + 7691 bytes	Unknown
 	Qt5WidgetsVBox.dll!QWidgetPrivate::invalidateBuffer_resizeHelper() + 8246 bytes	Unknown
 	Qt5WidgetsVBox.dll!QWidgetPrivate::syncBackingStore() + 71 bytes	Unknown
 	Qt5WidgetsVBox.dll!QWidget::underMouse() + 14914 bytes	Unknown
 	Qt5WidgetsVBox.dll!QApplicationPrivate::notify_helper() + 274 bytes	Unknown
 	Qt5WidgetsVBox.dll!QApplication::notify() + 7243 bytes	Unknown
 	Qt5CoreVBox.dll!QCoreApplication::notifyInternal2() + 168 bytes	Unknown
 	Qt5GuiVBox.dll!QGuiApplicationPrivate::processExposeEvent() + 277 bytes	Unknown
 	Qt5GuiVBox.dll!QGuiApplicationPrivate::processWindowSystemEvent() + 306 bytes	Unknown
 	Qt5GuiVBox.dll!QWindowSystemInterface::sendWindowSystemEvents() + 153 bytes	Unknown
 	Qt5GuiVBox.dll!QWindowSystemInterface::flushWindowSystemEvents() + 374 bytes	Unknown
 	qwindows.dll!00007ffba0e161b9()	Unknown
 	qwindows.dll!00007ffba0e20cf5()	Unknown
 	qwindows.dll!00007ffba0e2134c()	Unknown
 	user32.dll!CallWindowProcW() + 1016 bytes	Unknown
 	user32.dll!DispatchMessageW() + 924 bytes	Unknown
 	user32.dll!SendMessageTimeoutW() + 323 bytes	Unknown
 	ntdll.dll!KiUserCallbackDispatcher() + 36 bytes	Unknown
 	win32u.dll!NtUserDispatchMessage() + 20 bytes	Unknown
 	user32.dll!DispatchMessageW() + 682 bytes	Unknown
 	combase.dll!RoClearError() + 1131 bytes	Unknown
 	combase.dll!RoGetAgileReference() + 11354 bytes	Unknown
 	combase.dll!RoGetAgileReference() + 10555 bytes	Unknown
 	combase.dll!CoWaitForMultipleHandles() + 4854 bytes	Unknown
 	combase.dll!WindowsCompareStringOrdinal() + 2051 bytes	Unknown
 	combase.dll!CoInitializeEx() + 9499 bytes	Unknown
 	combase.dll!CoGetStandardMarshal() + 3028 bytes	Unknown
 	combase.dll!CStdStubBuffer_Invoke() + 366 bytes	Unknown
 	rpcrt4.dll!Ndr64AsyncServerCallAll() + 2884 bytes	Unknown
 	combase.dll!PropVariantClear() + 3080 bytes	Unknown
 	combase.dll!00007ffbc8239082()	Unknown
 	UICommon.dll!CVirtualBox::GetVersion() + 89 bytes	Unknown
 	VirtualBox.exe!00007ff72a8c9e55()	Unknown
 	Qt5CoreVBox.dll!QAbstractAnimation::event() + 201 bytes	Unknown
 	Qt5WidgetsVBox.dll!QApplicationPrivate::notify_helper() + 274 bytes	Unknown
 	Qt5WidgetsVBox.dll!QApplication::notify() + 7243 bytes	Unknown
 	Qt5CoreVBox.dll!QCoreApplication::notifyInternal2() + 168 bytes	Unknown
 	Qt5CoreVBox.dll!QCoreApplicationPrivate::sendPostedEvents() + 561 bytes	Unknown
 	qwindows.dll!qt_plugin_instance() + 9871 bytes	Unknown
 	Qt5CoreVBox.dll!QEventDispatcherWin32::registerEventNotifier() + 1330 bytes	Unknown
 	user32.dll!CallWindowProcW() + 1016 bytes	Unknown
 	user32.dll!DispatchMessageW() + 601 bytes	Unknown
 	Qt5CoreVBox.dll!QEventDispatcherWin32::processEvents() + 1172 bytes	Unknown
 	qwindows.dll!qt_plugin_instance() + 9833 bytes	Unknown
 	Qt5CoreVBox.dll!QEventLoop::exec() + 461 bytes	Unknown
 	Qt5CoreVBox.dll!QCoreApplication::exec() + 338 bytes	Unknown
 	VirtualBox.exe!TrustedMain() + 821 bytes	Unknown
 	VirtualBox.exe!TrustedMain() + 1489 bytes	Unknown
 	VirtualBox.exe!00007ff72a9b8a5e()	Unknown
 	VirtualBox.exe!00007ff72a9b6d97()	Unknown
 	kernel32.dll!BaseThreadInitThunk() + 20 bytes	Unknown
 	ntdll.dll!RtlUserThreadStart() + 33 bytes	Unknown

}}}
"	fandrei
19927	"Audio: garbled and hanging audio is caused by a ""bug"" in VirtualBox 5.x and up"	Windows	VirtualBox 6.1.14	defect	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
14291	Lots of error entries in VBoxSVC.log	Windows	VirtualBox 5.0.0	defect	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
19859	After executing a tutorial virtualbox is becoming super slow to run a Windows 10 instance	Windows	VirtualBox 6.1.10	defect	2020-09-04T15:12:27Z	2020-09-04T15:12:27Z	2020-09-04T15:12:27Z	"I wanted to find out how to do this task : https://www.youtube.com/watch?v=6wVJUimaq2U

I executed it without trouble up until 08:40 ... which means that I didn't need to go to execute the following steps since VirtualBox recognized the UEFI drive and start the Windows from the boot manager.

Version : [https://pasteboard.co/JpxlUmV.png]

Running screenshot : [https://pasteboard.co/JpxldMc.png]

So the problem is VirtualBox is running at 40% CPU usage, I have enable UEFI and 16 GB RAM with 8 cores but it is hanging in the screenshot which I sent.

It seems that there is a bug."	vritual-boxer
19842	Settings' 'OK' button not working.	Windows	VirtualBox 6.1.10	defect	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
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)	Windows	VirtualBox 6.1.10	defect	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
19790	virtual machine startup error (0x80004005)	Windows	VirtualBox 5.2.40	defect	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
8698	VirtualBox Host-Only Network Adapter prevents multicast traffic	Windows	VirtualBox 4.0.4	defect	2011-04-07T21:12:06Z	2020-06-28T14:04:55Z	2020-06-28T14:04:55Z	"After installing Oracle VirtualBox and VirtualBox installing the ""VirtualBox Host-Only Network"" on my Windows 7 64-bit machine, I am no longer able to receive multicast streams on the host machine. This problem occurs even when VirtualBox is not running.

To get around this issue, I have to go into Network Connections everytime I want to stream from a multicast source and disable the VirtualBox Host-Only Network adapter. I then have to remember to reenable it everytime I wish to use VirtualBox."	Michael Irigoyen
18969	VirtualBox manager sometimes crashes on start	Windows	VirtualBox 6.0.12	defect	2019-09-26T17:26:18Z	2020-06-25T16:29:55Z	2020-06-25T16:29:55Z	"I can't determine repeatable conditions, but sometimes VirtualBox.exe crashes on start. It's a normal install of the latest release (6.0.12) on Windows 10 x64 1903.
It always crashes in Qt5GuiVBox.dll, but the exception differs, sometimes it's 0xc0000005, sometimes it's 0xc000041d. Offset is always 0x00000000001e384e.

I'm not using VB that often nowadays, but I haven't seen any crashes when running VMs yet, only on start of the manager GUI."	pupertest
19668	Result Code: E_INVALIDARG (0x80070507)	Windows	VirtualBox 6.1.10	defect	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
17811	VirtualBox (vboxdrv) installation FAILED on some Windows 7 PCs	Windows	VirtualBox 5.2.12	defect	2018-06-08T02:16:11Z	2020-06-15T19:31:59Z	2020-06-15T19:31:59Z	"Hi All,

I'we got a new Win 7 PC: Toshiba Z40-C laptop with Intel Core i7 6600U CPU.
VirtualBox 5.2.12 (latest), but also tried 5.1.38 and 5.0.40, with the
same problem. (and even the ancient 4.1.6 version from 2011, before hardening)

One thing is special about this particular Windows 7 PC: It uses UEFI.
All the other dozens of my Windows 7 PCs, where VirtualBox works like
a charm, all use BIOS.
Maybe some kind of security properties do differ somehow.

VBox.log:
https://www.dropbox.com/s/8ss3510bofy4ntd/vbox.log.txt?dl=0

The problem is: no matter what I do, ""vboxdrv"" never gets installed.

It says cannot start VM : ""Make Sure the kernel module has been loaded
successfully"".

Error in supR3HardenedWinReSpawn
NtCreateFile(\Device\VBoxDrvStub) failed

Looking at a list of drivers in ""Device Manager"", I cannot see
""vboxdrv"" listed there. (Even with show hidden -> Non-plug-n-play
devices)

More info:
C:\Users\Alexey>sc.exe query vboxdrv

{{{
SERVICE_NAME: vboxdrv
        TYPE               : 1  KERNEL_DRIVER
        STATE              : 1  STOPPED
        WIN32_EXIT_CODE    : 2  (0x2)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0
}}}

It seems there is a conflict between VirtualBox and some other
software / device driver on my PC, or OS configuration. But how to figure it out ?
The PC is totally new, but it has a lot of Toshiba drivers & utils included.
Restarting the PC (the Windows way) didn't help either.

Registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\VBoxDrv
{{{
DisplayName=VBox Support Driver
ImagePath=\??\C:\Program Files\Oracle\VirtualBox\VBoxDrv.sys
ErrorControl=1
Start=3
Type=1
}}}

Event Viewer:
{{{
System/Information

---
A service was installed in the system.

Service Name:  VBox Support Driver
Service File Name:  C:\Program Files\Oracle\VirtualBox\VBoxDrv.sys
Service Type:  kernel mode driver
Service Start Type:  demand start
Service Account:

---
System/Error

The VBox Support Driver service failed to start due to the following error:
The system cannot find the file specified.
}}}


In reality the driver file exists:

C:\Windows\System32\drivers\vboxdrv.sys
and
C:\Program Files\Oracle\VirtualBox\drivers\vboxdrv.sys

yet, it is completely absent from Windows Device Manager (driver list).
So the driver was copied, but not loaded.


-Alexey Eromenko ""Technologov"". 08.06.2018."	Technologov
19626	VirtualBox host-only adapter keeps getting set to an invalid configuration, which breaks multicast.	Windows	VirtualBox 6.1.8	defect	2020-05-27T18:29:01Z	2020-05-28T14:51:14Z	2020-05-28T14:51:14Z	"Greetings!

OS: Windows 10 Pro x64
VirtualBox: 6.1.8r137981(Qt5.6.2)

The ""VirtualBox Host-Only Network"" adapter in Windows keeps getting set to an invalid state. When virtualbox is first installed, it populates the IPv4 IP address and DNS server. I also have to manually set the ""Automatic Metric"" to something like 800 as leaving it set to automatic breaks Multicast packets.

Every so often, I'll find I can't join a Multicast stream. Checking the settings in the ""VirtualBox host-only network"" adapter reveals:
- IP address/Subnet/Gateway are still set to manual, but are blank.
- DNS server is set to manual, and is completely blank
- Automatic Metric is set to automatic.

If I set the metric back to 800 and click ok, I get a message saying the IP address needs to be specified.

I have absolutely no idea what keeps changing the network properties for this adapter and setting it to an invalid state."	Fishscene
13884	Keys repeat in guest VM (Windows 7 Pro 32 bit OS)	Windows	VirtualBox 4.3.22	defect	2015-02-23T15:02:57Z	2020-04-13T08:19:51Z	2020-04-13T08:19:51Z	"Periodically the keys will repeat in the VirtualBox guest OS. I am running 4.3.22 r98236 with VirtualBox guest additions and the extension pack for the same version.

This has been happening for many months. I was following a discussion in https://forums.virtualbox.org/viewtopic.php?f=8&t=55373&sid=5dede60332149c70efbe3c8be4fcfd97&p=313722#p313722 but it was suggested to open a ticket for the issue.

The problem does not occur on the host, only the guest. I just had the issue occur  at 2/23/2015 9:40 AM, tried to check the vbox.log but did not see anything that I could relate to the problem. I have attached the logs. The 



"	kjoyce
19479	Unable to create Host-Only Network on Virtual Box	Windows	VirtualBox 6.1.4	defect	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
18629	Failed to open a session for the virtual machine vm1.	Windows	VirtualBox 6.0.6	defect	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
19417	incorrect power off handling with background vms	Windows	VirtualBox 6.1.4	defect	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
19389	win 7 problemes	Windows	VirtualBox 6.1.4	defect	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
19362	VirtualBox crash on start ReactOS with BTRFS	Windows	VirtualBox 6.1.4	defect	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
19354	Problems accessing lots of items with nvda screenreader in virtualbox	Windows	VirtualBox 6.1.4	defect	2020-02-27T09:06:14Z	2020-02-27T09:06:14Z	2020-02-27T09:06:14Z	"It is impossible to access lots of items in virutalbox using nvda screenreader. For example, you cannot choose one virtual machine if there are several virtual machines, you cannot choose an iso image file when first running a virtual machine. To reproduce the steps you should: 1. Launch nvda screenreader, 2. Open virtualbox, create a virtual machine and launch it. When the window with choosing the image disk opens press tab and you will hear the phrase ""uknown"". Expected behaviour: you should hear buttons such as continue, browse, you should be able to access the list with drives. I am also not able to quit the virtual machine using nvda screenreader."	Vsevolod Popov
19280	6.1.2 Installation failed, could not run required dll	Windows	VirtualBox 6.1.2	defect	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
6579	Cannot get a bridged network connection on guest OSes via a WPA2 wireless network with MSCHAPv2/PEAP authentication	Windows	VirtualBox 3.1.6	defect	2010-04-22T21:58:37Z	2020-01-28T17:49:10Z	2020-01-28T17:49:10Z	"I have WinXP SP3 as a host OS.  I have used XP SP3 and Ubuntu 9.10 as guest OSes.  The problem appears to happen when I am conencted to a WPA2 wireless network with PEAP/MSCHAPv2 authentication.  The guest OSes do not get an IP address.  On the Windows guest, I get a private IP.

When I try this with networks with no PEAP/MSCHAPv2 authentication, this problem doesn't happen as I am able to get IP addresses for both guest OSes.

There was also a discussion on the VB forums where I discussed this:  [http://forums.virtualbox.org/viewtopic.php?f=6&t=30093]

Please advise.  Thanks."	prefection9791
19250	processor execution cap is broken for single cpu vms	Windows	VirtualBox 6.0.16	defect	2020-01-21T19:37:35Z	2020-01-21T19:37:35Z	2020-01-21T19:37:35Z	"build a single cpu vm
set exec cap at 70%
host only ever uses 35% (as if 70% has been split between 2 cpus)

workaround create a dual cpu vm
set exec cap at 50%
host then uses 60% cpu (well it better than 35%)"	clive darra
19218	The driver detected an internal driver error on \Device\VBoxNetLwf.	Windows	VirtualBox 6.1.0	defect	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
14823	Error messages on a Windows 7 shutdown when VirtualBox is still open	Windows	VirtualBox 5.0.10	defect	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
19011	Right screen buttons etc	Windows	VirtualBox 6.0.12	defect	2019-10-13T17:55:23Z	2019-10-21T06:09:10Z	2019-10-21T06:09:10Z	"Win 10 pro / Chrome / 
Right side - menu ellipses, x out and minimize/maximize, more than 5 tabs -cease working.
VB reinstall was a temporary fix
"	Amadeo
19012	VERR_CFGM_VALUE_NOT_FOUND on boot.	Windows	VirtualBox 6.0.12	defect	2019-10-13T20:03:29Z	2019-10-16T03:34:08Z	2019-10-16T03:34:08Z	"Using VirtualBox version 6.1.0_BETA1 r133315. VM crashed on guest shutdown and now won't boot, throws ""Failed to construct 'efi'/0! VERR_CFGM_VALUE_NOT_FOUND (-2103) - Value not found."" on boot.

Logs: https://pastebin.com/sBQjAhfY

vbox: https://pastebin.com/HLNQWz4S"	DeezNutz
19017	Updated to 5.2.34 and now VM constantly crashes	Windows	VirtualBox 5.2.34	defect	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
18947	usb audio is extremely choppy	Windows	VirtualBox 6.0.12	defect	2019-09-19T18:21:53Z	2019-09-24T06:09:08Z	2019-09-24T06:09:08Z	"Guest: OS/2

In principle, usb audio does work under OS/2 but the sound is extremely choppy. I am using a USB 1.x sound device (compatible with usb audio standard 1.0). With older versions of VirtualBox, this problem did not exist but the guest was more unstable (guest crashed)."	lerdmann
18855	please add much better sound support for DOS VMs	Windows	VirtualBox 6.0.10	enhancement	2019-08-20T01:30:09Z	2019-08-20T06:30:37Z	2019-08-20T06:30:37Z	"The current implementation you have is apparently DMA-based only and is based on an unknown model number of SoundBlaster 16, which I think is the only choice that has a chance of working in DOS (I don't know about ICH AC97).

Most use in DOS hinges on making use of an I/O address such as A220. That is what I'm hoping you can implement along with the address for MIDI support (i.e. P330). I do not know how you implement the interrupt and high/low DMA but seems like the I/O address has been the biggest issue stopping sound from working.

Also, how exactly is your sound virtualization implemented?  Is there a module that can be added to VirtualBox to accomplish this (something like an Extension Pack for DOS), or is there a module that can be added as a 'pre-boot' BIOS extension inside the DOS guest (similar to how OnTrack DDO used to work)?"	Steve Sybesma
18837	VB Manager crash silently when maximizing window (Fixed in SVN)	Windows	VirtualBox 6.0.10	defect	2019-08-15T03:15:16Z	2019-08-18T19:50:44Z	2019-08-18T19:50:44Z	"host win10 10.0.17763 N/A Build 17763
VB 6.0.10 r132072 (Qt5.6.2)

* Open VM VB Manager, select VM
* Open VM logs
* Maximize window

List of VM widget become black and then process silently crash"	gvaduha
18381	Certain sounds seem to crash OS/2 guest	Windows	VirtualBox 6.0.4	defect	2019-01-29T06:24:16Z	2019-08-01T16:01:43Z	2019-08-01T16:01:43Z	"I don't know if this defect is new to version 6, but I've just noticed that generating some sounds crashes the guest. In particular generating system error sound in rapid succession does that. For example trying to delete non-existing characters in system editor. The guest will lock up with sometimes partial error sound playing in the loop and the mouse cursor will disappear when over the guest window. Selecting machine close action will change the window to not responding state (message in the title bar) and the subsequently clicking on the close button will cause the guest state to show aborted.
"	Rafcio
7756	Occasional Hang when saving machine state - data loss	Windows	VirtualBox 3.2.10	defect	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
18752	BSOD When Running VM in Windows 7	Windows	VirtualBox 6.0.8	defect	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
5104	VirtualBox taskbar item flashing for no reason (or reason not apparent)	Windows	VirtualBox 3.0.6	defect	2009-10-02T15:18:07Z	2019-06-21T08:02:39Z	2019-06-21T08:02:39Z	"The guest isn't doing anything, no CPU or disk activity on Windows XPsp3 or Ubuntu Guests with a Windows XPsp3 host but the actual window for that guest starts flashing in my taskbar, given enough time all of the running windows are flashing and it's just plain irritating :-p.

I open the window to expect some important message and nothing. I'm not sure what's causing it to flash or what it's altering my attention to but eventually it gets to me and I have to open it just to stop it.

"	Chris
18379	New OS/2 shared folders feature locks up the guest => Fixed in SVN	Windows	VirtualBox 6.0.4	defect	2019-01-29T05:44:57Z	2019-05-19T05:04:23Z	2019-05-19T05:04:23Z	"After adding the new shared folders installable file system (VBoxSF.IFS) the guest GUI started to lock up just a second after VBoxService is executed from STARTUP.CMD. The mouse cursor still moves, so this is not a hard lock, but any interaction with GUI is impossible. The guest has to be powered off. The only workaround is to comment out the IFS statement in CONFIG.SYS.
"	Rafcio
18642	Screen Video Recorder	Windows	VirtualBox 6.0.6	defect	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
18647	E_FAIL (0x80004005)	Windows	VirtualBox 6.0.8	defect	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
16220	Improper font scaling in VB Manager	Windows	VirtualBox 5.1.10	defect	2016-11-23T14:44:51Z	2019-04-30T13:38:53Z	2019-04-30T13:38:53Z	"I am running Windows 10 Professional on a Surface Pro 4. The VirtualBox Manager window has improper font scaling on my main display, a ""normal"" DPI external monitor. See attached image '''VirtualBox Manager on external monitor.png'''. If I drag the window to the Surface Pro 4's internal window, it looks worse; see '''VirtualBox Manager on Surface Pro 4 monitor.png'''.

BACKGROUND: In my current configuration, the Surface Pro 4 boots with its Surface Dock attached. It boots into a situation where an external, 1920x1080 monitor is the primary monitor; the built-in monitor is a secondary monitor. (It always boots this way if the Surface Dock is connected per my intentional configuration of Windows's display settings.) All applications, except VirtualBox, have fonts scaled properly for this normal resolution, main monitor.

This may relate to #9864, an old ticket."	Aren Cambre
18601	Oracle_VM_VirtualBox_Extension_Pack-6.0.6.vbox-extpack error	Windows	VirtualBox 6.0.6	defect	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
18590	keyboard losing functionality in guest	Windows	VirtualBox 6.0.6	defect	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
18556	I can´t able to start a virtual machine	Windows	VirtualBox 6.0.4	defect	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
18486	Black screen when trying to use Kali Linux	Windows	VirtualBox 6.0.4	defect	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
18481	Upgraded to 6.x and now VB is broken	Windows	VirtualBox 6.0.4	defect	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
18457	BSOD on Windows 7 host	Windows	VirtualBox 6.0.4	defect	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
18450	Main Window closes when second display has 150% scale	Windows	VirtualBox 6.0.4	defect	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
17933	RDP from iPad 3 (iOS 9.3.5) Problem Keyboard Access to Windows 10 pro	Windows	VirtualBox 5.2.18	defect	2018-08-16T06:38:46Z	2019-02-17T01:09:51Z	2019-02-17T01:09:51Z	"RDP from iPad 3 (iOS 9.3.5) Problem Keyboard Access, to access windows 10 pro.
Keyboard Loss can't access Windows 10 Pro. Can't input Any Char. 
Used VirtualBox 5.2.18 in Windows 7 and Virtualbox before same problem.

Thank You.

"	Kenzo
18395	animations and mouse movement flicker [OS/2 guest]	Windows	VirtualBox 6.0.4	defect	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
18306	Virtual box causes the PC to restart many times	Windows	VirtualBox 6.0.0	defect	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
18214	VM Crash when hovering optical media menu, with inaccessible media	Windows	VirtualBox 6.0.0	defect	2018-12-20T17:02:19Z	2019-01-14T17:33:13Z	2019-01-14T17:33:13Z	"Reproduce:
* Start VM
* Menu -> hover Optical media 
* an last used optical media exists which is on an inaccessible/office n etworkstorage
* the vm freezes and crashes after some seconds
* if you leave vboxmanager open, a second try works,
* if you close it, its crashing again

The bug exists at least since v5.0

Its very annoying to me, I'm using a NAS-Box which shutdowns over night till i manually start it, when i start a vm beforce that and hover the menu by accident -> crash

e.g. ISO image on \NAS542\image\Win10.iso"	serpen
18311	user interface not accessible any more using nvda screen reader	Windows	VirtualBox 6.0.0	defect	2019-01-14T12:02:40Z	2019-01-14T12:02:40Z	2019-01-14T12:02:40Z	"running windows 10 pro insider build with nvda screen reader.
can access file menus e.g file edit view but not able to hear the names of the virtual machines or arrow in the settings.
virtualbox 6.0
please could this be fixed?
Majid"	maj
18307	VM Hang during installing of Centos	Windows	VirtualBox 6.0.0	defect	2019-01-13T08:10:48Z	2019-01-14T08:13:22Z	2019-01-14T08:13:22Z	"Hello Team,
i created new VM and attach the Centos 7 ISO file
the installation screen appears after that it hang 
i tried to change the display settings as i suspect its video card issue 
but its the same issue 
i attached the logs 
thanks for support 
regards

"	Alaa
13187	VirtualBox 4.3.14 can't start VMs on certain Windows hosts	Windows	VirtualBox 4.3.14	defect	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
18241	unable to install centos in VM. Facing error which says kernel panic	Windows	VirtualBox 6.0.0	defect	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
18184	arp fails when connecting to a wireless connection on host via bridged network	Windows	VirtualBox 5.2.22	defect	2018-12-15T08:46:29Z	2018-12-18T13:51:03Z	2018-12-18T13:51:03Z	"Host: Windows 10 Pro
Guest: eCS 2.2 beta (drivers: all the latest and greatest)

From the guest, I am trying to connect to a wireless connection on the host. For sake of simplicity and performance I have set up ""bridged network"".

Sometimes but not always I have problems to access the net from the guest. When that happens, I see this (example) in the ARP table of the guest:

""arp -a"":

ARP table contents:
{{{
interface   hardware address   IP address       minutes since last use
lan 0       (incomplete)       www.xxx.yyy.zzz  0
}}}
Apparently, the ARP request does not pass through. If I reboot the guest a couple of times AND if I actually use the wireless connection on the host, then eventually, I will be able to access the wireless connection from the guest.
I have not observed this problem with a wired connection (on the host). This seems to always work ok."	lerdmann
18175	"Windows 10 build 1709 build 16299 64bit VM is not working showing error as ""Error In supR3HardenedWinReSpawn"""	Windows	VirtualBox 5.2.22	defect	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
16830	VM Manager does not remember its restored window size	Windows	VirtualBox 5.1.22	defect	2017-06-15T05:01:10Z	2018-12-07T05:30:57Z	2018-12-07T05:30:57Z	"If the window of VM Manager has been maximized and then restored, VM Manager does not remember its restored window size between restarts.
VirtualBox.xml stores the bounds of maximized window instead of the restored window in ExtraDataItem ""GUI/LastWindowPosition""."	robpats
18155	Unknown fatal error!	Windows	VirtualBox 5.2.22	defect	2018-11-28T15:28:51Z	2018-11-30T01:55:31Z	2018-11-30T01:55:31Z	Virtual box for Windows 7 x64.	AlnXpr
18128	Some strings are not translatable in macOS	Windows	VirtualBox 5.2.22	enhancement	2018-11-13T16:52:28Z	2018-11-14T19:08:34Z	2018-11-14T19:08:34Z	"In macOS some of the text is in english.
I would like the text to be translatable or removed for a more fully translation of VirtualBox.

Running the dmg file the first i see is the image from VirtualBox/.background/vbox_folder.tiff with the text:
""1 Double click on this icon:""
""2 Run the VirtualBox application
   from the Application Folder:""

Looking at other installers i have tried in macOS it seems they tend to use a way where you drag the icon to the application folder from left to right and then there might be an arrow suggesting what to do and some installations have no text.
If this is the ways its done in macOS then perhaps VirtualBox install could do it the same way so its consistent with how its done in other software and then perhaps the english text can be removed.



When i double click the installer (VirtualBox.pkg) i see some text like:
""Installer Oracle VM VirtualBox""
""Installering af Oracle VM VirtualBox""
""Oracle VM VirtualBox for Mac OS X""
""Welcome to Oracle VM VirtualBox 5.2.22 for Mac OS X! This installer...""

It seems to be from CoreServices/Installation so maybe the installer is already translated by Apple and then VirtualBox have added some strngs that is not translatable.
I would like the strings to be translatable."	scootergrisen
16127	Setting up virtual LPT port to connect through to real LPT port stops DOS VM starting	Windows	VirtualBox 5.1.8	defect	2016-10-29T23:19:37Z	2018-10-28T19:59:43Z	2018-10-28T19:59:43Z	"I run VirtualBox on a Windows 7 Ultimate 64 bit host.
I find that with VirtualBox 5.1.4, 5.1.6 and 5.1.8 and 5.1.9-111573 (with matching Extension Pack installed) my FreeDOS 1.1 VM will not start at all after issuing the following VBoxManage commands:
VBoxManage modifyvm ""FreeDOS 1.1"" --lptmode1 LPT1
VBoxManage modifyvm ""FreeDOS 1.1"" --lpt1 0x378 7
to create a virtual LPT port and connnect it through to my real LPT1 port (on a PCI card, at address I/O address C000)
I am reverting to VirtualBox 5.1.2 for now.
I am attaching the log files and configuration of the VM in a ZIP file.
The oldest log file ""VBox.log.3"" is one from when it last worked, the others are fails.
"	Brian Gregory
18003	Error -104 in supR3HardenedWinReSpawn	Windows	VirtualBox 5.2.18	defect	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
17978	Menuet64 intelhda does not work anymore	Windows	VirtualBox 5.2.18	defect	2018-09-11T05:44:01Z	2018-09-16T15:41:57Z	2018-09-16T15:41:57Z	"Menute64 boots fine on latest VB versions. However when updating form 5.1.30 to 5.1.38, initializing audio driver intelhda crashes VB. Included vbox.log (5.2.0).

M64 driver init while running: Menu->System->Setup (autom.driver search) (apply for audio)

Audio testapp at Menu->Coding->audio(.asm)

Menuet 64bit available at Menuetos . net / download area

Running VB on Windows 7 Home Service Pack 1, Intel Core i3, M 380, 2.53Ghz

"	MikaelM
14545	"""Failed to create host network interface"" on Windows 10"	Windows		defect	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
17955	fullscreen and gpu passtrough	Windows	VirtualBox 5.2.18	defect	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
17741	Raw-mode is unavailable courtesy of Hyper-V	Windows	VirtualBox 5.2.10	defect	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
17832	Vt-x is not available.  What tool will identify the problem?	Windows	VirtualBox 5.2.12	enhancement	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
17818	Guru Meditation 1155 (VING_EM_TRIPLE_FAULT)	Windows	VirtualBox 5.2.12	defect	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
17621	USB and LAN error when re-connecting notebook to dock	Windows	VirtualBox 5.2.8	defect	2018-03-14T14:54:10Z	2018-06-12T06:55:04Z	2018-06-12T06:55:04Z	"Environment 1:
Hardware: Dell XPS 15 with Dell Dock TB16
Software: Oracle VirtualBox 5.2.6, then updated to 5.2.8 r121009 

Environment 2:
Hardware: Dell Precision 5520 with Dell Dock TB16
Software: Citrix Desktop Player 2.5.0.10 with integrated Oracle VirtualBox 5.1.25 r117057(Qt5.6.2)


Reproducible error:

After disconnecting and reconnecting the notebook to dock:
- LAN and USB devices connected to the dock do not work
- In device manager the device ""ASMedia USB Root Hub"" shows an error:
""Windows cannot load the device driver for this hardware because a previous instance of the device driver is still in memory. (Code 38)""


Workarounds to temporarily fix the issue:

Environment 1:
Close all open VirtualBox windows

Environment 2:
Disable:
- DesktopPlayer Service 
- Citrix DesktopPlayer Mped Service
- VirtualBox Host-Only Network (in network connections)
"	ChrisSt
17023	Win 10 Surface Book and multiple Host screens, cannot start on Screen 3	Windows	VirtualBox 5.1.26	defect	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
17719	"Windows installer for 5.2.10 fails with dozens of ""Could not write value to key"" registry errors"	Windows	VirtualBox 5.2.10	defect	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
17652	Error message	Windows	VirtualBox 4.3.26	defect	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
17646	Failure to launch windows 10	Windows	VirtualBox 5.2.8	defect	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
17596	Critical Error occurs when trying to build Ubuntu 16.04.4	Windows	VirtualBox 5.2.8	defect	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
14846	VBoxManage Error about Machine XXX is not currently running and Machine XXX is really running in Windows Task Manager	Windows	VirtualBox 5.0.10	defect	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
17648	Host-Only adapter failed to install on Windows 10 OS	Windows	VirtualBox 5.2.6	defect	2018-03-29T07:20:36Z	2018-03-29T07:20:36Z	2018-03-29T07:20:36Z	"'''[How to reproduce]''' [[BR]][[BR]]
From fresh installation, I had no problem to use host-only network and the host-only adapter was present.[[BR]]
The problem began when I removed my host-only adapters using VirtualBox GUI. I was then not able to re-create it using either the GUI and the command line.

'''[Research]''' [[BR]][[BR]]
I've walk through the VirtualBox forum and Bug tracker before posting and I found a similar issue : [[BR]]
+ https://www.virtualbox.org/ticket/17354 [[BR]]
+ https://forums.virtualbox.org/viewtopic.php?f=6&t=86179 [[BR]]
Here the antivirus was involded and disable it resolved the issue. [[BR]]In my case I've completely uninstall my corporate antivirus + deactivate Windows Defender without success. [[BR]]

'''[Troubleshooting]''' [[BR]][[BR]]
+ Repair VirtualBox [[BR]]
+ Uninstall VirtualBox [[BR]]
+ Remove %userprofile%\.virtualbox [[BR]]
+ Remove drivers in %windir%\System32\drivers [[BR]]
+ Remove registry keys about VirtualBox [[BR]]
+ Install 5.2 VirtualBox [[BR]]
+ Run Installer as Admin right [[BR]]
+ Run a Ccleaner registry cleaning [[BR]]
[[BR]]
With a result always the same, failed to create host-only adapter. [[BR]]

'''[logs]''' [[BR]][[BR]]

VirtualBox Gui logs are showing : [[BR]]
{{{
Failed to create a host network interface.

Querying NetCfgInstanceId failed (0x00000002).

Code d'erreur : E_FAIL (0x80004005)
Composant : HostNetworkInterfaceWrap
Interface : IHostNetworkInterface {455f8c45-44a0-a470-ba20-27890b96dba9}
}}}

C:\Windows\INF\setupapi.dev.log
{{{
>>>  [Configure Driver Package - c:\windows\system32\driverstore\filerepository\vboxnetadp6.inf_amd64_37fe176ed22ac0b0\vboxnetadp6.inf]
>>>  Section start 2018/03/27 18:20:45.493
      cmd: ""C:\Program Files\Oracle\VirtualBox\VBoxSVC.exe"" /Helper VirtualBox\SVCHelper\{a2f92065-56fc-42e5-ada7-359a3774292e}
     sto: Source Filter  = VBoxNetAdp6.ndi
     sto: Target Filter  = ROOT\NET\0002
     inf: Class GUID     = {4d36e972-e325-11ce-bfc1-08002be10318}
     inf: Class Options  = Configurable
!!!  idb: Failed to open driver package object 'vboxnetadp6.inf_amd64_37fe176ed22ac0b0'. Error = 0x00000005
<<<  Section end 2018/03/27 18:20:45.540
<<<  [Exit status: FAILURE(0x00000005)]
}}}

'''[other]'''[[BR]][[BR]]
I remember once clicking [NO] on the UAC pop-up message asking to install host-only driver. Could the issue be trigered by this action?
[[BR]][[BR]]

Thanks for your help."	AlexRoux42
17630	wireshark can capture only one way packet	Windows	VirtualBox 5.2.8	defect	2018-03-20T11:30:15Z	2018-03-21T13:24:45Z	2018-03-21T13:24:45Z	"hi
I have windows 10 computer. 
I installed virtual box 5.2.8 and vmware workstation 14. 
I have created ubuntu vm on both virtual box and workstation and bridged network adapters to 
physical interface.  
I have installed wireshark to my computer. 
when I tried to get IP from DHCP server of DSL modem, virtualbox ubuntu get IP with same IP of the host computer. why? should it get different IP from host computer? isn't it?
I have set up static IP to ubuntu machines. I can send packets between host computer, virtual box ubuntu, vmware ubuntu and DSL modem.
when I tried to capture packets with wireshark from physical interface, I can capture both direction between host and vmware but I cannot capture virtual box packets both direction.
I can see only virtual box ubuntu outbound traffic to other machines, I cannot see inbound traffic from other machines. during this period, all traffic goes succesfully. 
why I couldn't see inbound traffic to virtual box machines. 
     "	sesci
10851	VM config file lost after host power off	Windows	VirtualBox 4.1.20	defect	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
17560	System Unstable	Windows	VirtualBox 5.2.6	defect	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
17476	Virtualbox causes SYSTEM_SERVICE_EXCEPTION on Win10	Windows	VirtualBox 5.2.6	defect	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
17508	USB Passthrough Keyboard sometimes does not detect keystrokes	Windows	VirtualBox 5.2.6	defect	2018-01-29T09:14:54Z	2018-01-29T14:07:24Z	2018-01-29T14:07:24Z	"Hi there!

I use Virtualbox on Windows 10 and have a Ubuntu 16 VM. I attach a seperate USB keyboard and mouse to the host and pass them through to the VM. This is pretty nice because with additional screen where the VM is in fullscreen mode, its almost like having two fully operational computers.

Everything works fine with the rather old version 5.0.8 r103449 of VB. I noticed that with later versions it happens that sometimes keystrokes get lost / do not get detected in the VM, especially when typing fast. The latest version I tried and I can still reproduce that behavior is 5.2.6 r120293 (Qt5.6.2). I always have the guest utilities updated and installed but they seem to have no effect here.

I really would appreciate you guys looking into that issue and fixing it, it worked in the past so maybe it's an small and easy fix. Unfortunately it's what keeps me from updating to later VB version.

Thank you and best regards,
Nils"	Nils Koenig
7972	Cannot install extension pack -- VERR_ACCESS_DENIED	Windows	VirtualBox 4.0.0	defect	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
17495	Échec de l'installation de l'extension	Windows	VirtualBox 5.2.4	defect	2018-01-22T21:49:35Z	2018-01-23T12:45:31Z	2018-01-23T12:45:31Z	"Échec de l'installation de l'extension C:/Users/moimeme
/.VirtualBox/Oracle_VM_VirtualBox_Extension_Pack-5.2.6.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-32428' -&gt; 'C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack')


VBoxExtPackHelperApp.exe: error: Failed to delete the temporary extension pack directory: VERR_ACCESS_DENIED ('C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack-_-inst-32428')


rcExit=1.

Code d'erreur : E_FAIL (0x80004005)
Composant : ExtPackManagerWrap
Interface : IExtPackManager {edba9d10-45d8-b440-1712-46ac0c9bc4c5}

"	dedalios
17446	Multiple pointing device reported when choosing USB Multi-Touch Tablet	Windows	VirtualBox 5.2.2	defect	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
17433	VMMR0.r0 Bluescreen on HP Laptop Win10 v1709	Windows	VirtualBox 5.2.4	defect	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
17413	simplify the automatically offered extension pack upgrade procedure	Windows	VirtualBox 5.2.4	enhancement	2018-01-03T09:28:31Z	2018-01-03T09:28:31Z	2018-01-03T09:28:31Z	"After upgrading an existing VirtualBox installation with extension pack installed and starting VirtualBox, a dialog is presented that an older extension pack was found and if the user wants to upgrade the extension pack. 

This is fine, however the procedure to upgrade the extension pack is rather complicated and goes as follows:

  - Older ExtPack was found, want to download and install new version? Click download
  - This is the file to download, still want to download? Click download
  - File was downloaded, upgrade? Click upgrade
  - Hey, here are the T&C for the ExtPack, agree? Click agree (after reading it carefully obviously  ;)
  - Installation occures
  - Installation successfull, do you want to delete the downloaded file? Click delete

Well, it's not that complicated but just rather annoying because it is every time the same thing and the user already made clear that he wanted to upgrade the ExtPack with the first click.

I would like to propose a simplification for this upgrade procedure:

  - After starting VirtualBox, the initial dialog is presented to give the user the chance to decide if he wants to upgrade or not
  - If the user decided to upgrade, a single dialog is presented.
    - It could contain either the link to the ExtPack that will be installed or a version comparison (current version vX.X.X, new version vX.X.Y)
    - It could contain a checkbox, which is checked by default, to delete the file after the upgrade
    - It could contain a linked message like ""By installing the extension pack, you agree to the T&C"" where the link poins to the said T&C
    - It has two buttons: ""Download & Install"" and ""Cancel""
    - Optionally display an OK dialog that installation was finished

This would drastically increase user friendliness and simplify the ExtPack upgrade procedure. Keeping the initial yes/no dialog choice to upgrade also helps the average joe to panic by being slapped in the face with a full blown dialog"	Aoshi
17393	failed to open a session Machinewrap E_FAIL 0x80004005	Windows	VirtualBox 5.1.16	defect	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
17344	VirtualBox 5.2.x installer: ProductID in MSI File and ProductID on installed system do not match	Windows	VirtualBox 5.2.0	defect	2017-12-04T13:22:11Z	2017-12-04T13:22:11Z	2017-12-04T13:22:11Z	"With the installation packages for VirtualBox 5.2.x on Windows the ProductCode that can be read from the MSI files, is not the ProductCode that is found on the system after Installation.

E.g.: 
||=Version=||=MSI value=||=""real"" value=||
|| 5.2.0-r118431 ||{1E6A323C-1BE9-49B6-8FDC-107307DBC6CE}||{9df09fcf-7f55-402e-aab8-67ffba56ea3b}||
|| 5.2.2-r119230 ||{9F5D10F9-A372-4B1E-BEB3-001B47E0C325}||{b4758fb7-76a2-4391-aca1-6bffcfc90c40}||
|| 5.2.3-119337  ||{8B91C2E7-6A86-43AE-8797-48A61E6C59AB}||{9988FC09-BE58-4DF3-9943-AC14E7A0882C}||

This breaks the common procedure ind automated software deployment:
1. extract ProductID from MSI
2. install MSI
3. check whether MSI for ProductID is installed"	WRatzka
14296	Failed to create COM object - 0x80040154	Windows	VirtualBox 5.0.0	defect	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
17272	My Windows 10 crash when I try to start the install of a linux vm	Windows	VirtualBox 5.2.0	defect	2017-11-14T15:55:31Z	2017-11-22T15:48:05Z	2017-11-22T15:48:05Z	My Windows 10 crash when I try to start the install of a linux vm. It works fine up until I hit start, I can load in the ISO file into storage but once i hit start windows crashes. I have tried the ISO for debian and ubuntu and it works fine with hyper V.	cgarry
17254	VM inaccessible due to guest additions attach issue	Windows	VirtualBox 5.2.0	defect	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
17233	vm not start	Windows	VirtualBox 5.2.0	defect	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
15633	Unable to uninstall VirtualBox	Windows	VirtualBox 5.0.22	defect	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
17223	virtualbox 5.2 win nt 4 sp1	Windows	VirtualBox 5.2.0	defect	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
17187	GPO: automatic update need to be disalbed per machine	Windows	VirtualBox 5.1.30	enhancement	2017-10-20T15:35:56Z	2017-10-20T16:20:49Z	2017-10-20T16:20:49Z	"We deploy the MSI file to some developer machines. However it annoys us permanently (every few weeks) about new unimportant version. I know there is a way to disable the warning per user, but this does not help as the software is installed per machine. I cannot change the settings file with a GPO.

We need a registry key or xml config file in app folder or a MSI propery (best) that allows us to disable automatic updates globally.

Always keep in mind that users are not allowed to install or update software."	Marc Bauer
17179	Extension pack upgrade failure (from within VirtualBOX offer to do so)	Windows	VirtualBox 5.2.0	defect	2017-10-18T18:54:04Z	2017-10-18T18:54:04Z	2017-10-18T18:54:04Z	"Running VirtualBox 5.2.0 on a recent Windows 10 Pro :
   After upgrading the software from version 5.1.28 to 5.2.0 it offered to install new extension pack to match the upgrade.
   Agreed to do so -- it showed the window and appeared as if it was downloading the pack (I believe it did, but I do not know where).
   Then it proceeded to install and failed, saying something about wrong url.
   Then it offers to retry, but the result is the same dialog, where it ""swears"" the same, so I cancel it.
   
   Downloaded the extension pack from the website. Tried to install it -- VirtualBox said I need to log on as administrator :). 
  
   Logged on as administrator, started VirtualBox and received an offer to upgrade the Extension pack to 5.2.0 -- agreed, dowloaded, and same failure trying to install with seemingly unrelated ""wrong url"".
   Downloaded the pack from the website. Fired it to install (this time as Windows administrator) -- it succeeded.
   "	Kestutiss
17138	Changes to VMDK image on USB Storage Not Preserved	Windows	VirtualBox 5.1.28	defect	2017-10-04T17:52:33Z	2017-10-05T14:06:38Z	2017-10-05T14:06:38Z	"I have a VM with a VMDK file mounted on a USB mass storage device (e:\ drive).  The Guest OS is CentOS 7.3.1611 (32 bit).  I have been using it without issues for about a week.

Yesterday, I modified a few files on the VM and then rebooted the VM --- and the file changes were gone!  I thought maybe user error, but I created a test file in my home directory and rebooted, and the file did NOT persist (as if the disk was a ramdisk, even though it's not).  I tried this several times, with different ways of rebooting (shutdown -r, manually typing sync first, CentOS GUI, etc), with the same result.

I looked through log files but didn't see anything that looked out of the ordinary.

I have a feeling this has to do with USB -- maybe plugging/unplugging other USB devices confused the OS or VirtualBox -- just a guess.  But in any case, there was no warning that my changes were not being saved onto the disk image.

After this testing, I restarted my host PC (Windows 7), and now things appear to be working -- although I have lost some trust with this setup since I don't really know what happened and it caused data loss."	Joe E Clark
17120	Installation of 5.1 & 5.2 Beta failing for Windows 10 Pro	Windows	VirtualBox 5.1.28	defect	2017-09-29T00:07:54Z	2017-09-29T02:07:06Z	2017-09-29T02:07:06Z	In multiple attempts to install on Windows 10 Pro 64 bit v1703 build 15063.608, VirtualBox fails to install. I've tried VirtualBox-5.1.24-117012-Win.exe, VirtualBox-5.1.28-117968-Win.exe, VirtualBox-5.1.29-118065-Win.exe and VirtualBox-5.2.0_BETA2-117563-Win.exe. I've attached a log from running from the command line as an admin using the --logging param. Any help would be appreciated.	ElysiumTacos
17054	Please fix virtualbox causing bsod, thx.	Windows	VirtualBox 5.1.26	defect	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
17064	VM setting for all PC users	Windows	VirtualBox 5.0.24	enhancement	2017-09-08T13:00:02Z	2017-09-08T13:00:02Z	2017-09-08T13:00:02Z	"we have '''VM Dos''' running on '''host windows'''.[[BR]]

our case is we need all users loged in this pc have this VM with same setting without call our helpdesk to config it."	NorMal PC
17063	Kernel panic on Other (Android-x86-4.4*) guest	Windows	VirtualBox 5.1.26	defect	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
16989	Snapshots should store differencing disks alongside parent virtual disks	Windows	VirtualBox 5.1.26	enhancement	2017-08-07T17:23:26Z	2017-08-15T17:01:59Z	2017-08-15T17:01:59Z	"With a VM with the VDI stored on volume J:\, after creating a snapshot, the differencing VDI is stored under C:\%USERNAME%\VirtualBox VMs\.

The VDI was stored on another volume due to space issues on C:, and the differencing disk ended up using up all space on C: when it should have been on J:"	Jessica Hamilton
10081	"Updating damages existing ""pinned"" shortcuts"	Windows	VirtualBox 4.1.8	defect	2011-12-24T21:47:27Z	2017-07-28T12:35:00Z	2017-07-28T12:35:00Z	"When you pin the shortcut to VirtualBox to the Start Menu or Taskbar in Windows 7, and then update VirtualBox (Min to Min[4.1.0 to 4.1.2], or Major to Major[3.x to 4.x]) the shortcut appears to be deleted, leaving a broken pinned shortcut that needs to be deleted, and then recreated.

No other software I have pinned appears to have this problem when performing updates.

Has happened with every version of VirtualBox I've had installed, starting around 3.1.8, possibly earlier.

Expected behavior should let existing shortcuts, pinned and otherwise, should still be functional after simple updates."	kookyman
16833	Installation of 5.x Prevents Host Machine Networking	Windows	VirtualBox 5.1.22	defect	2017-06-16T05:34:38Z	2017-06-22T15:47:40Z	2017-06-22T15:47:40Z	"I've used Virtual box for years, once it moved to 5.x I have not been able to use it due to the summary subject.   The physical machine is an i7 with Win7 x64 all the latest updates.  Contains VirtualPC, VMWare Player and VirtualBox.  The 4.3.40 works fine.  The last time I installed 5.1.22, it uninstalled 4.3.40, installed 5.1.22.  Everything worked fine for a couple days (the computer was left running or sleep mode).   On the reboot, the same thing happens, no networking on the host system, no connecting to domain controller, etc..  If you go to the control panel / network and sharing, it just has a circle hourglass going in circles and says ""Identifying..."" for the Connection: Local Area Connection and Access was ""No Network Access"".  So I went to adapter settings, right clicked on the ""VirtualBox Host-Only Network"" and clicked disable.  As soon as that was disabled, the local area network connected and everything was working again.  This is repeatable, last attempt was back in 2016.  Still a problem today."	dfatvb
12564	Unable to drag/drop ISO on cd icon on status bar	Windows	VirtualBox 4.3.6	enhancement	2014-01-03T01:05:58Z	2017-06-16T07:18:32Z	2017-06-16T07:18:32Z	"I know I do this in virtual pc (drag/drop ISO on the CD icon) and thought I was doing it in VirtualBox as well, but the latest update doesn't allow me to do that (vmware doesn't allow it which is why I don't use it much).

Can you bring drag/drop of .ISO back (or add it if it wasn't there before).  It's really a very big time saver.

"	dfatvb
16816	8042/BIOS16 keyboard issues	Windows	VirtualBox 5.0.12	defect	2017-06-06T13:02:08Z	2017-06-06T13:02:08Z	2017-06-06T13:02:08Z	"VB 5.0.12 keyboard for BIOS16 users (DOS etc) is not working good for two main reasons:
 a) modifiers keys (alt, shift, ctrl) are sticky or not detected
 b) spurios keys issued while no one key is pressed

2.
captured video: http://yadi.sk/d/Ibvjeu-03Jsfd7

video description:
i try to enter keys and try to edit the wrong one by pressing shift+cursor to block mark
- shift+cursor is not work, but instead i got
- some entered keys lost
- sometimes shift is switched ON without my will and begun to produce block selection when i enter text
- at last shift state of the DOS program and the shift state of real host keyboard lost sync

3.
i guess VBox 8042 emulated part or BIOS16 is not compatible with AT-386 existing software, 8042 can not be detected or 8042/BIOS16 can not be used by the software as needed

more decription of error is in forum here:
http://forums.virtualbox.org/viewtopic.php?p=394494#p394494

PS:
Advise me to install new version of VBox if only the keybord code in new version of VBox was really rewritten "	dldall
16776	use of USB Audio device in guest trap the host on exiting VM	Windows	VirtualBox 5.1.22	defect	2017-05-21T17:05:21Z	2017-05-21T17:05:21Z	2017-05-21T17:05:21Z	"Host: Windows 7, 32-bit
Guest: OS/2

When I use an USB Audio device (I have not tested any other isochronous
device) in the guest and if I subsequently end the VM,
a trap will happen inside VirtualBox, see attached screenshot.
Ejecting the USB Audio device in the guest before exiting the VM makes
no difference.
Using the very same USB Driver stack under an native OS/2 Installation
does not exhibit any trap."	lerdmann
16758	winxp	Windows	VirtualBox 5.1.22	defect	2017-05-15T10:17:11Z	2017-05-15T10:29:38Z	2017-05-15T10:29:38Z	Problem run VB	keriks
16684	VBoxManage.exe extpack command exhausts StdOut buffer	Windows	VirtualBox 5.1.20	defect	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
16645	"VirtualBox.dll"" failed, rc=1790"	Windows	VirtualBox 5.1.18	defect	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
16581	Scaled mode: documentation explains different	Windows	VirtualBox 5.1.18	defect	2017-03-19T11:28:38Z	2017-03-19T11:28:38Z	2017-03-19T11:28:38Z	"Previously, the 'Keep Aspect Ratio' feature was present in scale mode but removed since r59335 due to Qt5 migration.[[BR]]
However, the documentation, in chapter 1.8.5 still explains:


'''The aspect ratio of the guest screen is preserved when resizing the window. To ignore the aspect ratio, press Shift during the resize operation.'''"	ddixuike
16565	5.1.16 Guest Additions render CentOS7 VM unusable	Windows	VirtualBox 5.1.16	defect	2017-03-15T01:51:52Z	2017-03-15T02:17:56Z	2017-03-15T02:17:56Z	"After upgrading to 5.1.16 from 5.1.12, CentOS 7 fails to boot due to failure to load SELinux Policy.  Attempted (as root) 'yum reinstall selinux-targeted-policy' after GRUB coercion to boot without SELinux loaded.  Also tried (as root) 'touch /.autorelabel'.  Reboot successfully updated SELinux, however subsequent reboots fail on original issue.  
"	crowmastr
16442	Could not install Oracle_VM_VirtualBox_Extension_Pack-5.1.14-112924	Windows	VirtualBox 5.1.14	defect	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
16537	Hgh screen resoluton on a MS-DOS 6.22/Win 3.1 VM	Windows	VirtualBox 5.1.14	defect	2017-03-07T18:01:49Z	2017-03-07T21:59:21Z	2017-03-07T21:59:21Z	"Hi all,

Back when I was a kid, oh, about sometime in the mid 90s if you can go back in the ""wayback machine"" with me, I thought 640x480 was all the screen resolution I'd ever need.  My huge CRT displayed Windows 3.1 just fine back then, or so I thought.

Now, flash forward to 2017 and I have a spiffy 27-inch monitor on my computer at work.  This computer hosts a VirtualBox VM running MS-DOS 6.22 and Windows 3.1.  I am needing access to yesteryear for my job (!) because of the software this company maintains for some of its customers who, apparently, like running MS-DOS 6.22 just fine, thank you very much! :-)

So, I spun up a Oracle VM VirtualBox running MS-DOS 6.22 and Windows 3.1 thanks to some handy dandy tutorial and disk-image websites that I found.  Now, however, it will not allow me to change the screen resolution up beyond 640x480, which on my spiffy 27 inch monitor with its 2560x1440 resolution, looks soooo tiny.  Entering scaled mode does not really help, since now everything just is stretched accordingly (i.e., the Program Manager still has a small UI, just stretched and scaled into a bigger window.)

Is there any way I can tune my VM to have a higher screen resolution (i.e., smaller pixels)?  I seem to recall Windows 3.1 being responsive to those settings back in the day, but I can't quite get my head around it."	astrohart
16533	Boot from usb device.	Windows	VirtualBox 5.1.14	task	2017-03-04T11:39:58Z	2017-03-04T11:39:58Z	2017-03-04T11:39:58Z	Add boot from usb device.	q34er6ty7
16511	Running VBox prevents notebook from switching into sleeping mode	Windows	VirtualBox 5.1.14	defect	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
13889	VirtualBox Bridged Networking Driver error	Windows	VirtualBox 4.3.22	defect	2015-02-24T17:13:50Z	2017-02-24T06:32:40Z	2017-02-24T06:32:40Z	"Hi all!

If use Intel mainbord ethernet adapter and like setting VLAN - installed and ENABLED VirtualBox Bridged Networking Driver -, beyond possibility enabled status on for lan adapter.

If disabled VirtualBox Bridged Networking Driver in LAN adapter properties, work anyone.

(guest not running)"	Lacus
16484	Crash during guest OS startup	Windows	VirtualBox 5.1.14	defect	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
16434	Cannot resize VM Win7 on Win 10 Host	Windows	VirtualBox 5.1.14	defect	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
10317	Windows 8 Host: No network adapters after resume from sleep	Windows	VirtualBox 4.1.8	defect	2012-03-12T06:14:51Z	2017-01-26T05:07:15Z	2017-01-26T05:07:15Z	I am running Oracle VirtualBox 4.1.8 r75467 on a Thinkpad T510.  When I put my computer to sleep, the only way to get functioning NIC's on my host after resume is to go into device manager, uninstall the NIC and then scan for hardware changes to re-install the NIC.  I disabled the VirtualBox Bridged Network Driver on each NIC and I no longer have this problem.	Andrew
15565	Host adapter showing zero bytes traffic	Windows	VirtualBox 5.0.24	defect	2016-07-04T08:34:02Z	2017-01-25T09:26:28Z	2017-01-25T09:26:28Z	"On Windows 10 x64, I cannot get Microsoft Edge to connect to Virtual Box on the host adapter no matter what I try. (and I have researched this thoroughly on the web)

While trying to get the above working, I noticed that the host adapter shows 0 bytes of traffic, even though traffic is definitely passing through it.

My assumption is that there is something anomalistic with the host adapter on Windows 10, and I am hoping that it is this that is preventing Edge from accessing my guest OS.

For more info on this topic please see here:

https://forums.virtualbox.org/viewtopic.php?f=6&t=76805&sid=03dc09ac43bda2a553c78e31a5b89232&start=15
"	oivey
16358	USB MSD device BBB (bulk only) transfer fails due to CBW/CSW tag mismatch	Windows	VirtualBox 5.1.12	defect	2017-01-05T15:11:23Z	2017-01-07T15:46:29Z	2017-01-07T15:46:29Z	"Host is Windows 7, guest is OS/2 (eComStation, latest of everything).
I am using this set of USB drivers in the guest:
http://hobbes.nmsu.edu/download/pub/incoming/usbdrv213.zip

I have an ""Alcor Micro Corp."" USB stick (vendor id: 0x58F, product id:0x6387).
If I connect that device to the guest it is properly detected as a USB 2.0 device and I can access it in the guest. However, if I start some lengthy operation like a chkdsk.exe on the device, I eventually get a mismatch of the tag word in the sent out CBW block and the subsequently received CSW block (I have detected this by enabling tracing for USBMSD.ADD in OS/2 and looking at the trace output). At the point of failure, the CSW tag is off by 1 from the tag transferred in the corresponding CBW and it is equal to the CBW and CSW of the last (successful) transmission (as can be expected). If the tag is out of sync the USBMSD.ADD driver issues a MSD reset command and subsequently clears the input and output bulk pipes which of course is reported back to the OS as a transfer failure.

If I use the very same device under a native OS/2 installation with the very same set of USB drivers, I can successfully run the chkdsk.
To me it looks like that on a large number of BBB transfers (where I cannot give a hard and fast value for ""large""), that the USB virtualization eventually gets out of sync.

Let me know if you need any Virtualbox logs.




"	lerdmann
16282	Win7: Cannot start a virtual box machine	Windows	VirtualBox 5.1.10	defect	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
14145	Virtualbox installer does not ask for admin rights (UAC) automatically	Windows	VirtualBox 4.3.28	enhancement	2015-05-22T19:35:36Z	2016-11-22T23:16:27Z	2016-11-22T23:16:27Z	"Summary:

Since Virtualbox needs to install drivers, it always needs admin privileges. An installer can be compiled to require this, and many programs that need such privileges are (e.g. Networx, made by SoftPerfect).

Virtualbox is not. If a user has UAC at its default setting (enabled, one notch down from the top), as most people do, then at least in a Vbox upgrade scenario one must remember to run the installer ""as admin.""  If this isn't done, then the installation will still look like it worked, but Virtualbox's system drivers will likely not be installed (if you look at the drivers after the reboot -- e.g. vboxdrv.sys, vboxusb.sys, vboxusbmon.sys, etc -- they will not have been updated).

Proposal:

Virtualbox be made to force elevation upon a normal double click, thereby guaranteeing that this will not be a problem for the forgetful.

Note: I have not provided a log since this problem is one that's visible before setup begins to do anything more than show its initial screen. Also, this isn't specific to any particular version. It's been like this for any version for Windows that I can remember up through the current version."	rseiler
16157	Windows installer should add VirtualBox path to the PATH environment variable	Windows	VirtualBox 5.1.8	enhancement	2016-11-06T09:02:09Z	2016-11-06T09:02:09Z	2016-11-06T09:02:09Z	"I believe the title pretty much covers it, but in detail, installing !VirtualBox on a Windows host should modify the ""PATH"" environment variable to include the !VirtualBox installation directory as well (typically {{{""C:\Program Files\Oracle\VirtualBox""}}}).

Reason? One less step to issue ""VBoxManage"" commands, one less step to make a mistake. Plus, it's already there in the other hosts..."	Socratis
15838	download extension pack dialog displayed over upgrade extension pack dialog	Windows	VirtualBox 5.1.4	defect	2016-08-21T12:46:55Z	2016-10-19T20:55:59Z	2016-10-19T20:55:59Z	Under Win7, i just upgraded from VB 5.0.26 to 5.1.4, without opening VBox after the installation. After the upgrade was completed, i went on the 5.1.4 Extension Pack i had just downloaded, and double-clicked on it. The VBox GUI window was opened. Over it, an info dialog was displayed, saying that an older Extensions version is installed and asking if i wish to upgrade it. Over this dialog, another dialog appeared, informing me that a newer Extensions version exists and asking if i wish to download it. The last dialog was pointless since i was already trying to upgrade the Extensions Pack.	Wand
16077	Audio: When undocking a laptop, VirtualBox cannot switch to a different sound output	Windows	VirtualBox 5.0.26	defect	2016-10-18T13:56:43Z	2016-10-18T13:56:43Z	2016-10-18T13:56:43Z	"Host: Win10, VBox 5.0.26

Guest: Win10, x64

When undocking a laptop from a dock station, I expect VirtualBox to automatically switch to a different audio-out device. For example, WinAmp music player on native host does it correctly.

Sadly, VBox doesn't, which makes it impossible to use Skype or listening audio/video with docking station.

Steps to reproduce:
1. Start any music player or VoIP program in Windows (7 or 10) guest
2. Undock (unplug) laptop from docking station (which includes a separate USB Sound Blaster device)

Expected result:
Music should keep playing with max. 1 second audio drop

Actual result:
Music stops playing completely.

-Technologov, 18.10.2016."	Technologov
10057	clipboard integration not working for headless guest	Windows	VirtualBox 4.1.8	defect	2011-12-21T04:40:54Z	2016-10-10T21:37:11Z	2016-10-10T21:37:11Z	"I'm using v4.1.8, but I've noticed the problem with earlier versions, at least since 4.1.4.

I have a 64-bit Windows 7 host and both Windows XP and Linux VMs. The VMs are configured for bidirectional clipboards and those work as expected when the VMs are run from the VirtualBox GUI interface: I can copy text in a guest and paste it in the host and vice versa. When I run the same VMs using ""VBoxManage startvm <vm name> --headless"" and connect to them via the Windows RDP client, text copied in the guest not only is not available in the host's clipboard, it's not even available in the guest's.

The attached VBox.log shows clipboard-related errors from a headless Windows XP guest. The content copied during the logged session was text from a text editor (Notepad++) on the guest."	Evan Burkitt
16003	"Remove the ""Start after installation"" option from Windows installer"	Windows	VirtualBox 5.1.6	defect	2016-09-29T07:16:21Z	2016-10-07T15:30:29Z	2016-10-07T15:30:29Z	"It is becoming increasingly clearer that with Windows installers you have to install !VirtualBox with the ""Run as Administrator"" option after right-clicking on the installer. It is the only way to make sure that the drivers are installed as they should and are not rejected (silently sometimes) by Windows and UAC.

The problem is that if a simple user uses that tool, at the end of the installation when the installer offers to launch !VirtualBox, then !VirtualBox runs under the context not of the user that did the installation, but under the Administrator context. So if a user starts immediately to use !VirtualBox and creates a new VM, that VM won't be there next time the user re-launches !VirtualBox. It's going to be in the Administrator's account!

Solution: remove the ""Start after installation"" option at the end of the installation. The installer finishes and the user launches !VirtualBox under their own user context, as they would do it normally every other day.

PS. It doesn't have to be a simple user, driver installation fails sometimes even with an administrator user, so the ""Run as Administrator"" is becoming mandatory. Simply in that case the issue does not manifest itself."	Socratis
16036	supHardenedWinVerifyProcess failed with VERR_SUP_VP_REPLACE_VIRTUAL_MEMORY_FAILED	Windows	VirtualBox 5.1.6	defect	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
16033	Cannot attach hard drive to VM on 32-bit Windows 7	Windows	VirtualBox 5.1.6	defect	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
15968	Crashing VirtualBox	Windows	VirtualBox 5.1.6	defect	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
15882	Installer for VBox 5.1.4 doesn't honor non C: locations when creating shortcut	Windows	VirtualBox 5.1.4	defect	2016-09-03T17:18:27Z	2016-09-03T17:18:27Z	2016-09-03T17:18:27Z	"I install VirtualBox in G:\Program Files\Oracle\VirtualBox, not in the usual location, C:\Program Files\Oracle\VirtualBox. The ""Oracle VM VirtualBox"" shortcut is created to point to the nonexisting C:\Program Files\Oracle\VirtualBox\VirtualBox.exe, not G:\Program Files\Oracle\VirtualBox\VirtualBox.exe as I would prefer. This is new to 5.1.4. Manual intervention is required after installation. Note, this happened when upgrading from 5.1.2. Maybe the bug doesn't happen on a clean install."	trondfsi
1397	Feature request: Overcommitting of memory (swap in/out)	Windows	VirtualBox 1.5.6	enhancement	2008-04-08T13:32:45Z	2016-08-22T16:35:36Z	2016-08-22T16:35:36Z	I always get HostMemoryLow e.g. Knoppix 5.2. VMware and Microsoft Virtual PC work on this PC (IBM Thinkpad T40, 512 Mb RAM). I have enclosed the Logfile. How can I help?	IuK
15794	Can't install ReactOS	Windows	VirtualBox 5.1.2	defect	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
3972	OS/2 guest cannot write to floppy disk	Windows	VirtualBox 2.2.2	defect	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
15543	install path environment var not set	Windows	VirtualBox 5.0.22	defect	2016-06-22T14:56:42Z	2016-06-22T15:03:11Z	2016-06-22T15:03:11Z	"The VBOX_MSI_INSTALL_PATH environment variable is not set by the 5.0.22 installer.

Tried uninstalling/re-installing, running as administrator, rebooting. nothing helped

Uninstalling and reverting to the 5.0.20 installer set the env var as expected

Installation was on a brand new Windows 10 machine (build 10586.164)"	dansgeo
3974	OS/2 guest is limited to 1024x768x16777216 resolution	Windows	VirtualBox 2.2.2	defect	2009-05-08T23:53:12Z	2016-06-17T14:22:16Z	2016-06-17T14:22:16Z	"I have installed OS/2 ACP2 as a guest, and the virtual box OS/2 additions.
The maximum resolution I can select is 1024x768 in 24 bits. This is not much, especially if one wants to open many windows and use the VM for development. I have two monitors on my Vista host, a 24"" at 1920x1200, and a 30"" at 2560x1600 . I can use the full screen with my other guests (Solaris, Opensolaris, Win7). But with the OS/2 guest, I can only use a small portion of the screen. This is really limiting.

Even MS virtual PC supports a higher resolution (1600x1200) in the OS/2 guest. Unfortunately I can't use both Virtual PC and Virtual Box at the same time - it results in BSODs on the host. I have to choose one or the other.

While I realize the OS/2 guest will never have dynamic resolution support like the other hosts, I really wish you could offer some higher fixed resolutions for the guest, at least standard resolutions like 1280x1024, 1600x1200, 1920x1200, even if you don't go all the way to 2560x1600 .
"	Julien Pierre
15486	Cannot start VirtualBox.exe or VBoxSDL.exe because of ntdll.dll error.	Windows	VirtualBox 5.0.20	defect	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
15473	When started any virtual machine - VirtualBox crashes and pulls the machine down	Windows	VirtualBox 5.0.20	defect	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
15447	Win7 BSOD if DHCP server is On for Host-Only Ethernet Adapter	Windows	VirtualBox 5.0.20	defect	2016-05-26T13:22:57Z	2016-05-26T13:22:57Z	2016-05-26T13:22:57Z	"Host is Win7 Sp1, guest seems to be irrelevant: Linux 2.6, Ubuntu, Win7 - all fail with BSOD.
The BSOD happens only if I use Host-Only Adapter and check ""DHCP Server -> Enable Server"". Without the DHCP it works.
I've also tried with the legacy driver: VirtualBox-installer.exe -msiparams NETWORKTYPE=NDIS5 - same thing.
Attaching VBox.log and the picture of BSOD, though can't attach minidump because that is not saved for some reason."	wentwog
15347	RPC_S_SERVER_UNAVAILABLE when logging off host while VirtualBox.exe is running	Windows	VirtualBox 5.0.18	defect	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
15275	No host-only adapter	Windows	VirtualBox 4.3.12	defect	2016-03-26T06:37:27Z	2016-03-26T06:37:27Z	2016-03-26T06:37:27Z	"I have upgraded from windows7 to windows10 and my host-only adapter disappaered in Windows and virtualbox. 
I use virtualbox 4.3.12
"	louis14
15252	Application Error - Sudden crash	Windows	VirtualBox 5.0.16	defect	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
15242	cannot open VirtualBox imported any machine (Windows or Linux)	Windows	VirtualBox 5.0.16	defect	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
15234	Starting virutalbox causes ctrl, shift, alt and super key to stay pressed	Windows	VirtualBox 5.0.16	defect	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
15216	Guru Meditation after installing FreeDOS	Windows	VirtualBox 5.0.16	defect	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
14962	USB devices do not show up in VM	Windows	VirtualBox 5.0.12	defect	2015-12-22T13:22:00Z	2016-03-01T17:21:14Z	2016-03-01T17:21:14Z	"Host OS: Windows 8.1 x64
VirtualBox 5.0.12

When I try to attach a USB device into VM it seems to get ""stuck"" or locked. When I click Devices->USB->My device (USB flash stick), I see it disappearing in the host OS, but it never appears in the guest OS (checked via dmesg: no messages at all about any new USB attachments). When I open that USB submenu again and hover my device, the tooltip tells that it is now ""Captured"", but there is no checkbox near the device name (which would indicate that the USB device is attached to the guest), and when I run VBoxManage showvminfo, it tells that there are no currently attached USB devices.

If I try to click the same device again, I get the error message that the device ""is busy with a previous request"". If I remove the device physically and reinsert it into another USB port, it appears in the USB menu as a new instance (while the previous one, the ""Captured"", remains there as well). However, clicking this new instance leads to absolutely the same behaviour: the device disappears from the host, never appears in the guest and remains forever locked in the ""Captured"" state."	Konstantin Vlasov
13998	Windows 8 - VirtualBox Disables Wireless Display Support	Windows	VirtualBox 4.3.26	defect	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
15168	DOS batch file crashes on run attempt (Command Prompt Only) w98	Windows	VirtualBox 5.0.14	defect	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
9983	Virtualbox doesn't start on Windows 7 x64	Windows	VirtualBox 4.1.6	defect	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
14728	Virtualbox crash when closing laptop lid	Windows	VirtualBox 5.0.6	defect	2015-10-21T14:27:39Z	2016-01-25T16:51:46Z	2016-01-25T16:51:46Z	"I have been able to get the person who has this issue to work around it.

One of our guys has an issue where if you close his laptop lid with virtualbox running it crashes and the vm goes into aborted state.

Via our helpdesk:-

""The instruction at 0x69866f99 referenced memory at 0x00000000. The memory could not be read. Click on OK to terminate the program""

Does not go away when disabling 3d accelleration

"	lotsofjam
14007	Cannot Insert Linked Cloned Into Group	Windows	VirtualBox 4.3.26	defect	2015-03-29T20:05:41Z	2016-01-22T17:50:21Z	2016-01-22T17:50:21Z	"== Failed Scenario ==
Inserted a Base VM into a new Group[[BR]]
Created a snapshot while VM is off[[BR]]
Cloned the snapshot into a new Linked Clone[[BR]]
The linked clone appears on /VBOX main folder, and not under the Group folder[[BR]]
[[BR]]
Extra: Moving out of the group in Vbox UI and in again, or to another group and back, keeps it in the Main Vbox folder


== Workaround ==
Before cloning base VM, move it out of any group to main Vbox folder[[BR]]
Clone base VM[[BR]]
Move Base and Clone VMs into the group"	Zvika Dror Zend
7174	OS/2 Warp 4 Colors are wrong at 16 million setting	Windows	VirtualBox 3.2.6	defect	2010-07-15T00:41:30Z	2016-01-18T16:16:17Z	2016-01-18T16:16:17Z	Guest additions are working. When setting the resolution to 16 million colors, red and blue are reversed. Everything that is supposed to be blue, is red. Everything that is supposed to be red, is blue. Colors are right when using lower settings. 	Ron Schnatzmeyer
15013	Symbolic Links	Windows	VirtualBox 5.0.12	defect	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
15007	installing virtualbox on windows 10 version 1511 throws VERR_SHARING_VIOLATION	Windows	VirtualBox 5.0.12	defect	2016-01-05T04:59:25Z	2016-01-05T14:20:07Z	2016-01-05T14:20:07Z	so yea, just downloaded the latest version of virtualbox, and tried installing it, got the installer to run correctly only to try restarting the installer process from process explorer (due to installer not doing anything at all possibly due to windows issue yet to be discovered or pinpointed) and now upon the thing restarting, it throws that error, and no matter how many times I redownload the installer, it throws this error every time....even if I delete the file from all existance and redownload it, it still throws said error.	mmd123
14767	VirtualBox 5.0.8 causes Wireless Networks to Disappear	Windows	VirtualBox 5.0.8	defect	2015-10-30T11:18:18Z	2015-10-30T11:28:25Z	2015-10-30T11:28:25Z	"I installed VirtualBox 5.0.8 under Windows 10 Professional (x64), upgrading my system from 5.0.6.

Now, when I reboot, there is a red ""X"" in my wireless network connections on the login screen.  

When I login to my local desktop (Administrator account or user account with admin privileges) and click the Network Settings icon in the system tray, I get the message that there are no wireless networks.

I have to wait 2-3 minutes before they appear.  Once they do, then Windows 10 connects to them.  Sometimes it takes longer than 2-3 minutes.

I restored my machine to a Windows 10 image I had created prior to installing VirtualBox 5.0.8 and the problem has gone away.
"	Master VB Guru
14726	Remove option for Quick Launch shortcut from installer	Windows	VirtualBox 5.0.6	enhancement	2015-10-21T12:51:23Z	2015-10-21T13:01:43Z	2015-10-21T13:01:43Z	There should not be an option for a Quick Launch shortcut in the Windows installer. This feature was deprecated 6.5 years ago with the launch of Windows 7; then it took a settings change to bring it back. With Windows 10, it takes a registry hack to bring back this feature.	Aren Cambre
7094	VirtualBox kills network connectivity if VLAN tagging enabled on Realtek NIC	Windows	VirtualBox 3.2.6	defect	2010-06-30T23:46:16Z	2015-10-15T07:56:42Z	2015-10-15T07:56:42Z	"If VLAN tagging is enabled on the Realtek network card of a system with VirtualBox installed, and the ""VirtualBox Bridged Network Driver"" is bound to that network card (the default behavior), no network access is possible.  The only remedy is to either disable VLAN tagging or unbind the ""VirtualBox Bridged Network Driver"" and reboot the system.  The former is no remedy, because we use VLAN tagging (to the desktop) in our environment.  The latter remedy obviously means no network access for VirtualBox.  It would be nice if this issue could be fixed, as Microsoft HyperV does not suffer from this problem, and I'd much rather use VirtualBox.
{{{
Steps to reproduce:

1. Install the appropriate full Realtek NIC driver from http://www.realtek.com
/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false
2. Install VirtualBox on a system with a ""Realtek PCIe GBE Family Controller""
3. Open the Network Connection Control Panel
4. Right-click ""local Area Connection"" and choose ""Properties""
5. Click Configure
6. Click Advanced
7. Under the ""Propery:"" list, select ""Priority & VLAN"" then, under the ""Value:"" list, select ""Priority & VLAN Enabled""
8. Click Start --> All Programs --> Realtek --> Diagnostic Utility --> Realtek Ethernet Diagnostic Utility
9. Select ""Realtek PCIe GBE Family Controller"" from the list on the left
10 Click ""VLAN"" (from the middle column)
11. Click ""Add"" and enter a VLAN ID (for a VLAN that actually exists on your network) and press <ENTER>
12. Confirm adding of the VLAN and close the Realtek utility
13. Check to see if you still have network connectivity.  If you do, reboot.
14. You should not longer have network connectivity.
15. Open ""local Area Connection Properties""
16. Uncheck ""VirtualBox Bridged Network Driver"" and click ""OK"".  Reboot
17. Now you should have network connectivity.

This problem is happening on a system with the following characteristics;

- Windows 7 64-bit
- Realtek Realtek PCIe Gigabit Etherenet NIC
- Virtual Box 3.2.x
}}}"	viro
14614	Virtualbox kills keyboard when running on Windows 10	Windows	VirtualBox 5.0.4	defect	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
14603	"Installation fails on Windows 7 trying to access ""quick launch"" folder"	Windows	VirtualBox 5.0.4	defect	2015-09-16T23:55:50Z	2015-09-16T23:55:50Z	2015-09-16T23:55:50Z	"Our company employs a domain policy to direct each user's ""Application Data"" folder to a network share. Attempting to install VirtualBox 5.0.4 fails when attempting to access the ""Microsoft/Internet Explorer/Quick Launch"" sub-folder of ""Application Data"" because it resets network connections (thereby cutting off access to network shares) prior to accessing that folder. Upon failing to access the quick launch folder the installation fails (giving the user no option to continue even though the problem is minor) and rolls back the installation, leaving the existing host-only ethernet adapter drivers in a corrupted state.

I have tried the following steps to work around this problem:

1. Tell the installer not to add VirtualBox to the quick launch or start menu. (The installer ignores the user's request and still tries to access the quick launch folder)
2. Tell the installer not to install the network device drivers. (The installer resets network connections even though this is unnecessary)

Possible solutions to fix this problem:

1. Add VirtualBox to the Quick Launch and Start Menu (if the user requests it) *before* resetting network connections; or
2. After installing the network device drivers, ensure that network connections are properly re-established before attempting to access the Quick Launch and Start Menu folders; or
3. Give the user the option of continuing with the installation even if adding VirtualBox to the Quick Launch and Start Menu folders fails.

The same problem occurs when attempting to upgrade to version 4.3.30. I would really like to upgrade to a more recent version of VirtualBox (I'm stuck on 4.3.26) but I can't because I simply can't install any newer version.
"	srgerg
14452	Installing VirtualBox 5.0.2 blocks network on host (Windows 10)	Windows	VirtualBox 5.0.2	defect	2015-08-16T01:57:41Z	2015-09-14T12:59:20Z	2015-09-14T12:59:20Z	"I installed VirtualBox 5.0.2 on my host system which runs Windows 10.

It made my network fail.
The tray icons shows no error but trying to access a website does not work.
Restarting host does not help.

There are no errors in windows device manager. Both my network cards and VirtualBox's show.

Unintalling VirtualBox, immediately makes the network work again.

I have tried this on two computers with fresh windows 10 installs.

Both my computers have an intel network card.
One computer with ""Intel(R) Ethernet Connection (2) I218-V"",
and the other with ""Intel(R) Ethernet Connection I217-V"" (this computer also has a ""Killer e2200 Gigabit Ethernet Controller"").

"	spacebug
14582	Hostonlyif not fully initialized after create returns successful	Windows	VirtualBox 5.0.4	defect	2015-09-13T18:31:40Z	2015-09-14T04:14:39Z	2015-09-14T04:14:39Z	"When creating a new hostonlyif it appears that the adapter is not fully initialized when create returns success

Host OS - Windows 10 Build 10240
Virtual 5.0.4 - release and 5.0.5 102614

Example (note the garbage netmask returned)

{{{
vboxmanage hostonlyif create && vboxmanage list hostonlyifs
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interface 'VirtualBox Host-Only Ethernet Adapter #3' was successfully created
Name:            VirtualBox Host-Only Ethernet Adapter #3
GUID:            336f5edf-a838-43a1-a55f-7955e605ee59
DHCP:            Enabled
IPAddress:       192.168.56.1
NetworkMask:     15.0.0.0
IPV6Address:     fe80:0000:0000:0000:384b:5e06:3257:bdb1
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 0a:00:27:00:00:00
MediumType:      Ethernet
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #3

}}}

Here's the same example with ipconfig

{{{
vboxmanage hostonlyif create && ipconfig
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interface 'VirtualBox Host-Only Ethernet Adapter #3' was successfully created

Windows IP Configuration

Ethernet adapter VirtualBox Host-Only Network #3:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::8d8e:d529:1359:8373%22
   Default Gateway . . . . . . . . . :

}}}

If we wait ~5 seconds after creation and use list hostonlyifs we get the correct information

{{{
vboxmanage hostonlyif create && timeout 5 && vboxmanage list hostonlyifs
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interface 'VirtualBox Host-Only Ethernet Adapter #3' was successfully created

Waiting for 0 seconds, press a key to continue ...
Name:            VirtualBox Host-Only Ethernet Adapter #3
GUID:            c0b80be6-b9d2-499e-855b-b7043f26eec5
DHCP:            Enabled
IPAddress:       192.168.56.1
NetworkMask:     255.255.255.0
IPV6Address:     fe80:0000:0000:0000:a541:cd37:5679:1f0c
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 0a:00:27:00:00:00
MediumType:      Ethernet
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #3

}}}

This is big problem for tools like docker-machine,etc.
"	ronwilliams
14479	Virtual box hangs/crashes on VM rename	Windows	VirtualBox 5.0.0	defect	2015-08-20T23:38:06Z	2015-09-08T11:42:05Z	2015-09-08T11:42:05Z	"1) Make a new VM, called ""test""
2) Right-click VM > settings
3) Change name to be ""test (a:b)""
4) OK

An error will occur. On confirming the dialog, Virtual box will hang"	RoelV
7211	Captured mouse pointer is not released with Right-Control keypress on Windows when Canadian Multilingual Standard keyboard layout is active	Windows	VirtualBox 3.2.6	defect	2010-07-20T19:34:15Z	2015-08-27T16:01:32Z	2015-08-27T16:01:32Z	"Captured mouse pointer is not released with Right-Control keypress on Windows when Canadian Multilingual Standard keyboard layout is active

Reproduction steps:
 1. Use Windows control panel Regional Settings applet to add 'Canadian Multilingual Standard' keyboard layout and make it the default
 2. Start !VirtualBox
 3. Start a !VirtualBox guest OS which doesn't have Guess Additions installed
 4. Click in the guest window, observe mouse is captured
 5. Press Right-Control, observe that mouse is not released and remains captured.
"	Jon TURNEY
14504	VM VirtualBox crashes on Windows Server 2008 r2	Windows	VirtualBox 5.0.2	defect	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
11663	Host-only adapter slows down DNS resolution tremendously	Windows	VirtualBox 4.2.10	defect	2013-04-01T20:32:55Z	2015-08-13T16:45:38Z	2015-08-13T16:45:38Z	"I have tried VB 4.2.10 and 4.1.24 with the same result.

I recently compiled libcurl myself for a custom client. DNS resolution was awefully slow, around 5 to 10 seconds. After a [http://curl.haxx.se/mail/lib-2013-04/0007.html post] to the mailing list. I have figured out that when I disable the Host-only adapter, resolution screams again.

With host-only disabled:

{{{
D:\workspace-4.2\curlsimple\Debug>curlsimple.exe http://www.virtualbox.org
Provided URL: http://www.virtualbox.org
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   247  100   247    0     0    606      0 --:--:-- --:--:-- --:--:--   631
Name lookup time: 0.016000 s
Connect time: 0.187000 s
Pretransfer time: 0.016000 s
start transfer time: 0.188000 s
Total time: 0.407000 s
}}}

With host-only enabled:

{{{
D:\workspace-4.2\curlsimple\Debug>curlsimple.exe http://www.virtualbox.org
Provided URL: http://www.virtualbox.org
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   247  100   247    0     0     47      0  0:00:05  0:00:05 --:--:--    57
Name lookup time: 4.844000 s
Connect time: 0.188000 s
Pretransfer time: 0.000000 s
start transfer time: 0.187000 s
Total time: 5.219000 s
}}}

There must be something intercepting and blocking DNS resolution for some reason.

I am on Windows XP SP3, compiled libcurl 7.29.0 with mingw/gcc 4.7.2."	Michael-O
14274	BSoD in VBoxNetLwf with d1	Windows	VirtualBox 5.0.0	defect	2015-07-14T06:07:13Z	2015-07-31T11:58:40Z	2015-07-31T11:58:40Z	"'''Version:'''[[BR]]

VirtualBox 5.0.0-101573[[BR]]

'''Network Adapters:'''[[BR]]

RealTek Semiconductor RTL8168/8111 PCI-E Gigabit Ethernet NIC[[BR]]

VirtualBox Host-Only Ethernet Adapter[[BR]]

'''Minidump'''[[BR]]
{{{
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff880079c2007, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880042ab2a4, address which referenced memory

Debugging Details:
------------------

DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\nsiproxy.sys - file not found
DBGHELP: C:\Windows\System32\drivers\nsiproxy.sys - OK
DBGHELP: C:\Windows\System32\drivers\nsiproxy.sys found
DBGENG:  C:\Windows\System32\drivers\nsiproxy.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\mssmbios.sys - file not found
DBGHELP: C:\Windows\System32\drivers\mssmbios.sys - OK
DBGHELP: C:\Windows\System32\drivers\mssmbios.sys found
DBGENG:  C:\Windows\System32\drivers\mssmbios.sys - Mapped image memory
SYMSRV:  mssmbios.pdb from http://msdl.microsoft.com/download/symbols: 50755 bytes - copied         
DBGHELP: mssmbios - public symbols  
         f:\localsymbols\mssmbios.pdb\9ECFB21A2AD64292AB8AF8AB1B194C2E1\mssmbios.pdb
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\VBoxNetLwf.sys - file not found
DBGHELP: C:\Windows\System32\drivers\VBoxNetLwf.sys - OK
DBGHELP: C:\Windows\System32\drivers\VBoxNetLwf.sys found
DBGENG:  C:\Windows\System32\drivers\VBoxNetLwf.sys - Mapped image memory
SYMSRV:  f:\localsymbols\VBoxNetLwf.pdb\7E00272F27A1406CADE9A553C591E1CB1\VBoxNetLwf.pdb not found
SYMSRV:  http://msdl.microsoft.com/download/symbols/VBoxNetLwf.pdb/7E00272F27A1406CADE9A553C591E1CB1/VBoxNetLwf.pdb not found
DBGHELP: VBoxNetLwf.pdb - file not found
DBGHELP: F:\tinderbox\win-rel\out\win.amd64\release\obj\VBoxNetLwf\VBoxNetLwf.pdb - file not found
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for VBoxNetLwf.sys - 
DBGHELP: VBoxNetLwf - export symbols
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\VBoxNetAdp6.sys - file not found
DBGHELP: C:\Windows\System32\drivers\VBoxNetAdp6.sys - OK
DBGHELP: C:\Windows\System32\drivers\VBoxNetAdp6.sys found
DBGENG:  C:\Windows\System32\drivers\VBoxNetAdp6.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\ndis.sys - file not found
DBGHELP: C:\Windows\System32\drivers\ndis.sys - OK
DBGHELP: C:\Windows\System32\drivers\ndis.sys found
DBGENG:  C:\Windows\System32\drivers\ndis.sys - Mapped image memory
SYMSRV:  ndis.pdb from http://msdl.microsoft.com/download/symbols: 420783 bytes - copied         
DBGHELP: ndis - public symbols  
         f:\localsymbols\ndis.pdb\7F2704456B8949D6BD0D97D90F00DB912\ndis.pdb
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\Rt64win7.sys - file not found
DBGHELP: C:\Windows\System32\drivers\Rt64win7.sys - OK
DBGHELP: C:\Windows\System32\drivers\Rt64win7.sys found
DBGENG:  C:\Windows\System32\drivers\Rt64win7.sys - Mapped image memory
SYMSRV:  f:\localsymbols\rt64win7.pdb\CA0B16D985A346649CC5D6735331FF111\rt64win7.pdb not found
SYMSRV:  http://msdl.microsoft.com/download/symbols/rt64win7.pdb/CA0B16D985A346649CC5D6735331FF111/rt64win7.pdb not found
DBGHELP: rt64win7.pdb - file not found
DBGHELP: d:\svn\ndis_6\driver\src\src\sysw7x64\objfre_win7_amd64\amd64\rt64win7.pdb - file not found
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
DBGHELP: Rt64win7 - no symbols loaded
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\TDI.SYS - file not found
DBGHELP: C:\Windows\System32\drivers\tdi.sys - OK
DBGHELP: C:\Windows\System32\drivers\tdi.sys found
DBGENG:  C:\Windows\System32\drivers\tdi.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\afd.sys - file not found
DBGHELP: C:\Windows\System32\drivers\afd.sys - OK
DBGHELP: C:\Windows\System32\drivers\afd.sys found
DBGENG:  C:\Windows\System32\drivers\afd.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\WDFLDR.SYS - file not found
DBGHELP: C:\Windows\System32\drivers\WdfLdr.sys - OK
DBGHELP: C:\Windows\System32\drivers\WdfLdr.sys found
DBGENG:  C:\Windows\System32\drivers\WdfLdr.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\ACPI.sys - file not found
DBGHELP: C:\Windows\System32\drivers\acpi.sys - OK
DBGHELP: C:\Windows\System32\drivers\acpi.sys found
DBGENG:  C:\Windows\System32\drivers\acpi.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\tcpip.sys - file not found
DBGHELP: C:\Windows\System32\drivers\tcpip.sys - OK
DBGHELP: C:\Windows\System32\drivers\tcpip.sys found
DBGENG:  C:\Windows\System32\drivers\tcpip.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\vga.sys - file not found
DBGHELP: C:\Windows\System32\drivers\vga.sys - OK
DBGHELP: C:\Windows\System32\drivers\vga.sys found
DBGENG:  C:\Windows\System32\drivers\vga.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\VIDEOPRT.SYS - file not found
DBGHELP: C:\Windows\System32\drivers\videoprt.sys - OK
DBGHELP: C:\Windows\System32\drivers\videoprt.sys found
DBGENG:  C:\Windows\System32\drivers\videoprt.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\HIDPARSE.SYS - file not found
DBGHELP: C:\Windows\System32\drivers\hidparse.sys - OK
DBGHELP: C:\Windows\System32\drivers\hidparse.sys found
DBGENG:  C:\Windows\System32\drivers\hidparse.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\usbccgp.sys - file not found
DBGHELP: C:\Windows\System32\drivers\usbccgp.sys - OK
DBGHELP: C:\Windows\System32\drivers\usbccgp.sys found
DBGENG:  C:\Windows\System32\drivers\usbccgp.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\usbehci.sys - file not found
DBGHELP: C:\Windows\System32\drivers\usbehci.sys - OK
DBGHELP: C:\Windows\System32\drivers\usbehci.sys found
DBGENG:  C:\Windows\System32\drivers\usbehci.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\USBPORT.SYS - file not found
DBGHELP: C:\Windows\System32\drivers\usbport.sys - OK
DBGHELP: C:\Windows\System32\drivers\usbport.sys found
DBGENG:  C:\Windows\System32\drivers\usbport.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\umbus.sys - file not found
DBGHELP: C:\Windows\System32\drivers\umbus.sys - OK
DBGHELP: C:\Windows\System32\drivers\umbus.sys found
DBGENG:  C:\Windows\System32\drivers\umbus.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\usbhub.sys - file not found
DBGHELP: C:\Windows\System32\drivers\usbhub.sys - OK
DBGHELP: C:\Windows\System32\drivers\usbhub.sys found
DBGENG:  C:\Windows\System32\drivers\usbhub.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\watchdog.sys - file not found
DBGHELP: C:\Windows\System32\drivers\watchdog.sys - OK
DBGHELP: C:\Windows\System32\drivers\watchdog.sys found
DBGENG:  C:\Windows\System32\drivers\watchdog.sys - Mapped image memory
DBGHELP: C:\Windows\System32\win32k.sys - OK
DBGENG:  C:\Windows\System32\win32k.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\srv.sys - file not found
DBGHELP: C:\Windows\System32\drivers\srv.sys - OK
DBGHELP: C:\Windows\System32\drivers\srv.sys found
DBGENG:  C:\Windows\System32\drivers\srv.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\fltmgr.sys - file not found
DBGHELP: C:\Windows\System32\drivers\fltMgr.sys - OK
DBGHELP: C:\Windows\System32\drivers\fltMgr.sys found
DBGENG:  C:\Windows\System32\drivers\fltMgr.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\Ntfs.sys - file not found
DBGHELP: C:\Windows\System32\drivers\ntfs.sys - OK
DBGHELP: C:\Windows\System32\drivers\ntfs.sys found
DBGENG:  C:\Windows\System32\drivers\ntfs.sys - Mapped image memory

READ_ADDRESS:  fffff880079c2007 

CURRENT_IRQL:  2

FAULTING_IP: 
VBoxNetLwf+32a4
fffff880`042ab2a4 0fb64201        movzx   eax,byte ptr [rdx+1]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff880079c1460 -- (.trap 0xfffff880079c1460)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff880042ab2a4
rdx=fffff880079c2006 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880042ab2a4 rsp=fffff880079c15f0 rbp=fffff880042be4d8
 r8=0000000000000000  r9=fffff880042a8000 r10=0000000000000000
r11=fffff880079c1610 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
VBoxNetLwf+0x32a4:
fffff880`042ab2a4 0fb64201        movzx   eax,byte ptr [rdx+1] ds:4256:fffff880`079c2007=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c7fe69 to fffff80002c808c0

STACK_TEXT:  
fffff880`079c1318 fffff800`02c7fe69 : 00000000`0000000a fffff880`079c2007 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`079c1320 fffff800`02c7eae0 : fffff880`03572180 fffffa80`12a47b50 00000000`00000206 fffffa80`1c73f7a0 : nt!KiBugCheckDispatch+0x69
fffff880`079c1460 fffff880`042ab2a4 : fffffa80`1e81af50 00000000`000007ff fffffa80`1e81af50 fffffa80`1c73f670 : nt!KiPageFault+0x260
fffff880`079c15f0 fffff880`042ab72e : fffffa80`1ca55740 00000000`00000000 fffff880`042be4d8 fffffa80`1dbbb0e0 : VBoxNetLwf+0x32a4
fffff880`079c1690 fffff880`042abb78 : 00000000`00000000 00000000`00000000 fffffa80`1ca55740 fffff880`00000000 : VBoxNetLwf+0x372e
fffff880`079c1700 fffff880`01aac0a7 : 00000000`00000000 fffffa80`1c3491a0 00000000`00000000 00000000`00000000 : VBoxNetLwf+0x3b78
fffff880`079c1780 fffff880`05846cf4 : fffffa80`1c6ad000 fffffa80`1c6ad000 00000000`00000000 fffffa80`1c73f670 : ndis! ?? ::FNODOBFM::`string'+0xcd8f
fffff880`079c17d0 fffff880`058319c4 : fffffa80`1c349100 fffff880`05832c01 fffff880`0000000a fffff880`079c1a60 : Rt64win7+0x1bcf4
fffff880`079c19f0 fffff880`01b14542 : fffff880`00000000 fffffa80`1c3491a0 fffffa80`1c3491a0 fffffa80`00000000 : Rt64win7+0x69c4
fffff880`079c1a60 fffff880`01a9d56d : 00000000`00000002 00000000`0000000a 00000000`00000000 00000000`00000000 : ndis!ndisMiniportDpc+0xe2
fffff880`079c1ad0 fffff880`01ac3b7d : 00000000`00000002 00000000`00000002 00000000`00000000 fffffa80`1ca4ed78 : ndis!ndisQueuedMiniportDpcWorkItem+0xcd
fffff880`079c1b70 fffff800`02f1a456 : 00000000`27c49c63 fffffa80`3fae6b50 00000000`00000080 fffffa80`3fae6b50 : ndis!ndisReceiveWorkerThread+0x1bd
fffff880`079c1c00 fffff800`02c722c6 : fffff880`03500180 fffffa80`3fae6b50 fffffa80`1d67f6c0 00000000`ffffffff : nt!PspSystemThreadStartup+0x5a
fffff880`079c1c40 00000000`00000000 : fffff880`079c2000 fffff880`079bc000 fffff880`079c18c0 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
VBoxNetLwf+32a4
fffff880`042ab2a4 0fb64201        movzx   eax,byte ptr [rdx+1]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  VBoxNetLwf+32a4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: VBoxNetLwf

IMAGE_NAME:  VBoxNetLwf.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  559e4840

FAILURE_BUCKET_ID:  X64_0xD1_VBoxNetLwf+32a4

BUCKET_ID:  X64_0xD1_VBoxNetLwf+32a4

Followup: MachineOwner
---------
}}}"	bookevg
14354	"Simple Feature request: Please Change the ""Input"" Menue"	Windows	VirtualBox 5.0.0	enhancement	2015-07-31T08:32:15Z	2015-07-31T08:35:30Z	2015-07-31T08:35:30Z	"Hello

I have a german installation, therefore I try to translate the menue names...

The Window of a virtual machine has a menue:
File - Machine - View (or Display) - Input - Devices - Help

The ""Input"" Menue is unnecessarily nested and therefore the handling is (unnecessarily) intricate:

Input
 +- Keyboard
 |  +- Keyboard Configuration
 |  +- ----------------------
 |  +- Send Ctrl-Alt-Del
 |  +- Send Ctrl-Break
 |  +- Send Insert
 +- ----------------------
 +- Mouse-Pointer Integration


Because this Menue does not have many items, could your please change it for an easier and better usability to this Layout:

Input
 +- Keyboard Configuration
 +- Send Ctrl-Alt-Del
 +- Send Ctrl-Break
 +- Send Insert
 +- ----------------------
 +- Mouse-Pointer Integration

Thanks a lot in advance,
kind regards,
Tom"	Tom P
13235	Shutdown hangs in OS/2 guest	Windows	VirtualBox 4.3.14	defect	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
13234	Key repeating does not work in OS/2 guest	Windows	VirtualBox 4.3.14	defect	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
14112	BSoD in VBoxNetAdp6.sys with STOP 0x9F	Windows		defect	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
14197	can not install bridged interfaces on W7-64 Pro	Windows	VirtualBox 4.3.28	defect	2015-06-16T00:53:20Z	2015-06-28T00:38:11Z	2015-06-28T00:38:11Z	"Documented in this thread:

https://forums.virtualbox.org/viewtopic.php?f=6&t=68293&sid=bf442681877c87e603508a1aa2a0fb11

Hi there....readers digest. Dell replaced my M4800 laptop due to many different issues. The original is dual quad core intel core i7-4800MQ @ 2.7 Ghz, 8gb ram, 512mb hybrid drive, dual video processors Intel HD4600 and nVidia. Intel is default. Intel I217-LM ethernet adapter. Virtualbox installed normally but never got to run anything yet. 

new laptop is still a M4800 dual quad core I7-4810MQ @ 2.8 Ghz, 32gb ram, 512MB SSD + 512MB SATA drive. NVidia Quadro  K1100M is the other graphics processor. Same ethernet adapter.

I've attached a log from a failed attempt to install full product.

I need the bridged adapter.

Please help. If you need anything else, please let me know.

Thanks leon

"	Leon Zetekoff
3654	Bridged Networking does not find any adapters	Windows	VirtualBox 2.2.0	defect	2009-04-08T17:08:02Z	2015-06-10T20:15:06Z	2015-06-10T20:15:06Z	"When configuring a guest in version 2.2.0 under Windows Vista (I have x64, some others have reported with x32), under the bridged network configuration, the only selection for ""Bridged Network Adapter"" that I can choose is ""Not selected.""  This means that I cannot configure the network to work in bridged mode.  This has been reported on the forum: [http://forums.virtualbox.org/viewtopic.php?f=6&t=16202&start=0]."	brigad@rpi.edu
14164	Problem with installing VirtualBox on Windows 7	Windows	VirtualBox 4.3.28	defect	2015-06-02T08:04:01Z	2015-06-02T08:04:01Z	2015-06-02T08:04:01Z	"When I run the installer on my maschine (Windows 7 Enterprise), the installer seams to do what it is supposed to do. But when I afterwards try to start VirtualBox, the main windows of the programm is shown and almost immediately, it crushes down.
Please find the picture with the error screen and also the error text cutted out into a text file attached.
Solution for the problem is the following procedure:
The installer created a folder named "".VirtualBox"" under my user folder here on windows. As I compared some other installations from other maschines, in my new installation was one file missing named ""vbox-ssl-cacertificate.crt"". After adding this particular file to that folder, VirtualBox was able do run again.
Question: What is the problem for the installer that it fails to create this file during the installation routine?
I even ran the installation routine as admin and it didn't make any difference.
"	Jonas Bassl
3866	Host-only interface interferes with the current adapter	Windows	VirtualBox 2.2.2	defect	2009-04-29T03:21:22Z	2015-05-22T10:11:14Z	2015-05-22T10:11:14Z	When the host-only interface is installed, it '''suddenly''' screws up the connection for the physical adapter. The adapter says it is identifying the network when it is connected to it already.	Frank
14115	4.3.28 installation failed	Windows	VirtualBox 4.3.28	defect	2015-05-14T19:55:06Z	2015-05-21T09:05:49Z	2015-05-21T09:05:49Z	"Hi,
I tried to install 4.3.28 but I had a bluescreen during installation saying DPC_WATCHDOG_VIOLATION.
I tried after to install the 4.3.26 again and it failed.
I tried to do all sorts of fix found on your forums but nothing worked.
I link to this bug report a log of the last installation I tried"	Josk
14127	No bridged network adapter is currently selected	Windows	VirtualBox 4.3.26	defect	2015-05-17T02:22:10Z	2015-05-17T06:51:23Z	2015-05-17T06:51:23Z	"Windows 7, 64 bit., VirtualBox 4.3.26.

When adding a bridged network adapter to any virtual machine while running virtual box as normal user, the selection for network interfaces is empty. It also states: ""No bridged network adapter is currently selected"":

[[Image(bridge-empty.png)]]

When I run VirtualBox as admin, it works as expected.

The VirtualBox networking driver is setup and installed properly and is enabled for all network interfaces. Example shown here:

[[Image(vbox_driver_interface.png)]]

I found some references to exactly this kind of issue but it seems that the problem is something different in my case because all the workarounds did not work, including:

* Reinstallation of VirtualBox, rebooting, ...
* Delete HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\Config, reboot, re-install VirtualBox
* Set a higher value to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\MaxNumFilters (I Use 0x20), reboot, reinstall etc.

"	divB
14110	GUI anomalies on VHD display Windows 8.1	Windows	VirtualBox 4.3.26	enhancement	2015-05-12T10:01:42Z	2015-05-12T10:01:42Z	2015-05-12T10:01:42Z	Some of the list items in the Vbox GUI are malformed @ 3200x1800 resolution on a 16:9 monitor of Dell XPS13 (2015)	Wille
11712	Install Makes Windows 8 Host Boot Fail	Windows	VirtualBox 4.2.12	defect	2013-04-15T00:12:55Z	2015-04-09T12:31:56Z	2015-04-09T12:31:56Z	"This is bug: When I run the Virtualbox 4.2.12 install with its default settings, Windows will not finish booting on the next start up. I'll leave it try to boot for a while, kill the power, start it up and repeat until the Windows 8 auto recovery kicks in. Windows 8 will do a system restore t the point just before installing Virtualbox. Virtualbox will no longer be installed and the system will reboot  and operate normally. I ran the whole install Virtualbox, system repair cycle several times to confirm nothing else I did was tied to the problem. I eventually installed Virtualbox by not installing anything that looked like it was related to networking. With that install configuration Windows booted properly several times. I ran several clients in Virtualbox and they all were able to connect to the internet.

Machine Information: I am running Windows 8 x64 as my host. It is not an upgrade. I did a fresh install from CD, though I have since installed numerous other items. The laptop runs an AMD A8-4500, has 16 GB of RAM, and a sizable SSD. Because I develop for windows phone, I have hyper-v enabled and it has several network adapters setup. I use Virtualbox because hyper-v is inadequate for some things, so I have to have them both concurrently. I had previously used them concurrently without issue, but then I kept running into wireless networking issues (no internet access over WI-FI) definitively caused by Virtualbox somehow. As such I had no choice but to uninstall Virtualbox (though Windows seemed not to remove all of the settings related to Virtualbox's network adapter) and to start using hyper-v in its place.  Hyper-v was inadequate in some regards, so I installed Virtualbox 4.2.12 and got the above bug.

If I can help fix this issue or provide any useful information, even if it means retesting that whole mess installing nightly builds or anything else, please let me know as I am more than happy to help! I can be contacted directly if needed at [reportedbyname] {A T} [gmail address]"	jmessenger235
13875	Uninstaller doesnt remove all drivers	Windows	VirtualBox 4.3.22	defect	2015-02-21T11:30:57Z	2015-02-21T11:30:57Z	2015-02-21T11:30:57Z	"Hello,

The VirtualBox uninstaller on Windows does not remove the following drivers even after multiple reboots:

VirtualBox Host-Only Ethernet Adapter: 
\SystemRoot\system32\DRIVERS\VBoxNetAdp.sys

VirtualBox Bridged Networking Service: 
\SystemRoot\system32\DRIVERS\VBoxNetFlt.sys

This has the added effect of showing these devices to end-users when calling GetAdaptersAddresses and specifying the GAA_FLAG_INCLUDE_ALL_INTERFACES flag.

The uninstaller should add these drivers to the PendingFileRenameOperations registry key allowing Windows to remove them on system restart."	dmex04
13851	Linked clone not created in group subdirectory	Windows	VirtualBox 4.3.20	defect	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
12780	VBoxSVC.exe crashes on Windows with VBox 4.3.8 when setting VBOX_USER_HOME	Windows	VirtualBox 4.3.8	defect	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
12487	Disable ICH9 Chipset for NetWare Guests	Windows	VirtualBox 4.3.4	enhancement	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
12403	Feature Request - Mount VDI as Windows Drive	Windows	VirtualBox 4.3.2	enhancement	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
6057	[feature-request] Installer: warn users for incompatible drivers on Windows host	Windows	VirtualBox 3.1.2	enhancement	2010-01-22T10:11:14Z	2013-08-21T20:53:02Z	2013-08-21T20:53:02Z	"
I see there are some instances where vboxdrv or vboxnetflt drivers are incompatible with currently installed 3rd party drivers on Windows Host platform.

It would be better, especially for newbie users, if we detect such incompatibilities in our installer, and warn users.

Here is the known list: (and perhaps a few more that I overlook)

#3752 DNS protocol problem with Vista hosts => check Shrew Soft Lightweight filter rules

#5519 vboxnetflt: fatal BSOD installation on Marvell Server NIC

#3370 VBoxNetFlt: Conflict with the Trend Micro Anti-Virus driver

#3724 Host crash: vboxdrv crashes, when run together with coLinux

Other incompatible software:

-decndis.sys caused the crash on one user. decndis is part of the DEC (Digital Equipment Corp) LAT protocol that we use to access the VAX (reported by Huihong Luo of VMlite)

-Microsoft VirtualPC

-Microsoft Hyper-V

The same issues applies to Linux-host installer too, but since installers are platform-specific, it deserves a separate wish.

-Technologov, 22.1.2010"	Technologov
11338	OS/2 VBOXSERVICE.EXE 4.2.6 not working	Windows	VirtualBox 4.2.6	defect	2012-12-28T23:46:59Z	2013-03-27T23:13:02Z	2013-03-27T23:13:02Z	The guest additions for os/2 appear to be updated for 4.2.6 however they are not mentioned in the changelog.  When using VBOXSERVICE.EXE in os/2 (4.2.6 r82870 Dec 19 2012 15:02:33) my os/2 guest crashes with a TRAP 000d error.  I reverted VBOXSERVICE to 4.2.2 (r81494 Oct 18) and the guest is working again.	walter380
10996	Parallel port interrupts can not be used	Windows	VirtualBox 4.2.0	defect	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
5252	Intel vt-d/AMD IOMMU support	Windows	VirtualBox 3.0.8	enhancement	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
6358	Add official support for running as a service	Windows	VirtualBox 3.1.4	defect	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
9776	When using pause the gray out effect isn' working when running a 3D accelerated desktop (3D acceleration on) like Unity in Ubuntu	Windows	VirtualBox 4.1.4	defect	2011-10-17T13:07:28Z	2012-02-12T03:57:18Z	2012-02-12T03:57:18Z	"When using pause the gray out effect isn' working when running a 3D accelerated desktop (3D acceleration on) like Unity in Ubuntu

VirtualBox 4.1.4 

Guest Additions 4.1.4 installed 

Ubuntu 11.04 Up-to-date no extra packages other than the guest additions from the guest additions .iso installed.
 
ATI Mobility Radeon HD 5470 (Driver version 11.9) 

Windows 7 Home Premium 64-bit Intel VT-x enabled Core i3 proccessor (4 cores cores reported, I think it's 2 hyperthreaded to 4)
 
1 GB ram allocated to guest 2 CPU Guest SMP 8GB .vdi 
"	temp4746
7891	VBox doens't handle the user account correctly on Windows Hosts	Windows	VirtualBox 3.2.12	defect	2010-12-23T10:37:26Z	2012-01-10T23:47:17Z	2012-01-10T23:47:17Z	"Host : Windows 7 Pro 64 bits

Context : VBox is called by a PowerShell script. At development time, this script is run by me, manually. At production time, this script is run by a scheduled task or through an ASP.Net web interface.

I wrote a little PowerShell script to illustrate the defect:

{{{
""Windows 1: $([Environment]::UserDomainName)\$([Environment]::UserName)"" | Out-File ""out.txt""
""Windows 2: $([Security.Principal.WindowsIdentity]::GetCurrent().Name)"" | Out-File ""out.txt"" -Append

$vBox = New-Object -ComObject VirtualBox.VirtualBox
""VirtualBox: $($vBox.HomeFolder)"" | Out-File ""out.txt"" -Append
}}}

If the script is run manually by me, the result is:
{{{
Windows 1: <my domain>\robot
Windows 2: <my domain>\robot
VirtualBox: C:\Users\robot/.VirtualBox
}}}

To me, this is the CORRECT result.

If the script is called through the computer ASP.Net web interface, the result is:
{{{
Windows 1: <my domain>\robot
Windows 2: <my domain>\robot
VirtualBox: C:\Windows\system32\config\systemprofile/.VirtualBox
}}}

Here, the ASP.Net engine is setup with impersonation to enforce the user with the ""robot"", as shown with the 2 first lines, this works, so the VBox result is WRONG.

If the script is run through a scheduled task, the result is:
{{{
Windows 1: <my domain>\Robot
Windows 2: <my domain>\Robot
VirtualBox: 
}}}

Here again, the scheduled tasks enforces the user account to ""robot"", so here again, the VBox result is also WRONG.

I've found a tricky workaround to run from the web interface by backuping/copying VBox files from/to the robot/systemprofile accounts, so yes, really tricky.

For the scheduled task, as VBox returns nothing, I have no solution, until to hope to see this defect fixed.

Thanks."	Romuald Tisserand
9808	Cannot delete snapshot due to hidden differencing image	Windows	VirtualBox 4.1.4	defect	2011-10-25T08:40:44Z	2011-12-08T12:20:07Z	2011-12-08T12:20:07Z	"Fairly regularly, I find that when I try to delete a snapshot, the VBM (VBox Manager) reports that it cannot because there is more than one child hard disk.  However, the VBM does not show any indication of its existence in the snapshot hierarchy.  I can only see the extra disk in the VMM (VMedia Manager), where I can delete it and then successfully delete the snapshot from the VBM.

However, that the VBM and VMM disagree about the disk/differencing hierarchy must be a bug, right?

In all of the situations where this has occurred, I have done nothing more complex than periodically create snapshots and periodically delete them.  The disks are not shared across machines and I've not cloned any machines.  Unfortunately, it's not reproducible, it just occasionally happens.  I've come across this problem on 2 different hosts with 4.1.4.  I think I've seen it in earlier versions too."	simon marshall
9992	"Close button for ""already latest version"" window does not work"	Windows	VirtualBox 4.1.6	defect	2011-12-05T15:11:43Z	2011-12-05T15:11:43Z	2011-12-05T15:11:43Z	"The built-in close button for the ""you are already running the latest version"" window does not work. Nothing happens when I press the button. See attached screenshot.

The OK button works just fine (closes the window)."	Oskar
8649	[feature-request] VBox Windows Installer should check for python version	Windows	VirtualBox 4.0.4	enhancement	2011-03-29T06:57:13Z	2011-11-08T02:02:44Z	2011-11-08T02:02:44Z	"Host: Windows (all), VBox 4.0.4

VBox currently installs python bindings even on buggy python modules. (python 2.5.1 and pywin32 v213)

1. in ""vboxshell.py"" terminal colors on Windows Vista/7 must be disabled by default, and it is a known python bug, checking for python version fixes garbage on those platforms

2. We must check for pywin32 version. v213 is known to be broken. This fixes VBox bug #8605

We should refuse to install python bindings (gray out this option, or gives warning message), if python modules are old.

-Technologov, 29.3.2011."	Technologov
4753	ost-only network adapters settings change after reinstall	Windows	VirtualBox 4.1.4	defect	2009-08-11T15:32:38Z	2011-10-21T05:30:43Z	2011-10-21T05:30:43Z	"Every time I reinstall (mostly when updating to a new version) VirtualBox, my host-only network adapter settings are changed... I found out about this when the internet in the guests stopped working. The first time it took me a while to discover that the problem was on the changed settings, I never though they would be different for any reason.

The host-only settings for each adapter has two tabs, ""Adapter"" and ""DHCP Server"".

Since I have the DHCP Server disabled, I don't know if it happens to those settings. But for the Adapter, I change the IP and Network Mask to match my needs and every time I update (last time was 3.0.2 -> 3.0.4), those settings are reset to the default values and because of that, my network connection stops working in the guests because it can't find the Adapter IP I specified.

Don't you agree that any settings for custom configurations shouldn't be changed when the user re-installs or upgrades to a new version? I mean, I changed the settings for a reason, I'm not expecting them to change unless I explicitly change them."	Nazgulled
9792	Parent VM Still reports being parent of deleted VMs	Windows	VirtualBox 4.1.4	defect	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
9744	Cancelling out of VM creation deletes entire mount point / junction	Windows	VirtualBox 4.1.4	defect	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
9541	VirtualBox GUI does not support Windows 7 Jump Lists for recent machines.	Windows	VirtualBox 4.1.2	enhancement	2011-08-31T12:57:41Z	2011-08-31T12:57:41Z	2011-08-31T12:57:41Z	"Following on from a 2010 forum post http://forums.virtualbox.org/viewtopic.php?f=8&t=28017, this ticket is for the implementation of Windows 7 jumplists. 
As suggested in the forum posting, implementing a SHAddToRecentDocs call (from Shlobj.h) when Virtual Machines are started (or opened) on Windows XP and above should allow basic jumplist functionality."	Adam
5477	Mini toolbar option in GUI is confusing and inconsistent with Shared Clipboard option	Windows	VirtualBox 3.0.10	defect	2009-11-16T16:28:10Z	2011-08-18T05:36:42Z	2011-08-18T05:36:42Z	"Hi,
using VirtualBox 3.0.10 on Windows XP host. On General section on Advanced tab there are two settings: ""Shared Clipboard"" and ""Mini Toolbar"". Both of them are solving same type of problem, but there are solved very differently using GUI options, which can be very confusing, specially for new user.

I suggest to implement ""Mini ToolBar"" option like ""Shared Clipboard"" option and that is create drop down menu with three options: ""Disable"", ""Show At Top Of Screen"" and ""Show At Bottom of Screen"".

This kind of solving the same type of problem would make GUI tool more user friendly especially for new users.
Regards"	grof
8893	FATAL: Int13_diskette_function: read error	Windows	VirtualBox 4.0.6	defect	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
9385	"""Create a snapshot of the current state"" is not remembered when restoring snapshots"	Windows	VirtualBox 4.1.0	enhancement	2011-08-05T18:17:26Z	2011-08-05T18:17:26Z	2011-08-05T18:17:26Z	"Not using the English version so terminology may be slightly off.

Starting with 4.1.0 when you try to restore an snapshot and the current state is modified, the GUI asks if you want to snapshot the current state. But that checkbox is always marked by default and doesn't remember when you uncheck it, so you have to uncheck it every time.

Other checkboxes, such as the one about restoring the last snapshot when you force-power-down a machine, do remember their state."	jmausr
9344	Snaphot deletion status window	Windows	VirtualBox 4.0.12	enhancement	2011-07-29T15:54:47Z	2011-07-29T15:54:47Z	2011-07-29T15:54:47Z	"When you delete a snapshot, VB helpfully puts up a status window titled:
{{{
Machine: Deleting snapshot 'earlier':
}}}
Unfortunately the contents is:
{{{
Merging differencing image '{gah-internal-uid}'
}}}
Apart from the UID being fairly useless to the average user, it is also something that is not shown in the GUI itself, as the GUI only lists snapshot names.  So the average user has no idea what the UID is, or what it relates to.  The status window should use the snapshot name or some such.  

For example, if the snapshot following is called 'later', then:
{{{
Merging into snapshot 'later'
}}}
and if there is no later snapshot, then:
{{{
Merging into current state
}}}
"	simon marshall
3351	Normalise or repair the XML data models	Windows	VirtualBox 2.1.2	enhancement	2009-02-16T14:19:01Z	2011-06-23T00:16:25Z	2011-06-23T00:16:25Z	"Currently the VBox metadata models are denormalised in that data elements are duplicated between the central ''!VirtualBox.xml'' registry and the various machine.xml files.  The VBox application does not enforce proper transactional integrity between these various definition files and so various program errors can cause them to get out of sync.  A result of this is that VBox will then refuse to load the VM and the users are unable to recover the contents of any snapshotted HDs with understanding the XML schemas and manually patching up the XML files — not something that the average use is capable of doing.  Hence certain classes of VBox error can result in major data loss for most users.  There is sufficient volume of posts on the forum related to this issue to support the conclusion that this is a real problem.

As far as I can see there are three possible approaches to remove this product vulnerability:
 * '''Renormalise the data models'''.  For example the ''<!MediaRegistry><!HardDisks>'' tree would only contain HDs that are not allocated to VMs.  The complete set of ''<!HardDisks>'' could be obtained by enumerating this tree plus the ''<!HardDisks>'' in each attached machine.  (This node would replace the existing ''<!HardDiskAttachments>'' node).  Such an approach would also mean that a VM is now a self-contained entity that can be exported or imported (a frequent user request).  Yes this would require addition integrity checks to walk the VMs XML files when adding or removing HDs, but this is hardly a frequent occurrence.  This is my recommended option.
 * '''Provide a repair too'''.  This would walk the various XML files, identify inconsistencies and have a set of rules for when to recommend recovery and when to ask the user for a choice.
 * '''Move the meta data to a proper DB'''.  The obvious one to use here is SQLlite: simple, free, and able to handle the transactional issues.  Under this scenario the Machine schema would only be used for importing and exporting machines.
This metadata is critical to the protecting the user content maintained within the various VMs, yet there are no transactional, journalling or recovery mechanisms provided to ensure the integrity of this metadata.  This is unacceptable in product of VBox's maturity."	Terry Ellison
8606	Files remain installed and locked by Windows after uninstall or upgrade	Windows	VirtualBox 4.0.4	defect	2011-03-21T20:32:27Z	2011-05-17T18:24:20Z	2011-05-17T18:24:20Z	Upon upgrading from v4.0.2 to 4.0.4 I was unable to launch any VMs. I discovered that vboxdrv.sys, vboxnetadp.sys and vboxusbmon.sys were still from v4.0.2 and one of them was locked. Upon rebooting the machine and manually removing the files I was able to install 4.0.4 successfully.	Patrick Headley
8855	"Windows XP netcard doesnt work with ""VirtualBox Bridged network driver"" enabled"	Windows	VirtualBox 4.0.6	defect	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
8828	Back button in program installer doesn't work	Windows	VirtualBox 4.0.6	defect	2011-05-03T05:17:22Z	2011-05-03T05:17:22Z	2011-05-03T05:17:22Z	"This is while installing the software on WINDOWS (not sure about other systems) When you get to the last screen on ""Oracle VM VirtualBox 4.0.6 Setup"", the back button does nothing."	Jimmy
4682	"Remove ""Create Quick Launch Icon"" from installer on Windows 7 and above"	Windows	VirtualBox 3.0.4	enhancement	2009-08-05T09:31:40Z	2011-03-01T08:52:41Z	2011-03-01T08:52:41Z	"Since ""Quick Launch"" has been removed from Windows 7 and is unlikely to return in future builds of Windows, creating a quick launch icon should not be offered on Windows 7 an above. This is merely a cosmetic issue as this option has no effect on Windows 7 but should be fixed eventually."	Frank Freibuth
8048	Restless Guest window's preview	Windows	VirtualBox 4.0.0	enhancement	2011-01-10T06:18:14Z	2011-01-27T06:17:17Z	2011-01-27T06:17:17Z	"I noticed that the preview gets continuously updated while a VM is running,
which can be quite useless and CPU consuming.

I saw the preview can be disabled, but doing so involves loosing the possibility of seeing the last screen of a saved VM in the VirtualBox Manager.

I searched the manual looking for a way to '''have the preview updated only when closing down a VM''', but I did not find anything."	marcox
8148	Guest pre-boot check cycle of .vmdks with raw disks does not detect mismatch in drive geometry	Windows	VirtualBox 4.0.2	enhancement	2011-01-22T15:39:56Z	2011-01-22T15:39:56Z	2011-01-22T15:39:56Z	"Hi! :)

I asked a question about this on the forums (http://forums.virtualbox.org/viewtopic.php?f=6&t=38285&start=0), and then did some testing to try to satisfy my concerns.

Issue at hand: If I have set up my VBox guest on a Windows host to access disks using raw device .vmdks, what will happen when I add a new controller, change BIOS drive order, remove a drive, or similar, which would cause Windows' \.\PhysicalDriveX links to point to physical devices different to what has been described in the .vmdks. E.g. that a 2TB physical disk is referenced to by a .vmdk describing the geometries of the 1TB disk that used to be at that PhysicalDriveX path.

<Copy/paste from my post in the forums>
First test:
I picked out two .vmdks, one pointing at a 1TB drive, the other pointing at a 2TB drive. I then switched them around, i.e. renamed them.

The ""Storage"" list in the main manager window did not pick up on this change. It still listed the ""old"" settings, i.e. the sizes for the previously corresponding \.\PhysicalDrive targets. However, upon booting, the OS report I/O errors on the drives in question.

This suggests that VB kept the geometry info from when the drives were attached, but read in the new \.\PhysicalDrive paths. Not good. Had I set up md and zfs already, I'm guessing this would not have been good for my data.

Second test:
I edited the two .vmdks to switch around physical drives.

Again, there's no update in sizes in the ""Storage"" list, and again, booting results in ""Buffer I/O error"" messages in logs and TTYs. No warning from VB.
</Copy/paste from my post in the forums>

With these raw disk .vmdks, VBox is spending quite a bit of time doing its checks before booting a VM the first time. I believe this time should also be spent comparing the geometries registered in the .vmdk with the actual, current, geometries of each drive, and when finding a mismatch either aborting (seems sane) the process with an error, or at least warning the user and blocking the boot until the user has determined what to do.

The way it works now, a broken power line to a drive could cause complete reordering of a list of drives upon reboot (possibly initiated automatically by the BIOS subsequent to a crash on behalf of the failing drive). If the VM is set to automatically boot, and ignores the discrepancies in geometries, you might find yourself starting RAID systems or ZFS pools on drives that have bad geometries and will I/O error out on everything, possibly causing severe data corruption.
"	Daniel Smedegaard Buus
7843	"VBox host-only network is reported as ""Unidentified Network"" and Public on Windows7 hosts"	Windows	VirtualBox 3.2.12	defect	2010-12-14T01:28:54Z	2010-12-14T01:28:54Z	2010-12-14T01:28:54Z	"I am configuring virtual machines that are using the host-only network interface to connect to the host machine.

My host OS is Windows 7 and its firewall operates by classifying which network adapters and networks are public vs. work/home.  Based on this classification, the firewall determines which interfaces allow service connections (e.g. cifs, http, etc.) and which interfaces do not.

The host-only network interface cannot be modified to change the network name nor network access type in the Windows ""Network and Sharing Center""  If I click on the network type (Work, home, public) of any other adapter, a dialog comes up that allows me to change the type and name.  If I click on the bench of the vbox host-only iface, then I get an immutable dialog that shows me a read-only textfield and no capability to change the network type.

Please fix this.  I do not want to install 3rd party firewall software, nor do I want to needlessly expose my box to public-network elements when I need VM guests to connect to my host.  A host-only network is arguably more ""private"" than a ""public network"""	Perry
7791	If disk images are on a shared storage(eg. samba), clients crashes if there is networking error.	Windows	VirtualBox 3.2.12	defect	2010-12-04T16:37:19Z	2010-12-06T15:51:50Z	2010-12-06T15:51:50Z	"I keep all disk images in a samba share, and sometimes, If there is network problem, The guests fail constantly, Even if the share which contains disk images offline and go back within in a second, The guest fails(both windows and linux) still. Asked in #vbox channel, And finally the conclusion might be:

00:13 < lacqui> But honestly, the issue is that VBox is attempting to access a file that it assumes is constantly available
00:13 < lacqui> When there are network issues, that may no longer be the case.
00:13 < lacqui> VBox has the file open constantly.
00:13 < lacqui> I beleive that file pointers may be lost (on the OS level); I don't know if there is an application-level method of bypassing that
00:14 < xinming> Since the samba share returns again really soon, So I believe there may be a work around to detect this, and re-open the file.

Possible to fix this?
Or if this won't be fixed, Is there a way to prevent this situation please?

Thanks!
"	yiyihu
7646	Keyboard and mouseclick disabled at windows host with 'view login sceen at resume'	Windows	VirtualBox 3.2.10	defect	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
7546	Print Screen does not work on Windows XP if Virtual Box has Focus	Windows	VirtualBox 3.2.8	defect	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
1752	Software Installation not passed Windows Logo testing	Windows	VirtualBox 1.6.2	defect	2008-06-20T18:34:53Z	2010-10-05T22:06:06Z	2010-10-05T22:06:06Z	"During installation a dialog box appears warning that:

""The software you are installing has not passed the Windows Logo testing to verify its compatibility with Windows XP.  (Tell me why this is important)

Continuing your installation of this software may impair or destabilize the correct operation of your system either immediately or in the future.  Microsoft strongly recommends that you stop this installation now and contact the software vendor for software that has passed Windows Logo testing""

Some users may take Microsoft's strong advice and not install VirtualBox."	Jerry Waldorf
3461	Settings saved in wrong place (WinXP)	Windows	VirtualBox 2.1.4	enhancement	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
7083	character encoding munged in CLI on Windows	Windows	VirtualBox 3.2.6	defect	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
6917	Feature request: Prevent guest resolution auto adjust	Windows	VirtualBox 3.2.2	enhancement	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
4934	Cannot start VM bridged to a VLANs when another VM bridged to another VLAN is already running	Windows	VirtualBox 3.0.4	defect	2009-09-09T08:12:04Z	2010-05-24T12:31:28Z	2010-05-24T12:31:28Z	"Cannot start VM bridged to a VLANs when another VM bridged to another VLAN is already running.

Windows Vista Business 64bit host SP2

I have 3 VLANs on an Intel PRO/1000 MT Desktop Adapter lan card.
I have installed the Intel Proset drivers for the NIC v14.3
They enable me to have each VLAN with its own virtual NIC in the form of for example: Intel(R) PRO/1000 MT Desktop Adapter - VLAN : VLAN2018 (The only way to use VLAN in Windows I know of)
If I start a virtual machine bridged to one of the Virtual VLAN NICs it is OK, everything is working
I can also start more virtual machines bridged to the same Virtual VLAN NIC
But the problem is when I try to start a virtual machine bridged to a different Virtual VLAN NIC,
 while those VMs bridged to first Virtual VLAN NIC are still running.

I get a crash with message: VERR_INTNET_INCOMPATIBLE_TRUNK

I tried Virtual Box version 2.2.4-47978 and also latest beta 3.0.6_BETA1-51790 still the same
The only difference is that 2.2.4 locks up hard after a couple of VLAN crashes and I need to reboot my host.

For example:
start VM1 bridged to VLAN1 - OK
start VM2 bridged to VLAN1 - OK
start VM3 bridged to VLAN2 - CRASH!!!

Other example:
start VM1 bridged to VLAN1 - OK
start VM2 bridged to VLAN1 - OK
stop VM1 and VM2
start VM3 bridged to VLAN2 - OK
"	Boris
6547	"Cancelling ""Add host-only network"" causes ""Unknown device"" to be created."	Windows	VirtualBox 3.1.6	defect	2010-04-18T12:06:27Z	2010-04-19T10:08:34Z	2010-04-19T10:08:34Z	"How to duplicate:

 * Click File->Preferences...
 * Select Network page
 * Click the ""Add host-only network"" button
 * When the ""Hardware Installation"" dialog for ""!VirtualBox Host-Only Ethernet Adaptor"" appears, click the ""STOP Installation"" button.
 * If you then look at the Windows Device Manager, under Network Adaptors, there is an ""Unknown device"" entry that cannot be uninstalled.
 * When Windows is rebooted, it starts the ""Found New Hardware Wizard"" for the unknown device called ""Net"".  It keeps doing this every time Windows is rebooted.

!VirtualBox should really detect that the installation of the network driver was stopped by the user, and clean-up the Unknown device.

Tested on Windows XP SP3 (32-bit) host.

A related ticket is #4257."	gonk23
6178	[feature-request] Installer: Please introduce internal checksum	Windows	VirtualBox 3.1.4	enhancement	2010-02-12T23:36:09Z	2010-02-15T15:05:21Z	2010-02-15T15:05:21Z	"Some users, including me, experience bad downloads from time to time... which results in broken VBox installation.

Please introduce internal checksum, so installer won't proceed if it was damaged during download or by virus.

I had this problem on Windows hosts; Not sure if this is applicable to other hosts...

Similar issue: Bug #6177

-Technologov, 13.2.2010"	Technologov
5652	Bridge network driver breaks host network DHCP	Windows	VirtualBox 3.1.0	defect	2009-12-03T05:04:16Z	2009-12-03T05:06:41Z	2009-12-03T05:06:41Z	"Installing VirtualBox with the bridge network driver installed prevents the host machine from getting DHCP responses.  However, this issue only comes up after I reboot the host computer.  Here are the steps:

1.  Install VirtualBox.  Install completes successfully.  VMs run properly and can access the network.  Host networking works properly.  I can release my DHCP lease and acquire a new one successfully.

2.  Reboot the host computer.  Host is now unable to get DHCP responses and thus the IPv4 stack is not configured properly.  Interestingly, IPv6 is working properly.  The host is able to automatically configure its IPv6 address.

3.  Uninstall VirtualBox.  As soon as VB is uninstalled, the host gets the DHCP response and IPv4 works again.

I've had this issue since VB 3.0.10 at least.  I did not have the issue in 3.0.2.  I didn't install any versions between them.

Host is running Windows 7 Ultimate 64-bit.  It is an upgrade from Vista Ultimate 64-bit.  I had the same issue in Vista as well.  Several guests including Gentoo Linux and FreeBSD.  Although it doesn't appear to be a guest issue.

If I don't install the Bridge Network driver, I don't see the DHCP problem.  I did have Juniper Networks VPN installed.  I un-installed it, but it didn't help the problem.  I don't know if the un-install left any lingering drivers behind though.

I see from the DHCP server logs that the server is getting the DHCP query and is sending a response.  But the Windows box is clearly not getting the response.  Including 'ipconfig' output."	Ryan Moore
20752	VirtualBox-6.1.30-SunOS-amd64-r148432.pkg failed on Solaris 10 1/13 s10x_u11wos_24a	Solaris	VirtualBox 6.1.30	defect	2021-12-29T14:29:10Z	2021-12-29T19:36:19Z	2021-12-29T19:36:19Z	"Info for Solaris 10:

# cat release
                    Oracle Solaris 10 1/13 s10x_u11wos_24a X86
  Copyright (c) 1983, 2013, Oracle and/or its affiliates. All rights reserved.
                            Assembled 17 January 2013


VB installation console output:
# pkgadd -G -d VirtualBox-6.1.30-SunOS-amd64-r148432.pkg

The following packages are available:
  1  SUNWvbox     Oracle VM VirtualBox
                  (i386) 6.1.30,REV=2021.11.22.16.37.46.148432

Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]: 1

Processing package instance <SUNWvbox> from </tmp/VirtualBox-6.1.30-SunOS-amd64-r148432.pkg>

Oracle VM VirtualBox(i386) 6.1.30,REV=2021.11.22.16.37.46.148432

This appears to be an attempt to install the same architecture and
version of a package which is already installed.  This installation
will attempt to overwrite this package.


The installation of this package was previously terminated and
installation was never successfully completed.

Do you want to continue with the installation of <SUNWvbox> [y,n,?] y
Oracle Corporation
## Executing checkinstall script.
Checking package dependencies...
Done.
Waiting for services from previous installation to be removed.........
Warning!!! Some service(s) still appears to be present
Using </> as the package base directory.
## Processing package information.
## Processing system information.
   327 package pathnames are already properly installed.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
## Checking for setuid/setgid programs.

The following files are being installed with setuid and/or setgid
permissions:
* /opt/VirtualBox/amd64/VBoxHeadless <setuid root>
* /opt/VirtualBox/amd64/VBoxNetAdpCtl <setuid root>
* /opt/VirtualBox/amd64/VBoxNetDHCP <setuid root>
* /opt/VirtualBox/amd64/VBoxNetNAT <setuid root>
* /opt/VirtualBox/amd64/VBoxSDL <setuid root>
* /opt/VirtualBox/amd64/VirtualBoxVM <setuid root>

* - overwriting a file which is also setuid/setgid.

Do you want to install these as setuid/setgid files [y,n,?,q] y

This package contains scripts which will be executed with super-user
permission during the process of installing this package.

Do you want to continue with the installation of <SUNWvbox> [y,n,?] y

Installing Oracle VM VirtualBox as <SUNWvbox>

## Installing part 1 of 1.
/opt/VirtualBox/vboxconfig.sh
[ verifying class <none> ]
[ verifying class <manifest> ]
## Executing postinstall script.
Checking for older bits...
//opt/VirtualBox/vboxconfig.sh: syntax error at line 682: `refgroup=$' unexpected
## ERROR!! Failed to remove older/partially installed bits.
pkgadd: ERROR: postinstall script did not complete successfully

Installation of <SUNWvbox> failed.

"	Ming H
18134	Qt5 interface does not start with hardening, with qt-xcb enabled.	Solaris	VirtualBox 5.2.22	defect	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
11720	Solaris Autostart service can only work for 1st user in staff group => fixed in SVN	Solaris	VirtualBox 4.2.12	defect	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
15645	3D broken on Solaris 10	Solaris	VirtualBox 5.1.0	defect	2016-07-19T20:20:35Z	2016-08-10T10:53:22Z	2016-08-10T10:53:22Z	"After upgrading to 5.1.0, starting vb results in ""VMSetError: 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""
Disabling 3D allows VM to start. The problem didn't exist with VirtualBox-5.0.24.  The host graphics driver is NVIDIA-Solaris-x86-352.79.
"	bernievb
3072	Seamless mode prevents drag to host desktop	Solaris	VirtualBox 2.1.0	defect	2009-01-18T18:15:13Z	2010-04-09T07:19:46Z	2010-04-09T07:19:46Z	"When running a guest in seamless mode on my 64-bit OpenSolaris host, I am unable to drag and drop anything to the host's desktop, whether that is a URL from firefox, or a file from within nautilus.  I cannot even move a desktop icon around unless I first ""minimize"" the guest or switch it out of seamless mode.

I have observed this with all releases since at least 2.0.  I am not trying to drag items between guest & host--this is regarding only the host's desktop, icons, and files."	bqbauer
21507	Test, please ignore	other	VirtualBox-7.0.6	defect	2023-03-27T20:38:52Z	2023-03-28T16:07:15Z	2023-03-28T16:07:15Z	Checking if the notifications work properly.	Klaus Espenlaub
21504	windows guest on linux host unresponsive with high cpu	other	VirtualBox-7.0.6	defect	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
21503	VirtualBox 6.1.42 failed to install on MacOS 10.13.6 (High Sierra)	other	VirtualBox-6.1.42	defect	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
21498	"French translation missing for ""System"""	other	VirtualBox-7.0.6	defect	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
21491	Restore current snapshot checkbox missing when closing down the VM	other	VirtualBox-7.0.6	defect	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
21488	Crash when i change network settings in Ubuntu => fixed in SVN next/7.0.x maintenance	other	VirtualBox-7.0.6	defect	2023-02-09T17:43:54Z	2023-02-10T10:42:41Z	2023-02-10T10:42:41Z	In my windows host and ubuntu guest I have crashed VM, logs will attached	seven_vb
21489	VirtualBox Freeze Issue	other	VirtualBox-7.0.6	defect	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
21461	ver 7.0.6 failed to install	other	VirtualBox-7.0.6	defect	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
7381	Delete all snapshots at once	other	VirtualBox 3.2.8	enhancement	2010-08-26T07:01:04Z	2023-02-03T19:58:49Z	2023-02-03T19:58:49Z	"Hello,

I'd like to request the ability to delete all snapshots with one command.  Something like having an ""all"" parameter to the VBoxManage snapshot delete command, or other means to fully automate the updating of all snapshots back into the base virtual disk.

""Sasquatch"" suggested I open a ticket here and give a link to my suggestion thread in the forums: http://forums.virtualbox.org/viewtopic.php?f=9&t=33864

Thank you for your consideration.

Kind Regards,
--appyface
"	appyface
21318	Freeze on Oracle Linux 9.1 w. UEK Kernel	other	VirtualBox-7.0.4	defect	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
21421	Canonical has updated Ubuntu Linux kernel; DEB package from Oracle no longer works	other	VirtualBox-7.0.6	defect	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
21425	Unreadable fonts in Windows 11  as guest in Virtualbox	other	VirtualBox-7.0.6	defect	2023-01-22T14:59:02Z	2023-01-23T20:34:41Z	2023-01-23T20:34:41Z	Unreadable fonts in Windows 11  as guest in Virtualbox. I am unable to read the fonts as it is white on white in Word. THe system is using Fedora 37, nvidia 3070 with latest driver. 	Karo
21413	gdb crashes	other	VirtualBox-7.0.4	defect	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
21417	Different IGuestSession::processCreate behavior in v7 from v6	other	VirtualBox-7.0.6	defect	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
21406	USB devices not being enumerated on 7.0.4	other	VirtualBox-7.0.4	defect	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
21402	PXE boot gets stuck and does not hand over to next boot option	other	VirtualBox-7.0.4	defect	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
21401	VirtualBox stops operation. Log attached.	other	VirtualBox-7.0.4	defect	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
21400	E_FAIL when running Kali in VirtualBox 7.0.4	other	VirtualBox-7.0.4	defect	2023-01-08T10:49:55Z	2023-01-08T10:49:55Z	2023-01-08T10:49:55Z	"I was setting up my VirtualBox and I'm having problem when running kali in VirtualBox.

i've tried reinstalling and stepping down to versions and changing bios settings but still shows the same error.

version: vBox-7.4.4

error message shown as below:

The virtual machine 'kali' has terminated unexpectedly during startup with exit code -1073740791 (0xc0000409). More details may be available in 'C:\Users\Razal\VirtualBox VMs\kali\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0X80004005)
Component: MachineWrap
Interface: IMachine {300763af-5d6b-46e6-aa96-273eac15538a}



"	razii97
4503	NLS/Translation mistakes & suggestions	other	VirtualBox 3.0.2	defect	2009-07-13T09:22:35Z	2023-01-07T20:08:16Z	2023-01-07T20:08:16Z	Please use this ticket to report any issues with foreign language translations present in VirtualBox.	Sander van Leeuwen
21399	After updating to 7.0.4 r154605 Virtualbox Manager cannot connect to any VM	other	VirtualBox-7.0.4	defect	2023-01-07T15:56:10Z	2023-01-07T16:39:31Z	2023-01-07T16:39:31Z	"Uninstalled/reinstalled several times.
Installed guest additions on Host and VMs.
Launching guest as Headless, Detachable or Normal makes no difference.
VM's run in the preview window, but SHOW doesn't work to connect to the VM.

I've been using VirtualBox for many years without problems.  No version of 7.0 has worked for me."	FrankW
16093	Startvm --type headless on detached guest -> show window	other	VirtualBox 5.1.8	defect	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
21284	Bridge Adapter not Connecting in Virtualbox 7.x	other	VirtualBox-7.0.4	defect	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
21327	macosx M2 Unable to import OVA with error NS_ERROR_INVALID_ARG	other	VirtualBox-7.0.4	defect	2022-12-07T13:54:36Z	2022-12-13T11:22:24Z	2022-12-13T11:22:24Z	"Does anyone have a work around for importing .ova files into Version 7.0.4_BETA4 r154605 (Qt6.3.0) on Mac M2 silicone?

With Regards,
"	greyh0und
17708	I18N progress 4.0	other		defect	2018-04-23T08:37:38Z	2022-12-12T04:10:19Z	2022-12-12T04:10:19Z	"This is a continuation of ticket:14091 which is intended for two purposes:

 1. Submitting updated translations by attaching them to this ticket.
 2. The development team letting translators know about updated text to be translated.

Please read the document describing the translation process in detail [http://www.virtualbox.org/wiki/Translating here].

There is a separate ticket for NLS mistakes/suggestion (#4503).  We will add translation maintainers to CC on that ticket as necessary.

'''The current list of translators''':
||''language''||''id''||''maintainer''||''legal status''||
||English (built-in)||built_in||Oracle Corporation||OK (internal)||
||German||de||Oracle Corporation||OK (internal)||
||Russian||ru||Oracle Corporation||(comment:ticket:234:52, comment:ticket:234:47)||
||Bulgarian||bg||Stoyan Marinov (neter_bg)||OK (comment:ticket:2018:83)||
||Catalan||ca||Xavi Ivars (xavivars), Pau Iranzo (PauGNU), Josep M||OK (comment:66, comment:ticket:2018:448, comment:101)||
||Czech||cs||Radek Vybiral||OK (comment:ticket:234:183)||
||Danish||da||scootergrisen, Lars Sarauw Hansen (sarauw)||OK (comment:5), OK (comment:ticket:2018:186), OK (comment:ticket:2018:130)||
||Greek||el||Socratis Kalogrianitis (socratis), Anastasios Kazakis (tassos)||OK (comment:97, comment:107)||
||Spanish||es||David Gonzalez (pico.dev)||OK (comment:ticket:234:28, comment:ticket:2018:142)||
||Basque||eu||Xabier Aramendi (Azpidatziak)||OK (comment:ticket:2018:534)||
||Farsi||fa||Hessam Mohamadi (co22)||OK (attachment before comment:ticket:2018:411)||
||French||fr||Benjamin Masse||OK (comment:ticket:234:33, comment:ticket:2018:168, comment:ticket:2018:243, comment:ticket:2018:440)||
||Croatian||hr||Lovro Makovec (LockyGamer)||OK (comment:276)||
||Hungarian||hu||Tom Evin (evin)||OK (comment:ticket:2018:106)||
||Indonesian||id||Andika Triwidada (Andika)||OK (ICA by mail, attachment text above comment:ticket:2018:333)||
||Italian||it||Vincenzo Reale (smart2128)||OK (comment:ticket:2018:50)||
||Japanese||ja||Ikuya Awashiro (ikuya)||OK (comment:ticket:234:75, comment:ticket:2018:387)||
||Korean||ko||Shinjo Park (peremen)||OK (comment:ticket:234:224)||
||Dutch||nl||Richard E van der Luit (nippur)||OK (comment:ticket:2018:142 + 7, comment:ticket:234:163, comment:ticket:2018:270)||
||Polish||pl||Bartosz (hawkeye116477)||OK (comment:ticket:234:78, comment:ticket:234:80, comment:ticket:234:174, comment:ticket:2018:64, comment:143)||
||Portuguese (Brazil)||pt_BR||Erico Mendonca (docca)||OK (comment:ticket:234:98)||
||Slovenian||sl||Peter Klofutar (Peter Klofutar)||OK (comment:82)||
||Thai||th||Surasak Srisawan (sak)||OK (comment:185)||
||Turkish||tr||Burak Yavuz (BouRock)||OK (comment:ticket:234:254, comment:ticket:234:256, comment:ticket:2018:400)||
||Ukranian||uk||Daniel Korostil (wiseacre), Localize.org.ua community (6c6c6)||OK (comment:ticket:2018:90, comment:104)||
||Chinese (Simplified)||zh_CN||Lee Chenhwa (leechenhwa)||(comment:ticket:234:92, comment:ticket:2018:264)||
||Chinese (Traditional)||zh_TW||alan@stable (fei)||OK (comment:ticket:234:81, comment:ticket:2018:331)||

'''Disabled translations''':

||Catalan (Valencian)||ca_VA||Pau Iranzo (PauGNU)||OK (comment:ticket:2018:448)||
||Finnish||fi||Jarno Kiuttu, Timo Jyrinki, Ilkka Tuohela||OK (comment:ticket:234:137, comment:ticket:234:263, comment:ticket:2018:49)||
||Galician||gl_ES||Enrique Estévez (keko.gl)||OK (comment:ticket:2018:122)||
||Hebrew||he||Ariel Ben Zion, David Levi, Eli Zaretskii, Genghis (Genghis), Orgad Shaneh, Yaron Sheffer||OK (comment:121)||
||Khmer||km_KH||Khoem Sokhem||OK (comment:ticket:2018:77)||
||Lithuanian||lt||Mindaugas Baranauskas (Mindaugas), Algimantas Margevičius (gymka)||OK (comment:ticket:2018:192, comment:ticket:2018:313)||
||Portuguese||pt||Manuela Silva (mansil), José Melo, Marcelo Coelho||OK (comment:13, comment:ticket:234:230, comment:ticket:234:275)||
||Romanian||ro||Alexandru Ioan Eftimie||OK (comment:ticket:234:25)||
||Slovak||sk||Ivan Masár, Jozef Říha (jose1711)||OK (comment:ticket:234:231, comment:ticket:234:309)||
||Serbian||sr||Ozzii||OK (comment:ticket:234:234)||
||Swedish||sv||Daniel Nylander (yeager2)||OK (comment:ticket:234:122)||"	Michael Thayer
21275	Login issue	other	VirtualBox-7.0.2	defect	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
21236	VERR_CR_KEY_FORMAT_NOT_SUPPORTED	other	VirtualBox-7.0.2	defect	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
21215	Mouse scroll not working	other	VirtualBox-7.0.2	defect	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
21203	multiple virtual screen issues	other	VirtualBox 6.1.40	defect	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
21185	After upgrade to 7.0.2, VM will not launch	other	VirtualBox-7.0.2	defect	2022-10-21T13:43:10Z	2022-10-21T16:25:51Z	2022-10-21T16:25:51Z	"I've been running virtualbox on a Windows 10/11 machine for several years and this is the first issue I've ran in to like this. After upgrading from 7.0.0 to 7.0.2, the issue started. Here is the error I get:
I'll also mention I have uninstalled, rebooted, and reinstalled 7.0.2.
I have uninstalled, rebooted, and reinstalled 6.1.38 but the issue persists.
I did not have this issue when I was running 7.0.0 or 6.1.38, or 6.1.40

Failed to open a session for the virtual machine myserver.
Failed to open/create the internal network 'HostInterfaceNetworking-Realtek Gaming GbE Family Controller' (VERR_SUPDRV_COMPONENT_NOT_FOUND).
Failed to attach the network LUN (VERR_SUPDRV_COMPONENT_NOT_FOUND).
Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}"	vboxuser1001
20342	VirtualBox 6.1.20/6.1.22 breaks audio output on a Fedora 33 system	other	VirtualBox 6.1.22	defect	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
21123	Virtual machine crashes while installing the Guest addons	other	VirtualBox 7.0.0	defect	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
21127	windows 10 guest crash	other	VirtualBox 6.1.38	defect	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
21121	second network interface cannot talk to network	other	VirtualBox 6.1.38	defect	2022-10-09T16:33:38Z	2022-10-09T16:33:38Z	2022-10-09T16:33:38Z	I added a second interface to a Linux (Ubuntu) VM, bridged, and it does not talk to the network at all. It's supposed to get an IP address via DHCP, but it fails. It's the same class as the first interface, which means that ceteris paribus should work in identical ways.	philip orleans
19677	VM window size not restored after exiting save state	other	VirtualBox 6.1.10	defect	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
21105	Getting a Guru Meditation - Critical error during CentOS user settings configuration	other	VirtualBox 6.1.38	defect	2022-09-10T20:33:56Z	2022-09-10T23:49:24Z	2022-09-10T23:49:24Z		ktapodac
21098	Can't create VDI file from external hard drive	other	VirtualBox 6.1.38	defect	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
21080	'NS_ERROR_FAILURE' and '/sbin/rcvboxdrv' and similar commands produce a 'not found' error	other	VirtualBox 6.1.36	defect	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
20335	export VM disk image format: vdi instead of vmdk (ova or different VM container format)	other	VirtualBox 6.1.22	enhancement	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
21063	Windows 98 not running on windows 11	other	VirtualBox 6.1.36	defect	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
21049	Windows 10 Guest login on Fedora 36 crashes after mouse movement	other	VirtualBox 6.1.36	defect	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
21044	Virtual Machine does not open VMDK-file from VMWare	other	VirtualBox 6.1.36	defect	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
21053	Accidental shutdown click if click on `Machine` guest main menu	other	VirtualBox 6.1.36	defect	2022-08-07T05:51:27Z	2022-08-07T05:51:27Z	2022-08-07T05:51:27Z	"Some times a Guest shutdowns because of accidental single click on both menu items in the same time: `Machine` and `Machine->ACPI Shutdown`.

This can happen because:

1. Guest main menu is at the bottom of the screen.
2. Guest main menu and submenu does overlap.
3. Mouse left button down does click on item of the main menu, but mouse left button up does click on item from a submenu.

So, because `Machine` and `Machine->ACPI Shutdown` has all the above, then some times the click happens and machine does shutdown. This bug is very annoying.

To repro:

1. Click guest `Machine` main menu and hold the button.
2. Move cursor to `Machine->Setting...` and release the button.

Expected behaviour:

1. Mouse button release has no effect on a menu or a submenu if not been initiated on the same menu.
"	andry81
20504	vboxdrv: linux kernel errors on debug kernel and vbox modules built by akmods	other	VirtualBox 6.1.26	defect	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
20939	VBox on Windows 11 kernel panic - unable to sync on every VM	other	VirtualBox 6.1.32	defect	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
14253	Default VM Start Method	other	VirtualBox 5.0.0	enhancement	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
21009	macos 6.1.34 cannot change a static IP address in host-only mode	other	VirtualBox 6.1.32	defect	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
21006	DHCP provides wrong DNS server address if DNS server address is not requested	other	VirtualBox 6.1.34	defect	2022-06-23T13:15:35Z	2022-06-23T13:15:35Z	2022-06-23T13:15:35Z	"VirtualBox 6.1 on Fedora Linux with NAT networking:

If the DHCP client in the VM does not provide option 55 -  Parameter Request List - or does provide one, but does not provide Item 6 - Domain Name Sever - in DCHDISCOVER, then the VirtualBox builtin DHCP server will respond with a DHCPOFFER containing a DNS Sever option, anyway.

But the address specified in this option will be invalid. More specifically, instead of providing 10.0.2.3, it will provide whatever is in /etc/hosts. This may go unnoticed if the DNS sever listed in /etc/hosts has a routable address.

On a Fedora Linux the DNS server in /etc/hosts has the address 127.0.0.53, which is not routable and as such when the VM tries to talk to it, it fails (it has no such local address configured).

Interestingly, if I manually configure the DNS server address in the guest OS to 10.0.2.3, the VirtualBox DNS server does not respond on that address.

I can reproduce this on HelenOS as of Git revision 52214a2d97559c2396ecbcd3de80863dab438fb3. Unfortunately this cannot be tested with a binary release (e.g. the latest, HelenOS 0.11.2) as it misses a fix for another problem that HelenOS DHCP has in VirtualBox.
"	JiriS
21002	Better synchronisation between VboxManage CLI and GUI	other	VirtualBox 6.1.32	defect	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
20915	SessionState never unlocked	other	VirtualBox 6.1.32	defect	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
16237	VirtualBox can't find Virtual adapters for vlans on Windows 7	other	VirtualBox 5.1.10	defect	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
20899	show the VM logs from the running machine window	other	VirtualBox 6.1.30	enhancement	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
20887	Problème de démarrage de la machine	other	VirtualBox 6.1.32	defect	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
20882	SATA Controller Option Cause jbd2 blocking the disk access	other	VirtualBox 6.1.30	defect	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
20874	Failed to create cloud machine	other	VirtualBox 6.1.32	defect	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
20234	Kernel driver not installed launching VM on Version 6.1.18 r142142 (Qt5.6.3)	other	VirtualBox 6.1.18	defect	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
20852	Machine guest freeze on the host	other	VirtualBox 6.0.22	defect	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
20848	Time-consuming Guest Addition installation on Windows XP Pro SP3 32-bit.	other	VirtualBox 6.1.32	defect	2022-02-24T22:17:23Z	2022-02-24T22:17:23Z	2022-02-24T22:17:23Z	"Regards, sorry me for my bad english.
I opened a post in the forum about a problem with the Guest Addition installation on Windows XP Pro SP3 32-bit.
After a series of tests and comparisons with other users, they advised me to open a Bugtracker.
Using VirtualBox and Guest Addition version 6.1.32, when I try to install Guest Additions, I initially thought the installation would hang.
Speaking with other users we understood that the installation does not crash, but it takes a long time to complete.
I personally take about 15 minutes to finish it.
Searching the forum, I found another user who opened a post, where he writes that he too takes 15 minutes to install.
Another user writes that he takes 10 minutes to install.
It's not just me who has this problem.
To overcome this ""bug"", after many tests the only way to overcome it is:
Or start the Guest PC in safe mode;
Or disable the Network card;
Or wait 15 minutes;
Or at the end of the Guest PC installation, set up the optical reader, turn off the Guest PC, turn on the Guest PC and the Guest Addition installation is completed quickly.
I have tested many solutions and I am available to retest your suggestions.
Thank you."	ermete74
20847	Vbox 6.1 guest crashes when monitor powers off	other	VirtualBox 6.1.32	defect	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
20838	Discovered 2 vulnerabilities in VirtualBox	other	VirtualBox 6.1.32	defect	2022-02-22T19:08:52Z	2022-02-23T19:58:31Z	2022-02-23T19:58:31Z	"Hi, 
In the last couple of months I discovered 2 vulnerabilities in E1000 emulated device. I disclose it to you in order to fix them.
I provide a zip file which contains a README.md file, which is highly documented description of the vulnerabilities. It also describes other files in the zip file. I will be happy to be in touch with you to help you resolve this issues. In addition, I would be happy if you can create a CVE number for each one of these vulnerabilities. 

Thank you and hope to hear from you soon,
Adi

e1000_vulnerabilites.zip: md5 
"	nick1
20829	cannot assign static IP in host only adapter - other than 192.168.56.0/21	other	VirtualBox 6.1.32	defect	2022-02-16T12:05:22Z	2022-02-16T16:20:47Z	2022-02-16T16:20:47Z	"I'm trying to use my old vboxnetX adapters with my custom IPs, but for the last releases I cannot. Interfaces are starting but with no IPs

Fedora 35 / VirtualBox-6.1-6.1.32_149290_fedora33-1.x86_64

# VBoxManage hostonlyif create 
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interface 'vboxnet0' was successfully created

# VBoxManage hostonlyif ipconfig vboxnet0 --ip 10.88.88.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

in log I get:

00:00:00.154243 nspr-2   NetIfAdpCtl: failed to create process for /usr/lib/virtualbox/VBoxNetAdpCtl: iStats=38 enmReason=1
00:00:00.154256 nspr-2   Failed to EnableStaticIpConfig with rc=VERR_ACCESS_DENIED

# strace /usr/lib/virtualbox/VBoxNetAdpCtl vboxnet0 10.88.88.1 netmask 255.255.255.0
...
stat(""/sbin/ip"", {st_mode=S_IFREG|0755, st_size=719208, ...}) = 0
openat(AT_FDCWD, ""/etc/vbox/networks.conf"", O_RDONLY) = 3
newfstatat(3, """", {st_mode=S_IFREG|0644, st_size=28, ...}, AT_EMPTY_PATH) = 0
read(3, ""10.88.88.0/24\n10.88.89.0/24\n"", 4096) = 28
read(3, """", 4096)                       = 0
close(3)                                = 0
write(2, ""Error: permission denied\n"", 25Error: permission denied

cat /etc/vbox/networks.conf 
10.88.88.0/24
10.88.89.0/24

ls -ld /etc/vbox/networks.conf 
-rw-r--r-- 1 root root 28 Feb 16 13:46 /etc/vbox/networks.conf

all commands are as root

If I manually edit VirtualBox.xml and add the ips (this was my config until I removed the adapters to try from scratch)

# VBoxManage list hostonlyifs 

Name:            vboxnet0
GUID:            786f6276-656e-4074-8000-0a0027000000
DHCP:            Disabled
IPAddress:       10.88.88.1
NetworkMask:     255.255.255.0
IPV6Address:     
IPV6NetworkMaskPrefixLength: 0
HardwareAddress: 0a:00:27:00:00:00
MediumType:      Ethernet
Wireless:        No
Status:          Down
VBoxNetworkName: HostInterfaceNetworking-vboxnet0

Name:            vboxnet1
GUID:            786f6276-656e-4174-8000-0a0027000001
DHCP:            Disabled
IPAddress:       10.88.89.1
NetworkMask:     255.255.255.0
IPV6Address:     
IPV6NetworkMaskPrefixLength: 0
HardwareAddress: 0a:00:27:00:00:01
MediumType:      Ethernet
Wireless:        No
Status:          Down
VBoxNetworkName: HostInterfaceNetworking-vboxnet1

When I start VirtualBox I get in logs:
00:00:00.122927 nspr-2   failed to create vboxnet0, error (0xffffffff)
00:00:00.126670 nspr-2   failed to create vboxnet1, error (0xffffffff)

and upon starting a VM:

00:00:53.167974 nspr-2   NetIfAdpCtl: failed to create process for /usr/lib/virtualbox/VBoxNetAdpCtl: iStats=38 enmReason=1
00:00:53.168021 nspr-2   Failed to EnableStaticIpConfig with rc=VERR_ACCESS_DENIED

ifconfig vboxnet0

vboxnet0: flags=4098<BROADCAST,MULTICAST>  mtu 1500
        ether 0a:00:27:00:00:00  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
"	bilias
19237	VBoxSVGA OpenGL upsidedown	other	VirtualBox 6.0.16	defect	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
19967	VirtualBox fails to boot Ubuntu 20.10 beta ISO in EFI mode	other	VirtualBox 6.1.14	defect	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
20807	echec de l'ouverture de session pour la machine virtuelle XP	other	VirtualBox 6.1.32	defect	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
20804	Some keystrokes dont get recognized in vm [Windows-Host]	other	VirtualBox 6.1.32	defect	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
20781	starting guest with --type headless fails on macOS Mojave host	other	VirtualBox 6.1.32	defect	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
20766	Frequest VM crashes, looks like host virtio driver issues	other	VirtualBox 6.1.30	defect	2022-01-10T06:47:19Z	2022-01-13T08:53:02Z	2022-01-13T08:53:02Z	"After upgrade of host system from Debian Buster to Debian Bullseye (including upgrade of virtualbox package), I'm getting frequent crashes of linux VMs.

It looks like I'm away for a while, and when I return, VMs are not running, status in GUI is ""Aborted"", and several last log lines look like


{{{
...
00:55:34.164526 Pausing VM execution, reason 'host suspend'
00:55:34.164560 Changing the VM state from 'RUNNING' to 'SUSPENDING'
00:55:34.164612 PDMR3Suspend: after     0 ms, 1 loops: 1 async tasks - virtio-scsi/0
00:55:34.204298 AIOMgr: Endpoint for file '/home/nikita/VirtualBox VMs/vzvm/vzvm.vdi' (flags 000c0781) created successfully
00:55:34.225496 PDMR3Suspend: 60 917 038 ns run time
00:55:34.225515 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'
00:55:34.225530 Console: Machine state changed to 'Paused'
00:55:34.225681 GUI: Releasing keyboard on pause/stuck
00:55:34.225884 GUI: Releasing mouse on pause/stuck
00:55:45.439541 Resuming VM execution, reason 'host resume'
00:55:45.439633 Changing the VM state from 'SUSPENDED' to 'RESUMING'
00:55:45.439825 AIOMgr: Endpoint for file '/home/nikita/VirtualBox VMs/vzvm/vzvm.vdi' (flags 000c0723) created successfully
00:55:45.445823 virtioCoreVirtqAvailBufCount: Driver not ready or queue not enabled
00:55:45.445875 virtioCoreVirtqAvailBufCount: Driver not ready or queue not enabled
}}}


I'm not sure what is ""host suspend"" mentioned here, there was no manual host suspend at the shown time, although it could be something system-initiated.

Virtualbox is from virtualbox-6.1 package version 6.1.30-148432~Debian~bullseye

Host kernel is from debian package linux-image-5.10.0-10-amd64 5.10.84-1."	nikita_yoush
20759	VBoxTpG: error: Failed to start 'yasm' (assembler): VERR_ACCESS_DENIED	other	VirtualBox 6.1.30	defect	2022-01-05T17:05:08Z	2022-01-05T17:05:08Z	2022-01-05T17:05:08Z	build error see log file in attach.	custom
20751	Theme incompatiblity makes fonts invisible	other	VirtualBox 6.1.30	defect	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
20742	VirtualBox crashes when restoring from saved state	other	VirtualBox 6.1.30	defect	2021-12-22T20:13:18Z	2021-12-22T20:15:48Z	2021-12-22T20:15:48Z	"... then hangs when attempted to stop the VM.

"	TomerB
20005	POPCNT cpu flag not supported in 6.1 Ubuntu 16 guest	other	VirtualBox 6.1.16	defect	2020-10-27T22:37:42Z	2021-12-22T10:37:35Z	2021-12-22T10:37:35Z	Ubuntu 16 guest with Enable Nested Paging enabled.  On VirtualBox 6.0 guest Ubuntu 16.04 reports having the POPCNT CPU flag.  On 6.1 POPCNT is no longer there (causing my OpenCV app to fail).  I downgraded back to 6.0 and it runs again.  If this is in the release notes I didn't find it.	eben
629	the virtualbox GUI isn't accessible to those using screen readers	other	VirtualBox 2.0.4	defect	2007-09-05T00:00:03Z	2021-12-21T17:15:12Z	2021-12-21T17:15:12Z	"This issue has already been discussed on the vbox-users mailing list:

http://vbox.innotek.de/pipermail/vbox-users/2007-July/001803.html
http://vbox.innotek.de/pipermail/vbox-users/2007-August/001978.html
http://vbox.innotek.de/pipermail/vbox-users/2007-July/001834.html

Dmitry from innotek has already said that time would be invested into this 
issue, but I didn't see that a ticket was created for it, and thought it
would be a good idea to create one,
so that this problem isn't put aside and forgotten.

An ideal solution if possible, would be access via screen readers to the vbox 
GUI on all supported platforms, (I.E. windows, linux, macos, ETC.)."	Gregory Nowak
20739	Direct 3D Not Available On Virtualbox Windows 7 Guest	other	VirtualBox 6.1.30	defect	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
20691	Can't install virtualbox to other hard drive with msi parameter	other	VirtualBox 6.1.30	defect	2021-11-25T19:45:06Z	2021-12-10T08:02:36Z	2021-12-10T08:02:36Z	"Hello,


{{{
msiexec /i VirtualBox-6.1.30.msi /L*vx VirtualBox-6.1.30-install.log IAGREE=Yes /QB TARGETDIR=""D:\Program Files\Oracle\VirtualBox"" VBOX_INSTALLDESKTOPSHORTCUT=0 VBOX_START=0 ADDLOCAL=""VBoxApplication,VBoxUSB,VBoxNetworkFlt,VBoxPython""
}}}

D: is a hard drive formated in NTFS format


Virtualbox is installed to C:



"	Owned
20715	"VirtualBox 6.1.30: ""vboxmanage natnetwork"" lacks of options to set IPv6 prefix and enable/disable router advertisements"	other	VirtualBox 6.1.30	task	2021-12-03T18:14:14Z	2021-12-03T18:14:14Z	2021-12-03T18:14:14Z	"VirtualBox 6.1.30: ""vboxmanage natnetwork"" lacks of options to set IPv6 prefix and enable/disable router advertisements.

Example:
vboxmanage natnetwork add --netname ISP-Alpha \
   --network 172.31.255.0/24 \
   --enable \
   --dhcp no \
   --ipv6 yes

""--network"" only allows to configure the IPv4 network. There is no corresponding option for IPv6. It is only possible to turn IPv6 on/off, and the prefix gets configured automatically. Documentation about how the IPv6 prefix is computed is missing! (And there is a bug in this automatic configuration as well: https://www.virtualbox.org/ticket/20714)

DHCP can be enabled with ""--dhcp"", but there is no option to turn on ICMPv6 router advertisements and/or DHCPv6."	Thomas Dreibholz
20701	crash vm on share clipboard	other	VirtualBox 6.1.30	defect	2021-11-28T19:22:23Z	2021-11-28T19:22:23Z	2021-11-28T19:22:23Z	"
log error :[[BR]]

Shared Clipboard: Converting VBox formats 0x1 to 'INVALID' for X11 (idxFmtX11=0, fmtX11=0) [[BR]]
failed, rc=VERR_NOT_SUPPORTED[[BR]]

and [[BR]]

error log:[[BR]]

Shared Clipboard: Signalling of guest clipboard data to the host failed: VERR_NOT_FOUND[[BR]]

Thank corrige this bug !"	Sizy458
20698	crash vm on share clipboard	other	VirtualBox 6.1.30	defect	2021-11-28T15:59:26Z	2021-11-28T15:59:26Z	2021-11-28T15:59:26Z	"Hello,[[BR]]

the function copy/paste share clipboard work but [[BR]]

i had a crash.[[BR]]
"	Sizy458
20686	Turkish translate	other	VirtualBox 6.1.30	defect	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
20671	Unable to import	other	VirtualBox 6.1.28	defect	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
20666	VirtualBox UI (Qt5GuiVBox.dll) for Windows crashes on start up	other	VirtualBox 6.1.28	defect	2021-11-13T18:58:17Z	2021-11-16T13:26:09Z	2021-11-16T13:26:09Z	"The VirtualBox GUI simply freezes on load and then crashes.  To ""fix"" this, I have to uninstall/reinstall but the problem eventually reappears.  Not sure how to reproduce though.

!analyze-v output is below.

Note that this happens on the latest version (6.1.28) although the dump below is from 6.1.26 because I wanted to see if previous versions also have this problem (which they obviously do) and I didn't save the 6.1.28 dumps.  But the root case is the same as seen in the Event Log entries.


{{{
Faulting application name: VirtualBox.exe, version: 6.1.28.47628, time stamp: 0x616db42a
Faulting module name: Qt5GuiVBox.dll, version: 5.6.2.0, time stamp: 0x58e261e1
Exception code: 0xc000041d
Fault offset: 0x00000000001e384e
Faulting application path: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
Faulting module path: C:\Program Files\Oracle\VirtualBox\Qt5GuiVBox.dll


Faulting application name: VirtualBox.exe, version: 6.1.26.45957, time stamp: 0x6101832f
Faulting module name: Qt5GuiVBox.dll, version: 5.6.2.0, time stamp: 0x58e261e1
Exception code: 0xc0000005
Fault offset: 0x00000000001e384e
Faulting application path: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
Faulting module path: C:\Program Files\Oracle\VirtualBox\Qt5GuiVBox.dll
}}}




{{{
0:000> !analyze -v
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

DUMP_CLASS: 2

DUMP_QUALIFIER: 400

CONTEXT:  (.ecxr)
rax=0000000000000000 rbx=00007fffb5fdb610 rcx=0000000006388c70
rdx=000000000304e4e8 rsi=00000000004f5f00 rdi=00000000004f63f0
rip=00007fff25d9384e rsp=00000000004f66a0 rbp=00000000182a0100
 r8=000000000304e490  r9=0000000000000000 r10=000000000304e490
r11=000000000304e4e8 r12=0000000000000000 r13=0000000004e90c50
r14=00000000042b7600 r15=00000000058bbd58
iopl=0         nv up ei pl zr na po nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010244
Qt5GuiVBox!QRasterPaintEngine::transformChanged+0x1e:
00007fff`25d9384e 8388b803000040  or      dword ptr [rax+3B8h],40h ds:00000000`000003b8=????????
Resetting default scope

FAULTING_IP: 
Qt5GuiVBox!QRasterPaintEngine::transformChanged+1e
00007fff`25d9384e 8388b803000040  or      dword ptr [rax+3B8h],40h

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 00007fff25d9384e (Qt5GuiVBox!QRasterPaintEngine::transformChanged+0x000000000000001e)
   ExceptionCode: c000041d
  ExceptionFlags: 00000001
NumberParameters: 0

PROCESS_NAME:  VirtualBox.exe

ERROR_CODE: (NTSTATUS) 0xc000041d - An unhandled exception was encountered during a user callback.

EXCEPTION_CODE: (NTSTATUS) 0xc000041d - An unhandled exception was encountered during a user callback.

EXCEPTION_CODE_STR:  c000041d

WATSON_BKT_PROCSTAMP:  6101832f

WATSON_BKT_PROCVER:  6.1.26.45957

PROCESS_VER_PRODUCT:  Oracle VM VirtualBox

WATSON_BKT_MODULE:  Qt5GuiVBox.dll

WATSON_BKT_MODSTAMP:  58e261e1

WATSON_BKT_MODOFFSET:  1e384e

WATSON_BKT_MODVER:  5.6.2.0

MODULE_VER_PRODUCT:  Qt5

BUILD_VERSION_STRING:  19041.1.amd64fre.vb_release.191206-1406

NTGLOBALFLAG:  0

PROCESS_BAM_CURRENT_THROTTLED: 0

PROCESS_BAM_PREVIOUS_THROTTLED: 0

APPLICATION_VERIFIER_FLAGS:  0

PRODUCT_TYPE:  1

SUITE_MASK:  272

DUMP_FLAGS:  8000c07

DUMP_TYPE:  3

THREAD_ATTRIBUTES: 
OS_LOCALE:  ENU

BUGCHECK_STR:  FATAL_USER_CALLBACK_EXCEPTION

DEFAULT_BUCKET_ID:  FATAL_USER_CALLBACK_EXCEPTION

PRIMARY_PROBLEM_CLASS:  FATAL_USER_CALLBACK_EXCEPTION

PROBLEM_CLASSES: 

    ID:     [0n321]
    Type:   [@APPLICATION_FAULT_STRING]
    Class:  Primary
    Scope:  DEFAULT_BUCKET_ID (Failure Bucket ID prefix)
            BUCKET_ID
    Name:   Omit
    Data:   Add
            String: [FATAL_USER_CALLBACK_EXCEPTION]
    PID:    [Unspecified]
    TID:    [Unspecified]
    Frame:  [0]

LAST_CONTROL_TRANSFER:  from 00007fff25da0c3e to 00007fff25d9384e

STACK_TEXT:  
00000000`004f66a0 00007fff`25da0c3e : 00000000`0304e3c0 00000000`00000001 4079b000`00000000 40886800`00000000 : Qt5GuiVBox!QRasterPaintEngine::transformChanged+0x1e
00000000`004f66d0 00000000`61055708 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`004f6898 : Qt5GuiVBox!QPainter::PixmapFragment::create+0x90e
00000000`004f67b0 00000000`6105842f : 00000000`00000000 00000000`004f6a40 00000000`00000000 00000000`00000020 : Qt5WidgetsVBox!QGraphicsScene::wheelEvent+0x748
00000000`004f6940 00000000`61059e97 : 00000000`04e90c50 00000000`058bbd00 00000000`04e90c50 00000000`04e90c50 : Qt5WidgetsVBox!QGraphicsScene::removeItem+0x98f
00000000`004f6c20 00000000`6106ee42 : 00000000`0638b010 00000000`04e90c50 00000000`058bb880 00000000`0680a350 : Qt5WidgetsVBox!QGraphicsScene::destroyItemGroup+0x337
00000000`004f6d80 00000000`60d9ff5f : 00000000`61571a58 00000000`00000008 00000000`60d50000 00000000`00000000 : Qt5WidgetsVBox!QGraphicsView::paintEvent+0x622
00000000`004f7260 00000000`60e8d407 : 00000000`00000000 00000000`004f7d68 00000000`00000000 00000000`00000000 : Qt5WidgetsVBox!QWidget::event+0x59f
00000000`004f7430 00000000`61070644 : 00000000`00000024 00000000`61116ca8 00000000`61116ca8 00000000`067ea400 : Qt5WidgetsVBox!QFrame::event+0x37
00000000`004f7460 00000000`614739de : 00000000`027ef720 00000000`067ea400 00000000`00000000 00000000`00000000 : Qt5WidgetsVBox!QGraphicsView::viewportEvent+0xa4
00000000`004f74e0 00000000`60d653fe : 00000000`027efd40 00000000`0271aec0 00000000`067ea400 00000000`004f7d68 : Qt5CoreVBox!QCoreApplicationPrivate::sendThroughObjectEventFilters+0xde
00000000`004f7540 00000000`60d6a7bb : 00000000`023ea2e0 00000000`004f7670 00000000`004f7d68 00007fff`b8235ba1 : Qt5WidgetsVBox!QApplicationPrivate::notify_helper+0xfe
00000000`004f7570 00000000`61475038 : 00000000`004ff490 00000000`023ea2e0 00000000`004f7d68 00000000`067ea400 : Qt5WidgetsVBox!QApplication::notify+0x1c4b
00000000`004f7c60 00000000`60d9e49b : 00000000`067ea400 00007fff`25f54710 00000000`0663a100 00000000`023ea2e0 : Qt5CoreVBox!QCoreApplication::notifyInternal2+0xa8
00000000`004f7cc0 00000000`60d91fb1 : 00000000`004f80d0 00000000`02fc46d0 00000000`02fc46d0 00000000`ffffffff : Qt5WidgetsVBox!QWidgetPrivate::drawWidget+0x8db
00000000`004f7e10 00000000`60d9e66b : 00000000`058bb880 00000000`0663a188 00000000`058bb898 00000000`00000002 : Qt5WidgetsVBox!QWidgetPrivate::paintSiblingsRecursive+0x391
00000000`004f7f20 00000000`60d91fb1 : 00000000`004f8330 00000000`058bb880 00000000`058bb880 00000000`ffffffff : Qt5WidgetsVBox!QWidgetPrivate::drawWidget+0xaab
00000000`004f8070 00000000`60d9e66b : 00000000`02fc4e10 00000000`0663a188 00000000`02fc4e28 00000000`00000002 : Qt5WidgetsVBox!QWidgetPrivate::paintSiblingsRecursive+0x391
00000000`004f8180 00000000`60d91fb1 : 00000000`004f86a0 00000000`02fc4e10 00000000`02fc4e10 00007fff`00000000 : Qt5WidgetsVBox!QWidgetPrivate::drawWidget+0xaab
00000000`004f82d0 00000000`60d91ec6 : 00000000`04a168a0 00000000`0663a188 00000000`04a168b8 00007fff`00000001 : Qt5WidgetsVBox!QWidgetPrivate::paintSiblingsRecursive+0x391
00000000`004f83e0 00000000`60d9e66b : 00000000`04a168a0 00000000`0663a188 00000000`04a168b8 00000000`00000003 : Qt5WidgetsVBox!QWidgetPrivate::paintSiblingsRecursive+0x2a6
00000000`004f84f0 00000000`60d91fb1 : 00000000`004f8900 00000000`04a168a0 00000000`04a168a0 00000000`ffffffff : Qt5WidgetsVBox!QWidgetPrivate::drawWidget+0xaab
00000000`004f8640 00000000`60d9e66b : 00000000`02fc4c40 00000000`0663a188 00000000`02fc4c58 00000000`00000001 : Qt5WidgetsVBox!QWidgetPrivate::paintSiblingsRecursive+0x391
00000000`004f8750 00000000`60d91fb1 : 00000000`0661f28c 00000000`02fc4c40 00000000`02fc4c40 00000000`00000001 : Qt5WidgetsVBox!QWidgetPrivate::drawWidget+0xaab
00000000`004f88a0 00000000`60d9e66b : 00000000`02f990d0 00000000`0663a188 00000000`02f990e8 00000000`00000003 : Qt5WidgetsVBox!QWidgetPrivate::paintSiblingsRecursive+0x391
00000000`004f89b0 00000000`60d70dfb : 00000000`030394c0 00000000`004f8c00 00000000`615785c8 00000000`005e99a8 : Qt5WidgetsVBox!QWidgetPrivate::drawWidget+0xaab
00000000`004f8b00 00000000`60d71026 : 00000000`0661f240 00000000`0661f201 00000000`00000000 00000000`00000000 : Qt5WidgetsVBox!QWidgetPrivate::invalidateBuffer_resizeHelper+0x1e0b
00000000`004f8f70 00000000`60d91197 : 00000000`00000000 00007fff`0000000b 00000000`050eb6f0 00000000`064810f0 : Qt5WidgetsVBox!QWidgetPrivate::invalidateBuffer_resizeHelper+0x2036
00000000`004f8fd0 00000000`60dbcd32 : 00000000`004f9820 00000000`00000000 00000000`027ef720 00000000`0000001d : Qt5WidgetsVBox!QWidgetPrivate::syncBackingStore+0x47
00000000`004f9000 00000000`60d65412 : 00000000`064810f0 00000000`027efd40 00000000`064810f0 00000000`004f9820 : Qt5WidgetsVBox!QWidget::underMouse+0x3a42
00000000`004f9070 00000000`60d6a7bb : 00000000`027efd40 00000000`004f91a0 00000000`004f9820 00000000`004f9820 : Qt5WidgetsVBox!QApplicationPrivate::notify_helper+0x112
00000000`004f90a0 00000000`61475038 : 00000000`004ff490 00000000`023ea2e0 00000000`004f9820 00000000`06481000 : Qt5WidgetsVBox!QApplication::notify+0x1c4b
00000000`004f9790 00007fff`25bdce55 : 00000000`06639d80 00000000`00000011 00000000`00000000 00000000`023ea2e0 : Qt5CoreVBox!QCoreApplication::notifyInternal2+0xa8
00000000`004f97f0 00007fff`25be5d42 : 00000000`064810f0 00000000`00000000 00000000`06639d80 00007fff`25bc49e0 : Qt5GuiVBox!QGuiApplicationPrivate::processExposeEvent+0x115
00000000`004f9890 00007fff`25bc4c09 : 00007fff`261615c0 00000000`06639d80 00000000`00000000 00007fff`25bc4eb7 : Qt5GuiVBox!QGuiApplicationPrivate::processWindowSystemEvent+0x132
00000000`004f98e0 00007fff`25bc4e26 : 00000000`00000001 00007fff`261615c0 00000000`027efd40 00000000`00070f6c : Qt5GuiVBox!QWindowSystemInterface::sendWindowSystemEvents+0x99
00000000`004f9910 00007fff`3f5661b9 : 00000000`00000001 00007fff`261615c0 00000000`061908c0 00000000`00070f6c : Qt5GuiVBox!QWindowSystemInterface::flushWindowSystemEvents+0x176
00000000`004f9960 00007fff`3f570cf5 : 00000000`03d6d4a0 00000000`027fc358 00000000`027fc358 00000000`061908c0 : qwindows+0x61b9
00000000`004f9a10 00007fff`3f57134c : 00000000`027fc358 000061c8`000061c8 00000000`0000000f 00000000`00000000 : qwindows+0x10cf5
00000000`004f9b30 00007fff`b735e7e8 : 00000000`00070f6c 00000000`004fa050 00000000`00000000 00000000`00000000 : qwindows+0x1134c
00000000`004f9bd0 00007fff`b735e36c : 00000000`000020c8 00007fff`3f5712f0 00000000`00070f6c 00000000`0000000f : user32!UserCallWinProcCheckWow+0x2f8
00000000`004f9d60 00007fff`b7370f93 : 00000000`00000000 00000000`00000000 00000000`00000000 00007fff`b735a553 : user32!DispatchClientMessage+0x9c
00000000`004f9dc0 00007fff`b82b0ba4 : 00000000`004fa630 00007fff`b672e71b 00000000`004f9ee0 00000000`004f9f10 : user32!_fnDWORD+0x33
00000000`004f9e20 00007fff`b6201704 : 00007fff`b735e27a 00000000`004fa630 00007fff`b672e71b 00000000`004f9f70 : ntdll!KiUserCallbackDispatcherContinue
00000000`004f9ea8 00007fff`b735e27a : 00000000`004fa630 00007fff`b672e71b 00000000`004f9f70 00000000`004fa050 : win32u!NtUserDispatchMessage+0x14
00000000`004f9eb0 00007fff`b672eb6b : 00007fff`3f5712f0 00000000`004fa630 00000000`00280000 00000000`0000000f : user32!DispatchMessageWorker+0x29a
00000000`004f9f30 00007fff`b672ceda : 00000000`004f0020 00000000`00000028 00000000`02d49160 00000000`00000000 : combase!CCliModalLoop::HandleWakeForMsg+0x1c3
00000000`004f9fd0 00007fff`b672cbbb : 00000032`60f203a7 00000000`004fa0c0 00000000`032b4a5e 00000000`02d8dab0 : combase!CCliModalLoop::BlockFn+0x2de
00000000`004fa090 00007fff`b6704956 : 00000000`ffffffff 00000000`02d49160 00000000`004fa160 00000000`02d8d150 : combase!ClassicSTAThreadWaitForCall+0xbb
00000000`004fa100 00007fff`b672d143 : 00000000`02d49160 00007fff`b7dc79e0 00000000`00000000 00000000`02d49160 : combase!CSyncClientCall::SendReceive2+0x9d6
00000000`004fa600 00007fff`b674099b : 00000000`00000003 00000000`02d82460 00000000`02d49160 00007fff`b6720c84 : combase!ClassicSTAThreadSendReceive+0xa3
00000000`004fa730 00007fff`b672c494 : 00000000`02d7ec38 00000000`00000007 00000000`00000001 00000000`00000001 : combase!CSyncClientCall::SendReceive+0x18b
00000000`004fa960 00007fff`b677998e : 00000000`004fab80 00000000`004fb120 00000000`00000000 00000000`004fb120 : combase!CClientChannel::SendReceive+0x84
00000000`004fa9d0 00007fff`b7e4fd84 : 00000000`004fadb0 00000000`00000000 00000000`00000000 00000000`004fb120 : combase!NdrExtpProxySendReceive+0x4e
00000000`004faa00 00007fff`b6775458 : 00007fff`3f4beb20 00000000`004fb150 ffffffff`fffffffe 00000000`61635ee8 : rpcrt4!NdrpClientCall3+0x3a4
00000000`004fad70 00007fff`b67eb902 : 00000000`027fed98 00000000`004fb1d8 00000000`004fb200 00000000`004fb390 : combase!ObjectStublessClient+0x138
00000000`004fb100 00007fff`263a2fa9 : 00000000`02d7ec38 00000000`004fb180 00000000`00000091 00000000`004fb140 : combase!ObjectStubless+0x42
00000000`004fb150 00007ff6`b27aa185 : 00000000`00000000 00000000`004fb1d8 00000000`615785b0 00000000`02fe6070 : UICommon!CVirtualBox::GetVersion+0x59
00000000`004fb1b0 00000000`61495a79 : 00000000`027ef880 00000000`02fd2d20 00000000`02fcce20 00000000`02fd2d20 : VirtualBox!TrustedMain+0x8ad5
00000000`004fb290 00000000`60d65412 : 00000000`027efd40 00000000`0271aec0 00000000`027ef880 00000000`03019ac0 : Qt5CoreVBox!QObject::event+0xc9
00000000`004fb400 00000000`60d6a7bb : 00000000`023ea2e0 00000000`004fb530 00000000`03019ac0 00000000`00000000 : Qt5WidgetsVBox!QApplicationPrivate::notify_helper+0x112
00000000`004fb430 00000000`61475038 : 00000000`004ff490 00000000`023ea2e0 00000000`03019ac0 00000000`027ef800 : Qt5WidgetsVBox!QApplication::notify+0x1c4b
00000000`004fbb20 00000000`614753d1 : 00000000`03019ac0 00000000`03019a60 ffffffff`ffffff00 00000000`023ea2e0 : Qt5CoreVBox!QCoreApplication::notifyInternal2+0xa8
00000000`004fbb80 00007fff`3f5bcb2f : 00000000`023ea308 00000000`00000000 00000000`027ef640 00000000`004fbc30 : Qt5CoreVBox!QCoreApplicationPrivate::sendPostedEvents+0x231
00000000`004fbc30 00000000`614bd362 : 00000000`00000401 00000000`00000000 00000000`004fbce9 00000000`00000000 : qwindows!qt_plugin_instance+0x268f
00000000`004fbc60 00007fff`b735e7e8 : 00000000`00000001 00000000`004fbdf4 00000000`00000000 00000000`80000012 : Qt5CoreVBox!QEventDispatcherWin32::registerEventNotifier+0x532
00000000`004fbd50 00007fff`b735e229 : 00000000`00003dff 00000000`614bcfc0 00000000`00160d1c 00000000`00000401 : user32!UserCallWinProcCheckWow+0x2f8
00000000`004fbee0 00000000`614bed14 : 00000000`614bcfc0 00000000`027ef601 00000000`00000000 00000000`00000000 : user32!DispatchMessageWorker+0x249
00000000`004fbf60 00007fff`3f5bcb09 : 00000000`027ef640 00000000`00000024 00000000`004ff301 00000000`004ff300 : Qt5CoreVBox!QEventDispatcherWin32::processEvents+0x494
00000000`004ff2b0 00000000`6147205d : 00000000`027efd40 00000000`00000014 00000000`023ea2e0 00000000`027f85a0 : qwindows!qt_plugin_instance+0x2669
00000000`004ff2e0 00000000`61475e52 : 00000000`023efae0 00000000`00000000 00000000`023ea2e0 00000000`02303341 : Qt5CoreVBox!QEventLoop::exec+0x1cd
00000000`004ff360 00007ff6`b27a19e5 : 00000000`00000001 00000000`00000001 00000000`02303341 00000000`00000009 : Qt5CoreVBox!QCoreApplication::exec+0x152
00000000`004ff3d0 00007ff6`b27a1c81 : 00000000`00000001 00000000`00a880c0 00000000`00000000 00007fff`b82347b1 : VirtualBox!TrustedMain+0x335
00000000`004ff610 00007ff6`b28985ce : 00000000`00000001 00000000`00a881c0 00000000`00000000 00000000`00a880c0 : VirtualBox!TrustedMain+0x5d1
00000000`004ff6b0 00007ff6`b2896907 : 00000000`005039c4 00000000`00000000 00000000`00000000 00000000`00000000 : VirtualBox!TrustedMain+0xf6f1e
00000000`004ff730 00007fff`b8077034 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : VirtualBox!TrustedMain+0xf5257
00000000`004ff7e0 00007fff`b8262651 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x14
00000000`004ff810 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21


THREAD_SHA1_HASH_MOD_FUNC:  9d2090dc3709b14b4102aa77ed02b6f35ae1bfb2

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  c3edc6b6a6c9a6952d68b9bc3ca54986bf0cefaa

THREAD_SHA1_HASH_MOD:  838d5827d3d3c48cbd82674a2e0e7da4368e0351

FOLLOWUP_IP: 
Qt5GuiVBox!QRasterPaintEngine::transformChanged+1e
00007fff`25d9384e 8388b803000040  or      dword ptr [rax+3B8h],40h

FAULT_INSTR_CODE:  3b88883

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  Qt5GuiVBox!QRasterPaintEngine::transformChanged+1e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Qt5GuiVBox

IMAGE_NAME:  Qt5GuiVBox.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  58e261e1

STACK_COMMAND:  ~0s ; .ecxr ; kb

BUCKET_ID:  FATAL_USER_CALLBACK_EXCEPTION_Qt5GuiVBox!QRasterPaintEngine::transformChanged+1e

FAILURE_EXCEPTION_CODE:  c000041d

FAILURE_IMAGE_NAME:  Qt5GuiVBox.dll

FAILURE_MODULE_NAME:  Qt5GuiVBox

FAILURE_FUNCTION_NAME:  QRasterPaintEngine::transformChanged

FAILURE_PROBLEM_CLASS:  FATAL_USER_CALLBACK_EXCEPTION

FAILURE_SYMBOL_NAME:  Qt5GuiVBox.dll!QRasterPaintEngine::transformChanged

FAILURE_BUCKET_ID:  FATAL_USER_CALLBACK_EXCEPTION_c000041d_Qt5GuiVBox.dll!QRasterPaintEngine::transformChanged

TARGET_TIME:  2021-11-13T18:23:33.000Z

OSBUILD:  19042

OSSERVICEPACK:  1348

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt SingleUserTS

USER_LCID:  0

OSBUILD_TIMESTAMP:  2000-02-23 00:01:56

BUILDDATESTAMP_STR:  191206-1406

BUILDLAB_STR:  vb_release

BUILDOSVER_STR:  10.0.19041.1.amd64fre.vb_release.191206-1406

ANALYSIS_SESSION_ELAPSED_TIME:  57d0

ANALYSIS_SOURCE:  UM

FAILURE_ID_HASH_STRING:  um:fatal_user_callback_exception_c000041d_qt5guivbox.dll!qrasterpaintengine::transformchanged

---------

}}}

"	0xc0000022
20653	VirtualBox 6.1.26 fails to boot FreeBSD 13.0 install ISO in EFI mode	other	VirtualBox 6.1.26	defect	2021-11-09T11:59:11Z	2021-11-09T11:59:11Z	2021-11-09T11:59:11Z	VirtualBox 6.1.26 fails to boot FreeBSD 13.0 install ISO in EFI mode (https://download.freebsd.org/ftp/releases/ISO-IMAGES/13.0/FreeBSD-13.0-RELEASE-amd64-disc1.iso). However, with old version 6.1.10, I was able to boot this ISO in EFI mode. BIOS boot is working with both versions.	Thomas Dreibholz
20644	Whonix Workstation is not working	other	VirtualBox 6.1.28	defect	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
20633	VM Crashed	other	VirtualBox 6.1.28	defect	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
20631	Panic in 6.1.28 attempting to boot minix3 ISO cdrom image	other	VirtualBox 6.1.28	defect	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
20629	6.1.28 kernel trace on 5.15.0-0-rc3	other	VirtualBox 6.1.28	defect	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
20599	my vbox show an error when I try save machine. What is the problem???	other	VirtualBox 6.1.26	defect	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
20608	Crash on resume machine . Please fix this bug[[BR]]	other	VirtualBox 6.1.26	defect	2021-10-16T07:15:06Z	2021-10-18T20:43:02Z	2021-10-18T20:43:02Z	"Crash on resume machine with 3d enabled and host driver nvidia installed[[BR]]
Please fix this bug[[BR]]
Please fix this bug[[BR]]
Please fix this bug[[BR]]
Please fix this bug[[BR]]
Please fix this bug[[BR]]
Please fix this bug[[BR]]
Thank.[[BR]]
"	Sizy458
20616	[Feature request] Marking about the changed snapshot in group view	other	VirtualBox 6.1.26	enhancement	2021-10-17T12:43:06Z	2021-10-17T12:43:06Z	2021-10-17T12:43:06Z	"Hi All.

If I select a group, then see information only about the snapshot of the first virtual machine in the group:

[[Image(https://i.postimg.cc/qNRHQHnM/group.png)]]

[[Image(https://i.postimg.cc/9RjWLNC8/first.png)]]

But the snapshot of the second virtual machine is changed, and in the group viewing it is not visible:

[[Image(https://i.postimg.cc/hzMHVCj7/second.png)]]

Can you do anything like this?

[[Image(https://i.postimg.cc/v4d3Hr8R/final.png)]]

In a nutshell: I would like that when I selected a group, information about all snapshots of virtual machines would be displayed on the right, and not just about the first one."	Butcher
20604	Crash on application	other	VirtualBox 6.1.26	defect	2021-10-13T18:21:54Z	2021-10-15T15:40:47Z	2021-10-15T15:40:47Z	"I install last virtualbox addition with direct3d,[[BR]]

then i have fix crash on certain windows function.[[BR]]
Example : when i want configure directx by explorer.
[[BR]]
Example : When i launch visual studio 2017 and i exit it , then[[BR]]
i have crash dump devenv.exe[[BR]]
I denied disable 3d acceleration i have need.[[BR]]

"	Sizy458
20597	Running VBox in a VM that's running under VBox	other	VirtualBox 6.1.26	defect	2021-10-07T00:09:42Z	2021-10-07T07:49:40Z	2021-10-07T07:49:40Z	"Hi,

I have a VM that duplicates the Native Host I'm running; Fedora Core 36 (x86_64, Rawhide.

The only difference is that the VM has the ""latest"" kernel. My objective was to test that VB would support the new kernel.

I was playing with VB under VB and noticed several problems which make me ask if this config is supported.

1) The VM is x86_64 but NO x86_64 systems were listed in the first screen where the system name and system type are listed.

2) The create VM UI complained that acceleration is not supported but I didn't see any way to disable it.

3) The first level VM has only 2G allocated and the second level VM would only allow 2GB to be selected. I tried setting something else but the UI didn't want to forget my first selection.

4) The type of networking would only offer NATed networks.

Thanks,

Obiewan...
"	George R. Goffe
20586	VirtualBox additions: VMSVGA display is not resizable	other	VirtualBox 6.1.26	defect	2021-10-01T07:32:21Z	2021-10-01T09:05:27Z	2021-10-01T09:05:27Z	"When I select the VMSVGA display, I can't resize the display. VirtualBox additions are installed.

Additionally, selecting VBoxVGA or VBoxSVGA gives a compatibility warning.

I have also noticed that Google Chrome runs noticeable slower when I use the VBox--- display drivers, whereas it runs very well with the (not resizeable) VMSVGA driver"	paaguti-u
266	Process priority selectable...	other	VirtualBox 1.3.8	enhancement	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
20514	Networking is not functional under OPENSTEP 4.2/Mach for Intel	other	VirtualBox 6.1.26	defect	2021-08-20T03:26:00Z	2021-09-02T11:21:01Z	2021-09-02T11:21:01Z	"Being the lead developer of GNUstep it is sometimes useful to have OPENSTEP on hand.  Recently I installed OPENSTEP on virtualbox 6.1.97 (not sure why this is not listed in the versions dropdown).   The AMD PCNet 32 adapter which VirtualBox presents is detected, but it is not usable.   Oddly, under VMware it is useable but VMware doesn't support VESA display modes so networking works, but little else does on VMware.

The files you will need to install OPENSTEP are here...

https://openstep.bfx.re/

I would prefer to keep using VirtualBox as it is open source.  Please see if you guys can fix this. I have not tried 6.1.26, but I am certain it is not functioning there either."	GNUstepLeadDev
20530	Request Ability To Share Smartcard With Host and Guest	other	VirtualBox 6.1.26	enhancement	2021-08-31T15:09:38Z	2021-08-31T15:09:38Z	2021-08-31T15:09:38Z	Currently, VMWare Player is the only known software that allows the ability to share the USB smartcard reader with the host while still allowing the guest to read the smartcard. Virtualbox takes the smartcard away from the host and only allows the guest to see it when you attempt to activate the smartcard reader on the guest. With certain Windows security settings enabled, this effectively causes the host to immediately lock the screen, preventing the user from doing anything. I request to add this feature that has been long-supported in VMWare Player where the Host and Guest are able to share a connected smartcard.	Capt_Ahab
20158	"VirtualBox falsely claims that using hyperthreaded cores is an ""invalid setting"""	other	VirtualBox 6.1.18	defect	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
20458	Is kernel 5.14.0-0.rc0.20210709gitf55966571d5e.14.fc35.x86_64 supported?	other	VirtualBox 6.1.22	defect	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
20486	When I download an 18GB file	other	VirtualBox 6.1.26	defect	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
20460	host freeze in bridge network mode	other	VirtualBox 6.1.22	defect	2021-07-15T23:54:29Z	2021-07-15T23:56:14Z	2021-07-15T23:56:14Z	"I used to use bridge network mode with no issues... but now with my new laptop I faced this issue immediately after start up any host with bridge network mode 


in NAT everything is fine

I'm wondering it's because of wifi card 

"	mohdforever
20445	debian packages use version number in package name	other	VirtualBox 6.1.22	defect	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
20430	VirtualBox does not uninstall correctly under Fedora 34 (dnf/PackageKit)	other	VirtualBox 6.1.22	defect	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
20426	Pestaña de Aceptar No Activada	other	VirtualBox 6.1.22	defect	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
20384	VM not staring, was working perfectly two months ago.	other	VirtualBox 6.1.22	defect	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
20360	VB launches for two seconds then closes	other	VirtualBox 6.1.22	defect	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
20351	SNMP Issues & Mgmt	other	VirtualBox 6.1.22	defect	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
20332	Intel i7 2600K CPU	other	VirtualBox 6.1.22	defect	2021-05-01T07:06:53Z	2021-05-01T07:06:53Z	2021-05-01T07:06:53Z	"Hello, I am running the latest virtual box (6.1.22) on an old intel i7 2600K CPU. The motherboard is gigabyte p67a-ud7 with virtualization enabled on the bios.  I am using gns3 2.2.20.  Below is the error message when powering up the gns3 VM.  Thanks.

Appreciate your help.


Failed to open a session for the virtual machine GNS3VM.

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}

"	Eugene Crujido
20326	Server 2019 guest hangs	other	VirtualBox 6.1.20	defect	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
20327	No instala máquina virtual de windows Server	other	VirtualBox 6.1.20	defect	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
20319	Just installed v6.1.20's guest additions freezes Mac OS X El Capitan v10.11.6 guest VM & then host.	other	VirtualBox 6.1.20	defect	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
20301	vboxmanage startvm fails if new Linux Kernel is installed	other	VirtualBox 6.1.18	defect	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
20292	Trackpad and mouse failure on using trackpad gestures in Gnome 40	other	VirtualBox 6.1.18	defect	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
20243	All Virtual Machine freeze when loading into OS	other	VirtualBox 6.1.18	defect	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
20207	EFI: Incorrect behavior of ExitBootServices	other	VirtualBox 6.1.18	defect	2021-02-19T17:00:21Z	2021-03-19T19:46:01Z	2021-03-19T19:46:01Z	"After executing ExitBootServices function, all CPUs except boot one should be initial state. In current version of EFI, CPUs continue to execute EFI firmware code. If you then overwrite data structures assigned for page tables, then crash will occur.
Log fragment: 
00:00:10.797876 Guest CPUM (VCPU 1) state: 
00:00:10.797878 eax=00000640 ebx=00000000 ecx=3e8aaa00 edx=00000000 esi=3ed6d01a edi=3e8a8440
00:00:10.797879 '''eip=3ed6d05f esp=3ed6cf80''' ebp=00000000 iopl=0         nv up di nt zr ac po cy"	shmkv
20250	Guru Meditation on virtualbox	other	VirtualBox 6.1.18	defect	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
20259	Trouble shotting with connecting Print (forced reboot)	other	VirtualBox 6.1.18	defect	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)	other	VirtualBox 6.1.18	defect	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
20242	VBox Hangs when trying to create VM with 2 CPUs using a Ubuntu cloud image	other	VirtualBox 6.1.18	defect	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
20229	Windows10 will not boot after upgrading to 6.1.18	other	VirtualBox 6.1.18	defect	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
20227	Screen locks up during POST	other	VirtualBox 6.1.18	defect	2021-02-25T17:05:36Z	2021-02-25T17:05:36Z	2021-02-25T17:05:36Z	"ID 32
ID 455 
Codes"	Miles
20203	VirtualBox crashing	other	VirtualBox 6.1.18	defect	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
20195	error relaunching Virtual Box VM Process	other	VirtualBox 6.1.18	defect	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
20177	NtCreateFile(\Device\VBoxDrvStub) failed	other	VirtualBox 6.1.18	defect	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
20186	Program need tools for obsfucate logs and send it to developers.	other	VirtualBox 6.1.18	enhancement	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."	Дмитро
20184	VirtualBox - Ubuntu (20.04.1) error	other	VirtualBox 6.1.18	defect	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
20172	boot issues	other	VirtualBox 6.1.18	defect	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
20125	Loggin vboxdrv.sh fills syslog	other	VirtualBox 6.1.16	defect	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
20139	stealing focus while installing extension pack	other	VirtualBox 6.1.16	enhancement	2021-01-20T09:39:22Z	2021-01-20T09:39:22Z	2021-01-20T09:39:22Z	"When installing new version of VirtualBox and updating Extension Pack, then appropriate dialog will appear. After accepting licence conditions, password input dialog will appear and AFTER that also another dialog box with big yellow star, that is telling about current process: title is ""Extensions: installing extension..."" and content is also ""Installing extension pack..."". That lastly appeared dialog with big yellow star will steal the focus from password input dialog and additional password field dialog window activation is required to proceed. It makes quite often additional hassle and is quite disturbing. Don't see any benefit to show that additional window."	Edmund Laugasson
20122	Ayuda para mac	other	VirtualBox 6.1.16	defect	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
20120	Guest container crashes	other	VirtualBox 6.1.16	defect	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
20117	Kernel 5.11 RC2: Error building modules with mainline kernel 5.11 RC2	other	VirtualBox 6.1.16	defect	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
20101	I can't stat my virtual box machine	other	VirtualBox 6.1.16	defect	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
10676	mount.vboxsf does not support generic userspace mount options (nofail)	other	VirtualBox 4.1.16	defect	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
20052	Unable to start any VM since BigSur installation	other	VirtualBox 6.1.16	defect	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
20093	ubuntu doesnt starts	other	VirtualBox 6.1.16	defect	2020-12-14T05:34:49Z	2020-12-14T05:34:49Z	2020-12-14T05:34:49Z	coming black screen after starting the ubuntu os	mrun
20086	VM crashed when updating Windows 10 guest	other	VirtualBox 6.1.16	defect	2020-12-08T18:39:35Z	2020-12-10T04:38:41Z	2020-12-10T04:38:41Z	See the logs attached.	fandrei
9223	A running VM is listed as Powered Off	other	VirtualBox 4.0.10	defect	2011-07-18T10:23:36Z	2020-12-09T21:30:58Z	2020-12-09T21:30:58Z	"I have a VM that has been running for 11 days, but VBoxManage showvminfo and the VirtualBox Manager window both report that is it powered off.

The machine is working perfectly AFAICT (its console is alive and processes are running in it).

# ps -wwo lstart,command 6686
                 STARTED COMMAND
Wed Jul  6 12:45:57 2011 /usr/lib/virtualbox/VirtualBox --comment barker --startvm 91b05e8b-b485-49cb-849c-eb5dfed6dcf6 --no-startvm-errormsgbox

# VBoxManage showvminfo barker | grep State
State:           powered off (since 2011-07-06T10:44:00.000000000)

The log contains thousands of messages like this:

199:10:30.740 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={12f4dcdb-12b2-4ec1-b7cd-ddd9f6c5bf4d} aComponent={Session} aText={Failed to query the session machine (NS_ERROR_CALL_FAILED)}, preserve=false
"	mlw
19935	"When I try to install Windows Server 2019 with ISO, it goes to ""guru meditation state""."	other	VirtualBox 6.1.14	defect	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
20083	Import VM buttons below screen sized 1280x800	other	VirtualBox 6.1.16	defect	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
20072	uninstall option missing from help menu	other	VirtualBox 6.1.16	defect	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
20065	VM Starting with grey screen	other	VirtualBox 6.1.16	defect	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
20060	Unable to read complete notification	other	VirtualBox 6.1.16	defect	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
20057	long loading initial ramdisk virtualbox	other	VirtualBox 6.1.16	defect	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
20049	Испорченный образ Guest Addition Addon	other	VirtualBox 6.1.16	defect	2020-11-18T21:11:55Z	2020-11-18T21:11:55Z	2020-11-18T21:11:55Z	Отсутствует компонент NTDLL.DLL:NtQueryObject в файле VBoxWindowsAdditions.exe	IBw
19953	Cannot boot Windows 10 guest on OS X El Capitan host.	other	VirtualBox 6.1.14	defect	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
20001	i can not start 64bit installation	other	VirtualBox 6.1.16	defect	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
19983	critical eror occured while runing vm and vm stopped	other	VirtualBox 6.1.16	defect	2020-10-20T17:22:00Z	2020-10-20T17:22:00Z	2020-10-20T17:22:00Z		sebibala
19919	6.1.14 BSOD when VM starts	other	VirtualBox 6.1.14	defect	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
19970	memory could not be written error	other	VirtualBox 6.1.14	defect	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
19964	Address violation crash	other	VirtualBox 6.1.10	defect	2020-10-13T13:18:38Z	2020-10-13T13:18:38Z	2020-10-13T13:18:38Z	"I'm having some address violation crashes on my virtual machine:

Host OS: Windows 10
Guest OS: Windows 10

The crash occurs when i try to make a audio call from microsoft teams, on a remote (rdp) machine inside the guest OS.

Here is the log"	point
19958	I double click on Virtual Box and it does not open	other	VirtualBox 6.1.14	defect	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
19944	SIGSEGV on poweron	other	VirtualBox 6.1.14	defect	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
19941	virtualbox 6.1.14 on Ubuntu 20.04 (5.4.0-48-generic)	other	VirtualBox 6.1.14	defect	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
19928	VirtualBox hangs on shutdown	other	VirtualBox 6.1.14	defect	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
19925	"RTEXITCODE handleControlVM(HandlerArg *)"" at line 622 of file VBoxManageControlVM.cpp"	other	VirtualBox 6.1.14	defect	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
19874	Failed to create a host network interface	other	VirtualBox 6.1.14	defect	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
19861	Windows XP 32bit does not start	other	VirtualBox 6.1.10	defect	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
19858	Unable to resize guest window with multi-monitor	other	VirtualBox 6.1.10	defect	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
19846	VIRTUALBOX 6.1.6	other	VirtualBox 6.1.6	defect	2020-08-31T13:04:38Z	2020-08-31T13:15:16Z	2020-08-31T13:15:16Z	"Salve,gentilmente ho un problema in WINDOWS10 di installazione nuova versione, in poche parole non posso piu aggiornare Vb perche manga il file VirtualBox-6.1.6-r137129-Win.msi, non riesco piu ha trovarlo non ce lo piu, quindi non posso installare la nuova versione e neanche disistallare, ho fatto pure uno sbaglio ho cancellato alcuni file cartelle e file di registro manualmente senza risolvere il problema, non mi era mai capitato un problema del genere, il file.MSI lo scaricato da voi,e non lo trovo piu
se cortesemente mi potete aiutare ha trovare il file .MSI oppure mi date una soluzione, nelle faq non ho trovato la soluzione."	Tris
19826	Can only attach USB Scanner 1st Time Virtual Machine started	other	VirtualBox 6.1.10	defect	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
19822	Constant and varied problems installing ubuntu VM from Windows host	other	VirtualBox 6.1.10	defect	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
19808	Cannot get my VM to run with	other	VirtualBox 6.1.10	defect	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
19414	ljmp (mem48) fails	other	VirtualBox 6.1.4	defect	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
19810	"Can not run any VM's ""Error relaunching VirtualBox VM process: 5"""	other	VirtualBox 6.0.14	defect	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
17849	Error Relaunching VirtualBox VM Process:5	other	VirtualBox 5.2.14	defect	2018-07-02T16:22:53Z	2020-08-13T00:54:53Z	2020-08-13T00:54:53Z	Cannot start any VM of Virtual Box	Andres0910
19798	Can't load my document	other	VirtualBox 6.1.10	defect	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
19784	Win10 Quick Assist screen-share shows corrupted desktop	other	VirtualBox 6.1.4	defect	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
19710	Problem to start VM Virtual Box	other	VirtualBox 6.1.10	defect	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
19776	Linux Mint 20 Vir Box 6.1 cant turn off Hardware Virtualization	other	VirtualBox 6.1.10	defect	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
19757	Referenced memory at 0x000000... yadayadayada	other	VirtualBox 6.1.10	defect	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
19770	impossible to start restored machine	other	VirtualBox 6.1.10	defect	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
19745	Add emulation for x86, ARM guests	other	VirtualBox 6.1.10	defect	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
19707	Add ability to sort and group virtual computers with tags	other	VirtualBox 6.1.10	enhancement	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
19698	System Boot	other	VirtualBox 6.1.10	defect	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
12456	Failed to Delete Snapshot	other	VirtualBox 4.3.4	defect	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
18613	Oracle account got not merged with the correct VirtualBox account	other		task	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
19661	virtual sanal makine hatası önemlid	other	VirtualBox 6.1.10	defect	2020-06-12T04:37:12Z	2020-06-15T07:49:32Z	2020-06-15T07:49:32Z	Merhaba, görsel ektedir.	ferittrn
19222	Guest OS Windows 7 have 0x116 BSOD	other	VirtualBox 6.1.0	defect	2020-01-14T10:00:04Z	2020-06-15T02:07:49Z	2020-06-15T02:07:49Z	"play online video with chrome. and then open applications which consume a lot of system resource. we will find 0x116 BSOD easily.

while reboot, OS will hang windows logo. re-start it. have no minidump .
i will upload kernel dump if needed."	ramboliu
19648	VirtualBox mounts the same ISO in multiple virtual CD/DVD drives.	other	VirtualBox 6.1.10	defect	2020-06-09T10:16:39Z	2020-06-10T08:11:54Z	2020-06-10T08:11:54Z	"Related discussion topic, with logs. https://forums.virtualbox.org/viewtopic.php?f=8&t=98545

We've actually been seeing this error for years, but I can't find a ticket for it.

Users sometimes get confused and add a new CD/DVD drive to the VM recipe, instead of adding media to a drive.

If they do that while the GAs ISO is mounted in CD drive #1, then I believe that the next time they choose ""Insert Guest Additions CD"" in a running VM, VirtualBox sees the empty drive and inserts a second copy of the GAs ISO in drive #2, not noticing that drive #1 still holds a copy. That leaves you with the same media mounted in two CD drives, which obviously could never happen in the physical world. VirtualBox gets more confused from there, and users sometimes compound the problem by having this invalid state recorded in past snapshots. Once this happens the only known workaround is to manually edit the .vbox file.

Obviously, it should never be possible to mount the same media in more than one CD/DVD drive. I can think of a multitude of trivially easy ways to stop that happening, so I'm sure you will too.

Logs can be found in the linked discussion topic."	mpack
19618	No hardware acceleration on Ryzen7 4800HS	other	VirtualBox 6.1.8	defect	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
19601	virtio-scsi issue feedback	other	VirtualBox 6.1.8	defect	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
15152	Cannot unsubscribe from notifications for a single issue	other	VirtualBox 5.0.14	defect	2016-02-17T16:14:31Z	2020-05-15T12:18:28Z	2020-05-15T12:18:28Z	"The bugtracker needs a mechanism to unsubscribe from a single issue.

EG: If I write a one-line platform-specific issue confirmation, I don't necessarily want ongoing play-by-play notifications five years later when someone reopens the issue.

I am solving this by emptying my email preference for the time being.  I'll re-enter it in the future if I again have specific bugs that I'd like to track."	Justice
19563	A critical error has been occurred while running virtual machine and the machine execution has stopped	other	VirtualBox 6.1.6	defect	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
19543	WinVerifyTrust failed to start virtualbox 5.x.x	other	VirtualBox 5.2.40	defect	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	other	VirtualBox 5.2.40	defect	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
19534	Adding USB devices has useless serial number	other	VirtualBox 6.1.6	defect	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
18640	xoBV tag memory leak	other	VirtualBox 6.0.6	defect	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
19519	Add CloneVDI features to VirtualBox itself	other	VirtualBox 6.1.6	enhancement	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
17524	Various VBox binaries use a SHA1-timestamped SHA2 signature	other	VirtualBox 5.2.6	enhancement	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
17828	Can't move media due to out of memory errors	other	VirtualBox 5.2.12	defect	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
19472	Update from VirtualBox 5.2 to 6.1.4 errors	other	VirtualBox 6.1.4	defect	2020-04-08T19:17:32Z	2020-04-08T19:17:32Z	2020-04-08T19:17:32Z	I ran the VirtualBox 5.2 .run uninstall, which said it completed normally.  I then ran the VirtualBox6.1.4 .run and it said it installed fine.  VBoxManage -v indicates VirtualBox5.2 is still installed and the VirtualBox Manager does not look like the 6.1.4 version I have on another machine.  The Host machine is Centos6.7 and the guests I had on it were also Centos6.7	njmontfort
19468	VirtualBox 6.1.4 New Cloud VM (OCI) wizard public network radio button doesn't work	other	VirtualBox 6.1.4	defect	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
19467	VirtualBox 6.1.4 New Cloud VM (OCI) wizard does not handle errors gracefully	other	VirtualBox 6.1.4	defect	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
19447	Getting error when trying to install the virtualbox extension pack	other	VirtualBox 6.0.18	defect	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
19446	Virtualbox 6.1.4 r136177. -under MacOS Catalina - Host Only Does not work	other	VirtualBox 6.1.4	defect	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
19435	Critical error on boot of KISS linux - enters Guru meditation	other	VirtualBox 6.1.4	defect	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
14176	Failed to open a session for the virtual machine	other	VirtualBox 4.3.28	defect	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
19403	Why??? if i deactivated why can't i save ???	other	VirtualBox 6.1.4	defect	2020-03-15T06:42:25Z	2020-03-15T06:58:32Z	2020-03-15T06:58:32Z	https://imgur.com/d7BYRWu	Fe-lipelinux
19402	GuruMeditation in a simple hobby operating system	other	VirtualBox 6.1.0	defect	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
19401	Virtualbox host Windows 10 - CRASH	other	VirtualBox 6.1.4	defect	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
477	Hardware breakpoints don't work in Virtualbox (software virtualization only)	other	VirtualBox 3.1.6	defect	2007-07-02T14:32:40Z	2020-03-04T10:11:20Z	2020-03-04T10:11:20Z	"It seems that doesn't work setting hardware breakpoints in Virtualbox (Olly Debugger).
[Hardware, on Execution]
WinXP guest"	marius_mtm
5036	Guru Meditation -2304 (VERR_REM_TOO_MANY_TRAPS) when running warcraft 1's setup	other	VirtualBox 6.0.12	defect	2009-09-19T00:16:43Z	2020-03-04T09:58:25Z	2020-03-04T09:58:25Z	"Guest: Dos6.22 with soundblaster16 drivers installed
When starting warcraft 1's setup.exe to configure the audio, vbox crashes.
This is 100% reproducable.
"	Neighbour
19375	Crash bsod on guest machine	other	VirtualBox 6.1.4	defect	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
11160	.ova image created with Virtual Box, failed to import in VMware	other	VirtualBox 4.2.4	defect	2012-11-05T20:32:18Z	2020-03-03T15:45:33Z	2020-03-03T15:45:33Z	"The image can be imported into Virtual Box without any problems.

VMware fails:
{{{
The import failed because /home/user/Whonix-Gateway.ova did not pass OVF
specification conformance or virtual hardware compliance checks.

Click Retry to relax OVF specification and virtual hardware compliance
checks and try the import again, or click Cancel to cancel the import.
If you retry the import, you might not be able to use the virtual machine
in VMware Player.
}}}

Who is responsible for the bug? VMware or Virtual Box?

VMware Bug report:
http://communities.vmware.com/thread/423920

Download link Whonix-Gateway.ova:
http://sourceforge.net/projects/whonix/files/whonix-0.4.5/
 
project website:
http://whonix.sf.net

Source code:
https://github.com/adrelanos/Whonix

How the .ova image is created:
https://github.com/adrelanos/Whonix/blob/master/whonix_createvm"	Tsso
19304	MSDOS MODE freezes under 98 SE in VBox on latest version	other	VirtualBox 6.1.2	defect	2020-02-12T19:36:19Z	2020-02-12T19:36:19Z	2020-02-12T19:36:19Z	"Example:

https://youtu.be/GWq_it8qLc0"	ned33
19287	gcc10 problems	other	VirtualBox 6.1.2	defect	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)
18030	EXC_BAD_ACCESS (SIGSEGV) on macOS 10.14 (Mojave) if trying to start Windows 10 Guest	other	VirtualBox 5.2.18	defect	2018-10-04T09:06:30Z	2020-02-05T02:46:25Z	2020-02-05T02:46:25Z	"Process:               VirtualBoxVM [748]
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 [747]
Responsible:           VirtualBoxVM [748]
User ID:               501

Date/Time:             2018-10-04 10:52:39.613 +0200
OS Version:            Mac OS X 10.14 (18A391)
Report Version:        12
Bridge OS Version:     3.0 (16P375)
Anonymous UUID:        F0AE1762-A39B-8B31-FA72-EBFAC4B9E51B

Sleep/Wake UUID:       1526540A-27B6-482C-8AB3-864E562E4740

Time Awake Since Boot: 4400 seconds
Time Since Wake:       380 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 0x0000000000000010
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Segmentation fault: 11
Termination Reason:    Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [748]

VM Regions Near 0x10:
--> 
    __TEXT                 0000000103da3000-0000000103dc5000 [  136K] r-x/rwx SM=COW  /Applications/VirtualBox.app/Contents/MacOS/VirtualBoxVM

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   VirtualBox.dylib              	0x00000001044383e4 0x104338000 + 1049572
1   VirtualBox.dylib              	0x000000010441c3b3 0x104338000 + 934835
2   VirtualBox.dylib              	0x000000010471b8dd 0x104338000 + 4077789
3   org.qt-project.QtCoreVBox     	0x0000000104f36808 QMetaObject::activate(QObject*, int, int, void**) + 3048"	rharting
19253	Guest Additions not installing on Win 10 Pro 1903	other	VirtualBox 6.1.2	defect	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
19247	Accessability Bug: Certain user interface elements are not accessible with the keyboard.	other	VirtualBox 6.0.14	defect	2020-01-21T14:08:35Z	2020-01-21T14:08:35Z	2020-01-21T14:08:35Z	"Defect:  Certain user interface elements are not accessible with the keyboard.

Description: Please see the examples for details.

Notes: This defect may exist elsewhere within the application. 

Expected result: All interactive user interface elements are expected to be accessible via the keyboard. 

Reference: This defect is a failure against Section 508, 2.1.1 – Keyboard.

For more information, see the following link:
http://www.w3.org/TR/UNDERSTANDING-WCAG20/keyboard-operation-keyboard-operable.html

Steps to reproduce:

1.	Launch the application “VirtualBox v6.0.14”
2.	Press “Alt” to access the toolbar.
3.	Go to File>> Preferences
4.	Use the Arrow Keys to Navigate to “Network” Menu.
5.	Attempt to navigate to the side buttons “Add new NAT network”, “Removes selected NAT network” and “Edits selected NAT network”.

Example 1: Notice when the user attempts to access side buttons on the “Network” menu, they are not able to access it through the keyboard.

 


Example 2: of the Extensions Tab within the same Preferences Window:


6.	Tab to the “Extensions” Menu
7.	Attempt to navigate to the side buttons “Adds new package” and “Removes selected package”.

Notice when the user attempts to access the side buttons on the “Extensions” menu, they are not able to access it through the keyboard.

 










"	moshekaplan
19204	Virtualbox Manager Crashes when moved to 2nd monitor on Linux Host.	other	VirtualBox 6.1.0	defect	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
19206	Crash of VirtualBoxVM running ReactOS 0.4.12 guest on macOS 10.14.6 host	other	VirtualBox 6.1.0	defect	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
18296	mtype multiattach does not work	other	VirtualBox 6.0.0	defect	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
19164	WindowsXP guest 3D acceleration	other	VirtualBox 6.1.0	defect	2019-12-16T10:33:01Z	2019-12-16T10:33:01Z	2019-12-16T10:33:01Z	"It is a weird corner usecase nowadays but still. It is impossible to enable 3d acceleration support in XP. Guest additions installation have 3D acceleration feature grayed out, it says I need to have 256MB of vram assigned to the guest. But...

First: If I choose WinXP in the machine settings dialog it only let me enable 3D acceleration with VBoxVGA adapter and 128 of vram.

Second: Even if I lie and choose Win7 and VBoxSVGA 256MB, the guest addition setup doesn't change and still has this option grayed out. Yet the system recognizes that video adapter has 256MB of vram.

I've tried it in safemode also with no luck.
"	GnomeUser
19162	The virtual machine 'Windows XP' has terminated unexpectedly during startup with exit code 1 (0x1)	other	VirtualBox 6.0.14	defect	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)	other	VirtualBox 6.0.14	defect	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
19143	usb busy with previous request	other	VirtualBox 6.0.14	defect	2019-12-10T22:05:30Z	2019-12-14T22:49:29Z	2019-12-14T22:49:29Z	i have installed the extension pack, i still get the issue, i could not find vboxusb.inf i found vboxusb.sy i could not find uppperfilters on my windows registry.	foreign
19096	bug keyboard	other	VirtualBox 6.0.14	defect	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
19098	DR-DOS/Caldera-OpenDOS-7.01 floppy images not recognized	other	VirtualBox 6.0.14	defect	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)
19052	split of the soapC.cpp file triggers internal GCC 9+ bug	other	VirtualBox 6.0.14	defect	2019-10-29T11:40:12Z	2019-10-29T11:42:03Z	2019-10-29T11:42:03Z	"The split of the soapC.cpp file triggers an apparent internal bug in GCC 9+
Disabling the split makes the compilation succeed:

{{{
/home/ws/vbtrunk/trunk/out/linux.amd64/debug/obj/webservice/soapC-1.cpp: In function ‘int soap_putelement(soap*, const void*, const char*, int, int)’:
/home/ws/vbtrunk/trunk/out/linux.amd64/debug/obj/webservice/soapC-1.cpp:19905: internal compiler error: in subspan, at input.h:68
19905 | SOAP_FMAC3 int SOAP_FMAC4 soap_putelement(struct soap *soap, const void *ptr, const char *tag, int id, int type)
      | 
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://bugzilla.redhat.com/bugzilla> for instructions.
Preprocessed source stored into /tmp/cc6m3qIX.out file, please attach this to your bugreport.
kmk: *** [/home/ws/vbtrunk/trunk/kBuild/footer-pass2-compiling-targets.kmk:277: /home/ws/vbtrunk/trunk/out/linux.amd64/debug/obj/vboxsoap/gen/webservice/soapC-1.o] Error 1
}}}
Build system details that saw this bug:

1) Fedora 32 (Workstation Edition) Rawhide
{{{
$ uname -a ; gcc -v
Linux oradesk 5.4.0-0.rc4.git3.1.fc32.x86_64 #1 SMP Thu Oct 24 13:28:33 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-redhat-linux/9/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-redhat-linux
Configured with: ../configure --enable-bootstrap --enable-languages=c,c++,fortran,objc,obj-c++,ada,go,d,lto --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-shared --enable-threads=posix --enable-checking=release --enable-multilib --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-gnu-unique-object --enable-linker-build-id --with-gcc-major-version-only --with-linker-hash-style=gnu --enable-plugin --enable-initfini-array --with-isl --enable-offload-targets=nvptx-none --without-cuda-driver --enable-gnu-indirect-function --enable-cet --with-tune=generic --with-arch_32=i686 --build=x86_64-redhat-linux
Thread model: posix
gcc version 9.2.1 20190827 (Red Hat 9.2.1-1) (GCC) 
}}}

2) OpenSuse Tumbleweed:
{{{
Linux hpbox 5.2.8-1-default #1 SMP Fri Aug 9 17:51:51 UTC 2019 (bf37e83) x86_64 x86_64 x86_64 GNU/Linux
CPE_NAME=""cpe:/o:opensuse:tumbleweed:20190814""
gcc -v
Using built-in specs.
COLLECT_GCC=cc
COLLECT_LTO_WRAPPER=/usr/lib64/gcc/x86_64-suse-linux/9/lto-wrapper
OFFLOAD_TARGET_NAMES=hsa:nvptx-none
Target: x86_64-suse-linux
Configured with: ../configure --prefix=/usr --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib64 --libexecdir=/usr/lib64 --enable-languages=c,c++,objc,fortran,obj-c++,ada,go,d --enable-offload-targets=hsa,nvptx-none=/usr/nvptx-none, --without-cuda-driver --disable-werror --with-gxx-include-dir=/usr/include/c++/9 --enable-ssp --disable-libssp --disable-libvtv --disable-cet --disable-libcc1 --enable-plugin --with-bugurl=https://bugs.opensuse.org/ --with-pkgversion='SUSE Linux' --with-slibdir=/lib64 --with-system-zlib --enable-libstdcxx-allocator=new --disable-libstdcxx-pch --enable-libphobos --enable-version-specific-runtime-libs --with-gcc-major-version-only --enable-linker-build-id --enable-linux-futex --enable-gnu-indirect-function --program-suffix=-9 --without-system-libunwind --enable-multilib --with-arch-32=x86-64 --with-tune=generic --with-build-config=bootstrap-lto-lean --enable-link-mutex --build=x86_64-suse-linux --host=x86_64-suse-linux
Thread model: posix
gcc version 9.1.1 20190723 [gcc-9-branch revision 273734] (SUSE Linux) 
}}}
3) OpenSuse Tumbleweed:
{{{
Linux hpbox 5.3.7-1-default #1 SMP Mon Oct 21 06:03:17 UTC 2019 (3eea5a9) x86_64 x86_64 x86_64 GNU/Linux
gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib64/gcc/x86_64-suse-linux/9/lto-wrapper
OFFLOAD_TARGET_NAMES=hsa:nvptx-none
Target: x86_64-suse-linux
Configured with: ../configure --prefix=/usr --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib64 --libexecdir=/usr/lib64 --enable-languages=c,c++,objc,fortran,obj-c++,ada,go,d --enable-offload-targets=hsa,nvptx-none=/usr/nvptx-none, --without-cuda-driver --disable-werror --with-gxx-include-dir=/usr/include/c++/9 --enable-ssp --disable-libssp --disable-libvtv --disable-cet --disable-libcc1 --enable-plugin --with-bugurl=https://bugs.opensuse.org/ --with-pkgversion='SUSE Linux' --with-slibdir=/lib64 --with-system-zlib --enable-libstdcxx-allocator=new --disable-libstdcxx-pch --enable-libphobos --enable-version-specific-runtime-libs --with-gcc-major-version-only --enable-linker-build-id --enable-linux-futex --enable-gnu-indirect-function --program-suffix=-9 --without-system-libunwind --enable-multilib --with-arch-32=x86-64 --with-tune=generic --with-build-config=bootstrap-lto-lean --enable-link-mutex --build=x86_64-suse-linux --host=x86_64-suse-linux
Thread model: posix
gcc version 9.2.1 20190903 [gcc-9-branch revision 275330] (SUSE Linux) 
}}}

### sledgehammer Workaround in LocalConfig.kmk[[BR]]
### disable webservices build with:
{{{
VBOX_WITH_WEBSERVICES :=
}}}

Text string: soapC-1.cpp
{{{
  File         Line
0 Makefile.kmk 245 $(VBOXWEB_OUT_DIR)/soapC-1.cpp \
1 Makefile.kmk 812 $(VBOXWEB_OUT_DIR)/soapC-1.cpp \
}}}
from: trunk/src/VBox/Main/webservice/Makefile.kmk
{{{
236   ifdef VBOX_WITHOUT_SPLIT_SOAPC
237    vboxsoap_SOURCES = \
238         $(VBOXWEB_OUT_DIR)/soapC.cpp
239   else
240    BLDPROGS += split-soapC
241    split-soapC_TEMPLATE = VBoxBldProg
242    split-soapC_SOURCES = split-soapC.cpp
243 
244    vboxsoap_SOURCES = \
245         $(VBOXWEB_OUT_DIR)/soapC-1.cpp \
246         $(VBOXWEB_OUT_DIR)/soapC-2.cpp \
[..]
807 ifndef VBOX_WITHOUT_SPLIT_SOAPC
808 #
809 # Split up the soapC.cpp monster into manageable bits that can be
810 # built in parallel and without exhausting all available memory.
811 #
812 $(VBOXWEB_OUT_DIR)/soapC-1.cpp \
813 + $(VBOXWEB_OUT_DIR)/soapC-2.cpp \
814 + $(VBOXWEB_OUT_DIR)/soapC-3.cpp \
815 + $(VBOXWEB_OUT_DIR)/soapC-4.cpp \
[...]
841 : $(VBOXWEB_OUT_DIR)/soapC.cpp $$(split-soapC_1_TARGET) | $$(dir $$@)
842         $(RM) -f -- $(wildcard $(VBOXWEB_OUT_DIR)/soapC-?.cpp $(VBOXWEB_OUT_DIR)/soapC-??.cpp)
843         $(split-soapC_1_TARGET) $(VBOXWEB_OUT_DIR)/soapC.cpp $(VBOXWEB_OUT_DIR) 29
844 endif # !VBOX_WITHOUT_SPLIT_SOAPC
}}}

### disabling the split works reasonably well and compiles [[BR]]
### successfully on a 16GB memory/12 cpu cores system and[[BR]]
### on a 16GB memory/2 CPUs system despite the comment.

$ cat LocalConfig.kmk 
{{{
VBOX_WITHOUT_SPLIT_SOAPC := 1
}}}
"	Frank Batschulat (Oracle)
19032	bad display of IE	other	VirtualBox 6.0.14	defect	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
17509	Add ArcaOS as IBM OS/2 Version Type	other	VirtualBox 5.2.6	enhancement	2018-01-29T10:06:10Z	2019-10-19T00:39:31Z	2019-10-19T00:39:31Z	"Now that ArcaOS is out I think it would be good to add it to the GUI as an IBM OS/2 version.
It works great in VirtualBox and should be added to the list."	wbpayne
18991	QCOW2: Compressed images	other	VirtualBox 6.0.12	defect	2019-10-08T15:19:28Z	2019-10-09T07:19:27Z	2019-10-09T07:19:27Z	"Adding a compressed QCOW2 image as a hard disk to VirtualBox will work, but actually reading from the disk will fail silently.

== Expected behavior ==
If the QCOW2 image is using an unsupported feature, my expectation would have been that I get a corresponding information.

How to reproduce:
* Download any QCOW2 image from http://download.opensuse.org/tumbleweed/appliances/ (all of them seem to be using compression)
* Use this image as a boot disk for a virtual machine
 * ""FATAL: No bootable medium found! System halted.""
* When using / viewing the image as a secondary disk it will show up as an empty disk filled with zeros.
 * Writing to the disk (e.g. using `cfdisk`) will correctly prompt

   
{{{
The I/O cache encountered an error while updating data in medium ""ahci-0-2"" (rc=VERR_NOT_SUPPORTED). Make sure there is enough free space on the disk and that the disk is working properly. Operation can be resumed afterwards.
}}}
"	laenion
18977	"All VM's on VirtualBox  goes to ""Guru Meditation state "" when KVM(virt-manager) VM's are 'power on'"	other	VirtualBox 6.0.12	enhancement	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
18929	NS_ERROR_INVALID_ARG (0x80070057)	other	VirtualBox 6.0.12	defect	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
18903	VirtualBox does not start when docked	other	VirtualBox 6.0.10	defect	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
18895	Gray out, don't rearrange, disabled buttons	other	VirtualBox 6.0.10	defect	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
18894	Allow deleting running VMs	other	VirtualBox 6.0.10	enhancement	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
18889	Detect elementaryOS as Ubuntu 64-Bit	other	VirtualBox 6.0.10	enhancement	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
18887	I´ll try to initiate de sesion for install a windows XP and fail	other	VirtualBox 6.0.10	defect	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
18865	Prompt to assign another UUID when already exists.	other	VirtualBox 6.0.10	enhancement	2019-08-24T22:37:50Z	2019-08-28T10:08:39Z	2019-08-28T10:08:39Z	"This happens when I move and rename 'D:\test\mydisk.vdi' to 'D:\ubuntu64.vdi', it doesn't detect that it's not present anymore in the old location and thinks it's duplicated.

{{{
Failed to open the disk image file D:\ubuntu64.vdi.

Cannot register the hard disk 'D:\ubuntu64.vdi' {e2855e0e-fd02-40b0-ac5e-0d8bd297f1db} because a hard disk 'D:\test\mydisk.vdi' with UUID {e2855e0e-fd02-40b0-ac5e-0d8bd297f1db} already exists.

Result Code: E_INVALIDARG (0x80070057)
Component: VirtualBoxWrap
Interface: IVirtualBox {d0a0163f-e254-4e5b-a1f2-011cf991c38d}
Callee RC: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)
}}}

I would like to have a more friendly option to either re-check if the file exists in the previous location or alternatively change the UUID of the new file. The error message which is displayed looks pretty catastrophic like some sort of kernel panic or unrecoverable error with data loss.

Currently I have to run the following command manually to fix it.

{{{
VBoxManage.exe internalcommands sethduuid 'D:\ubuntu64.vdi'
}}}
"	DeGarden
18871	User Account delete	other	VirtualBox 6.0.10	defect	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
18841	enhancement: merge title bar and menu bar	other	VirtualBox 6.0.10	enhancement	2019-08-16T06:28:16Z	2019-08-25T01:52:00Z	2019-08-25T01:52:00Z	"menu bar should reside in the title bar area, this saves 1 row of screen.
or place the menu bar in the top left icon."	Leonz
18860	Error opening	other	VirtualBox 5.2.6	defect	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
18826	Starting VirtualBox on Windows 10 gives error	other	VirtualBox 6.0.10	defect	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
18795	Hotmail messages not loaded	other	VirtualBox 6.0.10	defect	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
10275	Horizontal tilting (in certain Guests) behaves like Vertical Scrolling	other		defect	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
18785	Host Bluetooth Stops Working	other	VirtualBox 6.0.10	defect	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
18777	Virtual Box 6 Crashes Windows due to Network device error	other	VirtualBox 6.0.10	defect	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
18773	VirtualBox-6.0-6.0.10_132072_fedora29-1.x86_64 doesn't build kernel modules	other	VirtualBox 6.0.10	defect	2019-07-18T23:28:37Z	2019-07-18T23:28:37Z	2019-07-18T23:28:37Z	"VirtualBox-6.0-6.0.8_130520_fedora29-1.x86_64 works on fedora 30, but VirtualBox-6.0-6.0.10_132072_fedora29-1.x86_64 simply doesn't build kernel modules, i.e. vboxdrv, etc.

[l@HP14 ~]$ uname -a
Linux HP14.localdomain 5.1.17-300.fc30.x86_64 #1 SMP Wed Jul 10 15:20:27 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
[l@HP14 ~]$ rpm -qi VirtualBox-6.0 
Name        : VirtualBox-6.0
Version     : 6.0.10_132072_fedora29
Release     : 1
Architecture: x86_64
Install Date: Fri 19 Jul 2019 07:16:19 AM CST
Group       : Applications/System
Size        : 240110974
License     : GPLv2
Signature   : DSA/SHA1, Fri 12 Jul 2019 09:00:54 PM CST, Key ID 54422a4b98ab5139
Source RPM  : VirtualBox-6.0-6.0.10_132072_fedora29-1.src.rpm
Build Date  : Fri 12 Jul 2019 07:25:46 PM CST
Build Host  : tinderlin4.de.oracle.com
Relocations : (not relocatable)
Vendor      : Oracle Corporation
URL         : http://www.virtualbox.org/
Summary     : Oracle VM VirtualBox
Description :
VirtualBox is a powerful PC virtualization solution allowing
you to run a wide range of PC operating systems on your Linux
system. This includes Windows, Linux, FreeBSD, DOS, OpenBSD
and others. VirtualBox comes with a broad feature set and
excellent performance, making it the premier virtualization
software solution on the market.
[l@HP14 ~]$ modinfo vboxdrv
modinfo: ERROR: Module vboxdrv not found.
[l@HP14 ~]$ 

"	trlu
18769	headless on server without xserver	other	VirtualBox 6.0.10	defect	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
18759	documentation error -> fixed as of 17 July 2019 (6.0.x and later)	other	VirtualBox 6.0.8	defect	2019-07-16T12:16:11Z	2019-07-17T07:53:19Z	2019-07-17T07:53:19Z	"https://www.virtualbox.org/manual/ch08.html#vboxmanage-modifyvm

""uarttype <1-N> 16450|16550A|16750: Confgures the UART type for a virtual serial port. The default UART type is 16550A.""

Is a seperate setting, should not be a subitem under ""uartmode"".
"	jpnielsen
18757	On Windows!0 very often the VM Win10 or Win7 goes in stuck state	other	VirtualBox 6.0.8	defect	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
18747	vt-x imbricate grayed	other	VirtualBox 6.0.8	defect	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
18750	Crash / BSOD of Windows 10 host when running any VM	other	VirtualBox 6.0.8	defect	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
18732	.iso file not listed when attempting to add it to a VM	other	VirtualBox 6.0.8	defect	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
18726	Unable to export	other	VirtualBox 6.0.8	defect	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
18716	Installation on macOS 10.15 fails	other	VirtualBox 6.0.8	defect	2019-06-20T10:40:24Z	2019-06-21T23:07:22Z	2019-06-21T23:07:22Z	It is impossible to install VirtualBox to macOS 10.15	tianyl
18712	Digest mismatch (VERR_NOT_EQUAL)	other	VirtualBox 6.0.8	defect	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
18701	virtual box and multiple ubuntu 16 vagrant images have intermittent hanging problems via ssh	other	VirtualBox 5.2.30	defect	2019-06-10T06:02:44Z	2019-06-21T16:51:18Z	2019-06-21T16:51:18Z	"I frequently have an issue using the bento/ubuntu16.04 or ubuntu/xenial64 images for vagrant on mac os 10.13.6 where the ssh session will completely freeze and I cannot vagrant ssh back in.  these two images use virtual box.

since I'm able to reproduce the problem with multiple images, and I've also just reinstalled my whole os from scratch and am still getting the problem I suspect this may be a virtual box issue related to ssh.

I am using virtual box 5.2.30 which is the version required for these two images."	openfirehawk
18665	VBOX doesn't work	other	VirtualBox 6.0.6	defect	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@…
18703	VirtualBox doesn't record the video/audio on FreeBSD: the .webm file isn't saved	other	VirtualBox 6.0.8	defect	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
18698	Проблема с запуском Kali-Linux	other	VirtualBox 6.0.8	defect	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
18683	Automount of Shared folder stopped working in 6.0.8	other	VirtualBox 6.0.8	defect	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
18681	Windows 10 1903 + VirtualBox 6.0.8	other	VirtualBox 6.0.8	defect	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
18684	Mini Toolbar stop working in full srceen in 6.0.8	other	VirtualBox 6.0.8	defect	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
14271	Start/Stop VM affect PPPoE link, with bridged networking.	other	VirtualBox 5.0.0	defect	2015-07-13T20:41:18Z	2019-05-12T06:07:40Z	2019-05-12T06:07:40Z	"VBox 5.0.0 on Windows 7 host, Starting Windows XP guest with '''Bridged networking''', will hang PPPoE link of host.

It also hang PPPoE connection while Stopping VM.

If VM networking is NAT, then all well.

It didn't happened with version 4.3.28"	NoNoNo
18622	Drag-and-drop replication causes BUG	other	VirtualBox 6.0.6	defect	2019-05-05T09:37:00Z	2019-05-05T09:37:00Z	2019-05-05T09:37:00Z	"explorer.exe crash.
Please watch the video:
URL：https://pan.baidu.com/s/1Fsvxtpkum0x5YD0bnq_NLw 
Extraction code：91n9 "	SkyBlue永恒
18557	Resolution import/export too low	other	VirtualBox 6.0.4	defect	2019-04-11T05:02:07Z	2019-04-11T05:02:07Z	2019-04-11T05:02:07Z	"OS: debian 9.8
Kernel: 4.9.0-8-amd 64
proc: i3-4010U (Haswell ULT)
screen: samsung 32"" (TV screen)

When upgraded from vbox 5.x to vbox 6 (r128.413[[Image()]] i noticed that import & export screen is not ok which results is not reading all info on screen.
If all screens would be full resizable (without min size), the problem wouldn't exists, i guess...

"	peter_temp
18537	Keyboard not working in Virtual box while installing ubuntu 18.04LTS on Windows10pro on Microsoft surface	other	VirtualBox 6.0.4	defect	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
11143	vboxmanage startvm fails with E_ACCESSDENIED	other	VirtualBox 4.2.4	defect	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
18528	ISO Windows 7 SP 4 - USB visible in host, not showing up in tree	other	VirtualBox 6.0.4	defect	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
18517	"blocage VM WIN7/32bits quand utilisation ""partage"""	other	VirtualBox 6.0.4	defect	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
18498	Machine switch to power off	other		enhancement	2019-03-15T16:48:05Z	2019-03-15T16:48:05Z	2019-03-15T16:48:05Z	"My virtual machine have a virtual disk vdi file hosted in the USB external disk.[[BR]]
When this external disk is diconnected, '''no''' dialog box
""read error disk [[BR]]
Abort Retry Ignore""[[BR]]
is showing.[[BR]]

Imagine that there is a false electrical contact of a USB port to the external disk.[[BR]]
This dialog box which is not showed if for avoiding power off and restart virtual machine.[[BR]]

It would require the implementation of a dialog box Read error disk with button [[BR]]
Abort Retry Ignore, and possibility to REOPEN (fopen) the VDI file if the usb disk [[BR]]
is reconnected again.[[BR]][[BR]]
Thank.


"	Sizy458
18480	VBoxManage hangs after some parallel operations	other	VirtualBox 5.2.22	defect	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
18471	Issue with OEL 7.2 on Macbook Pro VB 5.2/6 with Guest additions	other	VirtualBox 5.2.26	defect	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
18467	Unable To Install VM's	other	VirtualBox 6.0.4	defect	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
18463	console boot hangs/highcpu without vbox serial & console=ttyS0 in grub	other	VirtualBox 6.0.4	defect	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
17980	Menuet64 network I8254X does not work anymore	other	VirtualBox 5.2.18	defect	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
15638	Win10 Guests stopped working with upgrade to 5.1.	other	VirtualBox 5.1.0	defect	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
18449	Mouse Cursor Corrupts when running Citrix Session in VirtualBox	other	VirtualBox 5.2.26	defect	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
729	If you delete an iso image,you can't remove it from the list	other	VirtualBox 1.5.0	defect	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
18386	VirtualBox 6.0 crash and make Windows reboot	other	VirtualBox 6.0.4	defect	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
18360	iMac (mojave 10.14.2) repeated panic crashes	other	VirtualBox 6.0.2	defect	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
18354	Centos guest crashes when accessed form list of VMs in VBox	other	VirtualBox 6.0.2	defect	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
1139	Feature request: wider copy/paste support, in Console for instance -> user contributions welcome	other	VirtualBox 1.5.4	enhancement	2008-01-31T19:01:59Z	2019-01-21T14:57:32Z	2019-01-21T14:57:32Z	"[This would be a candidate for user contributions, due to lack of core developer time.  See comment:42 and comment:43.]

I'd like to see a wider copy/paste support, for exemple in console without X installed (typicall server config).

Beeing able to copy/paste from/to shell would be very nice for server config work, as many server daemon use text based configuration.

Use case : 
- (on windows host) : copy a config line from a webpage
- (on linux guest, debian etch with Zsh) : open vi, then paste the config line

Another use case : 
- (on windows host) : copy a command line from a webpage
- (on linux guest, debian etch with Zsh) : paste it on the shell to execute it

Another use case : 
- (on linux guest, debian etch with Zsh)) : copy the result of a command or a log file (from tail, more, cat, whatever)
- (on windows host): paste it on a forum to seek for help

This would turn virtual box into a powerfull tool for learning server admin, or to use it as a copy of a production server where you can test modifications..."	Julien Bidault
17318	Permanent, human readable anchors in the HTML User Manual	other	VirtualBox 5.2.0	task	2017-11-28T00:35:50Z	2019-01-21T12:05:37Z	2019-01-21T12:05:37Z	"The HTML format of the user manual and the links to different chapters/sub-chapters/paragraphs, often complain anchors in a ""non-human"" format. Example the GAs for Windows vs. the GAs for Linux:
* https://www.virtualbox.org/manual/ch04.html#additions-windows
* https://www.virtualbox.org/manual/ch04.html#idm2096
That second ""idm2096"" seems like something that was automatically created. My fear is that it might change down the road, making it difficult to link to specific sections, or even worse make links invalid. Especially if new chapters/paragraphs are inserted into the manual."	Socratis
18295	VM Audio appears distorted	other	VirtualBox 6.0.0	defect	2019-01-10T13:44:10Z	2019-01-15T17:56:25Z	2019-01-15T17:56:25Z	"I have a win10 VM running in a Win7 system. 
I've activated the audio dump file and it appears distorted in the host also.
I've produced the sound by clicking on the volume slide bar and by minimizing skype window. "	gio904
18309	VirtualVox 6.0.0-127566 will not start VMs under latest Windows 10 update	other	VirtualBox 6.0.0	defect	2019-01-13T23:37:04Z	2019-01-14T00:06:21Z	2019-01-14T00:06:21Z	"When trying to start a VM it fails with:

----------------
The virtual machine 'CentOS 7.5' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\${user}\VirtualBox VMs\CentOS 7.5\Logs\VBoxHardening.log'.
-----------------

Looking in that file I find:

------------------
2598.95c: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume3\Program Files\Oracle\VirtualBox'
2598.95c: System32:  \Device\HarddiskVolume3\Windows\System32
2598.95c: WinSxS:    \Device\HarddiskVolume3\Windows\WinSxS
2598.95c: KnownDllPath: C:\WINDOWS\System32
2598.95c: supR3HardenedVmProcessInit: Opening vboxdrv stub...
2598.95c: supR3HardenedWinReadErrorInfoDevice: 'Unknown image file \Device\HarddiskVolume3\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe at 00007ff702ae0000. (rc83Exp=-91)'
2598.95c: Error -5633 in supR3HardenedWinReSpawn! (enmWhat=3)
2598.95c: NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status -5633 (0xffffe9ff) (rcNt=0xe986e9ff)
VBoxDrvStub error: Unknown image file \Device\HarddiskVolume3\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe at 00007ff702ae0000. (rc83Exp=-91)
41f8.421c: supR3HardenedWinCheckChild: enmRequest=2 rc=-5633 enmWhat=3 supR3HardenedWinReSpawn: NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status -5633 (0xffffe9ff) (rcNt=0xe986e9ff)
VBoxDrvStub error: Unknown image file \Device\HarddiskVolume3\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe at 00007ff702ae0000. (rc83Exp=-91)
41f8.421c: Error -5633 in supR3HardenedWinReSpawn! (enmWhat=3)
41f8.421c: NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status -5633 (0xffffe9ff) (rcNt=0xe986e9ff)
VBoxDrvStub error: Unknown image file \Device\HarddiskVolume3\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe at 00007ff702ae0000. (rc83Exp=-91)
------------------

Here is the info from that file about my version of Windows 10. It was updated last Tuesday.

-------------------
41f8.421c: Log file opened: 6.0.0r127566 g_hStartupLog=0000000000000070 g_uNtVerCombined=0xa0456300
41f8.421c: \SystemRoot\System32\ntdll.dll:
41f8.421c:     CreationTime:    2019-01-10T02:36:52.431995500Z
41f8.421c:     LastWriteTime:   2019-01-10T02:36:52.457392000Z
41f8.421c:     ChangeTime:      2019-01-10T03:35:31.327390500Z
41f8.421c:     FileAttributes:  0x20
41f8.421c:     Size:            0x1e7010
41f8.421c:     NT Headers:      0xe0
41f8.421c:     Timestamp:       0xe8b54827
41f8.421c:     Machine:         0x8664 - amd64
41f8.421c:     Timestamp:       0xe8b54827
41f8.421c:     Image Version:   10.0
41f8.421c:     SizeOfImage:     0x1ed000 (2019328)
41f8.421c:     Resource Dir:    0x17d000 LB 0x6ea08
41f8.421c:     [Version info resource found at 0xd8! (ID/Name: 0x1; SubID/SubName: 0x409)]
41f8.421c:     [Raw version resource data: 0x17d0f0 LB 0x380, codepage 0x0 (reserved 0x0)]
41f8.421c:     ProductName:     Microsoft® Windows® Operating System
41f8.421c:     ProductVersion:  10.0.17763.194
41f8.421c:     FileVersion:     10.0.17763.194 (WinBuild.160101.0800)
41f8.421c:     FileDescription: NT Layer DLL
41f8.421c: \SystemRoot\System32\kernel32.dll:
41f8.421c:     CreationTime:    2018-09-15T07:28:44.342269900Z
41f8.421c:     LastWriteTime:   2018-09-15T07:28:44.342269900Z
41f8.421c:     ChangeTime:      2019-01-10T03:35:31.154027900Z
41f8.421c:     FileAttributes:  0x20
41f8.421c:     Size:            0xb1380
------------------------"	Richard Sharpe
18266	I met 0X00000000 error when I click the menu->device->usb on windows system.	other	VirtualBox 6.0.0	defect	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
2935	BIOS support for booting from usb devices	other	VirtualBox 3.1.6	enhancement	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
18256	Install failure for VB6.0.0 on openSUSE Tumbleweed	other	VirtualBox 6.0.0	defect	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
18236	Screen distortion with Cadence Allegro 17.2	other	VirtualBox 6.0.0	defect	2018-12-26T21:59:25Z	2018-12-30T15:57:11Z	2018-12-30T15:57:11Z	"I have image distortions when using the Cadence Allegro circuit board design package. I'm using Windows 7 Ultimate SP1 as the guest OS on a Debian 9.6 host with an Nvidia Quattro K620 video card. I have tried various settings and Virtualbox 5.22 and 6.0 and a different video driver but that didn't improve things. The picture below is with 3D accelleration disabled. With 3D accelleration enabled it won't even draw correctly:
[[Image(https://www.eevblog.com/forum/eda/problems-running-allegro-17-2-in-virtualbox/?action=dlattach;attach=605617;image)]]

The software (trial version) and the design file can be downloaded from here:
[https://www2.orcad.com/Extranet/96712/forms.aspx?msgid=b8d688a9-82e7-4c8e-afaf-2e4366069fad&LinkID=CH00096712eR00000066AD]

"	nctnico
18217	Stealing ram	other	VirtualBox 6.0.0	defect	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
18098	Screen does not refresh when connecting over RDP	other	VirtualBox 5.2.20	defect	2018-11-03T06:38:53Z	2018-12-21T12:59:49Z	2018-12-21T12:59:49Z	"With Guest Additions 5.2.20 installed and the guest running Fedora Linux, when connecting via RDP the screen does not get refreshed when running the graphical environment. It gives the impression the guest has hung but that isn't the case. If you reconnect then the screen is updated but once again no longer refreshes.

So far this occurs both under Fedora 28 and Fedora 29 guests. I will check with other versions of Linux and other OSs as time allows.

If I downgrade the guest additions to 5.2.18 then the issue goes away. If I uninstall the guest additions then the display also works as expected but obviously without the advantages of having guest additions installed.
"	oddsocks
18193	Increase vCore limit, 32 Cores are not enough	other	VirtualBox 5.2.22	enhancement	2018-12-17T14:34:25Z	2018-12-19T09:54:06Z	2018-12-19T09:54:06Z	"Increase the CPU Limit from 32 processors to actually available cores.

The current 32 Cores Limit does not account for modern processors in combination with multisocket systems."	multicoreuser
18191	VirtualBox VM start crashes Win10 host inside a Linux KVM	other	VirtualBox 5.2.22	defect	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
7633	Add an example of scan codes for VBoxManage controlvm	other	VirtualBox 3.2.10	enhancement	2010-10-22T15:51:32Z	2018-12-16T23:41:29Z	2018-12-16T23:41:29Z	"It is not clear from the documentation how to send Ctrl-Alt-Del to a vm using 'VBoxManage controlvm'. The solution is far from obvious, but the utility is high (as witnessed by the fact that there is a command for it in the GUI console. I propose adding the following bullet to 8.11:

- VBoxManage controlvm keyboardputscancode allows you to send keystrokes to the virtual machine. This is particularly useful for virtual machines that are running headless. The keystrokes are entered as the hex values of the scancodes. To send Ctrl-Alt-Delete, use the sequence ""1d 38 53 b8 9d"".
"	Paul Hoffman
16683	DHCP Reservations	other	VirtualBox 5.1.20	enhancement	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
18178	NAT driver drops inbound retransmits that happen after FIN	other	VirtualBox 5.2.22	defect	2018-12-12T03:11:43Z	2018-12-12T14:54:15Z	2018-12-12T14:54:15Z	"In TCP, it is possible and allowed (and actually, necessary) for the sending side to retransmit after sending the FIN but before receiving a FIN from the other side.  The sending side will send a final ""window"" of TCP segments, ending with a FIN packet.  If one of those is dropped, the receiving side should ACK the most recently received packet, then the sender will retransmit.  Only after all packets are received and acknowledged should the recipient ACK the sender's FIN segment and send back its own.

Instead, guests within virtualbox seem to immediately respond to the FIN with a FIN/ACK and tear down the connection.  This means that if a segment is dropped within the final window transmission, the download is silently truncated.  It's likely a rare bug, in that it only becomes high-probability with a combination of high latency, large window sizes, and nontrivial amounts of packet loss.  With almost all TCP schedule algorithms, even small amounts of packet loss result in a very small transmission window.  The new BBR, on the other hand, tries to probe the latency and bandwidth available rather than relying on packet loss for feedback, so it's far more likely to result in a large TCP window despite some packet loss."	Elliott
18158	Windows does not start when the virtual machine is allocated 9 or more processors	other	VirtualBox 5.2.22	defect	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
18140	perte du clavier après installation virtualbox Version 5.2.22 r126460 (Qt5.6.2)	other	VirtualBox 5.2.22	defect	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
18156	MacOSX shutdown wedges VirtualBox	other	VirtualBox 5.2.22	defect	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
18141	VBoxManage usbfilter add/modify --product does not set value	other	VirtualBox 5.2.22	defect	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
18126	Guest linux fails to receive key input after X11 screen appears on resume from saved state.	other	VirtualBox 5.2.22	defect	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
18112	VirtualBox crash on start ReactOS with BTRFS	other	VirtualBox 5.2.20	defect	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
18110	Unable to save window state	other	VirtualBox 5.2.20	defect	2018-11-06T03:23:40Z	2018-11-06T07:31:53Z	2018-11-06T07:31:53Z	On the KALI system, the state of the window could not be saved. Every time you click the close button on the window, after you close the program, you need to right-click the display toolbar.	meiying
18103	User-manual amendment regarding DHCP IP / NAT networking	other	VirtualBox 5.2.20	enhancement	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
18096	Download froze	other	VirtualBox 5.2.20	defect	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
12894	Deleted snapshots leave removable media attached	other	VirtualBox 4.3.10	defect	2014-03-31T10:22:54Z	2018-11-03T06:41:37Z	2018-11-03T06:41:37Z	"When taking a snapshot, removable media such as DVD images or floppy disks images are also referenced as part of that snapshot. However, deleting the snapshot still leaves the media attached to the snapshot and it can't be released or removed. This was done under Linux version 4.3.10 but the issue has been around for a while as far as I can tell.

For example:

1. Create a new guest, with a floppy drive controller
2. Attach a floppy disk image as drive a:
3. Take an offline snapshot of the guest
4. Edit the new guest's settings, and remove the floppy disk image
5. Delete the snapshot of the guest.

Go to the VMM and highlight the floppy disk image, it will still show it as being attached and it can't be released. This can be worked-around (on Linux at least) by doing

/etc/rc.d/init.d/vboxdrv restart

which obviously unloads and reloads the kernel modules, releasing the disk image.


When using the API, querying a floppy image for example to see what it's attached to, generates an invalid object reference, presumably the IMachine or ISnapshot reference no longer exists. Using the API I've tried to detach the disk before deleting the snapshot, but I can't because the IMachine reference returned by the ISnapshot class is immutable. Also using IMachine::MountMedium with a null medium reference doesn't work.

I suspect that IConsole::DeleteSnapshot should be taking care of releasing any removable media attached to the snapshot.

"	oddsocks
18063	Disk encryption causes guest to crash	other	VirtualBox 5.2.20	defect	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
18061	Choosing 64-bit Windows 7 machine, once I launch it the OS is 32-bit	other	VirtualBox 5.2.20	defect	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
18043	Virtual box starts up in the background	other	VirtualBox 5.2.18	defect	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
18038	Mouse Integration Bug Windows 10 April 18 Host - Pointer In Wrong Location	other	VirtualBox 5.2.18	defect	2018-10-08T09:10:53Z	2018-10-10T08:24:54Z	2018-10-10T08:24:54Z	"I have a VirtualBox Host running Windows 10 April 2018 Update, with a Guest VM also running Windows 10 April 2018, both configured to use the same 2 screens @ 1920x1080, both scaled to 100%.

I am running VirtualBox 5.2.18 with Guest Additions 5.2.18

Since the Guest was updated to April 2018 I have been unable to get Mouse Integration to work properly.

In Mouse Integration mode the Mouse Cursor is visible in the Guest but is showing at the wrong location. If I click bottom left corner on the Windows Start menu it correctly locates the click point and shows the Start Menu. However, as I move the Mouse around the screens the location of the Click Point drifts to the right(i.e the actual Point on the virtual screen moves progressively farther away to the right as I move across the screen, whilst the Mouse Cursor tracks as normal).

This has only started happening since the Guest OS was updated to Windows April 2018.

If I turn Mouse Integration off the Mouse Cursor and click Point behave correctly, which is usable but not ideal."	C0dif0rn1c4t10n
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?	other	VirtualBox 5.2.18	defect	2018-10-05T12:14:22Z	2018-10-06T00:40:34Z	2018-10-06T00:40:34Z		turi
17988	Change Group Fails - Forward-slash in VM name (host: Windows 64-bit)	other	VirtualBox 5.2.18	defect	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
14272	When VM run, Wacom_Tablet.exe consume much more memory	other	VirtualBox 5.0.0	defect	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
14499	vboxmanage guestcontrol never returns / hangs	other	VirtualBox 4.2.32	defect	2015-08-25T21:52:48Z	2018-08-28T13:20:04Z	2018-08-28T13:20:04Z	"We are running the following command in an automated test environment:

vboxmanage guestcontrol name_of_vm execute --image /bin/ls --verbose --wait-exit

It prints out ""0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%"", but never returns (kind of like this ticket: https://www.virtualbox.org/ticket/10616). We run /bin/ls to determine when the virtual machine has finished loading so we can run a test in the machine with another vboxmanage command.

We are running VirtualBox 4.2.32 on Xubuntu 14.04 with a virtual machine that is also Xubuntu 14.04. It should be noted that this also happens with VirtualBox 4.3.30"	mdriscoll
14765	Drag and Drop failure	other	VirtualBox 5.0.8	defect	2015-10-29T23:33:06Z	2018-08-28T12:30:16Z	2018-08-28T12:30:16Z	"Window manager is openbox 3.5.2.
File manager is spacefm 1.0.4
host is win7 64bit, fully updated
guest is gentoo linux 64bit, kernel version 4.0.9

Attempting to drag a file from the host to the guest never starts. The cursor never changes from the ""can't do that here"" icon. Releasing the drag while over the spacefm window has no effect. Guest additions are installed and started, copy paste works, both shared clipboard and drag and drop are set to bidirectional. Haven't tried guest to host.

Logs are attached, but the relevant portions are these, I think:

host

{{{
00:01:05.858907 DnD: Offered formats to guest:
00:01:05.858939 DnD: 	text/uri-list
}}}

guest

{{{
23:01:43.560189 00007ff0ea600780 main     DnD: Started
23:01:43.560215 00007ff0ea600780 main     DnD: 5.0.8_OSEr103449
23:02:10.685773 00007ff0ea600780 main     DnD: Entered new window 0x1000013 ('/home/myusername/Desktop'), supports Xdnd version=5
23:02:10.690882 00007ff0ea57e700 dndX11   DnD: Target window 0x1000bdc ('spacefm') is asking for data as 'text/uri-list'
23:02:10.716603 00007ff0ea57e700 dndX11   DnD: Target window 0x1000bdc ('spacefm') is asking for data as 'text/uri-list'
}}}

that last line repeats whenever I move the mouse in the window until I release the drag."	gotyaoi
17944	Critical Error	other	VirtualBox 5.2.18	defect	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
17943	Windows 2000 image does not start	other	VirtualBox 5.2.18	defect	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
17875	problems with win10 1803 and virtualbox	other	VirtualBox 5.2.16	defect	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
17894	Oracle_VM_VirtualBox_Extension_Pack-5.2.16.vbox-extpack not installing	other	VirtualBox 5.2.16	defect	2018-07-27T05:42:29Z	2018-07-29T13:38:10Z	2018-07-29T13:38:10Z	"Trying to install this Extension Pack on VirtualBox 5.2.16 but getting this error:

Failed to install the Extension Pack C:/Users/Public/Downloads/VirtualBox/Oracle_VM_VirtualBox_Extension_Pack-5.2.16.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-8664' -&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}

OS: Windows 10 Pro
8GB RAM
450GB HDD (243GB free)
Using the Administrator account
Extension pack downloaded and checksum verified


"	erch
17891	Cannot Create Host-Only Network on Windows 10	other	VirtualBox 5.2.16	defect	2018-07-24T20:17:10Z	2018-07-29T07:56:33Z	2018-07-29T07:56:33Z	"VirtualBox 5.2.16
Microsoft 10 Windows Professional
Version	10.0.17134 Build 17134

Try to add host only network via GUI or command line results in failure:
{{{
  Querying NetCfgInstanceId failed (0x00000002).
  Result Code: 
  E_FAIL (0x80004005)
  Component: HostNetworkInterfaceWrap
  Interface: IHostNetworkInterface {455f8c45-44a0-a470-ba20-27890b96dba9}
}}}

Probably because of failed install; setupapi.dev.log has 
{{{
       [Device Install (UpdateDriverForPlugAndPlayDevices) - sun_VBoxNetAdp]
       Section start 2018/07/24 14:30:48.164
       cmd: C:\Windows\System32\MsiExec.exe -Embedding BA4E62E93D721D463D6D0D2C75E94A47 E Global\MSI0000
       ndv: INF path: C:\Program Files\Oracle\VirtualBox\drivers\network\netadp6\VBoxNetAdp6.inf
       ndv: Install flags: 0x00000001
  !    ndv: Unable to find any matching devices.
       Section end 2018/07/24 14:30:48.164
       [Exit status: FAILURE(0xe000020b)]
}}}

I've danced random dances for hours to about a dozen different tunes called out by various forum posters on the Interwebs; including uninstalling, reinstalling, searching for infcache.1 in vain, deleting *.pnf files, standing on one foot, spinning around, I'm a little teapot, etc.  

Please: 

  -If anyone has another ""off the top of my head did you try this"" solution, note that very similar errors to this one keep popping up going all the way back to 2011.  So whatever you were going to say, I've probably seen it already.  

  -Maybe someone at VirtualBox could duplicate the issue on their own machine, diagnose and fix it!  As I've noted, confirmed by an elementary Google search, this kind of error has an impressively long pedigree. Sometimes errors, especially if they recur for as long as this one has, are REAL and are not due to accidental circumstances fixable by Dr. Reboot and the Installers.  

  -If there is any other information I can provide that would help someone in a position to fix the issue DUPLICATE the issue, please let me know.  I am happy to help contribute to a solution by helping to frame it and gather information.  I am done trying to fix the problem through thermodynamics.  "	ggraham412
17880	AppleKeyStore: operation failed (pid: 31 sel: 7 ret: 'e00002c2 ...	other	VirtualBox 5.2.16	defect	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
17899	Fail creating machine via SOAP vboxwebsrv	other	VirtualBox 5.2.16	defect	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
17868	VirtualBox doesn't work and can't finish reinstall (but booting virtual box still works) (cant boot my vm)	other	VirtualBox 5.2.14	defect	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
17900	after install old Ubuntu 8.04 and then reboot, the virtualbox will show error	other	VirtualBox 5.2.16	defect	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
17895	Cannot create a disk image via GUI	other	VirtualBox 5.2.8	defect	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
17871	Missing installation instructions at Web site (virtualbox.org) for openSUSE 15.0 -> fixed after 5.2.16	other	VirtualBox 5.2.16	defect	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
17872	virtualbox in text-only mode (for a better Accessibility of old guest systems, especially when using a Braille display on the host)	other	VirtualBox 5.2.16	defect	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
1347	USB device reported working, but no communication	other	VirtualBox 1.5.6	defect	2008-03-18T11:51:25Z	2018-07-16T19:04:50Z	2018-07-16T19:04:50Z	"I would like to report a USB device that appears as working in the guest OS, but programs cannot communicate with it.
I am using Vista 64-bit with XP 32-bit in VirtualBox. The main reason for using virtualization is the unavailability of a 64-bit driver for a reprogrammable USB FPGA board. This little board can be programmed using a utility (Adept Suite) of the manufacturer (Digilent). I added a USB filter for this device in VirtualBox and it got detected in the guest OS and installed the correct driver for it. It appears as enabled and working in Device Manager. The utility can also detect the board and its ID. However, when it tries to communicate with it (Initialize Chain) it fails. I can confirm that this same setup with another virtualization software works and the utility can communicate to the board.
I would gladly provide any kind of dump, log or other debug data for investigation. "	Elod 
17865	Error (rc=-5640): More than one thread in process - Windows 10	other	VirtualBox 5.2.14	defect	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
17200	Disable COW for disk images on btrfs	other	VirtualBox 5.1.30	enhancement	2017-10-22T17:41:02Z	2018-06-04T21:52:50Z	2018-06-04T21:52:50Z	"Since copy-on-write (COW) feature of modern file systems (e.g. BtrFS) decreases the performance of disk images significantly, it should be turned off by default.

Therefore, I suggest adding a checkbox in the ""New VM"" and ""VM Properties"" dialogues to disable COW and set this by default.

This way, the user still has full control, nothing happens ""in the background"" without the user noticing and it is a useful default for most of the users!

See some discussion on this topic in #11862"	darkdragon
17798	help info of autostart wrong => Fixed in SVN	other	VirtualBox 5.2.12	defect	2018-06-03T06:14:21Z	2018-06-03T10:10:40Z	2018-06-03T10:10:40Z	"The help says to use --autostart on|off to toggle autostart.
But actually it should be --autostart-enabled on|off.

Another tip: The help is missing message of how to set autostop-type. "	kinlion
17763	UI Fails to start - 5.2.12 - qtcore 5.9.4	other	VirtualBox 5.2.12	defect	2018-05-14T07:22:35Z	2018-05-24T08:53:34Z	2018-05-24T08:53:34Z	"Linux 64 bit, intel Core i77-7700, Gentoo
Linux kernel 4.9.95-gentoo

Virtualbox 5.2.12 built from source using Gentoo portage.

QTcore 5.9.4 built from source using Gentoo portage.

There is no qt4 on the system, only qt5.

Tried downgrading to VirtualBox 5.1.36

Don't have any Gentoo standard options to downgrade qtcore short of unmasking qt4

Built with gcc 6.4.0

Happy to build with debug, including qtcore, or supply any info that may assist with this.

{{{
$ VirtualBox 
Qt FATAL: ASSERT failure in QCoreApplication::sendEvent: ""Cannot send events to objects owned by a different thread. Current thread 0x0x5653f2bae6d0. Receivr '' (of type 'UITaskMediumEnumeration') was created in thread 0x0x5653f2877050"", file kernel/qcoreapplication.cpp, line 563
Aborted
}}}
"	Lyall Pearce
17784	Raw-mode is unavailable courtesy of Hyper-V. (VERR_SUPDRV_NO_RAW_MODE_HYPER_V_ROOT).	other	VirtualBox 5.2.12	defect	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
17757	writev() blocks over vboxsf on Linux 4.16 guest	other	VirtualBox 5.2.12	defect	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
17753	Failed to open a session for the virtual machine	other	VirtualBox 5.2.12	defect	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
17691	Status Window for .OVA Appliance Import as .VDI shows .VMDK File Extension	other	VirtualBox 5.2.8	defect	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
17699	Error when starting VM after a snashot restore	other	VirtualBox 5.2.10	defect	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
17698	The virtual machine does not start.	other	VirtualBox 5.2.6	defect	2018-04-19T11:05:02Z	2018-04-20T17:06:07Z	2018-04-20T17:06:07Z	"Hello!
I'm not running a virtual machine. When I try to run, I get this error. What should I do? Help me please!

VT-x is not available. (VERR_VMX_NO_VMX).

Error code: E_FAIL (0x80004005)
Component: Console
Interface: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}"	Grisha00
17689	Screen zoom Bug	other	VirtualBox 5.2.6	defect	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
17667	Screen freezes above 1439p	other	VirtualBox 5.2.6	defect	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
16539	Virtualbox Manager Doesn't Refresh Groups	other	VirtualBox 5.1.14	defect	2017-03-08T09:41:33Z	2018-04-06T10:56:56Z	2018-04-06T10:56:56Z	"Hello

VirtualBox Manager doesn't combine vms into groups after grouping them via CLI.

1) Open VirtualBox Manager

2) .\VBoxManage.exe list vms
""vm1"" {34ceb1d7-6435-409f-8deb-3ce3cb7654c0}
""vm2"" {2f60107c-456b-46d3-b49a-7fc4719efa07}

3) .\VBoxManage.exe modifyvm ""vm1"" --groups ""/group1""
4) .\VBoxManage.exe modifyvm ""vm2"" --groups ""/group2""

5) Switch to VirtualBox Manager

Result: VirtualBox Manager doesn't show newly created groups.

6. Restart VirtualBox Manager
Result: VirtualBox Manager shows the groups.

Please fix the bug.

Thank you"	lystor
17665	An error, log attached	other	VirtualBox 5.2.6	defect	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
17641	VM console not displayed properly	other	VirtualBox 5.2.6	defect	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
12969	SSL authentication failed	other	VirtualBox 4.3.10	defect	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
17615	spectre v2 mitigation: lfence not serializing. switching to generic retpoline	other	VirtualBox 5.2.8	defect	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
7345	Entering Fullscreen with Guest - Disrupts Synergy	other	VirtualBox 3.2.8	defect	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
17594	Tela azul	other	VirtualBox 5.2.8	defect	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
17567	why can't played  camera video  in windows 7  guest  by  web browser  with  DirectX	other	VirtualBox 5.1.30	defect	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
17582	Guest Addition don't work with latest version of Fedora 27	other	VirtualBox 5.2.6	defect	2018-03-02T10:56:47Z	2018-03-02T10:56:47Z	2018-03-02T10:56:47Z	It is not possible to (re)install VBox Guest Additions anymore. Don't know the exact reason, added the log.	pueffl
17550	drop when creating snapshot	other	VirtualBox 5.2.6	defect	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
17568	Option to bundle installation media into exported VM	other	VirtualBox 5.2.6	enhancement	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
14883	Sound Blaster 16 Issues Located	other	VirtualBox 5.0.10	defect	2015-12-01T20:18:45Z	2018-02-23T15:57:19Z	2018-02-23T15:57:19Z	"In Dev16.cpp - sb16WriteAudio, there seems to be a complete oversight in passing any variable to indicate 8/16 bit depth audio, and also the buffer size and calculations need to be adjusted to accommodate for the 64KB standard of the 8237A DMA controller.

Please refer to line 1519 of the current build at:
https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Devices/Audio/DevSB16.cpp

Also, I have provided very organized links to official documentation in the forums at:
https://forums.virtualbox.org/viewtopic.php?f=4&t=12425&start=15#p347179

A summary of the troubleshooting measures that lead me to this can be found 2 posts later:
https://forums.virtualbox.org/viewtopic.php?f=4&t=12425&start=30#p347199

Fixes to these issues should theoretically get the long-standing major problems with SB16 emulation out of the way and get most programs and games requiring the typical SB16 features working properly."	over_clox
6930	Error: Failed to open a session for the virtual machine - session was closed before any attempt to power it on	other	VirtualBox 3.2.4	defect	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
15844	vboxmanage option to enable advertising default route for ipv6	other	VirtualBox 5.1.4	enhancement	2016-08-22T09:44:26Z	2018-02-12T17:31:41Z	2018-02-12T17:31:41Z	At the moment this can be configured only via gui, the ticket is a request to make it possible to configure advertising of the default route in NAT network config via cli (vboxmanage)	mwasilewski
17530	I can not startup my Vbox, Somo time ago changed my computer and from the DVI backups cant run the machine	other	VirtualBox 5.2.6	defect	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
17516	Ubuntu Virtual Machine Aborts	other	VirtualBox 5.2.6	defect	2018-02-01T13:17:38Z	2018-02-01T13:17:38Z	2018-02-01T13:17:38Z	I have created an Ubuntu virtual machine on my Windows 10 machine using version 5.2.6 with AddOns version 5.2.7.  I use this Ubuntu VM to connect, via vnc, to a headless ubuntu server running x11vnc server.  Prior to the 5.2.6 version, this setup worked flawlessly.  With 5.2.6, it continually aborts.  Prior to doing so, the cursor flickers rapidly, and the display is unresponsive.	kpenrose
17510	E_FAIL (0x80004005) err	other	VirtualBox 5.2.6	defect	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
6023	VHD Delete Snapshot results in corrupt virtual hard disk or double snapshot revert	other	VirtualBox 3.1.2	defect	2010-01-19T02:50:05Z	2018-01-25T20:38:49Z	2018-01-25T20:38:49Z	"1) VHD double snapshot - Restore:

Restore Snapshot (snap2) immediately followed by Delete Snapshot (snap2) has the same effect as Delete Snapshot (snap2) followed by Restore Snapshot to the parent Snapshot (snap1).  Any changes made between snap1 and snap2 are lost.

Repro steps:
 * Start with a VM having a VHD file attached that has no snapshots. (I used the Windows XP Mode VHD extracted from the 32-bit Windows XP Mode download: MD5sum= 5189623a8e5c6ff518cdd4759037f109, newly attached to a new VM and not yet booted.)
 * Take a snapshot 'Snapshot 1'
 * Boot the VM and make a change (perhaps create a file).
 * Shutdown VM
 * Take a snapshot 'Snapshot 2'
 * Select 'Snapshot 2' and 'Restore Snapshot' immediately followed by 'Delete Snapshot'
 * Boot VM and note that your change has gone: The VM has been restored back to 'Snapshot 1'

2) Virtual hard disk corruption causes BSOD and/or registry repair messages at boot.

Repro steps:
 * Start with a VM having a VHD file attached that has no snapshots. (I used the Windows XP Mode VHD extracted from the 32-bit Windows XP Mode download: MD5sum= 5189623a8e5c6ff518cdd4759037f109, newly attached to a new VM and not yet booted.)
 * Take a snapshot 'Snapshot 1'
 * Boot the VM and make a change (perhaps create a file).
 * Shutdown VM
 * Take a snapshot 'Snapshot 2'
 * Boot the VM then shutdown.
 * Select 'Snapshot 2' and 'Delete Snapshot'
 * Boot VM and note that it BSOD's or has other corruption problems."	Mark Cranness
17172	VirtualBox crashes on adding new disk to VM	other	VirtualBox 5.1.30	defect	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
17406	Failed to create a host network interface (windows10)	other	VirtualBox 5.2.4	defect	2017-12-28T17:40:59Z	2018-01-19T22:55:01Z	2018-01-19T22:55:01Z	"Feature update to Windows 10, version 1709
i click on file ->Host Network Manager
create+
I get the following error:

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}"	gdubs
17429	VM  Manager crash crash when creating new VM Machine	other	VirtualBox 5.2.4	defect	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
6979	Hard disk boot order	other	VirtualBox 3.2.4	defect	2010-06-13T10:18:04Z	2018-01-15T16:10:37Z	2018-01-15T16:10:37Z	"When you have several hard drives set in your VM and the actual boot disk is SATA or on any other controller than IDE, while you have an IDE hard drive attached, it will fail to boot. There is no way to set the controller priority in the VM settings for booting the VM. The first detected hard drive is tried, but never another if that one fails.

Here is one of the examples, though the issue describes something else too:
http://forums.virtualbox.org/viewtopic.php?f=6&t=31956
The first reply (second post) is the vital one.

It is reported for version 3.2.4, but I think this problem exists in all versions where more controllers are available. It doesn't matter which host or Guest you have. It also appears that the OS you want to boot using the boot menu (F12) may fail.

I have attached two log files, it's the same VM, one where I let it boot without intervention and it just stays on a black screen with a blinking _ and 100% CPU on one core. It tries to boot from a data VDI, it doesn't contain an OS.
The second log is where I selected the proper device (AHCI SATA drive) and got the error ""A Boot Error Occurred""."	Sasquatch
17390	"Received a ""VirtualBox Manager has stopped working"" error when I click on import appliance or ""New"""	other	VirtualBox 5.2.4	defect	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
17379	https for download.virtualbox.org is wrongly configured	other	VirtualBox 5.2.2	defect	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
17383	VirtualBox crashed with SIGABRT	other	VirtualBox 5.2.4	defect	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
16854	virtualbox does not build reproducibly	other	VirtualBox 5.1.22	defect	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
17359	Bug in VirtualBox 5.2.2	other	VirtualBox 5.2.0	defect	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
17224	VM crashes after input switch with KVM switch	other	VirtualBox 5.2.0	defect	2017-10-29T06:59:38Z	2017-12-06T23:49:33Z	2017-12-06T23:49:33Z	"Simiar to Ticker #8004, but on a Mac OS X host.

To reproduce: 
1. Start VM, wait until it starts an X server. Guest additions don't need to be installed. Make sure VM has captured the mouse.
2. Switch keyboard and mouse input to different computer with KVM switch (I'm using a SeaWit 4 port HDMI KVM switch).
3. Switch input back to VirtualBox host
4. Release the mouse from the VM and click another Window on the host to transfer focus.
5. VM aborts.

I tried to capture a core dump, but for some reason I didn't get one. I followed the instructions here exactly: https://www.virtualbox.org/wiki/Core_dump. The terminal showed ""Segmentation fault: 11"" when the VM aborted.

Host is Mac OS X 10.11.6
"	Bernie S
17355	Key fingerprint in downloads area cannot be verified	other	VirtualBox 5.2.0	enhancement	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
17249	Opening VM Settings dialog can hang (infinite loop) if column is narrow	other	VirtualBox 5.2.0	defect	2017-11-06T23:46:47Z	2017-11-30T23:53:35Z	2017-11-30T23:53:35Z	"After upgrading to virtualbox 5.2.0-1 I found that opening Settings for any VM would hang the VirtualBox process (100% CPU usage). Deleting local settings, recreating VMs, etc, did not help with this.

After building the SVN trunk locally I found that it was infinite looping in SFTreeItemView::processColumn(). The ""strOneString"" variable had become an empty string (iTextWidth == 0) but as iIdentSize > cWidth, the loop condition was always true.

I believe this bug can always be triggered if the column has been resized to a low width (ie if cWidth has a low value) and if m_enmFormat == FormatType_EllipsisEnd. Possibly under other conditions as well.

Simple patch to break out of the loop if iTextWidth == 0 attached. This fixes the problem for me."	projectgus
15324	Mouse pointer offset in Linux client => fixed in releases higher than 5.1.4	other	VirtualBox 5.0.18	defect	2016-04-20T07:06:37Z	2017-11-29T20:01:18Z	2017-11-29T20:01:18Z	"After saving the running Linux (Mint Linux 17.1, 64 bit) to disk and reloading it, the mouse pointer shows an offset: The hot spot is not at the tip of the mouse pointer but located some pixels left of it. The Linux gues was running in full screen mode at that time. 

Disabling full screen mode and resizing the window the pointer offset is fixed. The client is configured to adjust to the screen size. PS/2 emulation is used for the mouse.

Host is Windows 7 Professional 64 bit."	meixner
17327	alt tab within vm passes alt tab to windows 10	other	VirtualBox 5.1.30	defect	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
17310	virtualbox extension pack accept-license issue	other	VirtualBox 5.2.0	defect	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
4456	Direct support for ZFS would be nice	other	VirtualBox 3.0.0	enhancement	2009-07-09T17:51:44Z	2017-11-20T13:21:53Z	2017-11-20T13:21:53Z	"There are several ways in which VirtualBox could better support the use of ZFS for VDIs:

 - put each in its own dataset or zvol (a zvol is like a virtual raw device; vbox should have first-class support for using raw devices for VDIs)
 - set the recordsize of each VDI's dataset to match the preferred block size of the filesystem type that will be used with that VDI (this requires either a way to set recordsize manually at VDI creation time, or asking about what the VDI will be used for at creation time)
 - set the compression at VDI creation time, and/or at any other time
 - support for using ZFS snapshots (and rollbacks)
 - support for using ZFS clones to create copies of VDIs (and vbox should automatically change the cloned VDI's UUID)

I'm setting the host type to ""other"" because ZFS has been ported to other operating systems than just Solaris (e.g., FreeBSD)."	nicoatsun
17148	5.1.28 r117968 (Qt5.6.2) VBoxTray.exe bug	other	VirtualBox 5.1.28	defect	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
17265	Error fetching directory count. (TIFFRewriteDirectory)	other	VirtualBox 5.1.30	defect	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
17258	vbox kernel modules should be signed for OL7	other	VirtualBox 5.2.0	defect	2017-11-09T17:47:36Z	2017-11-09T17:47:36Z	2017-11-09T17:47:36Z	"For OL7 running on a server with Secure Boot installation of VirtualBox will fail:

''fslin1:/root # yum install VirtualBox-5.1
...
Running transaction
  Installing : VirtualBox-5.1-5.1.30_118389_el7-1.x86_64                                                                              1/1

Creating group 'vboxusers'. VM users must be member of that group!

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.
  Verifying  : VirtualBox-5.1-5.1.30_118389_el7-1.x86_64                                                                              1/1

Installed:
  VirtualBox-5.1.x86_64 0:5.1.30_118389_el7-1

Complete!''

The reason for failure is the absence of module signature:

''fslin1:/root # modprobe vboxdrv
modprobe: ERROR: could not insert 'vboxdrv': Required key not available''

And the module is not signed:

''fslin1:/root # cd /lib/modules/`uname -r`/misc
fslin1:/lib/modules/4.1.12-94.3.9.el7uek.x86_64/misc # ls
vboxdrv.ko  vboxnetadp.ko  vboxnetflt.ko  vboxpci.ko
fslin1:/lib/modules/4.1.12-94.3.9.el7uek.x86_64/misc # modinfo vboxdrv.ko
filename:       /lib/modules/4.1.12-94.3.9.el7uek.x86_64/misc/vboxdrv.ko
version:        5.1.30 r118389 (0x002a0000)
license:        GPL
description:    Oracle VM VirtualBox Support Driver
author:         Oracle Corporation
srcversion:     8FBD7594E804ED618ED1A07
depends:
vermagic:       4.1.12-94.3.9.el7uek.x86_64 SMP mod_unload modversions
parm:           force_async_tsc:force the asynchronous TSC mode (int)''

There is no ''''signer'''', ''''sig_key'''' & ''''sig_hashalgo'''' in the above. Would you be able to sign VBox modules accordingly?"	dbv
17243	VirtualBox COM service process doesn't exit on its own	other	VirtualBox 5.2.0	defect	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
14336	Error with copyfrom	other	VirtualBox 5.0.0	defect	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
17216	Should be able to add USB filesystem dump	other	VirtualBox 5.0.40	defect	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
16131	Dual full-screen windows both displayed on monitor 1 at boot	other	VirtualBox 5.1.8	defect	2016-10-31T12:57:27Z	2017-10-26T12:11:11Z	2017-10-26T12:11:11Z	"Running VB5.1.8 on SuSE Linux host with Windows guest(various).  The guests are configured for dual full-screen monitors.  On bootup, both screens are displayed on monitor #1.  Sometimes screen #1 is in front, sometimes screen #2 is in front.  Using View/Full-screen Mode I disable full-screen, use alt-tab to select screen #2 and drag it to monitor #2 and then re-enable full-screen.  Usually screen #2 will not accept mouse commands in order to select and drag it unless I first select screen #1 and then select screen #2.

On guests that are not configured for full-screen, the size of screen #2 is not the way that it was saved at shutdown, but instead it seems to be the size of the VB Logo startup screen and is displayed in the upper left hand corner of monitor #2.    "	Don Hughes
17201	Installing 5.2 Extension pack disables the VB Shared Folders	other	VirtualBox 5.1.30	defect	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
17133	Direct3D 7 Failure at step40 - NVIDIA GTX460	other	VirtualBox 5.1.28	defect	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
17134	Arch Linux - kernel 4.13 video problems	other	VirtualBox 5.1.28	defect	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
17124	Host Hard not recognized	other	VirtualBox 5.1.28	defect	2017-09-29T17:00:36Z	2017-09-30T17:15:31Z	2017-09-30T17:15:31Z	"To Whom It May Concern:

My name is Paul Lau, I have installed ""Virtual Box"" to assist a client to install Mac 10.5 (Guest) on Mac 10.11 (Host).  The hard drive is recognized on the 10.11, but I cannot get a ""Macintosh HD"" (His old hard drive has a 10.5.8) to be recognized on the 10.5,.  It i s rrecognized on the 10.5 using a Vantec IDE/SATA to USB 2.0.  Can you please advise?  My cell # number (706)219-1992."	pcflau
16857	VBoxNetAdp.kext conflict with tap.kext on macOS	other	VirtualBox 5.1.22	defect	2017-06-27T01:12:07Z	2017-09-28T08:34:20Z	2017-09-28T08:34:20Z	"I have both tuntaposx and virtualbox installed on my macOS 10.12.5
I found I can't access any SMB share from my macOS host to any remote host. After some investigation, I can confirm remove any of these two software will fix the smb access problem.
I posted a topic on vbox forums. [https://forums.virtualbox.org/viewtopic.php?f=8&t=83587]

There's a similar bug report about tuntaposx on [https://sourceforge.net/p/tuntaposx/bugs/25/], but  hasn't mention vbox.

I don't known which side can fix this problem, so I report it here."	yaocl
17102	Virtual Box does not list Virtual USB device (created by fallocate)	other	VirtualBox 5.1.28	defect	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
17068	AVG installation locks up Virtual Box version 5.1.26	other	VirtualBox 5.1.26	defect	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
10818	modifyhd --resize should warn users about existing snapshots	other	VirtualBox 4.1.18	defect	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
17077	DVD in OVF does not appear in imported VM	other	VirtualBox 5.1.26	defect	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
17062	Login screen not working on VBox 5.1.26	other	VirtualBox 5.1.26	defect	2017-09-08T05:05:42Z	2017-09-08T05:05:42Z	2017-09-08T05:05:42Z	"After I updated VirtualBox to version 5.1.26 the login screen is not working anymore, instead I see only a black screen. My host operating system is Windows 10 64bits updated to the latest available patches as of Sep/7/2017, my guest operating system is Oracle Linux 7 updated to the latest packages as of Sep/7/2017.
"	Arturo Aranda
12562	With dual monitor setup, VirtualBox Crashes when in seamless mode and try to a phsical monitor is removed. Win7-64 host, linux guest	other	VirtualBox 4.3.4	defect	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
6050	[feature-request] GUI: Please allow to delete branched snapshots sub-tree	other	VirtualBox 3.1.2	enhancement	2010-01-21T16:08:03Z	2017-08-29T15:25:32Z	2017-08-29T15:25:32Z	"Please allow users to delete branched snapshots sub-tree.

Currently there is no way to right-click and delete branched snapshots sub-tree.

For example, I have the following tree:

-XP

+--SP2

+----IE6

+----IE7

+----IE8

+--SP3

+----IE6

+----IE7

+----IE8

I would like to have a GUI way to delete *all* of SP3 branch, including it's sub branches/sub trees.

See attached screenshot.

-Technologov, 21.01.2010"	Technologov
17036	VBOX_WITH_EXTPACK_VBOXDTRACE fails to build with glibc >= 2.26-2.fc27	other	VirtualBox 5.1.26	defect	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
17025	Problem in Virtual Box	other	VirtualBox 5.1.26	defect	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
16995	Vb 5.1.26 can't display GUI on Solaris 10	other	VirtualBox 5.1.26	defect	2017-08-10T02:45:56Z	2017-08-19T11:42:33Z	2017-08-19T11:42:33Z	"Hi,

After I upgarded vb from 5.1.22 to 5.1.26 as root, then launched vb GUI and I received the following message on the console:

Qt WARNING: Qt: XKEYBOARD extension not present on the X server.
Qt WARNING: Qt: Could not determine keyboard configuration data from X server, will use hard-coded keymap configuration.
Qt WARNING: Qt: Failed to compile a keymap!
Qt WARNING: Current XKB configuration data search paths are:
Qt WARNING: /usr/X11/lib/X11/xkb
Qt WARNING: Use QT_XKB_CONFIG_ROOT environmental variable to provide an additional search path, add ':' as separator to provide several search paths and/or make sure that XKB configuration data directory contains recent enough contents, to update please see http://cgit.freedesktop.org/xkeyboard-config/ .
Xlib:  extension ""GLX"" missing on display ""192.168.105.10:0.0"".

After these message, I got back the command prompt.

My Solaris /etc/release shows:
                    Oracle Solaris 10 1/13 s10x_u11wos_24a X86
  Copyright (c) 1983, 2013, Oracle and/or its affiliates. All rights reserved.
                            Assembled 17 January 2013


Any suggestion?

Thanks.
ming


"	Ming H
16924	Linux 4k Display with interface scaling double Hi-DPI VirtualBox too small	other	VirtualBox 5.1.22	defect	2017-07-20T11:37:26Z	2017-07-26T11:25:18Z	2017-07-26T11:25:18Z	"Ciao! How are you?

How can I change in VirtualBox? 
[[Image(https://i.stack.imgur.com/qGEsF.png)]]

Doesn't see on the picture, but in really it is can't see anything.
Not using Linux GUI scaling."	patrikx3
16917	vb virtual display adapter not VGA Compatible	other	VirtualBox 5.1.22	defect	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
16600	Strange icon under Fedora 25 KDE	other	VirtualBox 5.1.18	defect	2017-03-23T19:53:37Z	2017-07-16T09:41:40Z	2017-07-16T09:41:40Z	"Hi,

Under Fedora 21 and VirtualBox-5.0-5.0.36_114008_fedora18-1.x86_64.rpm I have nice KDE icon.

Now I'm trying to recreate look and feen under Fedora 25.
Instead of ""blue box"" I'm getting black square with green dots.

Screenshoots attached

Regards,
Mike"	Mike446
16862	problem with eCS (OS/2) guest on copy	other	VirtualBox 4.2.36	defect	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
16730	About Qt translations.	other	VirtualBox 5.1.22	defect	2017-05-04T20:42:56Z	2017-05-04T20:42:56Z	2017-05-04T20:42:56Z	"It's not correct just to copy qt_ru.qm file. Here "".ts"" file https://github.com/qt/qttranslations/blob/5.9.0/translations/qt_ru.ts so basically you must have all qm dependencies files in ""nls"" folder.

Or use ""windeployqt"" tool, if using windeployqt not an options, here source, example how they combine all dependencies into one qt_ru.qm file  https://github.com/qt/qttools/blob/dev/src/windeployqt/main.cpp#L934"	krab
16690	calculate required temp storage and check available storage before merging snapshots	other	VirtualBox 5.1.20	defect	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
16687	2D Acceleration breaks Scaled mode (Windows 7 host, Windows XP guest).	other	VirtualBox 5.1.20	defect	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
16612	Snapshots: Inheritance of options from parent snapshot should be improved (wishlist?)	other	VirtualBox 5.1.18	defect	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
16594	Apple trackpad bluettooth doen't work anymore	other	VirtualBox 5.1.18	defect	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
16560	Multiple password prompts for encrypted drives	other	VirtualBox 5.1.16	defect	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
16387	virtualbox 5.1 not reading properly certain box.ovf files?	other	VirtualBox 5.1.12	defect	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
16535	High CPU on Host while Low CPU on Guest	other	VirtualBox 5.1.14	defect	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
16534	Unable to detach media from past snapshot that causes warnings	other	VirtualBox 5.1.14	enhancement	2017-03-06T18:20:13Z	2017-03-06T19:31:24Z	2017-03-06T19:31:24Z	"Hello world :-)

In VirtualBox 5.1.14 macOS I have noticed that after removing a local ISO file I get this warning on unavailable media. But I am unable to remove this media from the list as it is attached to a past snapshot in one of my machines. So I had to revert the machine state in order to detach the missing image. This caused loss of work progress that I had on the machine I had to revert..

I think it should be possible to detach (missing) media images even from past snapshots..

Best regards,
Tomek"	CeDeROM
16522	Failed to open sessions after update to vm 5.1.14 on windows 7 sp1	other	VirtualBox 5.1.14	defect	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
16491	Problem with Open Semantic Desktop Search	other	VirtualBox 5.1.14	defect	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
16063	"Any immediate ""VBoxManage modifyvm"" commands after detaching a dvd drive fail with 'The machine 'vm_name' is already locked for a session'"	other	VirtualBox 5.1.6	defect	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
16468	Unable to fix the mislocated vboxguestadditions.iso file in Virtual Media Manager.	other	VirtualBox 5.1.14	defect	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
16443	Weston doesn't render a cursor.	other	VirtualBox 5.1.14	defect	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
16007	Allow overriding existing snapshots	other	VirtualBox 5.1.6	enhancement	2016-10-01T12:38:28Z	2017-01-30T15:21:01Z	2017-01-30T15:21:01Z	Currently, you can only specify a new snapshot from the Virtual Box VM menu. I think it would make sense if a window opens where you can select to override a snapshot, delete snapshots or create new ones.	Tobias (:Tobbi) Markus
16390	Problem with graphic interface	other	VirtualBox 5.1.10	defect	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
16345	fatal error while FreeBSD VM is configuring network interface for IPv6	other	VirtualBox 5.1.12	defect	2017-01-02T00:09:59Z	2017-01-02T00:23:54Z	2017-01-02T00:23:54Z	"fatal error while FreeBSD VM is configuring network interface for IPv6
The network interface is 'bridged' to my real nic.

I'm installing pfSense 2.4beta latest snapshot and configuring a 6to4 or 6rd on the wan nic.

Logs attached."	PiBa-NL
15281	Windows 7 guest hangs reading hard disk	other	VirtualBox 5.0.16	defect	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
13053	VirtualBox linked cloned machine (link lost when deleted)	other	VirtualBox 4.3.12	defect	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
16294	Snapshot confirmation after closing virtual machine	other	VirtualBox 5.1.10	defect	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
16269	Extension pack won't load - Windows 10	other	VirtualBox 5.1.10	defect	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
16225	When I Change Network setting to “Bridge” Mode, Virtual Machine isn't available again.	other	VirtualBox 5.1.10	defect	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
16223	Can't install VirtualBox on Windows 10	other	VirtualBox 5.1.10	defect	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
12382	Very slow guest OS performance when Windows XP Guest guest has more than 1 VCPU	other	VirtualBox 4.3.2	defect	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
16193	Need a way to save machien state when Windows 10 restarts automatically	other	VirtualBox 5.1.8	defect	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
16183	Add a warning if user running VirtualBox isn't in group vboxusers on Linux hosts	other	VirtualBox 5.1.8	enhancement	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
16179	BSOD after Update	other	VirtualBox 5.1.8	defect	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
16160	Add option to not return immediately after a contolvm command	other	VirtualBox 5.1.8	enhancement	2016-11-06T16:27:07Z	2016-11-06T16:27:07Z	2016-11-06T16:27:07Z	"While running VBoxManage from various systemd unit scripts, I found the following problem:

Systemd service commands like ExecStop return immediately, for example:

{{{
ExecStop=/usr/bin/VBoxManage controlvm MyVBoxVM acpipowerbutton
}}}

The above command will send an ACPI power down signal, which will cause the guest OS to start a shutdown procedure (if configured properly).

BUT

Systemd will see that the PID is still alive (since the guest OS is still powering down) and immediately issue a KILL signal to end the VM process. Thus, the guest OS will not have shutdown cleanly.

A temporary solution, is to create a dedicated shutdown script, which waits and constantly checks if the VM has shutdown or not, before returning. A better solution, would be to add a new parameter to VBoxManage that tells VBoxManage not to return immediately, like:

{{{
ExecStop=/usr/bin/VBoxManage controlvm MyVBoxVM acpipowerbutton noImmediateReturn
}}}

This will make VirtualBox more friendly with systemd units.

Thank you.
"	VirtualBarista
16152	ShCrOpenGL crashes in 5.1.8(including test build revision 111724) but not in 5.1.6 when activating input method framework in Ubuntu 16.04	other	VirtualBox 5.1.8	defect	2016-11-05T14:20:03Z	2016-11-06T00:39:04Z	2016-11-06T00:39:04Z	"== Reproduce Steps ==
This isn't too reproduce-friendly as most people doesn't uses IM Frameworks, however it happened to be reproduced on my [Custom Ubuntu VM Virtual Applicance project](https://github.com/Not-That-Ubuntu-Taiwan-Community/Ubuntu-TW-VM), and I also exported and released an Open Virtualization Archive recently!  So you may grab & import the 1.7GB VM and having the pretty much same guest system to reproduce this issue on :).  Here's the steps:

1. Import & launch the VM
2. The login screen will require you to manually set a new password by asking twice, then login to the X session.
3. Open the ""dash"" screen(an UI element in Unity DE, refer: https://help.ubuntu.com/stable/ubuntu-help/unity-dash-intro.html )
4. Hold-press-release the Control + Space key conbination

== Symptoms ==
* (Most of the time) VM crashes with ""ShCrOpenGL[19586]: segfault at 2d0 ip 00007fc1af685c90 s
p 00007fc16e42a9f8 error 4 in libc-2.23.so[7fc1af5e7000+1bf000]"" in system log
* (Very few) VM doesn't crash, however the UI of the IM Framework display abnormally

== Other Information ==
=== Operating System ===
Ubuntu 16.04LTS AMD64

=== Host Graphics ===
Intel Graphics on a NVIDIA Optimus Laptop(NVIDIA chip not enabled)

=== Mesa 3D ===
Stock version from Ubuntu 16.04 archive

=== Locale ===
zh_TW.UTF-8
"	林博仁(Buo-Ren, Lin)
16148	CAINE 8 VGA does not work fine	other	VirtualBox 5.1.8	defect	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
16098	VirtualBox Version 5.1.8 r111374 (Qt5.6.1) does not remember screen size	other	VirtualBox 5.1.8	defect	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
16083	VBox/Devices/EFI/Firmware/VBoxPkg/VBoxVgaDxe/Edid.c:401: bad sizeof ?	other	VirtualBox 5.1.8	defect	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
16044	version problem	other	VirtualBox 5.1.6	defect	2016-10-07T15:09:34Z	2016-10-07T15:26:31Z	2016-10-07T15:26:31Z	"inicio normal absurdo,en otras versiones no necesitabamos inicio con desacople.
el arranque de las vm´s en modo normal arroja :

The virtual machine 'other windows' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\tard.sebas\VirtualBox VMs\SERVER2003\Logs\VBoxHardening.log'.

y existen problemas con las auto-capturas de teclado y raton..no deja que esteen ambos en modo auto captura



lo unico bueno de estas versiones nuevas es que se puede configurar la vm´s estando encendida "	tard.sebas
16031	Video capture on 4K monitors is broken; bitrate too low producing blurry video	other	VirtualBox 5.0.26	defect	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
13466	VBox 4.3.16 dies when laptop w/ external monitor undocks	other	VirtualBox 4.3.16	defect	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
15963	VBoxSVC continues to run after closing Virtualbox manager / wakes host PC	other	VirtualBox 5.1.6	defect	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
14895	iscsi connection to QNAP failure / infinite loop	other	VirtualBox 5.0.10	defect	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
5582	Suggestion: allow disk image data to be aligned in VDI files, for optimal use with SSDs	other	VirtualBox 3.0.12	enhancement	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
15690	Error trying to run	other	VirtualBox 5.1.2	defect	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
15742	Problem with Full Screen Mode Guest windows 10  PRO 64B Update 2 1511	other	VirtualBox 5.1.2	defect	2016-08-03T19:56:54Z	2016-08-10T09:43:04Z	2016-08-10T09:43:04Z	"Problem to switch to full screen Mode with key Host + F max resolution is 1024x768

the driver monitor resolution display does not appear in view all modes 

Unistall Virtualbox 5.1.2 and install version 5.0.26 works correctly
"	Mike02
15746	At times when virtualizing a windows OS explorer not updating view	other	VirtualBox 5.1.2	defect	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
15756	Virtual USB Drive information	other	VirtualBox 5.1.2	enhancement	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
15766	Windows 10 - Black Screen After Logic	other	VirtualBox 5.1.2	defect	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
15410	USB driver issue	other	VirtualBox 5.0.20	defect	2016-05-11T16:33:14Z	2016-07-29T13:30:21Z	2016-07-29T13:30:21Z	"Hi guys.

New version  5.0.20 brought me unexpected problem with my ST-link device. I couldn't attach my stm32discovery board to my  guest Win 7 (64-bit). I tried usb filters and reinstalling drivers on my Win 7. No result. VirtualBox detects ST-Link attaced to my host OS X,  but don't give an access  to guest system. By that, I mean it doesn't attach it to the guest system. Next click, when I try to attache it again, VirtualBox show error ""Virtualbox failed to attach the usb device ....."".   Nothing helps. Only after I moved to version 5.0.16 I got it back. 

Please check it and do something. 
I don't wanna stay out of date. =( "	n0bd0y042
15657	File drag from linux host to windows vm when filename has colon causes error	other	VirtualBox 5.1.0	defect	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
15377	Delayed handling of mouse button	other	VirtualBox 5.0.20	defect	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
15376	"Keyboard key sticks in ""down"" state, cannot be cleared"	other	VirtualBox 5.0.20	defect	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
15548	PC speaker passthrough uses frequency tone from previous call	other	VirtualBox 5.0.22	defect	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
15591	Windows 10 and Host Only Networking	other	VirtualBox 5.0.24	defect	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
15520	vbox/src/VBox/Devices/Network/slirp/resolv_conf_parser.c:476: bad test ?	other	VirtualBox 5.0.22	defect	2016-06-17T14:19:59Z	2016-06-17T18:38:26Z	2016-06-17T18:38:26Z	"vbox/src/VBox/Devices/Network/slirp/resolv_conf_parser.c:476]: (warning) Logical conjunction always evaluates to false: EXPR == ' ' && EXPR == '\t'.

Source code is

    while (*psz && *psz == ' ' && *psz == '\t')

"	dcb
15449	No way to get DHCP-assigned IP address of natnetwork guest without guest additions	other	VirtualBox 5.0.20	defect	2016-05-26T18:16:06Z	2016-05-26T18:16:06Z	2016-05-26T18:16:06Z	It should be possible using showvminfo or a similar mechanism to get the IP address assigned to a guest, without requiring the guest to have the guest additions installed.	AxelFontaine
15408	Interaction between VboxManage and Node.JS	other	VirtualBox 5.0.20	defect	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
15407	VboxManage slash/backslash handling	other	VirtualBox 5.0.20	defect	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
15406	VBoxManage copyto file->file rather odd	other	VirtualBox 5.0.20	defect	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
15388	Please enable HTTPS for downloads	other	VirtualBox 5.0.20	defect	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
15382	Failed to create the host-only adapter	other	VirtualBox 5.0.20	defect	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
15359	20% clock drift in the guest	other	VirtualBox 5.0.18	defect	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
15364	USB shadowing to a temp drive (USB boot drive testing capability)	other	VirtualBox 5.0.18	enhancement	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
15340	Mac OS X operating system running virtual box with Ubuntu cannot access internet	other	VirtualBox 5.0.18	defect	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
15343	Internal networking remark on same UID policy is misleading	other	VirtualBox 5.0.18	defect	2016-04-24T21:36:00Z	2016-04-24T21:36:00Z	2016-04-24T21:36:00Z	"The User Manual states that ""As a security measure, the Linux implementation of internal networking only allows VMs running under the same user ID to establish an internal network"". This would be correct if the sentence ended with ""(by default)"".

Current wording suggests that if I wanted to create two VMs using two UIDs I would have to use e.g. a host-only interface instead. This requires more work, e.g. configuring a firewall so the traffic is allowed only between those two VMs.

It seems that ""internal networking"" interfaces work the same as ""host-only"" interfaces used to. Anyone who tried to share a vboxnet interface in older versions of VirtualBox had to use RestictAccess=0. Apparently the same works for ""internal networking"" interfaces. Both types are managed by the same parts of code and show up in logs as ""intnet"" interfaces so maybe it's not that surprising.

So even if authors do not want to write about RestrictAccess and AccessPolicy settings the manual should at least suggest there is a possibility of creating a shared ""internal networking"" interface."	wodny
15236	E_FAIL (0x80004005)  MachineWrap IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}	other	VirtualBox 5.0.16	defect	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
15212	BoxManage showvminfo --machinereadable vcpfile property value is not properly escaped	other	VirtualBox 5.0.14	defect	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
15143	Guest Windows 8.1 64 bits freeze every 2-15 minutes for several seconds/minutes	other	VirtualBox 5.0.14	defect	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
9066	Shared folders lose guest access to folder contents when folders renamed	other	VirtualBox 4.0.8	defect	2011-06-13T14:10:19Z	2016-02-23T05:50:40Z	2016-02-23T05:50:40Z	"On a Win7 x64 host and Ubuntu 11.04 x64 guest, whenever I rename a shared folder directory, the guest OS loses references to the files therein. The files are still there (and correct on the host OS) but somehow inaccessible on the guest: ls shows the filename, but gives ""no such file or directory"" errors for each file therein (so it would appear that it's there in the filesystem tables, but the pointer to the actual location has got broken somehow). This therefore definitely appears to be a vboxsf error.

The file access can be ""restored"" by remounting the folder, or by renaming the folder back to its original name. The error always occurs, however the renaming is done (console or file manager). It also occurs if the folder is renamed on the host.

This is a pretty serious error, especially because many apps put things in hidden folders and then rename these (e.g. backup utilities such as Unison)."	Stuart Rossiter
15126	"""X"" in corner does not close dialog box."	other	VirtualBox 5.0.14	defect	2016-02-08T14:44:40Z	2016-02-08T14:44:40Z	2016-02-08T14:44:40Z	"The ""X"" in the upper right corner does not close the dialog box to close it you must chose the ""OK"" button."	SWillis
15098	Windows VM defaults are well below the required minimum values to run the OS	other	VirtualBox 5.0.14	defect	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
15058	Host+<key> doesn't work if host layout not US	other	VirtualBox 5.0.14	enhancement	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
15036	SDK Python webserver bindings IMachine::setGroups() inconsistent signature	other	VirtualBox 5.0.12	defect	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
15077	Suggestion: GUI attaching to headless should default close to 'continue'	other	VirtualBox 5.0.14	enhancement	2016-01-25T18:17:58Z	2016-01-25T18:17:58Z	2016-01-25T18:17:58Z	"It's great to be able to attach to a headless machine with the GUI!
Many, many thanks.  One suggestion:

When closing the console after attaching to a headless machine, the default radio button
on the close VM window seems to be 'Power off"" initially, and 'last choice"" thereafter.
This is dangerous.

It would be best to default to 'Continue running in the background',
especially if the console window was created by attaching to a
background/headless VM.  Certainly if the machine started out
headless, chances are good that it wants to stay that way when the
console session is over.  And if the user has other wishes, leaving it running is much safer
than initiating a shutdown.

I'm not objecting to the radio button dialog, just the default selection.


It would be even better if the UI settings for the machine
allowed disabling the other choices.  One can always use Machine
on the menu bar to shut down.  I run ALL my VMs headless, and
shutting down/powering off needs to be a deliberate act.  And it's
rare.  The only time I use the console is when there are boot/network
problems, or software installs.  I can see other use patterns, of course.


FWIW.  Thanks for your consideration.
"	Timothe Litt
15052	VBox Manager icons don't adequately distinguish VMs - icons almost useless	other	VirtualBox 5.0.14	defect	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
7018	Enable user to import custom icons with the file menu and/or automatically from a specified directory.	other	VirtualBox 3.2.4	enhancement	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
15005	no 3D accelaration when using WebService or VBoxManage startvm --headless (iGPU HD4000)	other	VirtualBox 5.0.12	defect	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
15021	Pressure Sensitivity for USB Multitouch Tablet pointing device	other	VirtualBox 5.0.12	enhancement	2016-01-10T13:29:04Z	2016-01-10T13:29:04Z	2016-01-10T13:29:04Z	"I would like to run a Linux host on a Wacom Penabled TabletPC (Supporting both a pressure-sensitive pen and capacitive multitouch), and run windows-only, non-wine-compatible programs like Corel Painter in Virtualbox.

Unfortunately, it seems that neither option for emulating a USB tablet reports pressure data from the host tablet device. And, given the nature of the hardware (The digitizer is the primary input device for the whole machine, so the host must still be able to use it), USB passthrough is not an option."	MorningSong
14999	Bridge NIC, ssh from VM will freeze for some cmds	other	VirtualBox 5.0.12	defect	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
14969	"""Insert Guest Additions CD image..."" should not have trailing ""..."""	other	VirtualBox 5.0.12	defect	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
14913	Saved vm: Clone + reinitialize network doesn't really change MAC	other	VirtualBox 5.0.10	defect	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
14897	Windows 10 handles VBoxManage.exe incorrectly when importing and listing	other	VirtualBox 5.0.10	defect	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
14884	Cannot chmod directories within guesLinux guest/host	other	VirtualBox 5.0.10	defect	2015-12-02T02:50:20Z	2015-12-02T02:50:20Z	2015-12-02T02:50:20Z	"I have a Linux guest in Virtualbox with a directory tree mounted rw using vboxsf. Today I noticed that running chmod on a directory from within the guest has no effect. This is a problem for me, because I was trying to use git annex, which relies heavily on being able to modify directory modes during the drop operation, for example. 

I did some searching and found lots of commentary implying that other people were seeing the same problem, but no solutions anywhere, so I dug into the source code and gradually drilled down into vboxsf until I found the host-side implementation of mode change for directories, in vbsf.cpp on line 1444:
{{{
    /* TODO: mode for directories */
}}}

I have to give it credit for its conciseness, but I'd be very appreciative if a new release of VirtualBox included a more effective implementation :)"	Simon Ruggier
14825	Can not delete iscsi harddisk	other	VirtualBox 5.0.10	defect	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
14838	Search bar on VirtualBox website too small.	other		enhancement	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
14752	The GUI and the command line vboxmanage report different status of VM	other	VirtualBox 5.0.8	defect	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
14790	Network communication problem in newer versions of VirtualBox. Possible regression.	other	VirtualBox 5.0.8	defect	2015-11-05T06:18:32Z	2015-11-07T23:36:28Z	2015-11-07T23:36:28Z	"I recently found that !VirtualBox could no longer communicate with my printer/scanner (same device). The device is attached via network ethernet cable (NAT).

The operating system of the guest is Linux Mint release 17 (qiana) Mate 64-bit. The driver has worked fine for years. After an update of !Virtualbox somewhere in version 4.x, I was able to send print commands but I could no longer communicate with the scanner.

To help narrow down the problem, I tested the exact same operating system and printer driver with 2 different versions of !VirtualBox:

1. !VirtualBox v. 4.2.32 `r101581`: Scanner works
2. !VirtualBox v. 5.0.6 `r103037`: Scanner fails

Scanning hasn't worked for some time; at least since version 5.0 and possibly a bit before that. I estimate that it broke sometime after 4.3. Comments in !VirtualBox's forum indicate that it's a possible regression because nothing has changed except for the !VirtualBox version. Every time I downgraded or upgraded !VirtualBox, I always installed the corresponding guest additions for that particular version. I tested with version 5.0.8 `r103449` also; the problem persists.

To replicate the problem:
1. Install Linux Mint 17 Mate 64-bit as the guest. The host can be anything. It's a guest problem.
2. Install scanner and printer drivers for Lexmark Pinnacle Pro901. These are the respective files:

http://support.lexmark.com/index?docLocale=en_US&page=content&id=DR21641&locale=EN&userlocale=EN_US

http://support.lexmark.com/index?docLocale=en_US&page=content&id=DR21637&locale=EN&userlocale=EN_US

3. When installing the printer driver, add the printer to the operating system. Let the operating system detect the printer, then use AppSocket/HP JetDirect. The IP of the printer will be automatically detected without having to choose AppSocket/HP JetDirect.

4. There is a cups-insecure-filter error when you try to print. This is easily fixed:
{{{
cd /usr/local/lexmark/v3/bin/
sudo chmod 755 printfilter
}}}
Printing isn't the problem though. I include this just to be thorough.

5. Install any scanning program. gscan2pdf and Simple Scan both work well. On older versions of !VirtualBox (up to about the 4.2 I tested, possibly up to around 4.3), scanning will work just fine. All later versions cut off access to the scanner; the scanning program will say no scanners were detected.

// End of steps for reproducing the problem

A log file has been attached. During the time the log was created, I powered on the virtual machine, successfully tested that a printed document could be sent to the printer, tested the scanner (which failed), and then powered it off. I'll be happy to provide more details that might be relevant."	misterpenguin
14786	3D acceleration issues persisting on Intel HD video Card	other	VirtualBox 5.0.8	defect	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
7874	Guest keyboard starts sending multiple characters for a single keypress after Windows host hibernation	other	VirtualBox 3.2.12	defect	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
14766	VirtualBox breaks USB Drives Permanently Connected	other	VirtualBox 5.0.6	defect	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
14715	VM renaming	other	VirtualBox 4.3.28	defect	2015-10-19T07:21:10Z	2015-10-19T10:22:31Z	2015-10-19T10:22:31Z	"My VM is creating during automatic provisioning with Vagrant. After VM is created I have an error if I start this VM. (The same script uses on Mac OSX, have no issues with it)

VM has 2 network adapters: Nat & Host-Only Adapter. No GUI. No USB

Log file is attached"	tuborg
14492	drag and drop fails on win 10 host 64bit	other	VirtualBox 5.0.2	defect	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
14679	Deleting Snapshot Error: VBOX_E_FILE_ERROR (0x80BB0004) - File not accessible or erroneous file contents	other	VirtualBox 5.0.4	defect	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
14258	Detachable broken when 3d acceleration is enabled	other	VirtualBox 5.0.0	defect	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
93	Minimize main window to trayicon	other	VirtualBox 1.3.6	enhancement	2007-02-20T18:42:41Z	2015-10-02T19:45:25Z	2015-10-02T19:45:25Z	I would prefer it to minimize the !VirtualBox main window to a trayicon instead of a taskbar entry (current behavior). Therefore it would be nice if there is an option to choose in which way the main window will be minimized.	Ruhe
14628	Multiple Real Monitors/Screen-Sizing issue across multiple monitors	other	VirtualBox 5.0.4	defect	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
14378	Cannot access VirtualBox menus in full-screen mode	other	VirtualBox 5.0.0	defect	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
13002	Slow DNS resolving with enabled natdnsproxy	other	VirtualBox 4.3.10	defect	2014-04-29T15:50:12Z	2015-08-25T08:17:27Z	2015-08-25T08:17:27Z	"Outgoing network connections are very slow with VMs using 3.13+ kernel.

Below you can see the curl connect phase is taking 5+ seconds.  Problem exists reguardless of using virtio or intel adapters.

{{{
vagrant@vagrant-ubuntu-trusty-64:~$ curl -o /dev/null -s -w %{time_connect}:%{time_starttransfer}:%{time_total}\\n https://www.google.com
5.559:5.703:5.706
vagrant@vagrant-ubuntu-trusty-64:~$ uname -a
Linux vagrant-ubuntu-trusty-64 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
vagrant@vagrant-ubuntu-trusty-64:~$ lsmod
Module                  Size  Used by
vboxsf                 43786  1
nfsd                  280297  2
auth_rpcgss            59338  1 nfsd
nfs_acl                12837  1 nfsd
nfs                   236636  0
lockd                  93977  2 nfs,nfsd
sunrpc                284404  6 nfs,nfsd,auth_rpcgss,lockd,nfs_acl
fscache                63988  1 nfs
dm_crypt               23177  0
ppdev                  17671  0
psmouse               102222  0
serio_raw              13462  0
parport_pc             32701  0
parport                42348  2 ppdev,parport_pc
vboxguest             248441  2 vboxsf
ahci                   25819  1
libahci                32168  1 ahci
e1000                 145174  0
}}}

Here is my Vagrantfile that allows for simple re-creation of this issue:

{{{
 -*- mode: ruby -*-
# vi: set ft=ruby :

# Vagrantfile API/syntax version. Don't touch unless you know what you're doing!
VAGRANTFILE_API_VERSION = ""2""

Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
#  config.vm.box = ""ubuntu/trusty64""
  config.vm.box = ""ubuntu-trusty64-20140429""
  config.vm.box_url = ""http://cloud-images.ubuntu.com/vagrant/trusty/20140429/trusty-server-cloudimg-amd64-vagrant-disk1.box""

  config.vm.network :private_network, ip: ""192.168.33.10""
  config.vm.synced_folder "".."", ""/vagrant""

  config.vm.provider :virtualbox do |vb|
     vb.gui = false
     vb.name = ""slowconnection""

     # Use VBoxManage to customize the VM. For example to change memory:
     vb.customize [""modifyvm"", :id, ""--memory"", ""1024""]
  end
end
}}}

nslookup on www.google.com is fast, netperf is fast, download of files are fast once connection is made, mtr is fast (low response times)."	rynop
14473	No emails from answers to my tickets, adding address to the CC field impossible	other		defect	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
14423	2nd screen window - Fail to open	other	VirtualBox 4.3.30	defect	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
10105	Implement a keyboard shortcut key to minimize a fullscreen VirtualBox VM guest window	other	VirtualBox 4.1.8	enhancement	2011-12-29T21:49:04Z	2015-08-06T20:26:35Z	2015-08-06T20:26:35Z	"When a VirtualBox VM client is running with a fullscreen window, minimizing it is done with the mouse touching the bottom of the screen and clicking the minimize button when the toolbar appears, or pressing Host+F to leave fullscreen mode and minimizing it.

Both ways are cumbersome when working with a fullscreen VM and switching between the guest and host frequently.

A keyboard shortcut to minimize the guest window should be nice, without needing to use the mouse or leaving fullscreen mode."	3F776B3E
14243	Mini toolbar is 'Always on top' for all windows, even when VM does not have focus	other	VirtualBox 4.3.28	defect	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
14220	Resized differential drives causes guest crash	other	VirtualBox 4.3.28	defect	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
13866	Provide useful output when host interface for bridge is no longer available	other	VirtualBox 4.3.22	defect	2015-02-20T02:09:39Z	2015-06-22T23:25:16Z	2015-06-22T23:25:16Z	"If a VM has been setup to use eth1 of the host, the host shutdown, the interface exchanged and rebooted, then `VBoxManage startvm ""[name]"" --type headless` results in 

    Waiting for VM ""Ubuntu-12.04.5-i386"" to power on...
    VBoxManage: error: Failed to open/create the internal network 'HostInterfaceNetworking-eth1' (VERR_INTNET_FLT_IF_NOT_FOUND).
    VBoxManage: error: Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND)
    VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component Console, interface IConsole

which could easily replaced with an understandable and helpful error message."	krichter
12180	running slow	other	VirtualBox 4.3.0	defect	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
13564	Allow sorting of the VM snapshots	other	VirtualBox 4.3.18	enhancement	2014-10-28T19:09:33Z	2015-06-17T13:50:19Z	2015-06-17T13:50:19Z	"As of VirtualBox 4.3.18 it is not yet possible to sort snapshots, any new sibling will simply be appended to the end of the list - seems like sorting on the date of creation. However, I'd like to be able to re-sort one VM's snapshots in different ways. 

I have a VM with some (30) snapshots, where I'm testing a complex software project. Each snapshot holds a different revision of the project installed to be able to test and track down regressions quickly. Let's say that I create a snapshot each 100 revisions, so I begin with r63000, then r63100, r63200 and so on; then I suddenly have a need to expand the covered range into the history with r62000. If I create such a snapshot in VBox 4.3.18, it will be added to the end of the list, which could create confusing-to-search state quite quickly if I have to touch different ranges each time. Since I name the snapshots with the revision tested, I could just sort by name (+numerically). Or I could just drag and drop the single snapshot where I want it.

TL;DR I could very much use at least one of the { alphabetical, manual } sorting options in the snapshots list."	Black_Fox
14134	WDDM driver exposes only 384 MB VRAM, at least 512 MB needed (and 12 GB available!)	other	VirtualBox 4.3.28	defect	2015-05-18T18:52:29Z	2015-06-14T19:54:28Z	2015-06-14T19:54:28Z	"How does the WDDM driver determine the amount of VRAM to expose?

Our CAD software (Autodesk Fusion 360) checks for at least 512 MB VRAM. The WDDM driver presents only 384 MB VRAM so the CAD software reverts to software rendering.

The physical hardware has 12 GB VRAM (NVIDIA Titan X). Is it possible to tweak the WDDM implementation to provide more VRAM?

Host is Ubuntu 4.0.0-040000-generic and guest is Windows 7 x64 SP1.

Thanks"	Drew Robson
14172	Virturalbox doesn't start	other	VirtualBox 4.3.28	defect	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
14133	After update, the windows taskbar icon is wrong	other	VirtualBox 4.3.28	defect	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
10852	Automatic integer-factor scaling under full-screen mode	other	VirtualBox 4.1.20	enhancement	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
14111	Using SaveState is corrupting disk image when VirtualBox has been opened more than once (by multiple users)	other	VirtualBox 4.3.26	defect	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
14073	vbox doesn't know how to use my kernel signature to sign its modules	other	VirtualBox 4.3.26	enhancement	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
14027	VMs with bridged network do not start	other	VirtualBox 4.3.26	defect	2015-04-05T23:46:40Z	2015-04-09T09:06:05Z	2015-04-09T09:06:05Z	"I have created a forum thread that did not draw enough attention: https://forums.virtualbox.org/viewtopic.php?f=6&t=64797&p=317689#p317689

But the problem still exists.

It's a clear installation of a virtualbox 4.3.26 on my machine. I had 4.3.18 before, which was uninstalled before I installed and the whole laptop was rebooted.
And yes this time I installed 4.3.26 USING run-as-admin item (which did not change anything)

"	zerkms
14025	The Exception unkown software exception (0xc06d007e)	other	VirtualBox 4.3.26	defect	2015-04-04T23:42:04Z	2015-04-05T06:19:29Z	2015-04-05T06:19:29Z	"After a re-installing windows I am unable to launch virtualbox, it gives me this error: http://i.imgur.com/jtQC0k6.jpg . I have tried uninstalling and re-installing a few times no luck :( . Can see the log file here : http://pastebin.com/raw.php?i=cMfiN8FD

I've tried turning off firewall and sleeping Kaspersky with no luck. I apologize if this is in the wrong thread, please feel free to move it to the correct one if need be. "	n0rbertt
13916	Altium on VirtualBox	other	VirtualBox 4.3.24	defect	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
13920	Starting guest with multiple monitors on a different workspace causes virtual screens to disappear	other	VirtualBox 4.3.24	defect	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
13896	virtualbox installing rolling back in the end of the install	other	VirtualBox 4.3.22	enhancement	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
13870	Video driver for Windows 10 is turned off	other	VirtualBox 4.3.22	defect	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
13880	OperationalError: (1213, 'Deadlock found when trying to get lock; try restarting transaction')	other	VirtualBox 4.3.22	defect	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
13865	Make text from label in the overview of details of the machine copyable	other	VirtualBox 4.3.22	enhancement	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
13836	Not rendering the window properly when in fullscreen	other	VirtualBox 4.3.22	defect	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
7067	VERR_INTERNAL_ERROR: Inexistent host networking interface, named 'vboxnet0'	other	VirtualBox 3.2.6	defect	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
13743	NAT: port forwarding issues / collision	other	VirtualBox 4.3.18	defect	2015-01-07T11:28:33Z	2015-01-07T11:28:33Z	2015-01-07T11:28:33Z	"Host: Windows 7, Core i7, VBox 4.3.18

Guests: Linux, RHEL6 (CLI-only)

Setup localhost + 2 web servers VMs.

VM1: NAT host@1443 -> guest:443 (default 10.0.2.15 IP)

VM2: NAT host@2443 -> guest:443 (default 10.0.2.15 IP)

I connect by typing in local web browser:
https://localhost:1443

When I connect via HTTPS to first VM, it's okay, but when I connect to
second VM, the first one disconnects (connection timeout), and then I
get access to 2nd VM, and after I try to reconnect to 1st VM, 2nd VM
immediately disconnects, so there is some collision between NAT engine
on both VMs.

No way to connect to both VMs, from localhost web browser.

Not sure why this happens, as SLIRP NAT module is supposed to be
user-space, per-VM process.

I also ensured, that MAC addresses were different in 2 VMs.

--

-Alexey Eromenko ""Technologov"", 07.Jan.2015"	Technologov
242	No image with USB 2.0 webcams	other	VirtualBox 2.2.2	defect	2007-03-30T21:20:40Z	2015-01-07T00:16:31Z	2015-01-07T00:16:31Z	I need to test streaming video products inside of the virtual machine.  After installing the drivers inside the virtual machine and opening Windows Movie Maker, AMCAP, or my own software the stream is just blank.  The drivers are found and installed properly and it is not a problem with the hardware.  No error is given but the stream from the device (webcam of sorts) is just a blank black feed.	PeterValentine
13678	Networking Still Works After Not Installing	other	VirtualBox 4.3.20	defect	2014-12-10T08:36:05Z	2014-12-10T11:15:37Z	2014-12-10T11:15:37Z	"During installation it's possible to opt out of installing VirtalBox's networking features. However, despite this, it's still possible for VMs to connect to the host's network via NAT under the networking tab within its settings.

For the purposes in which the VM is to be used, I don't want it to be possible for the user to connect to the network/internet in any shape or form. I have tried this on both the stable, and the test version of VirtualBox (4.3.21)."	Pearson.S2
13599	Windows 7 guest renders Linux host unresponsive; uncompleted fence warnings	other	VirtualBox 4.3.18	defect	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)
13556	Unable to get out of scaled mode in Mac OS X	other	VirtualBox 4.3.18	defect	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
13351	names of saved virtual machine's cannot be changed	other	VirtualBox 4.3.14	defect	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
12089	Option to show host-side mouse pointer with mouse integration	other	VirtualBox 4.2.18	enhancement	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
13233	Please enable fPIC for libraries	other	VirtualBox 4.3.14	defect	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
13042	Support for Spice	other		enhancement	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
12989	guest display size indicator	other	VirtualBox 4.3.10	enhancement	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
12866	VBoxManage clonehd should fail early if not enough disk space	other	VirtualBox 4.3.8	enhancement	2014-03-25T14:37:38Z	2014-03-26T15:00:03Z	2014-03-26T15:00:03Z	"Given a 40GB .vmdk file, trying to clone the disk

  VBoxManage clonehd in.vmdk out.vdi --format vdi

will churn happily until it runs out of disk space many minutes later.

The command should first verify that there is sufficient space
for the output file (which will be roughly the same size),
and fail early if there is insufficient space. 

Care should be be taken for the case that the output file
is in a symlinked diretory; you need to check the canonical
location.

A --force option could bypass that check (for example, if there is
some other job running concurrently that will free up space
for the new file).

Same should be true for modifyhd or other operations that create virtual disk or other large files."	David Biesack
12816	Scale Mode reworked into Zoom function	other	VirtualBox 4.3.6	enhancement	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
32	"[feature-reques] Ability to suppress all stupid messages in ""File->Global Settings"""	other	VirtualBox 1.3.4	enhancement	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
12590	Add Run from last snapshot workflow option	other	VirtualBox 4.3.6	enhancement	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
12535	Notification dialogs should move when Mini ToolBar position is changed	other	VirtualBox 4.3.6	enhancement	2013-12-23T14:15:53Z	2013-12-23T14:15:53Z	2013-12-23T14:15:53Z	"Ever since the Virtualbox 4.3 series, the notification dialog are long, displayed at the top of the screen.
However, I run virtual guests fullscreen with the Mini ToolBar shown at the TOP.
This make notifications intrusive, since they're also displayed at the TOP.

There should be a way to move the dialogs, or just place them in the middle of the screen.

Note: in attachment screenshot, the Mini Toolbar is hard to see, but I have an arrow pointing to it"	Pack27
12331	The documentation is not entirely up to date regarding the NAT service	other	VirtualBox 4.3.2	enhancement	2013-11-08T12:14:06Z	2013-11-08T12:14:06Z	2013-11-08T12:14:06Z	"A part of the documentation hasn't been updated to reflect the newly introduced NAT Service.

Specifically, ""8.8.2. Networking settings"" doesn't include the ""natnetwork"" options and the ""--nat-network""  parameter, while they are correctly enlisted in ""8.2. Commands overview"".
"	sap239048
12294	small VM icon inconsistency, suggest using '2000' not 'w2k'	other	VirtualBox 4.3.2	enhancement	2013-11-02T22:06:40Z	2013-11-05T21:49:59Z	2013-11-05T21:49:59Z	"The icon for Windows 2003 is a Windows logo with the text '2003' on it.

The icon for Windows 2000 is a Windows logo with the text 'w2k' on it.

It would be more consistent if the Windows 2000 icon had the text '2000' on it.
"	ccijwlrjqj
12174	Configure internal DHCP server to pass arbitrary domains	other	VirtualBox 4.2.18	enhancement	2013-10-10T12:32:39Z	2013-10-10T13:25:31Z	2013-10-10T13:25:31Z	"Hi, 

virtualbox uses it's own internal DHCP server if the network interface type of a VM is set to 'NAT'. 

Unfortunaly I was unable to make VB's DHCP to offer any domain name. Although VBoxManage supports a --natdnspassdomain option, this can just turn domain passing on and off, and did not have any effect. I did not find a hint in the manual, where VB takes the domain from it is supposed to pass through. 

Would be quite useful if VB would allow to just configure which domain name is to be passed by the internal DHCP server to the VM. So one could set any random default domain. 

regards
"	DerHadmut
11778	Version names and error messages are not translatable.	other	VirtualBox 4.2.12	task	2013-05-06T21:10:49Z	2013-10-01T13:25:02Z	2013-10-01T13:25:02Z	Version names for operating systems like Other Linux and error messages are not translatable. For example: to translate Could not get the storage format of the medium 'filename' (code) into Korean (which is your mother tongue), you need someone speaking Korean man to get it translated.	Tae
12120	Cannot create snapshot with ampersand in the title	other	VirtualBox 4.2.18	defect	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
12045	Cannot attach new vm via multiattach when another vm is running	other	VirtualBox 4.2.14	defect	2013-08-22T17:55:08Z	2013-08-22T17:55:08Z	2013-08-22T17:55:08Z	"Cf. bug report: https://www.virtualbox.org/ticket/11700. The suggested solution doesn't work if the vdi file is read only (on the file system).

After running the commands

NAME=test1

VBoxManage createvm --name ""${NAME}"" --ostype Ubuntu --register

VBoxManage modifyvm ""${NAME}"" --memory 1024

VBoxManage storagectl ""${NAME}"" --name ""sata1"" --add sata

VBoxManage storageattach ""${NAME}"" --storagectl ""sata1"" --port 0 --device 0 \
    --type hdd --medium /path/to/my.vdi --mtype multiattach

to create a new vm (with an existing multiattach virtual disk), I start up the vm. While it's running, I create a new vm with similar commands, but I get the following error:

VBoxManage: error: Medium '/home/charlesj/vm/2100vm.vdi' is locked for reading by another task
VBoxManage: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component Medium, interface IMedium, callee nsISupports
VBoxManage: error: Context: ""COMSETTER(Type)(mediumType)"" at line 678 of file VBoxManageStorageController.cpp
VBoxManage: error: Failed to set the medium type

It looks like it's trying to set the medium type prematurely (in case it isn't multiattach).

Setting up a new vm with multiattach works when all attached vms are powered down / suspended, even when the vdi file is read only.

I've attached the log file for the first machine that successfully boots; the second machine does
not produce a log file on failure."	charlie-jacobsen
11885	Automatically detect SSD status of a virtual disk	other	VirtualBox 4.2.12	enhancement	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
11017	Outdated SMBIOS version	other	VirtualBox 4.2.0	enhancement	2012-10-03T12:25:20Z	2013-06-04T07:19:12Z	2013-06-04T07:19:12Z	Currently (Version 4.2.0), SMBIOS Version 2.5 is provided, the currently available specification (from 2011) is 2.7.1. Versions < 2.6 cause problems when used with the new consistent network interface naming of RHEL/CentOS 6/Fedora based on biosdevname since information about network devices is missing (types 9 and 41 of SMBIOS specification).	29erpete
6102	VirtualBox cannot load split VHD files.	other	VirtualBox 3.1.2	enhancement	2010-01-31T18:46:03Z	2013-05-20T09:34:35Z	2013-05-20T09:34:35Z	"When I try to open a split VHD file in the VirtualBox Media Manager, I get the following error:
{{{
Failed to open the hard disk D:\Fedora 7 Hard Disk.vhd.
Could not get the storage format of the medium 'D:\Fedora 7 Hard Disk.vhd' (VERR_NOT_SUPPORTED).
}}}
The VHD file is split because Microsoft Virtual PC automatically splits VHD files on disks that have the FAT32 filesystem.
"	theflash
11516	Please consider adopting the phpvirtualbox project	other	VirtualBox 4.2.6	enhancement	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
7822	"[feature-request] Scale Mode: option to ""keep original aspect ratio"""	other	VirtualBox 3.2.12	enhancement	2010-12-10T14:32:00Z	2013-03-24T12:55:25Z	2013-03-24T12:55:25Z	"Scale Mode is a very useful feature for gamers alike. This is because many older games have fixed resolution (such as 640x480), which cannot be modified at all.

Aspect Ratio: There must be some checkbox option to ""keep original aspect ratio"" (such as 4:3).

Currently Stretching works in any direction killing the experience of old games. (Starcraft I, Diablo I)

-Technologov, 10.12.2010."	Technologov
11417	User Manual controlvm options	other	VirtualBox 4.2.6	defect	2013-01-24T16:57:06Z	2013-01-24T16:57:06Z	2013-01-24T16:57:06Z	"In the HTML and PDF versions of the user manual, the description of the VBoxManage controlvm ""extra option"":

nic<1-N> null|nat|bridged|intnet|hostonly|generic

is incomplete, compared to the VBoxManage command's help, which lists:

nic<1-N> null|nat|bridged|intnet|hostonly|generic '''[<devicename>]'''

This was the one I was most concerned with. However, it appears that there are many other options and ""extra options"" that are not documented (i.e., not explicitly listed as options, but may be described elsewhere) in the user manual:

acpipowerbutton|acpisleepbutton

keyboardputscancode <hex> [<hex> ...]

nictrace<1-N> on|off

nictracefile<1-N> <filename>

nicproperty<1-N> name=[value]

natpf<1-N> [<rulename>],tcp|udp,[<hostip>],<hostport>,[<guestip>],<guestport>

natpf<1-N> delete <rulename>

gueststatisticsinterval <seconds>]

clipboard disabled|hosttoguest|guesttohost|bidirectional

draganddrop disabled|hosttoguest

vrdeproperty <name=[value]>

vrdevideochannelquality <percent>

plugcpu <id>
unplugcpu <id>

cpuexecutioncap <1-100>"	Stephen Rondeau
990	[feature-request] parallel port	other	VirtualBox 1.5.2	enhancement	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
950	Autostart a vm on startup	other	VirtualBox 1.5.2	enhancement	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
9769	Blue screen during install of Windows XP with slipstreamed SATA driver	other	VirtualBox 4.1.4	defect	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
11006	Creating a cloned or linked virtual machine does not allow to select destination folder	other	VirtualBox 4.2.0	enhancement	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
7111	[feature-request] Please allow to loop mount VBox HDD images on host	other	VirtualBox 3.2.6	enhancement	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
7214	[PATCH] Add BeOS and Haiku to the (Other) guest OS list	other	VirtualBox 3.2.6	defect	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
10272	Allow storing virtual machine settings in a directory thus multiple virtual box installation could share	other	VirtualBox 4.0.16	enhancement	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
10212	Problem with DNS lookups (NAT)	other	VirtualBox 4.1.8	defect	2012-02-04T17:43:53Z	2012-02-04T18:04:02Z	2012-02-04T18:04:02Z	"NAT network adapter

Running the following shell script on a Debian VM causes DNS lookups to timeout after ~15s of execution

Script:
{{{
while [ 1 ]; do nslookup google.pl; done
}}}

The error is:
{{{
;; connection timed out; no servers could be reached
}}}

It doesn't occur with bridged adapter.
It occurs on all network adapter types (i.e. Intel, PCnet, virtio-net) available in VirtualBox.

Tested on:

Windows 7 host - VirtualBox 4.1.6, 4.1.8

Debian host - VirtualBox 4.1.4
"	DragMZ
9480	VirtualBox + VirtualPC2007 = crash	other	VirtualBox 4.1.2	defect	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
8693	Consider pushing the java  vboxjws.jar client API jar in a Maven repository	other	VirtualBox 4.0.4	enhancement	2011-04-07T14:45:40Z	2012-01-05T19:23:52Z	2012-01-05T19:23:52Z	"Java projects build system rely more and more on Maven and jar repositories to find  APIs to use and consume,
GlassFish prjoect would love to be able to find vboxjws.jar in a maven repository.
If the javadoc is there as well (see previous bug, it can also be pushed there."	ludo
10123	Allow using raw host disks for guests via VirtualBox VM Manager (GUI)	other	VirtualBox 4.1.8	enhancement	2012-01-03T10:49:26Z	2012-01-03T10:49:26Z	2012-01-03T10:49:26Z	"Currently, the only way to provide access to raw drives to guests is by using ""VBoxManage internalcommands createrawvmdk"".  Since this is a major feature, providing a more obvious way to use it would be nice."	tlm
10098	Wrong manual entries for setting up VRDP authentication in the VBox end-user documentation	other	VirtualBox 3.2.14	defect	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
3852	vboxusers group should be added as a system group, not as an ordinary group	other	VirtualBox 2.2.0	enhancement	2009-04-26T17:04:25Z	2011-12-08T16:39:44Z	2011-12-08T16:39:44Z	"When installing VirtualBox-2.2.0_45846_fedora9-1.i386.rpm (on Fedora 10) a vboxusers group is created. Unfortunately it is created as an ordinary group and not as a system group, which means that it can clash with other (older) groups which haven't been (re)added yet to /etc/group.

The problem can be fixed by running ''groupadd'' with the '''-r''' parameter. Quoting from the man page:

  '''-r'''  This flag instructs groupadd to add a system account. The first available gid lower than 500 will be automatically selected unless the -g option is also given on the command line. This is an option added by Red Hat."	Cristian Ciupitu
9979	[feature-request] Please allow clones from running VMs	other	VirtualBox 4.1.6	defect	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
9971	Persistent DHCP database	other	VirtualBox 4.1.6	enhancement	2011-11-29T17:26:26Z	2011-11-29T17:26:26Z	2011-11-29T17:26:26Z	"(OSX Lion, VBox 4.1.6)

It would be useful if the VBox DHCP server for Host-only Networking keep a persistent database of MAC address to IP address assignments, so that when you start the VMs later they get the same IP addresses, independent of the order you start them in.

(Workaround: run a DHCP server in another VM)
"	Brian Candler
9970	DHCP gateway option	other	VirtualBox 4.1.6	enhancement	2011-11-29T17:23:24Z	2011-11-29T17:23:24Z	2011-11-29T17:23:24Z	"(OSX Lion / 4.1.6)

If would be useful if the built-in DHCP server on Host-only Networking could allow you to set a DHCP Gateway option. This would allow you easy to point guests at another VM as a way out of the network.

(Workaround: run a DHCP server in another VM on the same Host-only Network segment)"	Brian Candler
9234	GNU/kFreeBSD support: gnukfreebsd checks in the build system	other	VirtualBox 4.0.12	enhancement	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
9934	Suspend 3D Desktop Composition when entering Seamless Mode	other	VirtualBox 4.1.6	defect	2011-11-21T23:44:20Z	2011-11-22T10:43:58Z	2011-11-22T10:43:58Z	"This bug is relevant for all guests with 3D desktops : Aero/Kwin3D/GNOME-shell/Unity3D/Compiz.

I know, I know, this is not supported... but... it seems there is a
way to support it:

KDE 4.7 new:

""KWin now features an option for application developers to suspend
compositing when a fullscreen application calls for it. This should
increase performance for OpenGL games and GPU-accelerated video
playback.""

http://kde.org/announcements/4.7/platform.php

Something similar is possible for WinVista and Windows 7 Aero too. Not
sure about Unity and GNOME, but we can try opening wishes, if needed.

Basically when entering Seamless mode, VBox can request guest OS to
return to 2D mode.

-Alexey Eromenko ""Technologov"", 22.11.2011."	Technologov
9842	virtualbox doesn't list USB device with zero vendor and product ID	other	VirtualBox 4.1.4	defect	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
6957	More network adapters in VirtualBox	other	VirtualBox 3.2.4	defect	2010-06-10T12:47:49Z	2011-10-26T15:11:53Z	2011-10-26T15:11:53Z	"In VboxManage maximum is 8 network adapters, but in VirtualBox Gui only 4.
I make a simple patch to fix this, but only for OSE edition.
Please use it in feature release of closed source edition.
It's very usable function for testing in virtual environment."	eugene
8694	java client access via vboxjws.jar is not using https	other	VirtualBox 4.0.4	defect	2011-04-07T14:59:24Z	2011-10-10T18:49:15Z	2011-10-10T18:49:15Z	"java client access via vboxjws.jar is done via http and a user name and password.

But http communication is not secure, so it would be possible to see the name and password in clear on the wire.
Please consider adding https access as well for real security."	ludo
9733	Cannot set defaultMachineFolder globally	other	VirtualBox 4.0.4	enhancement	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.
9035	[feature-request] GuestControl execute must automatically handle extensions, like shell does	other	VirtualBox 4.0.8	enhancement	2011-06-06T18:53:53Z	2011-10-04T11:37:57Z	2011-10-04T11:37:57Z	"Host: Windows 7 x64 + VBox 4.0.8

Guest: Windows XP + GA 4.0.8

C:\Program Files\Oracle\VirtualBox>VBoxManage guestcontrol execute ""Windows XP V
M01"" ""ping"" --username Administrator --password 123456 --arguments ""10.0.2.2 -n
2"" --wait-for stdout

VBoxManage.exe: error: The file 'ping' was not found on guest.

When I change the above command to ""ping.exe"" it works.

Please handle extensions, according to guest's shell or desktop environment settings. Add "".exe"" or python interpreter where appropriate. Automatically.

-Technologov"	Technologov
9668	more facts, figures, and statistics	other	VirtualBox 4.1.2	enhancement	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
9202	Ommit selection dialog on close, when only one close action is possible	other	VirtualBox 4.0.10	enhancement	2011-07-14T09:00:57Z	2011-09-21T16:53:41Z	2011-09-21T16:53:41Z	"When locking down the close actions of the VirtualBox GUI via:
VBoxManage setextradata ""VM name"" GUI/RestrictedCloseActions ...

such that only one option is left, e.g. PowerOff

the action should be executed immediately without showing the selection / confirmation dialog (there is nothing to select if only one option is there).

"	Paolo Virtual
9060	Ideas to improve the list of VMs (GUI)	other	VirtualBox 4.0.8	enhancement	2011-06-11T05:52:18Z	2011-09-16T16:47:28Z	2011-09-16T16:47:28Z	"I have a larger number of VMs listed in the VBox GUI, and I've noticed the following problems with that GUI (widget that lists the VM), that become obvious when the list is bigger:

- the individual entries in the list have considerable height (big icons, two lines of text), this causes that only 13 VMs are visible at a time on my screen resolution (1024x768). Having an option here to use smaller height entries, possibly with reduced info would help here (like the style used by VMWare Server 1.x)

- entries are always listed in order they where added to the system. Ability to sort the list and to manually move the entries up/down the list would be quite an improvement. This is essential to handling a larger collections of VMs

- allow quick search in this widget to select a VM by quickly typing first few letters of a VMs name

- possibility to rename VMs from within the GUI"	Miroslav Rajcic
9339	[feature request] Enable remote management with GUI	other	VirtualBox 4.1.0	enhancement	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
7821	[feature-request] Scale Mode: Should work with Full-screen	other	VirtualBox 3.2.12	enhancement	2010-12-10T14:29:32Z	2011-08-29T23:56:26Z	2011-08-29T23:56:26Z	"Impossible to combine Scaled Mode + Full-Screen Mode.

Scaling only works for Windowed Mode.

This should work for Full-screen as well. Useful for Diablo 1 (2D/DirectDraw).

-Technologov, 10.12.2010."	Technologov
9389	Feature Request: Shutdown host if guest is shut down	other	VirtualBox 4.1.0	enhancement	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
9438	Provide a mechinism to set a guest OS's process priority to idle	other	VirtualBox 4.1.0	defect	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
9420	Selection for optical drives in the boot menu	other	VirtualBox 4.1.0	enhancement	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
9419	Sorting controller in the storage device menu	other	VirtualBox 4.1.0	enhancement	2011-08-11T23:19:45Z	2011-08-11T23:19:45Z	2011-08-11T23:19:45Z	Currently it is not possible to sort the controller in the storage device menu. The only way is to delete and recreate them in the correct order. I think it should be possible to move the controller with drag and drop.	Sworddragon
9341	Strange wizard help on cloning - no help on really needed info	other	VirtualBox 4.1.0	defect	2011-07-29T12:35:16Z	2011-07-29T12:35:16Z	2011-07-29T12:35:16Z	"Hi,[[BR]]
when using a cloning feaure from GUI the wizard pops up: ""Welcome to the virtual machine clone wizard. This wizard will help you to create a clone of your virtual machine. Use the Next button to go to the next page of the wizard and the Back button to return to the previous page. You can also press Cancel if you want to cancel the execution of this wizard."" At the bottom there is a checkbox: ""Reinitialize the MAC address of all network cards"".[[BR]]
What is strange is help above there is a lot of explaining about Next, Back, Cancel buttons which is a help of ""idiots"", but on the other hand there is no help about ""Reinitialize the MAC address of all network cards"" which is really needed for average user.[[BR]]

I suggest to use something like ""fixedwheel"" has answered on forum topic: http://forums.virtualbox.org/viewtopic.php?f=1&t=43515
Regards"	grof
9337	VM defaults for a new windows 95/98 image seem off	other	VirtualBox 4.1.0	defect	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
9316	Hardware presets - the next killer feature?	other	VirtualBox 4.1.0	enhancement	2011-07-26T18:45:58Z	2011-07-27T05:56:55Z	2011-07-27T05:56:55Z	"Or maybe it's just a bad idea. :) But here goes:

Some of the less techy VBox users have no idea what PAE is/does, or the difference between the PIIX3 chipset & the ICH9 chipset, or what IO APIC is, etc. It would be really nice if there were a ""hardware profile picker"" list, which basically is just a list of presets, e.g. ""Old Pentium 2 from 1999"" or ""Typical Intel Core 2 Duo"" to serve as starting points that people can use to emulate a particular type of virtual machine the guest will be running on. Choosing one of these presets would auto-fill in all the details for us.

My examples above are bad, I know. But this should illustrate the concept at least."	CaptSaltyJack
9195	In machine list details view, show actual size of attached VDIs	other	VirtualBox 4.0.10	enhancement	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
7823	[feature-request] Scale Mode: performance should improve	other	VirtualBox 3.2.12	enhancement	2010-12-10T14:34:57Z	2011-07-11T15:16:35Z	2011-07-11T15:16:35Z	"Host: Windows XP + ATI Radeon HD 3850 + Intel Core 2 2.4 GHz

Scale mode performance is not smooth.

Playing Diablo 1 in scaled mode (DirectDraw) is very ""jumpy"" -- window stops rendering for 0.1 second, then jumps several frames.
Both mouse movement and hero movement experience such issues.
Basically now the game is runnable, but unplayable.

If I switch to Normal Windowed Mode or Full-Screen Mode, Diablo plays smoothly.

-Technologov, 10.12.2010."	Technologov
6089	Inactive/non-functioning keyboard and mouse in fullscreen (Ubuntu 9.10 guest)	other	VirtualBox 3.1.2	defect	2010-01-28T15:51:52Z	2011-07-04T17:46:11Z	2011-07-04T17:46:11Z	"As described in [http://forums.virtualbox.org/viewtopic.php?f=6&t=27225 this post], my Ubuntu guest OS does not function in fullscreen in VirtualBox 3.1.2. 

I have previously been running this VM successfully in fullscreen on this computer using VB 3.0.10, but I have since reinstalled Windows. Though this should not matter since the OS remains the same (Windows 7 Pro x64).

Fullscreen renders the screen area ""unclickable""/static and all animated content is frozen until I return from fullscreen, at which time the VM resumes operation.

I have reinstalled VirtualBox Guest Additions after upgrading the kernel.
I have also tried reverting to an earlier kernel, but I still cannot go to fullscreen mode.

I can go into functioning fullscreen mode when not installing the Guest Additions, but I have a 16:9 screen (1280x800) and the picture when going fullscreen has an aspect ratio of 4:3.

Attached is the VBox.log from a session in which I boot Ubuntu 9.10, tries going fullscreen, reverts to windowed mode, and shuts it down."	Carl-Erik Kopseng
9077	VBoxManage showhdinfo fails on hdd with same uuid as different existing hdd	other	VirtualBox 4.0.8	defect	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
9072	implement copy-on-read for disk images	other	VirtualBox 4.0.8	enhancement	2011-06-14T11:53:04Z	2011-06-14T11:53:04Z	2011-06-14T11:53:04Z	"There is already support for read-only images with copy-on-write semantics. In some cases, where the disk image resides on a NAS connected over a relatively slow network link (e.g. Samba, NFS), it is desirable to have copy-on-read behaviour too:

Whenever a block from the read-only image is read, it is stored in the differential image (which the user can place on a local partition). The second and following accesses to the same block (e.g. when the VM is rebooted) will then be considerably faster.

This way, fast image access can be provided without explicitly copying the entire image to the local machine."	Marc Schütz
8974	--bootable=off doesn't apply to IDE controller	other	VirtualBox 4.0.8	defect	2011-05-26T20:27:00Z	2011-05-26T20:27:00Z	2011-05-26T20:27:00Z	"In deciding what's Hard Disk 0, the controller order is internal. IDE controllers are first in that order, and they can't be excluded, unlike every other type of controller. I don't know that the use case for this is tremendous, so it might be sufficient simply to document it. I was trying to use it in benchmarking to determine the performance difference between SATA and IDE, particularly because some recent bugs have had people suggesting that one ought at least try it. Solaris in particular has problems dealing with changes to the path to its boot device (grub will find the rpool and bootfs, but boot subsequently breaks because other config files store the path to the device), so things break if I've previously installed with a SATA boot VDI but want to try a benchmark with data stored on an IDE data VDI.

I already discussed the particulars on this one with MichalN on #vbox."	Bayard Bell
8904	Missing license information in About Virtualbox window	other	VirtualBox 4.0.8	defect	2011-05-17T00:26:44Z	2011-05-17T00:26:44Z	2011-05-17T00:26:44Z	"Open source software usually has the license information in the app's about window. Instead VirtualBox only says ""Copyright Oracle. All rights reserved"", implying to an enduser that the software is proprietary even if they have not installed the proprietary addons.

I also looked in the Help and while the GPL and many other licenses are included in the Licenses section, there is no mention anywhere to the enduser what license VirtualBox falls under."	Jeremy Bicha
8686	Change process directory to / before forking	other	VirtualBox 4.0.4	defect	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
8877	Ethernet frame larger than 1500 do no pass through bridged ethernet connection	other	VirtualBox 4.0.6	defect	2011-05-11T18:53:35Z	2011-05-11T18:53:35Z	2011-05-11T18:53:35Z	Large ethernet frame (9000 bytes) are dropped when going through a virtual ethernet adapter even when the guest and host are configured for jumbo frame support.	Louis-Philippe Lessard
4562	[feature-request] 'Default Gateway' parameter in DHCP server for host-only networks	other	VirtualBox 3.0.2	enhancement	2009-07-17T21:46:03Z	2011-05-09T05:20:44Z	2011-05-09T05:20:44Z	"Please add the 'Default Gateway' parameter in DHCP server for host-only networks.
Otherwise the TCP/IP configuration in guests which are use the VBox DHCP server is imperfect -- some of them cannot be configured to use any default gateway without to turn off using dhcp."	Michael
8847	Feature Request: Multiple Tabbed Interface	other	VirtualBox 4.0.6	enhancement	2011-05-04T22:08:30Z	2011-05-04T22:40:33Z	2011-05-04T22:40:33Z	Adding a tab interface for multiple VMs functioning at the same time. Tabs are a pretty integral part of multitasking software today. Such a feature would allow ease of use of multiple VMs and streamline the work process.	DNS
8808	Add option to stop machine on error warning	other	VirtualBox 4.0.6	enhancement	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
7642	[feature-request] Reverse Shared Folders	other	VirtualBox 3.2.10	enhancement	2010-10-24T19:17:20Z	2011-04-28T20:29:56Z	2011-04-28T20:29:56Z	"Hello,

I really would like to be able to work on Guest's hard disk from Host. (when guest is running)

This way I could use host's programs to search in guest's HDD, plus process data located on guest's HDD.

For example using Norton Commander on Windows host, is much nicer to manipulate _all_ the data on both Host and Linux guest, rather than use KDE Krusader or Midnight Commander in Linux guest. This simplifies my workflow.

Guest's filesystems should be mountable on host's filesystems (and as Driver Letters).

-Alexey ""Technologov"", 24.10.2010."	Technologov
8730	Portability: please allow to move VMs with Bridged NIC attached	other	VirtualBox 4.0.4	enhancement	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
8704	[feature-request] Mini-toolbar: allow to switch between VMs	other	VirtualBox 4.0.4	enhancement	2011-04-09T17:26:56Z	2011-04-09T17:26:56Z	2011-04-09T17:26:56Z	"Please allow to switch between VMs via Mini-toolbar. This is especially useful for full-screen mode.

Idea by ""Cilliers"", from http://forums.virtualbox.org/viewtopic.php?f=9&t=39186

Attached screenshot.

-Technologov, 9.4.2011."	Technologov
8664	vboxsf causing kernel panic with mounted loopback file system after restore from suspend	other	VirtualBox 4.0.4	defect	2011-04-01T18:28:38Z	2011-04-01T18:28:38Z	2011-04-01T18:28:38Z	"My CentOS 5.5 guest O/S uses a read/write NTFS shared folder from my Windows XP Pro SP3 host operating system drive.  This shared folder is automatically mounted on boot via /etc/fstab to /mnt/host.  Within that shared folder is a 100MB file that functions as a loopback filesystem which was created like this:
{{{
dd if=/dev/zero of=/mnt/host/my-loopback-fs.img bs=1M count=100 && mke2fs -F -j /mnt/host/my-loopback-fs.img
}}}

It can be mounted like:
{{{
mount /mnt/host/my-loopback-fs.img -o loop /mnt/lo-fs
}}}

Once mounted, I close the VM and save the state. 

I then bring the VM back to life. A kernel panic usually sets in seconds after the VM is reloaded. Sometimes it takes 2 minutes, sometimes it is immediate.  Odd things appear with the mounted loopback filesystem if I try to use it such as I/O errors. I've managed to unmount it and remount it before the kernel panic sets in, but I cannot seem to get around the fact that it will eventually occur.

Here's uname -a:
{{{
Linux ffm-023631-vm1.example.tld 2.6.18-194.32.1.el5 #1 SMP Wed Jan 5 17:53:09 EST 2011 i686 i686 i386 GNU/Linux
}}}

I've attached the kernel panic screen and a compiled version of vboxsf.ko."	Greg McLearn
6271	During Clonezilla Live CD Process, Text Only display shifts down so bottom lines appear off screen	other	VirtualBox 3.1.4	defect	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
8625	Shared Floppy Images cannot be accessed from several VMs	other	VirtualBox 4.0.4	defect	2011-03-24T09:16:41Z	2011-03-24T09:16:41Z	2011-03-24T09:16:41Z	"Host: Win7, x64, VBox 4.0.4

I have a shared floppy image, read-only. 

After I start first VM, second VM wouldn't start, erroring: ""Locking of Attached Media Failed"".

I expect read-only floppy images to be accessible to many VMs at once. (like ISO)

-Technologov"	Technologov
8302	Avoid showing VirtualBox GUI when starting in seamless mode	other	VirtualBox 4.0.2	enhancement	2011-02-08T16:58:23Z	2011-02-08T16:58:23Z	2011-02-08T16:58:23Z	When starting a virtual machine snapshot in seamless mode, e.g. by VirtualBox --startvm <mysnapshot> --seamless, the VirtualBox GUI still shows up until <mysnapshot> is running and only then switches to seamless mode. It would be nice if this could be avoided to make it really seamless from the beginning.  	Paolo Virtual
7143	Please expose the IgnoreFlush option to the GUI	other	VirtualBox 3.2.6	enhancement	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
8203	GUI highlighting of running VMs	other	VirtualBox 4.0.0	enhancement	2011-01-28T06:30:52Z	2011-01-28T06:30:52Z	2011-01-28T06:30:52Z	"I would find very useful, in the GUI Manager, some '''graphic indicators''' showing which VMs are '''running''' (for example, red bullets on the right side of the VMs' names) or, at least, a single indicator (maybe near the top command buttons) which stays on while one or more VMs are running.[[BR]]
When using multiple VMs as I do, often keeping some of them minimized, it would be useful, for example before shutting down the host system, to check at a glance whether all VMs are closed."	marcox
8099	Email address trac@virtualbox.org not found	other		defect	2011-01-17T19:38:26Z	2011-01-17T22:45:20Z	2011-01-17T22:45:20Z	"When bug reports are updated, email is sent out to the reporter (among others).  The return email address is 'trac@virtualbox.org', and the subject line contains enough information for Trac to add the reply to the right ticket.

Unfortunately, trac@virtualbox.org does not exist; replies to that address bounce with the error:
{{{
   ----- The following addresses had permanent fatal errors -----
<trac@virtualbox.org>
    (reason: 550 Unrouteable address)

   ----- Transcript of session follows -----
... while talking to mail.virtualbox.org.:
>>> DATA  
<<< 550 Unrouteable address
550 5.1.1 <trac@virtualbox.org>... User unknown
<<< 503-All RCPT commands were rejected with this error:
<<< 503-Unrouteable address
<<< 503 Valid RCPT command must precede DATA
}}}

The ticket #305 from 2007 mentioned this as well, as an aside.

This looks like you need the email2trac plugin for Trac, available here:
http://trac-hacks.org/wiki/EmailtoTracScript"	Penelope Fudd
7837	Feature Request: Option to hide Additions mismatch warning	other	VirtualBox 3.2.12	enhancement	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.
6495	VBox DHCP Server does not respect client identifier	other	VirtualBox 3.1.6	defect	2010-04-05T20:54:36Z	2011-01-11T19:19:37Z	2011-01-11T19:19:37Z	"VBox's build-in DHCP server does not respect the DHCP 'client identifier' option. Only the DHCP 'chaddr' field (typically the MAC address) is respected. 

Problem is that this is a violation of the DHCP protocol. (RFC 2131).
Below is an extract from the RFC where I've highlighted in bold what I think VBox does not implement:

    ""A DHCP server needs to use some unique identifier to associate a
    client with its lease. The client MAY choose to explicitly provide
    the identifier through the 'client identifier' option. If the client
    supplies a 'client identifier', the client MUST use the same 'client
    identifier' in all subsequent messages, and '''the server MUST use that
    identifier to identify the client'''. If the client does not provide a
    'client identifier' option, the server MUST use the contents of the
    'chaddr' field to identify the client. It is crucial for a DHCP
    client to use an identifier unique within the subnet to which the
    client is attached in the 'client identifier' option. Use of
    'chaddr' as the client's unique identifier may cause unexpected
    results, as that identifier may be associated with a hardware
    interface that could be moved to a new client. Some sites may choose
    to use a manufacturer's serial number as the 'client identifier', to
    avoid unexpected changes in a clients network address due to transfer
    of hardware interfaces among computers. Sites may also choose to use
    a DNS name as the 'client identifier', causing address leases to be
    associated with the DNS name rather than a specific hardware box.""


The current functionality of VBox's DHCP server creates problems for DHCP clients that for one reason or another sends a 'client identifier' as part of the DHCP negotiation and expects it to be respected over the 'chaddr' field.

My suspicion: VBox's DHCP server in its use of data structures seems to implement the BOOTP protocol rather than the DHCP protocol. (DHCP was invented as a successor to BOOTP in 1993). 


== How to implement: ==


Internally the DHCP Server should work with a unique lease identifier defined as follows (pseudo code):


{{{
If (! IsNull(DHCP-ClientIdentifier) )
  DhcpUniqueLeaseId = DHCP-ClientIdentifier
Else
  DhcpUniqueLeaseId = DHCP-chaddr
}}}



"	lmanman2
5811	Feature-request: New Storage GUI: VM/Storage Settings	other	VirtualBox 3.1.2	enhancement	2009-12-20T20:19:09Z	2011-01-08T07:28:54Z	2011-01-08T07:28:54Z	"
We (me+Sasquatch+other members) came up with few ideas, that seem better than current design.

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

Section 1: VM/Storage Settings

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

Look at the original problem: (BETA1)

http://img269.imageshack.us/i/smallbug01.png/

It has *way* too small fields for ISO and VDI names. Very bad. This is the biggest problem for config GUI.

This solves several problems: (positive)

1. Very short ISO and VDI names. <-- biggest issue

2. Too much white space in the ""controllers"" list... as it is infrequently used. (scroller can be used there)

3. This idea is minor redesign and can be implemented in V3.1.x -- afterwards we may re-think the GUI design again.

This doesn't solve problems: (neutral)

1. No separation between devices and mount (mpack's idea)

2. It also still looks possible to mistake the ""remove device"" and ""unmount media from device"" functions. (mpack's critics)

3. How-to Add Hard Disk Questions

This hurts the current Design in the following ways: (negative)

1. (None Found)

update: Dsen from Sun think it is possible to divide this into three panes, ""Storage Tree"", ""Attributes"", ""Information"", and make each one floating and user-configurable. Would be great ! (if it is resizeble)

And look at screenshot attached, the proposed design GUI.

-Technologov, 20.12.2009."	Technologov
8020	Add appropriate comments for strings that are used in other strings (in translation *.ts files)	other	VirtualBox 4.0.0	enhancement	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
7954	Different VBox question text deleting snapshots w/o merging	other	VirtualBox 4.0.0	enhancement	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
7965	Remove confusing geeky-internal VirtualBox snapshot language from GUI	other	VirtualBox 3.2.12	defect	2010-12-31T08:48:16Z	2010-12-31T08:48:16Z	2010-12-31T08:48:16Z	"On forum I have noted several questions about deleting and restoring snapshots. All what I see the cause is just a geek speaking language in VirtualBox snapshot GUI which is not needed and makes non-geek users very confused. I think that messages should be more non-geek friendly.[[BR]]

When deleting a snapshot there is a message: ""Deleting the snapshot will cause the state information saved in it to be lost, and disk data spread over several images files that VirtualBox has created together with the snapshot will be '''merged into one file'''...""[[BR]]

Above information is too geeky. On forum I have read several threads, the last one is:
http://forums.virtualbox.org/viewtopic.php?f=1&t=37552&p=168674#p168674
that people are thinking that data from two snapshots are going to be merged. They are confusing logical snapshots from physical vdi file restructuring.[[BR]]

I think that VirtualBox is not a geek system anymore and some little cosmetic changes should appear in VirtualBox snapshot GUI text messages. It does not bother me, I am using VirtualBox for years and I understand all this virtual-geek terminology, but new non-geek users are starting to use virtualization technology, because it became easy to use.[[BR]]

I think the above text should be changed, to something like: ""Deleting the snapshot will cause the state information saved in it to be lost, and disk data spread over several images files that VirtualBox has created together with the snapshot will be '''restructured'''...""[[BR]]

Second problem is, what is also too geeky is the length of message itself, it is so lengthy that you have to remember several things like ""losing data from snapshot"", ""long process of image restructuring"" and some confusing info related to ""merged"" word. It would be nice if message would be simplified, way simplified.[[BR]]

Third problem, if the process of deleting snapshot is lengthy there are some other info displayed like ""merging"", ""differencing image"" etc, this all all geeks info that non-geeks gets a lot of confusion and wrong impression that some snapshot data from logical point of view are merged. Instead of this ""merging/differencing"" messages, just give a message: ""Deleting snapshot...""[[BR]]
========[[BR]]
The similar problem appears when you try to restore a snapshot, the message is: ""Are you sure... This will cause you to '''lose your current machine state''', which cannot be recovered.""[[BR]]

You are restoring and getting some info of ""deleting"" this is strange. So user has to click on Cancel, create a snapshot of current state (to avoid losing current state data) and then go back to restore and click on restore snapshot. This is way too confusing for non-geek user.[[BR]]

I think this dialog should be changed. Message should be something like: ""You are going to restore a snapshot.""[[BR]]
Bellow add checkbox with text: ""Save current state before restoring old snapshot"" and make it by default checked.[[BR]]

In this case no fearful message of deleting/losing a current state is posed to user that is trying to restore a snapshot. And current state snapshot is automatically created (to avoid losing current state information), because of the checkbox.

It would also be nice if state of checkbox is preserved, so if checkbox is unchecked then unchecked state of checkbox is preserved when next restore is executed - this will make geek users happy - that they don't need to uncheck every time.[[BR]]
========[[BR]]
I suggest that for new release like v4.1 you try to remove geek language from Virtualbox snapshot GUI. You know VirtualBox is getting so popular that non-geek masses are using it."	grof
7896	VB creates wrong .vmdk on Mac OSX	other	VirtualBox 4.0.0	defect	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
7836	[feature-request] Floppy: Create Virtual FAT images from host's filesystem	other	VirtualBox 3.2.12	enhancement	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
7825	"[feature-request] Scale Mode: please make it work with ""Mouse integration"""	other	VirtualBox 3.2.12	enhancement	2010-12-10T14:43:11Z	2010-12-10T14:43:11Z	2010-12-10T14:43:11Z	"v4.0.0-BETA1 

Guest desktop and Scale Mode: please make it work with ""Mouse integration"".

The user experience of Scale Mode will improve.

-Technologov, 10.12.2010. "	Technologov
7824	[feature-request] Scale Mode: should optionally produce window w/ menus	other	VirtualBox 3.2.12	enhancement	2010-12-10T14:38:56Z	2010-12-10T14:38:56Z	2010-12-10T14:38:56Z	"v4.0.0-BETA1

Scale Mode produces minimal window, without menus and toolbar (SDL-like).

It would be nice to have an option with full menus, like normal ""Windowed Mode"".

-Technologov, 10.12.2010."	Technologov
7820	[feature-request] Scale Mode: OpenGL 3D Accelerated graphics should scale	other	VirtualBox 3.2.12	enhancement	2010-12-10T14:27:16Z	2010-12-10T14:27:16Z	2010-12-10T14:27:16Z	"OpenGL 3D Accelerated graphics should scale (TuxRacer). And with v4.0-B1, it doesn't.

Normal 2D surfaces scales fine.

-Technologov"	Technologov
7694	Add SCSI device passthrough support	other	VirtualBox 3.2.10	enhancement	2010-11-07T12:04:26Z	2010-11-07T14:25:44Z	2010-11-07T14:25:44Z	"Unable to register raw SCSI tape device (used for controlling wide format print / scan mode).

{{{
VBoxManage -nologo internalcommands createrawvmdk -filename scanner.vmdk -rawdisk /dev/st0
Error opening the raw disk '/dev/st0': VERR_DEV_IO_ERROR
The raw disk vmdk file was not created
}}}

Right now VmWare ALREADY supports this type of SCSI passthru (as with LPT passthru)"	linuxrulez
7681	extended keyboard layout support under the builtin vnc server (OSE)	other	VirtualBox 3.2.10	defect	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
1194	Request for seamless VRDP feature	other	VirtualBox 1.5.4	enhancement	2008-02-14T12:31:39Z	2010-10-26T16:53:51Z	2010-10-26T16:53:51Z	Seamless mode is very nice. It'll be much more nice if you could see in seamless mode remote (with VRDP or other way) machines. 	S
7570	VNC shows password in commandline	other	VirtualBox 3.2.10	defect	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
721	Feature request: ieee1394 (Firewire) UHCI/OHCI pass-through support	other	VirtualBox 1.5.0	enhancement	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
7441	"Expose ""--vrdpaddress 127.0.0.1"" in the GUI"	other	VirtualBox 3.2.8	enhancement	2010-09-07T09:53:53Z	2010-09-13T09:42:41Z	2010-09-13T09:42:41Z	"RDP is not just for remote access but also for local, headless machines. So it would be great to add a very simple ""restrict to local host"" checkbox in the Remote Display configuration tab. This checkbox would just configure ""--vrdpaddress"" to ""127.0.0.1"", for obvious security benefits.

I realize this feature is already available on the command line but having it exposed in the GUI would make a lot more of people using it, making VirtualBox a generally more secure product.

A more advanced (and maybe overkill) variant of this feature would let the user bind not just to its loopback interface but to any of its network interfaces.
"	mh
7340	Please make 3D Video card name consistent across APIs	other	VirtualBox 3.2.8	enhancement	2010-08-17T05:28:59Z	2010-08-17T05:28:59Z	2010-08-17T05:28:59Z	"Currently several API's show VBox card differently.

Windows GDI and DirectDraw shows card as ""VirtualBox Graphics Adapter""

OpenGL shows the VBox card card as ""Chromium""

Direct3D shows the card as either ""GeForce FX 5200"" or ""GeForce 3"", depending on version of VirtualBox/WineD3D.

This is misleading, and better should be shown as ""VirtualBox Graphics Adapter"" in all places. This would require modification to Chromium and WineD3D.

A related bug #3541 exists, and recommends a passthru approach. The problem with this approach is that the VBox card is functionally less than the real card, so it is confusing. The passthru approach fits better for VT-d use cases IMO.

-Technologov, 17.8.2010."	Technologov
6632	Virtualbox should warn if you aren't in vboxusers group	other	VirtualBox 3.1.6	defect	2010-05-03T13:18:08Z	2010-07-30T14:38:55Z	2010-07-30T14:38:55Z	"The scenario I keep finding myself here is as follows.

I perform an iPhone upgrade, the first half of the upgrade works since I can see the iphone over usb since the permissions are correct since I'm in whatever group means camera's are viewable.

The second half of the upgrade fails because the iphone turns into a different USB device, Which I know longer have permissions for unless I'm in vboxusers.

Would be a lot less painful if virtualbox just warned you"	John Ferlito
682	Binary prefixes	other	VirtualBox 1.5.0	defect	2007-09-12T23:34:56Z	2010-07-30T06:55:21Z	2010-07-30T06:55:21Z	"I suggest IEC standard prefixes (binary) for file size are used instead of commonly used but ambiguous prefixes KB, MB, ...

I encountered these in localization file.

Binary prefixes are defined in IEC 60027-2:2005
"	helix84
7246	VLAN support for virtual adapters	other	VirtualBox 3.2.6	enhancement	2010-07-28T17:00:47Z	2010-07-28T17:23:02Z	2010-07-28T17:23:02Z	In VMWare ESX you can add new NIC to virtual machine and give that virtual adapter it's own VLAN directly without configuring it in that virtual machine. This kind of feature should be in Virtual Box too.	raspi
6994	Raise maximum number of Host-Only networks	other	VirtualBox 3.2.4	enhancement	2010-06-14T11:31:08Z	2010-06-16T22:32:56Z	2010-06-16T22:32:56Z	The current limit of 8 is plenty for any reasonable application, but there are a lot of unreasonable applications out there.  In my case, I need at least 60 Host-Only networks.  I was able to achieve this by editing the VB OSE source code, but it would be nice if this was an official enhancement.	UglyPercy
6995	Permit names to be specified for Host-Only adapters	other	VirtualBox 3.2.4	enhancement	2010-06-14T11:34:49Z	2010-06-14T11:34:49Z	2010-06-14T11:34:49Z	"As opposed to the current fixed scheme of ""vboxnet0"", etc..  This would make it possible to encode various information in the name of the adapter, e.g. ""HOSTONLY_2_3"" might be recognized as interface 3 of VM 2.  This would enable one to easily collect per-VM statistics, etc.."	UglyPercy
6992	Add protections again DHCP rogue activity	other	VirtualBox 3.2.4	enhancement	2010-06-14T11:27:50Z	2010-06-14T11:27:50Z	2010-06-14T11:27:50Z	"With certain guest OS setups, it is very easy for the VB DHCP servers to turn into rogues, answering DHCP requests from other physical computers on a LAN (potentially many on a huge LAN).  This is a very unpleasant phenomenon, potentially career-ending for the engineer in some environments.  

If there is any way so, by default, restrict VB DHCP servers such that not only would they only serve requests seen on Host-Only interfaces, but would ''only'' serve requests actually generated by interfaces associated with local guest VM's, it would be very helpful (seems like a quick MAC address check would be 99% of the solution).  That way, even confusing setups involving accidental guest OS bridging (e.g. Linux ""brctl"") between Host-Only and Bridged/NAT adapters would not cause LAN disasters."	UglyPercy
6888	Automatic Name Wizard GUI issues	other	VirtualBox 3.2.0	defect	2010-06-04T03:50:52Z	2010-06-04T07:42:37Z	2010-06-04T07:42:37Z	"Automatic Name Wizard GUI: Windows 7 32 bit recognized as ""Windows 2000""

-Technologov, 4.6.2010."	Technologov
1735	feature-request: Hardware Virtualization GUI Info Utility	other	VirtualBox 1.6.2	enhancement	2008-06-16T21:23:28Z	2010-06-02T18:46:04Z	2010-06-02T18:46:04Z	"
Hi,

In continuing to the bug #1240, and other VT-x related bugs, I can say from personal experience, that hardware virtualization is not always transparent enough.

That is: Hardware virtualization becomes more and more sophisticated, but I'we not seen any ""user-friendly"" utility (either CLI or GUI), that shows that hosts VT capabilities.

I request either making a separate cross-platform utility for that purpose, or additional GUI Info Dialog within VBox GUI.

It must show the following:
 * Intel VT-x
 * Intel VT-d
 * Intel Extended Page Tables (EPT)
 * Intel !FlexPriority
 * AMD-V
 * AMD Nested Page Tables (NPT)
 * Whenever all the CPUs support all the features
 * Whenever other virtualizer already uses those features currently (so they are not accessible to VBox)
 * Whenever BIOS enables/disables those features.

Now, Linux has some limited capabilities in this field, and other platforms, provide even less info to the end-user.

It will really make life easier for lots of people.

-Technologov, 17.06.2008."	Technologov
6692	go to fullscreen mode when maximizing the guess window	other	VirtualBox 3.1.8	enhancement	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
1751	Allow SMBIOS information to be copied from host	other	VirtualBox 1.6.2	enhancement	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
893	[feature-request] Revolutionary CLI for mass-management of Virtual Linux Servers	other	VirtualBox 1.5.2	enhancement	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
6752	Option to ask for password when leaving virtual machine	other	VirtualBox 3.2.0	enhancement	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
6645	"Option to configure USB devices out of the Devices->""USB Devices"" menu"	other	VirtualBox 3.1.6	enhancement	2010-05-05T08:02:42Z	2010-05-05T08:02:42Z	2010-05-05T08:02:42Z	"It would be useful to be able to prevent host USB devices from appearing in the menu shown in the host's window for the VM's screen when using Devices->""USB Devices"".

The big benefit would be when the host's keyboard and/or mouse is a USB device because attaching either of these to a VM stops them working on the host and (ironically) on the guest too.

For other USB devices the benefit would be tidiness and simplicity.  In the case of USB devices always used with a particular VM it could prevent operational mistakes.

This enhancement could be implementated in the configuration GUI in the USB->""USB Device Filters"" list.  At the moment (version 3.1.6) this list shows all the USB devices on the host and the checked ones are attached to the VM when the VM is started.  Deleting an item from this list has no effect.  Perhaps deleting a device from this list could stop that device appearing in the Devices->""USB Devices"" menu."	Charles
1929	[feature-request] Allow Custom, per-VM BIOS	other	VirtualBox 1.6.4	enhancement	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
418	Sharing a single VM on multiuser accounts (Ubuntu)	other	VirtualBox 1.4.0	enhancement	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
6602	runtime change remembered through First Run Wizard	other	VirtualBox 3.1.6	defect	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
3990	VLAN support	other	VirtualBox 2.2.2	enhancement	2009-05-11T14:02:13Z	2010-04-23T13:21:44Z	2010-04-23T13:21:44Z	"Hi,

It would be great that, Internal Networking mode at least, supports VLANs. This would avoid creating as many IntNets as needed (V)LANs wich, with a maximum number of 8, can be rapidly limiting.

You can look at the following post for a scenario.

http://forums.virtualbox.org/viewtopic.php?p=75416

Thank you for this great piece of software

Bests"	Tarax
5668	[Feature-request] Global Shared Folders	other	VirtualBox 3.1.0	enhancement	2009-12-04T19:24:23Z	2010-04-22T11:37:31Z	2010-04-22T11:37:31Z	"It would be nice, if I could share host's folders with all VMs at once, instead of configuring shared folders for each VM.

This feature request is about host side (VBox) configuration only, not about guest side mapping of the folders.

-Technologov, 4.12.2009."	Technologov
6500	Virtualbox BIOS should implement USB legancy support	other	VirtualBox 3.1.6	enhancement	2010-04-07T00:08:05Z	2010-04-07T00:08:05Z	2010-04-07T00:08:05Z	"Hello,

I use a VM as a multi-seat solution (USB input devices on a second monitor). However, I noticed that USB HID devices are not supported before OS kernel takes place. In boot manager, the usb keyboard is useless. I guess this is related to legancy usb suport inside BIOS.

Maybe, this will help in a possible option to use the virtual keyboard as an USB key board."	Luiz Angelo Daros de Luca
6307	Partitions larger than 2T are not supported with Raw disks	other	VirtualBox 3.1.4	defect	2010-03-01T23:48:48Z	2010-03-18T18:31:54Z	2010-03-18T18:31:54Z	"Trying to create a raw partition for an 8TB Array on the host machine.  The partition IS created but will not mount on the guest.  The code for the creation of the raw disk looks correct, but the problem is the partition table in my opinion.

On the host, '''file -t''' sees this raw disk as a ext3 file system.  On the guest, the same command sees the raw disk as '''data'''.

My proof to this is that listpartitions command only sees 2TB.
{{{
VBoxManage internalcommands listpartitions -rawdisk /dev/sdc

Sun VirtualBox Command Line Management Interface Version 3.1.4
(C) 2005-2010 Sun Microsystems, Inc.
All rights reserved.

Number  Type   StartCHS       EndCHS      Size (MiB)  Start (Sect)
1       0xee  0   /0  /1   1023/254/63       2097151            1
}}}

parted -l shows:
{{{
Model: TRUSTED Mass Storage (scsi)
Disk /dev/sdc: 8796GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number  Start   End     Size    File system  Name  Flags
 1      17.4kB  8796GB  8796GB  ext3
}}}

My guess, having just scanned the code is that the problem lies within /src/VBox/Frontends/VBoxManage/VBoxInternalManage.cpp

In the '''partRead''', starting at line 646, it looks we are using u32 instead of u64.

That may be just part of the problem as 8T needs a GPT partition table and I am not sure that VB will read that correctly.  I would need to do more research to find that out myself and learn the VB code.

Because the bug exists on the host in reading the partition table in the first place, I am unsure of the VBox.log file needed.  I have attached a file with the host trying to connect using a 

The drive itself is a Drobo connecting via USB.

The reason this is a MAJOR priority is that this disk is a USB drive and ticket 4261 would also solve my problem.  But seeing as that is listed as minor and 8 months old, and VB will only give ~600kB/s bandwidth to USB devices, this becomes a MAJOR priority to guests working with large files.  Either solution would work.

As it stands right now, VBox is NOT able to deal with large files or large systems."	Tony Plack
543	confirm before doing dangerous commands or allow to disable those commands	other	VirtualBox 1.4.0	enhancement	2007-08-08T00:45:24Z	2010-02-25T20:20:05Z	2010-02-25T20:20:05Z	"I usually press combo keys by both hands. Too often I reset machines by mistakenly pressing Right Ctrl with R (which usually means ""reload"").
I don't want to change hot key because I see no other hotkey better than that. So please, show a confirmation dialog before doing commands such as reset, close... or just allow me to disable them.

BTW, thanks for this great product!"	pclouds
5768	[feature-request] Allow VM to run faster or slower than normal time	other	VirtualBox 3.1.0	enhancement	2009-12-16T16:04:15Z	2010-02-03T12:04:16Z	2010-02-03T12:04:16Z	"bochs and DOSbox can speed up or slow down VM by emulating CPU and/or timer slower or faster than normal. I would like to have a similar feature here.

In virtualization world, a possible way to achieve this, is to increase/decrease timer interrupt injections, so VM can either run at 50% speed or 200% speed.

In this case clock time sync in Guest Additions must be turned off.

It is (sometimes) useful for gaming.

-Technologov"	Technologov
6036	[Docs] Please document major dropped features	other	VirtualBox 3.1.2	defect	2010-01-20T13:11:26Z	2010-01-20T13:11:26Z	2010-01-20T13:11:26Z	"Besides documenting new supported OSes, I would like to see VBox also documenting drop in host OSes.

The following host platforms were dropped:

Windows 2000 - dropped in VBox 1.6.0

Linux 2.4 - dropped in VBox 2.?.?

Mac OS X 10.4 Tiger - dropped in VBox 3.1.0

If some guest OS is no longer supported by Guest Additions, I would like to know it too...

Please make it more clear, at least in the changelog. Dropped host platform is also ""major feature"".

-Technologov, 20.1.2010"	Technologov
5959	[feature-request] GUI: Show 3D Acceleration in status bar	other	VirtualBox 3.1.2	enhancement	2010-01-11T11:37:31Z	2010-01-11T21:53:23Z	2010-01-11T21:53:23Z	"Just like VT-x, Mouse Integration, and other mini-icons in VBox Status Bar, I would like to see when 3D support is active. (both host side and guest side)

-Technologov, 11.01.2010"	Technologov
5878	Virtual Media Manager drag and drop support	other	VirtualBox 3.1.2	enhancement	2009-12-31T23:26:40Z	2010-01-03T16:29:49Z	2010-01-03T16:29:49Z	Virtual Media Manager lacks drag and drop support for adding hdd/cd/dvd/floppy images to repository. It is not comfortable to click Add and browse to directory with images, when I already have folder opened.	Ondrej Galbavy
3061	Add Virtual Disk Tasks to Virtual Media Manager	other	VirtualBox 2.1.0	enhancement	2009-01-16T14:24:45Z	2009-12-01T20:05:14Z	2009-12-01T20:05:14Z	"On a periodic basis one can save a fair deal of disk space on a host by running ""VBoxManage modifyvdi [SomeVDI] compact"".  I would suggest that this documented but currently CLI-only feature be added to the Virtual Media Manager portion of the VirtualBox GUI.  Being able to manually specify when to compact a .vdi file in the GUI would save a lot of hassle for less-CLI-savvy users.

To use such a feature one might:
Open VirtualBox
Open the Virtual Media Manager
Select a Virtual Disk Image
Click a ""Compact"" button in the toolbar

Integration of virtual disk image management into Guest Additions could suggest that the user ""Compact"" when the guest's reported disk usage is beneath some threshold of the actual disk usage of the .vdi file on the host.
To use such a feature in a Windows guest one might:
Install Guest Additions
Guest Additions could run ""dir"" or some similar command in the background to get Windows' current free disk space estimate
VirtualBox could compare Windows' reported free disk space to the space left on a virtual disk image (Maximum size - current .vdi file size)
If the free space number differ significantly (say 20%) VirtualBox could, from within the guest, prompt the user to run a ""Guest VDI Compaction Routine""
VirtualBox could run ""sdelete -c"" in the background on the guest, send a shutdown signal after sdelete finishes, and then compact the .vdi once the guest is shut down

This second approach would be much more OS-specific and may not work (or be necessary) with all operating systems and file systems.  It would, however, simplify things for former Windows users who most run Windows for a handful of programs which have no practical replacements on the host platform."	Ryan Stonecipher-Fisher
2104	Better management of VMs, Disks and Snapshots in GUI	other	VirtualBox 2.0.0	enhancement	2008-09-05T19:58:32Z	2009-12-01T19:38:50Z	2009-12-01T19:38:50Z	"There are many features available in VirtualBox that are not present in the GUI. Although some of them are of advanced nature, others are very basic functionality that should be present for a long time.

I have been awaiting for these features since my first use in 1.4 and I really thought version 2.0 with the QT4 GUI would address them.

The features that I really miss in the GUI are:

* Register/Unregister an Existing VM[[BR]]
* Register a Disk as Writethrough[[BR]]
* Compact a VDI (show an Alert pointing to the manual section on the first time, talking about defrag, nullfile, etc)[[BR]]
* Take snapshot of a VM with a Writethrough disk (just ignore the disks instead of giving a fatal error, like VMWare)[[BR]]

Thanks."	nvivo
976	Feature request: automatic snapshots with merge	other	VirtualBox 1.5.2	enhancement	2007-12-14T01:50:33Z	2009-12-01T19:35:51Z	2009-12-01T19:35:51Z	"How about adding auto snapshots with auto merge - In other words the system could be configured to automatically create a snapshot before booting the vm and them merge the snapshot on the next on two successful snapshots thereafter.

[snapshot1] -> [snapshot2] -> [snapshot3]
                              [merge sbapshot1]

This feature would be great and helps to eliminate creating manual snapshots. It could event be useful in the event of (guess) system failure.

Auto snapshots could be enabled at anytime. We could event enable it after taking a few manual snapshots

[manual_snapshot1] -> [manual_snapshot2] -> [auto_snapshot]

"	xwisdom
5628	"Suggestion: Add a ""minimise writes"" option to Windows Guest Additions"	other	VirtualBox 3.0.12	enhancement	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
286	make console screen available when vm is powered off & addevirtual power buttons	other	VirtualBox 1.3.8	enhancement	2007-04-20T07:35:08Z	2009-11-27T21:41:21Z	2009-11-27T21:41:21Z	"also see my posting in the german forum for this: http://www.virtualbox.org/discussion/2/663

i think having access to the console of a vm via rdp is a great feature.

it would be even more great (very nice for VDI, Virtual Desktop Infrastructure -> http://www.vmware.com/partners/vdi.html) , if rdp access would not only be available if the VM is being powerdt on, but also when it is powered off - i.e. don't get disconnected when VM reboots/powers down.

the real killer here would be some feature, to add virtual power buttogns to that virtual rdp screen - so that after the admin adding a vm and ""enabling the desktop"" , the user could power on, suspend, reset, stop his own VM just via rdp - without any additional tools.

comments ?"	roland
715	[feature-request] Make virtual monitor (screen/display) customizable	other	VirtualBox 1.5.0	enhancement	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
5557	Allow user to specify network card option ROM image, and ship default PXE images for boot.kernel.org	other	VirtualBox 3.0.12	enhancement	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
5547	[feature-request] Log all loaded drivers currently running on host	other	VirtualBox 3.0.12	enhancement	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
3128	Fix PCI ID vendor	other	VirtualBox 2.1.2	enhancement	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
2578	Update sections 3.4.3 and 3.4.4 to reflect current functionality	other	VirtualBox 2.0.4	defect	2008-11-06T15:18:54Z	2009-11-15T22:09:43Z	2009-11-15T22:09:43Z	"'''Section 3.4.3'''

We've just had a novice user complain ([http://forums.virtualbox.org/viewtopic.php?p=44872| Help: Recover data lost from revert to snapshot?]) about the dangers of the ""Revert to the current snapshot"" checkbox.  He checked this during his shutdown and lost a lot of work.  His main complaints where (i) It isn't at all clear of the consequences of this; and (ii) there is no ""Are you sure that you want to delete your current work in progress confirmation.""

As to the second point the functionality here is consistent with the VBox GUI snapshot management (no confirmations either).  My main issue here is that the screenshot given in 3.4.3 is out of date. The current dialogue box now includes a ""Revert to the current snapshot"" checkbox.  This section in the User Guide should mention this and discuss what this is and what the consequences of checking it are.

'''Section 3.4.4'''

The note-box in this section states: ""In order to prevent such data loss while still making use of the snapshot feature, it is possible to add a second hard drive in “write-through” mode using the VBoxManage interface and use it to store your data. As write-through hard drives are not included in snapshots, they remain unaltered when a machine is reverted.""

This is sensible and what VBox should do, it is also factually incorrect.  If you try this then VBox raises an error:  
{{{
Cannot take a snapshot when there is a Writethrough hard disk attached ... E_FAIL (0x80004005)
}}}"	Terry Ellison
171	More GUI commands	other	VirtualBox 1.3.6	enhancement	2007-03-06T19:22:14Z	2009-11-14T23:53:29Z	2009-11-14T23:53:29Z	"Hi,

it would be nice to have more gui commands available.
For instance the duplication, compacting (, resizing) of a virtual harddisk.


Greets Reiner"	Reiner
5452	Auto detect active network interface	other	VirtualBox 3.0.10	enhancement	2009-11-12T12:54:32Z	2009-11-12T12:54:32Z	2009-11-12T12:54:32Z	"If you have two network interfaces (wireless and wired), would be good that VirtualBox can detected which is currently active.
You can add a checkbox to Settings -> Network -> Name with the option ""Autodetect (On/Off)"".

I commend you for your great work.
Regards. "	fgm81
5392	VRDP Multiconn looses track of connection details	other	VirtualBox 3.0.10	defect	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
5344	Add Haiku to the list of supported OS	other	VirtualBox 3.0.10	enhancement	2009-10-30T11:13:59Z	2009-10-30T11:13:59Z	2009-10-30T11:13:59Z	"Hi,

I played with Haiku with the newest VBox version. Apart from the GuestAdditions, everything seems to work fine. So it would be nice to see Haiku in the list of supported guest OS.

Regards, Stefan"	Stefan Ritter
5335	When running a VM, Hard Disks should be opened ShareMode=0 to prevent other processes writing to them	other	VirtualBox 3.0.8	defect	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
1944	VirtualBox Amazon EC2 Integration	other	VirtualBox 1.6.4	enhancement	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
5172	Improve RDP audio latency	other	VirtualBox 3.0.8	enhancement	2009-10-09T02:05:10Z	2009-10-09T02:05:10Z	2009-10-09T02:05:10Z	Currently, the latency of audio playback when connecting to a !VirtualBox RDP server is over half a second. This applies even when connecting to a !VirtualBox RDP server running on the local machine (i.e. localhost). While this is probably satisfactory for many users, this is extremely poor for vision impaired screen reader users who administer remote !VirtualBox machines. I understand that audio playback latency will never be instantaneous, but I am hopeful that this can at least be improved somewhat. Note that audio latency when connected to a Microsoft Windows machine over RDP is somewhat less than with the !VirtualBox RDP server.	James Teh
5053	options that are unavailable should be deselected in addition to being grayed out	other	VirtualBox 3.0.6	defect	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
4673	please add a machine configuration option to always show the boot device menu	other	VirtualBox 3.0.2	enhancement	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
3813	Discarding a Snapshot should not decrease space left on the device before increasing it	other	VirtualBox 2.1.2	defect	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
4338	enable/disable features of guest additions	other	VirtualBox 3.0.0	enhancement	2009-07-01T12:27:23Z	2009-07-09T12:50:35Z	2009-07-09T12:50:35Z	"You are currently not able to edit settings of the guest additions. 
I would like to have an options-screen that enables you to (for example) (temporary) disable time synchronisation. "	Sander
4367	Better folder sharing ideas	other	VirtualBox 3.0.0	enhancement	2009-07-02T22:30:04Z	2009-07-03T08:16:42Z	2009-07-03T08:16:42Z	"It took me some time to figure out how to do folder sharing with VMs and it seems from my research that I'm not the only one.  Some suggest using a smb share if the host is a linux OS.

A couple of suggestions, though not sure how hard to implement:

 * Ease the mapping, possibly something automatic:
 Currently for windows guests, you have to share the folder as a temporary or fixed share.  Then in addition to that you have to go into windows and create a mapped drive for that share.  That second part I didn't know about because on the mac, from what I recall it maps the share automatically in parallels and vmware fusion.

 It would be nice if something default could be done, like a share automatically created and a shortcut created on the desktop of the windows guest.

 If not that, at least give information in the window that creates a share that additional steps are necessary to see the share on the guest, maybe a link to help or some verbiage in the window itself.

 * Be able to drag and drop files - in addition it would be nice to have a way to drag and drop files between guest and host transparently.  Again, not sure how hard this is, but I recall that vmware fusion did that on the mac.  It's extremely nice :)."	Jeremy
4229	Allow specification of the configuration directory (VBOX_USER_HOME) from the command line.	other	VirtualBox 2.2.4	enhancement	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
3064	Wanted pre-start post-stop scripts	other	VirtualBox 2.1.0	enhancement	2009-01-16T22:17:29Z	2009-05-30T19:53:15Z	2009-05-30T19:53:15Z	"It would be very nice to be able to add a script/program so its run before resp after the vm.

Use case:
VBoxManage setextradata  global|<uuid>|<name> prestart /full/program/path_for_start

VBoxManage setextradata  global|<uuid>|<name> postrun /full/program/path_for_stop

These programs would be called with the machine name as parameter and could mount/unmount partitions(nice for rawmdk) or check other conditions.
If prestart fails(non-zero exit code) then the start would be aborted and whatever the script printed on stderr would be displayed.

 "	Bengt-Arne Fjellner
2957	[Suggestion] ISZ Compressed ISO Support	other	VirtualBox 2.1.0	enhancement	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
3814	All VMs running on X partition should pause (stop running) when there's only certain amount of space left on the X partition	other	VirtualBox 2.2.0	defect	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
3800	global alt-tabbing?	other	VirtualBox 2.2.0	enhancement	2009-04-22T00:17:06Z	2009-04-22T00:17:06Z	2009-04-22T00:17:06Z	I don't know if anyone has come up with this idea yet, but wouldn't it be nice if, by means of Guest Additions, window switching through Alt-Tab worked together for guest and host?	egasimus
3010	VM control on powerdown/reboot	other	VirtualBox 2.0.4	enhancement	2009-01-11T06:41:34Z	2009-01-11T06:41:34Z	2009-01-11T06:41:34Z	"It would be nice to control what the VM does when it tries to powerdown/reboot, similar to the control you get when using qemu.

Currently, if a VM is started from a script it must be polled to check if the VM has shutdown.

Image trying to create an unattended windows install via a script - the VM reboots during the install (which is a time you can make modifications to the VM filesystem if you want) but you can't tell when that happens.

The same goes for completing the install - there's no way to detect that installation has completed (windows just reboots the machine again).

A separate problem is that linux guests cannot poweroff the machine after they finish install in an OSX host (ie, debian lenny).


BTW, major is is a bit misleading as a default/medium priority (I know it's the default that comes with trac).  Wouldn't priorities of (very low, low, normal, high, very high) be a little bit more natural/meaningful?

"	andrew.sharpe.7.9
2906	Defining a keyboard filter	other	VirtualBox 2.1.0	enhancement	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
1415	using keyboard shortcuts to switch virtual desktops on the host while in full-screen mode	other	VirtualBox 1.5.6	enhancement	2008-04-15T12:07:47Z	2008-08-27T23:06:49Z	2008-08-27T23:06:49Z	"I would like to be able to run VirtualBox, full-screen, in a virtual desktop and still being able to use the Gnome (or KDE, or whatever) keyboard shortcuts to switch to other virtual desktops on the host machine.

Currently, I have to: first leave full-screen mode, then select a different windows and finally, use the keyboard shortcuts to move to a different desktop. It is a real nuisance."	Salvador Fandino
1526	Virtualbox 'Native' Menu of the Virtual Machine	other	VirtualBox 1.6.0	enhancement	2008-05-10T05:30:53Z	2008-08-19T20:26:56Z	2008-08-19T20:26:56Z	"Having a menu under the Applications menu(GNOME [linux OS]) wich is called 'VirtualBox' wich contains submenus of every virtual machine you have would be very useful, each of these submenus would contain the ""Start > all programs"" content of each of em, making it faster and easier for an end-user to access applications wich require Windows to be running, but these applications will run in seamless mode by opening them within this submenu making it feel like its a native application."	marcos
1888	"Option to configure a VirtualBox VM to automatically ""save the machine state"" upon exciting - and do this minimized."	other	VirtualBox 1.6.2	enhancement	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
767	[documentation] Explain to users how-to run VirtualBox on Windows in background/as a service on PC boot	other	VirtualBox 1.5.0	enhancement	2007-10-11T08:54:47Z	2008-07-15T14:16:57Z	2008-07-15T14:16:57Z	"This is easy on Linux and a bit more difficult on Windows, but I wrote a (untested) way of how this is can be possible on Windows 2000/XP hosts.

Look at this thread with question:
http://forums.virtualbox.org/viewtopic.php?t=1887

And my answer:

The way I see VirtualBox auto-start on boot working:

1. After you start Windows, your normal user starts...

2. (XP host) Start->Accessories->System tools->Scheduled tasks

3. You make a new user: ""VBoxUser"" with admin privileges.

4. You write a script (*.bat) that starts VirtualBox and your VMs.

5. ""Scheduled tasks"" should auto-start VBox with different user ""VBoxUser"", with 
admin privileges.

--NOTE: This is possible, if you supply ""VBoxUser""'s password to Scheduled Tasks.

I think we need to add that to VBox documentation (if it lacks)

-Technologov"	Technologov
20901	not letting me create a user name	other	VirtualBox 6.1.32	defect	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
21434	A critical error has occurred while running the virtual machine	Mac OS X	VirtualBox-7.0.6	defect	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
21424	can't create new vdisks; verr_write_protect returned	Mac OS X	VirtualBox-7.0.6	defect	2023-01-22T07:22:10Z	2023-01-22T07:22:10Z	2023-01-22T07:22:10Z	"Hi!
I'm using Mac OS X Ventura 13.0.1 M1 
VirtualBox Version 7.0.6_BETA4 r155176 (Qt6.3.0) and tried to create a new vdisk but returned ""verr_write_protect""
"	Red Cactus
21397	NS_ERROR_FAILURE (0X80004005) / signal 9 in VirtualBox 7.0.4 on macOS Ventura 13.1 host	Mac OS X	VirtualBox-7.0.4	defect	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
20758	Crash due to uncaught exception 'NSInvalidArgumentException'	Mac OS X	VirtualBox 6.1.30	defect	2022-01-03T23:19:27Z	2022-12-12T15:41:13Z	2022-12-12T15:41:13Z	"I get from time to time the following crash (here the crash handler of MacOS is involved).

Looks like a clipboard problem according to the call stack but I am not sure.
{{{
-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Process:               VirtualBoxVM [1079]
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 [1076]
Responsible:           VirtualBox [1071]
User ID:               501

Date/Time:             2021-12-27 21:17:06.9821 +0100
OS Version:            macOS 12.1 (21C52)
Report Version:        12
Bridge OS Version:     6.1 (19P647)
Anonymous UUID:        D0955692-800B-A779-8417-3D8A9A1CE55E

Sleep/Wake UUID:       7A903436-75D5-4BA1-9615-DE85095D92ED

Time Awake Since Boot: 97000 seconds
Time Since Wake:       15414 seconds

System Integrity Protection: enabled

Crashed Thread:        11  SHCLIP

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Application Specific Information:
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[__NSCFArray objectAtIndex:]: index (2) beyond bounds (0)'
terminating with uncaught exception of type NSException
abort() called


Application Specific Backtrace 0:
0   CoreFoundation                      0x00007ff818d0af0b __exceptionPreprocess + 242
1   libobjc.A.dylib                     0x00007ff818a6bb9d objc_exception_throw + 48
2   CoreFoundation                      0x00007ff818dc6434 _CFThrowFormattedException + 202
3   CoreFoundation                      0x00007ff818dc7763 _NSArrayRaiseInsertNilException + 0
4   CoreFoundation                      0x00007ff818c4efdc -[__NSCFArray objectAtIndex:] + 154
5   HIServices                          0x00007ff81e6d1672 _ZL11IndexToItemP19OpaquePasteboardRefl + 195
6   HIServices                          0x00007ff81e6d158f PasteboardGetItemIdentifier + 170
7   VBoxSharedClipboard.dylib           0x0000000127eab05a VBoxHGCMSvcLoad + 18602
8   VBoxSharedClipboard.dylib           0x0000000127eaac1e VBoxHGCMSvcLoad + 17518
9   VBoxRT.dylib                        0x0000000108d6c5ac RTThreadSelfAutoAdopt + 1788
10  VBoxRT.dylib                        0x0000000108e27ecc RTThreadGetExecutionTimeMilli + 396
11  libsystem_pthread.d


Thread 0::  Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        	    0x7ff818b8baba mach_msg_trap + 10
1   libsystem_kernel.dylib        	    0x7ff818b8be2b mach_msg + 59
2   CoreFoundation                	    0x7ff818c8faf2 __CFRunLoopServiceMachPort + 319
3   CoreFoundation                	    0x7ff818c8e1cb __CFRunLoopRun + 1325
4   CoreFoundation                	    0x7ff818c8d5dd CFRunLoopRunSpecific + 563
5   HIToolbox                     	    0x7ff8218c04f1 RunCurrentEventLoopInMode + 292
6   HIToolbox                     	    0x7ff8218c0247 ReceiveNextEventCommon + 587
7   HIToolbox                     	    0x7ff8218bffe5 _BlockUntilNextEventMatchingListInModeWithFilter + 70
8   AppKit                        	    0x7ff81b6bcb4c _DPSNextEvent + 886
9   AppKit                        	    0x7ff81b6bb1b8 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1411
10  AppKit                        	    0x7ff81b6ad5a9 -[NSApplication run] + 586
11  libqcocoa.dylib               	       0x1094e8eed QCocoaEventDispatcher::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 2205
12  QtCoreVBox                    	       0x109ad7791 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 401
13  QtCoreVBox                    	       0x109adbb4a QCoreApplication::exec() + 346
14  VirtualBoxVM.dylib            	       0x10879042e TrustedMain + 1502
15  VirtualBoxVM                  	       0x1084aef01 0x1084ab000 + 16129
16  dyld                          	       0x10ddba4fe start + 462

Thread 1:: nspr-1
0   libsystem_kernel.dylib        	    0x7ff818b93e4a __select + 10
1   VBoxXPCOM.dylib               	       0x108b4f8a0 0x108ac5000 + 567456
2   VBoxXPCOM.dylib               	       0x108b516e5 PR_Poll + 1061
3   VBoxXPCOMIPCC.dylib           	       0x10aa4de75 0x10aa3b000 + 77429
4   VBoxXPCOM.dylib               	       0x108b56a96 0x108ac5000 + 596630
5   VBoxRT.dylib                  	       0x108d6c5ac 0x108c7d000 + 980396
6   VBoxRT.dylib                  	       0x108e27ecc 0x108c7d000 + 1748684
7   libsystem_pthread.dylib       	    0x7ff818bc84f4 _pthread_start + 125
8   libsystem_pthread.dylib       	    0x7ff818bc400f thread_start + 15

Thread 2:: nspr-2
0   libsystem_kernel.dylib        	    0x7ff818b8e506 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	    0x7ff818bc8a69 _pthread_cond_wait + 1224
2   VBoxXPCOM.dylib               	       0x108b54dfe PR_WaitCondVar + 254
3   VBoxXPCOM.dylib               	       0x108b552ad PR_Wait + 61
4   VBoxXPCOMIPCC.dylib           	       0x10aa467b8 0x10aa3b000 + 47032
5   VBoxXPCOM.dylib               	       0x108b291f9 0x108ac5000 + 410105
6   VBoxXPCOM.dylib               	       0x108b56a96 0x108ac5000 + 596630
7   VBoxRT.dylib                  	       0x108d6c5ac 0x108c7d000 + 980396
8   VBoxRT.dylib                  	       0x108e27ecc 0x108c7d000 + 1748684
9   libsystem_pthread.dylib       	    0x7ff818bc84f4 _pthread_start + 125
10  libsystem_pthread.dylib       	    0x7ff818bc400f thread_start + 15

Thread 3:: VBoxSVCWatcher
0   libsystem_kernel.dylib        	    0x7ff818b8e506 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	    0x7ff818bc8a69 _pthread_cond_wait + 1224
2   VBoxRT.dylib                  	       0x108e23f3c RTSemEventWait + 364
3   VBoxC.dylib                   	       0x1129c0da1 0x1128c7000 + 1023393
4   VBoxRT.dylib                  	       0x108d6c5ac 0x108c7d000 + 980396
5   VBoxRT.dylib                  	       0x108e27ecc 0x108c7d000 + 1748684
6   libsystem_pthread.dylib       	    0x7ff818bc84f4 _pthread_start + 125
7   libsystem_pthread.dylib       	    0x7ff818bc400f thread_start + 15

Thread 4:: UIMainEventListeningThread
0   libsystem_kernel.dylib        	    0x7ff818b8e506 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	    0x7ff818bc8a69 _pthread_cond_wait + 1224
2   VBoxXPCOM.dylib               	       0x108b54de7 PR_WaitCondVar + 231
3   VBoxXPCOM.dylib               	       0x108b552ad PR_Wait + 61
4   VBoxXPCOMIPCC.dylib           	       0x10aa4071b 0x10aa3b000 + 22299
5   VBoxXPCOMIPCC.dylib           	       0x10aa403ed 0x10aa3b000 + 21485
6   VBoxXPCOMIPCC.dylib           	       0x10aa45039 0x10aa3b000 + 41017
7   VBoxXPCOM.dylib               	       0x108b382ed 0x108ac5000 + 471789
8   VBoxXPCOM.dylib               	       0x108b374eb 0x108ac5000 + 468203
9   UICommon.dylib                	       0x10e140642 CEventSource::GetEvent(CEventListener const&, int) + 162
10  UICommon.dylib                	       0x10df53a37 0x10de6d000 + 944695
11  QtCoreVBox                    	       0x10991d96b 0x1098f4000 + 170347
12  libsystem_pthread.dylib       	    0x7ff818bc84f4 _pthread_start + 125
13  libsystem_pthread.dylib       	    0x7ff818bc400f thread_start + 15

Thread 5:: UIMainEventListeningThread
0   libsystem_kernel.dylib        	    0x7ff818b8e506 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	    0x7ff818bc8a69 _pthread_cond_wait + 1224
2   VBoxRT.dylib                  	       0x108e23f3c RTSemEventWait + 364
3   VBoxC.dylib                   	       0x11290c0d0 0x1128c7000 + 282832
4   VBoxC.dylib                   	       0x11290d2fd 0x1128c7000 + 287485
5   VBoxC.dylib                   	       0x112aa202a 0x1128c7000 + 1945642
6   UICommon.dylib                	       0x10e140642 CEventSource::GetEvent(CEventListener const&, int) + 162
7   UICommon.dylib                	       0x10df53a37 0x10de6d000 + 944695
8   QtCoreVBox                    	       0x10991d96b 0x1098f4000 + 170347
9   libsystem_pthread.dylib       	    0x7ff818bc84f4 _pthread_start + 125
10  libsystem_pthread.dylib       	    0x7ff818bc400f thread_start + 15

Thread 6:: UIMainEventListeningThread
0   libsystem_kernel.dylib        	    0x7ff818b8e506 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	    0x7ff818bc8a69 _pthread_cond_wait + 1224
2   VBoxRT.dylib                  	       0x108e23f3c RTSemEventWait + 364
3   VBoxC.dylib                   	       0x11290c0d0 0x1128c7000 + 282832
4   VBoxC.dylib                   	       0x11290d2fd 0x1128c7000 + 287485
5   VBoxC.dylib                   	       0x112aa202a 0x1128c7000 + 1945642
6   UICommon.dylib                	       0x10e140642 CEventSource::GetEvent(CEventListener const&, int) + 162
7   UICommon.dylib                	       0x10df53a37 0x10de6d000 + 944695
8   QtCoreVBox                    	       0x10991d96b 0x1098f4000 + 170347
9   libsystem_pthread.dylib       	    0x7ff818bc84f4 _pthread_start + 125
10  libsystem_pthread.dylib       	    0x7ff818bc400f thread_start + 15

Thread 7:: MainHGCMthread
0   libsystem_kernel.dylib        	    0x7ff818b8e506 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	    0x7ff818bc8a69 _pthread_cond_wait + 1224
2   VBoxRT.dylib                  	       0x108e23feb RTSemEventWait + 539
3   VBoxC.dylib                   	       0x112a67e65 0x1128c7000 + 1707621
4   VBoxC.dylib                   	       0x112a68556 0x1128c7000 + 1709398
5   VBoxC.dylib                   	       0x112a6cb0b 0x1128c7000 + 1727243
6   VBoxC.dylib                   	       0x112a67c3f 0x1128c7000 + 1707071
7   VBoxRT.dylib                  	       0x108d6c5ac 0x108c7d000 + 980396
8   VBoxRT.dylib                  	       0x108e27ecc 0x108c7d000 + 1748684
9   libsystem_pthread.dylib       	    0x7ff818bc84f4 _pthread_start + 125
10  libsystem_pthread.dylib       	    0x7ff818bc400f thread_start + 15

Thread 8:: EMT
0   libsystem_kernel.dylib        	    0x7ff818b8efda __ioctl + 10
1   libsystem_kernel.dylib        	    0x7ff818b8efc7 ioctl + 150
2   VBoxRT.dylib                  	       0x108e324ad 0x108c7d000 + 1791149
3   VBoxRT.dylib                  	       0x108e2a6e6 SUPR3CallVMMR0Ex + 438
4   VBoxVMM.dylib                 	       0x10a569a32 0x10a4bb000 + 715314
5   VBoxVMM.dylib                 	       0x10a5689f1 0x10a4bb000 + 711153
6   VBoxVMM.dylib                 	       0x10a502dbb 0x10a4bb000 + 294331
7   VBoxVMM.dylib                 	       0x10a5681de 0x10a4bb000 + 709086
8   VBoxRT.dylib                  	       0x108d6c5ac 0x108c7d000 + 980396
9   VBoxRT.dylib                  	       0x108e27ecc 0x108c7d000 + 1748684
10  libsystem_pthread.dylib       	    0x7ff818bc84f4 _pthread_start + 125
11  libsystem_pthread.dylib       	    0x7ff818bc400f thread_start + 15

Thread 9:: nspr-3
0   libsystem_kernel.dylib        	    0x7ff818b8e506 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	    0x7ff818bc8a69 _pthread_cond_wait + 1224
2   VBoxXPCOM.dylib               	       0x108b54dfe PR_WaitCondVar + 254
3   VBoxXPCOM.dylib               	       0x108b552ad PR_Wait + 61
4   VBoxXPCOMIPCC.dylib           	       0x10aa467b8 0x10aa3b000 + 47032
5   VBoxXPCOM.dylib               	       0x108b291f9 0x108ac5000 + 410105
6   VBoxXPCOM.dylib               	       0x108b56a96 0x108ac5000 + 596630
7   VBoxRT.dylib                  	       0x108d6c5ac 0x108c7d000 + 980396
8   VBoxRT.dylib                  	       0x108e27ecc 0x108c7d000 + 1748684
9   libsystem_pthread.dylib       	    0x7ff818bc84f4 _pthread_start + 125
10  libsystem_pthread.dylib       	    0x7ff818bc400f thread_start + 15

Thread 10:: ShClipboard
0   libsystem_kernel.dylib        	    0x7ff818b8e506 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	    0x7ff818bc8a69 _pthread_cond_wait + 1224
2   VBoxRT.dylib                  	       0x108e23feb RTSemEventWait + 539
3   VBoxC.dylib                   	       0x112a67e65 0x1128c7000 + 1707621
4   VBoxC.dylib                   	       0x112a68556 0x1128c7000 + 1709398
5   VBoxC.dylib                   	       0x112a6917d 0x1128c7000 + 1712509
6   VBoxC.dylib                   	       0x112a67c3f 0x1128c7000 + 1707071
7   VBoxRT.dylib                  	       0x108d6c5ac 0x108c7d000 + 980396
8   VBoxRT.dylib                  	       0x108e27ecc 0x108c7d000 + 1748684
9   libsystem_pthread.dylib       	    0x7ff818bc84f4 _pthread_start + 125
10  libsystem_pthread.dylib       	    0x7ff818bc400f thread_start + 15

Thread 11 Crashed:: SHCLIP
0   libsystem_kernel.dylib        	    0x7ff818b92112 __pthread_kill + 10
1   libsystem_pthread.dylib       	    0x7ff818bc8214 pthread_kill + 263
2   libsystem_c.dylib             	    0x7ff818b14d10 abort + 123
3   libc++abi.dylib               	    0x7ff818b850b2 abort_message + 241
4   libc++abi.dylib               	    0x7ff818b761fd demangling_terminate_handler() + 266
5   libobjc.A.dylib               	    0x7ff818a73509 _objc_terminate() + 96
6   libc++abi.dylib               	    0x7ff818b844d7 std::__terminate(void (*)()) + 8
7   libc++abi.dylib               	    0x7ff818b86d55 __cxxabiv1::failed_throw(__cxxabiv1::__cxa_exception*) + 27
8   libc++abi.dylib               	    0x7ff818b86d1c __cxa_throw + 116
9   libobjc.A.dylib               	    0x7ff818a6bc9b objc_exception_throw + 302
10  CoreFoundation                	    0x7ff818dc6434 _CFThrowFormattedException + 202
11  CoreFoundation                	    0x7ff818dc7763 _NSArrayRaiseBoundException + 82
12  CoreFoundation                	    0x7ff818c4efdc -[__NSCFArray objectAtIndex:] + 154
13  HIServices                    	    0x7ff81e6d1672 IndexToItem(OpaquePasteboardRef*, long) + 195
14  HIServices                    	    0x7ff81e6d158f PasteboardGetItemIdentifier + 170
15  VBoxSharedClipboard.dylib     	       0x127eab05a 0x127ea2000 + 36954
16  VBoxSharedClipboard.dylib     	       0x127eaac1e 0x127ea2000 + 35870
17  VBoxRT.dylib                  	       0x108d6c5ac 0x108c7d000 + 980396
18  VBoxRT.dylib                  	       0x108e27ecc 0x108c7d000 + 1748684
19  libsystem_pthread.dylib       	    0x7ff818bc84f4 _pthread_start + 125
20  libsystem_pthread.dylib       	    0x7ff818bc400f thread_start + 15

Thread 12:: DragAndDropSvc
0   libsystem_kernel.dylib        	    0x7ff818b8e506 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	    0x7ff818bc8a69 _pthread_cond_wait + 1224
2   VBoxRT.dylib                  	       0x108e23feb RTSemEventWait + 539
3   VBoxC.dylib                   	       0x112a67e65 0x1128c7000 + 1707621
4   VBoxC.dylib                   	       0x112a68556 0x1128c7000 + 1709398
5   VBoxC.dylib                   	       0x112a6917d 0x1128c7000 + 1712509
6   VBoxC.dylib                   	       0x112a67c3f 0x1128c7000 + 1707071
7   VBoxRT.dylib                  	       0x108d6c5ac 0x108c7d000 + 980396
8   VBoxRT.dylib                  	       0x108e27ecc 0x108c7d000 + 1748684
9   libsystem_pthread.dylib       	    0x7ff818bc84f4 _pthread_start + 125
10  libsystem_pthread.dylib       	    0x7ff818bc400f thread_start + 15

Thread 13:: Timer
0   libsystem_kernel.dylib        	    0x7ff818b8e506 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	    0x7ff818bc8a69 _pthread_cond_wait + 1224
2   VBoxRT.dylib                  	       0x108e23f3c RTSemEventWait + 364
3   VBoxRT.dylib                  	       0x108e14d0d 0x108c7d000 + 1670413
4   VBoxRT.dylib                  	       0x108d6c5ac 0x108c7d000 + 980396
5   VBoxRT.dylib                  	       0x108e27ecc 0x108c7d000 + 1748684
6   libsystem_pthread.dylib       	    0x7ff818bc84f4 _pthread_start + 125
7   libsystem_pthread.dylib       	    0x7ff818bc400f thread_start + 15

Thread 14:: PDMNsTx
0   libsystem_kernel.dylib        	    0x7ff818b8e3da __semwait_signal + 10
1   libsystem_c.dylib             	    0x7ff818aa38a9 nanosleep + 196
2   VBoxRT.dylib                  	       0x108e27f53 RTThreadSleep + 67
3   VBoxVMM.dylib                 	       0x10a657e9a 0x10a4bb000 + 1691290
4   VBoxVMM.dylib                 	       0x10a5293af 0x10a4bb000 + 451503
5   VBoxRT.dylib                  	       0x108d6c5ac 0x108c7d000 + 980396
6   VBoxRT.dylib                  	       0x108e27ecc 0x108c7d000 + 1748684
7   libsystem_pthread.dylib       	    0x7ff818bc84f4 _pthread_start + 125
8   libsystem_pthread.dylib       	    0x7ff818bc400f thread_start + 15

Thread 15:: ShFolders
0   libsystem_kernel.dylib        	    0x7ff818b8e506 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	    0x7ff818bc8a69 _pthread_cond_wait + 1224
2   VBoxRT.dylib                  	       0x108e23feb RTSemEventWait + 539
3   VBoxC.dylib                   	       0x112a67e65 0x1128c7000 + 1707621
4   VBoxC.dylib                   	       0x112a68556 0x1128c7000 + 1709398
5   VBoxC.dylib                   	       0x112a6917d 0x1128c7000 + 1712509
6   VBoxC.dylib                   	       0x112a67c3f 0x1128c7000 + 1707071
7   VBoxRT.dylib                  	       0x108d6c5ac 0x108c7d000 + 980396
8   VBoxRT.dylib                  	       0x108e27ecc 0x108c7d000 + 1748684
9   libsystem_pthread.dylib       	    0x7ff818bc84f4 _pthread_start + 125
10  libsystem_pthread.dylib       	    0x7ff818bc400f thread_start + 15

Thread 16:: com.apple.NSEventThread
0   libsystem_kernel.dylib        	    0x7ff818b8baba mach_msg_trap + 10
1   libsystem_kernel.dylib        	    0x7ff818b8be2b mach_msg + 59
2   CoreFoundation                	    0x7ff818c8faf2 __CFRunLoopServiceMachPort + 319
3   CoreFoundation                	    0x7ff818c8e1cb __CFRunLoopRun + 1325
4   CoreFoundation                	    0x7ff818c8d5dd CFRunLoopRunSpecific + 563
5   AppKit                        	    0x7ff81b82ad98 _NSEventThread + 132
6   libsystem_pthread.dylib       	    0x7ff818bc84f4 _pthread_start + 125
7   libsystem_pthread.dylib       	    0x7ff818bc400f thread_start + 15

Thread 17:: GuestControlSvc
0   libsystem_kernel.dylib        	    0x7ff818b8e506 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	    0x7ff818bc8a69 _pthread_cond_wait + 1224
2   VBoxRT.dylib                  	       0x108e23feb RTSemEventWait + 539
3   VBoxC.dylib                   	       0x112a67e65 0x1128c7000 + 1707621
4   VBoxC.dylib                   	       0x112a68556 0x1128c7000 + 1709398
5   VBoxC.dylib                   	       0x112a6917d 0x1128c7000 + 1712509
6   VBoxC.dylib                   	       0x112a67c3f 0x1128c7000 + 1707071
7   VBoxRT.dylib                  	       0x108d6c5ac 0x108c7d000 + 980396
8   VBoxRT.dylib                  	       0x108e27ecc 0x108c7d000 + 1748684
9   libsystem_pthread.dylib       	    0x7ff818bc84f4 _pthread_start + 125
10  libsystem_pthread.dylib       	    0x7ff818bc400f thread_start + 15

Thread 18:: GuestPropSvc
0   libsystem_kernel.dylib        	    0x7ff818b8e506 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	    0x7ff818bc8a69 _pthread_cond_wait + 1224
2   VBoxRT.dylib                  	       0x108e23feb RTSemEventWait + 539
3   VBoxC.dylib                   	       0x112a67e65 0x1128c7000 + 1707621
4   VBoxC.dylib                   	       0x112a68556 0x1128c7000 + 1709398
5   VBoxC.dylib                   	       0x112a6917d 0x1128c7000 + 1712509
6   VBoxC.dylib                   	       0x112a67c3f 0x1128c7000 + 1707071
7   VBoxRT.dylib                  	       0x108d6c5ac 0x108c7d000 + 980396
8   VBoxRT.dylib                  	       0x108e27ecc 0x108c7d000 + 1748684
9   libsystem_pthread.dylib       	    0x7ff818bc84f4 _pthread_start + 125
10  libsystem_pthread.dylib       	    0x7ff818bc400f thread_start + 15

Thread 19:: GstPropNtfy
0   libsystem_kernel.dylib        	    0x7ff818b8e506 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	    0x7ff818bc8a69 _pthread_cond_wait + 1224
2   VBoxRT.dylib                  	       0x108e23feb RTSemEventWait + 539
3   VBoxRT.dylib                  	       0x108d6a1c2 RTReqQueueProcess + 146
4   VBoxGuestPropSvc.dylib        	       0x1208c6031 0x1208c0000 + 24625
5   VBoxRT.dylib                  	       0x108d6c5ac 0x108c7d000 + 980396
6   VBoxRT.dylib                  	       0x108e27ecc 0x108c7d000 + 1748684
7   libsystem_pthread.dylib       	    0x7ff818bc84f4 _pthread_start + 125
8   libsystem_pthread.dylib       	    0x7ff818bc400f thread_start + 15

Thread 20:: VMSVGA FIFO
0   libsystem_kernel.dylib        	    0x7ff818b8efda __ioctl + 10
1   libsystem_kernel.dylib        	    0x7ff818b8efc7 ioctl + 150
2   VBoxRT.dylib                  	       0x108e324ad 0x108c7d000 + 1791149
3   VBoxRT.dylib                  	       0x108e2f2b7 SUPSemEventWaitNoResume + 135
4   VBoxDD.dylib                  	       0x12107af2f 0x120fe5000 + 614191
5   VBoxVMM.dylib                 	       0x10a5293a3 0x10a4bb000 + 451491
6   VBoxRT.dylib                  	       0x108d6c5ac 0x108c7d000 + 980396
7   VBoxRT.dylib                  	       0x108e27ecc 0x108c7d000 + 1748684
8   libsystem_pthread.dylib       	    0x7ff818bc84f4 _pthread_start + 125
9   libsystem_pthread.dylib       	    0x7ff818bc400f thread_start + 15

Thread 21:: Port0
0   libsystem_kernel.dylib        	    0x7ff818b8efda __ioctl + 10
1   libsystem_kernel.dylib        	    0x7ff818b8efc7 ioctl + 150
2   VBoxRT.dylib                  	       0x108e324ad 0x108c7d000 + 1791149
3   VBoxRT.dylib                  	       0x108e2f2b7 SUPSemEventWaitNoResume + 135
4   VBoxDD.dylib                  	       0x1210d8259 0x120fe5000 + 995929
5   VBoxVMM.dylib                 	       0x10a5293a3 0x10a4bb000 + 451491
6   VBoxRT.dylib                  	       0x108d6c5ac 0x108c7d000 + 980396
7   VBoxRT.dylib                  	       0x108e27ecc 0x108c7d000 + 1748684
8   libsystem_pthread.dylib       	    0x7ff818bc84f4 _pthread_start + 125
9   libsystem_pthread.dylib       	    0x7ff818bc400f thread_start + 15

Thread 22:: AioMgr0-N
0   libsystem_kernel.dylib        	    0x7ff818b8e506 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	    0x7ff818bc8a69 _pthread_cond_wait + 1224
2   VBoxRT.dylib                  	       0x108e23feb RTSemEventWait + 539
3   VBoxVMM.dylib                 	       0x10a655c5b 0x10a4bb000 + 1682523
4   VBoxRT.dylib                  	       0x108d6c5ac 0x108c7d000 + 980396
5   VBoxRT.dylib                  	       0x108e27ecc 0x108c7d000 + 1748684
6   libsystem_pthread.dylib       	    0x7ff818bc84f4 _pthread_start + 125
7   libsystem_pthread.dylib       	    0x7ff818bc400f thread_start + 15

Thread 23:: Port1
0   libsystem_kernel.dylib        	    0x7ff818b8efda __ioctl + 10
1   libsystem_kernel.dylib        	    0x7ff818b8efc7 ioctl + 150
2   VBoxRT.dylib                  	       0x108e324ad 0x108c7d000 + 1791149
3   VBoxRT.dylib                  	       0x108e2f2b7 SUPSemEventWaitNoResume + 135
4   VBoxDD.dylib                  	       0x1210d8259 0x120fe5000 + 995929
5   VBoxVMM.dylib                 	       0x10a5293a3 0x10a4bb000 + 451491
6   VBoxRT.dylib                  	       0x108d6c5ac 0x108c7d000 + 980396
7   VBoxRT.dylib                  	       0x108e27ecc 0x108c7d000 + 1748684
8   libsystem_pthread.dylib       	    0x7ff818bc84f4 _pthread_start + 125
9   libsystem_pthread.dylib       	    0x7ff818bc400f thread_start + 15

Thread 24:: ATA-0
0   libsystem_kernel.dylib        	    0x7ff818b8efda __ioctl + 10
1   libsystem_kernel.dylib        	    0x7ff818b8efc7 ioctl + 150
2   VBoxRT.dylib                  	       0x108e324ad 0x108c7d000 + 1791149
3   VBoxRT.dylib                  	       0x108e2f2b7 SUPSemEventWaitNoResume + 135
4   VBoxDD.dylib                  	       0x1210134a9 0x120fe5000 + 189609
5   VBoxRT.dylib                  	       0x108d6c5ac 0x108c7d000 + 980396
6   VBoxRT.dylib                  	       0x108e27ecc 0x108c7d000 + 1748684
7   libsystem_pthread.dylib       	    0x7ff818bc84f4 _pthread_start + 125
8   libsystem_pthread.dylib       	    0x7ff818bc400f thread_start + 15

Thread 25:: ATA-1
0   libsystem_kernel.dylib        	    0x7ff818b8efda __ioctl + 10
1   libsystem_kernel.dylib        	    0x7ff818b8efc7 ioctl + 150
2   VBoxRT.dylib                  	       0x108e324ad 0x108c7d000 + 1791149
3   VBoxRT.dylib                  	       0x108e2f2b7 SUPSemEventWaitNoResume + 135
4   VBoxDD.dylib                  	       0x1210134a9 0x120fe5000 + 189609
5   VBoxRT.dylib                  	       0x108d6c5ac 0x108c7d000 + 980396
6   VBoxRT.dylib                  	       0x108e27ecc 0x108c7d000 + 1748684
7   libsystem_pthread.dylib       	    0x7ff818bc84f4 _pthread_start + 125
8   libsystem_pthread.dylib       	    0x7ff818bc400f thread_start + 15

Thread 26:: TaskSet0
0   libsystem_kernel.dylib        	    0x7ff818b8efda __ioctl + 10
1   libsystem_kernel.dylib        	    0x7ff818b8efc7 ioctl + 150
2   VBoxRT.dylib                  	       0x108e324ad 0x108c7d000 + 1791149
3   VBoxRT.dylib                  	       0x108e2f2b7 SUPSemEventWaitNoResume + 135
4   VBoxVMM.dylib                 	       0x10a527f77 0x10a4bb000 + 446327
5   VBoxRT.dylib                  	       0x108d6c5ac 0x108c7d000 + 980396
6   VBoxRT.dylib                  	       0x108e27ecc 0x108c7d000 + 1748684
7   libsystem_pthread.dylib       	    0x7ff818bc84f4 _pthread_start + 125
8   libsystem_pthread.dylib       	    0x7ff818bc400f thread_start + 15

Thread 27:: INTNET-RECV
0   libsystem_kernel.dylib        	    0x7ff818b8efda __ioctl + 10
1   libsystem_kernel.dylib        	    0x7ff818b8efc7 ioctl + 150
2   VBoxRT.dylib                  	       0x108e324ad 0x108c7d000 + 1791149
3   VBoxRT.dylib                  	       0x108e2a668 SUPR3CallVMMR0Ex + 312
4   VBoxDD.dylib                  	       0x121057858 0x120fe5000 + 469080
5   VBoxRT.dylib                  	       0x108d6c5ac 0x108c7d000 + 980396
6   VBoxRT.dylib                  	       0x108e27ecc 0x108c7d000 + 1748684
7   libsystem_pthread.dylib       	    0x7ff818bc84f4 _pthread_start + 125
8   libsystem_pthread.dylib       	    0x7ff818bc400f thread_start + 15

Thread 28:: INTNET-XMIT
0   libsystem_kernel.dylib        	    0x7ff818b8efda __ioctl + 10
1   libsystem_kernel.dylib        	    0x7ff818b8efc7 ioctl + 150
2   VBoxRT.dylib                  	       0x108e324ad 0x108c7d000 + 1791149
3   VBoxRT.dylib                  	       0x108e2f2b7 SUPSemEventWaitNoResume + 135
4   VBoxDD.dylib                  	       0x1210586b0 0x120fe5000 + 472752
5   VBoxVMM.dylib                 	       0x10a5293a3 0x10a4bb000 + 451491
6   VBoxRT.dylib                  	       0x108d6c5ac 0x108c7d000 + 980396
7   VBoxRT.dylib                  	       0x108e27ecc 0x108c7d000 + 1748684
8   libsystem_pthread.dylib       	    0x7ff818bc84f4 _pthread_start + 125
9   libsystem_pthread.dylib       	    0x7ff818bc400f thread_start + 15

Thread 29:: NATRX
0   libsystem_kernel.dylib        	    0x7ff818b8e506 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	    0x7ff818bc8a69 _pthread_cond_wait + 1224
2   VBoxRT.dylib                  	       0x108e23feb RTSemEventWait + 539
3   VBoxDD.dylib                  	       0x121131ada 0x120fe5000 + 1362650
4   VBoxVMM.dylib                 	       0x10a5293a3 0x10a4bb000 + 451491
5   VBoxRT.dylib                  	       0x108d6c5ac 0x108c7d000 + 980396
6   VBoxRT.dylib                  	       0x108e27ecc 0x108c7d000 + 1748684
7   libsystem_pthread.dylib       	    0x7ff818bc84f4 _pthread_start + 125
8   libsystem_pthread.dylib       	    0x7ff818bc400f thread_start + 15

Thread 30:: NATURGRX
0   libsystem_kernel.dylib        	    0x7ff818b8e506 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	    0x7ff818bc8a69 _pthread_cond_wait + 1224
2   VBoxRT.dylib                  	       0x108e23feb RTSemEventWait + 539
3   VBoxDD.dylib                  	       0x121131b3a 0x120fe5000 + 1362746
4   VBoxVMM.dylib                 	       0x10a5293a3 0x10a4bb000 + 451491
5   VBoxRT.dylib                  	       0x108d6c5ac 0x108c7d000 + 980396
6   VBoxRT.dylib                  	       0x108e27ecc 0x108c7d000 + 1748684
7   libsystem_pthread.dylib       	    0x7ff818bc84f4 _pthread_start + 125
8   libsystem_pthread.dylib       	    0x7ff818bc400f thread_start + 15

Thread 31:: HOSTRES
0   libsystem_kernel.dylib        	    0x7ff818b8e506 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	    0x7ff818bc8a69 _pthread_cond_wait + 1224
2   VBoxRT.dylib                  	       0x108e23feb RTSemEventWait + 539
3   VBoxRT.dylib                  	       0x108d6a1c2 RTReqQueueProcess + 146
4   VBoxDD.dylib                  	       0x121131ba1 0x120fe5000 + 1362849
5   VBoxVMM.dylib                 	       0x10a5293a3 0x10a4bb000 + 451491
6   VBoxRT.dylib                  	       0x108d6c5ac 0x108c7d000 + 980396
7   VBoxRT.dylib                  	       0x108e27ecc 0x108c7d000 + 1748684
8   libsystem_pthread.dylib       	    0x7ff818bc84f4 _pthread_start + 125
9   libsystem_pthread.dylib       	    0x7ff818bc400f thread_start + 15

Thread 32:: NAT
0   libsystem_kernel.dylib        	    0x7ff818b921ae poll + 10
1   VBoxDD.dylib                  	       0x121131cdb 0x120fe5000 + 1363163
2   VBoxVMM.dylib                 	       0x10a5293a3 0x10a4bb000 + 451491
3   VBoxRT.dylib                  	       0x108d6c5ac 0x108c7d000 + 980396
4   VBoxRT.dylib                  	       0x108e27ecc 0x108c7d000 + 1748684
5   libsystem_pthread.dylib       	    0x7ff818bc84f4 _pthread_start + 125
6   libsystem_pthread.dylib       	    0x7ff818bc400f thread_start + 15

Thread 33:: CaAud-0
0   libsystem_kernel.dylib        	    0x7ff818b8baba mach_msg_trap + 10
1   libsystem_kernel.dylib        	    0x7ff818b8be2b mach_msg + 59
2   CoreFoundation                	    0x7ff818c8faf2 __CFRunLoopServiceMachPort + 319
3   CoreFoundation                	    0x7ff818c8e1cb __CFRunLoopRun + 1325
4   CoreFoundation                	    0x7ff818c8d5dd CFRunLoopRunSpecific + 563
5   VBoxDD.dylib                  	       0x12112ef35 0x120fe5000 + 1351477
6   VBoxRT.dylib                  	       0x108d6c5ac 0x108c7d000 + 980396
7   VBoxRT.dylib                  	       0x108e27ecc 0x108c7d000 + 1748684
8   libsystem_pthread.dylib       	    0x7ff818bc84f4 _pthread_start + 125
9   libsystem_pthread.dylib       	    0x7ff818bc400f thread_start + 15

Thread 34:: AMCP Logging Spool
0   libsystem_kernel.dylib        	    0x7ff818b8baf6 semaphore_wait_trap + 10
1   caulk                         	    0x7ff82164c1c0 caulk::mach::semaphore::wait_or_error() + 16
2   caulk                         	    0x7ff82163308a caulk::concurrent::details::worker_thread::run() + 36
3   caulk                         	    0x7ff821632d4e 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       	    0x7ff818bc84f4 _pthread_start + 125
5   libsystem_pthread.dylib       	    0x7ff818bc400f thread_start + 15

Thread 35:: USBDevIo--1
0   libsystem_kernel.dylib        	    0x7ff818b8e506 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	    0x7ff818bc8a69 _pthread_cond_wait + 1224
2   VBoxRT.dylib                  	       0x108e23feb RTSemEventWait + 539
3   VBoxDD.dylib                  	       0x120ff1f3d 0x120fe5000 + 53053
4   VBoxDD.dylib                  	       0x1210ad38d 0x120fe5000 + 820109
5   VBoxDD.dylib                  	       0x1210a99e2 0x120fe5000 + 805346
6   VBoxRT.dylib                  	       0x108d6c5ac 0x108c7d000 + 980396
7   VBoxRT.dylib                  	       0x108e27ecc 0x108c7d000 + 1748684
8   libsystem_pthread.dylib       	    0x7ff818bc84f4 _pthread_start + 125
9   libsystem_pthread.dylib       	    0x7ff818bc400f thread_start + 15

Thread 36:: VUsbPeriodFrm
0   libsystem_kernel.dylib        	    0x7ff818b8e506 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	    0x7ff818bc8a69 _pthread_cond_wait + 1224
2   VBoxRT.dylib                  	       0x108e249c6 0x108c7d000 + 1735110
3   VBoxDD.dylib                  	       0x1210a7ba3 0x120fe5000 + 797603
4   VBoxVMM.dylib                 	       0x10a5293a3 0x10a4bb000 + 451491
5   VBoxRT.dylib                  	       0x108d6c5ac 0x108c7d000 + 980396
6   VBoxRT.dylib                  	       0x108e27ecc 0x108c7d000 + 1748684
7   libsystem_pthread.dylib       	    0x7ff818bc84f4 _pthread_start + 125
8   libsystem_pthread.dylib       	    0x7ff818bc400f thread_start + 15

Thread 37:: MixAIO-1
0   libsystem_kernel.dylib        	    0x7ff818b8e506 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	    0x7ff818bc8a69 _pthread_cond_wait + 1224
2   VBoxRT.dylib                  	       0x108e23feb RTSemEventWait + 539
3   VBoxDD.dylib                  	       0x12111e917 0x120fe5000 + 1284375
4   VBoxRT.dylib                  	       0x108d6c5ac 0x108c7d000 + 980396
5   VBoxRT.dylib                  	       0x108e27ecc 0x108c7d000 + 1748684
6   libsystem_pthread.dylib       	    0x7ff818bc84f4 _pthread_start + 125
7   libsystem_pthread.dylib       	    0x7ff818bc400f thread_start + 15

Thread 38:: MixAIO-2
0   libsystem_kernel.dylib        	    0x7ff818b8e506 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	    0x7ff818bc8a69 _pthread_cond_wait + 1224
2   VBoxRT.dylib                  	       0x108e23feb RTSemEventWait + 539
3   VBoxDD.dylib                  	       0x12111e917 0x120fe5000 + 1284375
4   VBoxRT.dylib                  	       0x108d6c5ac 0x108c7d000 + 980396
5   VBoxRT.dylib                  	       0x108e27ecc 0x108c7d000 + 1748684
6   libsystem_pthread.dylib       	    0x7ff818bc84f4 _pthread_start + 125
7   libsystem_pthread.dylib       	    0x7ff818bc400f thread_start + 15

Thread 39:
0   libsystem_kernel.dylib        	    0x7ff818b8baf6 semaphore_wait_trap + 10
1   caulk                         	    0x7ff82164c1c0 caulk::mach::semaphore::wait_or_error() + 16
2   caulk                         	    0x7ff82163308a caulk::concurrent::details::worker_thread::run() + 36
3   caulk                         	    0x7ff821632d4e 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       	    0x7ff818bc84f4 _pthread_start + 125
5   libsystem_pthread.dylib       	    0x7ff818bc400f thread_start + 15

Thread 40:: AQConverterThread
0   libsystem_kernel.dylib        	    0x7ff818b8e506 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	    0x7ff818bc8a69 _pthread_cond_wait + 1224
2   libAudioToolboxUtility.dylib  	    0x7ff8254eccd4 CADeprecated::CAGuard::Wait() + 54
3   AudioToolbox                  	    0x7ff82649f089 AQConverterManager::AQConverterThread::ConverterThreadEntry(void*) + 707
4   libAudioToolboxUtility.dylib  	    0x7ff8254cf067 CADeprecated::CAPThread::Entry(CADeprecated::CAPThread*) + 77
5   libsystem_pthread.dylib       	    0x7ff818bc84f4 _pthread_start + 125
6   libsystem_pthread.dylib       	    0x7ff818bc400f thread_start + 15

Thread 41:: com.apple.audio.IOThread.client
0   libsystem_kernel.dylib        	    0x7ff818b8baba mach_msg_trap + 10
1   libsystem_kernel.dylib        	    0x7ff818b8be2b mach_msg + 59
2   CoreAudio                     	    0x7ff81a80f95b HALB_MachPort::SendSimpleMessageWithSimpleReply(unsigned int, unsigned int, int, int&, bool, unsigned int) + 111
3   CoreAudio                     	    0x7ff81a69e0ff HALC_ProxyIOContext::IOWorkLoop() + 3937
4   CoreAudio                     	    0x7ff81a69cbc1 invocation function for block in HALC_ProxyIOContext::HALC_ProxyIOContext(unsigned int, unsigned int) + 63
5   CoreAudio                     	    0x7ff81a86576c HALB_IOThread::Entry(void*) + 72
6   libsystem_pthread.dylib       	    0x7ff818bc84f4 _pthread_start + 125
7   libsystem_pthread.dylib       	    0x7ff818bc400f thread_start + 15

Thread 42:
0   libsystem_pthread.dylib       	    0x7ff818bc3fec start_wqthread + 0

Thread 43:
0   libsystem_pthread.dylib       	    0x7ff818bc3fec start_wqthread + 0

Thread 44:
0   libsystem_pthread.dylib       	    0x7ff818bc3fec start_wqthread + 0


Thread 11 crashed with X86 Thread State (64-bit):
  rax: 0x0000000000000000  rbx: 0x0000700005f7b000  rcx: 0x0000700005f79648  rdx: 0x0000000000000000
  rdi: 0x0000000000013803  rsi: 0x0000000000000006  rbp: 0x0000700005f79670  rsp: 0x0000700005f79648
   r8: 0x0000700005f79510   r9: 0x00007ff818b87fa1  r10: 0x0000000000000000  r11: 0x0000000000000246
  r12: 0x0000000000013803  r13: 0x0000003000000008  r14: 0x0000000000000006  r15: 0x0000000000000016
  rip: 0x00007ff818b92112  rfl: 0x0000000000000246  cr2: 0x00007ff85a422f58
  
Logical CPU:     0
Error Code:      0x02000148 
Trap Number:     133


Binary Images:
    0x7ff818b8b000 -     0x7ff818bc1fff libsystem_kernel.dylib (*) <5aa1e5be-b5b8-3a02-9885-a8c99e0ca378> /usr/lib/system/libsystem_kernel.dylib
    0x7ff818c0f000 -     0x7ff819111fff com.apple.CoreFoundation (6.9) <eab0e216-2a9e-31ce-9164-fdf3ebcf7bd3> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
    0x7ff82188e000 -     0x7ff821b85fff com.apple.HIToolbox (2.1.1) <535dbc28-4d26-3609-86bb-5c40227b648c> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox
    0x7ff81b67e000 -     0x7ff81c50cfff com.apple.AppKit (6.9) <d23b9681-3764-3298-a716-fbb511dd5a7c> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
       0x1094c6000 -        0x109605fff libqcocoa.dylib (*) <fa226e50-20a3-3c6d-b04e-9262d65300bc> /Applications/VirtualBox.app/Contents/plugins/platforms/libqcocoa.dylib
       0x1098f4000 -        0x109e1bfff org.qt-project.QtCoreVBox (5.6) <3a7a08e0-9422-393e-bd97-fd15e751434c> /Applications/VirtualBox.app/Contents/Frameworks/QtCoreVBox.framework/Versions/5/QtCoreVBox
       0x108789000 -        0x1088acfff VirtualBoxVM.dylib (*) <3a6f5a29-74ff-313c-9220-82612f2b6fc7> /Applications/VirtualBox.app/Contents/MacOS/VirtualBoxVM.dylib
       0x1084ab000 -        0x1084b2fff org.virtualbox.app.VirtualBoxVM (6.1.30) <43e613e0-b296-3de8-92e1-fbee61a51a5e> /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM
       0x10ddb5000 -        0x10de20fff dyld (*) <cef5a27a-d50b-3020-af03-1734b19bc8c5> /usr/lib/dyld
       0x108ac5000 -        0x108b76fff VBoxXPCOM.dylib (*) <31c4ddec-f9f5-363e-ad9f-b8881543e336> /Applications/VirtualBox.app/Contents/MacOS/VBoxXPCOM.dylib
       0x10aa3b000 -        0x10aa52fff VBoxXPCOMIPCC.dylib (*) <4e46eacb-3d27-3668-8e43-a455d494d839> /Applications/VirtualBox.app/Contents/MacOS/components/VBoxXPCOMIPCC.dylib
       0x108c7d000 -        0x1091e7fff VBoxRT.dylib (*) <05fa665b-b1c8-3f62-861e-1b3579be4a9a> /Applications/VirtualBox.app/Contents/MacOS/VBoxRT.dylib
    0x7ff818bc2000 -     0x7ff818bcdfff libsystem_pthread.dylib (*) <6c7561b4-4b92-3f45-921e-abe669299844> /usr/lib/system/libsystem_pthread.dylib
       0x1128c7000 -        0x112cd5fff VBoxC.dylib (*) <7a8a2b64-5299-3eda-9b9b-85eac8f2d836> /Applications/VirtualBox.app/Contents/MacOS/components/VBoxC.dylib
       0x10de6d000 -        0x10ff1dfff UICommon.dylib (*) <275d65cb-226c-39b5-a840-5143c6007a6b> /Applications/VirtualBox.app/Contents/MacOS/UICommon.dylib
       0x10a4bb000 -        0x10a7c2fff VBoxVMM.dylib (*) <b600b9be-060e-373f-8e33-09248dd2c4b7> /Applications/VirtualBox.app/Contents/MacOS/VBoxVMM.dylib
    0x7ff818a93000 -     0x7ff818b1bfff libsystem_c.dylib (*) <e58814cc-dcb7-35a5-badc-e367ed3ac207> /usr/lib/system/libsystem_c.dylib
    0x7ff818b75000 -     0x7ff818b8afff libc++abi.dylib (*) <129b1912-eeaf-3eea-93be-79e201c13f7c> /usr/lib/libc++abi.dylib
    0x7ff818a56000 -     0x7ff818a8ffff libobjc.A.dylib (*) <2239a869-3275-3e4c-987b-b8afce4520e7> /usr/lib/libobjc.A.dylib
    0x7ff81e6bd000 -     0x7ff81e718fff com.apple.HIServices (1.22) <d8b67d06-a916-3e96-969f-6667a640b18a> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices
       0x127ea2000 -        0x127eacfff VBoxSharedClipboard.dylib (*) <4e735b5e-9e79-3671-810a-0ae59f8e4d13> /Applications/VirtualBox.app/Contents/MacOS/VBoxSharedClipboard.dylib
       0x1208c0000 -        0x1208c7fff VBoxGuestPropSvc.dylib (*) <9690915c-4290-3f30-b268-0cedb904c76d> /Applications/VirtualBox.app/Contents/MacOS/VBoxGuestPropSvc.dylib
       0x120fe5000 -        0x121360fff VBoxDD.dylib (*) <5cb81725-cb9b-3972-8892-0d4dfc80466a> /Applications/VirtualBox.app/Contents/MacOS/VBoxDD.dylib
    0x7ff821631000 -     0x7ff821653fff com.apple.audio.caulk (1.0) <e76d1ab3-89c2-3a93-990b-30827fcf89b0> /System/Library/PrivateFrameworks/caulk.framework/Versions/A/caulk
    0x7ff8254c3000 -     0x7ff8254f2fff libAudioToolboxUtility.dylib (*) <425edbb8-5503-3226-baf3-73006a252f9b> /usr/lib/libAudioToolboxUtility.dylib
    0x7ff826469000 -     0x7ff8265a3fff com.apple.audio.toolbox.AudioToolbox (1.14) <56b338e2-0fd3-3fd1-8899-9b2ba2862d60> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
    0x7ff81a4e7000 -     0x7ff81ac0efff com.apple.audio.CoreAudio (5.0) <33f55d9c-eaef-3fbd-add5-ed3e54925762> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio

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: 1
    thread_create: 0
    thread_set_state: 0

VM Region Summary:
ReadOnly portion of Libraries: Total=1.0G resident=0K(0%) swapped_out_or_unallocated=1.0G(100%)
Writable regions: Total=4.1G written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=4.1G(100%)

                                VIRTUAL   REGION 
REGION TYPE                        SIZE    COUNT (non-coalesced) 
===========                     =======  ======= 
Accelerate framework               640K        5 
Activity Tracing                   256K        1 
CG backing stores                 2688K        4 
CG image                           348K       31 
CG raster data                    1864K       34 
ColorSync                          232K       27 
CoreAnimation                    145.1M       26 
CoreGraphics                        12K        2 
CoreUI image data                 3536K       27 
Foundation                          40K        2 
Kernel Alloc Once                    8K        1 
MALLOC                             2.0G     3291 
MALLOC guard page                   48K       10 
MALLOC_MEDIUM (reserved)           1.5G       16         reserved VM address space (unallocated)
MALLOC_NANO (reserved)           384.0M        1         reserved VM address space (unallocated)
STACK GUARD                       56.2M       45 
Stack                             29.3M       45 
VM_ALLOCATE                       20.4M       52 
VM_ALLOCATE (reserved)              32K        1         reserved VM address space (unallocated)
__DATA                            37.8M      425 
__DATA_CONST                      21.2M      241 
__DATA_DIRTY                      1018K      145 
__FONT_DATA                          4K        1 
__LINKEDIT                       648.5M       35 
__OBJC_RO                         81.8M        1 
__OBJC_RW                         3136K        2 
__TEXT                           397.0M      433 
__UNICODE                          588K        1 
dyld private memory               1024K        1 
mapped file                      376.4M      281 
shared memory                      768K       16 
===========                     =======  ======= 
TOTAL                              5.7G     5203 
TOTAL, minus reserved VM space     3.8G     5203 



-----------
Full Report
-----------

{""app_name"":""VirtualBoxVM"",""timestamp"":""2021-12-27 21:18:29.00 +0100"",""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.1 (21C52)"",""incident_id"":""BA1CA984-513B-45A2-A402-E48BC5248827"",""name"":""VirtualBoxVM""}
{
  ""uptime"" : 97000,
  ""procLaunch"" : ""2021-12-17 19:32:29.5176 +0100"",
  ""procRole"" : ""Background"",
  ""version"" : 2,
  ""userID"" : 501,
  ""deployVersion"" : 210,
  ""modelCode"" : ""MacBookPro16,1"",
  ""procStartAbsTime"" : 351367777591,
  ""coalitionID"" : 1054,
  ""osVersion"" : {
    ""train"" : ""macOS 12.1"",
    ""build"" : ""21C52"",
    ""releaseType"" : ""User""
  },
  ""captureTime"" : ""2021-12-27 21:17:06.9821 +0100"",
  ""incident"" : ""BA1CA984-513B-45A2-A402-E48BC5248827"",
  ""bug_type"" : ""309"",
  ""pid"" : 1079,
  ""procExitAbsTime"" : 97525746109729,
  ""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"":""0B89E2E1-D9B1-5AFE-9E5A-63ED2813F35B"",""thirdParty"":true},
  ""parentProc"" : ""VBoxSVC"",
  ""parentPid"" : 1076,
  ""coalitionName"" : ""org.virtualbox.app.VirtualBox"",
  ""crashReporterKey"" : ""D0955692-800B-A779-8417-3D8A9A1CE55E"",
  ""responsiblePid"" : 1071,
  ""responsibleProc"" : ""VirtualBox"",
  ""wakeTime"" : 15414,
  ""bridgeVersion"" : {""build"":""19P647"",""train"":""6.1""},
  ""sleepWakeUUID"" : ""7A903436-75D5-4BA1-9615-DE85095D92ED"",
  ""sip"" : ""enabled"",
  ""isCorpse"" : 1,
  ""exception"" : {""codes"":""0x0000000000000000, 0x0000000000000000"",""rawCodes"":[0,0],""type"":""EXC_CRASH"",""signal"":""SIGABRT""},
  ""asi"" : {""CoreFoundation"":[""*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[__NSCFArray objectAtIndex:]: index (2) beyond bounds (0)'""],""libsystem_c.dylib"":[""abort() called""],""libc++abi.dylib"":[""terminating with uncaught exception of type NSException""]},
  ""asiBacktraces"" : [""0   CoreFoundation                      0x00007ff818d0af0b __exceptionPreprocess + 242\n1   libobjc.A.dylib                     0x00007ff818a6bb9d objc_exception_throw + 48\n2   CoreFoundation                      0x00007ff818dc6434 _CFThrowFormattedException + 202\n3   CoreFoundation                      0x00007ff818dc7763 _NSArrayRaiseInsertNilException + 0\n4   CoreFoundation                      0x00007ff818c4efdc -[__NSCFArray objectAtIndex:] + 154\n5   HIServices                          0x00007ff81e6d1672 _ZL11IndexToItemP19OpaquePasteboardRefl + 195\n6   HIServices                          0x00007ff81e6d158f PasteboardGetItemIdentifier + 170\n7   VBoxSharedClipboard.dylib           0x0000000127eab05a VBoxHGCMSvcLoad + 18602\n8   VBoxSharedClipboard.dylib           0x0000000127eaac1e VBoxHGCMSvcLoad + 17518\n9   VBoxRT.dylib                        0x0000000108d6c5ac RTThreadSelfAutoAdopt + 1788\n10  VBoxRT.dylib                        0x0000000108e27ecc RTThreadGetExecutionTimeMilli + 396\n11  libsystem_pthread.d""],
  ""extMods"" : {""caller"":{""thread_create"":0,""thread_set_state"":0,""task_for_pid"":0},""system"":{""thread_create"":0,""thread_set_state"":0,""task_for_pid"":1},""targeted"":{""thread_create"":0,""thread_set_state"":0,""task_for_pid"":0},""warnings"":0},
  ""lastExceptionBacktrace"" : [{""imageOffset"":1031931,""symbol"":""__exceptionPreprocess"",""symbolLocation"":226,""imageIndex"":1},{""imageOffset"":88989,""symbol"":""objc_exception_throw"",""symbolLocation"":48,""imageIndex"":18},{""imageOffset"":1799220,""symbol"":""_CFThrowFormattedException"",""symbolLocation"":202,""imageIndex"":1},{""imageOffset"":1804131,""symbol"":""_NSArrayRaiseInsertNilException"",""symbolLocation"":0,""imageIndex"":1},{""imageOffset"":262108,""symbol"":""-[__NSCFArray objectAtIndex:]"",""symbolLocation"":154,""imageIndex"":1},{""imageOffset"":83570,""symbol"":""IndexToItem(OpaquePasteboardRef*, long)"",""symbolLocation"":195,""imageIndex"":19},{""imageOffset"":83343,""symbol"":""PasteboardGetItemIdentifier"",""symbolLocation"":170,""imageIndex"":19},{""imageOffset"":36954,""imageIndex"":20},{""imageOffset"":35870,""imageIndex"":20},{""imageOffset"":980396,""imageIndex"":11},{""imageOffset"":1748684,""imageIndex"":11},{""imageOffset"":25844,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":12},{""imageOffset"":8207,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":12}],
  ""faultingThread"" : 11,
  ""threads"" : [{""id"":12581,""queue"":""com.apple.main-thread"",""frames"":[{""imageOffset"":2746,""symbol"":""mach_msg_trap"",""symbolLocation"":10,""imageIndex"":0},{""imageOffset"":3627,""symbol"":""mach_msg"",""symbolLocation"":59,""imageIndex"":0},{""imageOffset"":527090,""symbol"":""__CFRunLoopServiceMachPort"",""symbolLocation"":319,""imageIndex"":1},{""imageOffset"":520651,""symbol"":""__CFRunLoopRun"",""symbolLocation"":1325,""imageIndex"":1},{""imageOffset"":517597,""symbol"":""CFRunLoopRunSpecific"",""symbolLocation"":563,""imageIndex"":1},{""imageOffset"":206065,""symbol"":""RunCurrentEventLoopInMode"",""symbolLocation"":292,""imageIndex"":2},{""imageOffset"":205383,""symbol"":""ReceiveNextEventCommon"",""symbolLocation"":587,""imageIndex"":2},{""imageOffset"":204773,""symbol"":""_BlockUntilNextEventMatchingListInModeWithFilter"",""symbolLocation"":70,""imageIndex"":2},{""imageOffset"":256844,""symbol"":""_DPSNextEvent"",""symbolLocation"":886,""imageIndex"":3},{""imageOffset"":250296,""symbol"":""-[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:]"",""symbolLocation"":1411,""imageIndex"":3},{""imageOffset"":193961,""symbol"":""-[NSApplication run]"",""symbolLocation"":586,""imageIndex"":3},{""imageOffset"":143085,""symbol"":""QCocoaEventDispatcher::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)"",""symbolLocation"":2205,""imageIndex"":4},{""imageOffset"":1980305,""symbol"":""QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>)"",""symbolLocation"":401,""imageIndex"":5},{""imageOffset"":1997642,""symbol"":""QCoreApplication::exec()"",""symbolLocation"":346,""imageIndex"":5},{""imageOffset"":29742,""symbol"":""TrustedMain"",""symbolLocation"":1502,""imageIndex"":6},{""imageOffset"":16129,""imageIndex"":7},{""imageOffset"":21758,""symbol"":""start"",""symbolLocation"":462,""imageIndex"":8}]},{""id"":12602,""name"":""nspr-1"",""frames"":[{""imageOffset"":36426,""symbol"":""__select"",""symbolLocation"":10,""imageIndex"":0},{""imageOffset"":567456,""imageIndex"":9},{""imageOffset"":575205,""symbol"":""PR_Poll"",""symbolLocation"":1061,""imageIndex"":9},{""imageOffset"":77429,""imageIndex"":10},{""imageOffset"":596630,""imageIndex"":9},{""imageOffset"":980396,""imageIndex"":11},{""imageOffset"":1748684,""imageIndex"":11},{""imageOffset"":25844,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":12},{""imageOffset"":8207,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":12}]},{""id"":12603,""name"":""nspr-2"",""frames"":[{""imageOffset"":13574,""symbol"":""__psynch_cvwait"",""symbolLocation"":10,""imageIndex"":0},{""imageOffset"":27241,""symbol"":""_pthread_cond_wait"",""symbolLocation"":1224,""imageIndex"":12},{""imageOffset"":589310,""symbol"":""PR_WaitCondVar"",""symbolLocation"":254,""imageIndex"":9},{""imageOffset"":590509,""symbol"":""PR_Wait"",""symbolLocation"":61,""imageIndex"":9},{""imageOffset"":47032,""imageIndex"":10},{""imageOffset"":410105,""imageIndex"":9},{""imageOffset"":596630,""imageIndex"":9},{""imageOffset"":980396,""imageIndex"":11},{""imageOffset"":1748684,""imageIndex"":11},{""imageOffset"":25844,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":12},{""imageOffset"":8207,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":12}]},{""id"":12604,""name"":""VBoxSVCWatcher"",""frames"":[{""imageOffset"":13574,""symbol"":""__psynch_cvwait"",""symbolLocation"":10,""imageIndex"":0},{""imageOffset"":27241,""symbol"":""_pthread_cond_wait"",""symbolLocation"":1224,""imageIndex"":12},{""imageOffset"":1732412,""symbol"":""RTSemEventWait"",""symbolLocation"":364,""imageIndex"":11},{""imageOffset"":1023393,""imageIndex"":13},{""imageOffset"":980396,""imageIndex"":11},{""imageOffset"":1748684,""imageIndex"":11},{""imageOffset"":25844,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":12},{""imageOffset"":8207,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":12}]},{""id"":12605,""name"":""UIMainEventListeningThread"",""frames"":[{""imageOffset"":13574,""symbol"":""__psynch_cvwait"",""symbolLocation"":10,""imageIndex"":0},{""imageOffset"":27241,""symbol"":""_pthread_cond_wait"",""symbolLocation"":1224,""imageIndex"":12},{""imageOffset"":589287,""symbol"":""PR_WaitCondVar"",""symbolLocation"":231,""imageIndex"":9},{""imageOffset"":590509,""symbol"":""PR_Wait"",""symbolLocation"":61,""imageIndex"":9},{""imageOffset"":22299,""imageIndex"":10},{""imageOffset"":21485,""imageIndex"":10},{""imageOffset"":41017,""imageIndex"":10},{""imageOffset"":471789,""imageIndex"":9},{""imageOffset"":468203,""imageIndex"":9},{""imageOffset"":2963010,""symbol"":""CEventSource::GetEvent(CEventListener const&, int)"",""symbolLocation"":162,""imageIndex"":14},{""imageOffset"":944695,""imageIndex"":14},{""imageOffset"":170347,""imageIndex"":5},{""imageOffset"":25844,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":12},{""imageOffset"":8207,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":12}]},{""id"":12606,""name"":""UIMainEventListeningThread"",""frames"":[{""imageOffset"":13574,""symbol"":""__psynch_cvwait"",""symbolLocation"":10,""imageIndex"":0},{""imageOffset"":27241,""symbol"":""_pthread_cond_wait"",""symbolLocation"":1224,""imageIndex"":12},{""imageOffset"":1732412,""symbol"":""RTSemEventWait"",""symbolLocation"":364,""imageIndex"":11},{""imageOffset"":282832,""imageIndex"":13},{""imageOffset"":287485,""imageIndex"":13},{""imageOffset"":1945642,""imageIndex"":13},{""imageOffset"":2963010,""symbol"":""CEventSource::GetEvent(CEventListener const&, int)"",""symbolLocation"":162,""imageIndex"":14},{""imageOffset"":944695,""imageIndex"":14},{""imageOffset"":170347,""imageIndex"":5},{""imageOffset"":25844,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":12},{""imageOffset"":8207,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":12}]},{""id"":12616,""name"":""UIMainEventListeningThread"",""frames"":[{""imageOffset"":13574,""symbol"":""__psynch_cvwait"",""symbolLocation"":10,""imageIndex"":0},{""imageOffset"":27241,""symbol"":""_pthread_cond_wait"",""symbolLocation"":1224,""imageIndex"":12},{""imageOffset"":1732412,""symbol"":""RTSemEventWait"",""symbolLocation"":364,""imageIndex"":11},{""imageOffset"":282832,""imageIndex"":13},{""imageOffset"":287485,""imageIndex"":13},{""imageOffset"":1945642,""imageIndex"":13},{""imageOffset"":2963010,""symbol"":""CEventSource::GetEvent(CEventListener const&, int)"",""symbolLocation"":162,""imageIndex"":14},{""imageOffset"":944695,""imageIndex"":14},{""imageOffset"":170347,""imageIndex"":5},{""imageOffset"":25844,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":12},{""imageOffset"":8207,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":12}]},{""id"":12645,""name"":""MainHGCMthread"",""frames"":[{""imageOffset"":13574,""symbol"":""__psynch_cvwait"",""symbolLocation"":10,""imageIndex"":0},{""imageOffset"":27241,""symbol"":""_pthread_cond_wait"",""symbolLocation"":1224,""imageIndex"":12},{""imageOffset"":1732587,""symbol"":""RTSemEventWait"",""symbolLocation"":539,""imageIndex"":11},{""imageOffset"":1707621,""imageIndex"":13},{""imageOffset"":1709398,""imageIndex"":13},{""imageOffset"":1727243,""imageIndex"":13},{""imageOffset"":1707071,""imageIndex"":13},{""imageOffset"":980396,""imageIndex"":11},{""imageOffset"":1748684,""imageIndex"":11},{""imageOffset"":25844,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":12},{""imageOffset"":8207,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":12}]},{""id"":12646,""name"":""EMT"",""frames"":[{""imageOffset"":16346,""symbol"":""__ioctl"",""symbolLocation"":10,""imageIndex"":0},{""imageOffset"":16327,""symbol"":""ioctl"",""symbolLocation"":150,""imageIndex"":0},{""imageOffset"":1791149,""imageIndex"":11},{""imageOffset"":1758950,""symbol"":""SUPR3CallVMMR0Ex"",""symbolLocation"":438,""imageIndex"":11},{""imageOffset"":715314,""imageIndex"":15},{""imageOffset"":711153,""imageIndex"":15},{""imageOffset"":294331,""imageIndex"":15},{""imageOffset"":709086,""imageIndex"":15},{""imageOffset"":980396,""imageIndex"":11},{""imageOffset"":1748684,""imageIndex"":11},{""imageOffset"":25844,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":12},{""imageOffset"":8207,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":12}]},{""id"":12647,""name"":""nspr-3"",""frames"":[{""imageOffset"":13574,""symbol"":""__psynch_cvwait"",""symbolLocation"":10,""imageIndex"":0},{""imageOffset"":27241,""symbol"":""_pthread_cond_wait"",""symbolLocation"":1224,""imageIndex"":12},{""imageOffset"":589310,""symbol"":""PR_WaitCondVar"",""symbolLocation"":254,""imageIndex"":9},{""imageOffset"":590509,""symbol"":""PR_Wait"",""symbolLocation"":61,""imageIndex"":9},{""imageOffset"":47032,""imageIndex"":10},{""imageOffset"":410105,""imageIndex"":9},{""imageOffset"":596630,""imageIndex"":9},{""imageOffset"":980396,""imageIndex"":11},{""imageOffset"":1748684,""imageIndex"":11},{""imageOffset"":25844,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":12},{""imageOffset"":8207,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":12}]},{""id"":12668,""name"":""ShClipboard"",""frames"":[{""imageOffset"":13574,""symbol"":""__psynch_cvwait"",""symbolLocation"":10,""imageIndex"":0},{""imageOffset"":27241,""symbol"":""_pthread_cond_wait"",""symbolLocation"":1224,""imageIndex"":12},{""imageOffset"":1732587,""symbol"":""RTSemEventWait"",""symbolLocation"":539,""imageIndex"":11},{""imageOffset"":1707621,""imageIndex"":13},{""imageOffset"":1709398,""imageIndex"":13},{""imageOffset"":1712509,""imageIndex"":13},{""imageOffset"":1707071,""imageIndex"":13},{""imageOffset"":980396,""imageIndex"":11},{""imageOffset"":1748684,""imageIndex"":11},{""imageOffset"":25844,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":12},{""imageOffset"":8207,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":12}]},{""triggered"":true,""id"":12669,""name"":""SHCLIP"",""threadState"":{""r13"":{""value"":206158430216},""rax"":{""value"":0},""rflags"":{""value"":582},""cpu"":{""value"":0},""r14"":{""value"":6},""rsi"":{""value"":6},""r8"":{""value"":123145402422544},""cr2"":{""value"":140704642903896},""rdx"":{""value"":0},""r10"":{""value"":0},""r9"":{""value"":140703543361441},""r15"":{""value"":22},""rbx"":{""value"":123145402429440},""trap"":{""value"":133},""err"":{""value"":33554760},""r11"":{""value"":582},""rip"":{""value"":140703543402770,""matchesCrashFrame"":1},""rbp"":{""value"":123145402422896},""rsp"":{""value"":123145402422856},""r12"":{""value"":79875},""rcx"":{""value"":123145402422856},""flavor"":""x86_THREAD_STATE"",""rdi"":{""value"":79875}},""frames"":[{""imageOffset"":28946,""symbol"":""__pthread_kill"",""symbolLocation"":10,""imageIndex"":0},{""imageOffset"":25108,""symbol"":""pthread_kill"",""symbolLocation"":263,""imageIndex"":12},{""imageOffset"":531728,""symbol"":""abort"",""symbolLocation"":123,""imageIndex"":16},{""imageOffset"":65714,""symbol"":""abort_message"",""symbolLocation"":241,""imageIndex"":17},{""imageOffset"":4605,""symbol"":""demangling_terminate_handler()"",""symbolLocation"":266,""imageIndex"":17},{""imageOffset"":120073,""symbol"":""_objc_terminate()"",""symbolLocation"":96,""imageIndex"":18},{""imageOffset"":62679,""symbol"":""std::__terminate(void (*)())"",""symbolLocation"":8,""imageIndex"":17},{""imageOffset"":73045,""symbol"":""__cxxabiv1::failed_throw(__cxxabiv1::__cxa_exception*)"",""symbolLocation"":27,""imageIndex"":17},{""imageOffset"":72988,""symbol"":""__cxa_throw"",""symbolLocation"":116,""imageIndex"":17},{""imageOffset"":89243,""symbol"":""objc_exception_throw"",""symbolLocation"":302,""imageIndex"":18},{""imageOffset"":1799220,""symbol"":""_CFThrowFormattedException"",""symbolLocation"":202,""imageIndex"":1},{""imageOffset"":1804131,""symbol"":""_NSArrayRaiseBoundException"",""symbolLocation"":82,""imageIndex"":1},{""imageOffset"":262108,""symbol"":""-[__NSCFArray objectAtIndex:]"",""symbolLocation"":154,""imageIndex"":1},{""imageOffset"":83570,""symbol"":""IndexToItem(OpaquePasteboardRef*, long)"",""symbolLocation"":195,""imageIndex"":19},{""imageOffset"":83343,""symbol"":""PasteboardGetItemIdentifier"",""symbolLocation"":170,""imageIndex"":19},{""imageOffset"":36954,""imageIndex"":20},{""imageOffset"":35870,""imageIndex"":20},{""imageOffset"":980396,""imageIndex"":11},{""imageOffset"":1748684,""imageIndex"":11},{""imageOffset"":25844,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":12},{""imageOffset"":8207,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":12}]},{""id"":12670,""name"":""DragAndDropSvc"",""frames"":[{""imageOffset"":13574,""symbol"":""__psynch_cvwait"",""symbolLocation"":10,""imageIndex"":0},{""imageOffset"":27241,""symbol"":""_pthread_cond_wait"",""symbolLocation"":1224,""imageIndex"":12},{""imageOffset"":1732587,""symbol"":""RTSemEventWait"",""symbolLocation"":539,""imageIndex"":11},{""imageOffset"":1707621,""imageIndex"":13},{""imageOffset"":1709398,""imageIndex"":13},{""imageOffset"":1712509,""imageIndex"":13},{""imageOffset"":1707071,""imageIndex"":13},{""imageOffset"":980396,""imageIndex"":11},{""imageOffset"":1748684,""imageIndex"":11},{""imageOffset"":25844,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":12},{""imageOffset"":8207,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":12}]},{""id"":12674,""name"":""Timer"",""frames"":[{""imageOffset"":13574,""symbol"":""__psynch_cvwait"",""symbolLocation"":10,""imageIndex"":0},{""imageOffset"":27241,""symbol"":""_pthread_cond_wait"",""symbolLocation"":1224,""imageIndex"":12},{""imageOffset"":1732412,""symbol"":""RTSemEventWait"",""symbolLocation"":364,""imageIndex"":11},{""imageOffset"":1670413,""imageIndex"":11},{""imageOffset"":980396,""imageIndex"":11},{""imageOffset"":1748684,""imageIndex"":11},{""imageOffset"":25844,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":12},{""imageOffset"":8207,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":12}]},{""id"":12675,""name"":""PDMNsTx"",""frames"":[{""imageOffset"":13274,""symbol"":""__semwait_signal"",""symbolLocation"":10,""imageIndex"":0},{""imageOffset"":67753,""symbol"":""nanosleep"",""symbolLocation"":196,""imageIndex"":16},{""imageOffset"":1748819,""symbol"":""RTThreadSleep"",""symbolLocation"":67,""imageIndex"":11},{""imageOffset"":1691290,""imageIndex"":15},{""imageOffset"":451503,""imageIndex"":15},{""imageOffset"":980396,""imageIndex"":11},{""imageOffset"":1748684,""imageIndex"":11},{""imageOffset"":25844,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":12},{""imageOffset"":8207,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":12}]},{""id"":12801,""name"":""ShFolders"",""frames"":[{""imageOffset"":13574,""symbol"":""__psynch_cvwait"",""symbolLocation"":10,""imageIndex"":0},{""imageOffset"":27241,""symbol"":""_pthread_cond_wait"",""symbolLocation"":1224,""imageIndex"":12},{""imageOffset"":1732587,""symbol"":""RTSemEventWait"",""symbolLocation"":539,""imageIndex"":11},{""imageOffset"":1707621,""imageIndex"":13},{""imageOffset"":1709398,""imageIndex"":13},{""imageOffset"":1712509,""imageIndex"":13},{""imageOffset"":1707071,""imageIndex"":13},{""imageOffset"":980396,""imageIndex"":11},{""imageOffset"":1748684,""imageIndex"":11},{""imageOffset"":25844,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":12},{""imageOffset"":8207,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":12}]},{""id"":12806,""name"":""com.apple.NSEventThread"",""frames"":[{""imageOffset"":2746,""symbol"":""mach_msg_trap"",""symbolLocation"":10,""imageIndex"":0},{""imageOffset"":3627,""symbol"":""mach_msg"",""symbolLocation"":59,""imageIndex"":0},{""imageOffset"":527090,""symbol"":""__CFRunLoopServiceMachPort"",""symbolLocation"":319,""imageIndex"":1},{""imageOffset"":520651,""symbol"":""__CFRunLoopRun"",""symbolLocation"":1325,""imageIndex"":1},{""imageOffset"":517597,""symbol"":""CFRunLoopRunSpecific"",""symbolLocation"":563,""imageIndex"":1},{""imageOffset"":1756568,""symbol"":""_NSEventThread"",""symbolLocation"":132,""imageIndex"":3},{""imageOffset"":25844,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":12},{""imageOffset"":8207,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":12}]},{""id"":12807,""name"":""GuestControlSvc"",""frames"":[{""imageOffset"":13574,""symbol"":""__psynch_cvwait"",""symbolLocation"":10,""imageIndex"":0},{""imageOffset"":27241,""symbol"":""_pthread_cond_wait"",""symbolLocation"":1224,""imageIndex"":12},{""imageOffset"":1732587,""symbol"":""RTSemEventWait"",""symbolLocation"":539,""imageIndex"":11},{""imageOffset"":1707621,""imageIndex"":13},{""imageOffset"":1709398,""imageIndex"":13},{""imageOffset"":1712509,""imageIndex"":13},{""imageOffset"":1707071,""imageIndex"":13},{""imageOffset"":980396,""imageIndex"":11},{""imageOffset"":1748684,""imageIndex"":11},{""imageOffset"":25844,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":12},{""imageOffset"":8207,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":12}]},{""id"":12812,""name"":""GuestPropSvc"",""frames"":[{""imageOffset"":13574,""symbol"":""__psynch_cvwait"",""symbolLocation"":10,""imageIndex"":0},{""imageOffset"":27241,""symbol"":""_pthread_cond_wait"",""symbolLocation"":1224,""imageIndex"":12},{""imageOffset"":1732587,""symbol"":""RTSemEventWait"",""symbolLocation"":539,""imageIndex"":11},{""imageOffset"":1707621,""imageIndex"":13},{""imageOffset"":1709398,""imageIndex"":13},{""imageOffset"":1712509,""imageIndex"":13},{""imageOffset"":1707071,""imageIndex"":13},{""imageOffset"":980396,""imageIndex"":11},{""imageOffset"":1748684,""imageIndex"":11},{""imageOffset"":25844,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":12},{""imageOffset"":8207,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":12}]},{""id"":12818,""na"	jensseidel
21147	Display driver bug causes VM to abort upon start	Mac OS X	VirtualBox 7.0.0	defect	2022-10-13T21:25:25Z	2022-11-23T14:29:54Z	2022-11-23T14:29:54Z	"I upgraded from VirtualBox 6 to 7 on a Intel MacOS 11.7 host that has a Windows 10 guest. Upon upgrading to v7, the VM would be aborted upon starting with the following error message

{{{
VM Name: WIN10

The VM session was aborted.
Result Code:
NS_ERROR_FAILURE (0X80004005)
Component:
SessionMachine
Interface:
ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}
}}}

I opened a thread on the forums to get help with troubleshooting the issue and they isolated it to a display driver bug (https://forums.virtualbox.org/viewtopic.php?f=8&t=107326) and asked me to open a bug ticket here. They asked me to disable 3D acceleration which makes it start (often freezing after a few minutes now). I have attached the logs I had attached to the forum thread for reference here as well."	knockout
19726	Reported memory usage doubled in 6.1.4 on MacOS Mojave and later	Mac OS X	VirtualBox 6.1.10	defect	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
21096	Tab text do not shown at macOS Monterey	Mac OS X	VirtualBox 6.1.38	defect	2022-09-05T11:58:40Z	2022-09-05T12:04:16Z	2022-09-05T12:04:16Z	"Hello,
I'm using VirtualBox 6.1.38 at Macbook Pro 2015 running macOS Monterey 12.5.1.
When I go to any properties window that use tabs, it doesn't show it's text at the tab."	coldscientist
20947	VirtualBox and VirtualBoxVM segfault when focus changes	Mac OS X	VirtualBox 6.1.34	defect	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
20817	Monterey Guest is unstable, reboots every few minutes	Mac OS X	VirtualBox 6.1.32	defect	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
20802	Interface Bug macOS Monterey and VirtualBOX 6.1.32 r149290	Mac OS X	VirtualBox 6.1.32	defect	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
20693	VERR_VERSION_MISMATCH in VBoxExtPackRegister on 6.1.30	Mac OS X	VirtualBox 6.1.30	defect	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
7213	USB: failed to create a proxy device (VERR_OUT_OF_RESOURCES)	Mac OS X	VirtualBox 4.0.8	defect	2010-07-21T15:39:26Z	2021-10-20T16:37:24Z	2021-10-20T16:37:24Z	"I'm using vbox 3.2.6 on MacOS 10.6.4, trying to attach an Android phone in ""download"" mode, and I get:


00:08:37.463 USB: Failed to open device 'p=0x6601;v=0x04e8;s=0x0000004883dc07fe;l=0x26200000', plug-in creation failed with irc=0xe00002be.
00:08:37.463 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={6375231a-c17c-464b-92cb-ae9e128d71c3} aComponent={Console} aText={Failed to create a proxy device for the USB device. (Error: VERR_OUT_OF_RESOURCES)} aWarning=false, preserve=false


I get this for all 3 of my VMs: Ubuntu, WinXP & Win7

It's the first time I've tried this particular device, although I have successfully attached other USB devices to VMs, of course. I tried rebooting the Mac.
"	Calum Mackay
19153	VM crashes - Virtualbox vm quit unexpectedly	Mac OS X	VirtualBox 6.0.14	defect	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
20380	Suggestions for development for a Mac Host	Mac OS X	VirtualBox 6.1.22	defect	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
20362	VirtualBox Error using Ubuntu	Mac OS X	VirtualBox 6.1.22	defect	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
20361	vboxnet0 not working on startup	Mac OS X	VirtualBox 6.1.22	defect	2021-05-12T15:55:22Z	2021-05-12T15:55:22Z	2021-05-12T15:55:22Z	"When I boot up, vboxnet0 isn't created which means other tools that depend on it (i.e. gns3) can't start up and load virtualbox.

I've set virtualbox to start on login, which solves that problem, but now I have the issue whereby the interface is created without an IP address.

I have to go into virtualbox network settings and change the vboxnet0 IP address in order for an IP address to be created.

A secondary effect of this is that the UI isn't updated until Virtualbox restarts, so if you change the vboxnet0 address to something else (i.e. 192.168.56.2/24), ifconfig shows it correctly but the UI reverts to the previous state (i.e. 192.168.56.1/24). This means that you can't then revert to that address without restarting virtualbox. 

This is on macos 11.3 and 11.3.1."	craigmcfly
19386	FileVault	Mac OS X	VirtualBox 6.1.4	defect	2020-03-08T11:46:20Z	2021-04-30T07:12:52Z	2021-04-30T07:12:52Z	"VirtualBox successfully boots macOS Sierra, High Sierra, Mojave, or Catalina, and these operating systems allow encrypting volumes with FileVault2. Attempting to boot a FileVault2-encrypted volume in VirtualBox 6.1.4 or lower results in several boot errors, most importantly `**** ERROR _LoginUIInitializedGraphics Can't install updated AppleEvent protocol`. The FileVault login UI will not load, probably because macOS cannot find or use the VirtualBox EFI implementation of the UEFI Graphics Output Protocol.

An open-source (BSD 3-clause license) implementation of this graphics protocol is available through the [https://github.com/acidanthera/OpenCorePkg/blob/master/Library/OcConsoleLib/ConsoleGop.c OpenCore ConsoleGop.c] source file.

The FileVault2 prompt can be successfully loaded by loading OpenCore through the EFI Internal Shell, and macOS boots normally when the correct password is provided.

Maybe this protocol can be implemented in VirtualBox so FileVault could work without the OpenCore bootloader.

Log files are not attached because the error doesn't show up in the log, only the normal VM startup and shutdown procedures.

----

Steps to reproduce:
* Install any version of macOS Sierra, High Sierra, Mojave, or Catalina (and probably other versions that use FileVault2)
* Encrypt the system volume with FileVault2 (called simply FileFault in System Preferences).
* Reboot. The macOS kernel will not be able to load the FileVault password prompt.

Workaround:
* Load OpenCore.efi through the EFI Internal Shell with `ProvideConsoleGop` set to `true`. The password prompt will be displayed and the FileVault volume can be decrypted, continuing normal boot."	Jack_Smith
20257	Failed to open a session for the virtual machine Windows 10	Mac OS X	VirtualBox 6.1.18	defect	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	Mac OS X	VirtualBox 6.1.18	defect	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
19952	Virtualbox 6.1.14 breaks compatibility on Mac OSX	Mac OS X	VirtualBox 6.1.14	defect	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
20082	Virtualbox VM crashes with macOS Catalina host and High Sierra guest	Mac OS X	VirtualBox 6.1.16	defect	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
20066	Error on starting 6.1 with windows  on Mac with Big Sur w	Mac OS X	VirtualBox 6.1.16	defect	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
19929	VMs only start in headless mode on Big Sur	Mac OS X		defect	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
19558	Clipboard failure	Mac OS X	VirtualBox 6.1.6	defect	2020-05-04T17:44:40Z	2020-07-23T19:41:04Z	2020-07-23T19:41:04Z	"I've reverted to using the macOS version of Microsoft Remote Desktop (Version 10.3.9 (1767)) to connect to the Vm guest (Windows 10 1909). I've enable the Remote Display server in VB for this.

The clipboard text being copied is TextEdit to Notepad and vice versa. When I copy from host to guest, it works as expected (although I see in the log a note about on format that is not announced), but from guest to host it causes TextEdit and Microsoft Remote Desktop to freeze (spinning rainbow wheel) and to recover I either need to shutdown the VM, by opening a VB GUI client, or force quit the MSRDP client.

I see a number of changes in the shared clipboard of late, and I'm not sure if this is just a new bug or an issue with the MSRDP client not being supported (it has worked in earlier versions). Is there a specific configuration that is required to get this to work? I'm really looking for text based support, although the text may some times be a URL as well.

Attached are the logs where the issue has occurred."	ncj
11211	Feature request: add auto update functionality	Mac OS X	VirtualBox 4.2.4	enhancement	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
19697	Running VM crashes on macOS 10.13.6 with VirtualBox 6.1.10 r138449	Mac OS X	VirtualBox 6.1.10	defect	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
19694	Failure reading data from .iso (optical drive) at random locations	Mac OS X	VirtualBox 6.1.10	defect	2020-07-02T11:29:26Z	2020-07-02T11:29:26Z	2020-07-02T11:29:26Z	"I'm trying to install CentOS 8 in a virtual machine, but the VM keeps getting bad data from the ISO file.

This results in the system getting stuck booting into the installer or crashes at the disk verification step at varying procentages.

I know the ISO itself is flawless, its sha256sum matches the specified hash from CentOS. 
To me it seems like VirtualBox is having issues with providing the OS/Kernel with the right data.

I've also tried installing it with VirtualBox 6.0.22 and 5.2.42, both having the same issue. (5.2.42 has some graphical glitches as well, but likely unrelated)

I'm running OS X 10.15.5 on a MacbookPro16,1

How to reproduce:
1. Make new VM in Virtualbox on OS X, with the iso CentOS-8.2.2004.x86_64-minimal.iso
2. Let it boot the iso
3. Very likely to fail, is not run it a second time or try to complete the installation

Let me know if there is any other information I can provide"	smiba
19673	offering, downloading and installing new versions not supported by host	Mac OS X	VirtualBox 6.1.10	defect	2020-06-19T15:57:21Z	2020-06-19T15:59:46Z	2020-06-19T15:59:46Z	You have three opportunities to tell a user that the software they have been offered, are downloading, or installing is not supported by their OS. You don't. Instead, the user installs the software only to later discover some feature (such as installing an ExtensionPack) no longer works. This could be improved.	littlerunningdeer
19517	Support Sparkle application update framework on macOS	Mac OS X	VirtualBox 6.1.6	enhancement	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
19504	I'm not able to start a headless virtualmachine	Mac OS X	VirtualBox 6.1.6	defect	2020-04-17T11:26:11Z	2020-04-17T11:52:32Z	2020-04-17T11:52:32Z	"I'm not able to start the vm in headless mode from my macOS Mojave 10.14.6. I'm not ready to upgrade to Catalina because I have some 32 bits applications that doesn't work in Catalina.

I'm running the last version of VirtualBox 6.1.6r137129

It seems that error only happens when: Display > Screen > Acceleration > Enable 3D Acceleration is enabled,

"	arturocandela
19474	Incorrect checksum for freed object	Mac OS X	VirtualBox 6.1.4	defect	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
19434	some characters are not rendered in QML Application	Mac OS X	VirtualBox 6.1.4	defect	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
19388	crashes during win updates	Mac OS X	VirtualBox 6.1.4	defect	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
9812	VB v 4.1.4 Splitter Drag Handle Not Available	Mac OS X	VirtualBox 4.1.4	defect	2011-10-26T00:56:05Z	2020-02-22T14:51:05Z	2020-02-22T14:51:05Z	"Mac OS X 10.7.1 host. VirtualBox v 4.1.4. See Discussion:[https://forums.virtualbox.org/viewtopic.php?f=8&t=45512&p=205827#p205827]


{{{
Part A:
1.) With VirtualBox Manager frontmost
2.) Slide the Splitter all the way to the left
3.) Quit the program
4.) Open VB again
5.) Splitter handle is not available anymore
}}}


I had to edit the xml file at <ExtraDataItem name=""GUI/SplitterSizes"" value=""0,661""/> to get back my list of VMs.

Part B:
As above, but after step 2, instead of quitting the app, try to move the splitter handle back. The handle is only 1 pixel wide, very hard to grab."	Daniel
19323	"VirtualBox show me error when i click on ""Start"" button (it was working perfectly 3 month ago)"	Mac OS X	VirtualBox 6.1.0	defect	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
17500	macOS 10.13.3 - Host Only Networking - Host not accessible	Mac OS X	VirtualBox 5.2.6	defect	2018-01-25T23:22:52Z	2020-02-13T04:37:34Z	2020-02-13T04:37:34Z	"After installing macOS update to 10.13.3,  VirtualBox 5.2.6 host only networking started to show an issue never seen before.
VMs on the same hostonly network can communicate, 
while VM-host, in both direction, communication does not happen, every attempted connection times out

Eventually I worked around the issue with a host restart, but every new host-only network created is defective.
This is a big issue for example when using vagrantfiles to create clusters of VMs.

create a vboxnetX hostonly network in the VBox UI, with DHCP enabled
start a simple VM defined to use vboxnetX (eg vanilla ubuntu with DHCP) : host will NOT be reachable from VM, VM will NOT be reachable by host

shut down VM
restart macOS !!!
vboxnetX adapter is now NOT listed by ifconfig (before VB starts)

start VBox (-> vboxnetX created but not assigned an IP)

start the VM previously defined as using the vboxnetX adapter
vboxnetX will be assigned an ip ... and this time VM/host communication works

"	Edoardo
19268	VirtualBox Extension Pack 6.0.16 installation failure	Mac OS X	VirtualBox 6.0.16	defect	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
19212	Unexpected exception: std::bad_alloc [St9bad_alloc]	Mac OS X	VirtualBox 6.1.0	defect	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
18979	"Port forwarding ""NAT network"" window for IPv4 display issue"	Mac OS X	VirtualBox 6.0.12	defect	2019-10-03T09:17:44Z	2019-12-07T03:07:44Z	2019-12-07T03:07:44Z	The window does not display the name column properly and it is neither resizable	tutug
17803	Virutalbox fails to install on MacOS 10.13.5	Mac OS X	VirtualBox 5.2.12	defect	2018-06-05T16:45:46Z	2019-12-07T02:44:13Z	2019-12-07T02:44:13Z	"Virtualbox fails to install without any obvious explanation except this part of the logs:
{{{
error	18:32:10.563277 +0200	syspolicyd	Kernel Extension BLOCKED: <private>
default	18:32:10.563624 +0200	kextd	Kext rejected due to system policy: <OSKext 0x7f9b8a0dadb0 [0x7fffad793af0]> { URL = ""file:///Library/StagedExtensions/Library/Application%20Support/VirtualBox/VBoxDrv.kext/"", ID = ""org.virtualbox.kext.VBoxDrv"" }
default	18:32:10.563667 +0200	kextd	org.virtualbox.kext.VBoxDrv failed security checks; failing.
}}}
It was also tested with !VirtualBox-5.2.97-122902-OSX"	jav
18899	Allow VM window to close while VM settings window is open	Mac OS X	VirtualBox 6.0.10	defect	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
18896	Virtual hard disk UI often discards decimal point	Mac OS X	VirtualBox 6.0.10	defect	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
18876	Default window size is inscrutably small on macOS	Mac OS X	VirtualBox 6.0.10	defect	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
18743	Poweroff, Delete prompt NEVER REMEMBERS PREFERENCE	Mac OS X	VirtualBox 6.0.8	defect	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
18361	VirtualBox 6.0.2 assertion failed while starting a macOS VM	Mac OS X	VirtualBox 6.0.2	defect	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
18363	VirtualBox GUI infinite loop changing window layout - GUI unusable	Mac OS X	VirtualBox 6.0.2	defect	2019-01-26T12:59:28Z	2019-02-06T16:04:38Z	2019-02-06T16:04:38Z	"The GUI keeps flapping, with a frequency circa 1 sec, between two different layout, as you can see in the two screenshots attached. It looks like the layout/resize logic of the GUI is wrongly wired and in certain cases it can enter an infinite loop.

Worst problem is not the flapping, is the fact that the whole GUI is unresponsive, it is even impossible to reach the menu and to quit. Only way to quit is to ""force quit"" from Activity Monitor on macOS.

[[Image()]]"	marco.m
18366	Can't use vboxapi on Mac using Python bindings with anything other than the system version of Python	Mac OS X	VirtualBox 6.0.2	defect	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
18252	RFE. VirtualBox 6 MacOS 10.14.2 host with 10.12.6 guest - network share doesn't appear	Mac OS X	VirtualBox 6.0.0	enhancement	2018-12-30T20:43:01Z	2019-01-08T17:58:48Z	2019-01-08T17:58:48Z	"1. Guest Additions was added (copy/paste works).
2. A Share was setup and as many times as I go into settings for the VM I can see the share as I set it up.

Yes there's no directory on the guest OS
"	paul_h
18145	Installing VB 5.2 and VB 5.1 are not installing on my system.	Mac OS X	VirtualBox 5.2.22	defect	2018-11-22T17:39:42Z	2018-11-30T00:43:55Z	2018-11-30T00:43:55Z	I have downloaded and attempted to install both versions on my MacOS X High Sierra 10.13.6.  Each reports that the installation failed and created a crash file. I have sent the crash files attached and will follow with any other information to support this product.	TravelinMan
18118	After upgrade XP game hangs	Mac OS X	VirtualBox 5.2.20	defect	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
18047	VirtualBox Icon Not Centered	Mac OS X	VirtualBox 5.2.18	defect	2018-10-12T18:06:58Z	2018-10-25T19:53:54Z	2018-10-25T19:53:54Z	"This may seem stupid, but it's annoying.  The VirtualBox Icon for Mac is not centered.  It's shifted to the left, so it doesn't line up with other icons in the dock and is off center of text.  

"	deku
18011	Video capture doesn't work after upgrade from 5.1.38 to 5.2.18	Mac OS X	VirtualBox 5.2.18	defect	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
17928	Kernel panic for 5.2.16 virtual box on MacOs	Mac OS X	VirtualBox 5.2.16	defect	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
17794	Host Network Manager GUI for macOS lack of refresh	Mac OS X	VirtualBox 5.2.12	defect	2018-05-31T09:35:05Z	2018-05-31T12:10:21Z	2018-05-31T12:10:21Z	"Host Network Manager screen has problem of refreshing while changing from Virtual Media Manager or while you click through interfaces.
Workaround: resize window after any click inside HNM."	juHoyokobU
17593	Unable to Rename Screenshot - Keyboard Capture	Mac OS X	VirtualBox 5.2.8	defect	2018-03-06T08:28:48Z	2018-03-06T11:43:58Z	2018-03-06T11:43:58Z	When trying to do a Screenshot it is impossible to create a new named Folder, rename a Folder or rename the Screenshot File in the Popup Filerequester. This is due that the Mouse will be active in the Mac OS Popup but the Keyboard is still captured inside the VM and is not entering anything in the Filerequester. 	tops4u
17351	Virtual box GUI bad access crash on NAT network settings edit	Mac OS X	VirtualBox 5.2.0	defect	2017-12-06T13:25:06Z	2018-03-01T08:04:42Z	2018-03-01T08:04:42Z	"I can, rather consistently, get the GUI to crash when trying to edit the settings for a NAT network.

The crash follows the presence of some visual defects and that in turn is based on presence of the ""Global settings"" on the main GUI screen. If I don't enable the tabs for either of the global settings, I don't get the visual defects and I don't experience a crash.

Whilst the GUI defects don't bother me much, the patter here seems to relate to them and the new ""Global Tools"" tabs. Once either or both of the ""Virtual Media Manager"" or the ""Host Network Manager"" have been enabled from either the selection or the drop down.

Go to Preferences > Network > Add or selection a Nat Network > Edit > crashes.

My host is macOS 10.13.1, and VirtualBox 5.2.2. I've also tested it with 5.2.3-119405 and the effects and crash remain.

Forum discussion link; https://forums.virtualbox.org/viewtopic.php?f=8&t=85703
"	ncj
13118	Presenting compatible CPU architecture to Mac OS X guest VMs	Mac OS X	VirtualBox 4.3.12	defect	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
17442	Mac OS High Sierra VM crash	Mac OS X	VirtualBox 5.2.4	defect	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
17350	use of serial port crashes VM w/ non-mainstream OS	Mac OS X	VirtualBox 5.1.30	defect	2017-12-06T11:43:22Z	2018-01-10T22:44:44Z	2018-01-10T22:44:44Z	"I try to run a Cisco router VM based on x86 known as IOSv (virtual IOS). The same image works perfectly fine with KVM and VMware Fusion / Workstation / ESXi. It also works OK in VB as long as there is no serial port connected. However, the serial console is the only way to access the box (assuming it does not have a configuration which also would allow to SSH / Telnet into the VM / router).

When starting up the VM in VB it displays the Grub boot loader and then, in 9 out of 10 cases, instantly displays a Guru meditation instead of loading the kernel image. This is regardless of using a Pipe, a TCP port or a raw file for the port. Haven't tried host device as that's useless for our use case. If the port is enabled but  'disconnected' then the VM comes up fine all the time.

This was tested on a Mac (MacBook Pro Mid2017, Intel Core i7) with 
- VB 5.1.30
- VB 5.0.40
- VB 5.2.2

I also ran into this problem on Linux. Here I run VB in a nested VM running on KVM on an Intel i7 w/ host-passthrough and 5.0.40 on Ubuntu Xenial... It seems to work more often there (more than 1 in 10) but also produces the Guru meditation when trying often enough.
"	Ralph Schmieder
17240	GUI Bug With Snapshots on macOS	Mac OS X	VirtualBox 5.2.0	defect	2017-11-05T05:15:55Z	2017-11-10T09:30:30Z	2017-11-10T09:30:30Z	There is a bug in the GUI on macOS 10.13.1 on a MacBookPro11,2 and VirtualBox 5.2.0 r118431 (Qt5.6.3)	rj45
16474	5.1 installation fails on Sierra due to kext load issue	Mac OS X	VirtualBox 5.1.14	defect	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
17154	Guru meditation running OPENSTEP 4.2	Mac OS X	VirtualBox 5.2.0 RC 1	defect	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
17110	d3d9.dll error/Starting Quicken2015/Starting Adobe Acrobat Reader/OSX Host/Win 10	Mac OS X	VirtualBox 5.1.28	defect	2017-09-23T22:14:34Z	2017-09-23T22:14:34Z	2017-09-23T22:14:34Z	"Starting quicken RdrCEF.exe and qw.exe:  

RdrCEF.exe - Entry Point Not Found
qw.exe - Entry Point Not Found

The procedure entry point SfmDxGetSwapChainStats could not be located in the dynamic link library C\Windows\System32\d3d9.dll.

 "	EHES
6681	VirtualBox Accessibility for Mac OS X Hosts Reduced, Possibly Others	Mac OS X	VirtualBox 3.1.8	defect	2010-05-12T20:30:26Z	2017-09-04T21:44:21Z	2017-09-04T21:44:21Z	"I checked the changelogs between 3.0.12, when VirtualBox was (imperfectly, but adequately in conjunction with the command-line) accessible on Mac OS X, using VoiceOver.  Now, and confirmed as of VirtualBox 3.1.4 by others, whatever accessibility provided by QT disappeared. What has changed?  Can we have the accessibility back?  I have transitioned one of my machines per force to Fusion, a native app that does accessibility quite well.

To launch VoiceOver, press Cmd+F5.
"	Sabahattin Gucukoglu
16841	5.1.18 working on Mavericks, but not with 5.1.20	Mac OS X	VirtualBox 5.1.22	defect	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
16974	VirtualBox crashes whenever Microsoft Lifechat USB headphones are plugged-in/out on Mac	Mac OS X	VirtualBox 5.1.26	defect	2017-08-03T07:10:50Z	2017-08-03T09:15:52Z	2017-08-03T09:15:52Z	"Whenever I plug-in '''Microsoft Lifechat LX3000''' USB headphones to my Mac, which is my VirtualBox host, VirtualBox crashes. Below is the event log.

(removed)"	Shashank.Srivastava
1766	ctrl key on OS X is not usable	Mac OS X	VirtualBox 1.6.2	defect	2008-06-23T20:01:40Z	2017-04-05T22:26:56Z	2017-04-05T22:26:56Z	When using an OS X host, the control (ctrl) + mouse press key combination is not recognized correctly. Ctrl + left click results in a right-click, which means that selecting multiple items by ctrl-clicking on files, etc. is not possible. Using ctrl-click as a command (to open links in tabs in a browser, for example) is also affected by this, as ctrl opens a context menu. In many cases this makes typical tasks impossible or frustrating in the guest OS.	clf
16639	Virtualbox 5.1.X prevents Mac Sierra from sleeping / recognizing attached screen on resume from sleep	Mac OS X	VirtualBox 5.1.18	defect	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
16441	Kernel Panic on Mac host when doing file operations on shared NFS drives	Mac OS X	VirtualBox 5.1.14	defect	2017-02-01T23:19:30Z	2017-02-27T21:25:34Z	2017-02-27T21:25:34Z	"Virtualbox causes a kernel panic on Mac OSX Sierra host when doing file operations on a shared NFS folder. There are many things that can trigger the panic, but deleting files is the easiest to reproduce.

Steps to reproduce:
{{{ 
# create a new folder
mkdir vagrant; cd vagrant
# copy both the attached vagrant box image (freebds-10.3-amd64-virtualbox.box) and the vagrantfile into this folder

# add the box to vagrant (this is the easiest way to reproducibly set up a vm)
vagrant box add freebsd-10.3-amd64-virtualbox.box --name local/freebsd
# provision the virtual machine (this will take a while)
vagrant up

# ssh into the virtual machine
vagrant ssh
# we have mounted a shared folder at /vagrant
cd /vagrant
# we need to perform file operations, and the most reproducible way I've found to do this is by creating and destroying a virtualenv
virtualenv venv
rm -rf venv  # this should crash the host
}}}

 "	logan-ncc
16256	Host OS kernel panic when running Redox 0.0.3 in VirtualBox	Mac OS X	VirtualBox 5.0.26	defect	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
16344	macos sierra mouse focus	Mac OS X	VirtualBox 5.1.12	defect	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
16254	VxWorks guest broken on v5.X	Mac OS X	VirtualBox 5.1.10	defect	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
16228	"VM crashes with ""Aborted"" status when host machine connects to bluetooth device"	Mac OS X	VirtualBox 5.1.2	defect	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
11475	Shared Folders with OS/2 as guest.	Mac OS X	VirtualBox 4.2.6	enhancement	2013-02-09T03:23:38Z	2016-10-29T05:00:20Z	2016-10-29T05:00:20Z	"Shared folders with an OS/2 guest are apparently are not implemented or maybe just broken. This makes for a very awkward process of getting data into and out of the VM in many instances. Please consider fixing or implementing this. I as well as any other OS/2 user would be very glad to test what ever was done. OS/2 in general runs very well in VBox for which I am very thankful. If this issue was fixed it would be a great help.

Thank you for your consideration."	OS2Bud
16022	"""VBoxManage list usbhost"" misidentifies ""USB version/speed"""	Mac OS X	VirtualBox 5.1.6	defect	2016-10-03T18:29:37Z	2016-10-03T18:29:37Z	2016-10-03T18:29:37Z	"The output in the ""VBoxManage list usbhost"" has one line for ""USB version/speed"". This comes up always as ""'''0'''/Low"", ""'''0'''/High"", ""'''0'''/Full"" or ""'''0'''/Super"". On other hosts the information with the same devices comes up correctly. Sometimes the __same device__ will be identified as ""'''0/Low'''"" on an OSX host and ""'''1/Full'''"" on a Windows host.

For background on this, please see: https://forums.virtualbox.org/viewtopic.php?f=1&t=80008"	Socratis
15834	Mouse Integration on OS/2 - eCS causes double pointer after guest addition upgrade.	Mac OS X	VirtualBox 5.1.4	defect	2016-08-20T03:27:23Z	2016-08-20T05:27:25Z	2016-08-20T05:27:25Z	"OS/2-eCS guest. Upgraded from Vbox 5.0.26 to 5.1.4. Installing guest additions seem normal. Reboot and find two mouse pointers. One system pointer sitting on top of the Guest pointer. They move together, well almost, but when the Guest pointer changes shape the system does not. All was well before installing the 5.1.4 guest additions.

Disable mouse integration and the pointer is normal."	Cfly
15572	Fedora 24 Kernel 4.3.6-300 Breaks VB 5.0.24 on Mac OS X 11.5	Mac OS X	VirtualBox 5.0.24	defect	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
15647	VirtualBox 5.1: Ugly icons on non-HiDPI external monitor on OS X	Mac OS X	VirtualBox 5.1.0	defect	2016-07-20T07:48:42Z	2016-07-20T07:48:42Z	2016-07-20T07:48:42Z	"I'm using a MacBook with a HiDPI builtin screen and everything looks nice there. But when when the VirtualBox window is on one of my external non-HiDPI monitors, the icons all look distorted. See the screenshot.

This is a regression in VirtualBox 5.1.0, earlier versions didn't have this problem.
"	intgr_
15208	SSL certificate error on update check	Mac OS X	VirtualBox 5.0.16	defect	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
15369	mac osx i5 crashes when 3+ vms are using > 90% cpu each	Mac OS X	VirtualBox 5.0.18	defect	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
15255	USB devices not recognized when attached after wakeup	Mac OS X	VirtualBox 5.0.16	defect	2016-03-18T22:54:46Z	2016-03-18T23:01:51Z	2016-03-18T23:01:51Z	"The following sequence of events results in an OSX host not recognizing USB devices that are attached to it.

1) Start VirtualBox VM
2) Put computer to sleep, e.g. close laptop lid and unplug USB hub connected to keyboard and mouse
3) Wake computer up
4) Re-plug USB hub

I'm using OSX 10.11.4 with VirtualBox 5.0.16. My USB hub is a Dell Monitor, model P2715Q.

The following lines from system.log seem relevant.
Mar 18 15:24:54 pwnage kernel[0]: 043192.504567 HS05@14200000: AppleUSB20XHCIPort::resetAndCreateDevice: failed to create device, disabling port
Mar 18 15:24:56 pwnage kernel[0]: 043193.752262 HS05@14200000: AppleUSB20XHCIPort::resetAndCreateDevice: failed to create device, disabling port"	pwnall
15187	OS X 10.10 guest on 10.11 host, gurumediation after successful installation	Mac OS X	VirtualBox 5.0.14	defect	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
15153	Invalid machine state: GuruMeditation	Mac OS X	VirtualBox 5.0.14	defect	2016-02-17T17:43:52Z	2016-02-17T17:51:38Z	2016-02-17T17:51:38Z	"I am running two VMs on OS X El Capitan, one of the vm keeps getting rebooted randomly with error: 
32:16:18.536412 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Invalid machine state: GuruMeditation}, preserve=false aResultDetail=0"	wei1984
10153	Resizing from the left and top borders is erratic	Mac OS X	VirtualBox 4.1.8	defect	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
14805	Certificate error	Mac OS X	VirtualBox 5.0.10	defect	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
14824	Command-W does not close VirtualBox.	Mac OS X	VirtualBox 5.0.10	enhancement	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
14840	About dialog needs to be revamped.	Mac OS X	VirtualBox 5.0.10	enhancement	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
11881	Linux Mint 15 Cinnamon with 3D accelerator crashes ==> Fixed in SVN	Mac OS X	VirtualBox 4.2.12	defect	2013-06-19T13:29:23Z	2015-10-22T06:59:21Z	2015-10-22T06:59:21Z	"I installed a fresh Linux Mint 15 Cinnamon 64 Bit as a guest in Virtual Box 4.2.12 on a MacBook Pro 5,1 with OS X 10.8.4.

Linux Mint is requesting to turn 3D accelerator on.
After start of Linux Mint, the virtual machine crashes without further warning, e.g when using the main menu several times.
The virtual machine crashes that bad, even the log files don't show anything. The machine just disappears. No reboot. Nothing.
After turning 3D accelerator off, Linux Mint 15 Cinnamon does not crash, but a info-box explains, that now the CPU usage will get high."	Vietwoojagig2
13336	MacBook Pro Retina 2014 crashes when connected to Thunderbolt display	Mac OS X	VirtualBox 4.3.14	defect	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
4370	Guest fails to start w/VLAN Interface in OSX	Mac OS X	VirtualBox 3.0.2	defect	2009-07-03T06:20:29Z	2015-08-13T17:37:42Z	2015-08-13T17:37:42Z	"error: Unknown error creating VM (VERR_GENERAL_FAILURE).

how to reproduce:

1. Create VLAN Interface in OSX (Requires Supported Interface)[[BR]]
2. Assign VLAN Interface to Virtual Interface in a new or existing Guest.[[BR]]
3. Start Guest, error is encountered.[[BR]]

Note, this setup works fine in both OpenSolaris & Debian VBox Hosts."	Ryan
13868	[On Mac OS X] The installer encountered an error that caused the installation to fail... please contact software manufacturer for assistance	Mac OS X	VirtualBox 4.3.22	defect	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
5683	Configurable actions on signals	Mac OS X	VirtualBox 3.1.0	enhancement	2009-12-07T08:53:17Z	2015-02-16T05:00:21Z	2015-02-16T05:00:21Z	"Please see my last post in this thread for background:

http://forums.virtualbox.org/viewtopic.php?f=8&t=24244&p=114221#p114221

In OS X, launchd uses SIGTERM to stop running processes.  If VirtualBox trapped signals (SIGTERM, HUP, etc.), then launchd items could be created to cleanly shutdown running VM's for those of use using VB with headless mode with OS X in more of a ""server"" mode.  I believe once the signals are trapped, that the launchd plists have sufficient options to deal with the time it takes to process various shutdown options.

Best would be to have a setting in VB that would allow user-configurable actions based on the signal received.  For example, I might want HUP to suspend the VM and SIGTERM to run acpipoweroff...or HUP to acpipoweroff and SIGTERM to poweroff.

Ideally, this setting will be in the VM settings and work whether the VM is started with VBoxHeadless or from the GUI.

As it is, working around this without the capability to handle signals, particularly SIGTERM, with OS X's launchd leaves some doubt as to complete and clean shutdown of VM's upon system reboot/shutdown.

I'm more than happy to help out with testing under 10.5/10.6 on my lab machines.  Thanks!
"	ae3265
7779	Dock issue causing log pollution when using Spaces	Mac OS X	VirtualBox 3.2.10	defect	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
1461	Virtualizing physical partition with createrawvmdk fails on Mac OS X Leopard	Mac OS X	VirtualBox 3.0.4	defect	2008-05-03T20:22:21Z	2014-01-15T14:58:50Z	2014-01-15T14:58:50Z	"On Mac OS X 10.5.2 (Intel iMac Core Duo) with VirtualBox 1.6.0, trying to create a VMDK for disk0s3, running the command

{{{sudo VBoxManage internalcommands createrawvmdk -filename test.vmdk -rawdisk /dev/disk0 -partitions 3 -register}}}

returns:

{{{Error while creating the raw disk VMDK: VERR_INVALID_PARAMETER}}}"	jtbandes
2251	cannot specify disk geometry	Mac OS X	VirtualBox 2.0.2	defect	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
11491	VirtualBox GUI unnecessary dynamic and complex.	Mac OS X	VirtualBox 4.2.6	enhancement	2013-02-14T12:44:17Z	2013-02-14T15:34:29Z	2013-02-14T15:34:29Z	"Please reconsider some of the current VirtualBox GUI aspects and remove dynamic windows, dynamic buttons and ""intelligent"" one time only displaying of information. It adds unnecessary complexity and does not conform to application and interface standards. 

My suggestions: Appropriate settings should be in the VirtualBox application preferences, where the user can customize the options. For instance:

[ ] Show descriptive dialog windows.
[ ] Disable keyboard and mouse capturing info
[ ] Show dialog if no bootable medium found. 
"	Dude
1668	Mac version needs option to pass system keyboard shortcuts through to OS X	Mac OS X	VirtualBox 1.6.2	enhancement	2008-06-05T12:44:08Z	2012-11-28T23:36:14Z	2012-11-28T23:36:14Z	"VMware Fusion has an option to pass Mac system keyboard shortcuts (such as Cmd-Tab and the Spaces/Exposé shortcuts F8-F11) through to OS X.

VirtualBox for Mac really needs this option too.  It's very annoying that you can't switch applications or workspaces when a guest window has focus, even with the guest extensions installed.  This is one of the main issues that's stopping me switching all my VMs over from VMware right now."	Calum Benson
3640	Additional Preference to swap Control (CTRL) and Command (CMD) keys per virtual machine	Mac OS X	VirtualBox 2.1.4	enhancement	2009-04-05T18:18:16Z	2012-10-25T18:23:21Z	2012-10-25T18:23:21Z	Both Parallels and VMWare Fusion have a really useful preference that allows a user to optionally swap the key mappings for CMD and CTRL within a virtual machine.  It would be fantastic if someone could implement this in VirtualBox as it is extremely useful on Mac OS X.  It means you can continue using the same keyboard shortcuts regardless of whether you are in the host or guest operating system, and regardless of guest OS.	Elliot
9972	Connection sharing for host-only networking	Mac OS X	VirtualBox 4.1.6	enhancement	2011-11-29T17:37:22Z	2011-12-09T16:34:25Z	2011-12-09T16:34:25Z	"VBox under OSX offers these networking choices:

* Host-only networking, where the guests can see each other and the host, but cannot reach the Internet

* NAT, where the guest can make outbound connections to the Internet, but is not reachable from other guests or the hosts (except by means of port forwarding)

This means that if you want guests to form a local network but also be able to download updates from the Internet you need to configure them with two NICs, one of each type. Or else you can set up another VM as a gateway running IP masquerading, but to use this you need to set an explicit default gateway on each of the other guests.

It would be very useful if Host-only networking could allow outbound connections via the Host using NAT. For Linux this would probably just require an iptables rule. In the case of OSX, I think the cleanest way to do this would be to expose the vboxnet interfaces in the Internet Sharing settings (System Preferences > Internet and Wireless > Sharing > Internet Sharing). It would also be necessary to return a gateway in the DHCP response (see #9970)
"	Brian Candler
302	wrong path for settings under mac os x	Mac OS X		defect	2007-04-23T17:02:10Z	2011-10-31T08:04:36Z	2011-10-31T08:04:36Z	"First of all thank you for porting it to mac os x! It really rocks with WXP and Ubuntu!

But I've noticed that the wrong path has been taken for the settings. It currently uses ~/Library/VirtualBox. This is neither the right place from Apples point of view. Nor would users look in there for their data.

VirtualBox should use instead ~/Library/Application Support/VirtualBox.

:-)"	wolfie
9815	Mark virtual machines as excluded from backups	Mac OS X	VirtualBox 4.1.4	enhancement	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
9692	OSX: Mini Toolbar is not visible in Full Screen mode	Mac OS X	VirtualBox 4.1.2	defect	2011-10-04T19:05:18Z	2011-10-04T19:07:35Z	2011-10-04T19:07:35Z	"Frequently the mini toolbar is not visible when running in full screen mode.  Occasionally it is, and I have not figured out what makes it sometimes work.

Running OSX 10.6.8."	jayfinger
4703	VBoxManage creterawvmdk on osx only allows first 4 partitions.	Mac OS X	VirtualBox 3.0.4	defect	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
9182	Pause dock menu item on OS X does not work while Virtual Machine is not front	Mac OS X	VirtualBox 4.0.10	defect	2011-07-11T12:59:28Z	2011-07-11T12:59:28Z	2011-07-11T12:59:28Z	"The pause item in the dock menu of a virtual machine on OS X has an effect only while that the virtual machine is the active application, i.e., its window is in front.
Clicking the item has no effect (it will neither pause a running VM nor resume a paused VM) while another application is active."	Wolfgang Lux
8862	launchd recipe for vboxwebsrv doesn't work	Mac OS X	VirtualBox 4.0.6	defect	2011-05-08T20:10:17Z	2011-05-08T20:11:19Z	2011-05-08T20:11:19Z	"The example plist file for vboxwebsrv (on MacOS) declares the Socket on which it will be listening.  That would be awesome for on-demand launching, except that it causes the socket to be held open for listening, and when vboxwebsrv is launched it finds that the address is already in use:

  00:00:01.677 SQPmp    #### SOAP FAULT: Address already in use [SOAP-ENV:Server]

and fails to do its job.  I don't know how you're supposed to deal with this, but anyway...

Furthermore, if you try to use that plist file in /Library/LaunchDaemons, it won't work because vboxwebsrv doesn't work if some other service isn't already available.  I'm not sure which service it depends on, but the launchdaemon can be started later.  Apple doesn't provide any way of expressing this dependency, and suggests instead the two services should use IPC to negotiate things like this :-("	David Abrahams
7763	configure needs to check for glib2	Mac OS X	VirtualBox 3.2.10	defect	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
4238	Option to define shortcuts to be passed to host os	Mac OS X	VirtualBox 2.2.4	enhancement	2009-06-16T15:07:56Z	2010-07-13T19:27:40Z	2010-07-13T19:27:40Z	"I really would like to see an option in the applications ""input"" preferences panel where one can define custom shortcuts (or maybe even special keys) to be passed to the host os instead of the guest. 

I am thinking about something like the mac os x pref pane in ""keyboard & mouse"" where one can define shortcuts. A list could be used to redefine or deactivate all the shortcuts already present for example cmd-q or cmd-h in the mac os x version. One could select from internal functions (reset, pause etc.) or pass the command to the host os. (and maybe even modify it: send cmd-tab to host os.)

This approach would solve annoying bugs like #4208, #2145, #1668 and #1773"	Stephan Müller
4949	Need to be able to re-assign keys for Mac	Mac OS X	VirtualBox 3.0.6	enhancement	2009-09-10T23:49:05Z	2010-01-14T09:12:25Z	2010-01-14T09:12:25Z	"The main modifier key on Mac is the ""Command"" button - not the ""Control"" button which is used on Windows. It would be really useful to be able to map the Command button to Control inside VirtualBox. This is what you can do in Parallels and it's a very handy feature.

Also very useful would be to add support for specific key combinations to be automatically sent to the host without having to press the host key. For example on the Mac Command-Tab is used to switch applications, so it would be really useful for this key combination to always be sent to the host to help with fast switching between VirtualBox and the other applications running on the host.

Many thanks for a fantastic product,

Simon"	Simon Wade
4167	Mac OSX Host: Enable CD/DVD Eject Key in Guest	Mac OS X	VirtualBox 2.2.4	enhancement	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
5555	Mac OS X: Time Machine-friendly storage	Mac OS X		enhancement	2009-11-25T02:26:45Z	2009-11-25T02:26:45Z	2009-11-25T02:26:45Z	If you use VirtualBox and don't tell Time Machine to ignore your hard disks, you'll soon end up copying the entire image to the Time Machine server or disk every time you run the VM. Storing these hard disks in a sparse bundle would allow the OS to copy only the changes to the VMs' hard disks at update time.	Jeff Kelley
3163	Can't create snapshots when ~/Library/VirtualBox is a symlink	Mac OS X	VirtualBox 2.1.2	defect	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
5428	Mac OS X: Deleting Virtual Hard Disks Should Move to Trash	Mac OS X		enhancement	2009-11-09T03:43:29Z	2009-11-09T03:43:29Z	2009-11-09T03:43:29Z	"It would be nice if, when removing a virtual hard disk from the Virtual Media Manager, deleting the hard disk would move it to the Trash under Mac OS X. This would, among other things, allow the operating system to securely erase the disks if the user has opted to do that. More information may be found in [http://developer.apple.com/mac/library/documentation/Cocoa/Conceptual/LowLevelFileMgmt/Articles/FileManagement.html Apple's File Management documentation]. If this is implemented, the dialog box should change the word ""Delete"" to ""Move to Trash"" to indicate to the user what is occurring."	Jeff Kelley
4828	Usability issue when deleting multiple hard disks using Virtual Media Manager	Mac OS X	VirtualBox 3.0.4	defect	2009-08-21T17:05:37Z	2009-08-21T17:05:37Z	2009-08-21T17:05:37Z	Documented completely at http://blogs.sun.com/gridbag/entry/are_you_sure_are_you	Rohan Ranade
4661	VirtualBox creates folder in /Volumes/ directory when disk with virtual machines is not present	Mac OS X	VirtualBox 3.0.2	defect	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
18018	'About' box text is unreadable	Linux	VirtualBox 5.2.18	defect	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
21477	Custom VM icons don't show up in Ubuntu Dock with VirtualBox 7	Linux	VirtualBox-7.0.6	defect	2023-02-08T22:05:46Z	2023-02-08T22:05:46Z	2023-02-08T22:05:46Z	"In Virtualbox 6, I modified the iconfile for each vm, and that icon would show up in the Ubuntu dock. 

On upgrading to 7, the custom icons are still shown inside the VBox Manager GUI, but I just get the default icon in the OS dock bar.

Desired capability shown here: https://twitter.com/0xdf_/status/1529429480858697728

Host OS is Ubuntu 22.04."	dfors
21452	Please add require for kernel headers in Fedora rpm packages	Linux	VirtualBox-7.0.6	enhancement	2023-02-01T03:03:22Z	2023-02-01T03:03:22Z	2023-02-01T03:03:22Z	"A long time annoying missing thing is that Fedora rpms does not by itself fetch the required kernel headers,
and therefore won't work until user figures out whats missing.

YES - I am aware that Fedora have HAD a problem with fetching the wrong version - and that's most likely why you don't do it ....... but this is FIXED now.

Fedora now has a new package in all repos, that should fix this problem - it is called kernel-devel-matched

coming with this description:
This meta package is used to install matching core and devel packages for a given kernel.

Please add ""Requires: kernel-devel-matched"" for new releases, to finally fix this annoyance 
"	Yoda
21419	"Error ""kmk: glslangValidator: Command not found""while building VirtualBox"	Linux	VirtualBox-7.0.6	defect	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
21266	good day. The guest additions CD does not work. I think the CD drive is not working.	Linux	VirtualBox-7.0.2	defect	2022-11-11T23:19:44Z	2023-01-18T15:29:07Z	2023-01-18T15:29:07Z	I tried several things but the cd player does not work, what would be the solution.	yuvlower.hacsshikkennvyu@…
21351	GetFileInformationByHandleExfor VBoxSharedFolderFS  works incorrectly	Linux	VirtualBox-7.0.4	defect	2022-12-21T13:12:21Z	2023-01-04T12:13:46Z	2023-01-04T12:13:46Z	"it returns ERROR_FILE_NOT_FOUND, while there are files in a directory

details:


https://github.com/boostorg/filesystem/issues/261#issuecomment-1335574338"	basiliscos
17721	Vbox crashes under heavy disk IO	Linux	VirtualBox 5.2.10	defect	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
21169	Deprecation of libIDL on Linux	Linux	VirtualBox 7.0.0	enhancement	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
21193	Update build instruction page	Linux	VirtualBox-7.0.2	enhancement	2022-10-22T17:26:27Z	2022-10-22T17:26:27Z	2022-10-22T17:26:27Z	"The wiki page (https://www.virtualbox.org/wiki/Linux%20build%20instructions) containing the build instruction seems to be a bit out of date.

The instructions for a Linux host are missing at least 
the reference to `glslang`, `liblzf` and maybe others.
gcc-3.3.3 might still work, but nowadays, `gcc-12.2.0` is recent.
What about Java versions beyond JDK6, how to use newer JDKs (9, 11, 17 or even newer) than JDK8?
"	Moody
20873	HDAT2 crashes under SysLinux 6.04 in VirtualBox 6.1.32 r149290 (Qt5.15.2)	Linux	VirtualBox 6.1.32	defect	2022-03-17T15:59:04Z	2022-10-22T11:20:35Z	2022-10-22T11:20:35Z	"Steps to reproduce:

* Create a HDD with the Syslinux 6.04 bootloader and add HDAT2 (HDAT2IMG_74.IMG from www.hdat2.com) to the menu
* Start it.

Result: VBox crashes.

NB: This crash does not happen when using the floppy image directly mounted as a floppy"	Artem S. Tashkinov
19595	memtest86 8.3 freezes	Linux	VirtualBox 6.1.8	defect	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
20600	Fedora 35 compatibility / udev rules errors	Linux	VirtualBox 6.1.26	defect	2021-10-09T22:50:29Z	2022-10-21T12:53:24Z	2022-10-21T12:53:24Z	"There are some error messages which I guess should be fixed:


{{{
vboxdrv: /etc/udev/rules.d/60-vboxdrv.rules:1 Only network interfaces can be renamed, ignoring NAME=""vboxdrv"".
vboxdrvu: /etc/udev/rules.d/60-vboxdrv.rules:2 Only network interfaces can be renamed, ignoring NAME=""vboxdrvu"".
VBoxNetFlt: Successfully started.
VBoxNetAdp: Successfully started.
vboxnetctl: /etc/udev/rules.d/60-vboxdrv.rules:3 Only network interfaces can be renamed, ignoring NAME=""vboxnetctl"".
}}}

I'm using VirtualBox-6.1-6.1.26_145957_fedora33-1.x86_64.rpm"	Artem S. Tashkinov
21148	VBoxManage: error: Invalid command 'hostonlynet'	Linux	VirtualBox 7.0.0	defect	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
21115	freeze gnome gui ubuntu	Linux	VirtualBox 6.1.38	defect	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
20997	Scancode returned by int15h call in BIOS keyboard handler(int09h) is ignored.	Linux	VirtualBox 5.2.34	defect	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
20994	PXE UNDI driver transmit seems to be mapping existing transmit buffer instead of making a copy	Linux	VirtualBox 6.1.34	defect	2022-06-19T04:07:03Z	2022-06-19T04:07:03Z	2022-06-19T04:07:03Z	"To be fair, haven't dug that far into VirtualBox code (don't really use SVN, and don't have an easy web interface to search the code for what I'm looking for) but, the most recent code I could find on GitHub for VBox seems to suggest it's mapping the supplied transmit buffer and not copying it before return: https://github.com/TedHartDavis/VBoxMirror/blob/3d7f37ab5b248566e1dc17df8ee495628bb007e5/src/VBox/Devices/EFI/FirmwareNew/OptionRomPkg/UndiRuntimeDxe/Decode.c#L1214, https://github.com/TedHartDavis/VBoxMirror/blob/3d7f37ab5b248566e1dc17df8ee495628bb007e5/src/VBox/Devices/EFI/Firmware/OptionRomPkg/UndiRuntimeDxe/E100b.c#L1100

Given that, I'm currently the following behavior running GRUB in VirtualBox and it sending DNS:

1. GRUB (2.06) allocates a single, fixed scratch-space buffer for sending packets via PXE UNDI; this buffer is reused for every packet send. (See https://github.com/rhboot/grub2/blob/ef36b3c93d27bdfc7a68469be33bd8be95630e6a/grub-core/net/drivers/i386/pc/pxe.c#L259)
2. When running in VirtualBox, I can get GRUB to send DNS requests manually with the net_nslookup command.
3. When GRUB is in prefer-ipv4 mode (default), it tries to send one A DNS request followed by an IPv6 AAAA request.
4. Looking in Wireshark, I can see it just sending two AAAA requests instead (seems like the AAAA query contents are somehow clobbering the A query), separated by about 0.2ms.
5. When I set debug=dns in GRUB, the delay of debug-print-to-console seems to introduce enough delay that I see separate A and AAAA requests in Wireshark (now separated by about 1ms).

The best explanation I have for these observations is that VirtualBox's UNDI/PXE implementation is not mixing well with GRUB's extreme transmit buffer reuse, and causing a sufficiently quick sequence of transmits to clobber previous packets' contents.

I'm not that familiar with PXE or UNDI API requirements, but it seems like the driver should not return without at least making a copy of the data buffer, even if it doesn't transmit the packet immediately? In any case, would hope someone can take a look at the spec and determine whether this is actually a bug on VirtualBox's side or GRUB's.

Thanks in advance!"	henryptung
15043	VMSetError for ACPI tables < 64k	Linux	VirtualBox 5.0.12	defect	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
19043	XWayland breaks mouse behavior on Linux/Wayland Hosts	Linux	VirtualBox 6.0.14	defect	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
20775	Mouse click doesn't work in window for choice iso	Linux	VirtualBox 6.1.32	defect	2022-01-19T09:18:22Z	2022-04-22T10:23:49Z	2022-04-22T10:23:49Z	"My OS is Debian 11 with KDE Plasma
When I try to select iso in virtual machine settings, mouse left button click doesn't work. But the keyboard in this dialog works"	blbulyandavbulyan
20812	VirtualBox GUI doesn't work well with dark themes	Linux	VirtualBox 6.1.32	defect	2022-02-05T17:32:23Z	2022-02-05T17:32:23Z	2022-02-05T17:32:23Z	VirtualBox GUI doesn't work well with dark themes. Some parts of the GUI are dark and some are light, but the worst are light fonts on light background. Please see attachment.	XorOrNor
20625	After hardware upgrade OS/2 does not boot	Linux	VirtualBox 6.1.26	defect	2021-10-22T05:44:13Z	2022-01-25T14:25:45Z	2022-01-25T14:25:45Z	"opensuse tumbleweed 20211012
linux v5.14.9-1-default x86_64
VBox v6.1.26_SUSE r145957

After an hardware upgrade the OS/2 guest has stopped booting. The boot proceeds normally to a point, then simply stops.

Old CPU: AMD Athlon II 4x
New CPU: AMD Ryzen 5 5600x

Mainboard
Old: asus m5a88-m
New: asus tuf gaming b550+
"	James Moe
20785	VM will not start, Guru Meditation -79 (VERR_INVALID_STATE)	Linux	VirtualBox 6.1.22	defect	2022-01-20T21:10:17Z	2022-01-21T20:55:33Z	2022-01-21T20:55:33Z	"Virtual machines will not start any more.
Both Windows and Ubuntu guests seem to be having the same project.
I am using VirtualBox 6.1.22_Ubuntu r144080 and I am running Ubuntu 20.04
Linux 5.13.0-27-lowlatency #29~20.04.1-Ubuntu SMP PREEMPT

Yesterday everything works fine and now machines wont start.
When exporting and importing a machine to a different host, the machine does start so it seems the issue is related to the virtual box host.

In the logfile I see:

00:00:04.713444 Display::handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0 flags=0x0
00:00:04.713532 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=720x400, Sending to async-handler
00:00:04.713611 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=720x400
00:00:04.713634 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=720x400
00:00:04.713659 GUI: UIFrameBufferPrivate::performResize: Size=720x400, Directly using source bitmap content
00:00:10.049433 PIT: mode=3 count=0x4dae (19886) - 60.00 Hz (ch=0)
00:00:10.069842 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'
00:00:10.069860 Console: Machine state changed to 'GuruMeditation'
00:00:10.070003 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:00:10.070003 !!
00:00:10.070004 !!         VCPU0: Guru Meditation -1701 (VERR_MM_HYPER_NO_MEMORY)
00:00:10.070037 !!
00:00:10.070063 !!
00:00:10.070063 !! {mappings, <NULL>}
00:00:10.070064 !!


I will attach the logfile to this ticket.

Any help is highly appreciated"	DeHouthakker
20764	Linux host seamless mode with windows 10 guest often don't display anything	Linux	VirtualBox 6.1.30	defect	2022-01-08T21:02:10Z	2022-01-08T21:02:10Z	2022-01-08T21:02:10Z	"I installed windows 10 as a guest and run a few apps using seamless-mode but it won't work quite often (no error or anything.. it just doesn't display anything of the vm in seamless when it doesn't work).
I think the issue first appears after restoring from a snapshot (save machine state) instead of rebooting, but a reboot doesn't fix it.
after some time (a few reboots of host and guest it ""randomly"" works again but I can reproduce it very often..).

I already tried all Display / Graphics settings on the vm.

the issue happens on both KDE and XFCE.
I currently use the version from the ubuntu repos:
6.1.26
but I also tried with 6.1.30 and the same issue occurs."	test111
20728	VirtualBox Manager UI elements flicker with compositing disabled	Linux	VirtualBox 6.1.30	defect	2021-12-14T23:26:06Z	2021-12-14T23:26:06Z	2021-12-14T23:26:06Z	"Since upgrading to 6.1.30, the manager UI (not the guest window) seems to flicker/lag when interacting with certain UI elements. Enabling compositing in xfwm4 fixes the issue.

System details:

{{{
user@host:~$ vboxmanage --version
6.1.30r148432
user@host:~$ cat /etc/*release
PRETTY_NAME=""Debian GNU/Linux bookworm/sid""
NAME=""Debian GNU/Linux""
ID=debian
HOME_URL=""https://www.debian.org/""
SUPPORT_URL=""https://www.debian.org/support""
BUG_REPORT_URL=""https://bugs.debian.org/""
user@host:~$ uname -a
Linux host 5.14.0-2-amd64 #1 SMP Debian 5.14.9-2 (2021-10-03) x86_64 GNU/Linux
user@host:~$ lspci -k | grep -A3 VGA
00:02.0 VGA compatible controller: Intel Corporation CometLake-U GT2 [UHD Graphics] (rev 02)
	Subsystem: Lenovo UHD Graphics
	Kernel driver in use: i915
	Kernel modules: i915
user@host:~$ xfwm4 --version
	This is xfwm4 version 4.16.1 (revision 5f61a84ad) for Xfce 4.16
	Released under the terms of the GNU General Public License.
	Compiled against GTK+-3.24.24, using GTK+-3.24.30.

	Build configuration and supported features:
	- Startup notification support:                 Yes
	- XSync support:                                Yes
	- Render support:                               Yes
	- Xrandr support:                               Yes
	- Xpresent support:                             Yes
	- X Input 2 support:                            No
	- Embedded compositor:                          Yes
	- Epoxy support:                                Yes
	- KDE systray proxy (deprecated):               No
user@host:~$ xfconf-query -c xfwm4 -p /general/use_compositing
false
user@host:~$ sudo X -version
[sudo] password for user: 

X.Org X Server 1.20.11
X Protocol Version 11, Revision 0
Build Operating System: linux Debian
Current Operating System: Linux host 5.14.0-2-amd64 #1 SMP Debian 5.14.9-2 (2021-10-03) x86_64
Kernel command line: BOOT_IMAGE=/vmlinuz-5.14.0-2-amd64 root=/dev/mapper/host--vg-root ro quiet
Build Date: 13 April 2021  04:07:31PM
xorg-server 2:1.20.11-1 (https://www.debian.org/support) 
Current version of pixman: 0.40.0
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
user@host:~$ 
}}}

Video of issue attached. (Apologies for phone camera video. Recording the window with `ffmpeg -f x11grab ...` makes the issue disappear.)

Same issue on latest v6.1.31 test build."	adsr
20498	PATH_SDK_QT5_INC auto-detects to .../QtGui	Linux	VirtualBox 6.1.26	defect	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
20622	Python wrapper of VirtualBox API under Debian Bullseye doesn't work	Linux	VirtualBox 6.1.26	defect	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
20605	3D opengl with vulcan nvidia	Linux	VirtualBox 6.1.26	task	2021-10-13T18:27:19Z	2021-10-13T18:27:19Z	2021-10-13T18:27:19Z	"Hello[[BR]]

[[BR]]
[[BR]]

Would it be possible to implement in future version VirtualBox the functions[[BR]]

3d acceleration NVIDIA vulkan technology?[[BR]] Opengl 3.0 or more....[[BR]]


like do software vmware player and vmware workstation .[[BR]]

Thank.[[BR]]
"	Sizy458
20549	installing virtual box on Linux  5.10.0-kali9-amd64	Linux	VirtualBox 6.1.26	defect	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
20485	CentOS 7, VirtualBox 6.1: compiler_types.h:214:24: error: expected ‘(’ before ‘__inline’	Linux	VirtualBox 6.1.26	defect	2021-08-02T14:37:07Z	2021-08-10T10:57:17Z	2021-08-10T10:57:17Z	"CentOS 7, kernel 5.4.137-1.el7.elrepo.x86_64, Virtual Box 6.1

I try to start Virtual machine on Virtual Box 6.1.

''/sbin/vboxconfig''


but I get error:

''vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: failed: Look at /var/log/vbox-setup.log to find out what went wrong.

There were problems setting up VirtualBox. To re-start the set-up process, run
/sbin/vboxconfig
as root. If your system is using EFI Secure Boot you may need to sign the
kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load
them. Please see your Linux system's documentation for more information.''

Here error in file var/log/vbox-setup.log

''In file included from <command-line>:0:0:
./arch/x86/include/asm/page_64.h: In function ‘clear_page’:
././include/linux/compiler_types.h:214:24: error: expected ‘(’ before ‘__inline’
 #define asm_inline asm __inline
                        ^
./arch/x86/include/asm/alternative.h:256:2: note: in expansion of macro ‘asm_inline’
  asm_inline volatile (ALTERNATIVE_2(""call %P[old]"", ""call %P[new1]"", feature1,\
  ^
./arch/x86/include/asm/page_64.h:49:2: note: in expansion of macro ‘alternative_call_2’
  alternative_call_2(clear_page_orig,''


P.S.

''
gcc --version

gcc (GCC) 8.3.1 20190311 (Red Hat 8.3.1-3)''
"	a_subscriber
20252	[SVN version] compile error under python 3.9: _Py_NewReference was not declared in this scopt	Linux		defect	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
20377	Can not select extension file for install in host	Linux	VirtualBox 6.1.22	defect	2021-05-24T19:37:00Z	2021-07-21T18:51:46Z	2021-07-21T18:51:46Z	"In Fedora 33/34 is not possible to select the extension file in the GUI manager...mouse click does not select anything and it is only possible to close the file window by closing the window from OS/desktop.

Desktop is KDE
Vbox is  6.1.22"	Knud
20441	Kernel module compilation error - VirtualBox 6.1.22 kernel 5.12.13	Linux	VirtualBox 6.1.22	defect	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
20363	building kernel modules on a multiarch host fails	Linux	VirtualBox 6.1.22	defect	2021-05-13T15:17:30Z	2021-05-13T15:17:30Z	2021-05-13T15:17:30Z	"In the Makefile-header.gmk of the three actual kernel modules, the BUILD_TARGET_ARCH_DEF variable, that reflect in BUILD_TARGET_ARCH, the actually used one, is set by the shell command 
$(shell dpkg-architecture -qDEB_HOST_GNU_CPU)
But on a multiarch environment is perfectly sane having a 32 bit version of dpkg-architecture, even if running a 64 bit kernel or building for a 64 bit kernel installed but not running at the moment of building.
In such a case, the build fails because BUILD_TARGET_ARCH is set to i686.
Maybe it's a bug in dpkg, but please consider using a different method to find the target kernel architecture.
Regards
Claudio"	Claudio Laurita
19104	Ubuntu18.04 NS_ERROR_FAILURE	Linux	VirtualBox 6.0.14	defect	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
20322	Bug from Red Hat Bugtracker	Linux	VirtualBox 6.1.20	defect	2021-04-24T07:40:16Z	2021-04-26T20:37:48Z	2021-04-26T20:37:48Z	"https://bugzilla.redhat.com/show_bug.cgi?id=1952869 

Having some wierd bug with a Fedora VM on an Ubuntu host "	bittin-
20253	file system damage on flashUSB	Linux	VirtualBox 6.1.18	defect	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
20246	vboxmanage modifymedium lock not released immediately	Linux	VirtualBox 6.1.18	defect	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
20240	Host Freeze Ubuntu 20.04	Linux	VirtualBox 6.1.16	defect	2021-03-08T09:47:09Z	2021-03-08T09:47:09Z	2021-03-08T09:47:09Z	"Sometimes i got a freeze of the Host (Ubuntu 20.04.1) after several guest are up. (kernel panic)

Host: Linux 5.8.0-44
Guests are all RHEL 7.8"	Chris81
20230	Windows 10 guest crashed when trying to paste image to guest	Linux	VirtualBox 6.1.18	defect	2021-03-02T03:52:03Z	2021-03-02T03:58:24Z	2021-03-02T03:58:24Z	"When trying to paste image from Windows 10 guest to Linux host, the guest crashed.

I'm running linux test build version 6.1.19 r142946 (Qt5.6.1)

Steps before the crash:

1. Guest: Select and copy an image from the Windows Draw application
2. Host: In GIMP, select menu File -> New -> From clipboard
3. The guest crashed

Attached is the crash dump"	cooldog
20225	Voice synthesis software rhvoice doesn't work in VirtualBox	Linux	VirtualBox 6.1.18	defect	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
20106	AC97 possible regression in rev 76862	Linux	VirtualBox 6.1.16	defect	2020-12-29T10:56:52Z	2021-01-25T12:25:45Z	2021-01-25T12:25:45Z	"I'm investigating why ac97 driver (https://github.com/deadw00d/AROS/tree/alt-abiv0/workbench/devs/AHI/Drivers/ac97) that we created stopped working with VBox. The driver continues working with real hardware and QEMU. After debugging and analysing VBox code I think a regression was introduced in rev 76862 by deleting the ichac97R3StreamFetchBDLE(pThis, pStream); call when setting up LVI register.

What happens now is that CIV register is advanced, but the PICB register is not refreshed (refresh is done ichac97R3StreamFetchBDLE(pThis, pStream)). What then happens is when ichac97R3StreamTransfer() is called, the cbLeft is zero so the whole logic of this function is skipped. The ""hardware"" hangs in mode where DMA is saying its active, Bus Master is enabled but nothing is tranfered. The only way to kick the ""hardware"" again is to set the CR register where the code again advanced the CIV but then calls ichac97R3StreamFetchBDLE() to update PICB. This way however a previous buffer is lost.

There are two places I see possible to change:
- restore the call to ichac97R3StreamFetchBDLE when setting LVI and advancing CIV
- allow ichac97R3StreamTransfer to operate with *initial* empty PICB just like the code in the look (when it sees empty PICB it continues to next buffer)"	deadwood
20078	Trend FDE Post Login Fault	Linux	VirtualBox 6.1.16	defect	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
20017	VB installation failing in linux kernel drivers installation	Linux	VirtualBox 6.1.16	defect	2020-11-04T18:13:31Z	2020-11-06T08:08:19Z	2020-11-06T08:08:19Z	"Host is a Debian 10.
Kernel is 5.9.3.

Compilation of modules located in /usr/src/vboxhost-6.1.16 fail during the install stage.
It is the vboxpci driver.

I checked its content and it seems there has been some cleaning there (all Makefile*) files, etc.

I have managed to bypass that failure to install and all other drivers get installed
(I just renamed the vboxpci to vboxpci.del in order to be bypassed).

I can run VirtualBox but then (my guess is that) VT-d, for the guest machines, cannot be enabled.


Regards,
Josep"	jepjepus
19957	Virtualbox can't co-exist with python3 on Ubuntu 20.10 (even though python2 is also installed)	Linux	VirtualBox 6.1.14	defect	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
19984	PulseAudio not working on Fedora 33	Linux		defect	2020-10-20T18:53:34Z	2020-10-25T21:57:40Z	2020-10-25T21:57:40Z	"Hi there,
I've been using VirtualBox version 6.1.97 r140489 and r140902 (Q.t 5.6.1) which I compiled myself.
What I noticed is that if I pick PulseAudio on the host, both Windows 10 Enterprise x64 and Windows XP Professional x86 are completely silent and on playback, they fail, with players not showing any kind of progress.
If I choose ALSA, however, audio works, but the guest cannot receive any input from the microphone of the host.
I also tried to make a brand new virtual machine with Win10 and it didn't change, I was able to reproduce the error.
The host is Fedora 33 x64, kernel 5.8.15.
I just wanted to let you know so that you can get it fixed before releasing a new stable version.

By looking at the logs https://pastebin.com/dwYh7C6i it seems that the problem lies here:

00:00:01.525860 PulseAudio: Using v13.99.0

00:00:01.527615 PulseAudio: Retrieving server information ...

but then it gets stuck on ""Retrieving server information""

00:01:39.235641 PulseAudio: Retrieving server information ...

00:01:39.243184 PulseAudio: Retrieving server information ...

00:01:39.246628 PulseAudio: Retrieving server information ...

00:01:39.254586 PulseAudio: Retrieving server information ...

00:01:39.257787 PulseAudio: Retrieving server information ...

00:01:39.269556 PulseAudio: Retrieving server information ...

00:01:39.282748 PulseAudio: Retrieving server information ...

00:01:39.291351 PulseAudio: Retrieving server information ...

00:01:39.300245 PulseAudio: Retrieving server information ...

00:01:39.304005 PulseAudio: Retrieving server information ...

00:01:39.306203 PulseAudio: Retrieving server information ...

00:01:39.308411 PulseAudio: Retrieving server information ...

00:01:39.311230 PulseAudio: Retrieving server information ...

00:01:39.323857 PulseAudio: Retrieving server information ...

00:01:39.337777 PulseAudio: Retrieving server information ...

00:01:39.346414 PulseAudio: Retrieving server information ...

00:01:39.356345 PulseAudio: Retrieving server information ...

00:01:39.360085 PulseAudio: Retrieving server information ...

00:01:39.362385 PulseAudio: Retrieving server information ...

00:01:39.365149 PulseAudio: Retrieving server information ...

00:01:39.368284 PulseAudio: Retrieving server information ...

00:01:39.381721 PulseAudio: Retrieving server information ...

00:01:39.396202 PulseAudio: Retrieving server information ...

00:01:39.408159 PulseAudio: Retrieving server information ...

00:01:39.417439 PulseAudio: Retrieving server information ...

00:01:39.421454 PulseAudio: Retrieving server information ...

00:01:39.424015 PulseAudio: Retrieving server information ...

00:01:39.427194 PulseAudio: Retrieving server information ...

You can see the full logs in the pastebin if you're interested, though.

Cheers,
Frank."	FranceBB
18583	building virtualbox without opengl on server without X11	Linux	VirtualBox 6.0.6	defect	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
19905	"GUI glitches on Wayland running ""sudo virtualbox"""	Linux	VirtualBox 6.1.14	defect	2020-09-20T23:09:18Z	2020-09-21T20:12:14Z	2020-09-21T20:12:14Z	"Buttons and virtual machine names highlight is not working normally when hovering with a mouse and virtual machine window is only partially updated. 

The bug appear on recent GNOME on Wayland running ""sudo virtualbox"".
I've reproduced the bug on Ubuntu 20.04 and Fedora 32. There was no such glitches on earlier GNOME versions from Fedora 31 and there is no such glitches on Xorg, only Wayland and recent GNOME.

VirtualBox is required to run from a privileged user to access physical hard drives (as documented in VB manual chapter 9)."	GnomeUser
19850	Error Cloudera Virtual Box	Linux	VirtualBox 6.1.10	defect	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
19727	Cannot connect to OCI Cloud: VERR_CR_KEY_UNSUPPORTED_CIPHER	Linux	VirtualBox 6.1.10	defect	2020-07-16T07:23:18Z	2020-07-16T07:23:18Z	2020-07-16T07:23:18Z	"VirtualBox running on CentOS Linux release 7.8.2003 (Core)
- Linux 3.10.0-1127.13.1.el7.x86_64

has problem opening the Key from profile because of unsupported cipher
(Works in Windows, exact same profile)

VBoxManage cloud --provider=OCI --profile=oci list instances
Parameter 'compartment' is empty or absent.
Trying to get the compartment from the passed cloud profile 'oci'
Found the compartment 'ocid1.compartment.oc1..xxxxxxxxxxxxxxxxxxxxx':
Reply is in the form 'instance name' = 'instance id'
0%...
Progress state: VBOX_E_IPRT_ERROR
VBoxManage: error: Failed to list instances
VBoxManage: error: Failed to read signing key from ""~/.oci/oci_api_key.pem"": VERR_CR_KEY_UNSUPPORTED_CIPHER
VBoxManage: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005), component CloudClientWrap, interface ICloudClient
VBoxManage: error: Context: ""RTEXITCODE listCloudInstances(HandlerArg*, int, PCLOUDCOMMONOPT)"" at line 229 of file VBoxManageCloud.cpp"	SpongeTort
19718	Failed to start VirtualBox hub service	Linux	VirtualBox 6.1.10	defect	2020-07-14T18:54:01Z	2020-07-15T06:54:19Z	2020-07-15T06:54:19Z	"I'm using VirtualBox 6.1.10_Ubuntu r138449 on Linux Mint MATE 19.3.
When starting Linux, I've got this error message : ""Failed to start VirtualBox hub service"".

I've got another message error when I type this command line :
$sudo dpkg-reconfigure virtualbox
See https://github.com/linuxmint/mintsystem/issues/121"	InfoLibre
19688	Linux 5.7.x + VBox 6.1.10 driver install failure	Linux	VirtualBox 6.1.10	defect	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
19687	Kali problem	Linux	VirtualBox 6.1.10	defect	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
19637	QT 5.15 breaks VirtualBox (6.1.8)	Linux	VirtualBox 6.1.8	defect	2020-06-03T15:05:50Z	2020-06-03T15:12:46Z	2020-06-03T15:12:46Z	"Some Qt header files have changed in 5.15 and on my Gentoo box I am no longer able to compile VirtualBox (tested only with 6.1.8, others might break also). The issue is a complaint about QPâinterPath. E.g.:


{{{
kBuild: Compiling UICommon - /tmp/VirtualBox-6.1.8/src/VBox/Frontends/VirtualBox/src/globals/UIImageTools.cpp
/tmp/VirtualBox-6.1.8/src/VBox/Frontends/VirtualBox/src/globals/UIImageTools.cpp: In function ‘QImage betaLabelImage(const QSize&)’:
/tmp/VirtualBox-6.1.8/src/VBox/Frontends/VirtualBox/src/globals/UIImageTools.cpp:225:18: error: aggregate ‘QPainterPath tp’ has incomplete type and cannot be defined
  225 |     QPainterPath tp;
      |                  ^~
/tmp/VirtualBox-6.1.8/src/VBox/Frontends/VirtualBox/src/globals/UIImageTools.cpp:231:5: error: ‘QPainterPathStroker’ was not declared in this scope; did you mean ‘QPainterPath’?
  231 |     QPainterPathStroker pps;
      |     ^~~~~~~~~~~~~~~~~~~
      |     QPainterPath
/tmp/VirtualBox-6.1.8/src/VBox/Frontends/VirtualBox/src/globals/UIImageTools.cpp:232:18: error: variable ‘QPainterPath pp’ has initializer but incomplete type
  232 |     QPainterPath pp = pps.createStroke(tp);
      |                  ^~
/tmp/VirtualBox-6.1.8/src/VBox/Frontends/VirtualBox/src/globals/UIImageTools.cpp:232:23: error: ‘pps’ was not declared in this scope
  232 |     QPainterPath pp = pps.createStroke(tp);
      |                       ^~~
kmk: *** [/tmp/VirtualBox-6.1.8/kBuild/footer-pass2-compiling-targets.kmk:277: /tmp/VirtualBox-6.1.8/out/linux.amd64/release/obj/UICommon/src/globals/UIImageTools.o] Error 1
kmk: *** Waiting for unfinished jobs....

}}}
"	sqrt
19621	vboxwebsrv is not connected to port 18083	Linux	VirtualBox 6.1.8	defect	2020-05-25T15:32:22Z	2020-05-25T15:32:22Z	2020-05-25T15:32:22Z	"in version 6.1.4 no problems
in version 6.1.6 & 6.1.8 
ss -lntu | grep 18083  no response
ps aux | grep 18083    no response

running Head-Less-Server with Leap 15.1 and
5.5.0-1.g3f183bf-default #1 SMP Mon Jan 27 08:34:09 UTC 2020 (3f183bf) x86_64 x86_64 x86_64 GNU/Linux

Let me know if you need additional infos
hgf_m "	hgf_m
19489	UI garbled when run through SSH	Linux	VirtualBox 6.1.4	defect	2020-04-14T18:01:53Z	2020-04-14T18:01:53Z	2020-04-14T18:01:53Z	"When using SSH to log into a machine to run VirtualBox, the UI is garbled. Version 6.0.18 works correctly. To duplicate, run 'ssh -X localhost', log in, and run VirtualBox.

Attached are screen shots. "	Larry998
19445	Clipboard broken	Linux	VirtualBox 6.1.4	defect	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
19387	Install of VirtualBox 6.1.4 crashes Sudoers on Ubuntu 18.4.4	Linux	VirtualBox 6.1.4	defect	2020-03-09T01:29:27Z	2020-03-09T06:39:53Z	2020-03-09T06:39:53Z	When I install VirtualBox 6.1.4 on Ubuntu 18.04.4 the sudoers complex of files is corrupted somehow and the owner of the system can no longer use the sudo command to run as administrator. One example of this is trying to install VirtualBox extensions after installing VirtualBox which always fails on authentication. This behavior survives a reboot.	jgossage
17612	Unable to create RAWDISK vmdk which includes extended partition	Linux	VirtualBox 5.2.8	defect	2018-03-10T13:09:40Z	2020-03-04T10:10:45Z	2020-03-04T10:10:45Z	"System is dual boot between Windows 7 Professional and Debian 9. 
The bare-metal Windows 7 system is installed on a 256GB SSD which has the 
system reserved partition, Windows system partition and two data partitions, one of which is a logical partition. 

Debian has VirtualBox 5.2.8 installed and a separate instance of Windows 7 is installed within a virtual machine which requires RAW DISK access to the two data partitions mentioned above. 

Issuing parted from Debian shows the following (correct) partition structure for the drive,


{{{
Disk /dev/sdb: 256GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type      File system  Flags
 1      1049kB  106MB   105MB   primary   ntfs         boot
 2      107MB   41.3GB  41.2GB  primary   ntfs
 3      41.3GB  68.1GB  26.8GB  primary   ntfs
 4      68.1GB  256GB   188GB   extended               lba
 5      68.2GB  256GB   188GB   logical   ntfs 
}}}
 

Issuing the VBoxManage listpartitons -rawdisk command does not give the same results, as shown below.


{{{
VBoxManage internalcommands listpartitions -rawdisk /dev/sdb
Number  Type   StartCHS       EndCHS      Size (MiB)  Start (Sect)
1       0x07  0   /32 /33  12  /223/19           100         2048
2       0x07  13  /0  /52  1022/254/63         39290       208896
3       0x07  1022/254/63  1022/254/63         25600     80674816 

}}}

It does not appear to have recognised the extended/logical partition 
structure and has also calculated partition 3 as the size of the whole drive.

Attempts to create a RAW DISK vmdk just referencing relative partitions 3 and 5 give the following warning message :


{{{
VBoxManage internalcommands createrawvmdk -filename ""/disk/VM System/Raw Disks/Windows Data.vmdk"" -rawdisk ""/dev/sdb"" -partitions 3,5 -relative
VBoxManage: warning: It is not possible (and necessary) to explicitly give access to the extended partition 5. If required, enable access to all logical partitions inside this extended partition.
RAW host disk access VMDK file /disk/VM System/Raw Disks/Windows Data.vmdk created successfully. 

}}}

Whilst the VMDK is created it does not map the logical partition correctly. When seen from within the Windows 7 guest, the 175GB logical partition shows up as free space."	Feline
19344	VirtualBox 6.1.14 install fails on RedHat family	Linux	VirtualBox 6.1.4	defect	2020-02-24T11:29:57Z	2020-02-29T07:46:02Z	2020-02-29T07:46:02Z	"Can not install VirtualBox using the repository:

{{{
# cat /etc/yum.repos.d/virtualbox.repo
[virtualbox]
name=Yum Repository
baseurl=http://download.virtualbox.org/virtualbox/rpm/fedora/$releasever/$basearch
enabled=1
fastestmirror_enabled=0
gpgcheck=1
gpgkey=https://www.virtualbox.org/download/oracle_vbox.asc

#  dnf install -y VirtualBox-6.1
[...]
Error: Transaction test error:
  file /usr/bin/VBox conflicts between attempted installs of VirtualBox-6.1-6.1.4_136177_fedora31-1.x86_64 and VirtualBox-5.2-5.2.38_136252_fedora29-1.x86_64
[...]
}}}

The same problem appears with several distros (Fedora 30, Fedora 29, CentOS 7.7) and with several versions of the package (VirtualBox-6.1-6.1.4, VirtualBox-6.1-6.1.2, VirtualBox-6.0-6.0.18)

Looks like VirtualBox-5.2 is attempted to be installed alongside VirtualBox-6.x, as a dependency, and both packages clashes.

Seems very similar to issue #18924"	luisg.muniz
19325	6.1.4_136177_fedora31-1 : Checksum mismatch	Linux	VirtualBox 6.1.2	defect	2020-02-20T10:22:35Z	2020-02-20T11:37:48Z	2020-02-20T11:37:48Z	"When updating Virtualbox by Fedora dnf tool, following message appears:

{{{
# LANG=C  dnf update
Fedora 31 - x86_64 - VirtualBox                                                                     1.2 kB/s | 181  B     00:00    
Dependencies resolved.
====================================================================================================================================
 Package                         Architecture            Version                                  Repository                   Size
====================================================================================================================================
Upgrading:
 VirtualBox-6.1                  x86_64                  6.1.4_136177_fedora31-1                  virtualbox                  100 M

Transaction Summary
====================================================================================================================================
Upgrade  1 Package

Total download size: 100 M
Is this ok [y/N]: y
Downloading Packages:
[MIRROR] VirtualBox-6.1-6.1.4_136177_fedora31-1.x86_64.rpm: Downloading successful, but checksum doesn't match. Calculated: 21ee97ad781368ae5655a2d87f3e172139ecd022e640b47419075633e5dfd9fd(sha256)  Expected: 64d3c8e3462d6b229664f80845486ae8c576bc38a7a3eb633b01a93a906de55a(sha256) 
[MIRROR] VirtualBox-6.1-6.1.4_136177_fedora31-1.x86_64.rpm: Downloading successful, but checksum doesn't match. Calculated: 21ee97ad781368ae5655a2d87f3e172139ecd022e640b47419075633e5dfd9fd(sha256)  Expected: 64d3c8e3462d6b229664f80845486ae8c576bc38a7a3eb633b01a93a906de55a(sha256) 
[MIRROR] VirtualBox-6.1-6.1.4_136177_fedora31-1.x86_64.rpm: Downloading successful, but checksum doesn't match. Calculated: 21ee97ad781368ae5655a2d87f3e172139ecd022e640b47419075633e5dfd9fd(sha256)  Expected: 64d3c8e3462d6b229664f80845486ae8c576bc38a7a3eb633b01a93a906de55a(sha256) 
[MIRROR] VirtualBox-6.1-6.1.4_136177_fedora31-1.x86_64.rpm: Downloading successful, but checksum doesn't match. Calculated: 21ee97ad781368ae5655a2d87f3e172139ecd022e640b47419075633e5dfd9fd(sha256)  Expected: 64d3c8e3462d6b229664f80845486ae8c576bc38a7a3eb633b01a93a906de55a(sha256) 
[FAILED] VirtualBox-6.1-6.1.4_136177_fedora31-1.x86_64.rpm: No more mirrors to try - All mirrors were already tried without success

The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: Error downloading packages:
  Cannot download VirtualBox-6.1-6.1.4_136177_fedora31-1.x86_64.rpm: All mirrors were tried
}}}

Obviously packages are broken or checksum was calculated wrong.

Due to security reasons this update was rejected by package manager."	bitkocher
19318	Critical Error	Linux	VirtualBox 6.1.2	defect	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
18964	storageattach --hotpluggable while running makes disk unremovable	Linux	VirtualBox 5.2.32	defect	2019-09-25T17:36:26Z	2020-01-24T03:41:58Z	2020-01-24T03:41:58Z	"Machine `w10` is running. I do:
gsovetov@gsovetov:~$ VBoxManage storageattach w10 --storagectl SATA --port 4 --type hdd --medium po.vdi --hotpluggable on
VBoxManage: error: The machine is not mutable (state is Running)
VBoxManage: error: Details: code VBOX_E_INVALID_VM_STATE (0x80bb0002), component SessionMachine, interface IMachine, callee nsISupports
VBoxManage: error: Context: ""SetHotPluggableForDevice(Bstr(pszCtl).raw(), port, device, TRUE)"" at line 901 of file VBoxManageStorageController.cpp
}}}

I expect it to complete successfully as I explicitly enable hot-plugging when actually hot-plugging. But it's not all.

The biggest problem is that the disk get irreversibly associated with the VM! Neither attaching the disk again to this or another VM, nor `closemedium`, nor Release/Remove in Virtual Media Manager after unregistering the VM help.

{{{
gsovetov@gsovetov:~$ VBoxManage storageattach w10 --storagectl SATA --port 4 --type hdd --medium po.vdi 
VBoxManage: error: Cannot attach medium '/home/gsovetov/po.vdi' {47bb8284-7df3-42db-8132-c7d1248ee59d}: medium is already associated with the current state of machine uuid {490c11af-e66f-45fa-9e7d-f9f8ed156169}!
VBoxManage: error: Details: code VBOX_E_OBJECT_IN_USE (0x80bb000c), component MediumWrap, interface IMedium, callee nsISupports
VBoxManage: error: Context: ""AttachDevice(Bstr(pszCtl).raw(), port, device, DeviceType_HardDisk, pMedium2Mount)"" at line 776 of file VBoxManageStorageController.cpp
}}}

{{{
gsovetov@gsovetov:~$ VBoxManage showvminfo w10 --machinereadable | grep -iE 'storage|sata'
storagecontrollername0=""SATA""
storagecontrollertype0=""IntelAhci""
storagecontrollerinstance0=""0""
storagecontrollermaxportcount0=""30""
storagecontrollerportcount0=""8""
storagecontrollerbootable0=""on""
""SATA-0-0""=""/home/gsovetov/VirtualBox VMs/w10/Snapshots/{e27504b0-359a-4caf-bbaa-6770cc83fff1}.vdi""
""SATA-ImageUUID-0-0""=""e27504b0-359a-4caf-bbaa-6770cc83fff1""
""SATA-1-0""=""none""
""SATA-2-0""=""none""
""SATA-3-0""=""none""
""SATA-4-0""=""none""
""SATA-5-0""=""none""
""SATA-6-0""=""none""
""SATA-7-0""=""none""
}}}

{{{
gsovetov@gsovetov:~$ VBoxManage list hdds | grep -C5 po

UUID:           47bb8284-7df3-42db-8132-c7d1248ee59d
Parent UUID:    base
State:          created
Type:           normal (base)
Location:       /home/gsovetov/po.vdi
Storage format: VDI
Capacity:       100 MBytes
Encryption:     disabled

}}}

{{{
gsovetov@gsovetov:~$ VBoxManage showmediuminfo po.vdi 
UUID:           47bb8284-7df3-42db-8132-c7d1248ee59d
Parent UUID:    base
State:          created
Type:           normal (base)
Location:       /home/gsovetov/po.vdi
Storage format: VDI
Format variant: dynamic default
Capacity:       100 MBytes
Size on disk:   2 MBytes
Encryption:     disabled
In use by VMs:  w10 (UUID: 490c11af-e66f-45fa-9e7d-f9f8ed156169)
}}}

{{{
gsovetov@gsovetov:~$ VBoxManage unregistervm w10  
gsovetov@gsovetov:~$ VBoxManage showmediuminfo po.vdi 
UUID:           47bb8284-7df3-42db-8132-c7d1248ee59d
Parent UUID:    base
State:          created
Type:           normal (base)
Location:       /home/gsovetov/po.vdi
Storage format: VDI
Format variant: dynamic default
Capacity:       100 MBytes
Size on disk:   2 MBytes
Encryption:     disabled
VBoxManage: error: Could not find a registered machine with UUID {490c11af-e66f-45fa-9e7d-f9f8ed156169}
VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBoxWrap, interface IVirtualBox, callee nsISupports
VBoxManage: error: Context: ""FindMachine(machineIds[i], pMachine.asOutParam())"" at line 1375 of file VBoxManageDisk.cpp
gsovetov@gsovetov:~$ VBoxManage closemedium /home/gsovetov/po.vdi
VBoxManage: error: Medium '/home/gsovetov/po.vdi' cannot be closed because it is still attached to 1 virtual machines
VBoxManage: error: Details: code VBOX_E_OBJECT_IN_USE (0x80bb000c), component MediumWrap, interface IMedium, callee nsISupports
VBoxManage: error: Context: ""Close()"" at line 1648 of file VBoxManageDisk.cpp
}}}

The only way to detach it is to power off all VMs, wait for VBoxSVC to terminate, then manually remove the record from XML file, then run GUI and open Virtual Media Manager and remove the disk there."	georgesovetov
13380	When I try to look for updates I get Wrong SSL certificate format	Linux	VirtualBox 4.3.14	defect	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
19167	Repository metadata broken for Fedora	Linux	VirtualBox 6.1.0	defect	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
19092	6.0.14 Extensio Pack installation error on Linux Mint Debian Edition 3	Linux	VirtualBox 6.0.14	defect	2019-11-16T22:39:26Z	2019-11-17T01:57:01Z	2019-11-17T01:57:01Z	Система LMDE 3,Ошибка установки VirtualBox 6.0.14 Oracle VM VirtualBox Extension Pack.	gri
19063	Multiple VBoxSVC processes on Linux host	Linux	VirtualBox 5.2.32	defect	2019-11-05T10:01:27Z	2019-11-05T10:01:27Z	2019-11-05T10:01:27Z	"Hello,

I use VirtualBox on headless Linux server.

From time to time I get second VBoxSVC process running:
{{{
#: ps aufx | grep VBoxSVC
jenkins   6445  0.0  0.0  14856  1040 pts/0    S+   09:19   0:00              \_ grep VBoxSVC
jenkins  19100  2.2  0.0 1077660 84388 ?       Sl   Oct17 604:18 /usr/lib/virtualbox/VBoxSVC --auto-shutdown
jenkins  27511  1.7  0.0 875548 28544 ?        Sl   Nov04  15:58 /usr/lib/virtualbox/VBoxSVC --auto-shutdown
}}}
I have to kill processes every time I get this issue.
All VBoxHeadless processes always start by user jenkins.
/tmp permissions: drwxrwxrwt  root root
{{{
#: ls -la /tmp/
drwx------  2 jenkins jenkins  4096 Nov  4 18:14 .vbox-jenkins-ipc

#: ls -l /tmp/.vbox-jenkins-ipc/
srwx------ 1 jenkins jenkins 0 Nov  4 18:14 ipcd
-rw------- 1 jenkins jenkins 6 Nov  4 18:14 lock
}}}

User jenkins is in vboxusers group.

Version: 5.2.32r132073.

Host: Ubuntu 18.04.3 LTS"	mgubanov
18881	Guest additions installation fails with: The network operation failed with the following error:  During network request: Unknown reason.	Linux	VirtualBox 6.0.10	defect	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
17044	Doing network copy from shared folder does not transfer file correctly: wrong md5sum	Linux	VirtualBox 5.1.26	defect	2017-08-30T02:50:26Z	2019-08-29T10:40:50Z	2019-08-29T10:40:50Z	"When I copy file from shared folder to remote target with scp, scp exists with success 0, yet the md5sum on the remote target is different from the source.
Coping / scp'ing the same file from non-shared folder within same Vm works correctly: same md5sum on remote target.
Scp transfers different file sizes in the two cases.

E.g. 
md5sum  /media/sf_dloads/dhnc_m4_fw.tar.bz2

403f9fe21ed74762923d3d7c2087d62a  /media/sf_dloads/dhnc_m4_fw.tar.bz2

md5sum dhnc_m4_fw.tar.bz2 

403f9fe21ed74762923d3d7c2087d62a  dhnc_m4_fw.tar.bz2

scp -v /media/sf_dloads/test/dhnc_m4_fw.tar.bz2  root@192.168.1.110:/tmp/

.....
Transferred: sent 455796, received 1796 bytes, in 1.2 seconds
Bytes per second: sent 367895.7, received 1449.6
debug1: Exit status 0

on target:

md5sum  /tmp/dhnc_m4_fw.tar.bz2

ed67bef761dbfb2b35f62510b2c930c5  /tmp/dhnc_m4_fw.tar.bz2

scp -v dhnc_m4_fw.tar.bz2  root@192.168.1.110:/tmp/

.....
Transferred: sent 456788, received 1856 bytes, in 1.6 seconds
Bytes per second: sent 291460.5, received 1184.2
debug1: Exit status 0

on target:

 md5sum  /tmp/dhnc_m4_fw.tar.bz2

403f9fe21ed74762923d3d7c2087d62a  /tmp/dhnc_m4_fw.tar.bz2
"	dry
18870	vboxwebsrv IPerformanceCollector.queryMetricsData failed.	Linux	VirtualBox 6.0.8	defect	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
18808	VirtualBox 6.0.10 Segmentation fault in openSUSE 13.2	Linux	VirtualBox 6.0.10	defect	2019-08-03T06:43:53Z	2019-08-03T06:43:53Z	2019-08-03T06:43:53Z	"VirtualBox 6.0.10 has segmentation fault in openSUSE 13.2, immediately on startup.[[BR]]
VirtualBox-6.0-6.0.10_132072_openSUSE132-1.x86_64.rpm[[BR]]

Syslog shows:[[BR]]
ug 03 12:16:11 trinity.cgl kernel: UINetworkReplyP[7796]: segfault at 7f4a3a4d1550 ip 00007f4a02fba22e sp 00007f4a03ffe328 error 7 in libkdecore.so.5.14.9[7f4a02f1b000+2b3000][[BR]]
Aug 03 12:18:43 trinity.cgl kernel: UINetworkReplyP[7903]: segfault at 7fa643541550 ip 00007fa62059222e sp 00007fa6217f9328 error 7 in libkdecore.so.5.14.9[7fa6204f3000+2b3000][[BR]]
Aug 03 12:21:23 trinity.cgl kernel: UINetworkReplyP[8062]: segfault at 7f0b1d4f9550 ip 00007f0aef24222e sp 00007f0b048e9328 error 7 in libkdecore.so.5.14.9[7f0aef1a3000+2b3000]

user@trinity:/usr/lib64> rpm -qi  libkdecore4-4.14.9-27.1.x86_64[[BR]]
Name        : libkdecore4[[BR]]
Version     : 4.14.9[[BR]]
Release     : 27.1[[BR]]
Architecture: x86_64[[BR]]
Install Date: Sat 20 Feb 2016 12:32:55 PM SGT[[BR]]
Group       : System/GUI/KDE[[BR]]
Size        : 3034361[[BR]]
License     : LGPL-2.1+[[BR]]
Signature   : RSA/SHA256, Tue 26 Jan 2016 06:53:58 PM SGT, Key ID b88b2fd43dbdc284[[BR]]
Source RPM  : kdelibs4-4.14.9-27.1.src.rpm[[BR]]
Build Date  : Tue 26 Jan 2016 06:46:52 PM SGT[[BR]]
Build Host  : cloud107[[BR]]
Relocations : (not relocatable)[[BR]]
Packager    : http://bugs.opensuse.org[[BR]]
Vendor      : openSUSE[[BR]]
URL         : http://www.kde.org[[BR]]
Summary     : KDE Core Libraries[[BR]]
Description :[[BR]]
This package contains the core libraries of the K Desktop Environment.[[BR]]

This package is absolutely necessary for using KDE applications.[[BR]]
Distribution: openSUSE 13.2[[BR]]
user@trinity:/usr/lib64>[[BR]]

Version 6.0.8 seems to be working fine and I am now using it, having removed version 5.2.0 which i was using previously.[[BR]]

This issue is probably identical to the one identifed in Ticket #18767:[[BR]]
https://www.virtualbox.org/ticket/18767"	CHIN_Gim_Leong
18767	VirtualBox 6.0.10 segfaults at startup on CentOS 7.6	Linux	VirtualBox 6.0.10	defect	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
18624	Vbox 6.0.6 build failure on Linux with gcc 9.1.0	Linux	VirtualBox 6.0.6	defect	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
18771	vboxdrv.sh does not attempt to build modules on Fedora if Secure Boot is enabled	Linux	VirtualBox 6.0.10	defect	2019-07-18T14:28:35Z	2019-07-18T16:48:12Z	2019-07-18T16:48:12Z	"When running vboxdrv.sh with Secure Boot enabled it exits with the message ""You must sign these kernel modules before using VirtualBox..."" before checking if the modules have been built."	thomasfedb
18679	Segmentation fault on startup up of `VirtualBox` under sway-wm using Wayland	Linux	VirtualBox 6.0.8	defect	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
18730	Ignore extra entries in OVF manifest file (.mf)	Linux	VirtualBox 6.0.8	defect	2019-06-28T14:33:18Z	2019-06-28T14:50:03Z	2019-06-28T14:50:03Z	"When a faulty program adds additional entries in the manifest file [1], VirtualBox crashes sometimes without error, sometimes with the error ""NS_ERROR_CALL_FAILED (0x800706BE)"". I propose that it should instead just ignore these entries.

[1] https://code.vmware.com/forums/3086#613566|5230149"	darkdragon
10534	Virtualbox overrides umask, making it unusable for shared setup	Linux	VirtualBox 4.1.14	defect	2012-05-09T04:40:53Z	2019-03-13T11:08:00Z	2019-03-13T11:08:00Z	"I want to setup Virtualbox to use a common directory to be used by any user who sits at the console (using VBOX_USER_HOME and the machinefolder property). Problem: The VirtualBox tools (GUI or command line) ignore umask and use 0600 instead. The next user runs into ""permission denied"" problems.

This makes it impossible for us to deploy VirtualBox as a replacement for VMware.
"	Harri
18422	Cannot install Extension Pack 6.0.4	Linux	VirtualBox 6.0.4	defect	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
18414	Menu bar very small on portrait screen	Linux	VirtualBox 6.0.4	defect	2019-02-06T06:51:02Z	2019-02-07T00:02:25Z	2019-02-07T00:02:25Z	"When I have a VM on my portrait screen with 6.0.4, it's menu bar is tiny.  This isn't a hidpi screen or anything fancy.  When I drag it back to the other landscape screen, the menu bar looks ""normal"".

I've attached a screenshot"	iwienand
18389	numeric username issue	Linux	VirtualBox 5.2.26	defect	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
18314	6.0.2 RPM was built for fedora26, while 6.0.0 RPM was built for fedora29. Regression?	Linux	VirtualBox 6.0.2	defect	2019-01-16T06:50:53Z	2019-01-16T07:02:14Z	2019-01-16T07:02:14Z	"Summary says it all. 6.0.0 installed fine on Fedora 29, because the RPM had a requires for libvpx.so.5()(64bit) from libvpx-1.7.0.

6.0.2 doesn't upgrade on Fedora 29, because it has a requires for libvpx.so.4 from libvpx-1.6.* which is no longer present on 29."	Valdis Kletnieks
18304	VirtualBox 6.0 crashes on Ubuntu 18.10	Linux	VirtualBox 6.0.0	defect	2019-01-11T21:15:19Z	2019-01-12T21:05:58Z	2019-01-12T21:05:58Z	"VirtualBox 6.0 crashes immediately after launching on fresh Ubuntu 18.10 host (ASUS N551JW laptop)

{{{
$ virtualbox
Gdk-Message: 21:32:35.060: VirtualBox: Fatal IO error 2 (No such file or directory) on X server :0.

$ sudo virtualbox
Qt WARNING: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
Qt WARNING: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
Qt WARNING: The X11 connection broke: Maximum allowed requested length exceeded (code 4)
XIO:  fatal IO error 2 (No such file or directory) on X server "":0""
      after 612 requests (612 known processed) with 0 events remaining.
}}}

My installation process:

{{{
wget -q https://www.virtualbox.org/download/oracle_vbox_2016.asc -O- | sudo apt-key add -
wget -q https://www.virtualbox.org/download/oracle_vbox.asc -O- | sudo apt-key add -
sudo add-apt-repository ""deb [arch=amd64] http://download.virtualbox.org/virtualbox/debian $(lsb_release -cs) contrib""
sudo apt-get update
sudo apt-get install virtualbox-6.0 -y
}}}
"	kipc
18300	VNC connect callback problem	Linux	VirtualBox 6.0.0	defect	2019-01-11T09:14:53Z	2019-01-11T09:18:35Z	2019-01-11T09:18:35Z	"Hello.

This is code fragment of new vnc connect.
VirtualBox-6.0.0\src\VBox\ExtPacks\VNC\VBoxVNC.cpp:
{{{
enum rfbNewClientAction VNCServerImpl::rfbNewClientEvent(rfbClientPtr cl)
{
    VNCServerImpl *instance = static_cast<VNCServerImpl *>(cl->screen->screenData);

    /// @todo we need auth user here

    instance->mCallbacks->VRDECallbackClientConnect(instance->mCallback, (int)cl->sock);
    instance->uClients++;

    cl->clientGoneHook = clientGoneHook;
    return RFB_CLIENT_ACCEPT;
}
}}}

We can see that numbers of clients (part of IVRDEServerInfo) increase. Why dont call VRDECallbackProperty to fire VRDEServerInfoChangedEvent? I need to callback vnc connect situation by pyvbox:VBoxEventType.on_vrde_server_info_changed, but i cant, because IVRDEServerInfoChangedEvent not triggered.
"	Karlo Dipetrio
18281	Feedback of /sbin/vboxconfig on failing module load not always helpful	Linux	VirtualBox 6.0.0	enhancement	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
18183	vbox-dkms  modules (vboxnetadp vboxdrv) compilation error  against kernel 4.20.0-rc6 -> fixed after (not in) 5.2.22	Linux	VirtualBox 5.2.22	defect	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
18180	Linux host, Windows and Linux guests: CPU does not exceed 1.99GHz	Linux	VirtualBox 5.2.22	defect	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
18138	Please add a fedora 29 repo	Linux	VirtualBox 5.2.22	enhancement	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
8473	Error opening current controlling terminal for the process	Linux	VirtualBox 4.0.4	defect	2011-03-02T06:43:45Z	2018-11-22T09:51:57Z	2018-11-22T09:51:57Z	"Trying to install Oracle_VM_VirtualBox_Extension_Pack-4.0.4-70112.vbox-extpack I got an error popup saying

Failed to install the Extension Pack /export/harri/Oracle_VM_VirtualBox_Extension_Pack-4.0.4-70112.vbox-extpack.

The installer failed with exit code 127: Error creating textual authentication agent: Error opening current controlling terminal for the process (`/dev/tty'): No such device or address.

Details

Result Code: 
NS_ERROR_FAILURE (0x80004005)
Component: 
ExtPackManager
Interface: 
IExtPackManager {2451b1ba-ab1c-42fb-b453-c58433bea8c7}


Of course I checked the access permissions to /dev/tty. Its readable and writable for everybody:

% ls -al /dev/tty
crw-rw-rw- 1 root root 5, 0 Mar  2 06:04 /dev/tty


Please note that running Virtualbox as root is not an option.
"	Harri
18086	vboxa uthentication segfaults SQW01	Linux	VirtualBox 5.2.20	defect	2018-10-27T04:54:52Z	2018-11-10T11:18:47Z	2018-11-10T11:18:47Z	"When using the VirtualBox web service to login, the authentication backend segfaults after a successful login. In order to be able to login again, I have to restart the web service. This has been happening for several releases of VirtualBox now.

I see the following in dmesg

[147969.086688] SQW01[17397]: segfault at 7f9e6da76700 ip 00007f9e6da76700 sp 00007f9e6e3366f8 error 14 in libcap-ng.so.0.0.0[7f9e6d8ee000+200000]
[147969.086705] Code: Bad RIP value.
[147969.213300] SQW01[17400]: segfault at 7f9e6da76700 ip 00007f9e6da76700 sp 00007f9e6e3366b8 error 14 in libcap-ng.so.0.0.0[7f9e6d8ee000+200000]
[147969.213310] Code: Bad RIP value.
[148328.226581] SQW01[17517]: segfault at 7f4f596ec700 ip 00007f4f596ec700 sp 00007f4f59fac6f8 error 14 in libcap-ng.so.0.0.0[7f4f59564000+200000]
[148328.226597] Code: Bad RIP value.
[148328.349869] SQW01[17520]: segfault at 7f4f596ec700 ip 00007f4f596ec700 sp 00007f4f59fac6b8 error 14 in libcap-ng.so.0.0.0[7f4f59564000+200000]
[148328.349879] Code: Bad RIP value.


I'm currently running VirtualBox-5.2-5.2.20_125813_fedora26-1.x86_64 on Fedora 28. 
"	oddsocks
18053	Query Installed Guest Extensions Version	Linux	VirtualBox 5.2.18	enhancement	2018-10-16T14:35:29Z	2018-10-25T23:52:41Z	2018-10-25T23:52:41Z	"Not a bug, but a question. I tried looking at the forums but was unable to answer it.

Is there a way to determine the version of Extensions installed on a VM without it running? I looked at ""vboxmanage showvminfo"" but it didn't seem to be listed there nor is there any information shown in the VirtualBox Manager GUI. 

Thanks,"	jim.rather
18025	Can't launch VirtualBox 5.2.18-1 on fedora 28.	Linux	VirtualBox 5.2.18	defect	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
17997	Re-ordering VMS is a royal pain	Linux	VirtualBox 5.2.18	defect	2018-09-19T17:30:55Z	2018-09-19T17:31:49Z	2018-09-19T17:31:49Z	When trying to re-order guest images in the list, it takes several attempts to do so.	iMarkM
17964	5.2.18 still not availale for RHEL / CentOS 7 -> fixed	Linux	VirtualBox 5.2.18	defect	2018-08-31T06:42:40Z	2018-09-12T12:12:23Z	2018-09-12T12:12:23Z	"Hello!

VB 5.2.18 is still not available for the above mentioned platform. Yesterday I tried to update and any update from 5.2.16 -> 5.2.18 was found, so finally I tried a workaround and installed a downloaded RPM manually (from http://download.virtualbox.org/virtualbox/rpm/rhel/7/x86_64/VirtualBox-5.2-5.2.18_124319_el7-1.x86_64.rpm, so it is really existiing and at it right place).

But that's what I still get from yum:
{{{
# yum --disablerepo ""*"" --enablerepo ""virtualbox"" list available
Loaded plugins: aliases, changelog, fastestmirror, langpacks, verify
Loading mirror speeds from cached hostfile
Available Packages
VirtualBox-4.3.x86_64 4.3.40_110317_el7-1  virtualbox
VirtualBox-5.0.x86_64 5.0.40_115130_el7-1  virtualbox
VirtualBox-5.1.x86_64 5.1.38_122592_el7-1  virtualbox
}}}
Just as a try to get back to the ""standard install"" from REPO:
{{{
# yum reinstall VirtualBox-5.2
Loaded plugins: aliases, changelog, fastestmirror, langpacks, verify
Loading mirror speeds from cached hostfile
 * base: mirror.cuegee.de
 * epel: ftp-stud.hs-esslingen.de
 * extras: mirror.cuegee.de
 * updates: mirror.cuegee.de
Installed package VirtualBox-5.2-5.2.18_124319_el7-1.x86_64 not available.
Error: Nothing to do
}}}
Maybe this is a duplicate of another ticket, but I found any for RHEL/CentOS 7.

With regards."	HRZ d. Universität Bielefeld
17950	5.2.18 still not in fedora 28 repository	Linux	VirtualBox 5.2.18	defect	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
17940	For Fedora, Virtualbox is being built for unsupported releases (Fedora 26)	Linux	VirtualBox 5.2.18	enhancement	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
17938	Deleting snapshot on-line causes I/O errors in guest	Linux	VirtualBox 5.2.16	defect	2018-08-18T21:53:28Z	2018-08-19T09:09:22Z	2018-08-19T09:09:22Z	"Host: Fedora 28
Guests: Fedora 28 x2 + (2 older Fedora machines)

Both guests in this event are F28 & had a single snapshot + current state, and were up (but largely idle).

Deleted snapshot of first machine.  (Using VirtualBox GUI).  It took quite a while, as the snapshot was almost 2 yrs old.

While the delete was running, I had an ssh session into the VM.  I got an error ""Read only filesystem"", then ""ps not found"".  ls worked - for a while.

This typically means that the kernel got an unrecoverable Disk I/O error - e.g. a timeout.  But as the logs live on the disk in question, and it went read-only, I can't prove it.

shutdown was also not found.  I waited a while, and commands started getting bus errors.  Seemed clear that the disks were off-line.

So I waited for the disk merge (snapshot delete) to finish, did a vboxmanage reset, and rebooted the VM.

Log file will be attached.  Note that it also shows a lot of display resize events - I see no reason for this.  The VM was started detachable; the GUI is visible, but it seems to blink for no particular reason...

Here is an 'ls' of the VDI involved:
{{{
 ls -lih /home/root/VirtualBox_VMs/Overkiller/*.vdi /home/root/VirtualBox_VMs/Overkiller/*/*.vdi
12323679 -rw-------. 1 root root 1.6G Mar 20  2016 /home/root/VirtualBox_VMs/Overkiller/Fedora23_Overkiller.vdi
12320772 -rw-------. 1 root root  35G Aug 18 16:04 /home/root/VirtualBox_VMs/Overkiller/Fedora_17_Overkill.vdi
13893639 -rw-------. 1 root root  22G Aug 18 15:49 /home/root/VirtualBox_VMs/Overkiller/Snapshots/{e981f25e-0fc7-4ba7-9666-9d00bc48eae3}.vdi
}}}

The I/O errors don't appear to be a one-off event.  I had a second VM which also had a single snapshot that I deleted the same way.  It suffered the same fate.  Log also attached.  Its ls:
{{{
ls -lih /home/root/VirtualBox_VMs/WikiWorld/*.vdi /home/root/VirtualBox_VMs/WikiWorld/*/*.vdi
9306120 -rw-------. 1 root root 30G Aug 18 16:08 /home/root/VirtualBox_VMs/WikiWorld/Snapshots/{1bb6e5e7-1e5a-40c8-8d61-daf4ff6611be}.vdi
9306115 -rw-------. 1 root root 49G Aug 18 16:08 /home/root/VirtualBox_VMs/WikiWorld/atto_wiki.vdi

}}}

Snapshot delete times were on the order of 30 minutes (each).

If deleting a snapshot on-line can cause this much havoc, it should not be allowed...
"	Timothe Litt
17936	ERROR: could not insert 'vboxdrv': Exec format error	Linux	VirtualBox 5.1.38	defect	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
11031	'Bridged Networking' on host vlan interfaces does not work	Linux	VirtualBox 4.2.0	defect	2012-10-05T22:17:44Z	2018-07-09T14:30:18Z	2018-07-09T14:30:18Z	"I have searched the forums, and looked on the internet... and this seems to be a regression in the 4.2.0 release.  Downgrading back to 4.1.22 on the same kernel resolves the issue.

I am on gentoo 64-bit, running gentoo-sources-3.6.0.  Same results on 3.5.4

I have a vm-host with several 1q vlan interfaces on it.  I then bind my VM's to a particular interface using the 'Bridge Adapter'.  The VM's are vlan-agnostic.

The symptom I have on VB 4.2.0 is that none of my VM's have network access.  As soon as I switch to NAT on the VM's everything works fine.  Downgrading to 4.1.22 on the same kernel restores network access for the 'Bridge Adapter'.

{{{
daffy TAZ6 # cat /proc/net/vlan/config
VLAN Dev name    | VLAN ID
Name-Type: VLAN_NAME_TYPE_RAW_PLUS_VID_NO_PAD
eth0.10        | 10  | eth0
eth0.11        | 11  | eth0
eth0.12        | 12  | eth0
eth0.13        | 13  | eth0
eth0.14        | 14  | eth0
eth0.20        | 20  | eth0
eth0.25        | 25  | eth0
}}}

My VM-HOST network layout:
{{{
[ROUTER]====1Q-TRUNK===[VM HOST]
                              eth0.10--bridged--VM1, VM2, VM3....
                              eth0.11--bridged--VM6, VM7, VM8
                              eth0.12--bridged--VM4
                              eth0.13
                              eth0.14--bridged--VM5
                              eth0.20
                              eth0.25
}}}

The ROUTER and VM-HOST have the VM's MAC address in their arp tables.  The VM itself only has the VM-HOST's MAC address - but not the ROUTER's.  The VM can communicate with the VM-HOST but not anything else on the same L2 vlan.  All other devices on the same L2 vlan have VM's MAC address (after a ping, say) but the VM never has any of the other hosts in it's arp table.  Seems like packets destined to the VM never make it past the VM-HOST.  I don't see any odd kernel events.

This is the forum post I started prior to this bug - https://forums.virtualbox.org/viewtopic.php?f=7&t=51886

I can attach all the details here if need be."	nocternal
17797	Error in ipl windows xp	Linux	VirtualBox 5.1.34	defect	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
17754	Installation without disabling secureboot	Linux	VirtualBox 5.2.12	enhancement	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
17712	ed stat  Guest VM with OS/2 does not resume from saved state	Linux	VirtualBox 5.2.10	defect	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
14855	Linux: Link local IPv6 address is the only one returned for host-only interfaces	Linux	VirtualBox 5.0.10	defect	2015-11-21T22:08:52Z	2018-04-19T07:50:45Z	2018-04-19T07:50:45Z	"When configuring IPv6 on Linux, the interface may have a Link Local Address (fe::) in addition to the address configured through VirtualBox. VirtualBox retrieves the addresses from {{{/proc/net/if_inet6}}}. Here is an example of what these entries look like:
{{{
$ cat /proc/net/if_inet6 
00000000000000000000000000000001 01 80 10 80       lo
fd22dfff102810700000000000000000 06 40 00 80 vboxnet3
fe80000000000000020acdfffe20a291 02 40 20 80     eth0
fe80000000000000080027fffe000003 06 40 20 80 vboxnet3
}}}

Note the order of the addresses. When VirtualBox parses the file, the code assumes there would only be one entry for an interface (and does not terminate early), i.e. (this is NetIf-linux.cpp):
{{{#!c
173             for (;;)
174             {
[...]
182                 if (n == EOF)
183                     break;
184                 if (n != 9 || uLength > 128)
185                 {
[...]
188                     break;
189                 }
190                 if (!strcmp(Req.ifr_name, szName))
191                 {
192                     pInfo->IPv6Address.au32[0] = htonl(IPv6Address.au32[0]);
193                     pInfo->IPv6Address.au32[1] = htonl(IPv6Address.au32[1]);
194                     pInfo->IPv6Address.au32[2] = htonl(IPv6Address.au32[2]);
195                     pInfo->IPv6Address.au32[3] = htonl(IPv6Address.au32[3]);
196                     ASMBitSetRange(&pInfo->IPv6NetMask, 0, uLength);
197                 }
198             }
199             fclose(fp);
200         }
}}}

For the above example, the last, Link-Local entry wins. Since VirtualBox does not handle multiple addresses per interface, it should at least ignore the Link-Local automatically created addresses. Unfortunately, this means that it would be impossible to tell which address to pick if a user configures a different link-local address.

I attached a proposed patch to resolve this."	timuralp
17683	vboxdrv.sh: failed: modprobe vboxpci failed with linux 4.15 (centos7) -> fixed after (not in) 5.1.36	Linux	VirtualBox 5.1.34	defect	2018-04-13T10:06:03Z	2018-04-18T15:46:01Z	2018-04-18T15:46:01Z	"centos7  update kernel to 4.15.11 elrepo ,and vbox install have some problems with ""vboxpci: 

Unknown symbol vfs_write (err 0)""
{{{
uname -a
Linux crmdev205 4.15.11-1.el7.elrepo.x86_64 #1 SMP Mon Mar 19 11:46:06 EDT 2018 x86_64 x86_64 

x86_64 GNU/Linux


 ./VirtualBox-5.1.34-121010-Linux_amd64.run 
Verifying archive integrity... All good.
Uncompressing VirtualBox for Linux installation.............
VirtualBox Version 5.1.34 r121010 (2018-02-26T15:29:57Z) installer
Removing previous installation of VirtualBox 5.1.32 r120294 from /opt/VirtualBox
Installing VirtualBox to /opt/VirtualBox
Python found: python, installing bindings...
vboxdrv.sh: failed: modprobe vboxpci failed. Please use 'dmesg' to find out why.

There were problems setting up VirtualBox.  To re-start the set-up process, run
  /sbin/vboxconfig
as root.

VirtualBox has been installed successfully.

You will find useful information about using VirtualBox in the user manual
  /opt/VirtualBox/UserManual.pdf
and in the user FAQ
  http://www.virtualbox.org/wiki/User_FAQ

We hope that you enjoy using VirtualBox.

[root@crmdev205 soft]# dmesg | tail -f 
[1746570.104013] vboxdrv: Successfully loaded version 5.1.34 (interface 0x002a0000)
[1746570.312366] VBoxNetFlt: Successfully started.
[1746570.318263] VBoxNetAdp: Successfully started.
[1746570.321467] vboxpci: Unknown symbol vfs_write (err 0)
[1747176.620175] vboxdrv: Found 32 processor cores
[1747176.635978] vboxdrv: TSC mode is Invariant, tentative frequency 1999998028 Hz
[1747176.635979] vboxdrv: Successfully loaded version 5.1.34 (interface 0x002a0000)
[1747176.840965] VBoxNetFlt: Successfully started.
[1747176.844354] VBoxNetAdp: Successfully started.
[1747176.846577] vboxpci: Unknown symbol vfs_write (err 0)
}}}"	zw
17364	With python3 find_machine always throws TypeError	Linux	VirtualBox 5.1.30	defect	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
7009	Starting VM with Intel-VT enabled freezes system	Linux	VirtualBox 3.2.10	defect	2010-06-15T21:35:34Z	2018-03-21T06:23:27Z	2018-03-21T06:23:27Z	"When starting a VM on my laptop with Intel-VT enabled, the host freezes immediatly.
As workarround I can disable VT in BIOS.

I experience the problem with:
VirtualBox-3.2.4 and 3.1
Fedora-12 and Fedora-13 + rawhide-2.6.34

Because the system freezes immediatly after starting the VM, log files are empty.
I'll attach a log file generated when VT was disabled."	Linuxhippy
17609	problem with kernel	Linux	VirtualBox 5.2.8	defect	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
16105	Audio capture for multiple VMs problem since 5.0 version	Linux	VirtualBox 5.1.8	defect	2016-10-22T14:31:49Z	2018-02-14T10:18:47Z	2018-02-14T10:18:47Z	"I have 3 virtual machines, all with android x86 image, and using audio input device for capturing audio.
On host machine I run linux and using pulseaudio.
After booting up the VM, it's up with sink name same ""Virtualbox"", when I booting up second VM it also starts with sink name ""Virtualbox""...(I see it in pavucontrol application on Inputs tab).
No possibility to apply separate inputs for different VMs(because all of them has same name of sink in pavucontrol).
Also no possibility to change sink name, because starting from version 5.0 all VMs starts with sink name ""VirtualBox"", in alder versions(4.3.40 for examle) VM create the sink name same as vertual machine name.
No workaround for this problem, only rollback to version 4.*"	antonIO
17532	virtualbox-5.2 depends on libfontconfig1 (>= 2.9.0); (Ubuntu 14.04 LTS)	Linux	VirtualBox 5.2.6	defect	2018-02-07T21:11:20Z	2018-02-07T21:11:20Z	2018-02-07T21:11:20Z	"install of virtualbox-5.2_5.2.6-120293~Ubuntu~trusty_amd64 fails on fully upgraded 14.04 LTS[[BR]]
[[BR]] uname -a[[BR]]
Linux vm530.loc 3.2.0-68-generic #102-Ubuntu SMP Tue Aug 12 22:02:15 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux[[BR]]

[[BR]]
See attached installer log, summary follows:[[BR]]
[[BR]]
The following packages have unmet dependencies:[[BR]]
 virtualbox-5.2 : Depends: libfontconfig1 (>= 2.9.0) but[[BR]]
2.8.0-3ubuntu9.2 is to be installed[[BR]]
                  Recommends: libsdl-ttf2.0-0 but it is not going to be installed[[BR]]

E: Unable to correct problems, you have held broken packages."	AndreasFG
17389	VM starts, but UI stuck at creating process	Linux	VirtualBox 5.2.4	defect	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
3500	Auto startup and shutdown for VMs	Linux	VirtualBox 2.1.4	enhancement	2009-03-05T10:24:05Z	2017-09-19T08:32:39Z	2017-09-19T08:32:39Z	It would be good to have an option to allow (headless ?) VMs to be started automatically on host boot and gracefully shut down when the host shuts down. I know that scripts exist, but configuring this in an easy and uncomplicated way via the GUI would be a great enhancement.	mark_orion
16118	Ubuntu 16.04.1 crash of UI	Linux	VirtualBox 5.1.8	defect	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
9103	modifyvm --resize doesn't work with snapshots	Linux	VirtualBox 4.0.8	defect	2011-06-24T10:27:29Z	2017-09-13T14:31:41Z	2017-09-13T14:31:41Z	"I have a 20GB dynamic .vdi which I want to resize to 40GB so I issue:

VBoxManage modifyhd /full/path/to/hd.vdi --resize 40960

and it responds (instantly) with:

0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%

Running VBoxManage showhdinfo on the image tells me:

...
Logical size:         40960 MBytes
Current size on disk: 18464 MBytes
Type:                 normal (base)
Storage format:       VDI
Format variant:       dynamic default
...

and also reports the same logical size for the snapshot files.

The problem is that gparted reports that the drive is still 20G (not the partition; the whole drive).

Windows disk management also sees the drive as 20G.

It looks like while VirtualBox can see the new logical size, it's not reporting it to the guest correctly."	jonsiddle
17045	"""vboxmanage list hostinfo"" fails if CPUs have gaps in their processor IDs."	Linux	VirtualBox 5.1.26	defect	2017-08-30T15:21:53Z	2017-08-30T17:03:33Z	2017-08-30T17:03:33Z	"I have a server containing two Intel(R) Xeon(R) CPU X5675[1] @ 3.07GHz with 6 physical cores each and hyperthreading enabled, which results in 24 processors in total. Running ""vboxmanage list hostinfo"" results in the following shortened output:

{{{
VBoxManage: error: Code NS_ERROR_FAILURE (0x80004005) - Operation failed (extended info not available)
VBoxManage: error: Context: ""GetProcessorDescription(i, processorDescription.asOutParam())"" at line 241 of file VBoxManageList.cpp
VBoxManage: error: Code NS_ERROR_FAILURE (0x80004005) - Operation failed (extended info not available)
VBoxManage: error: Context: ""GetProcessorDescription(i, processorDescription.asOutParam())"" at line 241 of file VBoxManageList.cpp
VBoxManage: error: Code NS_ERROR_FAILURE (0x80004005) - Operation failed (extended info not available)
VBoxManage: error: Context: ""GetProcessorDescription(i, processorDescription.asOutParam())"" at line 241 of file VBoxManageList.cpp
VBoxManage: error: Code NS_ERROR_FAILURE (0x80004005) - Operation failed (extended info not available)
VBoxManage: error: Context: ""GetProcessorDescription(i, processorDescription.asOutParam())"" at line 241 of file VBoxManageList.cpp
Host Information:

Host time: 2017-08-29T09:42:55.061000000Z
Processor online count: 24
Processor count: 24
Processor online core count: 12
Processor core count: 12
Processor supports HW virtualization: yes
Processor supports PAE: yes
Processor supports long mode: yes
Processor supports nested paging: yes
Processor#0 speed: 3066 MHz
Processor#0 description: Intel(R) Xeon(R) CPU           X5675  @ 3.07GHz
Processor#1 speed: 3066 MHz
[...]
Processor#11 speed: 3066 MHz
Processor#11 description: Intel(R) Xeon(R) CPU           X5675  @ 3.07GHz
Processor#12 speed: unknown
Processor#12 description: 
Processor#13 speed: unknown
Processor#13 description: 
Processor#14 speed: unknown
Processor#14 description: 
Processor#15 speed: unknown
Processor#15 description: 
Processor#16 speed: 3066 MHz
Processor#16 description: Intel(R) Xeon(R) CPU           X5675  @ 3.07GHz
[...]
Processor#23 speed: 3066 MHz
Processor#23 description: Intel(R) Xeon(R) CPU           X5675  @ 3.07GHz
Memory size: 145055 MByte
Memory available: 143530 MByte
Operating system: Linux
Operating system version: 4.10.0-33-generic
}}}

As you can see, while the overall number of processors is known, the command fails to retrieve the description of some of those. The reason is pretty simple: The implementation uses a loop to iterate all processor IDs and fails, because my IDs have gaps. Look at the following output of lscpu:

{{{
NUMA node0 CPU(s):     0,2,4,6,8,10,16,18,20,22,24,26
NUMA node1 CPU(s):     1,3,5,7,9,11,17,19,21,23,25,27
}}}

The following is the implementation of VBoxManageList.cpp:

{{{
static HRESULT listHostInfo(const ComPtr<IVirtualBox> pVirtualBox)
{
	[...]
	Bstr processorDescription;
	for (ULONG i = 0; i < processorCount; i++)
	{
		CHECK_ERROR(Host, GetProcessorSpeed(i, &processorSpeed));
		if (processorSpeed)
			RTPrintf(""Processor#%u speed: %lu MHz\n"", i, processorSpeed);
		else
			RTPrintf(""Processor#%u speed: unknown\n"", i);
		CHECK_ERROR(Host, GetProcessorDescription(i, processorDescription.asOutParam()));
		RTPrintf(""Processor#%u description: %ls\n"", i, processorDescription.raw());
	}
	[...]
}
}}}

12, 13, 14 and 15 are not used currently and I'm pretty sure that I don't have any influence on those IDs. Have double-checked the BIOS and from what I've researched on the topic on how those IDs are assigned, I have the feeling that this is really some attribute of the CPUs itself and only used by the Linux kernel, not assigned. So gaps in those IDs should be a valid use case:

> The x2APIC id space is not continuously mapped to logical processors however; there can be gaps in the mapping, meaning that some intermediate x2APIC ids don't necessarily correspond to any logical processor.

https://en.wikipedia.org/wiki/CPUID#EAX.3D4_and_EAX.3DBh:_Intel_thread.2Fcore_and_cache_topology

{{{
c->cpu_core_id = apic->phys_pkg_id(c->initial_apicid, index_msb) &
 				       ((1 << core_bits) - 1);
}}}


http://elixir.free-electrons.com/linux/v4.0.9/source/arch/x86/kernel/cpu/common.c#L546

http://elixir.free-electrons.com/linux/v4.0.9/source/arch/x86/include/asm/processor.h#L114

With 8-core CPUs in mind, the gap of 2 per CPU might even make sense, because it's one additional core with hyperthreading, while the other core might simply be added at the end of the IDs.

So it seems using a loop might be a bit too naive and needs to be reworked to really use the available CPU IDs. I didn't came across any other errors like this one for now and hosting some VMs it looks like all CPUs are used by VirtualBox properly.

[1]: https://ark.intel.com/de/products/52577/Intel-Xeon-Processor-X5675-12M-Cache-3_06-GHz-6_40-GTs-Intel-QPI"	Thorsten Schöning
16999	VBoxDrv: Too many CPUs (288) for the GIP (max 256)	Linux	VirtualBox 5.1.26	defect	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
16942	removing the deb package should also remove the systemd service	Linux	VirtualBox 5.1.24	defect	2017-07-25T06:44:32Z	2017-07-25T06:44:32Z	2017-07-25T06:44:32Z	"As said, a lot of people remove virtualbox-4.2 virtualbox-5.0 virtualbox-5.1, and they try to install the Ubuntu version.

The problem is that without a --purge, your virtualbox package doesn't remove the systemd services, leading to install errors
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1705940

DKMS: install completed.
Configurando virtualbox (5.0.40-dfsg-0ubuntu1.16.04.1) ...
insserv: script virtualbox: service vboxdrv already provided!
insserv: exiting now!
update-rc.d: error: insserv rejected the script header
dpkg: error al procesar el paquete virtualbox (--configure):
 el subproceso instalado el script post-installation devolvió el código de salida de error 1
dpkg: problemas de dependencias impiden la configuración de virtualbox-qt:
 virtualbox-qt depende de virtualbox (= 5.0.40-dfsg-0ubuntu1.16.04.1); sin embargo:
 El paquete `virtualbox' no está configurado todavía.
  El paquete `virtualbox-4.2' que provee virtualbox no está instalado.


so, please remove your files when virtualbox is removed :)

thanks
"	LocutusOfBorg
16694	Host fails to resume from suspend when virtualbox installed	Linux	VirtualBox 5.1.18	defect	2017-04-25T07:35:52Z	2017-04-25T07:38:26Z	2017-04-25T07:38:26Z	"Since I installed virtualbox my laptop fails to suspend to RAM properly.

Looks like it suspends, but when I open the lid it just reboots.

Laptop is a Dell XPS 13 9350 Developer edition
OS: Ubuntu 16.10 / 17.04
Virtual box does not need to be running, just installed


Steps to reproduce:
- close lid and suspend to ram
- open lid and it will just restarts most of the time

From the logs:
Suspending:

Apr 21 16:55:24 XPS13 systemd[1]: Starting TLP suspend/resume...
Apr 21 16:55:24 XPS13 psensor.desktop[15786]: [2017-04-21T15:55:24] [ERR] lmsensor: Cannot get value of subfeature temp1_input: I/O error.
Apr 21 16:55:24 XPS13 systemd[1]: Started TLP suspend/resume.
Apr 21 16:55:24 XPS13 systemd[1]: Reached target Sleep.
Apr 21 16:55:24 XPS13 systemd[1]: Starting Suspend...
Apr 21 16:55:24 XPS13 systemd-sleep[26264]: Failed to connect to non-global ctrl_ifname: (nil)  error: No such file or directory
Apr 21 16:55:24 XPS13 systemd-sleep[26265]: /lib/systemd/system-sleep/wpasupplicant failed with error code 255.
Apr 21 16:55:24 XPS13 systemd-sleep[26264]: Suspending system...
Suspend never finished

And it just reboots:
Apr 21 17:59:10 XPS13 rsyslogd: [origin software=""rsyslogd"" swVersion=""8.16.0"" x-pid=""902"" x-info=""http://www.rsyslog.com""] start

Let me know if more info is needed"	silles
14724	Need way to move virtual-disk files of running VM	Linux	VirtualBox 5.0.6	enhancement	2015-10-20T23:35:20Z	2017-03-17T11:01:58Z	2017-03-17T11:01:58Z	"This is an enhancement request to permit virtual disk files to be moved while they are in use by a (paused) VM.

If an out-of-disk condition occurs, VBox very nicely pauses the VM and pops up a message so you can fix the problem and resume.  However, it continues to hold the virtual disk (including snapshot) files open, so even if they are moved and replaced by symlinks, no disk space can be freed up.  If the VM was running in a dedicated partition, i.e., there is nothing else to move or delete besides VM's files, then there is no possible recovery without loosing VM state; VBox won't close the old files until the VM is shut down, and it and it can't save the VM state if disk is full.

Following are a couple of suggestions, one basic and the other fancy:

Method A (Basic): When a VM is ""paused"", close all the VM's files, at least the virtual disks; re-open them only when the VM is resumed.

   This would let you manually relocate a virtual disk and replace it with a symlink while the VM is paused.  Using the symlink would be necessary because the .vbox file still could not be edited while VBox is running.

Method B (Fancy): Provide a comprehensive command to move a virtual disk, updating VirtualBox.xml or the VM's .vbox file as appropriate.  For example

  VBoxManage modifyvm <vmident> --movemedium <uuid|filename> /destination/folder/
  VBoxManage modifyvm <vmident> --movesnap <snapid|filename> /destination/folder/

This would 
  1. pause all VMs using the specified virtual disk *if not already paused*
(and make them close the underlying files, just as in the simpler method above); 
  2. move the file, 
  3. update and rewrite VirtualBox.xml or the VM's .vbox file with the new path; 
  4. resume VMs paused in step 1 (but not VMs which were already paused)

"	Jim Avera
16351	Segfault on Wayland, QTBUG-55583	Linux	VirtualBox 5.1.12	defect	2017-01-03T15:19:08Z	2017-01-03T15:19:08Z	2017-01-03T15:19:08Z	"The GUI would often crash with this error on Wayland (I am on Fedora 25, but other people reported it on Arch as well):

{{{
(VirtualBox:13367): Gdk-WARNING **: gdkwindow-x11.c:5573 drawable is not a native X11 window
zsh: segmentation fault  virtualbox
}}}

For instance, trying to add the extension pack always leads to this crash, when clicking on the file system browsing arrow.

The issue has been patched in QT : http://zashikiro.hateblo.jp/entry/2016/11/28/005916

Several reports do exist all around (http://zashikiro.hateblo.jp/entry/2016/11/28/005916), but I guess this must be fixed upstream.

"	phocean
16312	RPM upgraid fails when VBoxSVC --auto-shutdown is running	Linux	VirtualBox 5.1.12	defect	2016-12-22T04:44:18Z	2016-12-22T04:44:18Z	2016-12-22T04:44:18Z	"When trying to upgrate VirtualBox with yum/rpm, the first attempt fails if VBoxSvc --auto-shutdown is running.  The preinstall script shuts down services, but only waits 1 second for VBoxSVC to terminate, when it takes closer to 10 (which is documented in the error message, but the script doesn't take into account!).  Thus the upgrade fails, but works if you try again after the service terminates.

The solution is to chane the 'sleep 1' on line 103 of /usr/lib/virtualbox/routines.sh to 'sleep 10' (or do a loop checking ever second for 10 seconds, or something like that).

{{{
# yum update
Loaded plugins: aliases, auto-update-debuginfo, changelog, fastestmirror, filter-data, keys, list-data, merge-conf,
              : priorities, ps, remove-with-leaves, rpm-warm-cache, show-leaves, verify
Loading mirror speeds from cached hostfile
 * base: mirrors.centos.webair.com
 * elrepo: mirrors.evowise.com
 * epel: mirror.symnds.com
 * extras: mirror.umd.edu
 * nux-dextop: mirror.li.nux.ro
 * updates: mirror.datto.com
Skipping filters plugin, no data
Resolving Dependencies
Skipping filters plugin, no data
--> Running transaction check
---> Package VirtualBox-5.1.x86_64 0:5.1.10_112026_el7-1 will be updated
---> Package VirtualBox-5.1.x86_64 0:5.1.12_112440_el7-1 will be an update
--> Finished Dependency Resolution

Dependencies Resolved

===================================================================================================================
 Package                     Arch                Version                             Repository               Size
===================================================================================================================
Updating:
 VirtualBox-5.1              x86_64              5.1.12_112440_el7-1                 virtualbox               75 M

Transaction Summary
===================================================================================================================
Upgrade  1 Package

Total download size: 75 M
Is this ok [y/d/N]: y
Downloading packages:
No Presto metadata available for virtualbox
VirtualBox-5.1-5.1.12_112440_el7-1.x86_64.rpm                                               |  75 MB  00:00:05     
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
A copy of VirtualBox is currently running.  Please close it and try again.
Please note that it can take up to ten seconds for VirtualBox (in particular
the VBoxSVC daemon) to finish running.
error: %pre(VirtualBox-5.1-5.1.12_112440_el7-1.x86_64) scriptlet failed, exit status 1
Error in PREIN scriptlet in rpm package VirtualBox-5.1-5.1.12_112440_el7-1.x86_64
  Verifying  : VirtualBox-5.1-5.1.12_112440_el7-1.x86_64                                                       1/2 
VirtualBox-5.1-5.1.10_112026_el7-1.x86_64 was supposed to be removed but is not!
  Verifying  : VirtualBox-5.1-5.1.10_112026_el7-1.x86_64                                                       2/2 

Failed:
  VirtualBox-5.1.x86_64 0:5.1.10_112026_el7-1              VirtualBox-5.1.x86_64 0:5.1.12_112440_el7-1             

Complete!
}}}
"	Joshua Megerman
15653	VRDP not working after upgrading to 5.1	Linux	VirtualBox 5.1.0	defect	2016-07-21T07:23:59Z	2016-12-20T18:37:34Z	2016-12-20T18:37:34Z	Host: Debian 8 (and Ubuntu 16.04). Updated from 5.0.26 to 5.1. Extension Pask updated. Firewall is not set, the ports are opened. Tested on the local (127.0.0.1) and remote connection.	Mik Foxi
16297	vboxweb and vboxbaloonctrl service scripts depend on 'killall', which is not installed by default on CentOS7	Linux	VirtualBox 5.1.10	defect	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
16283	Detachable run won't let its window close correctly	Linux	VirtualBox 5.0.18	defect	2016-12-12T21:16:10Z	2016-12-15T16:13:55Z	2016-12-15T16:13:55Z	"VirtualBox 5.0.18 r106667, Ubuntu 14.04.4 (64-bit) guest running on CentOS 7 (64-bit) host. I run the guest in detachable mode, but when I close the window and select ""Continue to run in background"", I get this message:

Failed to set the extra data for key GUI/Fullscreen of machine  to value {}.

The object is not ready.

Result Code: E_ACCESSDENIED (0x80070005)
Component: SessionMachine
Interface: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}

...and the guest aborts."	Daniel U. Thibault
16236	Bug in the vboxdrv module (rtR0MemAllocEx) on Linux 4.8.8+ (grsecurity)	Linux	VirtualBox 5.1.10	defect	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
16263	VDE networking support seems not to be present	Linux	VirtualBox 5.0.24	defect	2016-12-03T22:26:40Z	2016-12-03T23:06:23Z	2016-12-03T23:06:23Z	"Hi,

I am trying to use my vbox in conjunction with VDE switch.
Checked in the docs, that it should be compiled with --enable-vde flag to make it effective so that in interface's properties I will be able to choose VDE next to other native options.

I got virtualbox sources for Ubuntu 16.04 and I can see the VDE flag is set to 1 by default. Recompiled it for the formality and installed those packages, still there is no VDE option present.

Can you guys confirm you still support VDE?"	maq123
8435	VirtualBox only works with floppy disk images which have a certain filename extension	Linux	VirtualBox 4.0.4	defect	2011-02-25T15:38:34Z	2016-10-10T15:42:12Z	2016-10-10T15:42:12Z	"VirtualBox 4.0.4 seems to refuse to work with floppy disk images unless the image filename has a certain extension. For example, on selecting ""myfloppy.bin"" in the GUI, VirtualBox says:
  Failed to open the floppy image /home/user/myfloppy.bin.
  Could not get the storage format of the medium '/home/user/myfloppy.bin' (VERR_NOT_SUPPORTED).

  Result Code: 
  VBOX_E_IPRT_ERROR (0x80BB0005)
  Component: 
  Medium
  Interface: 
  IMedium {9edda847-1279-4b0a-9af7-9d66251ccc18}
  Callee: 
  IVirtualBox {d2de270c-1d4b-4c9e-843f-bbb9b47269ff}

However, if I rename the file to myfloppy.dsk, there is no problem. I suggest that the filename limitation be removed. (If the selected file is exactly 1474560 bytes long, it will be a raw floppy disk image.)

"	Donuts
16045	On later RHEL6.8 kernels, hostonly networks stop working after just a few minutes	Linux	VirtualBox 5.1.6	defect	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
15995	Video corruption with gengradd.dll from OS/2 guest additions	Linux	VirtualBox 5.1.6	defect	2016-09-28T02:56:54Z	2016-09-28T02:56:54Z	2016-09-28T02:56:54Z	"When using the OS/2 guest additions video driver (gengradd.dll) mouse artifacts are left on the screen from selected applications (generally when mouse pointer changes while moving across other dynamic content).

I have seen this for some time (VBox 4?), and continue to see it on:

VirtualBox-5.1-5.1.6_110634_openSUSE132-1.x86_64

with the latest additions installed.

Screenshots attached.

Rolling back to the default gengradd.dll installed with the guest OS, no corruption is seen."	Lewis Rosenthal
15919	No sound when VirtualBox is installed	Linux	VirtualBox 5.0.26	defect	2016-09-12T09:10:47Z	2016-09-12T09:42:50Z	2016-09-12T09:42:50Z	"The original report was filed here:
https://github.com/NixOS/nixpkgs/issues/15005

When VirtualBox is installed in NixOS, the kernel emits a backtrace which then results in the host not having any sound. So far it only seems to be happening on the Skylake architecture. We tried multiple Linux versions with always the same result.

None of us have kernel debugging experience, do you mind pointing us to the right direction?"	zimbatm
15775	Could not read from the boot medium. System halted	Linux	VirtualBox 5.0.10	defect	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
8947	Serial port raw mode should use O_APPEND for the file	Linux	VirtualBox 4.0.8	enhancement	2011-05-23T02:51:16Z	2016-08-22T09:41:00Z	2016-08-22T09:41:00Z	"When setting a serial port to output to a file, the file should be opened with the O_APPEND flag. This allows the user to insert markers into the file (using ""echo marker >> file"" from the host machine) that will not be overwritten by virtualbox.

This change should literally be a one-liner.

Shachar"	Shachar Shemesh
11947	High I/O on SharedFolders hangs system	Linux	VirtualBox 4.2.16	defect	2013-07-09T15:52:02Z	2016-08-17T15:05:50Z	2016-08-17T15:05:50Z	"Running a deep file scan (IdentityFinder) within a 32bit Windows XP guest on a Shared Folder is causing multiple VMs to independently hang. Guest OS remains somewhat responsive (right click on start bar provides menu) but Explorer or other applications remain unresponsive. 

Task Manager is still running/updating and shows 0% CPU usage.

I've included virtual box log. Machine went unresponsive at 10 minutes. Resized window at 35 minutes to provide timeline. Host OS shows vmware process as utilizing between 13-40% cpu utilization.

Host OS is Fedora 19 with yum packages ""akmod-VirtualBox Virtualbox"" installed.



"	dsiercks
15809	Virtual machine not runing	Linux	VirtualBox 5.1.2	defect	2016-08-17T11:19:04Z	2016-08-17T13:23:46Z	2016-08-17T13:23:46Z	(removed pasted VBox.log content)	SerhiiNI
15655	KDE Active Screen Edge Actions of host are not disabled when running a guest OS in full screen mode	Linux	VirtualBox 5.1.0	defect	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
14538	Ubuntu 15.04 Desktop - vboxautostart does not work on boot (no output)	Linux	VirtualBox 5.0.2	defect	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
15353	Incorrect quoting in balloon control startup script	Linux	VirtualBox 5.0.18	defect	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
15352	Poor/missing documentation of Balloon parameters	Linux	VirtualBox 5.0.18	defect	2016-04-25T23:17:39Z	2016-04-25T23:17:39Z	2016-04-25T23:17:39Z	"The parameters involved in the balloon control (in VBoxBalloonCtrl) are very poorly described (section 9.22.1).  I had to read the code to understand how they are being used.

BalloonLowerLimitMB - despite the confusing name, this parameter is the minimum free memory that should be maintain in the Guest. It is not a ""balloon lower limit"", it is a Guest free memory lower limit.

VBOXWATCHDOG_BALLOON_SAFETYMARGIN - this parameter is only visible in the daemon start up script. While I assumed this was the memory safety margin in the Guest, it is not. It is the memory safety margin the Host. The balloon daemon will not reduce the balloon in a Guest if that would cause the Host to not have enough memory.


"	prensing
15273	Inconsistent state of attached disks, cannot close medium	Linux	VirtualBox 5.0.16	defect	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
10157	Adding vCPUs degrades network performance.	Linux	VirtualBox 4.1.8	defect	2012-01-11T12:28:32Z	2015-10-12T11:19:25Z	2015-10-12T11:19:25Z	"Observed on both Ubuntu 11.04 (2.6 kernel) and Mac OS X 10.6 hosts, both with quad core Intel i7 CPUs. Below is pasted from my forum post: https://forums.virtualbox.org/viewtopic.php?f=7&t=47136. 

I decided to run some network throughput benchmarks (mainly interested in max packets per second), and have noticed a large discrepancy when assigning one CPU to a VM vs 2 or more CPUs. My setup (all 64-bit):
Host: Ubuntu 11.04 2.6.38-13-generic #53-Ubuntu SMP, 3 GHz Intel i7 950 (4 phys cores + HT), 12GB RAM, Ethernet: Intel 82574L Gigabit
Guest: Ubuntu 11.10 3.0.0-12-server kernel, 1GB Ram assigned
VirtualBox version: 4.1.8 

Following are the results of the basic testing I performed using netserver/netperf against a bridged network interface (bridged to above Intel device). The following commands were run on the Guest against its local interface (not the loopback):
netserver -4 (starts an ipv4 tcp/udp server). 
netperf -H <IP_address_of_eth0> -t TCP_CRR (runs a TCP connect/request/response transaction benchmark) 

Single-CPU VM
~17-18k transactions per second

2-CPU VM
~5k TPS

2-CPU VM with eth0 interrupts and netserver/netperf all pinned to the same core
~7k TPS
Confirmed v. low scheduling interrupts during benchmark (watching /proc/interrupts)

2-CPU VM with 2nd core disabled via hotplugging
Disabled the second cpu with: echo '0' > /sys/devices/system/cpu/cpu1/online and confirmed via /proc/interrupts and other system tools.
~8.5k TPS

Also worth noting that on the host system, the same test yields around 26k TPS. netfilter/conntrack is disabled on both host and guest. 

So even with the second cpu disabled I'm seeing around a 50% performance degradation vs the single-cpu VM. The results with more than 2 CPUs were very similar to the 2-CPU scenario. 

I would like to understand why this is the case (I'm certainly no virtualization expert); are additional extensions/emulations loaded when starting a multicore guest?

Update
I repeated the same test on an OS X 10.6 host on similar architecture (quad core intel i7) and the results were the same, also on VBox 4.1.8. 

I decided to extend the test to something CPU bound and ran a Linpack benchmark (single thread), but the results are unaffected by number of vCPUs (which is good). And so I also ran a a disk read benchmark using hdparm, and this was also unaffected, so this seems to be confined to network performance for now."	james little
14591	Critical Error - Failed to create VirtualBoxClient COM object	Linux	VirtualBox 5.0.4	defect	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
13752	VM freezes after leaving Haiku operating system running for several hours	Linux	VirtualBox 4.3.18	defect	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
4214	VirtualBox 2.2.4 and bonded host interface with guest bridge networking	Linux	VirtualBox 2.2.4	defect	2009-06-11T08:31:59Z	2015-08-13T17:06:54Z	2015-08-13T17:06:54Z	"My host has two Gigabit NICs. It runs on 64 Bit Ubuntu 8.0.4.2 Server. I have bonded the two interface to become bond0.

I created another guest using 32 Bit Ubuntu 8.0.4.2 Server and configured it to be bridged with bond0.

It seems to work for a while, but halfway through the guest networking stops responding (could not ping to the network gateway or access the Internet from the guest). The host network works well as I was accessing the guest through remote desktop."	John Huong
2760	Feature request: direct tun/tap support not available since 2.1.0	Linux	VirtualBox 2.1.0	enhancement	2008-12-17T19:17:21Z	2015-05-19T17:36:20Z	2015-05-19T17:36:20Z	"It was very nice that virtualbox supported the direct usage of tun/tap interfaces and NOT used another driver which means one more possible point of failure or incompatibility. That was a major advantage compared to other virtualisation systems (vmware for example). Now there is possibly a ""double bridge"" (on in the ""filter driver"" and one in the working and very stable kernel mainline bridge code) which means double work, possibly worse performance.

Why reinvent the wheel? Please readd direct tap support again!
"	M. Schinkel
13578	Option to disable the USB device filters	Linux	VirtualBox 4.3.18	enhancement	2014-10-31T12:18:10Z	2015-03-21T21:47:42Z	2015-03-21T21:47:42Z	To activate USB devices on the guest they must be either registered in the USB device filter list or the device must be manually activated in the guest. Probably there could also be an option that disables the USB device filters which would cause that all USB devices would automatically be avtivated on the guest.	Sworddragon
544	Full Screen shown behind kicker	Linux	VirtualBox 1.4.0	defect	2007-08-08T08:20:25Z	2015-03-20T22:14:14Z	2015-03-20T22:14:14Z	"Host machine: Slackware 12.0, KDE 3.5.7

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

I'll attach screenshot which I think explains everything."	AbsintheSyringe
3883	Moving VM window status bar to the top of the window would save space	Linux	VirtualBox 2.2.2	enhancement	2009-04-30T00:05:24Z	2014-12-03T15:23:56Z	2014-12-03T15:23:56Z	Is it possible/feasible to move the status bar icons from the bottom right of VM windows to the right side of the menu bar? That would save space, allowing a larger guest desktop size for a given VM window size.	Donuts
8985	Use 'addgroup' instead of 'groupadd' in installer	Linux	VirtualBox 4.0.8	defect	2011-05-29T05:57:03Z	2014-02-27T17:32:49Z	2014-02-27T17:32:49Z	"When testing one of the generic Linux builds (e.g. 'VirtualBox-4.0.8-71778-Linux_x86.run') on a minimal distribution that lacks the 'groupadd' command the 'vboxusers' group will not be created.

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

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

After checking a few of the ""big"" (or should one rather say ""bloated"") distributions (e.g. Natty Narwhal or FC-14) I've realized that not all are having 'addgroup' in their base, so first a check of the availability of the respective command would be required."	maronz
12635	Can't import to different basedir	Linux	VirtualBox 4.3.6	enhancement	2014-01-22T21:03:11Z	2014-01-22T21:03:11Z	2014-01-22T21:03:11Z	"It's nice to have --basedire option for cloning, and the very same option would be quite useful also when importing OVF or other formats.

Otherwise, to move my VM to the correct basedir I first have to import it,  clone --basedir , and finally remove the old copy.

Not very straightforard"	Alex
6049	JACK audio support for Virtualbox (Linux host)	Linux	VirtualBox 3.1.2	enhancement	2010-01-21T15:16:26Z	2013-04-01T04:56:32Z	2013-04-01T04:56:32Z	"It is difficult to use audio from one or more Virtualbox VMs and other applications simultaniously. Or to route the audio stream between VMs and applications.
Virtualbox currently supports OSS, ALSA and pulseaudio. While the pulseaudio implementation on many distros (Ubuntu) is buggy and difficult to configure, OSS and ALSA usually do not support multiple applications using the audio device at the same time.
I suggest additional support for JACK (Jack Audio Connection Kit). JACK is a well established soundsystem that many (semi)professional audio users use."	mark_orion
11333	configure script rejects --prefix	Linux	VirtualBox 4.2.6	defect	2012-12-26T07:05:03Z	2013-02-05T12:01:26Z	2013-02-05T12:01:26Z	"as far as i can see, there is no way to teach vbox' configure script the used prefix.

sabotage linux uses """" (empty, i.e. ""/"") as prefix. there is no /usr."	John.Spencer
8769	VLAN tagged packets mangled on bridged adapter	Linux	VirtualBox 4.0.6	defect	2011-04-22T22:05:14Z	2013-01-14T13:43:24Z	2013-01-14T13:43:24Z	"A guest that is bridged to a physical adapter on which VLAN tagged packets (ethertype 0x8100) are received, the packets arrive in the guest without the VLAN tag.

I will attach a Wireshark packet decode of a frame as seen from the host and the guest for review."	Kevin Otte
7142	SHUTDOWN=acpibutton fails to wait for shutdown of headless/vrdp guest with parrallel boot activated on host	Linux	VirtualBox 3.2.6	defect	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
11104	Ubuntu Quantal package: migrate from libpython2.7 to libpython3	Linux	VirtualBox 4.2.2	enhancement	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
11029	/etc/init.d/vboxautostart-service stop has no effect	Linux	VirtualBox 4.2.0	defect	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
8279	Use FreeRDP instead of rdesktop	Linux	VirtualBox 4.0.2	enhancement	2011-02-05T18:35:53Z	2012-03-11T08:52:55Z	2012-03-11T08:52:55Z	"In the Linux version, a modified version of rdesktop is included. The rdesktop project has been dead for quite some time now, at least I haven't seen many changes and improvements recently.
Even though rdesktop works, freeRDP is more active in development and has more features currently.

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

Please evaluate this new RDP client and include it in the next major version if you decide to include it."	Sasquatch
10222	Please implement readPhysicalMemory or a raw memory dumper	Linux	VirtualBox 4.1.8	enhancement	2012-02-07T01:46:11Z	2012-02-22T12:45:28Z	2012-02-22T12:45:28Z	"Hello,

We are studying the use of VBox in a forensic course. However, the access to VM memory is critical.

I found many references at the forum about people trying to get the VM memory contents. However, no one provided a solution. I still can get the memory, treating it as a real machine, but that would taint the VM memory with the memory dumper. The best solution would be to collect the VM memory using the VM solution resources, specially in a paused state. The best solution would be to have a simple read function that could access a Snapshot.

The VBOX SDK guide describes the function readPhysicalMemory and notes that it is not developed in 4.0.0. We are already in 4.1.8 and it is still not imeplemented. I got this error message when running a python script that calls this function:

 0x80004001 (Method ReadPhysicalMemory is not implemented)

Please, could you please provide the implementation of this function in the next vbox release. Alternatively, this could be implemented in a VBoxManage debugvm option, specially if considering snapshots. The needed function is a raw VM memory dump.

Vmware Server/Workstation, for example, stores the memory in a flat vmem file. Libvirt has the virDomainMemoryPeek API function. Just Vbox lacks at this point.

Thanks,"	Luiz Angelo Daros de Luca
9791	Improved support for Ubuntu Unity	Linux	VirtualBox 4.1.4	enhancement	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
8070	Less reliance on absolute paths in VirtualBox	Linux	VirtualBox 4.0.0	enhancement	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
9430	Fedora15 does not hook into my wireless connection	Linux	VirtualBox 4.1.0	defect	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
9353	Seamless mode is broken on Linux host with Openbox and composite manager	Linux	VirtualBox 4.1.0	defect	2011-07-30T18:36:12Z	2011-07-30T18:43:07Z	2011-07-30T18:43:07Z	"Seamless mode is completely broken with any composite manager enabled while using Openbox. I have tried using compiz as its own wm and seamless mode works fine on the same machine. 

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

I am using kernel 2.6.39 on an Archlinux x64 host. The guest is Windows xp. Both 3d and 2d are disabled for the guest. I am also attaching the vbox log in case it has something useful to show. "	rsk02
9219	Shared Folder Enhancement	Linux	VirtualBox 4.0.12	enhancement	2011-07-17T21:35:30Z	2011-07-18T06:52:38Z	2011-07-18T06:52:38Z	"Would it be possible to implement a feature for Windows guests in the Shared Folders to allow a user to define the drive letter for the auto-mount to use when mapping the shared folder? This could also be useful for Linux guests being able to set where you want the shared folder to be mounted.

Thanks!"	TheShiv
9087	"Linux: Please optimize output of VBoxHeadless in ""top"""	Linux	VirtualBox 4.0.8	enhancement	2011-06-17T21:05:07Z	2011-06-17T21:05:07Z	2011-06-17T21:05:07Z	"On a Linux host the ""top"" program is a great tool to see how many resources (memory, CPU usage,...) are used by various Linux processes[[BR]]
But when running multiple headless virtual machines on one physical server it's not possible to see which virtual machine is using how many resources. Instead every virtual machine process is  visible as ""VBoxHeadless"" process (which is of course in principle correct).[[BR]]

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

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

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

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

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



"	Helge Deller
9052	Have Virtual Machines create .desktop icons for Gnome 3	Linux	VirtualBox 4.0.8	enhancement	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
9041	The example python script src/VBox/Frontends/VBoxShell/vboxshell.py	Linux	VirtualBox 4.0.4	defect	2011-06-07T12:24:55Z	2011-06-09T09:10:18Z	2011-06-09T09:10:18Z	"The example python script src/VBox/Frontends/VBoxShell/vboxshell.py, has the ability to save screen-shots. When no file-name for a screen-shot the takeScreenshot function writes the screen-shot to ""/tmp/screenshot.png"".
Potentially ""/tmp/screenshot.png"" could be a symbolic link to another file. The other file would be over-written if a user saved a screen-shot without specifying the file-name."	ra
8819	Keyboard layout 'Programmer Dvorak'	Linux	VirtualBox 4.0.6	enhancement	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
8764	Regression: VirtualBox and VM configuration broken if VM folder exists	Linux	VirtualBox 4.0.6	defect	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
8637	Inappropriate Runlevel for openSUSE 11.4	Linux	VirtualBox 4.0.4	defect	2011-03-27T13:01:30Z	2011-03-27T13:01:30Z	2011-03-27T13:01:30Z	"/etc/init.d/vboxdrv and /etc/init.d/vboxweb-service contain runlevel 4 
in the openSUSE 11.4 RPM package, however, runlevel 4 is not used at all 
in openSUSE and thus leads to errors when trying to change any of the 
runlevel scripts.

- No Log-Attachment needed for this -"	Michael Kromer
6600	VBoxService.exe does not terminate in os/2 guest	Linux	VirtualBox 3.1.6	defect	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
7773	USB does not work with NIS or LDAP login	Linux	VirtualBox 3.2.10	defect	2010-11-29T11:29:03Z	2010-11-29T11:29:03Z	2010-11-29T11:29:03Z	"When users are authenticated via NIS or LDAP and uid and gid are provided via NIS or LDAP ordinary users can not mount USB devices in guests onless the provided uid and/or gid are identical on the host and the provided uid and gid from NIS or LDAP.

The problem is that when a user is installing Virtualbox the installation script apparently scans the local group and passwd files and if user and group vbox* is not found then these users and groups are created locally and the information created is used in the following installation process."	Michael Rasmussen
7419	SSH tunnel headless mode	Linux	VirtualBox 3.1.8	enhancement	2010-09-02T19:54:43Z	2010-09-04T08:27:30Z	2010-09-04T08:27:30Z	Emulation of a Headless Virtual Machine through Supression of any standard Drawn Display, where I would perform all operations through an ssh tunnel.	shiny
7407	feature request - double-click action in main window customizable (i.e. open settings instead of starting vm)	Linux	VirtualBox 3.1.8	task	2010-08-31T22:25:07Z	2010-08-31T22:25:07Z	2010-08-31T22:25:07Z	"just a feature request. i would like it if the double-click action in the main gui window were customizable (i.e. i could open wm settings instead of starting vm, useful perhaps if i were tweaking settings alot to fine tune things, or swapping a bit of storage media while the vm's are down)

""shiny"""	shiny
4134	Host Only Networking: Route Connections	Linux	VirtualBox 2.2.4	enhancement	2009-05-30T12:49:28Z	2010-05-31T06:50:17Z	2010-05-31T06:50:17Z	"To make host-only networking more user-friendly add the folwing configuration options to
File -> Global Settings -> Networking -> HostOnly Networking Connection -> Change.

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

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

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

Keep in mind that virtualbox is used often on laptops - therefore the networking settings are changeing
i.e. if you are at home (using wlan) or at work (using ethernet).
"	Marc Schoechlin
3236	hostif networking doesn't work when link is down	Linux	VirtualBox 2.1.2	enhancement	2009-01-30T17:15:04Z	2010-05-03T17:44:31Z	2010-05-03T17:44:31Z	"I route traffic from eth0 to wlan0, and use hostif eth0 for VirtualBox. If no devices are physically connected to eth0 (and turned on), the kernel reports 'eth0: link down', and virtualbox networking doesn't work. When a devices is on and connected to eth0, the kernel reports 'eth0: link up', and virtualbox networking starts working. If I disconnect the device from eth0 it stops working again.

I could just use wlan0 hostif instead, but then it's difficult to filter the traffic, run my own DHCP server, etc. Also I already forward eth0 to wlan0 for physical devices, and it makes sense to use the same setup for virtualbox."	Bryce Allen
6514	Host only interfaces and DHCP servers show strange behavior	Linux	VirtualBox 3.1.6	defect	2010-04-09T09:45:04Z	2010-04-09T10:00:59Z	2010-04-09T10:00:59Z	"I am using the PHP web api to create a few host only interfaces and dhcp servers for them. 

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

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

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

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

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

Am I missing something or is there something wrong here?"	Sm0k1n
5624	PXE does not work with virtio	Linux	VirtualBox 3.1.0	defect	2009-12-01T15:48:04Z	2009-12-01T18:53:54Z	2009-12-01T18:53:54Z	"Hello,

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

Unknown Ethernet controller! Aborting PXE boot...

The workarround is to revert to the old nic (intel/pcnet)"	Luiz Angelo Daros de Luca
4804	creating directories with umlauts in a shared folder fail with error 0x80070057 on Windows Host	Linux	VirtualBox 3.0.2	defect	2009-08-18T15:42:26Z	2009-08-18T15:42:26Z	2009-08-18T15:42:26Z	"A) cannot create folders with umlauts in a shared folder within a Windows Server 2008 guest.
(probably windows guest in general...)

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

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

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

I'm using virtualbox-bin 3.0.2 

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

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


GUESTS:

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

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

"	rottex
4678	Linux host running on MacBook Hardware: Default release key should be left-winkey	Linux	VirtualBox 3.0.4	defect	2009-08-05T02:03:49Z	2009-08-05T08:16:12Z	2009-08-05T08:16:12Z	"Here's a simple one:

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

However the same decision isn't taken when you run on Linux (or, I imagine, Windows,) running on a MacBook. It'd be neat if the installer would figure out that we're on an Apple device and set the release key to something different!"	Chris Smowton
4635	Allow remapping of parallel port addresses	Linux	VirtualBox 3.0.2	enhancement	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
2736	It is impossible to set a user's font table for text output in a graphics mode	Linux	VirtualBox 2.0.6	defect	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
21354	"Blue Screen when I run any virtual machine in ""Normal Start"""	all	VirtualBox-7.0.4	defect	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
19634	vboxweb.cpp fails to compile with gSoap 2.8.103	all	VirtualBox 5.2.34	defect	2020-06-01T02:30:10Z	2020-09-07T11:24:50Z	2020-09-07T11:24:50Z	"It appears gSoap 2.8.103 change the soap_socket_errno macro used by src/VBox/Main/webservice/vboxweb.cpp

{{{
kBuild: Compiling vboxsoap - /wrkdirs/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.34/out/freebsd.amd64/release/obj/webservice/soapC-3.cpp
/wrkdirs/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.34/src/VBox/Main/webservice/vboxweb.cpp:947:38: error: called object type 'int' is not a function or function pointer
                       if (soap_socket_errno(soap.master) == SOAP_EINTR)
                           ~~~~~~~~~~~~~~~~~^
}}}

From gSoap 2.8.103 gsoap/stdsoap2.h:


{{{
#ifdef WIN32
# ifdef UNDER_CE
#  define soap_errno GetLastError()
#  define soap_socket_errno GetLastError()
#  define soap_reset_errno SetLastError(0)
# else
#  define soap_errno errno
#  define soap_socket_errno WSAGetLastError()
#  define soap_reset_errno _set_errno(0)
# endif
#else
# ifndef WITH_NOIO
#  define soap_errno errno
#  define soap_socket_errno errno
#  define soap_reset_errno (errno = ENOENT)
# else
#  define soap_errno 0
#  define soap_socket_errno 0
#  define soap_reset_errno
# endif
#endif
}}}


"	Derek Schrock
19541	Poor disk write performance for fully allocated sparse-extent VMDKs	all	VirtualBox 6.1.6	defect	2020-04-28T22:48:04Z	2020-04-28T22:52:20Z	2020-04-28T22:52:20Z	"Using sparse VMDK disk images, VirtualBox's disk write performance drops dramatically if the ""sparse"" image is fully allocated. This was surprising and unintuitive since we figure that using a sparse image is meant to be a tradeoff where we sacrifice performance in exchange for a smaller file size. 

I've attached two 4GiB VMDKs. Both are completely empty and both are technically sparse-extent VMDKs, but one is 100% pre-allocated and the other is 100% unallocated. If you attach these VMDKs as second and third disks to an Ubuntu VM running on VirtualBox and measure their write performance (using dd to write to /dev/sdb and /dev/sdc, for example) the difference in write speeds is clear."	vorteil-alan
19500	VirtualBox should now prohibit assigning all physical CPUs to a VM and/or fix VirtualBox CPU assignment manual	all		defect	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
18893	Enhancement: CLI flag to sleep host for N seconds	all	VirtualBox 6.0.10	enhancement	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
18666	feature request	all	VirtualBox 6.0.8	enhancement	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
18661	Audio ouput is obfen disabled at start up since VBox 6	all	VirtualBox 6.0.8	defect	2019-05-20T14:43:29Z	2019-05-20T14:43:29Z	2019-05-20T14:43:29Z	"Hello,

Reproduced on the following host OS:
- Windows 10 latest update
- Debian 9 ""Stretch""

Tested guest OS:
- Debian 8
- Debian 9

I'm a blind person so I rely only on sound so me and other people using sound (included many other blind people) I know has confirmed this issue to me.

Steps to reproduce:
1) Download the Debian 8 iso here:https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/archive/8.11.0+nonfree/amd64/iso-cd/firmware-8.11.0-amd64-netinst.iso
2) Create de Debian 64 bits virtual machine
3) Configure the sound control on Intel and check if enable audio output is checked
4) Boot on the Debian installer
5) On the first screen choose install with speech (press s and enter with keyboard)

Result:
No speech

Expected result: 
speech

7) Disable and then enable audio output on the fly

Result:
Speech

Note: The issue also exists on installed OS but I've give the easiest way to reproduce it
Note2: The issue doesn't appear on Virtualbox 5.2
Note3: The issue doesn't appear on a physical machine

Best regards,
Alex."	alexarnaud
18654	Todas as Máquinas Virtual Apresentando:  Código de Resultado:  E_FAIL (0x80004005)	all	VirtualBox 6.0.8	defect	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
17735	Guru crash with Redox 0.3.5	all	VirtualBox 5.2.10	defect	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
17348	Virtualbox built-in debugger does not work	all	VirtualBox 5.2.0	defect	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
17271	New OS icon for ArcaOS	all	VirtualBox 5.1.30	enhancement	2017-11-14T01:17:04Z	2017-11-14T01:19:49Z	2017-11-14T01:19:49Z	I have the following icon to submit for ArcaOS (OS/2 distro).	Lewis Rosenthal
12167	Security Tab is missing in shared folders	all	VirtualBox 4.2.18	enhancement	2013-10-08T03:09:04Z	2017-02-13T01:40:27Z	2017-02-13T01:40:27Z	"When you open properties of file in shared folder (via VirtualBox sharing), it's security tab is missing. This produces problems when you want read ACL of that file so applications that need such capabilities (like Visual Studio) get an exception trying to access file placed there. I suggest that files in shared folder will have permissions for all to read or to modify according to the settings of that folder.

I post 2 screenshots: the first of VirtualBox shared folder and the second of folder shared via SMB protocol."	Hopungo
15361	HDA fails to restart when LPIB == CBL	all	VirtualBox 5.0.18	defect	2016-04-27T12:29:27Z	2016-04-28T12:11:42Z	2016-04-28T12:11:42Z	"The HDA spec describes LPIB as:
Link Position in Buffer (LPIB): Indicates the number of bytes that have been
received off the link. Since this register reflects the number of bytes that have
been received into the current buffer, for the first buffer SDnLPIB will count from
0 to the value in the Cyclic Buffer Length (SDnCBL) register, inclusive. For
subsequent buffers, SNnLPIB will count from a value of 1 to the value in the
Cyclic Buffer Length register, inclusive.

There seems to be a problem with hdaStreamGetTransferSize() such that when LPIB is the same as CBL and the DMA is stopped, it will not restart. I think that hdaStreamGetTransferSize() should behave as if LPIB is 0 when it has the value of CBL.

I'm using an RTOS called INTEGRITY when I encountered this, but I think that this could happen for any guest which stops and restarts the streams. I would think that it is relatively likely that LPIB could be the same as CBL as the natural time to stop the stream would be following an IOC event."	Julian Day
14754	OS/2 virtual machines crashes when pressing Ctrl-Alt-NumLock or Ctrl-Alt-F10 and restarting	all	VirtualBox 5.0.8	defect	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
13601	multiple keyboard related issues	all	VirtualBox 4.3.18	defect	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
11297	poor entropy performance	all	VirtualBox 4.2.4	defect	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
12106	Include Quiet Mode in VBOXGUEST.SYS	all	VirtualBox 4.2.18	enhancement	2013-09-12T21:25:43Z	2013-09-12T21:25:43Z	2013-09-12T21:25:43Z	"On the OS/2 Guest Add-ons package there is an OS/2 driver called ""VBOXGUEST.SYS"". 

This driver always shows up this message when you boot up OS/2 and it can not be removed for a clean no-message boot up.  

""VirtualBox Guest Addition Drivers for OS/2 version 1.6.51
Copyright (C)2008 Sun Microsystem, Inc.

My suggestion is to do not show any message on boot. Only show a message if there is an error loading the driver. 

Include the /V (verbose) mode to the driver to show up all the version and copyrights if the user want it. 

There is a suggestion on how to show the messages of OS/2 driver on this wiki:
http://www.edm2.com/index.php/Suggestion_for_OS/2_and_eComstation_Drivers_Arguments"	martiniturbide
11570	NPIV Support Request	all	VirtualBox 4.2.8	enhancement	2013-03-06T23:28:50Z	2013-03-06T23:29:36Z	2013-03-06T23:29:36Z	Adding NPIV support would greatly enhance testing capbilities for VirtualBox for Scenarios like running Oracle VM Server, Microsoft Hyper-V or VmWare ESXi inside VirtualBox on hosts with SAN Storage (Closed LAB). Also alot of multipath developement tests could be run this way.	efstathiou_e
11358	VBoxManage cannot resize fixed size disks	all	VirtualBox 4.2.6	enhancement	2013-01-04T02:42:52Z	2013-01-04T03:40:15Z	2013-01-04T03:40:15Z	"It shows an error instead:

VBoxManage.exe: error: Resize hard disk operation for this format is not implemented yet!

Another (easier and safer) solution would be to add a --resize option to the clonehd command of VBoxManage"	Csq
